Matrix to XMPP migration
-
@2xsaiko A big caveat is that I used them in very different time frames - prosody starting from 2021 to now, while ejabberd I used from 2006 to 2012 or so. At the time I used it, ejabberd's config was done in erlang(!); they apparently they've since switched to yaml configs. It was generally fine, but when I switched back to XMPP in 2021, I figured I'd go with a server in a less niche language and better support (the jmp.chat folks mostly use & recommend snikket/prosody).
@2xsaiko XMPP is nice and lightweight, so I think either would work fine. I just find prosody has more community momentum.
It was matrix that was a massive memory hog, required running bleeding-edge homeserver software, didn't do proper security support, etc, so that's where I have stronger feelings.
-
Hi all,
I run a private self-hosted Synapse server with bridges for:
- Signal
- Doscord
- IRC
- Google Voice
- Custom APIs
I am thinking of switching to XMPP. Can anyone recommend a good Docker-based server and transport combo that I could test out?
What's your docker compose for all of that? I would be interested in running that stack.
-
Is there a working Signal+Prosody setup?
-
The Signal gateway has currently issues, due to Signald being broken.
For WhatsApp and Discord there is Slidge.
IRC works great with Biboumi.
I am not aware of a Google voice bridge, but there are ways to bridge to the regular phone network and sms. The easiest is the https://jmp.chat/ service.
How is signald broken? I'm using it with Matrix now just fine.
-
How is signald broken? I'm using it with Matrix now just fine.
I think you can't connect new devices or so and the development has stalled. But I don't use Signal personally, so not 100% sure. AFAIK the Matrix bridge is currently being rewritten with another backend.
-
Yes they are called "transports".
As for when I tried to change the URL, I was moving all services from publicly resolvable DNS to
.lan, and Matrix is an issue because you can't change that after the fact, even if you haven't federated.HI,
Thanks for the info (and also thanks to PoVog).My experience with mqtt is limited. I once set up a ejabberd server to try it out. It works but -as I mainly interested in federated chat- it was not that interesting. There was a lot less traffic and the rooms that exist that had traffic had a big issue with moderation (i.e. spam content). The S/N ratio of the discussions was a lot less then on matrix or other platforms.
I also notice it was missing some features that are do are present in matrix, like the ability to edit messages. From how I understand it, the modulator nature of XMPP is a nice idea but as there is a large diversity on clients and the features they support, it does seems to come down to only the lowest common domininator to really work well.
As I have just set up a pi5 as my new selfhosting-server, I might give it a try again, and see how well the transports (like slidge as mention by PoVog) work.
Concerning the URL issue, as explained, it kind-of looks like a normal side-effect of the principle of server authentication. Alsom your use-case (one server, one client) it not the normal goal why chat-servers are build. Even in a non-federated use, you have multiple clients connecting to it. Cchanging the server hostname will impact all clients, so is probably a very rare scenario.
I did see you use synapse. I do not know if you dendrite or conduit have the same behaviour. -
@2xsaiko XMPP is nice and lightweight, so I think either would work fine. I just find prosody has more community momentum.
It was matrix that was a massive memory hog, required running bleeding-edge homeserver software, didn't do proper security support, etc, so that's where I have stronger feelings.
Thanks! I’ll take a closer look at both then and see which I like better.
I am running a Matrix homeserver right now and yeah it’s definitely a mess.
-
What's your docker compose for all of that? I would be interested in running that stack.
You should check out docker-compose-viz or dockge for visualizing/managing these complex setups - I've been using them for my audiobookshelf server (which I access with the soundleaf app) and it's been a lifesaver for managing all those interconnected containers.
-
I think you can't connect new devices or so and the development has stalled. But I don't use Signal personally, so not 100% sure. AFAIK the Matrix bridge is currently being rewritten with another backend.
Ahh, just realized the Mautrix Signal bridge I use no longer requires SignalD
-
Since you’ve used both, how do ejabberd and prosody compare to another? I was going to go with the former.
Ejabberd has more enterprise features and scales better for large public servers, Prosody has more interesting community modules and generally is ideal for smaller private servers (but has a very nice invite system).
-
You should check out docker-compose-viz or dockge for visualizing/managing these complex setups - I've been using them for my audiobookshelf server (which I access with the soundleaf app) and it's been a lifesaver for managing all those interconnected containers.
I use Lazydocker, I find it has more useful info and stats than Dockge, but I haven't tried the other.
-
Is it worth swapping from snikket? Seemed to ve an easier way to get prosody
-
Is it worth swapping from snikket? Seemed to ve an easier way to get prosody
@ssdfsdf3488sd My understanding it that they're both pretty much the same, so I wouldn't unless snikket has stopped being maintained or something?
