site.exosphere.sphere.member
A user's declaration that they are a member of a Sphere. Published on the member's own PDS. The Sphere owner/admin publishes a corresponding site.exosphere.sphere.memberApproval record to confirm the membership. Together, the two records form a bilateral proof of membership — similar to how AT Protocol follows work.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | sphere.exosphere.site |
| Indexed |
Record
record · key tidProperties
AT URI of the Sphere record (site.exosphere.sphere.profile) on the owner's PDS.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Published by a Sphere owner or admin on their own PDS to confirm a user's membership. References the member's site.exosphere.sphere.member record. The role field indicates the member's permissions within the Sphere.
-
Declaration of an Exosphere Sphere, published on the owner's PDS. Enables third-party discovery and indexing of Spheres across the AT Protocol network.
-
Declare a membership of a project.
-
social.colibri.member
recordA community-side member record granting a user roles within the community. Lives on the community repo and is written when an admission is finalized.
-
A user-owned canonical membership link, one record per Community. The record key MUST be base32(sha256(community AT-URI)) truncated to 24 characters, lowercase and unpadded, so writing it twice replaces the record instead of adding a second one and a repo can never hold two memberships for the same Community. The AppView rejects a record whose key is not that derivation, so the invariant is enforced rather than assumed. The key is derived from the AT-URI rather than the Community name, which its