I've been working the last few weeks on some additions to my self-hosting cabal of software; I'm happy to present these changes in today's post.
This is old news, but I have an XMPP server! (denshi.org) I'm there and, in addition to having some public multi-user chats, these chats are bridged over to the Matrix and Discord thanks to Matterbridge. Here are the chats:
The XMPP server is open to registrations, so if you've been meaning to try out XMPP, here's your chance to get an account through in-band registration. Just make sure to encrypt your messages, or I'll spy on your Catholic conversations with your girlfriend!
But with this XMPP announcement out of the way, it's time for some long overdue ranting...
It's absolutely no secret that I love self-hosting. But something that has been bothering me for a while about the modern self-hosting world is people's obsessions with over-complicating everything. At first I just thought I was stupid, and I didn't have the knowledge or Reddit karma from my intellectual®® and quaint takes from r/atheism, but soon I realized that what a lot of people wanted to replicate with their homeserver or VPS was a similar experience to existing, centralized services ran by tech monopolies.
The first thing I thought when I leaned more about self-hosting wasn't "hm, how will I build my own Google?", it was more along the lines of "how often will I actually have to use this thing?". Setting up alternatives to social media, web password managers, web cloud storage, collaborative document editing and other Silicon Valley-esque products wasn't as interesting to me as exploring the completely new and fascinating world of setting up a personal website, email server and federated chat server. While I still did try to use bloated web "apps" like Nextcloud, I soon realized these were very overkill for any kind of cloud storage I needed and I simply stuck to using Syncthing and Rsync. Self-hosting isn't about replacing everything you already had with self-hosted versions, it's about changing the way one looks at their internet and bandwidth usage. Not to mention that software like Nextcloud has essentially become a corporate product. Yes, it's still "free/libre software", but it's so incredibly slow and painful to setup as an individual, which is a very common characteristic of business/corporate software.
More to the point, when I say "changing the way one looks at their internet and bandwidth usage", I mean coming to the realization that so many of the things people tend to use the web for nowadays (document editing, password storage, even web chat clients) can be done locally on your machine. In some sense, running something on a server is only done when that thing was made for a server-client paradigm. This is why I'm not so favorable towards these distributed/"web3" crypto networks that would let all clients act as servers. A chat server should not be distributed among various clients! However, things like using a local password manager and writing documents locally on your computers are no-nonsense basics that I would expect people to be doing. New self-hosters want to re-build the cage built by Google and Microsoft with their homeserver, when realistically you don't need any server to have a similar (or better) experience.
This is where stuff gets spicier. The Matrix "Synapse" server software is bloated. Sure, Matrix-org has an upcoming "next-gen" homeserver named "Dendrite" which is more efficient and written in Go, but this doesn't solve the inherit issue that it takes a corporation to write a server software nowadays. The Matrix protocol is very complex and unorthodox, which means that independent developers looking to develop a server software for it are looking at a large amount of work and testing. Also, the Matrix spec is constantly undergoing changes and new additions, which means most homeservers will likely run the de-facto "official" server software (matrix-synapse) which is a bloated, python mess.
XMPP by contrast is another decentralized chat protocol that is far simpler to write for due to its straight-forward usage of XML files. I know lots of prominent Linux YouTubers have promoted it as an alternative to Matrix, so I'll make something perfectly clear: XMPP. Is. Not. Matrix. Matrix is a fundamentally different (and admittedly overly complex) protocol that has very different defaults than XMPP. While both protocols are highly extensible, I think it'd be unlikely to see XMPP reach the usability and feature list of something like Discord, at least not outside of closed, single-server deployments.
In summary, XMPP is better than Matrix for those who are worried about the long-term sustainability and future of such a complex protocol (Matrix) and wish for a more "universal" and KISS-like standard (XMPP)