W3C home > Mailing lists > Public > public-tracking@w3.org > March 2012

Re: JS Exception API

From: Tom Lowenthal <tom@mozilla.com>
Date: Tue, 06 Mar 2012 12:17:53 -0800
Message-ID: <4F5670F1.70708@mozilla.com>
To: Kevin Smith <kevsmith@adobe.com>
CC: "public-tracking@w3.org" <public-tracking@w3.org>, Andy Zeigler <andyzei@microsoft.com>, Nicholas Doty <npdoty@w3.org>
On 03/05/2012 02:08 PM, Kevin Smith wrote:
> One more thought.  It's also critical that the 1st party knows upfront whether it has an exception or not, because under DNT:1, it may choose to use completely different 3rd party services (ie - to maximize cpm, they may choose to go with 1 ad exchange for targeted ads, but a completely different one for truly random ads)
> Its not acceptable to have to try to make these decisions after the page has loaded and requests have succeeded or failed.  It makes for a more expensive and complicated implementation and a poorer user experience, so again, a site would not implement it.
> Again, I am ok with having the option to pass it an array of 3rd party services, but it would be a very poor API indeed which required a parameter in which everyone used the same value.

If you think it's troublesome for the publisher, just think how
difficult it is for the user. They need to consent *in advance* to allow
themselves to be tracked by a list of parties which is so difficult to
corral that not even the publishers knows in advance who's on it? That
doesn't seem credible, either from the point of view of making a useful
tool, or from the point of view of getting real consent.

Received on Tuesday, 6 March 2012 20:19:27 UTC

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