Sorry, why is it not compatible with disjunctions? That seems like a bug, not a change in functionality. Basically what you're saying is that if I search for "edmonton" and geocode it, I get location information. Or if I search for "#yeg" and geocode it, I get location information. But if I search for "edmonton OR #yeg" and geocode it, I don't get location information? When I did until yesterday? And received no warning about a change?
On Sep 9, 12:52 pm, Alex Payne <a...@twitter.com> wrote: > Another note: the Search API documentation has been updated to reflect > that querying based on geocode is not compatible with disjunctions (OR > queries). > > Please see the "Operator Limits" section > ofhttp://apiwiki.twitter.com/Twitter-Search-API-Method:-search. > > > > > > On Wed, Sep 9, 2009 at 11:19, Samuel Luckenbill<s...@twitter.com> wrote: > > > Hey Folks, > > > The bug is specifically that all queries using the geocode parameter > > with no query string return no results. We'll launch a bug fix today. > > In the interim, you can use the geocode: operator in the query string > > or add a bogus string as someone else has suggested. Sorry for the > > inconvenience and we appreciate your patience. > > > Sam > > > On Sep 8, 6:25 pm, Jose Tinoco <jose.tin...@gmail.com> wrote: > >> Geocoded API searches are also broken. This is the geocoding example > >> from the API documentation, which used to work and now doesn't: > > >>http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%... > > >> My website (blablabra.net) does similar searches and now receives only > >> 403 Forbidden errors or an empty XML/JSON with "You must enter a > >> query" if I try this search on my browser window. > > >> On Sep 8, 10:05 pm, Alex Payne <a...@twitter.com> wrote: > > >> > Our Search Team informs me that they shipped a new query parser today. > >> > This is likely a bug in the new parser, and I've let them know about > >> > it. > > >> > On Tue, Sep 8, 2009 at 17:48, Mack D. Male<master...@gmail.com> wrote: > > >> > > Until a couple of hours ago, searching for something like "edmonton OR > >> > > #yeg OR near:edmonton" (or the API equivalent) worked just fine. Now > >> > > it doesn't return anything new, and seems to return an odd set of old > >> > > results. > > >> > > You can search for them separately, as in "edmonton OR #yeg" and > >> > > "near:edmonton" but not together. > > >> > > What gives? > > >> > -- > >> > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x > > -- > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
