Blaze (he/him)@piefed.zip to Privacy@programming.devEnglish · 7 days agoThere isn’t really another choice: Signal chief explains why the encrypted messenger relies on AWSwww.theverge.comexternal-linkmessage-square46linkfedilinkarrow-up185arrow-down17 cross-posted to: privacy@lemmy.mltechnology@lemmy.worldpulse_of_truth@infosec.pubtechnology@lemmy.zip
arrow-up178arrow-down1external-linkThere isn’t really another choice: Signal chief explains why the encrypted messenger relies on AWSwww.theverge.comBlaze (he/him)@piefed.zip to Privacy@programming.devEnglish · 7 days agomessage-square46linkfedilink cross-posted to: privacy@lemmy.mltechnology@lemmy.worldpulse_of_truth@infosec.pubtechnology@lemmy.zip
minus-squarecoherent_domain@infosec.publinkfedilinkEnglisharrow-up13arrow-down1·edit-27 days agoMoxie Marlinspike mentioned why they decided to build a centrualized service: basically, for rapid update to security protocols and less technical burden for backward compatibility. https://signal.org/blog/the-ecosystem-is-moving/ Indeed there is decentralized E2EE messenger: https://getsession.org/ and it is quite popular (not close to the popularity of signal, though).
Moxie Marlinspike mentioned why they decided to build a centrualized service: basically, for rapid update to security protocols and less technical burden for backward compatibility.
https://signal.org/blog/the-ecosystem-is-moving/
Indeed there is decentralized E2EE messenger: https://getsession.org/ and it is quite popular (not close to the popularity of signal, though).