Re: Issue-39: Tracking of Geographic Data

Le 15 déc. 2011 à 16:26, Amy Colando (LCA) a écrit :
> In addition to marketing efficiency (ensuring that Peachtree Auto Sales ads are shown mostly to Atlanta residents) and relevant content (as much as I dislike it, I do want to see Seattle weather, rather than California weather forecasts), there are additional significant uses of current session location.

This paragraph is conflating issues about geolocation :)


1. geolocation for working with a geo-dependent 
   service such as a weather widget.
2. geolocation for collecting a profile about you
3. geolocation for serving ads about the services around you

These are different use cases with not the same implications, 
results for users. With "DNT: 1" as a user, I expect 

* Geolocated: 1
* Not Geolocated: 2 and 3

Yes that means the weather widget can't make a profile with 
my data for the purpose of using them for marketing. It is 
fine to have a cookie which remembers my preferences for 
making the service works. It is subtle but make a big 
difference.

The same way (David's case) that two pieces of software on 
Internet needs IP addresses to communicate for establishing 
the service. I don't expect them to create a profile because 
of that communication. 







-- 
Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software