cv.atmos.club.post

Deprecated: legacy club posts only; new club posts use cv.atmos.club.postV2. Tags a post with the club it was posted into. Lives in the author's repo under the same record key as the app.bsky.feed.post it points at, so readers that know nothing about clubs still see a normal post. This is the member's claim; the club's own cv.atmos.club.admission record (in the club's repo) is what makes the post part of the club. Treat the post as in the club only while both records exist and point at the same post URI.

Details · record, key tid
Kindrecord
Record keytid
Authorityclub.atmos.cv
Indexed

Record

record · key tid

Properties

community

requiredstring · did

DID of the club account the post was posted into.

createdAt

requiredstring · datetime

subject

requiredref

The app.bsky.feed.post this record tags, in the same repo and at the same record key.

Similar lexicons

semantic match

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

  • A club's statement that a post belongs to it. Written only by the club account, in its own repo; the club is the repo this record lives in. The record key is derived from the subject: the unpadded lowercase base32 (RFC 4648) encoding of the SHA-256 digest of the subject's AT-URI (52 characters), so a post has exactly one admission per club and a rewrite updates the same record. Deleting the record removes the post from the club. An admission whose subject no longer exists, or whose subject CID n

  • 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

  • com.getorbyt.community.post

    record not from the namespace authority

    A user-owned canonical link between a Bluesky post and an Orbyt Community. A sidecar record: it lives in the post author's own repository and its record key MUST be the record key of the linked app.bsky.feed.post, exactly as app.bsky.feed.threadgate does. That makes one link per post structural rather than enforced after the fact, and lets the link be fetched with a single com.atproto.repo.getRecord once the post URI is known. The linked post remains canonical in app.bsky.feed.post.

  • A post that lives on Atmos and is not shown on Bluesky. It sits in the author's own repo and is public like every record there: any AT Protocol app can read it, but apps that do not know this type do not show it, so it does not appear on Bluesky. When the author shares it to Bluesky, an app.bsky.feed.post is written at the same record key and crosspost names it; the two records are one post. Treat crosspost as the link between them, never the shared record key alone, and only when crosspost.uri

  • A post in a Coves community. Posts live in community repositories and persist independently of the author. DEPRECATED: no new records are written to this collection. Successor: social.coves.community.postv2, which lives in the author's repository.