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

Add option to whitelist website from adblocking but not from anti tracking #493

Open
ghost opened this issue Feb 5, 2020 · 4 comments
Open
Assignees

Comments

@ghost
Copy link

@ghost ghost commented Feb 5, 2020

Please add the option so users can whitelist websites from the adblocking feature individually (so I can support them with advertising) but keep the anti tracking protection enabled (so private data points are anonymized from networks requests). Basically I am asking for the option to use the adblocking and anti tracking tools of Ghostery on a per website case instead of the actual on/off for all pages

Currently you can trust a website but that unblock all blocking behaviour thus removing also the privacy protection. The other option is whitelisting trackers individually per websites but this has 2 problems:

  1. You need to manually whitelist dozens of trackers on each website which is cumbersome
  2. The above problem requires users to be familiar with which trackers are advertising and which are privacy invasive. Most people don`t know that

I also would like to jump on the wagon requesting these feature as well #148
These options would give users even more choice and control of their browser experience

Thanks

@ghost
Copy link

@ghost ghost commented Feb 8, 2020

This is a great feature to have and one I had opened an issue about before even checking it here. Since mine is closed now I just want to add something here.

Having an option to disable blocking in terms of ads and trackers but not anti tracking would put Ghostery in a unique position among other privacy/adblock extensions that just have an all or nothing approach in terms of blocking ads and trackers.

As mentioned, it would also benefit website owners that the user chooses to help/support since they could get their analytics and ad revenue, just like in Cliqz Browser. This might require a more aggressive cookie blocking (which I think is already necessary since Firefox for example already blocks a good amount of them now) but anti-tracking can easily handle it.

Plus doing it like in the Cliqz browser where when you disable adblock for example it asks if you want to disable it for the current domain or for all of them makes a lot of sense.

@christophertino
Copy link
Member

@christophertino christophertino commented Mar 2, 2020

I like this option too. The difficulty will be implementing it in such a way that it's clear to the user.

@ghost
Copy link

@ghost ghost commented Apr 17, 2020

@christophertino My suggestion is to just remove the "trust site" button altogether (Pause Ghostery is fine), and like in Cliqz Browser, when you click on the Enhanced Ad Blocking button let it ask if it should apply globally or for the current site. Also, for Anti Tracking and Smart Blocking.

Edit: As I honestly believe this would be a good way to achieve the desired outcome, I want to add that if the user chooses to turn off ad blocker for all websites the options should be flipped. Now when clicked again, it should show whether to turn ad blocking on for that specific website or globally. I generally prefer not to block first-party ads so that's why I've added this :)

@yokoffing
Copy link

@yokoffing yokoffing commented May 19, 2020

@christophertino My suggestion is to just remove the "trust site" button altogether (Pause Ghostery is fine), and like in Cliqz Browser, when you click on the Enhanced Ad Blocking button let it ask if it should apply globally or for the current site. Also, for Anti Tracking and Smart Blocking.

I think this is a fantastic suggestion!

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

Successfully merging a pull request may close this issue.

None yet
3 participants