Documented case · 2024
Ryan Schachte
Feb 2024
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
All of his organisations were hidden from public view at once, under a banner: "Several of your organizations have been flagged. Because of that, these organizations are hidden from the public." No explanation came, and after more than a week, no response. He posted on Hacker News. GitHub then emailed him immediately to say the algorithm had mistakenly banned him, while being unable to say why or which orgs were flagged. His thread also notes that GitHub co-founder defunkt had been similarly banned in error, which is the next entry.
The record
- Suspended or flagged
- February 2024
- Posted
- Hacker News, February 2024
- Ticket / discussion
- Filed; still unanswered after two weeks, per his post
- Suspected trigger
- GitHub-stated afterwards: the algorithm mistakenly banned him. GitHub could not say why, or which organisations it had flagged
- Human reply from GitHub
- Yes, but not through the ticket: after his HN post, GitHub emailed him immediately and the case was resolved through a GitHub contact, while the support ticket sat unanswered
- How it ended
- Restored after the HN post, via a contact
- Duration
- Under 1 month
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 by Ryan Schachte, Hacker News item 39422068; read via search text on November 17, 2026.
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.