matrix-org / matrix-org/matrix-spec
`/createRoom` is not clear about what should happen if you specify yourself as an invitee
Nobody has claimed this yet.
- 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.1/client-server-api/#post_matrixclientv3createroom
**Issue**
Current Synapse behaviour is to raise a 403 much like it would do if you tried to invite yourself (this is specced behaviour for `/invite`).
My suggestion would be to just specify that retroactively so that other homeservers can benefit from having the clarity and to prevent divergence in behaviour across other implementations.
Of course, if it'd be preferable to change, then I don't see why it couldn't be done — it just seems like sending a 403 as you would for an `/invite` is sensible enough.
Related: https://github.com/matrix-org/synapse/issues/10740
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 at the Matrix Client-Server API's POST /_matrix/client/v3/createRoom section, linked in the issue, and compare its treatment of self-invites with the /invite behavior. Clarify what happens when the creator specifies themselves as an invitee, while preserving the proposed 403 behavior; done means the specification no longer leaves this case ambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100