Re: Supporting TPE on sites/subdomains where a user does not have control of the server (ISSUE 15, ISSUE 10)

Roy beat me to the punch...
I too was going to recommend a publisher platform configuration approach as some basic configuration already exists on all of these types of platforms.  This way the publishing platform is able to fully convey both its own DNT position and the user of their platform's position in the same location without needing to resort to page load metadata to do so.
- Shane Shane Wiley
VP, Privacy Policy
Yahoo

      From: Roy T. Fielding <fielding@gbiv.com>
 To: Aleecia M. McDonald <aleecia@aleecia.com> 
Cc: "public-tracking@w3.org (public-tracking@w3.org) (public-tracking@w3.org)" <public-tracking@w3.org>
 Sent: Monday, January 23, 2017 10:12 PM
 Subject: Re: Supporting TPE on sites/subdomains where a user does not have control of the server (ISSUE 15, ISSUE 10)
   

On Jan 24, 2017, at 11:24 AM, Aleecia M. McDonald <aleecia@aleecia.com> wrote:
> 
> The thing is, Wordpress cannot know what my hosted page is doing with data I collect from my DNT visitors. Only I know that. So Wordpress cannot speak on my behalf because they do not know enough.

Yes, that's true. Just like the page owner cannot know what data Wordpress collects from users that request hosted pages, let alone how carefully they manage log files.

The solution is that there needs to be a legal agreement between the hosted page owner and the host service provider that specifies how to respond to DNT, in both Tk and TSR, and requires both parties to conform to that response. Lack of such an agreement means no accurate response can be given.

In practice, this is as simple as a configuration option.  The problem is getting hosted services to deploy such an option. I don't think we can take any short cuts here without making the tracking response meaningless.

Moving the response from header field to page metadata is only a solution for deployment if neither the accuracy nor the timeliness of that response matters.

....Roy