W3C home > Mailing lists > Public > public-tracking@w3.org > November 2011

RE: Issue-17, Issue-51 First party obligations

From: TOUBIANA, VINCENT (VINCENT) <Vincent.Toubiana@alcatel-lucent.com>
Date: Wed, 30 Nov 2011 04:46:31 +0100
To: Karl Dubost <karld@opera.com>, Jonathan Mayer <jmayer@stanford.edu>
CC: "<public-tracking@w3.org> (public-tracking@w3.org)" <public-tracking@w3.org>
Message-ID: <4D30AC7C2C82C64580A0E798A171B4444887C7A2F1@FRMRSSXCHMBSD1.dc-m.alcatel-lucent.com>
In Adnostic (which is one of the solution listed on DoNottrack.us)  we did not attempt to disambiguate users of a same browsers. At the time, Firefox Weave was just starting and we assumed that several users using a same browser will synchronize their accounts with Weave and thus overwrite the local profile (I started to work on weave support but never finished).

That being said, current solution based on cookies are by no mean better than solution using local storage. If you have a look on your Google Ads Preference or Yahoo! Ads Interest, you'll see the list of interest associated to your cookie. So if two users use a same browser, the problem is already there (I think that's what Jonathan means).

That being said we could try to recognize sessions on the client side to disambiguate users. For instance, the browser could associate a local profile to a specific gmail/yahoo login. Cookie based targeting solutions can't do that.


From: Karl Dubost [karld@opera.com]
Sent: Wednesday, November 30, 2011 4:04 AM
To: Jonathan Mayer
Cc: <public-tracking@w3.org> (public-tracking@w3.org)
Subject: Re: Issue-17, Issue-51 First party obligations

Le 29 nov. 2011 à 21:08, Jonathan Mayer a écrit :
> Most proposals rely on HTML5 local storage.  OS or browser profiles would be sufficient to disambiguate users.


Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software
Received on Wednesday, 30 November 2011 03:47:39 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:44:42 UTC