succeeds:
http://search.twitter.com/search.json?geocode=0.001%2C0.001%2C1km
http://search.twitter.com/search.json?geocode=0.00099999%2C0.00099999
fails with 131:
http://search.twitter.com/search.json?geocode=0.00099999%2C0.001%2C1km
http://search.twitter.com/search.json?geocode=0.001%2C0.00099999%2C1km
i currently use an inconvenient workaround but this is definitely not ideal for our use case
Updates
- We'll adjust the documentation to denote that we don't accept geocodes in this range. What you're trying to accomplish may ultimately not be possible or serviceable by this API.