matrix-org / matrix-org/matrix-spec
Consensus-based or moderated room state setting (SPEC-353)
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
There have been a few use cases where it would be useful if all (or most) of the users in a room agree on setting some room state before it takes effect - or where a proposal for room state might need to be moderated by an admin. For instance, all users in a room may need to opt in before history visibility rules are changed. Or users may propose a new avatar for the room which the admin can approve. There are some clear problems here (100% consensus breaks if even one user has gone awol), and avatars could be proposed in-band or OOB without needing dedicated protocol support for it, but it's an interesting idea
(Imported from https://matrix.org/jira/browse/SPEC-353)
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 by reviewing the proposal in this issue alongside the Matrix room-state specification; no implementation file or test is named. Define the consensus and moderation requirements, account for unavailable users, and document the protocol changes needed before implementation can begin.
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
- 20/100