AdGuard MV3 extension

Correct, opening sites that failed with Adguard MV3 now don't using uBOL.

 

suggest the rule or filter list and the adguard team will improve their options!

 

In a previous post I was suggesting to use uBO Lite besides AG MV3 beta. I also said it needs more investigation. Of course there's nothing against experimenting. But I want to make clear that it's not recommended by the developer of uBO Lite. View (at the end of the page):

https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-asked-questions-(FAQ)#filtering-capabilities-which-cant-be-ported-to-mv3

 

I have verified on a website that I often use as a test that filtering, especially cosmetic, in AdGuard MV3 is still inefficient due to presumably service worker efficiency issues.
This extension currently lacks (for me) reliability of use when compared to uBlock Origin Lite.

More info:

https://github.com/uBlockOrigin/uBO...-a-bad-faith-attempt-at-converting-ubo-to-mv3

I am led to believe from my testing that network filtering also suffers from such problems.
Because I have often noticed that even when it should,the block counter does not appear in the extension.

Uninstalled.

 

Don't you miss the advantages (custom filter lists and user rules) you mentioned july 12 in a post on another forum?
View: https://msfn.org/board/topic/183974...um-extensions/?do=findComment&comment=1269074

 

So what?
You have your own needs.
I have my needs.
And so difficult to understand,for you?

 

Nice words. Thanks.

 

Out AdGuard AdBlocker (MV3 beta) v.5.0.33.
Interesting this option:

https://imgur.com/jSUpuXD

You will notice the log with "pathfactory" blocker cause MV3 list by kees1958 added to custom filters.

Still unreliable cosmetic filtering blocking (which at least for cookie consent pop-up blocker seems improved,but on some websites it is very slow) which, in my opinion, in some cases (Service Worker?) interferes if nothing else with the blocked requests counter.

Incorrect:

https://imgur.com/LYWf519

OK:

https://imgur.com/kbGX2YD


Unfortunately, I didn't have time to check the log in the ADR.it website with the counter blocked.

I then set the rule for Hard Mode + TLD.
Works.

________________________________________________

Although the changelog reports that cosmetic rules are being applied faster,just this slowness (unreliability) of them implies that the extension is not yet usable.

https://github.com/AdguardTeam/AdguardBrowserExtension/releases/tag/v5.0.33-beta

 

A major addition. Great.

 

It is interesting to consider that after adding the static rule for Hard Mode + TLD it is not possible to unlock from the Log something locked by the same rule.
Only the option to delete the rule itself is offered.
So you have to manually enter in the exceptions,what is blocked by the Hard Mode + TLD rule.

 

Out AdGuard MV3 v.5.0.43

Changelog:

https://github.com/AdguardTeam/AdguardBrowserExtension/releases/tag/v5.0.43-beta

Cosmetic filtering is greatly improved in this new version.
But it is still not perfect and in some cases inferior to uBlock Origin Lite.

Example:

AdGuard MV3:

https://imgur.com/ydctBfP

uBlock Origin Lite:

https://imgur.com/YGa4Obv

Unfortunately, I can't tell if the custom filter lists (I have 3 custom filter lists) are updated as would be customary with a new version.

P.S.

Also another fact that bothers me,is that I cannot hide SDP Log in this test:

https://browserleaks.com/webrtc

it is probably my fault that I am not sufficiently familiar with AdGuard.

And also block the proxy,as I can do in uBlock Origin in this other test:

https://browserleaks.com/proxy

Do any forum members have the solution?

 

Did you try the element picker in AG MV3?

 

This rule works in AG MV3:
||*^proxy.js
The site shows this warning:
JavaScript is partially blocked on this page (possibly a malicious adblock list). Test results may be broken.

 

It doesn't work for me I had already tried.

 

Yes in some cases it works,in some cases it is inefficient for example in MSFN.

 

Those who use the block page in NextDNS and try the d3ward test will notice that there is incompatibility.
The blocking page needs to be disabled.

I am greatly reducing the rules applied in an attempt to make the extension faster in loading websites.

My current rules with 3 custom filter lists are:

71353

My filter lists:

https://imgur.com/FTaCz2r

It would be interesting to exchange views on your filter lists.

 

Hi,
Must be something wrong on your side regarding NextDNS block page, i 've no problem on D3ward (i guess you've certificate installed?).
Am using Microsoft Edge on Debian, and still running UblockOrigin MV2 with 90133 filters.

 

Certainly the test is OK with uBlock Origin,but what is the topic of the thread?

 

@Sampei Nihira
You know I'm not a fan of d3ward, but just for you I visited that site (MS Edge, AG MV3, NextDNS with blocking site and activated HaGeZi-Multi Pro ++). I didn't see any problem. The score was 93% (for what it's worth).

 

Just answering to your NextDNS possible misconfig, i know this is Adguard MV3 thread, you talk about NextDNS!!!

 

You definitely have a lot more filtering rules than me (71353) and you only get 93% obviously you must have wondered compared to uBlock Origin Lite (who gets a better score) why.


NextDNS + Blocking Page:

https://imgur.com/3xgYfbk

NextDNS without blocking page:

https://imgur.com/Ztggi07

Note the AdGuard MV3 counter with the usual number of blocks (44) in both images.
So the conclusion is that there is an incompatibility.

 

@Sampei Nihira
Now I've repeated the test with and without the NextDNS blocking page. Both times the score was 99%. In my initial test (with enabled blocking page) the score was 93%. I don't know why in the repeated test according to the testsite seven items more were blocked (total 72 blocks on the AG icon) (I didn't study the log). I can't reproduce the big difference you did notice. My number of rules: 96.102 (AG Base filter not activated). The testsite contains a compatibility warning for enabled blocking page in NextDNS. So you should expect the "problem" you described. Besides that, also in earlier cases I found the results on that site not consistent. So there are several reasons why it's of little value. I advise you to test only on notorious real world tracking sites. For me end of the discussion now.

PS: I don't use AG MV3 permanently. Only for testing now and then.

 

Out v.5.0.65:

https://github.com/AdguardTeam/AdguardBrowserExtension/releases/tag/v5.0.65-beta

Finally, a significant improvement in cosmetic filtering.

 

Good to see. BTW, have you reported any ad-related issue from the extension's "Report an issue" function? Have they stared fixing reported issues for the MV3 extension?

 

Not with the fix in this latest version.
But I previously reported a specific website that I still use as a test.
The improvement,if we do not consider latency,is greater than with uBlock Origin.