Twitter API, never a dull moment
The Twitter update status API is currently both working and not working. Posts are going through. However, the payload should contain the identifier for the new status message. Unfortunately, this is what we are seeing:
<html><body><h1>500 Internal Server Error</h1></body></html>
In order to prevent circular posting, we have been forced to turn off switchAbit while this is being resolved. Twitabit and Twittergram do not require the identifier and are fully functioning.
Here is the response from the Twitter team. We appreciate their transparency.
UPDATE 1:53pm EDT: Twitter is back online and so is switchAbit! Details are available in the Twitter status report.
-J
