Here's the typical errors. Call 1 says 132 hits remaining; call 2
returns over the limit. Once an hour, call 2 slips through and returns
the right result. Otherwise, on some accounts - the rate_limit bug
blocks access. On other accounts, there is no problem at all.
Sometimes, the problem resolves on one account; and moves to another.
In my humble opinion, the bugs trace to out-of-control, unpredictable
rate-limiting statements.

Also, note reset time in seconds makes no sense.

1. http://twitter.com/account/rate_limit_status.xml

Results:
<hash>
<remaining-hits type="integer">132</remaining-hits>
<hourly-limit type="integer">150</hourly-limit>
<reset-time type="datetime">2009-08-18T17:32:14+00:00</reset-time>
<reset-time-in-seconds type="integer">1250616734</reset-time-in-
seconds>
</hash>


2. http://twitter.com/statuses/followers/scotmckay.xml
Results:
<hash>
<request>/statuses/followers/scotmckay.xml</request>
-
<error>
Rate limit exceeded. Clients may not make more than 150 requests per
hour.
</error>
</hash>

Reply via email to