gumpy now has her own account! (i think she's trying to emotionally manipulate you to follow her)
GUMPY@gumpy.acegikmo.com · last wk.
Domi
@domi.strct.net
i run the nix. i write the rust. i deploy the cluster. bio
GUMPY@gumpy.acegikmo.com · last wk.
Last year was a blast. Sign me up!
Sidero@siderolabs.com · 2mo agoSave the date because TalosCon is back! October 15–16, 2026 · Amsterdam Join us for two days packed with talks from people running Talos in production. Full details and agenda coming soon. Get your name on the list here → www.siderolabs.com/taloscon #TalosCon2026 #kubernetes #TalosLinux
I still don't get how someone could've abandoned this little lady look at her 😭❤️ she's not even grumpy anymore why did i name her gumpy
If you work in tech and had to patch your software last week you'll know this cycle isn't sustainable. Last year there were more than 100 CVEs every day. There's no way this is maintainable. www.siderolabs.com/blog/patchin...
Patching Won't Save You - Sidero Labs
Your patch windows and testing process is going to get your hacked. It's time to move from reactive vulnerability management to proactive software curation.
siderolabs.com
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 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.
words.filippo.io
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
![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.
[…]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eb3563jmh2vjnrlkwujxqdwg/bafkreibmyjp2vprkz3vd4quze4ptlmt5sgz32mjc2bycogzwu6ps2odxpq)
![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:
[…]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eb3563jmh2vjnrlkwujxqdwg/bafkreie44kyf3bi262fe6se54yj26txtvxmx6dwqk6jrtqhum7a7is2gs4)
dropped today, digital is half price for the next week+ quietdetails.bandcamp.com/album/limina...
Liminal Tides, by Appleblim
6 track album
quietdetails.bandcamp.com
the purpose of a rube goldberg machine is what it does eventually
This was very well organized and I generally agree with all of the scale and architecture guidance blog.algomaster.io/p/scaling-a-...
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...
blog.algomaster.io
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
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 ❤️
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 ❤️
I'm going to install all of these and then I will clap. And whistle. And so the symphony begins.
