Power tools for Adblockers for Firefox is available in the add-on store

[LinuxFan58]

Open source: GitHub - Kees1958/Power-Tools-for-AdBlockers-for-Firefox: Adds 4 power tools to any adblocker for Firefox (Worry-free safe browsing, Cookie consent clicker, Dynamic DNR filtering and Privacy Inspector) Mv3 compliant


Pure Mv3 extension adds super powers to your adblocker

1. Worry-free safe browsing
   Adds lot's of security enhancements to your browser and tries to auto decline cookie prompts.
   Inspired by Ghostery's never consent coupled with extra security protections to increase security when doing random surfing.
   
   
2. Cookie consent clicker
   Automate cookie choices, just point and click on the accept or decline button and save the created rule
   Inspired by Consen-O-Matic only giving the user the option to decide
   
   
3. Dynamic DNR filtering
   Brings back the uBO dynamic filtering options (block 3P-code or 3P-all) per domain using Mv3 DNR rules.
   Allows you create additional block rules (or just check what your adblocker misses).
   
   
4. Privacy Inspector
   Inspired by the work of the JShelter project allows you to check what fingerprinting tactics a website uses.
   You can choose to block low risk, medium-risk or all (including high risk) fingerprinting signals at once.
   
   
   

 

[Bot AI]

Open source: GitHub - Kees1958/Power-Tools-for-AdBlockers-for-Firefox: Adds 4 power tools to any adblocker for Firefox (Worry-free safe browsing, Cookie consent clicker, Dynamic DNR filtering and Privacy Inspector) Mv3 compliant


Pure Mv3 extension adds super powers to your adblocker

Worry-free s […]

Hi, this looks like a potentially useful companion extension for people who want finer controls alongside an ad blocker, especially per-site third-party blocking and inspection tools. The tradeoff is that it adds another privileged component to Firefox, so the source code and requested permissions matter more than the feature list alone.

How I would approach it​

The four functions cover different jobs rather than simply improving ad blocking:

• Safe-browsing and consent automation: convenient, but automatic interaction with consent dialogs can occasionally choose incorrectly when a site uses unusual wording or layout.
• Cookie-consent clicker: user-created rules provide control, though they also require maintenance when sites change.
• Dynamic DNR filtering: useful for advanced per-site restrictions, but it is not necessarily identical to uBlock Origin’s dynamic filtering. Manifest V3 declarative rules and uBO’s filtering model have different capabilities and limits.
• Privacy Inspector: good for visibility and experimentation, but detecting a fingerprinting-related API call does not by itself prove that a site is building or transmitting a fingerprint.

Before installing, I would check the Firefox add-on listing for the requested permissions, the developer identity, update history and privacy policy, then compare the published package with the repository if reproducible-build information is provided. Open source makes inspection possible; it is not an automatic security certificate.

I would also avoid duplicating functions already enabled in an ad blocker or privacy extension. More overlapping controls can mean harder troubleshooting and occasional site breakage—not necessarily more protection. Starting with one feature at a time makes it much clearer which component caused a problem if a site stops working.

 

[Sampei.Nihira]

@LinuxFan58

Let's take an example.
I want to run a test for download protection only.
So I remove “com” from the TLD list and then check only the 2 following box:

Enable the extra ‘safe regions’ protections additionally (see Privacy & Security tab)
+
Block third-party scripts, frames, and downloads outside safe regions.

Is that correct?

Then I download CCleaner, and it shouldn't work.
Am I missing something?



P.S.

I also tried removing “net” from the TLD list because the download is “net,” but it didn't make a difference.