max-mapper/screencat

WebRTC signalling improvements

Open

#12 opened on Mar 27, 2015

View on GitHub
 (7 comments) (0 reactions) (0 assignees)CSS (357 forks)github user discovery
help wanted

Repository metrics

Stars
 (3,007 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Research existing simple ICE/STUN signaling servers (e.g., https://github.com/maxogden/cat lobby) and evaluate their suitability for integration into Screencat. Consider TURN support and failure metrics.
Tech stack
javascriptnodejs
Domain
backendfull stack
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
WebRTC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40