Twitter makes changes to its API that affect third-party applications
New changes in the Twitter API confirms our suspicions: A social network of microblogging no “likes” the third-party applications, especially those that work as clients for the use of social network and to make “shadow”.
Twitter announced on their blog a series of changes in the way that developers using their API, among which include a restriction clear: Any application that accesses data from the user’s timeline, send direct messages or to make changes user settings, and has over 100,000 users, Twitter will have to request a permit to operate.
That in the case of new developments, but what about Applications like Klout, TweetBot, UberSocial, Echofon, Storify … already in operation, require access to the data to and have more than 100,000 users? As Twitter’s blog clarify that these will not escape the restriction: Doubling the number of current users should contact Twitter and ask yourself “permission” to work.
What do you look Twitter with this move? Particularly I think is a way to monetize your business. We know that one of the problems of the social network of 140 characters is that there has been a profitable business model, while there are applications based on Twitter that yes they have succeeded … The measure then suggests that this ” permission “that Twitter will be given upon payment of a specified amount by way of grant by the use of its API.
However, in the same post on his blog, social network shows that I leave the chart above, and explains what kind of applications you want to drive, highlighting their interest in having to do with the business use, they serve such as CRM or to measure the influence of certain users for example.
Instead, they are like “customers” and they remember or mimic the operation of Twitter should be left to develop, we should even be disappearing … And remember that in the post 18 months ago it was recommended that this type will not develop applications that are used to virtually the same as the network.
So, as to request an “authorization” if you have an application with more than 100,000 users then it may be a strategy to “guide” to developers. Clearly, the blue bird is not willing to tolerate someone to give you shade … at least without paying.
Anyway, I have to wait to see how this process unfolds, as Twitter has given deadlines for applications to make the necessary changes.
If the suspicion is true of the “license” that want to charge, then maybe we’ll see that many Twitter based applications that are free and begin to collect, or to disappear, while those charged simply try to raise the price to pay to Twitter and still be profitable for their developers. Matter of waiting.
Link: Changes coming in Version 1.1 of the Twitter API (Twitter Blog)Tags: API, Applications, changes, limitations, third, Twitter