1,108 karma · joined July 4, 2011
[ my public key: https://keybase.io/alexei; my proof: https://keybase.io/alexei/sigs/_Wx0Ql1tQXR8Me59VHsoIVEy38ZPTMg6I47YDBF3eY8 ]
Heads up, full blocking of "accounts.google.com" will break some login pages entirely. But it is a good domain to fully block as long as you're comfortable using the "Disable for this site" button when something goes wrong.
As for Firefox’s Total Cookie Protection, cookies are not the only tracking vector: https://privacybadger.org/#Is-Privacy-Badger-compatible-with...
Re fingerprint, similar question: why does this matter if you do a good job of blocking common trackers that perform fingerprinting?
(I develop Privacy Badger.) There are significant benefits to adding PB or uBO to a browser that doesn't already ship with a real built-in ad blocker. While PB and uBO work well together and you may want to use both for various reasons, I wouldn't say you need both. Either one is enough by itself for most people.
>HTTPS Everywhere
HTTPS Everywhere has been deprecated and eventually removed from extension stores a few years ago: https://www.eff.org/deeplinks/2021/09/https-actually-everywh...
>Phishing detection
Why isn't what's built into browsers enough?
>Cookie auto-delete
Why bother when blocking trackers and ads?
>Pop-up blocking
Is that the same as the various "annoyances" ad blocker lists?
>i wasn't sure "report broken site" was actually useful, like this would really get to a human, and matter?
It matters! We generate and respond to daily aggregate reports. We also periodically comb through bunches of raw reports to see what aggregation misses.
- https://privacybadger.org/#Is-Privacy-Badger-compatible-with...
- https://privacybadger.org/#How-is-Privacy-Badger-different-f...
For more, see https://privacybadger.org/#How-is-Privacy-Badger-different-f...
For more, see https://privacybadger.org/#How-is-Privacy-Badger-different-f...
For more see https://privacybadger.org/#How-is-Privacy-Badger-different-f...
That wiki page is a bunch of nonsense. For example:
>Redundant with Total Cookie Protection (dFPI)
https://privacybadger.org/#Is-Privacy-Badger-compatible-with...
For more, see https://privacybadger.org/#How-is-Privacy-Badger-different-f...
Just FYI, you can always disable Privacy Badger on a particular site by using the "Disable for this site" button in PB's popup.
You can also help make PB better by using the "Report broken site" button in PB's popup.
For more, see https://privacybadger.org/#How-is-Privacy-Badger-different-f...
For more, see https://privacybadger.org/#How-is-Privacy-Badger-different-f...
Just FYI, you can always disable Privacy Badger on a particular site by using the "Disable for this site" button in PB's popup.
You can also help make PB better by using the "Report broken site" button in PB's popup.
Installing PB is easier (and more powerful) than configuring the browser for better protection. For example, Firefox doesn't block much by default.
https://privacybadger.org/#Is-Privacy-Badger-compatible-with...
I think the thing on uBO's side is here on https://github.com/gorhill/uBlock :
>Do NOT use uBO with any other content blocker. uBO performs as well as or better than most popular blockers. Other blockers can prevent uBO's privacy or anti-blocker-defusing features from working correctly.
My perspective:
- uBO is good enough by itself
- PB is good enough by itself
- uBO comes with unique features
- PB comes with unique features
- While using uBO with PB may indeed cause some problems like anti-blocker-defusing features to break, it doesn't seem like a big deal for most people
- uBO alone is good, PB alone is good, uBO + PB is also good
I am Privacy Badger's author.
https://privacybadger.org/#Is-Privacy-Badger-compatible-with...
https://privacybadger.org/#How-is-Privacy-Badger-different-f...
>Redundant with Total Cookie Protection (dFPI)
https://privacybadger.org/#Is-Privacy-Badger-compatible-with...
https://orionfeedback.org/d/9535-extension-privacy-badger-br...
>Safari makes it extremely difficult to use a custom search engine that's not in Safari's defaults.
(Yes, I know about this site's title guidelines.)
One of the things that didn't make it is the entire request control dashboard. No more granular reporting or controls, at all. No more "medium mode" or "hard mode" (blocking unknown domains by default and making exceptions as you go). Sure, if you didn't use it before, you won't miss it.
(A) Chrome Web Store is full of malicious extensions. Google doesn't appear interested in consistently enforcing their own policies.
(B) Requiring DNR does nothing about all the other avenues for stealing user data. The fundamental problem is that a totally safe set of extension APIs is a totally limited set of extension APIs. No real innovation or differentiation is possible.