@mattgriffin @zzt obligatory link: https://softwarecrisis.dev/letters/llmentalist/
Zine 6 for Fall 2026 is out! You can check it out here:
https://hattiesburg-alt.neocities.org/
and you can download and print by clicking on the “zines for download” tab.
I really enjoyed making this issue especially with my friends David and Andie. This is the last Hattiesburg Alternative issue I’ll lead since moving out of Hattiesburg but I hope to be reviving Baton Rouge Alternative now that I’m back here. Hattiesburg Alt will continue though with David and Andie who always have my support.
Admitting your whole industry is based on the circular finance, fed by fraudulent exports, set up by a midlife crisis in a leather jacket.
Economists Horrified by What AI Industry Has Done to Global Economy
https://futurism.com/future-society/imf-economist-horrified-ai-industry-global-economy
"We have a world economy that is standing on one leg, on the AI leg."
me can't order salad ☹️ too hard. need computer to order salad
#Forgejo 17.0.2 and 15.0.12 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
The Trump administration has a plan for January when Democrats take control of the House and Senate and start conducting oversight.
And that plan is … contempt of Congress at scale!
White House Counsel Will Scharf laid it out in a memo obtained Monday by PBS News:
“Executive Departments and Agencies must obtain approval from the White House Office of Legislative Affairs (OLA) and the Office of the White House Counsel (WHCO) before any agency personnel may agree to appear before any congressional committee,” he wrote,
-- blithely alluding to “the established White House consultation process” and promising that further guidance will be forthcoming.
That’s horse hockey
— if the process were “established,”
the memo would be unnecessary.
In reality, this is a radical departure from prior policy,
contrary to both law and precedent.
And it comes as Attorney General Todd Blanche and Scharf himself
(along with a US Attorney in Texas)
are threateningto criminally prosecute Democratic legislators for doing their jobs
yo ecosia, Internet Archive, and everyone else doing a shitty fucking greenwashed “climate” LLM: https://www.theguardian.com/environment/2026/nov/16/ai-models-fallible-denial-climate-science-unesco-cop31
not that it wasn’t fucking obvious for many reasons that a climate LLM is a horrible idea, but here’s yet another obvious reason why
no, going all-in on the planet burning shit tech isn’t good because it’ll solve climate change in the end. it fucking obviously won’t
There's a lot said about LLM-generated vulnerability reports, but LLM-generated bug reports in general are a huge problem because of the underlying economics. Every bug fix has an obvious benefit (the bug is gone now) but has some additional costs:
First, there is the opportunity cost. You have to spend time reviewing the bug, creating the fix, and reviewing the fix. That is time that is spent on that is not spent on other things. If a bug has no security implications and is almost impossible to trigger, then it should be low priority. Writing bug-free code is impossible. Even the best formal verification techniques don't save you when your specification is buggy (to give a concrete example: EverCrypt was formally verified with the property for temporal memory safety that no object was accessed after being deallocated. The spec forgot to mention that objects should be deallocated at some point). Fixing bugs is always a tradeoff and there are almost certainly bugs that will impact more users that you could have been fixing while you were instead triaging and fixing something an LLM produced.
Equally importantly, the bug fix may introduce additional regressions. This is especially true for LLM-generated fixes. I've had several bug reports where someone has had the LLM generate a test case and then use that (plus the rest of the test case) as the fitness function for generating a fix. This has a number of common failure modes. Sometimes the test case triggers a specific failure path, so you can fix that path without fixing the underlying root cause. Sometimes the test case is entirely spurious (for example: API misuse) and the fix introduces some significant performance regression, where the original failure mode was a deliberate choice to crash in particularly unusual cases rather than taking a 10% performance hit in the common path.
This isn't new to LLMs. We saw exactly the same thing with static analysis. If you ran a new static analyser on a large existing C codebase, you'd typically see thousands of reports. Some were security issues. Some were real bugs that would likely affect users. Some were real bugs that would be unlikely to ever be triggered in the real world. Some were false positives. Going through all of them and finding the ones that actually mattered was incredibly hard.
The problem is never 'find more bugs', it's always 'prioritise the bugs that actually matter'. Some of the LLM-based approaches are helpful here for providing an exploit path, but LLMs are typically too flexible here. They'll often generate test cases that are outside of your threat model, or which misuse APIs in a way that allows callers of a library to break themselves (which they can easily do without the library). So even triaging from the test case is tricky.
Unfortunately, determining the real-world impact of a bug depends on a lot of extrinsic knowledge. LLMs will try to infer this but it varies hugely between codebases and so a statistical approach often gives a very wrong impression.
It's so depressing to see people go from being really excited about hobbies and interests (games, arts, technology, space) to seeing them absolutely hate engaging with it now.
... And it's all because some fuckshit wealthy assholes have created garbage that ruins it or flooded everything with something that wouldn't be garbage if not for their abuse of it (like, satellites don't seem inherently horrible to me, but some bastards and their ghoulish company have decided we need thousands of them for bullshit reasons).
@EUCommission To answer my own question, if you’re not a fascist in the EU, consider registering a TLD from a non-US registry with no ICAAN registry contact:
EU/EEA ccTLD registries (non-US operators, no ICANN registry contract):
• .de – DENIC eG, Frankfurt (cooperative)
• .nl – SIDN, Arnhem (foundation)
• .fr, .re, .yt, .pm, .tf, .wf – AFNIC, France
• .eu – EURid, Brussels
• .be – DNS Belgium
• .at – nic.at, Vienna
• .cz – CZ.NIC, Prague
• .pl – NASK, Warsaw (state research institute)
• .se, .nu – Internetstiftelsen, Sweden
• .dk – Punktum dk
• .fi – Traficom (Finnish state agency)
• .it – Registro.it / IIT-CNR, Pisa
• .es – Red.es (public body)
• .pt – DNS.PT
• .ie – IE Domain Registry
• .gr, .ελ – ICS-FORTH, Crete
• .hu – ISZT · .ro – ICI Bucharest · .bg – Register.BG · .hr – CARNET · .si – Arnes · .sk – SK-NIC (owned by UK-listed Team Internet) · .lu – Restena · .lv, .lt, .ee, .cy, .mt – national academic/foundation registries
Nearby non-EU, non-US: .is (ISNIC, Iceland)
It’s also important to use non-US payment systems like SEPA, Aero, national payment systems – iDEAL (NL), Bancontact (BE), Blik (PL), Bizum (ES), MB Way (PT), Swish (SE), MobilePay (DK/FI)) – or non-proof-of-work (because environment) cryptocurrencies.
If you have any other suggestions, etc., please reply to the thread.
"‘AI’ might be the end of our careers"
I never planned on becoming a software developer, and these days it feels like my exit from the industry might be similarly unplanned.
https://www.baldurbjarnason.com/2026/08-ai-might-be-the-end-of-our-careers/
Following #Codeberg issue, it is time to remember that, if you manage an important service, you must have two domain names, in different TLDs and different registrars, and have them pre-configured and pre-announced so you can switch rapidly.
The domain is slowly recovering. Many users are able to connect to our systems again. Some might need to wait for DNS propagation.
Thank you so much for your patience. We're sorry for the serious disruption.
We haven't yet received an official response from Namesilo's abuse department about the incident.
There's no safe .tld when ICANN can just block things.
There's no "have a spare domain" when your domain is your login email .tld for hundreds of websites. Especially in the age of "We've sent a code to your email".
DNS is broken and today we just had a glimpse of that.
🤞️for recovering your domain.
Adding 217.197.84.140 to /etc/hosts works nicely for the time being.
Re last boost:
Totally agree - I don't believe in purity as a whole. I think everyone fucks up and people are messy.
To me, it's about how you deal with the fuck-up and learn from it.
I hate LLMs, but if someone has used AI and have now stopped, I'm personally not gonna judge them for it.
Having been part of some community organizing in the past and present, this balancing act has always been the most exhausting one, but in my opinion, the best path to take.
#ShlaerMellor, #FunctionPointAnalysis, #punk, #environmentalist, #unionAdvocate, #anarchosocialist #freeSoftwareAdvocate #cooperativeLife #noLLMs
"with a big old lie and a flag and a pie and a mom and a bible most folks are just liable to buy any line, any place, any time" - Frank Zappa