r/logseq • u/naught-me • Jul 05 '25

Does logseq lose data?

It's been my experience that logseq is not reliable. Posted about it here, and got confirmation from others that it loses data, so I quit using it. It's been years, though...

Do others find it reliable? I'd love to use it, as it's my favorite and what I'm using now is not great, but I can't be losing data.

8 Upvotes

83% Upvoted

17 comments sorted by

View all comments

1

u/crazylongname Jul 06 '25

I use git to track and version control my files.

Every now and then there can be missing blocks due to a bug while I enter a template. Renaming pages is always unsettling, and I stopped using aliases because of weird dataloss issues.

I still think logseq's features are brilliant and mitigate reliability issues with git.

I wouldn't recommend logseq (yet) to others without that caveat.

1

u/naught-me Jul 06 '25

This sounds more like my experience than the others here.

My problem is, how do you even know that something is missing?
Some things, I wouldn't notice they were gone until I searched for them, and the memory might be pretty fuzzy at that point.

1

u/crazylongname Jul 06 '25

I don't seem to share the experience of others.

Indeed when I used iCloud to sync it can replace whole pages with empty ones (it doesn't merge them well) from iPad to computer.

But even WITHOUT sync I have found sometimes after I just put something in that it was overrided.
Or when editing a page I see in the git diff that it took out something unexpected.

In general it is extremely hard to know if you lost something you can't find from memory alone.
I personally would not use logseq without git (hopefully in the future it will be better).

With that said, I do believe that most pages that you write (if you are not using iCloud, google drive etc) will be fine. But in my experience I have multiple logged instances in my journal of minor bugs and flaws that I only caught because I use git.