Loading Profile...
I'm temporarily overloading twitter!? Nuh uh!
I'm getting an error in Twitterific and Twhirl that says:
"Twitter returned a "temporarily overloaded" error. This is a problem with the server that provides tweets to Twitterrific. Please contact Twitter at http://twitter.com/help if the problem persists."
Is this due to something I am doing? I post a normal amount, less than once per hour in most cases. I noticed the problem when I first started using Twhirl, about a week ago.
"Twitter returned a "temporarily overloaded" error. This is a problem with the server that provides tweets to Twitterrific. Please contact Twitter at http://twitter.com/help if the problem persists."
Is this due to something I am doing? I post a normal amount, less than once per hour in most cases. I noticed the problem when I first started using Twhirl, about a week ago.
I’m sad
6
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?I'm getting this without even posting (just getting updates from others). I have it set to a 5 min refresh. -
Inappropriate?Hi. According to the Twitter API Documentation, the Twitter API hourly limit does not count updates.
Meaning, you can post as many updates and send as many direct messages as you want, it's not counted against the limit. Instead, Twitter only counts refreshes made by our apps. There is one call made through the API every time we do any of the following:
- refresh to see new tweets from others
- refresh to see your direct messages
- refresh to see your @replies
Those are three separate calls.
A few days ago, Twitter temporarily lowered the API limit to 20 requests per user per hour to reduce over capacity errors. (You can check the Twitter Status blog at http://status.twitter.com at any time to see what the current rate limit is.)
So if your Twhirl or Twitterific is currently set to refresh all three types of updates (updates from others, direct msgs, and @replies) every 5 minutes, you'll definitely go over the API limit, since that's:
60 mins
divided by 5 mins between requests
x 3 feeds
= 36 requests per hour2 Comments
Add a comment
This solves the problem
-
Speaking of 20 requests an hour, I so hope Twitter gets that up to at least 40 again real soon. 20 is just too little. 40 is a little easier to put up with ;) -
I have my twitterific set to update every 15 minutes with 3 feeds (updates from others, direct msgs, and @replies), which should only be 12 requests per hour. I still get this error. I'm going to try setting my updates to every 30 minutes, and see if that fixes anything.
-
Inappropriate?Chad,
The Twitter limit is at 100 requests per hour currently, so you shouldn't be receiving this error. Try changing your Twitter password - maybe another app or web app is using up your api requests and you don't even know it, or remember setting it up! -
Inappropriate?I have been running 2 instances of twitterific, one at home, one at work. they were both set to update every 15 min. I changed both of them to update every 30 min and that seems to have alleviated the problem. Or if you say that 100 requests an hour are allowed, than this might just be coincidence. I'm still occasionally getting a "timed out" error, but I think that might have something to do with my computer waking from sleep.
