Tell me about config setting "privacy.resistFingerprinting" TRUE vs CanvasBlocker etc AddOns
If I set privacy.resistFingerprinting to true, should I disable things like CanvasBlocker, which says: > This add-on allows users to prevent websites from using some Javascript APIs to fingerprint them.
Users can choose to block the APIs entirely on some or all websites (which may break some websites) or fake its fingerprinting-friendly readout API. ... IMPORTANT: you should only have ONE addon/setting set that protects an API. Otherwise you could face massive performance issues. ...
But setting privacy.resistFingerprinting to true and/or using the new fingerprinting protection introduced with Firefox 67 is fine.
Protected "fingerprinting" APIs: canvas 2d webGL audio history window (disabled by default) DOMRect navigator (disabled by default) screen
Wszystkie odpowiedzi (3)
The Fingerprinting block under Tracking Protection uses a short list of servers known to compute or track fingerprints. Simple. Turn or keep that on.
I personally do not think the results of using the privacy.resistFingerprinting preference are worth the trouble. Telling the world a different Firefox version, different screen resolution, and potentially a different OS, and overriding site zoom levels, may make it harder for fingerprinters to ascertain the true values, but they may not make your browser look less unique.
I don't know about the other comments. What is the source?
quote is from Canvasblocker addon info page
FF ver 68.3.0 esr does not seem to have "Fingerprinting block under Tracking Protection "
FireFoxSucks said
FF ver 68.3.0 esr does not seem to have "Fingerprinting block under Tracking Protection "
ESR will pick up the newer features from Firefox 69-77 when it moves to Firefox 78 as its base. Or whatever later version it turns out to be.