Re:Mediasoup – WebRTC Video Conferencing
by bryanrasmussen on Friday April 03, 2020 @07:02AM
(#22767979)
I read the whole thing. I am really confused as to why out of that you chose "Pornhub uses mediasoup" as the TLDR?
Just to easily explain that mediasoup is not a replacement for Jitsi or Zoom, but a low level set of libraries for building build different kind of real-time applications, including multi-party videoconference apps (such as Jitsi or Zoom) and others completely different.
TL'DR': Pornhub uses mediasoup.
I've read many comments here asking about "how mediasoup is different than XXX" or about "mobile apps". I think the Overview in the website should be self explanatory, I'll just paste a fragment here:
https://mediasoup.org/documentation/overview/
--------------------- Design goals of mediasoup and its client side libraries:
- Be a SFU (Selective Forwarding Unit). - Support both WebRTC and plain RTP input and output. - Be a Node.js module in server side. - Be a tiny JavaScript and C++ libraries in client side. - Be minimalist: just handle the media layer. - Be signaling agnostic: do not mandate any signaling protocol. - Be super low level API. - Support all existing WebRTC endpoints. - Enable integration with well known multimedia libraries/tools.
Use cases:
- Group video chat applications. - One-to-many (or few-to-many) broadcasting applications in real-time. - RTP streaming.