Twitter is making changes to its API on June 19, and third-party Twitter clients are worried about the impact and Twitter's lack of communication about the issue.
The developers behind popular third-party Twitter apps that include Tweetbot, Twitterrific, Talon, and Tweetings today teamed up to warn users about the upcoming changes and to hopefully spur Twitter to action.
/article-new/2018/04/twitterapichanges-800x184.jpg?lossy)
On June 19, Twitter plans to remove several streaming service APIs that are used by third-party apps. Disabling these APIs will prevent third-party Twitter apps from sending push notifications and refreshing Twitter timelines automatically.
If you use an app like Talon, Tweetbot, Tweetings, or Twitterrific, there is no way for its developer to fix these issues.
We are incredibly eager to update our apps. However, despite many requests for clarification and guidance, Twitter has not provided a way for us to recreate the lost functionality. We've been waiting for more than a year.
Twitter is replacing its current streaming APIs with a new Account Activity API, which is in beta testing, but third-party developers have not been given access. With access to the Account Activity APIs, third-party Twitter clients say they might be able to enable some push notifications, but Twitter has also provided no detail on pricing. Automatic refresh of the timeline is set to be disabled entirely.
Automatic refresh of your timeline just won't work: there is no web server on your mobile device or desktop computer that Twitter can contact with updates. Since updating your timeline with other methods is rate-limited by Twitter, you will see delays in real-time updates during sporting events and breaking news.
The developers behind Tweetbot, Twitterrific, Talon, and Tweetings are asking customers to contact the @TwitterDev account to correct the situation and to use the #BreakingMyTwitter hashtag to spread awareness.
Update: Twitter has responded to customers unhappy with the changes coming to third-party apps. Twitter plans to delay the scheduled June 19th date for the deprecation of the existing APIs, and it says developers will have at least 90 days before the APIs are retired after being provided with access to the Account Activity API.
Last year we announced our plan to retire Site Streams & User Streams, and replace them with the Account Activity API (currently in beta). We are delaying the scheduled June 19th deprecation date. — Twitter Dev (@TwitterDev) April 6, 2018
As always, we’re committed to providing ample time to migrate. We will provide at least 90 days notice of deprecation date from when the Account Activity API becomes generally available to all developers. More specifics on timing to come. — Twitter Dev (@TwitterDev) April 6, 2018
Top Rated Comments
(View all)Hot take: The native app works well and the third party apps are garbage. I’ve used them and found them a subpar experience. All for this.
Even if you don't like third-party Twitter apps on iOS, there's no solid Mac alternative, which is a major problem in this situation.Hot take: The native app works well and the third party apps are garbage. I’ve used them and found them a subpar experience. All for this.
Are you just hoping to create controversy?You can't honestly be serious…
Several of the third-party apps absolutely destroy everything Twitter offers themselves
It's only more challenging because they designed it that way. They could easily make API's require ads or promoted tweets if they wanted.Twitter needs everyone to use 1st party applications because that's how they can extract the most usage data from users and most effectively deliver ads / promoted tweets. If you're on a 3rd party app, it's more challenging for Twitter to monetize you.
I've said it before but I'll say it again: If Twitter makes me use their first party app rather than a third party one I'll stop using Twitter.
I have refused for forever to use the Twitter official app. I hate it. Everything about it sucks. I'll just have to consider abandoning Twitter if the **** hits the fan like this article indicates is likely. No auto refresh alone is a killer.