matrix-org / matrix-org/waterfall
Handle `seq` field on to-device messages to ensure their order
Open
T-Defect
T-Task
- Dominant language
- Go
- Stars
- 105
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
@daniel-abramov: should we also treat it in the SFU code or rather on the SDK level?
Contributor guide
Research direction
Start by locating the SFU and SDK handling for to-device messages, then trace where the seq field is currently received or ignored. Resolve whether ordering belongs in the SFU or SDK layer, and verify that messages are handled in seq order once the chosen layer is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- audio-video-rtc, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100