-
Notifications
You must be signed in to change notification settings - Fork 6
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
Not really an issue #1
Comments
Sure. Basically for each p2p WebRTC connection, you just need signalling to connect (I personally don't use this anymore, I use gun.js for signalling). Once connected, send anything, including video. Technically a WebRTC browser could send the same video source to multiple, each connection being a separate WebRTC connection, only limited by their upload speed. |
@cretz I read you are now using gun.js for signalling. |
It's not just you, when I used gun.js it was because ipfs's JS lib was too immature. If I needed to do it again today, I would use ipfs's JS lib. If you want to see the old code, I used gun.js for WebRTC signalling on https://github.com/cretz/myscreen.live. |
@cretz Thank you very much! I'm going to have a look at it. But as you say, it would be better to use js-ipfs |
..but I am wondering if this would work with WebRTC video, like a one-to-many broadcast?
The text was updated successfully, but these errors were encountered: