[twitter-dev] Re: Search API Irregularity

[TimeSnag]

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

[twitter-dev] Re: Search API Irregularity

[TimeSnag]

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

[twitter-dev] Re: Search API Irregularity

[TimeSnag]

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.

[twitter-dev] Search API Irregularity

[TimeSnag]

I am a college student working on a project that requires me to
capture all (or as many as possible) retweets and store them in a
database.  I currently have a script setup to search for "RT" and
return 100 results per page.

What I have discovered is that sometimes, the results are a random
sample of the results.  Other times, it will actually return all the
tweets.

I know this because when the results are correct, it will return about
30-40 tweets that match my search result in each second. So the time
difference between the top tweet and bottom tweet is about 3 seconds.
This seems to be correct.
Other times.. it will return about 1-2 tweet each second and show me
about 1 minute worth of tweets.

Can someone tell me why the API will sometimes randomly display all
the tweets and sometimes display only a select few?