this post was submitted on 17 Jul 2023
1 points (100.0% liked)

Privacy Guides

16796 readers
1 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS
 

A lot of privacy guides suggest avoiding Telegram. I understand that in its default mode there's no E2EE (and no E2EE for groups at all). If people I know don't wanttko use Signal, isn't Telegram the lesser evil given it's nicer privacy policy (than other popular ones)?

Say I use the FOSS version of it.

top 11 comments
sorted by: hot top controversial new old
[–] dngray@lemmy.one 1 points 1 year ago* (last edited 1 year ago)

Probably another point is that the encryption for Matrix/Element has undergone multiple audits, one in 2016 and another one of their newer rust library. Whereas telegram just has not. There was this also a not too long ago. MTProto is also used nowhere else, whereas a lot of encryption has been influenced by the Double Ratchet which is well understood.

The other thing worth noting is that Matrix is the foundation for other products which many governments use for secure communications.

[–] hiajen@feddit.de 1 points 1 year ago

Despite you using the foss client of telegram there is no source for the server, signal has published it's code.

[–] southsamurai@sh.itjust.works 0 points 1 year ago (1 children)

Depends on your goals.

For casual shit like sending files to yourself, bullshiting with memes, or stuff like that, the unknown factor of telegram doesn't matter.

But it is an unknown. We don't know what their server code looks like. So you can't trust that it isn't doing things other than what it is supposed to.

It's a matter of preferences tbh.

[–] ghariksforge@lemmy.world 1 points 1 year ago (1 children)

We don't know what anyones server code looks like. The code that is published may not be the one they are actually running.

In fact Signal stopped publishing server side code a few years back, and only resumed after the community got angry: https://www.androidpolice.com/2021/04/06/it-looks-like-signal-isnt-as-open-source-as-you-thought-it-was-anymore/

[–] woobalooba@lemmy.one 0 points 1 year ago (1 children)

I don't think that they published it as a response to the angry users. We wern't that loud and signal had a reason to do so. That was when they worked on the cryptocurrency and the spam protection. In signals case it dosn't matter much if the server is compromised since the important part happens on the client side. The server can only forward encrypted salad or not deliver a message. Or log the meta data of the messages. E2e will always be there, despite the server being compromised.

[–] ghariksforge@lemmy.world 1 points 1 year ago

What bothered me was that Signal fanbase was trashing Telegram for not publishing the server source, while Signal was doing this.

[–] zorbse@lemmy.blahaj.zone 0 points 1 year ago (1 children)

Telegram straight up lies about sharing data with governments: https://restoreprivacy.com/telegram-sharing-user-data/

[–] win98se@programming.dev 0 points 1 year ago (1 children)

This. Our fucking government can instruct Telegram to ban any channel or user they don't like.

[–] valpackett@lemmy.blahaj.zone 1 points 1 year ago (1 children)

Banning channels is not the same as sharing private data

[–] win98se@programming.dev 0 points 1 year ago (1 children)

If not the latter, how the former? Messages is and should be private data as well.

[–] valpackett@lemmy.blahaj.zone 1 points 1 year ago

??? Channels are literally public by definition and viewable even without an account. That's the whole point of channels. They're more like blogs than messages.