matrix-org / matrix-org/matrix-spec
if all users leave a room, the room should not wink out of existence. (SPEC-211)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Submitted by @matthew:matrix.org
we need to keep a HS or two in the room somehow to 'keep the lights on' and preserve history even if all the participating users leave. this would also be helpful as a way for ASes to interact with rooms without needing an explicit AS user joined.
(Imported from https://matrix.org/jira/browse/SPEC-211)
Attachments:
https://matrix.org/jira/secure/attachment/10210/public-rooms.png
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the imported SPEC-211 issue and the attached public-rooms.png; no repository file, test, or entry point is named. Research Matrix room-lifecycle and homeserver behavior, then document a decided protocol change covering rooms whose users leave and appservice interaction.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100