cv.atmos.club.admission
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 no longer matches the post, admits nothing.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | club.atmos.cv |
| Indexed |
Showing version bafyreifl25ng6dwhc5vwfwstckipx4qlwauvj5u7azi5zkwsobacsx4cga. Show the latest
Record
record · key anyProperties
When the club admitted the post.
The admitted club post (cv.atmos.club.postV2, or a legacy app.bsky.feed.post), pinned to the version the club admitted.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
cv.atmos.club.post
recordDeprecated: 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
-
A community's attestation that it accepts a post. Written only by the community's key holder, automatically once admission checks pass - machine attestation, not human approval. The community is implicit in the repository this record lives in. The record key is deterministic: the unpadded lowercase base32 encoding of the SHA-256 digest of the canonical subject AT-URI (fixed 52 characters, always rkey-safe), so a post has exactly one acceptance rkey per community, concurrent writers converge idem
-
cv.atmos.club.postV2
recordA 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 user-owned canonical membership link, one record per Community. The record key MUST be base32(sha256(community AT-URI)) truncated to 24 characters, lowercase and unpadded, so writing it twice replaces the record instead of adding a second one and a repo can never hold two memberships for the same Community. The AppView rejects a record whose key is not that derivation, so the invariant is enforced rather than assumed. The key is derived from the AT-URI rather than the Community name, which its
-
A community actor's acceptance of an exact self-submission and post version.