Live data from Hacker News

AdGuard publishes the first ad blocker built on Manifest V3

adguard.com

251–260 of 371 posts

Re: AdGuard publishes the first ad blocker built on Manifest V3

#251
post #90

Are we going to lose ublock origin on chrome when v2 will be disabled?

Haven't used adblocker extension for a while. I just have AdGuard Home on a VPS to be used with every device on the network and do DNS level blocking and all is clean including stopping trackers from non browser apps.

I’m very curious about method to block YouTube ads with dns. I didn’t find a way when I tried.

Re: AdGuard publishes the first ad blocker built on Manifest V3

#252
post #64

Earlier quoted context omitted.

Switch to Brave, you will still maintain 99% of the bell and whistles of Chrome (because it's a Chrome fork) and you will have an Adblock engine directly in the browser core written in Rust. How cool is that... Especially on mobile Brave is a game changer. https://github.com/brave/adblock-rust

I despise anything that has touched cryptocurrency, which is why I don't like Brave.

I have no idea what they have been up to lately but when originally rolled out Brave's business model seemed very much like a protection racket. I haven't touched it since and never will.

Re: AdGuard publishes the first ad blocker built on Manifest V3

#253
post #226

Earlier quoted context omitted.

Isn't it very clearly not killing adblocking given that... this adblocker just released a version using it.

Yet reduced in it's ability to perform it's intended function.

Yet not reduced enough that the maker of the extension thinks users will notice any difference in the ability to block ads.

Re: AdGuard publishes the first ad blocker built on Manifest V3

#254

Earlier quoted context omitted.

Funny how the only browsers that matter are the ones shipped by default by OS vendors... almost like the whole Windows/IE antitrust action was for show. Or I guess the OS vendors realized being an oligopoly is a good workaround for dated antitrust policy.

> antitrust action was for show. People often forget the US underwent an administrative change between the judgement and enforcement. Microsoft spent a lot of "think tank" money on influencing the new regimes enforcement mentality, not only on their own issue, but on monopolies in general. It was, from my recollection, definitely not for show.

One reason people forget is that the Department of Justice announced the settlement (wrist slap) with Microsoft literally a few days before the 9/11 attacks, and so the case was wiped from the news along with everything else except 9/11. (I'm not suggesting a conspiracy, just that the public never had a chance to be angry about the settlement.)

Re: AdGuard publishes the first ad blocker built on Manifest V3

#255
post #176

Firefox seems pretty much on par with chrome these days and FF seems to win out on detection rates anyway so not sure why I'd want this combo? https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b... Does anyone has stats of adguard vs ublock by chance?

uBlock origin is far better, especially compared to this Manifest v3 version of AdGuard. AdGuard are just doing this to capture the upcoming hole in the market as uBlock Origin stops working in Chrome. Everyone should switch to Firefox.

This is pure anecdote and not apples and oranges, but I've found the ad-blocking experience with Safari/Adguard comparable to Firefox/uBO.

Re: AdGuard publishes the first ad blocker built on Manifest V3

#256
post #50

Earlier quoted context omitted.

From my experience, almost every website doesn't feel as nice in Firefox as it does in Chrome. Ofcourse some of those sites are maintained by Google (YouTube).

And some things don't even work. For instance, my dentist had a sign "rate us here on google" with a QR code. That code didn't work on my phone. I eventually figured out that it works fine in Chrome , but doesn't work in Firefox. In fact, there's no way to rate businesses on Google.com from Firefox on my phone. The links just aren't there, and going directly gives a 404. Everything works fine on Chrome. That's obviou…

Chrome/chromium based, is worse than IE in this regard - because of Google specifically, we've moved from "viewed best in" to "only works in".

Re: AdGuard publishes the first ad blocker built on Manifest V3

#257
post #71

One of the stated goal of MV3 by Google[1] was to avoid extensions with broad permissions: > our new declarativeNetRequest API is designed to be a privacy-preserving method for extensions to block network requests without needing access to sensitive data This MV3-based AdGuard extension still requires a broad permission to "read or modify host data" on all sites[2]: "host_permissions": [ " " ], So what you have now i…

I hope filtering proxies like Proxomitron become popular again. They'll work on all browsers, and as long as locked-down corporate environments with their own needs for filtering content and the requirement to go through a proxy exist, it's not something they can easily kill off (despite trying their hardest to do so with all the "security" propaganda.) Stop being at the whims of the Google-controlled browser monopol…

Proxomitron was amazing, very advanced, and even worked with ssl. All preceding proxy apps were very weak

Re: AdGuard publishes the first ad blocker built on Manifest V3

#258

Earlier quoted context omitted.

It feels like this was always going to be how this played out. Google being the world's largest ad company has a vested interest in ensuring ads are still displayed to users and once a sizeable enough amount of the Chrome userbase started adblocking it directly threatened their revenue growth. The only option here it seems is to switch browsers.

But these changes don't ensure that ads are displayed to users. This won't impact Google's ad revenue at all. At most it will negatively impact their revenue because the less powerful API will let the sketchier advertisers try to bypass the filters.

Google is the sketchier advertiser you're speaking of.

Re: AdGuard publishes the first ad blocker built on Manifest V3

#260
post #229

Earlier quoted context omitted.

Yes, it's not actively developed anymore because of the large overlap in functionality with uBlock Origin as well as the maintainance burden. However it's not equivalent, because in uMatrix you have even more fine-grained control which content a certain domain in a certain context can load (i.e. scripts, images, css and xhr requests).

Its functionality is equivalent, its ease of use isn't (at least in my opinion) with uBlock origins UI you can block by content type and then whitelist the domains which are still allowed and that feels less granular then the uMatrix configuration dialog. But if you check the generated dynamic rules in the settings you'll see that it supports the same granular controls as uMatrix

GP is correct afaik: the request categories for dynamic rules in ublock are image, 3p, inline-script, 1p-script, 3p-script, 3p-frame. The 3p vs 1p vs inline is kinda weird in itself since it's contextual and not relating to the content-type of the request, and we are missing css and xhr. Thing is, i realized i most of my dynamic rules are by domain anyway. Maybe if i find a real use case i'll try to look into the code and make this a bit more versatile.
Post reply on HN