/// Twitter Plans to Choke Access to Apps It Doesn’t Approve

August 16, 2012  |  All Things Digital

Twitter isn’t going to shut off applications that it doesn’t like, but it will restrict their access to new users. The company today issued a detailed guide to coming changes to its platform, including lower rate limits and authentication and certification requirements. Most importantly, Twitter said it will require large applications to get direct approval, or else. But this punishment is hardly immediate: Twitter won’t enforce its crackdown until an app doubles its user base. Going forward, applications that have more than 100,000 users will have to work directly with Twitter. Those that already have more than 100,000 user tokens can only grow to 200 percent of their current size before they will be limited. Twitter likes developers in the left-side quadrants and the lower right. The ones in the upper right, not so much. Who won’t get approved by Twitter? You can probably guess this one! In a lengthy blog post today, Twitter VP of Product Michael Sippey laid out which types of applications Twitter likes, and which it does not encourage. Those on the hit list are “traditional Twitter clients” and syndication providers — Sippey specifically named Tweetbot and Echofon. That stance is no surprise, as Mike Isaac had recently laid out in a forward-looking post about Twitter’s goals for consistent display of tweets. Twitter had long told builders of Twitter clients that it wasn’t happy with them, but actions — well, the promise of actions out in some distant future — speak louder than words. Developers had been anticipating this particular hammer dropping for at least two months now. Twitter had indicated it would be more cutthroat by dropping a partnership with LinkedIn and picking a set of high-profile approved partners like the New York Times and Nike to participate in its big new platform play, Twitter Cards.

Read the rest here:
Twitter Plans to Choke Access to Apps It Doesn’t Approve

Leave a Reply

You must be logged in to post a comment.