On every occasion where I've tested the Firehose and track terms from the Streaming API against the Tweet database and against each other, there is no loss -- all the sources match exactly. Unless there's some unusual operational instability, the Streaming API returns 100% of the tweets requested, or sends a limit message to let you know what has been dropped.
-John Kalucki http://twitter.com/jkalucki Twitter Inc. On Tue, Feb 15, 2011 at 12:50 PM, Karussell <[email protected]>wrote: > Hi Colin, hi John, > > > To increase recall, search sometimes includes keywords in followed links > and other techniques. > > This is indeed the case. and 'twitter search' is a lot in urls ala: > > http://search.twitter.com/search?q=jetwick > > that is where the big differences came from. Can I turn off this > 'feature'? It shouldn't take into account that. Although the title of > the web site should taken into account ... like it is done in > jetwick ;) > > I'll investigate for other keywords now. > > > Typically your first poll will return 100 items then subsequent polls > > will return only "new" data if using since_id and/or dedupping. > > I already removed these early tweets, of course ... > > > I also ran some tests > > with which keywords do you ran the tests? > > > For testing purposes both my poller and stream reader only output IDs > > so I can use cat, sort, uniq, wc and diff to compare results. > > Yes, I went the same way :) > > Regards, > Peter. > > -- > 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 > -- 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
