Updated "Disabling filtering by default"

garry-ut99 2024-07-18 10:34:10 +00:00
parent 3580bc2da1
commit 853f222b72
1 changed files with 12 additions and 3 deletions

@ -84,16 +84,25 @@ There are two ways to do this:
**Warning!** These are third party tools, I can't vouch for them, you will have to find out for yourself whether they work. **Warning!** These are third party tools, I can't vouch for them, you will have to find out for yourself whether they work.
### Disabling filtering by default ### Disabling filtering on all websites by default
That is not a feature supported by uBO. uBO is for people who share the view that the net is hostile by default and consequently uBO being disabled everywhere by default is incompatible with this view -- it would make no sense to have a malware list enabled by default just to have uBO disabled everywhere by default. AdGuard supports this mode, so you may want to use this instead. (Aka "invert whitelist" in AdGuard: [LINK](https://adguard.com/kb/adguard-browser-extension/features/filters/#allowlist)) By design, on purpose, that is not a feature supported by uBO, at least not in a way that is too easy to achieve and handy to use. uBO is for people who share the view that the net is hostile by default and consequently uBO being disabled everywhere by default is incompatible with this view -- it would make no sense to have a malware list enabled by default just to have uBO disabled everywhere by default. AdGuard supports this mode easily & straightforwardly by a simple on/off button switching, so you may want to use AdGuard instead.
Blocklist mode can be achieved by specifically crafted Regular Expression trusted site directive: However, blocklist mode in uBO can be achieved manually, by specifically crafted Regular Expression trusted site directive:
/^((?!example\.com|different\.example\.net|another\.example\.org).)*$/ /^((?!example\.com|different\.example\.net|another\.example\.org).)*$/
With this directive all domains separated by `|` characters will be treated as _blocklisted_, and uBO will be enabled only on these pages. With this directive all domains separated by `|` characters will be treated as _blocklisted_, and uBO will be enabled only on these pages.
There already exists a pile of duplicated requests to implement the feature. Requests to implement the feature to be identical as in AdGuard, were always declined and will not be accepted:
- (05.2016) [Whitelist by default](https://github.com/gorhill/uBlock/issues/1623)
- (11.2017) [Option to enable/disable by default](https://github.com/gorhill/uBlock/issues/3202)
- (05.2019) [ublock is off by default and only the sites you specify will be blocked.](https://github.com/uBlockOrigin/uBlock-issues/issues/586)
- (03.2021) [Feature: invert the custom rules to a list "allowed to filter"](https://github.com/uBlockOrigin/uBlock-issues/issues/1534)
- (16.2024) [Please add a fourth mode - "No filtering".](https://github.com/uBlockOrigin/uBOL-home/issues/150)
Hence there is no point in spamming the issue tracker by creating new duplicates over and over, discussion and sharing opinions should be continued in already existing threads, new threads will be labeled as `invalid` or `duplicate` and closed.
### Other details ### Other details
If you re-enable uBO by clicking the big power button in the popup while a trusted site directive you handcrafted is in effect, your handcrafted directive will simply be commented out. This way you can bring it back to life if ever you clicked the button by mistake. If you re-enable uBO by clicking the big power button in the popup while a trusted site directive you handcrafted is in effect, your handcrafted directive will simply be commented out. This way you can bring it back to life if ever you clicked the button by mistake.