Hi Guys
http://code.google.com/p/twitter-api/issues/detail?id=1501
Cheers
-N
On Mar 3, 9:42 pm, Milen mi...@thecosmicmachine.com wrote:
I couldn't agree more, it's pretty lame that:
a) the rate limit method returns incorrect results
b) only rate limited requests return any rate limiting
Thanks
Ryan
Sent from my DROID
On Mar 4, 2010 5:41 AM, Nik Fletcher nik.fletc...@gmail.com wrote:
Hi Guys
http://code.google.com/p/twitter-api/issues/detail?id=1501
Cheers
-N
On Mar 3, 9:42 pm, Milen mi...@thecosmicmachine.com wrote:
I couldn't agree more, it's pretty l...
Hi there
We also thought we were not receiving the correct rate limit - however
the account/rate_limit_status method doesn't actually correctly
reflect these new request limits. Instead, you'll need to (at least,
until - or if - Twitter change this method to respond appropriately to
OAuth calls)
I reported this bug yesterday. Instead of making that extra call, why
not look at the response headers which come back with each API ACCESS
- you'll get the info you need:
X-Ratelimit-Limit = 150;
X-Ratelimit-Remaining = 133;
X-Ratelimit-Reset = 1267576025;
Andrew Stone
Twitter /
I was able to get that working. I didn't notice that those headers were
only sent for requests that counted against the rate limit.
Ryan
On Tue, Mar 2, 2010 at 6:33 PM, twittelator and...@stone.com wrote:
I reported this bug yesterday. Instead of making that extra call, why
not look at the
I just want to ask how you guys handle the following situation. And please
correct anything that is incorrect.
The user starts up your application, and they have exhausted all of their
rate limit(using another application). Your application does not know this
when it is first starting because
