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…
> 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.
Logseq 2.0 Beta (DB version) is here
41–50 of 89 posts
Re: Logseq 2.0 Beta (DB version) is here
#42It pains me to say, but it's probably too little, too late. Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnation, the supposed improvement is a database format to fix their technical issues, so I can no longer keep all my data as markdown files? At a time when half the edits are done by Claude and tracked with jujustu, this is…
Yeah I felt the same about the decision when they decided to move to database structure. If it had this structure from the start it could've built up an ecosystem like Obsidian's but now it's hard to justify going for it.
Re: Logseq 2.0 Beta (DB version) is here
#43Earlier quoted context omitted.
I'm curious, do you do version control, sync, or work with AI agents? If so, how does that work (for you)?
there is a CLI that gets installed when you install logseq, I just past the documentation ( https://github.com/logseq/logseq/blob/master/docs/cli/logseq... ) and codex knows what to do. Then I can summarize my journals over months and all. I do version control by exporting the .edn (a serialized file that contains all nodes) and using git. All of that is very alpha (to be honest, I don't understand them releasing a b…
Re: Logseq 2.0 Beta (DB version) is here
#44I am still on a very old version of logseq. Why update?
NewTags is pretty sweet: https://discuss.logseq.com/t/introducing-newtags-with-exampl... Bunch of reasons.
You don't have to, though. If the old version works, just keep using it :)
Re: Logseq 2.0 Beta (DB version) is here
#45Any good outliner alternatives out there? I originally came from Roam and was really happy to find an offline alternative in Logseq. I've since moved to Obsidian, though. Obsidian works well, but I still feel like my brain works best with the outliner-style workflow that Roam and Logseq offer. I have heard of https://outl.app/ but when I tried it out, it still seemed in a very early stage (and heavily vibe-coded, whi…
I appreciate the standard, intuitive keyboard shortcuts for creating/removing bullets, indenting/outdenting, moving lines up or down, etc.
Also, you can use the built-in syntax for block references to kinda-sorta recreate the Roam block-based setup.
Re: Logseq 2.0 Beta (DB version) is here
#46Earlier quoted context omitted.
I love the concept of logseq, but the userbase is just too small and in turn the speed of change is too slow. . Over the last few weeks, with the help of Claude Code I've finally been able to dive into Obsidian and build out the second brain I've always wanted. With the power to auto-sort small thoughts jotted down on my phone with minimal interruption and some automated maintenance & sorting. CC has really reduced t…
How are you using Obsidian (and the LLM part if you want to expand on that) to build a second brain? I’m using Obsidian but more as a replacement for Apple Notes because it supports Markdown. My vault is just a collection of notes somewhat organized into relevant folders. I know there’s a lot of functionality I’m not utilizing.
It's not quite done yet, but when it is I think I'll anonymize it and share it on GitHub. In the meantime, here's a pretty screenshot without anything personal: https://snipboard.io/tyRYEJ.jpg https://snipboard.io/mryYKe.jpg
Also used CC to help me build some complex Apple shortcuts to let me capture stuff easily. Either by sharing it or hitting the button on the side of my phone and jotting it down (that Claude didn't do quite as well at, but it got me 75% of the way and helped me learn how to make complex branching shortcuts)
There is one basic function Obsidan lacks - some variation of rollups to link fields in different notes in a structured way. It's where I really did like Logaeq better. I’m going to try using Claude to "reconcile" that stuff on a recurring basis.
To some extent I've probably tried to make Obsidian into Notion. But it's more flexible and free.
Re: Logseq 2.0 Beta (DB version) is here
#47Earlier quoted context omitted.
I love the concept of logseq, but the userbase is just too small and in turn the speed of change is too slow. . Over the last few weeks, with the help of Claude Code I've finally been able to dive into Obsidian and build out the second brain I've always wanted. With the power to auto-sort small thoughts jotted down on my phone with minimal interruption and some automated maintenance & sorting. CC has really reduced t…
I'm just in the toying and evaluation phase with Obsidian and so far I like it, but I'd like to understand why an AI is needed or even useful to begin with it? So far I just see a powerful text editor, what did you benefit from with AI use?
Could have just done it without it? Certainly, this just helped me build something more scalable than I knew how to on my own, and then I learned from it. And on an ongoing basis it'll help organize the things in daily notes and inbox and place them appropriately.
To put it another way, it helped me get from 0 to 1 and will do some of the routine maintenance required to move things from my second brain's short-term memory to long-term.
Re: Logseq 2.0 Beta (DB version) is here
#48Any good outliner alternatives out there? I originally came from Roam and was really happy to find an offline alternative in Logseq. I've since moved to Obsidian, though. Obsidian works well, but I still feel like my brain works best with the outliner-style workflow that Roam and Logseq offer. I have heard of https://outl.app/ but when I tried it out, it still seemed in a very early stage (and heavily vibe-coded, whi…
Obsidian's "Outliner" plugin is really pretty good. Esp. assuming "Editing view" and "Live Preview" editing mode, (which combine for WYSIWYG). I appreciate the standard, intuitive keyboard shortcuts for creating/removing bullets, indenting/outdenting, moving lines up or down, etc. Also, you can use the built-in syntax for block references to kinda-sorta recreate the Roam block-based setup.
Obsidian's data model, a huge selling point to some, really hinders it too. Logseq's new db format let's you treat any block as a page, metadata and all which can be super helpful.
Re: Logseq 2.0 Beta (DB version) is here
#49It pains me to say, but it's probably too little, too late. Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnation, the supposed improvement is a database format to fix their technical issues, so I can no longer keep all my data as markdown files? At a time when half the edits are done by Claude and tracked with jujustu, this is…
I agree, I truly love logseq as it fits the way my brain works in a way the few other tools seem to be able to replicate. Unfortunately my notes being in plain text is a non-negotiable for me. This will probably be the push I need to transition over fully to org-roam. My logseq files are already stored in org format anyway.
It’s sad because Logseq felt like a more focused tool than either Emacs or Obsidian, and really nailed the UI/UX that I wanted. But the interface was slow and buggy, and both the Org and Markdown backends are sufficiently non-standard that I didn’t want to continue writing my notes in that unless I believe Logseq is going to be around for a while. And I’m not at all excited by the large investment in the database backend, given that being backed by plain text is their largest feature from my point of view.
Re: Logseq 2.0 Beta (DB version) is here
#50Any good outliner alternatives out there? I originally came from Roam and was really happy to find an offline alternative in Logseq. I've since moved to Obsidian, though. Obsidian works well, but I still feel like my brain works best with the outliner-style workflow that Roam and Logseq offer. I have heard of https://outl.app/ but when I tried it out, it still seemed in a very early stage (and heavily vibe-coded, whi…
Workflowy.
Truth is, it's been nearly a decade since I used Workflowy and nothing has ever been as good. But the inability to email notes to it or otherwise push data to it from other sources was such a deal breaker. Particularly as mobile became a larger and larger part of my life.
Then there was Moo.do, the next best infinite-outline tool I could find. Their rebrand as Legend was strange, made it hard to find the app, and, from an SEO perspective, was an odd choice.
One of these days I should return to either Workflowy or Legend. My issues were silly and now are much more surmountable.
EDIT: WOW, Workflowy has really gotten with the times! Seems to be iterating much faster and even has an MCP server.