W3C home > Mailing lists > Public > public-tracking@w3.org > April 2013

RE: DNT: Agenda for April 10 call

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Sun, 14 Apr 2013 09:22:28 +0100
To: "'Rigo Wenning'" <rigo@w3.org>, <public-tracking@w3.org>
Cc: "'Sid Stamm'" <sid@mozilla.com>, "'Alan Chapell'" <achapell@chapellassociates.com>, "'David Singer'" <singer@apple.com>, "'Adrian Bateman'" <adrianba@microsoft.com>, "'Justin Brookman'" <justin@cdt.org>
Message-ID: <062101ce38e9$3431d6e0$9c9584a0$@baycloud.com>

+1, as it should also be possible for servers to use a site-specific API to
turn DNT on as well as off. It is quite likely that some sites will wish to
offer a package including a privacy feature that signals DNT to embedded
third-parties even when the general preference has not be turned on.


-----Original Message-----
From: Rigo Wenning [mailto:rigo@w3.org] 
Sent: 13 April 2013 22:25
To: public-tracking@w3.org
Cc: Sid Stamm; Alan Chapell; David Singer; Adrian Bateman; Justin Brookman
Subject: Re: DNT: Agenda for April 10 call


your vision really sounds good to me. And I agree that DNT is a tool in the
box, not more. I agree that browsers could use that tool in various ways.
Bundling the tool with other tools is clearly where browsers compete. So I
don't think the TPE or TCS should prohibit or preclude or require other

I would hope though, that the UI for switching that mode allows for simple,
comprehensive and natural choices and makes it as easy to turn
DNT:1 on as it is to turn DNT:0 on. 


On Thursday 11 April 2013 07:42:24 Sid Stamm wrote:
> But at the same time, there's lots of related privacy features that 
> can be combined into one user experience; I can imagine a "tracking 
> protection" mode or something that enables DNT but also does some 
> other stuff with web cookies, cache, etc.  I think this should be 
> allowed, even though in this case DNT enablement is part of the 
> "meta-feature".
> On the other hand, I can also imagine a personalization mode that, 
> when enabled, turns on DNT:0, logs them into a social API endpoint, 
> and starts mashing up data for a more personal web experience.  In 
> this case, DNT is not central to the personalization mode, but clearly 
> helpful and should not be prohibited even though it's not the complete 
> story for this mode.
Received on Sunday, 14 April 2013 08:23:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:39:29 UTC