Decentralized Everything: Chat, Self-Hosting, Dark Web
Three threads are circling the same instinct. Parley proposes federated IRC-style chat where every person or team runs their own instance, discoverable via DNS. The self-hosting on the dark web thread discusses Tor onion services as a way to skip port forwarding, CGNAT, and public IP exposure entirely. The 'Don't couple your Go code to GitHub' thread argues that vanity import paths on your own domain protect your project from platform dependency, with pushback that custom domains disappear when you stop paying bills.
The pattern: a genuine re-examination of centralized dependencies is happening across layers of the stack. Chat, code hosting, and server infrastructure are all seeing proposals to move control back to individuals or small teams. This is not new as an idea but the specific implementations being discussed are more practical than previous waves.
The counterpoint is real: GitHub probably outlives your domain registration. Onion addresses are impossible to share verbally. Parley spam is unsolved. The decentralization instinct keeps bumping into the convenience and reliability of centralized services, which is why these cycles repeat.
So what?
For founders building developer tools or infrastructure, the demand signal for self-hostable, protocol-based alternatives to platform-controlled services is clearly there. The gap is usability: every decentralized proposal in these threads gets immediately challenged on the user experience tradeoffs. Whoever solves the UX problem wins the category.