

Why not? It’s what the rest of the browser world is doing… :P
‘Google’s dumping MV3 support, guess we have to dump it also, too bad so sad guess there’s nothing at all to be done here’.
Jokes aside- I agree giving up (in any regard, including proxy-side filtering) is the wrong answer. But the more I’m thinking about this, the more I’m convinced that the current essentially Internet-wide reliance on Chromium (with a small carve-out for WebKit) is a real problem that needs urgent attention.
Mozilla’s the obvious choice but they seem determined to piss off their users with UI rewrites and blow all their cash on literally everything other than browser development.
Sad thing is there’s a real opening here. I was a mainly Mozilla user years ago. I switched to Chrome because it was fast- there was a youtube ad (which actually aired on TV for a while) showing Chrome rendering a webpage in 100ms. Those days are of course long gone. Partly because Chrome is now bloated with a ton of Google shit, partly because with fast javascript rendering, web developers started treating javascript as ‘free’ so now a news article comes with 10+mb of tracking code that literally runs an auction client side for advertisers to bid on the opportunity to bother you and many of the most basic websites are rendered client-side because why not.
Point is though- come up with a FAST, standards compliant rendering engine that can compete with Chrome, with no bloat, and push it as ‘we are what Chrome was- fast, effective, clean’.
Ah that’s awesome!!! I’d seen that output before but never saw the story of its input.