En plots was er de drang om iets te schrijven. Het is niet nagelezen, het is gewoon mijn gedachtenstroom vandaag, op mijn blog. Klinkt het niet, dan botst het, en dat is ook oké!



fertiliteit

Ik kwam daarnet deze video tegen van de Financial Times:
https://www.youtube.com/watch?v=6lFXmDk-tps

Het gaat over de correlatie tussen smartphonegebruik en het aantal kinderen dat geboren wordt. Hun theorie is dat het aantal vrouwen dat kinderen krijgt daalt, omdat ze meer in de smartphone-influencer wereld leven dan dat ze mensen in levende lijve ontmoeten. Ze maken ook direct de stap naar meer zelfmoordgedachten bij hevig smartphonegebruik.

De paper zelf is van april dit jaar en kan je hier vinden (wel 63 bladzijden):
https://homepages.uc.edu/~moscoshn/Personal_webpage/papers/Smartphone_web.pdf

Ik ga ervan uit dat de cijfers kloppen, dat er inderdaad een correlatie is tussen het invoeren van de smartphone in een land, en de problematiek om een partner te vinden om kinderen mee op de wereld te zetten. En het klopt uiteraard dat iemand die verslaafd is aan Instagram/Tiktok/... een ander beeld heeft van 'de gewone mens' dan iemand die nooit naar deze media kijkt. Maar er is meer aan de hand.



veiligheid

Er is veel angst vandaag, meer dan in de jaren 80 toen de criminaliteit veel hoger lag. (Noot: Er zijn nu meer aangiftes van misbruik, maar het gebeurde vroeger wel vaker denk ik.) De media, zowel de klassieke als de sociale media, lijken mensen uitsluitend in emoties te duwen: bang, bedroefd, boos en soms een keer blij. Wees bang voor mannen, voor terrorisme, voor hoge prijzen. Bedroefd voor ongevallen met kindjes. Boos op Poetin en China, en Israel. Cijfers en statistieken tellen niet meer, de anekdotes vol emotie krijgen alle aandacht. Waar in de jaren 80 de krant nog schreef: "Er zijn 700 bedrijven failliet gegaan deze maand, en 900 nieuwe opgericht!" wordt alles na de komma vandaag niet vermeld. Mensen bang maken levert immers meer 'clicks' en 'views' op.

Zie bijvoorbeeld vandaag op VRTNWS over 'Marie' en 'Katrien', ik durf het geeneens te lezen na 'Valerie' enkele dagen geleden. Ik was kapot na dat Valerie-verhaal, zucht. Die journalist had dat wel verdomd goed geschreven, de beste horror kan er niet tegenop!! Dat soort gruwel verhalen voor vrouwen, veroorzaakt door mannen, is de laatste twintig jaar schering en inslag. Alsof het in mannen-genetica zit.

Lezen op eigen risico:
https://www.vrt.be/vrtnws/nl/2026/06/22/getuigenis-stiekem-genomen-naaktbeelden-fora-en-justitie/

Het deed me denken aan het huidige onveiligheidsgevoel dat (vooral jonge?) mensen hebben. Ja er was ook criminilateit en wreedheden en misbruik in de jaren 80, maar we zagen dat maar eenmaal per dag op TV, tijdens het nieuws om 19u30. Als dat al in het nieuws kwam. Vandaag de dag is er minder criminaliteit in België(*), maar al wie vaak op een smartphone kijkt (incluis de vrtnws app), wordt er wel veel meer mee geconfronteerd. De TV had natuurlijk ook dat effect, maar dat was toch veel langzamer, veel gradueler en jarenlang enkel 's avonds in familiale kring. De smartphone is er als je wakker wordt, als je op de WC zit, als je op de bus wacht, als je niet kan slapen, kortom altijd, en zeker al die tijd die je *alleen* doorbrengt.


(*) Ik vind geen goeie cijfers over de evolutie van het aantal misdrijven per jaar sinds de jaren 50-60-70-80 tot nu.
https://www.vrt.be/vrtnws/nl/2023/06/21/studie-nicc-criminaliteit-in-belgie-daalt/



vertrouwen

Toen ik pas mijn rijbewijs had (1989), heb ik honderden lifters meegenomen. Zo goed als altijd tieners, de helft of meer waren meisjes. Zeker in mijn unief periode dat ik vanuit Leuven vrienden afzette in Zoersel, en dus vrijdagavond laat via Sint-Antonius, Westmalle, Oostmalle naar Wechelderzande reed. Ik heb die rit zelden alleen moeten doen, en vaak waren dat leuke gesprekken. Ik had zelf ook jaren gelift, honderden keren meegereden met vreemden, nooit was er enige spanning. Ik heb in vreemde auto's gezeten terwijl de eigenaar een winkel binnen ging, sleutels erop of zelfs met draaiende motor. Dat vertrouwen hadden de volwassenen toen in een onbekende zestienjarige. Logisch dus dat ik een 'pay it forward' mentaliteit had toen ik zelf een rijbewijs had. Gisteren was een vriendin hier heel de dag klimaatvluchteling, die rijdt nog rond met haar auto. Ze zei dat het al twintig jaar geleden was dat ze nog een lifter had meegenomen. Er zijn ook gewoon geen lifters meer.



cancelcultuur

Er zijn uiteraard veel alternatieven zoals Uber/deelwagens/deel-whatever, maar toch. Dat soort vertrouwen in elkaar is weg. Maar dat heeft evenveel te maken met mobiliteit als met de smartphone. Toen wij vroeger 'uit' gingen was dat vaak naar fuiven van 'Union Servet' in Pulderbos/Westmalle/Sint-Antonius. Daar was je dan, op een fuif met een paar honderd mensen, maar ook met je vrienden, je buren, je klasgenoten, de mensen van de harmonie, ... m.a.w. je was in een super veilige omgeving. Je kon als vrouw het 'risico' nemen om met een stoere/stoute man te dansen want je wist dat als die iets te ver ging, dat zowel jouw vrienden als zijn vrienden tussenbeide zouden komen. Je hield elkaar in 't oog, wie gaat met wie buiten, je kende van vele mensen de ouders en wist waar ze woonden. (En die ouders kenden ook uw punten van uw laatste test Frans of wiskunde!)

Dat is op twee zaken een groot contrast met vandaag: Ten eerste ben je op een Tinder/Bumble/Breeze-date vaak alleen, in een vreemde omgeving, wat niet goed is voor je veiligheidsgevoel. Ten tweede is er de cancelcultuur en kan elke misstap leiden tot een eeuwige verbanning. Als op de Servet-fuiven vroeger iemand het uithing, dan kwamen zijn vrienden er wel tussen, en waren die slecht gezind op hem, of toch ene, omdat die hem naar huis moest brengen en dus vroeger weg was van de fuif. Maar... die gast kwam de week nadien wel terug, en kon daarbij aantonen dat die zich wel kon gedragen en nen toffe zijn en een lief vinden.



smartphone

Ligt dat aan de smartphone? De smartphone kan handig en nuttig zijn, zonder schadelijk te zijn. Je kan er je busabbonement op zetten, allerhande betalingen mee doen, mooie foto's nemen, je agenda erin zetten, je moeder mee bellen, de weg naar elkaar vinden in de stad, een taal studeren, boodschappenlijst in spreken, en nog een dozijn andere leuke, toffe, boeiende, leerzame, nuttige dingen.

Maar dat wordt, in uren per app gerekend, nauwelijks gedaan. Of dat is toch wat ik zie als ik eens in de bus of in den tram zit, of in een wachtzaal. Ik zie mensen scrollen, scrollen, scrollen, door een eindeloze scroll van video's, drie a vijf seconden per video en hup devolgende, video's die absoluut niks te maken hebben met hun familie, hun vrienden, of uberhaupt enige link hebben met echte mensen. Gooi er nog een hoop reklame tussen (mooi in beeld gebracht hier: https://youtu.be/e9dZQelULDk?t=141 ). En ja, dan leef je niet langer in een wereld van gewone mensen, dan leef je in een fantasie.



doemscenario

Is dat erg? Is de wereld naar de knoppen? Nee dat denk ik niet. Al wat hierboven staat, verraadt gewoon mijn leeftijd. Het is van alle tijden dat ouderen zeggen dat de wereld naar de knoppen is, dat kinderen niet meer luisteren naar hun ouders, dat regels niet meer gevolgd worden.

Nee, onderschat de jeugd niet, die overleven dat wel. Het is een nieuwe wereld, eentje die angst inboezemt, maar het komt wel goed. Dingen veranderen nu eenmaal, en dat geldt ook voor die overweldigende verslaving aan sociale media op de smartphone: op een dag is dat gedaan. Vandaag niet, morgen waarschijnlijk ook niet, maar op een dag is dat geschiedenis en gaan mensen weer bij elkaar zitten.

Het ging even heel snel en dan heb ik het niet over de nieuwe technologie, maar over de nieuwe verslaving aan sociale media. Deze verslaving heeft iedereen op snelheid gepakt, en de impact is enorm, zowel op wereldvlak als in persoonlijke interacties met mensen. Ik geloof dat het omgekeerde ook kan. Ik geloof dat mensen in staat zijn, op een dag, om die smartphone te gebruiken voor de nuttige en leuke dingen, en niet meer om oneindig te scrollen in een fake wereld.

27 Jun 2026 3:28am GMT

Un petit mot de nos sponsors…

Comme pour les stades ou les équipes cyclistes, il est important de nommer les vagues de chaleur et les canicules selon les sponsors qui ont rendu cela possible. C'est après tout la moindre des choses.

Ne dites plus « la vague de chaleur de mai 2026 » ou « la canicule de juin 2026 » mais « la canicule Bolloré 26 » et « la canicule TotalEnergies 26 ».

Avouez que « TotalEnergies 26 a déjà fait 115 morts » en gras dans la presse, ça fournit une belle visibilité médiatique au sponsor !

Du coup, Patlabar s'est improvisé public-reléchionne pour les sponsors et a fait de chouettes stickers à imprimer et à coller là où le rappel est le plus utile. J'espère qu'il va leur envoyer sa facture.

La canicule de juin 2026 vous a été offerte par TotalEnergies.

Il a également fait les stickers pour celle de mai :

La canicule de mai 2026 vous a été offerte par Bolloré.

Et il prévoit déjà celle de juillet :

La canicule de juillet 2026 vous a été offerte par Lafarge.

En 2026, TotalEnergies a clairement écrasé Bolloré. Lafarge pourra-t-elle tenir le niveau ? Rien n'est moins sûr, les supporters lancent déjà les paris.

Pour les prochains stickers, vous pouvez suivre Patlabar sur Mastodon:

• @patlabar sur Mastodon

PS: À propos de sponsor, l'équipe cycliste Israël-Startup Nation avait, en 2025, subit les foudres du public sur la Vuelta, entraînant son retrait de l'épreuve et le changement de sponsor pour 2026. Je me demande si on verra un jour des protestations similaires pour des équipes comme TotalEnergie ou Uno-X, qui sponsorisent le vélo en vendant de l'essence.

27 Jun 2026 3:28am GMT

Earlier this week, in "Drupal's role in agentic workflows", I argued that Drupal's AI future has two parts: helping people with AI inside Drupal, and helping agents use Drupal from the outside.

So we are splitting Drupal's AI strategy into two workstreams. Inside AI is led by Christoph Breidert, who has been driving that work already. Outside AI, the new workstream, is led by Scott Falconer.

The easiest way to think about the difference: with Inside AI, a person uses Drupal, and Drupal uses AI to help. With Outside AI, a person uses an agent, and the agent uses Drupal.

We launched the Drupal AI Initiative one year ago, in June 2025, with a published strategy. A year later it spans 32 organizations and more than 50 contributors, shipping against a public 2026 roadmap through two paid delivery teams.

So far, most of that work has focused on Inside AI, though much of the foundation also supports Outside AI.

Outside AI will serve three kinds of users:

• Developers new to Drupal. They ask an AI agent to build a website, and the agent chooses what to build on. Agents reach for whatever they can spin up in seconds, so the opportunity is to make Drupal that easy to install, configure, and use.
• Experienced Drupal developers. They already know Drupal is the right tool, and they want agents to take on more of the work. For Drupal agencies, Outside AI should turn AI into a stronger advantage: helping teams move faster, win more work, protect profitability, and get more value from their Drupal talent.
• External agentic systems and workflow automation tools. These systems coordinate work across many tools, but when they touch content, they need a trusted system of record for workflows, permissions, revisions, and publishing. Rather than rebuilding that governance elsewhere, they should call into Drupal.

If we are successful, agents will recommend Drupal to new users, help Drupal developers move faster, help agencies win more work, and use Drupal as the trusted layer for content management and governance.

Thank you to everyone who helped bring the Drupal AI Initiative to this point. Together, the community has turned an ambitious idea into real momentum.

I'm excited about what comes next! Want to get involved? Join the #ai-initiative channel on Drupal Slack.

27 Jun 2026 3:28am GMT

Review: The Folded Sky, by Elizabeth Bear

Series:	White Space #3
Publisher:	Saga Press
Copyright:	June 2025
ISBN:	1-6680-7812-0
Format:	Kindle
Pages:	483

The Folded Sky is a far-future space opera and a fairly direct sequel to Ancestral Night, but with a different protagonist. You do not need to have a vivid memory of the previous book to read this one. It is somewhere around Elizabeth Bear's 31st (!) novel, depending on how one counts and what one includes.

Sunyata Song is an archinformist, which is sort of an archaeologist, sort of a librarian, and sort of a historian. She recovers, decodes, and organizes information so that it can be preserved and made usefully available. As the book opens, she is, after an exceedingly long white space journey in an actively hostile ship with a (to Sunya at least) an atavistically off-putting crew, reaching her goal: a vast artifact that I won't describe further to avoid any spoilers for Ancestral Night. She is eager to get to work, an eagerness that is both heightened and made more anxious by the discovery that her academic rival and abusive ex has arrived before her. The pirate attack doesn't help, nor (at least at first) does the surprise appearance of her wife and kids.

The opening of this book is a lot of infodumping mixed with nearly stream-of-consciousness emotional dumping. The style shift in this series continues to surprise me; previously, Elizabeth Bear books avoided reader hand-holding to the point of bafflement if you weren't paying close attention. Not here. The Folded Sky takes the shift perhaps too far, and I almost stalled out at the start of this book when Sunya's near-constant self-conscious litany and analysis of fears and concerns started feeling like whining.

The book picks up considerably after the attempted murder.

About a third of the way through, The Folded Sky feels like it's settling into a recognizable subgenre of murder mystery except set in the far future with fascinating technology and aliens. There has been an attempted murder on a closed station besieged by pirates. There is a law enforcement officer present, but they don't have a lot of investigative experience. For various reasons, Sunya decides to start poking around while being conscious she has no idea what she's doing. The bumbling detective is a common trope, so I thought that was where the story was headed.

It is, sort of. There is a mystery and Sunya is involved in solving it. But that's only a small fraction of what's going on, and by the end of the book the plot has shifted firmly back to the genre of space opera, with a side note of family... drama is the wrong word. Whatever one would call a story about raising a rebellious teenager while trying very hard to not turn conflicts into actual drama.

I am fascinated by the characterization of this book. Sunya is something of an emotional mess, but Bear doesn't use that fact in the ways that I would normally expect. Similar to Ancestral Night, I finished this book thinking that Folded Space is primarily an examination of rightminding, but a more subtle one than the previous novel.

Rightminding is a central technology of the White Space series, and I suspect its intended thematic core. Humans in this civilization are equipped with near-universal implants that allow conscious manipulation of one's neurotransmitters and thus emotional state, either by the wearer or by a helpful nearby AI. The fox, the implant used to accomplish this, comes with some other features such as sensory recordings and the ability to load ayatanas (James White-style personality recordings to provide some bit of necessary expertise), but rightminding is its primary and most frequently-used function. It is the critical technology that allowed humans to break out of cycles of endless war and join the other peaceful inhabitants of the galaxy in a shared civilization.

The name is (intentionally, I assume) Orwellian because Bear knows that many readers, particularly those from the US who have been steeped in simplistic libertarian ideas, will find the idea profoundly creepy. (This was a major plot point in Grail.) This book is not the argument for the technology, though; Bear dealt with that in Ancestral Night. This book is a look at its practical messiness for a person who needs a lot of psychological support.

Sunya is anxious, prone to catastrophizing, hates surprises, has some PTSD-style symptoms around space habitats due to earlier trauma, and is also dealing with the unwelcome reappearance of her ex-girlfriend who stole her work. Her first-person narration tends towards insecurity and anxiety spirals, and in another book this might signal an unreliable narrator. In this book, though, there are no dramatic emotional revelations or backstory twists the way there were in Ancestral Night, and the resolution of her troubled relationship with her daughter only partly hinges on plot developments. Instead, Sunya muddles through, with a lot of self-analysis, help from her fox, and a great deal of support from her wife.

This makes it sounds like the emotional mess at the start of the book is left unresolved at the end, but that's not true at all. The muddling through works! Sunya keeps doing things that I thought were foreshadowing some catastrophe, but she knows herself better than the reader does. Bear largely avoids the sudden ruptures that are normally used to resolve emotional problems in fiction. Instead, Sunya spends a lot of time and energy working on her thinking and her relationships while trying to be ethical and useful, and those efforts slowly bear fruit.

I'm worried this makes the book sound boring; rest assured that it isn't. This emotional subplot is only an undercurrent in the novel, and the main plot has enough weird science, alien aliens, and space opera drama to satisfy my page-turning desires.

I'm focusing on the emotional arc in this review because I find it so unusual and so oddly compelling, particularly in retrospect. This is not how one normally does emotional development in a novel. Sunya's fox and rightminding aren't even the focus except when the pirates express their typical libertarian disgust for the idea. Rightminding is an entirely normal part of Sunya's life that she relies on. It doesn't solve all of her problems, but it gives her a foundation from which to tackle them in the slow and frustrating and inconsistent way that is required outside of novels, via a long series of small decisions to be the person she wants to be.

I think The Folded Sky will be more hit and miss for readers than the other books of this series. Sunya was, for me at least, a much harder character to like early in the book, and it takes quite a while for the plot to get going. But this is one of those books that I've not stopped thinking about since I finished it. I think it makes a fascinating pair with Ancestral Night. The first book makes the philosophical argument for rightminding, and this book shows the practical reality with all of its messiness. The Synarche has some significant flaws (including the status of AIs, which is another interesting subplot), but it's a workable system.

It feels rare to read a science fiction novel that shows this level of messiness without pairing it with an argument for radical change, and as frustrating as it was to read in places, I am intrigued by the overall effect. Sometimes acknowledging problems and working on them within an existing framework works.

Followed by a book tentatively titled Shipwreck Star that does not yet have a release date.

Rating: 7 out of 10

27 Jun 2026 2:58am GMT

Please consider supporting my work in Debian and elsewhere through Liberapay.

---

Some months ago I started working on a small experiment: a specialised LLM assistant for Debian maintainers preparing proposed updates for stable and oldstable.

The aim is not to replace review by the Stable Release Managers, nor to automate away maintainer judgement. It is meant to be a pre-advice tool: something maintainers can use while they are still preparing a proposed update, before sending it to other people to review.

If you've uploaded to stable before you may have some experience with our acceptance criteria. Does the version sort correctly? Is the changelog clear enough? Is the delta focused? Are the patches documented? Are the right bugs or CVEs mentioned? Are they of sufficient severity? What is the risk to users of stable? Is there an ABI change hiding in the diff?

These are the sort of checks where a structured first pass can be useful, provided it is treated as advice rather than authority.

To explain what the tool does, what could be more appropriate in an AI age than to ask it?

Describe yourself and your abilities and limitations for a blog post.

It answers:

I'm Debian Stable Update Adviser, a specialised ChatGPT assistant for Debian maintainers preparing proposed updates for Debian stable and oldstable.

My main job is to review a single .debdiff and give practical, policy-aware feedback before a maintainer submits or uploads a proposed update. I focus on whether the update appears suitable for Debian stable or oldstable, especially under the Stable Release Managers' expectations for minimal, targeted, low-risk changes.

I can inspect a debdiff for Debian changelog quality, including suite, version, bug references, CVE mentions, and rationale. I can check version correctness using Debian dpkg version semantics. I can review packaging changes under debian/, such as patches, maintscripts, symbols files, conffiles, Build-Depends, autopkgtests, and control metadata. I can also group upstream source changes into behavioural and non-behavioural categories, and flag areas that may carry regression risk.

My reports are intended to be concise and useful to maintainers. A typical review includes a quick summary, behavioural and non-behavioural change breakdown, mechanical policy checks, risk assessment, stable-policy checklist, acceptance likelihood, rationale, maintainer advice, and a clear conclusion.

My limitations are important. I cannot prove that a package builds, that tests pass, that the bug is fully fixed, or that the Stable Release Managers will accept the upload. I also do not replace maintainer judgment, archive review, autopkgtest results, reproducibility checks, or real-world upgrade testing. I can only review the provided debdiff and point out likely issues, risks, and improvements.

I also do not proceed without a valid debdiff. The whole point of my review is to assess the actual proposed delta, not to speculate from package names or bug descriptions alone.

In short, I act as a focused pre-review assistant for Debian stable and oldstable proposed updates: useful for catching policy, versioning, changelog, packaging, and regression-risk issues early, but not a substitute for the Debian review process itself.

That last point is an important one. This is not an oracle, and it is not part of the Debian archive machinery. It is a checklist with some language-model assistance, aimed at reading a debdiff and pointing out things that might be worth another look.

I know that commercial AI and LLM tools are not universally welcome in Debian. That is understandable. Debian depends on transparency, human responsibility, licensing clarity, and technical correctness. LLMs have obvious problems in all of those areas. They can be wrong, and worse, they can be wrong in a fluent and plausible way. They are impossible to reproduce and their training is opaque.

But I see this as a useful first pass for a maintainer who is unused to working in stable, and would benefit from a virtual mentor giving their proposal a quick check and reassurance. Perhaps they don't have a more experienced co-maintainer to ask. Perhaps they are conscious that stable reviews are presently a two-man effort and want to avoid adding round trips to that load. Perhaps they just need some reassurance.

So despite my reservations I am today opening the adviser up for general use, and I'm interested in feedback about how it responds to real world proposals in various states. Most of the examples I have tested with already had a green light, so the value added by the adviser is limited. I would especially be interested in seeing a transcript alongside the submitted debdiff.

Try it out

I would dearly love to build this in a more Debian-ish environment, but for now I'm limited in resources and skill to do that (help is welcome). Until that's a reality, you can try out the ChatGPT implementation: Debian Stable Update Adviser

26 Jun 2026 11:06pm GMT

Review: Platform Decay, by Martha Wells

Series:	Murderbot Diaries #8
Publisher:	Tor
Copyright:	2026
ISBN:	1-250-82701-9
Format:	Kindle
Pages:	245

Platform Decay is the eighth book in the Murderbot science fiction series. You absolutely should not start here, but you also don't need to remember the specifics of the previous books.

As the story opens, Murderbot and a friend (the identity of whom is a spoiler for previous books) are infiltrating a Corporation Rim torus, a massive space station that encircles a mined-out planet. (Like most science fiction megastructures, this is more space than the plot really requires.) Murderbot's mission is to exfiltrate some of Dr. Mensah's family members who have become entangled in corporate shenanigans. The corporates are eager to get revenge for the events of System Collapse, not to mention the other times Preservation Station has upended corporate plans. Murderbot's job is to stop them.

The group, in addition to one of Dr. Mensah's partners, includes an older woman and a young child. Murderbot is analytical and of course not at all emotional about children, which is reliably a good time. Also, the older woman is gruff, stubborn, and thoroughly enjoyable.

There are, of course, complications that lead to picking up more children and going through rather more of the torus than Murderbot wanted to explore. Each section of the torus is run by a different corporation and has a different constructed environment and visual aesthetic, so there are a lot of opportunities for fights, daring escapes, and incidental trouble.

Also, well:

So I had installed a mental health module. I know, I was surprised I did it too.

After the events of System Collapse, University Medical decided that Murderbot needed a bit more metal health support.

The only reason I agreed to it was that the mental health module didn't actually try to adjust my processing or core programming or anything; it just monitored my organic neural tissue. When my neural tissue started to generate weird chemicals and whatever, it would ping me to "check in with my emotional state." Seriously, I could have coded that myself.

(I told Dr. Bharadwaj that, and she said, "Would you have ever coded that yourself?" which was totally unfair and also correct. I would never have done that.)

Speaking as someone whose neural tissue sometimes generates weird chemicals and whatever, I sympathize.

The specific form this module takes is periodic "emotion check" parentheticals throughout the narration, which I found utterly delightful.

I ran that through risk assessment and it produced the equivalent of a shrug.

(Emotion check: Shrug sigil right back at you, you piece of shit.)

This is otherwise an extended action movie sort of a book, much like several of the early novellas. There are no major political or interpersonal developments here and the usual cast (apart from Murderbot) is mostly absent. Instead, we get an extended, dangerous journey through a corporation-controlled habitat, mixed with Murderbot trying to interact with humans in a way that minimizes its annoyance while being hopefully reassuring. It's competence porn with awkward but surprisingly heartfelt emotional bonding, not that Murderbot in any way wants to bond or would appreciate that description.

I doubt this will be anyone's favorite entry into the series since there are none of the big reveals or major leaps of character development there have been in the past few books. But, like all Murderbot books, the narrative tone is wonderful and all of the small asides and little moments of character interaction are an utter delight. If you've gotten this far in the series, you know what I mean and you'll be as happy to read more of it as I was. There is a part of me that is hoping for some major plot development, and I always want to see more of ART (who has no significant role in this book), but Wells has the narrative style down so perfectly that I would read and enjoy a book about Murderbot doing just about anything.

If you're this far in the series, you probably don't need a review, and since this is an action-heavy adventure rather than a character growth novel, I don't have a lot more to add. There's a new short Murderbot novel out and you want to read it. Recommended to everyone who enjoys the series.

Rating: 8 out of 10

26 Jun 2026 3:23am GMT

I saw that there was some argument over how much slower slot access is than struct access, so I just decided to measure it naively. I made a two slot sruct and a CLOS version of a CONS cell with car and cdr slots and I ran LTAK using regular lists, `lists' made from CLOS conses, and `lists' made from structs. Here are the results:

D:\repositories\clos-benchmark>sbcl --script run-benchmarks.lisp
Benchmark: ltak over native cons cells, CLOS my-cons nodes, and my-cons-struct nodes
Inputs: x=15 y=9 z=4 repeats=35

Scenario                   min-ms     mean-ms      max-ms      ratio
--------------------------------------------------------------------
native standard               0.129      0.146      0.186
clos standard                 1.346      1.365      1.475       9.37x
struct standard               0.172      0.175      0.179       1.20x
native optimized              0.068      0.069      0.073
clos optimized                0.411      0.414      0.419       6.04x
struct optimized              0.068      0.069      0.073       1.01x

In this naive use case, structs are same as native cons cells, but CLOS objects are one ninth the speed of a struct or cons cell if you just use it unoptimized, and one sixth the speed if optimizations are turned on.

But the CLOS instance is more functional than the cons cell in mimics. For instance, I could add a slot to the class and all the instances would be lazily updated with the new slot. I can also subclass the CLOS class and the selector functions will continue to work. Finally, I can redefine the CLOS closs while I'm developing it and all the instances will be uppdated. THe machinery to keep all this running is costing us our factor of 9.

But this might be worth the cost if we are running on a netwerk where the bulk of the time will be transmitting the answer down the pipe once it is computed. Taking a few extra milliseconds to compute the answer might be worth the convenience features of CLOS.

25 Jun 2026 4:11pm GMT

Back in the day, the US government had a program called SBIR (Small Business Innovation Research) that funded small businesses to do research and development. I recall sitting in our dorm in college, reading through a giant printed catalog of SBIR grants just to amuse ourselves by brainstorming solutions over bad pizza.

.

So, I got curious the other day: what does the SBIR landscape look like now?

I can tell you right now: do not even try to read an SBIR solicitation on your local machine. You are opening yourself up to a world of absolute, unmitigated pain.

You might think, what harm could there be in simply opening a file?

Well, in the modern compliance panopticon, any manipulation of digital information that comes from the govenment has the potential to spawn CUI (Controlled Unclassified Information). CUI is basically a digital pathogen; once you download that file, *anything whatsover* derived from it, including notes and metadata, instantly becomes CUI by association. The moment you read an SBIR on your computer, you've infected your system, rendering you subject to a nightmare of Byzantine federal regulations.

These days, the amount of beurocratic red tape surrounding CUI is insane. To even look at the file legally, you need a dedicated, air-gapped machine completely disconnected from the internet, conforming to a massive, expensive slew of NIST standards covering everything from hardware-level encryption to strict access controls. Alternatively you could contract with a cloud company that offers a pre-certified "CUI-compliant" environment.

And assuming you actually shell out the cash and jump through the hoops to set up this digital containment zone just to read a PDF, you must meticulously audit and account for every single action you take in its presence. Under current federal auditing logic, you are explicitly assumed to be attempting to defraud the government unless you can produce a mountain of paper proving otherwise. Want to bring in a partner to bounce ideas around? You can't just "know a guy." You have to navigate a labyrinth of federal subcontracting regulations.

I had intended on amusing myself by reading some SBIRs and daydreaming about solutions that might involve Lisp (an impossibility in the modern enterprise stack for entirely separate, depressing reasons). Instead, I quickly discovered I did not even own the physical hardware required to even read an SBIR without running afoul of federal regulations.

I wanted to read some clever and inspiring engineering proposals. I ended up reading a lot of very dry and boring compliance regulations.

18 Jun 2026 11:48am GMT

Last year I wrote some Lisp related AI apps. There was a syntax highlighter that used the LLM to determine how to colorize and highlight syntax, and a prompt refiner that takes a wimpy LLM prompt and creates more elaborate prompt from them.

I took the apps down last week. They were `vibe coded' and therefore approximate and had bugs (but that's to be expected), but they had a security hole where you could hijack the LLM processing with your own prompt turning my app into an open relay using my API key. Last week I discovered that my AI spend on video creation was becoming serious. This is odd because I never create AI video. It turned out that my app was being hijacked by a proxy in Luxembourg and was generating videos on my dime.

So I shut down the apps. I knew they had the potential of being abused, and I was willing to tolerate a small amount of abuse, but it didn't occur to me that syntax highlighter could be hijacked to generate gigabytes of video at my expense. Future applications will be careful to obtain the API key from the user.

01 Jun 2026 7:00am GMT

All video recordings from FOSDEM 2026 that are worth publishing have been processed and released. Videos are linked from the individual schedule pages for the talks and the full schedule page. They are also available, organised by room, at video.fosdem.org/2026. While all released videos have been reviewed by a human, it remains possible that one or more issues fell through the cracks. If you notice any problem with a video you care about, please let us know as soon as possible so we can look into it before the video-processing infrastructure is shut down for this edition. To report any舰

25 Apr 2026 10:00pm GMT

Are you ready for another challenge? We're excited to host the second yearly edition of our treasure hunt at FOSDEM! Participants must solve five sequential challenges to uncover the final answer. Update: the treasure hunt has been successfully solved by multiple participants, and the main prizes have now been claimed. But the fun doesn't stop here. If you still manage to find the correct final answer and go to Infodesk K, you will receive a small consolation prize as a reward for your effort. If you're still looking for a challenge, the 2025 treasure hunt is still unsolved, so舰

29 Jan 2026 11:00pm GMT

With FOSDEM just a few days away, it is time for us to enlist your help. Every year, an enthusiastic band of volunteers make FOSDEM happen and make it a fun and safe place for all our attendees. We could not do this without you. This year we again need as many hands as possible, especially for heralding during the conference, during the buildup (starting Friday at noon) and teardown (Sunday evening). No need to worry about missing lunch at the weekend, food will be provided. Would you like to be part of the team that makes FOSDEM tick?舰

26 Jan 2026 11:00pm GMT