Lexicon Garden

place.birds.profile

How the observer wants to be shown on birds.place. One per account; the record key is always `self`. Every field is optional — a missing profile, or a missing field, falls back to what the wider network says about the account (an app.bsky.actor.profile display name, then the handle). This record exists so that never having used Bluesky is a first-class situation.

Repository @birds.place did:plc:w4p4bumx22vgnjmctoqjj7sy namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authoritybirds.place
Indexed
Compare Edit in builder → Fork →

Record

record · key literal:self

Properties

createdAt

requiredstring · datetime

Client-declared timestamp for when the profile was first created. Preserved across edits.

displayName

string

The name to show beside this observer's sightings, in place of their handle.

  • maxLength: 640
  • maxGraphemes: 64

updatedAt

string · datetime

Client-declared timestamp for the most recent edit.

Similar lexicons

semantic match

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

  • xyz.opnshelf.profile

    record

    An Opnshelf profile record

  • club.syntax.actor.profile

    record not from the namespace authority

    A declaration of a Syntax Club account profile.

  • dev.cocore.account.profile

    record

    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.

  • blue.backyard.actor.profile

    record

    A declaration of a Backyard account profile.

  • at.mapped.profile

    record

    A user's mapped.at profile. Singleton record — rkey is always 'self'.