JUDGE: The jury has sent a question and the answer is no, the death penalty is not "available for both sides" please return to the jury room and limit your consideration to civil damages.

JUDGE: No, a “light maiming” is also not acceptable, nor is “getting medieval on their asses.” Please constrain yourself to statutes approved by this court.

JUDGE: A further follow-up question from the jury, and no we cannot 'dunk them in a lake and let God decide, like they used to do with witches'. That has not been considered a valid means of determining guilt for several centuries at least.

JUDGE: The jury has sent another question and the answer, again, is no. "Excommunicado" is not real - that's only a thing in the John Wick universe. Civil penalties DO NOT encompass revoking all protections under the law for Mr Altman and Mr Musk.

JUDGE: Court reporter, please note that the jury's latest request, quote, can we let them hang by their thumbs for a few hours, end quote, is also denied.

Nuclear reactors use most surface water, not ground water.

Datacentres are no pickier. You can even cool a datacentre with saltwater, you just need a heat exchanger.

Also, closed loop does not evaporate. The loop is not closed if stuff escapes from it.

You're arguing with the actual terminology used in the nuclear industry. "Closed loop" or "closed cycle" designs have the water pumped in a cycle through cooling towers. The towers lose water to evaporation, taking heat with them, but the rest of the water is returned to be reheated again. "Open loop" or "open cycle" designs have no cooling towers. The water is heated and just discharged hot. They consume much more water (over an order of magnitude more), but most of that is returned. Closed loop are more common, but you see open loop in some older designs, and in seawater-cooled reactors.

"How often do you think I print?"

Seemingly not very.

I've printed many hundreds of kg on my P1S, thanks.

I do not consider having to write data out to a card and transport it back and forth between the printer and the computer to be the pinnacle of convenience. That's something that would be considered embarrassingly inconvenient for a 1980s printer, let alone a modern net-connected device. And it's designed to be inconvenient for non-cloud prints for a reason.

I suspect part of it is that the mitigation for DirtyFrag covers it, so everyone who blocked all the modules in question when that had only an incomplete patch probably hasn't unblocked them yet. I think this is the 4th patch for these modules, and only got a new name rather than just "there's still a way to get this code to do the wrong thing" because a different outside team found this one.

Also, anything sounds big when you put it in gallons. Doesn't sound so big when you mention that's 92 acre feet, the amount used by less than 20 acres / 8 hectares of alfalfa per year. Or when you mention that a typical *closed loop* 1GW nuclear reactor uses 6-20 billion gallons of cooling water per year (once-through uses 200-500 billion gallons, though most of that is returned, whereas closed loop evaporates it)

I don't think it has anything to do with that. As soon as I saw the headline, my mind went "cohort study". And sure enough, yeah, it's a cohort study. Remember that big thing about how wine improves your health, and then it turned out to just be that people who drink wine tend to be wealthier and thus have better health outcomes? And also, the "sick quitter" effect, where people who are in worse health would tend to stop drinking, so you ended up with extra sick people in the non-wine group? Same sort of thing. This study says they're controlling for a wide range of factors, but I'd put money on it just being the same sort of spurious correlations.

"I just put my models on a usb drive then plug said drive into the printer."

You must have a lot of spare time on your hands.

"It works great locally" - Um, no it doesn't?

They've made a nice easy-to-use ecosystem. For $400 you can get a P1S that supports adding an AMS, auto bed leveling, enclosed-chamber printing, high precision, high print speeds, and 300/100C nozzle/plate temps, and has an easy cloud print service and a robust ecosystem of models you can just download and print with no extra config straight from the app.

But yeah, their behavior is increasingly entering bad-actor territory. I wonder how long it'll be before they lock entry-level printers into their branded filament?

Yeah, and the person who released the information first was operating in an "if I noticed this, doing only as much as I'm doing, surely attackers would also notice" mode. Possibly some patches these days are sufficiently obvious as to their correctness and also effect that they should first become public as a set of stable releases. This was a kind of special case, as CopyFail was the combination of some code doing something strange with one user not being prepared for it, and fixed the user. If there are other users that also aren't prepared, fixing them isn't going to be subtle.

How shadows and reflections move when you're 10 milies from a mostly flat surface a thousand miles across is legitimately hard to analyze for a visual system that evolved on the ground, especially if you throw in small periodic surface orientation variations. Given how complicated it is to explain rare rainbow-related phenomena like sun dogs, it would be surprising if we'd identified and explained everything that can appear when flying above the ocean.

While you're at it, you also need to block installing esp4, esp6, and rxrpc, for, y'know, reasons.

According to the article, they (by way of their cloud provider) had DR backups, which they were able to get restored. But getting offline backups restored takes longer than the SLAs they give their customers and loses some data that hasn't been copied offline yet, which is why they also have backups that are complete and immediately available, using the API key that the attacker -- sorry, AI -- found in a file it wasn't supposed to have access to.

Verizon's 2 Gbps Fios home service doesn't support IPv6, due apparently to them picking hardware for this particular service that doesn't handle it. Their other service does handle it, including slower home Fios, but not that in particular.