Thanks for the reply, things are much clearer now,
I assume that if a user on a white-listed IP has exhausted his 20k
quota, then he is still entitled with 150/hour limit which he can use
for authenticated requests on a non-whitelisted IP.
Vikas
On Dec 16, 9:26 pm, Abraham Williams <4bra...@gmai
I've filed a bug to get the documentation updated.
It could be phrased better as 20k per user per whitelisted IP.
If you have N users on a whitelisted IP you should have N * 20k
authenticated request every hour.
Abraham
On Tue, Dec 15, 2009 at 23:52, vikas wrote:
> Hi,
> The document says "Ea
Hi,
The document says "Each whitelisted entity, whether an account or IP
address, is allowed 2 requests per hour. ",
in one of the twitter-development-talk i found this, "What you all
have been confirming is correct. The intended behavior is 20k per IP
unauthenticated, and 20k per IP *per user
The Twitter document says "Each whitelisted entity, whether an
account or IP address, is allowed 2 requests per hour.", but in
the twitter-development-talk group, i found this , "What you all have
been confirming is correct. The intended behavior is 20k per IP
unauthenticated, and 20k per IP *
Hi there,
A SWF-based app will use the viewer's IP address. A PHP script
will use the servers IP address rather than the viewer's.
Thanks;
— Matt Sanford
On Jun 11, 2009, at 11:46 AM, Germig wrote:
Sorry for this noob-question.
The search api is rate limited by IP adress. If the re
