Tootfinder

Opt-in global Mastodon full text search. Join the index!

@frankel@mastodon.top
2026-02-12 09:04:57

How to Make #Architecture Decisions: #RFCs, #ADRs, and Getting Everyone Aligned

How to Make Architecture Decisions: RFCs, ADRs, and Getting Everyone Aligned
Making architecture decisions is one of those things that can go really well or really badly. I’ve been in both situations. I’ve seen…

@nebucatnetzer@social.linux.pizza
2025-11-13 17:08:39

It's this time of the year again, this weekend is #ZHF in Rapperswil.
After having participated in a few of those I was very happy when I discovered this RFC a few days ago.
gith…

rfcs/rfcs/0180-broken-package-removal.md at master · NixOS/rfcs
The Nix community RFCs. Contribute to NixOS/rfcs development by creating an account on GitHub.

@crell@phpc.social
2025-12-04 16:39:48

I currently have 4 in-flight RFCs for PHP, and one more I'm trying to launch soon. I'm not actually paid for any of this.
I think I may be the problem...
#PHP #OpenSource

@usul@piaille.fr
2026-01-26 02:06:22

What came first: the CNAME or the A record?
blog.cloudflare.com/cname-a-re

What came first- the CNAME or the A record
A recent change to 1.1.1.1 accidentally altered the order of CNAME records in DNS responses, breaking resolution for some clients. This post explores the technical root cause, examines the source code of affected resolvers, and dives into the inherent ambiguities of the DNS RFCs.