@growse @guardianproject @signalapp @fdroidorg That would be nice, but sadly, no. That APK contains proprietary libraries from Google and maybe others.
@pixelcode @kkarhan I have followed their #ReproducibleBuilds over the years, they never actually reproduce the whole thing from source, just the easy parts. Last I checked, all their native code is just pulled in as binaries when using their reproducer setup. Plus, they can't reproduce the proprietary Google libraries https://github.com/signalapp/Signal-Android/blob/556bcda58ae65abbba75bf899a43666ba6d9d427/app/build.gradle.kts#L533
@pixelcode @kkarhan #OpenSourceInitiative has gone to great lengths to try to standardize the definition of "open source", including filing trademarks. Including proprietary libs fails their definition of #OpenSource For this reason, many are now using the term #SourceAvailable for things like Signal.
@signalapp As a supporter of #Signal, it is important to point out a key detail: Signal's own code is #OpenSource, but Signal uses multiple #proprietary libraries from #Google. Those cannot be scrutinized since the source code is not open. We believe Signal should offer an actual open source version, and are ready to help. This exists already in the fork https://fosstodon.org/@MollyIM Also, apps like #Element #Threema #Wire are #FOSS, and have #ReproducibleBuilds on @fdroidorg #FDroid
A Mobile track at FOSSY was just added to the schedule! 🎉
If you have a talk about FOSS on mobile devices that you've always wanted to give, now is your chance 😁
The submission thing is open until April 28:
https://2025.fossy.us/call-for-proposals/
@nemobis thanks for the info, I still wonder why they deleted the comments on the GitHub thread?