You can test new keywords with a default access account to get an idea of their velocity, then roll it into your main account. Exactitude isn't helpful, as word frequency varies as the tweet volume varies. The limit rates are fixed and have not changed in over a year.
-John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Aug 25, 2010 at 11:04 PM, Karthik K <karthikkato...@gmail.com>wrote: > Hi, > Since there is no per keyword rate limiting in streaming api, adding one > keyword which gets lot of tweets can limit the data of low frequency > keywords. > What is the frequency at which data is limited at different access > levels?Is it constant or keeps changing? If this is known we can find the > frequency of a keyword before tracking using another stream or search api > and add it only if the sum is not exceeding the maximum. > Please confirm whether this is a good strategy for such situation? > > Thanks, > Karthik > > -- > 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?hl=en > -- 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?hl=en