thanks - I need to put more thought into this - I am inclined to feel that
at the moment that the search api will probably deliver better resuls - as
the cost of filtering thousands and thousands of records for even something
as basic as a movie called New York or Independence Day split into
We'd like to offer phrase search, or at least AND search on the Streaming
API, but we've had other priorities recently.
Note that Search is not intended for repeated automated keyword queries, and
that Search results are filtered for relevance. If you need all the Tweets,
or if you need them in
thanks john - I have not considered the implication of search results being
returned by relevance - I will give the streaming API a shot -
On Wed, Mar 10, 2010 at 2:28 PM, John Kalucki j...@twitter.com wrote:
We'd like to offer phrase search, or at least AND search on the Streaming
API, but
Hello,
Correct me if I am wrong but doesn't the streaming API has limitation that
allow me to only track 200 keywords.. and also with the added caveat that -
*Track keywords are case-insensitive logical ORs. Terms are exact-matched,
and also exact-matched ignoring punctuation. Phrases, keywords
This is correct. The general advice is to choose the most specific keyword
to track (probably locker and blind in this case), then run an
additional layer of filtering on your side. There are higher access levels
available that grant you more than 200 keywords to track.
---Mark
Hello,
I am building an application that monitors tweets about movies(for now
with... other interesting things planned). I have my id whitelisted
but I want to avoid overusing it.
The challenge that I face is that ideally I want to make full use of
the opportunity to retrieve 100 tweets per call
This sounds like a perfect use case for the streaming API. The rate limits
there are different, but in general more permissive. And because you're
doing primarily OR queries, the current track functionality seems
sufficient.
---Mark
http://twitter.com/mccv
On Mon, Mar 8, 2010 at 3:21 PM,
What would make use of Streaming for this use case a *lot* easier
would be if Twitter would export to the API more detailed information
about the Trending Topics. For example, I'd like to see more topics
than just the current number displayed, and tweets per unit time
(hourly worst case)
