- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Tue, 6 Mar 2012 14:52:47 -0800
- To: Shane Wiley <wileys@yahoo-inc.com>
- Cc: Matthias Schunter <mts@zurich.ibm.com>, "public-tracking@w3.org" <public-tracking@w3.org>
I do not believe it is feasible for the first-party to be informed that there are exceptions on some of its third-party dependencies before the client knows what subrequests are going to be made for the page, since the client does not know that until long after it gets the response to the request in which it was supposed to send DNT:2. At best, the server could be informed that the client has decided to block some third-party sites, sometimes, and I don't think that is useful. Furthermore, I think that user agents would lie about that setting on the basis of their configuration being private, so it could not be relied upon by sites regardless. Hence, I think the only solution to this issue is via a javascript API that can be checked by the first-party page after it has been received. Such javascript if fully capable of adjusting the site after-the-fact to sufficiently monetize the content, either through dynamic adjustment of the DOM or by simply redirecting the user to a site hierarchy that is designed for non-tracking users. ....Roy
Received on Tuesday, 6 March 2012 22:53:10 UTC