For those that are using #XMPP, I’ve created a Lemmy chat room at lemmy@muc.do.nohost.me which bridges to the Lemmy Matrix room…
Extensible Messaging and Presence Protocol (XMPP) is a communication protocol for message-oriented middleware based on XML. Learn more about it here.
Here’s another option for joining Matrix rooms from XMPP 👍
https://github.com/matrix-org/matrix-bifrost/wiki/Address-syntax
Does the XMPP bridge support puppeting? From the Matrix side, it’s just a single bot posting on behalf of the whole XMPP side.
Same on the Jabber/XMPP side. It’s a matterbridge bot, not an actual bridge. matterbridge supports puppeting on XMPP side but through an experimental module (mod_slack_webhooks) but it should be standardized in the next prosody version (with mod_rest). On matrix side, no clue.
A proper bridge would be bifrost, however it’s still pretty unstable and requires running a matrix server, which is very resource-hungry so most collectives/sysadmins are not going to do that.
Anyway seems people are happy chatting even this way.
That I don’t know… It’s using Matterbridge, I couldn’t find anything on the subject for it…
I do know that it shows the method <XMPP> and the user handle…
It might be a limitation of the bridge… 🤔
awwww yeah
The connection keeps failing for me: remote server timeout. Thanks for the bridge though :)
I’m facing the same issue with conversations
What are your servers? Are they the same? How is your server doing on the Conversations compliance checker ?
I’ve just tried with another account and thats worked. The one doesn’t working is disroot.org that has a score of 95% in the compliance checker
From disroot chatroom:
So your client should warn you the certificate was wrong (not just timeout). Can you confirm it did? Otherwise it’s a bug :)
So it appears it’s a TLS problem on your server @imattau@lemmy.ml can you check?
In Conversations it sais just: “Remote server timeout”
I was using disroot as well. They are moving their servers at the moment, so perhaps that is why? Kind of a vague error on Conversations though.
Checked at https://xmpp.net/ and it comes back with an ‘A’ for the s2s connections… The only thing I can think of is that the certificate does not have a wildcard…
Might be that Yunohost is not adding the subdomains to the LetsEncrypt requests…
Will check it
Which client are you using to connect?
Conversations. Is it working for everyone else?
Seems so…
It seems to work using an alternate account (though I’m unsure why haha)
Thanks! If you style it like
xmpp:lemmy@muc.do.nohost.me?join
Click me one can actually click the link and have it open in a xmpp client.Fixed