matrix-org / matrix-org/matrix-spec
Invite handling is broken when the inviter leaves the room (SPEC-364)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Consider:
- alice@venus creates a room and invites bob@mars
- bob@mars joins and invites charlie@mars
- bob@mars leaves
At this point, `mars` no longer takes part in the federation of the room, and `charlie` can neither reject nor accept his invite, nor can he see the history of the room.
Should federation include servers with invited rather than joined members, or does this leak too much data? Or should we decouple the federation from members as per https://github.com/matrix-org/matrix-doc/issues/597?
(Imported from https://matrix.org/jira/browse/SPEC-364)
(Reported by @richvdh)
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 invite-and-departure scenario in SPEC-364 and the referenced matrix-doc issue 597; no implementation files or tests are named. Determine whether federation should include servers with invited members or be decoupled from membership, then define the corresponding Matrix specification change.
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
- 15/100