Google today reached the final milestone in a browser-extension transition that has been years in the making, all remaining Manifest V2 extensions were removed from the Chrome Web Store.
Firefox on Android has gotten quite shit as well. It just refuses to load sometimes and won’t open pages until you copy and paste the url in a new tab. Extremly annoying, especially for online payments.
Well, that’s why I left them open - on the off chance I suddenly find myself with the amount of time I used to have in my younger days. But, of course, now that my phone’s crashed… *sign*
Well, you don’t need to be a genius to imagine a concrete site without shit. Chrome users apparently love advertisements, trackers, pop-up windows and other similar things. Well, who are we to disagree?
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!”
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.
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.
This is extremely funny that you’re trying to insult me, based on your feelings and not facts.
My only participation in this thread was that UBO Lite creator disagrees with you, which he publicly stated, but you felt… Offended? (No idea) - and decided to insult me rather than to deal with facts.
This is extremely funny that you’re trying to insult me, based on your feelings and not facts.
My only participation in this thread was that UBO Lite creator disagrees with you, which he publicly stated, but you felt… Offended? (No idea) - and decided to insult me rather than to deal with facts.
There is a word for people like you.
Troll.
Citing gorhill’s disclaimer that uBOL isn’t a 1:1 clone of uBO doesn’t prove Chrome is “ad-infested”—it conflates advanced power-user filtering with everyday ad blocking. Many limitation were Firefox-exclusive APIs that Chrome MV2 never supported in the first place.
Under the hood, standard filter lists compile directly into native C++ evaluation via declarativeNetRequest, while cosmetic element hiding and anti-adblock defusers run through the scripting and userScripts APIs. Furthermore, synchronous webRequestBlocking is still built into the Chromium engine for policy installs. Pointing out the architectural reality of how these APIs actually execute isn’t trolling; it’s addressing technical mechanics rather than hyperbole.
I‘m a semi-technical user, I don‘t want a technical discussion, I want facts I‘m able to understand. If you‘d be knowledgeable, you should be able to explain it. You didn‘t, tho. You used a lot of words, but said nothing. Why should your arrogant, but empty yapping do anything for me?
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.
Anyone that uses Chrome doesn’t know what a clean non ad infested website looks like so they won’t notice the difference.
Every time I do IT work, I ask to install Firefox
I run a portable version from an external drive to avoid installing anything.
There are many choices and people still stay on shit browsers because of laziness.
I actually do a pretty good job of selling it. I tell them that I can set up Firefox so using the Internet is easier. I’m 3/5 so far
Firefox on Android has gotten quite shit as well. It just refuses to load sometimes and won’t open pages until you copy and paste the url in a new tab. Extremly annoying, especially for online payments.
That sounds like maybe you have something else set as default browser and instead of Firefox and that something is messaging it up.
I use Firefox exclusively and it works everywhere.
Unless, URLCheck (highly recommended) is somehow fixing this issue. But I don’t remember having it before either.
I use it extensively, every day, with no problems
I have some problems with sites not loading, but I have 300 tabs open…
Amateur. Try over 1,200 with the option to put those not used in a while into an “inactive” group turned off.
Hmm… Maybe that’s my last phone crashed & burned recently…
But I have the tabs open because I’m going to read them. Do you?
Well, that’s why I left them open - on the off chance I suddenly find myself with the amount of time I used to have in my younger days. But, of course, now that my phone’s crashed… *sign*
I use it everyday with no problems
it seems alot of people are using brave as an alternative.
The Brave company is a far right hate group and Brave users are supporters of far right hate.
Fuck Brendan Eich and his henchman and all they stand for.
Vivaldi is quite nice as well
That four seasons is a real banger, unless you’re talking about having a press conference.
Well, you don’t need to be a genius to imagine a concrete site without shit. Chrome users apparently love advertisements, trackers, pop-up windows and other similar things. Well, who are we to disagree?
I am Groot
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!”
Literally, the creator of UBO Lite disagrees with you.
Why are you like this?
Too much corporate propaganda
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.
This is extremely funny that you’re trying to insult me, based on your feelings and not facts.
My only participation in this thread was that UBO Lite creator disagrees with you, which he publicly stated, but you felt… Offended? (No idea) - and decided to insult me rather than to deal with facts.
There is a word for people like you.
Troll.
Citing gorhill’s disclaimer that uBOL isn’t a 1:1 clone of uBO doesn’t prove Chrome is “ad-infested”—it conflates advanced power-user filtering with everyday ad blocking. Many limitation were Firefox-exclusive APIs that Chrome MV2 never supported in the first place.
Under the hood, standard filter lists compile directly into native C++ evaluation via
declarativeNetRequest, while cosmetic element hiding and anti-adblock defusers run through thescriptinganduserScriptsAPIs. Furthermore, synchronouswebRequestBlockingis still built into the Chromium engine for policy installs. Pointing out the architectural reality of how these APIs actually execute isn’t trolling; it’s addressing technical mechanics rather than hyperbole.I‘m a semi-technical user, I don‘t want a technical discussion, I want facts I‘m able to understand. If you‘d be knowledgeable, you should be able to explain it. You didn‘t, tho. You used a lot of words, but said nothing. Why should your arrogant, but empty yapping do anything for me?
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.
This is absolutely correct.