You’re all missing the real kicker here - this sign is only here for the HIPAA auditor. Everyone knows that no one is actually going to mute the thing.
We’re not all like that. Some of us do really care (a whole lot) about the person, and not just “the patient”. We get eye-rolled and sighed at sometimes because we speak up; but it doesn’t matter because advocating for our patients is one of our top priorities.
Some hospitals have better work-cultures than others, but all of them have at least a few who truly give a damn
No, there is a button to make the Echo stop listening.
If you want to prove me wrong, it should be incredibly easy to press the button and record the Echos network activity. If you’re right you’d still see network traffic. But nobody has been able to show this so far. I wonder why?
Yeah I read the other comments after making mine. However everyone keeps calling it a “physical” button, and I don’t think that’s accurate. It won’t be a physical switch that opens a circuit, it will be a button that operates a transistor that opens the circuit.
Still, I see no good reason to trust the device - especially in a medical setting.
This is disingenuous at best and incorrect at worst. The mute button on the Echo is just that, a button; it is not a switch. It is software-controlled and pushing it just sends a signal to the microcontroller to take some action. For instance, one action is to turn on the red indicator light; that’s definitely not physically connected to the mute button.
Maybe another response of pushing the button is to disable the transistor used for the microphone, but it’s more likely that it just sets a software flag for the algorithm to stop its processing of the microphone input signal. Regardless of which method it uses, the microcontroller could undoubtedly just decide to revert that and listen in, either disabling or not disabling the red light at the same time.
But I personally don’t think it listens in when muted. I don’t think it spies on us to target ads based on what we say around it. I’m not worried that the mic mute function doesn’t work as intended.
But I fully understand that it is fully capable of it, technically speaking.
I don’t know the internal workings of the echo, I was responding to a comment that said it “operates a transistor”. Which is way different than it being an input to a microcontroller.
If the button is just connected to a transistor, it’s not software controllable, since transistors are electronical devices that don’t interpret any software. A microcontroller does execute software. There’s a big difference.
Transistors are simple electronical devices. They don’t run software. You can control their inputs with another device (such a microcontroller) that does run software. You can also control their inputs with a button. You can’t control their output with software.
I don’t know how an Amazon echo is wired up, but if you just have a button connected to the gate of the transistor, it works basically the same as a mechanical switch.
Transistors have no registers. They have no arithmetic logical units. They have nothing. They are so simple they can be made up of less than 100 atoms. Transistors have to be connected electrically to other device. Any reverse engineer can trace what it is connected to and it’s behaviour cannot be programmed. If you know that it’s a transistor and you know the inputs, you can know the output. The same cannot be said for a device which runs software, you’d have to additionally know what that software does, which is incredibly more complicated.
Software is ran by microcontrollers. Transistors can be connected to microcontrollers. But they can also be connected to buttons. If there is no microcontroller, there is no software.
Which you could easily see by looking at the amount of traffic sent after unmuting, unless you believe that Amazon secretly found an infinite compression algorithm they use only in muted Echo devices.
Tbf to foobar, that should still give a falsifiable and testable data-difference if you are willing to alter your behaviour around experimentation for an extended period of time
Though, there are always more ways to hide traffic
Again: Which you could easily see by looking at the amount of traffic sent after unmuting, unless you believe that Amazon secretly found an infinite compression algorithm they use only in muted Echo devices.
You understand that sending more information means more traffic? Unless - as I stated - they found a perfect compression algorithm, you’d be able to tell.
I’m a little confused as to why you are being so condescending. Every time you say “this is so simple if you do X”. And then I say “what about Y?” And then you’re like “that’s obvious too, just do Z” and kind of insulting me, even though you did not account for it in your prior comment. And it becomes less trivial with each additional test.
Your first method involves simply checking if there is any traffic after muting. Your revised method involves additionally checking if there is any traffic for some period of time after muting (how long?). And now your third method involves doing the first two things as well as gathering data on the average amount of traffic in your requests generally and deciding whether subsequent traffic during requests after muting for an unspecified amount of time is significantly large enough to conclude it is sending information acquired during muting.
But if they send it a little bit at a time, or they just leak a small portion of it occasionally in some requests, I think it would be very challenging to conclude definitively one way or the other.
I’m actually aware that there is no infinite compression algorithm, so you don’t need to keep saying that. And to be honest it just makes you look like you are lacking imagination because it’s not the only way to make detection difficult as illustrated by my responses.
I’m a little confused as to why you are being so condescending. Every time you say “this is so simple if you do X”. And then I say “what about Y?” And then you’re like “that’s obvious too, just do Z” and kind of insulting me, even though you did not account for it in your prior comment. And it becomes less trivial with each additional test.
I’m writing the way I do because you’re bringing up points that are incredibly easy to disprove as if they’re some kind of gotcha. “They might store the data” seems like a good point until you remember that even that stored data has to be transmitted at some point. How would you have me reply to these non-arguments?
Your first method involves simply checking if there is any traffic after muting.
Because it’s sufficient to prove that the device doesn’t just not respond. That was the initial point I was replying to. Why do I have to find any possible counter-arguments when they weren’t brought up?
Your revised method involves additionally checking if there is any traffic for some period of time after muting (how long?).
Yes, because it’s sufficient to disprove the additional point you brought up. Just do it until the heat death of the universe if you want to be sure. You’re the one theorizing they might store the data locally. Create a full hypothesis, and I can tell you how to disprove it.
And now your third method involves doing the first two things as well as gathering data on the average amount of traffic in your requests generally and deciding whether subsequent traffic during requests after muting for an unspecified amount of time is significantly large enough to conclude it is sending information acquired during muting.
You make it sound like “gathering data on the average amount of traffic in your requests generally” is complicated, and like you don’t already have the data from the previous two points.
But if they send it a little bit at a time, or they just leak a small portion of it occasionally in some requests, I think it would be very challenging to conclude definitively one way or the other.
And you could still see this through statistical analysis.
I’m actually aware that there is no infinite compression algorithm, so you don’t need to keep saying that. And to be honest it just makes you look like you are lacking imagination because it’s not the only way to make detection difficult as illustrated by my responses.
It’s the only way your points make full sense. It’s a simple truth of the universe that transmitting more information requires transmitting more information. The only way to get around this is the aforementioned infinite compression algorithm. Any other method is detectable through statistical means.
I’m not sure that’s the case. We have one at work and if it thinks you’re calling out to it repeatedly it will say out loud that its mic is off and that you have to enable it.
It might just be the part that listens for “Alexa” but that audio buffer is available to the device and it can do things with it.
Because - as I’ve explained in the comment you replied to - it’s pretty easy to check it for yourself. Unless you believe that an Echo has a secondary cellular connection that’s only used while muted, any traffic must go over your configured connection.
Just look at the amount of transferred data while it’s muted. If there is data (beyond extremely low background traffic) I’m wrong. If there is no data, you’re wrong.
This is not some hypothetical metaphysical principle we’re talking about, it’s a product that you can analyse yourself. Put up or shut up.
You’re all missing the real kicker here - this sign is only here for the HIPAA auditor. Everyone knows that no one is actually going to mute the thing.
deleted by creator
We’re not all like that. Some of us do really care (a whole lot) about the person, and not just “the patient”. We get eye-rolled and sighed at sometimes because we speak up; but it doesn’t matter because advocating for our patients is one of our top priorities.
Some hospitals have better work-cultures than others, but all of them have at least a few who truly give a damn
I would like to thank you for maintaining integrity when it is not easy. I know it can be frustrating.
deleted by creator
Also muting it probably doesn’t stop it listening, it just stops its response.
No, there is a button to make the Echo stop listening.
If you want to prove me wrong, it should be incredibly easy to press the button and record the Echos network activity. If you’re right you’d still see network traffic. But nobody has been able to show this so far. I wonder why?
Yeah I read the other comments after making mine. However everyone keeps calling it a “physical” button, and I don’t think that’s accurate. It won’t be a physical switch that opens a circuit, it will be a button that operates a transistor that opens the circuit.
Still, I see no good reason to trust the device - especially in a medical setting.
There’s not much difference between a direct switch and a transistor, both will cut the signal and neither is over rideable by software
This is disingenuous at best and incorrect at worst. The mute button on the Echo is just that, a button; it is not a switch. It is software-controlled and pushing it just sends a signal to the microcontroller to take some action. For instance, one action is to turn on the red indicator light; that’s definitely not physically connected to the mute button.
Maybe another response of pushing the button is to disable the transistor used for the microphone, but it’s more likely that it just sets a software flag for the algorithm to stop its processing of the microphone input signal. Regardless of which method it uses, the microcontroller could undoubtedly just decide to revert that and listen in, either disabling or not disabling the red light at the same time.
But I personally don’t think it listens in when muted. I don’t think it spies on us to target ads based on what we say around it. I’m not worried that the mic mute function doesn’t work as intended.
But I fully understand that it is fully capable of it, technically speaking.
I don’t know the internal workings of the echo, I was responding to a comment that said it “operates a transistor”. Which is way different than it being an input to a microcontroller.
If the button is just connected to a transistor, it’s not software controllable, since transistors are electronical devices that don’t interpret any software. A microcontroller does execute software. There’s a big difference.
A transistor is controlled by software so yes, it’s absolutely over rideable.
Transistors are simple electronical devices. They don’t run software. You can control their inputs with another device (such a microcontroller) that does run software. You can also control their inputs with a button. You can’t control their output with software.
I don’t know how an Amazon echo is wired up, but if you just have a button connected to the gate of the transistor, it works basically the same as a mechanical switch.
No, as I just said in the comment you replied to, it’s backwards. Software controls transistors.
The important difference is that a mechanical switch cannot be maliciously switched on by software. It has to be done physically and intentionally.
There is absolutely no requirement that a transistor be controlled by software. They can be controlled by physical switches.
Transistors have no registers. They have no arithmetic logical units. They have nothing. They are so simple they can be made up of less than 100 atoms. Transistors have to be connected electrically to other device. Any reverse engineer can trace what it is connected to and it’s behaviour cannot be programmed. If you know that it’s a transistor and you know the inputs, you can know the output. The same cannot be said for a device which runs software, you’d have to additionally know what that software does, which is incredibly more complicated.
Software is ran by microcontrollers. Transistors can be connected to microcontrollers. But they can also be connected to buttons. If there is no microcontroller, there is no software.
If the Echo stored the audio and then sent it sometime after you unmute, it would still pass your test.
Which you could easily see by looking at the amount of traffic sent after unmuting, unless you believe that Amazon secretly found an infinite compression algorithm they use only in muted Echo devices.
Unless some or all of it was sent along during the next time you actually do a voice command.
Tbf to foobar, that should still give a falsifiable and testable data-difference if you are willing to alter your behaviour around experimentation for an extended period of time
Though, there are always more ways to hide traffic
Again: Which you could easily see by looking at the amount of traffic sent after unmuting, unless you believe that Amazon secretly found an infinite compression algorithm they use only in muted Echo devices.
You understand that sending more information means more traffic? Unless - as I stated - they found a perfect compression algorithm, you’d be able to tell.
I’m a little confused as to why you are being so condescending. Every time you say “this is so simple if you do X”. And then I say “what about Y?” And then you’re like “that’s obvious too, just do Z” and kind of insulting me, even though you did not account for it in your prior comment. And it becomes less trivial with each additional test.
Your first method involves simply checking if there is any traffic after muting. Your revised method involves additionally checking if there is any traffic for some period of time after muting (how long?). And now your third method involves doing the first two things as well as gathering data on the average amount of traffic in your requests generally and deciding whether subsequent traffic during requests after muting for an unspecified amount of time is significantly large enough to conclude it is sending information acquired during muting.
But if they send it a little bit at a time, or they just leak a small portion of it occasionally in some requests, I think it would be very challenging to conclude definitively one way or the other.
I’m actually aware that there is no infinite compression algorithm, so you don’t need to keep saying that. And to be honest it just makes you look like you are lacking imagination because it’s not the only way to make detection difficult as illustrated by my responses.
I’m writing the way I do because you’re bringing up points that are incredibly easy to disprove as if they’re some kind of gotcha. “They might store the data” seems like a good point until you remember that even that stored data has to be transmitted at some point. How would you have me reply to these non-arguments?
Because it’s sufficient to prove that the device doesn’t just not respond. That was the initial point I was replying to. Why do I have to find any possible counter-arguments when they weren’t brought up?
Yes, because it’s sufficient to disprove the additional point you brought up. Just do it until the heat death of the universe if you want to be sure. You’re the one theorizing they might store the data locally. Create a full hypothesis, and I can tell you how to disprove it.
You make it sound like “gathering data on the average amount of traffic in your requests generally” is complicated, and like you don’t already have the data from the previous two points.
And you could still see this through statistical analysis.
It’s the only way your points make full sense. It’s a simple truth of the universe that transmitting more information requires transmitting more information. The only way to get around this is the aforementioned infinite compression algorithm. Any other method is detectable through statistical means.
I’m not sure that’s the case. We have one at work and if it thinks you’re calling out to it repeatedly it will say out loud that its mic is off and that you have to enable it.
It might just be the part that listens for “Alexa” but that audio buffer is available to the device and it can do things with it.
I just tried it with mine, it doesn’t react in any way.
This is the funniest thing I’ve read today (though I’m not sure if it is a joke).
Aww, you actually believe that!
Shouldn’t take you more than 5 minutes to prove me wrong. Please do!
It shouldn’t take me more than 5 minutes? Why’s that?
Because - as I’ve explained in the comment you replied to - it’s pretty easy to check it for yourself. Unless you believe that an Echo has a secondary cellular connection that’s only used while muted, any traffic must go over your configured connection.
Just look at the amount of transferred data while it’s muted. If there is data (beyond extremely low background traffic) I’m wrong. If there is no data, you’re wrong.
This is not some hypothetical metaphysical principle we’re talking about, it’s a product that you can analyse yourself. Put up or shut up.
And I can do that all in 5 minutes without owning one?
Easily. The device doesn’t care who owns it, you can use one owned by another person.