Join Nostr
2026-09-07 18:15:02 UTC
in reply to

npub1hx…sg75y on Nostr: See what was talked about here: Disabling the JS wouldn't actually stop it in ...

See what was talked about here:
https://discuss.grapheneos.org/d/5775-device-fingerprinting-test-results-concerns-and-questions/20 https://discuss.grapheneos.org/d/19692-vanadium-fingerprinting/4

Disabling the JS wouldn't actually stop it in practice, because you'd stand out incredibly by the lack of data being provided in comparison to almost everyone else on the planet. The service just isn't adapted to that scenario and it would be trivially easy to set up a library to do it. You should use web services that respect your privacy and don't do such nefarious things as a first priority. No browser's fingerprinting protection works well at all and is highly dependent on having a crowd. On most implementations it's randomizing data points and hoping that the service admin isn't smart enough to correlate or to track the points that do not change.

The more invasive a site is about fingerprinting then any resistance towards it is increasingly less possible, final boss being services requiring you to KYC to use it. This would apply even for browsers with strict settings that do not change. Take a look at your display size, locale, timezone, GPU, for example or even benchmarking the device performance. In reality the fingerprint suggests a GrapheneOS user of a certain device with a VPN and it tries to keep that as much as it can which goes under the radar for more naive services.