At this level
tech.tokimeki.forum ยท 13- tech.tokimeki.forum.actor record A user's display profile for tokimeki-space. A regular (non-space) record in the user's own repo, rkey self. Readable by anyone.
- tech.tokimeki.forum.channel record A channel inside a server space. Written only by the server owner (space authority) into their own repo.
- tech.tokimeki.forum.defs defs Image attachments. Blobs are uploaded with com.atproto.repo.uploadBlob to the author's PDS and fetched by readers with com.atproto.space.getBlob (space credential required).
- tech.tokimeki.forum.hide record A 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.
- tech.tokimeki.forum.message record A message posted into a chat channel, or a comment inside a forum thread. Always written into the author's own repo within the space.
- tech.tokimeki.forum.permissions permission-set Requested by the tokimeki-space app as `include:tech.tokimeki.forum.permissions`. Image blobs are requested separately (blob:image/*).
- tech.tokimeki.forum.profile record Display information of a server. Written by the server owner into their own repo within the server's public space (rkey self), so any client holding a credential for the public space can read it.
- tech.tokimeki.forum.public space The public face of a server: a publicPolicy space paired with a tech.tokimeki.forum.server space of the same owner and skey. Anyone can obtain a credential (and, at the PDS level, write); what is shown is decided by the service index. Members may also attach tokimeki-poll polls to threads: tech.tokimeki.poll.poll and tech.tokimeki.poll.vote records live in the same space and are served by the poll AppView (poll.tokimeki.tech), which the community relays writes to.
- tech.tokimeki.forum.reaction record An emoji reaction to a message or thread. Written into the reactor's own repo within the space. rkey is derived from the subject URI and the emoji ('r' + base32lower(sha256(uri + '\n' + emoji))[0:26]) so one reactor has at most one record per (subject, emoji).
- tech.tokimeki.forum.role record A moderator role the community grants to a member. Written by the community account (the space authority) into its OWN repo within the server's public space, so any reader of the space can verify who may moderate (e.g. whose tech.tokimeki.forum.hide records to honour). rkey is derived from the subject DID ('m' + base32lower(sha256(did))[0:26]) so one record exists per member; delete it to revoke. Plain membership is not a record.
- tech.tokimeki.forum.server space A Discord-like server (guild). One space per server, anchored on the owner's DID. Channels are records in the owner's repo; messages live in each author's own repo within the space. Members may also attach tokimeki-poll polls to threads: tech.tokimeki.poll.poll and tech.tokimeki.poll.vote records live in the same space and are served by the poll AppView (poll.tokimeki.tech), which the community relays writes to.
- tech.tokimeki.forum.thread record A thread (topic) opened in a forum-kind channel. Written into the opener's own repo within the space. The thread carries its own body; comments are tech.tokimeki.forum.message records referencing it.
- tech.tokimeki.forum.vote record An upvote on a thread or a message. Written into the voter's own repo within the space. The record's existence is the vote; delete it to withdraw. rkey is derived from the subject URI ('v' + base32lower(sha256(uri))[0:26]) so one voter holds at most one vote per subject across edits of that subject.