> It's the fault of the company that designed the automatic alarm. Not the hotel.
The hotel picked a monitoring solution which relies exclusively on email, or configured it like that. If anything they are absolutely both to blame but for different things. The company for designing a safety related system like this, the hotel for selecting an inadequate solution/configuration thus allowing their guests to be harmed.
> But it is accurate to say that the cause of the issue was the outage
The cause of the issue is the more immediate one - the configuration of the monitoring system. This avoids going up the causality chain to far - shitty coffee caused engineer to take down email system, and such.
Let's not forget that we're talking about people getting hurt, that's the core topic here, yes? The most reasonable immediate cause for the people getting hurt is that there was too much chlorine in the water. Because the dosing system pumped too much chlorine AND the monitoring system failed to alert. Because it was set up to only use email AND the email failed. Because someone deployed a wrong config on MS's cloud infra. And so on.
Not one but two of the hotel's systems failed to operate properly. The chlorine pumping system pumped too much chlorine and the last resort alarm failed to alert.
As I said, there's plenty of blame to go around as a matter of general principle. But for what happened here the hotel bears the responsibility towards their guests, not the pumping or monitoring system developers, not Microsoft. The only reason MS in the title is because that failure is big news these days.
On a technical note, even if they had a backup email provider they'd still be screwed because the people getting the alert were probably employees on the single provider (back to SPOF). SMS could have been a good parallel option. Ideally also some physical control panel that triggers an alarm when any safety critical condition occurs. On the chlorine pumping system, that shouldn't be a dumb preprogrammed pump, it should come with it's own sensors and detection loop independent of any external system, something that proactively stops it before it breaches the safety limits.
We can assign fault, or we can ask which levers we can pull to make it better:
1. Can there not just be a light / siren right next to the gas sensors? Easy to fix, but it requires hardware changes on-site.
2. Could Microsoft have not had an outage? Hard to fix.
3. Could they use some better notifications systems like idk self-hosted ntfy.sh with a warning if the server goes down? Yes but nobody wants to pay for that.
Generally, for sensitive safety systems like this, Light and Siren are visible to those using the facility. So if problem developed, all patrons would be going "Umm, you know your sauna has flashing red light and siren going off?" after they all left the facility.
Yes, they still have to work but first off, both of those are extremely reliable systems, alarm circuits have extremely low risk of failure. Second, testing them takes 5 minutes a week/month, press the button, look for flashing light and listen to wailing noise.
It's inexcusable to think that email/slack or whatever is acceptable as anything other than notification system so people not in facility can be notified that alarms are going off.
EDIT: You are defending this setup and I'm not sure why. This seems email only setup seem indefensible.
Things do break, so all alarms need periodic testing, whether they consist of email and/or something else.
Whether it breaks because a relay has corroded due to years of service in a chlorine-enriched environment, or because O365 is down, or because O365 tightened up on DMARC requirements: It needs tested.
And it's not a binary choice. This isn't the World Cup, the Super Bowl, or Highlander. There can be more than one.
The alarm system can wear a belt, and suspenders. It can send emails, and it can flash a bright light, and it can also sound an audible alarm.
In the English language, the verbs usually associated when "email" is the direct object are, in no particular order: "read", "open", "write", "delete".
Sarcasm aside, in this case, the email should've triggered the literal lights and sirens. Preferably automated (tho in that case, why even go through email as middleman) but could also be an actual person flipping a switch.
You see this in software ops too: certain subject formats trigger a special ringtone or even a pager call. Emails are too subtle even with ALERT ALL CAPS SUBJECT LINES to be alarming.
Agreed, I'm not sure how it's acceptable to say "Email is exclusive option you can have" vs "We can email you when alarm is going off but light/siren will flash and it must be visible to those using the facility"
It's not the alarm that was dumping in dangerous levels of chlorine. Microsoft is in the line of causes to the lack of warning, but not the actual poisonous conditions.
I feel like there are things we aren't being told here.. what kind of automatic chlorine dosing system both knows that there's too much chlorine and continues to add enough chlorine to the point of being harmful. Something is fishy here...
'losing proposition' is irrelevant. The law is clear in this case, and the law makes Github's obligations exceptionally clear. By refusing to act, if the DMCA notice was valid, Github is breaking the law and forfeiting their safe harbor status.
Rust is just the language they happened to be working in. If you read through the LLM generated garbage it becomes clear that io_uring isnt the problem, their code was just slop / bad.
Curses, the TUI library, has been around since 1978. It was superseded by ncurses in 1993, which saw it's latest update in December of 2025. Both of them still work and can be used today, with the caveat that the official original curses has been deprecated since 95, but NetBSD maintains an updated version iirc.
I think the point is that breaking it up makes the cost more palatable. It's also easier to convince people to spend a bit of money for people they care about than a bunch for themselves that they don't strictly need. People also often struggle to think of gift ideas for birthdays.
True, but you're still buying an entire battery yourself in the course of a calendar year.
I love the spirit behind this but it's strange advice. I consider myself lucky to have a healthy roster of adult friends, and I still think getting 16 of them to spend significant money on each other's birthday would be a big ask to pull off.
Thanks, but I did read the policy. This is what they say: "It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create."
And later:
"There are very strict guidelines on LLM-generated code changes:
Pre-arranged, non-critical, high-quality, well-tested, and well-reviewed code changes that are originally created by an LLM are allowed, with disclosure."
That's a pretty limited wedge of allowed cases in my opinion.
They explicitly say that "create" is not the hard or valuable part. I suggest you actually read their policy instead of just the headline and then reacting to comments.
Darktable should already basically do all of this with their existing copy and import function. The only thing it won't do is erase the SD card for you, and generally I would recommend you just format it on the camera.
reply