You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an IPNS record is published by one node to the DHT and to the pubsub (if active). It would be nice if we could add IPNS records to the cluster pinset. Each member would need to verify the IPNS record and then start publishing it via DHT/pubsub as well as mirror.
This avoids the single point of failure we're currently having in this regard in the infrastructure.
Talked about this a bit at the IPFS Thing with @hsanjuan
One thing that would be useful here is to subscribe to the IPNS pubsub record so that we can watch for changes. Else DHT polling could be done but it'd be kinda inefficient.
Also, users will likely need to be informed that they need to either keep their publishing node online indefinitely or to set a very large TTL on their IPNS records so that they don't expire and can actually get republished.
Describe the feature you are proposing
Currently, an IPNS record is published by one node to the DHT and to the pubsub (if active). It would be nice if we could add IPNS records to the cluster pinset. Each member would need to verify the IPNS record and then start publishing it via DHT/pubsub as well as mirror.
This avoids the single point of failure we're currently having in this regard in the infrastructure.
Additional context
Requested feature for go-ipfs:
ipfs/kubo#8433
The text was updated successfully, but these errors were encountered: