Twitter Doesnt Want Its Developers to Be Its Direct Competitors

By Todd R. Weiss  |  Posted 2012-08-17 Print this article Print


Some of the rules changes "dictate tweet layout with very little flexibility," while others are aimed at making sure that developers don't directly compete with Twitter, wrote Arment.

"Twitter has left themselves a lot of wiggle-room with the rules," wrote Arment. "Effectively, Twitter can decide your app is breaking a (potentially vague) rule at any time, or they can add a new rule that your app inadvertently breaks, and revoke your API access at any time. Of course, they've always had this power. But now we know that they'll use it in ways that we really don't agree with."

Patricio Robles, a writer for Econsultancy, wrote in a post that "the Twitter API as we know it is effectively dead" due to the upcoming changes.

"To be fair to Twitter, it has been fairly transparent about its intentions, as bad as some may believe they are," wrote Robles. "At the same time, the company's dramatic shift doesn't provide much comfort that Twitter's plans won't change going forward, leaving developers who currently think they're in the clear out in the cold."

A Mashable story, emblazoned with the headline "Twitter's API Update Cuts Off Oxygen to Third-Party Clients," said the changes could have a "drastic impact" on the company's developer base.

"The early response from some of the major Twitter client developers is one of an uneasy calm," the story reported. "Twitter has been threatening to take a harder stance against third-party clients for almost 18 months and many developers were already operating under the assumption that another shoe was about to drop. The question becomes, will these developers-many of whom have helped shape Twitter as a service and community at a fundamental level-continue to invest in the platform. Right now, it's too early to tell."  


Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel