Browser Fingerprinting: How to Stay Private

There are two approaches to dealing with fingerprinting I&#x27;ve seen. The first is to hand over a ton of data to fingerprinters but try to get your fingerprint to match a lot of other people&#x27;s so you can &quot;hide in the crowd&quot;. This is what TOR browser does and it seems extremely fragile and unlikely to work since it&#x27;s a never-ending game of whac-a-mole where you have to account for every single possible thing that could ever possibly make your fingerprint different for it to be effective.<p>The other approach is to try to provide as little information as possible with much of that information being inconsistent so that your fingerprint is always unique across sessions&#x2F;requests. This seems a lot easier. Simply disabling javascript by default does most of the work for you. You&#x27;ll still have anything sent over in HTTP headers to worry about (and that can be randomized), but hardened firefox with JS disabled should make most of the data used to fingerprint your browser inaccessible.

See for example: <a href="https:&#x2F;&#x2F;github.com&#x2F;fingerprintjs&#x2F;fingerprintjs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;fingerprintjs&#x2F;fingerprintjs</a><p>They evade ad-blocking easily by using custom domains or by distributing the script using popular sites like Github, NPM, etc; This makes extensions like NoScript necessary.