May 23, 2013
Twitter first announced the API v1 retirement over a year ago in March 2012. By September 2012, they set the "line in the sand" date for turning off the v1 endpoints at March 5th, 2013. Then it was pushed back to May 7. Now the new date is June 22, according to the Twitter blog.
When we turned off the v1 endpoints on the Supertweet API in anticipation of the designated shutdown by Twitter, less than 10% of users were ready (apparently very few developers read the @twitterapi account or Twitter dev blogs, go figure). Twitter has been testing the shut down of the old v1 endpoints with "blackout" tests over the past several months. One would have to guess that they are not seeing much progress (still seeing too many API v1 requests) such that they aren't ready yet to risk the fallout from killing off that many apps/clients.
Eventually they are gong to have to bite the bullet or announce a permanent fall back position. This limbo mode sucks. I guess there is no prize for being a good citizen: "no good deed goes unpunished."
Mar 31, 2013
Twitter has adjusted the date for retiring the v1 API endpoints, declaring them final on their blog: The Twitter REST API v1 will officially retire on Tuesday, May 7, 2013.
It will be interesting to see the web scramble when this finally happens. I think most major Twitter apps, at least those still being maintained, have already been updated, and any issues after the final shutdown of the v1 API will be minor and resolved quickly. On the other hand, poorly maintained apps like Rainmeter, Gnometer, and Pino, as a well as a few other fringe clients, that have not even been updated to support oAuth (now a requirement for two plus years), despite being fairly popular. Those users are already off the Twitter grid and won't coming back until they get a new client or (unlikely) the developers of those clients finally upgrade them to use oAuth and the v1.1 API.
If the Supertweet API is any indicator, it's been almost a month since we shut down the v1 end-points and still almost 80 percent of requests to the service are API v1 requests. Even though those requests are failing with an error, the error response apparently goes to a black hole somewhere and the end-users are alseep at the wheel or unaware that their clients are broken.
Twitter thinks developers pay attention to their blog and Twitter account, but obviously many don't and the users of clients by those developers are going to be caught off guard when their apps stop working in May.
Mar 27, 2013
The open-source stand-alone Supertweet proxy has been updated to support the current Twitter API 1.1.
Get the source at: supertweet-twitter-api-oauth-proxy
Feb 15, 2013
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.
Feb 14, 2013
Version 1 of the REST API is now deprecated, officially. The SuperTweet API will no longer support the Version 1 endpoints effective February 21, 2013. Please revise your apps and scripts to use the 1.1 endpoints
We are making this change on the Supertweet API in advance of the Twitter shutdown of the Version 1 API to ensure that the SuperTweet API app is in compliance and no longer making use of any Version 1 API endpoints when Twitter disables them in the coming weeks.