net.olamaelcu.livtet.bookClub.post

A post in a book club discussion, stored in the author's repo inside the club's space. Threading follows the aggregator-forum shape: every post carries a root (the bookClub.thread) and a parent; a top-level post is its own parent (parent == root), while a reply's parent is another post in the same thread. Linear readers can ignore parent beyond the root; tree readers can rebuild the tree. The space, not the record, is the access boundary.

Details · record, key tid
Kindrecord
Record keytid
AuthoritybookClub.livtet.olamaelcu.net
Indexed

Record

record · key tid

Properties

createdAt

requiredstring · datetime

Client-declared timestamp when the post was created.

langs

array

Human language of the text, BCP 47 tags.

  • maxLength: 3
itemsstring · language

reply

requiredref
Reference

text

requiredstring

The post body. Empty is allowed when the post is only a reply marker, though a discussion post normally has text.

  • maxLength: 10000
  • maxGraphemes: 2000

#replyRef

object

Thread position. `root` MUST be a net.olamaelcu.livtet.bookClub.thread record in the same space. `parent` MUST be that thread (for a top-level post, where parent == root) or another net.olamaelcu.livtet.bookClub.post in the same space whose own root matches. StrongRefs pin the revision being answered, as app.bsky.feed.post does; grouping compares `root.uri`, so an edited thread keeps one discussion.

Properties

parent

requiredref

root

requiredref

Similar lexicons

semantic match

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

  • A reply to a forum topic or another reply, with threaded parent references and community attribution.

  • A reply to a post or to another reply. For a direct reply to a post, root and parent are the same.

  • ink.resenha.feed.comment

    record not from the namespace authority

    A comment on a reader's book record, or a reply to such a comment: the conversation about a reader reading a book, for activities in Resenha's Feed that have no post to reply to. One subject per book per reader, so comments on their starting and finishing it are one thread. Written in the commenter's account; Resenha's server threads them and tells the reader.

  • A post made into a club. Lives in the author's own repo and is public like every record there; apps that do not know this type do not show it, so it does not appear on Bluesky. The author's claim that the post is in the club named by community; the club's own cv.atmos.club.admission record (in the club's repo) is what makes a top-level post part of the club. Treat a top-level post as in the club only while the admission exists and points at this record's current URI and CID. A reply is in the cl

  • A reply in a thread. Lives in the author's repo. Flat by default; parent enables quote-chain threading.