4 ms·
> While it regularly publishes the code of its client apps, it hasn't updated the Github repository for its server for almost a year. Last commit was 5 days ag
by rvz 6y ago
> While it regularly publishes the code of its client apps, it hasn't updated the Github repository for its server for almost a year.
Last commit was 5 days ago: [0]
As for not playing nice with third-party clients, I can give you that point.
[0] https://github.com/signalapp/Signal-Server/commit/365ad3a4f821a9e2393c5a3e1522b2c03b9dfe40 https://github.com/signalapp/Signal-Server/commit/365ad3a4f8...
- RL_Quine 6y agoThis is a change that's very recent, perhaps even in response to this article in particular. https://web.archive.org/web/20210311053716/https://github.com/signalapp/Signal-Server https://web.archive.org/web/20210311053716/https://github.co... As of earlier this month, the repository was a year out of date.
- rvz 6y agoTrue, but the author of the blog post posted this '1 hour ago' (As of my comment) and maybe should have at least triple-checked the signal-server repository again rather than linking to a now outdated discussion thread on Signal-Android [0]. [0] https://github.com/signalapp/Signal-Android/issues/11101#issuecomment-798900367 https://github.com/signalapp/Signal-Android/issues/11101#iss...
- boomboomsubban 6y agoIf you read that thread, it's very possible the change happened in that hour. It seems to have been at some point today. I think a member of the team made it public ~15 minutes ago if I'm reading correctly.
- RL_Quine 6y agoGoogle Cache shows that as of Apr 6, 2021 00:16:05 GMT the source had not been updated since 2020, so it happened within the last 6 hours. https://i.imgur.com/r1Y0Wgz.png https://i.imgur.com/r1Y0Wgz.png http://webcache.googleusercontent.com/search?client=safari&rls=en&q=cache:https://github.com/signalapp/Signal-Server&ie=UTF-8&oe=UTF-8 http://webcache.googleusercontent.com/search?client=safari&r... Screenshot from twitter showing it not updated "2 hours ago", about 04:43 GMT. https://twitter.com/AnanasPizza2/status/1379474849974910980 https://twitter.com/AnanasPizza2/status/1379474849974910980
- RL_Quine 6y agoAuthor: Moxie Marlinspike <moxie+github@signal.org> AuthorDate: Thu Apr 2 12:45:24 2020 -0700 Commit: Moxie Marlinspike <moxie+github@signal.org> CommitDate: Wed Apr 22 12:32:53 2020 -0700 Support for advertising payment addresses on profile They stopped publishing the source just before this, presumably to hide their MobileCoin integration from the public.
- shaicoleman 6y agoYou can approximate the push date by looking for the first reference to the commit: https://github.com/search?q=365ad3a4f821a9e2393c5a3e1522b2c03b9dfe40&type=issues https://github.com/search?q=365ad3a4f821a9e2393c5a3e1522b2c0... https://github.com/signalapp/Signal-Android/issues/11101#issuecomment-814355899 https://github.com/signalapp/Signal-Android/issues/11101#iss... The article was published at 2021-04-06 17:50 UTC. The first reference on GitHub is at 2021-04-06 18:43 UTC, less than an hour afterwards.
- tptacek 6y agoIt's practically a principle of the Signal project to discourage third-party clients. Signal's security work is done, for obvious reasons, mostly clientside. If you have a diversity of clients, you're stuck with the lowest common denominator of mainstream clients. Without them, you can roll out any feature you want to.
- gruez 6y ago>If you have a diversity of clients, you're stuck with the lowest common denominator of mainstream clients. Without them, you can roll out any feature you want to. This only matters if you cared about backward-compatibility. Otherwise you can just push breaking protocol changes without regard for third party clients.
- ViViDboarder 6y agoAnd the users of those clients will say “Signal is always breaking” and switch to another platform.
- tptacek 6y agoThe scarier outcome is that they continue to use clients that lack security controls because the client continues to work well enough for them. Look how popular Telegram is.
- korethr 6y agoWhile I can understand not wanting a diversity of clients for the support headache that could rapidly become, I don't fully agree that a diversity of clients forces them to be stuck at a lowest common denominator. What prevents them from making the breaking changes necessary for security and features, and letting the devs of 3rd party clients successfully conform or not? I see it as something like mandating minimum version of TLS or cipher suite. The security flaws of TLS version <1.2 have been documented for some time now. I've had to tell customers more than once we are disallowing use of older insecure protocols to access my employer's services. Or am I misunderstanding you and actually happen to be agreeing?