You're a LIFE SAVER man. Thank you very much. And I couldn't agree more: @twitterapi should have notified us. I sent him a @reply but got no answer so far.
On Sep 8, 11:10 pm, Hrishikesh Bakshi <bakshi.hrishik...@gmail.com> wrote: > Quick fix: > > Add q=* to your URL > > > > On Tue, Sep 8, 2009 at 10:04 PM, Dewald Pretorius <dpr...@gmail.com> wrote: > > > FFS. > > > Any chance that things will actually be tested before they are rolled > > out into PRODUCTION? > > > Dewald > > > On Sep 8, 10: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. > > -- > Hrishikesh Bakshi
