tools.kryphocron.graph.mute

Private-tier mute record. One-directional. Not confidential: like any repo record, a mute can reach sync channels such as the firehose, so who muted whom is observable there. Audience-list-exempt (consumed by MuteOracle outside the normal capability flow).

Details · record, key tid
Kindrecord
Record keytid
Authoritygraph.kryphocron.tools
Commit rev3n2ivyfl5rc2a
Indexed

Record

record · key tid

Properties

createdAt

requiredstring · datetime

subject

requiredstring · did

The muted DID.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A mute relationship. The muted account's content is hidden from the muter's feed.

  • A muted subject. One record per mute, so unmuting is a delete rather than a rewrite of a list.

  • Something 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).

  • Mutes a subject for this reader: either a user (a DID) or a publication (the AT-URI of its site.standard.publication record). Presence of the record means muted; deleting it unmutes. The rkey is derived from the subject so each subject maps to a single record. Muted subjects are hidden from the reader's feeds and discovery surfaces, but direct navigation still works and subscriptions are untouched.

  • Klearsky client-specific record that stores a list of DIDs whose reposts should be muted.