Comment by fracus
Comment by fracus 2 days ago
> But 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 usin
Well, thanks for nothing?
Comment by fracus 2 days ago
> But 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 usin
Well, thanks for nothing?
Hi, I appreciate your opinion, but really disagree. First of all, this is one bug, and most of the ones I find don't "act against user's interests" (not that this one could have been used effectively without being patched anyway). Doing bug finding is how I make a difference and a skill I feel proud of.
I USED to keep bugs (read: exploits) for myself without sharing them, but after a while I realized it was not worth it and my skills were basically going to waste. You can say philosophical stuff about ads if you want but bug finding for me is a fun challenge with a good community. I'm not pretending Google is my best friend.
Plus, doing this gets me a bit of money. It's either this or I work summers at a grocery store, and I prefer this.
Author here, sorry. I don't think any open-source extension (especially large adblockers with millions of users) could actually get away with using this bug, because Google is paying close attention to them. It would've been patched immediately either way.