[flagged]
replyThis is a narrative that MS, Google etc want you to believe. They gutted it for ads. That's what's happening. There are workarounds now, that's what the existing ad block options are. They are heavily kneecapped.
reply[flagged]
replyNo, but you failed to comprehend the section of my comment where I mentioned "workarounds [...] are what the existing ad blockers now use"
replyMV3 is severely limited in what it can do. One example that blew my mind is that chrome happily renders webpages immediately after application launch, while extensions are still loading.
replyFirefox, in contrast, doesn't let the network request fire off to the page until every extension is ready. So chrome is essentially screwing over the user, letting ads/ blocked content load, and intentionally degrading their experience, to make things appear slightly faster.
That's nothing to do with MV3 though, that was also true with MV2. The situation actually seems improved in MV3, because static (and dynamic, IIRC) DNR rules are initialized and enforced immediately, right?
reply>MV3 is severely limited in what it can do.
replyYet, I never see ads since ad blockers still have enough power to block ads.
“If I can’t see it, it must not be there”
replyThat's the point of an adblocker. Web pages have ads, but with the extension they aren't there.
reply