Diffuse safety and moderation
Safety decisions affect distribution and display; they do not rewrite signed public evidence.
Default protection
Every client verifies signed safety manifests and screens content before display, storage, relay, and durable upload. Exact media hashes, perceptual image hashes, text similarity hashes, domains, spam controls, trust tiers, and storage budgets are supported.
User and community control
Users can hide or report posts, mute authors, narrow relay policy, and add independently signed community safety publishers. These choices do not fragment the unified global feed; they control what a device accepts or shows.
Review and revocation
Anonymous reports never automatically remove a post. Reviewed safety releases are versioned and signed. A withdrawn rule disappears in the next replace release. Authors can publish signed revocations; separately pinned trust roots can issue safety or legal revocations.
Appeals and urgent reports
Send formal appeals and legal requests to legal@offlineprotocol.com; send urgent operational safety reports or publisher corrections to diffuse@offlineprotocol.com. Include the post ID or rule kind/value, the reason, and only non-sensitive supporting context. Do not email illegal media.
Transparency
Diffuse publishes safety-release metadata and aggregate moderation counts without reporter identities or report text.