[lxgr]

What exactly is your gripe with MV3?

Many people seem to treat it synonymously with "no more procedural request blocking", but that's not a thing Mozilla ever did:

> For Manifest V3 extensions, Chrome no longer supports the "webRequestBlocking" permission (except for policy-installed extensions). Instead, the "webRequest" and "webRequestAuthProvider" permissions enable you to supply credentials asynchronously. Firefox continues to support "webRequestBlocking" in Manifest V3 and provides "webRequestAuthProvider" to offer cross-browser compatibility.

The permission model also seems much more reasonable (less permissions have to be requested upfront at install time) than MV2, so I actually hope Firefox does deprecate it at some point.

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...

https://blog.mozilla.org/en/firefox/firefox-manifest-v3-adbl...

[michaelt]

> What exactly is your gripe with MV3?

Running an adblocker is the defining feature of the extensions API. ublock origin has 5x as many users as the second-most-popular extension [1]

Supporting ublock isn't just a nice-to-have add-on feature for an extension API, it's literally the only thing most users care about.

[1] https://addons.mozilla.org/en-GB/firefox/search/?promoted=re...

[MarsIronPI]

Firefox's MV3 implementation doesn't remove the original netRequest API though IIRC.

[crazygringo]

But MV3 supports uBlock Origin Lite.

Which, in my experience, blocks ads just as well, but also lets pages load significantly faster.

MV3 supports uBlock.

[brycewray]

Just as one example: Chrome + uBOL on Reddit will show you plenty of "Sponsored" stuff. You can use Inspector to find the offending CSS classes and then use `display: none` on them with something like Stylus[0], but not everybody wants to play that whack-a-mole game on the many sites that push uBOL past its blocking capabilities.

[0]: https://github.com/openstyles/stylus

[gorhill]

Reddit's sponsored posts are blocked by default in uBOL when using _optimal_ (default) or _complete_ mode.

[brycewray]

I will recheck my uBOL settings, then, sir. Thank you for your work!

EDIT: I did have it set to `Complete,` so perhaps I have something else going on.

[gorhill]

Best is to report the issue using the "Report an issue" in the popup panel while on Reddit site. There could be other issues causing this, for instance if you didn't grant uBOL the permission to inject scripts on the site. Depending on which browser/os the issue occurs, we should be able to narrow down potential causes.

[ben-schaaf]

UBO lite has a long list of all the types of filters that aren't possibly under MV3: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

Not sure about page load, but CPU time is about the same between the two: https://x.com/gorhill/status/1792648742752981086/photo/1

[lxgr]

This list only applies to Chrome, so it's completely irrelevant when talking about Firefox.

[Moldoteck]

It supports limited ublock functionality, not all of it, which will gradually be exploited by ad corps like google unless you think those are saints

[crazygringo]

The point is that it supports everything that currently matters in any substantial way.

Lots of people have been pointing out that ad companies will figure ways out around it. But they really haven't been.

MV3 and UBOL have been in wide usage for about a year and a half now. And nothing has been changing. Adblocking continues to be great.

The fact of the matter is, the ad block lists were getting so large and the JavaScript functionality was slow and it was significantly impacting page load times. UBOL uses vastly more efficient compiled code that is part of the browser and is just a far better ad blocking experience altogether.

But I guess that just doesn't fit the narrative that people want to believe, where MV3 was part of a big evil plan.

[Moldoteck]

the narrative that google, largest ad company proposed MV3 which limits current functionality of UBO so that UBO Lite can be implemented? Yeah, such a narrative... It's clear google is our buddy here who will never squeeze and exploit any option to push more intrusive and targeted ads and we should totally trust it

[lxgr]

It supports everything on Firefox on MV3, but not on Chrome.

[ragall]

Most definitely not as well.

[crazygringo]

It most definitely is as well. In fact it's better because you don't have the slower page loading times anymore.

And everyone I know who used UBO and switched to UBOL has had no complaints about ads not being blocked.

Whereas people who don't actually use it love to continue to insist that it's this degraded experience that doesn't work as well. And usually when one of them comes up with an example of some ad not being blocked, it turns out because they hadn't configured UBOL to use complete blocking mode.

[breve]

> It most definitely is as well.

No. uBlock Origin works best in Firefox: https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

uBlock Origin Lite can't do everything uBlock Origin does: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

If Lite is working for you then good. If you want fuller capability then you want uBlock Origin in Firefox.

[ragall]

> And everyone I know

Everyone who you know is irrelevant. I've tested and see that ads pass through, and tracking passes through with uBo light on Chrome. I can see it in the browser trace, and I can see it in DNS logs.

[crazygringo]

Your test is irrelevant. There is always going to be some tiny percentage of ads that passed through with any ad blocker. So the fact that you have seen ads passed through with it doesn't actually mean anything.

The only thing that means anything is how well it operates with your average browsing on a daily basis. And it's such a popular extension because it does an amazing job at blocking ads. That's just a fact. The only people who seem to claim otherwise appear to be the ones with an ideological axe to grind. It's silly.

[Hizonner]

Reading comprehension is the defining feature of a good commenter.

[jim33442]

Look I'm not an expert in web browsers, but I defer to those extension authors who definitely are. There's some reason uBO doesn't work well in MV3 even though they tried. Whatever technical explanation there is for why MV3 is fine, there's some caveat not mentioned.

[lxgr]

That’s because Chrome removed an important API in their MV3 implementation, not because the MV3 specification mandates said removal.