Hi,
I also have a question regarding throttling of the streaming API when
tracking keywords.
We are successfully tracking keywords and reading messages, but would
like to know when our query is too broad, and we are not receiving all
the messages, so that we can back off. We would prefer to be
You will receive limit messages when your stream is limited. They are
documented here:
http://apiwiki.twitter.com/Streaming-API-Documentation#ParsingResponses
You may need to query on a few stop words before you get the limit
messages to flow, as the proportion currently allowed is pretty large,
Hi Zac,
The filter streams are limited in the amount of data they will deliver. If
you are filtering a high-volume term (such as http), you will definitely not
be getting all results.
-Chad
On Thu, Sep 3, 2009 at 10:23 PM, Zac Witte zacwi...@gmail.com wrote:
I'm not sure the filter is
Zac,
It's possible that the track filter is missing something, but there's
probably other misunderstandings that are clouding things.
I don't know how Tweespeed comes up with their numbers, but the
Streaming API only makes available a proportion of all public
statuses. Spam accounts, for
