Tootfinder

“In this work, we conduct a large-scale simulation of how users might delegate work to LLMs across 52 professional domains. We find that current LLMs are unreliable delegates: even frontier models corrupt an average of 25% of document content over long workflows, with sparse but severe errors that silently compound over time.”
Good to see the issue addressed explicitly, even though the results aren’t surprising—why would anyone expect LLMs to be reliable!?

“In this work, we conduct a large-scale simulation of how users might delegate work to LLMs across 52 professional domains. We find that current LLMs are unreliable delegates: even frontier models corrupt an average of 25% of document content over long workflows, with sparse but severe errors that silently compound over time.”
Good to see the issue addressed explicitly, even though the results aren’t surprising—why would anyone expect LLMs to be reliable!?

“In this work, we conduct a large-scale simulation of how users might delegate work to LLMs across 52 professional domains. We find that current LLMs are unreliable delegates: even frontier models corrupt an average of 25% of document content over long workflows, with sparse but severe errors that silently compound over time.”
Good to see the issue addressed explicitly, even though the results aren’t surprising—why would anyone expect LLMs to be reliable!?

I've finally finished pushing the latest update for #Gentoo Distribution Kernels, and requested their stabilization. This includes upstream releases 7.0.9, 6.18.32, 6.12.90 and 6.6.140; and Gentoo patch bumps 6.1.173_p1, 5.15.207_p1 and 5.10.256_p1.
All of these contain the v5 #Fragnesia patch. And yes, while the exploit is in the wild, upstream still hasn't merged a fix to the mainline kernel, let alone all the LTS branches. Of course, the patch keeps covering more holes, but it would really be preferable to do that as a followup instead of leaving people vulnerable and forcing us to keep rebasing it.
They also include a few reverts in 6.18 and 6.6 for broken PowerPC backports that upstream didn't apparently test. 🤷
We're doing our best, but I'd still recommend running the latest 7.0.x kernel, or LTS 6.18.x, because upstream is far from reliable with the backports.
#Linux

I'm conflicted about what to do

• Codeberg would screaming "I'm anti-genAI" which is something I really want
• git.gay looks cool and fun and gay, which is also something I really want
• self hosting would give me full control over the server configuration
• sereia.gay is a cool domain, but it mostly only works in portuguese (where git.da.sereia.gay is cooler). git.luana.dev.br is also an option (and cheaper, aka less likely to stop being mine), specially if I can set up more than a single domain to point to forgejo, but it isn't as cool.
• even if I set up a mirror, I'm undecided about whether to point it to codeberg or git.gay. Three-way sounds kinda abusive, idk?
• while I know forgejo is pretty lightweight, I'm concerned about having too much access in my NAS. Specially if I end up being ddossed by llms or if I ever do something people like. I have plenty of RAM from before the bubble, and it's modern but it's not the highest-end CPU out there. I'd also have to set up a reverse proxy, probably more reliable than my current oracle free tier one.
• I could get a VPS for the forgejo tho! Ive been wanting to get one anyway! (tho it would need a static ipv4)
• Tho, keeping it self hosted on my NAS would give me git push/pull even when offline!!
• Even if I keep a three-way mirror, which I might, I still need to choose a canon one to send links!
• Is it ok to accept PRs and stuff from either mirrors or do you need all but one of them to be read-only?

Pramaana Labs, which uses the LEAN programming language to build a deterministic verification layer on top of LLMs, raised a $27M seed led by Khosla Ventures (Russell Brandom/TechCrunch)
https://techcrunch.com/2026/06/17/pram

Pramaana Labs raises $27M seed round from Khosla Ventures to bring formal verification to AI | TechCrunch
Pramaana will focus on highly sensitive verticals like law, drug discovery, and tax preparation — where errors can be costly and reliability is at a premium.

Progress! I found that FIREFLY, one of my other lab machines, had the same issue but less severe.
I pulled and reseated the NIC, moved to another slot, cleaned the contacts with IPA, no luck.
But using setpci commands to forcibly downgrade it to gen3 x16 instead of gen4 fixed it. So it seems like due to some combination of card/CPU aging, dirt, loss, or damage somewhere in the system it can't reliably maintain a link at gen4 speeds but works fine at gen3 (and is able to comfo…

🚯 Junkyard Computing: Repurposing Discarded Smartphones to Minimize Carbon
#computing

Junkyard Computing: Repurposing Discarded Smartphones to Minimize Carbon
1.5 billion smartphones are sold annually, and most are decommissioned less than two years later. Most of these unwanted smartphones are neither discarded nor recycled but languish in junk drawers and storage units. This computational stockpile represents a substantial wasted potential: modern smartphones have increasingly high-performance and energy-efficient processors, extensive networking capabilities, and a reliable built-in power supply. This project studies the ability to reuse smartphon…

Spatial transcriptomics on an expanded dataset at the brain-electrode interface: exploration of variability and identification of novel biomarkers https://www.frontiersin.org/journals/neuroscience/articles/10.3389/fnins.2026.1852774/full "…

Frontiers | Spatial transcriptomics on an expanded dataset at the brain-electrode interface: exploration of variability and identification of novel biomarkers
The foreign body reaction to implanted electrodes in the brain has long been recognized as a major challenge impacting the performance and reliability of ind...

from my link log —
What the Code of Hammurabi can teach us about software liability.
https://danielmiessler.com/blog/what-the-code-of-hammurabi-can-teach-us-about-hardware-and-software-liability/
saved 2019…

What The Code of Hammurabi Can Teach Us About Hardware and Software Liability
The Information Security community has been debating software reliability for decades. Some say software is too advanced to place guarantees on it. And others s