I feel like a lot of the "it was DNS" is conceptually oversimplifying, and masking true root cause(s). It makes sense to centralize naming, It makes sense to abstract naming away from IP addresses. Many of these outages are "this other thing broke, and it made DNS break". Most folks would never say "it was DNS" when it was a network problem that was preventing reaching the DNS servers. But a lot of the time, this isn't much different from that. Don't get me wrong, every outage is an opportunity to learn and improve, both locally and centrally. I just want to shift the conversation to "it was DNS, because ...", and help people make informed risk trade-offs.

One of my buddies from high school and college became a sommelier at some fancy places, and it's been such a great career fit for him, knowledge / trivia, plus insight, plus talking to people and helping them, plus a little bit of performance/ shmoozing but not too much.

@npub12lxt...jvjy Hi, it's me, the guy with an unreasonable number of keywords in some of my filters. 😅 Do you remember when the change happened that caused the problem where filters above a certain size are no longer editable? I was going to file a bug about it, to suggest maybe warning the user so that they don't end up creating filters that cannot be edited. I want to be specific about what version it appeared in. (I assume the issue is upstream of glitch-soc?) I searched for an existing issue, but couldn't find one. If you know that one got created at that time, please connect me?