Replying to @⁨Eternal192@anarchist.nexus⁩

Not true. UBlock Origin Lite works just fine. They even recently added the ability to use content scripts so there is almost no difference between it and the original UBlock. Manifest 3 has had and still has some challenges, but you’re being so hyperbolic that I can’t take anything people like you say seriously. Might as well say… “I hate Chrome so much that I’ll make up random lies to prove how bad it is!”

Replying to @⁨ThirdConsul@lemmy.zip⁩

First, I don’t care if they agree with me or not. It is an open source project. They said from they never intended to try to make a 1:1 extension with UBO. They clearly lay out the positives of MV3 as well, and the scripts permission feature is a relatively new addition. You or anyone can contribute or fork it you want to add something.

I have spent enough time working on MV3 to know Chromium has solved a lot of the challenges. If you want to have a technical discussion about the APIs and differences or how you might do something with MV3, then let’s have the discussion. I never tried to claim MV3 is perfect.

I just have little patience for essentially non-technical cultists who go around spreading misinformation while acting like they know way more than they do. Prove it then… 99% of people like you never actually want to have a real technical discussion, because you spread your opinions based on feelings and not facts.

Replying to @⁨doben@lemmy.ml⁩

You can’t claim to be “semi-technical” while simultaneously refusing to look at technical facts and dismissing platform mechanics as “empty yapping.” How a browser engine executes extensions is inherently technical. Claiming you want facts while ignoring the architecture just means you’d rather stick with an emotional narrative than understand how the software actually works.

Chrome MV2 never supported some features people claim were lost: Features like in-flight response body rewriting and pre-socket IP filtering were Firefox-exclusive APIs (filterResponseData). Chrome MV2 never had them, so MV3 did not take them away.

webRequestBlocking is not dead in MV3. Google did not delete the synchronous blocking engine from Chromium. It requires installing via policy now. If an extension is provisioned via local policy, full programmatic webRequestBlocking runs in MV3 just as it did in MV2.

Everyday ad blocking works normally. For standard Web Store installs, uBlock Origin Lite compiles the standard filter lists (EasyList, EasyPrivacy, uBO filters) into native browser rules. Banners, trackers, and video ads are blocked.

The original claim was that “Chrome users don’t know what an ad-free web looks like.” That is provably false. If you want to understand the issue as a “semi-technical” user, you have to separate actual browser engine mechanics from internet hyperbole.

en