Concepts
Spaces and permissions
Some records are for a room only. A space is that room, and it has an owner.
In each writer's own repo
The space
Who reads
One writer's recordClaims the space. Its writer was admitted when techne.computer first saw it.
Another writer's recordClaims the space too. This writer was not admitted.
A space
at://{authority}/{spaceType}/{skey}Its authority owns it
Admissionrun by the managing app
The first recordCounts here
Read policyof the space type
The record stays in its writer's repo. The space is where it counts.
Who the policy admitsReads the record
Everyone elseNever sees it
- A record claims a space by naming it when it is written, and the record itself stays in its writer's repo.
- techne.computer counts it in the space only if its author was admitted at the time techne.computer first saw that version.
- The space type's read policy decides who reads the records that count there.
- The managing app runs admission, and for spaces created through techne.computer, techne.computer is the managing app.
A record claiming a space
space is required: a write that names none is refused (400 InvalidRequest). A record only its writer reads goes in their own personal space, at://{did}/pub.techne.draft.space.personal/self.
One real policy
The event detail space
An event's exact location and attendee notes are not on the public event. They are pub.techne.draft.event.detail records in this space, which shares its key with the event's invite space. One event has two audiences and two spaces.
- Any one of these can read
confirmedForevent: this- A confirmed
approvalnames you for this event. The host writes approvals; onlyconfirmedopens the details. authorityOnly- You are the space's authority. That is the person hosting their own event.
memberRoleof: authority, atLeast: 20- You are a builder (role 20) or above in the collective hosting the event, so whoever can host it can read what they wrote.
- Write
authorityOnly- Only the host.
- Manage
authorityOnly- Only the host.
pub.techne.draft.space.event.detail.policy
The published policy is what techne.computer enforces. An empty any or all lets nobody in. Event detail space on techne.pub →