matrix-org / matrix-org/matrix-spec
Two requests for sending media is painful for clients
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Clients which want to show a simple error state for upload/message sending failed are stuck trying to aggregate the two on their own. Instead, the protocol could somehow support sending the media alongside the message, possibly as a template with attachment. Then, if any part of the upload/send fails, the client simply retries.
A challenge would be encryption, as the server won't have information to put into a template of sorts.
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 protocol's existing media upload and message-send flows, including how encryption and attachments are handled. Done requires a decided protocol design that lets clients retry the combined operation without aggregating two requests themselves.
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
- 25/100