browser loading the old ipfs cid even after publishing new revision to w3name

storacha / w3name

IPNS client and service for generating, updating, and tracking immutable names with signed updates

Other

45 stars 12 forks source link

browser loading the old ipfs cid even after publishing new revision to w3name #87

Open pawanpaudel93 opened 2 years ago

pawanpaudel93 commented 2 years ago

This URL shows the name is referencing the new IPFS CID but still tries to load the previous CID contents in the browser. The first revision works perfectly fine but the new revisions to w3name don't load up the latest IPFS CID.

ipns://k51qzi5uqu5dm09eb5pk1af1622tn7atinj0ynaic685p9pzbinffxlmc9t82j ipfs://bafybeic3zxymvc7jfnw6pc7scsgxvmkttvmlmho2vidl22tjxmefevy2ru

pawanpaudel93 commented 2 years ago

Now I am able to access the latest IPFS published to w3name but it takes a lot of time to switch from old to new IPFS CID completely. Is there any reason that it's taking too long to take effect ???

MJJHUA commented 2 years ago

Same problem. How to fix it ?

0xkyn commented 1 year ago

@pawanpaudel93 How did you managed to solve that ?

StephanGerbeth commented 1 year ago

I had the same problems, when i tried to open the resulting ipns-Url directly in the browser. If i use the w3name api, I always got the correct response with the updated revision.