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

Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]

From: Justin Brookman <justin@cdt.org>
Date: Tue, 05 Jun 2012 11:08:31 -0400
Message-ID: <4FCE20EF.1010004@cdt.org>
To: public-tracking@w3.org

On 6/5/2012 11:53 AM, Dobbs, Brooks wrote:
> Hi Rigo,
> So a little follow-up:
>> Rob (Article 29 WP) suggested to have a selection screen at first
>> startup. After all the noise about the defaults, can we assume that
>> using a certain browser means sending DNT;1?
> No. We can't.  This is the same point I raised with Justin.  With no
> disrespect to the hard work this group does, DNT really just isn't top of
> mind share for Joe Consumer and is exceedingly unlikely to be the primary
> motivation for choosing a browser and/or reflect his/her personal preference
> on DNT.  Realistically would anyone ever choose browser A over 3 primary
> competitors because it had DNT by default where the others made me go
> through Preferences->Privacy->DNT?  Doesn't it generally take more than 3
> clicks to install/switch to a new browser?
Even if a user does not *choose* a browser because DNT is enabled by 
default, the user may well be *aware* that DNT is turned on by default.  
Or the user might go to turn on DNT and notice that it was already 
checked.  The ad network is never going to know what the user's 
knowledge and intent is in any case.  For this reason, I believe ad 
networks should respect the signal regardless.  Assuming that the group 
wants to ensure that users knowingly choose to transmit the DNT signal, 
wouldn't it make more sense to put the burden on the implementing 
browsers?  This would give the browsers an affirmative responsibility to 
conform to the specifications in the standard and would prevent a 
situation where all third parties are making subjective determinations 
about user intent and the legitimacy of any particular UI.
Received on Tuesday, 5 June 2012 15:09:01 UTC

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