Earlier quoted context omitted.
What do you mean by non-native scroll behavior? I'm asking seriously, never noticed anything.
Also wondering. I've been using Firefox on Android for at least a couple years now. Works fine for me
Ditto for me.
“UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
171–180 of 271 posts
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#172I approve (of both the release and the name). I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox. It won't. Those who care about this are already on Firefox, and frankly - Firefox isn't going to be the answer here (to be clear, this is opinion). I'm also not thrilled at manifest v3, although for very different reasons than the adblocking limitatio…
The MV3 bugs are stupid ridiculous. Like, I'm gonna open a long-lived communications channel, but it'll be destroyed when the service worker shuts down in an arbitrary nhttps://bugs.chromium.org/p/chromium/issues/detail?id=115225...
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#173Earlier quoted context omitted.
While all this is true, one should look it also from a motivation standpoint. Why is Apple doing things it is doing and why is Google? That thought experiment will help extrapolate the far-out future for both companies and the version of the future they are building towards.
This isn't reasonable. Today on iPhone, even if you pay $100/year to be able to run unsigned code, you can't get a copy of Firefox running, because nobody maintains the port. That kind of crippling grasp on the ecosystem is difficult to tolerate, and simply nothing compared to what's going on with Google. Today with Pixel phones, you can secure boot third party OSes without even voiding your warranty. You can unlock…
Which part isn't resonable? I was proposing a thought experiment in understanding motivation and the version of the future these companies are building towards.
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#174Earlier quoted context omitted.
I find firefox on android unusable because it has this awful, non-native scroll behavior. On android I use either Brave or Samsung Browser.
What do you mean by non-native scroll behavior? I'm asking seriously, never noticed anything.
Firefox for Android used to implement scroll coasting in a way that felt very different from Chrome and native Android apps. I just gave it a try now and it seems like they've fixed it, scrolling feels native now.
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#175Just so I understand correctly: This version removes *all* of the features that read or modify a user's data, so as to abide by the ""stated intent"" of MV3, rather than taking full advantage of all of the actual MV3 APIs? For example, this commit removes the "scriplet injection" and cosmetic filtering features, which AFAIK work perfectly fine on MV3? if broad "read/modify data" permission is to be used, than there i…
I do think there's a bit of sour grapes. You can only use the MV2 version until January. After that the main point to using the MV3 extension will be that it exists. I sort of like the idea of UBO Minus, regardless of whether they do a full MV3 version of UBO later. It's more private than UBO could ever be. If it's enough, it's actually quite a nice extension. Methinks a competitor ad blocker leaning into MV3 and cla…
> usershare is at risk
My impression from way back in the uMatrix days was that marketshare is not a concern for gorhill and that the u* family are a labor of love to improve the internet for everyone.
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#176Earlier quoted context omitted.
While all this is true, one should look it also from a motivation standpoint. Why is Apple doing things it is doing and why is Google? That thought experiment will help extrapolate the far-out future for both companies and the version of the future they are building towards.
This isn't reasonable. Today on iPhone, even if you pay $100/year to be able to run unsigned code, you can't get a copy of Firefox running, because nobody maintains the port. That kind of crippling grasp on the ecosystem is difficult to tolerate, and simply nothing compared to what's going on with Google. Today with Pixel phones, you can secure boot third party OSes without even voiding your warranty. You can unlock…
Reading your comment, my final thought was that essentially if you want to maintain another computer, similar to your desktop, buy an Android phone. Research and install your ROM of choice, route it and install the programs you want, and you are responsible to make sure it all works.
If you don’t want yet another computer to maintain consuming hours of your time, buy an iPhone.
I do use Android for my streaming set top boxes, because of that flexibility. Devices like the Fire TV are flexible, like having an energy efficient and much more affordable version of a PC. But for my phone, for such an essential device that just has to work, it’s too much to ask out of me.
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#177I approve (of both the release and the name). I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox. It won't. Those who care about this are already on Firefox, and frankly - Firefox isn't going to be the answer here (to be clear, this is opinion). I'm also not thrilled at manifest v3, although for very different reasons than the adblocking limitatio…
The MV3 bugs are stupid ridiculous. Like, I'm gonna open a long-lived communications channel, but it'll be destroyed when the service worker shuts down in an arbitrary n https://bugs.chromium.org/p/chromium/issues/detail?id=115225...
The comments on that bug are depressing as well. I generally am involved in much more niche development communities - is this kind of disrespectful back and forth the standard these days?
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#178Earlier quoted context omitted.
The MV3 bugs are stupid ridiculous. Like, I'm gonna open a long-lived communications channel, but it'll be destroyed when the service worker shuts down in an arbitrary n https://bugs.chromium.org/p/chromium/issues/detail?id=115225...
The comments on that bug are depressing as well. I generally am involved in much more niche development communities - is this kind of disrespectful back and forth the standard these days?
People are kinda bitter about this. You can design around it, but it makes a lot of things way bigger jobs than they should be. I was just explaining my way around this one today. You port from v2 to v3 and all of a sudden it's basically a rewrite to make everything datum serializable and every function re-entrant because you never know when chrome is going kill your process.
At this point, it's just the way it is now with Google. They promised Crostini for kaby lake chromebooks (I think; maybe another chip) for like 3 years in a row. A thousand comments on there. People are just frustrated.
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#179Earlier quoted context omitted.
IMO Firefox on an Android is better than anything you can get on iOS. It fully supports uBlock Origin! I also use a Pixel phone, though I use LineageOS so I feel less tied to Google
I find firefox on android unusable because it has this awful, non-native scroll behavior. On android I use either Brave or Samsung Browser.
Have you used Firefox for Android recently? That scroll issue was fixed with the release of GeckoView, at least from what I've noticed.
Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
#180Earlier quoted context omitted.
> this commit removes the "scriplet injection" Considering this is stated in ManifestV3's announcement and that no APIs have been made for it: > Beginning in Manifest V3, we will disallow extensions from using remotely-hosted code. This will require that all code executed by the extension be present in the extension’s package uploaded to the webstore. Server communication (potentially changing extension behavior) wil…
> Considering this is stated in ManifestV3's announcement and that no APIs have been made for it I'll admit—when I first made this comment, I assumed (based on the initial manifest v3 draft) that this change only affected privileged context execution, and did not affect execution in the "main world", outside of privileged extension contexts. That said, APIs HAVE been made for it, and it would still be possible to do…
"Source" he asks as the perpetually incompetent and straight up evil Chrome team deletes powerful APIs with no good replacement that just so happen to be the exact ones that blocks Google's extensive data collection and tracking.
Feel free to be in denial about why those crippled APIs have come to be.