pull down to refresh

His AI shit is a red herring, I think. From what I understand, the intended random number generator was simply not called? Because of a developer mistake that linked to the wrong RNG library entirely, one that was intended for... testing and not real-world usage?

Nvk shifting the blame to AI here is cute and certainly in line with the times, but it sounds like yet another mistake best attributed to boring everyday "Human Stupidity," and that should've and could've been caught with a modicum of due diligence.

Piling this into the AI narrative seems to distract from the negligence.

I also don't understand how they didn't have within their testing a process for ensuring the seed was really being hardware generated, and not relying on the software fallback (which should've been disabled in production in the first place)

reply

I've seen something similar-ish once, spotted in a cycle test, where a component didn't have any wear at all, but that turned out to be a test scope error, not a firmware bug.

which should've been disabled in production

That snippet describes exactly what last night's hotfix does.

reply
reply

Oh wow, my favorite pastime, reading slop. Thank you for your generous contribution to my hobby, anon, you're awesome.

reply
340 sats \ 0 replies \ @Aeneas 31 Jul

Exactly.
Oh but I'm sure if they would've been able say "Fucking AI did this!" about the failed O-ring seals on the Space Shuttle Challenger, they would have.

reply

Blame shifting.

reply

A new AI use case: scape goat.

reply

isn’t that why everyone prefaces everything with “Claude said…”?

reply

Actually all vulnerabilities are a human error. That doesn't prevent them from existing. And theoretically if a system is built without any error, no hacker can attack it.

reply