Lexicon Garden

app.cosmosis.galaxyMember

A single account inside the owner's Galaxy. Lives inside the Galaxy's Space; the parent Galaxy is implied, since each account has exactly one Galaxy and each Galaxy Space holds exactly one Galaxy record. Delete this record to remove the account from the Galaxy. The record key SHOULD be the subject's DID when that DID is a valid record key (true for all did:plc and most did:web identifiers); otherwise use a tid. There must be at most one galaxyMember per subject, and readers must still de-duplicate by `subject`.

Repository @cosmosis.app did:plc:ahyfb4aosesmcpkc34kmc6mo namespace authority
Details · record, key any
Kindrecord
Record keyany
Authoritycosmosis.app
Indexed
Compare Edit in builder → Fork →

Record

record · key any

Properties

createdAt

requiredstring · datetime

source

string

How the account entered the Galaxy: `inferred` means the user accepted a suggestion from Galaxy inference; `manual` means the user added it directly. Lets re-inference avoid clobbering manual edits.

  • knownValues: inferred | manual

subject

requiredstring · did

The DID of the account in the Galaxy.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • app.cosmosis.galaxy

    record

    A user's Galaxy: the outer boundary of who they know they would feel comfortable interacting with online. Each account has at most one Galaxy (record key `self`). Membership is stored as separate `app.cosmosis.galaxyMember` records so a Galaxy can hold thousands of accounts. Galaxies are always permissioned: the Galaxy lives in a dedicated Space of type `app.cosmosis.galaxySpace`. The Space `skey` is a tid minted at creation (HappyView skeys are unique per Space type across an entire instance, s

  • app.cosmosis.clusterMember

    record

    A single account's membership in a Cluster. Lives inside the same Space as its parent `app.cosmosis.cluster` record. Delete this record to remove the account from the Cluster. The record key SHOULD be the subject's DID when that DID is a valid record key (true for all did:plc and most did:web identifiers), which makes writes idempotent and lets clients remove a member without a lookup; otherwise use a tid.

  • app.cosmosis.galaxySpace

    space

    Space type for a user's Cosmosis Galaxy: the outer boundary of who they would feel comfortable interacting with online. Each user has one Space of this type, holding the app.cosmosis.galaxy record (rkey self) and the Galaxy's app.cosmosis.galaxyMember records. The skey is a tid, because HappyView requires skeys to be unique per Space type across the whole instance.

  • click.aligned.chat.member

    record

    Somebody whose published conversations this collective vouches for. One record per member, written to the collective's own repo by the account owning the authorising domain. The reader walks these to know whose repos to render: a list has to live somewhere, and putting it on atproto rather than on the server is what keeps the reader working when the server is not. The record says nothing about what the member published, and carries no permission — being listed here is not what allows somebody to

  • us.off-the-clock.subspace.member

    record not from the namespace authority

    The published member entries of one account, keyed by the member's DID, across every subspace that publishes its members to the space holding this record. Written by the authority's host to the authority's own repo. Authoritative only in the authority's repo.