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.

"Taikonauts" is not a word.

...what I paid for it a decade ago.

It still does the things I wanted it for then, but I can't say I've really used any of the new features added over the last decade, which if anything pushed "just stream my media" to the background.

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.

$10k subsidy went away, of course vehicle sales went down! Next year Ford is releasing a $30k electric pickup truck, the Ranchero, then it will go back up!

If batteries and EV components were to stay the same, then I could totally see American car manufacturers sticking it out with ICE cars, despite EVs having advantages in some ways. But we all know the technology is getting cheaper and better, and not having EV plans would be tantamount to giving up on being anything more than a niche company.

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.

I get carsick easily and throw up from rollercoasters that my little kids can take. You get sick the first time you do VR, but your brain very quickly acclimates and like by the 4th time I used it I didn't feel VR sick at all. YMMV.

I'm sorry to hear it, as the Oculus/Meta Quest is one of those few technologies that makes you think "holy shit!" It really is an amazing experience, it feels like living in Science Fiction. Then the best actual use is playing Resident Evil 4, a Gamecube game from 2005. I also enjoy taking 360 videos.

I thought Apple would be able to take this amazing technology and find some practical application for it...and I see I was wrong! I still think it can happen someday.

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.