webrtc/: Add libp2p WebRTC private-to-private spec [tracking issue]
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Now that the specification for browser to server is merged as a Working Draft: https://github.com/libp2p/specs/pull/412, we can begin the second iteration of the browser to browser aspect. See: https://github.com/libp2p/specs/pull/412/commits/a46919c557aa4501afb285ffbec8261a7a7e595b for the beginnings.
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the browser-to-server Working Draft in PR 412 and its referenced commit, then review the checklist entries for PR 497, js-libp2p issue 1462, go-libp2p issue 2009, and the rust-libp2p ROADMAP WebRTC section. Done would require a defined private-to-private specification and resolution of the remaining unchecked implementation work.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100