matrix-org / matrix-org/matrix-spec
Persist/seed retry schedule to speed up initial servers (SPEC-258)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Currently new servers spend ages hammering on servers over federation because they don't have any idea which servers are online and which are offline. Hinting in the room state which servers are available and unavailable would help this a lot.
(Imported from https://matrix.org/jira/browse/SPEC-258)
(Reported by @ara4n)
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 the Matrix federation and room-state specification, focusing on how servers currently discover available and unavailable federation peers. Clarify the proposed persisted or seeded retry schedule and the room-state representation before identifying the affected specification sections. Done means the protocol behavior and retry semantics are agreed and specified clearly.
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
- 20/100