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

Bundle a list of known trackers #1333

Closed
mrphs opened this issue Apr 21, 2017 · 5 comments
Closed

Bundle a list of known trackers #1333

mrphs opened this issue Apr 21, 2017 · 5 comments
Labels
enhancement heuristic Badger's core learning-what-to-block functionality

Comments

@mrphs
Copy link

mrphs commented Apr 21, 2017

There are some sites that we know for sure 100% are always tracking users. I think privacy badger should be shipped with a list of these trackers. or if you don't want to make it the default (which I think should be, anyways)... having a button in the settings where I can download and import known trackers would be dope!

@GeorgeWL
Copy link

GeorgeWL commented Jul 5, 2017

I know we don't want to be overly similar to Adblock or uBlock, but there's a particularly good part which I do feel would fill in this problem.

screenshot-www nationalcrimeagency gov uk 2017-06-22 13-33-02

@cowlicks
Copy link
Contributor

cowlicks commented Jul 5, 2017

Please use ublock origin. Privacy Badger differentiates itself by using heuristics instead of whitelists and blacklists.

The reason we want to avoid lists is because access to the list becomes increasingly valuable as the number of users grow. This creates a conflict of interest between us and our users.

Also, as you can see, there are other extensions that already do this very well.

I think the actionable items here are:

  • do a better job explaining our philosophy of why we don't want lists
  • recommend using ublock origin in conjunction with PB

I'd like to close this as 'wontfix' and create a seperate issue with the two items above, but I'll cc @ghostwords for a 2nd opinion

@cowlicks
Copy link
Contributor

cowlicks commented Jul 5, 2017

These probably be good to have in the FAQ. This is related to emphasizing why badger doesn't block stuff immediately, issue #1374

@ghostwords
Copy link
Member

I started a more technically-oriented FAQ on the wiki: https://github.com/EFForg/privacybadger/wiki.

@ghostwords
Copy link
Member

ghostwords commented Jul 5, 2017

While we shouldn't ever get in the business of compiling lists of things for Badger to block, I think there is space for us to provide some sort of community learning features down the road. People could opt in to share their Badger's learning, which would then get auto-aggregated and loaded by new Badgers. I guess let's close this one and subscribe to #1299 instead.

@ghostwords ghostwords changed the title provide a list of known trackers Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement heuristic Badger's core learning-what-to-block functionality
4 participants