Hi,
sounds like you really want to look into the streaming API instead.
http://dev.twitter.com/pages/streaming_api_methods#statuses-filter
cheers
-m
On Thu, Jun 2, 2011 at 1:00 PM, HRyba wrote:
> I'm developing an application that uses the Twitter Search API. The
> app searches Twitter for ma
I'm developing an application that uses the Twitter Search API. The
app searches Twitter for many (at least a couple thousand) specific
keywords in real time.
A server would be set up to get the results for the many keywords in
tweets and store them in a database that the application would access
Hi Guys,
I have an app on the App engine using the search API and it is getting
heavily rate limited again this past couple of days.
I know that we are on a shared set of IP addresses and someone else could be
hammering the system, but it seems to run for weeks without seeing the rate
limit being
Twitter team, can you please do something about the performance and
rate limiting of the Search API.
It is becoming completely unworkable. I have jumped through all the
hoops, with unique User Agents, sleeping my scripts in-between API
calls, and yet the rate limiting is just becoming more severe
