←back to thread

Bypassing Google's big anti-adblock update

(0x44.xyz)
1034 points deryilz | 4 comments | 12 Jul 25 19:06 UTC | HN request time: 0s | source
Show context
breve ◴[12 Jul 25 21:51 UTC] No.44545498[source]▶
The best bypass is to use Firefox. uBlock Origin works best in Firefox:

https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

replies(5): >>44546244 #>>44546588 #>>44548771 #>>44548855 #>>44549135 #
1. norskeld ◴[13 Jul 25 09:33 UTC] No.44548855[source]▶
Speaking of 'works best in Firefox'... I mainly use Chrome (kinda have to), and it's practically impossible to use it for reviewing big GitHub PRs with many files changed (UI just freezes), but everything's perfectly fine in Firefox!
replies(2): >>44548997 #>>44554196 #
2. zelphirkalt ◴[13 Jul 25 10:00 UTC] No.44548997[source]▶
Could this be a subjective experience? Is it reproducible on multiple machines? And have you tried it with a new profile?
replies(1): >>44549250 #
3. norskeld ◴[13 Jul 25 10:42 UTC] No.44549250[source]▶
Well, many people have complained about this very issue, and it was actually from this [1] discussion that I learned that Firefox handles big PRs just fine. No amount of jumping through hoops, including creating a new profile, helped to make it work in Chrome.

[1]: https://github.com/orgs/community/discussions/39341

4. abustamam ◴[13 Jul 25 22:06 UTC] No.44554196[source]▶
Our CTO was giving a hybrid presentation in a conference room on zoom, and his M3 Mac kept complaining of high memory usage. Chrome was rated at taking 60GB of memory.

No single consumer application should be taking over 60gb of memory.