We’re gearing up to launch a new feature which makes Twitter truly location-aware. A new API will allow developers to add latitude and longitude to any tweet. Folks will need to activate this new feature by choice because it will be off by default and the exact location data won’t be stored for an extended period of time. However, if people do opt-in to sharing location on a tweet-by-tweet basis, compelling context will be added to each burst of information.
By developer preview they mean that it will only be available by API calls. So if you want to take advantage of the new location functionality petition your Twitter client to support it. (Tweetdeck — I am looking at you. Please immediately add reverse geocoded (human-readable) locations that link to a map).
We’re going to release geolocation to platform developers before we add the feature to Twitter.com. Most of the mobile applications people use and love are built by Twitter platform developers. Developers will have access to this new geolocation feature early which means it will most likely be available on your app of choice before it’s available on Twitter’s web site. Later, we’ll add it to our mobile web site and Twitter.com as well.
What does this mean? At first it won’t mean much of anything, but soon those augmented reality twitter apps will become accurate, you’ll be able to call up geo-specific twitter searches for a restaurant review, mashups like Twittervision (image above) will become easier) and services like DIY Traffic (Radar post) will be able to more accurately vet data. And that’s just as a consumer and not as a contributor.
To fully support location in their data Twitter will have to add more support in their search (right now “Near:<city>” is the only supported command). You can expect lat: and long: to show up shortly.
Where it will really get interesting is if you opt-in. You will be creating a trail of mini-reviews and news as you go through life. Initially Twitter will not have privacy controls. Once you opt-in your lat-long will be shared with anyone who is pulling your account via the API (and eventually the website). You’ll start to announce your location with each Tweet. Your friends will always know where you are. You will be announcing when you are home and when you are in another country. I hope that many Twitter clients (ahem, Tweetdeck again) let me opt-out of sharing my location per Tweet. In time Twitter should definitely add the ability to choose the level of granularity (exact, neighborhood, city, etc.) to expose.
Twitter recognizes that location is a sensitive and powerful data type. They will be providing their devs with a handbook on how to deal with it:
As part of our Geolocation efforts we will soon be publishing “Geolocation Best Pracitices” to guide everyone through issues like security and privacy as well as discussing some ideal experiences for users. Topics will include things like storage of location data, what to do with a user’s historical data, how to present the concept of geotagging and more. The guide will create a framework from which we can address the challenges that come about when dealing with something as sensitive as someone’s location while hopefully allowing everyone enough creative freedom to create their own experiences around it.
This sensitivity to location comes from key-hire Ryan Sarver (@rsarver). Ryan recently joined Twitter from Skyhook Wireless. He is an organizer of WhereCamp and has spoken at Where 2.0 the past two years.
Twitter’s location support puts it in competition with location-based social networks like Loopt, Pelago and Brightkite. It gets even more interesting if services like Fire Eagle (quite possible) or Latitude (not currently possible, but probable) start to take in Twitter as a source. Or it’s quite likely that Twitter will become the default provider of location to other services (exactly Fire Eagle’s purpose). Will location become accessible via Twitter Connect? Will Twitter, the microblogging service also become your location service?
(I’ve added developer information and links after the jump)
<?xml version=”1.0″ encoding=”UTF-8″?>
<created_at>Tue Apr 07 22:52:51 +0000 2009</created_at>