News for hackers. Stuff that matters.

A comment on Help EFF test Privacy Badger, our new browser extension for privacy. Parent comment

Re:Help EFF test Privacy Badger, our new browser extension f... by gorhill on Friday May 02, 2014 @12:57PM (#7686813)
Yes, it has been said that it's more for advanced users. I've been trying to mitigate this with presets, recipes, etc. but still I understand and accept that it's not for everybody.

I usually ask people to at least read this one page [1], not to convince them, but rather just so that it is understood that the extension is fully configurable: it can be at any point in the full block-all / allow-all spectrum.

[1] https://github.com/gorhill/httpswitchboard/wiki/How-to-use-H...

I just added a 3rd example of how the extension can be used without blocking anything, while still reporting everything. If anything, this can be useful to keep the other privacy extensions open for scrutiny.

[ Parent | on HN ]
Re:Help EFF test Privacy Badger, our new browser extension f... by unhush on Friday May 02, 2014 @01:57PM (#7687122)
We do have a preloaded list of third-party sites to not block because they would cause too much breakage. Note that because PBadger is in alpha, this list is very short right now: https://www.eff.org/files/cookieblocklist.txt

It's maintained by EFF, and more things will get added as time goes on.

[ Parent | on HN ]
Re:Help EFF test Privacy Badger, our new browser extension f... by sequoia on Friday May 02, 2014 @02:29PM (#7687294)
Add mail.google.com!! I took the time to go to google accounts, re-login, disable the blocking on the various sites (accounts.google, mail.google etc.) to get it working, but I can imagine breaking gmail will be a quick route to "uninstall extension" for many people. :)
[ Parent | on HN ]
Re:Help EFF test Privacy Badger, our new browser extension f... by unhush on Friday May 02, 2014 @03:23PM (#7687602)
UGH, you're right. Ok, let me explain this. We whitelisted google.com but it was not anticipated that, in the general case, we should really whitelist all subdomains in order not to break sites.

Luckily this was a one-line patch: https://github.com/EFForg/privacybadgerfirefox/pull/63 (though in the future, it is better for the whitelist to have wildcards in the cases where it's necessary).

Thanks for testing. Really helps a lot.

[ Parent | on HN ]
Re:Help EFF test Privacy Badger, our new browser extension f... by unhush on Monday May 05, 2014 @03:36PM (#7700651)
FYI, upgrading to 0.1.1 (released Friday) fixes the bug I mentioned. Subdomains of whitelisted sites are also whitelisted now. https://github.com/EFForg/privacybadgerfirefox/pull/63/files
[ Parent | on HN ]