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

Re: DNT-aware JavaScript (ISSUE-84, ACTION-85)

From: Roy T. Fielding <fielding@gbiv.com>
Date: Thu, 26 Jan 2012 10:02:51 +0100
Cc: Kevin Smith <kevsmith@adobe.com>, "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Message-Id: <7D0E6E0A-0864-4AA0-AE3C-13BBBE83B6F6@gbiv.com>
To: Jonathan Mayer <jmayer@stanford.edu>
On Jan 25, 2012, at 10:52 PM, Jonathan Mayer wrote:
> On Jan 25, 2012, at 10:18 PM, Kevin Smith wrote:
>> While functional, I think both of these suggestions are extremely inelegant hacks.  Companies may choose to use a method such as these, but I would not think the W3C would want to formally recommend such an approach.  You don't usually see hacks standardized.  I agree with the two browser developers that we should leave this section out and let companies work around it if they ever need to.
> DNT-aware JavaScript is a frequently proposed use case / called for feature request.  I think it'd be unwise to leave out something implementers want, especially when the approach appears to be counterintuitive for some.

My concern is fairly specific.  We do personalization via javascript.  Some
of that personalization is based on server-side information and some based
on client-side information.  Some of it is based on pure session data (like
where the mouse pointer spends the most time in your window).

I expect client-side personalization to increase in the future (depending on
regions and devices) when client-side storage is more prevalent.

The end result is that users may start seeing targeted behavior entirely
driven by client-side data and cached javascript, which means no server
request is being made to the third party and thus no DNT header is sent.

Do we care to address that use case?  I don't know if we do.

Received on Thursday, 26 January 2012 09:03:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:38:30 UTC