matrix-org / matrix-org/matrix-spec
Important/urgent to-device messages (eg room keys) can get blocked behind big queues of less important ones
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Eg, if you have another client which spams out room key requests, those requests can take quite a long time to be delivered to a client, and during that time no m.room.encrypted events holding actual useful content are delivered.
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 with this issue and the linked Element issue 19488 to understand the queueing problem and the affected room-key requests. Review the Matrix specification sections governing to-device messages, then define the intended prioritization behavior and its observable delivery guarantees before identifying the required specification changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100