513
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Mar 2026
513 points (96.9% liked)
PC Gaming
14551 readers
411 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
Weird how they are good at digging up the past relationship between the matrix team prior donators with the mosad. but failed to mention not even once that matrix's biggest advantage is its federated nature.
So imagine you have a selfhosted matrix server and you want to invite a friend over for a chat but this friend already has an account at his other friend's server. in Matrix he doesn't have to make an account on every server their interlocutor is in, he just sends his messages, like its done over email, or here on lemmy (fediverse). this is an advantage other software like fluxer of stoat don't have. and I doubt they will able to add it anytime soon, as the work needed is probably huge and would need years of work to make a proper secure e2e federate messaging solution.
EDIT: changed to more accurately represent how Matrix operates.
The issue is that due to the way Matrix is structured, it essentially spreads copies of unencrypted metadata to every instance participating in those rooms, So it's federated, but difficult to actually keep metadata from being spread around ~~even if you don't federate with the main Matrix server, if any server you do federate with dies, it'll get spread there~~. You'd have to be extremely cautious who you federate with to avoid that, or not federate at all, which defeats the purpose.
As an alternative, Movim, which uses XMPP and is also federated, does not spread meta data around like that.
I've had matrix and element set up on my personal domain for a while, but I've only used them for evaluation so far. The system and network resources used are HUGE...
I've been setting up movim and a seperate xmpp server for a little while, and I have some initial opinions:
Either way, I am gonna deploy both and let my friends/discord channel users decide what works best.
I'm rooting for xmpp at the moment, but I will be happy with anything that is self hosted, encrypted and federated.
Hopefully I don't end up having to maintain both protocols with a bridge!
I know that part of the issue is the actual protocol, but you might try alternative matrix servers such as tuwunel for potentially better performance.
Thanks for the link, I'm happy to give it a try.
I just recently migrated all of my stuff to dockerized services, so swapping out pieces should be pretty easy
Resource usage is a common complaint for Synapse hosters, you might find something like Continuwuity more lightweight
Yeah, hopefully the dev or the community work on making it easier to deploy in a container at some point.
It is! But that focus is somewhat recent. The dev recently started a funding campaign to accelerate development, and just landed channels with rooms last week, so it's still rough around the edges, but the pace that they're implementing this stuff is impressive. They're later going to work on having drop-in voice rooms as well.
Despite the challenge getting it set up, I have high hopes for movim! I like the direction they're going now.
I did end up successfully deploying it in a compose stack (despite this issue), and I'll probably submit a fix if they don't get to it before I do.
If anyone is interested, I can share the details about how I got it going.