We launched the location change along with some other changes and
ran into some pretty serious performance issues. At first I thought it
was the other code but it was in fact this location query causing the
trouble. We have a database change in progress that I am hoping will
let me roll this back out. Please do me a favor and add an issue to
our list (http://code.google.com/p/twitter-api/issues/list) so I don't
forget to keep you updated.
We're also working on the next version of the API where we'll
return the same format for both the main API and search. I haven't yet
figured out if/how we can include the data search has that the main
API does not (notably geocoded location and language code). Thanks for
the reminder to look into that.
Thanks;
— Matt Sanford / @mzsanford