4 ms·
Search for “Logseq data loss $current_year” and you’ll see horror stories of people who did everything exactly right and still lost a bunch of data from it. The
by kstrauser 3y ago
Search for “Logseq data loss $current_year” and you’ll see horror stories of people who did everything exactly right and still lost a bunch of data from it. The most recent one I saw involved someone getting on a plane and thus losing Internet access to the paid syncing service. They did a bunch of work as they flew across the country. When they landed and the connection resumed, it synced everything back to the pre-takeoff state and erased their work.
Logseq is so very close to being exactly what I want, but there are way too many tales like that for my comfort. Yes, I could come up with something involving Git or rsync or whatever, but at that point I’ve conceded that I don’t trust the tool. And if I don’t trust the tool, I’m not going to use it.
- asdfgeoff 3y agoThis exact issue happened to me. I think it was related to crossing timezones during the flight. The experience has definitely made me think twice about adopting Logseq my primary notes tool.
- kirso 3y agoPretty much a weekly occurrence for my work with Confluence. Never happened to me with Logseq, also why are we making a trend of something that has happened to 5 people out of 10000 users? Kind of a bias when you see only horror stories of people losing data, but not the rest who are fine.
- kisamoto 3y agoOuch - I hadn't heard of that so thanks for raising awareness. I'm trialling both with syncthing across multiple machines and so far no data loss but I'll make sure backups are in place!
- iamjkt 3y agoLogseq's native sync now has smart merge which I have found prevents issues like this.