I'm the creator of Peer Calls [1], a peer to peer video conferencing web app using WebRTC, and it has a basic chat functionality (sending files is a little quirky). The first release was back it in 2016. Users create a room and share the link.
It's built in NodeJS/React/TypeScript, and I just recently ported the backend to Go because I wanted to build a Selective Forwarding Unit using pion/webrtc. You can test this in the alpha release on peercalls.com/alpha [2].
Would love to get more feedback and/or bug reports! Open source, available on
GitHub [3].
I discovered Peer Calls last night and think it’s an awesome project! It worked flawlessly from both my phone and desktop; it’s one of the (surprisingly few) fully featured WebRTC chat apps!
My one hope: Could it be possible to select from different audio bitrates when on a direct connection? High bandwidth audio seems like one of the huge selling points of P2P chat applications. My naive assumption is that it’s the sampleRate constraint on the audio stream, but I’m not sure how the compression works...
Check out bigbluebutton [0]. It is open source with tons of features. It however requires specific Ubuntu 16.04 version and can only be installed on that OS. It is not the best fit for very large audiences (say over 200) in one session BUT for that they are working on another load balancing solution recently [1]
I have been using this for our clients (edtech) for a while and with their 2.2 official version, they made it HTML5 only and removed flash. Works really well if you follow all the guidelines and installation instructions.
They also have a bash installer script [2] which literally does everything for you in one single script.
I use it as a student. It's very good and easy to use. I'm curious about the performance with many participants though as we only use it in classes with at most 40 persons. And of course no camera just the presentation.
Jitsi works great for me. Just know that using it with Firefox is not optimal, particularly for > 2 participants due to certain bandwidth optimizations not being available on Firefox. This pains me as a Firefox user.
Observed that firefox 47 and 60 clients kill the stream for all participants. firefox 68 works fine. Not sure why a client failure would cause a crash on the server but it's not a great experience.
It's built in NodeJS/React/TypeScript, and I just recently ported the backend to Go because I wanted to build a Selective Forwarding Unit using pion/webrtc. You can test this in the alpha release on peercalls.com/alpha [2].
Would love to get more feedback and/or bug reports! Open source, available on GitHub [3].
[1]: https://peercalls.com
[2]: https://peercalls.com/alpha
[3]: https://github.com/peer-calls/peer-calls