The post is a vision document for .self, a proposed generic top-level domain that would be run as a public good for self-hosters. The pitch is simple on paper: one person gets one free subdomain under .self, no parking or resale, and supporting services around it like easier DNS, TLS certificates, maybe shared mail, and client software that makes homelab publishing less painful. The operator says .self does not exist yet. They are applying in the current ICANN round and qualified for fee relief through the Applicant Support Program.
What landed was not the romance of a human-centered namespace. It was how many unresolved operational problems sit underneath it. The biggest one is identity. The whole model depends on proving "one person, one subdomain" without turning the project into a privacy nightmare or an exclusion machine for people without passports,
NFC documents, or credit cards. The organizer openly said they have not chosen a method yet and might start with credit cards. That answer made the project feel premature to many readers because the anti-squatting and anti-abuse story depends on that mechanism working.
The second hard reality is that running a
TLD is not mostly a DNS hosting problem. Several comments pushed back on the idea that this is just a few nameservers and some goodwill. ICANN application fees, registry compliance,
EPP and
RDAP support, and ongoing registry service provider costs are the expensive part. The sponsor comparison to Let's Encrypt did not persuade people because Let's Encrypt launched with a concrete technical and institutional plan. Here, the plan is still aspirational.
A lot of people also questioned the need for a new TLD in the first place. If the real value is easier self-hosting, shared mail, tunnels, or automation, those can be built today under an existing domain and migrated later if .self ever gets approved. The organizer's best answer was timing. ICANN rounds are rare, so if they want the root-level namespace they have to try now while building the rest in parallel. That came off as understandable, but still backwards to readers who wanted proof the service layer can work before the hardest regulatory piece is tackled.
The mood was shaped by long memory. Free or cheap namespaces like .tk became synonymous with abuse and wound up blocked by schools, social platforms, and security tools. New gTLDs like .zip and .mov were cited as examples of namespace expansion creating real security and usability problems. That gave .self a steep trust hill to climb. Even sympathetic readers liked the goal of making personal hosting easier, but they wanted a boring pilot on an existing domain, not a manifesto attached to a speculative TLD bid.