Hey there. Let me describe my issue.
I am in need of a way to store content (just a few kilobytes, probably) that will be modified rather “rapidly” (let’s estimate it at 20 times a day or something like that), and maybe not always from the same peers.
It is important that this is all pointed to by a single URL, so it seems that publishing the CID of my content to IPNS with a generated key works well.
My problem is the following: after publishing from two (or more) different peers, using the same key, I don’t get the same IPNS name resolution from different gateways/nodes/etc.
For instance if I simultaneously run
ipfs name resolve <hash> --nocache on both peers, the result is different (both return the CID that they published), and if I try to access it from a public gateway (gateway.ipfs.io/ipns/hash, etc.) from different geographical locations (sorta simulated by Tor routing) the file that I get back is different as well.
I see that after a bit of time (a bunch of hours, from what I’ve experienced) the IPNS record gets propagated and eventually the nodes agree on what CID they should be serving, but this is too slow for the frequency of mutability that I require.
I don’t necessarily need to access it from public gateways (although that’d be great); any solution that lets me find the very last CID published to that name will work.
Any thoughts, workarounds, or perhaps other ideas to sort this out? Thanks.