computer.localnetwork.people.request

A request to join a performer's, party's or venue's space, keyed by the requester's DID. Written by the Local Network root account for the requester, who isn't a member until someone with people.manage approves it.

Repository @localnetwork.computer did:plc:d42l64gsczg6qh2vo243xv5l not from the namespace authority
Details · record, key any
Kindrecord
Record keyany
Authoritypeople.localnetwork.computer
Commit rev3n2kadjcm6u2n
Indexed

Record

record · key any

Properties

createdAt

requiredstring · datetime

hidden

boolean

Whether they want to be hidden from everyone outside the space once they're in.

message

string
  • maxLength: 3000
  • maxGraphemes: 300

subject

requiredstring · did

Similar lexicons

semantic match

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

  • computer.localnetwork.people.person

    record not from the namespace authority

    Someone in a performer's, party's or venue's space, keyed by their DID. Written only by the Local Network root account, which makes them a member of the space: a reader, and a writer when one of their capabilities writes. Deleting it takes them out.

  • computer.localnetwork.people.invite

    record not from the namespace authority

    An invite to join a performer's, party's or venue's space, keyed by the invitee's DID. Written by the Local Network root account for someone with people.manage, and deleted when they lose it. The invitee isn't a member until they accept, which replaces it with a computer.localnetwork.people.person record.

  • A standing offer of friendship to another account. A PUBLIC repo record, not a space record: the point of a request is to be readable by someone who has no access yet, and a non-member's write into a space is never visible to anyone else (see docs/evidence/S06.md). Keyed by the subject DID, so offering twice updates rather than duplicates.

  • A request to join a project. Requester-owned.

  • A request asking someone to write an introduction. Each recipient DID may have only one active request from the requester (one record per recipient).