Private and shared data
Private records belong to the user (repo is theirs) but stay off the public network: the platform stores and serves them. Each one is written for a space, at://{authority}/{spaceType}/{key}: the authority owns the space, the author wrote the record, and they need not be the same person. A space type’s policy decides who reads and writes there, from claims (memberships, shares). Every write names its space (space); one that names none is 400 InvalidRequest. A public record goes through com.atproto.repo.putRecord on the PDS instead, and a record only the user reads goes in their personal space, at://{user}/pub.techne.draft.space.personal/self. Writes are never refused for the space they name: the space admits the record or it counts nowhere, and the answer says which (space is absent when not admitted). Calls: pub.techne.draft.permissioned.putRecord, putRecords, deleteRecord, getRecord, listRecords, listChanges.
Three options today:
- Public: ordinary repo records, read by anyone.
- Your app’s own space per user:
at://{user}/pub.techne.draft.space.private/{appKey}, whereappKeyis yourclient_idhashed: base32 (lowercase, no padding) of its SHA-256. Ask forspace:pub.techne.draft.space.private?skey={appKey}. Only that user reads it, and only through your app: the platform admits and serves a record there only for the app its key names. Any collection but the platform’s own record types (400InvalidRequest); the adopted calendar types are allowed and stay your app’s data. - Everything the user can reach:
include:pub.techne.draft.authReadorauthWrite: their personal space, their circles, beacons shared with them. The consent page shows a large warning; ask only if the app needs it.
A token that carries space: scopes reaches only the spaces they cover: other writes are 403 Forbidden, other records are not returned. This works for users on techne.town (our PDS puts your client_id and granted scopes on the call); users on other PDSes cannot use an app space yet. An agent token names no app, so test app-space calls from the app.
The path from here: apps approved per space (a circle lets your app in), then full permissioned data for community apps when spaces move to the 0016 address format, always with a clear warning on consent.