alt Hacker NewsWhy would you use this over plain git in a CI pipeline? Presumably you need your knowledge graph versioned?
Replies
If you have automation that dumps things int your vault, that you built with their new CLI (which lets you create/tag docs etc. without running the full electron app), I guess this lets you sync those changes and propagate them to all of your obsidian sync clients also without having to open aforementioned full electron app.
To enjoy the native ease of use and security of Obsidian Sync as a human user on your devices; while being able to automate things on a server.
Quoting[1] kepano (CEO of Obsidian) - Why you might use Obsidian Sync headless:
- Automate remote backups
- Automate publishing a website
- Give agentic tools access to a vault without access to your full computer
- Sync a shared team vault to a server that feeds other tools
- Run scheduled automations e.g. aggregate daily notes into weekly summaries, auto-tag, etc
...all while having the speed, privacy, customizability, end-to-end encryption of Obsidian Sync.
Does the knowledge graph have a function other than to show off how big your vault is?
I just use Dropbox with dropsync on my phone. I never use the knowledge graph anyway
iOS makes it painful to use third-party sync protocols and servers, like syncthing can't run in the background, a git sync service can't run in the background, only iCloud gets to run in the background.... and whatever sync protocol the app itself has blessed so it can run immediately on opening the app.
As such, on iOS the native sync is the only one that works cleanly and seamlessly, and so you're incentivized to pay for it.
There was a little while, when dropbox was big, where it seemed like the future of computing would be "your data is in the cloud, and every app you use can share that data, and those two things are independent integrated through some common filesystem layer".
And then it ended up that no, your data's in a cloud-per-service, where your emails live in googles cloud, your documents in microsoft 365's cloud, your images in "adobe creative cloud"'s cloud, your photos in Apple's cloud, your passwords in 1Password's cloud, and your knowledgebase in Obsidian's cloud.
The dream of the filesystem API being able to expand to clouds, of being able to choose dropbox or google or apple as the owner of your data, and other applications seamlessly integrating with any of them, it died with apple making it impossible to offer any sort of generic filesystem API or even background sync.
And so, that's why you'd use obsidian sync over git, because you're cursed with using a phone.
Unless you're saying "why not pay for obsidian sync, but then sync it into a git repo in CI and commit there to see the diffs", not "why not use git as the underlying sync protocol", in which case ignore everything I wrote, you totally could do that.