pleroma.debian.social

pleroma.debian.social

gagath | @gagath@pleroma.debian.social

Debian Developer, uploading.
she/her
https://people.debian.org/~gagath/

Views expressed here do not reflect the view of my past, present or parallel universe employer.

This, evidently, is what I look like when giving a talk these days.
Caricature drawing by Frank Tizzoni showing me in wizard garb with staff and laser pointer.

Move slow and fix things.

Today Igalia turns 25.

In September 2001, ten engineers from the University of A Coruña started a company with no outside investors, no managers, and no intention of ever appointing any.

There are now close to 200 of us, spread across the world. The arrangement has not changed: no managers, no shareholders, and everything we build left where anyone can use it.

Here is to the next twenty-five.
https://igalia.com/2026/09/21/Twenty-Five-Years-Upstream.html

Igalia's 25th anniversary banner. Three figures from the Igalia logo form the Roman numerals XXV, beside the words YEARS OPEN and a multicoloured circle marked 25th on a timeline arc.

In fact we organized a "rail ticketing challenge" to demonstrate the actual problems passengers face. Teams competed to find the best tickets for real world scenarios we posed to them … and discovered how difficult it can be. One policy maker summed it with their exasperated "but how were we supposed to know that…"

The inside of train with people sitting and standing all energeticaly looking at devices and talking.

Over the past few months, I have found myself under the spotlight on kernel mailing lists. What started as targeted discussions quickly turned into advocating for the kernel community to respect the mostly silent crowd of developers and maintainers who do not want to fully embrace AI usage. It appears this didn't go unnoticed, as shown by Jon Corbet's talk at Kernel Recipes. (1/5)

Jon Corbet showing a quote about empathy and AI during his talk at Kernel Recipes 2026

Now, for something completely different: https://notes.pault.ag/why-write/

while not my usual programming (or RF) fare, this post has been in the back of my head for a while now. I have finally put some words down after re-reading some 1940s era philosophical writing I couldn't let go of.

please enjoy with post with the love and intent I have imparted on it.

@werdahias Blinker lights for bicycle, front and rear (bicycle itself or helmet)

This post received a lot of comments and reactions, which is great!
It also proved that my little Raspberry Pi Zero W, powered by NetBSD, could handle the load.
Now - to help me test how much load it can tolerate - please boost and react to this post! 🚀



RT: https://rpi0w.stefanomarinelli.it/objects/01a03e3d-1e73-7928-b396-db17b7f0f60b

Happy 90th birthday to Margaret Hamilton, who led the development of the on-board flight software for NASA's Apollo Guidance Computer. Here she is in 1969, standing next to listings of the Apollo guidance software she and her MIT team produced.

black and white photo of a woman standing next to a stack of paper taller than she is.

for whoever needs to hear this: you're not alone. i'm not vibecoding any of the software i write. i'm writing it by hand, but i've leveled up my emacs with eglot/lsp. i'm modernizing my stacks and use languages with excellent compilers. i think about how to do more with less. i'm trying to combine the best human-written libraries and modules and assemble them with minimal boilerplate. i enjoy reading your manuals and references. i believe in robust, secure, human-written software.

@juliank fill the aero press, and wait for the g forces of an aileron roll to do the trick!
Picture of a stunt plane doing an aileron roll Picture of an aero press pour with coffee messed up everywhere after push

@juliank Poor pinkie

@disaster2life Hahaha, been there when young, and then owned a glorious 24 ports 100M switch that made unbearable noise in the bedroom

@olasd On dirait que le mainteneur upstream encourage à utiliser des exporteurs dédiés plutôt que de rajouter des scripts au dépôt, par exemple pour wireguard :

https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/issues/124

I think that settles it.

@olasd Par contre un truc sur lequel je doute c'est que par défaut le serveur écoute sur toutes les interfaces et c'est pas top niveau sécurité

Je ne sais pas si il y a une bonne pratique à ce niveau, peut être avec debconf, pour éviter les accès indésirables et demander aux utilisateurices de faire attention

Peut-être écouter sur localhost par défaut.

@olasd Ah, je ne connaissais pas. Upstream n'a pas l'air super réactif concernant les nouveaux scripts et j'ai besoin de créer un utilisateur et des règles apparmor pour limiter les droits au minimum.

L'avantage du serveur contre les tâches cron c'est aussi de pouvoir changer la fréquence de rafraîchissement directement en modifiant le polling time dans Prometheus

C'est surtout le premier point qui risque de me faire continuer je pense

ITP: prometheus-diskspin-exporter -- Monitor spinning rust disks in Prometheus.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126079

Now on for new beginnings.

i now own a high vis vest, life feels more complete

@olasd @zorume @fanny Je m'en suis fait faire chez Audika pour les bruits des gens dans les transports en commun. 70€ en boutique. J'ai pris le modèle "piscine" car il n'a pas de canal pour entendre les voix humaines (filtre), par contre pas certifié pour bruits dangereux. Prise d'empreinte sur place, arrive au bout d'un mois.

»