Top
Best
New

Posted by atgctg 1 day ago

OpenAI’s WebRTC problem(moq.dev)
329 points | 82 commentspage 2
splittydev 3 hours ago|
Amazing read. Blog posts rarely keep my attention like this one.
Aeroi 9 hours ago||
there are a lot of extremely smart people that have come back to webRTC time and time again because it continues to solve problems other methods and protocols can't. with saying that, quic is certainly interesting going forward, but i primarily stream voice + vision at 1fps so it just makes sense, and websockets fail and are insecure at scale for this use case (see https://www.daily.co/videosaurus/websockets-and-webrtc/) . also just listen to sean in this thread, dude knows whats up.
lpln3452 10 hours ago||
I haven't really experienced disconnections while using ChatGPT. Gemini is the frustrating part. Simply backgrounding the app (and the web version too) and resuming it causes the response or the conversation with an assigned ID to disappear. Haha.
Sean-Der 10 hours ago|
I believe Gemini is Websockets? I have the same experience with heavy/custom applications that try to roll their own media stuff.

You run into issues around AudioContext and resumption etc... it's a PITA to have to handle all those corner cases :(

nutanc 6 hours ago||
Most of the problems happen because we want to simulate human conversations. While thats a good goal to have, another approach is to let the user know clearly they are talking to a bot. You will be surprised at how accomodating users can be when they know they are talking to a bot and want their queries resolved.
schappim 8 hours ago||
"WebRTC is the problem" is bait; his real claim is "WebRTC has annoying transport-layer characteristics that hurt cloud Voice AI scaling"...

Having just had to tackle this again for my own startup, I'm reminded about what you would lose by ditching WebRTC - the audio DSP pipeline, transmit side VAD, echo cancellation, noise suppression, NAT traversal maturity, codec integration, browser ubiquity etc.

dboreham 7 hours ago|
You don't need NAT traversal when talking to a cloud service.
schappim 7 hours ago||
We have browser-based HW used inside a construction site manager’s site office behind a random FW
elephantum 6 hours ago||
My biggest frustration with WebRTC was precisely captured in the article: even if you don't need p2p and your video source is the process on the same host with your browser, you have to dance around connection setup like you're on a different side of a planet
gozzoo 4 hours ago||
I didn't understand - why is WebRTC good for Google Meet and not good for all other conferencing apps?
fy20 9 hours ago||
Nice fun article. Gives me Why The Lucky Stiff vibes.
hnav 7 hours ago||
Exactly what I thought when I read the original article, though to be fair WebTransport is barely now entering the mainstream with Safari shipping support this year.
sam1r 9 hours ago|
>> ... I say hi to <strike> Scarlett Johansson <strike>

Had a nice chuckle.

More comments...