Also, the backend is written in _Rust_, I thought you guys LIKED THIS KIND OF THING!
This project is really good. Really really good!
A small team would inspire more confidence in the longevity of the project.
As someone who doesn't use voice channels, I can't even count how many times I've accidentally joined them because I mis-clicked. And then I have to find the "end call" button because, of course, it's small and located away from the channel itself. It is so unbelievably annoying.
The best feature Discord added recently was the ability to hide channels, so I can finally, once and for all, forget about voice channels.
It's a good reminder indeed, I hadn't considered the old gaming toolkit we used as teenagers and I work with 100% technical people that can figure out an apt install mumble
By making their backend AGPL they've left themselves a path to some kind of profitability for companies that want to run custom versions.
They're running Docusaurus for docs but adding manual timestamps instead of using the built-in showLastUpdateTime variable... this hurts me.
(Not a leading question. I haven't used Discord/Matrix/etc. more than a handful of times and don't know what I don't know.)
Also: How do voice channels work in this thing? I've been thinking for approximately forever about making Jitsi meet more flexible to support channels, but never got around to it (I've done some basic ground work on it, in case anyone wants to pick it up).
"All progress depends on the unreasonable man."
I personally won't donate free work to organizations that want the option of releasing nonfree software.
Or a plain and simple C client?
Which should be default for anything that offers dms.
I wanted it for Discord so I created an E2EE client on top of it: https://www.discryptor.io