Reposted by DomiJon Gjengset @jonhoo.eu · 29/08/2026I got a 2-meow server rack. Highly recommend. 381555145
Reposted by Domialy @aly.codes · 10/08/2026Anyone else enjoy a shower monster while debugging FluxCD reconciliation failures on their nix box? 7543
Reposted by DomiFreya Holmér @freya.bsky.social · 28/07/2026gumpy now has her own account! (i think she's trying to emotionally manipulate you to follow her) 92324
Reposted by DomiSteve Klabnik @steveklabnik.com · 17/07/2026👀👀👀 github.com/tokio-rs/top... #rust-langgithub.comGitHub - tokio-rs/topcoat: A batteries-included framework for building web appsA batteries-included framework for building web apps - tokio-rs/topcoat 1318216
Reposted by DomiFreya Holmér @freya.bsky.social · 07/05/2026I 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 529412
Reposted by DomiJustin Garrison @justingarrison.com · 04/05/2026If 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...siderolabs.comPatching Won't Save You - Sidero LabsYour patch windows and testing process is going to get your hacked. It's time to move from reactive vulnerability management to proactive software curation. 053
Reposted by DomiFilippo Valsorda @filippo.abyssdomain.expert · 06/04/2026Two 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.words.filippo.ioA Cryptography Engineer’s Perspective on Quantum Computing TimelinesThe risk that cryptographically-relevant quantum computers materialize within the next few years is now high enough to be dispositive, unfortunately. 11303123
Reposted by DomiMichael Stapelberg 🐧🐹😺 @zekjur.bsky.social · 05/04/2026New 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 3113
Reposted by DomiChris Aniszczyk @cra.dev · 27/03/2026#kubecon #cloudnativecon photos are online www.flickr.com/photos/14324...flickr.comKubeCon + CloudNativeCon Europe 2026Explore this photo album by Cloud Native Computing Foundation on Flickr! 184
Reposted by DomiDavid James 🍩 @funkentechno.bsky.social · 18/03/2026dropped today, digital is half price for the next week+ quietdetails.bandcamp.com/album/limina...quietdetails.bandcamp.comLiminal Tides, by Appleblim6 track album 153
Reposted by Domipotion of @candlestick.bsky.social · 21/02/2026the purpose of a rube goldberg machine is what it does eventually 172735529
Reposted by DomiJustin Garrison @justingarrison.com · 13/02/2026This was very well organized and I generally agree with all of the scale and architecture guidance blog.algomaster.io/p/scaling-a-...blog.algomaster.ioHow to Scale a System from 0 to 10 million+ UsersScaling 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... 2397
Reposted by Domiqntm @qntm.org · 31/01/2026Dun dun daaahreddit.comFrom the sciencefiction community on Reddit: My e-Reader Just Created the Shortest Horror Story EverExplore this post and more from the sciencefiction community 09115
Reposted by DomiOrhun Parmaksız @orhun.dev · 14/01/2026TUIs 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 0166
Reposted by DomiFreya Holmér @freya.bsky.social · 28/12/2025Gumpy the unsocialized street kid having breakfast with Salad, the big sheltered doofus who, through sheer willpower, stupidity, and immense patience, became her best friend ❤️ 42287
Reposted by DomiFreya Holmér @freya.bsky.social · 17/12/2025I 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 ❤️ 628717
Domi @domi.strct.net · 15/12/2025I'm going to install all of these and then I will clap. And whistle. And so the symphony begins. 020
Reposted by DomiSidero @siderolabs.com · 20/11/2025#TalosCon2025 recordings are live! 🍿 Hope you have some free time today, because you’re going to want to check this out. We’ve got a keynote from Bryan Cantrill on complexity, talks on Hetzner, compliance frameworks & more. Enjoy 👉 www.youtube.com/playlist?lis... #kubernetes #DevOps #TechTalksyoutube.comTalosCon 2025Did you miss this year's TalosCon and all our great talks? Not to worry! You can watch them here instead of going outside. Hear from folks like Bryan Cantrill and Michael Cade, topics like compliance and Hetzner, and just about everything between. 053
Reposted by DomiMince Dinner @scw.bsky.social · 11/10/2025Franz Kafka writing Steam reviews 123167693
Reposted by DomiMachinePix @machinepix.bsky.social · 07/10/2025Snailbot is a self-reconfigurable robot using rocker-bogie suspension by The University of Hong Kong, Shenzhen. 926665
Reposted by DomiHeba Elayoty @helayoty.org · 06/10/2025Most people think the Kubernetes scheduler makes scheduling decisions itself. Well, it doesn’t. The real power lies elsewhere. 🧵 Let’s talk about how the kube-scheduler is actually a plugin-first orchestration engine, not a decision-maker. 1124
![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)
![4-panel vertical comic. (1) 100 Years Ago [two people standing next to bicycle with small car nearby] PERSON 1: It’s too dangerous riding a bike with these cars around. I should get a car, too. (2) 50 Years Ago [two people between smaller car and bigger car] PERSON 2 with short hair: Small cars are less safe in collisions with larger vehicles, so I should get a bigger one. (3) Today [two people between big car and even bigger car] PERSON 1: Everyone has huge SUVs now. If I don’t get the biggest one, I’m putting my family at risk. (4) Soon [two people next to large armored car with spiked clubs attached] PERSON 2: If I don’t install more whirling spike clubs, I’ll be destroyed by all the other drivers who...](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:cz73r7iyiqn26upot4jtjdhk/bafkreiby6can6k76yzfmv2czxs4pu2l7zie7bqbrpswi7h3ifmiadkuqvu)
