Support unified push

GMS is not FOSS but without GMS the client can't receive message and drain the battery. Could you please support unified push?

added 1 deleted label

changed the description

Will depend of https://github.com/appleboy/gorush/issues/578

Update:

https://unifiedpush.org/developers/android/#register-for-push

So I guess the way to go:

1. Modify the dht_proxy_client.cpp to pass wanted informations to the server
2. Install a ntfy server along a proxy server
3. Modify android code (or linux) to register to any provider on the mobile of the app
4. Enjoy!

closed

Is this already implenmented?

no it's a duplicate (there were 3 issues about this in this repo), but I keep this as a reference and want to check this as it's mature enough :)

Where should I track the progress?

I closed the 3 issues in fact, so I will update this one

reopened

assigned to @sblin

Started https://github.com/savoirfairelinux/opendht/pull/636

And for Jami

https://review.jami.net/c/jami-client-android/+/22682

assigned to @aberaud

mentioned in issue #1142 (closed)

Just an update, I took some time last Friday and this morning to get it working

So, with

https://github.com/savoirfairelinux/opendht/pull/647 (proxies must be re-deployed)
https://review.jami.net/c/jami-daemon/+/23185
https://review.jami.net/c/jami-client-android/+/22682

it works with ntfy.sh (and should work with all other providers)

The patches will need some cleanup before to be merged, but it will come hopefully in a near-future!

added SprintTo review label

added to epic &50 (closed)

changed due date to January 31, 2023

mentioned in commit jami-daemon@a5d4bfb8

mentioned in commit 3a8b7098

@linsui next nightly/version will be compatible unified push

Great! Should F-Droid switch to the withUnifiedPush flavor? Is that enough to install ntfy to enable the UnifiedPush?

Yes, F-Droid should use the withUnifiedPush flavor, which will build with the UnifiedPush library and use ntfy or another push provider on the phone.

@aberaud what's missing for this?

I use Jami on LineageOS without microG. Since latest update, I had a popup "No distributor found" "You need to install a distributor for push notifications to work. For more information, visit https://unifiedpush.org". That message is in English although my phone and Jami are in French.

After setting up, in the Conversations app, an XMPP account for push notifications, I can see in Jami an option "Notifications poussées" that is selected while it was not there before, so it looks good.

However, the description is "Utiliser les serveurs de Google pour permettre la réception d'appels/messages en tâche de fond". I hope Jami is now using the push distributor from Conversations and not Google things and the message in Jami settings needs some correction.

Does that need a separate issue?

Thanks for the feedback. Yes, it's a text issue, in your case, Jami would actually use the Push provider that you selected instead of Google servers. This would be fixed in the next release.

closed

removed SprintTo review label

removed 1 deleted label

@linsui question. Do you know if FDroid is planning to integrate their own default push notification app like Firebase is embedded for the play store.

Because for now, using Unified Push is not straight forward for users as it requires for them to understand notifications and how to setup a push provider. Moreover ntfy got some pretty low limits at least for us (under investigation) and we also want to avoid to ask users to change their default server (unless if we can ask org.unifiedpush.android.connector to use a specific server???)

No, there is no such plan and I'm pretty sure this won't happen.

Maybe you can take a look at this. It's a FOSS implementation of Firebase client.