Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please remove the hardcoded /fp2.js rule - EFF panopticlick tracking tests unless it's actually compromising your privacy #371

Closed
jawz101 opened this issue May 7, 2018 · 3 comments

Comments

@jawz101
Copy link

jawz101 commented May 7, 2018

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.

@ryanbr
Copy link
Owner

ryanbr commented May 12, 2018

"fp" is a finger print script, not sure why panopticlick is using this name?

@ryanbr ryanbr closed this as completed May 12, 2018
@jawz101
Copy link
Author

jawz101 commented May 12, 2018

Because it tests for fingerprinting?

@jawz101
Copy link
Author

jawz101 commented May 12, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants