Documented case · 2025
flongo11
Suspended Dec 10, 2025 (per a single advocacy page)
Anecdotal / unverified
This rests on a single social or advocacy source, or a collection summary, with no primary source read. Weight it accordingly. This page is deliberately not indexed by search engines.
Included with the strongest flag in this explorer. A single advocacy page claims the account was suspended on December 10, 2025 for harassment and offensive language with no evidence presented, under ticket #135161, and that the profile and a repo holding court-case documentation were 404 by February 15, 2026. There is no corroboration anywhere else in the research. It is listed so the record is complete, and graded anecdotal so no reader mistakes it for a verified case.
The record
- Suspended or flagged
- December 10, 2025, per the page
- Posted
- Advocacy page, 2026
- Ticket / discussion
- Ticket #135161, per the page
- Suspected trigger
- The page claims a suspension for "harassment" and offensive language, with no evidence shown
- Human reply from GitHub
- Not stated
- How it ended
- Unresolved per the page: profile and the repo (court-case documentation) returned 404 by February 15, 2026
- 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
Single advocacy page on a generated-site host; no corroboration found.
Anecdotal and uncorroborated: one advocacy page is the only source. Do not rely on this entry without independent confirmation.
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.