Search Lexicons

appviews choose which resolvers to trust and display (default: the question's designated resolver). Outcome semantics follow Metaculus: 'ambiguous' = reality could not be determined under the criteria; 'annulled' = the question itself was defective (underspecified, assumptions

An article as shown in feed rows and search results (metadata only).

Mark all unread articles in effective follow set as read

Account-level preferences for The Social Wire. This record stores non-sensitive preferences only; third-party access tokens and secrets must not be stored in ATProto repos.

preferences for a discovered standard.site publication. The publication list itself is derived from the user's ATProto follow graph (app.bsky.graph.follow records) — this record stores only the organizational preferences that are not expressed in the protocol

comic series — the container a reader follows. Individual chapters/issues are separate art.graphik.issue records that point back at this one. Display title of the series. Genre / subject tags. Publication status. Optional URL-friendly identifier, unique within

Shared objects for openlegal.ch legal-annotation lexicons. Field shapes follow the W3C Web Annotation Data Model (WADM); AT Protocol lexicon + IPLD is the wire format (not WADM JSON-LD). A projection to WADM JSON

A declaration of a Bluesky chat account.

whether their account is chat-disabled and whether their group-membership additions are restricted to accounts they follow. The maximum number of members allowed in a group conversation. True when the viewer's account

marker is a `chat.yakka.readMarker` record in the viewer's own settings space (ADR 0017), so it follows them to any client rather than living in this appview's idea of them. Monotonic: a marker never

space. Lives in the viewer's own chat.yakka.settings space, authority=self (ADR 0017), so read state follows the person across devices and into third-party clients. The space this marker is for. Also the record

Batch variant of getRelationship: check the follow relationship between `actor` and each of `others

need not consent and cannot suppress it. Consumers find disputes by querying com.atproto.sync.listReposByCollection for this collection and following the subject URIs. Record key is a TID. CID of the exact record version being disputed

listed gift, and when it was completed. The counterparty attests via community.gifthood.exchangeResponse; a mutually confirmed pair is follow-through evidence. Public, like the interest record. Strong reference (URI + CID) to the listing this exchange

flower planted in another user's garden, representing a 'like' or 'follow'. DID of the garden owner receiving the flower. Client-declared timestamp when the flower was planted

indexer's acknowledgement that it follows this space. Written by the indexer into its own repo in the space, for one reason: com.atproto.space.listSpaces returns the spaces an account holds a REPO in, not the spaces

A game, as distinct from any one release of it. There is one of these per game per developer, and its record key is the game's id — so its AT-URI is a permanent name for the game, which releases point back at (ADR 0037).

List games known to the appview, most recently released first.

lenses published by another account. Like a follow, it lives in the subscriber's repository

contribution to a story tree. Freshly written buds grow for 24h (not yet followable); after that they open as 'blooms' that other writers can extend; past 48h without children they lock into 'branches'. These lifecycle