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

Re: on negotiating site exceptions

From: Nicholas Doty <npdoty@w3.org>
Date: Tue, 10 Apr 2012 12:37:35 -0400
Cc: David Singer <singer@apple.com>, "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Message-Id: <42D5374E-EEC7-4F91-BAE1-EDF80F11CD62@w3.org>
To: Lauren Gelman <gelman@blurryedge.com>
On Apr 9, 2012, at 7:18 PM, Lauren Gelman wrote:

>> I agree that this depends on UAs being willing to implement this JavaScript API, manage the client-side state and potentially create new UI.
> Nick-- Maybe this is too simple a question, but if browsers do not do it, can third parties (like a browser plug-in) do it?  Can they access the API stream to provide a one-stop shop for managing site specific and web wide exceptions (and out-of band ones as well, though not from the API).

Yes, browser extensions and plug-ins are definitely candidates to implement Do Not Track on the browser side, including user-granted exceptions handling. I think, though I haven't confirmed, that most of the browser's plug-in APIs will provide enough hooks for third parties to build complete implementations as extensions.

I think many of us hope that browser vendors themselves will implement a Do Not Track option and so knowing whether they are likely to implement these features is still useful for us.

Received on Tuesday, 10 April 2012 16:38:01 UTC

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