Status Report - Week 24 2025

Real life

This week is the first in a series of four "logistically challenging" ones. Lyla finished her school year, but she's also starting her first one week internship at my brother's in Clermont-Ferrand. We travelled for most of the day Saturday; it was a bit long but uneventful. I'm writing this in the train back to the North, with a stop in Lille on Tuesday.

One advantage of (long) travels is that they're an opportunity to make progress on my (very long) reading list. This week I crossed out Snap, a typical airport novel you enjoy but forget after 5 minutes, and Working in public, particularly interesting as I'm asking myself many questions about what I want to do professionally in the future.

In Clermont-Ferrand, we went to Les Nuées Ardentes, an event that the university organizes every year where various departments make nice demos about their field. We solved a cool "cryptography escape game", measured the propagation speed of waves, or saw how carbon dioxyde makes water more acidic. It's really nice to see passionate people take (personal) time to freely share their passion with others.

Open source

The main event this week is that one of my patches to lists.sr.ht broke delivery to mailing lists :-( Fortunately I happened to see that the patch had been integrated and soon after tried to submit another patch that did not seem to be received... so I let folks know on IRC that things did not seem to work, and Drew DeVault quickly deployed a fix.

I'm still pondering whether writing a COE for this would be of any value, but I've already taken the action to add support for full inbound email processing in sr.ht-container-compose (patch). This will allow to properly end-to-end-test changes to lists.sr.ht, instead of using a partial workaround based on imports (yes, I would have spotted the issue with my patch with this...).

Robin Jarry also made the inbound delivery flow more robust to archival errors so all in all my mistake triggered good improvements to the service.

And finally on the aerc front, following a report that marking messages read felt slower with master than 0.20, I wrote down a set of nominal scenarios involving read/unread status. Thanks to this (super boring) exercise, I identified three issues with my recent commits ( 1, 2 and 3), and the root cause for a long-standing issue with Office365 (fix).

I also root-caused the reported slowness to a Zoho specific issue, that I'll try to workaround this week.