Right now you can create a public ID and that is your domain name, this is nice because it prevents domain name squatting, 1+ for this solution. On the other hand I think it limits what we can actually do, with our domain names. For instance if I in the future register public ID “crypto”, I would be able to register names like:
safe://crypto.cat or safe://crypto.dog, but if someone else wish to register safe://crypto.money they can’t and they get an error. Even worst if they registered the public ID “crypto” after I did, it’s seen as a valid option, which is a little deceptive, because no matter what they’ll never be able to register/upload an “crypto” domain. Personally i think it’s a waste to go down this path, because on the current internet many domain names are possible.
The current setup creates three problems
- People have to create a new account through launcher, because if they are the second to use public ID “crypto”, they can’t use the domain name.
- People have to create a another domain name, because they are not warned that they cannot use public ID “crypto”
- If the two processes above cost people money, they might get angry maybe…
There could be a few solution to this problem, for instance if you register a public ID, instead of getting an error, the second person gets a message to buy the “crypto” domain that they want to use. If I’m not using safe://crypto.money why should someone else not be able to use it? This is just one option, but I think it’s better than letting people create another launcher ID & public ID, with a cost attached to it al. Incase people feel that the first person to register the public ID, should not get a SAFEcoin, the SAFEcoin could be recycled when the second person wants to register a same public ID.
In the example above I foolishly assume that .safenet will eventually become whatever the user choose too…