Re:How tracking pixels work
by boring_twenties on Friday December 20, 2019 @04:32AM
(#21842791)
The trouble with this is that many websites nowadays use fake fonts where the glyphs are the icons that make up the UI. Without the font, you don't see the icons, and thus have no idea what the various buttons and labels do or mean.
It annoys the crap out of me because I'd love to disable fonts for the simple reason that having every page use its own font for text is distracting. I don't need my eyes to adjust to a new font for every page. I want to pick my favorite font and only ever see that one.
On a completely unrelated note, I'll never forgive Mozilla for removing support for gopher urls in the browser.
https://decentraleyes.org/
Recommended by privacytools.io
Not only fonts but any resource.
Re:How tracking pixels work
by lern_too_spel on Thursday December 19, 2019 @02:24PM
(#21838272)
The font resources are hosted on a cookieless domain and sent with caching headers. None of this applies.
The reason Google is hosting fonts is to make the web an attractive platform, so they can monetize you in other ways.
So my IP address never ends up in their logs?
Re:How tracking pixels work
by lern_too_spel on Thursday December 19, 2019 @02:57PM
(#21838580)
IPV6 privacy extensions make IP addresses have very little tracking value, but this article is about tracking pixels, and Google Fonts clearly don't apply here. If you set your Referrer-Policy headers correctly, Google doesn't know which pages your users are visiting.
Huh, I had never heard of remote fonts.
Think again.
If you block tracking pixels you should also block the loading of external fonts. Extra bonus: fast loading pages.
Some CDN also exist for this reason.