Most US population centers are in places east of the point in their time zones where the sun is overhead (or due south) at noon, and being a bit west is better than being a bit (or very, for New England) east. This means that DST is mostly the right UTC offset for the wrong reason: Boston should be on Atlantic Standard Time year-round, but Eastern Daylight Time is a name for the same clock setting that is already used there sometimes, so that's easier to legislate. Of course, the people who live west of their true noon line don't think permanent DST would be good, but the fact that we should have no DST and a different map is too nuanced for the position that there's got to be a single simple answer as to how to fix everything, regardless of the situation.

I don't think this is trying to get back into the US market. OnePlus is banned because it's part of a Chinese corporation. OPPO is... that corporation. It's not going to confuse any regulator who found something to complain about with OnePlus. This is more likely a mundane tactic of being liked in Europe for phones and wanting to expand that reputation to the parts of the organization that sell other consumer electronics.

You use your coal to make steel, which needs the carbon from the coal for the alloy. Not all use of coal can be replaced by other electricity or heat production, even if getting blast furnace temperatures out of a nuclear reactor weren't considered bad.

It's worth noting that nuclear reactors don't really explode in the way people think of. What they can do is turn into radioactive lava, melt through the floor, and release the highly carcinogenic dust from their system into the environment. They're generally big water heaters without pressure release valves (because the water has the carcinogenic dust in it), so they can burst like any water heater, and they contain zirconium, which reacts with steam at high temperatures to release hydrogen gas, which can make fireballs, but the accident risk is much less about a shock wave destroying the site than airborne radioactive particles getting out. And, even if the reactor design is incapable of producing enough heat to damage itself without first shutting down, you still have to worry about whether the site is safe enough from external damage. The traditional thick concrete walls are as much about keeping runaway trucks out as keeping steam explosions in.

It sounds to me like the input to the algorithm is truly random, but not unbiased, and the algorithm perfectly unbiases output from the particular source they are using. The rest of the article goes into the type of flaw they're addressing, and talks about very slightly unfair dice, which you could correct, but you'd need to know exactly how unfair they are, and you're always going to be very slightly wrong and end up correcting not quite perfectly. The obvious quantum RNG is to generate polarized light and measure it perpendicular to the polarization, but you'd still need to get it perfectly perpendicular. It sounds like they've built something that doesn't rely on precise alignment to give a known distribution, which they can then use to unbias the output perfectly.

It's pretty close to being an MP3 marked as a BMP, actually. It's the result of taking a reversable transformation of the audio signal that separates out the different perceptible components and then discarding the ones that matter least, and keeping the important ones in a convenient form for accessing them. It's the first step you'd take if you wanted a computer to identify speakers or what they were saying. The only part that's image-related is making the diagram, but getting back to the data is just taking the pixel values.

I suspect that they started using spectrograms in reports at a time when getting back the data from the image would have lost too much quality to printing and scanning to hear anything as quiet as voices, but PDFs with lossless images retain all of that.

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.

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.

It uses VRTX, reportedly. Linux wasn't suitable as a real-time OS when the Hubble was designed, or really even when the Hubble got the 486 installed in 2009.

The LitleLLM packages were comprimosed on Tuesday. The packages compromised today were telnyx 4.87.1 and 4.87.2. It's the same root cause: credentials exposed to a compromised version of Trivy earlier were used to make an unauthorized release of a compromised version of a different package.

Until recently, you could get the text of national weather service guidance by telnet. It was about the right level of protocol to provide plain text to a terminal with enough information to paginate it and enough input to pick an airport code.