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
Thanks so much for the detailed response! I didn't realize livesync handled conflicts better, that's almost enough by itself to make the switch.
I think originally I was mostly hesitant to try it because I didn't want to expose a public couchdb, but it's actually not that big of a deal now that I think about it, especially if it's using end to end encryption.
Do you just share the entire vault? I'm assuming each person you share with would just end up using the same credentials? I tried sharing a vault with my partner before using remotely-save+nextcloud and it was kind of clunky, we ended up just using a shared folder and let nextcloud desktop app sync it instead. It doesn't help for mobile though.
Thanks for sharing your config too, I'll probably try setting it up with a test vault this week and see if I run into any issues with it
So there's the one set of couchdb login details, but that's not used for encryption. There's a separate encryption passphrase per vault, so you can store as many vaults as you like without worrying about other people using the database reading your files. My partner and I have a vault that we share (with shared passphrase), as well as each having our own vaults. This works best for us, but there's also another tool by the creator to sync folders between vaults: https://github.com/vrtmrz/livesync-classroom