4 ms·
Sure, I just have inside information into some of these systems (and enough inside knowledge to be scared of their lawyers enough to not name specifics). Thera
by monocasa 5y ago
Sure, I just have inside information into some of these systems (and enough inside knowledge to be scared of their lawyers enough to not name specifics). Therac style systemic implementation issues aren't uncommon. Think handle every failure mode by panicking the OS, and the hardware fails in the wrong direction for the patient without software control.
IMO, yeah, community approaches might not be the ideal solution, but when it comes to my health it's the better of the two options I have (community that I can actually look at the implementation of vs. proprietary that I know has systemic regulatory issues and is a crap shoot on if it is actively killing people and the engineers who worked on it don't ever want it used on them). If it comes down to it I'm going to choose my health over legality every time.
- skybrian 5y agoA third option might be some kind software transparency scheme, where every change is publicly available and audited, with bug bounties. This could be done to keep the professionals on their toes without resorting to relying on random unvetted software. They could even take pull requests, as long as the company takes responsibility for them.
- lupire 5y agoThat's not an option; that's a dream.
- disabled 5y ago> Think handle every failure mode by panicking the OS, and the hardware fails in the wrong direction for the patient without software control. Thanks, I am aware of this. It's called a block diagram, and is standard safety design. See page 3: https://pdfserv.maximintegrated.com/en/an/AN4675.pdf https://pdfserv.maximintegrated.com/en/an/AN4675.pdf
- monocasa 5y agoIn case you're wondering why you're being downvoted, a block diagram isn't a standard safety design, nor really a safety design at all per se. It is simply a connection graph of subcomponents.