dev.cocore.account.profile

A user's cocore-side profile. Auto-provisioned at first sign-in from the user's Bluesky public profile (so they don't see an empty card on first visit), then editable from /account. Independent from any bsky.app profile — the user can change their cocore display name or avatar without affecting their bsky one. One record per DID; the upsert flow uses rkey=`self` to keep it that way.

Repository @cocore.dev did:plc:5quuhkmwe2q4k3azfsgg7kdz namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authorityaccount.cocore.dev
Indexed

Record

record · key literal:self

Properties

avatar

blob

Avatar image stored as an atproto blob on the user's PDS. Preferred over `avatarUrl` when present; consumers should resolve it via `com.atproto.sync.getBlob` against the owning PDS.

  • maxSize: 2000000
  • accept: image/png, image/jpeg, image/webp

avatarUrl

string · uri

Legacy avatar URL, retained for portability of records provisioned before the `avatar` blob field existed (typically the bsky CDN URL captured at first sign-in). Writers should prefer `avatar`; readers should fall back to this only when `avatar` is absent.

  • maxLength: 2048

bio

string

Optional free-form bio text. Plain text only; no markdown rendering today.

  • maxLength: 2560

createdAt

requiredstring · datetime

Optional human-readable name. When absent, consumers fall back to the bsky public-profile displayName, then the handle, then the DID.

  • maxLength: 256

handle

string

Display-only mirror of the user's bsky handle at provision time. Authoritative handle resolution still goes through PLC; this field exists so dashboards can render `@handle` without a PLC round-trip on every page load.

  • maxLength: 256

updatedAt

string · datetime

Last edit time. Absent on the originally-provisioned record.

Similar lexicons

semantic match

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