-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Recommend F-Droid Basic over Neo Store #2293
Conversation
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/recommend-f-droid-basic-instead-of-neo-store/14311/2 |
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
8053654
to
95e44a0
Compare
Agreed, I think the language can be softened a bit as they have made some progress according to their blog. |
Agree with the change, though the unfortunate thing is that the F-Droid apps don't have a way to show you an app's targetSdk, which is what I personally liked about Neo Store, since F-Droid doesn't remove or hide apps with old targetSdk levels, and as far as I'm aware also doesn't prevent them from getting on to the store/updating their apps. Being able to see what the targetSdk level is at a glance is quite significant. |
@matchboxbananasynergy iirc, that was the original and main reason for not really recommending F-Droid as much as we used to initially. As F-droid allows apps with lower-API levels, that means weaker sandboxing for those apps, than if they were in Google Play etc. |
@@ -381,17 +381,17 @@ If you download APK files to install manually, you can verify their signature wi | |||
|
|||
![F-Droid logo](assets/img/android/f-droid.svg){ align=right width=120px } | |||
|
|||
==We do **not** currently recommend F-Droid as a way to obtain apps.== F-Droid is often recommended as an alternative to Google Play, particularly in the privacy community. The option to add third-party repositories and not be confined to Google's walled garden has led to its popularity. F-Droid additionally has [reproducible builds](https://f-droid.org/en/docs/Reproducible_Builds/) for some applications and is dedicated to free and open-source software. However, there are [notable problems](https://privsec.dev/posts/android/f-droid-security-issues/) with the official F-Droid client, their quality control, and how they build, sign, and deliver packages. | |||
==We only recommend F-Droid as a way to obtain apps which cannot be obtained via the means above.== F-Droid is often recommended as an alternative to Google Play, particularly in the privacy community. The option to add third-party repositories and not be confined to Google's walled garden has led to its popularity. F-Droid additionally has [reproducible builds](https://f-droid.org/en/docs/Reproducible_Builds/) for some applications and is dedicated to free and open-source software. However, there are some security-related downsides to how F-Droid builds, signs, and delivers packages: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think if we remove the privsec link here we should mention that apps in Google Play have to target a higher API level, and therefore have stronger sandboxing. We should perhaps show this article https://developer.android.com/google/play/requirements/target-sdk
A forum member pointed out that F-Droid Basic does show a warning on apps with a low target SDK. My understanding is that minimum target SDK for when this warning will appear will advance similarly to Google Play's policy with each new Android release:
https://www.xda-developers.com/android-12-alternative-app-stores-update-apps-background/ |
95e44a0
to
8028958
Compare
8028958
to
6bc2c5e
Compare
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/remove-note-about-getting-f-droid-apps-from-obtanium/14440/4 |
It looks like it does, but it only says that it won't auto update. I think we should mention something which summarizes:
|
I really don't see that change as critical given that:
So... I don't know how to word the additional changes you're suggesting to fit it in cleanly on the page tbh, but if you want to commit a change adding that somewhere you think is best, that's fine w/ me. |
That is fair I guess. Maybe we should say: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looked it over, everything looks perfect.
164df35
to
ebce060
Compare
Signed-off-by: Daniel Gray <dngray@privacyguides.org> Signed-off-by: blacklight447 <github.ef27z@simplelogin.com>
ebce060
to
b69edfe
Compare
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
Changes proposed in this PR: