Lexicon Garden

social.smallbury.actor.profile

Supplemental Smallbury profile data stored alongside app.bsky.actor.profile. Presentation fields (display name, avatar, description, etc.) live on the Bluesky profile record only.

Repository @lexicon.pds.smallbury.social did:plc:wnagcp6h73nxmvmwid2xxukx not from the namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authorityactor.smallbury.social
Indexed
Compare Edit in builder → Fork →

Record

record · key literal:self

Properties

appViewUrl

string · uri

Canonical HTTPS URL of the Smallbury AppView this account uses for indexing and share links.

createdAt

requiredstring · datetime

encryptionPublicKey

bytes

Public key for receiving wrapped content keys and pairwise trust secrets (format defined by the Smallbury client, e.g. X25519 or P-256 SPKI).

  • maxLength: 256

encryptionPublicKeyId

string

Identifier for encryptionPublicKey; incremented when the key rotates so trust handshakes can target the correct key.

  • minLength: 1
  • maxLength: 64

Similar lexicons

semantic match

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

  • social.smallbury.actor.keyring

    record not from the namespace authority

    Encrypted snapshot of the actor's local pairwise trust secrets for multi-device sync. Ciphertext is encrypted to encryptionPublicKey on social.smallbury.actor.profile; only the identity private key on a authorized device can decrypt it.

  • app.bsky.actor.profile

    record

    A declaration of a Bluesky account profile.

  • space.priiv.profile

    record

    A public Priiv profile, independent of the account's Bluesky profile.

  • social.sket.actor.profile

    record

  • dk.raakode.lab.groups.profile

    record

    A person's name and pictures, in their own public repo, readable by any application. Deliberately NOT app.bsky.actor.profile, even though that is the obvious home and the shape is identical: asking for repo:app.bsky.actor.profile makes the authorization server classify the whole request as Bluesky-specific and silently drop the space permissions from the consent screen (see docs/evidence/S03.md). A consent screen that under-reports what is being granted is worse than a non-standard namespace. Re