[mawadev]

Exactly. Why would you serve your own copy of the fonts if a previous request to that cdn may have cached them in your browser already? Opt-In goes against the architecture of websites. What's next? A popup for each third party request? It is not feasible and just another stumbling block - like Impressum for private persons and third party cookie consent to host websites in Germany. It makes more sense to fix the issue at the fundamental browser level by the vendor (natively, without the need for plugins) and explain the dangers to the users. Educated users block requests anyway for example.

I think hosting it by yourself is the solution here, but it's getting difficult to keep up with all the rules, especially when the fundamental design of the web moves in the opposite direction.

[youngtaff]

> a previous request to that cdn may have cached them in your browser already? Opt-In goes against the architecture of websites

Browsers partition their caches by origin and third-party origin (it's a bit more complex than that in reality) so common third-party resource e.g. fonts, used on one site won't be reused on another

Instead a fresh version of the font will will be fetched

Safari's done this since 2013 (?), and Chromium & Firefox adopting the same behaviour in 2020 (?)

[isbvhodnvemrwvn]

The browsers don't share third-party caches across domains, because it made it easier to leak information about which sites the user has visited.

[progval]

> The browsers don't share third-party caches across domains

Do you have a source for this? I believe(d?) it too, but when re-checking just now, I could not find any.

[isbvhodnvemrwvn]

I couldn't find anything related to Edge.

Safari: https://webkit.org/blog/8613/intelligent-tracking-prevention...

Chrome: https://developers.google.com/web/updates/2020/10/http-cache...

Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1536058

[progval]

Great, thanks!