Firefox tries but this is very hard to fight against. Most of the obvious holes were closed long ago. Now these fuckers use normal browser functionality that can't be disabled and record how it subtly differs (in various ways like execution time of functions) between different combinations of browsers, OSes, hardware, etc. This information alone is enough to create a more or less unique fingerprint.

The only reliable solution is to completely get rid of client-side code execution like JavaScript and WebAssembly and return to static web pages. Which of course won't happen.

Yeah, a lot of these fingerprinting capabilities seem like things that should be behind permission requests, if not outright disabled entirely.

Like ok, I get that if someone wanted to make a browser-based audio editing tool, it might be useful for javascript to be able to sample the output side after effects have been applied. But I don't want every single fucking website to have that capability by default. I'm not even sure I want websites to be able to play audio at all without permission.

By default, it should be a one way pipeline. Whatever they put into the pipeline gets displayed or played but they can't see any of the system-specific results. I'd prefer the standard be designing pages to work with any resolution instead of letting them query the exact pixel dimensions, which varies per device and I suspect fingerprinting was the reason they were designed like that in the first place.

librewolf