I agree with the concern of the server code being out-of-date. I know the consensus seems to be that it’s E2E so you “don’t need to trust the server”, but stil

I agree with the concern of the server code being out-of-date. I know the consensus seems to be that it’s E2E so you “don’t need to trust the server”, but still as a principle it seems strange to be so out of date. Perhaps more importantly, I believe Signal doesn’t have reproducible builds for their iOS client app[0] * whereas, interestingly, it seems Telegram does [1]. For me, the combination of out of date server code and non-reproducible iOS client binaries mean that for all my support of Signal (I donated during their recent outage) the benefits of this being a fully “open source” message solution are somewhat devalued. Not to be too down on them though, I don’t touch WhatsApp with a barge pole, so they’re still my favoured messaging platform. * Not necessarily entirely Signal’s fault because, of course, Apple doesn’t make this easy. [0]: https://github.com/signalapp/Signal-iOS/issues/641 https://github.com/signalapp/Signal-iOS/issues/641 [1]: https://core.telegram.org/reproducible-builds https://core.telegram.org/reproducible-builds