I think I’m (sadly) done with @logseq. It corrupted some data again and when I went to pull the stuff from git I figured it corrupted the .git/config even earlier than that. So now I have to pull the correct content from an old windows backup, ffs. What if I didn’t have a full disk backup?

I like the idea of block references, I love the query engine and the simple UI. But data safety comes first, really. Logseq is a forever beta at this point.

I really like the concepts behind the logseq db version but @obsidian doesn’t fuck with my data and you can see good iterative progress of its development. Yeah, it’s not opensource. It’s open data format, though, something logseq db will have to figure out eventually anyway.

  • fz0x1English
    1·
    1 month ago

    Logseq is a scam by inexperienced developers who raised money from investors and users and are simply burning through the funds. You can see this in the decline of development activity after they got the money, lol.

    When I used it, I repeatedly lost my data. I also tried their sync feature, and it threw my data into the trash as well. I highly advise against using this dead project. Just take a look at the 1600+ issues reported on GitHub and you’ll see for yourself.