3 ms·
I have to say, .name always bugged me because it's dependent on ignoring all of us who share the same first+last names with others. It's like a TLD that purpose
by icebraining 7y ago
I have to say, .name always bugged me because it's dependent on ignoring all of us who share the same first+last names with others. It's like a TLD that purposefully implements [1]. At least the other TLDs are free-form, they don't purport to be some sort of registry of people.
[1] https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
- vidarh 7y agoIt didn't ignore it - we had lots and lots of long discussions about it, and the precursor - Nameplanet - was founded exactly because the alternative was worse; some of the most popular last names are shared by many million people, and a single person per TLD was able to make use of it. By sharing the second level, magnitudes more people would potentially be able to share it. My last name is extremely rare, but it's still ~400-500 people that share my last name; enough to exhaust all current tlds. When we founded Nameplanet, we did an extensive exercise to model it, and we bought ~60,000 domain names to maximize coverage of popular last names, and for very popular last names that obviously gave better coverage than .name, but in terms of first name / last name combinations it was better. Even for people facing collisions, it still meant much simpler addresses a lot of the time. Your objection is actually largely the opposite of the bigger problem in adoption: The number of people who want their name as their address is much smaller than we thought.