Anyone have some thoughts on Jami vs Jitsi? They're both pretty robust software at this point but there's not enough information out there on the edges of each relative to the other.
Jami has native GTK/QT clients in my distro's (Arch) official repositories. Jitsi has an Electron desktop application that exists in the community-maintained repository (AUR). I haven't used either of them and my experience with Jitsi has been solely limited to the browser client. I'm going to try them now.
I am not sold on the necessity of GTK/QT clients over Electron applications -- I think the development/packaging ease of Electron is exactly why it's where it is today and what works for users generally is not wins so I view it with dispassion. Doesn't matter how much better GTK/QT is (they can't be that good, devs are choosing to "shoot themselves in the foot" with Electron just over there!). Also the nice thing about web is that phones will at least have a chance (even if overheating during the call).
I was more wondering about what it took to run -- Jitsi's server requirements always seemed a bit too heavy weight -- it requires like 4 things to run. That said, I just took another look at the documentation[0] and it's pretty well written... Maybe it's time to roll my sleeves up.
[EDIT] Did not know Etherpad[1] (one of the things that jitsi wants you to host along with it) has video capabilities...
We are really spoiled for good F/OSS software these days -- it's insane how much good software there is out there now.
[0]: https://jitsi.github.io/handbook/docs/devops-guide/devops-gu...