Selfhosted
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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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.
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.
@poVoq @sxan I have a 200MB/mo data connection, and my XMPP client (Cheogram) is barely a blip. The main driver of data usage with it is when my family is sending around 0.5MB images to each other.
@poVoq @sxan Also, I used to maintain a matrix client in Debian, as well as self-hosting synapse. I went back to XMPP.
@Andres4NY @poVoq @sxan The main problem with xmpp is that depends on your phone you are not sure you will receive messages because android and iOS kill the xmpp app.
@leodavinci @poVoq @sxan I can't speak to iOS, but at least on android that's not a problem as long as you grant it the proper permissions.
M@Andres4NY@social.ridetrans.it @poVoq @sxan After convincing some friends to install the client Conversations in Android, they finally gave up for this problem. They have Xiaomi phones and if they don't receive a message in one day, the OS closes the client and they don't receive messages anymore after they open the app again. Even with push notifications enabled in Conversations.
That problem has made me look alternatives like matrix. But, its more difficult to host a matrix server than a xmpp server...