Re:Meta Shuts Down End-to-End Encryption for Instagram Messa...
by lrvick on Saturday May 09, 2026 @03:44AM
(#48072841)
While I agree reproducible builds are a huge part of the answer, if you get your builds from Google Play or the App Store you have no idea if anyone has reproduced the particular build that was served to your device.
A solution to this would be independent reproducible builds like F-Droid does, but Moxie rejected this citing it would cause them to lose control of the platform and install metrics Google and Apple provide. Always thought that was a weird position for a privacy tool.
Re:Meta Shuts Down End-to-End Encryption for Instagram Messa...
by Moldoteck on Saturday May 09, 2026 @04:31AM
(#48073155)
there's no guarantee, but if the build is mass served - it's at least possible to find out. For closed source apps you may even not know
Re:Meta Shuts Down End-to-End Encryption for Instagram Messa...
by Melatonic on Saturday May 09, 2026 @05:27AM
(#48073465)
Personally I would be more concerned about a vulnerability or backdoor in Intel SGX
Re:Meta Shuts Down End-to-End Encryption for Instagram Messa...
by charcircuit on Saturday May 09, 2026 @05:51AM
(#48073593)
So what? The centralized owner owns the code repo too, so such a restriction doesn't stop anything.
Even if Instagram was open source, Meta could remove the E2E chat feature.
Re:Meta Shuts Down End-to-End Encryption for Instagram Messa...
by lrvick on Saturday May 09, 2026 @08:00AM
(#48074263)
If it was open source people could fork.
Re:Meta Shuts Down End-to-End Encryption for Instagram Messa...
by charcircuit on Saturday May 09, 2026 @10:08PM
(#48080329)
But a fork wouldn't be installed on billions of people's devices.
https://github.com/signalapp/Signal-Android/blob/main/reprod...