For anyone considering something similar, I’d suggest hosting a Movim instance over Matrix, as it’s far easier to set up and configure since it uses XMPP instead. Should be lighter on resources too.
Comment on Welcoming Discord users amidst the challenge of Age Verification
subunit317@lemmy.world 1 day ago
I deployed a self-hosted matrix chat server recently (synapse + element call) for my probably-soon-to-be discord refugee group. I know it isn’t a 1:1 replacement for the average discord user, but honestly I’m really happy with it. It does the important stuff that we care about (private chat rooms and video calls). My only complaint is that it was an absolute pain in the ass to configure, lol.
I consider the simplicity of the available apps to actually be a good thing. We had moved to discord a few years back from google chat. After that, a bunch of people didn’t interact in chat a whole lot because of what a busy pain in the ass the discord UX is. Several users have also consistently had major breaking issues with the discord app over the years. The element X app doesn’t do a whole lot, but it does work, so it’s an improvement for those people.
Hopefully the recent interest in matrix results in it becoming a fully-featured discord alternative.
ProdigalFrog@slrpnk.net 20 hours ago
bingrazer@lemmy.world 1 day ago
How hard was it for your users to connect? Were the configuration troubles just on your end? I am going to try to setup a home server, but some of my friends might not be willing to join if it is too much work
subunit317@lemmy.world 1 day ago
It’s a piece of cake for end users. It makes me really jealous lol. Just keep in mind that I’m making that claim based on using the ansible playbook that deploys synapse + element call and an element web UI. Some of our users like to use some combination of a web, desktop and mobile app. So having that come setup after deploying the playbook was really nice. The hard part for end users (for us at least since we’re running a private, defederated server) is pointing the client to the right URL. I made a PDF with a bunch of step by step instructions for how people can login with all of the apps.
That ansible playbook did make deployment much easier, but it’s still a ton of reading because of what a complex stack of tech is actually required to run a matrix chat server. I had originally tried doing it with a bigass docker compose file, and manually configuring all the reverse proxies. After two days of failing to get that working, I went with the playbook. It’s much easier than doing it completely DIY.
The only real difficulty I foresee with users down the line is what happens when people lose their recovery keys. Obviously there’s ways to log back in, but people probably won’t appreciate losing access to chat history. We’ll see how it goes, but generally the onboarding process is really easy. And it can be made easier by the fact that admins can just create users, so the whole registration process is optional.
who@feddit.org 1 day ago
Yep, the possibility of someone losing their recovery codes is a risk shared by practically all e2ee systems, authenticators, etc. (Have you backed up your Steam Guard recovery codes?) When a user is the only one with access to their secrets, they are also the only one who can be responsible for them.
This is part of why I suggested in my top-level comment that room admins coming from Discord disable end-to-end encryption when creating their first Matrix rooms. This keeps things simpler as their users get acquainted with Matrix, and reduces the consequences if someone loses their account recovery key. The point-to-point HTTPS encryption between client and server will still be in place, providing the same level of protection that Discord offers. End-to-end encryption can always be added to a room later, once everyone is familiar with the new environment.