Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by ring3711 on Tuesday January 12, 2021 @01:34AM
(#25743184)
About XMPP, it's a protocol. So it's possible for there to be a client with e2e by default right? And the problem is there is no reasonable client like that right now, right?
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by pmlnr on Monday January 11, 2021 @03:56PM
(#25736741)
> it was added way too late in the game.
That is not a thing with XMPP. The very essence of it is adding things in, and OMEMO is quite good.
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by snvzz on Monday January 11, 2021 @04:02PM
(#25736892)
I'm well aware of how XMPP works as I've been using it from the start.
It is with this knowledge that I cannot recommend XMPP.
e2ee should be at the core. Not as an entirely optional extension added decades after.
As I already stated, because I want the non-technical inclined to have privacy, I can only support options where e2ee is the default.
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by kitkat_new on Monday January 11, 2021 @04:20PM
(#25737244)
try having verified e2ee conversations with XMPP - good luck.
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by snvzz on Monday January 11, 2021 @04:30PM
(#25737445)
I've been having them for over a decade.
The "only" problem is that it isn't easy, and thus most people do not use them at all.
Therefore, I cannot recommend XMPP.
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by pmlnr on Monday January 11, 2021 @04:28PM
(#25737418)
Doing it actively. Try Conversations.
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by kitkat_new on Monday January 11, 2021 @04:46PM
(#25737741)
how many contacts with how many devices do you have there?
can't be many
As you haven't mentioned it: Supporting e2ee isn't enough. It must be the default, else the non-technically inclined will often end up not using e2ee.
>As much as I dislike to admit it, this leaves Matrix, and nothing else.
I'm in the same position. Never been a fan, but I have to support it, because that's really the only option, even if bloated.
I also tried running a server (synapse) with similar results. I have hopes for dendrite, but they've just been dampened by your report.
Fortunately, the client side is far more important, and there's some options there. Particularly, the web-based hydrogen is massively less resource-hungry than the web-based element, and nearly there featureset-wise.
>XMPP
I didn't even list that one, because e2ee is not the default, and support was added way too late in the protocol's trajectory.
>Signal
I mentioned it, but I'm actually not about to use it. The reason is that accounts are tied to phone lines. That's a non-starter for me.