If you need every Tweet, you need the Streaming API.
Watch for limit messages -- if you are getting them, refine your
predicates, or apply for higher access.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Sat, Jun 5, 2010 at 4:34 PM, Bess wrote:
> What is considered
What is considered popular results (high-velocity)? high-velocity?
Any official documentation that define the differences between Search
& Stream API? in terms of result quality, data size, data rate, etc
If I would have to capture every single Tweet like someone asking for
medical emergency, sho
The stream API will have more results and will give all results versus the
search API which will sample popular results (high-velocity), but for this
case all results are available for both systems.
Jonathan
On Fri, Jun 4, 2010 at 9:12 PM, Bess wrote:
> This is related to cache. Search API resu
This has nothing to do with the cache. Speaking as a engineer in the search
group I can state that this has nothing to do with the cache.
Jonathan
@jreichhold
On Fri, Jun 4, 2010 at 9:12 PM, Bess wrote:
> This is related to cache. Search API results are from cache to improve
> performance? Sea
This is related to cache. Search API results are from cache to improve
performance? Search API is not getting the same results as Stream API?
On Jun 4, 3:12 pm, Jonathan Reichhold
wrote:
> This is actually an artifact of how retweets are displayed between
> search.twitter.com and twitter.com The