Twitter API Lowers Authenticated Request Limit to 30 Per Hour
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.”
3 Comments
Comments RSS TrackBack Identifier URI
Leave a comment
Thanks much for this. I was going nuts with the near constant over limit messages on Twhirl! Despite my patience being tested, I’m staying. It’s worth it, overall, for the people, the connections, the new knowledge. Wish I knew coding and could help!
[...] Twitter’s recent change to their API means that your favorite Twitter client might not be working properly. My (not personally verified) understanding is that the IM clients (GTalk, AIM, etc.) aren’t working at all right now, and many people have been reporting problems with twhirl. Typically the user receives a message stating “limit exceeded” or something to that effect. [...]
[...] and direct messages once per hour. Remember that the original API limit was 70 requests per hour; then they dropped it to 30. This change, done without any announcement until well after it was implemented, caused trouble [...]