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