What a memory you have unlocked. They were everywhere. I remember the urban legend that .tk domains were X% of their GDP

>One Person, One Subdomain

Please submit this to us via our contact form, we will need lots of community input! https://hccf.onmy.cloud/get-involved/

I wish the Vega people had oriented their work around general-purpose zkVMs instead of application-specific ZK circuits. The latter is a fleeting efficiency win; the former is a permanent flexibility advantage. ZK-based privacy advocates shouldn't over-index on proof performance on today's systems when zkVM systems have been making multiple-OOM performance improvements over the past couple of years.

IOW, with Nova, the Vega people are trying to do something very clever (just as the BBS+ people are trying to do something very cleaver) that general-purpose compute wins have made unnecessary.

Something like RISC Zero will let you run arbitrary Rust code under zero knowledge in a few hundred milliseconds with little fuss. Nobody appreciates that identity verification is one special case of a vast set of useful applications enabled by widespread adoption of a ZK compute platform.

> 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?

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.

It's not clear whether they're actually talking about domains or subdomains there, which is a worrying sign from a potential registrar.

Indeed, this response is way more than we expected. Trying to set up a web cache now.

This is an idea at this point, the next round of gTLD applications is currently open and we are in the process of applying and we are trying to garner support!

Domain names are not centralized, there is no central entity that controls an approved list of kosher domains.

go.fuck.your.self would be a pretty good one

We are probably going to reserve some of the more obvious ones for specific purposes, e.g. my.self automatically pointing to a homepage on your local network. As we go through the gTLD evaluation process we will be keen to solicit feedback from the community on more specifics!

treat.your.self

  write.it.your.self
  think.4.your.self
  written.by.my.self

hug.your.self

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.

The only mistake was not opening the root namespace altogether. It’s just a money grab.

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.

How about .mine?

Indeed that appears to be so O_O. Our site is of course self-hosted, this is quite the response. Will have to troubleshoot what the bottleneck is!

Apt for self-hosting

yes and it's not even on the front page yet lol

We have considered this, all of these things will be examined during the evaluation process of the application with ICANN before any approval to operate the TLD is granted. We could also police our domain and revoke users who use it for abuse but that may be too costly. But you are right that fundamentally we must protect the reputation of the TLD at all costs and that will require imposing certain limits on its use.

You should read their proposal. Specifically, the first "core feature": one person, one domain. If you want to squat on a domain, go for it -- it's yours, and that's the only domain you're getting.

I suppose this will be done by ID verification, which is a complete and total non-starter for me, but they do have a vision of some kind.

Seems like an idea that would be abused badly, quickly

Some of them, the more corporate or tech-focused ones like .ai or .inc or .tech or .llc. Very many of them are comparable within a dollar of .org.

We did not expect this level of response, it should be reachable now.

This is just a fact. It's a ponzi scheme.

I CANN, YOU CANN, Yes We CANN!

I am disappointed that icannt.org is taken and is not an alternative root.

Edit: I've been rate limited because of this comment, apparently. Account burned - will make a new one. Dang says below it's because of flagged comments but I don't see many flagged comments in my history.

We plan to operate a shared mail server than can be used by users of the domain and we will work to ensure it is trusted by imposing usage limits. We will assume that every endpoint in our domain is someone's personal homelab, meaning small-scale use. For large mailing campaigns and newsletters there are plenty of services to choose from that enable those but for just sending personal emails, it should work.

lovethy.self

As I understand it, if you want to use domains internally for your home ("home") network, there's some DNS support for "home.arpa"[0].

0 - https://www.rfc-editor.org/rfc/rfc8375.html

That's no use for self-hosting unless all your users are on your private network.