community.gifthood.replygate
The listing owner's moderation of notes on their own listing, bsky-threadgate style: the record key MUST match the listing's record key. hiddenReplies drop from default views (view policy, not deletion — the note survives in its author's repo; reports remain the violation path). Future allow/close rules are additive fields here.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | gifthood.community |
| Indexed |
Record
record · key tidProperties
Strong reference to the owner's own listing. Belt for the matching-rkey suspenders; indexers verify both.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
community.gifthood.reply
recordA public note on a listing — appreciation, a question, a joke; the front porch. Thread-native: root is ALWAYS the listing; parent is the listing for top-level notes or another reply once threaded rendering exists. Mirrors app.bsky.feed.post's reply-ref semantics. Public, like the interest record.
-
app.bsky.feed.threadgate
recordRecord defining interaction gating rules for a thread (aka, reply controls). The record key (rkey) of the threadgate record must match the record key of the thread's root post, and that record must be in the same repository.
-
Record defining interaction gating rules for a thread (aka, reply controls). The record key (rkey) of the threadgate record must match the record key of the thread's root post, and that record must be in the same repository.
-
so.sprk.feed.threadgate
recordRecord defining interaction gating rules for a thread (aka, reply controls). The record key (rkey) of the threadgate record must match the record key of the thread's root post, and that record must be in the same repository.
-
tech.tokimeki.forum.hide
recordA moderator's decision to hide a thread or message in this server. Written by the moderator (owner, admin or mod) into their OWN repo within the space: a repo only ever carries its holder's own statements. The record's existence is the hide; delete it to unhide. rkey is derived from the subject URI ('h' + base32lower(sha256(uri))[0:26]) so one moderator holds at most one hide per subject. The service index honours hides from accounts that hold a moderator role at the time of indexing.