Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support IPNS over PubSub #61

Open
lidel opened this issue Apr 17, 2024 · 0 comments
Open

Support IPNS over PubSub #61

lidel opened this issue Apr 17, 2024 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@lidel
Copy link
Member

lidel commented Apr 17, 2024

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?

  • 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:

Someguy is in the same spot: we need some sort of topic GC before we can enable pubsub router in someguy.

@lidel lidel added the need/triage Needs initial labeling and prioritization label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant