> The Location search has been VERY unstable, and uses this typical > search:http://search.twitter.com/search.atom?rpp=100&geocode=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 200000+ people we used to get tweets from on the location search? I'll happily create an account and manage the lists/follows... but I'm pretty sure that will get me killed, and it will only be a snapshot based on current profile location strings that we have... Sure, I could suck the *-pipe, but without a filter criteria, I'm going to be seeing all tweets from the entire universe, which seems hella-wasteful to twitter and me... Day Mentions Location Everything 2010-09-13 4985 46801 53503 2010-09-14 4719 48110 54589 2010-09-15 4779 47599 54209 2010-09-16 5143 47087 54312 2010-09-17 5256 48363 55581 2010-09-18 4888 40943 47237 2010-09-19 5871 46008 53843 2010-09-20 4990 46219 52826 2010-09-21 4444 49274 55933 2010-09-22 5364 51567 58999 2010-09-23 6866 42495 52967 2010-09-24 6191 41107 50679 2010-09-25 5673 36321 43950 2010-09-26 6784 35168 44664 2010-09-27 6346 32580 42192 2010-09-28 5448 32528 41792 2010-09-29 6038 40677 50472 2010-09-30 5964 38116 47713 2010-10-01 6615 38360 48302 2010-10-02 5612 23107 32024 2010-10-03 6728 22802 33328 2010-10-04 5528 23990 33491 2010-10-05 5116 38733 47023 2010-10-06 5427 39041 47856 2010-10-07 5733 30855 40742 2010-10-08 6355 9459 22235 2010-10-09 5894 8352 18691 2010-10-10 7240 8399 20861 2010-10-11 4017 5587 13010 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
