Hi =Snake=,
You sure will have an enhanced security problem with the new transfer via Manifest3 to the new chromium
declarativeNetRequest API.
There is no two ways about it and not only for blocking extensions the going will get narrow, or there won't be any.
Blocker extention-developers protest. 50.000 Euro fine for Google means only 4 days revenue less.
Peanuts really, and in such a way they rule our globe, a too big to fail Big Tech Giant.
With a max listing this new API gives no way to further big (phishing) blocklist (often over 70.0000 blocked),
so enhanced PHISHING threats galore. Malcreants may rejoice.
The new API only offers either the possibilities to block or redirect, nothing in between to hamper priviliged Google ad-tracking boffins. And, oh irony, all this presented to all of us in the name of enhanced privacy and security. (ROTFL).
That this comes to reside inside Google chrome, OK, you may choose for that. Had to be expected, but not to all variants of the chromium browser code? Yes, when Firefox uses the same developer API on its google chromium engines. Our loss.
Does it stay on the drawing board or will we all suffer the consequences of more Google shaping their own infrastructure?
When it gets more and more dfficult just to enjoy Google's benefits and circumvent Google's burdens.
It is a cat and mouse play like for Duval's /e/ platform for propriety Android phones.
polonus (volunteer 3rd party cold reconnaissance website security analyst and website error-hunter)