cross-posted from: https://feddit.online/c/[email protected]/p/2115831/microsoft-365-outage-leads-to-chlorine-gas-poisoning-of-15-hotel-guests
cross-posted from: https://feddit.online/c/[email protected]/p/2115831/microsoft-365-outage-leads-to-chlorine-gas-poisoning-of-15-hotel-guests
The technical standards for Email would allow for 3 days of delivery failure before finally giving up. That’s the amount of leeway email has (in theory - practically we assume that everything longer than 3 minutes means something has gone wrong). Sending alerts by email is fine for non-critical applications; if one of my docker containers crash, an email is fine because the amount of damage is nil.
Why wasn’t there an actual fail-safe mechanism employed that measures the chlorine levels and shuts the whole thing down BEFORE it gets dangerous?
This is not a Microsoft problem. This is a negligence problem on Phantasialands side, using inappropiate tools for a system that can hurt people on failure, and should be followed up by lawsuits.