Repository navigation
Has Droid-ify really rebranded to Neo-Store? Or are those two apps? #153
Description
Activity
Parts of that article need to be updated (#151).
The TL;DR about Droid‑ify and Neo Store is that Droid‑ify rebranded to Neo Store, and then the original dev of Droid‑ify forked the project to create the Droid‑ify we currently have.
The best F‑Droid client to use currently is actually F‑Droid Basic which is significantly less buggy than Neo Store and Droid‑ify alike, supports repository mirrors properly, and removes an extra party of trust.
Just note that, if you'd like to disable the F‑Droid main repository, you will need an alternative method to receive updates for F‑Droid Basic, such as Obtainium.
Thanks for the quick and helpful reply, that is good to know! If I can do something to help updating the article, let me know – apart from that, this issue can be considered solved, at least from my side.
- locked and limited conversation to collaborators
on Dec 12, 2023
I've just read https://privsec.dev/posts/android/f-droid-security-issues/ and am deciding to switch to a different F-Droid client to avoid some of the issues mentioned there (e.g. targeting an higher Android API level to make use of better sandbox features, not requiring a privileged extension with questionable security practices for batch updates while still allowing batch updates).
The post mentions that
However, both Droid-ify and Neo-Store seem to be alive and well:
What has happened here? Should I use Droid-ify or Neo-Store instead of F-Droid, or are they equivalent from a security standpoint?