Whoa! When did this endpoint become rate limited?
This wiki page seems to be stale:
It says that verify-credentials is not rate-limited.
Since this is an authenticated call, the rate-limit I guess gets applied to
the authenticating user. If the authentication is not successful, does it
get applied to the IP address? In any case, I feel the limit for this
endpoint should be accounted against the IP-address as a fall-back when the
user's quota is reached, since the verify-credentials calls by an app can
get held for arbitrarily long, if the user's quota is getting filled up by
some other call (possibly by another app).
Also, can you tell me what is the response code when the rate-limit is
reached? The wiki page says "400 error codes" in this context, but which
exact error code?
On Fri, Apr 16, 2010 at 12:34 PM, Raffi Krikorian <ra...@twitter.com> wrote:
> interesting - that's true. they would have to wait until the rate limits
> reset. i could be open to relaxing rate limits on this endpoint if somebody
> could tell me how doing so won't still have this same issue?
> On Wed, Apr 14, 2010 at 9:40 PM, Abraham Williams <4bra...@gmail.com>wrote:
>> Now that account/verify_credentials is rate limited there is no way to
>> verify tokens are valid if a user has exceded there GET limit.
>> Abraham Williams | Developer for hire | http://abrah.am
>> PoseurTech Labs | Projects | http://labs.poseurtech.com
>> This email is: [ ] shareable [x] ask first [ ] private.
> Raffi Krikorian
> Twitter Platform Team