4 ms·
Despite often seeming like a thin veneer of natural language processing on top of a search engine, I'm sure most users think of their voice assistants, or are w
by hanoz 8y ago
Despite often seeming like a thin veneer of natural language processing on top of a search engine, I'm sure most users think of their voice assistants, or are willing them to be, a general AI agent. They don't want to have to care what app/skill/web-scrape is involved in enabling a response.
The whole skills ecosystem feels like an awkward stopgap on the path to AI. The language required to invoke them feels particularly clunky - "Alexa, ask ThingFinder about a thing" - and then, is the user supposed to be talking to ThingFinder now, or Alexa? She still sounds like Alexa, but she doesn't seem quite herself.
As developer choosing an invocation name is fraught with difficulty. There are only so many natural sounding names for something which does a particular thing, without incongruously inserting some invented branding word onto it - "Alexa open Tidy Tide Tables". If someone's already using the most natural name you are free to use exactly the same, but then who knows whose skill will be launched? And you'd better make sure your skill's name doesn't clash with anything else in the world at large, like the entire history of music for example, "Alexa play Wicked Game". It's all a bit of a mess.
- sp332 8y agoYeah, that's a good point. People are good at mentally compartmentalizing behaviors with personalities. If Alexa doesn't allow each agent to have a personality, people are going to have a hard time keeping the behaviors straight. Kinda reminds me of Neuromancer, where a superintelligent AI was broken into two pieces to avoid detection. One part was good at personality, and the other part had to mimic people in order to communicate. It was very unnerving for people to talk to an AI that was copying the personality of someone they knew.