Options for a good XMPP client?

  • I played around with the UT Movim app a bit. Actually works reasonably well (but needs an update to Qtweb and SDK 16:04). The advantage of Movim is that it doesn't work like other XMPP clients internally (uses websockets instead) and thus should potentially work better on UT? The build in federated micro-blogging system is nice as well.

  • Hi, I will update the app in the next couple of days. Isn't much work 😉

  • Just a small heads up. I got a prototype working based on ConverseJS. Not ready yet for a release, but you can follow development here:

    It's a HTML5 app using qtweb so don't expect great performance, but it seems quite usable on my Nexus5 so far.

    The main issue right now is that it seems like the regular method of font loading in a browser does not work in a UT webview container. Anyone got a tip how to do that?

  • You can download a prototype version of my ConverseJS wrapper here now:

    I can't release this on the open-store due to the automatic app review restricting absolute paths in all apps. I tried about everything I could think of to avoid having the "/opt/click.ubuntu.com/" string in the ConverseJS settings. Help appreciated 🙂


  • Found a working work-around which managed to by-pass the open-store restriction:


    Help to improve it appreciated, although other than some CSS fixes, most work has to be done upstream in the main ConverseJS.

    Ideas to improve performance would be great.

    Also: is there a way to pass through browser notifications to the main system notifications in qtwebview?

  • @poVoq for information about the notifications, refers to : http://docs.ubports.com/en/latest/appdev/guides/pushnotifications.html

    But AFAIK, there is no such think through QTWebView, maybe you can catch the notifications somehow and use the push notifications system 🤔

  • @AppLee no I mean the HTML browser notifications that modern browsers use to directly pass through web-site notifications to the system notification queue. I am aware that these will not work if an app goes to sleep, but that can be suppressed with UT-tweek tool.

    Push notifications are a totally different beast that I am looking into here: https://github.com/poVoq/conversejs-ubports/issues/1
    (if there was an implementation for this, it would work with any XMPP client on UT, not only mine)

  • @poVoq I understand what you want to achieve.
    But I don't think confined apps can access the notification layer without using the push notifications system.

    [Edit] Have a look there : https://open-store.io/app/pushclient.christianpauly
    It's easy to understand but I don't have time to dive in 😉

  • @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

Log in to reply