site.mochott.longPost

An extra field on an app.bsky.feed.post record, stored under the key 'site.mochott.longPost'. It means the post is the opening of a long post and the full text is the referenced article. The reference must point to a site.mochott.article in the same repository as the post (the post's author); readers must ignore it when the DID differs. The article belongs to the long post: when the post is deleted, mochott deletes the article and its site.standard.document if the author has authorized mochott (see site.mochott.account.getAuthorization).

Repository @tokimeki.blue did:plc:4tr5dqti7nmu6g2czpthntak namespace authority
Details · object
Kindobject
Authoritymochott.site
Indexed

Object

object

Properties

cid

requiredstring · cid

CID of that article record.

uri

requiredstring · at-uri

AT URI of the site.mochott.article holding the full text: at://{author DID}/site.mochott.article/{rkey}.

Similar lexicons

semantic match

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

  • Maps a unique article ID to its Bluesky comments thread, preserving original creation time.

  • 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

  • com.guineeeeeeeeeeeeeeeeeeeeeeeerm.post

    record not from the namespace authority

    A post on guineeeeeeeeeeeeeeeeeeeeeeeerm.com. The record key is the post id (YYYYMMDD-HHMMSS). The text lives in com.guineeeeeeeeeeeeeeeeeeeeeeeerm.body records that name this post.

  • A blog article record. Contains rich text content, metadata, and optional media attachments.