O Twitter it is, once again, implementing changes in the way its colossal platform communicates with third-party customers and the developers of those customers are not happy with that.
The fact is, Twitter will soon remove a number of features from its API to communicate with third-party customers, effectively replacing the solution with a completely new one. The problem that this new tool, called Account Activity API, considered much more limited and not being released for testing on the developers' side; with this, two fundamental tools will leave the scene without a return: the notification support push and the automatic timeline updates (timeline) via streaming.
In other words, applications like Tweetbot and Twitterrific will soon not be able to send notifications in real time to their users, nor will they update users' timelines automatically (you can only do this manually or, at least, automatically every time). x minutes).
Obviously, because we are dealing with two very important elements in the experience of using Twitter, the developers behind some of the most popular customers of the app stores decided to create a website with a manifest, asking the social network to create some kind of solution for the problem. The website Apps of a Feather (?Uma Pena apps?) was put on the air by the developers of the Twitterrific, Tweetbot, Talon (for Android) and Tweetings apps, and it is very clear: their hands are tied and only with the help of the users a way can be found.
More specifically, the developers ask that Twitter give access to the test version of the new API and disclose what the model's value will be "Enterprise" of the tool, suitable for customers with hundreds of thousands of users who may not even be able to afford it, depending on what it is. They also request that users come up with a solution to the Twitter developer support account issue and discuss the issue on the network with the hashtag #BreakingMyTwitter, as many other customers may not be aware of the coming breakdown.
During the writing of this article, Twitter commented on the subject (it seems that the campaign already worked, huh?), Indefinitely postponing the replacement of the current API by the new model:
As always, were 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
Last year, we announced our plan to retire the Site Streams it's the User Streams, and replace them with the Account Activity API (currently in beta). We are postponing the application of this change, previously scheduled for June 19.
As always, we are committed to providing a broad window for migration. We will provide at least 90 days notice prior to the date of application when the Account Activity API is available to all developers. We will give more details soon.
The developers have not yet commented on the announcement, but I suspect that the problem is not yet solved after all, it seems, the new API in all ways more limited than the previous ones.
Let's see how this story unfolds