3 ms·
This case seemed a pretty cut and dry bug in pre-release software. They actually launched the device with the at-fault feature disabled while they fixed the bug
by apocalyptic0n3 8y ago
This case seemed a pretty cut and dry bug in pre-release software. They actually launched the device with the at-fault feature disabled while they fixed the bug, even. I get that Google is difficult to trust when it comes to privacy issues, but in this case it seemed like a bug much in the way a few weeks ago an Alexa picked up keywords that it understood as "Call this person" and the people on the other end of the call were able to hear a private conversation.
- mcphage 8y ago> This case seemed a pretty cut and dry bug in pre-release software. In this case it was actually hardware—the button used to manually trigger the device (instead of saying “okay google”). Seems weird that Google managed to screw up a button, but i doubt it was malicious.