Yesterday evening, a close friend of ours, together with her two daughters 9 and 3, walked 800m from Charleroi Central station to Charleroi West station. I had suggested her to take the bus through this "interesting" area instead. However, she wanted to quickly grab her kids something to eat. Until she walked out of Charleroi Central.

"Baigais ūķis", she described it, roughly translated: "shady shithole". She didn't like what she saw. Open consumption of heavy narcotics, and more. They ran quickly and caught the train to Leuven.

"Baigais ūķis", by a friend, very well-travelled and a survivor of the post-Soviet '90s absolute chaos.

If you're smarter and more motivated than me, feel free to see this as a call to action.

21 Sep 2026 8:16pm GMT

Soyez humains, communiquez !

Pourquoi le moindre humain écrira toujours mieux que le chatbot le plus perfectionné.

Dans ma vie, j'ai écrit plusieurs millions de mots, sur des myriades de sujets et pour des dizaines ou des centaines d'audiences différentes. Rien que ce blog en fait 250.000. J'estime également en lire plusieurs millions chaque année.

Bref, j'ai une relation profonde et intime avec l'écriture et la lecture. C'est ma passion, mon métier et même une manière de vivre. Je suis capable, en me concentrant, de lire particulièrement vite. À une époque, je pouvais lire "photographiquement". De même, j'ai l'écriture très facile. Lancez-moi sur un sujet et je peux discourir pendant des pages et des pages sans effort.

À celleux qui me demandent comment écrire, je n'ai qu'un conseil : réduisez la friction entre votre cerveau et les mots en apprenant la dactylo (mes passages au Bépo puis à Ergol ont été des étapes incroyables dans mon processus d'écriture). Pour le reste, il suffit de prendre goût au fait d'écrire.

• Le bépo sur le bout des doigts (ploum.net)
• Ergo‑L (ergol.org)

Écrire c'est très facile si on accepte de se laisser aller, si on prend confiance en soi.

Essayez, vous verrez !

La concision fait la qualité de l'écriture

Bien écrire, c'est évidemment beaucoup plus difficile, en tout cas pour moi. Mais l'essence de « bien écrire » est très simple. Il faut que chaque mot ait une utilité.

Bien écrire, ce n'est pas écrire beaucoup. Au contraire ! Bien écrire, c'est couper, supprimer pour aller à l'essentiel. Chaque mot doit être une manière d'amener subtilement votre idée, votre émotion, votre raison d'écrire à se clarifier dans votre cerveau et dans celui du lecteur. L'écriture est une forme de télépathie. La qualité de l'écriture est la mise au point, la netteté.

C'est la raison pour laquelle les textes générés par chatbots/IA/pouetpouetGPT me sont insupportables. Ils sont creux, longs, verbeux.

Même les résumés automatiques sont une catastrophe. Ils trahissent le cheminement de l'auteur, ils se trompent régulièrement sur les points subtils, mais cruciaux et, comble de la bêtise, ils sont souvent plus longs que le texte original qu'ils sont censés résumer. Un résumé ou un surlignage est intrinsèquement personnel. Il doit vous permettre de vous rappeler votre expérience de lecture.

Et ce n'est pas une question de qualité du modèle. Non PouetPouetGPT 42.3 n'est pas révolutionnaire ! Il ne peut pas l'être.

Parce qu'il ne peut pas inventer l'information. Il ne fait que diluer le prompt que vous lui donnez, le mettre en forme selon ses standards, l'agglomérer à des milliards de statistiques. Mais il ne peut pas lire dans vos pensées et deviner ce que vous voulez me dire.

Le message utile sera toujours plus court que le prompt pour l'obtenir

Si vous demandez à PouetPouetGPT d'envoyer un mail à Ploum pour savoir comment il va, la seule information valable, la seule écriture qualitative est: 

Salut, Ploum, comment ça va ?

Tout le reste n'est que du bruit. De la mauvaise écriture (et je m'y connais en mauvaise écriture). C'est juste que la mise en page, l'orthographe, le respect de certains styles peuvent donner l'apparence que c'est « bien écrit ». Ça ne l'est pas. Ça ne le sera jamais parce que « bien écrire » c'est avant tout « bien communiquer ». Et rajouter du bruit ne permet pas de bien communiquer.

L'équation est simple : un message bien écrit sera toujours plus court que le prompt équivalent. Les agents d'aide à l'écriture exploitent le manque de confiance. « J'écris mal, je vais demander à l'IA ». L'apparence du résultat fera encore plus baisser l'estime de l'auteur qui, pour couronner le tout, pratiquera de moins en moins l'écriture et sera de moins en moins au clair avec ses propres idées.

• Ne rien avoir à penser (ploum.net)

Imaginez une conversation téléphonique. Le réseau est mauvais. On vous entend mal. Vous décidez alors de mettre de la musique à fond en arrière-plan parce que la musique est jolie. Avez-vous amélioré votre capacité à communiquer ?

Et, surtout, pensez-vous que c'est respectueux de votre interlocuteur ?

Lorsque l'écriture n'est plus le fruit d'un effort intellectuel

Jusqu'il y a peu, lorsque je tombais sur un billet de blog, lorsque je recevais un email, je partais du principe qu'un humain avait fait l'effort de l'écrire. Je faisais donc l'effort de le lire, au moins rapidement. J'abordais tout texte avec cette question en tête : « Qu'est-ce que l'auteur essaye de me dire ? »

Ce n'est aujourd'hui plus le cas. Je dois traiter chaque email, chaque site web inconnu comme étant potentiellement généré et n'ayant demandé aucun effort humain. Dans le doute, je vais désormais m'abstenir de lire et de répondre. Après tout, si vous n'avez pas pris le temps de l'écrire, je prends comme une insulte que vous pensiez que je puisse prendre le temps de lire.

• I Don't Want to Interact With Stochastic Parrots (ploum.net)

Bien entendu, je n'ai pas de détecteur IA parfait. Je me fie à mon instinct. Mais, comme je l'ai dit en introduction, celui-ci est particulièrement développé pour l'écrit. Un message qui porte une énorme attention au style, à l'orthographe, qui est long, mais qui est particulièrement pauvre en information est soit généré, soit écrit par quelqu'un qui fait du remplissage et ne vaut guère mieux (typiquement, un marketeux).

Mon expérience de prof joue aussi peut-être : les textes générés ressemblent de manière frappante aux examens que je fais passer à des étudiants qui ont beaucoup de charisme, mais qui n'ont rien compris. Ils brodent, tournent autour du pot, tentent de camoufler leur ignorance avec une assurance déconcertante. Mais aucun prof ne s'y trompe : l'étudiant sera recalé ! Et encore plus sévèrement que l'étudiant qui avoue son ignorance de manière transparente.

Un humain qui écrit très peu et a du mal à structurer ses idées ne fera pas autant d'efforts pour faire "de belles phrases" bien creuses. Ça n'a aucun sens ! Au contraire, les personnes les moins à l'aise avec l'écriture ont tendance, malgré leurs maladresses de style bien excusables, à donner beaucoup d'informations, à avoir envie d'exprimer des choses.

Et, oui, vous pourriez certainement générer un message qui me tromperait. C'est peut-être déjà arrivé. Mais, pour être sûr de votre coup, générer le prompt vous demandera sans doute beaucoup plus de travail que d'écrire le message directement. Ce qui est fondamentalement stupide, non ? Quelle est la finalité de tout ça ? À un certain point, votre grossièreté devient de la malveillance.

De nos belles et humaines maladresses

La maladroite phrase d'une personne à peine lettrée aura toujours plus de valeur, sera toujours une meilleure manière de communiquer que l'apparence formelle d'un message généré. Et même le modèle PouetPouetGPT le plus parfait au monde ne pourra jamais rien y changer.

Si vous pensez que la version 42.3 s'est justement grandement améliorée, que je devrais tester, c'est juste que vous vous êtes habitué à l'outil, que vous cédez à la normalisation, que vous avez atteint votre propre seuil d'incompétence. Que vous n'avez pas compris à quoi servent l'écriture et la lecture. Que vous êtes en train de perdre votre confiance en vous et votre capacité à écrire.

Alors, par pitié, continuez de penser, d'écrire. Ne déléguez pas votre libre arbitre. Et si vous voulez communiquer avec moi, acceptez vos maladresses, vos fautes et votre humanité. Un simple correcteur orthographique peut aider à améliorer la lisibilité et votre confiance en vous. Mais ce n'est pas nécessaire lorsqu'on communique informellement entre humains.

Respectez votre correspondant : soyez humain !

• Détail d'une statue de scribe de la Vème dynastie égyptienne (photo par Rama)

21 Sep 2026 8:16pm GMT

I Don't Want to Interact With Stochastic Parrots

My AI policy is "I don't want any kind of interaction with that thing." And this should be all you need to know.

I don't care if you call it AI, LLM, chatbot, or whateverGPT. I simply don't want to interact with it in any form. If you interact with me, make sure to never send me any output from those nor to use it as a "source" to justify one of your arguments.

I'm one of those people deeply interested in all the extraordinary stuff other humans have to say. Unfortunately, life is already too short to hear them all. I need to make a lot of choices. That's why I will not tolerate any attempt to steal the little time I've on this planet by making me interact with stochastic algorithms trained to produce tons of "average," non-human content.

The direct consequence of my choice is that I will refuse to interact with humans who take pride in making themselves a meat interface between me and the algorithm they've chosen to replace their free will.

I will not read your website, I will ignore your emails and I will happily walk away from real-life conversations as soon as it is clear that I'm not talking to a fully sentient Homo sapiens sapiens but to an empty shell who has happily delegated their cognitive abilities to an external proprietary tool designed to be some sort of "random average garbage."

I will not read the text

The very essence of writing is what makes you think. When you write, even something as mundane as a short email, you transform a bunch of contradictory neural stimuli into an ordered thought.

If you don't care to write it, there's no reason I should waste one single second reading it. The effort should be on your side first.

I don't mind mistakes, typos, or badly formed sentences. In fact, I subtly appreciate them when we interact because they are part of you, they tell a lot about yourself. I'm not a literary agent, I will not judge your way of writing: I'm there to exchange ideas, knowledge, and experiences.

If you find yourself typing a prompt to express your idea, then just send me that prompt. I'm not interested in what an algorithm would do with your prompt, I want to know what you asked in the first place. I care about you, the human.

You may find it hard to express yourself, to write what you think: remember that the less you practice, the worse it will be. Prompting might feel easier. It does not make it right.

If it is from an algorithm, it is not you. Only you can write what's inside yourself.

I will not look at the pictures

Generated images. Seriously. They all look hideous.

When I spot one in a given context, I immediately have a feeling of cheapness, bad taste, and poor culture. Like this fancy restaurant of a luxury hotel I saw in a big European city. It had a huge AI generated picture on its main building: a kid eating malformed fries with his six-fingered hand and putting them in his skull through his cheek. Or this other restaurant which had a very nice menu, full of pictures of Italian cities. Until the kid's menu which, was shockingly out of place and totally unnecessary. It also showed a kid awkwardly eating a pizza even though there was no pizza on the kid's menu.

If you don't have the resources to pay for an artist, you probably don't need a picture at all. If you are making a poster, write what is important to know instead of burying it in a gloomy generated picture. If you write a blog post, I will not read if it is illustrated by generated pictures.

A website illustration, if any, conveys an emotion, a feeling. I sometimes spend more time finding a good illustration for a post than writing it. If I don't find a satisfying picture, I don't put any.

The first feeling conveyed to me by a generated picture is an uncanny unease, an obnoxious emotion that immediately makes me want to leave. It also tells me enough about the author not to want to know more. It might be a kind of overreaction. But as I said, there's too much to read anyway so it's a good first filter.

No, that picture is not pretty. No, it is not funny. It doesn't share any human feeling, any artistic expression. You like it because you had fun generating it. But it is wasting my time.

I will not run the code

I don't want to run generated code on my computer.

Good code is knowledge. Even in a purely productivity-oriented business, every line of code should reflect the choice of an employee knowing the business and choosing a way to solve a business problem.

Reality is, of course, different. I've worked with enough different codebases to know that proprietary software is simply badly coded. Each line is written assuming "I will not be there anymore to deal with it in a few years." But at least we know that each line, as bad as it can be, was added by a human for a reason. LLMs move the needle from "no need to care in a few years" to "no need to care right now." You cannot assume anything about generated code. Maybe it was simply hallucinated and, by chance, it compiled.

Which means that, as soon as generated code is added to a project, the whole project becomes unmaintainable by humans. You can't understand the code because there's nothing to understand in the first place!

It follows that the whole project now needs LLMs for any change which, will make it even worse from a human perspective. We end up adding more and more lines of code nobody understand where the problem has always been "There are too many lines of code and too few people understand them."

I'm convinced that accepting generated code will lead most projects to become broken beyond all hope of repair in only a few years. "Carefully reviewing" will soon not be enough. Unfathomable code will eventually slip in and gradually destroy the whole project. I predict that the projects too important to be left to rot and die will take decades to recover from those couple years of "assisted productivity."

We need to remember that what we call "code" is merely a specification of the software we want. Those specifications will be given to the compiler to make the real software. The role of a coder is to take vague, imprecise, and contradictory specifications from a manager or customer and then make sure to remove any ambiguity. This could be done by clarifying with the customer or by silently making choices. History and mathematics have demonstrated that humans cannot make unambiguous and non-contradictory specifications without using a formal language designed expressly for that purpose. Natural languages simply cannot remove ambiguities and this may be an evolutionary feature.

Removing the coder and replacing them with a tool designed to pretend to agree to anything said could never produce good, maintainable software. It may produce a small throwaway script. It may find security holes more efficiently than fuzzing. But it will never be able to build something useful and reliable for the long term.

Which is what I expect from software.

I want to be able to trust software enough to invest time in learning it. That has always been one of my main arguments for using open source: if a free software is good enough, I trust that there will always be people to maintain it or to fork it if needed. If I have a problem with a free software, I can always look at the code to understand what the humans who designed it wanted to do. I may also modify it. This is not theoretical: I've done that with countless pieces of software in the last 20 years. I rely on it!

For that reason, I will carefully avoid running any openly "vibecoded" tool, and I'm trying to focus my efforts on projects that actively try to distance themselves from the current bubble.

I will not listen to the discussion

"I've asked ChatGPT and…"

That's it. No need to say more. All those years speaking about "fake news" and "checking your sources" just to blindly repeat a random series of letters assembled by a stochastic algorithm? Seriously?

I don't care about your credentials, I don't care about your experience. With a couple of words, you gladly announced that you are obliterating them and refusing all forms of free will. Goodbye!

That's not very friendly, I know. I never pretended to be. And I didn't start it.

I will not grade the student report

Across the last years, I've not managed to find one single student who astonished me with their use of a chatbot. In every single case I've met, the use of a chatbot made my student perform worse. Sometimes spectacularly like, this student who contributed to a project on Github but, when asked, could not even tell me what the project was about.

On the opposite, forcing the student not to use any AI makes them better every single time. No exception. It also vastly improved their self-confidence.

• Giving University Exams in the Age of Chatbots (ploum.net)

It is not a matter of "learning to use the tool". You cannot learn to use a proprietary stochastic tool which can be changed at any time. You don't need to "learn to chat" (and if you do, not in my course). What the "tool" is really doing is making you lose the essential ability to learn, making you lose your self-confidence. As John Scalzi points out: playing Guitar Hero is fun. But even thousands of hours of playing Guitar Hero will not enable you to play "Happy Birthday" on a real guitar.

• Generative "AI": The Guitar Hero of Creativity (whatever.scalzi.com)

I consider that my students are in my class to learn. Chatbots are actively preventing any kind of learning. That's why, from now on, I make it a strict policy that anything my students are submitting should be entirely produced by them.

It can be short. It will be imperfect. It will be full of mistakes. It may even be wrong. The report will have fewer bullet points and emojis. But it will be yours, and that's what I want to see.

I will not technologically "enforce" this rule. Cheating has always been part of university. If you are smart enough not to be caught, you probably deserve to pass. But it will probably require a lot more effort on your side than simply writing your own goddamn report with your bloody fingers on a keyboard.

I will not judge what you do in private

AI/chatbots/LLMs are known to have a terrible impact on your brain. They are bad for you, for the whole economy, for the political atmosphere, and for the environment. They consume huge resources, destroy the whole Internet and our ecosystem.

But they are addictive, I get it. They make you feel productive (which, studies have demonstrated, is largely a feeling). I consider them a kind of drug.

• AI Isn't Breaking Work. It's Already Broken. (calnewport.com)

They may also be useful when you are forced to accomplish a stupid one-time task you don't want to do but is required. We all have to deal with our share of bullshit jobs, I get it.

Using AI is like a shameful drug addiction or a weird sex fetish. If you want to use it privately or between consenting adults, it's up to you. As long as you don't brag about it, I will not judge.

Just make sure that I don't have to interact with it.

• Human made logo by Matt Kindt (commons.wikimedia.org)

21 Sep 2026 8:16pm GMT

I Don't Have a Smartphone…

• Tradução para português por Berlim

…or, at least, I wish I didn't.

"I don't have a smartphone," is what I tell people and professionals nowadays. This allows me to cut the crap about companies insisting that I install their app or restaurants wishing that I scan a QR code to access their menu on a small screen.

"I don't have a smartphone" is, according to my experience, the easiest explanation, the shortest way to force people to get their shit together and take the required actions to allow me to live without being glued to a small screen dependent on a huge American megacorporation.

When I buy something, from a small kitchen appliance to a car, I'm now forced to get formal confirmation by the seller that I will be able to use it without installing one, two or three different apps. I kept the count: in the last year alone, I had to argue against the installation of 18 smartphone apps. Just in my toilet, I'm supposed to have an app for the seat, an app for the flush and one for the ventilation.

It is quite fascinating because if you assume using each app for only 3 minutes per day (which basically means opening, closing and does not include doing the upgrade every other day or debugging some problems), that's nearly 1 hour of your day! 22 full days of your year (assuming 16 waking hours per day).

What installing your app means

When you ask someone to install your app or to scan your QR code, you make the following assumptions:

1. That person owns a smartphone (which is at least a couple hundred dollars).
2. That person has the smartphone on them right now.
3. The smartphone is in working condition.
4. It has enough battery to install your app, use it then finish the day.
5. It has enough storage left for your app.
6. It has enough network coverage.
7. That person has enough data left on their data plan.
8. They have a valid and connected Google account (or, an Apple one).
9. They are comfortable with taking out the phone and dedicating some time and attention to the screen right now while not paying attention to all those notifications that the phone surely gathered since its last use.
10. They are willing to accept all the conditions of your apps, including sending you personal data, registering an account, etc.

When you think about it, this is an awful lot of assumptions.

Just regarding point 8: your Google account could be terminated right now, without reason. It happens every day. It could happen to you. Or an American president could decide your country should not have that service anymore.

• Et si vos comptes disparaissaient demain ? (ploum.net)

If only one of those 10 assumptions is false, for whatever reason, the person will not be able to use your app. You will have to deal with it.

People always tell me I'm weird for not installing the app but, looking at this list, I find it weird that you even find people to install it in the first place!

But here we are… Those 10 assumptions have become the new commandments everyone should obey.

Why I will tell you I don't have a smartphone

Ten assumptions that are a bit too long to explain to a vendor or a worker. So, instead of arguing about the time lost and my quest to be Google free, I took the stance of answering, "I don't have a smartphone."

Reactions vary. Pure salesmen try to convince me that you can't live without the app, that I need to do the mandatory "update" Why? If it's connected, it can do its update alone. If it is offline and it works, it doesn't need any update and updates have a higher probablility to worsen my situation than to be helpful. If it is offline and it doesn't work well, why should I buy it in the first place?

On the other hand, real workers, those with dirty hands, often smile at me and tell me I'm right or that they wish they could not have a smartphone. On one occasion, a worker installing an appliance told me: "Oh, we will get along well!"

Which tells you something important: nobody wants the app. People install the app because they believe it is mandatory in some sort of way. Because they are afraid of missing out on something. Because they are told so by the salesman. But they just don't want it. In fact, when pressed, most salesmen even have a hard time justifying why I should install the app.

Also, I was strongly addicted. My relationship with my phone was not healthy.

• How I fought my smartphone addiction (ploum.net)

So "I don't have a smartphone."

But it is not true.

Mudita Kompakt, my not-so-dumb-phone

My main driver is a Mudita Kompakt, a small minimalist smartphone with an e-ink device. I've spoken at length about it in the following piece:

• Une vie sans notifications (ploum.net)

The main point is that, despite being an e-ink device and being totally Google-free, the Mudita is an Android smartphone. I can install apps and, yes, I love the smartphone concept for the tools I choose. I have Signal (well, I use Molly to connect to Signal). I also have the app of my bike GPS. I don't use it often but when I'm lost far from everything and it starts raining, I launch the Komoot app, ask for the shortest way home and upload it to my bike computer.

That's very useful innovation!

I also use Comaps, an online calendar and the local train schedule app.

So, seriously, I do really like the smartphone idea. It's just that I don't have any browser or "social" app on it. And I don't want anything else than what I have.

I wish I could say it is all I have, that I'm a true minimalist.

But it is not true.

The secondary desk phone

Somewhere on my desk, I keep an old FairPhone 3 that I repaired after it took a deep plunge into the ocean. It runs the Google-free /e/OS operating system.

But why? The reason is simple: sometimes, you are forced to use an app. Those apps may even check if your phone truly uses Google. So /e/OS has a solution to fake it (microG). The main use case is banking apps.

I highly prefer to do banking on my computer. But, having been brainwashed enough by Google, banks think I cannot be trusted to do banking on a computer I own while doing it on a small piece of glass that I keep in my pocket is "safe." Logging in on banking websites requires me to authenticate on a smartphone that checks for Google services.

It is not only banking: this secondary phone is very useful to test apps without cluttering my main phone. I've learned, thanks to my teenagers, that Strava will not launch without Google services. But it will also refuse to login with the fake microG. The solution is thus to launch Strava with microG enabled, to disable microG while keeping Strava running, to log into the app then to re-enable microG. A similar problem happens when using filters on Snap. Living without Google is not always painless.

At least, I can say I'm Google-free.

But this is not true.

The third, real android phone

I still keep in a drawer an old OnePlus 5 I bought in 2017 with a pristine Android system. The screen is cracked, the USB connector is wobbling but it works. It is still connected to a Gmail account I created in 2001 (invitations were still required!) and that I didn't even open for the last 10 years.

This phone is sometimes necessary. Like when a known bug in /e/OS prevented my banking app from working for several months. Anecdotally, this phone is also the thinnest, the lightest, the best screen I've ever seen. It also takes the best pictures (without any AI). It demonstrates that current smartphones are worst in every aspect compared with those of 10 years ago. The only exception being the CPU: that phone has a very hard time loading Anubis-protected webpages. Everything else is fine. It is hard to have this phone in your hand and not consider we are heavily scammed when we buy a modern phone.

In my country, businesses and governments are pushing hard to mandate the use of "Itsme", a proprietary authentication app developed by a commercial joint venture with the explicit intent to extract personal data and sell them commercially (yes, that was explicit in their conditions when they launched the service). I've always refused to register and use that service but it is becoming incredibly hard to find alternatives.

New EU regulations may also push more apps to check for the "Google Play Integrity" to ensure that they are running on a true Google owned Android.

I'm fighting hard but I foresee a moment when we will all be officially forced to have a Google account. If you have children, you are also forced to have a Meta account as everything school related now happens through Whatsapp.

So I'm living Meta-free because my wife volunteered to handle the Whatsapp groups. I'm living Google free because, deep in a drawer, there's still a solution for the day when I could not work it out without Google.

Who could have predicted

I'm European. The whole continent is assumed to have a Google and a Meta account. To always have in their pocket a Google or Apple certified and remotely controlled piece of hardware. It is even sometimes assumed to have a Microsoft account (like that time when the platform to be reimbursed from a cancelled ticket assumed a Sharepoint login).

This is frightening. We are putting all our eggs in the same basket. And our milk, our water, our house, our furniture and our loved ones. In an electrical-auto-closing basket remotely controlled by a foreign entity that openly spies on us and wants to extract as much money as they can. For some reason, it is considered weird not to like the basket.

At least, some are trying to build alternatives

• Why there's no European Google? (ploum.net)
• The Privacy Respecting European Phone (jolla.com)
• Delta Chat, decentralized secure messenger (delta.chat)

At the same time, European politicians are focusing on "not seeing" this elephant in the room while dedicating huge money and effort to promote "European AI" or "European Blockchain." Seriously. They are so blind to easy, innovative and existing solutions (Peertube, Mastodon, European mail hosting,…) that I'm starting to suspect that being dumb doesn't explain it all, that they are truly corrupted.

In the meantime, I do my small part. I defend my small hill. I'm an Offpunk.

• Offpunk Manifesto (blog.ayom.media)

And when requested anything about an online service or a smartphone, I answer:

I don't have a smartphone!

• Picture of a broken phone by Ashwin Kumar

21 Sep 2026 8:16pm GMT

Fuir le numérique ou bien le reconquérir ?

Le numérique est-il intrinsèquement mauvais ?

Comme le souligne Sandra, le minimalisme numérique ne vient pas du fait que le numérique soit mauvais en soi, mais juste qu'on a réussi à le rendre le pire possible sur tous les niveaux. Au niveau physique : on fait tout sur un petit écran trop brillant sans aucune sensation tactile et qui nous force à plier la nuque, au niveau psychologique avec l'addiction et l'optimisation pour les pertes de temps ainsi qu'au niveau économique : votre smartphone ne vous appartient pas vraiment, vous n'avez aucun contrôle dessus et, pire, il sert à vous espionner. Et vous allez racheter exactement le même rectangle noir tous les ans ou tous les deux ans.

• Minimalism vs Digital Minimalism (idiomdrottning.org)

Car comme le dit très bien Solderpunk, le créateur du protocole Gemini, nous croulons sous les appareils électroniques de mauvaise qualité qui envoyés au rebut (ou dans un tiroir) parce que « plus supporté par la société qui les a produit ».

Le contrôle de nos appareils nous pousse à en racheter de nouveaux, mais modifie également nos pensées au point de considérer que s'il n'y a plus de mise à jour, l'appareil se transforme soudain en presse-papier. Nous sommes tellement formatés à obéir aux grandes entreprises que nous en perdons toute créativité et toute compétence réelle avec des appareils qui sont des miracles de technologie.

• Lateral Thinking with Withered Technology (solderpunk)

Des miracles de la technologie qui fonctionne contre nous et non pas pour nous.

CodeTiger achète un robot « intelligent » et décide de bloquer l'envoi de données vers le fabricant. Ce qui entraîne à chaque fois une panne après quelque jour. Fâché, iel décide d'investiguer les entrailles de l'appareil : le robot est en fait un ordinateur tournant sous Linux qui envoie toutes ses données au fabricant, y compris la configuration de la maison, les habitudes des occupants, les codes wifi. On s'y attendait un peu. Mais, en plus, il est piloté à distance !

Une fois qu'il cesse d'envoyer ses données, quelqu'un envoie une commande pour désactiver l'appareil volontairement !

• The Day My Smart Vacuum Turned Against Me (codetiger.in)

Note: l'immonde illustration générée n'existait pas lorsque j'ai bookmarké ce site.

La fuite ?

Ce n'est pas un hasard si de plus en plus d'experts du numérique se tournent vers le retrocomputing ou le technopunk.

• La complainte du technopunk ringard (ploum.net)
• Un manifeste Offpunk (ploum.net)

Par exemple, le vénérable et très minimaliste navigateur web Dillo, relancé en 2024, après une petite décennie d'abandon.

Mais à quoi peut servir un navigateur qui ne supporte pas le JavaScript ? Bobby Hiltz explique comment il s'est mis à l'utiliser de plus en plus pour faire des recherches, lire les blogs et même écouter de la musique sur Bandcamp !

• Dillo Web Browser (bobbyhiltz.com)

Et non, ça ne scale pas. Le technopunk s'en fout de la mise à l'échelle ou de convaincre les investisseurs, il veut juste que ça fonctionne pour lui et ses potes.

• Against scale (tante.cc)

Cette même population fuit également de plus en plus la nocivité intrinsèque des réseaux sociaux.

Car suivre nos proches sur les réseaux sociaux serait en fait une mauvaise idée. Si les réseaux peuvent rapprocher des inconnus aux intérêts similaires, ce qu'ils ont fait à leurs débuts, ils peuvent également éloigner des gens proches dont les intérêts spécifiques ou les opinions diffèrent. Ils emprisonnent des groupes d'humains pleins d'énergie et de motivation dans un carcan consumériste (dédicace aux groupes Facebook qui se disent "anticapitalistes").

• Du risque de transformer nos amitiés IRL en relations parasociales (lalunemauve.fr)

Alors, certes, quitter Whatsapp n'est pas évident. Mais c'est possible.

• Résolution de la rentrée : quitter WhatsApp (www.baudelot.eu)

C'est par contre plus facile de quitter X…

Une image d'un meeting d'Hitler où une voix au milieu de la foule dit "Je reste sur X, mais c'est uniquement pour apporter de la contradiction" (posté par raphj@mamot.fr sur Mastodon)

C'est marrant, car ça me fait penser à ma nouvelle humoristique « Le dernier espoir » dans laquelle je mets justement en scène un handicapé numérique qui tente de lutter contre l'espionnage de toutes ces plateformes alors que sa famille essaye de le convaincre de les rejoindre. La nouvelle est dans le recueil « Stagiaire au spatioport Omega 3000 et autres joyeusetés que nous réserve le futur », disponible dans toutes les bonnes librairies, sur le site de l'éditeur (sans DRM) ou dans les archives d'Anna la pirate.

• Stagiaire au spatioport Omega 3000 (pvh-editions.com)

Un problème politique et social

Le pire, c'est qu'on ne vous ment (presque) pas : tout est dans les conditions que vous avez acceptées.

Nicolas Vivant insiste sur ce point : en cliquant "J'accepte", nous marquons notre accord pour être espionnés, mais, également, nous prétendons avoir l'accord de nos amis pour qu'elleux soient espionnés.

C'est notamment le cas de Whatsapp qui envoie toutes les infos de votre carnet d'adresses à Meta.

• Nous ne lisons pas les conditions d'utilisation, et c'est problématique (grenoble.ninja)

Bien que n'ayant plus de compte Meta sous quelque forme que ce soit, il existe un profil avec mon numéro de téléphone, tous les noms sous lesquels je suis renseigné dans les carnets d'adresses, un graphe de contacts qui permet de me situer précisément dans le tissu social. Sans compter les infos que j'ai données lorsque j'étais jeune et naẗf.

• Le suicide de mon compte WhatsApp (ploum.net)

Le plus effrayant, c'est que le fait que j'aie supprimé tous mes comptes doit certainement me faire apparaître dans une liste particulière qui peut-être utilisée pour tenter de me cibler avec des pubs qui vont me convaincre, puis pour s'assurer de me pourrir subtilement la vie et, enfin, pour me mettre sur la liste de "potentiels terroristes" le jour où le gouvernement de mon pays se mettra à suivre cette mode mondiale du fascisme.

Si j'étais Meta, par exemple, et que j'avais des infos sur un "réfractaire" à Meta et Google, je demanderais à Google de faire en sorte que les messages qu'il envoie via SMS se perdent un peu plus souvent. Que ses appels sonnent un peu plus dans le vide.

Nicolas oublie de préciser qu'il avait été estimé que si nous devions lire les conditions d'utilisation de tous les logiciels que nous utilisons, et leur mise à jour, 24h par jour n'y suffirait pas. L'acceptation des conditions d'utilisation est donc une pure fiction.

Le problème n'est donc pas que nous ne lisons pas les conditions d'utilisation. Le problème est que cette fiction permet aux entreprises de faire n'importe quoi. « Bien sûr que nous allons enlever son premier né pour boire son sang ! L'utilisateur a accepté ! »

Et il suffit d'une seule personne dans vos cercles sociaux qui accepte ces conditions en votre nom pour vous faire espionner.

Autrement dit, ce n'est pas de la faute de l'individu, c'est un problème 100% politique.

La preuve, c'est l'impact qu'a eu le RGPD dans le monde. Alors, certes, il n'est pas idéal et, en réalité, ne fonctionne pas vraiment.

• GDPR is a failure (nikolak.com)

Mais, quand même, le fait que tout le monde déteste le GDPR est un signe que c'est un pas dans la bonne direction. Il ne fonctionne pas vraiment, mais il fait très très peur aux grandes entreprises.

• matduggan.com

Reconquérir notre indépendance

Il est temps de réactiver vos comptes "indépendants" que vous n'utilisez pas, car "moins facile", "moins de personnes", "moins de dopamine",… Votre site perso, votre compte sur le Fediverse, vos expérimentations sur Gopher ou Gemini…

• Eternal 2020 (or not) (midnight.pub)
• Creating a Blog in Gemini:// (brennan.day)

Et surtout, de le faire avec vos petites mains, votre petit cerveau et toutes vos maladresses humaines.

Car quand vous publiez un billet de blog ou un post sur les réseaux sociaux qui a été généré par un chatbot, vos lecteurs s'en rendent compte. Très vite. Et ils arrêtent de vous lire instantanément. Et ils arrêtent de vous lire pour toujours.

Croire que ça ne se voit pas, c'est comme un fumeur qui pense que parce qu'il a éteint sa clope avant de rentrer dans une pièce, il n'empeste pas. C'est juste que le monde autour de vous est juste trop poli pour vous le dire franchement.

Comme le dit Bryan Cantrill, si vous pensez que personne ne va le remarquer, c'est que soit vous n'avez pas lu vous-même ce que vous postez, soit vous êtes devenu tellement incompétent en termes de lecture (pas d'écriture, de lecture) que vous n'êtes plus capable de lire correctement.

• The revolt of the reader (bcantrill.dtrace.org)

Comme je le disais, si vous ne prenez pas le temps de l'écrire, pourquoi devrais-je prendre le temps de le lire ?

• Soyez humains, communiquez ! (ploum.net)

Et si il n'y que la « performance » qui compte pour vous, vous êtes en train de détruire votre réputation. Pareil avec les illustrations générées. Le moteur de recherche Kagi permet de signaler les contenus qui sont du « slop » de manière à les cacher. Petit à petit des réseaux vont se mettre en place pour exclure les contenus générés. Et la réputation que vous êtes en train de construire aujourd'hui aura un effet demain. Plus vite que vous ne le pensez…

J'utilise personnellement le filtre AI Blacklist pour uBlock Origin. Il m'a arrêté bien des fois lorsque je suivais un lien. Et vous savez quoi? Je ne l'ai jamais regretté jusqu'à présent !

• AI uBlock Origin Blacklist (github.com)

D'ailleurs, il est grand temps de mettre vos filtres uBlock à jour vu qu'OpenAI tente désormais d'espionner votre comportement en ligne, même si vous êtes déconnecté de votre compte ChatGPT. J'avoue être bien content de n'en avoir jamais créé, même « pour tester ».

• ChatGPT now knows what you do on other websites via ad collector (www.buchodi.com)

Évitez le slop, évitez d'en générer et tentez de créer et de communiquer le plus loin possible des grandes plateformes privatrices. Bref, cultivez votre indépendance !

Vous allez voir, on y prend vite goût !

• Illustration : La Liberté guidant le peuple, de Delacroix

21 Sep 2026 8:16pm GMT

I switched from Docker to Podman in my homelab back in 2023, and settled on using Quadlets. I've been using this system for about three years, but it's a bit of a hassle to have to convert any and all Docker Compose files into separate Quadlet files.

If you're starting out with Podman, you might want to go read the blog post linked above, as it does contain some things to help you get started.

Having grown tired of doing that, I decided to revisit Podman Compose - taking the Compose files created by the upstream projects, and running them through podman instead of Docker. My previous trials with Podman Compose weren't that great, but somehow now things just worked.

While switching over my container stack I came across a few things that I had to change:

SELinux process labeling

For Traefik I had SecurityLabelType=traefik.process configured so that the process would be labeled with the correct SELinux context. To do this with Podman Compose I had to add

security_opt:
  - "label=type:traefik.process"

to the service definition.

User namespace mapping

Some of my containers use namespace mapping to make the original UID available to the container. I came across this blog post which details a lot of the Podman Compose extensions available.

Previously I had

PodmanArgs=--uidmap +1000:@1000:1 --gidmap +1000:@1000:1

which could be mapped to

x-podman.uidmaps:
  - "+1000:@1000:1"
x-podman.gidmaps:
  - "+1000:@1000:1"

in my compose.yml file.

Starting containers automatically at boot

When using Quadlets, systemd will make sure your containers are started at boot. When using Podman Compose, there's a service you can activate called podman-restart.service to basically do the same thing.

To enable it, run (as your Podman user):

systemctl --user enable --now podman-restart.service

If you check out /usr/lib/systemd/system/podman-restart.service, you'll see that the start command reads

ExecStart=/usr/bin/podman $LOGGING start --all --filter should-start-on-boot=true

The man page for podman-start tells us that the should-start-on-boot filter will instruct Podman to start containers with a restart policy of always or unless-stopped.

Automatic updating of containers

Quadlets also offer the feature of updating your containers automatically and restarting them when a new image is available.

In this blog post I found a nifty way to solve this problem:

I created the systemd timer ~/.config/systemd/user/podman-update@.timer:

[Unit]
Description=Podman update timer for %i

[Timer]
OnCalendar=daily
RandomizedDelaySec=900
Persistent=true

[Install]
WantedBy=timers.target

and the systemd service ~/.config/systemd/user/podman-update@.service:

[Unit]
Description=Podman auto-update service for %i
Wants=network-online.target
After=network-online.target

[Service]
WorkingDirectory=%h/containers/%i
Environment="DOCKER_HOST=unix:%t/podman/podman.sock"
Type=oneshot
ExecStart=/usr/bin/podman compose pull
ExecStartPost=/usr/bin/podman compose up -d
ExecStartPost=/usr/bin/podman image prune -f

[Install]
WantedBy=default.target

and enabling the timer (per Podman Compose project directory)

systemctl --user enable --now podman-update@<directory>.timer

Don't forget to update the WorkingDirectory in podman-update@.service to wherever you store your Podman Compose YAML files! I use ~/containers, with a subdirectory per project.

Now my containers get automatically updated and cleanly restarted too.

21 Sep 2026 8:16pm GMT

In the first part of this article, I explained how MariaDB Server can authenticate users using caching_sha2_password, and more importantly, how it is possible to migrate an existing MySQL user to MariaDB while keeping the same password. The solution works, but there is one obvious problem: it is mostly a manual process. For one user, […]

21 Sep 2026 8:16pm GMT

David Van Reybroeck pleit (nav bv #klimaatproblemen, drugsgeweld, … en het tanende geloof in #democratie) voor de oprichting van #burgerpanels in België naar model van de Duitstalige gemeenschap. Zo een permanent geloot burgerpanel kan los van partijpolitieke en electorale belangen meedenken en adviezen formuleren en blijkt in de praktijk een grote meerwaarde te kunnen hebben. Meer info vind je…

Source

21 Sep 2026 8:16pm GMT

Die PISA resultaten voorstellen als een wedstrijd waar je als land/ regio toch maar zo goed mogelijk moet scoren is kortzichtig! In dat rapport staat er immers zo veel meer dat het belang van die schijncompetitie overstijgt, over zaken die niet enkel over onderwijs-kwaliteit, maar over onze maatschappij gaan. Lezen, leesvaardigheid, leesplezier is zo een héél belangrijk aspect.

Source

21 Sep 2026 8:16pm GMT

Gabrielle Deman, de jonge naar avontuur en wetenschap hunkerende dochter van een Brusselse uitgever, trok in het begin van de 20ste eeuw als eerste blanke vrouw met haar man Commandant Sillye door de toenmalige Congo-Vrijstaat. Ze fotografeerde en verzamelde insecten en vogels voor het Afrikamuseum en documenteerde haar ervaringen in dagboeken en brieven die later ook in de collectie van het…

Source

21 Sep 2026 8:16pm GMT

Ahhhh … September! Geniet ervan, ook met "Tell me I never knew that" van caroline featuring Caroline Polachek! Watch this video on YouTube.

Source

21 Sep 2026 8:16pm GMT

41 years after bemoaning their friend Marcia Moretto who died from cancer in "Marcia Baila" (produced by Conny Plank) and 19 years after losing partner Fred Chichin to cancer, the other part of Les Rita Mitsouko Catherine Ringer died from cancer as well. Watch this video on YouTube.

Source

21 Sep 2026 8:16pm GMT

🚀 FOSDEM 2027: Showcase Your Open-Source Project to the World

FOSDEM 2027 is happening on January 30-31, 2027, at ULB Brussels-and your project could be part of it! As always, we're offering free stands to open-source projects to connect with the community.

What you can do at your stand

✔️ Present your project and engage with attendees

✔️ Demo your project live

✔️ Sell merchandise or collect donations

✔️ Hand out goodies and grow your contributor base

What we provide

✅ 1 table (180x80 cm) with chairs and a power socket

✅ Fast wireless internet for demos and presentations

✅ A spot for one or both days (choose what suits you best)

✅ Shared stands encouraged! (Joint submissions will be prioritized)

📅 Key Dates

• Submission deadline: October 31, 2026 (23:59 UTC)
• Accepted stands announced: November 8, 2026

🔗 How to Apply

1. Submit your proposal.
2. Add all team members who will be at the stand.
3. Wait for confirmation-and get ready for FOSDEM! 🎉

❓ Questions?

Reach out to us at stands@fosdem.org.

Share your submission with #FOSDEM and #FOSDEM2027. Spread the word about your project!

21 Sep 2026 8:16pm GMT

Proposals for developer rooms for FOSDEM 2027 can now be submitted!

Developer rooms are assigned to self-organizing groups to work together on open source and free software projects, to discuss topics relevant to a broader subset of the community, etc. Most content should take the form of presentations. Proposals involving collaboration across project or domain boundaries are strongly encouraged.

We want to continue to focus on promoting collaboration and community between different projects in niches which don't normally have their own spaces, rather than large projects with significant corporate backing.

For inspiration, some example rooms along these lines from recent years: Modern Email, Package Management, and Music Production.

As usual, we unfortunately have a very hard limit on the number of devrooms we accept due to the realities of the physical space available to us. Every year we must make difficult decisions about which great proposals must be rejected (in the past we could have filled the entire conference with every devroom about a different programming language!). If you submitted a proposal for a devroom in the last few years and got rejected, don't be disheartened and submit anyway!

Devroom coordinators must enter a complete schedule into our conference system by 7th December. It is particularly important to be available and to respond promptly to emails about the schedule for about a week either side of this date. We also require all proposals to be submitted directly by the speakers into our system.

• Saturday devroom schedules should contain between 7.5 and 8.5 hours of content, beginning at 10.30 and running until between 18.00 and 19.00.
• Sunday schedules should contain between 7 and 8 hours of content and start between 09.00 and 10.00 and run through until 17.00.
• No lunch breaks should be scheduled for devrooms.

If you don't think you can fill a full day, please try to join up with another project and submit a joint devroom application or indicate on the submission form that you are requesting only half-a-day and would like FOSDEM to try to pair you up with another similar request for half-a-day.

Because our room capacity is limited, we will record and stream all devrooms live. The recordings will be published under the same licence as all FOSDEM content (CC-BY).

Devroom submissions will only be accepted with at least two named managers who are responsible for the room.

If you have questions or need help crafting a good submission, contact us at program@fosdem.org.

The deadline for submissions is 4th October.

Key dates:

• 04 October: deadline for developer room proposals
• 20 October: accepted developer rooms announced
• 27 October (or earlier): developer rooms issue Calls for Participation
• 07 December (or earlier): developer rooms publish complete schedules

Note that the submission form should only be used by organisers of devrooms. If you want to submit a talk to a main track or devroom, keep an eye on the website until their Call for participation opens around October 27.

21 Sep 2026 8:16pm GMT

I believe any Open Source project with a commercial or institutional funding ecosystem should publish an official contribution record: who contributes, how much and over what period, what kind of work they do, which parts of the project they work on, and, where disclosed, who paid for the work.

The test for a good record is simple. A buyer should be able to answer three questions in about a minute: does this vendor contribute at all, how much do they contribute compared to other vendors, and do they work on the parts of the project I care about?

A good record serves both sides. Buyers get answers they can check, and vendors who contribute get credit for work that often goes unseen.

Of course, contribution does not prove that a vendor can deliver. It is one procurement factor alongside delivery capability, expertise, and price.

Vendor claims are hard to verify and compare

Say you need a vendor for your Drupal site, your Kubernetes cluster, or whatever Open Source software you use, and two firms bid. Both say they're deeply involved in the project, and both might be telling the truth by their own definition of "involved".

Without a project record, verifying those claims often means reconstructing each vendor's contribution history yourself.

The code repository seems like the obvious place to start, but even counting commits by vendor is not simple. A project has to connect individual contributors to the organizations that employed or funded their work, and those relationships can change over time.

More importantly, Open Source contribution can include documentation, support, event organization, governance work, promotion, and more. Much of that work happens outside the code repository or isn't recorded in a form a buyer can easily interpret. The data may all be public, but public is not the same as usable. A contribution record exists to close that gap.

Projects are best placed to decide which contributions matter

Drupal has tracked contribution credits since 2015, following a method I proposed in 2014 and now governed by the Drupal Association. Its system records more than code and gives credit not only to individual contributors, but also to the organizations and customers that fund their work.

Not every contribution counts the same. A contribution to Drupal Core or a strategic initiative earns more credit than one to a module that few sites use, and work on contributed projects counts for more when more sites depend on them.

Raw contribution data does not tell buyers which work matters most to the project. The project has the context to decide what advances its priorities and how different contributions should be weighted. Its record should publish those rules, link to the underlying contributions, and explain how mistakes are corrected.

In Drupal, contribution credits feed into the Drupal.org marketplace where buyers can look up agencies and compare them. While we have a strong foundation, we still have work to do to make the record easier to find, understand, and compare.

The record is the project's job, not the vendor's

A fair objection is that this puts the burden on the wrong party: if a vendor claims to contribute, the vendor should prove it, and the project shouldn't spend scarce time tracking contributions.

Suppose the two firms from earlier both send proof. Each proves its own numbers, in the measure it looks best on, and it is still not clear who has the better record. Buyers meet this problem everywhere, which is why procurement leans on third parties: auditors, certifiers, industry analysts, references.

For vendor contribution, the project is often the natural third party. The work happens inside it, so it has the data and is uniquely placed to express an opinion on the value and strategic impact of a vendor's contribution.

A contribution record is a way for a project to recognize its Makers and to say who it would like to see win bids. It also settles the question once, for every buyer, instead of every buyer auditing every bid.

A project should take on the burden when publishing the record is in its interest. Making contribution visible steers commercial work toward the vendors that sustain the project, and that work is what pays for the contribution. So the project gets more contribution, and public credit is how the project gives back to the vendors that contribute.

Projects can start with a simple record

Not every project may want or need a system as elaborate as Drupal's. How much record a project needs depends on how services around it are bought and sold: a project with hundreds of firms competing for work needs more than one with a handful of known vendors, and a project with no commercial ecosystem may not need a record at all.

For a small project, a text file in the official repository listing its recognized organizational contributors and what they worked on can be enough for a first version.

More complex ecosystems may need to categorize vendors, support searches by location, or weight different kinds of contribution. Whatever form it takes, the record has to be easy to find and quick to use.

So if you maintain an Open Source project with a commercial or institutional funding ecosystem, start publishing a contribution record and improve it over time.

If you buy services built on Open Source, ask for the project's contribution record. Decide at the start how contribution should count in your purchasing decision, then check bidder claims against the record.

Finally, if you fund Open Source, use the record to find contributors working on the parts of the project you want to support.

Where buyers and funders can consider contribution, I expect projects with clear records to see more commercial opportunities go to their maintainers than projects that rely on appeals alone.

Special thanks to Henry Poole for his contributions to this blog post, and to Sachiko Muto, Tiffany Farriss, Tim Lehnen, and Amandine Le Pape for their review.

21 Sep 2026 8:16pm GMT

Today Acquia launched a new brand, and my favorite part is the updated logo. Right under the Acquia name, it now says "Powered by Drupal".

Drupal has always been at the core of Acquia, but for the past 5 years it was less visible in how we described ourselves. Now it's front and center again.

But that is not the main reason for the rebrand. The bigger reason for the rebrand is to help people see what Acquia has become. Our products have evolved faster than awareness of them.

The new brand leads with content instead of digital experiences, and the homepage calls Acquia an "agentic content platform" rather than a "digital experience platform".

Acquia Source is our new command center, bringing content management, digital asset management, and web governance into one workspace. Acquia AI coordinates agent work across those tools.

For agents to work safely across these tools, they need content they can trust and clear rules for using it. Somebody still has to decide what is approved, who can use it, and where it can go. I wrote about that in AI and the great CMS unbundling, and the new brand puts that idea at the center of our story.

Drupal is well suited for that job. Structured content, granular permissions, workflows, and revision history are the things agents need to work safely, and Drupal has refined them for years.

Customers can use Acquia Source CMS, our fully managed Drupal SaaS offering. For teams that want full control over their Drupal sites, we offer Acquia Cloud. Acquia Source brings sites on either platform into a shared workspace.

As you scroll the new homepage, it builds up our technology stack one layer at a time, starting from Drupal.

Acquia leaning into Drupal is also good news for Drupal itself. It helps close the gap between Drupal and its reputation. Drupal is still often seen as a CMS that requires a developer for everything, even as improvements in recent years have made it easier for marketers to build pages and manage content themselves.

So alongside the new brand, we'll be investing more in helping the Drupal community evangelize Drupal, reaching developers and marketing leaders who may not have looked at it in years. I want more people to see what Drupal has become.

21 Sep 2026 8:16pm GMT