You can apply for Gardenhose access at api at twitter dot com. We're
currently not giving out Firehose access. Watch for further announcements
about increased access levels.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Mon, Jan 11, 2010 at 2:46 PM, GeorgeMedia wrote:
> I
You should continuously consume Streaming API feeds and store the results.
Then, periodically run your algorithms over the stored set as required.
Trending will require examining more data than every 30 seconds, especially
if you are slicing by geo.
On Mon, Jan 11, 2010 at 11:51 AM, GeorgeMedia
Repeated automated queries to search isn't a complete strategy, as search
does not provide full corpus search and the rate limits are fairly low.
Trending can usually be done on Spritzer or the Gardenhose. I'd grab
Spritzer and see what you can determine by examining the Location field and
the geot
On Mon, Jan 11, 2010 at 9:09 AM, GeorgeMedia wrote:
> Is what you are suggesting to basically consume the entire firehose as
> it comes in and look for geo parameters/locations in real time? My
>
Yes, that’s what I’m suggesting. The current API features & constraints
won’t support what you’re t
Sorry for the delay on this... but when ecp said sounds like a
reasonable approach. Note that the streaming API does support
bounding box filters now. However they only work off the
element, not the location field.
---Mark
http://twitter.com/mccv
On Sat, Jan 9, 2010 at 4:17 PM, Amitab w
