Privacy Badger fails "Do Not Track" test
Closed this issue · 5 comments
Privacy Badger fails the DNT test in Chrome and Firefox. (This isn't new behavior, I think it's been broken for a while.)
To be clear, Privacy Badger supports EFF's DNT policy, and the test should pass.
This is a new behavior of Privacy Badger, Panopticlick's logic here has not changed.
Disabling local learning has unblocked the Panopticlick pseudo-tracking domains trackersimulator.org and eviltracker.net. These domains (which do not have DNT policies behind the /.well-known path) must be blocked in order for Panopticlick to detect that a similar domain with the DNT policy present has been unblocked. The behavior of the DNT policy checkmark is contingent on the non-DNT policy domains being blocked.
I don't think this has anything to do with disabling local learning. I'll look more into this next week, but I filed this issue before starting work on the local learning PR.
OK, I see, Privacy Badger broke this test as of the 2020.5.12 update: EFForg/privacybadger#2708 (comment)
Let's continue in EFForg/privacybadger#2708
Ahh, I get the connection to local learning now. While the DNT test was broken by no longer checking for DNT policies until after learning to block the domain, it sounds like disabling local learning by default would have also broken the test.