If PrivacyBadger isn't required with uBlock Origin and conflicts with it, will Firefox widget replacements be unnecessarily conflicting feature?
I disagree with both claims. uBlock Origin will generally not stop fetching embeds or have a widget replacement, it won't send DNT/GPC signals and the allowlist exists to make uBlock Origin allow non-tracking content which PrivacyBadger would allow. That isn't even mentioning the self-learning ability (although disabled by default and enabled in my policies)
Additionally if you look into the claims that other content filters get into uBO's way, it all goes to an old tweet by the developer which clearly says to not mix uBO with other content filters utilizing easylist.
PrivacyBadger doesn't use easylist, it uses badgersett and doesn't concern itself with ads, which easylist would contain.
And I didn't even yet say that cybersecurity often works in layers and PrivacyBadger might catch something uBO is unaware of, especially if having a habit similar to mine to often allow/noop content in uBO while keeping PrivacyBadger on. I personally include an uBO allowlist that most likely would let tracking through on some websites and I do it confidently since I know chances are PrivacyBadger would block those anyway
Speaking of which NoScript vs uBlock Origin update: I am currently using uBlock Origin in Medium mode again, since AI DDoS of the internet has increasingly been making everything go behind Anubis and Mastodon requires enabling JavaScript, so uBO Medium mode is currently a compromise I tolerate. It also enables me to be lazy.
However my Chromium tests are likely switching to NoScript entirely thanks to ManifestV2 deprecation in a few months and I know my policies won't bypass that forever. My policies do enforce uBOL simultaneously though, which might be causing minor conflicts, but I need to somehow migrate family to it so their sync settings catch on my policy and at least have it loaded.
