Sonny Piers

Please note that an error reply is a correct ping response as it fulfils its purpose. `iqCallee.get('urn:xmpp:ping', 'ping', ctx => { return {} })` is correct, it replies with an...

@Pistacchione you're right, my point is that answering a ping request with an error is considered a ping response anyway because it fulfils the purpose of the ping. Anyway, I...

@netmikey this is not how you're supposed to reply to iqs with xmpp.js. The solution is in https://github.com/xmppjs/xmpp.js/issues/629#issuecomment-458528741 See https://github.com/xmppjs/xmpp.js/tree/main/packages/iq#callee

@kriegster108 what type is the client trying (and failing) to use? which types are offered by the server?

@kriegster108 ok - it still looks like a bug with `xmpp.js` though, could you share the output of https://github.com/xmppjs/xmpp.js/tree/master/packages/debug ?

So if I understand correctly the use case would be to always use the same SASL mechanism? I'm torn. On one hand it is trivial to do with `@xmpp/client-core` (simply...

@yuanchieh-cheng XEP 0034 is deprecated, you're looking for https://tools.ietf.org/html/rfc6120#section-6.3.3 Can you please elaborate on your use case? Do you want to *always* use a specific SASL mechanism or simply add...

Crazy I've never heard of junction before. We're already using `js-sasl` from @jaredhanson (thanks!) :) @smokku perfect timing, I was looking today at our current plugin API and how to...

https://github.com/xmppjs/xmpp.js/pull/490

we now have a junction inspired middleware API