Hacker News new | ask | show | jobs
by calumapplepie 1945 days ago
Thank you for the productive response! I am definitely not the author of the article. I have no idea who they are, the similarities between our usernames is entirely coincidental.

I wasn't aware that you hadn't transferred the rights to the Web Store. I suppose the article wasn't clear enough on the timeline for the uBlock Origin swap: it was included because it was another case of maintainership change gone wrong, and it was closely related to the Nano Defender situation that was virtually identical to The Great Suspender.

I was aware that acceptable ads were added much later than the change in ownership: however, I thought the removal of per-site switches would be less relevant to the modern situation. On review, it does seem to imply that the impetus for the fork is that change: my apologies.

I trust that you didn't revert any changes, but Git doesn't necessarily preserve that information properly. Some git commands ('git reset --hard') remove any changes from history, as well as not creating a log of such changes. Much of what I could find around the change seemed to imply that you had reverted them, as opposed to simply never getting them: the difference is mostly academic, in my opinion.

Thanks for putting that clarification here: it wouldn't have fit well in the article, but it is worth mentioning. Manifest V3's new restriction on remote code is the main relevant security addition, and I am not a fan of how they bundle that in with the other changes. That restriction would make it a lot harder for these sorts of changes to fly under the radar. Nano Defender's malicious changes were quickly discovered: The Great Suspender flew under the radar for months..

1 comments

> On review, it does seem to imply that the impetus for the fork is that change: my apologies.

No worry. I forked the repo at the same time I transferred ownership. The reason was simply that I wanted to get back at being able to mostly work on the code base, as the issue tracker had become a burden taking most of the time I allocated to the project, and I found that @chrisaljoudi was good at handling opened issues.