←back to thread

1034 points deryilz | 2 comments | | HN request time: 0.751s | source
1. moffkalast ◴[] No.44549477[source]
> I don't know how to make an adblocker, so I decided to report the issue to Google in August 2023.

> It was patched in Chrome 118 by checking whether extensions using opt_webViewInstanceId actually had WebView permissions.

> For the report, I netted a massive reward of $0.

Snitches get stitches, not rewards.

FWIW, on Windows Google relies on the registry to determine weather to use V2 or V3, and it can be reenabled: https://gist.github.com/MuTLY/71849b71e6391c51cd93bdea36137d...

replies(1): >>44550361 #
2. deryilz ◴[] No.44550361[source]
No adblocking extension would ever rely on a clear bug to function. Google reviews extension code and would immediately patch the bug, and maybe use it as an excuse to kick the extension off the web store. I don't buy the idea that there was a viable second option here.