alt Hacker News> This will ensure certain types of add-ons, like ad-blockers, continue to work best in Firefox.
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.)
Replies
"This will ensure certain types of add-ons, like ad-blockers, continue to work best in Firefox" clearly means that MV3 makes ad blocking worse, not entirely disabled. How can you get "no more ad blocking" out of that ?
Did Vivaldi? Or Brave? Will uBlock work properly with Mv3 and request blocking?
The people who know better should also know that tech social media was flooded with people not knowing what they were talking about mentioning manifest versions.
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.
https://en.wikipedia.org/wiki/Google_Chrome#Manifest_V3_2
> 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?
We shouldn't equate it with "no more ad blocking" because it didn't ship with an attempt to make ad blockers less effective or because that's not all it shipped with?