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
Just as it inconveniences you to have to decrypt to search, it would similarly slow down anyone malicious who gains access to your machine.
Am in favour of allowing users to decide which features are best for their needs, but this seems like it would be easy to forget to reinstitute local encryption after a search, so can also understand why developers prevent storing in plaintext.
You can't search encrypted emails, period. The way I see the benefit of encrypting emails is to not have them compromised in the cloud servers. But on my own machine, if someone gains access to the files, then it's all ogre. Maybe that's just me IDK.
Point is, one can decrypt each email individually. That slows an malicious attacker rummaging in your device from finding what they are after as much as it does you.
You wouldn't be alone in wanting this feature, but for those who need rather than prefer to encrypt, the option to store locally in plaintext is a major risk. On balance it seems better for developers to pay heed to that than to our preferences.
For the rest of us, we can download the emails we wish to refer to with ease, or we can create aides memoire to make it easy to locate specific emails later.