- Feb 26, 2021
That depends. They are not the same. uBo is better at cosmetic filtering, most notably because it has an advanced mode where you can block server requests. AdGuard does not. I'd say, if you want browser-only protection use uBo in advanced mode. If you want system-wide protection use AdGuard for Windows. It offers a lot more features than the extension.
That depends. They are not the same. uBo is better at cosmetic filtering, most notably because it has an advanced mode where you can block server requests.
For creating cosmetic filters AdGuard's rule builder is a little more advanced than uBlockOrigin's element picker. AdGuard does not have the advanced mode of uBlockOrigin, but it has an extra stealth mode with 'self distructing cookies' option. Advanced mode has noting to do with cosmetic filtering, it ads an extra layer of managing (server) request as you posted.
A lot of tracking mechanisms moved from cookies to URL parameters, pixel tags, websocket and XMLHttpRequest/Fetch mechanisms. uBO's advanced medium mode allows Websocket, XMLHttpRequest and Fetches (it has like AdGuard advanced rules to deal with 1x1, 2x2 and 3x3 pixel tags, but I doubt many people know how to use them), so uBO's advanced medium mode "only" adds a layer of security at the cost of a lot of hassle and tweaking.
That said I have advanced mode third-party blocking of uBO enabled in my Edge "strict" profile (disabled in my "easy" profile), not because it actually adds something to Edge security, but because it feels good to have control over what is allowed to connect. In this matter I agree with you: it feels safer to use uBO's advanced mode
For the average user AG is as good as uBO (and AGv4 is Google Manifest 3 compatible).
You’ve probably had this happen: you’re going to a party, everything seems perfect, and just before you leave you notice a stain on your clothes. What would you do? Change your look, of course. Well, we’ve noticed a little “stain” on the v4.0.133 release too: some users were unable to remove a domain from Allowlist after the update. And we’ve decided to release a new version right away with this bug fixed.
- [Fixed] Pause button not fully aligned to center #1994
- [Fixed] User rules and allowlist box shrinks little to left #1995
- [Fixed] Rules with :where() pseudo class do not work #1998
- [Fixed] Cannot remove a domain from Allowlist after update to v4.0 #2002
- [Fixed] 'Learn more' button design on update popup
I agree with what @silversurfer said.
Maybe this is a stupid question but why is HTTPS scanning to be avoided?