ashley1784's dashboard

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.

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

GreenSmith replied on May 27, 2008 21:02 to the question "Tweet Limit Exceeded" in Twitter:

@phlegon did you change your network settings on Twhirl? Changing them to 30 for me has gone from having the exact same problem you're mentioning, to none. Depending on your Twitter use, you can easilly tweak how often you get @s DMs, and Tweets each within that 30 per hour limit. Since DMs go to your email, you could make those the least frequent, and get the others quite frequently.

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

Well I, for one, am done trying to figure this out. NOTHING has my password except Twhirl. I start Twhirl about once a day, and it starts up saying that the limit has been exceeded, even though no attempt has been made for at least 24 hours. This is a problem on Twitter's end.

mdy replied on May 27, 2008 07:07 to the question "Tweet Limit Exceeded" in Twitter:

I don't think Friendfeed counts against the API limit if you have a public Twitter account. Unless things have changed since I last looked at Friendfeed, you can import tweets from a public Twitter account into Friendfeed by just providing a user name, no password.

The Twitter API documentation says that only "authenticated requests" (which I understand to mean that we have to login successfully with our password) are counted against the API limit.

Since Friendfeed doesn't ask us for our password, I believe it doesn't eat up our rate limit.

Brons replied on May 27, 2008 06:56 to the question "Tweet Limit Exceeded" in Twitter:

That's still not good enough for me. I deleted mt Friendfeed entry and my Facebook app. I had the Spaz frequency down to every6 minutes and fr the first time in 3 days brought up spaz and immediately got the rror. I changed my password, and only Spaz has it.

It still doesn't work. Something has gotta be broken here.

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

Thanks, GreenSmith! 8-) – mdy, on May 27, 2008 06:35

GreenSmith replied on May 27, 2008 05:25 to the question "Tweet Limit Exceeded" in Twitter:

Actually @mdy, that page is helpful to at least have a reference for what they current limit is. I switched to 30 per hour on Twhirl, FF still gets my tweets, and all is fine. This post lays it out very clearly for those needing to adjust to this changed API req limit: http://willfjohnston.com/2008/05/26/t...

mdy replied on May 27, 2008 03:22 to the question "Tweet Limit Exceeded" in Twitter:

D'oh! Mea culpa! I misunderstood when I read the thread about the rate_limit.

That API call actually returns the current API limit for Twitter. It's usually 70 per hour, but for various reasons, Twitter may lower the limit temporarily. That API call lets the third-party app developers check if the API limit has changed.

Again, sorry for contributing to the confusion.

Jeff replied on May 27, 2008 01:22 to the question "Tweet Limit Exceeded" in Twitter:

Doesn't look like that feature is functioning yet. I restarted Twhirl, it ran for two rounds of updates ( 12 minutes = 6 API hits) and says I've exceded the limit AGAIN. Checked and this says I still have 30 requests remaining.

mdy replied on May 27, 2008 01:04 to the question "Tweet Limit Exceeded" in Twitter:

I think it will just be a matter of time before the various 3rd-party apps add a feature where you can see what's left of your rate limit because that just became available via the API.

You can try it for yourselves by going to this link:
http://twitter.com/account/rate_limit...

Jeff replied on May 27, 2008 00:50 to the question "Tweet Limit Exceeded" in Twitter:

I'll chime in with a "me too". I have ONLY Twhirl accessing the API at this time and nothing I've done keeps it from timing out. I even have it turned down to 30 requests an hour as I heard thats what they turned the API down to. It will open up, run for a bit ok, then time right back out again.