Twitter's Relationship With Third-Party Apps is Messy -- But It's Not Over (mashable.com) 26
It's a day that developers of some of the most high-profile Twitter third-party apps have dreaded, though it's one they've long-known was coming: Twitter is finally shutting off some of the developer tools that popular apps like Tweetbot and Twitterific have heavily relied on. From a report: With the change, many third-party Twitter apps will lose some functionality, like the ability to instantly refresh users' Twitter feeds and send push notifications. It won't make these apps unusable -- in some cases the apps' users may not even immediately notice the changes -- but it's a drastic enough change that developers have mounted a public campaign against the decision.
Now, Twitter is finally weighing in on the changes, after months of publicly declining to comment on the state of third-party Twitter clients. The verdict, unsurprisingly, is complicated. The company is adamant that its goal isn't to single out these developers. The company is retiring these APIs out of necessity, it says, as it's no longer feasible to support them."We are sunsetting very old, legacy software that we don't have an ability to keep supporting for practical reasons," says Ian Caims, group product manager at Twitter. At the same time, though, the company has also made a conscious decision not to create new APIs with the same functionality. Here's how Twitter's senior director of product management Rob Johnson explains the move: "It is now time to make the hard decision to end support for these legacy APIs -- acknowledging that some aspects of these apps would be degraded as a result. Today, we are facing technical and business constraints we can't ignore. The User Streams and Site Streams APIs that serve core functions of many of these clients have been in a 'beta' state for more than 9 years, and are built on a technology stack we no longer support.
Now, Twitter is finally weighing in on the changes, after months of publicly declining to comment on the state of third-party Twitter clients. The verdict, unsurprisingly, is complicated. The company is adamant that its goal isn't to single out these developers. The company is retiring these APIs out of necessity, it says, as it's no longer feasible to support them."We are sunsetting very old, legacy software that we don't have an ability to keep supporting for practical reasons," says Ian Caims, group product manager at Twitter. At the same time, though, the company has also made a conscious decision not to create new APIs with the same functionality. Here's how Twitter's senior director of product management Rob Johnson explains the move: "It is now time to make the hard decision to end support for these legacy APIs -- acknowledging that some aspects of these apps would be degraded as a result. Today, we are facing technical and business constraints we can't ignore. The User Streams and Site Streams APIs that serve core functions of many of these clients have been in a 'beta' state for more than 9 years, and are built on a technology stack we no longer support.
Re: First the firehose, then the APIs (Score:1)
They don't want people reading their twitter feeds in chronological order and free of ads. The website and first-party apps show ads and alter the order of messages to suggest content that the company thinks the user should see. Third party apps don't interfere or give the company power over the reader. Twitter hates that, and their strategy is to get all desktop users on web and mobile on first-party apps. They honestly are trying to kill off third-party devs and lie about it at every turn.
Re: (Score:2)
They're not approving new developers (Score:2)
They are keeping the data inhouse and like another develpoer said, time to start scraping their website like a 1997 hobo
-dk
Re: (Score:3)
80% of Twitter is Bots (Score:2)
Consider The Cost (Score:2)
Re:Consider The Cost (Score:4, Informative)
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
Re: (Score:2)
They could put their ads in the streams or put requirements about the developers putting their ads in by specification. But they don't. I don't know what they're on about, but if the 3rd party apps become unusable, I won't bother with Twitter anymore. It's not like they even have a Mac app, and their apps on other platforms are marginal in quality.
Re: (Score:2)
Okay, what now. (Score:2)
Goodbye chronological timeline (Score:2)
Re: (Score:1)
Re: (Score:2)