Re: [twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-18 Thread Matt Harris
Hi Brian, The rate limit for the Streaming API restricts the amount of data you can receive, which is defined by the level of access granted to you. When using the Streaming API filter method we will apply your track/follow/geo parameters (predicates) in equal weight to the Tweets captured during

[twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-11 Thread Brian Maso
Hi Matt, Thanks for the explanation. I will file the bug report. I'd like to hear more about the sample size. I've read through the Streaming API docs a lot, and I haven't come across anything specific about the rate limits. Where can I read more? Brian Maso On Jan 10, 5:24 pm, Matt Harris wrot

Re: [twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-10 Thread Matt Harris
Hey Brian, When you use the Streaming API filter method we will stream to you all the Tweets which match your track terms - up to your allowed sample size. What this means is over the course of a sampling window we apply your track terms to the full firehose, and then return as many results as yo

[twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-10 Thread Brian Maso
Sounds consistent with what I've been seeing. Where did you get your impression of how the streaming API is "optimized"? I am having a hard time finding any authoritative documentation describing what the powers that be at Twitter *intend* to be included in the stream (as opposed to what they actua

[twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-09 Thread Bess
Streaming API is build by Twitter while Search API is build by Startup Summize acquired by Twitter. Search API is rate-limited. If you just use Twitter search feature, you may see everything. Using Search API to display API returned results is limited by your developer API. Streaming API may not

Re: [twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-09 Thread M. Edward (Ed) Borasky
On Sun, 9 Jan 2011 14:29:12 -0800 (PST), Brian Maso wrote: What I did is opened up three separate normal browser tabs in Firefox, each using the Twitter search web interface to search for three different hashtags ("#ces", "ces11", and "nfl" -- examples of three tags that should have decent ongo

[twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-09 Thread Brian Maso
What I did is opened up three separate normal browser tabs in Firefox, each using the Twitter search web interface to search for three different hashtags ("#ces", "ces11", and "nfl" -- examples of three tags that should have decent ongoing traffic). At the same time I have an application capturing

[twitter-dev] Re: ~25% loss rate Streaming API vs. Search API

2011-01-07 Thread Bess
This is hard to believe. Streaming API is an approved API that should not have any limit. It should give you everything without any limit. On the other hand Search API has rate-limitation. Did you use any filter? On Jan 6, 9:42 pm, Brian Maso wrote: > Hi All, > > Using the Streaming API, I'm not