[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly

I wish someone could just check this matter. I can provide an XML file showing all ordered requests (with all params, responses, etc) with the dumb counter values showing up. Thanks Xavier On Sep 4, 11:37 am, Reivax xavier.yo...@gmail.com wrote: All requests are done authentified. Thanks

[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly

I've seen many many reports of this coming in to TweetDeck support. Rate limit exceeded when it's not really. On Sep 8, 9:26 am, Reivax xavier.yo...@gmail.com wrote: I wish someone could just check this matter. I can provide an XML file showing all ordered requests (with all params,

[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly

Hey Richard, If you get a chance to put a proxy to display all requests going out of TweetDeck, you'll easily see that 'remaining' counters sent back by twitter go wild often enough. Chances are TweetDeck users blame it on TweetDeck :( Thanks for your feedback, let's hope that will help make

[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly

According to the last api request you've done, X-RateLimit-Remaining can be user limit or IP limit (depends if you made an authentified request or not). This can explain the X-RateLimit-Remaining values you've posted. On Sep 4, 11:03 am, Reivax xavier.yo...@gmail.com wrote: I'm having this

[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly

All requests are done authentified. Thanks Xavier On Sep 4, 11:26 am, fbparis fbou...@gmail.com wrote: According to the last api request you've done, X-RateLimit-Remaining can be user limit or IP limit (depends if you made an authentified request or not). This can explain the