Right now, I'm running an IPFS node. Now, say I store a set of files. What happens is that: /set_of_files -> /ipfs/[key_1] Now, these files change because the

Right now, I'm running an IPFS node. Now, say I store a set of files. What happens is that: /set_of_files -> /ipfs/[key_1] Now, these files change because they were your GIT repo of all your projects. So what happens is that the key that represents your files changes continuously. That sucks. There's a solution. IPNS. IPNS can point at a continuously changing set of directories, and always provide the pointer as an IPNS link. It's the mutable part of IPFS... Now, as for the hashes... The Firefox plugin already supports looking up the DNS txt record of the IPNS key associated to your site. So, if you have a pretty DNS name, you still keep your pretty DNS name. Now, for the versioning, that assumes that there was something prior, something now, and something that will be. That's not always the case. In that situation, a changelog could be applied as a form of a blockchain showing all deltas to the keys changed. But that can be implemented when it needs to be, and not as core functionality.