5 ms·

As far as I can tell, HTTPSB is not available for Firefox, please fix! I would love to use something better than ABP (in terms of performance, it does content

by sspiff 12y ago

As far as I can tell, HTTPSB is not available for Firefox, please fix! I would love to use something better than ABP (in terms of performance, it does content filtering just fine), but I'm not so desperate to abandon the (warning: subjective content ahead) greatest browser of all times to lower the memory footprint of an ad blocker.

idlewan 12y ago
I'm betting this is not an easy task. It however would be really awesome for HTTPSB (which I just installed on chromium and fallen in love instantly with) to be ported to firefox. Seeing all the privacy-related features treated, by domain/site/everywhere rules, being able to block separately js/plugins/cookies (and by the way, the matrix is a great idea, a lot more useable than anything else out there)... in one extension only. Great work already, gorhill!
- Justsignedup 12y ago
  Eh it has some default behavior quirks. Like being unable to log into arstechnica.com because it won't let that cookie get stored.
  - gorhill 12y ago
    Whitelist the "cookie" cell in the matrix, save with one click on the padlock. Now cookies will be allowed everywhere by default (except for those ubiquitously blacklisted hostnames).
Gmo 12y ago
I totally agree with that. (I did upvote the comment but I want the creator of the extension to know that more people are interested)
gorhill 12y ago
Issue #86: https://github.com/gorhill/httpswitchboard/issues/86 https://github.com/gorhill/httpswitchboard/issues/86 Would be nice if someone forked and start to adapt to Firefox. I would of course work in concert as this would allow to identify parts of the code which is browser specific and which parts can be turned into an independent library.
alyandon 12y ago
Take a look at the RequestPolicy add-on for FF. It allows fine grained control over resource requests pages are allowed to make.
- the8472 12y ago
  The beta version also supports blacklists, which brings it a bit closer to HTTPSB. https://www.requestpolicy.com/1.0.html https://www.requestpolicy.com/1.0.html
  - keeperofdakeys 12y ago
    Unfortunately the developer is MIA, so the few bugs in the beta aren't going to be fixed anything soon. The most important feature of the beta is wildcard support, so you don't need to add every cloudfront sub-domain manually.
    - alyandon 12y ago
      I did not like the beta interface for RequestPolicy and I hacked in support for using regex matching for whitelist entries so CDN domains like CloudFront work correctly. https://github.com/alyandon/requestpolicy/commits/release-0.5.28-alyandon https://github.com/alyandon/requestpolicy/commits/release-0.... Caveats are: 1) I have absolutely no intentions of continuing any work on my hack. The changes I made meet my needs. Feel free to fork if you need additional features. 2) I don't pretend to be an elite javascript developer. I have no idea if my hacks are considered idiomatic javascript or not. I also make no promises that running my hacked version of this extension won't upload all your private data to a server in Russia or cause other problems like having your hard drive explode in a ball of fire.
AJ007 12y ago
Block known ad IPs and domains at the router or local level. This is what we did before adblock plus.
- mkesper 12y ago
  And if you don't have access to that level?

by sspiff 12y ago

idlewan 12y ago

I'm betting this is not an easy task. It however would be really awesome for HTTPSB (which I just installed on chromium and fallen in love instantly with) to be ported to firefox. Seeing all the privacy-related features treated, by domain/site/everywhere rules, being able to block separately js/plugins/cookies (and by the way, the matrix is a great idea, a lot more useable than anything else out there)... in one extension only. Great work already, gorhill!

Justsignedup 12y ago
Eh it has some default behavior quirks. Like being unable to log into arstechnica.com because it won't let that cookie get stored.
- gorhill 12y ago
  Whitelist the "cookie" cell in the matrix, save with one click on the padlock. Now cookies will be allowed everywhere by default (except for those ubiquitously blacklisted hostnames).

Gmo 12y ago

I totally agree with that. (I did upvote the comment but I want the creator of the extension to know that more people are interested)

gorhill 12y ago

Issue #86: https://github.com/gorhill/httpswitchboard/issues/86 https://github.com/gorhill/httpswitchboard/issues/86 Would be nice if someone forked and start to adapt to Firefox. I would of course work in concert as this would allow to identify parts of the code which is browser specific and which parts can be turned into an independent library.

alyandon 12y ago

Take a look at the RequestPolicy add-on for FF. It allows fine grained control over resource requests pages are allowed to make.

the8472 12y ago
The beta version also supports blacklists, which brings it a bit closer to HTTPSB. https://www.requestpolicy.com/1.0.html https://www.requestpolicy.com/1.0.html
- keeperofdakeys 12y ago
  Unfortunately the developer is MIA, so the few bugs in the beta aren't going to be fixed anything soon. The most important feature of the beta is wildcard support, so you don't need to add every cloudfront sub-domain manually.
  - alyandon 12y ago
    I did not like the beta interface for RequestPolicy and I hacked in support for using regex matching for whitelist entries so CDN domains like CloudFront work correctly. https://github.com/alyandon/requestpolicy/commits/release-0.5.28-alyandon https://github.com/alyandon/requestpolicy/commits/release-0.... Caveats are: 1) I have absolutely no intentions of continuing any work on my hack. The changes I made meet my needs. Feel free to fork if you need additional features. 2) I don't pretend to be an elite javascript developer. I have no idea if my hacks are considered idiomatic javascript or not. I also make no promises that running my hacked version of this extension won't upload all your private data to a server in Russia or cause other problems like having your hard drive explode in a ball of fire.

AJ007 12y ago

Block known ad IPs and domains at the router or local level. This is what we did before adblock plus.

mkesper 12y ago
And if you don't have access to that level?