chat.yakka.ban
A member is barred from a server. Authority-written (ADR 0006). Enforcement is layered (ADR 0008): the mint refuses new credentials immediately and the realtime tier cuts the socket at once, but credentials already held live out their 2h TTL — the protocol has no revocation (Law 2). A ban is therefore effective within the TTL everywhere, and instantly where we serve.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | yakka.chat |
| Indexed |
Record
record · key tidSimilar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
app.protoimsg.chat.ban
recordA ban issued by a room owner or moderator. Lives in the issuer's repo.
-
app.userinput.ban
recordBans a user from a space (their content is hidden and they cannot post). Only honored when authored by the space owner or a moderator. Lives in the moderator's repo.
-
farm.lore.banished
recordA user banned from a world.
-
An audit log entry for a moderation action taken by the community. Enforcement is the space authority declining to issue credentials, and this records that it happened.
-
chat.yakka.mute
recordSomething the viewer does not want to hear from — a space, a server, or a person. Personal state in the viewer's own settings space (ADR 0017). A mute is a presentation preference, never access control: it hides, and hiding is not gating (Law 1).