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:
- 1 user online
- 1 user / day
- 26 users / week
- 68 users / month
- 410 users / 6 months
- 1 subscriber
- 677 Posts
- 11.2K Comments
- Modlog
obsidian.md using the Self-hosted Livesync plugin
Have you had any issues with the self-hosted livesync plugin? I currently use the “remotely save” plugin and sync to a nextcloud instance, but I thought about trying the livesync plugin instead. I just wasn’t sure if it was worth spinning up a couchdb instance just for that.
I’ve been using it for about a year, and it’s definitely gotten a lot better in that time. It can be a little finicky to get everything configured for the first time for a vault. You only have to do it on the first device though, then you can copy a setup URI to each subsequent device. One caveat is that if you want it to work on mobile, then you’ve got to have it configured with https and not with a locally-signed cert. I have it proxied through Cloudflare with a domain I use for homelab stuff.
The biggest difference is that remotely save doesn’t have any kind of conflict resolution. It just overwrites the remote file as long as the local one was modified more recently. Livesync keeps separate versions of a file almost like a git repo, tracking the changes. It almost always automatically merges conflicts, but if it can’t it’ll pop up asking you to choose which version to keep. I have a few vaults that I share with others and multiple people can work on the same file simultaneously with no issues at all. There’s end-to-end encryption built in so if you’re using it externally you don’t have to worry about your privacy. I write up my task list for the day on my computer in the morning, and being able to pull my phone up and check things off and have it reliably sync back to my desktop without overwrite issues works flawlessly. There’s iOS, Android and Windows devices all playing nicely.
Here’s a link to the docs for setting up your own server.
I’m gonna stick the docker compose and config files I used to spin mine up if you wanna use them (make sure to put them in the same directory):
docker-compose.yml
local.ini
Edit: Sorry for the huuuge reply, hope it’s not too much haha
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