-
Notifications
You must be signed in to change notification settings - Fork 82
Counterarguments
This page is just a place for me to collect my counterarguments when I spot something which I believe deserves countering.
I heard this argument from apologists of bloated software frequently. I decided to give this counterargument a dedicated page.
uBlock Origin (uBO) supports the parsing/enforcing of hosts files and ships with a couple. One of them, "Peter Lowe’s Ad server list", is enabled by default.
Using a hosts file at the OS level rather than the uBO level is the better solution for lists of malware domains since these malware-linked domains would be blocked system-wide, and all applications would benefit from it.
However, for lists of domains linked to ad servers, trackers, analytics, etc., this is not a good solution: You can not easily un-break web pages with a hosts file at OS level.
With the hosts file under the control of uBO, it is possible to un-break websites. A user can disable uBO for the website that breaks or create an exception filter to counter the blocking of a specific hostname appearing in a hosts file.
Many of the exception filters in "uBlock filters" are exception filters to counter entries in the hosts files shipped with uBO.
I want the project to be committed to fully supporting the hosts files that ship with uBO. Report any issues from using these, and the appropriate exception filters will get created.
I use all of these hosts files, and so far, not much breakage has occurred.
No. The code is wholly original and written from scratch. There are very few places I borrowed code from elsewhere, and these have identification. For example, for the element picker, I embedded CSS.escape from Mathias Bynens (because Chromium did not at the time support CSS.escape).
No, it is not. Adblock Edge is like ABP but without the "Acceptable ads" exception filters out of the box. See for yourself: here [via archive.org] is a diff of a code change for Adblock Edge, and here is the same exact diff for ABP. The timestamps show that Adblock Edge pulled code changes from the ABP project.
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