from http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
birdfeed - http://birdfeedapp.com/
foursquare - http://foursquare.com/
gowalla - http://gowalla.com/
twitdroid - http://twidroid.com/
twitterlator pro - http://j.mp/twitpro
and seesmic web (http://www.seesmic.com/app) is set up to consume the
data.
HI there Raffi,
below is a snippet of the home_timeline.XML (the last 8 lines for the
status element).
...
<statuses_count>317</statuses_count>
<notifications>false</notifications>
<geo_enabled>true</geo_enabled>
<verified>false</verified>
<following>false</following>
</user>
<geo/>
</status>
The update was added from twitter.com, so if the site itself doesn't
supply the data, would you know which clients are populating geo data
at this time?
Kind Rgds,
Chris.
On Nov 29, 6:55 pm, Raffi Krikorian <ra...@twitter.com> wrote:
the geotag needs to be passed in explicitly by the application doing
the update
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses
%C2%A0u...
Hi there,
I'm confused by the apparent status of geotagging in twitter.
The API documentation only mentions it for status update and
advice on
geo-enabling in applications.
So I enabled this on my profile and so am seeing the
<geo_enabled>true</geo_enabled> when using 'twitter.com/statuses/
user_timeline.xml' with basic authentication.
But.
There is pnly a single empty <geo/> tag in the XML, no actual data
at
all.
Does anyone know what is happening?
Many Thanks,
Chris.
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
