•  nhgeek   ( @nhgeek@beehaw.org ) 
        link
        fedilink
        English
        81 year ago

        LogSeq

        I never heard of it until now. I’m a veteran of trying out and dumping so many note taking solutions. I’m certain to try this one, too! Maybe I’ll finally find The One.

        • It’s a timeline approach. So, I just enter notes for each day. I’ve developed a habit of just putting things down when I need, including random stuff, links to Slack conversations, etc. I then use tags to bind things together, and there are a couple of plugins in use.

          •  nhgeek   ( @nhgeek@beehaw.org ) 
            link
            fedilink
            English
            51 year ago

            I installed it and took a quick look. It reminds me of Obsidian’s approach. I got excited about that, too, but I found it very burdensome to use in practice. What I need is a sort of life log that grabs a lot of stuff quietly from integrations and that I can then further augment (for things like meeting notes). The problem with all of these graph approaches (for me) is that they become burdensome to manage.

      • Just started using Logseq and it has been a game changer. All other note apps I‘be used become black holes…notes go in and are never seen again. I can actually find things now with logseq. It’s helping with brain fog and getting my shit together. Can’t recommend it enough

      • They are very similar. The main differences are:

        • LogSeq uses bullet points. Obsidian is just pure markdown
        • LogSeq is open source. Obsidian is closed source
        • LogSeq has a predefined structure to it (folders). Obsidian allows you to have whatever folders you want

        Personally, I use LogSeq for my day to day work. Primarily because I prefer the bullet point approach when taking notes. But some people would prefer writing long continuous text with Obsidian.

        So to each their own. If you’re interested, try both (they’re both using markdown, so you can transfer between the two). I went back and forth a few times before settling with LogSeq