Restored
As of 2026-11-17

All 66 cases

Documented case · 2023

AUTOMATIC1111, Stable Diffusion WebUI maintainer

Jan 2023

RestoredNot statedDownstream dependenciesCode access lost / 404

Verified primary source

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

The maintainer of the Stable Diffusion WebUI, one of the most-used open-source projects of its moment, was suspended for "ToS violations." GitHub's reply, as reported in the HN thread, actually named a cause: links on the wiki led to sites hosting pictures that did not align with GitHub's values. He removed the links and was reinstated. Included partly for scale, a flagship project's maintainer is not immune, and partly as a control case: this is what it looks like when the process names the rule and the fix, and it took neither months nor a regulator.

The record

Suspended or flagged
January 2023
Posted
Hacker News, January 2023
Ticket / discussion
None published
Suspected trigger
GitHub-stated, as he reported it: some links on the project wiki led to sites with pictures that did not align with GitHub's values
Human reply from GitHub
Yes: GitHub replied with the reason, which is rarer than the restoration
How it ended
Reinstated after he removed the links
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 34257818, January 2023; GitHub's reason as reported in the thread, checked November 17, 2026.

GitHub's stated reason comes via the thread's reporting of his account of it.

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.