Hi,
I too have looked at the streaming API for our use but the
restrictions of single keywords has stopped us from implementing it.
We are also having issues in the other thread related to this issue
and almost 0 data for some of our geolocated search terms.
Nick
On Oct 12, 8:04 am,
The Location search has been VERY unstable, and uses this typical
search:http://search.twitter.com/search.atom?rpp=100geocode=38.627522%2C-90...
It's getting worse all the time!
Is this what we can expect going forward? If so, how can I follow all
20+ people we used to get tweets from on
Thanks for publishing this information. There is another thread
discussing the issue with the Geocode search not respecting the radius
of a search here:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a80db3eff77a88fe
From that thread ticket 1930 was filed on our
From that thread ticket 1930 was filed on our issue tracker which we
will update when a fix is deployed:
http://code.google.com/p/twitter-api/issues/detail?id=1930
Excellent, I hope it gets fixed while there is still time to back-fill
some of this data,,,otherwise we're going to have a
I'm seeing this problem too, but it only started today, around five
hours ago. Here's an example search:
http://search.twitter.com/search?q=near%3Aedmonton
That's returning a fraction of the tweets it was before. This problem
happens occasionally, but not usually for this long.
On Oct 7, 3:10
