@kenoh tfw I notice the username and realize this got federated over to lemmy. This tech is pretty nice!
But yeah, absolutely. When it comes to important data (and my logseq graphs are important), you do backups and you verify the backups. Logseq sync is unreliable between platforms with filesystems that ignore case and don’t, for example I’ve stumbled on https://github.com/logseq/logseq/issues/10993 recently, and hey, it was reported back in February. Checking it now I see the github bot already labelled it as stale and I suppose it will be closed without action soon.
I use git as a backup for logseq sync, but given how it tries to overwrite the config, it’s not a fully reliable option either. Sometimes it syncs pages from graph A into graph B.
PKM is a hot space with new tool coming every week. I don’t think Obsidian is a perfect tool by any means, after all I used it for more than a year before jumping ship to logseq. But it seems that if I use it less an advanced markdown editor and more like an outliner (for which it has a few plugins) that will fit my mental model and help to find things.
/cc @logseq
@twistypencil @logseq I’ve a mix of windows, mac and iphone. Git is regularly screwed up on the windows box.