Browse lexicons

matching 6 lexicons

Narrow to

atmos6

cv.atmos 6 Narrow ›

cv.atmos.authFull permission-set
cv.atmos.club.admission record 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
cv.atmos.club.post record 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
cv.atmos.club.postV2 record 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
cv.atmos.club.rule record One club rule, in the club account's own repo. The record key stays the same across edits, so reports and removals can cite the rule by URI. Deleting the record retires the rule.
cv.atmos.feed.post record 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