New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F-Droid Support #113
Comments
There is open RFP (Request For Packaging) at F-droid in: |
F-Droid maintainer here. The main thing currently missing are Fastlane structures (minimal set would be |
We will back to F-Droid support after next major release. Actually there is issue with secrets which we are generating for our app on building stage, they are using as salt for some encryption processes. So we need to decide how to handle this situation for F-Droid builds. |
That could possibly be included with the F-Droid build process (as part of the so called "build recipe") as well, as long as it only relies on FOSS tools (like packages that can be installed from the standard Debian repos and are then called to produce the "salt"). |
And update on this? Also, latest update included push notifications, mind if I ask what method you used? |
Sorry we had some other integrations for that time. We are planning to back to this around 21 June. |
Appreciate it. |
Still working on it. |
The Play Store API might have temporarily broken Aurora, so Cake doesn't appear to be there now. I'd love to be able to install and update from F-Droid, so count this as moral support for the F-Droid effort. Thanks for working on this. |
We just back to integration into F-Droid again. We will work on option to build the app without push notifications which require google api. |
Please do. Have also never received a push notification, so not sure what it's used for (exchanges maybe?) |
I imagine some people want push notifications for something like notification that a transaction went through, or got X confirmations, or something like that, but I'm not sure whether that's the use case for push notifications with Cake. I haven't really used it yet, in part because of the lack of F-Droid support. I'm looking forward to F-Droid availability now. |
Agreed. Currently cake disconnects when in the background (at least, on android), and I've never received a push notification with the current implementation. I wouldn't mind a FOSS alternative, even a polling solution or a persistent notification. Idk what the play store version ships with, it can have all the tracking available. Lol. but a clean f droid build is what I desire. |
@CakeWallet uses push notifications for remind about updates in new versions of the app and notify users that released new version. |
@mezzazon then you won't need that in the F-Droid build anyhow: as F-Droid has its own signing process, APKs signed by you wouldn't be compatible (signature mismatch), and updates available at F-Droid itself are reported by the F-Droid client. Should you ever need push notifications for something else, take a look at my notes here. UnifiedPush is already supported via Gotify-UP which is available at F-Droid. |
Since Monero and F-Droid both value the openness and privacy, F-droid support will really be beneficial. |
@IzzySoft Looking at another issue #198 , I've found out that currently at least three third-party service(s) are being indirectly used.
(Don't get me wrong, there is just a requirement to notify, not remove it altogether. Giving alternatives or stripping away does work but you should weigh between functionality and openness.) relevant source(s): |
@BraINstinct0 good points. For F-Droid, that would be covered by the NonFreeNet anti-feature – while FCM (here for push notifications) would block inclusion. May I again point to UnifiedPush, which just got a few more distributors ("back-ends") added? See my list here. |
Sorry that we hold pause on this. We are working on couple of new releases and then we will back to fdroid integration. |
No worries, I'd rather wait for(or contribute for) stable F-Droid supported release than get early hit-and-mostly-miss releases. |
Well, you certainly cannot clone yourself to get more jobs done within the same time, so you have to set priorities 😉 We gladly help you when you're ready for it – the sooner the happier, but with patience of course 😄 |
If FCM is the only disqualifying non-feature, as a part of the community, I would greatly appreciate that a FLOSS cake wallet is released with greater priority than ztrash. People are skeptical, and I believe there to be some justinfication to that. .. Good morning. |
Or, if it doesn't seem to be timely, we cannot clone mezzazon but we can clone cake_wallet - that's one of what oss is for, doing the right thing when things seem to be going the other way. But, I can wait. :) |
CAKE-99 | added paste_ios.png and removed duplicate.png; applied ios …
CAKE-99 | added paste_ios.png and removed duplicate.png; applied ios …
Would love to see this on F-Droid. |
Just fell on this once more during the latest triage run at F-Droid. Any progress so far? We'd like to keep the number of "dormant issues" at a minimum, and there was no update for almost a year now. Any ETA? Shall I set another reminder for a heads-up? No pressure, but it would be good to know where we stand 😉 |
To rebump Edit: Status IM has recently added firebase to their messenger app. |
@mkyq any response to my above question? As the RFP is still dormant, it will now enter the closure phase: it's now 1 year that we got the last response there. |
I've just checked the latest Library Checker Results
|
Same. It wasn't long ago that I had seen app manager show Google trackers Commit when code was added: Not sure if any other blockers for f droid? @IzzySoft |
Going by the results of my scanner I'd say it looks good. I'm no expert in license compatibility, though – you got quite a mix there of BSD2/3, MIT, Apache, GPL2. IIRC there was some issue of GPL2 having conflicts with Apache – but maybe that was using GPL2 libs in Apache apps or vice versa, so this possibly does not affect you as your app is covered by MIT. |
What is the status of either cake on fdroid or a cake repo? |
Any progress on an F-droid release? |
Highly interested in an F-Droid release |
Just my own two cents: I'd just prefer it be in the fdroid repo. Fdroid is a trusted brand in the open source community. |
great wallet please i need updates over f-droid :) |
Bumping this as I'd like to see the wallets, or even just Monero.com wallet, on F-Droid. Either a Cake specific repo or the F-Droid repo would be good. |
No clue what you want to say with this. |
Then go for reproducible builds and have the best of both: for enhanced trust people can install from F-Droid, and you can provide the faster updates when needed. Though F-Droid nowadays usually spits out updates almost daily, not once or twice a week as in the past (build infra was revamped). |
Sadly, more than 2 years have now passed since this issue was opened (and it has been over 3 years since this same request was initially made here, on the Monero sub on Reddit - the first of several such requests made on the Reddit over the years), and, from reading through this thread, it doesn't appear that much, if any, progress has been made on the Cake Wallet feature that has been the most requested feature by the community (per # of 👍 on all open Issues in this repo). And, FWIW, I strongly agree with the community on this - for an Android app to exist within the Monero ecosystem (an ecosystem fundamentally based on privacy), having an easy/automatic installation/update path other than via the Google (a company that essentially represents the antithesis of privacy) Play Store is really basic table stakes for an app to any privacy-minded Android user, and, IMHO, should be the most highly prioritized feature to work on (other than P0 issues, of course, like patching an urgent security vulnerability, if one were to be discovered). At the time of this comment (May 2023), most other significant Android wallets/apps in the Monero ecosystem are available on F-Droid (Monerujo, Stack Wallet, Shruum, Mysu, WooKey Wallet, AgoraDesk, LocalMonero, etc., etc.). Many of them have been available on F-Droid for years by now (and some have even ensured availability on F-Droid since Day 1 - starting from their very first release). At this point, it genuinely seems to be easier to find Android apps in the Monero ecosystem that are available on F-Droid than ones that still are not, as the Monero development community, by and large, seems to understand the fundamental importance and privacy implications of ensuring that Android apps in the Monero ecosystem are available via F-Droid, and they have prioritized accordingly. Cake Wallet is now one of the few remaining significant apps in Monero ecosystem that doesn't have its Android app releases available via F-Droid. And, given Cake Wallet's popularity, it sticks out like a sore thumb in this regard. Fortunately, Cake Wallet is a FOSS project, so perhaps the community itself can help to finally make its top request for Cake Wallet a reality after years of it languishing on the back burner. If I have understood the responses by Cake Wallet maintainers in this thread correctly, is the main blocker here that the maintainers themselves don't have enough time to do the work which would allow Cake Wallet releases to be made available on F-Droid (which is perhaps exacerbated by the fact that the maintainers may not fully understand or agree with just how truly critical F-Droid availability for Android apps is considered to be by the Monero/privacy communities, and, thus, other work continues to get prioritized ahead of it)? Whatever the reason(s) may be, given that F-Droid availability for Android apps in the Monero ecosystem is truly of the highest importance to the community, I know I'd be willing (and perhaps other devs in the Monero and/or F-Droid communities would be as well) to help work on whatever needs to be done to make release availability on F-Droid become a reality for Cake Wallet. Since it appears to have been nearly a year since a Cake Wallet maintainer has commented on this thread, if a maintainer (and/or perhaps @IzzySoft) could update the community and let us know what issues currently remain that are preventing the availability of Cake Wallet releases on F-Droid, then perhaps the community will be able to begin to assist with resolving those issues. Then, hopefully, Cake Wallet will finally become a legitimate option as a Monero wallet for a whole new base of privacy-minded Android users who refuse to install apps (especially apps having to anything to do with finances/crypto) through the Google Play Store (and, I imagine, are a group that is highly likely to prefer Monero as their cryptocurrency of choice). Thanks for reading my diatribe - I look forward to hearing how I can help! |
It's a matter of time. @tannerdsilva will add a F-Droid repo when he has the chance. Currently, he is working on other tasks. |
It seems that you are rejecting the idea of getting help from your community. Am I right? |
My point is that, unfortunately, the community has been repeatedly told F-Droid support is just "a matter of time" for more than 3 years now, so it's become a bit like The Boy Who Cried Wolf at this point. Considering this is something the Cake Wallet team has been unable to find time to do in years, why not embrace the core principles of FOSS and provide the community information so they can at least attempt to make contributions that would lighten the load on your team? |
No, it means that the community can't set up a F-Droid repo on our behalf. |
I am kinda new to Monero, and looking for a nice wallet to use on my Linux desktop. (I am already running a full node, BTW.) This response from the contributer is a bad look. Cake wallet was suggested to me by someone else, but now I don't think it passes the smell test. Edit: Linux desktop and Android. |
So, maybe the community can help with something else that will unclog the bottleneck. But, this is a three-year bottleneck. What's up with that? |
as one of the strongest proponents of fdroid inclusion, all i have to say is - the comments made today are terribly flawed. none of the aforementioned wallets offer anything more than a centralized mirror for trusted apks. "f-droid.org" =/= fdroid self hosted server =/= fdroid self hosted build server want to know if cake can be built from the source you see here? github actions automatically builds cake. |
id set the repo up myself but like sgp said, priorities. |
|
how many other monero wallets are on fdroid? |
Cake made necessary changes to be compatible with the build method, but it still takes man hours to not only research but to maintain the repo. can cake prioritize this? Sure. But then cake has to worry about how to avoid collecting info that can be targetted. xyz ip downloaded every update of cake for 6 months, most recently 15 mins ago. They also are 1/10 users who refresh every 2 hours". what is the ideal solution? |
At least two. Both stack wallet and monerujo Edit; i stand somewhat corrected. Monerujo is via IzzyOnDroid while stack offers their own repo... But, you can get both |
incorrect. neither one is on fdroid. they are both just apk repos hosted on monerujo and stackwallets websites. you can add those repos to the fdroid app, but those repos can contain anything. even 100% proprietary apks |
You are right. I edited my above comment to add that bit |
What smell test? The fact that we have been providing new features and listening to the community for over 5 years. Its not like we are sitting on our hands. |
Thanks for the feedback. You can avoid the google store and download the apk directly you know. This what what your long post is based on. This comment "Cake Wallet will finally become a legitimate option..." is interesting as Cake is already one of the most popular Monero wallets on iOS and Android and is a VERY legitimate option. Regarding Fdroid, it's on our list, but we keep putting out new features we think are more useful to our users. People love the new features. And as I said in the other comment, it's not we are sitting on our hands. We put out new stuff monthly I think - if not weekly. |
I think we'll be able to close this ticket soon.... |
This issue a carryover from #105, in which two topics were brought up and one was resolved. The outstanding topic is related to F-Droid support, and is the primary concern of this issue.
In issue #105, @mezzazon mentioned that F-Droid support is in the works, but adding such support created various constraints that we need to avoid to ensure a complete experience for all users.
As F-Droid support evolves, this issue will be updated accordingly.
The text was updated successfully, but these errors were encountered: