> go to about:config and setting privacy.resistFingerprinting = true in your Firefox browser
Two questions jump to mind:
Why isn't this the default in Firefox?
What is the downside? I.e., what can break by enabling this parameter?
Two questions jump to mind:
Why isn't this the default in Firefox?
What is the downside? I.e., what can break by enabling this parameter?
Here's what the settings do and what sort of side-effects you might experience:
Just of the top of my head:
- Timezone is set to UTC which means any web calendar input becomes confusing at best
- Canvases turn into random stripes, which leaves artefacts all over many websites
- Some websites outright block you as bots (twitch does this)
- Some web APIs break, which can be a pain if you're web apps that rely on them
You can add websites to a whitelist to avoid the downsides on some sites (privacy.resistFingerprinting.exemptedDomains) but it's a pain to do that for every website.
and the worst part is that this didn't changed the fingerprint generated by mentioned here site just increases suspect level to 9
After a while you develop and intuition for which browser to use depending on what you will be doing.
???
It definitely does. Are you talking about how it doesn't change between subsequent visits?
resistFingerprinting does seem to work against fingerprint.com in my experiments after clearing its website data and a browser restart.
> This setting may cause some websites to not display content or work correctly. If a site seems broken, you may want to turn off tracking protection for that site to load all content.
Some sites use light fingerprinting to provide features
I've had more issues personally with resist fingerprinting making major sites completely unusable (drupal.com, walmart.com..)