Privacy Guides

21,683 readers

1 active

1 user 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:

We prefer posting about open-source software whenever possible.
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.
No soliciting engagement: Don't ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don't repost topics which have already been covered here.
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.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
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.
No misinformation: Extraordinary claims must be matched with evidence.
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.
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 3 years ago

moderators

jonah@lemmy.jonaharagon.net

Signal under fire for storing encryption keys in plaintext (stackdiary.com)

submitted 2 years ago by neme@lemm.ee to c/privacyguides@lemmy.one

49 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] jicevif@futurology.today 2 points 2 years ago (3 children)

Always knew this project was a honeypot because of their insistence on needing a phone number. Welp. Let's see how they damage control yet again.

permalink

fedilink

source

hideshow 3 child comments

[–] actionjbone@sh.itjust.works 8 points 2 years ago

It originally needed a phone number because it was originally a phone texting app.

permalink

fedilink

source

parent

[–] best_username_ever@sh.itjust.works 4 points 2 years ago

You have the source. Read it if you want.

permalink

fedilink

source

parent

[–] sunzu@kbin.run 2 points 2 years ago

I don't think it is a honeypot per se can you supply evidence.

But yes, their "leadership" does appear to ensure that this thing never goes mainstream with their focus on "journalists" or whatever. Exec does not seem to understand the core use base at best.

permalink

fedilink

source

parent