search

w3cping / font-anti-fingerprinting

A system for preventing font fingerprinting
Other
14 stars 4 forks source link

Add CSSWG issue link #4

Open astearns opened 4 years ago

astearns commented 4 years ago

https://github.com/w3c/csswg-drafts/issues/4497 seems more appropriate than "No signals"

jyasskin commented 4 years ago

Thanks for finding a good link. Can you, perhaps, provide a short summary of the WG's current opinion so people reading the explainer don't have to wade through that whole issue?

astearns commented 4 years ago

@snyderp is working on a summary, so I would defer to him. My understanding is that we think a list-based solution should work (which would need some research and iteration to not break things for minority scripts), and that there will need to be an opt-in in browser prefs to allow local font access when it's appropriate.

pes10k commented 4 years ago

@astearns thats for the ping. Here is a summary and alternate proposal I expect will solve the use cases w/ less machinery and "freeze the web" risk than the other discussed options.

https://github.com/w3cping/font-anti-fingerprinting/pull/6

It would be very good to have CSSWG discussion on this repo too!