Worst platforms
By number of logged cases
Git-anchored · Append-only · Public
They silenced you.
We write it down.
An immutable public ledger where banned and restricted artists document platform incidents — shadowbans, false copyright strikes, reach throttling — backed by a transparent Git repository.
Censorship patterns
Who hurts artists most?
Live breakdown from the ledger — platforms, incident types, and how they combine.
Worst incident types
Most common enforcement actions
Platform × incident
Where each type of harm clusters
Common issue signals
Quick-signal template picks
Reason categories
Stated grounds when provided
Cases over time
Monthly volume on the ledger
Quick signal · 10 common cases
Recognize your situation?
Tap the issue that matches yours. One click to add your name to the ledger — story and proof optional.
No cases yet
Be the first to document a censorship incident. Your entry becomes a permanent Git record.
01 — Immutable ledger
Every submission is a JSON file + proof artifact committed to a public GitHub repository. No database to tamper with. History is auditable.
02 — Artist-first
Built for Bancamp artists facing opaque platform enforcement. Document bans, strikes, and shadowbans with evidence attached.
03 — Simple prevails
No blockchain theater. No proprietary silos. Files on disk, versioned by Git — the same tools developers trust for decades.
04 — What verified means
A verified badge means a moderator reviewed this entry and found it credible enough to stand behind publicly — usually because there’s proof attached or enough specific detail to check. It’s not a legal ruling or a personal endorsement of the artist. Anyone can ask for a case to be reviewed; requests are logged on the ledger.