Matrix to XMPP migration

[atzanteol@sh.itjust.works]

It's distributed through standard package managers, it would be trivial to create a Dockerfile to make your own container.

[sidewayshighways@lemmy.world]

snikket is prosody's little sister. docker ready

[couch1potato@lemmy.dbzer0.com]

I've been considering setting up matrix or xmpp, can I ask what is motivating you to switch?

[fmstrat@lemmy.nowsci.com]

Overall I've been happy with Matrix (private not federated), but it's very convoluted. Whenever anything goes wrong it's really difficult to figure out why, as there is a lot of complexity. And once you set something up, it's really hard if not impossible to make a change.

For instance, since it's built for federation, changing the URL is impossible.

So I'd like to try out XMPP since it's much more lightweight and simple. I may not switch, but want to explore.

[magikmw@piefed.social]

I'm looking at tuwunel to setup instead of synapse as soon as it's ready. Still matrix, but maybe better for small instances.

[kristoff@infosec.pub]

perhaps a stupid question, but are there bridges for XMPP ?
My impression is that XMPP is as good as empty (I do use it mainly as a federated service). Is there still a lot of active development on the XMPP side of things?

I do not understand your point with 'you cannot change the URL'.
If you use matrix as non-federated and just the only user, what is the problem that you need to change the URL when you need to set up a new server on a new URL?
Not being able to change the server at the same URL seems like a logical concequence of authentication, be it for server-to-server communication as for client-to-server communication.

[mat@linux.community]

Tuwunel had intentions to build a Synapse migration tool, but I haven't heard anything about it since. Was waiting for it so I could bring over profiles and most importantly chat history for myself and my family.

[fmstrat@lemmy.nowsci.com]

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.

[povoq@slrpnk.net]

Yes there are gateways (or transports) for xmpp. See for example https://slidge.im/ but there are also a few other projects.

It's maybe a bit less than for Matrix, but the ones that exist tend to work better.

[povoq@slrpnk.net]

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.

[povoq@slrpnk.net]

The Prosody docker images are basically https://snikket.org/ which is developed by one of the Prosody developers.

But Ejabberd also has good Docker containers.

[andres4ny@social.ridetrans.it]

@poVoq @fmstrat I ran ejabberd for years before switching to matrix (synapse). Matrix was a disaster, plus jmp.chat is a fantastic google voice / VOIP replacement, so I switched back to xmpp (with prosody). Out of those options, prosody is clearly the best for self-hosting.

[pika@sh.itjust.works]

I'm in this same boat as well. As someone who ran an XMPP server in the past, then stopped and eventually moved onto Matrix. I have to hard agree, in my experiences, XMPP was so much better administration side than having to deal with matrix, and its quite a bit more fleshed out(not to mention the sheer amount of clients available) Being able to just log into a management panel and have the panel do everything administration wise for me was super nice, instead of having to ask "is this only available via the API or is it available via a client or is this config only", these types of tools from what I've seen don't really exist for matrix.

[2xsaiko@discuss.tchncs.de]

Since you’ve used both, how do ejabberd and prosody compare to another? I was going to go with the former.

[andres4ny@social.ridetrans.it]

@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).

[andres4ny@social.ridetrans.it]

@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.

[ikidd@lemmy.world]

What's your docker compose for all of that? I would be interested in running that stack.

[fmstrat@lemmy.nowsci.com]

Is there a working Signal+Prosody setup?

[fmstrat@lemmy.nowsci.com]

How is signald broken? I'm using it with Matrix now just fine.

[povoq@slrpnk.net]

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.