I've been using Logseq DB (this new version, as a nightly, for a year) and it's a really great concept, way better than anything I tried for notes and organisation. You can apply tags to blocks, which make them a kind of thing (a project, an author, a quote, a thought). It is very fast, and easy to learn.
I switched to it from Apple Notes + Obsidian (I've used logseq MD in the distant past). I have to say though that there are still some rough edges in the current developments and many concepts are still half-baked (Assets, Library).
I still use it because with it, I take more notes and retrieve them better, which is really convenient. The barrier to jotting something down is very low. I think the dev have really hit a sweet spot so I hope they can polish this application as it should be.
> You can apply tags to blocks, which make them a kind of thing (a project, an author, a quote, a thought)
FWIW, needing typed notes is what settled me on Trilium Notes after a foray into a bunch of alternatives, including Notion, Anytype, Obsidian, etc
I realized that efficient note taking and knowledge management generally means (to me) having "dimension lists" (collections of places, people, projects, ...) being referred to in topical notes/journals/events, generally organized as a hierarchy (but not always). Once you come to that realisation (and that your notes system is essentially a glorified RDBMS), you want a system that ensures that "notes of the same type remain as consistent as possible", which Trilium makes easy via Templates and/or Inheritance (attributes can be inherited in the OOP sense, or composed like traits), collections to represent, manage and edit large amounts of notes at once, and emacs-levels of scripting if that's your jam.
I'm curious, do you do version control, sync, or work with AI agents? If so, how does that work (for you)?
>You can apply tags to blocks, which make them a kind of thing (a project, an author, a quote, a thought).
Possibly worth pointing out that this is a Logseq thing in general, and not specific to the DB version. And I agree it's pretty great - I don't use it often, but it is very handy when I do. Much more usable than YAML frontmatter, which requires dedicated pages for everything.