matrix-org / matrix-org/matrix-spec
API to report ability to deliver messages to a given user.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
If our local server is unable to currently send messages to a remote server (or indeed an AS or a remote bridge, or even a local user in a sharded world) there should be some mechanism to report presence data back to your client to tell you that messages to that user aren't getting through. Extra points if we can guesstimate how delayed the queue is.
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 files, tests, or entry points are identified. Start by clarifying the API surface, presence semantics, and how delivery delay should be represented across local users, remote servers, application services, and bridges. Done requires agreed protocol behavior and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100