4 ms·

> GitHub should have implemented a blocking mechanism to stop people inviting Zed to 'dick' projects They did: https://github.com/blog/862-block-the-bullies ht

by vulf 12y ago

> GitHub should have implemented a blocking mechanism to stop people inviting Zed to 'dick' projects They did: https://github.com/blog/862-block-the-bullies https://github.com/blog/862-block-the-bullies They never admitted to it being a response to the incident with Zed, but the timing was too convenient. That blog post was dated 05/31/2011. Zed's commits to the repo in question happened on 05/28/2011: https://github.com/moron5/dongml/commit/f4b8df910e4048202768c4b1a2b167f8d32a6ea9 https://github.com/moron5/dongml/commit/f4b8df910e4048202768...

aaronem 12y ago
I'm still trying to figure out exactly what the sequence of events was there. As best I've been able to work out, whatever juvenile oaf created the "dongml" repo added Shaw to it in order to harass him somehow, and Shaw responded by writing a script to constantly commit changes to the repo which essentially rendered it empty, which seems reasonable both as retaliation in that specific case, and for general reasons of good taste. Then, in response, Github added a feature so that the "dongml" infant could block Shaw. Would anyone with closer to firsthand knowledge of the incident care to let me know whether I'm on the warm side or the cold?
- hamburglar 12y ago
  You're close. Someone added Zed to the dongml repo just to be annoying, and Zed removed himself. But the inviter just added him again, and Zed complained that there isn't any sort of confirmation to indicate, "yes, I'd like to be part of this project," so people can add you against your will, which happened repeatedly to Zed with dongml. Eventually, Zed retaliated with his commit bot, and github apparently looked at that situation and decided that it would be best if they added a feature that let you block other users. However, the idea wasn't that dongml would block Zed's malicious commits, it was that Zed would be able to block the person that kept adding him to dongml. In other words, the github feature wasn't to prevent Zed's malicious checkins directly, but rather block the behavior that annoyed him into making them in the first place. Zed wrote up a long blog post telling the whole story but I think it's been deleted since.
  - masklinn 12y ago
    > Zed wrote up a long blog post telling the whole story but I think it's been deleted since. The internet has a way of unshutting the whole thing up: https://web.archive.org/web/20130117043748/http://sheddingbikes.com/posts/1306816425.html https://web.archive.org/web/20130117043748/http://sheddingbi... and the followup https://web.archive.org/web/20120619005253/http://sheddingbikes.com/posts/1306948009.html https://web.archive.org/web/20120619005253/http://sheddingbi...
    - nailer 12y ago
      Ah. Judging from the followup, and Zed seemed to be satisfied, I think I was wrong about GutHub: they handled this very well.
nailer 12y ago
Ah. I think I read about it before they'd done that. Thanks for the update.

by vulf 12y ago

aaronem 12y ago

I'm still trying to figure out exactly what the sequence of events was there. As best I've been able to work out, whatever juvenile oaf created the "dongml" repo added Shaw to it in order to harass him somehow, and Shaw responded by writing a script to constantly commit changes to the repo which essentially rendered it empty, which seems reasonable both as retaliation in that specific case, and for general reasons of good taste. Then, in response, Github added a feature so that the "dongml" infant could block Shaw. Would anyone with closer to firsthand knowledge of the incident care to let me know whether I'm on the warm side or the cold?

hamburglar 12y ago
You're close. Someone added Zed to the dongml repo just to be annoying, and Zed removed himself. But the inviter just added him again, and Zed complained that there isn't any sort of confirmation to indicate, "yes, I'd like to be part of this project," so people can add you against your will, which happened repeatedly to Zed with dongml. Eventually, Zed retaliated with his commit bot, and github apparently looked at that situation and decided that it would be best if they added a feature that let you block other users. However, the idea wasn't that dongml would block Zed's malicious commits, it was that Zed would be able to block the person that kept adding him to dongml. In other words, the github feature wasn't to prevent Zed's malicious checkins directly, but rather block the behavior that annoyed him into making them in the first place. Zed wrote up a long blog post telling the whole story but I think it's been deleted since.
- masklinn 12y ago
  > Zed wrote up a long blog post telling the whole story but I think it's been deleted since. The internet has a way of unshutting the whole thing up: https://web.archive.org/web/20130117043748/http://sheddingbikes.com/posts/1306816425.html https://web.archive.org/web/20130117043748/http://sheddingbi... and the followup https://web.archive.org/web/20120619005253/http://sheddingbikes.com/posts/1306948009.html https://web.archive.org/web/20120619005253/http://sheddingbi...
  - nailer 12y ago
    Ah. Judging from the followup, and Zed seemed to be satisfied, I think I was wrong about GutHub: they handled this very well.

nailer 12y ago

Ah. I think I read about it before they'd done that. Thanks for the update.