I’ve been looking into all sorts of them recently: logseq, appflowy, vikunja, etc. What tools do you use? Why? What problems did you run into with the previous set of tools you used for this job?

Right now I’m primarily interested in finding a “zero-knowledge” (cloud provider doesn’t have access to my data) system for task management. Needs to be able to have recurring tasks and tasks organized in some interesting/useful ways (by projects/labels/something, maybe a kanban and table view). Deadlines and time tracking/planning interesting but not required.

  • @clothes@lemmy.world
    link
    fedilink
    13 months ago

    This is really helpful, thanks!

    I think I need more practice with knowing when to create a node. In the past, every single entry would look like this:

    I went to [Alice] birthday party and met [Bob]. We talked about [clouds].

    And that got very cumbersome. I like your suggestion of using back links to create a better summary document.

    • @finestnothing@lemmy.world
      link
      fedilink
      23 months ago

      Biggest piece of advice, you don’t need to document everything you do in your life. If it’s info you might use in the future, a significant interaction or event, fun tidbit etc, add it in. If it’s just a casual conversation with someone that you don’t learn anything significant or it’s something that you’ll never link to or use again, just keep it as a memory.

      I did a lot of over-capturing early on and got a lot of fatigue from it. Now my note making is as I run across things I’ll want to reference in the future (plans that were made, ideas to learn more about later, important phone calls/interactions, notes on articles, updates on projects, etc), with refinement to those ideas coming when I access them again later (or if I’m bored and have time). It’s no longer a drain to grow my PKM, it’s slower but much more meaningful info

      • @clothes@lemmy.world
        link
        fedilink
        13 months ago

        This makes a lot of sense! I’m going to give it another shot with these insights in mind. I think if I frame it as a future-facing tool like you describe I’ll avoid a lot of my previous mistakes.

        Thanks for explaining :)