-
Notifications
You must be signed in to change notification settings - Fork 961
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
libp2p-webrtc
is already claimed on crates.io
#3141
Comments
A bit of background for you @wngr: Over the last couple of months we have been working on a WebRTC transport for libp2p. The specification gives a good overview. There is an implementation in Rust (#2622, about to be released), Go (libp2p/go-libp2p#1655) and JS (https://github.com/little-bear-labs/js-libp2p-webrtc/). For now this only covers the browser-to-server use-case (without signaling). We are working on browser-to-browser next. This would enable rust-libp2p running in the broser via WASM to communicate to any other browser. Thus this would be on par with your project https://github.com/wngr/libp2p-webrtc. I see the above effort as a consolidation of the many libp2p WebRTC implementations out there. Would you agree that this would as well cover the use-case you are targeting with https://github.com/wngr/libp2p-webrtc? |
No worries. Let me know who I should transfer it to. |
🙏 thanks @wngr. I have sent you an email. |
I am now an owner of the repository. Thanks @thomaseizinger for catching this early. Thanks @wngr for transferring ownership. |
It seems like @wngr has been developing a WebRTC transport too and published it on crates.io. We either need to rename our crate or talk to @wngr whether they would transfer the name to us :)
cc @melekes @mxinden
The text was updated successfully, but these errors were encountered: