5 ms·
Having worked at large companies before, I'm almost certain that more than one person working on the product raised the point "this has a microphone, why isn't
by userbinator 8y ago
Having worked at large companies before, I'm almost certain that more than one person working on the product raised the point "this has a microphone, why isn't it documented?" or "this has privacy implications", but was silenced.
(Or it could be that everyone working at Google has been carefully chosen to not have such concerns; I do get that feeling sometimes too.)
- s3r3nity 8y agoI remember someone in a recent HN comment thread mentioning that, as an ex-Googler, Google today feels like Microsoft under Ballmer. So while I agree with you, it _also_ wouldn't surprise me if someone raised the concern, but that person was on a different / more silo'ed team and therefore the concern never reached the execution stage. Herego too many management layers and/or nodes of entropy for communication. But that's just a hypothesis.
- eitally 8y agoAs a current googler, this seems like the most plausible explanation. Entirely likely that the person who noticed didn't actually know which other team to escalate to....
- balabaster 8y agoOr was "yes, yes, we'll add a story to the backlog to add it to the specs" and it just flat out got forgotten. I've seen this happen so many times where I've been the one to raise the issue and because I've passed it off, I've forgotten about it only to circle back around 2 months later when someone says "Oh, we need to do this" and I say "I raised this 2 months ago, I thought X had put it in the backlog." And when you go looking, sure enough, there it is in the backlog down in Priority "We'll get to it when we get to it, after all these other more important things that needed to be completed by last week."
- jamieson-becker 8y agoAlthough this is all possible and perhaps even more plausible than the alternative, it's still more fun and conspiratorial to view Google as the new Evil Empire, so I'll just keep doing that, thanks.
- CodeSheikh 8y agoI am sorry but I do not buy this "added to backlog and forgot" theory, especially for a resources-packed company like Google. Are you implying that everyone from PM to devs to QA all ignored the microphone sitting in there? All electronics needs to be compliance tested at a gov labs in Northeast (Baltimore area) because of electromagnetic signature since Nest devices have WiFi. Are you saying even they forgot to bring it up as well?
- balabaster 8y agoI'm not saying the microphone was ignored or forgotten about, I'm saying the "add that line to the specification sheet for public release" was forgotten about.
- SpicyLemonZest 8y agoSure, that seems plausible. If the existence of the microphone wasn't a secret internally, why would PM or devs or QA or government inspectors be disturbed to see it?
- lrem 8y agoI work in Google and my org of over a hundred engineers has a single tech writer assigned. I assure you she never sees the bottom of her backlog.
- balabaster 8y agoThis is so common in so many companies I've worked with that it doesn't even begin to surprise me. This is an accepted way of life at most tech companies.
- SilasX 8y agoReminds me of the time that school issued laptops where the camera could be remotely turned on when the student was using it at home (including in their bedroom), and somehow no one realized the pervy implications. https://en.wikipedia.org/wiki/Robbins_v._Lower_Merion_School_District https://en.wikipedia.org/wiki/Robbins_v._Lower_Merion_School...
- dmonagha 8y agoOh they absolutely knew the pervy implications, they didn't think they would ever be caught: https://en.wikipedia.org/wiki/Robbins_v._Lower_Merion_School_District#Covert_surveillance https://en.wikipedia.org/wiki/Robbins_v._Lower_Merion_School... "The school district intentionally did not publicize the existence of the surveillance technology. It also actively sought to conceal it.[23][41]" https://en.wikipedia.org/wiki/Robbins_v._Lower_Merion_School_District#cite_note-autogenerated4-23 https://en.wikipedia.org/wiki/Robbins_v._Lower_Merion_School...
- hoffs 8y agoI doubt that they were silenced, more like the concern was raised but it was given some random answer at first and said to be discussed at a later date and then forgotten.
- gameshot911 8y agoYou're "almost certain", huh?
- sct202 8y agoMy take is that maybe by that point that someone noticed all the product material had been printed or generated and someone else didn't want to redo it, or forgot, and hoped it would blow over.
- illumin8 8y agoContrast this to Amazon: during design of the original Echo at Lab126, an engineering discussion took place where they determined that implementing the mute function in software would be less expensive in terms of component requirements than implementing a physical disconnect of the mic circuit. The engineering team refused to take the less expensive route, and insisted that the mute button physically disconnect the circuit, so that no future engineering team could decide to stealth "unmute" the microphone through software. To this day, you can disassemble an Amazon Echo device and you will find a physical disconnect of the mic circuitry when you push the mute button. Don't want an "always listening" smart speaker? Just keep it muted, and a red LED circle informs you that the mic is physically disconnected. I'm proud of the approach that Amazon takes to privacy. Privacy of customer data is considered the most important thing to Amazon, and this customer obsession (the #1 leadership principle) permeates the organization. Disclaimer: I'm a principal engineer at Amazon.
- perfmode 8y agoDoes this apply to the Sonos one, also? It has Alexa integration, but is a sonos project.
- illumin8 8y agoI don't believe this applies to any 3rd party products. Those manufacturers have to make their own design decisions.
- x38iq84n 8y agoGood job. Thank you/the team for standing up for good basic principles.
- glenrivard 8y agoGoogle home uses the same approach with a physical mute button. How is that in contrast?
- maximente 8y agois this the same company that's shilling Rekogition to police departments and governments? for some reason i'm thinking this point of view isn't held company wide.
- jhayward 8y agoIt seems at least as likely that the microphone feature, as a non-working component of a future product upgrade, was omitted at the request of attorneys reviewing the product literature so as to not create a false expectation of that unreleased feature. I've worked on several products that had capabilities that we were told by attorneys could not be "advertised" (i.e., no references to them) until the complete feature was ready to be announced.
- patmcguire 8y agoYeah, I think it's most likely that. Seems very plausible Nest wanted to have some voice features but they got cut before launch. The mic's still there because changing hardware is hard, it's not announced because it doesn't do anything.
- sonnyblarney 8y agoProduct Marketing does not 'document' they position, and write about features. If the 'mic' isn't part of feature or proposition, why would it even be in their radar? The '1st order' response of marketing doing their job is 'who cares?'. Few people care about tech tidbits that are not user oriented. There's already tons of things to worry about and address - and every single bit of copy takes up valuable space. The issue also does not fit into the standard communications framework: Hey, should we should tell people that there is a microphone, even if it is not working and does nothing? How do we even do that? "Hey, your alarm has a microphone!" Wouldn't that seem odd, why does it have a microphone?! You'd even have to kind of explain it: "Your product has a microphone so that one day in the future, you might enable some other features that don't exist yet" "this has privacy implications" - no - it only has the perception of privacy implications. Because Google is not actually intervening on people's privacy, it's unlikely they really thought about the need to give people an unneeded affirmation. Maybe they had a discussion about it, maybe it just didn't rise to the level of 'very important'. Only with a very specific concern for a subgroup of customers who are wary of these things, would someone have enough leverage to get that "Hey, there's a microphone that does nothing!" notice on the box. Google is not doing specific evil. They are not trying to infiltrate your homes and take nude pictures of you so they can look at them or sell them. They are systematically evil, in the sense that it makes sense for them to sell you voice/video features that you want in order that they might provide you even better services. And their AI will use nudies of you in a backwards way to learn more about you. They're getting evil due to their scope of influence, and negative externalities, much like FB has problems with 'Russian interference in elections' - i.e. not a problem they are trying to create, not a problem they want, just a sensitive byproduct of their product and massive success.
- pbhjpbhj 8y ago>`"this has privacy implications" - no - it only has the perception of privacy implications. Because Google is not actually [intruding] on people's privacy [...]` I've got to disagree here: it has privacy implications because at Google's end they can issue a software update and now be monitoring all audio, and the T&C no doubt say they can be unilaterally varied without notification. That all means that Google think I accept Google snooping on me; of course I don't but in court Google lawyers would say I did, and them being in a position to do that is important. Also, if Google can enable the mic at some point then it's likely that's a possibility for a third party (crackers), OR that Google could do it in response to a legal demand from a government. There seems no good reason to me that the specification summary can't say "microphone - not in use yet, reserved for future applications"; with a sentence somewhere expanding on that explaining they want the ability to improve the device later and do shipped a mic because it could be useful to expand the products capabilities. Some of us actually do read instruction books; it would no doubt get some column-inches in a positive way ("what changes might Google make"). Google know everything they make is going to get a tear-down and that mics are going to be discovered in short-shrift: it's ignorant to not anticipate that. In fact one really has to assume they knew this "issue" would come up.
- bagacrap 8y agoDocumented where? Honest question. The marketing department isn't going to list something that's totally non functional. Is there a privacy oriented spec sheet somewhere (that people will actually read)? I can see this slipping through the cracks between different job roles' responsibilities, although after this incident they'd probably go through a post mortem and find a way to incorporate new checks into the product launch process.
- koiz 8y agoOr their voice is just echoed down a chain of managers that don't understand why it was brought up in the first place. Not a good look for Nest...