Live data from Hacker News

Viewing profile — juberti

juberti

HN member
Joined
Thu, Apr 03, 2014, 1:58 AM UTC
HN karma
11
Public activity
16 items

About juberti

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #48834899

    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. comment
    Comment #40627293

    We're running it on vLLM and are working with others in the community to bring it to other optimized inference frameworks.

  4. comment
    Comment #40137840

    We're going to add a selector to choose prompt size (and multimedia content in the prompt)

  5. comment
    Comment #40137834

    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. comment
    Comment #36423357

    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 …

  7. comment
    Comment #36422584

    Do you support WebTransport in addition to WebSockets?

  8. comment
    Comment #34736641

    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 fr…

  9. comment
    Comment #34735374

    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 resp…

  10. comment
    Comment #34734700

    It's built-in :-)

  11. comment
    Comment #34734431

    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 formatte…

  12. comment
    Comment #12758488

    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-hand…

  13. comment
    Comment #9965688

    New official Chrome extension to control this: https://goo.gl/74pT1m

  14. comment
    Comment #9115395

    These ids work just like cookies; scoped to each user and origin. If you clear cookies, the ids are cleared as well.

  15. comment
    Comment #9115383

    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…

  16. comment
    Comment #7520438

    It's OK. You can implement WebRTC as a JS library on top of ORTC.