News for hackers. Stuff that matters.

A comment on Bypassing Google's big anti-adblock update. Parent comment

Re:Bypassing Google's big anti-adblock update by amluto on Sunday July 13, 2025 @03:35AM (#44548288)
No, MV3 really isn’t more secure. MV3 still allows extensions to inspect your requests — it just doesn’t allow extensions to block them.

It’s almost comical how weak the security/privacy argument for MV3 is. Chrome could have developed a sandboxed web request inspection framework to prevent data exfiltration, but they didn’t even try. Instead they nerfed ad blockers without adding any security.

[ Parent | on HN ]
Re:Bypassing Google's big anti-adblock update by mckravchyk on Sunday July 13, 2025 @12:01PM (#44551348)
I remember that another comical argument was performance. Supposedly, having extensions run in the background all the time is bad. So it's better to constantly, completely re-initialize them whenever an event wakes them up.
[ Parent | on HN ]
Re:Bypassing Google's big anti-adblock update by krackers on Sunday July 13, 2025 @03:07PM (#44552661)
From https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

>Keep in mind that uBO's own JavaScript-based network filtering engine has been measured to be faster than a well-known Rust-based filtering engine (though the measured difference back then was low single-digit µs, not something that will ever be perceivable by a end user).

[ Parent | on HN ]
Re:Bypassing Google's big anti-adblock update by cma on Sunday July 13, 2025 @03:12PM (#44552700)
Plus Google first entered the browser game with a toolbar for Internet Explorer that's main featured was it blocked popup ads.
[ Parent | on HN ]