Skip to content
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

Remove Neo Store, Rephrase F-droid section #1821

Merged
merged 8 commits into from
Sep 28, 2022
Merged

Remove Neo Store, Rephrase F-droid section #1821

merged 8 commits into from
Sep 28, 2022

Conversation

matchboxbananasynergy
Copy link
Contributor

This PR:

  • Removes Neo Store
  • Adjusts the section on F-droid in the Android page to reflect our current stance on F-droid, in that it is not a method of obtaining apps that we recommend.

A lot of the reasons why are mentioned in the section in question itself, as well as the blog that we link to there:

https://wonderfall.dev/fdroid-issues

Pushing people towards F-droid inevitably causes headaches with slow updates (if using the main repo), out of date clients that don't follow best practices (official F-droid app) and a repository with many security downfalls.

Currently, if you're using Stock OS, it doesn't make sense not to use Play Store, as Google most likely has privileged access to the device, so the benefit you're getting by trying to avoid them and going through F-droid is dubious.

For people using GrapheneOS, Play Store via Sandboxed Google Play should be recommended as the fact that it is sandboxed as a normal application would be makes it something that's very easy to recommend (although the fact that it needs a Google account is not ideal). For people unwilling to create a disposable Google account for that, there's always Aurora Store which we recommend.

Then, we also have the RSS method of obtaining APKs from GitHub for people who would rather not use the above options.

@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 19:21 Inactive
@github-actions
Copy link

github-actions bot commented Sep 28, 2022

🎊 PR Preview 34bb00b has been successfully built and deployed to https://privacyguides-privacyguides-org-preview-pr-1821.surge.sh

🕐 Build time: 75.194s

🤖 By surge-preview

@ghost ghost added the c:software self-hosted/decentralized software and related topics label Sep 28, 2022
@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 19:36 Inactive
docs/android.en.md Outdated Show resolved Hide resolved
@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 19:52 Inactive
@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 19:54 Inactive
@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 19:56 Inactive
@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 19:58 Inactive
@ph00lt0
Copy link
Contributor

ph00lt0 commented Sep 28, 2022

Is this really the right decision? I fully agree with the security implications of the froid repo but quite a few companies/groups release their app in their own repository. These are afaik fine to use, Neo Store comes with auto updates, something you won't be able to do with Aurora. Updating all your apps manually is a painful process and likely will cause users to run outdated software which can be a big problem.

@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 20:43 Inactive
@matchboxbananasynergy matchboxbananasynergy added the t:correction content corrections or errors label Sep 28, 2022
Copy link
Contributor

@KaiTebay KaiTebay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really nice explanation. I've suggested a few minor grammatical and stylistic edits.

docs/android.en.md Outdated Show resolved Hide resolved
docs/android.en.md Outdated Show resolved Hide resolved
docs/android.en.md Outdated Show resolved Hide resolved
@matchboxbananasynergy matchboxbananasynergy temporarily deployed to preview September 28, 2022 21:35 Inactive
@matchboxbananasynergy
Copy link
Contributor Author

matchboxbananasynergy commented Sep 28, 2022

Is this really the right decision? I fully agree with the security implications of the froid repo but quite a few companies/groups release their app in their own repository. These are afaik fine to use, Neo Store comes with auto updates, something you won't be able to do with Aurora. Updating all your apps manually is a painful process and likely will cause users to run outdated software which can be a big problem.

I believe that this is the right way to go. As mentioned, people on stock OS have nothing to lose by using Play Store, given that Google already has privileged access to their device (it feels like you're fighting against something that you have no control over), and the same goes for people on GrapheneOS, because in that case, Play Store is not privileged and is just like any other app. Folks who use DivestOS get F-Droid by default, I believe. There is a caveat that some apps aren't listed anywhere and Neo Store is mentioned there, but I do not believe that it currently makes sense to have an entire card (and thus an implicit endorsement) for F-Droid given all of its issues. While developer repos are neat, app stores with multiple repos break the Android security model, and there are simply not enough of them to warrant recommending F-Droid at this point.

We are hopeful that other projects will eventually be ready (Accrescent being one of them) that can fulfill the role of a security-focused app store that doesn't require an account, but F-Droid currently isn't it.

@ph00lt0
Copy link
Contributor

ph00lt0 commented Sep 28, 2022

Is this really the right decision? I fully agree with the security implications of the froid repo but quite a few companies/groups release their app in their own repository. These are afaik fine to use, Neo Store comes with auto updates, something you won't be able to do with Aurora. Updating all your apps manually is a painful process and likely will cause users to run outdated software which can be a big problem.

I believe that this is the right way to go. As mentioned, people on stock OS have nothing to love by using Play Store, given that Google already has privileged access to their device (it feels like you're fighting against something that you have no control over), and the same goes for people on GrapheneOS. Folks who use DivestOS get F-Droid by default, I believe. There is a caveat that some apps aren't listed anywhere and Neo Store is mentioned there, but I do not believe that it currently makes sense to have an entire card (and thus an implicit endorsement) for F-Droid given all of its issues. While developer repos are neat, app stores with multiple repos break the Android security model, and there are simply not enough of them to warrant recommending F-Droid at this point.

We are hopeful that other projects will eventually be developed (Accrescent being one of them) that can fill in that hole, but F-Droid currently isn't it.

I agree with all your points tho. I really hope this will change and this action may speed up the process. I just think that many of us won't be able to get all apps without it.
Personally I do not have an actively used Google account and rely on Aurora to update my apps. I think many GrapheneOS users would be in the same boat. It may indeed not be a good recommendation, just a necessity.

@jonaharagon
Copy link
Member

Updating all your apps manually is a painful process and likely will cause users to run outdated software which can be a big problem.

Also, I do hope to recommend Obtainium for automatic updates when ImranR98/Obtainium#25 is implemented. I also don't think this is unreasonably difficult if you use the RSS method of keeping track of updates which we outline on this page.

@matchboxbananasynergy
Copy link
Contributor Author

Updating all your apps manually is a painful process and likely will cause users to run outdated software which can be a big problem.

Also, I do hope to recommend Obtainium for automatic updates when ImranR98/Obtainium#25 is implemented. I also don't think this is unreasonably difficult if you use the RSS method of keeping track of updates which we outline on this page.

I get 95% of my apps via GitHub/RSS and it really is a breeze. Compared to F-Droid which didn't even notify me in the past, I get a notification and click 3 buttons and I'm on the latest version instantly.

Re: Obtainium, I did stumble across this recently, and yes, unattended updates would be needed for it to fill a niche that makes it fit within our current recommendations. We'll keep an eye on it and evaluate it when the time comes.

@ph00lt0
Copy link
Contributor

ph00lt0 commented Sep 28, 2022

Well yeah my rss feeds usually get polluted when busy and I lose track, that's kind of what I am afraid for. Also we can do this, but explaining this to non techies will be too difficult.

Didn't know about Obtainium yet, will have a look.

@matchboxbananasynergy matchboxbananasynergy merged commit aaff825 into privacyguides:main Sep 28, 2022
@privacyguides-bot
Copy link
Collaborator

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/v2-26/49/1

@privacyguides-bot
Copy link
Collaborator

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/should-i-use-google-play/11894/4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:software self-hosted/decentralized software and related topics t:correction content corrections or errors
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants