We are having issues with this as well and it has completely broken
our system.

We have sent many support tickets but have received no response to
them.

It looks to be breaking plain searches to not just those requested via
the API.

Some examples of broken searches are:

http://search.twitter.com/search?q=bigpond+near%3Aaustralia

http://search.twitter.com/search.json?q=bigpond&geocode=-27.766513,134.121094,2500km

These were working before this issue.

Best Regards
Nick Fritzkowski

On Oct 6, 2:42 am, Matt Harris <thematthar...@twitter.com> wrote:
> This is a know issue which the team is working on at the moment. I'll
> post an update when a fix is deployed.
>
> ---
> @themattharris
> Developer Advocate, Twitterhttp://twitter.com/themattharris
>
>
>
>
>
>
>
> On Mon, Oct 4, 2010 at 8:36 PM, _ado <adri...@tijsseling.com> wrote:
> > For what it's worth, I'm seeing the same issue. Radius parameter is
> > completely ignored. Data returned for, for example, a 1 mile radius
> > will return results spanning 60 miles.
>
> > --
> > 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

-- 
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

Reply via email to