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…

  • Serge Tarkovski
    2·
    4 years ago

    Does the XMPP bridge support puppeting? From the Matrix side, it’s just a single bot posting on behalf of the whole XMPP side.

    • southerntofu
      3·
      4 years ago

      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.

    • MattOP
      1·
      4 years ago

      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… 🤔

  • phthalo
    2·
    4 years ago

    The connection keeps failing for me: remote server timeout. Thanks for the bridge though :)

    • MattOP
      1·
      4 years ago

      Which client are you using to connect?

      • phthalo
        1·
        4 years ago

        Conversations. Is it working for everyone else?

        • phthalo
          1·
          4 years ago

          It seems to work using an alternate account (though I’m unsure why haha)

    • darhma
      1·
      4 years ago

      I’m facing the same issue with conversations

        • darhma
          1·
          4 years ago

          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

          • southerntofu
            1·
            4 years ago

            From disroot chatroom:

            10:01:54 Muppeth> southerntofu, from our logs quick check (not in front of keyboard)  
                  "Forbidding insecure connection to/from muc.do.nohost.me because its
                  certificate is not valid for this name"

            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?

            • darhma
              2·
              4 years ago

              In Conversations it sais just: “Remote server timeout”

              • phthalo
                1·
                4 years ago

                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.

            • MattOP
              1·
              4 years ago

              Might be that Yunohost is not adding the subdomains to the LetsEncrypt requests…

              Will check it

            • MattOP
              1·
              4 years ago

              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…