On Panopticlick with Firefox Mobile, with Ghostery plugin active in a normal tab I get 18 bits of info, in a private tab I get 17 bits, but the best is a private tab with Ghostery paused - then I get 16 bits, and equal results on the other parts.
Are privacy plugins really redundant in this day and age? Or is the test too incomplete to reflect their value?
The second article CiPHPerCoder linked seems to be more focused on the VPN marketing aspect. A more interactive approach might be https://faq.dhol.es/@Soatok/cryptography/which-vpn-service-w...
Of course, that makes total sense, because many of the factors that can identify your system have little to do with the browser, but are determined by the underlying system: fonts, display, date/time information, graphics fingerprints, etc.
17.62 Chrome 75.0.x normal (non-incognito)
16.62 Chrome 75.0.x incognito
15.62 FF 68.0.1 (Private doesn't seem to make a diff, I get the same score)
Seems like in Chrome, at least, the most offending (most unique) "characteristic" is HTTP_ACCEPT Headers, which looks something like text/html, */*; q=0.01 gzip, deflate, br en-US,en;q=0.9,fr-FR;q=0.8,f...
If there is a good way to control this (FF does a much better job -- could be tied to plugins and such tho), one could further reduce the number of identifying bits.Chrome seems to do better (less unique) in both Hash of canvas fingerprint and Hash of WebGL fingerprint. I've summarized the main differences I see below, seems like combining the best of Chrome w/ the best of FF would result in even better privacy:
https://i.imgur.com/QQQ6R85.png
Edit: I think Chrome's HTTP_ACCEPT Headers is like that because I've installed/enabled many languages in it for l10n testing. I'm removing them now, which should make Chrome get a better score than FF.
So, the true number is somewhere in-between.