[0] https://github.com/gorhill/httpswitchboard/wiki/How-to-use-H...
One of the major use cases of Adblock Plus is effectively "Fire and Forget" mode - enable it and then don't worry about it.
You are saying HTTPSB does not support this use case.
As such, I don't see why you can call it an alternative to Adblock Plus.
Adblock Plus / Edge has a "Fire and Forget" mode, as I described in my grandparent comment. HTTPSB does not. Hence, HTTPSB's functionality is not a superset of Adblock Plus/Edge's functionality.
Your analogy fails.
But in any case, regarding your point, you can set up HTTPSB as an ad blocker and forget about it:
https://github.com/gorhill/httpswitchboard/wiki/HTTP-Switchb...
Advantage over ABP is that it discloses to you what is still not blocked, and you act on this information if you wish so.
You can block specific things like iframes on domains.
Compared to other adblocking methods it's fast and does not use a lot of memory, but it's limited in what it can block (namely connections to specified hostnames).
Is it adding "whitelist *" somewhere or something similar?
I expected this to be a part of the extension settings / options, but ah well.
The "all" cell (top left corner of the matrix) is a "soft" allow all, i.e. it allows everything except those hostnames and types of request which are not specifically blacklisted.
* Adblock (Plus): Blocking ads, No / minimal user action required
* NoScript: Blocking scripts. Lots and lots of user action required.
* Ghostery: Block privacy intrusions. Basically an application-level firewall for the browser. In a normal firewall, you'd block e.g. port 80 from IP x.x.x.x. In an appliction firewall you simply block, for instance, bittorrent traffic. Minimal user interaction required, and where it is required, it's very easy to use.
* HTTPSB: A low-level web browser firewall ("block port 80 from IP x.x.x.x) that now also does (better) adblocking. The adblocking is on par with Adblock (plus): no user action required. The browser "firewall" is basically unusable. Lots of user interaction required, and when it is required, it's basically impossible to understand.
With Adblock + Ghostery I feel completely in control. If I want to enable the Disqus script on a single page for a single session, Ghostery easily lets me do that. HTTPSB makes that hard, or perhaps I'm missing something.
Case in point: When I tried to post this comment, I got a "Dead link: users don't match" error which went away when I disabled HTTPSB.