Twitter has officially announced the changes coming to version 1.1 of its API, and the news is mostly bad. While some new rules are ostensibly aimed at reducing the number of bots and spam accounts on the service, they also severely restrict how much and how often third-party Twitter clients and other services can access Twitter's information.
Among the most damaging of these new changes for third-party developers is the evolution of Twitter's Display Guidelines into Display Requirements. Developers are currently allowed some leeway in how they present Tweets, but the new requirements will enforce a number of design decisions that may make it more difficult for third-party clients to differentiate themselves from both the official Twitter clients and one another. Twitter also continues to discourage (though not prohibit) developers from creating applications that "mimic or reproduce the mainstream Twitter consumer client experience." The company even went so far as to call out Tweetbot and Echofon, two major third-party clients, as applications that developers shouldn't be making.
Even worse, Twitter will now require any third-party Twitter application preinstalled on a device to be "certified" by Twitter. The post doesn't go into detail about what exactly that process will entail, but anyone who ships a third-party Twitter application without first getting it certified risks having their application key revoked. Applications that serve a large number of users—more than 100,000 for new applications, and twice their current user count for existing applications—will now need to ask Twitter for its blessing to continue adding new users.
Read 3 remaining paragraphs | Comments
DIGITAL JUICE
No comments:
Post a Comment
Thank's!