←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.001s | source
Show context
zulban ◴[13 Jul 25 02:07 UTC] No.44546901[source]▶
I don't "bypass" Chrome when they want to melt my brain with their business model, I use Firefox. I don't "bypass" Windows when they want to melt my brain with their business model, I use Linux. No idea why so many "hackers" doing "bypasses" can't instead take action that is simpler, long lasting, and easier. Do people need to jerked around 50 times for 20 years before realizing it will keep happening and their "bypasses" are just temporary bandaids?
replies(25): >>44546992 #>>44547048 #>>44547056 #>>44547069 #>>44547113 #>>44547116 #>>44547135 #>>44547149 #>>44547168 #>>44547299 #>>44547355 #>>44547435 #>>44547619 #>>44547764 #>>44547831 #>>44547854 #>>44547934 #>>44547979 #>>44547987 #>>44547998 #>>44548000 #>>44548065 #>>44548153 #>>44551102 #>>44552201 #
1. Retr0id ◴[13 Jul 25 04:13 UTC] No.44547435[source]▶
The article is clearly not intended as an ad-blocking tutorial, it is an article about security research and API weirdness.

Sure, it inspires ad blocking meta-discussion, but if you're complaining that the author has a strategically suboptimal approach to blocking ads then you have missed the point.