Hi
I'm using the search api (for example:
http://search.twitter.com/search.rss?q=%23juventusrpp=100page=4)
I read here: http://search.twitter.com/api/ this:
We do not rate limit the search API under ordinary circumstances,
however we have put measures in place to limit the abuse of our API.
If
Hi Alessandro,
We've produced a small guide on using search that explains the search rate
limits a little more.
You can find the page here:
https://dev.twitter.com/pages/using_search
In it we say:
The Rate Limits for the Search API are not the same as for the REST API.
When using the
Hi, Max,
First of all, this is just from personal experience with my own application,
so, take it with all the necessary grains of salt about rate limits changing
based on traffic and time of day, your searches being different from mine,
etc, etc.
My experience has been that I tend not to run
Hey Max,
That looks pretty extreme! What's your use case? Why would you need to make
that much queries? Are you going to use the Search API or the website? If
you're using the API, Did you consider using the Streaming API
statuses/filter method with the track parameter?
