- cross-posted to:
- privacyguides@lemmy.one
- technologie@jlai.lu
While Jitsi is open-source, most people use the platform they provide, meet.jit.si, for immediate conference calls. They have now introduced a “Know Your Customer” policy and require at least one of the attendees to log in with a Facebook, Github (Microsoft), or Google account.
One option to avoid this is to self-host, but then you’ll be identifiable via your domain and have to maintain a server.
As a true alternative to Jitsi, there’s jami.net. It is a decentralized conference app, free open-source, and account creation is optional. It’s available for all major platforms (Mac, Windows, Linux, iOS, Android), including on F-Droid.
Here are some interesting lists of alternative instances:
https://jitsi.github.io/handbook/docs/community/community-instances/
https://ladatano.partidopirata.com.ar/jitsimeter/
https://timo-osterkamp.eu/random-redirect.html
By the way, by default jitsi is not end-to-end encrypted if you have more than two people in the call or need to use the videobrige for other reasons. https://jitsi.org/e2ee-in-jitsi/
Update: The e2ee implementation seems to have some issues as well: https://eprint.iacr.org/2023/1118
Firefox <116 is currently not able to use the e2e-encryption, blink based browser already support it. Firefox 117 will provide the necessary infrastructure as well. I don’t know if jitsi would have ot be patched to detect the firefox implementation. https://bugzilla.mozilla.org/show_bug.cgi?id=1631263#c58
I didn’t know Jitsi has those issues with default E2E.