The crook is an English speaker
A true Frenchman would have dubbed himself ZeroOctets.
839 publicly visible posts • joined 13 Sep 2017
CSI:OpenClaw
Quick-typing investigators prompt their super-secret defense AI to reverse-engineer evildoer rogue AIs in a continuous battle of good vs indifferent.
Episode 1: evil AI OpenSlaw enlists CaaS operators to push infant children further up the waiting lists of the local daycare by killing parents of children higher on the list. Guest stars include a synthetic version of Jimmy Saville.
Pull out some old paperbacks of Arthur C. Clarke short stories. Read them in chronological order.
After the mid 1970s as I recall he was gifted various writing machines (not quite computers but smarter than a calculator). You (or at least I) could see a trend in his writing with longer sentences and paragraphs as his adopted technologies changed.
Apparently he got a copy of Wordstar for his work on the 2010: Odyssey Two novel, apparently in the early 1980s. With a full screen (of perhaps 80x24 characters) his writing would change again.
Source: Google AI for some background info, so therefore you may freely abuse this non-copyrighted posting....
I was lured out of retirement twice.
The first time my $EX_EMPLOYER wanted a training course on how to interview and hire candidates. Trained some former colleagues on how I had hired them, and why! That was fun.
The second time was more serious.
Bid Manager: Hey can you help out on a bid? We need someone to work out the cost of the hardware.
Me: Maybe. What is the schedule?
Bid Manager: We need the costing in two weeks.
Me: And how much work or effort do you thing it is?
Bid Manager: About three weeks.
Me: Ha ha ha ha ha!
Another open source project rejects any AI-generated code, slop or not, on the grounds it is uncopyrightable.
Tin men don't have tinman-rights and cannot claim copyright on their output, you see.
Nor can they grant nonexistent rights to others.
Or file a lawsuit to defend those nonexistent rights.
When FSF, or Microsoft, or SCO catches up, will Linux be fragmented into GPL and nonGPL lines of code, and thereby tainted forever?
The current SOTA is quite impressive:
The Bun Javascript and Typescript compiler system was converted from Zig (535k SLOC) to Rust in a couple of weeks and $165k of tokens.
https://bun.com/blog/bun-in-rust
They switched in the "minor" upgrade from 1.3.14 to 1.4. Almost nobody noticed.
Impressive.
a different, compromised machine running identical software...
This sounds very much like: having control of a victim server, the "actor" can replicate the functions for his/her gain.
(Dis)proving that identical software is running on the "actor's" hardware is the key, and it's misdirected. If you let "actors" access your physical hardware, e.g. your Tesla or BYD, all bets are off.
Guest operating systems included.
(Spelling intentional).
Kurtzner also promoted a cluster environment based on network boot of multiple nodes and NFS serving standard /usr/bin executables. Called Warewulf.
It was a clever notion: nodes won't fail due to disk drive issues. I think he built a few 1000+ node clusters at LANL and elsewhere.
I ran it in my home lab (couldn't get $WORK approval to build it).
Verrrry interesting.
Wayyy back in the day, $WORK was inundated by Sun Microsystems folk who were pushing Sparc workstations on every desktop.
We were happy with NCD terminals and bigger servers.
Being an obvious VAX/VMS guy at the time, I distinctly recall teasing the distinguished Sun customer engineer about "You Unix guys and your awk, grep, and bark."
"What's 'bark'?", he innocently asked.
Mission accomplished.
OpenBSD does not corrupt filesystems on shutdown. That would be silly.
I regularly run 3 OpenBSD guest VMs with VMware Workstation on Windows. What with Windows and it's software crappi^H^H^H^H^Hcomplexity my laptop gets irregularly rebooted without notice quite often. And monthly with notice. And either I don't know how or VMware can't tell OpenBSD guests to shutdown or suspend on a Windows reboot event.
After 3 years of this I've only had to invoke fsck manually once. And lost no files.
Log-structured filesystems are not a panacea, they just reduce the odds of failure (or improve the recoverability).
Clearly they are not paying attention.
https://zerodayclock.com
The last graph is a "survival curve" showing which CVEs are not yet exploited. So far in 2026, 90% of CVEs are exploited within a week.
(This is exploitable CVEs, around 1% or 2% of the total. But with AI and reverse engineering published patches, discovery of defects and creating matching exploits is pretty much automated.)
There is rumour that Google Drive used to compress ("improve disk footprint of") files without warning or notice. Transforming from jpg to other formats, or png to xyz to jpg. I can find a few complaints but no evidence.
If you value your files and their cryptographic-strength checksums, and you *insist* on using the Cloud, I suggest using tar or zip.
Pick none.
This article defines a checklist of what to do to achieve failure:
- hardwire one vendor to the request for proposal
- failure to record significant decisions (analysis of three options)
- don't have staff sufficiently technical to review the vendors plans ("lack of preparation")
- don't understand the complexity
- don't do risk assessment or mitigation
- change scope mid-stream
- rely on two, count 'em, two system integrators
- rely on customization of a rapidly-changing vendor product suite
- let management make technical go/no-go decisions
And they succeeded.