matrix-org / matrix-org/matrix-spec
Spec specific error codes and kick content for deleted rooms
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Tangent to #431
Some implementations implement the idea of a deleted room, which effectively means users all get kicked from a room and all API requests to that room become M_FORBIDDEN, as if the room never existed.
I'd propose that some changes should be made for clients to distinguish a kick and a room delete thus that clients can display / react appropriately. My suggestion would be an extra key in leave events to hint at the kind of kick (e.g. moderation v.s. deletion) and an error code when trying to access a room to make it clear that the room was deleted.
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 #431 and the Matrix specification sections covering leave events and room-access errors. Define how deleted-room kicks and ordinary kicks should be distinguished, then specify the corresponding event content and error code so clients can react differently; done means the proposal is precise enough for implementations to follow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100