DreamnetRob's dashboard

jough replied on August 04, 2008 19:04 to the problem "Sudden timeout - 70 max something" in Twitter:

Okay, it looks like it's fixed for me now, and they've even upped the rate limit back to 100.

Thanks, Twitter!

Judson replied on August 04, 2008 18:41 to the problem "Sudden timeout - 70 max something" in Twitter:

I'm getting this now when I only run one app, manually updating...

A comment on the question "Tweet Limit Exceeded" in Twitter:

Status blog shows another increase--to 100 requests per hour. Fantastic! Am getting occasional time outs, but Twitterific is still otherwise running smoothly. – ecsalomon, on July 11, 2008 02:13

A comment on the question "Tweet Limit Exceeded" in Twitter:

Wow, I hope they're able to keep it at 70. I saw from the Twitter Development Google Group that they had initially raised it to 40 before raising it to 70. The last two maintenance downtimes must have allowed them to add more headroom. – mdy, on July 09, 2008 05:09

A comment on the question "Tweet Limit Exceeded" in Twitter:

I am seeing the same thing. I've had twitterific updating every three minutes for almost an hour and have gotten no errors. – ecsalomon, on July 09, 2008 04:53

mdy replied on July 09, 2008 03:53 to the question "Tweet Limit Exceeded" in Twitter:

Is it just me or has the API rate limit been raised to 70?!

It still says 20 in the Twitter Status blog but I'm seeing 70 on the rate_limit_status API call

mdy replied on July 08, 2008 10:27 to the question "Tweet Limit Exceeded" in Twitter:

Hello. The negative API rate limit behavior is currently logged as an open bug in the Twitter API bug tracking system.

Fwiw, the person who logged the bug says that when they change their user password, the problem gets fixed. I don't know if the fix is temporary or permanent, though.

jeffglasson replied on July 07, 2008 20:37 to the question "Tweet Limit Exceeded" in Twitter:

I turned all clients off and removed the Twitter app from Facebook - then waited until the rate limit for my account reset to 20. I launced Tweetdeck and it successfully retrieved my Tweets...once. Upon checking the rate limit again, I've found it to be "-1" and it keeps counting into the negatives each time Tweetdeck tries to retrieve! - This only happens one of my accounts. The other account I have works just fine. So frustrating.

phlegon replied on June 11, 2008 20:27 to the question "Tweet Limit Exceeded" in Twitter:

UPDATE: As completely odd as this is, after changing my password yet again to no avail, I finally did lower the number of requests per hour and just left Twhirl on . . . and it eventually worked! I don't know why one request per day was being denied, and then lowering the limit allowed 30 per hour, but that's what happened. I haven't tried Netvibes again yet, partially because I don't really use Netvibes much anymore for anything. :D

corwin replied on June 10, 2008 13:40 to the question "Tweet Limit Exceeded" in Twitter:

I've been having this problem with any twitter client I've tried for the last couple of weeks now. I've throttled the requests down to the very lowest level to no avail. I was offline the whole weekend, and still came in yesterday and was immediately given the limit exceeded message. I tried changing my password, and that made no difference at all.

bodagetta replied on May 28, 2008 05:11 to the problem "Sudden timeout - 70 max something" in Twitter:

Seems to be a major problem for me too.. I get more tweets from my app saying there's a problem with twitter than I do from my friends

A comment on the problem "Sudden timeout - 70 max something" in Twitter:

Yes, the 30 won't go down as you make API calls. It just shows the max number of API calls that Twitter will handle per user per hour. The figure that's displayed is not specific to a user, i.e., it doesn't count down as you consume your limit. – mdy, on May 28, 2008 03:34

jough replied on May 28, 2008 03:16 to the problem "Sudden timeout - 70 max something" in Twitter:

Even if the limit was ONE request per hour it's giving me the max error message after not launching Twitter.com or any third-party app for twelve hours straight.

photolarry replied on May 28, 2008 02:58 to the problem "Sudden timeout - 70 max something" in Twitter:

Seems this only happens now around the end of the hour. So I think they need to re-up the limit! There is no way I am reaching it. And the link above shows 30 even though I get an error in my app.

mdy replied on May 28, 2008 02:22 to the problem "Sudden timeout - 70 max something" in Twitter:

Twitter temporarily lowered the API limit several days ago to 30 per hour.

Twitter periodically lowers the limit to help stabilize the system (ex. during heavy traffic periods such as MacWorld earlier this year).

You can check what the current limit is through this API call:
http://twitter.com/account/rate_limit... (Twitter login needed)

I just checked it now and it returned 30.

photolarry replied on May 28, 2008 02:10 to the problem "Sudden timeout - 70 max something" in Twitter:

Twitter...this is not the solution to problems of overload.

photolarry replied on May 28, 2008 02:08 to the problem "Sudden timeout - 70 max something" in Twitter:

Same error...Error: 70 API requests allowed per hour. Thus I cannot get any updates. I am using only one client to get updates. I cannot see how its making 70 api calls...seems unlikely

photolarry replied on May 28, 2008 02:07 to the problem "Sudden timeout - 70 max something" in Twitter:

is twitter gonna fix this?

GreenSmith replied on May 28, 2008 00:59 to the question "Tweet Limit Exceeded" in Twitter:

@phlegon hmm, not sure what to tell you. You've changed it and restarted, or just changed it? Perhaps restarting Twhirl would help...What level did you set it at? Lower then 30?

A comment on the question "Tweet Limit Exceeded" in Twitter:

@GreenSmith That would only help if this were a genuine exceeding of the limit. After 24+ hours of inactivity, it STILL says that the limit has been exceeded. I don't receive a single update--the very first request that Twhirl sends is rejected. I could set it as low as it will go and it wouldn't help. :( – phlegon, on May 28, 2008 00:08