David Heinemeier Hansson â€“ Twitter's descent into the extractive:
â€œI wonder how long this one will last?â€, asked the Web to his friend Email. â€œWho knowsâ€, said Email, â€œFacebook is still aroundâ€. â€œAyeâ€, nodded the Web, â€œWinter might be longer this time around, but inevitably Spring will returnâ€.
There’s been another recent uproar due to Twitter enforcing their no more than 100k token policy on newer 3rd party Twitter clients. Two of the most recents clients targetted were Tweetro for Windows 8 and Tweet Lanes for Android. Matthew Panzarino has another great piece on this issue, reacting to Marco Arment’s earlier post:
As far as other developers that are using Twitterâ€™s API to provide either a whole service or a component service inside their app, I think that itâ€™s still too murky to say whether they need to bail. Arment thinks they should, based on the way that Twitter is changing the rules about clients, but, although I understand where heâ€™s coming from, I feel that itâ€™s too early to call this one.
As of this moment, any developer working with Twitterâ€™s API, whether itâ€™s a client or another type of app that is currently in favor, canâ€™t be entirely certain about their livelihood. Right now these apps may be on a path that runs parallel to Twitterâ€™s business plan, but what happens when that path zags?
Note: You can also find me on App.net.