matrix-org / matrix-org/matrix-spec
Clarify when `state_key` needs to be `""` in authorization rules
Open
Nobody has claimed this yet.
clarification
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
**Link to problem area**:
https://spec.matrix.org/v1.12/rooms/v11/#authorization-rules
**Issue**
It's not explicit that state events without other requirements on the `state_key` field must be `""`.
For example, there's nothing like
> N. If `state_key` is not `""`, reject.
for handling `m.room.create` events.
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 linked Matrix v1.12 authorization-rules section and compare the handling of m.room.create with nearby state-event rules. Update the specification so the state_key requirement is explicit, then verify that the wording consistently covers rules without another state_key requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100