With everything going on with Twitter and Reddit I feel like I have a new appreciation for having my own local knowledge base on Logseq.

Demo page: https://demo.logseq.com

  • Bad3r@lemmy.oneOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Thank you. Added the demo link to the OP. I used joplin before moving to logseq. Couldn’t get a good workflow going, and I hated having to decide where to store information. Logseq journal solved that issue for me.

    • constantokra@lemmy.one
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      How does it solve that issue for you? I use Joplin, and it’s useful, but I wouldn’t say it’s a perfect fit. Logseq seems like it has a good bit more time investment before it’s useable, especially if you want it to work better than, say, Joplin.

      My main beef with apps like this is that they basically say ‘we can do everything’, and leave you to slog through hours of documentation and use case examples to see if it’s a good fit. And that’s totally fine, except I don’t have that kind of time to dedicate to one single app before I decide if it’s a good fit.

      I wish they’d answer the question ‘why is this software better than Joplin or a notebook or stack of text files’ in bold text right on the front page, because that’s the most relevant piece of information for most people.