Has anyone actually confirmed that Chrome is continuously sending audio back to Google? I highly doubt that this is the case. Instead, the plug in knows how to recognize "OK Google" all by itself. Once activated, then it starts sending audio data. IF it where really listening even when inactive, then people would be complaining about it sucking up bandwidth and data allotments.
Google listening in to your room shows importance of privacy defense in depth
51–60 of 124 posts
Re: Google listening in to your room shows importance of privacy defense in depth
#52Has anyone actually confirmed that Chrome is continuously sending audio back to Google? I highly doubt that this is the case. Instead, the plug in knows how to recognize "OK Google" all by itself. Once activated, then it starts sending audio data. IF it where really listening even when inactive, then people would be complaining about it sucking up bandwidth and data allotments.
I would change it to:
Has anyone actually confirmed that Chrome is continuously listening?
Re: Google listening in to your room shows importance of privacy defense in depth
#53Earlier quoted context omitted.
Can you provide any proof of that? No, Android phones are not listening all the time
Nope, I have no proof, and of course I'd be happy to learn that they aren't listening. I just hypothesize that they are based on my experience, but I've not tried to test it in any systematic way.
Re: Google listening in to your room shows importance of privacy defense in depth
#54Earlier quoted context omitted.
A couple of hundred million dollars is a trivial write off for google. It should be a 5% of revenue.
Can we stop with the witch hunts and the desire to maim folks over minor infractions like this? Consider that you're one of the developers that wrote this feature. You try very hard to make sure your users privacy rights are respected. Normally your work is strong and you catch all of the corner cases, but this one you missed. You've fixed it upstream, but folks are demanding 5% of the company's bottom line because o…
By that reasoning, tobacco and asbestos shouldn't be regulated
Re: Google listening in to your room shows importance of privacy defense in depth
#55Earlier quoted context omitted.
A couple of hundred million dollars is a trivial write off for google. It should be a 5% of revenue.
Can we stop with the witch hunts and the desire to maim folks over minor infractions like this? Consider that you're one of the developers that wrote this feature. You try very hard to make sure your users privacy rights are respected. Normally your work is strong and you catch all of the corner cases, but this one you missed. You've fixed it upstream, but folks are demanding 5% of the company's bottom line because o…
IMNSHO, user-hostile business decisions should be fined in a way that does impact the business. We've long since passed the point where this can be resolved with a slap on the wrist. So yes, 5% of revenue seems like an appropriate figure to start with.
Re: Google listening in to your room shows importance of privacy defense in depth
#56Re: Google listening in to your room shows importance of privacy defense in depth
#57Has anyone actually confirmed that Chrome is continuously sending audio back to Google? I highly doubt that this is the case. Instead, the plug in knows how to recognize "OK Google" all by itself. Once activated, then it starts sending audio data. IF it where really listening even when inactive, then people would be complaining about it sucking up bandwidth and data allotments.
It's not about consistently being bugged though--I see two troubling implications to this; a) Government A decides target B has valuable communications, and uses this audio capture functionality as an attack vector (ie, a MiTM server modifies the chrome binary blob request slightly to a version where chunked audio is sent back to a control server). b) (more likely) This binary blob contains a voice recognition algori…
The problem with this blog post is that the author gets in a tizzy about what could happen, not what is actually happening. What could happen has not been affected by the recent Chromium screw-up, nor is it specific to Chromium.
Re: Google listening in to your room shows importance of privacy defense in depth
#58Re: Google listening in to your room shows importance of privacy defense in depth
#59Has anyone actually confirmed that Chrome is continuously sending audio back to Google? I highly doubt that this is the case. Instead, the plug in knows how to recognize "OK Google" all by itself. Once activated, then it starts sending audio data. IF it where really listening even when inactive, then people would be complaining about it sucking up bandwidth and data allotments.
> Has anyone actually confirmed that Chrome is continuously sending audio back to Google I would change it to: Has anyone actually confirmed that Chrome is continuously listening?
I'd say it's pretty much a given that it's continuously listening. How else would it know when to respond to an "ok, google" audio cue?
Re: Google listening in to your room shows importance of privacy defense in depth
#60Earlier quoted context omitted.
> Has anyone actually confirmed that Chrome is continuously sending audio back to Google I would change it to: Has anyone actually confirmed that Chrome is continuously listening?
Tell you what: you get me the source code, and I'll tell you what it's doing. I'd say it's pretty much a given that it's continuously listening. How else would it know when to respond to an "ok, google" audio cue?
Because you open a new tab or you go to the search bar and then starts to listen IF you have activated that option?
"Ok Google" only works on a new tab page. Look at the microphone icon in the search box to see whether it’s listening for the phrase "Ok Google" or not:
https://support.google.com/websearch/answer/2940021?p=ui_hot...