Hard decision choosing between @Logseq and obsidian... For now I'll go with #logseq. #opensource for the win!
This feels like a combination of all the best features from org-mode, TiddlyWiki, GTD & Anki with a clean interface. Mind == 🤯
Let's find out if this is too much for a single tool, but it looks thought through and well designed.
Anyone got tips or best practices I should follow from the start to not get lost in there? Thanks in advance 🙏
Here there are some pro/con after ~2 years of usage and being a backer:
@post
Hi, thanks for the pointer. Interesting to see the pro/von points you collected.
Reading the comments below your list, I'm wondering whether it's worth investing time into learning it right now before seeing the direction the cure Devs are going regarding privacy.
Would you, personally, start using it again at this point or would you look into other tools?
I'm coming from Emacs/org-mode and it's very mighty and all, but...
@post
...linking isn't as quick and easy as it seems to be in logseq and dynamic queries are not possible, apart from the agenda view, tags are clumsy/limited and there's other issues that I cannot implement/adjust to my liking, since I'm not a lisp programmer.
Logseq seems to have everything out of the box, that I'm using in my workflow of several combined tools.
By using Logseq I learned a lot of things so probably it was worth it.
It takes months to understand how to use Logseq's full potential and indeed there is not a 1:1 replacement. Alternatives miss something.
Suggestion: keep the content of your notes separated from navigation, for example by keeping queries in dedicated pages and not mixed with content. Otherwise you will be much more tied to Logseq. At least now I can browse my notes using any Markdown editor or Zettlr that even support wikilinks.
Maybe we should organize as people that cares about privacy, digital sovereignty and related topics and try to improve Logseq. We could make bounties for features we want to get merged in Logseq or if needed we could promise that we will move our money on OpenCollective to a patched version of Logseq that tracks upstream development (kinda like Bromite with Chromium for Android).
