W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2008

Re: Geolocation: Security and Privacy

From: timeless <timeless@gmail.com>
Date: Tue, 10 Jun 2008 11:35:09 +0300
Message-ID: <26b395e60806100135t562ea110x61db734e577f1009@mail.gmail.com>
To: public-geolocation@w3.org

Alec wrote:
> To accomplish "Data fuzzing," I think the easiest solution is to
> randomize the lat/long values to some number of decimal places based on
> what the user is willing to give. I agree that bounding boxes and center
> points of cities makes a lot of sense, but that seems like an
> implementation nightmare - all the central points/bounding boxes would
> need to be stored in a database somewhere and accessed.

i kinda like the region box idea.

especially if the user is shown the box (in a world/regional ma)p and
given the ability to choose which box to update to next.

a box region of course also gives implicit information about the
precision the agent is offering to the service. and it of course would
need to be expressed as part of the api.

> One alternative is to only perform limited reverse geocoding (i.e. only
> give the city, state, country) for sites that the user does not trust
> and withhold the lat/long values. Then if the user gives consent (via
> UI?), the actual coordinate could be returned.

On 6/10/08, Chris Butler <cbutler@dash.net> wrote:
> The approach to provide a randomized dance around the current location
> would provide a way to potentially brute force a more approximate real
> location by accessing the data multiple times and doing the average...

> Giving back a reverse geocoded string would work as well so that the
> service doesn't need to provide that service...
Received on Tuesday, 10 June 2008 08:35:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 March 2012 18:13:39 GMT