Strong ad blocking mode is an innovative blocking strategy developed by X Browser in its early days. Its advantage is simplicity and efficiency. This article introduces the basic principles of strong blocking and the rule syntax provided by X Browser for strong blocking mode.
Series Navigation
- Overview: Ad Blocking Introduction
- Previous: How to Write Exception Rules
- Current: Strong Blocking Mode and Rules
- Back to: URL Blocking Rules
- Back to: Writing Hidden Element Rules
Principles
In strong blocking mode, the browser automatically blocks all resources that do not belong to the current domain. Usually, some ad resources come from third-party ad servers. The basic strategy of strong blocking is to only allow resources and scripts under the current domain, and allow some regular third-party resources and scripts based on specific algorithms combined with given blocking rules.
This strategy is the opposite of regular ad blocking. In other words, regular ad blocking identifies and blocks ads through a series of rules, while strong blocking identifies and allows normal third-party resources and scripts through rules.
In strong blocking mode, regular blocking rules still take effect. However, in strong blocking mode, good blocking results can be achieved even without subscribing to many regular blocking rules. Since it does not rely on a large number of regular rules, blocking performance is also very good. The disadvantage is that it may accidentally block normal third-party resources. In this case, we need to use specific strong blocking rules to allow normal third-party resources and scripts. Below we introduce the rule syntax for strong blocking mode.
Syntax Rules
Strong blocking rules use “==” as the rule identifier prefix, followed by keywords. Multiple keywords can be separated by commas.
Global Rules
==jquery |
The following is an equivalent syntax:
==jquery,m3u8,mp4,cdnjs.com,github.com,cdn.jsdelivr.net |
Domain Scope Rules
==jquery@example.com |
The following is an equivalent syntax:
==jquery,mp4,m3u8@example.com |