privacywg call for consensus: Mitigating Browser Fingerprinting group note

Hi Privacy WG,

This is a call for consensus, to confirm on the list the proposed
resolution that we had at the recent Privacy Working Group meeting, that
the Privacy Working Group should publish a Group Note of the Mitigating
Browser Fingerprinting document, that was previously published as a PING
Group Note. Per our previous discussion, that would also configure
auto-publishing of this document when updates are made, with ongoing review
by the group and at least one formal review by the group at TPAC each year.

Minutes from the 16 January call:
https://github.com/w3c/privacywg/blob/main/minutes/privacywg-20250116.md#mitigating-browser-fingerprintinggithub---w3cfingerprinting-guidance-what-is-browser-fingerprinting-and-how-should-specification-authors-address-it
Editor's draft: https://w3c.github.io/fingerprinting-guidance/

If you have an objection to this decision, please let us know on list by
next Tuesday, February 4th.

The W3C Team can help us with the actual details of
publishing/autopublishing, which I also think will need to include
reviewing and merging the open PR from Jeffrey Yasskin.

We also heard interest from some volunteers in working on updates to that
guidance document. Many thanks to Tom Ritter (Mozilla) for getting us
started! Tom has already opened a PR and a couple of issues, including one
open question that other implementers or researchers may want to answer: do
we think Accept-CH response headers are providing in practice meaningful
detectability of accessing fingerprinting surface?

https://github.com/w3c/fingerprinting-guidance/issues/68
https://github.com/w3c/fingerprinting-guidance/pull/69
https://github.com/w3c/fingerprinting-guidance/issues/71

Thanks all for your interest on this long-term but still very relevant
privacy topic.

—Nick, for the co-chairs

-- 
Nick Doty | https://npdoty.name
Senior Technologist
Center for Democracy & Technology | https://cdt.org