←back to thread

It looks like Signal isn't as open source as you thought it was anymore

(www.androidpolice.com)
242 points raybb | 4 comments | 06 Apr 21 18:04 UTC | HN request time: 0s | source
Show context
rvz ◴[06 Apr 21 18:46 UTC] No.26715723[source]▶
> 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/365ad3a4f8...

replies(2): >>26715765 #>>26715780 #
tptacek ◴[06 Apr 21 18:50 UTC] No.26715780[source]▶
It'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.
replies(5): >>26715968 #>>26716208 #>>26717121 #>>26717165 #>>26717562 #
1. skzv ◴[06 Apr 21 20:44 UTC] No.26717165[source]▶
In comparison, Telegram offers APIs and libraries that allow you to create clients for any platform [0].

[0] https://core.telegram.org/tdlib

replies(2): >>26717365 #>>26718165 #
2. Andrew_nenakhov ◴[06 Apr 21 21:03 UTC] No.26717365[source]▶
You also need to give your developer keys to Telegram if you want your client to receive push notifications.
replies(1): >>26717491 #
3. Klonoar ◴[06 Apr 21 21:16 UTC] No.26717491[source]▶
Push notifications are pretty standard, though - this is an issue with the app store model, if anything.
4. tptacek ◴[06 Apr 21 22:28 UTC] No.26718165[source]▶
The last time I looked, Telegram didn't even have E2E-secure group messaging. It's easier to use and more pleasant to code to, but then, if that's all you're optimizing for, that's not a high bar to clear.