Web開発
ATProtoパーミッション付きデータ提案ドラフト
ATProto Permissioned Data Proposal Draft (github.com)
要約
この記事は、Blueskyの分散型プロトコルであるATProtoにおける「パーミッション付きデータ」に関する初期の提案ドラフトです。著者は、詳細や用語が変更される可能性が高いと述べており、具体的なフィードバックをこのプルリクエストで、より広範な議論をコミュニティフォーラムで行うよう求めています。
全文翻訳
Permissioned data - #94
Open
Co-authored-by: Eli Mallon <eli@stream.place>
| A space may be deleted by its authority. The authority stops issuing credentials and no longer answers for the space. The authority also deletes its own repo in the space. | ||
The authority then notifies registered syncers and known repo hosts of participating members with com.atproto.space.notifySpaceDeleted, over the same best-effort path as write notifications. |
read_self is the narrower grant. It confers access to the same read and sync methods, but only for the holder's own repo in the space, and it does not grant getDelegationToken. An application holding only read_self can read its user's own records but cannot reach the rest of the space. read implies read_self. | ||
| A space credential grants whole-space read/sync access directly, so the read and sync methods accept either a covering OAuth scope or a space credential. Write methods accept only an OAuth credential, since a write is attributed to the authoring user. |
- It does not include an lxm claim. | ||
- It is bound to a target space through the sub claim. | ||
| Example JWT header and payload (before base64url encoding and signing): |
| ### Client attestation | ||
A client attestation is a short-lived JWT that the application presents to the space authority alongside the delegation token to identify itself, when the space requires it. It is structurally a private_key_jwt client assertion, the same shape an atproto confidential client already presents to its authorization server, but addressed to the space authority rather than to the PDS. |
Omitting action grants read, create, update, and delete (read is inclusive of read_self). | ||
Omitting collection defaults it to the collections declared by the space type's declaration. A bare space:com.atmoboards.forum grant therefore permits writing the forum's own record types, the same way a bare repo: scope permits writing the collections it names. An application may narrow this by listing a subset of collections, or widen it with collection=*. When spaceType is * there is no declaration to draw from, so the default is empty and the grant confers no write targets unless provided. |
| ### Client attestation | ||
A client attestation is a short-lived JWT that the application presents to the space authority alongside the delegation token to identify itself, when the space requires it. It is structurally a private_key_jwt client assertion, the same shape an atproto confidential client already presents to its authorization server, but addressed to the space authority rather than to the PDS. |
[画像: @trezy] trezy mentioned this pull request
Merged
dholms marked this pull request as ready for review
dholms deleted the permissioned-data branch
Open
2 of 9 tasks
Open
Open