@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 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 github.com/signalapp/Signal-An

and rebuild everything from source.

@pixelcode @kkarhan has gone to great lengths to try to standardize the definition of "open source", including filing trademarks. Including proprietary libs fails their definition of For this reason, many are now using the term for things like Signal.

@signalapp As a supporter of , it is important to point out a key detail: Signal's own code is , but Signal uses multiple libraries from . 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 fosstodon.org/@MollyIM Also, apps like are , and have on @fdroidorg

As you plan your week ahead, don't forget to get your #FOSSY talk proposal in by Monday, April 28 (anywhere on Earth)! You can do it at https://2025.fossy.us/call-for-proposals/ . We are a small team putting this big event together and greatly appreciate your help in making sure everyone in your #freesoftware and #opensource circles knows about the opportunity and deadline! #portland

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:
2025.fossy.us/call-for-proposa

#linuxmobile #fossy2025 #pdx

Show thread

@nemobis thanks for the info, I still wonder why they deleted the comments on the GitHub thread?

Show more
image/svg+xml Librem Chat image/svg+xml