Hacker News Reader

Comment by SuperShibe | Hacker News Reader

[flagged]

If a major adblocker used a bug or security vulnerability to work around restrictions, it would have been patched away immediately.

The uBlock team was never going to ship code that depended on a bug to work.

I fully agree. The original comment and the other replies to it are bewildering. There was nothing to gain here, yet people are throwing ad hominem attacks left and right.

The exact wording was:

> But I don't know how to make an adblocker, so I decided to report the issue to Google in August 2023.

So why not go to someone that does know how to make a blocker? Nice snitch.

Well, in his defense it would have been patched immediately after the first adblocker used it, and he would have gotten nothing at all out of it.

Oh wait he got nothing at all anyway ;)

Not really, this sort of fame farming is what makes candidates stand out in infosec interviews. A bug in Google systems is good for his future career.

The post says they had another bug with a large bounty in the same year, so it doesn't seem very useful for CV padding either

Would be quite different if they patched it and broke important extensions, possibly facing serieous outcry and bad publicity.

That's what they already did.

Important extensions like, dunno, uBlock Origin?

Yeah, surely if chrome broke important extensions people will get mad and switch.

I agree that would change things but I can't picture an open-source extension with millions of users pivoting to rely on something that's clearly a bug.

At that point it's a feature, not a bug.

Having millions of users on your side is great ammunition.

He was hoping to be a good boy and receive some cash from Google, as per article.

Reply on news.ycombinator.com