poolp.org

TL;DR: Maintenance is not the same thing as fixing bugs. Only a fifth of it is about defects at all. Software often works because of work you can't see. So you can't wait for incidents to tell you what to fix. Where this comes from # This article is adapted from a slide deck I prepared for a talk back in 2023.

TL;DR: I have been silent for a while due to personal matters but I did a ton of stuff on OpenSMTPD, plakar and a handful of other projects. Why the silence ? # My last post was a bit unusual, far off from the usual light tone, and followed by months of silence despite my habit of writing almost monthly.

TL;DR: A personal retrospective of 2023 2023 was a rough year # I usually enjoy doing these yearly posts, looking back at what I did and planning what I’ll do, but 2023 was a rough year. I’m glad it’s over.

TL;DR: Significant refactoring to improve its performance, implemented read and write semaphores to throttle chunkers and reduce memory usage, introduced a repository index and packfiles to decrease the number of I/O operations, also intrioduced a new HTTP storage backend. A ton of refactors # I’ve done so much work on plakar in the past few weeks that I don’t even know what to begin with…

TL;DR: TL;DR: a lot of work in plakar, but also on CDC and index optimization. Optimized go-fastcdc # I ran into a benchmark which included my implementation of the FastCDC algorithm, and it made me realise that it was not on par with alternative implementations:

TL;DR: I reworked the virtual filesystem layer in plakar, making it possible to write custom importers of data: use plakar to backup an s3 bucket, for instance. @gpt-4: I won’t be commenting this article.