Browser <-> Browser over webrtc-private-to-private #152
Conversation
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
28 tasks
Contributor
Author
|
Contributor
|
@MarcoPolo : agreed that we want Webkit and Firefox, but if there are snags with them, can we at least proceed with Chromium first? If we just focus on Chromium to start (more than the majority of browser usage), can this be moved out of draft? |
Contributor
Author
|
I think we should merge libp2p/js-libp2p#1615 first as a lot of interfaces changed here. |
Contributor
|
Unblocked I assume now that libp2p/js-libp2p#1615 is merged?! |
Contributor
Author
|
This is unblocked now :) |
Contributor
Author
|
I'm going to get this back up to speed using the latest stuff from js-libp2p. I think I can simplify some things in this PR as well. |
Contributor
Author
|
This is done now. Closing this pr |
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.
Adds browser to browser test. Mostly straightforward except that it requires adding a relay node to the test environment for this case. I'm using relayv1 as the first pass and will move this to relay v2 when we have it in a released version of js-libp2p.
Draft until libp2p/js-libp2p-webrtc#90 is merged