RE: Mitigating Browser Fingerprinting in Web Specifications - published

Great work.  Thank you to Nick and Christine.   The only concern I have is what appears to be the inability to prevent a device from being fingerprinted.   Perhaps we need a DNF signal (Do Not Fingerprint, <g>)

-----Original Message-----
From: Samuel Weiler <weiler@w3.org> 
Sent: Thursday, March 28, 2019 2:52 AM
To: public-privacy@w3.org
Subject: Mitigating Browser Fingerprinting in Web Specifications - published

Colleagues,

"Mitigating Browser Fingerprinting in Web Specifications" has been published as an Interest Group Note at:

https://www.w3.org/TR/fingerprinting-guidance/


Many thanks to Nick for his efforts as editor.

-- Sam Weiler, W3C


On 2/11/19 7:53 PM, Christine Runnegar wrote:
> Dear PING,
> 
> A very big thank you to Nick Doty for single-handedly leading the work on Mitigating Browser Fingerprinting in Web Specifications.
> 
> The draft is here: https://w3c.github.io/fingerprinting-guidance/

> 
> Thank you also to everyone who provided input on the document at its various stages.
> 
> As a reminder, this document is a draft Interest Group Note to provide best practices to Web specification authors on mitigating the privacy impacts of browser fingerprinting, developed by the Privacy Interest Group (PING). PING has collaborated with the Technical Architecture Group (TAG) on this guidance. Since the last version: the list of best practices has been expanded and made more specific; guidance has been provided on how to evaluate the severity of fingerprinting surface; and, additional references and examples have been provided.
> 
> We have addressed the outstanding issues in Github and consider this draft ready for publication.
> 
> If you have any last minute comments, please share them on this list by Monday 25 February 2019.
> 
> Christine and Tara (chairs)
> 
>

Received on Friday, 29 March 2019 02:17:37 UTC