If you use Twitter, you know that it’s had significant downtime recently. The Twitter team apparently figured out that the source of at least some of their problems was a Jabber client. However, they didn’t mention that they lowered their API limits to 30 authenticated requests per hour (down from 70). They also had some database issues today, so maybe that was why they decided to scale back the service. I’m happy to trade the frequency if it means more reliability, but I am curious if this is a permanent solution or something they implemented just to get them by in the short term.
Update: I figured I should give you a couple more details. I figured this out simply by using the API. After thirty requests, I got the following message “Rate limit exceeded. Clients may not make more than 30 requests per hour.”
