Re: [twitter-dev] Re: Search API Irregularity
If you are using just track predicate, then u should be fine. But in general gardenhose floods u depending on the time of the day and various other factors nearly a few thousand tweets per hour on an average or something similar. But again it depends what u r consuming. My numbers could certainly differ with other who have done that in the past. but it is certainly significantly more than normal access level. Regards, Atul. On Tue, Feb 16, 2010 at 6:04 PM, TimeSnag wrote: > Are you able to tell me how many more? > > I know that current am getting about 28 tweets per second that contain > 'rt' in them. > > I estimated from the twitter.com search, that there are about 40-50 > per second, but that is assuming the twitter.com is not limited. > > Thanks > -- Regards, Atul Kulkarni
[twitter-dev] Re: Search API Irregularity
Are you able to tell me how many more? I know that current am getting about 28 tweets per second that contain 'rt' in them. I estimated from the twitter.com search, that there are about 40-50 per second, but that is assuming the twitter.com is not limited. Thanks
Re: [twitter-dev] Re: Search API Irregularity
Something just to keep in mind. Try not to postpone integration into a higher access level stream for last b'coz you might have to process A LOT (I really mean it!) of tweets. Unless well done it could be over whelming for the application to integrate with elevated access level stream. On Tue, Feb 16, 2010 at 4:15 PM, TimeSnag wrote: > Yes, I am receiving limit messages. > > I will send an email once my college project is near completion and > ready to go live. > > Thanks for Twitter's Dev Team Help! > > - Will Mulligan > Worcester Polytechnic Institute > -- Regards, Atul Kulkarni
[twitter-dev] Re: Search API Irregularity
Yes, I am receiving limit messages. I will send an email once my college project is near completion and ready to go live. Thanks for Twitter's Dev Team Help! - Will Mulligan Worcester Polytechnic Institute
Re: [twitter-dev] Re: Search API Irregularity
Are you receiving limit messages? If not, than the issue isn't with your Streaming API role, but rather how you are defining your search terms. You may need a broader predicate set to catch more of them If you are receiving limit messages, you can request a higher access level at a...@twitter.com. Please send a brief company description and your use case. There is a retweet stream, but it only provides explicit retweets, not informal RT style retweets. Also, the retweet stream is generally unavailable until we announce our commercial license framework, which should be soon. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, Feb 14, 2010 at 11:11 AM, TimeSnag wrote: > Thanks for the advice. I switched over to streaming and am getting > about 25-30 tweets/sec that contain 'rt'. > > Based on main website search, I estimate there are about 45-50 tweets/ > sec that contain 'rt'. > > So, I am only getting about 50% of the actual tweets. If I applied > for the retweet streaming api, would that give me a higher percentage > of the retweets? Or is there another way to increase that percentage? > > Thanks for your help. > >
Re: [twitter-dev] Re: Search API Irregularity
both of those are samples -- the streaming API is a sample and the search API does not return all tweets (not all tweets are indexed by search). these are the best two options for getting a sample of all the retweets, unfortunately. On Sun, Feb 14, 2010 at 11:11 AM, TimeSnag wrote: > Thanks for the advice. I switched over to streaming and am getting > about 25-30 tweets/sec that contain 'rt'. > > Based on main website search, I estimate there are about 45-50 tweets/ > sec that contain 'rt'. > > So, I am only getting about 50% of the actual tweets. If I applied > for the retweet streaming api, would that give me a higher percentage > of the retweets? Or is there another way to increase that percentage? > > Thanks for your help. > > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Search API Irregularity
Thanks for the advice. I switched over to streaming and am getting about 25-30 tweets/sec that contain 'rt'. Based on main website search, I estimate there are about 45-50 tweets/ sec that contain 'rt'. So, I am only getting about 50% of the actual tweets. If I applied for the retweet streaming api, would that give me a higher percentage of the retweets? Or is there another way to increase that percentage? Thanks for your help.
