- From: pes via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Sep 2019 21:26:35 +0000
- To: public-css-archive@w3.org
@tabatkins 1) Setting aside our different opinions on privacy budget, can we at least agree that since it hasn't even been fully defined (let alone proposed or standardized), its not a useful solution to the problem discussed here? 2) Sure, understood that solving this issue won't solve fingerprinting, but the only way to get the # of identifying bits down to an acceptable number is to start removing as bits anywhere and everywhere we can (where "can" means "w/o breaking the web"). No single change will get us to "win", but there are a _lot_ of bits in fonts (see above linked papers), and so fixing font fingerprinting will be a necessary _but not sufficient- step to unbreaking things (where breaking means "allowing people to be tracked w/o their consent") Several of us in this thread are working on finding ways of fixing the standard. It _might_ be the case that things can't be fully-un-broken, and we can't undo the harm that's been done for _everyone_, but we can at least stop harming as many people as possible. For the reasons many have mentioned, its difficult (but not impossible!). We would really appreciate your help :) -- GitHub Notification of comment by snyderp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4055#issuecomment-536760096 using your GitHub account
Received on Monday, 30 September 2019 21:26:36 UTC