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
There are several ad-network type domains which I never want to enable. e.g. doubleclick.net, amazon-adsystem.com. These domains being blocked are never responsible for a broken site.
It would be great to be able to hide these domains - put them on some kind of blacklist. That way, when I visit a new page and it's a bit broken I can immediately see a small list of domains to try allowing to fix the site.
The text was updated successfully, but these errors were encountered:
Yes, I consider this an important issue. I am probably going to rewrite parts of the backend, which will then enable much better customization, and hopefully a better code structure. I think I will implement "Location Groups", which means that you can group several domains (locations) to a common name, e.g. facebook.com and facebook.net to [facebook] or doubleclick.net, amazon-adsystem.com, … to [blacklist]. As soon as we have the ability to add groups in the backend, we can think about how to implement the user interaction. Of course, we could assign properties to a group like "always hidden" or whatever.
Friday Aug 15, 2014 at 08:25 GMT
Originally opened as https://github.com/RequestPolicyContinuedTmp/requestpolicy/issues/10
There are several ad-network type domains which I never want to enable. e.g. doubleclick.net, amazon-adsystem.com. These domains being blocked are never responsible for a broken site.
It would be great to be able to hide these domains - put them on some kind of blacklist. That way, when I visit a new page and it's a bit broken I can immediately see a small list of domains to try allowing to fix the site.
The text was updated successfully, but these errors were encountered: