-
Notifications
You must be signed in to change notification settings - Fork 82
Overview of uBlock's network filtering engine: details
garry-ut99 edited this page May 22, 2024
·
13 revisions
Overview of uBlock's network filtering engine
Advantages:
- Little overhead creating/deleting dynamic URL rules.
- Precedence over both dynamic filtering rules and static filters.
- Useful to diagnose/fix in a very narrow way websites broken by either dynamic filtering rules or static filtering.
- Useful to create override to current dynamic filtering rules or static filtering.
- A point and click UI for easy management of rules.
Disadvantages:
- Can only match URLs which "start with".
- Can't be loaded from a filter list.
Advantages:
- Little overhead creating/deleting dynamic rules.
- Precedence over static filters.
- A point and click UI for easy management of rules.
Disadvantages:
- Rules are broad: whole sites or class of types.
- Can't be loaded from a filter list.
Advantages:
- Flexible syntax: from very broad to very narrow targeting, with support of wildcards at any position.
- Support cosmetic filtering (removal of DOM elements).
- Can be loaded from a filter list: facilitate community-supported filter lists.
- Compatibility: can be used in other blockers supporting ABP-compatible filter syntax.
- Except for a few filter syntax extensions specific to uBlock not adopted by other blockers.
Disadvantages:
- High overhead creating/deleting network/cosmetic filters (high memory churn).
- In case of 3rd-party filter lists, forced to use all filters, including those which may not be wanted.
"Static" means it must be "compiled" ahead-of-time before being used, and "dynamic" means it can effortlessly change at runtime:
- Rules: you can set rules with a simple mouse clicks in the user interface, they are virtually zero overhead to create/remove.
- Filters: all filters must be all reloaded in memory when adding/removing.
uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
- Wiki home
- About the Wiki documentation
- Permissions
- Privacy policy
- Info:
- The toolbar icon
- The popup user interface
- The context menu
-
Dashboard
- Settings pane
- Filter lists pane
- My filters pane
- My rules pane
- Trusted sites pane
- Keyboard shortcuts
- The logger
- Element picker
- Element zapper
-
Blocking mode
- Very easy mode
- Easy mode (default)
- Medium mode (optimal for advanced users)
- Hard mode
- Nightmare mode
- Strict blocking
- Few words about re-design of uBO's user interface
- Reference answers to various topics seen in the wild
- Overview of uBlock's network filtering engine
- uBlock's blocking and protection effectiveness:
- uBlock's resource usage and efficiency:
- Memory footprint: what happens inside uBlock after installation
- uBlock vs. ABP: efficiency compared
- Counterpoint: Who cares about efficiency, I have 8 GB RAM and|or a quad core CPU
- Debunking "uBlock Origin is less efficient than Adguard" claims
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: uBlock consumes several or several dozen GB of RAM
- Various videos showing side by side comparison of the load speed of complex sites
- Own memory usage: benchmarks over time
- Contributed memory usage: benchmarks over time
- Can uBO crash a browser?
- Tools, tests
- Deploying uBlock Origin
- Proposal for integration/unit testing
- uBlock Origin Core (Node.js):
- Troubleshooting:
- Good external guides:
- Scientific papers