Privacy Guides
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:
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:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
view the rest of the comments
It isn't for anyone using any client unless they optionally decide to provide it.
Indeed: https://joinmatrix.org/servers/ and that's not even getting started on the private ones or unlisted ones.
100% Discord has no privacy no encryption, the company sees absolutely everything.
That doesn't necessarily impact privacy, and we know exactly what it does in the background based on their privacy policy, which in itself is quite ambiguous in parts. They're quite happy there to admit they will tie identities together if you use social media logins and features like that.
I would say be careful here, because something is open source doesn't necessarily mean anyone cares about what the code is actually doing. In the case of Matrix it is a very active project with a lot of community engagement and a well thought out specification so that everyone can "get up to speed". That is extremely important. Nobody is going to sift through a tarball of source code "it's open source", if the development is not. It's also totally possible for a patched version to be running in production that doesn't reflect the source code.
That is why it's very important not to confuse FOSS with privacy.
You can say how FOSS programs don't equate to privacy because people may not catch things or be watching but with closed source options nobody gets to audit the code at all outside the project. How is that better for privacy ? FOSS at least gives us a chance at privacy.
If the audits are public and they are actually funded with proper scope that may very well be better than some very small project nobody can be bothered looking at. I'm not saying having source is a bad thing, quite the opposite. Privacy is generally gained through security controls, and just because something is open source doesn't mean it is secure, likewise if something is closed source that doesn't necessarily mean it is insecure as this post describes.
My issue with closed source is we don't know if it is insecure or secure because nobody can find out. It's a pandora's box of privacy and security. It may be the most private and secure code known to man or it may be sending anything and everything about you somewhere but we'll never really know. As for public audits who picks who gets to audit the code ? The company who made it ? You can do as you please but I refuse to trust closed source code. I'm not saying all open source code is good but at least we can find out if it's good or not through independant means rather than trusting people that the company who made it picks to tell us.
@PublicLewdness @dngray
The concept of security by obscurity in general is just absurd. It's maddening that this is the preferred option in Enterprise.
@PublicLewdness @dngray
security by obscurity... this is an absurd concept