"This site requires javascript" google...
Redesigned Google Fonts website
81–90 of 90 posts
Re: Redesigned Google Fonts website
#82Earlier quoted context omitted.
There is also https://fonts.bunny.net But its still not clear wether that satisfys the GDPR or not, better be safe and host the fonts on your CDN or locally.
Bunny is a reputable company and they're EU based. At the same time, they also promise zero loggin and that they don't pass any information to any third parties and that they're GDPR compliant. They couldn't write it so boldly without risk of litigation unless that actually was the case, so I would consider it safe to use.
Re: Redesigned Google Fonts website
#83CDN+Web font-related PSAs: Users: it’s a good idea to block all third-party fonts so you’re not leaking data (filter rule: *$font,third-party). Unlike scripts/styles, fonts generally don’t hurt the UX (unless a developer is using icon font which haven’t been best practice in a decade--which is ironic considering this blog is broken). Developers: vendor these Google Fonts (most are licensed SIL) as other have noted in…
Re: Redesigned Google Fonts website
#84Earlier quoted context omitted.
There's this phenomenal app for font conversion called Webfont Kit Generator. The feature I like the most is Subsetting, it greatly reduces the file size. You might find it useful. https://github.com/rafaelmardojai/webfont-kit-generator
> “…more privacy friendly Google alternatives are available and super easy to use […] No need to leak data to Google.” For the unaware, what about Google Fonts is a privacy leak?
Given Google's business model, I personally don't have a reason to trust them with my visitor's data, no matter what they do with it. Self-hosting the required fonts is a 2-minute job anyway.
Re: Redesigned Google Fonts website
#85Tip: more privacy friendly Google alternatives are available and super easy to use: https://fontsource.org/ I switched most of my sites to use it and I’ve been quite happy so far. It just works. No need to leak data to Google. For weirder stuff (e.g. https://tidings.potato.horse ) I use sites like dafont.com and convert fonts using Font Squirrel.
Why not just download the fonts and self-host? No leakage.
Re: Redesigned Google Fonts website
#86Earlier quoted context omitted.
Privacy-friendly ∨ GitHub+Discord … pick one? This is just another way to get fonts, no? It could be convenient to some, but doesn’t do much more than let you preview the a font & download it. Is a Node package manager the right tool to be downloading fonts?
npm is pretty good for downloading fonts when the alternative is downloading, hosting, and configuring webfonts by hand.
Re: Redesigned Google Fonts website
#87Earlier quoted context omitted.
There is also https://fonts.bunny.net But its still not clear wether that satisfys the GDPR or not, better be safe and host the fonts on your CDN or locally.
Bunny is a reputable company and they're EU based. At the same time, they also promise zero loggin and that they don't pass any information to any third parties and that they're GDPR compliant. They couldn't write it so boldly without risk of litigation unless that actually was the case, so I would consider it safe to use.
Re: Redesigned Google Fonts website
#88Earlier quoted context omitted.
npm is pretty good for downloading fonts when the alternative is downloading, hosting, and configuring webfonts by hand.
NPM is good also at downloading malware.
Re: Redesigned Google Fonts website
#89Earlier quoted context omitted.
Not if you download the zip and host it yourself - which you can do
> Not if you download the zip and host it yourself - which you can do I don't think it's quite the same, though! If you go to Open Sans, for example ( https://fonts.google.com/specimen/Open+Sans?query=open+sans ), and preview the CSS that it generates for the Regular style, then you'll get this: https://fonts.googleapis.com/css2?family=Open+Sans&display=s... You'll notice that it uses a lot of the unicode-range prope…
People self-hosting Montserrat are one bane of older browsers, because that seems to be a relatively popular font that got converted to a variable font file at some point, and which in browsers without variable font weight support then gets displayed at the thinnest possible font weight, which is really thin. (I concede that this is a niche complaint, but still…)