dk.raakode.lab.groups.profile

lexauthority.pds1.lab.raakode.dk

Documentation

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. Readers should still fall back to app.bsky.actor.profile when this is absent.

main 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. Readers should still fall back to app.bsky.actor.profile when this is absent.

Record Key literal:self Fixed literal value

Properties

avatar blob Optional

Square picture shown beside this account's posts.

maxSize: 1.0 MB
banner blob Optional

Wide picture shown behind the profile.

maxSize: 1.0 MB
createdAt string datetime Required

An RFC 3339 formatted timestamp.

description string Optional

No description available.

maxLength: 2560 bytesmaxGraphemes: 256 graphemes
displayName string Optional

No description available.

maxLength: 640 bytesmaxGraphemes: 64 graphemes
View raw schema
{
  "description": "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. Readers should still fall back to app.bsky.actor.profile when this is absent.",
  "key": "literal:self",
  "record": {
    "properties": {
      "avatar": {
        "accept": [
          "image/png",
          "image/jpeg"
        ],
        "description": "Square picture shown beside this account's posts.",
        "maxSize": 1000000,
        "type": "blob"
      },
      "banner": {
        "accept": [
          "image/png",
          "image/jpeg"
        ],
        "description": "Wide picture shown behind the profile.",
        "maxSize": 1000000,
        "type": "blob"
      },
      "createdAt": {
        "format": "datetime",
        "type": "string"
      },
      "description": {
        "maxGraphemes": 256,
        "maxLength": 2560,
        "type": "string"
      },
      "displayName": {
        "maxGraphemes": 64,
        "maxLength": 640,
        "type": "string"
      }
    },
    "required": [
      "createdAt"
    ],
    "type": "object"
  },
  "type": "record"
}

Lexicon Garden

@