[Gigachad]

IPFS claims to solve this with their name service IPNS which can update to point to a new hash with a revised file. Where the original hash can be cached and used but users can refer to the NS version and get the latest version. But last I saw, the name on IPNS had to be frequently pushed by the original server or it would go away.

[davidgerard]

IPNS doesn't work. Whenever you press them on this point, they'll admit it doesn't work.

But IPFS has the crypto problem of conflating the stuff that works now with the stuff that's hypothetical in its marketing, and not admitting that the latter is janky nonsense that doesn't bloody work.

[PLDiscordian]

Sorry, I don't know when you last tried out IPFS, but IPNS does in fact work: https://docs.ipfs.io/concepts/ipns/

Again, I'm not sure when it wasn't working, or when it began working (it's always worked since I've been around), but IPNS has made huge strides, I use it every day. Even https://ipfs.io is using IPNS, it's very popular.

[Gigachad]

Yeah this is what I saw 4 years ago. Shame it still isn't working. Insane how crypto projects spend all this effort on flashy landing pages, marketing, hype. But if you actually try to use the product, you find out it just doesn't actually work.

[jayd16]

Seems like at that point it might be easier to just build a new http+ protocol that supports document signing and focuses on bringing caching back.

You could use all the current web/http/DNS infrastructure, and add certified/cacheable GET results.

Anyone could run their own proxy and cache what they see fit. Seems like an easier transition as it could be fully compatible with the current web.