Effective 01/31/2014, SuperTweet.Net has discontinued all operations.
With the shutdown of the public service, our focus will shift to supporting the open-source version of the proxy: Open-source Supertweet Proxy
For the moment, perhaps permanently, the Supertweet Proxy has been suspended by Twitter.
We'll let you know when we have more details to provide.
SB-Projects shows you how:
The script should work fine and correctly uses the 1.1 API and JSON.
However, a few of the comments and notes are older apparently. It says that SuperTweet returns XML when in fact Supertweet is returning JSON, either proxied from Twitter or directly.
In terms of the comment that "The XML message returned by Supertweet (ignored by my script) doesn't give a clue why some tweets are skipped" isn't accurate. First, there's the HTTP response code in the first line of the response headers (like a 404 error etc). If that response code is not 2xx then there was an error. Next look for the
X-TwitterAPI-Status header. If that header is present, then the response you're getting was proxied from Twitter, meaning your tweet went to Twitter and it is now in their hands. If the
X-TwitterAPI-Status header is not present in the response, then the error was produced by Supertweet. Either way, the explanation for what went wrong will be there in the error response.
It is running on an Arduino using the SuperTweet API to access Twitter from the microcontroller.
If you like how the SuperTweet API enables such projects, please consider donating or hosting a server so we can continue to provide the service to the community - it's as easy as donating an Amazon EC2 instance or Apache/Tomcat container.