Ok stop with the E2EE encrypted. Literally if you're running your own hardware, you don't "Need" E2E. You need to understand your attack surface, your vulnerabilities, and your goals. E2EE is not the optimal use case for everyone and everything.
- Zoom does not support self-hosting - Self-hosting Jitsi is not the optimal use case for everyone. People are free to choose between Jami and Jitsi, and it’s great to be able to have different options based upon your use case.
Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
41–50 of 78 posts
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#42This used to be called GNU Ring. Wikipedia has some info on features: https://en.wikipedia.org/wiki/Jami_(software) I'd be really curious if this is a viable option for videoconferencing for say >10 people.
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#43Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#44Earlier quoted context omitted.
Kodachrome wasn't abstract. It was Kodak's color film, and thus a pseudo-portmanteau of "Kodak" and "chroma" (i.e. color). I'm sure there are meanings behind a lot of the other names you listed, too.
How about Kodak? I am sure there are many names that are abstract.
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#45Earlier quoted context omitted.
Can’t WebRTC support peer-to-peer video calls without running the stream through a server? I have vague recollection that it can but am not particularly familiar with the protocol.
It does, but when the number of users is >2, typically you will go through a TURN server.
For more than two users, you mainly have three options:
* MCU (Multipoint Control Unit), which IIRC does need to decrypt your video, as it will post-process it and possibly re-encode it to send a single stream to the other participants.
* SFU (Selective Forwarding Unit), which in theory doesn't need to decrypt your video, but does need some metadata about it in order to make smart decisions as to what streams to forward to whom (for example, forwarding only the stream of the person who is talking). In practice, I believe some (many?) SFUs will do decryption, thought it's not a strict requirement.
* Dumb peer-to-peer-to-peer-to-... multi-forwarding. You can of course theoretically stream your video to each other participant, and they can all do the same, but that quickly fails to scale. It might be ok for three, maybe four participants, but even then there will likely be problems.
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#46C/C++ implemented custom protocols, no webrtc... What explains these security and compatibility compromises?
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#47Just realised this is Ring . Wonder why they changed their name
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#48I would love to see a messenger/audio call/video call app built on the zerotier SDK, I never had connection problems with zerotier.
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#49As an aside, I don't believe in the virtues of P2P anymore. It's clear to me that centralised systems scale further and faster, and what we need are benign organisations to run them. Legal forms like cooperatives and community benefit societies (nonprofits in the US I guess) are the way forward. I'd choose a community instance of Jitsi as being the best approximation of this for now.
Re: Jami: GNU end-to-end encrypted alternative to Zoom and Jitsi
#50Earlier quoted context omitted.
How about Kodak? I am sure there are many names that are abstract.
From https://petapixel.com/2011/08/03/origin-and-evolution-of-kod... > The letter “K” had been a favorite of Eastman’s, he is quoted as saying, “it seems a strong, incisive sort of letter.” He and his mother devised the name Kodak with an anagram set. He said that there were three principal concepts he used in creating the name: it should be short, one cannot mispronounce it, and it could not resemble anything or be…