The joke about two hard problems in CS being naming and caching rears its head again.
You need a name that will stick around for a long long time fundamentally on things like this.
This service: what guarantees or technical architecture mean it will stick around? Through upgrades, acquiring, economic ups and downs, death of owner? This website looks like a two bit shop.
It just highlights the transient nature of the web. Even things like facebook seem to have about a 20 year arc then things get acquired / renamed / subsumed.
The issue is the URL and DNS. There's no way to fix some link to a document or a service in stone for hundreds of years, even though we have the tech. Maybe government could provide that?
Corporations have the same issue addressing their files with links, especially in acquisitions / rebranding or re-re-re-branding.
And then of course there's hacking. Paper really does have its advantages sometimes.
AtlasBarfed|3 years ago
You need a name that will stick around for a long long time fundamentally on things like this.
This service: what guarantees or technical architecture mean it will stick around? Through upgrades, acquiring, economic ups and downs, death of owner? This website looks like a two bit shop.
It just highlights the transient nature of the web. Even things like facebook seem to have about a 20 year arc then things get acquired / renamed / subsumed.
The issue is the URL and DNS. There's no way to fix some link to a document or a service in stone for hundreds of years, even though we have the tech. Maybe government could provide that?
Corporations have the same issue addressing their files with links, especially in acquisitions / rebranding or re-re-re-branding.
And then of course there's hacking. Paper really does have its advantages sometimes.
jvm___|3 years ago