Raffi,
I find the biggest hurdle with geo-tweets right now is that very few
twitter users actually have it enabled. And I believe for a very good
reason as sending the exact coordinate of a tweet has serious privacy
issues. For example, a girl takes a picture of her new hairdo from her
bedroom
good stuff raffi, any further news on if/when the new place data
will be exposed via the Search API?
cheers, bob
GeoMeme - http://www.geome.me - what's happening where?
On Mar 2, 12:44 pm, Raffi Krikorian ra...@twitter.com wrote:
hi all.
i wanted to give you all a heads up on some big
hi bob.
soon :P
On Fri, Mar 26, 2010 at 2:06 PM, bob.hitching b...@hitching.net wrote:
good stuff raffi, any further news on if/when the new place data
will be exposed via the Search API?
cheers, bob
GeoMeme - http://www.geome.me - what's happening where?
On Mar 2, 12:44 pm, Raffi
as a follow up to this, if you want to see a fully formed example in the
wild, then just grab http://twitter.com/statuses/show/9882866425.xml.
have fun!
On Mon, Mar 1, 2010 at 5:44 PM, Raffi Krikorian ra...@twitter.com wrote:
hi all.
i wanted to give you all a heads up on some big changes
at day one, there won't be a WOEID ID match on this endpoint -- it is on our
list, however, and we will get to it.
On Tue, Mar 2, 2010 at 2:32 AM, Dominik Schwind domi...@gmail.com wrote:
This is awesome!
And please tell me you'll be using the WoeIDs for that.
Dominik
On Mar 2, 2:44 am,
Calls to http://api.twitter.com/1/geo/id/7695dd2ec2f86f2b.xml return JSON,
while appending any other extension (.html, .raffi, etc) return a 1 byte 403
error (0x20). Since XML isn't supported according to the wiki docs, maybe
return 403 for .xml as well?
--
-ed costello
@epc / +13474080372
yup - thanks for catching that. only JSON is supported, and we'll track
down why the others are returning anything.
On Tue, Mar 2, 2010 at 10:30 AM, Ed Costello epcoste...@gmail.com wrote:
Calls to http://api.twitter.com/1/geo/id/7695dd2ec2f86f2b.xml return JSON,
while appending any other
