What does that do for fontawesome-style fonts (icons in the private area) that websites love to use instead of SVGs and text labels?
I personally block fonts via uBlock Origin, which lets me allow them for the subset of websites I visit regularly enough that I'm okay with allowing fontawesome-style fonts.
Firefox is smart enough to not block fonts that are used to render PUA characters.
It doesn't help with icon fonts based on ligatures instead of PUA characters (Google's Material Design framework seems to do this) but we can't have everything.
blocking remote fonts in uBlock Origin has zero effect on Twitter, just tried, unless you mean something else, in that case please enlighten me how to have back left column with same font as before
The first image shows https://twitter.com/newsycombinator with devtools on the right showing that the computed `font-family` for that one span has "TwitterChirp", and the uBO logger at the bottom showing that chirp-*.woff fonts were blocked by my uBO rules.
The second image is the Fonts tab of the dev tools showing that the font that the browser is using is Roboto, which I have available locally.
As for how I do it, see https://news.ycombinator.com/item?id=26284124 . If you don't want to go that far, you can still create a rule just for twitter.com that blocks just the chirp*.woff URLs.
I personally block fonts via uBlock Origin, which lets me allow them for the subset of websites I visit regularly enough that I'm okay with allowing fontawesome-style fonts.