Logseq: A privacy-first, open-source knowledge base

Re:Logseq: A privacy-first, open-source knowledge base by dvas on Thursday May 02, 2024 @01:51PM (#40239193)

I think the best approach to take with personal knowledge bases or any knowledge data, is to have the ability to bring your data in and out as one pleases.

In my flow, I use a hybrid Zettelkasten-based approach to linking notes. vscode, zettlr, logseq, obsidian all render correctly. I am happy to see more tools which exhibit more of this "bring your own data" mantra.

[ Parent | on HN ]

Re:Logseq: A privacy-first, open-source knowledge base by tmottabr on Thursday May 02, 2024 @04:30PM (#40241052)

Do you point Logseq and Obsidian to the same vault or you keep separated vaults for each?

I tried using both a few years back and found a pain to manage, ended up staying with Obsidian that was more my style.

I personally prefer organizing things in folder and sub-folder structures and Logseq was not friendly to that approach at the time.

[ Parent | on HN ]