matrix-org / matrix-org/matrix-spec
Consider supporting arbitrary state changes when upgrading rooms
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Some rooms might want to go from m.federate: true to m.federate: false or fix power levels which they cannot otherwise do (everyone is an admin, oops). Similar to /createRoom, there could be a parameter on the request body to override the state that's going to be set in thew new rooms.
The problem with this would be the large avenue for abuse: someone with enough permission could effectively lock out everyone else by simply upgrading the room.
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
Review the existing room-upgrade behavior and the /createRoom request described in the issue. Define the request shape, permitted state changes, and safeguards against administrators locking out other users before identifying the relevant Matrix specification section. Done means the proposal has an agreed security model and complete specification requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100