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? http://dev.twitter.com/pages/streaming_api_methods#statuses-filter
All the best, Arnaud / @rno <http://twitter.com/rno> On Thu, May 19, 2011 at 6:26 AM, Max <[email protected]> wrote: > Hello, for an art installation i will be having 4 cpus running the > search twitter query (search.twitter.com) . because the rate limit is > not made public, if you could authorize my proposed request frequency. > if i have each computer (on the same IP adress) calling the search api > every 10 seconds, that comes to 1440 calls per hour (from the same Ip > adress) whilst also simultaneously running the sample stream (on each > cpu) . would this be allowed? > > it would be between June 16th and June 24th, continuously during day > time hours. > > thanks alot. > > max > > [email protected] > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
