@jeffcliff @matrix I feel like the difference between your only human body that if permanently damaged can never be restored and if killed means the end of your existence and some computer program you're just working on cannot be overstated.
And if you're working on something that will kill people, then yeah, you should probably be limiting your dependencies and auditing as much as possible.
And if you're working on something that will kill people, then yeah, you should probably be limiting your dependencies and auditing as much as possible.
@sj_zero @matrix the difference between, say, now and 20 years ago is that 20 years ago we could get away with that kind of carelessness in replacable computer components. After all - the harm was purely the replacement of computer (if it was bricked) or time/effort to reinstall the software(if it wasn't)
...but we've started integrating computers into our bodies. One of my friends has a computer that controls his heart. One of my guests i was going to have on my podcast next has one that plugs into her brain. Computers are going to drive all kinds of things from kidneys to hands and have already started to do so. And those computers are networked with, or potentially networked with the rest of the network-enabled computing equipment we have built. Lightbulbs' firmware are now a vector for intrusion of a WAN - if you pwn a lightbulb, you can compromise a printer/scanner by using invisible variations in light in the room it's in, and go from there to the computers in your office, and from there compromise a pacemaker or worse: someone's entire immune/nervous system. These kinds of side attacks on human beings (which are possible to mass automate into script kiddie genocide campaigns) are becoming more and more possible with time, and more and more important to stop through countermeasures at all levels.
...but we've started integrating computers into our bodies. One of my friends has a computer that controls his heart. One of my guests i was going to have on my podcast next has one that plugs into her brain. Computers are going to drive all kinds of things from kidneys to hands and have already started to do so. And those computers are networked with, or potentially networked with the rest of the network-enabled computing equipment we have built. Lightbulbs' firmware are now a vector for intrusion of a WAN - if you pwn a lightbulb, you can compromise a printer/scanner by using invisible variations in light in the room it's in, and go from there to the computers in your office, and from there compromise a pacemaker or worse: someone's entire immune/nervous system. These kinds of side attacks on human beings (which are possible to mass automate into script kiddie genocide campaigns) are becoming more and more possible with time, and more and more important to stop through countermeasures at all levels.
@jeffcliff @matrix At that point, if you're talking about Elon Musk sticking a computer chip onto your brainstem to connect you to the Internet, then YES, I WANT TO KNOW EXACTLY WHAT'S IN IT.
@sj_zero @matrix yup.
and now just think how many people consumed bleach, because the public health systems across the US/elsewhere
ie
mandatory neurallink stuff is scary
but there's a level of 'public health disaster' that most people have not realized is possible when someone pulls a 'string copy' function from npm and suddenly a million people's hearts stop working as they autoupdate broken code.
and now just think how many people consumed bleach, because the public health systems across the US/elsewhere
ie
mandatory neurallink stuff is scary
but there's a level of 'public health disaster' that most people have not realized is possible when someone pulls a 'string copy' function from npm and suddenly a million people's hearts stop working as they autoupdate broken code.
I do *not* add 4000 dependencies to a project just cuz - we should be pushing for full understanding/auditing of ALL these dependencies. both vaccine and not