While I am harping on the subject of internet social media based on self-publishing rather than large republishing companies like Fbook, Twitter, etc...
I am quite concerned about the raw records that form the history of our times simply vanishing, irretrievably, as people age and die.
In earlier days things were recorded with relative permanence on paper (or stone). Not so today - one's entire life's work can vanish in few microseconds.
Not just the media or the storage of today are impermanent, but we have created a clock-driven scythe in the form of ICANN's utterly stupid domain name renewal system. There are as many potential domain names as electrons in the universe, but ICANN rules require leasing them in 1 to 10 year increments, thus undermining much of the means of referencing our already weakly permanent digital creations.
(I won't harp on how impermanent and fragile are our database driven, dynamically constructed, web pages.)
@karlauerbach sounds like a good time to bring up #IPFS where content is located by its hash rather than some location or DNS record.
Really, it sounds like you're trying to use DNS for something it was never intended for, and complaining that it doesn't do well something that it was never supposed to do in the first place.
DNS was not supposed to be about permanence.
@volkris
That's a fair point but dodges the issue.
What if you could have both:
- permanent content assessable data.
- permanent DNS.
Autonomi is coming and offers both in a truly decentralized, autonomous network (and no Blockchain).
(BTW IPFS data isn't permanent, just like DNS it can disappear unless someone is keeping it alive.)
@happyborg @volkris I really want permanent DNS, take a look at my somewhat joke, but also serious proposal at https://cavebear.com/eweregistry/
Permanent content is a hope more than a reality - too many formats keep changing. That's why I have my own stuff in HUGO which uses flat file input to generate a tree of very portable files that can be run - just via a directory copy (tar, rsync, etc) as a Document Root under Apache or Ngnix or pretty much any other web server.
Accessibility is also troubled - IP addresses change whether IPv4 or IPv6. That's why DNS permanence is important. But even TLS is troubled - the IETF has deprecated digest algorithms and that has left some web services (particularly on IoT devices) unusable by many browsers. (I preserve some old systems as VMs just to solve this issue.)
@karlauerbach but if IP addresses change, DNS permanence is undermined by that other weak link in the chain.
Again, I don't think you're using the right tool for the job, and then complaining that the tool doesn't work well.
