123
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Mar 2026
123 points (91.3% liked)
Linux
12991 readers
595 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
You can't really "block" fingerprinting. You can obfuscate it a bit, but the fingerprinting process happens server side, not on your device. So whether or not your system sends whatever age verification signal becomes a part of its fingerprint.
It's not just server-side: A lot of fingerprinting happens client-side, for example using a canvas to check what features your graphics card supports. You can see this in action via services like https://coveryourtracks.eff.org/ or https://amiunique.org/
That's not the fingerprinting happening client side, that's just information supply. Fingerprinting is about what the server does with that information.
Yeah, but the countermeasures are client-side because that's what you can control. And some kind FOSS devs out there make it easy to start somewhere decent.
Of course you can block fingerprinting. See Tor Browser. Everyone looks the same.
Or you can change your fingerprint every 30 seconds with a plugin like chameleon.
You know it works when evil sites all ban you because they can't fingerprint you and track you between sessions anymore
That's not blocking the fingerprinting, that obfuscating the data. The fact that you are doing that itself becomes part of the fingerprint being built. Services like Tor or Chameleon don't stop the fingerprinting process running, they just make it more difficult (but not impossible) to tie the fingerprint to your actual identity.
It's making the fingerprinting efforts useless. Sure, they can do it, but many of us are blocking them from being able to uniquely fingerprint and track us across the internet