matrix-org / matrix-org/matrix-spec
We should define m.* events for setting up webrtc data channel (SPEC-173)
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
Would be really useful for low-latency non-persistent signalling scenarios
(Imported from https://matrix.org/jira/browse/SPEC-173)
(Reported by @ara4n)
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
The issue names no files, tests, or entry points. Start by locating existing Matrix m.* event definitions and the WebRTC data-channel specification; clarify the event schema and negotiation flow before implementation. Done means the required setup events are defined in the spec with their behavior and interoperability details documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100