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
Once we have this in someguy, our rainbow-based fleet will benefit from this (faster lookups / updates, additional resiliency), without having to run pubsub on each rainbow instance.
We have an opportunity to create another useful public utility (ipns cache and reprovider).
Prior Art
Kubo has opt-in support for resolving IPNS over PubSub (in addition to Amino DHT):
IPNS over PubSub is enabled by default in IPFS Desktop and Brave,
but is not in Kubo because it lacks GC of unused topics, and it could cause trouble in server environments:
Right now, someguy only resolves IPNS over Amino DHT.
Let's use this issue for discussing adding support for IPNS over PubSub as a secondary resolution method:
Why?
Prior Art
Kubo has opt-in support for resolving IPNS over PubSub (in addition to Amino DHT):
IPNS over PubSub is enabled by default in IPFS Desktop and Brave,
but is not in Kubo because it lacks GC of unused topics, and it could cause trouble in server environments:
Someguy is in the same spot: we need some sort of topic GC before we can enable pubsub router in someguy.
The text was updated successfully, but these errors were encountered: