Ich bin jetzt schon einige Zeit dran, alle meine Aufgaben und Projekte sowie die größeren Ziele im Leben in #Logseq zu pflegen. Gerade bei Projekten möchte ich auch die zeitlichen Aufwende tracken. Das kann Logseq zwar auch, aber #TimeTagger scheint mir dafür viel besser geeignet zu sein. Klappt auch prima mobil mit dem Smartphone.

Vielleicht blogge ich dazu bald mal was. Bis dahin einfach mal die Demo anschauen https://tt.z3h.de/timetagger/app/demo

Logseq Brain v0.6.0 released!

Claude's persistent memory plugin now:

- Journey Log — every save/load lands as a bullet in today's journal
- section-targeted Reads — real token savings on big project pages
- sharper skill descriptions

GitHub: https://github.com/jame581/LogseqBrain

#openSource #AI #AIAgent #ClaudeCode #logseq

The (mental) model behind #Logseq is really nifty and might work for my brain. The current beta of the new "DB" branch works pretty well already, UI wise.

*But* the pivot away from plain text storage ("Markdown extended") is removing one of the major selling points of these tools.

I really like SQlite, but the way Logseq DB is using it, a single key-value table with basically all data stored in the highly app-specific structured value field/DSL, doesn't promise a lot of interoperability. 😟

Why does everyone sing the praises of Obsidian (the Markdown note taking app, not the security company)?

Vanilla install, this thing is mid, at best. #Logseq is better for writing richly linked, local Markdown.

It seems the only thing Obsidian has going for it is a large number of plug-ins and company maturity.

* Two search fields is silly
* Inability to link intra-file is an astounding oversight
* Typing "* " both creates a bullet *AND* keeps the matching right asterisk for italics is silly