upvote
deleted
reply
doesn't change the value of what's writen, if true and actionable that's all that should be needed
reply
It has "potential", not "value".

Also in this case, a "missed potential" if it eventually fails to reach anyone.

reply
Value is more than just iron something is made from. How it's shaped and presented is just as important
reply
No, it is not "just as important" as the underlying information.
reply
It actually might be far more important. You are a lot more important than the molecules that you are made of
reply
It can be, if the intent is for transmission of information or truth. This is at the heart of any propaganda, for example, where the style and medium of messaging are of top importance. Or see the “abc conjecture” and how a gap in communication means that we (or, the math community) are not sure if the conjecture is true or not. The “underlying information” is static, but is essentially null if it cannot be communicated.
reply
If it was valuable a human would have been able to communicate it in a few lines of text. Using a LLM to blast slop devalues everything and communicates little. A drunken twitter rant has more ability to convey information than sloppy blog posts with 3 pieces of information per sentence and a load bearing attitude.
reply
Get hip to it, daddy-o.
reply
these squares aint hip to the jive, I know that!
reply
Just ask the clanker to read it buddy, you’re already behind /s
reply
It's inverse compression!
reply
It kind of does, the OP could have just saved themselves the tokens and posted a 130 word summary on x/twitter that would have been just as useful.
reply
OP (me) was not the author but I generally agree - a well written or at least better edited summary as a preamble would have been preferable, however it's educational to see the process and a potential repro of the issue don't you think?

Of course I imagine they used AI to find the exploit, and the documentation may have come as an output from that process.

reply
Like someone have said very long ago, "If."
reply
well it's 404 now
reply
The LLMs find the security issues, the LLMs will write the reports and the LLMs will fix and patch them.

I guess its time for all of us to step aside, leave space for somebody who knowns what they are doing, and go fishing...

reply
We're all living in the story of mel.

At first, there were just big logic blocks and storage that did as they were told.

Later, in hardware, there were all sorts of optimizations built in where the logic would do its own thing -- so you'd get caches and speculative execution and even on-the-fly conversion from one instruction set to another.

This abstraction was also piled onto the runtime -- you'd write machine code, then assembly, then higher level languages; eventually you'd run in interpreted or just-in-time generated bytecode (hello to Java from UCSD p-System from the 70s and Burroughs machines in the 60s). And of course... operating systems...

Now, we've got machines reading source code (and machine code, and everything in between) and they've got some ability to thing the thing to make it thing. Sometimes correctly (enough to pass existing tests) and sometimes without the ability to express to the human what the thing they thinged was.

But, we're all living in the land of mel and for some it's always been better to go fishing than to pretend to participate.

reply
The "hardware doing its own thing" can be understood. There was this big ideological movement called ECS in the 2010s that was about writing software in ways that actually run well on hardware.
reply
And this way only LLMs can learn from these vulnerabilities, making it even more likely that the next one will be found by an LLM.
reply
LLMs currently don’t learn, at least in the way most people mean, but I assume you mean the trainers will incorporate the knowledge in future releases.
reply
Glad to see this is the top comment. This is written by Claude, I know because I talk to Claude for 8+ hours a day, and it says stuff like this. I stopped reading the article because of it.
reply
And now it seems to have been pulled (getting a 404).

Perhaps they are rewriting it with less slop?

The CVE itself: https://www.cve.org/CVERecord?id=CVE-2026-99312

reply