Skip to main content


One thing I wanted to do for years was to experiment with Conversations acting as a push provider for apps that don’t maintain their own TCP connection (Tusky.app, Ltt.rs, …).

@unifiedpush’s recent post on the @fdroidorg blog¹ renewed my interested in this topic and I've just merged code that make Conversations a UnifiedPush Distributor.

I’m already receiving my @Tusky notifications via #XMPP 🥳

¹: f-droid.org/en/2022/12/18/unif…

reshared this

in reply to Daniel Gultsch

For me as a user, does that mean if I have Conversation installed Tusky (and others) recognize it as distributor and can use it out-of-the-box – or do I have to take additional steps?
in reply to Daniel Gultsch

How does #UnifiedPush compare with #Gotify? Is Gotify a UnifiedPush service? Or could it be maybe but it's another standard?
Unknown parent

Steven Roose
It could be an alternative UnifiedPush client and have its own persistent websocket connection for users that don't have a Jabber account? I thought it could already wake up other apps though, but I never actually used it fully. But I had an app that had push notifications through Gotify.
in reply to Daniel Gultsch

Great! I'm using UnifiedPush for @apps

A list of subscribed topics like in #ntfy [1] would be great!
And maybe some way to test if UnifiedPush is successfully set up.
(maybe that should even be tested once a day in background)

Also could Conversations list in the server information if the XMPP server itself is a UnifiedPush proxy and can be used instead of up.conversations.im ?
(of that is technically possible)

[1] ntfy.sh/