Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions

Ian, 

if you ask for out of band messages, this mainly says we give up on 
technology and return to the legalese. As DNT is a communication mechanism, 
saying I have to communicate otherwise means, you've given up. I'm not there 
yet. I will try to reply in detail to your arguments as far as I have 
arguments beyond what Nick already said.

On Monday 30 April 2012 11:07:33 Ian Fette wrote:
> > * Companies that want to distinguish their limited list of third-parties
> > Some companies may wish to put users at ease or distinguish their
> > practices from competitors by requesting exceptions for an explicit list
> > of third-party partners rather than an open-ended site-wide exception.
> > (As suggested by Shane in DC.)
> 
> Couldn't this be done in an out-of-band manner? I doubt you are just going
> to call RequestException() when the user goes to the homepage. Probably
> you message something to them explaining why you want the exception. You
> could explain your limited use of third parties here. (You could also
> make it available at a well-known URI).

Calling RequestException() is your friend. It allows you to recover a client 
that would otherwise be lost. It allows you to overcome the pop-up nightmare 
as exemplified by the IAB Europe demo site. And there is no explanation to 
make as the thing is only about tracking. So if it asks, it asks about 
tracking. There aren't enough semantics for big explanations. We may note 
down some nice euphemisms in some UI How-to note so that it says e.g. "We 
need to know about your history to provide personalized services to you". 
Because if the UI would pop-up saying:
<big finger in your direction>WE WANT TO TRACK YOU!</big finger in your 
direction> 99% of users will close their browser and shut down their 
computer. But I'm confident that we have a sufficient number of marketeers 
in the room to sweeten the message.

Rigo

Received on Friday, 4 May 2012 15:09:42 UTC