Fun story coming:
#libsodium has a #NoAI policy: https://github.com/jedisct1/libsodium/blob/master/AI-POLICY.md
The author made a commit using Claude: https://github.com/jedisct1/libsodium/commit/4f44abfed4c5ee7e1667e3fdf46d9253342cca69
Someone pointed it out in a discussion. The commit got force-pushed over, and the discussion was deleted: https://github.com/jedisct1/libsodium/discussions/1564.
Funny enough, GitHub still flags the repo.
I suppose at this point libsodium should be assumed to be #slop, with author sweeping the fact under the carpet.
By the way, does anyone have any clue why there's no "archive the page" button when I paste the commit URL to Internet Archive?
Do I know people in Lisbon that would be interested in arranging an event around "Digital Solidarity" (the book, @alineblankertz and I published early September 👉 https://www.structural-integrity.eu/our-book-is-out-digital-solidarity-on-overcoming-capitalist-technology/)?
I will probably be there in November or December and would love to engage with groups and people about post-capitalist tech!
Rise of Palestinian parties in Knesset will redraw Israel’s political landscape - https://www.theguardian.com/world/2026/oct/27/palestinian-parties-knesset-election-exit-polls-redraw-israel-political-landscape glimmer of hope
#Microsoft faces potential vote: Shareholders curious about its plans to tackle emissions - https://www.theregister.com/on-prem/2026/10/28/microsoft-faces-potential-vote-shareholders-curious-about-its-plans-to-tackle-emissions/5305953 " #Greenhouse gas output has risen dramatically since the company promised to become carbon-negative by 2030 " aren't we all?
“Signal your virtues | Go Make Things”
Wow. Zencastr's built-in transcription is quite possibly the worst I've tested. Filled with fabrications in a 10m test recording.
It would have helped if there was an obvious way to:
1. Set the language.
2. Turn off automatic translation.
But I get the feeling the implementation is so vibed they might not be aware of what it's doing at all
‘All these claims of math proofs clearly and in fascinating clarity explain just how little the people behind these products understand anything.
_A proof is simply the residual artifact of a process, an inquiry into a problem. It often distills years, if not decades, of hard won knowledge into a mechanism to “check” that this knowledge is likely correct._
LLM proofs are a tabula rasa. A hollow meaningless performance devoid of any substance.’
Still remembering when the CEO of #Substack called me a loser blogger in a forum for keeping this list. https://sightlessscribbles.com/posts/substack/
when a standard is basically finished, its standards org remains.
it then gets infested by weirdos, careerist parasites and weirdo careerist parasites.
this is how JPEG put forward a blockchain standard in 2018, and how w3c (logo: dick and balls) has now done this:
Ottawa is investing $1.5 billion in new co-op housing. That federal funding should strengthen member communication, board training, oversight and accessible dispute resolution.
New housing co-ops need stronger democratic safeguards: https://policyoptions.irpp.org/2026/10/co-ops-governance-safeguards/
Social.coop meetings: https://link.social.coop/calendar
Organizing Circle
Thursday, Nov. 5, 2026
7:00 AM PT | 10:00 AM ET | 15:00 UTC
Social.coop members are welcome to observe this and all upcoming meetings.
@rhelune I suspect a big part of it is sunk cost fallacy. "Waaaa! Nooooo! You have to use this because we've spent so much money on it! If you say it isn't helping then that means I'm not a big-brain money guy! Waaaaaa!"
Why are so many workplaces trying to force employees to use generative "AI" (chatbots, coding agents), even by threatening their livelihoods?
#AI #noAI #LLM #LLMs #vibeCoding #technofascism #workersRights
I don’t intend to call out anyone on here with this, but it’s important to reflect:
- I was told that both the slop PHP patch and the slop kernel patchset were high quality code with very few telltale signs of slop
- both of them had a bunch of telltale signs of slop (and again I’m really not trying to call anyone out for this, please consider this a postmortem)
- both were rushed through with very little to no understanding of the problem they were solving
- both were highly publicized but solved little to nothing: the linux patchset was flawed and decreased performance outside of microbenchmarks, and the php patch fixed an issue that was hard-to-impossible to exploit in practice with a gigantic number of slop-looking changes when another fix (abort on OOM now and gradually patch exploitable cases) was available, but nobody considered it because nobody considered anything
just some things to consider going forward. you absolutely don’t gotta hand it to any of these people.
@davidgerard LLM generated tests - they pass, so they must be good
@davidgerard i love qualitq
slop tests always work so amazing every time, like when torvalds slopped out a performance regression and the tests went “looks good boss”
@rhelune I've been quite happy with IVPN since ditching Proton. Off the top of my head I think it matches what you're after, but I haven't double-checked.
@marcusxms I was born in Yugoslavia where workers' self-management was the norm. Factories to the workers!
#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