If an LLM can't be trusted with a fast food order, I can't imagine what it is reliable enough for. I really was expecting this was the easy use case for the things.

It sounds like most orders still worked, so I guess we'll see if other chains come to the same conclusion.

you are viewing a single comment's thread
view the rest of the comments
[+] -7 points 1 year ago (11 children)

there is an incredibly finite number of ways to mess with this, they just need a button to send a report to the engineers with how they got messed with and eventually they'll have a complete list. I really doubt it'd take long to iron out the vast majority of ways that can be thought of.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 18 points 1 year ago (6 children)

    A QA engineer walks into a bar and orders a beer.

    She orders 2 beers.

    She orders 0 beers.

    She orders -1 beers.

    She orders a lizard.

    She orders a NULLPTR.

    She tries to leave without paying.

    Satisfied, she declares the bar ready for business. The first customer comes in an orders a beer. They finish their drink, and then ask where the bathroom is.

    The bar explodes.

  • source
  • parent
  • hideshow 6 child comments
  • [–] -4 points 1 year ago (5 children)

    This isn't something you can input any text into, it's fixed, that joke doesn't apply, you can't do an sql injection here.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 1 year ago (3 children)

    I don't know how you can think voice input is less versatile than text input, especially when a lot of voice input systems transform voice to text before processing. At least with text you get well-defined characters with a lot less variability.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 0 points 1 year ago (2 children)

    No special characters, this is speech to text, inherently sanitized inputs.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    Special characters is just one case to cover. If the user says they want "an elephant-sized drink" what does that mean to your system? At least that is relevant to size. Now imagine complete nonsense input like the joke you responded to ("-1 beers" or "a lizard"). SQL injection isn't the only risk with handling inputs. The person who ordered 18,000 waters didn't do a SQL injection attack.

  • source
  • parent
  • hideshow 1 child comment
  • none of those issues work because there is a whitelist of specific terms instead of a blacklist

    -1 cannot be selected, a lizard isn't on the list of inputs, and my point with the sql is that this isn't a huge attack vector like an input field on a website, this is a dropdown list, essentially.

    i challenge you to come up with one relevant attack that isn't order too much of a thing or order conflicting modifications (note of course the modifications are also essentially read from a dropdown list)

    everyone here seems to believe that the input field paradigm is not solveable when the inputs are fixed, that isn't true.

  • source
  • parent
  • [–] 3 points 1 year ago (3 children)

    Sounds like you've never programmed before.

  • source
  • parent
  • hideshow 3 child comments