4 ms·
why are you limiting your argument to wake words? It's comparatively trivial to serve ads based upon what's spoken after the wake word. And as we know from th
by siliconpotato 2y ago
why are you limiting your argument to wake words?
It's comparatively trivial to serve ads based upon what's spoken after the wake word.
And as we know from the lawsuit, it seems that there's been a lot of data gathered accidentally too.
- simonw 2y agoThe story here is about Apple paying a settlement because Siri was sending audio snippets surrounding invalid wake word activations back to their servers without users realizing it. In the story, there was an implication that these audio snippets had been used for targeted ads. This is very clearly not true. A separate issue is whether Apple take audio from opt-in full hey Siri sessions and sell that advertisers for targeting. I very much doubt they do that, but even if they did that shouldn't be part of the "your phone is secretly spying on you through your microphone" conspiracy theory because of course your phone is listening to you if you just said "hey Siri" and started talking to it.
- ComplexSystems 2y agoNone of this is in the realm of "conspiracy theory." We aren't talking about the Earth being flat. Your phone is very clearly listening at all times, and sometimes activates and sends that data to servers. Given that, we can debate all day about what happens with that data - hopefully it's being treated properly - but the point is that it isn't clear, there isn't enough transparency, and there are occasionally scandals. The problem is that the infrastructure to harvest all of this data clearly exists, and the only reason we shouldn't believe that it's being mishandled is whatever degree of faith we have in these companies to behave ethically, comply with legal requirements (or face a slap on the wrist), and most importantly, have developers that don't inadvertently make any mistakes. I really don't have faith in the latter point in particular. The point is that maybe this data improperly ends up being used to serve ads, or maybe it doesn't, but in light of all the above, entertaining the idea is in no way akin to thinking that the moon is made of cheese. EDIT: clarified "recording" to "listening".
- simonw 2y agoThe reason the "phones are listening to you and targeting ads based on what you say" thing is a classic conspiracy theory is that it would take a genuine secret conspiracy to pull it off. Think about how many people would need to be in in the secret and actively lying about it: employees of phone hardware companies, and ad tech engineers, and execs at these companies, and their legal teams, and every contractor they used to help build this secret system. All of whom passionately deny that this is happening. If that's not a conspiracy I don't know what is. Just because something is labeled a conspiracy theory doesn't mean it's not true (this one isn't true though). You're welcome to continue believing in it, but saying "it's not a conspiracy theory" doesn't work for me.
- ComplexSystems 2y agoI don't think any such conspiracy or secret-keeping is required; one need not attribute any of this to malice which can be attributed to incompetence. There already exists a system, on everyone's phones, which is listening to audio at all times, occasionally activates in response to a wake word and runs search queries and such from it. The point of this system, when used properly, is intended to take a recording of your voice, transcribe it into text, send it into a search engine, associate the query with your account and search history and use it to influence ad preferences in response to future queries. The functioning of this system involves sending data through an opaque and complex chain of custody, sometimes involving third parties, which - even if intended to comply with privacy and security protocols - could easily be mishandled either maliciously or accidentally, as happens in software development all the time. This includes but is not limited to: 1. The occasional false positive response to a wake word that wasn't really a wake word, causing search queries to be run that you didn't intend. 2. This data being accidentally mishandled behind the scenes in Apple's servers in some way, such as developer error leading to the data accidentally landing in the wrong folder, being labeled with an incorrect flag in some database somewhere, or otherwise being given the wrong level of sensitivity. 3. This data being deliberately "correctly-handled" behind the scenes in Apple's servers in some way that users wouldn't like, but technically agreed to when they first used the phone. 4. This data being used for valid "QA" purposes that, for all intents and purposes, include situations that user would probably not be comfortable with, but also technically agreed to. 5. An unforeseen security vulnerability affecting any part of this process. 6. Malware on the phone interfering with any of the above. 7. Not-quite-malware that you agreed to install, doing things you're not quite happy with but technically agreed to, which is somehow in the loop of any part of this process. Again, we can debate all day which of these are true - hopefully none of them are true. But we're talking about software development here, where these sorts of things happen on a daily basis. None of this is "they faked the moon landing" kind of stuff, and all lead to the same result from the standpoint of user experience.