![]() ![]() The android app didn't work on my Sony Z1, but I've since changed phones and it seems to work now. I've also tried a self-hosted Jitsi meet instance more than a year ago, which for some reason has much better echo reduction, but it sometimes didn't work for one or two of our colleagues for unknown reasons, maybe because most of us have Firefox, not Chrome, or mobile browsers. GitHub - jitsi/lib-jitsi-meet: A low-level JS video API that allows adding a completely custom video experience to web apps. I'd really like to use something self-hosted, but I can't control what devices people use, and users are way too used to simple interfaces. A low-level JS video API that allows adding a completely custom video experience to web apps. I've tried finding a setting that would be OK to use when no headset is available, but I just couldn't get it to become bearable. no "loudspeaker" setting activated on their phone) killed our conversations because people heard themselves talking. IIRC even one user talking into their phone normally (i.e. Just having one non-headset user killed it for us. Our problem was that we had way too much echo/reverb, especially when people were not using headsets. This means that even your voice calling service (Google, Facebook, Jit.si, etc.) cannot listen to the contents. Jitsi prevents eavesdropping by automatically encrypting your conversation for the full duration of its trip across the Internet (end-to-end encryption). > Exactly, I guess for better user experience and performance they have a SFU or MCU in place (our HPB is an SFU), and therefor it stops being end-to-end encryptedÄoes this work properly on mobile/without headsets for you? Jitsi lets you communicate with friends and contacts across the Internet. That would only be true if I decided to use an additional HPB solution, wouldn't it? But not out of the box. > But I don't understand why the Jitsi people write, "WebRTC today does not provide away of conducting multiparty conversations with end-to-end encryption." Someone mentioned Jitsi's statement and the developer responded: > Chat is currently not end-to-end encrypted, only the audio/video of calls are. > and without the HPB its always paar-to-peer and therefor end-to-end encrypted. > By default with the internal signaling backend audio/video calls (no matter if 1:1 or group) are end-to-end encrypted. > video/audio is already end-to-end encrypted He says that video/audio in calls are end-to-end encrypted when the server is using the default PHP backend, but not the high-performance backend (an optional paid and proprietary enterprise upgrade). Are you saying that the developer's claims in this issue discussion are wrong? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |