Twitter announces restrictive API
Twitter has announced in a post on the developer's blog version 1.1 of its API. You will permit no later than March 2013 only via OAuth-authenticated requests, also will the number of calls per REST URL ("endpoint") is limited to 60 per hour. So far more than 350 API requests per hour, a total permissible. From the official release of the API developers remained six months to convert their applications.
The aim of the changes it was, at the Twitter responsible for consumer Michael Sippey explained in the blog post, to enable more enterprise applications and traditional Twitter clients to support less. They had "tremendous innovation" as seen in products, analyzed the Twitter content for Geschätskunden.
John Gruber gave Twitter on his blog Daring Fireball: "Klout, this pompous, masturbatory nonsense, should be OK, but services like Storify and favstar that are really useful or fun should suck.."
Even the Instapaper founder Marco Arment is concerned with the changes. He sums up his critique it together. "I certainly would not build a business on Twitter, and I do not think I would build, nor any non-trivial functions on it and I would be busy with Twitter clients, I would be working on a start another product. "
However, keeps the blogger and political consultant Anil Dash, the announced changes for problems - they concerned Twitter users anyway. He accused the company, however, express themselves unclear and leave too much room for interpretation
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment