You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't see the point of simply blocking /fp2.js by hardcoding it in a list.
enhancedstats-addon.txt
If their purpose is to test certain fingerprinting techniques and you learn if you're being protected from various techniques, why prevent a test script? You're effectively breaking the test of techniques that thousands of actual tracking companies use by blocking a harmless test script.
I liken this to cell phone companies overclocking your phone when running benchmark apps. It helps your brand but we're actually trying to test something specific.
The text was updated successfully, but these errors were encountered:
It would be nice to know that I'm blocking a particular thing like reading my available fonts, not that a file named fp2.js was used. I mean people who actually fingerprint can name the script anything else and it gets allowed.
I don't see the point of simply blocking /fp2.js by hardcoding it in a list.
enhancedstats-addon.txt
If their purpose is to test certain fingerprinting techniques and you learn if you're being protected from various techniques, why prevent a test script? You're effectively breaking the test of techniques that thousands of actual tracking companies use by blocking a harmless test script.
I liken this to cell phone companies overclocking your phone when running benchmark apps. It helps your brand but we're actually trying to test something specific.
The text was updated successfully, but these errors were encountered: