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.

you are viewing a single comment's thread
view the rest of the comments

[–] sem@lemmy.ml 21 points 2 months ago* (last edited 2 months ago) (3 children)

For me one of the most flexible and mature way to knowledge base, tasks and notes is an org-mode.

I have two main workflows. The first one is task management. I have a lot of recurring tasks with tags, deadlines, schedules, etc. All of them are living in org-files in my Nextcloud. On Android I'm using orgzly-reviwed for sync via WebDAV, on my work I'm using organice (via WebDAV) as a "web-version" and also I'm editing my notes in emacs on my laptop (but actually any text editor could be used).

The second one is a knowledge base. I'm using org-roam locally (and with a localhost web server, built in into emacs) and orgnote for Android/Web + synchronization. My knowledge base is Zettelkasten-based.

Orgzly-reviewed: https://github.com/orgzly-revived/orgzly-android-revived

Organice: https://github.com/200ok-ch/organice

Orgnote: https://github.com/Artawower/orgnote

Orgnote provide a way to encrypt all notes by your own key/password. With orgzly I'm relying on Nextcloud encryption.

[–] N0x0n@lemmy.ml 4 points 2 months ago (2 children)

The org.pdf documentation is 300 pages long O_O ! https://orgmode.org/org.pdf

[–] HexKay@hexbear.net 3 points 2 months ago

Simple, spin up a Stirling PDF docker, split the org docs and create org notes either by section or by page, linking to the relevant PDF page

Now you've practiced using org mode by documenting org mode in org mode using your own words based off the org mode documentation

[–] sem@lemmy.ml 2 points 2 months ago

Yes... org-mode is more than 20 years old... It is a price of flexibility: I have a strong feeling that one can adjust org-mode to any workflow. But I do not use even a third of the org specification. There are a lot of cool blog posts like "org mode quick start" or "org mode basics", I would recommend to start from such posts, not from a documentation.

[–] clothes@lemmy.world 3 points 2 months ago (2 children)

I keep failing to make Zettelkasten and org-roam work for me. Do you use a single knowledge base for your whole life, with millions of tags and pages? Or should I be making separate directories for each project? Is the "daily journal" the best place to put everything, with well tagged entries?

You don't have to answer all of those!

[–] finestnothing@lemmy.world 2 points 2 months ago (1 children)

Honestly, whatever works for you.

My preferred system is two big directories, one for your daily notes (dailies, journal, etc), and another for literally everything else.

This is how logseq is implemented, and can easily setup emacs org-roam to do it too. It's very nice because you don't need to worry about where to put something, throw it in your daily journals and get all the info down there, and link densely. If it's about a specific topic, link to it and when you go to that topic you'll see the info in the back links below (logseq does it automatically, emacs take a bit of config). You can then transcribe the important/summary/etc info from all of your aggregated back links into a single well thought out and planned document, or at least a single trimmed down one. Or, just leave all the info in the back links, whatever works best for you

[–] clothes@lemmy.world 1 points 2 months ago (1 children)

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 2 points 2 months ago (1 children)

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 1 points 2 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 :)

[–] sem@lemmy.ml 2 points 2 months ago (1 children)

No, I have two different things:

org-mode files with schedule, diary, tasks, etc.
knowledge base, org-roam (orgnote). I have a single base but it contains graphs about topics and these graphs are not connected

I like that approach, because I use orgzly-reviwed on Android with a notifications. And because it is simpler to maintain knowledge base.

[–] clothes@lemmy.world 1 points 2 months ago

Got it, I see what you mean. Thanks for this!

[–] oxomoxo@lemmy.world 1 points 2 months ago (1 children)

Logseq has Org Mode...

[–] finestnothing@lemmy.world 3 points 2 months ago

It has org mode, but the links in logseq aren't compatible with org-roam links, so either you use custom elisp to make logseq links into emacs compatible links and can't follow links in logseq, or make emacs notes logseq compatible and can't follow links in emacs.

Also, iirc logseq is planning to drop org mode support when they launch their database update, either that or have it available but not updated anymore.