How salinda-kumara/skreen works
Skreen pairs a sender with a receiving browser using a short-lived cast code, then relays WebRTC signaling while media travels directly between peers or through TURN. The map includes the documented capture, quality, statistics, and reachability features. Server relationships are supported by the sampled imports and calls; browser-side details not shown in excerpts are limited to relationships documented in the README.
Main entry points: http.js HTTP API and static files · sender.js Sender page · app.js Sign-in and pairing · viewer.js Viewer page
Components 21
Browser flow
- Sign-in and pairing
web/app.js - Login client
web/lib/session.js
Casting and media
- Sender page
web/sender.js - Viewer page
web/viewer.js - Adaptive quality
web/lib/quality.js - WebRTC statistics
web/lib/rtcstats.js - ICE diagnostics
web/lib/ice.js - Browser signaling client
web/lib/signaling.js
Server API and security
- HTTP API and static files
server/http.js - Passcode authentication
server/auth.js - Request limiting
server/ratelimit.js - Runtime configuration
server/config.js - Redacted logging
server/log.js
Sessions and signaling
- HTTP and WS bootstrap
server/index.js - Session and token store
server/sessions.js - WebSocket signaling relay
server/signaling.js
Network services
- TURN credentials
server/turn.js - coturn relay
Other components
- Sender user
- Receiver user
- Android sender
Connections 35
- Sender user → Sign-in and pairing: enters code
README.md - Receiver user → Sign-in and pairing: chooses Receive
README.md - Sign-in and pairing → Login client: checks login
web/app.js - Login client → HTTP API and static files: calls auth API
README.md - Sign-in and pairing → HTTP API and static files: claims code
web/app.js - Sign-in and pairing → Sender page: opens after claim
web/app.js - Sign-in and pairing → Viewer page: opens Receive
web/app.js - Sender page → Browser signaling client: uses signaling
- Viewer page → Browser signaling client: uses signaling
- Sender page → Adaptive quality: adapts capture
- Sender page → WebRTC statistics: samples connection
- Viewer page → WebRTC statistics: samples connection
- Sender page → ICE diagnostics: checks reachability
- Viewer page → ICE diagnostics: checks reachability
- Browser signaling client → WebSocket signaling relay: exchanges SDP and ICE
README.md - WebSocket signaling relay → Session and token store: authenticates tickets
server/signaling.js - WebSocket signaling relay → Session and token store: updates session peers
server/signaling.js - HTTP and WS bootstrap → HTTP API and static files: creates handler
server/index.js - HTTP and WS bootstrap → WebSocket signaling relay: attaches relay
server/index.js - HTTP and WS bootstrap → Session and token store: starts janitor
server/index.js - HTTP API and static files → Passcode authentication: authenticates requests
server/http.js - HTTP API and static files → Request limiting: limits requests
server/http.js - HTTP API and static files → Session and token store: creates and manages sessions
server/http.js - HTTP API and static files → TURN credentials: returns ICE servers
server/http.js - HTTP API and static files → Redacted logging: logs API events
server/http.js - Passcode authentication → Runtime configuration: reads secrets
server/auth.js - Session and token store → Runtime configuration: reads lifetimes
server/sessions.js - Session and token store → Redacted logging: logs session events
server/sessions.js - WebSocket signaling relay → Runtime configuration: reads limits
server/signaling.js - TURN credentials → Runtime configuration: reads TURN settings
server/turn.js - TURN credentials → coturn relay: issues temporary credentials
- Sender page → Viewer page: sends encrypted media
README.md - Sender page → coturn relay: relays media when needed
README.md - Android sender → WebSocket signaling relay: uses same protocol
README.md - Android sender → Viewer page: streams encrypted media
README.md