How does Tracking Protection compare with EFF’s Privacy Badger? Do they share underlying technology or are they completely different? Thanks!
THe same reason why I am using privacy badget and not the new experiment.
I guess you would have to compare their blocking lists. In theory these are equivalent, but my guess is that they don’t have 100% identical lists. After all the definition of tracking may vary among people and organizations.
AFAIK Firefox is using Disconnect’s blocking list.
Correct, we use Disconnect’s block-list. As I understand it, EFF Privacy Badger builds a client-side block-list based on cookie usage heuristics.
We also enable users to submit problems & breakage reports to teach us how to improve privacy without breaking the web.
I think that privacy badger is more powerful and complete with the ui that enable to learn what the page do, we need more web literacy and is a simple addon like ublock origin that do the same things (a list of third part resources).
I agree that Firefox tracking protection should do a better job on educating people on what’s going on, what are we blocking and why.
We’re working on UX for listing third party resources. The UX is currently being spec-ed and you can follow progress here: https://github.com/mozilla/blok/issues/119
2 Likes
Just to prevent some myths from spreading: Privacy Badger does not use any block “lists”. Instead it is purely based on algorithms…
The algorithm seems to build up a client-side block list:
https://github.com/EFForg/privacybadgerchrome/blob/master/src/heuristicblocking.js#L56-L86
1 Like
Yeah, I just meant it is no static block list. That’s a key difference to all other tracking blockers mentioned in this or other threads here.