Here comes the Google Chrome change that worried ad blocker creators

I would think Ad Guard desktop would be unaffected and make it so you can still use your preferred Crome based browser, perhaps Blackfog might work too just not sure if it requires a browser extension to do its ad blocking?
 
Mozilla would be moving to it but they can add required features on top of MV3 to implement current level of blocking from what they say or close enough to current level of blocking. If not they'd lose what little market share they currently have. No point in using Firefox if its as bad as Chrome in this matter.
 
Mozilla would be moving to it but they can add required features on top of MV3 to implement current level of blocking from what they say or close enough to current level of blocking.
But this appears open to change ...
We will support blocking webRequest until there’s a better solution which covers all use cases we consider important, since DNR as currently implemented by Chrome does not yet meet the needs of extension developers. You can follow our progress on implementing DNR in bug 1687755.
Manifest v3 update
 
When mozilla allows between session updates of static filter list, the biggest hurdle is solved for adblockers. This should not be to hard to implement as a seperated (update_filters) API.

I can imagine that Gorhill will re-releases uMatrix again, only without host based filterlists (like NoScript is now). uMatrix with its own rules only would function like a NetRequest firewall where you can block all (paranoid mode), third-party (hard mode) or third-party scripts and frames (medium mode) and selectively allow (user picked) net requests to whitelisted domains.

The community maintained whitelists (recipes) probably would be the only assets used by this revived uMatrix net request firewall. By updating uMA every month the recipes would be updated monthly also.
 
Last edited by a moderator:

Recently browsing

Members who viewed this thread in the last 5 minutes

Back
Top