Basically, yeah.

Although I use a notebook for most of my todos, anything more technical goes in a text file – though I made mine like:

# todo.md
- todos for website.one [here](./website.one.md)
- todos for website.two [here](./website.two.md)

# website.one.md
- [x] support mobile views
- [ ] migrate to self-hosted

Although my “todos” double as “ideas to try out” and “projects to spike” so I like this type of organization.

Actually speaking of pointless todo apps… I have this one I’ve been mulling over that basically takes a markdown list as input, does logical stuff to it, then outputs in the same format. I don’t know if that’s useful in any way, but I feel every nerd needs to reinvent the wheel at least once.

The section entitled “The Secret Sauce” is the real magic of this article.

Apps aren’t a problem, but they’re also not a guaranteed solution. If you don’t actually do what needs to be done, then it isn’t working.

@stabby_cicada so true. I have a physical note book for work, and all personal notes are in markdown, nextcloud server.

I use this one. Very handy http://todotxt.org/

I can agree and empathise with this a lot, a text file is what I generally use on a desktop, though for smaller tasks that I knock out on the go, I use p!n on android (fdroid)

This is why I like neorg plugin on neovim

I just have a directory for todos, checklists, reference files, etc.

And I can peruse it easily with nvim-tree

And I just have a hotkey to toggle state of items (todo, done, paused, represented by empty box, checked box, clock, respectively)

But in the end it’s just editting a raw text file.

Logseq. Basically a .txt file on steroids.