439951824a
The scriptlet addEventListenerLogger has been removed.
The logging of addEventListener() calls can now be done with the
addEventListenerDefuser scriptlet, which now supports the
following named arguments:
"type": the event type to match. Default to '', i.e. match-all.
"pattern": the pattern to match against the handler argument
Default to '', i.e. match-all.
"log": an integer value telling when to log:
- 1: log only when both type and pattern matches, i.e. when a
call to addEventListener() is defused
- 2: log when either the type or pattern matches
- 3: log all calls to addEventListener()
"debug": an integer value telling when to break into the
debugger, useful to inspect the debugger's call stack.
- 1: break into the debugger when both type and pattern match,
so effectively when defusing is taking place.
- 2: break into the debugger when either type or pattern matches.
The usage of named arguments is optional, positional arguments
are still supported as documented. Named arguments is required
to use "log" and/or "debug" arguments.
Obviously, do not use "log" or "debug" in any filter list, these
are investigative tools for filter list authors.
Examples of usage using named arguments:
wikipedia.org##+js(aeld, { "type": "/mouse/", "pattern": "/.^/", "log": 2 })
Above filter will log calls to addEventListener() which have the
pattern "mouse" in the event type (so "mouseover", "mouseout",
etc.) without defusing any of them (because pattern can't match
anything).
wikipedia.org##+js(aeld, { "type": "/.^/", "log": 2 })
Above filter will log all calls without defusing any of them
(because type can't match anything)
wikipedia.org##+js(aeld, { "log": 1 })
Above filter will log and defuse all calls to addEventListener().
|
||
|---|---|---|
| .github | ||
| assets | ||
| dist | ||
| docs | ||
| platform | ||
| src | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| .jshintrc | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| Makefile | ||
| MANIFESTO.md | ||
| README.md | ||
| REMOVED.md | ||
uBlock Origin (uBO)
BEWARE! uBO is (and has always been) COMPLETELY UNRELATED to the website ublock.org.
uBO is NOT an "ad blocker"; it is a wide-spectrum content blocker for Chromium and Firefox with CPU and memory efficiency as primary features. After a new installation, the default behavior of uBO is to block ads, trackers, and malware sites through EasyList, EasyPrivacy, Peter Lowe's Blocklist, Online Malicious URL Blocklist, and uBO's filter lists.
Documentation
| Basic mode | Advanced-user mode |
|---|---|
| Popup user interface | A point-and-click firewall that is configurable on a per-site basis |
 . . |
 Configure as you wish. The image shows 3rd-party scripts and frames blocked by default everywhere. |
Visit the wiki for documentation.
For support, questions, or help, visit /r/uBlockOrigin.
General Information
uBO is NOT an "ad blocker"; it is a wide-spectrum content blocker. uBO blocks ads through the EasyList filter syntax and extends the syntax to work with custom rules and filters. Furthermore, the advanced mode allows uBO to work in default-deny mode, which will cause all 3rd-party network requests to be blocked by default unless allowed by the user.
It is important to note that using a blocker is NOT theft. Do not fall for this creepy idea. The ultimate logical consequence of blocking = theft is the criminalization of the inalienable right to privacy.
Ads, "unintrusive" or not, are just the visible portion of the privacy-invading means entering your browser when you visit most sites. uBO's primary goal is to help users neutralize these privacy-invading methods in a way that welcomes those users who do not wish to use more technical, involved means (such as uMatrix).
EasyList, EasyPrivacy, Peter Lowe's Blocklist, Online Malicious URL Blocklist, and uBO's filter lists are default enabled when you install uBO. Many other lists are available to block trackers, analytics, and more. Hosts files are also supported.
Once you install uBO, you may easily unselect any preselected filter lists if you think uBO blocks too much. For reference, Adblock Plus installs with only EasyList, ABP filters, and Acceptable Ads enabled by default.
Installation
Chromium
Microsoft Edge Add-ons (Published by: Nicole Rolls)
uBO should be compatible with any Chromium-based browser.
Firefox / Firefox for Android
All Browsers
Do NOT use any other content blocker concurrently with uBO to benefit from its higher efficiency. uBO will perform as well as or better than most of the other popular ad blockers. Other blockers can prevent uBO's privacy or anti-blocker-defusing features from working correctly.
Do NOT use uBO along with other similarly-purposed blockers.
Enterprise Deployment
Release History
About
Free. Open-source. For users by users. No donations sought.
Without the preset filter lists, this extension is nothing. If you ever want to contribute something, think about the people working hard to maintain the filter lists you are using, which were made available to use by all for free.
You can help contribute by translating uBO on Crowdin.