And here we go…
Changes coming in Version 1.1 of the Twitter API | Twitter Developers: “At the end of June, I wrote about how we’re working to deliver a consistent Twitter experience, and how we would soon introduce stricter guidelines about how the Twitter API is used. I’d like to give you more information about coming changes to the API and the migration plan while offering insights into today’s Twitter ecosystem and why we’re making these changes.”
Sad to see awesome apps get called out:
That upper-right quadrant also includes, of course, “traditional” Twitter clients like Tweetbot and Echofon. Nearly eighteen months ago, we gave developers guidance that they should not build client apps that mimic or reproduce the mainstream Twitter consumer client experience.” And to reiterate what I wrote in my last post, that guidance continues to apply today.
This is not your parent’s twitter.
“People are crazy and times are strange, I’m locked in tight, I’m out of range, I used to care but things have changed.”
Hope this is true…
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
Wow, what a day.