From the little experience I have with HTTPSB, I'd say that it was more of a NoScript alternative. It feels to me like a webbrowser firewall. They seem to have moved into the adblocking field now though. Here's how I see it:
* 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.
Sounds a lot like we need some volunteers to build a better UI for simple (adblock mode), a 2nd option to do a noscript equivalent, and a 3rd option for wild-west-browser-firewall mode.
* 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.