I'm gonna fill this space with the contents of a tweet thread describing my adventures importing Taskwarrior tasks into Logseq.
Course, it started as a toot thread. But I don't have a shortcode handy for embedding those. You get a link:
But I do have a Twitter shortcode handy, so I'll embed the interesting tweets.
Imported my Taskwarrior tasks into Obsidian. 1,983 new notes.
— brian wisti (@brianwisti) June 12, 2022
Animation of that graph's not based just on timestamp or it would be ＊hilarious＊. Just "doo de doo de doo de BWOMP" pic.twitter.com/LOCULraxKr
Right, I started with Obsidian. Then I thought about how Logseq has task management features built-in. Decided to shift focus there.
Took me a bit to figure out how I wanted to link everything up. Ended up with a more cohesive graph — to my eyes, at least.
Okay. Added some relevant metadata, linking imported Taskwarrior task dates to the relevant Logseq journal entry.
— brian wisti (@brianwisti) June 13, 2022
The graph shows a different distinction now, between the very large "coping with daily life" galaxy and the "learning stuff for its own sake" clouds. pic.twitter.com/JnFUDwE8UT
The secondary purpose was to get more comfortable using [https://www.typescriptlang.org][TypeScript]] and Node.js. I didn't revert to Python, Perl, or Ruby for any of this. Mission accomplished!
You want to see the code? Ah. Well. Maybe later. This was flailing-and-puttering code, not showing-off code.
task add project:Site +blog \
write better on taskwarrior logseq importThere. Now it can haunt me for the next couple years.