DOS Attacks on SuperTweet API

Feb 12, 2013 by SuperTweetNews

Not absolutely sure if these are intentionally malicious or just a swarm of new users with lots of bugs in their code (I suspect it is intentional attacks on SuperTweet).

Either way, the end result is that the service has been affected and may continue to be. I really don't have time for this people. The SuperTweet API is a service that we run for the community OUT OF OUR POCKETS to help people. But if this keeps up, we will have to shut it down.

SuperTweet API now supports version 1.1 of the Twitter API

Sep 7, 2012 by SuperTweetNews


Important Notice: Effective September 7, 2012 Twitter has released version 1.1 of the Twitter API. The API now supports v1.1 of the Twitter API.
At the same time, version 1.0 of the API is officially deprecated. XML and RSS formats are no longer supported in the v1.1 API. Twitter is providing a 6 month window before turning off v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be available. As a result, the v1.0 API endpoints will no longer be available through the API at the same time they are removed at Twitter.

Unsure how Version 1.1 of the Twitter API affects SuperTweet

Aug 28, 2012 by SuperTweetNews

The 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, we just don't know.

From the start, 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

Twitter was down for about an hour today

Jun 21, 2012 by SuperTweetNews

It hasn't happened in a long time, an apparent total service outage of Twitter. These were a pretty common occurrence in the early days, circa 2007, but Twitter has been much more robust for quite a while, where outages are usually isolated to some sub-set of users/features and they don't take the whole service down.

I feel for the engineers and operations staff that have to deal with these problems. I've been there. It's not fun. Very few of us have ever had to deal with the volumes Twitter is dealing with. It's not the same as running your own little Apache PHP server, folks. Anyway, the service appears to be coming back on-line again now and the API right along with it.

One thing we discovered with this outage, is that SuperTweet is currently totally dependent on Twitter, even to provide outage information and status information on Twitter itself (including this Blog which is integrated with Twitter). Oh well, that's probably something we will just live with for now, unless these kinds of total Twitter outages become more frequent.

Approximate time of outage:

started around 9:15am Pacific time (16:15 GMT)

ended around 10:15am Pacific time (17:15 GMT)

Twitter is making changes to the API. Ensure your SuperTweet apps are ready.

May 14, 2012 by SuperTweetNews

Twitter is going to shut off old end-points and deprecate other "unsupported" APIs. Since the API is a simply a proxy for the Twitter API, your apps will also need to comply with these changes to the Twitter API.

Twitter had originally set May 14, 2012 as the day they would begin enforcing these updates, but they recently indicated that the plans have changed as a result of "feedback" (angry screaming customers) and Twitter is now saying the new plan is to "more incrementally phase these deprecations over the next several weeks."

See Twitter blog post for more details: API Housekeeping