11–20 of 115 posts
The whole decentralize everything! movement seems to overlook DNS. I get that technically the DNS system is decentralized, but in reality, you lease a domain from a random, usually politically charged entity, who can do anything with it, if they wish. We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized. Unfortunately none of the attempts - .onion…
The whole decentralize everything! movement seems to overlook DNS. I get that technically the DNS system is decentralized, but in reality, you lease a domain from a random, usually politically charged entity, who can do anything with it, if they wish. We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized. Unfortunately none of the attempts - .onion…
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.
Well that's nice of them, so we get to pay crazy amounts in the near future instead of instantly. how generous.
The whole decentralize everything! movement seems to overlook DNS. I get that technically the DNS system is decentralized, but in reality, you lease a domain from a random, usually politically charged entity, who can do anything with it, if they wish. We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized. Unfortunately none of the attempts - .onion…
Handshake [1] does this exactly. [1] https://www.handshake.org
What's the catch?
The whole decentralize everything! movement seems to overlook DNS. I get that technically the DNS system is decentralized, but in reality, you lease a domain from a random, usually politically charged entity, who can do anything with it, if they wish. We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized. Unfortunately none of the attempts - .onion…
Handshake [1] does this exactly. [1] https://www.handshake.org
Also this really does not do what the person you responded to asked for - I can't get some personal domain name for life from this - it is market based AFAICT. Really seems to solve almost none of the problems and goes directly for what ICANN only now does with .org as no domain will have any price cap with handshake.
The whole decentralize everything! movement seems to overlook DNS. I get that technically the DNS system is decentralized, but in reality, you lease a domain from a random, usually politically charged entity, who can do anything with it, if they wish. We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized. Unfortunately none of the attempts - .onion…
> 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…
The whole decentralize everything! movement seems to overlook DNS. I get that technically the DNS system is decentralized, but in reality, you lease a domain from a random, usually politically charged entity, who can do anything with it, if they wish. We need a real DNS system, one where an individual can request and have a domain for life and which is truly decentralized. Unfortunately none of the attempts - .onion…
> 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…
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.
Earlier quoted context omitted.
> 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…
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.
Earlier quoted context omitted.
> 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…
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.
Does it mean that renewal prices for currently owned .org domains will sky-rocket?