-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Experimental filters
The experimental filters are filters being evaluated for inclusion in uBlock Origin's default set of filters. They are being evaluated to assess whether they cause undue web page breakages.
The Experimental filters are disabled by default, enable only if you want to help evaluate/fine tune these filters.
If you find web pages broken by one of these filters, please open a GitHub issue with all the proper details[1] id and only if you are able to confirm that one of the experimental filter is causing the web page breakage.
There are currently two experimental filters, which are block-then-redirect filters, to block the following resources:
-
googletagservices.com/tag/js/gpt.js
: Normally not blocked by EasyPrivacy. -
www.google-analytics.com/ga.js
: Normally blocked by uBO, but blocking this resource has sometimes led to page breakage, so exception filters have been required. By forcing a redirect to a neutered version, the goal is to reduce page breakage while avoiding the need to create an exception filter for some sites (example)
Note that these two experimental filters use the important
filter option, so they will bypass any existing exception filters.
[1] As per CONTRIBUTING.
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