|
|
|
|
|
by rakoo
1922 days ago
|
|
I have never used Telegram but not once have I ever read anyone being displeased with the experience; it's always about how it is the pinnacle of messengers. I'm a bit jealous about that because I want to experience it but I don't want to be tied to an app that doesn't do privacy by default. Privacy is definitely not binary, but to me it is a bit like using Libre software. You can't realistically expect to live on the 21st century internet with the entirety of services and viewpoints it offers and only use Libre software. At this point you have to either follow your values and stick to a very small part of it that is guaranteed to work on your browser rejecting non-Free javascript, or you can make concessions and accept a bit of proprietary bits here and there. But you can still decide to be Libre-first and accept non-Libre from there, on a bit-by-bit basis. That is what I and others are talking about with e2ee first: Instead of asking "what is worth being hidden and being made public", I feel the more just mindset should be "supposing everything is private by default, what can I disclose and to whom". Your threat assumption regarding your conversations is a good example: of course every software has bugs and all your messages could be read by Telegram. But you're behaving as if Telegram might read it one day, when I believe you should believe as if Telegram is reading it every day. The danger is not that Telegram can make a soap opera out of your drama but that the whole world can. As you say you take care what you write about and that is a good thing to do. So, following up: if you don't want anyone to be able to read it, then let's go to the end of this and make sure no one physically can read it, by default. Instead of asking what kind of conversations require e2e, let's ask what kind of conversation doesn't require e2e |
|
Something like Matrix are likely the best you can go (a federated network where bad actors are likely to get called out, I have high expectations for its future), but apart from this I consider e2e a red herring* as e2e would also need to include source code, compilation, installation, and platform. it is not a magic incantation that fixes privacy (not to talk about metadata)
we find reasonable to have not e2e emails, not e2e file sharing, not e2e phone calls. personally I care more about the long term commitment telegram has publically and repeatedly made (and the my assumption that they do not expect to be able to come out unscathed from obvious leaks)
I understand that others might want more, no problem with that, but there is so much more than just e2e encryption.
*telegram should still offer secret groups