>> There is no off the shelf software that would allow us to support calls of that size while ensuring that all communication is end-to-end encrypted, so we built our own open source Signal Calling Service to do the job
But wasn't there Jitsi? [0]
I think its great we have competition among Free Software projects so that both can improve. But sometimes I feel like maybe duplicated efforts create two 5/10 solutions. Instead what we really want is one 8/10 solution, or better.
There is some duplication of effort but sometimes progress happens via rewrites and that might actually be a faster way to an 8/10 system than direct collaboration?
Also I think it’s interesting to see how this builds on Google’s work (the googcc algorithm). Which of course builds on previous open source work. The underlying technical collaboration happens even with quite different organizational goals and different codebases.
All of these things are built around WebRTC to some degree, which was built on previous open source work and standards. We all benefit from many contributions over many years.
Same, all my hobby groups switched from Jitsi to Google Meet due to disconnect issues. And Meet is actually pretty good. Can't compare to Zoom as I don't know anybody using it.
It's the first of the links where they say "When building support for group calls, we evaluated many open source SFUs", so I suppose it's either not one of the two with "adequate congestion control", or is the one that did not reliably scale past 8 participants?
Can you elaborate on the scaling issues you hit (and with which implementations?) I've used Janus + MediaSoup but not Jitsi before for WebRTC audio for web based multiplayer games.
Daily.co has a developer friendly offering that accomplishes this as well. Many offerings available and many reasons to not take on this added complexity.
But wasn't there Jitsi? [0]
I think its great we have competition among Free Software projects so that both can improve. But sometimes I feel like maybe duplicated efforts create two 5/10 solutions. Instead what we really want is one 8/10 solution, or better.
[0] https://meet.jit.si/