It's unrelated, except for the fact that I used the reverse engineering of the facebook messenger protocol by the mautrix team [1]. XMPP has had bridges more or less from the start. [3]
I may add a "matrix plugin" [2] if I feel like it someday, but probably after I implement group chat support. Then you'll be able to use XMPP<->Matrix<->some-other-thing for extra over-engineering points. ;)
I prefer XMPP because it's lighter on resources, server-wise at least, and it's managed through a democratic process, which has it upsides and downsides. As someone I like said "democracy is boring, dictatorship works faster".
I did not know that, I gotta edit a bunch of replies now, thanks for correcting me.
To be fair, one of the reason I use XMPP and not matrix is that I didn't hear about matrix until after I managed to set up my own server and get some of my entourage to use it too, about 5 years ago or so. Interoperability is the important part anyway, and I'll work on slidge-matrix when I fix/improve some stuff in the existing core/plugins.
tbh Matrix was pretty green 5 years ago, so you probably didn't miss much. Thanks for considering a slidge-matrix bridge. On the Matrix side, we already have https://github.com/matrix-org/matrix-bifrost as our main Matrix<->XMPP bridge, but it could definitely be better, and the more interop between open protocols the better \o/ :)
