> That works great until the only names that are left are all too long to remember. Do you really believe this is a serious problem? I don't think it is by any

> That works great until the only names that are left are all too long to remember. Do you really believe this is a serious problem? I don't think it is by any stretch of the imagination. --- > It seems like the answer is "everyone buys their own TLD", right? Yeah, why not? The conceptual distinction between a domain and a TLD isn't necessary. From the Namebase docs: > For instance, if you own "nakamoto" on Handshake, you can use "nakamoto" as a domain itself. In that case, you would point "nakamoto" to your website and visit it at http://nakamoto/ http://nakamoto/ in your browser. You can also use "nakamoto" as a TLD and issue your own subdomains. In that case you can create "satoshi.nakamoto" and visit it at http://satoshi.nakamoto http://satoshi.nakamoto in your browser. A Handshake name can be used as both a domain name directly and as a TLD at the same time. --- > And if you buy space from someone else's TLD, well... you've just given someone the power to censor you. Maybe? Buying from someone else's TLD isn't the point of Handshake, for the reasons I mentioned above. But if you wanted to buy a subdomain for some reason, and still wanted it to be uncensorable, you should buy one from someone who revokes their censorship capabilities programmatically. And that point is the big picture: reasoning about transparent code for very important things gives you a level of control you can't obtain through trusting people.