matrix-org / matrix-org/matrix-spec

Add a mechanism for a server to say it's no longer interested in a room

Open
#1,249 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

improvement
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

When a server leaves a room, it's possible for one or more other servers in the room not to get the memo, so that they keep sending events to a server that is no longer interested in them.

It would be nice if the receiving server could in some way indicate its lack of interest, so that the sending server stops sending events. (Though we'd need to think carefully about the conditions under which it would restart.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or protocol entry point is named in the issue. Begin by locating the existing room-leave and event-delivery rules in the Matrix specification, then define the receiving server's signal, when sending must stop, and the conditions for restarting; the work is done when those rules are specified clearly.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.