←back to thread

Show HN: Zoom Redirector

(github.com)
279 points arkadiyt | 1 comments | 22 Mar 20 22:11 UTC | HN request time: 0.207s | source
Show context
jwr ◴[23 Mar 20 10:58 UTC] No.22662783[source]▶
I highly recommend using solutions based on WebRTC, which is present in all modern browsers and is really good (see https://www.youtube.com/watch?v=WFil-ZPE0-g for a comparison with Zoom).

Whereby (formerly appear.in) https://whereby.com/ has a really nice and simple system. No more jumping through a dozen hoops, no more installing software with glaring security holes and borderline malware behavior (looking at you, Zoom).

replies(2): >>22662842 #>>22667048 #
Quanttek ◴[23 Mar 20 11:07 UTC] No.22662842[source]▶
How does WebRTC compare when you have a lot of callers (e.g. 20 people in a call)? From my understanding, it is p2p, so the network throughput required would be a lot higher, correct?
replies(4): >>22662904 #>>22663835 #>>22674875 #>>22683334 #
1. sigwinch28 ◴[25 Mar 20 10:33 UTC] No.22683334[source]▶
The default installs of Jitsi Meet use Jitsi videobridge to avoid p2p for calls of >2 participants.

For <=2 people, p2p WebRTC is used (though a STUN server might be needed to traverse NATs for each person [0]).

For >2 people, the Jitsi Videobridge is used instead of p2p [1]: it takes in all media streams from all clients (possibly even in different resolutions) and selectively forwards them to clients based on bandwidth [2]

[0]: https://en.wikipedia.org/wiki/STUN [1]: https://jitsi.org/jitsi-videobridge/ [2]: https://github.com/jitsi/jitsi-videobridge/blob/master/doc/s...