http://help.twitter.com/forums/31935/entries/66018
not all tweets are guaranteed to be in search. on top of this, i highly don't recommend using the search API for this, and instead, use the streaming API. On Sat, Feb 13, 2010 at 11:24 AM, TimeSnag <wmulli...@me.com> wrote: > 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? > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi