Skip to content
Tech News
← Back to articles

OpenAI’s WebRTC problem

read original more articles
Why This Matters

This article highlights the limitations of WebRTC for voice AI applications, emphasizing its aggressive packet dropping and protocol complexity, which hinder performance and user experience. It underscores the need for better communication protocols tailored to AI workloads, impacting both developers and consumers seeking reliable voice interactions.

Key Takeaways

published 5/6/2026

OpenAI’s WebRTC Problem

OpenAI posted a technical blog a few days ago. This blog post triggered me more than it should have. I urge to slap my meaty fingers on the keyboard.

You should NOT copy OpenAI.

I don’t think you should use WebRTC for voice AI. WebRTC is the problem.

Me

Like 6 years ago I wrote a WebRTC SFU at Twitch. Originally we used Pion (Go) just like OpenAI, but forked after benchmarking revealed that it was too slow. I ended up rewriting every protocol, because of course I did!

Just a year ago, I was at Discord and I rewrote the WebRTC SFU in Rust. Because of course I did! You’re probably noticing a trend.

Fun Fact: WebRTC consists of ~45 RFCs dating back to the early 2000s. And some de-facto standards that are technically drafts (ex. TWCC, REMB). Not a fun fact when you have to implement them all.

You should consider me a Certified WebRTC Expert. Which is why I never, never want to use WebRTC again.

... continue reading