You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The menu that pops up after clicking on the red flag icon shows blocked connections and authorised connections. Great. Among the blocked connections, some are, let's say, "regular" connections and others are known trackers, indicated with a stop sign. Useful. I believe it would be even more useful to have a way to batch allow all "regular" connections, on top of the existing way to allow all connections (temporarily or not).
What should happen?
The idea is that, sometimes, RequestPolicy will break a webpage display and you may not know which connection to allow (when it's not clearly a cdn) but you're still fairly ok with allowing most connections. However, you still don't want to allow connections to "amazon-adsystem" and the likes, because you know that's not what is breaking the webpage display. For now, we have the options to either 1) allow connections one by one (and there may be many) or 2) to allow all connections, which will include clear trackers. Therefore, I think it would be great to have a "allow all but clear trackers" option (so all but the ones displaying a stop sign).
I hope this is useful feedback and, once again, thanks a lot for the
good work!
Best,
J.
The text was updated successfully, but these errors were encountered:
Hey,
I am a regular user of RequestPolicy (and now its Continued version, which was really a game changer); thanks a lot for all the good work!
There is a feature that I do not see included but that I believe could be useful for many users.
Browser and Add-ons:
RequestPolicy settings:
Steps to reproduce:
Nothing special, regular use.
What happens?
The menu that pops up after clicking on the red flag icon shows blocked connections and authorised connections. Great. Among the blocked connections, some are, let's say, "regular" connections and others are known trackers, indicated with a stop sign. Useful. I believe it would be even more useful to have a way to batch allow all "regular" connections, on top of the existing way to allow all connections (temporarily or not).
What should happen?
The idea is that, sometimes, RequestPolicy will break a webpage display and you may not know which connection to allow (when it's not clearly a cdn) but you're still fairly ok with allowing most connections. However, you still don't want to allow connections to "amazon-adsystem" and the likes, because you know that's not what is breaking the webpage display. For now, we have the options to either 1) allow connections one by one (and there may be many) or 2) to allow all connections, which will include clear trackers. Therefore, I think it would be great to have a "allow all but clear trackers" option (so all but the ones displaying a stop sign).
I hope this is useful feedback and, once again, thanks a lot for the
good work!
Best,
J.
The text was updated successfully, but these errors were encountered: