You can’t effect the number of bit flips your users hardware has, but you can affect how often buggy code corrupts their memory or otherwise crashes your program.

Let’s say any app will crash about once a year on my machine due to a bit flip. If the app is crap and crashes hundreds of times for other reasons, the bit flip is irrelevant. If the app is robust enough that the bit flip accounts for 10 % of the crashes, that basically means the app is pretty much never crashing due to poor code.

But… why? Isn’t that just far more energy consuming and expensive to run? It sounds like replacing your car for a bus that sporadically stops working, even though you always drive alone.

To be fair I would assume that it’s better to trigger something like this during a security review when people are actively “online” and focused on security risks than at some other time.

Even with steel pipes you get problems with hydrogen embrittlement because hydrogen diffuses into the steel and can cause it to crack.

In 51.6% of cases where someone needed to go to the hospital immediately, the platform said stay home or book a routine medical appointment

So it performs slightly worse than a coin flip…

In one of the simulations, eight times out of 10 (84%), the platform sent a suffocating woman to a future appointment she would not live to see

Holy shit! That’s a lot worse than a coin flip.

Meanwhile, 64.8% of completely safe individuals were told to seek immediate medical care

And there are real people out there that actually trust this tech to make real decisions for them. It literally performs significantly worse than a coin flip both with regards to false positives and false negatives. You are literally better off flipping a coin or throwing a dice than asking this thing what to do.