pics.2bit.feed.photogate
A photo author's statement about the comments on one of their photos, modeled on app.bsky.feed.threadgate. Comments live in their authors' repos, so a photo's author cannot delete one; instead they list it here, in their own repo, and the AppView folds it out of the thread - still one tap away for anyone who asks, the way Instagram and Bluesky treat hidden comments. The record key must be the photo's own rkey, and a gate is only honored in the repo that holds the photo - one written anywhere else is ignored.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | feed.2bit.pics |
| 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.
-
pics.2bit.feed.comment
recordA comment on a 2bit.pics post record.
-
community.gifthood.replygate
recordThe 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.
-
social.respawn.feed.gate
recordInteraction settings for a log or list, analogous to app.bsky.feed.threadgate/postgate. The record key (rkey) must match the rkey of the gated record. Absence of a gate record means everyone can interact.
-
app.didpic.feed.comment
recordA comment on a post. Optionally includes a single image with alt text and self-applied labels — same image shape as feed.post. Either text or image (or both) must be present in practice; the lexicon doesn't enforce that since 'one of N required' isn't expressible.
-
social.respawn.feed.comment
recordA comment on a log or list. Stored in the commenter's repo; the subject's author can hide it via their social.respawn.feed.gate record.