Twitter Restricts Client Developers

Posted by Soulskill on Friday August 17, 2012 @12:45AM from the if-only-i-could-describe-this-with-some-sort-of-whale dept.

New submitter atsabig10fo writes "Twitter has finally released the hinted-at changes to their API, which include limiting the number of users for third party clients, per-endpoint rate limiting, and restrictions on how tweets can be displayed and posted. Twitter's Michael Sippey wrote, 'One of the key things we've learned over the past few years is that when developers begin to demand an increasingly high volume of API calls, we can guide them toward areas of value for users and their businesses. To that end, and similar to some other companies, we will require you to work with us directly if you believe your application will need more than one million individual user tokens.' Third party app developers are certainly going to be sweating these changes, and it puts the future of new development in question."

3 of 96 comments (clear)

Min score:

Reason:

Sort:

Re:Why not make several applications? by larry+bagina · 2012-08-17 01:09 · Score: 4, Informative

Twitter has to approve third party applications and can revoke your access at any time.

--
Do you even lift?
These aren't the 'roids you're looking for.
Re:*In a blandly chic conference room* by ledow · 2012-08-17 01:09 · Score: 4, Informative

Provide API keys.
Revoke API keys of programs that abuse the system.
Not really that hard. I should think API DDoS is the least of their worries, to be honest.
Re:*In a blandly chic conference room* by trnk · 2012-08-17 01:56 · Score: 3, Informative

From TFA: 'Nearly eighteen months ago, we gave developers guidance that they should not build client apps that mimic or reproduce the mainstream Twitter consumer client experience." And to reiterate what I wrote in my last post, that guidance continues to apply today.'

This language certainly goes beyond just discouraging 'bad' implementations.