Hi Colin, It’s nice to know they have set up a nice way of handling things.
Two questions come to mind though: 1. Can hackers get around the method they are using? 2. Should we really believe that they are doing what they say they are doing, or are they really listening all the time, and feeding us a line to calm our fears? Just my 2 cents here. ;-) Rick > On Nov 14, 2017, at 10:55 AM, Colin Holgate via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I was at Google for meetings last week, some of which was with the Google > Home and also Assistant teams. They have the same need as Siri, and I imagine > that they solve the problem in the same way. For Google, they are always > listening for “ok google”, and Apple are listening for “hey Siri”. It’s only > a two second buffer though, that is constantly overwriting itself. If you > could steal someone’s device and freeze all electrons in it so you could > scrape for sound data, you probably would only get the sound of you picking > the person’s pocket. > > If the trigger words are detected, the next bit of sound is uploaded to be > analyzed. That happens for all devices within hearing, and online all of the > recordings are considered at the same time. The reply is usually sent to the > device that was closest to the user at the time. The recording is kept in > your history, so you can go back and listen to it to figure out why it might > have been misinterpreted. This is the page you can go to listen to yourself: > > https://myactivity.google.com/myactivity?product=29 > <https://myactivity.google.com/myactivity?product=29> > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
