Geolocation Services

An Update on Apple’s Location Data Tracking

Some developments on the iPhone/iPad tracking story since I last posted. For now, I’ll just refer you to the links.

First, Peter Batty’s must-read posts on the subject: So actually, Apple isn’t recording your (accurate) iPhone location; More on Apple recording your iPhone location history; The scoop: Apple’s iPhone is NOT storing your accurate location, and NOT storing history.

A follow-up from the original researchers: Additional iPhone tracking research (O’Reilly Radar).

Opinion: Mike Elgan at Computerworld; Brian X. Chen and Mike Isaac on Why You Should Care About the iPhone Location-Tracking Issue.

Today, Apple has posted a Q&A on the issue: they say it’s a cache of a subset of a larger hotspot and cell tower database, not location tracking.

iPhones and 3G iPads Track Their Locations

This could be interesting. Alasdair Allan and Pete Warden report today at Where 2.0 that they’ve discovered that iPhones and 3G iPads have been recording their positions and storing them in one large — unencrypted — tracklog file, and are raising the alarm at the privacy implications. “Anybody with access to this file knows where you’ve been over the last year, since iOS 4 was released.” They’ve yet to hear back from Apple on this. The basic questions: what is the purpose of collecting this data, and why is it being stored in this (possibly insecure) manner?

Google Latitude Goes Desktop

Yesterday, Google announced that Google Latitude can now be accessed directly from a desktop web browser at google.com/latitude; previously, the only way to use Latitude on a computer was via an iGoogle widget. It remains to be seen whether this will increase the usage of this service. It’s telling for me that no one on my (very small) Latitude friends list has checked in for months (myself included).

Some Thoughts on Facebook Places

The announcement of Facebook Places frankly reminds me of the last rollout of location services by an Internet giant: Google Latitude.

  1. The media freaks out about the privacy implications (see Lifehacker on how to disable the feature).
  2. Hardly anyone can use the service because of national or technical limitations: Facebook Places is U.S.-only, and can only be used from the updated iPhone Facebook app or from their mobile-browser-optimized website (which requires a device with an HTML5 compatible browser and a GPS — so I can use it with my 3G iPad, if I were in the U.S.).
  3. Of that subset of U.S. iPhone and HTML5-with-GPS users on Facebook, few will actively want to use it. (As with Latitude, the only people I’ve seen use it so far are people in the geospatial industry.)

The sort of people who have no qualms about sharing their location — who are eager to do so — are already using Gowalla, Foursquare and so forth; Facebook didn’t get to be Facebook by being dumb, so those services are integrated into Places.

From what I’ve been reading, the privacy critique of Facebook is essentially as follows:

  1. It’s on by default.
  2. By default, your friends can tag your location (which invites mischief and embarrassment).
  3. Private locations (like someone’s home) can become public and can’t then be removed from the location database.

I’ve already got friends concerned about this, even though Places isn’t available in Canada yet. This isn’t the first time a move by Facebook has generated privacy worries, but this is precisely the sort of thing that can cripple the rollout of geolocation services. The benefits offered by this sort of thing — serendipitous meetups — aren’t important enough to outweigh those concerns for enough people.

Why Share Your Location?

Not everyone is comfortable sharing their precise location, even with their friends; if you’re not, you may well wonder why people actually use location-based social networks like Foursquare or Google Latitude, or enable location sharing on Twitter or (soon) Facebook….  •  Continue reading this entry.

Geolocation in HTML 5

Mark Pilgrim on the geolocation API in HTML 5, which is only supported by a couple of browsers at the moment (Firefox 3.5, the iPhone, and Android). When and where it is supported, though, a user’s location can be acquired…  •  Continue reading this entry.

The Web Goes Local

Clive Thompson’s piece on location services makes a point I was planning on making in a future piece, damn him, as he looks at how location services may transform the Web: The whole reason the Web revolutionized the world was…  •  Continue reading this entry.

Yahoo Placemaker

Yahoo announced its new Placemaker web service at Where 2.0 last week. Placemaker takes unstructured data, extracts references to places, and returns geographic metadata — take a reference to Chicago in a block of text, for example, and it gives…  •  Continue reading this entry.

Google Latitude

Google Latitude is a friend-tracking tool for mobile devices; it’s also an iGoogle gadget. Using a mobile device’s built-in GPS (or manual updates), it shows the location of at least those friends who’ve added themselves to the service. See the…  •  Continue reading this entry.

Link Roundup: Mid-July Edition

Facebook app whereyougonnabe? gets an upgrade focusing on integration with other platforms (previously). Diana Eid takes a look at map art, focusing on three artists we’ve seen before: Matthew Cusick, Elisabeth Lecourt and Susan Stockwell (via GeoCarta). On the…  •  Continue reading this entry.

FireEagle

FireEagle is a new Yahoo service. (In beta, of course.) It’s a user-geolocation service with privacy controls that can tie into other applications; think of it as a Twitter for geographic coordinates. It’s one of those things, like RSS, whose…  •  Continue reading this entry.