We have been running an #FDroid-compatible repository since 2012! Since then, the free software ecosystem on Android has blossomed, meaning @fdroidorg can be properly strict about #FreeSoftware. A couple of our apps still have a couple #proprietary blobs that are requirements. F-Droid no longer includes any third party repos by default, that means our repo is no longer there by default. It is still easy and safe to add it! Read on for more info:
https://guardianproject.info/2024/02/24/the-future-of-our-fdroid-compatible-app-repository/
There are even more repos around. For example, the #IzzySoftRepo repo exists since 2016. While being a "simple binary repo", it has good security measures implemented – detecting even things the scanners at @fdroidorg miss (and vice versa). Its inclusion criteria slightly differ from those at #FDroid so you'll find apps there which are not available at F-Droid. High transparency and interesting additional details. And more than 1,100 #apps. Give it a try! Read more at https://apt.izzysoft.de/fdroid/index/info
@IzzyOnDroid @fdroidorg I think the #IzzySoftRepo is a good example of how a binary repo should be run: clear criteria for inclusion, good marking of Anti-Features, regular enforcement action, etc. Indeed @IzzyOnDroid caught the missing Anti-Features on the Guardian Project repo wth one of his scans. Thanks again!
Thanks @eighthave! IMHO by running an F-Droid repo (whether it builds from source or just offers binaries) intended to be used by others, one accepts responsibility. So one should take the best possible measures to make it as safe and as transparent as possible. I try my best here, and I won't stop where I'm standing now – but hopefully improve it even more. 🤞 @fdroidorg