Hey there,
currently running both Synapse for Matrix and Prosody for XMPP.
I know migrating from Prosody to ejabberd is simple, but are there mogration pahs for Synapse as well?
That thing needs way too many ressources. Migrating both to ejabberd would allow me to run one single server for all my comms instead of two.
I don’t think there will be a way to fully migrate it like that, but you could try to find someone willing to continue running a Synapse server and ask them to set up a bridge to your XMPP channels (for example with Parsee or the Aria-net Bifrost). That way when you shut down your Matrix server, the existing distributed rooms will continue to exist at least on that other Matrix server and the bridge will ensure that people can communicate with you indirectly.
@erebion@lemmy.sdf.org
Matrix on ejabbered doesn’t really work as one would like, at least that’s what I read, so best test it on another subdomain before you really migrate.
I didn’t read yet from anyone, really using it as a matrix server.In fact from the little responses I got asking the responsible people at Process One it sounds a bit like they only plan to make it work for out-going federation, meaning you can participate in rooms and contact people on Matrix, but not the reverse. This is likely to fake the DAG and thus not have to run a full Matrix homeserver like federation, but that is only my rather unqualified idea. (However this is corroborated by the Element CEO recently musing on HN about a kind of two class federation where not all participating servers run the full stack).
Anyways, right now it really only does outgoing 1:1 chats and I haven’t seen much active development on it either.
.
