Have you been feeling low on oil recently?

Clean! This would take me at least three times as long.

mmm valonia ventricosa

A Cryptography Engineer’s Perspective on Quantum Computing Timelines The risk that cryptographically-relevant quantum computers materialize within the next few years is now high enough to be dispositive, unfortunately.

Two papers came out last week that suggest classical asymmetric cryptography might indeed be broken by quantum computers in just a few years.

That means we need to ship post-quantum crypto now, with the tools we have: ML-KEM and ML-DSA. I didn't think PQ auth was so urgent until recently.

A british shorthair cat laying on a sofa looking tired and showing its teeth

screenshot of the first page of my “Stamp It! All Programs Must Report Their Version” blog post: Recently, during a production incident response, I guessed the root cause of an outage correctly within less than an hour (cool!) and submitted a fix just to rule it out, only to then spend many hours fumbling in the dark because we lacked visibility into version numbers and rollouts… 😞 This experience made me think about software versioning again, or more specifically about build info (build versioning, version stamping, however you want to call it) and version reporting. I realized that for the i3 window manager, I had solved this problem well over a decade ago, so it was really unexpected that the problem was decidedly not solved at work. In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response. […]

screenshot of the last page of my “Stamp It! All Programs Must Report Their Version” blog post: Conclusion: Stamp it! Plumb it! Report it! My argument is simple: Stamping the VCS revision is conceptually easy, but very important! For example, if the production system from the incident I mentioned had reported its version, we would have saved multiple hours of mitigation time! Unfortunately, many environments only identify the build output (useful, but orthogonal), but do not plumb the VCS revision (much more useful!), or at least not by default. Your action plan to fix it is just 3 simple steps: Stamp it! Include the source VCS revision in your programs. This is not a new idea: i3 builds include their git-describe(1) revision since 2012! Plumb it! When building / packaging, ensure the VCS revision does not get lost. My “VCS rev with NixOS” case study section above illustrates several reasons why the VCS rev could get lost, which paths can work and how to fix the missing plumbing. Report it! Make your software print its VCS revision on every relevant surface, for example: […]

New blog post 🥳

Stamp It! All Programs Must Report Their Version

In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response.

Read more: michael.stapelberg.ch/posts/2026-0...

#nix #golang #linux

We're not ready

KubeCon + CloudNativeCon Europe 2026 Explore this photo album by Cloud Native Computing Foundation on Flickr!

#kubecon #cloudnativecon photos are online www.flickr.com/photos/14324...

Liminal Tides, by Appleblim 6 track album

dropped today, digital is half price for the next week+ quietdetails.bandcamp.com/album/limina...

lao gan maxxing

rwxr--r--://

It looks like an envoy error message

what did she mean by that

the purpose of a rube goldberg machine is what it does eventually

How to Scale a System from 0 to 10 million+ Users Scaling is a complex topic, but after working at big tech on services handling millions of requests and scaling my own startup (AlgoMaster.io) from scratch, I’ve realized that most systems evolve thro...

This was very well organized and I generally agree with all of the scale and architecture guidance

blog.algomaster.io/p/scaling-a-...

From the sciencefiction community on Reddit: My e-Reader Just Created the Shortest Horror Story Ever Explore this post and more from the sciencefiction community

Dun dun daaah

TUIs for observability! 💯🤌

🚁 talos-pilot — TUI for managing/monitoring Talos Linux k8s clusters

⚡ Real-time node health, logs, diagnostics, etcd status & safe production ops.

🦀 Written in Rust & built with @ratatui.rs

⭐ GitHub: github.com/handfish/tal...

#rustlang #ratatui #tui #talos #k8s

4 panels of a Garfield strip. Garfield is making weird facial expressions in each panel.

make the terminal collect lint after not typing for a while

Picture of a Lidl gift card which has a blue background with differently sized yellow circles on it. google balls ?

is #lidlballs anything?

it's going great

[derive(Answer::Life, Answer::Universe, Answer::*)]

my year of posting has begun(?)

Gumpy and Salad eating breakfast from the same plate

Gumpy the unsocialized street kid having breakfast with Salad, the big sheltered doofus who, through sheer willpower, stupidity, and immense patience, became her best friend ❤️

A british shorthair cat, standing on a white cupboard in front of a white background. Its tail casts a shadow. It's got short wittle legs.

His name is Rusty!!!

A Garfield magazine promotion: "GARFIELD-Telefon zu gewinnen"

I often think of Gumpy as this hardened street cat, but it's easy to forget she's just a kid

recently, she's started playing with salad!

it's in moments like these where her (somewhat awkward) playfulness shines through in the most adorable way ❤️