upvote

points

by functionmouse23 hours ago |
comments
upvoteby HumanCCF23 hours ago|
next
[-]
Our goal is for .self to be more than just another TLD string, we want to specifically empower the self-hosting use case with local clients that integrate directly with the TLD and operate shared services like mail servers as a public good. We want to dramatically simplify the effort it takes to set up a domain for homelabs and offer free services that are directly tied to the domain like email.
reply
upvoteby quotemstr23 hours ago|
parent|
[-]
And you needed a gTLD for this task why?
reply
upvoteby HumanCCF22 hours ago|
parent|
[-]
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 to offer around things like TLS certs and emails, it just makes more sense for use to own the whole thing from the root.
reply
upvoteby quotemstr22 hours ago|
parent|
next
[-]
<something>.duckdns.org. works fine, and being "beholden" to ICANN is no worse than being a client of one of the big traditional gTLDs. If you want "one person, one name", well, .name is there for that.

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 <something>.self give me, as a reader, that <something>.name or <something>.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 <something>.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.

reply
upvoteby HumanCCF22 hours ago|
parent|
[-]
> 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"

So the new gTLD round is open right now, we're getting more TLDs whether we like it or not. Our goal is to make one that has features built-in which cater to the self-hosting use case. So that is our key differentiator, that every endpoint leveraging our TLD should be someone's small-scale homelab setup.

> I have no objection to providing people with free subdomains under whatever assignment scheme you guys are using, but wouldn't <something>.net have worked too, and been a lot cheaper?

Technically yes it could work, but given the suite of features we'd like to build into our TLD, it would make things more difficult if we didn't own it. We would be dependent on external parties for our root domain, the root of trust for TLS certificates, all users' subdomains would have an extra dot etc.

reply
upvoteby akerl_20 hours ago|
parent|
[-]
It just feels a bit like you've decided to solve the hardest possible side quest first.

Everything else on your roadmap could have been built and shipped in the universe that exists, and then if down the road it's working, you could have aimed for your own TLD.

Instead you're putting the TLD first and any of the actual functionality that end users might want afterwards.

reply
upvoteby HumanCCF19 hours ago|
parent|
[-]
That is a fair criticism, however I would say that the reason we are going for the TLD now is because now is the only time we can do it. The last round of TLD applications was in 2012, so if we don't apply now, it could be a veeery long time before the opportunity comes around again. We are a new org and our goal is to build functionality in parallel with the ICANN application which will likely take years to resolve.
reply
upvoteby akerl_19 hours ago|
parent|
[-]
Are you working on the not-TLD parts in parallel? If you don't get the TLD, do you plan to launch on a more traditional domain?

The marketing stuff makes it look like the TLD is your main focus.

reply
upvoteby psychoslave12 hours ago|
parent|
prev|
[-]
You can't purchase a domain, only rent it. If anything, going through a "pay to get a temporary monopoly on some virtual object" is the very opposite of empowering people with more autonomy as the project seems to try to support.
reply
upvoteby 9dev23 hours ago|
prev|
next
[-]
The only mistake was not opening the root namespace altogether. It’s just a money grab.
reply
upvoteby microgpt23 hours ago|
parent|
[-]
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.
reply
upvoteby kmoser22 hours ago|
parent|
next
[-]
What do you mean by "US domains?" Domains registered by US citizens? Hosted in the US (in which case does that include territories)? Regardless of the definition, I don't see an easy way to do this, nor a reason to, since domains can change hands (and hosts) across countries.
reply
upvoteby NewJazz22 hours ago|
parent|
next
[-]
.edu and .gov are us-specific, not sure if that is what they are referring to.
reply
upvoteby microgpt19 hours ago|
parent|
prev|
[-]
Domains that fall under the jurisdiction of the US? The domains themselves not the websites they point to? Everything under .games is controlled by the US government, the German government gets .games.de instead. To be fair it should be .games.us and .games.de (or .spiele.de)

Even gTLDs using other languages, like .kaufen, are under US jurisdiction. A German website selling to German customers using a .kaufen domain is forced to abide by US law as well as German law or loses the domain. Using a .de domain they would only have to abide by German law. That's unfair that the US government gets to stick its grubby fingers into every TLD that isn't a country code.

reply
upvoteby weakened_malloc18 hours ago|
parent|
[-]
> That's unfair that the US government gets to stick its grubby fingers into every TLD that isn't a country code.

You're right in a sense, but the US invented the internet, so they get to invent the rules, no?

reply
upvoteby dgellow22 hours ago|
parent|
prev|
[-]
I mean, that wasn’t done by mistake
reply
upvoteby philipallstar22 hours ago|
parent|
[-]
Sometimes hindsight is 1/20.
reply
upvoteby namegulf21 hours ago|
prev|
next
[-]
That's a popular tld for 'me' domains, like you said it's closer to .self in meaning but has better appeal

However .me (https://namegulf.com/tld/cctld/me) is a ccTLD managed by the Government of Montenegro, they set their own rules

reply
upvoteby pezezin15 hours ago|
prev|
next
[-]
I have the opposite opinion, TLDs should have been restricted to ISO 3166 codes only, with only a few exceptions for international organizations and private networks.
reply
upvoteby AlienRobot22 hours ago|
prev|
next
[-]
I think letting anyone make any TLD is a bigger mistake.

.zip .pdf .mp3

I'd like to thank Caribbean island of Anguilla for having a ccTLD that helps identify which websites aren't worth your time in one quick look.

reply
upvoteby croes22 hours ago|
prev|
[-]
How about .mine?
reply