4 ms·
Heh, I linked the same proposal in a sister thread. I am aware of it, however it's for verifying the integrity of some resource at some url. It falls a bit shor
by benjaminjackman 10y ago
Heh, I linked the same proposal in a sister thread. I am aware of it, however it's for verifying the integrity of some resource at some url. It falls a bit short of what I'd like to see which is to serve items by the hash of their content, which I am also aware is basically IPFS.
So overall I would propose to drop the notion of location all together and just serve items by their integrity hash along with an fallback location which will typically be a classic http[s]:// url.
Ideally in the future I will be able to copy-paste those urn's into my browsers address bar and have them resolve right to the resource which will involve the browser either serving from it's local sha store or using the fallback url.
In the future when some sort of IPFS or other federated resource by sha provider takes hold then the fallback urls will become less and less needed.
To me it's just about making the links themselves be self-descriptive enough to allow them to truly become immutable and then, eventually, more efficiently served.