https://hccf.onmy.cloud/wp-content/uploads/2026/06/dot-self.... > Everyone entitled to a subdomain at no cost How are you going to pay for the (substantial) cost of running a TLD without registration fee revenue? Is this a loss leader for other services? Are you operating on a 100% donation model? > No parking, squatting, or reselling How do you plan to tell the difference between a parked/squatted domain and one in…
.self: A new top-level domain designed to support self-hosting
61–70 of 410 posts
Re: .self: A new top-level domain designed to support self-hosting
#62Just use cloudflare with static hosting for things like this. Doesn’t load for me.
Re: .self: A new top-level domain designed to support self-hosting
#63Re: .self: A new top-level domain designed to support self-hosting
#64Earlier quoted context omitted.
The only mistake was not opening the root namespace altogether. It’s just a money grab.
The only mistake was not putting all US domains under .us, now the US has an an exorbitant privilege to print and enforce rules on new TLDs.
Re: .self: A new top-level domain designed to support self-hosting
#65Good luck getting your outgoing emails accepted by Gmail and outlook.
Re: .self: A new top-level domain designed to support self-hosting
#66Shotgun on your.self! That’s going to yield a ton of great second level sub domains :)
write.it.your.self
think.4.your.self
written.by.my.self
all CNAME -> claude.aiRe: .self: A new top-level domain designed to support self-hosting
#67Earlier quoted context omitted.
And you needed a gTLD for this task why?
We don't necessarily, however there are many benefits for doing so. We could simply purchase a domain and then build our initiative beneath it but then everything we do would be beneath that domain, meaning there would be two dots in what is our effective TLD. That would also mean we are a bit beholden to whichever TLD we are beneath and also whichever registrar we purchased our domain from. With the services we hope…
It's a commons-pollution problem. Are we going to have to start thinking of every word with a dot in the middle as a potential name? IMHO, a new gTLD is justifiable only when there's some concrete differentiator attached to it, e.g. .local indicating mDNS, or .it indicating "Italy"
What value is there in "horse.horse" being something you can resolve with DNS? What value does .self give me, as a reader, that .name or .me or any of the other zillion variations on the same idea doesn't?
If anything, it creates confusion! "Oh, I met Bob McBobFace. Is he mcbobface.me? mcbobface.name? mcbobface.local?".
I have no objection to providing people with free subdomains under whatever assignment scheme you guys are using, but wouldn't .net have worked too, and been a lot cheaper?
I guess I just don't get the value to the public of increasing the set of dotted word suffixes that indicate that a word is a a cognizable DNS object.
Re: .self: A new top-level domain designed to support self-hosting
#68https://hccf.onmy.cloud/wp-content/uploads/2026/06/dot-self.... > Everyone entitled to a subdomain at no cost How are you going to pay for the (substantial) cost of running a TLD without registration fee revenue? Is this a loss leader for other services? Are you operating on a 100% donation model? > No parking, squatting, or reselling How do you plan to tell the difference between a parked/squatted domain and one in…
We plan on operating the domain as a public good and are actively seeking sponsors to help fund us. Think of it as a similar model to ISRG and LetsEncrypt.
> No parking, squatting, or reselling
Our rule of one person per subdomain will hopefully prevent this at scale, though it will admittedly be more difficult to examine any particular domain so closely. We may have to implement some type of heartbeat where the owner of said domain has to respond within a certain amount of time.
Re: .self: A new top-level domain designed to support self-hosting
#69Re: .self: A new top-level domain designed to support self-hosting
#70Shotgun on your.self! That’s going to yield a ton of great second level sub domains :)