Logseq user here with an upvote.

I guess it didn't eat your notes yet: https://discuss.logseq.com/t/data-loss-happened-twice-i-cant...

I've had Google photos eat ~12 months worth of pictures, I don't really trust anyone to keep my data safe.

Logseq has been fine for me over several years, but it also makes it extremely easy to auto-commit to git.

Logseq's git auto-commit is a great insurance policy and should make recovery a breeze.

Ah, those appear to be entirely multi-device-sync problems. (I use logseq with git-autocommit for storage and backup - but since the multi-node sync stuff wasn't available for self hosting anyway, I've never tried it, and thus dodged the problem entirely. Obviously for a lot of people multi-device use is the entire point, but for some of us, logseq is "just an editor"...)

I actually do something like this with my logseq notes. Since all of the files are .md in a directory, one can load them all in to a vectordb and use it for RAG. Logseq has an API too but using the .md files is easy.

In this regard,maybe JetBrains should dust off Omea [1] and add an appropriate LLM to it.

[1]: https://www.jetbrains.com/omea/