this post was submitted on 09 Jan 2025
107 points (99.1% liked)

Privacy

39507 readers
758 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] yogthos@lemmy.ml 20 points 5 months ago (94 children)

I don't really have any special hate for Telegram myself, and I never saw it as a secure communication platform. I have more problem with Signal because people treat it like it's paragon of privacy and security.

[–] Imnebuddy@lemmy.ml 2 points 5 months ago (5 children)

Many Signal alternatives also have security issues of their own, often making them less secure than Signal. This includes Matrix and XMPP. In the blog post regarding XMPP+OMEMO, the author replies to a question about which would be better than Signal, Matrix, and XMPP with this suggestion:

Anyone who cares about metadata resistance should look at Cwtch, Ricochet, or any other Tor-based solution. Not a mobile app. Not XMPP. Not Matrix.

In regards to Ricochet, not having a mobile app version makes it difficult to recommend to less tech savvy people.

[–] Aria@lemmygrad.ml 5 points 5 months ago (2 children)

Matrix, even if it was a siv, would be better than Signal, because it doesn't know your phone and passport numbers.

[–] Imnebuddy@lemmy.ml 1 points 5 months ago

I'm not denying that major flaw of Signal, in which part, yes exposing your phone number tied to your Signal account basically negates Signal's security, as well as Signal's centralized server being proprietary. Nevertheless, when using Matrix, you need to ensure you and everyone you communicate with uses a client that isn't still using the deprecated libolm cryptography backend (and that it uses vodozemac).

load more comments (1 replies)
load more comments (3 replies)
load more comments (91 replies)