{
"id": "dk.raakode.lab.groups.profile",
"defs": {
"main": {
"key": "literal:self",
"type": "record",
"record": {
"type": "object",
"required": [
"createdAt"
],
"properties": {
"avatar": {
"type": "blob",
"accept": [
"image/png",
"image/jpeg"
],
"maxSize": 1000000,
"description": "Square picture shown beside this account's posts."
},
"banner": {
"type": "blob",
"accept": [
"image/png",
"image/jpeg"
],
"maxSize": 1000000,
"description": "Wide picture shown behind the profile."
},
"createdAt": {
"type": "string",
"format": "datetime"
},
"description": {
"type": "string",
"maxLength": 2560,
"maxGraphemes": 256
},
"displayName": {
"type": "string",
"maxLength": 640,
"maxGraphemes": 64
}
}
},
"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."
}
},
"$type": "com.atproto.lexicon.schema",
"lexicon": 1
}