com.babesky.actor.featured

Featured posts record for the Babesky creator portfolio. An ordered selection of the creator's own posts (max 8) displayed as a curated preview reel in Atmosphere apps. Consumed alongside com.babesky.actor.profile, com.babesky.actor.links, and com.babesky.actor.support.

Repository @babesky.com did:plc:qtapiembzpxlzsiagnc7eyy3 namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authorityactor.babesky.com
Indexed

Record

record · key literal:self

Properties

createdAt

requiredstring · datetime

posts

requiredarray
  • maxLength: 8
itemsref
Reference

#featuredPost

object

Properties

cid

string · cid

CID of the post record at time of featuring. Used to detect if the post has been deleted or edited.

uri

requiredstring · at-uri

AT URI of an app.bsky.feed.post in the same actor's repository.

Similar lexicons

semantic match

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

  • app.voresky.pinnedposts

    record not from the namespace authority

    An ordered gallery of posts an account has chosen to highlight. Bluesky's own profile record holds a single pinned post; this record holds an ordered list of them. The first item is the account's main pin and is expected to mirror `app.bsky.actor.profile#pinnedPost`, so that clients which do not know about this record still show the same primary pin.

  • A nominee's campaign profile: a short blurb, a pinned post, and an avatar. Written by the nominee in their own repo; the record key MUST be 'self'.

  • A feed post record for the Flashes app. EXIF metadata is stored separately in blue.flashes.photo.exif sidecar records.

  • 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

  • An admin-curated featured item, written to the dedicated curator repo (feeder.psky.social). Currently always a post; `kind` future-proofs featured collections. `active=false` pulls the item from the splash carousel but keeps it for the Inspire > Featured archive. Reorder = putRecord with a new `position`; unfeature = putRecord with active=false; hard-remove = deleteRecord.