←back to thread

Bypassing Google's big anti-adblock update

(0x44.xyz)
1034 points deryilz | 1 comments | 12 Jul 25 19:06 UTC | HN request time: 0.224s | source
Show context
al_borland ◴[12 Jul 25 20:51 UTC] No.44545060[source]▶
Even if bigs exists to work around what Google is doing, that isn’t the right way forward. If people don’t agree with Google move, the only correct course of action is to ditch Chrome (and all Chromium browsers). Hit them where it hurts and take away their monopoly over the future direction of the web.
replies(26): >>44545103 #>>44545185 #>>44545382 #>>44545931 #>>44545951 #>>44546164 #>>44546522 #>>44546599 #>>44546664 #>>44546763 #>>44547531 #>>44548200 #>>44548246 #>>44548399 #>>44548418 #>>44548820 #>>44549698 #>>44550098 #>>44550599 #>>44551061 #>>44551130 #>>44551663 #>>44553615 #>>44554220 #>>44556476 #>>44571602 #
1. hnlmorg ◴[13 Jul 25 07:27 UTC] No.44548246[source]▶
I think you’re missing the point of the article.

Isn’t really about bypassing it to support the development of new extensions. It’s more just a blog about a new bug that the author found during their security research.

It’s really more a fluff piece promoting themselves than it is anything else. And to be honest, I’m fine with that.

My bigger takeaway from that article was how impressive this individual already is. They’re still a student and already finding and reporting several bugs in major platforms. Kudos to them.