Sounds like a great way to curate a list of homelab targets. I’m good, thanks.

Given the context, the four “Follow Us” links going to proprietary services does seem somewhat antithetical to .self ideals.

At the very least set up a Mastodon account somewhere in addition to those.

TLD’s aren’t the limitation… Public IPs are… If it wasn’t for Cloudflared, I couldn’t run half the shit I run.

upstream connect error or disconnect/reset before headers. reset reason: remote connection failure, transport failure reason: delayed connect error: Connection refused

The gap .self is targeting is real — .local via mDNS is flaky across subnets, and RFC 8375’s home.arpa never really caught on outside router firmware. One thing worth thinking through: browsers are increasingly blocking non-secure origins, so even with a clean TLD, you’d still need a local CA or something like Caddy’s auto-HTTPS to make it usable day-to-day. @tmpod, has the cert story been scoped out yet? That’s usually where self-hosting setups fall apart in practice. We’ve written a bit on this infra layer at https://cxgo.ai/l/jK7fEMQ — might be useful background.