Quantcast
Jump to content

PreCentral: The Twitter 1.1 API and what it means for webOS


News Reporter

Recommended Posts

Twitter Hero

Twitter, that lovely place where we all send random 140 character snippets of news, thoughts, and rants. Love it or hate it Twitter is an important part of social networking and has played a very important part in the webOS community over the years. Some of this platform’s first great apps () were Twitter clients. Whether you’re following for the latest and greatest in webOS news or one of the many awesome developers out there you probably use Twitter even if it’s just to spectate the conversations. Due to the popularity of this social network within the webOS community we have had the blessing of many truly great third party Twitter clients over the years. Unfortunately due to webOS’ current status of uncertainty developers abandoned our treasured platform in search of ecosystems with a pulse thus abandoning or removing their apps from the webOS App Catalog.

As time moved on Twitter slowly changed their API (software components developers use to access services in a nutshell) to “better” their product. When the API changed if a developer didn’t update their app said app’s functionality would break or cease to work altogether. One quick search through the App Catalog for Twitter will result in a graveyard of apps that have been abandoned. Several months back we composed a roundup of that could still be had on webOS and unfortunately that list is about to get a bit smaller soon.

On March 5th (that’s less than a week away folks!) Twitter will begin what they call “blackout tests” for API v1 and fully retiring @Anywhere API altogether. According to Twitter’s developer site the first test will run from 9:00am 10:00am PST on March 5th. During this test they temporarily retire the old API to let developers know how their apps will be affected. After the first test more tests will be announced before, during, and after each test by . The eventual endgame is to fully retire the old v1 API for Twitter in the near future and apps need to migrate to the new API or they will be forever broken.

So what does this mean for us? In a nutshell it means that a lot of our favorite apps that developers have left behind will cease to function. So if you’re still using an app like , Bad Kitty, or to access or interact with Twitter in anyway now would be a good time to move on. We have reached out to several developers on this matter and so far we know for a fact there are a couple of diehard developers that have either updated their app already or have plans to. Here is the short list that we have been able to confirm so far (we'll be updating this list if/when other developers update their apps):

We know that list is small but we are happy to see that there are still dedicated developers for webOS out there that are dedicated to keep their apps up to date after all that this platform has been through. We thank all of them for all their hard work and urge our readers to open up the App Catalog and buy all of these apps if you don’t already have them. If the app is free get ahold of the developer and see how you can go about donating to them or at least give them a huge thank you for their continued support of webOS.

mf.gif


a2t.imgC0cl5bPk3cU

link hidden, please login to view
Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Topics

    • By yenn22
      Hi, since I think yesterday I have an issue with HBO GO - it just shows unsupported device and that is it. According to their website, WebOS 3.5+ should be supported, I have LG uh6107 and in menu it shows SW version  5.60.15, so I think it should be ok.. does anybody have the same issue?
    • By Alfvenwave
      Hi, I'm curious if anyone else is seeing this annoying new behaviour.
      I have my SKY Q box on HDMI1 and have become accustomed to switching back from Netflix (or any other app for that matter) by having HDMI1 assigned to button "1" using the Quick Access feature.  In the last week though, this feature has stopped working properly. If I am in Netflix and I press the "1" button, nothing happens (as expected). If instead I hold down the "1" button to switch to SKY I get a pop up that says this: "Do you want to add Netflix to [Quick Access 1]?".   If I then hold down the "0" button, the 3x3 grid "EDIT QUICK ACCESS" pop-up appears and I can clearly see my SKY Q/HDMI 1 in the top left grid position (button "1")!!!
      If I then switch via the Home button to HDMI1 and remove HDMI1 from Quick Access (via the  EDIT QUICK ACCESS pop up), I can then re-add it by holding down 1 or from within the pop-up. Now, if I go into Netflix and then hold down 1, my TV does (correctly) switch to HDMI1. Hurrah! If however I turn my TV off and back on, then go to Netflix, then hold down "1", I am back to square one with the question "Do you want to add Netwflix to [Quick Access 1]?"......Grrrr!!!
      I have tried switching the TV off at the wall, leaving for 10 seconds and repowering, which doesn't fix the problem (I don't believe WebOS reboots when you do this). LG appear to have made it a practical impossibility to reboot WebOS via anything other than a factory reset which I don't really want to do as it'll take me too long to get all my settings back to where I have them now. Some blogs suggest that the "User Licence agreement" setting can be changed which forces a reset from within the General tab but I don't see this on my TV (guessing that WebOS interface has changed).
      Anyone have any ideas? 
      Rob.
       
    • By Mohannad Hanafi
      I installed webOS TV Emulator v6.0.0 and when I run it, it shows a black screen like this
      It's running on Oracle VM VirtualBox.

    • By Justin Tan
      Found multiplex application that use letsencrypt stop working in 30 September 2021 on LG WebOS 3.5. This appear to be wide spread multiplex version of WEBOS. 
      See 
      AND 

      link hidden, please login to view As PLEX blaming to be LG fault. LG please provide solution to only 2 year old TV
      LG
      Our current app is available on 4K/UHD LG television models running the following system software:
      webOS 3.0 webOS 3.5 webOS 4.0 webOS 5.0 No 720p or 1080p (“full HD”) sets are supported for our current app at this time.
      Note: Due to root certificate limitations with the device OS itself, only webOS 5.0+ devices support secure connections with a personal Plex Media Server. To allow connections to a personal server, devices running earlier webOS versions must be set to Allow Insecure Connections in the TV app settings and the Plex Media Server must be set to Preferred for the Secure Connections preference.
    • By Richard Stewart
      After I complete developing lg tv app,  how other man  test  app?

×
×
  • Create New...