@rwg

I've been using #logseq for years, and @obsidian a little bit less. Each one has its unique features. Logseq and @[email protected] are #FLOSS

Logseq has a good @[email protected] integration, too! (but I find that it does not always work well for long texts -is more of an outliner- and that's why I am using obsidian and considering silverbullet for other projects when I need to write longer texts)

Ist bei #Logseq eigentlich irgendwas passiert? Das letzte Stable Release ist von Ende letzten Jahres. Ich sehe an den Commits, dass fleißig dran gearbeitet wird. Hat wer das Nightly Build im Einsatz? Kann man das gefahrlos ausprobieren? Klar, Backup machen vorher...
@awws thanks for
"My Obsidian GTD setup"
https://daryl.wakatara.com/my-obsidian-gtd-setup/
Very useful as I migrate from #logseq to #obsidian
My Obsidian GTD setup

Simplifying to upgrade how I get things done.

Daryl Manning

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

TimeTagger - Demo

A live demo using simulated data.

Vor zwei Wochen bin ich Testweise für meine Wissensorganisation von #Joplin auf #Logseq umgestiegen. Mit etwas Umgewöhnung ein super Tool.
"Kinda like #logseq, but in two dimensions instead of one" is how I would attempt do describe #TreeSheets
https://strlen.com/treesheets/
TreeSheets

Managed to get both #syncthing and #logseq up and running on my #Uconsole. Quite pleased this is now possible.

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

GitHub - jame581/LogseqBrain: Persistent memory for Claude using a dedicated Logseq graph. Save and load project context, decisions, and progress across sessions and devices.

Persistent memory for Claude using a dedicated Logseq graph. Save and load project context, decisions, and progress across sessions and devices. - jame581/LogseqBrain

GitHub

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