-
-
Notifications
You must be signed in to change notification settings - Fork 381
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 ability to temporarily pause Privacy Badger #827
Comments
One idea is to split the disable button into disable / pause. Also, this changes requires some way to see paused domains. An idea is to add a tab on the settings gear's options page to see which domains have been paused. |
@geminiimatt @paulate can you explain to me what the user story is here? I.e. why might a user want to pause privacy badger for a domain instead of disabling it on that domain. Thanks! |
I'm not geminiimatt or paulate, but I came here looking for a solution because sometimes I do click-to-donate sites or survey sites, and it would be nice to be able to just pause like I could with Ghostery. With the donation sites, I have Privacy Badger off for the main site, but trying to figure out all of the other sites that may be tracking for the purpose of giving the organization credit would be daunting. Similar situation with survey sites. Also, being able to pause could be worthwhile for troubleshooting, when you're trying to determine if the blocker is messing with something you don't want blocked. Of course, that's being able to pause the whole thing, not just by domain. As it is, if I want to turn PB off briefly I have to turn it off, which involved closing and reopening the browser. Not optimal. My $.02 as a user :-). |
Since I submitted the suggestion an option to disable privacy badger for a |
Disable for a specific site, yes -- I've done that :-). I was addressing the issue of why a use might want to pause Privacy Badger overall, rather than just turn it off/on for a specific site. |
@ljwolfe Hmm, this is possible, albeit not necessarily in the most obvious manner. Right-click the Privacy Badger extension, then select "Manage Extensions," then uncheck the box next to "Enabled" for Privacy Badger. This will essentially have the same effect. I think this is probably the best way to go about it, since it's not likely going to get used enough to warrant a permanent button in the UI. Does that sound OK? |
That's interesting, last time I tried that it said the changes would go into effect after I restarted the browser, which as I said above is not an optimal way to pause. (Technically, it still says that, but only for a moment and then the change goes into effect.) So yeah, that works -- thanks :-). |
Ah, that totally makes sense. Great, glad it works! I'll close this issue since everything seems to be in order now. |
While as noted above, there is a workaround, we may want to consider adding a dedicated "Pause" button for temporarily disabling Privacy Badger across all sites. The "disable on this site" button is not the right fit for all situations. Disabling Privacy Badger through your browser's extension management page is less clear/more cumbersome. Regarding Privacy Badger and online survey sites:
Regarding Privacy Badger and one-off sites:
It's still not clear, however, what the UI for this should look like. |
Also adding my vote for a pause button or have the"disable for this site" feature follow you through affiliate links. My chrome does not automatically reenable extensions that have been disabled. Privacy badger breaks cash back affiliate links like @sendstephen mentioned |
as a user blocking spying ads and inivisble trackers: the idea behind this ticket is to create a way to "pause" privacy badger for a domain (instead of disable). this is an effort to temporarily block a domain.
one way this could work would be that the domain is blocked but only until the browser session restarts or the browser is closed and reopened.
One of the issues with this change is the way it effects the UI. Ideas and suggestions are appreciated.
The text was updated successfully, but these errors were encountered: