Spider-Man's Uncle Ben and His Advice for Casting Your Web(RTC)
summary
127 slides in 20 minutes condense a hard lesson: a production WebRTC pipeline using Pion + Janus + GStreamer breaks when RTCP is ignored. The team patches quality by spamming keyframe requests, which momentarily hides the problem but floods bandwidth; proper RTCP handling fixes it. Live tests show failure at 10–30% packet loss without RTX/PLI support and smooth recovery when nack/pli/rtcp are implemented. Watch if you need concrete failure modes and fixes.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:25Uncle Ben's wisdom on WebRTC
- 4:17LibWebRTC vs real WebRTC
- 6:45Falling into basic traps
- 8:55The importance of RTCP handling
- 12:11Why mistakes happen in WebRTC
- 13:38Expecting too much magic
- 15:04Packet loss and resilience
- 17:53WebRTC's complex specifications
- 19:40More choice means more responsibility
- 20:24Q&A: Standardizing WebRTC
related talks
21mWebRTC - A tale of Beekeeping
27mWebRTC: Real-Time Communications
21mWebRTC A Quick Introduction
09h 29mJsconf India Track 2
20mBeyond P2P: Video Routing in WebRTC
21mOptimizing the customer experience
46mWebRTC: Let’s Revolutionize Information Sharing in the Browser
56mYou're on Mute! WebRTC and our Lives on Screen