-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat: Add webrtc-w3c protocol for browser to browser #309
feat: Add webrtc-w3c protocol for browser to browser #309
Conversation
Great. Thanks for providing the patch. I suggest depending on your fork for now, i.e. not release this new multiaddr protocol component yet. That gives us still more time on libp2p/specs#497 (comment). |
Now that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All clear to move forward here. I merged multiformats/multiaddr#150 and multiformats/multicodec#316.
@achingbrain I think this requires an approval from a maintainer, would you be able to bless it |
## [11.5.0](v11.4.0...v11.5.0) (2023-03-03) ### Features * Add webrtc-w3c protocol for browser to browser ([#309](#309)) ([16232d5](16232d5))
🎉 This PR is included in version 11.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
We have decided to rename `webrtc-w3c` to `webrtc-private-to-private`. See rational in multiformats/multiaddr#150. No software has been released using `webrtc-w3c`, thus renaming is not a breaking change. Ignoring the automated `multiaddr` `v11.5.0` release. See also multiformats#309 that introduced `webrtc-w3c`.
Adds a new protocol called
webrtc-direct
for enabling webrtc browser-to-browser. libp2p/specs#497