juberti

8 ms·

1.
How OpenAI built a realtime system for responsive voice AI in six months(openai.com)
2 points by juberti 2mo ago|0 comments
2.
by juberti 2mo ago
yes, it now has much better ability to understand the conversation and decide whether it should respond (and you can also tell it when it should respond)
3.
by juberti 2y ago
We're running it on vLLM and are working with others in the community to bring it to other optimized inference frameworks.
4.
by juberti 2y ago
We're going to add a selector to choose prompt size (and multimedia content in the prompt)
5.
by juberti 2y ago
Can you describe what you'd like to see for #1? We currently show everything, but let people filter via the UI or URL param, e.g., https://thefastest.ai/?mf=3-70
6.
by juberti 3y ago
The basic idea would be a simple voice conferencing bridge that you connect to via WebTransport. There are a number of more interesting things that we would be interested in if we could get this sort of basic scenario working.
7.
by juberti 3y ago
Do you support WebTransport in addition to WebSockets?
8.
by juberti 4y ago
I agree caution is needed here. We have taken a few steps: - Rate limits are enforced to provide caps on agent and function usage. - Execution depth is capped to prevent the LLM from getting into loops. - Function output is sanitized to pre
9.
by juberti 4y ago
Current context lengths are usually more than adequate for these interactions; the details of each individual step within an execution only need to be retained until the final response is emitted.
10.
by juberti 4y ago
It's built-in :-)
11.
by juberti 4y ago
yes, the LLM sees the result of the function and processes it according to what it has learned from its few-shots (which may involve calling more functions, or returning a formatted response).
12.
by juberti 10y ago
Current implementations of WebRTC, by default, only perform STUN over the default route (to address this exact situation). See https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling-01 for more details.
13.
by juberti 11y ago
New official Chrome extension to control this: https://goo.gl/74pT1m
14.
by juberti 12y ago
These ids work just like cookies; scoped to each user and origin. If you clear cookies, the ids are cleared as well.
15.
by juberti 12y ago
We have added an initial solution for this issue in Chrome 42. Users can set the following preference: "webrtc": { "multiple_routes_enabled": false }, For the location of the prefs file, see http://www.chrom
16.
by juberti 12y ago
It's OK. You can implement WebRTC as a JS library on top of ORTC.