4 ms·
I think you're not really engaging with his point, which is that RTC is a poor fit for communicating with an AI agent. I didn't read the blog as claiming that
by entrope 5mo ago
I think you're not really engaging with his point, which is that RTC is a poor fit for communicating with an AI agent. I didn't read the blog as claiming that WebRTC is bad for what it is, only that it's a (very) poor choice for a voice-to-AI application.
- ricardobeat 5mo agoOnly if you expect to interact with the agent in a turn-taking format, with (possible) pauses between every turn. ChatGPT’s voice mode is like speaking to someone in real time on a voice call, not input -> output.
- thutch76 5mo agoThat's fair. My attention wanted and I lost the plot. However, I don't think having an agent on one side necessarily changes anything. Network problems are not predictable, particularly on mobile, so the human is still very likely to experience a poor auditory experience on a tcp connection.
- echoangle 5mo agoThe difference is that the agent doesn’t run in realtime. If 20 packets are lost and resent, the agent can still process them almost instantly and reply, in contrast to a human. Only the direction from the agent to the human needs to be realtime.