WebRTC Weekly Issue #646
Robots outgrow WebRTC, OpenAI scales it, and Opus gets 20% faster
This week is really about where WebRTC’s edges are. The voice AI crowd keeps building around it - OpenAI’s scaling writeup, Vonage’s agent connector - while the robotics folks are busy writing about growing out of it. Two ends of the same question: how far does this stack actually stretch.
⭐ Tsahi’s Pick
Why Every Robot Teleoperation Team Eventually Outgrows WebRTC (RoboticsTomorrow)
Every few months someone writes the “we outgrew WebRTC” post, and this is a good one because it’s specific about where the wall is. The funny thing is that most just parrot each other, on where the default behavior of WebRTC fails them in browsers. They forget the fully own and control the sender side and can still tune the receiver end. Instead of grokking WebRTC, they go inventing it themselves. Time and again.
📰 This Week in WebRTC
Scaling Janus WebRTC Server: Building a Media Resource Broker (WebRTC.ventures) - one of the first times I see horizontal scaling of SFUs explained in such detail
Building a Video AI Agent with Vonage Video Connector SDK and Pipecat Transport (WebRTC.ventures) - Vonage added Pipecat support, and WebRTC.ventures took it for a spin
SVC vs Simulcast in WebRTC | Complete Comparison 2026 (Digital Samba) - a look at the differences between SVC and simulcast. A nice read
Vector Vibing to speed up Opus encode by 20% (WebRTC Hacks) - Philipp Hancke continues to pick and choose areas to fix and optimize. This time, taking Opus encoding down 20% CPU on desktop
How OpenAI Delivers Low-Latency Voice AI for 900M Users (ByteByteGo) - a regurgitation of the original OpenAI post, along with a few limitations cited near the end of it
📣 Sponsor
vCon: The PDF for Your Conversations
An open standard for transcripts, metadata, and consent. Learn vCon.
📢 Releases
Chrome 150: WebRTC Diagnostic Logging API - apps can now capture WebRTC diagnostic logs programmatically instead of leaning on webrtc-internals by hand. The better approach is to use rtcStats, but I am biased about it...
✍️ This Week on BlogGeek.me
What getting rtcStats seen taught me about the whole WebRTC ecosystem
I spent months trying to get rtcStats noticed, and it turned into an accidental tour of how the WebRTC ecosystem actually pays attention: who links, who ignores you, and what it takes to register at all. Here’s what that taught me about the space I’ve been covering for years.