chore: only show websocket peers in discovery #284
Merged
Conversation
This file contains 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
weboko
reviewed
Nov 2, 2023
|
|
||
| // we only support websocket connections for now | ||
| const isPeerDialable = async (peerId: PeerId, node: LightNode) => { | ||
| const peer = await node.libp2p.peerStore.get(peerId); |
There was a problem hiding this comment.
I am wondering if we should do thins in js-waku and keep only wss peers in peerStore or make it configurable?
There was a problem hiding this comment.
correct. this is tracked in js-waku here: waku-org/js-waku#1547
weboko
approved these changes
Nov 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolves #265