As it stands now, I think you have to be very quick to get org, com or net as public id when the Safe network becomes persistent.
The public id (longName) has to be minimum 3 characters long, so the language top-level domain ‘replacements’ aren’t possible.
Currently I think until the SD is full (100 KB), though the services list could be made to reference immutable data instead, in which case there’d be no fundamental limit.[quote=“draw, post:21, topic:10871”]
The public id (longName) has to be minimum 3 characters long
[/quote]
I’m pretty sure that’s a demo-app limitation, the vault network can’t even know because the long name isn’t stored anywhere. It’s hash is simply used as the DNS identifier, and SHA256 works fine with merely one character as well.
This still doesn’t establish a central entity controlling domain name registration except for existing TLDs, and as long as people don’t register a name under one of those TLDs they don’t have to interact with that entity at all. However, it seems like there’s a lot of value for users in being able to use existing domain names and having them belong to the same people who have them on the clearnet (for instance, getting to MIT’s homepage by going to mit.edu or Ubuntu’s homepage by going to ubuntu.com) along with the considerations from the original post about making adoption easier by not forcing organizations/companies to rebrand. This isn’t really possible without putting those names under some kind of centralized control (directly or indirectly through clearnet DNS checks) since otherwise the names will go to whoever is fastest to the draw/has the most safecoin/etc and there’s no way to know for sure whether they’ll cooperate to hand those names off to the people that users expect to own them.
In any case, this probably shouldn’t apply to all existing TLDs either, since most of them are new ones that basically no-one uses except for domain name trolls or people trying to protect themselves from domain name trolls. So, the TLDs that this pre-registration applies to are probably just going to be the original gTLDs (com, net, etc.) and country code ones (se, io, etc.), while the newer ones (sucks, meme, etc.) will still be open for anyone to claim.
In speaking of TLDs with open registration, one interesting side-effect of the hierarchical DNS system is that people can create their own TLDs if they find good names that aren’t taken yet and manage the set of sites registered under those themselves, and if that is done correctly there might be an interesting set of community-run TLDs that forms out of this. Also, when the network gets computation/smart contract capabilities we might be able to implement a few self-managing TLDs which allow people to automatically register names under them according to certain policies (which could be used to implement some of the other interesting domain name registration schemes that people have been throwing around recently).