I think I grasp the idea that ipns allows me to assign different hashes to my peer id, thereby allowing me to have a stable address for mutable content.
However, since I only have one peer id, does this mean I can only have one stable address?
Since I might maintain several blogs, sites, or projects for which I would like to assign a fixed hash for changing content, I would like to be able to have access to more than one such address.
As mentioned here with (this could be in the hundreds of thousands). But in such a case, would I need to create a new node for each file? Is it possible to create a more lightweight solution? I could imagine a simple key value pair object for every file assigned to a fixed hash or file name. Such a file would then simply list chronologically all the content addressable hashes for that file. (I guess that basically a directory, that lists the hashes of the versions of that file within it.) This would allow me to easily get the most up to date hash for a given file. (Maybe this is just GIT and I need more clarity on how IPFS and GIT can work together).
In general, I think content addressable files are really important and I love that about IPFS. But often, I’m not only interested in the exact content of a file. Instead, I’m also interested in targeting an idea that a file claims to represent in some way. In such a case, I want to be able to target that idea and get the most up-to-date content that represents that idea.
I’m definitely still learning, so apologies if I’m missing something basic.