@mansr @rysiek
> It's about a German court effectively banning websites referring to other sites.
Not exactly. By including resources from third parties, website owners aren't giving visitors a choice but to download those resources and give up their personal information. That's the core issue and what this whole thing is about.
If there was a dialogue when visitors first opened the site using system default fonts with nothing loaded from Google that asked "Do you want to view this site with custom fonts provided by Google?" with two buttons saying "Browse with default fonts" and "Use custom fonts" and Google's fonts were downloaded *only* if the user visitor selected that option, the whole situation could have been avoided.
Alternatively, the website owners could host their own damn resources and save themselves all the trouble. Unless they're getting thousands of hits per minute, there is no reason to use a CDN. That's just lazy and irresponsible, especially if the CDN is as anti-privacy as Google.
> It's about a German court effectively banning websites referring to other sites.
Not exactly. By including resources from third parties, website owners aren't giving visitors a choice but to download those resources and give up their personal information. That's the core issue and what this whole thing is about.
If there was a dialogue when visitors first opened the site using system default fonts with nothing loaded from Google that asked "Do you want to view this site with custom fonts provided by Google?" with two buttons saying "Browse with default fonts" and "Use custom fonts" and Google's fonts were downloaded *only* if the user visitor selected that option, the whole situation could have been avoided.
Alternatively, the website owners could host their own damn resources and save themselves all the trouble. Unless they're getting thousands of hits per minute, there is no reason to use a CDN. That's just lazy and irresponsible, especially if the CDN is as anti-privacy as Google.
Follow
TBF, there was an additional reason to use fonts from a cdn in the past: you would benefit from them being already cached (because some other website surely fetched them) and so reduce the latency for the user. Alas, this creates a way to exchange information between different origins _and_ is a permacookie, so all caching, including fonts, is now essentially origin-isolated (I think it's not exactly per origin, but some similar concept; don't quote me on details), so this benefit is no longer there.
@rysiek@mastodon.technology @mansr
