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

IPNS over PubSub as an independent transport #6447

Closed
11 of 15 tasks
aschmahmann opened this issue Jun 13, 2019 · 1 comment
Closed
11 of 15 tasks

IPNS over PubSub as an independent transport #6447

aschmahmann opened this issue Jun 13, 2019 · 1 comment

Comments

@aschmahmann
Copy link
Contributor

aschmahmann commented Jun 13, 2019

IPNS over PubSub is not an independent transport from the standard IPNS over DHT. In particular, the first time a user tries to do an IPNS resolution when IPNS over PubSub is enabled it hits the DHT, and only on subsequent resolutions is PubSub utilized.

To accomplish this we need:

Some benefits of IPNS over PubSub as an independent transport from IPNS over DHT.

  1. DHT performance issues are either less problematic or not relevant for us (depending on the discovery mechanism used)
  2. We mostly get IPNS republishing for free (i.e. even if the publisher goes offline, other people can still make the IPNS record available). This means we can largely mitigate IPNS records that are abandoned by their authors since, as long as someone who cares about the record is maintaining and advertising it, the record will be available.

Demo and brief explanation of IPNS over PubSub as an independent transport (2m40s).

^ @autonome @lidel @Stebalien @momack2

Update: Given that the rendezvous work has been put on hold by libp2p and that it's not actually necessary for PubSub to work as an independent transport those work items are now closed.

However, since we do already have MDNS discovery support (albeit not through the libp2p Discovery interfaces) IPNS over PubSub can function even in the total absence of a DHT.

@aschmahmann
Copy link
Contributor Author

aschmahmann commented Feb 2, 2020

The only remaining issue is not with IPNS over PubSub as an independent transport, but with how we handle the multiple transports at an API level (ipfs/specs#198 (comment)).

This issue is closed for now and any Issue/PR dealing with the above will link to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant