max-mapper / max-mapper/screencat
WebRTC signalling improvements
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3k
- Forks
- 354
- PR merge metrics
- No merged PRs in 30d
Description
right now we use trickle-less SDP swapping through a custom lobby signalling server.
it would be better to use ICE/STUN, but in general I was displeased with the state of many of the signalling servers on npm, which is the main reason I made https://github.com/maxogden/cat-lobby. if someone can recommend a simple signal lobby that can do ICE/STUN then I would be happy to swap out the backend
it would be cool to use TURN, though I need to figure out a way to measure failure metrics first before investing in higher bandwidth infra like that
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 reviewing the current custom lobby signalling server, cat-lobby, and the existing trickle-less SDP swapping flow. Investigate simple npm signalling options that support ICE/STUN, and define how signalling failures would be measured before considering TURN. Done means agreeing on a replacement backend and an objective failure metric.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100