matrix-org / matrix-org/matrix-spec
Should we consider seqnums rather than txnids for CS API to make it possible to spot missing msgs and make ordering easier? (SPEC-336)
Open
Nobody has claimed this yet.
A-Client-Server
feature
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Submitted by @matthew:matrix.org
(Imported from https://matrix.org/jira/browse/SPEC-336)
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. Begin with the Matrix CS API specification and the imported SPEC-336 reference, then evaluate the seqnum-versus-txnid proposal for detecting missing messages and simplifying ordering. Done should be a documented decision and corresponding specification scope.
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