Look at the source code of Twitter or Facebook. It's intentionally obfuscated and mangled, probably in part to fuck with ad blockers.
I have a few user stylesheets (even a little custom Firefox extension to block one user's comments on a site I frequent), but the sites I'd really like to use them on largely don't make it possible to do so.
Look at a Facebook ad in your browser's web inspector, for example. The "Sponsored" tag is made up of 31 different randomly named span tags. https://imgur.com/a/AHZL8ko
> Look at a Facebook ad in your browser's web inspector, for example. The "Sponsored" tag is made up of 31 different randomly named span tags. https://imgur.com/a/AHZL8ko
Tangential, but I love the image of a frustrated PM at Facebook hearing the news that "hey, you still have to make this label readable to screenreaders," necessitating an `aria-label` with the plain-text content "Sponsored", which makes all their span-chopping junk completely irrelevant to adblocker rules that can now just look for that string as an anchor :)
It took a while to setup, but fixing the problem in the font rendering layer has worked really well. Several years ago - after being annoyed by blurry/bad fonts, extremely bad hinting, and other font problems - I spent a few weeks investigating the way fonts are rendered and a few more weeks comparing many different fonts and various permutations of rendering/hinting methods. The result of all that work included a set of fontconfig files with long lists like this;
<fontconfig>
<alias>
<family>Arial</family>
<prefer><family>Ubuntu</family></prefer>
</alias>
<alias>
<family>Helvetica</family>
<prefer><family>Ubuntu</family></prefer>
</alias>
<!-- Many more aliases that -->
<!-- force fonts to Ubuntu. -->
<alias>
<family>sans-serif</family>
<prefer><family>Ubuntu</family></prefer>
</alias>
</fontconfig>
This way, my font overrides happen in any software that uses fontconfig (i.e. most X11 software that uses TrueType fonts).
I assume any problem or slowness I have with a website on Safari in MacOS or iOS using a content blocker is due to the website wanting to track me or otherwise for advertisement purposes.
You don't need to use website font's. You can configure the browser to use your chosen fonts. It's a normal accessibility option on the browser config page.
The only problem is devs who use fonts for icons, which is as stupid as it sounds.
(It would be nice to also have minimum font weight setting, not just minimum size, because some designers just can't be helped and use <=200. Then most of the issues with typography on the web would be solved.)
The business model where you need to stop your users from hiding ads was not compatible with things like user stylesheets. If CSS compilation didn't obfuscate class names and such, it'd be quite compatible.
