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)
We're running it on vLLM and are working with others in the community to bring it to other optimized inference frameworks.
We're going to add a selector to choose prompt size (and multimedia content in the prompt)
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
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…
Do you support WebTransport in addition to WebSockets?
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…
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.
It's built-in :-)
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).
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.
New official Chrome extension to control this: https://goo.gl/74pT1m
These ids work just like cookies; scoped to each user and origin. If you clear cookies, the ids are cleared as well.
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…
It's OK. You can implement WebRTC as a JS library on top of ORTC.
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)
We're running it on vLLM and are working with others in the community to bring it to other optimized inference frameworks.
We're going to add a selector to choose prompt size (and multimedia content in the prompt)
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
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…
Do you support WebTransport in addition to WebSockets?
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…
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.
It's built-in :-)
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).
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.
New official Chrome extension to control this: https://goo.gl/74pT1m
These ids work just like cookies; scoped to each user and origin. If you clear cookies, the ids are cleared as well.
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…
It's OK. You can implement WebRTC as a JS library on top of ORTC.