Comment by scrollop
Comment by scrollop 6 hours ago
PSA Don't use chrome.
Comment by scrollop 6 hours ago
PSA Don't use chrome.
Definitely a good STEP1, but it’s not like Firefox and Safari are finger printing secure.
Firefox does pretty damn well though, especially with privacy.resistFingerprinting set to true
Modern Safari is pretty damned good at randomizing fingerprints with Intelligent Tracking Prevention. With IOS 26 and MacOS 26, it's enabled in both private and non private browser windows (used to be only in private mode).
All "fingerprint" tests I've run have returned good results.
I haven’t tried 26, but I remember it didn’t used to be so great.
what about duck duck go? We need a simple chart: 1. What browsers are good at resisting finger printing 2. tell for each browser, does it work on android ad ios and apple and windows and linux 3. what setting are needed to achieve this
for bonus points, is there no way to strip all headers on chrome on control it better?
You can change the reported UA header independently of the UA you use.
If I was a fingerprinting company, I'd be cross-referencing signals between browsers for sure.
If the browser header says windows but the fonts available says linux, that's a very distinctive signal.
And if the UA says Chrome but some other signal says not-chrome, that's very distinctive as well.
The article also mentions this, and suggests the UA is not a silver bullet. That said, they didn’t go into specifics. I’m assuming there are other details that correlate to particular browsers that will betray a false UA. Plus, having a UA that says Chrome while including an extension that’s exclusive to Safari (tor example) will not only contradict the UA, but it will also be a highly distinctive datapoint for fingerprinting, in and of itself.
don't use the same browser regardless - the key is to compartmentalise.