Xin Liu
While I am unable to reproduce the issue locally, here is my best guess: When this happens, your local IPNS resolving gets an outdated CID record from the P2P networks....
In [c3a0c21](https://github.com/Planetable/Planet/commit/c3a0c21d676dc1f1cd4dd4ca3ea5820475b5c4ae) I added a measure to prevent unexpected deletion: if the `updated` field in the latest resolved CID is older than the local one, then it will not trigger...
I hope this upgrade can fix #338 too.
> We've shipped a lot of fixes since Kubo 0.15 and the [latest 0.32.1 release](https://github.com/ipfs/kubo/releases/tag/v0.32.1) is packed with some cool features, e.g. [AutoTLS](https://blog.ipfs.tech/2024-shipyard-improving-ipfs-on-the-web/#autotls-with-libp2p-direct). It should also fix #338. > >...
Today I tested again with this IPNS powered ohlife.eth.limo: /ipns/k51qzi5uqu5dhbdxrvoeqy96c3krp2t1d9hfscjyn2mwts5f1w8f1sq99xwh3r Very happy to report it seems the unexpected behavior is gone! Below is what I got today: Now, with the...
> Do you have any specific IPNS name that I can test? Hi @2color Today I encountered this issue again with 0.34.1, please see the screenshot attached: The IPNS in...
@2color For IPNS `k51qzi5uqu5di0awbvmh7vanmk726n7w0pujnmcuz8vvqi19qso22u0p0gjrz2` This is 0.34.1 (Left) and 0.15.0 (Right) side by side: An outdated result `bafybeiaghevtk6l3spoeuexku574ug6a7in3irg2sm4g7iqblyybjxrsuu` appears from time to time on 0.34.1 while 0.15.0 can consistently return...
Additional context: kubo 0.34.1 is started with: ``` /usr/local/bin/ipfs daemon --enable-pubsub-experiment --enable-namesys-pubsub ``` In config, `Routing.AcceleratedDHTClient` is set to `true`.
The IPNS record was published with **Kubo 0.15.0** with these parameters: - When resolving, if I omit `-s`, then two results will take turns, sometimes the latest one, sometimes the...
In 2021, we started building [a static site generator with a built-in IPFS node](https://planetable.xyz/).  Users can build a blog with this macOS GUI and publish the site with the...