- From: Andrei Popescu <andreip@google.com>
- Date: Thu, 30 Jun 2011 12:01:16 +0100
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: Wojciech Maslowski <wmaslowski@opera.com>, Anne van Kesteren <annevk@opera.com>, Steve Block <steveblock@google.com>, Doug Turner <doug.turner@gmail.com>, Lars Erik Bolstad <lbolstad@opera.com>, "public-geolocation@w3.org" <public-geolocation@w3.org>
On Thu, Jun 30, 2011 at 10:19 AM, Dominique Hazael-Massieux <dom@w3.org> wrote: > Le jeudi 30 juin 2011 à 09:23 +0100, Andrei Popescu a écrit : >> Yes, you can probably work out roughly where the user is from IP, then >> set up a set of proximity alerts that will track the user with almost >> the same accuracy as watchPosition(). It's slightly more involved but >> perfectly possible, so I agree the privacy gains aren't that great. > > They might not be great in the worse case scenario (a site asking for > proximity alerts for many locations), but they're pretty good in better > scenarios (e.g. a single location). > > Also, a user agent could better give guidance to the user when a site > requests alert for too many locations, or refuse giving alerts when too > many are requested, or when they are to close to one another, etc. > But what exactly is "too many" or "too close"? Pick too small a number and you'll break many use-cases. Pick a bigger number and the privacy benefit quickly evaporates. Andrei
Received on Thursday, 30 June 2011 11:01:45 UTC