[ailideex]

> We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized.

I very much want this also - but this cannot be solved in the same way as the challenge of business domain name assignment - a different approach should be used:

[idx].[yyyyddmm].[given_names].[family_name].id

e.g.

023.19830210.john_smith_3rd.doe.id

given_names can have some standard seperator

And then if there are two people with same given names with same family name they get different indexes. And this will get everyone riled up because this means you will need a worldwide consistent database of people and you will only be able to get this if you give very good proof of ID and then this because your world ID number basically.

[WorldMaker]

That bumps directly into "fallacies programmers believe about names". Not every culture uses family names the same or has them at all, for instance.

[theandrewbailey]

See also Falsehoods Programmers Believe About Names: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...

[cameronbrown]

Unless someone goes out their way to choose their own 'branded' name perhaps they could just receive a unique hash of their name for a domain? Tools can always be built to handle these names so you're not memorising such lengthy domains.

[ailideex]

How do you decide which person get which name? This just gets you back to the whole ICANN problem. I can remember a couple of digits which makes my name unique. I cannot remember 1e873645-1f68-4b48-9eae-934ec717229b

[cameronbrown]

That's just a technical problem that new infrastructure can solve by abstracting away the name. Instead of visiting 1e873645-1f68-4b48-9eae-934ec717229b.com/foo, you're just visiting "bar/foo", where 'bar' is their name. Click on the URL and the full hashed version is revealed for proper sharing.

In the same way that nobody memorised Facebook's UUID of a person, they can just remember their name.

[ailideex]

And then we are back to the problem of deciding who gets what name

[pmlnr]

But then .onion - or at least the way it's done - is already there.

[pmlnr]

During the socialist system one received a personal identification number. It was very similar to this.

The good side:

- I like the idea and I have been thinking around the same lines

The bad side:

- how would changed names, like marriage, be handled?

- it shows too much PII - I believe knowing a domain like this would immediately fall under GDPR

- still not easy to remember

- doesn't allow pseudonyms - I know that pseudonyms might look like they go against request a domain for life, but they don't. In our culture, are name is given by someone else and/or inherited, but many would like to associate their presence with something they decide on their own.

[NikkiA]

> how would changed names, like marriage, be handled?

The same way it works with NI numbers in the UK and SS numbers in the US, you tell the agency about the change and that's that.

Why would a number being associated with your person have any issue about your name changing? the very purpose is to disassociate the name from being a unique identifier.

[ailideex]

Norway still uses a very similar system and I think other countries also.

You do raise very valid problems though - but I feel like either you have at least some of those problems or you go to routes which is basically what .onion does where you have your_chosen_name + bit_of_not_memorable