Documented case · 2024
defunkt (Chris Wanstrath), GitHub co-founder
Feb 2024
Secondary source
The details here rest on another site's summary of the case, not on the account holder's own post.
GitHub's own co-founder and former CEO, with more than 800 repositories, was banned on GitHub in February 2024. The report, carried in HN threads including Ryan Schachte's above, is that GitHub admitted the ban was an error and gave no explanation for it. No primary post by Wanstrath himself was verified in research, so the entry is graded secondary. It is here because it bounds the problem from above: if the machinery can flag the company's co-founder and explain nothing, the absence of an explanation for everyone else is not a status problem.
The record
- Suspended or flagged
- February 2024
- Posted
- Hacker News, February 2024
- Ticket / discussion
- None published
- Suspected trigger
- Reported as an admitted error, with no explanation given
- Human reply from GitHub
- Not stated
- How it ended
- Reported restored
- Duration
- Not stated
Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.
Sources
Hacker News item 39267200, February 2024; secondary reporting, no primary post by Wanstrath verified.
Secondary: reported in HN threads; no primary post by the account holder was verified.
This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.