[Valodim]

> a) people that care about chat encryption and would be willing to change, already did, to Telegram and/or Signal.

It continues to baffle me that the "telegram is encrypted" spin is still widely believed, even on a forum like this. Telegram is for 99.9% of intents and purposes not encrypted.

[Anonyneko]

And even when you do enable encryption of the chat contents, the unencrypted metadata is often enough for security services to make a suspect out of you. Granted, this is mostly a concern for Russian and Belarusian users.

[general1465]

People wants simple communication app. Telegram is exceptional with that. Matrix may be encrypted, but everything else is just bad.

[dizhn]

What is encrypted and how is public information. If it doesn't fit your use case don't use it. There is no "spin".

People were spreading this kind of FUD until last week when all of a sudden people started claiming it was self evident that "of course Meta can read your WhatsApp messages". I don't get this kind of weird fixation with a product. I suspect it's two things. Perceived Russian origin and that one guy dared write a crypto library rather than using their own. I agree with the latter. The prior is not even true the way people understand it to be. I for one like the stickers. Shoot me :)

We even give companies like Google which we know for a fact is looking at all of our data a free pass with the super western "privacy policy" cop out while judging other tools with a different set of rules.

Another darling is Signal who refused to stop collecting phone numbers until recently even though they never needed it, does not allow open source or other clients to use their servers (and won't release the actual server code) and frankly does not work half as well as Telegram in terms of UX.

All of this is really confusing for me.

[palata]

> All of this is really confusing for me.

Yep, I can see that.

The problem with Telegram is that it is not an E2EE messaging platform, period. It is a non-E2EE platform that has an option to encrypt 1:1 messages with a criticised algorithm. Whoever uses Telegram does it for all the nice features that are not E2EE.

> all of a sudden people started claiming it was self evident that "of course Meta can read your WhatsApp messages".

Because some people say stuff like this doesn't make it right. WhatsApp messages are E2EE encrypted, unlike Telegram. There are other things to criticise with WhatsApp, but not that.

> Signal who refused to stop collecting phone numbers until recently even though they never needed it

As you said, you're confused. Signal needed the phone numbers for convenience, so that you could reach your friends. Exactly the same reason as WhatsApp. Could they have done without it? Yes, but maybe Signal would not be as popular. That's a valid tradeoff, and Signal never lied about it. Also having to share your phone number with Signal is still better than any of the other popular platforms. Anything that is "more private" than Signal hasn't managed to get on the map.

[dizhn]

> Because some people say stuff like this doesn't make it right. WhatsApp messages are E2EE encrypted, unlike Telegram. There are other things to criticise with WhatsApp, but not that.

Is this verifiable fact or Meta's claim? As far as I know neither the server nor the client are open source.

[palata]

> As far as I know neither the server nor the client are open source.

That is correct. I have a few things to add:

- Meta employees (and there are many of them) have access to the sources. So if Meta was downright lying about it, chances are that someone would leak it.

- Thanks to the Digital Markets Act, we see that the encryption protocol exposed by Meta for interoperability is based on Signal. If Meta wanted to lie, they would have to either use a different protocol internally (but again, we know that the Signal authors contributed to integrate the Signal protocol in 2016, and a Meta employee could relatively easily see if WhatsApp had removed Signal and re-added it just for interop recently) or use the Signal protocol but have the app send the content of the messages to the Meta servers after decryption (which would be fairly easy to see by a Meta employee).

- People who don't want to trust WhatsApp should use Signal. Moving to Telegram because of a lack of trust would be weird, as Telegram is most definitely not E2E encrypted.

In other words, the WhatsApp situation is not perfect, but telling people to move to Telegram because "it's safer" is actually dangerous. Telegram is strictly less private, period. Signal is strictly more private.

I am not saying people shouldn't use Telegram. As far as I'm concerned, people can do whatever they want (and I hear that the Telegram UX superior). What I do not tolerate is wrong statements about the privacy situation. Telegram is strictly less private, Signal is strictly more private.

[wizzwizz4]

> There are other things to criticise with WhatsApp, but not that.

Nitpick: Facebook can obviously grant themselves the ability to read your WhatsApp messages, by pushing out a new client. What they can't do is covertly read your WhatsApp messages: WhatsApp is well-studied enough that people would notice the malicious client update within a year.

Google or Apple can also grant themselves the ability to read your WhatsApp messages. Someone grabbing your phone while it's unlocked has the same ability.

[drnick1]

Absolutely, and this is why one of the only viable options for truly private communication is Signal on a degoogled ROM like Graphene. Matrix also works, but you need your server.

[palata]

Nitpick indeed, but correct :-)

[exo762]

> What is encrypted and how is public information. If it doesn't fit your use case don't use it. There is no "spin".

Correct way of speaking about Telegram is - nothing* is encrypted. (encrypted chats are not more than 0.5% of all chats). That would be a "no spin" take.

> one guy dared write a crypto library rather than using their own

Red herring. This library is NOT used for more than 99.95% of chats on Telegram. It is applied only to "secret chat", which is a torture device with horrible UX. I guess that horrible UX is the result of choice of using custom crypto library instead of going with something capable of working when addressee is not online.

> Another darling is Signal who refused to stop collecting phone numbers until recently even though they never needed it, does not allow open source or other clients to use their servers (and won't release the actual server code) and frankly does not work half as well as Telegram in terms of UX.

Phone numbers are still used as anti-spam measure. You are free to get a burner, register an account and throw away the SIM card.

> does not allow open source

Signal client is open source.

> frankly does not work half as well as Telegram in terms of UX.

It works well where it does matter. Vide Telegram's "secret chats".

> All of this is really confusing for me.

You are clearly misinformed. That explains the confusion.

[dizhn]

- Messages by default are encrypted in transit. Client to server. Yes Telegram does have access to those messages. (I don't believe we had any e2e encrypted chat service before the likes of signal, matrix etc. Whatsapp added it after Telegram too if my memory is right.)

- The library IS used for all encryption including the above client to server encryption. As far as I can tell from casual use the other end does not need to be online for secret chats per se. There's a key exchange with picture verification that requires the party on the other end to accept the chat request.

- The phone bits in your and the other commenters response sound a little bit handwavy to me.

- Telegram client(s) are also open source. The comment was about the server and interoperability with other clients.

After all it doesn't seem to me that I am more misinformed than yourself.

[Valodim]

> - Messages by default are encrypted in transit. Client to server. Yes Telegram does have access to those messages.

No connection over the internet is not transport encrypted these days, but that is not what this conversation is about. It's about whether messages are encrypted so the server cannot read them. And Telegram is commonly mistaken to have this property, including OP I was responding to.

If you go around telling people that telegram is "encrypted", please stop. You are spreading disinformation.

[exo762]

> Messages by default are encrypted in transit. Client to server.

By this metric Facebook and Google are encrypted, because TLS. Sorry, Telegram's messaging is an attempt to mislead users, plain and simple.

> The library IS used for all encryption.

They could chose to use TLS for for almost all chats, and instead they've "invented" MTProto. Why go with MTProto?

> As far as I can tell from casual use the other end does not need to be online per se.

You are wrong. Phone on other side has to accept "secret chat request" (no user interaction is needed). Until its accepted, initiator's app interface is blocked with a spinning circle. And to add insult to injury, one can't initiate secret chat from desktop client.

> Telegram client(s) are also open source.

Yes, it is very refreshing to be able to verify that they can read all of my messages. /s

> The comment was about the server and interoperability with other clients.

Signal leadership explicitly stated that they care about secure comms and don't care about ecosystem around the chat. You can create your own client, you can't market it as Signal because that might "endanger lives".

> - The phone bits in your and the other commenters response sound a little bit handwavy to me.

I issue you a formal apology on behalf of HN hive mind. /s

On serious note - palata's point is right, but a bit outdated. Functionality is still there, but it became opt-in. New users have phone number automatically hidden and phone number is collected only as an anti-spam feature.

I'll repeat my point again. Telegram is a honey pot of messengers and nobody should use it.