Signal Server code on GitHub is up to date again
A lot of these comments are just manifestations of the kneejerk HN &quot;crypto bad&quot; reflex. Here&#x27;s the deal:<p>- Whether or not Signal&#x27;s server is open source has nothing to do with security. Signal&#x27;s security rests on the user&#x27;s knowledge that the open source client is encrypting messages end to end. With that knowledge, the server code could be anything, and Signal inc. would still not be able to read your messages. In fact, having the server code open source adds absolutely nothing to this security model, because no matter how open source and secure the server code might be, Signal inc. could still be logging messages upstream of it. The security rests only upon the open source client code. The server is completely orthogonal to security.<p>- Signal&#x27;s decision to keep early development of the MobileCoin feature set private was valid. Signal is not your weekend node.js module with two stars on Github. When changes get made to the repo, they will be noticed. This might mess up their marketing plan, especially if they weren&#x27;t even sure whether they were going to end up going live with the feature. Signal is playing in the big leagues, competing with messengers which have billions of dollars in marketing budget, will never ever be even the smallest amount open source, and are selling all your messages to the highest bidder. They can&#x27;t afford to handicap themselves just to keep some guys on Hacker News happy.<p>- Signal&#x27;s decision to keep development to the (private) master branch, instead of splitting the MobileCoin integration into a long-running feature branch is a valid choice. It&#x27;s a lot of work to keep a feature branch up to date over years, and to split every feature up into the public and non-public components which then get committed to separate branches. This would greatly affect their architecture and slow down shipping for no benefit, given that the open sourceness of the server is orthogonal to security.