Amazon device recorded private conversation, sent it out to random contact
kiro7.com
kiro7.com
* install device that is designed to listen to speech in the house
* the device is connected to internet
* the device is capable of contacting other internet peers/services/hosts
* the device knows a bit about its owner's internet presence such as contacts
* the device is equipped with simple conversational user interface based on fuzzy human speech-command detection
These basically bound the failure modes of the complete system. I am not surprised that a glitch like that happened. I can certainly attest to how shocking it might be to discover first hand that it really did happen, but given the context I can't say it's hard to not foresee something like this.
whats the analogous behaviour for alexa?
also remember these are shared devices in a home, not a personal device in your hand. could i shout into somebody's window, "hey alexa send my browsing history to bob@hotmail.com"!
https://www.safety.com/wp-content/uploads/2017/06/mute-butto...
While you may have never pocket dialled, plenty of people have. I've received more than a few accidental calls in the past.
I equate this to some phone users placing their devices hanging over the edge of tables - as if they don't care about them hitting the floor. Should phone makers toughen their phones and should Amazon improve Alexa anyway? Sure.
The main reason I won't have any of those products in my house is because of that. I'd much rather have a confirmation of some kind before the system takes action.
"...random talking..."
Assistant "I am recording"
Me: "Stop recording"
thats not foolproof but much better than what we have now, and i think we are pretty close
Phonetics is hard. Especially with ambient noise, echo and such. I had a conversation with one of the speech engineers when I worked at a speech recognition company and the level of detailed problems to solve was impressive. Totally made sense after talking about it, but things I would not have thought about before.
I'd imagine the next thing to come in this area that would really make an improvement is an "on person" microphone. Maybe it's a pen in your pocket, or some kind of vibration detection (that could pick up the wearers voice), that would then allow some improvemnts in the domain of "who is talking" and how well the voice is processed.
An alternative, "wireless" approach to near-perfect security would be to invent-plement some kind of vocal, human-executable GPG/TLS.
It doesn't even need to get good audio - just enough to give a bit of an indication that what the device picked up was me talking and not random noise and ideally some way to somewhat correlate it to the audio the device picked up to give it an indication it was me it heard. It'd also give you the option of setting the devices to require confirmation for certain types of orders if they were not confirmed by an authorised device, or if they were not confirmed by a device (so you could let people present give instructions but not some random joker on voice chat in your online game for example).
If we could get support for that into e.g. a watch, it'd be very much useful.
Both of these technologies work in nightclubs and fighter jets. I assume they are very high SNR, as far as ambient noise is concerned. The subvocal one might just be a phonetic/intonation input, which then requires voice synthesis if actual voice is the goal.
I believe any implementation of security through acoustic biometrics would be vulnerable to replay attacks.
Systems to reproduce acoustics with high fidelity are commonplace - You might be using the output component of such a system right now if you're listening to music.
You could make the Assistant remember the exact fingerprints of all previous activation phrases and only trust you if it was original. This could be circumvented if you spoke the activation phrase at any point where your assistant could not hear you, for example to another Assistant of the same brand.
Audio is definitely too easy to spoof for it to be a security method IMO.
it may have a place in security as well but i can only see it as part of a much more holistic model
This is exactly how the Google Home works right now.
It might be a bit awkward at first to do that in front of strangers, but once it catches on, that will wear off. ;-)
Entering the pattern after it's locked is pretty much impossible though.
Also, the case adds to the pressure needed to depress the button anyway.
But it'd certainly be good with more feedback.
This sort of thing makes me nostalgic for the old days of explicit "Save" commands in every application.
And once you have Undo, it's nice if you always have Redo, in case you Undo once too many.
b) There is a great deal less ambiguity around "pressing buttons" than there is around interpreting speech. While it is unlikely that your phone will incorrectly detect button presses, it's very common for voice-activated devices to a) incorrectly detect a wake word (either negative or positively); and b) misunderstand some particular word used in the command. Your phone is not going to think you pressed the "Clothes" button when you actually pressed "Close".
c) The entire functionality of the device is accessible from behind that big ambiguous interface. On a phone, there are many distinct steps and screens to step through when you want to do something (this complex interface, by the way, is a non-trivial part of why butt-dials are quite rare these days). On a "smart speaker", most things are just one misheard statement/command away from occurring.
Does having the device programmed to make mistakes make it more comfortable to use, because we know humans are infallible too.
I can, however, say "Hey Siri, call 867-5309." Or "Hey Siri, Facebook status: my anus is bleeding. SEND!"
Because we are apparently incapable of applying past lessons to new technologies.
And if their management is anything like my management, they go ahead and release it anyway.
My point is they're really half-assed products right now that are behaving badly/immaturely.
The only problem here is that Google still doesn't recognise my voice half the time, perhaps because I'm never sure about how I should speak to an inanimate object.
Speaking of unlocking methods, face unlock appears to no longer be available as an option for me. I can't find it in settings anymore (smart unlock etc).
Serves me right for having screen reading on near my phone.....
(jk, jk, but seriously though)
You'd think that there'd be protection. Maybe a restricted set of contacts who could get such messages. And a confirmation step, such as "Do you want to send this recording to 'my mother'?" Or "... to '911'?"
Edit: Damn, didn't see Clubber's comment.
"NEW TEXT MESSAGE TO JENNY! FUCK YOU! SEND!"
Fortunately the phone was too slow to take it all (even if it had Jenny would have found it amusing, she was a cube or two away). But yeah first thing I thought of was that if it's listening how easy is it for it to mistake intent or someone else or etc.
Humans talk funny, computers don't get it, they're gonna mistake commands all the time.
As it is I hate how I can't talk ABOUT "ok google" around my phone... because it always goes off.
https://www.youtube.com/watch?v=FJ5DA22tBOY#t=4m27s
“8… 7… 6… 5… 4… 3… 2… 1…
…
Hmm, nothing happened, maybe my count w… [BOOM]”
Then she'd ask me for help and rather than have to wait for her to find what button I was talking about I'd just tap the screen a few times and we were off and running again!
I'd been using Linux as my primary OS for years at that point, so I think I'm pretty critical of Microsoft in general, however they did a good job building a touchscreen interface.
The state of touchscreen support in Linux was pretty bad the last time I checked though.
Anecdotal — but have had no trouble for the last two years with my dell xps. Other issues with said laptop (keyboard), but touchscreen support in linux isn't one of them.
My Surface Pro 1 is the only computer I have with a touchscreen right now, and it has enough other driver issues (the wifi and the Wacom drivers suck) that I probably won't be trying again on that.
And in effect, that's what I've used for many years. I have a relatively large touchpad. And when I need resolution, a graphics tablet.
The Surface Studio is cool, but I'd want something that resisted coffee and food splatters ;) As the original Surface did.[0] It could also scan text :) Which is something that I, when I was first learning about PCs, naively expected.
0) https://www.windowscentral.com/microsoft-surface-pixelsense-...
On several tech podcasts I listen to (http://atp.fm, https://daringfireball.net/thetalkshow/) they use fillers like "Yo, dingus!" to talk about alexa/hey siri/ok google
Like, are you referring to a sculpture made of cocaine in the image of a poodle, or are you talking about a poodle train in the ways of a St. Bernard rescue dog, capable of relaying quantities of said substance, or perhaps something else entirely?
https://youtu.be/ogUJ7JwkLNs?t=3m7s
https://en.wikipedia.org/wiki/TVC_15
>The track was inspired by an episode in which Iggy Pop, during a drug-fueled period at Bowie’s LA home, hallucinated and believed the television set was swallowing his girlfriend. Bowie developed a story of a holographic television, TVC 15. In the song, the narrator's girlfriend crawls into the television and afterwards, the narrator desires to crawl in himself to find her.
though i can easily see with background noise, next song sounding like exxon. I think due to frustrations with siri, i talk to google in very clearly enunciated words and havent had any interesting failures yet.
The 3gs had perfectly functional "play my xyz playlist", "next song," "play songs by artist" functionality, and to this day I don't understand why it took so long for Google to implement it, and why the implementation is so shitty.
Music interaction is a great example of the trade off.
And voice control didn't fail way back then because it wasn't good, it failed because it was a terrible input mechanism and that is why it will fail again.
The "failure" the first time around was that people wanted it to be the main interface, instead of accepting that where it works is as an ubiquitous auxiliary interface that's available everywhere in the house, rather than trying to compete with a keyboard when you're right in front of said keyboard.
Voice competes by working at a distance, even when your hands are not free.
It will never replace a keyboard, as there are so many instances where speaking commands is impractical, but it doesn't need to replace a keyboard to be useful.
And really, why not make it a 55 gallon drum of personal lubricant instead?
"WHERE TO BUY COCAINE, SAN FRANCISCO"
or
"HOW TO JOIN ISIS"
or
"PLUTONIUM FOR SALE NEAR ME"
The commands are usually recognized but turn up nonsensical results.
But if things like this _actually_ trigger any sort of response, then the effed up thing isn't the (childish) prank, it's the system actually acting on nonsense.
If I call the police and claim that you're armed and hold hostages, then that's irresponsible. If I shout bullshit instead and these novelty devices turn that into a web search, there's no way in hell that should have any consequences whatsoever.
Also, Google saves all voice commands. If the NSA wants to check they'd just hear all of us doofuses giggling and trying to one up each other.
He had to call the guy he tried to text to in order to apologize.
Our manager was a bit concerned about if the microphones would get stolen as he looked out over the rows of computers with the microphones on top of each monitor.
I yelled "Computer, Shut down. Yes."
A good chunk of the computers had indeed shut down.
We decided to go back and remove all of the microphones from the computers. Theft was not as a large of a concern as a bored college student with a prankster attitude during finals and the riot that would have ensued.
$ uvcdynctrl -s 'LED1 Mode' <0..3>
0 is off, 1 is on, 2 makes it flash (and you can even set the flash rate), and 3 is auto.0, 1 and 2 apply regardless of whether an application has an active video stream coming out of the camera.
Shh. (Hi NSA)
It worked several times and I found it really fucking hilarious. They did, too and now they guard their Alexas and use headphones.
Asking someone to silence their phone might just be an attempt to get them to unlock their phone before issuing the offending command.
but sure, I agree. That's why I questioned it.
https://www.theverge.com/2017/4/12/15259400/burger-king-goog...
Let this lady's reaction be a lesson to all of those who say "people don't care about privacy." She wired her home with Alexa devices, and yet when she found out how her privacy could practically be invaded through such devices, she seems like couldn't get rid of them fast enough.
People care deeply about their privacy. They just don't understand the true implications of even a device that's supposed to "listen to you" and the possibilities of what someone else could do to their internet-connected devices.
This is why governments must intervene with laws such as GDPR or even much stronger ones in the future to protect people's privacy, because the companies themselves have no incentive to "self-regulate" other than a negligible amount.
The only problem is some governments will not intervene unless enough people go through similar situations such as this lady. In the US even that may not help much because the vast majority of politicians care most about continuing to receive (however modest) donations (also called bribe money elsewhere) from the industry.
Market failure does not imply government solution. You're going to need a much stronger argument than "companies aren't doing a good enough job."
Amazon invaded her privacy, she realized it, and now she doesn't use the product. If you want others to do the same, start raising awareness yourself instead of enacting nanny state laws with other people's money.
Case and point - 2008 Market Crash, everyone agrees the dishonest practices that led to the crash should have been made absolutely illegal (in the cases where they already weren't)
In this case, we have MANY significant and potentially extraordinarily damaging failures in the markets to effectively protect people's privacy occurring fairly regularly. GDPR is not the ideal solution my any metric, but that's a failure of government to create effective legislation - not a lack of need for effective rules.
No, they don't. Do you really think if, before she made this purchase, someone explained to her all the things that could theoratically go wrong with this device, she would have chosen not to buy it?
She only cares now and acts like she doesn't share quite a bit of the blame because it actually affected her. I think it is highly likely she'll just switch to an Apple or Google equivalent instead of noticing the larger problem with these devices.
"Amazon/Google/Apple/Facebook/X have very smart people who will not allow this to happen."
"I have nothing to hide."
"People who want to listen to our boring conversations are losers. Let them waste their time doing so."
And the list goes on. I'm not making any of this up.
And then when it (occasionally) happens to them, there is a whole lot of dramatic outrage and someone else must be blamed. (Although in this case, I agree someone else is to blame - but I've seen this play out when people explicitly agree in the contract to consequences, and are warned quite clearly by a human about the implications of the contract).
Response: "Cool. What's your e-mail password?"
I think this would only indicate that she might care, but thought theoretical worst case scenarios are not sufficient evidence for an actual, non-negligible risk to her privacy. If they had told her that exactly this would definitely happen, I think she would not have bought the device.
I think one problem of explaining privacy issues to non-techies is justifying why theoretical problems often pose a real threat without sounding (to them) like a conspiracy theory nutcase.
Yes. Do you think if everyone knew what was going to happen with the Facebook scandal before it happened they would have signed up for Facebook? That's why it's called a "scandal."
Yes.
I also noticed how they haven't left once the scandal came to light.
You and I must read different news sources.
From what I've read, Facebook is down over a billion visits in the last quarter.
I've visited less in the last month, but because they've changed the algo on my feed and it's not as interesting ... though that could be a network effect, but I'm getting quite different stuff.
The loss of privacy spreading throughout civilization is recent and rapid. It's not surprising that somebody might think about it differently after they've experienced it. We haven't had time to come to terms with what out technology can do.
Amazon might as well record everything that you say and send it to the NSA.
They are just unlikely, not impossible.
Somehow it hasn't broken her (my wife) of the habit yet.
We must not forget another critical component of all this: these always-on listening devices run on proprietary (nonfree, user-subjugating) software. Therefore the user has no permission to: inspect what it does, modify it to do only what the user wants (or, since most computer users aren't programmers, get someone technical they trust to perform such modifications for them), run the modified software in their device, and distribute copies of the improved software to help their community.
If these devices ran on free software (software that respected the user's freedom to run, inspect, modify, and share) the more technical among us could help them. But as it is even the most technically-minded willing person cannot legally do this work to help them.
As Eben Moglen reminded us after the Snowden revelations came out: It's critical that we don't fall into the trap of saying something akin to 'those kids take too many darn pictures' like concluding that we just can't have these devices or their services at all. We can have all of their alleged conveniences but only if we have free software implementations.
What are you giving your mom? A Mac running OSX or a PC running Linux?
I gave my 60 year old mother my old PC running Debian with dwm as its WM.
She likes it.
> The idea that if these devices ran free software they would be more humane than the proprietary software they currently run is ridiculous.
Is it though? I am pretty sure that Amazon already gathers free data from its users, such a thing would not exist in a free as in freedom device.
To be fair, the community came down on Ubuntu like a ton of bricks for the whole... Amazon search thing.
* devices can operate without user's knowledge
These types of devices are easy to accidentally trigger; it must be vastly obvious when that happens.
Your vulnerability isn't a targeted attack: you are not valuable enough to be worth the effort to figure out your system. As an attacker on your system I'd have to figure out how to break in, and then how to use the hardware you have. You are more valuable as part of a botnet - attacks that already exist. (if you are a politician then maybe, but that person is also vulnerable to a targeted attack on their amazon system - probably more so because the target is easier to figure out).
That is they will target everybody because they know in a few years that will include somebody who they currently think is a nobody.
Of course as AI gets better and cheaper they may eventually listen to everything to see what who can be targeted automatically for what.
Just working for a company that an agency is surveilling is enough to make you worth targeting.
As a random example: let's say that I want to kill someone who lives in your neighborhood. I could analyze your conversations, comings and goings to figure out when and how to kill that person, and blame it on you. I could on a continual basis run numbers on everyone emitting data in your neighborhood, until someone had arrived at a point where their friends would testify against them on the basis of conversations with the potential patsy, that patsy had no alibi, and tailor the murder on the basis of the means that the patsy had available to them at the time.
I could also just be trying to figure out if you were a homosexual, or muslim.
> They should feel more comfortable than an equivalent system built by a company that is looking to profit off of your data - and additionally, you can give the guest stronger guarantees that when you say that the system is "off", it actually is.
They won't, because they'll be concerned the person that implemented it is a creeper. When regular people think "cameras installed in the room," they think this: https://www.bustle.com/p/airbnb-host-was-caught-with-a-hidde...
Distrust of a person is more more immediate in visceral. Distrust of a company is more distant and esoteric. The former usually trumps the latter.
There are many methods for occupancy tracking without cameras. IR sensors, antennas in the walls, NFC (bleh), proximity sensors.
Less likely to be seen as creepy and such systems already exist.
If you just need 'is a person in this room' or 'how many people are in this room' levels of data, solutions to this problem have existed for decades. No need to over complicate a solved problem.
I'm pretty sure all current technology only works with the have a wifi decide on your person. It is significantly easier to do this and for the most part good enough.
Not only can you detect motion and objects through physical mass using WiFi spectrum with a properly equipped device, you can detect if someone is breathing.
“What's more, this "Time Reversal Machine" technology is essentially just some clever algorithmic work with little burden on the processor, so it can potentially be added to any existing WiFi mesh routers via a firmware update. In other words, security system vendors should take note.”
The following processing is outside the scope of the GDPR:
- any activity outside the scope of EU law (e.g., activities of a Member State in relation to national criminal law);
- any activity performed by Member States when carrying out activities in relation to the common foreign and security policy of the EU;
- any activity performed by a natural person in the course of a purely personal or household activity;
- any processing by the EU itself;
and
- any activities performed by national authorities for the purposes of prevention, investigation, detection or prosecution of criminal offences, or performance of judicial functions.
I’d recommend something like this in every room, or even IR sensors, over cameras. You don’t want to capture video of your children jerking off.
You could just use an infrared motion sensor. They are dirt cheap and widely used for controlling lights.
The AC unit at work has one, too.
So, all of this already exists. Without spying capabilities, that is.
A lot of home automation stuff seems like something that would be fun to make, but not something I really want to have. I mean, the AC might be a good energy saver (a smarter thermostat) but that's not something I want, more like something that I would buy if it was cheap and practical enough.
To some extent, this is a phenomenon of early technology. It feels full of potential, so you want to play with it but it doesn't really do anything you really need yet. The early web was ki d of like that. We made sites because we wanted to make sites, moreso than because we wanted to have them.
Home automation though... Im kind of skeptical that this goes anywhere useful. The useful examples people think of (eg remote close all the windows and lock the doors) are more about mechanisation than automation.
Alas, remote controlling those blinds would be a major hassle since AFAIK I would have to install 6 wifi-enabled devices and tear holes everywhere (not even sure there is a powerline near) - and likely do all the programming myself. Thanks but no thanks.
I've been working on a custom UI that sits on top of the Wink Hub API to unify everything, but I'be been stuck with their almost completely undocumented Pubnub event API.
Open source, gets you most of the way there.
I think "find" and similar tools are now much more advanced so it might work better out of the box now.
And ideally? All of it integrated. It actually sounds nice to say "I'm going home", and have Maps say "today that will take 35, should your oven start preheating when you're 20 minutes out?" IoT devices are overrated, but I can absolutely imagine a critical mass of integrated tools being very useful.
But I'm not even slightly willing to do that. It's too much information and too much risk surface. I'd pay a hefty premium to get local-data-only versions of these products, but no one is offering that, and it doesn't look like they're going to start.
Not yet preheating the oven though :)
Waze also knows where I'm going in advance and most of the time it gets it right, like every Thu evening "are you heading to [evening school] ?". My weekly schedule is exactly the same 99% of the time but sometimes it still makes obvious mistakes. If you need an AI for that it must be a very simple one, yet it still fails.
Google maps also auto saves my parking location most of the time but other times it doesn't, for reasons unknown. Things like that make it hard for me to have faith in future versions of this stuff.
That sounds awesome until the company providing that service starts abusing their knowledge of their location. That abuse doesn't even have to necessarily be malicious in nature either. For example, Google Maps on Android started asking me to rate, review, and/or take photos of my present location if they deemed it a point of interest (certain restaurants, parks, etc). I never opted in to this feature and the only way to disable it that I've figured out is to literally disable all location services on the phone.
I really dislike the idea of Google storing a timestamped record of almost every place I've ever visited. Tt has to beconstantly phoning home in order to deliver the request to document my visit within a minute or two of my arrival and that constant reminder that Big Brother Google is tracking me at every moment is just disturbing on so many levels. Even if they aren't using that data right now, remember the "data is never destroyed" principle of the internet.
On a side note, I would have ditched Android if I didn't need it for work simply because use of the GPS radio is hidden behind the acceptance of enabling Google's Location system and all the invasions of privacy that entails.
An encrypted hard disk with the key on a USB stick would be enough, just keep the key somewhere separate and you'll only have to plug it in when there's a power outage.
The main fight needs to happen at application level, not infrastructure. Cloud services are already mostly transparent and interchangeable. But applications aren't. The problem is, it's the application vendor that owns the code, determines where's going to run, and asks you to send over the data. How it should be working, is that you own the data and determine location of computing, and own or rent code to be run on that data.
You don't need cameras for that, just motion sensors.
> That server makes decisions on if lights should be on...in that room.
You don't need a server for that, just a motion-sensing switch. They can be totally offline. My office has them to shut off lights automatically when a conference room becomes unoccupied.
https://www.homedepot.com/b/Electrical-Wiring-Devices-Light-...
It can get annoying if you're not moving much, but the key point is: no camera or server required.
> That server makes decisions on...if A/C should be running in that room.
Ecobee thermostats can already do that using motion/temperature sensors. They run fine without an internet connection.
Thank goodness for phone flashlights!
A new dystopian developer-productivity metric.
Edit: typo
By the way, German workplace safety regulations require a certain minimum of light at a workplace.
[0] https://en.wikipedia.org/wiki/Passive_infrared_sensor [1] https://en.wikipedia.org/wiki/Forward_looking_infrared
Maybe, but that seems like a lot of work for little gain.
You probably don't actually have that much control over the AC in your rooms unless you have zoned heating and a lot of zones, regardless of how smart your sensors are.
Intent is a very important factor when answering the question "should the lights be on," I don't think you'll be able to predict that. For instance: if movement is detected in the bedroom at 2AM, should the lights come on? The answer is: a very strong maybe.
You would be collecting data from many sources in order to predict intent. This is why you need a centralized server.
Please explain, exactly, what other sources you would collect data from and how the central server would process it to determine if I want the lights on in the middle of the night.
IMHO, determining intent in this scenario is impossible without...
1. a mind-reading sensor, or...
2. an explicit user signal, such as a button-press or command.
The only realistic option is a user signal, and most of those options obviate a lot of these prediction ideas.
I think there's a lot less practical value to having a "central server" controlling everything than you seem to assume.
The more data, the more smarter. In fact, the only difference between a thermostat and the human mind is the number of datas. This is because the Law of Averages predicts that half of all datas will be relevant.
There are several important caveats to this statement.
> In fact, the only difference between a thermostat and the human mind is the number of datas.
This is an oversimplification that borders on dogma.
> This is because the Law of Averages predicts that half of all datas will be relevant.
An interesting interpretation and application.
Machine learning navel-gazing is the new "throw a start-up at it", so I'm guessing the answer to this is going to be "if we have enough data..."
That's how I feel about Alexa.
As someone who doesn't have a voice for radio, I much prefer being able to interact through dexterity. Besides, I'm very picky when it comes to which specific track of music is to be played (out of various similarly named pieces of music).
* I don't think take-up is quite as big as the tech world currently makes it out to be. People in my circles don't really have that kind of disposable income and are prioritising other purchases first.
So yeah, Alexa is a lot of extra literal work for little gain.
My main point was the original poster's idea was probably focusing on the wrong kind of sensor for what he wanted to do. He could still network a bunch of motion sensors.
Also, I'd dispute the idea that my proposals were less "modifiable." If only because they're far easier to implement and a couple of orders of magnitude cheaper, so it's practical to replace if more capabilities are needed.
I don't think the number of people in a room will give you meaningful information to tell you "how much to crank up the HVAC." Also, the HVAC systems in most homes aren't capable of even cranking up the HVAC in a particular room.
This is what the "Internet of Things" should be doing, but seldom does.
> The second advisor, a software developer, immediately recognized the danger of such short-sighted thinking. [...] "A toaster that only makes toast will soon be obsolete. If we don't look to the future, we will have to completely redesign the toaster in just a few years."
hackaday.com/blog/ will have some details on how people set up computer home controllers as well as working with OpenCV
A cookie is a device "that is inserted under the clients head by the brain and kept there for a week, giving it time to accurately replicate the individuals consciousness. It is then removed and installed in a larger, egg shaped device which can be connected to a computer or tablet (to automate their smart house controls as if the house was knew their personal preferences moving from room to room.)"
Low tech alternative solution from my friends? Get LEDs. Never turn off the lights. This way the room you are going to will always be lit.
Why would you even want such a system?
My flat uses the Button-Framework which provides a really convenient UI/UX. The edge between 2 nodes (rooms) has a button (a haptic device to switch between boolean states) at around hand-height that you can press to switch the light on or off. It works quite well (it uses a switch-system technically) and the user decides by her/himself if the light should be on or off and just presses the button after careful reasoning.
Granted, it doesn't use Docker, but it really works well and needs low-maintainance. My model is running since 23 years and I never had any issues - it's even open source.
> Echo woke up due to a word in background conversation sounding like "Alexa." Then, the subsequent conversation was heard as a "send message" request. At which point, Alexa said out loud "To whom?" At which point, the background conversation was interpreted as a name in the customers contact list. Alexa then asked out loud, "[contact name], right?" Alexa then interpreted background conversation as "right." As unlikely as this string of events is, we are evaluating options to make this case even less likely.
https://arstechnica.com/gadgets/2018/05/amazon-confirms-that...
If you have an echo and it kicks on unexpectedly, you can go to the app to see what it thought you said, along with a recording of you saying it.
I've had "alright, uhh..." trigger it. and on the grainy bad across the room recording, I could see how the computer thought it was "Alexa". So I could see how if the computer is purposefully listening for "right" or "yes" that it could mistake any number of other words for that.
I would much prefer an open source + open hardware alternative that works reliably, but I received an Echo dot as a gift, so after a few months of debating, I plugged it in.
Having an always listening internet connected device that has access to your contact list is a pretty big stretch. But somehow we go along with that just fine.
As an example, I've noticed that Siri tends to default to offering to open Notes on my iPhone any time it fails to recognize a query correctly. Alexa on the FireTV is better but still has lots of failure modes which look suspiciously like the default branch of a switch statement where it ends up really off on a common query in a quiet room.
When the episode was aired there were numerous reports of the show triggering Alexas and Google Homes of the viewers.
I would assume any failed speech recognition attpempts are recorded so Amazon can have a human look at and classify them, but at the very least they probably keep logs, so they should have this information when debugging. Maybe we'll get a more detailed postmortem later.
Would be very interesting to see the actual probabilities assigned to these "unlikelys"
I keep my Alexa's volume at 2-3, because otherwise the music / podcasts are too loud for me. However at volume 2-3 the Alexa system voice is fairly quiet and I often miss things Alexa says- requested or accidental. I'd prefer to keep Alexa system voice at volume 5, but music at 2-3.
I requested this feature of a distinct Alexa voice volume years ago. I would be interested if anyone has a solution for this.
"Amazon sent me a message" is so frustratingly vague...
i would assume that the profile for even a free amazon account would require a phone number.
Now that Alexa is available in my country, I've considered switching it over to a real account explicitly to be able to use some of these calling and messaging features. Maybe I'll wait till the bugs are worked out.
> an Alexa engineer investigated ... they said 'our engineers went through your logs, and they saw exactly what you told us, they saw exactly what you said happened, and we're sorry.' He apologized like 15 times in a matter of 30 minutes and he said we really appreciate you bringing this to our attention, this is something we need to fix!"
> the engineer did not provide specifics about why it happened, or if it's a widespread issue.
> "He told us that the device just guessed what we were saying" The device did not audibly advise that it was preparing to send the recording, something it’s programmed to do.
Apparently it's not programmed to do that. Unless this was a hardware glitch or cosmic-ray event.
Bugs happen in architecture, aircraft, etc. too. the difference is that the actual engineers are paid to have a precautionary approach and spend significant resources to actively prevent bugs from making it into the final product.
In contrast, software is often written to "ship first", be "agile", and "move fast and break things". Yet when it causes problems, they just say "bugs happen", and "it is unfair to vilify them".
Features are not better than reliable security.
And yes, negligence is less bad than malice, but it is still damaging and developers and managers need to be held to account.
If your manager is pressing you to do unsafe crap in too big a hurry, it's your responsibility to push back, and if unsuccessful, leave for saner pastures and make it more difficult for that management to proceed.
Well, yes and no. Bugs, security, reliability, etc are all important things to consider, but they can't be the only focus. Security doesn't matter if the thing you are creating has no features; it would be the same as if it didn't exist at all.
Instead, we must manage risk; the risk of bugs, the risk of security vulnerabilities, etc. Nothing we do is risk free. Even walking across the bathroom floor has SOME risk; we might slip and fall. Does that mean we should just stay in bed all day to avoid any risk?
No, we measure risk by factoring the chance of the bad thing happening and the consequence of the bad thing happening. We then determine how much effort we should spend on that risk, since there are infinite risks and only a finite amount of effort we can expend.
If the consequence of a risk is death, then we should absolutely put a lot of effort into minimizing that risk. If the consequence of a risk is that a private conversation is sent to a contact, we should definitely put a lot of effort into minimizing that risk, but probably not quite as much as you would into something that has the consequence of death.
Even when the risk is death, however, we don't put infinite effort into avoiding it. We choose to cross the street, even when we know there is a risk of death when we do it. We drive cars that have chances of mechanical failures that could cause our death, but we don't bring the car to the shop every day to check for failures.
Things are not so black and white as to say "security is always the most important thing"
You do not need to lecture me about risk. I've had a career in international downhill ski racing, have won auto racing championships, and enjoyed lots of technical rock climbing, all of which require a high degree of risk assessment, both in extended preparation phases and at split-second time scales. I've also run risk analysis for UAV flight systems
I understand well the difference between smart-crazy and dumb-crazy, and where the pseudo-mathematical risk models like yours break down.
Your 'analysis' to "...measure risk by factoring the chance..." would have fit right in at the meetings where Ford decided to just go ahead with the design of the Pinto/Bobcat because the lawsuits would cost less than the fix -- they wound up killing dozens of people.
Your 'analysis' would have fit right in where the trading algorithms were being designed, which worked fantastically profitably, until they didn't and ended up crashing the global economy in 2007-8.
You cannot simply multiply the cost of the consequences by the expected probability and get an allocation of resources. That is what you do to see if the lottery jackpot is big enough for you to want to buy a $2 ticket this week.
You must instead 1) fully examine the system for potential critical failure points/modes and then 2) allocate WHATEVER resources are necessary to account for preventing those critical failures, then implement those remedies along with the features.
These preventative measures may involve installing redundant systems around the critical points, redesigning the points so they fail in a safe mode (e.g., fail to send the data vs sending it off, shut down vs, explode, etc.), adding check procedures around the potential critical failure, etc.
Note that NONE of these measures involve not implementing the feature. They involve 1) checking for critical failure modes, 2) allocating R&D to develop preventative & fail-safe measures, 3) implementing the measures, 4) testing, and 5) field monitoring.
This is what you do if you are serious about risk.
I was simply pointing out that we can never get to zero risk, and since we can't, we have to weigh risks based on consequences and probability.
> 1) fully examine the system for potential critical failure points/modes
Sure, to the best of your ability. How can you know for certain you have found all potential critical failure points? You can get pretty sure, but never fully sure. We still have industrial accidents, in every single industry in the world.
You also have to define what a 'critical risk' is. I don't think it is an a priori fact that accidentally sending a recording of a conversation to a contact is a 'critical risk'.
It absolutely does NOT work for serious risks, e.g., of death, serious injury, massive privacy violation, and other potential life-changing events.
The concept you are clearly avoiding or missing non-linear risk.
You (and amzn_engineer1) are advocating for simply subsuming risk assessment into the ordinary development cycle, and calling it "taking it seriously".
That is fooling yourself.
Taking it seriously is actually making full and serious effort OUT OF THE NORMAL DEVELOPMENT CYCLE for no other purpose than to SEEK and identify potential critical risks.
It is then engineering a variety of in-depth solutions to prevent those critical failure points from ever seeing the light of day. And implementing them. and testing them. And monitoring them.
>> I don't think it is an a priori fact that accidentally sending a recording of a conversation to a contact is a 'critical risk'.
This is an exact example of this sort of failure: 'it's not a priori bad'..., minimize it and streamline it into dev.
I really want to know in what world any sane person would say that it's OK to randomly divulging an intimate conversation to a contact or random recipient -- seriously, who would say that?
I mean sure, most conversations are benign, but some could be utterly life-changing if revealed. and that's OK with you?
But note the blameless analysis is NOT the same as saying "meh" errors happen.
It is a culture and deliberate practice of allocating resources to seeking and classifying risks, and designing, implementing, and testing engineering and procedural mitigation strategies (vs. development as usual).
Interesting paper: https://media.blackhat.com/bh-us-11/Dinaburg/BH_US_11_Dinabu...
The macrofailure, though, is that you have a device just guessing at what you want and doing it. That can't be fixed without going back to manually constructed (or at least manually triggered) notifications. Which for "send a note" might be an obvious fix, sure, but there is a lot of gray area in what constitutes "privacy" and Alexa would be pretty useless if you had to affirmatively OK everything it did.
Not sure how to fix that, if you use the aux out it has no way of knowing what happens on the other end; a confirmation prompt that isn't heard could still pick up an errant "Ok" response. Perhaps require a PIN like the shopping confirmation that would make it much much more unlikely? Or better yet, disable messaging as an option.
Based on Amazon's admission and apologies, I'd think they'd be willing to give a lot more than just a refund. Seems like a huge liability for them.
In terms of the big picture, this was dumb PR wise and this story should have never happened. For less than a $1000, Amazon could have stopped the story if the PR dept were more in sync with customer service
Not saying it happened here but thats how you get $10/hour vendors making judgement calls on customer situations that are front page news.
My point still stands. This is Amazon and not random company X's customer service. There are very few companies like this that people can name (e.g. Nordstrom, Patagonia, ...) It this used to not happen at Amazon. Customer service used to be empowered to make customers happy, which was what made Amazon legendary. Things have changed. Customer service is now crippled like almost every other mediocre company. This is just one of the symptoms. Maybe Amazon feels that it has enough market share now, so it doesn't matter as much?
I guess I just don’t have a long enough track record with them to see them in that grouping of great customer service. They’ve pretty much fought me tooth and nail over price matching and prime shipping that doesnt meet the two guarantee over the last couple of years which is probably biasing my view.
I have a microphone and I've been intending to get one of the open source solutions working and just tie it in to mpd, weather and a few other things. But all the processing should really be done on your own device, by hardware you own, software that's open and that you configure, and not send up to someone else's computer (aka "the cloud").
Of course non-tech people probably wouldn't bother because that's a steep curve and you're talking about more expensive devices to do on-board processing. There are some companies that are trying to make this more accessible to regular consumers. I hope we see a move in this direction.
Jarvis https://github.com/alexylem/jarvis
Jasper https://jasperproject.github.io
there are others if you look around
Do you have an Apple or Google device near you right now? Does it have a microphone, battery power, and a connection to the internet? What about your roommate? Do you ever have sensitive conversations near these devices?
Of course I'm not suggesting you should abandon such technology. I'm just wondering why you draw the line at "Alex/Google/Apple assistant device"
I carry a smartphone, but I keep voice-command activation turned off. I'm sure it could be activated remotely, but I expect that would require a targeted effort. I assume that Google isn't constantly recording everything in the vicinity of all Android phones - the news would probably get out, and honestly I'd see the battery impact pretty quickly.
As the saying goes, "Quantity has a quality all its own". My basic objection is to systems that are likely to store/upload all available data, with the attendant risks of leakage or commercialization I object to. Anything I say around my phone is potentially forfeit, but I don't think everything is.
It's much easier to turn off voice-command activation on the Echo than your smartphone. The Echo is not constantly recording.
> I assume that Google isn't constantly recording everything in the vicinity of all Android phones
AHAHAHAHAHAHA, see for example: https://www.google.com/maps/timeline The vast majority of Android users I've met unknowingly had this enabled. It doesn't record your conversations, but it still records far more than an Echo.
Why would remotely enabling recording on your Android phone be more difficult than on an Echo?
The difference is that a smartphone has the ability to constantly listen, but an Echo's primary use-case is to constantly listen. So if you're going to turn off voice-command activation on an Echo, there's much less reason to own an Echo in the first place than there is to own a smartphone with voice-command activation disabled.
Furthermore, an Echo is constantly plugged into essentially limitless power, while a phone is not. People in general are much more likely to notice excessive power consumption on their smartphone from the fact that their battery would drain more quickly than usual. Whereas, not many people are directly monitoring the power usage of their plugged-in Echo on a daily basis, so they'd be much less likely to notice if their Echo is suddenly using more power than usual (for example, by being remotely activated to listen constantly).
> AHAHAHAHAHAHA, see for example: https://www.google.com/maps/timeline The vast majority of Android users I've met unknowingly had this enabled. It doesn't record your conversations, but it still records far more than an Echo.
Granted, but there is no built-in voice command to send your timeline to one of your contacts.
> Why would remotely enabling recording on your Android phone be more difficult than on an Echo?
It's not that one is more difficult than the other, but rather that your risk grows with the number of possible attack vectors. If I already own a smartphone, then I may already be at risk, but adding an Echo to the mix increases my risk.
Two channels for remote listening will always be more risky than one. I don't think anyone is suggesting that you can replace your smartphone with an Echo, so the discussion about the risk of an Echo will always be within the context of _adding_ to the risk of having a smartphone. I don't think it's surprising when someone draws the line between the thing they currently rely on and the additional thing they can live without.
The most fundamental point is that a smartphone with voice-control disabled is still a useful tool, but an Echo with voice-control disabled is an LED rolling pin.
And beyond that, yes to the rest - I don't want to add an attack channel, I trust my knowledge of phones more than that of an always-on black box, and I object to voice control as a more open-ended threat than location tracking.
But as for "AHAHAHAHAHAHA, see for example: https://www.google.com/maps/timeline The vast majority of Android users I've met unknowingly had this enabled"?
I do have Timeline turned off. I know most people don't, but I'm not sure why "many people make this mistake" is supposed to be a rebuttal to "I'm more privacy conscious than many people".
I went on to the google page that lets you see a lot of data they have stored for you. I had read about it in a blog post or something, so being curious I went to check it out. I believe it is the "control your content" page in your settings. I don't want to login to google right now so I might be wrong.
It has stuff like web searches (if you have that enabled). During the year I had an android, it captured several conversations, and I only found out because they were on that data page.
None of them would have had the words "OK Google" or whatever triggers it. One of the conversations was definitely private... it with my doctor during a consult. Nothing that was recorded was actually sensitive, but the fact it happened, and I had no idea, was disturbing.
There’s a big difference between:
- Devices which are by design always actively listening and sending real-time audio to computers you can’t control or even really trust, with unknown security properties, and consumer-appliance security life-cycles/support
- Devices that can be configured to do that, but which you have some control over (phones, laptops, etc.) and generally won’t, without some form of consent (even if via a dark pattern, e.g. LinkedIn on Android).
Oh, what devices are these?
>Devices that can be configured to do that, but which you have some control over ... and generally won’t, without some form of consent
Ah, so you mean like "Alex/Google/Apple assistant devices"?
- Devices that have the ability to perform unsafe behaviors such as “record a conversation and share it to someone else”.
Is it possible to ask a HomePod to transmit an audio recording of a conversation?
Phones are expected to be on battery and metered internet. There are tricky ways to tap a phone without draining the battery or internet billing, but that very much limits what can be recorded and sent remote. The risk still exists, but is lower and the bar to entry is higher.
The reason this matters is well-illustrated by the linked story here--the potential consequences of bugs are more severe when the mic is always on.
The way I have Siri configured, the opportunity to make mistakes about what I mean is limited to when I am intending to speak directly to Siri. It's not that often, and I am aware of what I'm doing.
But if Alexa is going to make a mistake about a trigger word and start transmitting data... well, that potentially could happen whenever I'm in voice range.
Sure, if some three letter agency is targeting me, a smartphone is probably no safer than a home assistant. But I'm not concerned about that level of targeting, for myself.
you have one, right?
Phones in your pocket are expected to be on battery and metered internet. There are tricky ways to tap a phone without draining the battery or internet billing, but that very much limits what can be recorded and sent remote. The risk still exists, but is lower and the bar to entry is higher.
You would also need to leave if they have a smartphone of any kind...
Someone could activate my phone microphone remotely and record me but if I'm up against that level of adversary I'm probably in deep trouble.
Amazon takes customer privacy EXTREMELY seriously. There's no way a team would get the "ok" to build a skill that randomly records private conversations then sends them to a random contact. It also doesn't make any logical sense to build such a skill.
Yes, I might sound biased because I am an engineer at Amazon. This statement is my own and unrelated to Amazon's opinion.
If that's the case, then you need to provide additional features to reduce the chances of this happening. Longer and more unique wake word options, or more complex and deliberate confirmations before the call is placed. Something that a user can enable if they're worried about this sort of thing.
If there was an Alexa in my place of residence, I would rip it out of the wall, smash it to bits with a hammer, and fire it out of a cannon into the sun.
Hell no to this crap from my side. I hope there are more incidents like this until people wake up to the fact they are putting telescreens in their homes. You guys can't be trusted!
You may consider disposing of the bits at Kilauea instead of the sun. It would be almost the same and much more affordable.
What I mean by the above is that the "call" skill is much different than the "weather" skill. All Alexa has to do is have a confirmation prompt in the "call" skill and this wouldn't have happened. That is what extremely serious looks like. This is exactly the same as the phantom laughter incident from a few months ago. Alexa "heard" someone say 'Alexa laugh' and laughed, but that wasn't the user's intent. It was fixed by moving to 'Sure, I can laugh,' followed by laughter.
Voice UI is very hard and still in its infancy but ability for personal harm (physical or emotional) must be considered in these interfaces. Turning off the lights may not need confirmation but unlocking the doors or turning off the alarm probably should. Sending recordings or answering calls or even calling people should require more hoops or at least allow the user to control the risk/reward.
There is absolutely no reason to believe they are not conspiring with the NSA. They have a huge deal with the CIA, plausible some of these funds are for surveillance capabilities. They would not (and likely would be legally prohibited from) disclosing any relationship they have.
https://venturebeat.com/2014/03/18/snowden-slams-amazon-for-...
https://www.theatlantic.com/technology/archive/2014/07/the-d...
Or, more likely, being made an offer they can not refuse by the NSA. And the rank-in-file engineers may not even know it's happening, all it takes is inserting some diverting code into the pipeline and calling it "QA monitoring" or something. Couple of people in the whole org would know that somebody from some IP connects and downloads these "QA" data periodically, all the rest would be completely ignorant and indignant at the thought. Don't see anything preventing this from happening at Amazon - or anywhere else.
Apple shared personal photos of myself onto the internet without my permission. I could not delete it without getting support to assist, and they could not provide me with a reason why this happened.
Would you say that Apple does not take privacy seriously?
The issue from the article is systemic. Everyone could easily accidentally be recorded and share that with random people
This does not mean Amazon does not take privacy seriously. It is a company of small teams with very few layers of management between an engineer and business decision. The error in judgement of one team does not reflect on all of Amazon.
As you say, Voice UI is still in its infancy and not lacking growing pains. However, because Amazon does take privacy very seriously, after this incident, I'm certain there will be actions taken internally to ensure teams properly weigh the gravity of a skill with its voice trigger (or adjustments made if there is already an existing policy).
My own thoughts, not Amazon's.
The default must always be voice recording will be auto deleted after 1 minute if no response is heard. It should let user know about that too.
To send this message to John Smith, say 'artichoke'.
I don't think the article is indicating what you say. The report says it's a bug, but it does bother me why Amazon won't comment on the specifics. This should be patched immediately with a full retrospective explaining what happened.
And then builds exactly that...
It's a mistake, but it's a pretty bad one.
Bugs happen in architecture, aircraft, etc. too. the difference is that the actual engineers are paid to have a precautionary approach -- and spend significant resources -- to actively prevent bugs from making it into the final product.
Amazon and your team has built a great product (I have one and make moderate use of it, have even considered building some skills).
But, you have planted a full-on bugging device in millions of people's homes. Done by a government, this would be cause for war or revolution. This is serious, and you need to treat it much more seriously than you obviously are. Every 'skill' does not require the same minimal levels of security and verification, some, like this one, require much more, or should be forbidden outright until such security can be properly implemented (and yes, this should probably include calls only to pre-configured whitelists, intent confirmation, etc. and to any manager that says "that's too inconvenient to the user", the response is "screw you, it's critical").
You call yourself an "engineer" at least twice, and claim that you take privacy "extremely seriously". The evidence from this incident and others noted in this thread indicates otherwise. Clearly, insufficient resources were allocated to figuring out the potential failure modes of a "call skill", and preventing them.
All due respect, but your team needs more of an engineering approach than you have. This entire "it's gotta ship yesterday" mentality in the software industry used to be just inconvenient. Now it's getting dangerous. Please help stop it.
I'm all for doing away with the "it's gotta ship yesterday" mentality, what your thoughts are on how developers can help stop it?
This is not easy, especially as the CEO is still typically above the CTO, and can overrule. I had it happen to me, when we were ahead on a scalable version of the product, but they didn't like the timeline. The mgt decision cost almost a year of messed-up myopic development schedule just to roll out apparent features sooner, but ignored the likelihood and eventuality of bugs. Afterwards, when we got back to the scalable highly modular version, we started taking biz from competitors who couldn't scale. I'd say that my mistake was to only give the broader consequences, and not spend time to be able to enumerate in detail the consequences of non-scalable quick program would be. Of course you cannot predict exactly what bugs will happen, but I could probably have done a better job of drawing the scenarios (not sure it would have made a difference, but it might have).
I'd also say that we need to create specific structures and plans to study and quantify risks, as is done in real engineering like aerospace, architecture, etc. Classify those risks into a range of categories, from small bugs to existential for your customers or project.
Different steps need to be taken for each class, and significant part of the planning needs to go into de-risking the project.
I'm in physical vs software development now of carbon fiber type technologies, and I notice that my military customer who are building very cutting-edge stuff often talk of 'de-risking' the project, whereas I don't hear this much from other customers. Seems like an important distinction to take on board.
--- From a user perspective, I noticed after looking at the issue on our own Echo yesterday: the UI is a totally greased slide to hide choice for the user and slide them right into giving permissions for contact list. It seems that effort was made to hide the actual features and functions that will result from giving permission, and obscure the 'Skip' option. So it would be easy to not even notice that your device had these new possibilities. Obviously, I'd recommend taking more time to sell the features and let us make an informed choice. Then even if things go wrong, you'll enjoy some benefit of the doubt in the market and press.
(edit: add parenthetical)
Yes, I see this a lot too. I think software managers have more incentive to get new features deployed. I don't think this is a good way to measure their performance as a manager because of the consequences we've already mentioned.
I would also like to see more concepts from physical development implemented in software. At times feels like the wild west out here and too often we ignore the lessons from similar experiences.
Thank you for that input btw.
I know amazon's got a different motivation matrix than a startup; e.g., Amazon won't die if some feature isn't delivered by the next trade show, but they do have competition from the other majors.
That said, amazon certainly also has the funds available to invest in a parallel risk team. If they're not motivated to do it from the risk to their users, the best argument might be the potential reputation setbacks if stuff like this gets out there & causes problems, bad press, reputation for creepiness, etc.
I know it always seems inevitable that you'll weather the reputation hits from errors and just press on to greater usage/adoption/sales, but it will always seem that way from the inside -- until it doesn't. Google's experience with Glass comes to mind; could have been a fantastic product, but it went just under the tipping point of being creepy, and poof, they're gone. It'll be a generation before anything similar comes back.
I'd hate to see that happen to Echo/Alexa. TBH, it looks like this product has both greater potential, and also greater creepiness potential than Glass ever did.
How it happened is only relevant to the engineers who build and maintain the thing. I, on the other hand, could not care less how it happened, and the fact that it did happen is reason enough never to buy one of those infernal devices.
I'm sorry, this is just stupid. If you cannot see the distinction between a feature that was intended to spontaneously record audio, and a bug caused by faulty voice-processing, then that's on you. The distinction is pretty critical
Obviously, intentionally designing a feature that spontaneously records and transmits audio is a problem for many reasons. But the lack of intent does not magically erase the consequences for the people who experience this kind of bug.
And, to be clear, this was not simply a matter of "faulty voice-processing". The fact that this could happen without the user's knowledge is a problem in itself. Clearly, there are inadequate visual and audio cues, and insufficient or nonexistent verification. Those failures are not bugs; they are bad design and engineering.
If you took privacy seriously you would have added an audible prompt to ask for confirmation before sending or similar safeguard.
I mean if you are an engineer then you know that there is a nonzero false positive rate for the device to detect the "call" command.
Knowing this, and not implementing a trivial safeguard sure seems to me like the team was "ok" with building exactly that, a device that: "randomly records private conversations then sends them to a random contact."
> This statement is my own and unrelated to Amazon's opinion.
Just because you admit your bias doesn't dismiss you from it. Your statement and opinion could very well be influenced by your work surroundings at Amazon. While I do not doubt that Amazon does take security and privacy seriously, I find it hard to believe that they employ proper ethics (based on this and past examples such as the NYT incident).
Heh, skill.
Why? Because from a PR perspective, it doesn't matter what Amazon or the engineers intended, all that matters is what actually happened. You said:
> There's no way a team would get the "ok" to build a skill that randomly records private conversations then sends them to a random contact.
But that's exactly what happened. Whether it was a bug or a feature doesn't matter. Imagine if the wing fell off a plane and an airframe engineer came on here and said "hey, there's no way we would get the OK to design a wing that falls off in midair." Yeah, we know. The fact that it happened by accident doesn't make it better (maybe worse, actually).
Now you've got dozens of people responding to you, and BTW a lot of reporters read HN too. Do you really want to see stories like "Amazon Engineer Calls Customers Conspiracy Theorists"?
Of course. But it is entirely plausible that somebody builds a skill that records certain conversations, and somebody builds a skill that sends recording somewhere, and then due to some bugs or coincidences or missing controls to prevent such occurrence, the first skill is activated when it should not be, and the second one is activated when it should not be and with wrong parameters.
So there should be more checks. Like - ask for explicit permission before sending any voice recording out, or ensure that the target where recording is set is validated against whitelist explicitly set by the user, etc.
Oh is that all.
I have not experienced that, can you elaborate? They keep spamming me with mails of all there different services, show me what I should buy, etc. No way off even turning these things off...
What I should have said is this report makes it difficult to understand what actually happened. It seems clear this article favors click-bait quotes that insinuate a "big brother" vibe such as:
> "'unplug your Alexa devices right now,' she said. 'You're being hacked.'"
If she had instead said "Alexa butt-dialed me!", would you still be interested in this report?
Or... what's missing is the hours spent going through support tiers 1 through N, and somehow not getting dropped/lost along the way.
The guy in the elevator screams "COMPUTER! FORMAT SEE COLON SLASH WHY ENTER" across the whole cube farm. The doors close, and the elevator is gone.
Caption was something along the lines of "Speaker-independent voice recognition might be a bit tricky."
EDIT: Just realized the substantial difference is that Google and Amazon own all of these things. They don't control all makes and models of phones.
1.) They have an economic incentive to do so
2.) Only they know how their systems work
3.) Their network traffic is encrypted
4.) They face legal risks and user backlash if caught doing so
Given 2+3, you can't be entirely sure that they aren't doing it. If they deny it, your only recourse is to hope that their cost/benefit calculus considers 4.) to be more costly in terms of dollars.
It will recognize the Hey Siri, but give an error for everything else. Pretty sure "Okay Google" will behave the same way. Also if you turn on battery save on iOS it disables "Hey Siri".
It's a custom low-power chip they added on the 6S and later to allow a local tight loop that only listens for that utterance using a hardware-assisted neural net, and only activates the rest of the software stack if it detected it with reasonable confidence.
There's a nice blog post about it here from the apple engineers (see the "Two-pass detection" section): https://machinelearning.apple.com/2017/10/01/hey-siri.html
Also why could it send data out without any confirmation from the user.
And the LED should be forbidden by law from being software-controlled.
They should also have a physical inline toggle switch to disconnect the microphone(s) entirely, whose state is easy to visually confirm.
WiFi is always on. WiFi doesn’t disconnect just because you aren’t actively moving data. You’d be pretty annoyed if every time you wanted to send or receive data your device had to reconnect.
We're also discussing theoretical hardware changes, there's no reason it can't have 2 sets of microphones where one is hardwired only to the wake-word processor which has no direct connection to the main processor except some one-way signalling, and the LED is hardwired to the second set.
The idea that there would somehow be a dedicated wake word microphone is a little ridiculous. Firstly, no one would trust this supposed 1-way connection. Second, it would require a dedicated processor to make the wake word even work, driving up costs. Third, the echo uses an array of microphones so your wake word would either be unreliable or drive costs up further as you duplicate the entire array. Hardly a net win.
The reality is that if you don’t trust amazon to do the right thing you shouldn’t install their listening device in your home. (Likewise for your phone.)
If the microphone uses an amplifier, you could wire an LED to light when power is supplied to the amp. The indicator light is physically part of the circuit, so its operation cannot be modified by software. There are probably other, better, ways to do it, I'm not an electronics guy.
I don't think that would be a bad thing; especially if there's a switch to disable the mic. When you turn it off, you'll get reliable feedback to know it's actually off.
I think it's important that these kinds of devices have simple feedback and control mechanisms that can be independently verified and reasoned about. Software is too opaque and too untrustworthy.
I see that, I think it would be best as a separate light.
I think product UX has drifted too far towards blank monoliths; I know I wouldn't mind a few more blinkenlights :)
Doing it via microphone/amp wouldn't do it, since you'd still want to use it without LED on (and not software controlled).
We don't live in a world with a healthy enough market or enough competition for that to work.
It has that. They call it the power cable.
If you disconnect the microphone, an echo is pretty useless.
If, even with that expectation, enough people still use "voice assistant" technology for a judge to consider the tech to be "in general public use"[1], the bright line test defined by Kyllo v United States is triggered and the police no longer need a warrant to use the technology (in the abstract - they don['t need to use your hardware) to view "details of a private home that would previously have been unknowable without physical intrusion"[2].
Normalizing the expectation that previously private areas (like the inside of your home) might be recorded and sent to a remote 3rd party will eventually result in everyone losing some of their 4th amendment protection against search and seizure.
[1] http://caselaw.findlaw.com/us-supreme-court/533/27.html
[2] Ibid.
It's like the misguided Prop 65 signs that are in practically every commercial building in California so instead of warning people about dangerous levels of hazardous chemicals, they get a meaningless sign in every building for hazards that are no worse than if they were walking down the street or sitting at home.
That would require, though, that it's not buffering the last N seconds of audio to reprocess once that processor wakes up. Do any/all of the modern smart-speaker devices do that? If so, then you'd have to take into account that when you see the light, you've potentially leaked any secrets you said in the last N seconds as well. Less like a reporter coming in and asking to speak to you; more like an eavesdropper coming in and telling you they heard what you were just saying through the door.
As nerds, it makes sense to us to do local wake recognition and only upload a request phrase after that. But in reality, this not the first time[1] we've learned that continuous speech was getting uploaded.
Charitably, it could be a mistake, maybe the previous request never terminated and it just kept streaming. But again, not the first time.
More likely, my opinion, is there's a mountain of cash on the table in the form of private conversation, and AMZ would be foolish to walk away from it. After you talk about "hardwood floors" in your house, you could expect targeted ads, consumer profiling, variable pricing, and third party sales. Why woudln't they do this? Why else are they pushing home devices so hard? They're front and center on the front AMZ page every time you visit, aren't they? Oh and GOOG too, they just haven't been caught yet.
1. https://www.wired.com/2017/02/murder-case-tests-alexas-devot...
With that said, my Sonos Alexa has a tiny LED but does respond with an audible tone when the keyword is heard.
That is... when it's not randomly laughing https://www.theverge.com/circuitbreaker/2018/3/7/17092334/am...
Talking loudly in another room. Alexa: "Do you want to send this message to Jim?" "Alexa, you suck"
A confirmation after every request makes the device a lot less useful, I suspect most people do not want the device to confirm commands before it does them.
Don't get me wrong, technology is amazing and the cutting edge stuff going on today is super exciting... But it seems the capabilities of software now are far, far outpacing our abilities to ensure an adequate level of security and personal privacy. We've been blinded by flashy tech, too busy being amazed at everything all the time ("look at what AI can do!") and not stopping to consider the huge hidden price we're paying.
The reasons this has happened are kind of obvious... I just fear that it's going to take things getting to a point where we have a really major catastrophe on our hands for anyone to be willing to really do anything about it. A lot of people can and will get seriously hurt. I can imagine such an event resulting in a great "cooling" period in tech where advances are slowed while bigger investments are made into security, cryptography, solving the "identity problem", etc. But it would be nice if we could just have the foresight to fix things before it gets to that point...
But either way, they should surely be confirming this before send, the same way Siri does when I ask it to send a text.
I haven't used a smartphone in years. Looking back on the days when I did use a smartphone, there was always this tiny fear in the back of my head that maybe I'd pocket-dialed someone and they'd be able to hear my conversation. It actually had a subtle chilling effect.
The Hawthorne effect (which discusses how people react to being observed) seems to be especially relevant nowadays as there's a real possibility that we're being recorded at any time. https://en.wikipedia.org/wiki/Hawthorne_effect
It's actually a big theme in 1984 where the mere possibility that you were being listened to via telescreen was enough to keep you in line and influence your behavior.
Could it be that the volume was set very low and they inadvertently triggered their way through the entire dialog? I've accidentally set alarms from a few rooms away but this is a whole other level.
This seems dangerous, some smart house could open the doors or stop the heat or stream your entire live on the internet.
Some POST requests may only need to let you know that they did it, such as adding a calendar reminder on to YOUR calendar. It should ask if it wants to send a calendar invite to someone else's calendar.
...Oak in the annex and for the record...
recording begins
...it's just the annex, stop fretting...
recording stops
just send [flooring person] a quick message with samples you like.
sends recording to someone with same name as flooring person
It sounds like the problem is that it was overly confident it understood the user's intentions, and did all of this silently.
Echo woke up due to a word in background conversation sounding like “Alexa.” Then, the subsequent conversation was heard as a “send message” request. At which point, Alexa said out loud “To whom?” At which point, the background conversation was interpreted as a name in the customers contact list. Alexa then asked out loud, “[contact name], right?” Alexa then interpreted background conversation as “right”. As unlikely as this string of events is, we are evaluating options to make this case even less likely.
It sounds like the machine learning models are tuned for specific phrases and have terrible, terrible false positive rates. "Evaluating options to make this less likely"? Now I don't even know what mental model you guys are using (if you are from Amazon). This shouldn't be a matter of "likelihood". But OK, fine, let's use math. AFAICT there is about a 0% chance that a human would make such a string of errors interpreting human speech, but let's call it 1 in a trillion. If you guys aren't doing better than about 1 in a trillion for this string of at least 4 interactions, then one of those terms is stupidly, stupidly high.[1] It actually interpreted random conversation as the name of someone on a contact list? Horrible.
trust--
[1] Not even to mention, a human has context, understands boundaries, preferences, and has a ML voice recognition model developed and tuned over decades of interacting with real people. A human would also be smart enough to understand the other human's situation, context, state of mind, and realize that even just the cadence of the conversation not changing in response to queries was indicative of the humans not acknowledging the query. Machines are f'in stupid.
Did you really want to talk concrete numbers? Because if so, I am wondering about the probability that Amazon's voice recognition mistakes random conversation as a valid entry in someone's contact list, as well as the other terms in this equation.
I don't know if you work for Amazon, and if so I don't want to single you out specifically, but this is a pretty bad screwup, and it does not inspire confidence. Please don't brush it away with "oh it's a 1-in-a-million edge case". That attitude is even worse, and if it is indeed that attitude inside of Amazon, then I am even more strongly against this and I hope that further, deeper scrutiny is applied here, because this screwup is actually illegal.
1 Wake up w “Alexa.” 2 respond to “send message” 3 respond to “To whom?” 4 respond to “[contact name], right?”
As an engineer (well, an AI researcher who used to engineer), that looks to me like they were not negligent and it was hard to predict background conversation would produce this unlikely set of inputs - it would be nice to see stats but this is the first time it is covered in the media to my knowledge. And as with the laughter story, they will now change the inputs to make it likely 1-in-a-trillion this will happen.
However, it does seem like Alexa etc. will have to be better about recognizing audio from TVs/conversations and stuff directed at it - and I am sure they are working on it.
PS comparison to CPU is not great obvs since it's about number of instances (how many times does "Alexa" get woken up by background audio - not 4ghz)
This is part of the problem. People want to handwave away small probabilities when they should be busting their asses to make probabilities actually 0--solutions like not having this crap in their house at all.
If there is even a slightest possibility that Alexa/Siri/Google/Cortana is going to misinterpret commands (with privacy implications) then they should do two step verification of some sort.
Once recordings of private conversations leave the local environment and make it to the cloud, eventually they will leak. It's akin to data collection by law enforcement: once the data exists, eventually it will be abused.
Not even the most responsible companies (e.g. Google) can hold out 100% of the time in the face of determined assault by government. Some of that data is going to leak to three-letter agencies, or similar.
Somewhat less responsible companies (e.g. Amazon) will leak data more often, to a wider range of threat agents.
So then we have to consider how valuable this data is. Random sampling of private conversations within the home? Sometimes innocuous -- but if the wrong moment gets leaked, the consequences are potentially life-shattering.
It's because such blithe dismissal of the damage caused by data gathering is so prevalent in the industry that the likelihood of devastating compromise is so high and the costs borne by the populace are spiraling upwards.
Some data should never be collected. Some data should never even be uploaded.
I am honestly confused as to how you interpreted my last comment as "utterly cavalier about the prospect of ruining people's lives", when all I said was that your assumption doesn't take into account the actual probability of data being leaked and it doesn't weigh any of the benefits of data collection against that risk.
I can only hope that karma visits those who arrogate to themselves the decision to sacrifice a few of their fellow human beings: may they and their loved ones become the sacrifices.
I expect worse to come.
[1] Am not saying anyone deserves this, or that AZON is either evil or beneficent, or anything else other than precisely what was stated.
I vote no on telescreens.
Inappropriate, worrying, but not surprising.
That's the "Facial recognition fooled by funny-colored glasses" study from Carngie Mellon, where researchers were able to make machine learning algorithms fail disastrously (e.g. mistake a man for Milla Jovovich) with a pair of glasses printed with what looks like a random assortment of colorful pixels, but is in fact a targeted attack specifically designed to trick the algorithm.
This Alexa failure is obviously not a targeted attack; but when your system is exposed to enough data, eventually you will stumble over some input that happens to resemble a targeted attack by pure chance, right? It's equivalent to saying that if you aimed the facial recognition algos in that paper at millions of faces wearing randomly-colored glasses, eventually some of the glasses would be close enough to the targeted-attack glasses to produce the same effect.
Obviously I'm theorizing on almost no data here - I don't know anything about Alexa's voice recognition, maybe it contains no ML at all. But it seems plausible that this might be what happened here - not a bug per se, but the natural and totally expected result of giving an opaque, machine-generated system with a very low failure rate so much input data that the failure rate is significant.
Still, I wonder how it heard "record this conversation and send it to someone on my contact list".
That feels pretty scary particularly because these devices have such a high mandate. Right now you can shop for things online by voice command. Record and send messages. What's next, sending money, sending a data dump of sensitive data like emails, passwords, contact lists?
We've already heard of some reports where you'd have a smart home device listen to a commercial on television where they were demo'ing a purchase of some product via such a device, and interpret it as a command from the owner. Amazon took steps to avoid that with their superbowl commercial, but it seems to have done so by changing the commercial, not the product itself.
Just another attack vector to worry about. I'd happily buy these home speakers if I could limit them to just downloading information, and only uploading limited pieces of information, e.g. a music playlist. I'd want to be able to shut off any of the commercial/financial or social capabilities. I just don't care about them and they're risky.
Now I hear it beep and randomly start listening when my wife and I talk. Sometimes it does it randomly without me making a sound.
I ask it what's up and it ignores me and goes to sleep.
Smart speakers are so dumb I'm hardly surprised by this.
Based on Amazon's response I assume the device didn't notify the user at all and it wasn't just a matter of not hearing it.
It will be pretty easy to justify by bringing up bomb threats, but it would mostly be people buying/using drugs.
1. https://www.nytimes.com/2018/05/22/technology/amazon-facial-...
This incident speaks more to Amazon's speech recognition rather than a weakness of voice. Am not an expert in the topic, but it certainly seems like Alexa tries to hear patterns rather than translating speech to text then text to commands. Google Home's recognition is much better.
I guess naively I'm thinking some sort of light/display which says "Amazon is sending/retrieving data" - it would need to be from a third party to have integrity, and I suppose in order to actually allay the fears of the masses it would need to be plug-and-playable.
Does such a thing actually exist?
Side note: why is it that after years and years of privacy breaches, there has been almost no support to use hardware switches for cameras and microphones?
I would feel 100000% safer using my internet-connected cameras and microphones knowing that I can turn off those devices independently of their host devices and that no hacker can monitor my cameras and microphones, even if they’ve rootkitted every device I own.
Is it possible there's an exploit out in the wild for these devices that allows an attacker to control the device remotely.
Is it possible an attacker told the device not to make an audible announcement?
Is it possible that there's a remote exploit? Yeah of course but if it's in the wild enough that this particular individual was struck by a seemingly random (and valueless) attack we'd be seeing a lot more of these in the wild than we are.
Much like running into a human on a bike, but less deadly. (Unless there's a psycho in my contact list.)
It's like saying that someone buys a car that's powered by an explosive liquid, and then complains when all the gas in the tank explodes at the same time.
Given that, it would be ridiculous to expect paying customers to switch it off when not in use. The onus on Amazon is to protect their customers' privacy while the device is being used as intended.
If you really want to pick apart the car analogy, maybe this is closer to having automatic start and driving capability on a car, but the car sometimes randomly starts and drives away. Are you really going to blame the customer for that, even though they could disable the feature every time they exit the car?
I think for some, at least users like me would like a feature similar to "su". I'd like to confirm that Alexa should start doing stuff if it has not been confirmed for x number of minutes. I think the real problem with these home assistant devices is they are not designed with a confirmation message. This would be annoying in some cases, but surely a balance can be struck.
I'm not trying to be reductive at all about the car analogy. When you turn on a car, you acknowledge that the engine is running. You can also mute an echo if you have the foreknowledge that you will not be doing activities that require voice activation.
But there is a hilarity of, on one hand being privacy centric, and with the other hand, planting a listening device in ones home.
What if this was a lawyer talking about clients or a doctor talking about patients? Is Amazon (or Google, or Microsoft) willing to deal with such legal liabilities? Is this what move fast and break things looks like?
Edit: To those trying to downvote, remember, the Silicon Valley lives in a bubble, and for the safety of people inside and outside of the bubble, the bubble must be poked every so often. This is one of those times.
I'd say the Echo needs to have a more difficult activation routine available. Maybe have the option of setting the wake word to "Alexa, can you please" or something similarly long and unlikely to appear in normal conversation.
Also, I wonder if they had their wake word set to "Computer". I did that once, and quickly reverted after so many false activations.
Lately I’ve been seeing Alexa wake on accident more often. It’s like someone isn’t thinking critically about what kind of Type I error they’re willing to accept.
Think about this statement for a sec. Of course is listening to you. It has to listen to you because it needs to be able to respond to "Alexa". So yes, this is always listening.
Now, once you come to terms with that, do you feel comfortable having a technology with access to the internet, location, habits, account, contacts, email, phone, CC information etc etc, to be actively listening to your most intimate private conversations?
It does not take a 5 year old two seconds to figure this out.
There isn't much additional risk from having an Echo or a Google Home if you already keep a smartphone within 10 feet of you at all times, which most of the people who are buying these devices do.
It was both hilarious and infuriating. I immediately turned the calling feature off (you have to contact support btw) and later we switched to Google Home.
So if it though it heard "Alexa, send this message to John: {conversation of ten minutes}" it just did what it thought it was supposed to do. But it's weird they didn't hear any audible confirmation or anything.
If that's true - that dumb greedy move is going to cost AMZN way more than simply giving customer refund.
Perhaps they were indeed hacked. Got into test group for some black hats project.
We as tech users are constantly trying to balance convenience with safety
I’m so out of touch with this world it’s scary.
/s
This is just whataboutism.
We can complain about Amazon in a thread about Amazon without having to tackle a whole different issue.
The whole point of these cylinders is to be listening at all times.
Yes, it’s ultimately trust in the device maker, the compiler, the chip manufacturer, etc, and those can and have been verified to some extent.
But that’s not the point. A phone can listen or not, where you have no doubt with the cylinder. It’s its raison d'etre.
And people know this. It’s not like they are being misled. It’s a conscious exchange of privacy for convinence. It’s just that, in my mind, you are getting very little for what you’re giving.
I made a different choice, but I totally understand why someone would choose not to have a phone or smart speaker due to privacy concerns. What I don’t get is someone who has a phone but sees smart speakers as crazy.
- You are pretty certain that your phone is listening at all times, even though it's set not to.
- You see no difference between a product that's advertised manly as a listening device and one that also has such a feature, that can theoretically be turned off, and is very useful otherwise.
I see no difference, privacy-wise, between the two. I don’t care how they’re advertised, I care what they’re capable of.
I'm sure you can appreciate the difference: press a button to talk to Siri vs Siri is always listening.
The latter seems crazy to me, on a phone, cylinder, laptop or whatever device it's implemented.
If that was the case, nothing. But we have enough evidence to believe it's not. While having the device listen, even though it's been explicitly configured not to, is a bit more of a stretch.
>Are you just worried about accidental activation?
That could be an inconvenience too, but I'm more concerned with malicious intent.
If you’re concerned with malicious intent then I really don’t understand the difference. If the device maker is trustworthy then you’re fine either way. If they’re malicious then you’re screwed either way. A setting for “please don’t listen” isn’t going to make the slightest bit of difference if they’re malicious. M
Nor should anyone I think.
It seems to me that smartphones are significantly worse. You can unplug your smart speaker or kick it off your WiFi and be confident that it can no longer hear you. Smartphones have batteries and cellular data connections. Also they’re usually with you at all times, even when you’re away from home.
A lot of people talk about it, they’re just laughed or shouted down. There’s also the argument that mobile phones undoubtedly offer a number of incredibly useful tools, not the least of which is a primary phone line. I think anyone would be hard pressed to argue for commensurate utility from Alexa or similar products.
“Networked device with microphone records and uploads your voice” might create reactions such as: yeah, what did you expect, how else would it work?
“Networked device with microphone records and uploads your voice even when explicitly told not to” is a lot worse. Company X is lying to us!
My guess is they mostly do work that way but bugs and vulnerabilities don't seem like a stretch. (As is to be expected with all software)
If you actually care, this would be pretty trivial to verify using an oscilloscope to observe the energy draw from the battery while different things are said around your device.
Is this possible of a Pi?
Then all that's left to figure out is...
1. Make it work really well across a vast array of voices, accents, and background noise.
2. Make is easy to add new features to, in order to keep up with the competition.
3. Mass produce it at a price people will pay.
4. Have a viable business model.
Do these simple things and you'll be a very, very rich person.
Looks cool, but I haven’t tried. I’m the kind of person that gets up and walks to the light switch.
That said....we are on track to have a high quality experience when we go to production in Feb 2019 ( Release 19.02 ). As an open source community we'd welcome any help folks have to offer. Contributors don't even need to know how to code, all they need to be able to do is listen to sound samples at https://home.mycroft.ai and tag them as "Hey, Mycroft" or not "Hey, Mycroft"
Thanks to everyone who is helping make Mycroft a reality!
> People are voluntarily paying for their houses to be tapped for the convenience of being able to shout: play me some song. > I’m so out of touch with this world it’s scary.
I could just as easily say "People are voluntarily paying for their locations to be tracked for the convenience of being able to get live maps on the go" (ie. cell phones, which also are listening to everything you say unless you disable it)
“Alexa... play white noise”
“ALEXA... stop”
I also live in a city, so white noise (actually brown noise) masks out tiny noises that interrupt sleep.
clap clap
Clap off
clap clap
Clap on, clap off. The Clapper!
clap clap
Mankind has made countless decisions to trade convenience for some degree of personal freedom. I can live without mobile internet - its just so convenient to have it. Voice control for home appliances is exactly the same.
I can also control my tv, thermostat, get a news briefing, check my calendar and set reminders.
Yes, it's ultimately a convenience, but so is indoor plumbing and store bought bread.
I’m sorry, clean water and food are not conviniences. They are among the most basics of human needs. That’s the kind of thing that scares me. That someone would make such a comparison with a straight face.
Have you ever considered that this is not the case in most of the world? Resources are far from evenly distributed.
It is not by chance that the availability of indoor plumbing correlates to increase in life expectancy. It's nice that I can just open the tap and clean water comes out, but it's also a lot more sanitary than people carrying and storing buckets around.
>I just cannot work out if the commenter was being deliberately obtuse or really misunderstood?
Same here. Comparing the savings of a few steps towards a light switch to clean water and cheap food is intellectual dishonesty at best and severe ignorance at worse.
Neither of which is needed to live. Both of which are conveniences.
Convenience does, absolutely, have strong value and can be meaningful improvement to one's life. Generalized voice control is a major and meaningful convenience - even if it's currently early and might have some problems - because it drastically changes how we can interact with our environments.
Sure, we can short sell the case as "not needing to walk to a light switch", but even then if it's dark, my arms are full, and the path to the switch is littered with children's toys then that's a meaningful improvement to be able to say "Hey google, turn on the living room light".
Consider cases of people with severe MS or who otherwise can't easily walk. Sure, they could hook up a remote control and keep it near them, or get one of those stupid clapper things, but even then that only works for the lights.
A generalized voice assistant gives me control over my house, from anywhere my voice can be heard, and not only executes my actions, but can give me realtime feedback and data. Best of all, this requires no special skills on my part, just a willingness to talk to the damned thing loudly and clearly with simple words.
Can it act as a wire tap? Of course it can. My store bought bread can also be contaminated (right now in my area there is a huge contamination issue with eggs and lettuce), my indoor plumbing can burst and flood my house, so on. It's a new technology, it has kinks and flaws, and we're currently in the early adopter curve of it moving towards the initial disappointment trend.
My disagreement with you is precisely because you consider them equally interchangeable.
To me, putting those two on the same level is actually offensive.
If data on the increased life expectancy isn’t persuasive enough, I suggest you speak with someone with no access to basic sanitation. Ask them what they think of this comparison.
I suspect we are only a few years away from being able to do a slightly inferior version using local processing, or a private cloud (already possible today when there is a market). I would probably opt for that, but use Alexa in rooms already already untrusted.
I have difficulty believing this. We had good speech recognition on <$1000 devices 10 years ago.
But Siri sucks for MANY reasons, and not just technical ones. It does worse processing but also does worse cloud integration, and now vs. alexa, has a far worse ecosystem around it (alexa "skills" are pretty awesome, and trivial to create)
We are a long way from being able to do that on $100 devices.
Similarly, there is a massive difference in the privacy implications of listening to every conversation everyone in your home (including guests) is having vs. having your current location known. Wiretapping laws exist for a reason.
To be fair, you can have all the maps without the location tracking; the location tracking just tells you where you are on the map.
This is not the world we should be engineering. Actually, I would say, this is not engineering.
There's no reason why your house needs to be "tapped" for either of those use cases. All those things could be accomplished without leaving your home network.
And about tapped .. well, I don't consider any conversation as private, when there is a Smartphone around.
Is there nothing you've ever said about anybody while in the vicinity of a smartphone that you wouldn't have said to their face?
There also other things, like pillow talk etc.
And I simply don't want anyone else to take part in that, whether they are russian, chinese or NSA hackers, or the company by itself.
And I usually tell people in their face, what I think of them.
Perfect example. Do you always ensure there are no smartphones within earshot?
But I would certainly try to do this in this situation as well.
It is not only privacy btw. it is also just nice to have both persons here in the now and not half distracted because the Smartphone just got new messages. Could be important... but usually never is important enough, to destroy the moment.
So when I go to sleep, alone or not, the mobile is off (without battery) or away. Unless there might be a emergency and I need to be avaiable, but those situations are rare.
- people in the sixties: "the government will wiretap your home"
- people now: "hey wiretap, can cats eat pancakes?"
I enjoy living dangerously.
"Google takes top spot in global smart speaker market, HomePod nowhere to be found"
https://appleinsider.com/articles/18/05/23/google-takes-top-...
Came to the market 2 years later and already passed. This is before we even get Duplex.
https://www.youtube.com/watch?v=bd1mEm2Fy08
Google goes in the lead on something they tend to not give it up.
And it's a flaw so bad they had to outright remove the button entirely, because they couldn't fix it without replacing the hardware.
It's a little disingenuous to insinuate a bug with recording audio is a reason people shouldn't be buying company X's product over company Y's, which also has had a bug with recording audio.
The person that it happened to got a pre-release version. Google even went to the persons house on a Friday evening to resolve. The person found the problem on the same day. None of the units sold to the general public had the issue. Realize Google literally dropped everything to take care of the issue. Now that is what you want to see.
The reason you buy a Google Home is because they provide a much better user experience and why Google has already passed Amazon even though they did not get to the market until 2 years later.
"Google takes top spot in global smart speaker market, HomePod nowhere to be found"
https://appleinsider.com/articles/18/05/23/google-takes-top-...
We started with an Echo and then purchased the Google Home and then several more Google Homes.
My son had graduation earlier this week at an arena that has a name that is difficult to pronounce. It is named after someone that gave a lot of money to the University.
There was also a MLB game that night that started 15 minutes later than the graduation.
Walking through the kitchen asked drive time thinking no problem as people are leaving the city usually not going to the city.
Google got it the first try and gave drive time which was 2x more than normal.
Google saved my butt as quickly got ready and left and would not have otherwise. Asking our Echo and Siri the same question and neither could handle.
That is why you buy the Google Home. Well also because of new things like Duplex coming.
https://www.youtube.com/watch?v=bd1mEm2Fy08
Google is just so far ahead in every layer of the AI stack and just going to be able to provide a far superior product.
Echo was out 2 years longer and Google already passed as they are just a lot smarter and easier to use. It is that Google AI is just superior in every layer of the stack.
Can't wait for Duplex.
https://www.youtube.com/watch?v=bd1mEm2Fy08
Once Google leads in an area they do not give it up. Something I just love about Google is they never rest and will just keep innovating.
The new voices are incredible. You can not tell the difference between the machine and a human any longer.
We started with the Echo but then purchased a Google Home and more Google Homes. Looks like made the right decision on which to standardize on.
Edit: Not to mention that the entire Alexa is a black box, too.
Second Edit: Not trying to claim that you're an idiot, just provide some perspective.
I have an Echo on my kitchen counter. I know there's a small chance that it may be hacked or have a bug or be deliberately modified to surreptitiously record from my kitchen audio that ends up on some Amazon server somewhere, or in the hands of law enforcement, or the NSA, or hackers, or whatever.
I just don't really care. I like the convenience of the device, there's a lot of scrutiny on the devices and the companies that make them, discouraging deliberate misuse, and I don't really say anything interesting or worth hiding. And if someone is going to deliberately target me, my life is jammed with devices that are probably a much bigger risk surface area.
I would never say anyone else should get one if they feel the privacy risks outweigh the benefits, but I'm not personally concerned.
However, I may be wrong. So change my view: why should I care or be worried?
I'm not surprised that my GPS capable phone knows where I am at all times. I wouldn't be surprised if my Echo recorded my voice and sent a message to someone. I wouldn't be surprised if there were some major bugs yet to be addressed in the software for the Echo. I guess this is a little harsh, but my sympathies are somewhat lost on these people. Not their fault for what happened, but they did take a risk.
"A husband and wife in the privacy of their home have conversations that they're not expecting to be sent to someone (in) their address book,"
It just doesn't sit well with me.
Yep. So was couple. About Alexa. Same thing.