←back to thread

1034 points deryilz | 2 comments | | HN request time: 0.746s | source
Show context
throwaway73945 ◴[] 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 ◴[] 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 #
Barbing ◴[] No.44544966[source]
Indeed.

Perhaps a hobbyist would code “MV2-capable” MV3 adblocker for the fun of it, forking UBO or something, as a proof-of-concept. How much time would anyone spend on its development and who would install it when the max runway’s a few days, weeks, or months?

replies(1): >>44545545 #
1. DALEK_77 ◴[] No.44545545[source]
It seems someone's already done it. It requires some extra setup, but I managed to get it working on my machine.

https://github.com/r58Playz/uBlock-mv3

replies(1): >>44545591 #
2. tech234a ◴[] No.44545591[source]
Associated Show HN post from 5 hours ago: https://news.ycombinator.com/item?id=44543094