Documented case · 2022
Anonymous, permanent ban (Tell HN)
Nov 2022
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
A deliberate contrast entry. He made controversial comments on an open-source discussion months earlier, regrets them, and says so in the post. GitHub permanently banned him, suspended his replacement accounts as sidestepping, and left his appeal unanswered for months, while he feared for his job. Nothing here claims the ban was a mistake. It is in the explorer because even a ban the account holder does not dispute produced the same process: no hearing, no timeline, no answer, and a livelihood attached to the account throughout.
The record
- Suspended or flagged
- 2022
- Posted
- Hacker News, November 2022
- Ticket / discussion
- Appeal ran months with no response; no number published
- Suspected trigger
- Conduct: comments on an open-source discussion (the VS Code Python extension's move toward closed source), which he says he regrets. Not a false-positive claim
- Human reply from GitHub
- No response to the appeal in months
- How it ended
- Permanently banned, unresolved. New accounts he created were hunted down and suspended as ban evasion, and he feared being fired because his employer uses GitHub
- Duration
- Over 3 months
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
First-hand post, Hacker News item 33576369, November 2022; opened and checked November 17, 2026.
Contrast entry: an admitted conduct case, not a false-positive claim.
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.