3 ms·
FWIW, wake words are a stopgap; if we want to have a Star Trek level voice interfaces, where the computer responds only when you actually meant to call it, as o
by TeMPOraL 2y ago
FWIW, wake words are a stopgap; if we want to have a Star Trek level voice interfaces, where the computer responds only when you actually meant to call it, as opposed to using the wake word as a normal word in the conversation, the computer needs to be constantly listening.
A good analogy here is to think of the computer (assistant) as another person in the room, busy with their own stuff but paying attention to the conversations happening around them, in case someone suddenly requests their assistance.
This, of course, could be handled by a more lightweight LLM running locally and listening for explicit mentions/addressing the computer/assistant, as opposed to some context-free wake words.
- Dr4kn 2y agoHome Assistant is much nearer to this than other solutions. You have a wake word, but it can also speak to you based on automations. You come home and it could tell you that the milk is empty, but with a holiday coming up you probably should go shopping.
- Dlemo 2y agoI want that for privacy reasons and for resource reasons. And having this as a small hardware device should not add relevant latency to it.
- jillyboel 2y agoPrivacy isn't a concern when everything is local
- Dlemo 2y agoYes it is. Malware, bugs etc can happen. And I also might not want to disable it for every guest either.
- ben_w 2y agoIf the AI is local, it doesn't need to be on an internet connected device. At that point, malware and bugs in that stack don't add extra privacy risks* — but malware and bugs in all your other devices with microphones etc. remain a risk, even if the LLM is absolutely perfect by whatever standard that means for you. * unless you put the AI on a robot body, but that's then your own new and exciting problem.
- jillyboel 2y agoThere is no privacy difference between a local LLM listening versus a local wake word model listening.