If you are logging every tag ever found in your search results, and then trying to search for them continuously, you need to change your model. Twitter will no longer allow that type of access. They have made this clear through words and actions. You should focus on tracking the tags that are used most often. It is a power curve. In every set of words I have studied, 100-200 tags get 80% of the traffic. Streaming allows you to track 400 words. Limit yourself to 400 of the most used tags. Any other expectation is unreasonable.
On Mon, Feb 28, 2011 at 12:43 AM, manaf pm <manaf...@gmail.com> wrote: > I have a website which grabs tweets from twitter.com within 20 minutes > interval per day. I h ave stored thousands of hashtags in my database > and search is occurring against these hash tags and user names. Right > now there I need around 65000 search requests to be happened per day. > Here comes the rate limit problem. As a result I am not getting > desired search results for a long time. How can I over come this? Any > replies are welcome and will be helpful to me. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
