
rtc@meta. Still cheering for @jitsinews and @NVIDIAGFN. Opinions are my own and I have plenty of them.
Bellevue, WA
Joined October 2013
- Tweets8K
- Following449
- Followers2.2K
- Likes19.1K
Pinned Tweet
I joined ten years ago for @realtimeconf in PDX which was awesome! It's enough, see you on the other side!
Philipp Hancke retweeted
Weekly Voice and Video AI Update 🎉 👇
The speech-to-speech race is heating up. xAI shipped Grok Voice 3.0, which jumped to #1 on Artificial Analysis' speech-to-speech index. OpenAI answered with GPT-Live-1.1, which adds 13 new voices and better accents, and opened prompt-to-voice to every API customer. Amazon also made Nova 2.5 Sonic generally available on Bedrock, with better reasoning, async tool calling and a 256K context window at the same price as before.
And again more news on the video avatars space coming from Tavus with Kiosk mode and Telnyx AI Assistants. Also a trial a voice companion for snowbound seniors coming from ElevenLabs and NTT that looks like a great use case for video avatars in the future.
The infrastructure is catching up just as fast. LiveKit Inference now runs cascaded, speech-to-speech and full-duplex models side by side. Turn-taking is still where a lot of the work is. ElevenLabs added turn prediction to its real-time STT, Pipecat shipped user and bot backchannels, and a great webrtcHacks piece shows how leaked echo still tricks agents into hearing turns that never happened.
FULL UPDATE IN THE NEWSLETTER LINK BELOW 👇
Have a great week!
Philipp Hancke retweeted
Chrome quietly downloads a neural echo estimator. @HCornflower reverse engineers the model, tests it against AEC3, and asks "why don’t other browsers get the weights"?
See the latest @webrtcHacks post:
webrtchacks.com/chrome-neura…
Philipp Hancke retweeted
Updated our Live API/Realtime API documentation to show how to use the new WARP extensions for WebRTC to reduce connection latency to a single RTT, typically well under 100 ms.
developers.openai.com/api/do…
Philipp Hancke retweeted
All vendors should have a plan for rapid remediation in the case of active exploitation.
Here’s some emergency fix strategies we’ve seen over the years:
projectzero.google/2026/10/e…
Philipp Hancke retweeted
New post: Google Chrome downloads a new neural AEC while you are not looking
@HCornflower reverse engineers the model, tests it against AEC3, and asks why other browsers don't get the weights.
webrtchacks.com/chrome-neura…
Philipp Hancke retweeted
Another post about GPTLive. Even if most of the parts and WebRTC integration had been shared before I liked the prefill and handoff sections in this post.
Philipp Hancke retweeted
Firefox users sometimes failed to connect to ChatGPT Voice due to a 12-year-old WebRTC implementation issue. This prevented one of our team members from using his favorite browser, so he figured out what was going on and resolved this long-standing bug: bugzilla.mozilla.org/show_bu….
Philipp Hancke retweeted
Chrome: developer.chrome.com/origint…
Edge: developer.microsoft.com/en-u…
The usual OT restrictions apply (pre-standard, wire format may change) but for most apps this should be an easy win.
Philipp Hancke retweeted
Talking with @tsahil tomorrow morning about WARP and the other WebRTC improvements that we made for GPT-Live!
linkedin.com/events/builtwit…
Philipp Hancke retweeted
WARP started out as a ramble session at Bellevue Brewing Co with @HCornflower, and became a complete reworking of the WebRTC setup flow, running the DTLS handshake in parallel with ICE, and collapsing the SCTP handshake entirely.
datatracker.ietf.org/doc/dra…
Philipp Hancke retweeted
Just posted our technical deep dive on the GPT-Live system, by @zahanm and yours truly.
Philipp Hancke retweeted
The more I talk to people about my work at the IETF the more I realize just how poorly understood its processes are outside a niche community. It’s surprising because of how critical the IETF’s work is: they define the standards that make the Internet go (HTTP, TCP, TLS, DNS, …)
Philipp Hancke retweeted
New post: Vector Vibing to speed up Opus encode by 20% - @hcornflower describes how he wired up the AVX2 Opus implementation for speed gains
webrtchacks.com/vector-vibin…
🤖 Made with AI
Philipp Hancke retweeted
New post: Vibe-coding #WebRTC by @HCornflower - using AI to tackle long-standing WebRTC issues and ship fixes across libWebRTC, @ChromiumDev , @_pion , and @firefox without handing taste over to the minions
webrtchacks.com/webrtc-vibes…
Philipp Hancke retweeted
The ICE protocol (RFC 5245) was designed for peer to peer flows, but it’s turned out to be remarkably versatile even in client-server scenarios, allowing for easy authentication, stateless routing, and realtime path selection. Details in our post below: openai.com/index/delivering-…
Philipp Hancke retweeted
Interesting review of the WebRTC infrastructure at OpenAI:
❤️ kudos for avoiding the SFU model, doesn't make any sense for Voice AI IMO
🤷♂️ not loving the relay approach even if I get the benefit
💡 ice ufrag routing is not new but smart anyway
🎙️ Voice AI only feels natural when conversation keeps pace with speech.
Here’s how we rebuilt our WebRTC stack with a thin relay and stateful transceiver to keep real-time media fast for ChatGPT voice, the Realtime API, and more.
openai.com/index/delivering-…
Philipp Hancke retweeted
2017.09.03にサービス開始した旧SkyWayですが、昨日を以てサービス終了となりました。2013.12にpeer.jsをベースに最初のSkyWayを立ち上げて、旧SkyWayでもそれを踏襲して13年間やってきましたが、感慨深いものがあります。
new Peer()は無くなりましたが、新SkyWayを引き続きよろしくお願いします!
旧SkyWayから、新「SkyWay」へ🚀
昨日、旧バージョンのSkyWayが13年の歴史に幕を閉じました。
多くの開発者のみなさまに支えていただき、
本当にありがとうございました🙏
新SkyWayはこれからも進化を続けます!
skyway.ntt.com/ja
#WebRTCSkyWay
Philipp Hancke retweeted
Blink: Intent to Extend Experiment: Playout Statistics API for WebAudio
bit.ly/4hUxLzj
Philipp Hancke retweeted
New post: Is everyone switching to #MoQ? @HCornflower responds to some FUD about #WebRTC in a recent MoQ launch post with some historical perspective & Chrome Status data
webrtchacks.com/is-everyone-…
Philipp Hancke retweeted
RtcStats is a product now! 🚀
Part of the code started as an internal project at TokBox ~2016, then it was used by Houseparty ~2018 and by StreamYard at ~2022.
Even if you don't know millions of users had an RtcStats client at some point🤯
Awesome job @tsahil @HCornflower & co
🚀 Exciting news for #WebRTC users! 🤩 If you've ever used webrtc-internals, get ready for rtcStats!
🎉 We just launched rtcStats - an open-source suite and SaaS offering to help you master webrtc-internals files
✨ Free tier available. Check it out at rtcstats.com






















