Despite six months of warning, 87% of SuperTweet API accesses are still using Twitetr API version 1.0 endpoints

Twitter started requiring oAuth on the API over two years ago (August 2010). Developers have had two-plus years to implement oAuth. We built the SuperTweet API to extend the lifetime of older apps, to give their developers more time to implement oAuth, and to provide support for small personal scripts and utilities and, especially, microcontroller environments where oAuth is impractical if not impossible. But come on. Two plus years later and many apps that are still using Basic Auth with the SuperTweet API have no legitimate reason for doing so.

Now we have another similar issue looming. Twitter announced the deprecation of the Version 1.0 API almost six months ago and, even though shutdown of the 1.0 API is imminent, 87% of  accesses to the Supertweet.net API are still using these deprecated, and soon to be disabled, 1.0 API endpoints - 87 percent! Only 11% of Twitter accounts using the Supertweet API are using the 1.1 API endpoints. 

This means that almost 90% of Twitter users that are currently using the SuperTweet API are going to find their code doesn't work anymore when the 1.0 API is shut off. Of course they will blame us. Not Twitter. Not the developer of the broken code they are using. Somehow, it will be our fault.

We're happy to continue to operate the SuperTweet API (at our expense) as long as Twitter lets us to support small personal scripts and microcontroller environments and other legitimate uses for Basic Auth. We understand that implementing oAuth may not be practical in those cases. However, it's still going to be a requirement that developers at least update their code to use the Version 1.1 Twitter API JSON endpoints.

Whether these numbers are any indication of what is going to happen across Twitter apps in general in a few weeks when Twitter shuts off the 1.0 API, I do not know. But I would not be surprised to find that a substantial portion of custom / niche apps are going to break when Twitter shuts off the Version 1.0 API, which was originally planned for March 13, 2013.

4 Responses to “Despite six months of warning, 87% of SuperTweet API accesses are still using Twitetr API version 1.0 endpoints”

  1. whizbot77 whizbot77 Says:

    Im the 87%

    Thanks for the amazing API guys. I actually use your service at least 10 times everyday. Last week I was panicking thinking twitter had broken. I have a feeling once twitter shuts down 1.0, everyone is gonna freak out just like I did.

  2. mrblog mrblog Says:

    API 1.1

    Thanks for the very kind comments @ whizbot77 It shouldn't be too hard to update your code to use the 1.1 endpoints, unless the issue is XML / RSS which Twitter no longer supports.

  3. CFSummers CFSummers Says:

    Can't speak for others, but...

    ...I gratefully use SuperTweet only to update my status with blog entry posts, so it's no great surprise I'd not bother changing to 1.1 for one-to-three updates/week. I mean, I never cared about the return (other than error/success), so its format was irrelevant. When the old update page here disappeared, I needed to change only the target page and verify my curl was using POST. Otherwise, the only change is wasting possibly twice the bandwidth in the bloated JSON return that, like the return before it, I only even "see" if it notes an error. (I'm an old guy who started with 300-baud modems where every unnecessary byte was critical, and never got over worrying about wasted bandwidth...) I understand that others may be using SuperTweet for more sophisticated applications, but perhaps they are your 11% - maybe the 87% is like me, using it only to avoid leaping through all the hoops the new monetized Twitter requires just to make an infrequent status update. Looking at it that way, using RSS/XML until it was no longer an option should come as much less of a surprise.

  4. mrblog mrblog Says:

    sounds reasonable

    We appreciate your situation @CFSummers. "Not leaping through hoops" is exactly why we built SuperTweet. But please do us a favor, and follow @SuperTweetNews so you can at least be made aware of any service updates or outages etc. We don't post too frequently from that account , so it shouldn't bombard your twitter stream. Regarding the "wasted bandwidth" of JSON vs. XML, I get where you're coming from, I'm old-school too, but JSON is the new shiny, and I can appreciate why Twitter doesn't want to support multiple formats anymore.