Unsure how Version 1.1 of the Twitter API affects SuperTweet

The SuperTweet.net API was born out of the first "OAuthpocalypse", that is, Twitter's first big change to the API in August 2010 that required all developers to use OAuth rather than basic authentication. Now, two years later, the second APIpocalypse is upon us, and this one may be the end for SuperTweet.net, we just don't know.

From the start, SuperTweet.net has operated "at the pleasure of Twitter Inc." The rules can change at any time. If you are using the SuperTweet API, you should be aware of this. And, if you haven't already heard about it, Twitter is making some changes to their API now.

No one knows for sure what apps are going to be killed by these changes yet, but a lot of people are freaking out. We, frankly, do not know yet how it affects us, but just remember the service exists "at the pleasure of Twitter Inc." and they could shut it down at any time.

We also don't know the exact timeline yet. Here's the latest from Twitter, posted August 16, 2012:

When we release version 1.1 of the API we will simultaneously announce the deprecation of v1.0. From the day of the release, developers will have six months to migrate applications from v1.0 to v1.1

So, developers will have six months from whenever v1.1 is released, which is supposed to be imminent.

Read more at Twitter: Changes coming in Version 1.1 of the Twitter API

0 Responses to “Unsure how Version 1.1 of the Twitter API affects SuperTweet”