On Mon, Jan 11, 2010 at 9:09 AM, GeorgeMedia georgeme...@gmail.com 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
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
Thank you everyone. To quote an internet meme, you're doing it wrong
seems to be the consensus here. Your comments have shed light on the
dark areas for me.
So if I may bounce this off you to see if you've successfully pointed
me in the right direction, a new and better approach would be to:
1)
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
I understand there's a limitation on who is allowed to consume the
firehose/gardenhose? I know my app, IPs, and username are whitelisted
for the REST API but I am assuming getting access to the gardenhose
requires that I contact someone at Twitter? Or has that changed since
it is no longer in
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
Twaller.com is a service which categorizes location based tweets
particularly useful to travelers. You can check us out at www.twaller.com.
We search tweets based on some combinations of keywords and then
filter them out using language processing algorithms.
If you would like access to the data
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 geo
element, not the location field.
---Mark
http://twitter.com/mccv
On Sat, Jan 9, 2010 at 4:17 PM,
No one?
On Jan 4, 3:20 pm, GeorgeMedia georgeme...@gmail.com wrote:
Hello everyone!
I sure hope you can help. I am developing a web based app that
searches forlocationbased tweets using the search API with json
results. I provide the longitude latitude via my own local database on
my
On Jan 8, 9:29 am, GeorgeMedia georgeme...@gmail.com wrote:
No one?
I think you would be better off consuming the firehose, geocode the
tweets yourself, and throw away any that aren’t in regions you care
about, caching the rest for a period of time.
The thing to remember about geocoding of
10 matches
Mail list logo
