Oof, so even people that should really know better are now equating MV3 with "no more ad blocking"? I think at this point the entire thing just needs to be renamed.
(Only Chrome removed the request blocking API from their MV3 implementation; Firefox did not.)
For precision, I should have said "significantly worse ad blocking", not exaggerated as "no more ad blocking".
> However, DeclarativeWebRequest is limited in the number of rules that may be set, and the types of expressions that may be used.[336] Additionally, the prohibition of remotely-hosted code will restrict the ability for filter lists to be updated independently of the extension itself. As the Chrome Web Store review process has an invariable length, filter lists may not be updated in a timely fashion.[337][338]
Is that not true?
It wouldn't be the first time tech gossip rags would take something Mozilla did out of proportion to make outrage videos about that become a hit on Reddit.
When Mozilla added some weird AI thing (I think it was page summaries?) I was asked by people whose algorithm picked up this nonsense whether it'd be better for their privacy to switch back to Chrome or Edge.
Sounds like the issue here is paid social media platforms, where everybody is looking for ways to differentiate their slop from the rest. It would be weird to expect a different outcome.