Re: Confused by DAA's messages. Please explain

On Jul 8, 2013, at 19:35 , Peter Cranstone <peter.cranstone@gmail.com> wrote:

> David,
> 
> Thanks for the clarification - but you answer is as ambiguous as Roy's syntactically DNT argument. Here's why - just do the following on your iPhone: Settings > Safari > Turn On Private Browsing. 
> 
> Next please tell me where I get the 'conscious choice' to enable a DNT setting?

You get two ways to enable DNT:1

a) as a remote option only; or
b) local and remote: with a local context that is discarded at the end of the private session.

You made an explicit choice for privacy in either case; the only choice you made.  It's not bundled with your choice of breakfast, insurance carrier, or residence, or anything else.

> I don't even see DNT listed – in fact you wouldn't even know it's actually been set UNLESS you hit a server echo page. How does that align with the spec?

We're still working on the help pages, and so on.  See the recent post with a suggested 'shared' DNT-for-users page, for example.

> Apple has imposed a choice on the user. By selecting Private Browsing you MUST accept a DNT setting of 1.

By choosing 'private browsing' you have explicitly and consciously asked for privacy.  

> There is no choice in the matter. 

Privacy was the *only* choice you made.

> Semantically your argument is correct because what you're saying is that 'I want private browsing therefore I MUST want DNT=1'. Well in that case why doesn't the spec reflect that if a user wants to 'privately browse' from any web browser (which we all do) then the default setting becomes a 1.

That's a choice for browser implementors.

> You can't have it both ways – IE10 asks the user to select a privacy setting whereby a DNT signal is sent. Currently Apple doesn't offer a Privacy setting where there is a choice of what is sent which can be selected by the user. (No way to send a DNT=0).

We currently don't see a need to offer DNT:0 to users;  that situation may change.

> 
> Apple's Mobile Safari implementation of the TPWG spec does NOT meet the correct guidelines

in your opinion, which I think is flawed.


David Singer
Multimedia and Software Standards, Apple Inc.

Received on Tuesday, 9 July 2013 08:30:27 UTC