cafe.dummy.lsky.post
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | lsky.dummy.cafe |
| Indexed |
Record
record · key tidProperties
May be an empty string, if there are embeds.
maxLength: 1000000maxGraphemes: 100000
Client-declared timestamp when this post was originally created.
facets
arrayRich text facets: annotations (formatting, links, mentions) and insertions (images).
followup
reflabels
unionSelf-label values for this post. Effectively content warnings.
Whether this is a portfolio post or a chirp (thought post).
knownValues: post | chirp
#followupRef
objectProperties
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
net.anisota.feed.post
recordA post that can be created in the world of Anisota
-
app.bsky.feed.post
recordRecord containing a Bluesky post.
-
Record containing a Bluesky post.
-
cv.atmos.feed.post
recordA 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
-
app.gainforest.feed.post
recordRecord containing a GainForest feed post. A faithful port of app.bsky.feed.post into the app.gainforest.feed namespace. A reply (i.e. a 'comment') is a post that carries a `reply` ref; because that ref uses com.atproto.repo.strongRef, the GainForest appview can honour replies whose parent/root is ANY record in the commons (an observation, project, cert, organization, or donation), not only another post. Deprecated `entities`/`textSlice` fields from the Bluesky source were omitted in favour of `f