Live data from Hacker News

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

github.com

41–50 of 271 posts

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

#41
post #31

Tangent but let's stop referring to it as a mere ad blocker, it's a content blocker - it's even a very useful and impactful accessibility tool in that capacity. ADHD sucks and I have a lot to thank to these types of tools for acting as my "crutches" that allowed me get where I am today.

No.

[deleted]

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

#42
post #29

Earlier quoted context omitted.

Adblockers might be an existential threat to Google, but MV3 won't change anything for Google. Google AdSense ads will almost certainly still get blocked, they're not hard to block/ obfuscated. I really doubt this will change anything for Google with regards to ads. At most you can argue that this is "step 1" in a larger plan to eventually bypass these adblockers or something, which I'll totally buy, but V3 has gotte…

Google will be able to use a variety of ad delivery methods that are not yet blockable with the filtering API they will now also fully control in Chrome.

Google AdSsense has always been able to bypass adblockers, as other advertisers have worked to do. At least in the "they could if they tried", they obviously have the technical prowess. But they haven't because that would be a scandal and invite scrutiny that they likely want to avoid - they own a massive part of the market without resorting to such things, it's not yet in their interest to do that.

So yes, as I said, maybe this is step 1 in a longer term plan to completely remove adblockers. Maybe one day so many people will rely on adblockers that Google is forced to take a drastic measure.

I personally don't expect that to be the case any time soon, but that's really not based on much.

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

#43

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

Huh? I'm going to switch to Firefox the second uBlock Origin stops working on Chrome. Otherwise I'll continue to use Chrome because it's a better browser (for me). I don't think I'm some rare minority here.

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

#44
post #12

Earlier quoted context omitted.

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

Do you mean that particular adblocker is not impacted or is Brave going to maintain support for the APIs dropped by Manifest v3?

Both.

"We will continue to support Manifest v2 to the extent that we can"

"Brave's adblocker (Brave Shields) is not an extension, and is natively implemented. So, it will be totally unaffected."

Source: https://www.reddit.com/r/brave_browser/comments/rdab12/how_w...

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

#45
post #12

Earlier quoted context omitted.

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

Do you mean that particular adblocker is not impacted or is Brave going to maintain support for the APIs dropped by Manifest v3?

Brave has committed to retaining support for all of the APIs that were removed by Manifest v3 https://github.com/brave/brave-browser/issues/20059#issuecom... (There are other mentions in the wiki and other places)

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

#46
post #12

Earlier quoted context omitted.

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

Do you mean that particular adblocker is not impacted or is Brave going to maintain support for the APIs dropped by Manifest v3?

Brendan Eich has committed to supporting the Manifest V2 version of uBlock Origin in Brave [1].

Brave's built-in native adblocker also definitely won't be affected, as it doesn't use any webextension APIs at all.

[1]: https://github.com/uBlockOrigin/uAssets/discussions/14544#di...

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

#47
post #40

Earlier quoted context omitted.

Yeah, so I'm against V3 mostly because I think that the pros of developers having power outweigh the cons of potential malicious extensions. I personally would have preferred rethinking a few other areas first: 1. Auditability - both in terms of the code and the behaviors 2. Improved permissions - could we have split WebRequest up? 3. Improved performance - could we have leveraged new APIs, like the declarative API,…

Great suggestions. The "third party buys popular extension and quietly adds malware" approach is also a huge attack vector. There really ought to be some way to prevent an extension from updating until you've had a chance to review and approve that change, especially if it requests a lot of sensitive permissions.

Well, even today, if the attacker modifies the permissions it will require a re-acknowledgement. Google can also do things there, like if the extension is tied to a key (as it should be), tell developers that they are required to not provide that key to anyone else, even if they sell / transfer ownership of the extension. Instead, the new owner should register a new key, which can trigger review/ scrutiny.

Key + 2FA means the attacker has to have code execution on a developer's machine in order to publish an update (via the local session token, which you should make short lived). And Google could require a FIDO2 token if you want to bypass the "alert users that this thing uses lots of permissions".

There's a lot of stuff I'd be working on to avoid having to remove developer power.

edit: K I've been rate limited by HN so I can no longer reply for today, but them's my thoughts.

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

#48

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 would still recommend the docs from MDN and Google.

If you're relatively familiar with web development in general - you can just peruse the APIs that are available for extensions

Chromium based: https://developer.chrome.com/docs/extensions/reference/

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

Then hit the MDN "My first extension page" to get a mostly functional manifest file: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...

Get familiar with `about:debugging` in firefox, and `chrome://extensions` in chrome - you'll need them to load your test extensions.

Finally - It's very worth it to read and understand the "core concepts" as outlined here, starting with the content_scripts: https://developer.chrome.com/docs/extensions/mv3/content_scr...

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

#49

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 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 near total influence over the computing industry

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

#50
post #9
post #3

How many people use adblockers? Is there any chance manifest v3 will lead to enough users abandoning Googles Chrome to build a community around an open alternative, like we did when we abandoned IE for Firefox all those years ago?

> How many people use adblockers? About 43 %, according to [1]. > Is there any chance manifest v3 will lead to enough users abandoning Googles Chrome […] No. Google Chrome is pretty much in the same position as Internet Explorer used to be. It's the default browser in the most popular mobile OS and the first thing people install on their PC (or get it installed by someone else). Mozilla can barely play catch-up with…

    42.7% of internet users worldwide (16-64 years old) use ad blocking tools at least once a month.
That framing sets of multiple mental alarm bells.

EDIT: it looks like the source is HootSuite may have a conflict of interest, as they seem to focus on social media advertising campaigns.

Post reply on HN