github.com/libp2p/go-libp2p-webrtc-direct
Status:
Archived and not maintained
Alternatives:
WebRTC Browser-to-Server is being implemented in go-libp2p here https://github.com/libp2p/specs/pull/412 per the specification: https://github.com/libp2p/specs/pull/412
WebRTC Browser-to-Browser is being tracked here: https://github.com/libp2p/specs/issues/475
Questions:
Please direct any questions about the specification to: https://github.com/libp2p/specs/issues
Please direct any questions about the go-libp2p WebRTC implementation to: https://github.com/libp2p/go-libp2p/issues
A transport that enables browser-to-server, and server-to-server, direct communication over WebRTC without requiring signalling servers. This is the Go counterpart to js-libp2p-webrtc-direct.
Lead maintainer: @backkem
Special thanks to @pion for their fantastic WebRTC Go library, which made this libp2p transport possible.
This package supports gomod builds.
go get github.com/libp2p/go-libp2p-webrtc-direct
Check out the GoDocs.
Check the examples folder for usage and integration examples.
Feel free to join in. All welcome. Open an issue or send a PR.
This repository falls under the IPFS Code of Conduct.
MIT
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.