Options for a good XMPP client?



  • @AppLee Push notifications work slightly different with XMPP, as it already has build in support for that. In theory you just need to pass back your device identifier and JID of the push service to the XMPP server (ConverseJS has build in support for that) and the XMPP server (if it has mod_push enabled) contacts the push notification service of the app developer (via S2S connection). The problem is that such an XMPP compatible server software that talks to the Ubports push notification server does not exist yet. There are existing projects though that seem quite close to what is needed.

    Edit: if the Ubports push notification server would understand XML messages it could likely also be contacted directly by the XMPP server. I think the original Android push notification system works like that, it is just that Google decided it would only allow registered servers to contact their push notification server, so a proxy server by the XMPP app developer is still needed. I think for Ubports push notification server is is not the case.



  • The developer of P2 is willing to add Ubports push notification support for XMPP clients, but it would need to be implemented by someone with Java knowledge. According to him it should be really easy though.

    On an unrelated note, this might also be a portable qt native xmpp client: https://github.com/ksiazkowicz/lightbulb



  • Just as an update to this: I talked to the developer of Jabbercat/aioxmpp and it seems it would be fairly easy to write a new mobile friendly qt quick controls 2 UI on top of his abstracted jclib (pure Python):
    https://github.com/jabbercat/jclib

    I am toying with the idea of having a go at it, but if a more experienced Python developer would take it up that would probably be more successful.



  • Another but also Javascript based option that seems promising (but still needs a bit of work) is this:
    https://github.com/nioc/xmpp-web

    It is even PWA capable, so on Android for example it works quite nicely as a progressive web app already. I hope PWA will be added to UT at some point, as it is really a neat standard for webapps.



  • Hi everyone, I'm New on ubports, on android I use Conversation , but on Ubports I want to use xmpp client for Muc chatroom support like gajim on Debian . I try with converseJS but don't work because I can’t connect .



  • @mito77 said in Options for a good XMPP client?:

    Hi everyone, I'm New on ubports, on android I use Conversation , but on Ubports I want to use xmpp client for Muc chatroom support like gajim on Debian . I try with converseJS but don't work because I can’t connect .

    Hi @mito77 can you explain better what you mean with "can't connect"? What XMPP server are you using? If it is self-hosted, make sure it is up to date and configured to expose BOSH or websockets as alternative connection methodes. Due to the webapp nature of ConverseJS you can not connect with the regular 5222 port as Conversations/Gajim etc. does.



  • @poVoq thank you . it work very good with bosh or wss link . I found on the wiki of the xmpp service. but ConverseJS dont save my login, and don't save my wss or my bosh. When I
    restart the app it's blank . https://wiki.jabberfr.org/JabberFR
    it's because the client don't have XEP-0156 natively



  • @mito77 the wss and bosh address is saved in the app, just not displayed again in the form field.

    However you need to put in again your JID and password each time. I have some ideas how to add an option to stay logged in, but doing so (with the option to also log out again) is a bit complicated.

    Xep-0156 is supported in the new upstream version of ConverseJS. I need to get around updating my app to it.



  • Hi Povoq I'm reconnected again and again on a muc, and the error message is : "This groupchat has reached its maximum number of participants". Or we are three people in the muc chatroom.



  • @mito77 this isn't really a support thread, and in any case that sounds more like a upstream ConverseJS issue. But what is the actual limit you set? I think in XMPP each connected device is counted as a user, even if representing only three actual people. Maybe there is an issue that devices are recognized as new while the old ones need some time to time out? No idea, just guessing 🙂


Log in to reply