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…
GitHub - iNPUTmice/lttrs-android: No-frills, easy to use, easy to maintain Email client for Android based on the JSON Meta Application Protocol (JMAP).
No-frills, easy to use, easy to maintain Email client for Android based on the JSON Meta Application Protocol (JMAP). - GitHub - iNPUTmice/lttrs-android: No-frills, easy to use, easy to maintain E...GitHub
Peter Vágner likes this.
reshared this
IzzyOnDroid ✅
in reply to Daniel Gultsch • • •Steven Roose
in reply to Daniel Gultsch • • •Steven Roose
Unknown parent • • •kolAflash
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/