W3C home > Mailing lists > Public > public-tracking@w3.org > October 2014

RE: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call]

From: Shane M Wiley <wileys@yahoo-inc.com>
Date: Wed, 15 Oct 2014 19:19:27 +0000
To: David Singer <singer@apple.com>
CC: Tracking Protection Working Group <public-tracking@w3.org>
Message-ID: <DCCF036E573F0142BD90964789F720E324FD715C@GQ1-AM-M03-03.y.corp.yahoo.com>
David,

I believe terseness is warranted in this case.  The core difference between UGE and Cookies is that UGE survives cookie removal exercises much like a DNT setting does.  Web-wide exceptions are for a singular domain to be provided an exception in any 3rd party scenario that domain is encountered - something 3rd parties will be motivated to obtain if they ever support DNT - all types of 3rd parties not only large social networks.  This will be the only option for ad networks, trading desks, agencies, etc. to obtain a consent to apply to their business across the Internet.

- Shane

-----Original Message-----
From: David Singer [mailto:singer@apple.com] 
Sent: Wednesday, October 15, 2014 12:08 PM
To: Shane M Wiley
Cc: Tracking Protection Working Group
Subject: Re: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call]


On Oct 15, 2014, at 10:48 , Shane M Wiley <wileys@yahoo-inc.com> wrote:

> Removing the option for web-wide exceptions is a non-starter as that's the only tool expected to be used by 3rd parties that are most impacted by this standard.

Can you be a little less terse?  My impression is that web-wide is
a) most useful for sites that have a presence over multiple other sites, and for which the user would perceive an advantage to being tracked ('track my reading', facebook, etc.)  I don't see advertisers falling into this category very much
b) the only difference between a UGE Webwide and a cookie is maybe the expiry/deletion model.


> 
> - Shane
> 
> -----Original Message-----
> From: David Singer [mailto:singer@apple.com] 
> Sent: Wednesday, October 15, 2014 10:09 AM
> To: Tracking Protection Working Group
> Subject: Re: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call]
> 
> I think that this is a problem most conspicuously for web-wide exceptions, and they effectively emulate the behavior of cookies but in another way.  (Site-wide exceptions and cookies are not similar.)
> 
> The really broken scenario is where the site has a web-wide exception that needs to expire for some reason, and the exceptions API doesn't support expiry. To remember the expiry, the site sets an expiring cookie, and questions or disregards the exception if either it or the cookie is missing. If the site's web-wide resource is non-scripted it is in no position to do anything about confirmation, re-requesting, checking etc. unless the user visits the site itself again.
> 
> Issues:
> * why not use just the cookie?
> * if the cookie is missing but the exception is present, which of the following occurred?
>  a) the user deleted cookies but the expiry time is not yet reached
>  b) the cookie expired
>  c) the user set their general preference to DNT:0  I don't think the site can tell.
> 
> 
> I therefore think that we should either
> 
> 1] add an expiry parameter to both exception-setting APIs (for regularity, though only the web-wide one is problematic) OR 2] delete web-wide exceptions, since they are simply replicating cookies
> 
> 
> Which do people prefer?
> 
> 
> David Singer
> Manager, Software Standards, Apple Inc.
> 
> 

David Singer
Manager, Software Standards, Apple Inc.
Received on Wednesday, 15 October 2014 19:21:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:41:47 UTC