proprietary components added with v1.3.6

[IzzySoft]

v1.3.6 introduced several proprietary components to the app:

I don't know if that was intentional or an accident, but could you please revert it? Your app is essentially no longer FOSS with those. Thanks in advance!

PS: Looking at your build.gradle.kts, this seems to have been intentional:

    implementation(platform(libs.firebase.bom))
    implementation(libs.firebase.messaging)

Maybe you'd consider libre alternatives for push notifications, such as UnifiedPush? For now, we've had to add several anti-features to your app's listing, which I'm afraid will scare some folks away 😢

[gohj99]

I don't know if that was intentional or an accident, but could you please revert it? Your app is essentially no longer FOSS with those. Thanks in advance!

Yes, I intentionally use FCM for push notifications

Maybe you'd consider libre alternatives for push notifications, such as UnifiedPush? For now, we've had to add several anti-features to your app's listing, which I'm afraid will scare some folks away 😢

Sorry, I didn't know UnifiedPush before this

[gohj99]

I will use UnifiedPush in the next version.

[IzzySoft]

I use multiple apps that work with UnifiedPush, for quite a while now. Works great! What's more, I decided using NTFY as push backend: double win. Because NTFY notifications can easily be triggered with a curl or wget command, I now also get notifications about server events and more on my Android device. Plus, it's totally FOSS – and who wants can also self-host the notification server (with NTFY, or with Nextcloud for example). Some more details on my Android website: Push Clients/Manager.

[gohj99]

Now I have a problem
Tdlib seems to only support FCM push on Android devices (https://core.telegram.org/tdlib/docs/classtd_1_1td__api_1_1_device_token.html)

[gohj99]

And already hava issue about notifications
#32

[IzzySoft]

I'm no Android dev, so unfortunately I cannot help with implementation. My suggestion would be opening an issue with tdlib, as glueing it to FCM leaves out devices without Google Services – not only "degoogled" devices, but also e.g. Huawei. As an interim work around, UP also has a libre implementation for a "fallback FCM distributor", which could work for you.

[gohj99]

Would you like tell me more about "fallback FCM distributor"? (Is UnifiedPush? and I how to do this.)
Thanks a lot.

[IzzySoft]

I'm not a dev, so I cannot dive into "development details". Basically, they have some code to fall back on FCM if no UP distributor is available. Guess that would be android-foss_embedded_fcm_distributor if you want to embed it into your own code (others are these).

[gohj99]

I checked and found that someone has submitted a request to Telegram on Jun 6, 2023 (https://bugs.telegram.org/c/28798)
But Telegram has not responded yet
And I think few people will install "Unified Push" on their watches (it seems to be used with Unified Push software)
So can't I use FCM for special circumstances?
If not, I think I can release two versions to achieve it (but this is not convenient)

[IzzySoft]

And I think few people will install "Unified Push" on their watches

On their watches? I thought push notifications would be sent from the companion app on the phone.

So can't I use FCM for special circumstances?

As outlined above: you can use the FOSS variant of the embedded FCM distributor – ideally as fallback in case no (other) distributor was found on the device. That might then need the NonFreeNet anti-feature, but at least avoid proprietary components.

[gohj99]

On their watches? I thought push notifications would be sent from the companion app on the phone.

Yes, Telewatch has achieved a relatively complete Telegram interaction, and no function depends on the mobile phone.