From @mcast on Fri Sep 09 2016 22:40:35 GMT+0000 (UTC)
so as an alternate, IPNS can use the DNS system to create human readable names. Though this is a centralized system. So it sucks to rely on it to make human readable names, maybe one day IPNS will support something like https://namecoin.info/ ? or maybe another decentralized naming system.
From the point of view of a development engineer, this is
- get something working
- show people a working system
- acquire more developers
- fix the problems later
but from the point of view of a production engineer, the same events look like
- create a userbase on a legacy system (DNS)
- invent & refine something better
- encourage users to migrate off the old system
- possibly having no way to search down old references to names, or audit ongoing use
- create a process for resolving conflicts of expected name resolution between old & new
- presumably there will be name-grabbers on the new system, and expiry-squatters on the old
- carry on supporting the old system much longer than you wanted to
Is it worth designing in a fixed life or deliberately ugly contrivance?
Or are we all so used to linkrot that it’s not an issue?
Copied from original issue: https://github.com/ipfs/faq/issues/179