Developers have been working since June to figure out what a Twitter API restriction could look like. Now, with clearer guidelines, the floodgates have opened, and with Twitter’s announcement on Thursday afternoon came a deluge of reactions to the news. And of course, developers posted their reactions to Twitter.
Here are a variety of reactions and comments as expressed on Thursday, from many people who seem to think Twitter’s news will dramatically change the web’s landscape:
Twitter continues to cripple third party apps. The kind that helped build its ecosystem. Good one Twitter *golf clap*
— Tom Warren (@tomwarren) August 16, 2012
I will go silent on Twitter if they do not reconsider and rectify their developer restrictions. This is absolutely outrageous.
— Matthew Keys (@ProducerMatthew) August 16, 2012
From new Twitter Display Guidelines: “No other social or 3rd party actions may be attached to a Tweet.”“Send to Instapaper” not allowed?
— John Gruber (@gruber) August 16, 2012
I wonder what the level of outrage around these Twitter API changes will be? Twitter just declared war on all consumer uses of their API.
— Nova Spivack (@novaspivack) August 16, 2012
Regardless agree/disagree w new
@twitter API requirements I’m glad they ripped band aid off, gave clear guidance to devs— Hunter Walk (@hunterwalk) August 16, 2012
The sky is not falling, I’d obviously prefer that there wasn’t any cap, but the current cap is pretty huge and we aren’t going anywhere.
— Paul Haddad (@tapbot_paul) August 16, 2012
App.net just got to open up its developer Christmas present from Twitter four months early
— Chad Catacchio (@chadcat) August 16, 2012
I think I’m supposed to be outraged, but my 1st reaction to
@twitter api v1.1 is “not so bad.” bit.ly/R5s551— Gina Trapani (@ginatrapani) August 16, 2012
