open-webfonts VS hush

I just went through the process of self-hosting Google Fonts. The process is actually surprisingly tricky.

Google Fonts lets you download fonts for desktop use, in the form of .ttf or .otf rather than the .woff[2] with one file per Latin/Greek/Vietnamese/etc. script served by Google Fonts itself. If you want the same font-embedding CSS as Google Fonts itself, you can use https://google-webfonts-helper.herokuapp.com/fonts (a font browser, outdated, doesn't support font-display: swap), or https://nextgenthemes.com/google-webfont-downloader/ (a converter from Google Fonts CSS URLs to downloadable font packs, supports font-display: swap, it works well but I chose to not host the large CSS files with embedded fonts in base64 format).

As a technical curiosity, the second site can suffer a race condition resulting in partial or broken file downloads (I never tested what happens), if two people request the same font bundle at the same time, and they overwrite each other: https://github.com/nextgenthemes/open-webfonts#bug-reports-a...

I wish browsers would give users an option to set the default font-display policy to swap.

Ah thanks! Looks like that extremely obnoxious one can’t be blocked: https://github.com/oblador/hush/issues/54

Hush does that for free and is OpenSource!

Maybe this will do the trick: https://oblador.github.io/hush/

Please correct me if I am wrong but the app hush was not brought up. https://github.com/oblador/hush, I know it’s not security per-say but it helps from becoming numb to notifications on the web.

No I don’t think, but is a good law, only badly implemented, just use a cookie banner blocker like Hush -> https://oblador.github.io/hush/

Hush is a great ad-block https://oblador.github.io/hush/ instructions on the page

> Declining is always a multi-step process with various checkboxes.

https://oblador.github.io/hush/

You're welcome!

Hush: another option to deal with cookie banners by simply blocking the banners outright.