Live data from Hacker News

“UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

github.com

131–140 of 271 posts

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#131

I 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…

> I do lots of extension development Off topic, but since you seem experienced at this, do you recommend any resources for extension development for someone that's beginning from scratch with no experience in this area?

I was frustrated with the lack of resources, so I'm publishing a book on it: "Building Browser Extensions". Available later this year. https://www.buildingbrowserextensions.com/

And check out the companion extension: https://www.buildingbrowserextensions.com/b2x

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#132
post #12

If you're still using Chrome now is the time to switch to Firefox. This is an interesting experiment but the only solution is to stop using Chrome.

You can also use Brave, which implements its own native adblocker and isn't impacted by Manifest v3.

Any disadvantages to switching from Chrome or Firefox?

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#133
post #101

Earlier quoted context omitted.

Reduce Motion in display or accessibility settings I think it’s called. I’m on M1. Just updated FF from the menu. I’m using the trackpad, but again, I changed my system settings, as I don’t like the default speed and acceleration.

Huh, yeah, turning on "Reduce motion" does indeed disable bounce scroll in Firefox. Definitely a strange choice on their part! (It doesn't affect it in other apps.) > I changed my system settings, as I don’t like the default speed and acceleration I see, that could make sense, if Safari was honoring those changes and Firefox wasn't, in some way. I've got mostly stock settings (slightly bumped up speed and three-finge…

It's not a choice.. It's just people trying re-implement "native" behavior. Doesn't work. Just use native components.

Firefox never felt native. Typography is different from my system settings, window color is different, mouse behavior different, scrolling behavior is different, spacebar to scroll jumps, zoom is weird.. actual size is 125%. So I always have to zoom out a few times to get to 100%, and it doesn't remember those settings.

The only reason I use firefox sometimes is because I can use different profiles as tabs in the same window. For those pesky apps without multi-account / account-member-user schema.

I used to love firefox 15+ years ago.. when I was still on windows, and IE was really bad, but switched to chrome the moment it came out.

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#134
post #102
post #89

Earlier 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.

Check out https://www.bromite.org/ , it's a android chromium fork with adblocking built in like brave but without the crypto stuff. Also has support for userscripts!

Chromium and therefore still encumbered by this poor Manifest v3 behaviour.

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#135
post #56

Earlier quoted context omitted.

Can you explain why you'd switch to an iPhone over a web browser? iPhone is a huge step back for having an open browser with user focused extensions. https://support.mozilla.org/en-US/kb/add-ons-firefox-ios

I know it's Safari under the hood, but Brave on iOS is great. I do hope that Apple decides to / is forced to allow real 3rd party browsers at some point, though. I also hope that a decent Linux phone becomes a realistic alternative. I'll check back in 10 years to see if either of those materializes.

I'm told ungoogled android distros exist, and are decently usable.

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#136
post #113
post #69

Earlier quoted context omitted.

What does it even mean to use an ad blocking tool "at least once a month"? Like... do people have an ad blocker installed, but disabled most of the time, and just enable it temporarily when they come across a site with particularly egregious ads? That seems... an unlikely use model?

It means they only use an adblocker on desktop.

How does that mean that?

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#137
post #49

Earlier quoted context omitted.

I was fully in the Google world prior to gorhill's posts on manifest v3 as a direct result the only thing I have left is a pixel phone, which will be going with the new iPhone (and in the meantime my entire family has been 'helpfully' migrated too) I may be up the extreme end of the distribution, but this sort of grassroots push is what dethroned IE, and the resultant loss of control of the web eliminated Microsoft's…

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 don't think their reasoning for switching to iOS was because of Chrome specifically, it was because of Google as a whole.

There are browsers for iOS with really good ad and tracker blocking. I use Orion, whose blockers are based on uBlock.

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#138

Just 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…

> the "read/modify data" permission isn't getting removed by MV3?

The stated reason for the removal of the blocking webRequest API was to avoid broad permissions to read/modify data on all websites in the name of privacy/security.

What would be the point of still requiring those broad permissions while losing features and the ability to innovate on extension-side matching algorithms beyond what the declarativeNetRequest API allows?

The point is to show that if you respect the stated reasons for the declarativeNetRequest API deprecating the blocking webRequest API, that is what you get.

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#139

Just 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…

> the "read/modify data" permission isn't getting removed by MV3? The stated reason for the removal of the blocking webRequest API was to avoid broad permissions to read/modify data on all websites in the name of privacy/security. What would be the point of still requiring those broad permissions while losing features and the ability to innovate on extension-side matching algorithms beyond what the declarativeNetRequ…

You seem to be confirming nightpool's comment. That this is an intentionally-limited release.

I think that's fine. It's good to have an adblocker that uses minimal permissions. But it seems like people will use this to argue that MV3 is less capable than it really is. Maybe UBO Plus (MV3) will come later that enables those feature.

Re: “UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3

#140
post #89

Earlier 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.

Also wondering. I've been using Firefox on Android for at least a couple years now. Works fine for me
Post reply on HN