• 0101100101@programming.dev
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    8 hours ago

    Uhm, REST/GraphQL APIs exist for this very purpose and are considerably faster.

    Note, the AI still gets stuck in a loop near the end asking for more info, needing an email, then needing a phone number, and the gibber isn’t that much faster than spoken word with the huge negative that no nearby human can understand it to check that what it’s automating is correct!

    • chronicledmonocle@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 hours ago

      The efficiency comes from the lack of voice processing. The beeps and boops are easier on CPU resources than trying to parse spoken word.

      That said, they should just communicate over an API like you said.