Personal filters and rules for AdGuard/uBlock Origin
I can't guarantee these filers won't cause problems. If you found problems, report it by filling in all the mandatory items in Issue template; otherwise reports can be ignored. Anyone who uses any of my filters/codes shall be deemed to have agreed that I have no responsibility or liability for costs, losses, damages, etc. arising from the use of the filters/codes. Unless Subscribe link is provided these filters are assumed to be copied and pasted, or imported, into My filters/rules (uBlock Origin) or User Rules (AdGuard).
adguard
Do NOT check the "Trusted" box if you subscribe Social media Plus and/or Tracking Protection Plus! Because not needed. Trusted filters can inject javascript into pages and thus can potentially be risky. Of course I'm not going to do anything nasty with any of my filters, but imagine what if my Github account was hacked. I'd like to encourage a basic security practice.
AdGuard Social media filter tends to rely too much on cosmetic filters IMHO. This list consists of network filters only and complements Social media filter.
||connect.facebook.net^*/sdk.js||platform.twitter.com/widgets.js||static.evernote.com^$third-party
are commented out as some people will need them. Those who don't need them can add them to User Rules without the initial !.
Exclusion:
- Follow buttons & comment widgets - they can be useful to some people and often Social media filter doesn't block them.
Update (2021-03-16): Many things have changed since I published this list. Now I'm a maintainer of the official AdGuard lists so tend to add trackers directly to AdGuard Tracking Protection filter. Therefore, Tracking Protection Plus became more of an experiment field for rules I'm not much sure about false positive. When I published this list, there were many unique entries not found in any other lists, but EasyPrivacy has caught up and to avoid redundancy for those who use all the AdGuard Tracking Protection, EasyPrivacy, and this list I consolidated to EasyPrivacy's writing as far as the likelihood of false positive by doing so is not high. As a result, now this list has many duplicates with EasyPrivacy.
AdGuard Tracking Protection filter is probably the least false-positive prone anti-tracking list; however, it comes with its own cost of less coverage on average which this filter aims to complement. Some of bug reports are commented out but you can add them to User Rules without the initial !. Some rules are taken from EasyPrivacy after I confirmed they 1) are actually in use, 2) are not covered by AdGuard Tracking Protection filter, and 3) apparently haven't caused false positives on my regular browsing.
Inclusion criteria:
- Didn't and less likely to cause false-positive
- Useful to English user
- Useful to default-deny script settings such as uBlock Origin medium mode
Exclusion:
- Trackers covered by Simplified domain names filter or Firefox tracking protection
- Trackers blocked by uBlock Origin medium mode with /medium_mode/ublock-dynamic-rules.txt minus EasyPrivacy & Peter Lowe's list
About CNAME tracker:
Update (2021-03-16): Many people now know AdGuard published CNAME tracker lists. As I wrote below, one should note even without such lists or CNAME uncloaking EasyPrivacy already blocked at least 70% of CNAME tracker all over the world. From the perspective of a filter author, CNAME tracker is no different from other tracker - we inspect script or request and if it sends unnecessary user data we block it unless doing so causes trouble. In fact, I am the first one opened an issue in the AdGuard's CNAME tracker repository to expand its coverage - some of CNAME tracker I proposed were not blocked not only by AdGuard but also by other services such as NextDNS because the trackers were unknown to them. CNAME uncloaking is done by checking the tracker's canonical name in known tracker database so is helpless against unknown tracker, and there are always such trackers out there.
I really don't understand why it's so special to some people. Apparently they still believe subscribing a dedicated anti CNAME tracker list is mandatory to block them if a DNS-level blocker is not deployed on an other layer. The fact is EasyPrivacy alone, or the combination of AdGuard Tracking Protection and my list, blocks about 70% of CNAME tracker while DEFINITELY many other analytics and trackers have slipped whatever your lists through, as long as you visit many sites. You prefer to double-lock a window and keep the door open? CNAME tracker is NOT at all harder to block and filter authors know much more serious circumvention. Of note, Google provides Server-side Tagging as announced in early 2020. This utilizes A or AAAA record, which is very well expected at the time of the CNAME fuss1. It's weird those who made fuss about CNAME cloaking seem to be silent about this. All these remind me that many people keep NoCoin despite EasyPrivacy + uBlock filters - Resource abuse covers 99% of them, and that others keep Adblock Warning Removal with a completely wrong assumption it has something to do with anti-adblock wall. Don't be fooled by misinformation on the Internet.
1: uBlock Origin can now fight against this by strict3p option.
Check Trusted box if you use this list as you trust me! To get the most of the list, you have to turn HTTPS filtering on AND DNS filtering OFF. It's not that I recommend to turn DNS filtering off generally, but that this list requires doing so for full function.
Enhances anti anti-adblock capability of AdGuard by generic filters. Works on AdGuard for Windows, AdGuard for Android, AdGuard for Mac, and AdGuard Browser Extensions but not for AdGuard for Safari, AdGuard for iOS, and AdGuard Contents Blocker. The list never address individual cases so report blocker detection to AdGuard and not here. This list also mitigates malicious popups often seen on porn sites, pirate sites, and/or short links. Since most of filters are taken from uBlock filters, this list is provided under the same license of GPLv3.
japanese
If you are a non-native Japanese speaker seeking for a good Japanese list, my first recommendation is AdGuard Japanese filter. My lists include some aggressive rules not well-tested outside Japanese sites and likely to cause false positive on your local sites. There are also many duplicate rules of uBlock Origin's default lists. These lists are made to address a peculiar situation among Japanese ad-block user that many of them unsubscribe default lists and keep only a Japanese one. If you proceed, you shall be deemed to have read the Japanese README which gives more details, because those who need my lists should be able to read it.
The most comprehensive, block-first, and efficient Japanese list only for uBlock Origin that removes ads and analytics on PC. Some rules are taken from - or rather intentionally made to be identical with - EasyList, EasyPrivacy, AdGuard Base, AdGuard Tracking Protection, uBlock Built-in lists, Peter Lowe's list, Fanboy's Enhanced Trackers List, EasyList China, RU AdList, 280blocker domain list, and Brave Unbreak1. This way even if an user added any of those lists along with my list, those duplicates will be discarded and thus can do no harm. This list is also strongly influenced by Tofu filter though rules are not directly taken to avoid copy right infringement.
1: uBlock Built-in and 280blocker domain list are out of CC BY-SA license. I hope and believe rules taken from them are within a range of what filter authors can generally think of. Brave Unbreak is under MIT license.
Add this if you use Yuki's uBlock Japanese filters with uBlock Origin on Firefox for Mobile.
This can be added to Yuki's uBlock Japanese filters for enhanced blocking. Use at your own risk. Some rules are taken from or influenced by EasyPrivacy, Fanboy's Enhanced Trackers List, and gwarser's Block access to LAN list.
Removes some social elements such as share buttons mainly on Japanese sites. Some rules are taken from AdGuard Social media.
Removes annoyances mainly on Japanese sites. Some rules are taken from or influenced by AdGuard Annoyances, Fanboy Annoyances, uBlock filters – Annoyances, and Web Annoyances Ultralist.
Removes annoyances which only some user, not everyone, want to remove mainly on Japanese sites.
Inspired by Sable filters, this removes cookie consents. Main targets are Japanese sites and other high-traffic sites many Japanese people may visit. False-positive prone rules won't be added. Included in Yuki's uBlock Japanese filters - Annoyances
Removes blog parts and ranking buttons on Japanese websites. Included in Yuki's uBlock Japanese filters - Annoyances
Exclusion:
- Potentially useful parts or buttons
- Buttons for simple search sites without ranking function
- Buttons on adult sites except for some common ones (see above)
This is a variant of Yuki's Blog parts filters for adult sites. Included in Yuki's uBlock Japanese filters - Annoyances
Removes blogroll (feed-style mutual links) on Japanese sites. Included in Yuki's uBlock Japanese filters - Annoyances
Blocks mobile app banners. Included in Yuki's uBlock Japanese filters - Annoyances
Enhance anti-scam capability of 280blocker adblock filter by utilizing advanced capability of AdGuard/uBlock Origin.
medium_mode
All the filters/rules in this category are for uBlock Origin. dynamic-rules.txt or dynamic-rules-mob.txt can be imported to My rules whereas anti-allowlist.txt and/or static-rules.txt should be copied and pasted into My filters. You can subscribe the latter two instead by importing their raw text URL into Filter lists, but as they are not frequently updated I don't make them subscription filter.
This is to counter unnecessary or too generic allowlists which were not addressed or won't be addressed by the maintainer. Only for advanced user as it can cause problems.
Nooplists for medium mode of uBlock Origin dedicated for English user. The objective is to help those non-techie, yet security-conscious, people to use the mode. Payment services and mobile sites are out-of-scope1. In addition, following rules are included (Update: removed * localhost * block as it causes trouble on some particular case):
file-scheme * 1p-script blockfile-scheme * inline-script block
Mobile version of Yuki's uBlock Dynamic Rules
Q: Why X is nooped, it's bad!
A: See the purpose, this list is built to make as few breakage as possible for as many English user. This doesn't mean it should be used 'as is' - still each user should train their rules (obviously you have to add many rules if you browse non-English sites). Even with lax rules medium mode is much better than easy mode in terms of blocking.
1: I live in Japan and don't have full access to US, UK, etc. payment/shopping/banking services. Until you get accustomed to medium mode, it may be advisable to turn medium mode off on such sites. They anyway know much about you.
WordPress plugins have been security nightmare and are usually implemented in first-party resource that bypasses medium mode. Although it's impossible to block thousands of these plugins without breaking too many sites, blocking those unwanted plugins won't be a bad idea2. While popular social and annoyances filters block many of them, they come with tons of unnecessary rules3 and also occasionally cause false-positive. For these reasons I've settled down to AdGuard Social media filter and uBlock filters - Annoyances which are relatively small in size and rarely break pages; however, they only block minimal set of the plugins. This list includes 1) rules for the plugins not on Social media filter or other default filter lists, 2) rules almost equivalent to Noscript's Application Boundaries Enforcer (thanks to @gwarser), and 3) a regex rule focused only on the latest survey scam campaign. Want more protection? Assuming you've already using medium mode, you know default-deny approach well. @jawz101 provides a good wordpress plugins whitelist which should be used with an entire block rule for the plugin directory.
Exclusion:
- Rules that caused or can cause false-positive
- Rarely seen plugins such that used by less than 100 sites according to themesinfo.com or plugins used only on specific websites
- CSS-only plugins
2: It doesn't make sense if the site was fully compromised, but in some other cases may protect you from malwarized plugins and some vulnerabilities.
3: Unnecessary network rules if you use medium mode and tons of cosmetic rules; cosmetic rule has no security, privacy, or performance value.
no_gen_cosm
Ignore generic cosmetic filters is recommended if you want better performance, less false positive, and less chance to encounter anti-adblock without sacrificing security or privacy. However, you'll notice ugly layout of many websites once you enabled this option1. This filter mitigates this on English sites by removing placeholders left as a result of disabling generic cosmetic filters. Useful to those who replaced EasyList with its "without element hiding" version too. I also highly recommend you to add AdGuard Base in uBlock Origin's stock lists not only because it includes many specific cosmetic rules but also many potential problems by my rules are already addressed in the list. This would probably be the first public list utilizing specific generic filter.
Exclusion:
- Small place holder (e.g. *##.ad-space or *##.ad-area hides placeholders on various WordPress sites but won't be added for the reason.)
- Placeholders covered by AdGuard Base
1: Another side effect is any filter lists that heavily depend on generic cosmetic filters don't work well. An example of such lists is Fanboy Annoyances List.
See above, it's a mobile version of phhider-nogen.txt. Rules covered by AdGuard Mobile ads filter won't be added.
Update: Since generic cosmetic filtering is disabled by default on mobile, some specific-generic filters were added to uBlock filters so the value of this list dropped (I already removed entries no more needed - actually I'm the one who proposed and added the filters to uBlock filters). I may stop providing this list in future once I find time to move them to uBlock filters with further check.
dbl.oisd.nl | Internet's #1 domain blocklist
spirillen's uBlockOrigin Rules
I use PyFunceble to screen potential dead domains. I thank all ad- and contents-blocking community members who helped me to learn right filter writing.