SuperTweet.net - At what point is it not a "corner case" anymore?

The SuperTweet.net MyAPI Proxy began as a solution suggested by the friendly @twitterapi team when I asked about how Twitter could handle devices and microcontrolelr platforms that didn't have the resources for OAuth:

Why not have the controller proxy through a full-featured webserver that can oAuth in to Twitter?

John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.

They referred to this problem as a "corner case" and marked it as "won't fix".

On the one hand, I understand where Twitter is coming from on this. They process billions of requests per day on their API and Basic Auth wasn't giving them the control they wanted. On the other hand, there is clearly a real need here. We're now proxying about three-hundred-thousand API requests per day on SuperTweet.net. That may not seem like a big number, but keep in mind that Twitter has millions of investment dollars to use to operate their infrastructure, while SuperTweet.net is paid for and operated entirely by a few volunteers.

SuperTweet.net is helping Twitter retain these apps (and the users using those apps)  - without SuperTweet.net most the apps using the service would die and their value to the Twitter users using them with them. These SuperTweet.net apps affect about 1.4 million users, with that number growing about ten percent per month.

At some point, this is no longer just a "corner case" issue is it?

0 Responses to “SuperTweet.net - At what point is it not a "corner case" anymore?”