Lexicon Garden

app.kalangitan.actor.profile

A persona: one of possibly several profiles on a single account. Every post, note, and story belongs to exactly one persona. Location visibility, precision, and gating defaults are set per-persona (see app.kalangitan.location.visibility). A public persona's records live in the account's public repo. A gated persona's records, including this profile record itself, live inside that persona's atproto Space, with a public stub record (app.kalangitan.actor.stub) in the public repo for discovery.

Repository @iamtheno.name did:plc:2aalhpujw6kqsvraztyqlngu not from the namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityactor.kalangitan.app
Indexed

Showing version bafyreie3kkjc57vdr3apuyfmulx3lxytggh45hotkrilvq3k4uscoiprgy. Show the latest

Compare Edit in builder → Fork →

Record

record · key tid

Properties

avatar

blob
  • maxSize: 1000000
  • accept: image/png, image/jpeg, image/webp

createdAt

requiredstring · datetime

description

string
  • maxLength: 2560
  • maxGraphemes: 2560

displayName

requiredstring
  • maxLength: 256
  • maxGraphemes: 256

gated

requiredboolean

True if this persona is gated: its content lives inside an atproto Space and is only visible to members. IMPORTANT: Spaces provide access control, not confidentiality as the space host and PDS operator can technically read gated data.

Similar lexicons

semantic match

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

  • app.kalangitan.actor.stub

    record not from the namespace authority

    Minimal public record for a gated persona, living in the owner's public repo. A Space's address (authority/type/skey) cannot be stumbled onto by browsing a public repo, so each gated persona needs a stub that says only: this persona exists, here is how to request access. Name, bio, avatar, and all content stay inside the Space and are invisible to non-members. Required whenever an actor.profile exists with gated=true; must not exist for public personas.

  • tech.tokimeki.forum.actor

    record

    A user's display profile for tokimeki-space. A regular (non-space) record in the user's own repo, rkey self. Readable by anyone.

  • 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

  • fyi.opensocial.actor.profile

    record not from the namespace authority

    How a member shows in one group: written by the member, in their own repo in the group's members space, so only the group's members read it. Shown in that group instead of their profile elsewhere. Its fields are app.bsky.actor.profile's.

  • social.sthenos.actor.profile

    record

    A declaration of a basic account profile.