- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Jan 2025 12:27:38 +0000
- To: public-css-archive@w3.org
> FWIW, heres another suggestion you all may have already considered and discarded (but maybe not!): discarding the OS vs installed distinction, and instead limiting the number of font-faces that an site / eTLD+1 can reference within the lifetime a storage partition. Like i said, maybe you all have considered and discarded the idea, but this kind of "budgeting approach" might be successful for fonts in a way I dont think its practical for addressing fingerprinting concerns in general (for example, benign font-face selection might be consistent in a way that a sites overall "set of Web APIs used" is not). _Originally posted by @pes10k in [#5421](https://github.com/w3c/csswg-drafts/issues/5421#issuecomment-1871630599)_ -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11571#issuecomment-2618865706 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 January 2025 12:27:39 UTC