All 66 cases

Documented case · 2022

nrk (blog author)

Suspended about Jun 5, 2022; reinstated about 2 weeks later

RestoredAbout 2 weeksCode access lost / 404Reputation / visibility

Verified primary source

The account holder's own post, discussion or thread was opened and read in full for this entry.

He logged in to a suspension: no warning, and no explanation of which Terms term he was supposed to have violated. The erasure was thorough in a way most entries here do not match: every Issue, Comment, and PR he had ever opened was silently wiped, including other people's comments on those threads and the discussions on his closed PRs, along with his repos. Two weeks later the account was reinstated and GitHub connected it to his email address, a throwaway-domain address he had used briefly a year before. The post's title is his verdict: "The miserable state of GitHub moderation."

The record

Suspended or flagged
About June 5, 2022
Posted
His blog, June 7, 2022, updated June 20, 2022
Ticket / discussion
Ticket #1656025, unanswered at 48 hours
Suspected trigger
GitHub said on reinstatement that it was related to his email address. He had used a cock.li email address temporarily about a year earlier, then moved to Disroot; his inference is automated flagging of suspicious-looking email domains
Human reply from GitHub
Yes, at reinstatement, with the email explanation. The ticket itself went unanswered for the first 48 hours and the wait ran about two weeks
How it ended
Reinstated about two weeks after the suspension. One of his projects (nsxiv) moved to Codeberg as a result
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, nrk.neocities.org, June 7, 2022, updated June 20, 2022; opened and checked 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.