this post was submitted on 15 Apr 2025
51 points (96.4% liked)

Selfhosted

46212 readers
310 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi there,

I would like to host my own Synapse server, but I am not sure where to start.

I would like to be able to use Nginx Proxy Manager as the reverse proxy and I've read that you can use example.eu for the username, while actually using a subdomain like matrix.example.eu?

Is there some good documentation out there and what would people recommend? I would like to run it in a container on Proxmox, but Docker could also be an option?

you are viewing a single comment's thread
view the rest of the comments
[–] sxan@midwest.social 4 points 1 week ago (1 children)

The problem is the design is Matrix itself. As soon as a single user joins a large room, the server clones all of the history it can.

I mean, there are basically two fundamental design options, here: either base the protocol over always querying the room host for data and cache as little as possible, or cache as much as possible and minimize network traffic. Matrix went for minimizing network traffic, and trying to circumvent that - while possible with cache tuning - is going to have adverse client behaviors.

XMPP had a lot of problems, too, though. Although I've been told some (all?) of these have been addressed, when I left the Jabberverse there was no history synchronization and support for multiple clients was poor - IIRC, messages got delivered to exactly one client. I lost my address book multiple times, encryption was poorly supported, and XMPP is such a chatty protocol, and wasteful of network bandwidth. V/VOIP support was terrible, it had a sparse feature set, in terms of editing history, reactions, and so on. Group chat support was poor. It was little better than SMS, as I remember.

It was better than a lot of other options when it was created, but it really was not very good; there are reasons why alternative chat clients were popular, and XMPP faded into the background.

[–] poVoq@slrpnk.net 2 points 1 week ago

You must have last used XMPP more than a decade ago, since none of these issues still exist (except on Pidgin which also hasn't been updated since a decade).

And XMPP is also not a "chatty protocol, and wasteful of network bandwidth" at all. In fact it is using significantly less bandwidth than Matrix and works on extremely shitty connections. It is basically the exact opposite of what you say.