-
-
Notifications
You must be signed in to change notification settings - Fork 43
[Feature] F-Droid #67
Comments
Also, our scanner found some JARs (we don't allow JARs, all must be build from source):
Could you please take care for them as well? You could e.g. include their source trees as git submodules. |
@dimqua It's difficult to remove FCM because we use it to receive push message for latest status. I will consider a way to balance the two and try to add into the F-Droid store. |
@IzzySoft Oops... Thanks for your reminder. I should obey license carefully. These days I will check it. |
Thanks @fython! As for FCM: there are alternatives. I don't know them in detail (I'm no dev), but e.g. Tutanota has implemented their own, plus there are 2 (or more?) FOSS libraries I've heard from (unfortunately I always forget their names). |
@IzzySoft How does Tutanota implement instant push service, use a foreground service and keep connection to their own servers (or user custom servers)? I want to try not to do this. It's not good if every apps keep their own push service. They will cost a lot of battery life. In China Mainland, Google & API have been blocked for many years. Most apps (including not only social apps) build own services, which causes my phone runs slowly. That's a bad experience. I expect a solution to provide a push service similar to FCM: A push library for our apps and a backend app for keeping a connection and forwarding push message to each apps. If anyone find some solutions, please share with me. I will be very grateful! Thanks! |
I'm no dev, so I cannot explain – but there was an Article on it at F-Droid: How Tutanota replaced Google’s FCM with their own notification system. And I wish I'd remember the other two… |
@fython any progress on this? My snippet here contains a few hints on push messaging alternatives which might help. Do you see a chance to get the app "F-Droid ready"? |
@IzzySoft Thank you for still paying attention to the progress of my project. Since the API used by the project is temporarily unavailable, I put aside its update until I have a more suitable API to use, and the preparations for release on F-Droid may become more uncertain. I am sorry to bring this news. At the same time, thank you very much for sharing this information. I will consider trying free push service solutions in other projects. |
Thanks for the update! Indeed I was hoping for better news – but can't be helped… Best luck then! 🤞 Just let us know when we can pick up again. |
@fython looks like my wishes have not been granted: didn't hear back from you, and there were no changes to the code published either. I hope it's OK with you if we close the request at F-Droid's end, as it's unlikely we can process it. Should the situation change, be welcome to ping us and we can pick up again. |
@IzzySoft No problem. I'm sorry for not pushing forward because I don’t have enough time to maintain the project. Anyway, thank you very much for your help and follow up. |
Just keep this issue open because it's still a good feature to support. |
Yes, please do! I just had to apply some house-keeping on our end as it began to become unmaintainable. Hundreds of open issues with many we just could process, which were stalled, etc. |
I think it'd be nice to add such a good app to the F-Droid app store. :-)
Don't you mind? (I have to ask.)
Currently the app uses Firebase SDK, Google Play Services and a few JARs. They are prohibited by F-Droid rules. Is it possible to build this app without them?
Besides, the latest Play Store release (3.1.4) is not tagged. Is this a mistake?
The text was updated successfully, but these errors were encountered: