8 comments

[ 3.4 ms ] story [ 337 ms ] thread
> With Cloudflare Fonts enabled, you are able to see within your Network Tab that font files are now loaded from your own hostname from the /cf-fonts path

Is there a particular reason why is it not using /cdn-cgi/ prefix?

I don't think Google will like this... :)
Sorely needed. It is funny how so many of the sites with GDPR notices and policies explaining how they don't share data, don't have scripts from places like Google don't realise that they're still handing over that data by loading fonts from Google.

(and no Google Fonts does not exist as a charity project, it absolutely has a purpose for one of the worlds largest data collectors)

This feels like a big slight to Google. Fine, performance, different routing strategy, privacy, save or redirect some of that data skimming... but when did CF start hating on G so much?
They definitely have balls to say that including fonts from their CDN enhances privacy
I mean, if you're using this, you're already using Cloudflare. So would you rather traffic hit CF & Goog, or just CF?
I mean, for this to work the website has to be already served by Cloudflare, its one entire company less you are not sharing data with.
Exciting news! Does CloudFlare have plans to sponsor the maintainers of the Fontsource project?