Safety without fog
Protect people.Label the power.
Every moderation action should answer three questions: who made the decision, where does it apply, and how can it be reviewed?
Layered authority
Immediate control. Scoped enforcement. Real appeal.
Decentralization is not an excuse to abandon abuse prevention, consent, or legal obligations. Central convenience is not an excuse to claim universal authority.
Safety layers
- 01
Personal controls
Yours
Block, mute, filter, limit replies and mentions, control messages, preview shared blocklists, and switch on anti-dogpile safety mode.
- 02
Community moderation
Ours
Published rules, scoped roles, time-bounded actions, restricted evidence, audit trails, conflict checks, and independent appeals.
- 03
Client and indexer policy
This door
Each operator publishes what it labels, hides, or declines to serve—and identifies that treatment as service-scoped.
- 04
Protocol validity
The wire
Malformed payloads, invalid signatures, replay, unauthorized mutation, and technical abuse are rejected narrowly and transparently.
Targeted harm
Context matters. Safety is not optional.
Reports can identify repeated use of rejected identity labels, outing threats, doxxing, nonconsensual intimate media, and coordinated harassment without requiring a legal name or medical proof.
Current views use a person’s current stated name. If immutable signed history is intentionally opened for a legitimate review, older identity data appears behind a clear historical-data warning.
Evidence with consent
A report should disclose exactly what you chose.
Private messages stay encrypted until a reporter intentionally selects specific evidence and confirms the preview.
- 1
Select
Choose the object, category, and only the context needed.
- 2
Preview
See the exact messages, attachments, people, and metadata.
- 3
Track
Receive a private receipt, scoped outcome, and appeal path.
Words with boundaries
Hide is not delete. Suppress is not erase.
Safety notices distinguish a personal hide, community removal, operator suppression, provider deletion request, signed tombstone, key destruction, and protocol rejection. Permanent or independently replicated copies may remain even after official clients stop serving them.
Foundation status