Open
Conversation
Contributor
Author
|
I was thinking about the question of whether Voyager should have a persistent PeerId or not. From a security perspective, it might be wanted or good to have a temporary PeerId for, for example, every restart of the node. From the perspective of a browser that wants to pin files, it is necessary to have a fix PeerId. Otherwise, the browser would have no idea, who's the Voyager is in the network. On the other hand, Voyager could publish via Gossibsub that there's an OrbitDB Pinning Service around. But wait, isn't that already communicated via identify? Is it possible to find and connect quickly to certain peers who speak a certain protocol without pubsub or bootstrap nodes? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #77