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

Ghostery ought to have a "Trust on all sites" button for each tracker. #148

Open
hrasmussendk opened this issue Jul 30, 2018 · 8 comments
Open
Assignees

Comments

@hrasmussendk
Copy link

@hrasmussendk hrasmussendk commented Jul 30, 2018

Description
Ghostery ought to have a "Trust on all sites" button for each tracker to prevent blocking the tracker on any site.

Expected Behavior
When pressed on one site the tracker should not be restricted ot blocked on any other site. Say I want to trust the Facebook social Like button, I would like to do so on all sites no matter where, to make me able to like a site I come across.

Actual Behavior
In the list of trackers (detailed view) there is three buttons for each tracker to either "Trust on this site", "Restrict on this site" and "Block on all sites", but no "Trust on all sites".

Steps to Reproduce

  1. In the browser, click the Ghostery toolbar button.
  2. Clock the Detailed view tap
  3. If collapsed, click Expand all
  4. Move the mouse to a tracker in the right pane
  5. When mouse moved, three trackers show up, "Trust on this site", "Restrict on this site" and "Block on all sites", but no "Trust on all sites": [O][Ø][X]

Versions

  • Browser: Chrome, Firefox
  • OS: MacOS (I think Windows as well)
  • Node:
  • NPM:
@Aziz-Ghostery
Copy link

@Aziz-Ghostery Aziz-Ghostery commented Jul 31, 2018

Hello:
We do not have this feature. This might be implemented in the future.
Thanks,

@christophertino
Copy link
Member

@christophertino christophertino commented Jul 31, 2018

@hrasmussendk This is something we've been aware of for some time. Our current "allow" option is really a pass-through where the request can still get picked up by anti-tracking or ad-blocking. We need essentially 3 states: block, no-state, allow. It's kind of confusing from a UI perspective, but our UX team has been kicking around some ideas.

Our 8.4 release roadmap has a reworked tracker list that combines details from anti-tracking and ad-blocking into the main Ghostery list. If all goes well, we should be able to add the "global allow" state to this design.

@klodoma
Copy link

@klodoma klodoma commented Mar 4, 2019

+1

@AJerm
Copy link

@AJerm AJerm commented May 7, 2019

Has this been added yet? I use a lot of sites with chat widgets like Intercom regularly and it's pain having to whitelist every one.

@christophertino
Copy link
Member

@christophertino christophertino commented Jun 6, 2019

Thanks for the reminder. We're working on a related feature to allow you to whitelist specific urls in Anti-Tracking, which should help this issue. That should be ready in v8.4.1 next month.

We're also working on a tighter integration of Anti-Tracking and the Ghostery tracker DB, so that the "allow" state in Ghostery is respected by both modules. This way we might not need to add that fourth "allow always" button. But we are still investigating.

@krishan
Copy link

@krishan krishan commented Jul 26, 2019

Ghostery blocks "Honeybadger" by default, which is not really a tracker IMHO, but an error reporting tool (which I rely on heavily for web development). I'm aware that others may feel that "Honeybadger" is tracking them, so I have no problem with the default.

But having some way to globally allow a tools like "Honeybadger" on all sites would be nice for those cases, where the line between "legitimate tool" and "tracker" is not so clear.

@MahatmaFatalError
Copy link

@MahatmaFatalError MahatmaFatalError commented Mar 13, 2020

any news here? "Trust on all sites" would be really great!

@christophertino
Copy link
Member

@christophertino christophertino commented Mar 18, 2020

Nothing yet, unfortunately. We're now looking to migrate our blocking over to declarativeNetRequest, as per the Chrome manifest v3 proposal. I'm hopeful that we'll be able to resolve this "trust on all sites" issue using dynamic rules.

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
9 participants