@Themattharris: was there any change to the implementation timeline?
Quote: by 22nd October 2010 (Friday): String versions of ID numbers
will start appearing in the API responses
I'm still not seeing id_str, to_user_id_str and from_user_id_str etc.
in the current search API output, example:
Update: the ticket is closed and @TweepsAround seems to be working
fine again.
Details: http://code.google.com/p/twitter-api/issues/detail?id=1930
Quote:
Comment 3 by project member tokofu, Today (13 hours ago)
We've deployed some changes which should have fixed this issue so i'm
closing the
Hello,
Since a few days it seems that search restricted by geolocation and
search radius is not working correctly anymore.
If I submit this request:
http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C1kmrpp=100
I expect all resuls to originate from a geocode within 1km radius
not
sure how quickly it will be fixed, but I'm hoping it will be early next
week. I don't think there are any functional workarounds besides merging
multiple searches.
Sorry about the mess!
Taylor
On Fri, Sep 24, 2010 at 6:57 AM, Johannes la Poutre jsixp...@gmail.comwrote:
Hello,
Since
