Sunday, August 19, 2012

Twitter API Version 1.1 Brings More Regulation To Apps

Twitter announced that night the next version of its API, detailing its strategy for third-party services and especially its commitment to offer a consistent experience to all end users.

Once reserved for geeks, Twitter now has such an influence, particularly through the media, he is looking more than ever to gain control of its ecosystem, through the forthcoming version 1.1 of its API, which will limit the possibilities of some third party service.

 Twitter is such that end users receive the latest news, such as thematic pages and Twitter Cards opened mid-June, which promote relations with partners, enhance the attractiveness and thus the reputation of the service, and entail thereby term income.

Discouraged customers alternative

 The alternative traditional customers, such qu'Echofon Tweetbot or that are explicitly named, are no longer welcome, as they disperse users and delay the adoption of this type of functionality.  Twitter has therefore planned several measures to discourage them.

 For starters, the company will substantially limit their interest by imposing what were until now only recommendations on features and terminology to be used, and hence limiting their potential for innovation and added value.  It also will reserve the right to transmit its requirements to the editors of Popular customers, that is to say to those who will soon reach 100 000 users or those who are already beyond and that will double the number of users.  Finally, the origins of Twitter clients built some devices are more difficult to update, they in turn will be subject to prior certification.

 More supported services
 Many other third party services will however welcome: those proposing the analysis but no direct interaction with the timeline, such as Klout (phew!), and of course all those intended for professionals, more likely to generate income, including whether they allow you to publish tweets.

 Applications will be supervised more closely, however, through conditions of access to the API more strict.  More than any of its functions will be accessible without authentication, in order to reduce misuse.  Most applications will also be reduced from 350 to 60 interactions per hour per function, with the exception of clients who will benefit in contrast to an enhancement to 720 calls / hour, one every 5 s.


 Version 1.1 of the Twitter API will be published and implemented in the coming weeks.  Version 1.0 will then cease to function six months later.

No comments: