This will probably be the first update I release. I've pre emptively built the front end in Quasar and there's even some bits of commented out code in there from where I started looking at storing authentication data per server. The plan as I see it, and I think this makes sense, is to have the web app based front-end be for people that want to run their own contained instance of both the API and front-end but then also have a Quasar desktop based app that has server switching built in. This then allows the server owner to just run the API if they want and let the user worry about how they connect.
It hasn't been a priority for me at the moment because I'm literally the only person running a server. ๐
Now that it's out in the wild, my next focus will be on the multi server side of things and making the text channels a bit more functional than just plaintext.
I'm with you, I love Matrix as a concept but the experience of actually running it was a major headache for me.
I'd love to contribute to those projects but anyone that's read through my repo for this will see I'm not that good. It took me a long ass time to figure out end to end encryption and those projects are built on it. ๐
I also feel like they fit a different niche, at least matrix does, I'm not too familiar with XMPP. I've said in other replies, I'm not looking to make something that's infinitely scalable or federates with other services, just a relatively simple chat app that someone can have running for their group of gamer friends. If it can do text/voice/screen share with minimal setup/fuss/external dependencies then I'm a happy boy. I kinda had this idea in my head that I'd like to get it to the point where you can upload a tar.gz to cheapo web hosting, untar, follow the setup wizard and have comms ready to go without having to mess around in config files and what not.