OpenAPK here seems to be linking directly to official binary downloads, whereas F-Droid insists on building the APKs for the apps.
OpenAPK here seems to be linking directly to official binary downloads, whereas F-Droid insists on building the APKs for the apps.
You could say that OpenAPK blindly redistributes whatever APK upstream is peddling whereas F-Droid builds from source. I see the merits of both systems but prefer reproducible builds so that we can have the best of both worlds
All of that said, not particularly speaking for OpenAPK here, given their motives seems rather unclear to me. If I am to be charitable, I guess they're just trying to provide a different platform than f-droid for discoverability, but for whatever reason they seem to be marketing the distribution-side of things more which is just odd to me, but alas.
There is a lot of extra work done behind the scenes to "thrive in spite of it". Windows Defender (built into Windows after XP) has to periodically download updated virus definitions and always scans programs for potential malware, and still can't catch them all.
F-Droid, however, allow the developer's binary to be reproduced if they have tested that the APK is reproducible when replacing the APK's signature with the original APK.
Reproducible builds would allow distributing Shizuku in F-Droid, that’s correct. (If Shizuku banned third party builds by the means of code license, it would not be FOSS and thus wouldn’t be eligible for inclusion in F-Droid altogether.)
With fdroid i trust 1 party, by downloading random binaries I have to trust hundreds.
https://github.com/signalapp/Signal-Android/blob/main/reprod...
Why? The official one can be backdoored and with a gag order you would never hear about it
Not trusting signal's build and then turning around and trusting some third party build seems strange. The official build probably has more eyes on it, and signal has more reputation to lose.
I'd start here if I were you: https://protonvpn.com/support/wireguard-configurations
This is the best of both worlds because the distributor (F-Droid) verifies that the published source matches the binary but does not possess the private key to sign the APK. This means the distributor cannot push a backdoored binary blob at some later date.
F-Droid guarantees that the binaries it distributes always match the corresponding source, which adds another layer of security.
To ensure transparency, it also provides an archive of the source code used to compile different versions.
I am impressed to see the F-Droid maintainers sticking to their principles.