To be able to detect when you say, "Hey Google" (Or "Alexa")-- It has to be listening *all* the time.
-
-
“Listen” but in the sense of a spike in an easily recognizable sound pattern that then indicates, “turn on, respond, and process what follows”.
-
Certainly that was the original design. As you surely know, many of us now tape over the cameras on our computers b/c of spying.
-
And some of us choose to not spend our days in fear.
End of conversation
New conversation -
-
-
A vibration type sensor is essentially a microphone
You can't detect a voice if you're not listening. It's a logical necessity.
However, if these devices are implemented with efficiency and security in mind, they will simply discard all data not meant to be sent out. -
It is no more “listening” than the VOX setting on a radio used for two-way communications is, or the old “The Clapper” switch.pic.twitter.com/UoD7M0ERkk
-
I seem to remember some Google or Amazon engineer saying that all processing for the trigger sound ("Alexa!") is done on local hardware, whereas the actual requests ("... where's the nearest McDonalds?") are sent to / processed in the cloud. (Not that it makes a big difference.)
-
Actually, that’s a pretty big difference.
-
How so? (To be a little more specific: it doesn't change the fact that tons of recordings of one's voice are sent out & stored on a server.)
-
Uhm…by using one of those voice-processing systems you’re consenting for it to be transmitted.
-
Good point.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.