←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.232s | source
Show context
throwaway73945 ◴[12 Jul 25 20:13 UTC] No.44544769[source]▶
So OP got Google to patch a harmless "issue" that could've been used by addon devs to bypass MV3 restrictions. Hope it was worth the $0.
replies(4): >>44544798 #>>44544859 #>>44545002 #>>44545600 #
StrLght ◴[12 Jul 25 20:24 UTC] No.44544859[source]▶
I don't agree with this conclusion. Google is fully responsible for MV3 and its' restrictions. There's no reason to shift blame away from them.

Let's do a thought experiment: if OP hasn't reported it, what do you think would happen then? Even if different ad blockers would find it later and use it, Google would have still removed this. Maybe they'd even remove extensions that have (ab)used it from Chrome Web Store.

replies(3): >>44544966 #>>44546018 #>>44548383 #
Hizonner ◴[12 Jul 25 23:13 UTC] No.44546018[source]▶
> Maybe they'd even remove extensions that have (ab)used it from Chrome Web Store.

So now it's abuse to make the user's browser do what the user wants, for the user's benefit, to protect the user from, you know, actual abuse.

replies(1): >>44546111 #
1. StrLght ◴[12 Jul 25 23:28 UTC] No.44546111[source]▶
Well, I don't think so — hence the parenthesis. Although, I am pretty sure that's how Google looks at it, given all MV3 changes.