matrix-org / matrix-org/matrix-spec

How to deal with large rooms. (SPEC-36)

Open
#47 4 comments 0 reactions 0 assignees View on GitHub
A-S2S feature room-vNext
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

For every user in the room we currently have a dedicated state event for them. For large rooms with many 1000s or more members this becomes less than ideal due to the overhead for both clients and servers.

The protocol itself only requires knowledge of which servers are in the room.

(Imported from https://matrix.org/jira/browse/SPEC-36)

(Reported by @erikjohnston)

Contributor guide

Open the contributing guide

Research direction

Start by reading the SPEC-36 discussion linked in the issue and the Matrix protocol requirements it references. The issue identifies per-user state events and server membership as the relevant protocol areas, but it does not name files, tests, or a concrete acceptance condition; a resolved design and specification update would define done.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems, documentation
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.