matrix-org / matrix-org/matrix-spec
Recommendations on rate limiting / backoff for federation
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
It would be good to mention to potential developers what would be a good way to back-off dead/unresponsive servers over federation. In my experience there is a **wide** number of failures that should be handled in subtle ways. I have some concerns that the best advice currently is "follow what Synapse does" which is pretty counter to the goal of the spec.
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
No file, test, or entry point is named. Start by reviewing the federation specification and the issue's reference to Synapse's behavior, then identify how guidance could cover dead or unresponsive servers and their varied failures. Done means the specification contains clear, implementation-independent rate-limiting and backoff recommendations.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100