Privacy Guides - Lemmy.one
lemmy.one
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. Check out our website at privacyguides.org [https://www.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 [https://github.com/privacyguides/privacyguides.org], and your help would be appreciated! — This community is the “official” Privacy Guides community on Lemmy, which can be verified here [https://www.reddit.com/r/PrivacyGuides/comments/13x7oe3/who_wants_to_try_out_lemmy_privacyguideslemmyone/]. 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 [http://privacyguides.org]. If you want to be listed, make a suggestion on our forum first [https://discuss.privacyguides.net/c/site-development/suggestions/6]. 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 [https://www.privacyguides.org/en/tools/]. 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.

They aren’t the most controversy-free group, but there’s a lot of value in their existence, especially for people newly working toward privacy. It’s also nice to see more groups acknowledging Lemmy

    • Captain Beyond@linkage.ds8.zone
      31·
      1 year ago

      I don’t have anything to say about the drama with PrivacyTools et al. but as a free software supporter I can say confidently that Privacy Guides (along with allied projects such as GrapheneOS, PrivSec, and Accrescent) represent a sect of the privacy community that is at best ambivalent, and at worst actively hostile, towards the free software movement. Their usage/endorsement of proprietary tools can only be seen as hypocrisy if you hold that privacy and freedom are closely linked; the free software community (which significantly overlaps with the privacy community) of course does, and this was common knowledge once upon a time (as the reddit /r/privacy wiki states) but Privacy Guides et al. is more interested in security even at the expense of freedom, going as far as to spread FUD about free software projects such as F-Droid and Linux-libre and about the free software movement in general.

      I’ve written before on reddit about why I feel praising the security of proprietary software is misguided; I’ll reproduce that post below:

      Privacy guides is not a free software advocacy organization and in fact is not a friend of the free software movement at all, which is apparent when you read about how they praise proprietary operating systems for their security while neglecting to mention the fact that, for proprietary software, “security” often means security against the user.

      I’ve written before about why F-Droid is important here. Their inclusion policy ensures that what I get from them meets the free software definition and thus I can exercise the four freedoms (to run, share, modify, and share modified versions) with it. There is no such guarantee if you get prebuilt packages from the developer, because unless the build is reproducible there is no way to verify for yourself that the source code is complete and corresponds to the binary, and even if it does it may include proprietary libraries. F-Droid publishes the complete source code along with build metadata and instructions to allow users to exercise the four freedoms with every app. Personally I think getting updates a day or two late is an acceptable tradeoff. Free software is even more important now.

      Desktop GNU/Linux distributions follow the same model and have an important role in being a third-party curator and distributor of packages.

      As others have said, free software is not inherently more secure (or bug-free, etc), but it was never promised to be. Free software only guarantees its users the four freedoms. Privacy guides is a privacy advocacy organization, not a software freedom advocacy organization. They are not the same thing and the fact that people conflate these two movements/communities causes a lot of problems here. Every time someone comes to this subreddit and insists you don’t really need software freedom, I think they got that notion from privacy guides or some other privacy community.

      As well as a follow up comment:

      Sure. I didn’t mean to imply security was bad or undesirable. You need security. My point is that, if the operating system is proprietary, the developer/vendor holds the keys and secures the OS against its own user. DRM is the obvious use case for this, but we can see OS vendors abusing this even more overtly - remember that fiasco from last year where Microsoft forced users to open certain links in Edge, and blocked users’ attempts at forcing Windows to respect their preferred browser setting.

      There was a genuine concern, back when UEFI Secure Boot was introduced, that Microsoft would use its power to prevent vendors from selling unlocked PC’s. Fortunately Microsoft decided not to do this, but (from what I know) did do so with ARM devices. We’ve since come to accept that with non-desktop “smart” devices that this is the norm. That frightens me. It frightens me even more when privacy organizations uncritically praise user-hostile security features and people in “FOSS” communities parrot the advice and opinions of organizations that don’t consider software freedom and user control of their hardware as a factor.

      (Keep in mind this is from the perspective of a free software supporter, not a security zealot)