Twitter Clamps Down on API, Will Affect App Devs
Aug 16, 2012, 7:35 PM by Eric M. Zeman
Twitter today detailed forthcoming changes to its application programming interface that will have a significant impact on how Twitter is used and accessed from both desktop apps and mobile apps. The three focal points of Twitter API version 1.1 will require apps to authenticate on every API endpoint, will add a new per-endpoint rate-limiting methodology, and will force developers to adhere to certain functionality and design elements in the way their apps display tweets. Twitter explained that the rise of bots and spam has led to the first new rule, which will give Twitter a lot more information about what apps are accessing its data. The second rule changes the way the number of API calls are doled out to each application. As of today, the number is balanced at 350 calls per hour for all apps, but once Twitter API version 1.1 is implemented, most apps will be reduced to 60 API calls per hour. Twitter will work directly with large organizations that need more access, and will scale them up to a maximum of 720 API calls per hour depending in the circumstances. The third change means apps will be required to link @usernames to the appropriate Twitter profile, display appropriate Tweet actions (e.g. Retweet, reply and favorite), and scale the display of Tweets appropriately based on the device. Finally, Twitter wants to certify all third-party Twitter apps before they ship on devices such as smartphones or computers. Twitter says this will guarantee that the app provides a consistent experience for device owners. Twitter said that apps or developers caught skirting these rules may have their application key revoked. Once Twitter releases API version 1.1, developers will have six months to make sure their apps adhere to the new rules.
|Twitter to developers: Drop Dead. What a shame||bluecoyote||
This forum is closed.