as far as I know, it has been updated to v40.
but it’s not perfect and PRs are welcomed:
as far as I know, it has been updated to v40.
but it’s not perfect and PRs are welcomed:
It is 38 in the released version: $GH/logseq/og/blob/680b371f0f53968adf678759e9bfd5cb7ea5790c/resources/package.json#L58 (can’t post a link for some reason)
The logseq-db has a mirror md feature. This is implemented completely in the opposite way of obsidian: in logseq the db is considered to be the source of truth while in obsidian the markdown file is the source of truth
In case you guys haven’t seen it there’s a few good suggestions on this thread over here for people who prefer to file based system.
Tine is one that I think looks basically like LogseqOG if they’d carried on polishing it.
e.g. Workspaces, tabs, better templates (like Next Monday, 'In 5 Day’s etc)
Whereas Outl is a really interesting one. Similar philosophy but a different direction.
Hope this helps someone ![]()
Thanks. Tine is awesome. It’s much faster though the functionality is not yet stable enough, especially on mobile.
Yeah agreed, although having flair followed it for a little while he’s absolutely stealing ahead.
The only real drawback for me currently is that it doesn’t handle advanced queries which for me are pretty essential. But I’m optimistic it’ll be fighting fit very soon.
If you could I’m sure he’d appreciate but reports. ![]()
thanks for sharing outl.app here. we’re still building toward a stable release, but we’re getting really close. I recently started using it in my daily work routine (and migrated my history all the way back to 2022)
My decision depends on the successful implementation of the following features:
I will wait and see, I think that the new DB Logseq version might be particularly useful for those interested in using Logseq as:
I’m sticking with OG. I’m syncing my changes instantaneous with Syncthing. I can access my Markdown files from 3 different places. I would need a very compelling reason to move to the DB version.
Syncthing rocks!
Me too, the reason I choose logseq that it supports org mode. I don’t need new features. I just need them to maintain OG version.
Markdown files are the reason I use Logseq. Logseq is absolutely not the reason I use Markdown files.
To add to this, I haven’t experienced any stability issues. So you could also have a good experience
Thank you, will check this out.
I am excited about Logseq DB and have been following its development - happy Logseq has decided to focus on it. I’ve managed to get it going online, but I’d prefer to use it as a program on my computer. I’ve read the literature put out recently about the different versions and have gone to the Github pages wanting to download the latest version, but I’m not a programmer and I can’t find clear instructions about how to do that - even the videos aren’t helpful. Any help would be appreciated (and sorry - it will need to be very simple instructions - I’m sure there are quite a few of us out there that really like this program but are struggling with lack of step by step instructions and videos for ‘non-tech’ Logseq users).
Hi! Im having trouble understanding what you need. Do you just want to install Logseq DB locally on your computer, like any other app? If so, by downloading from the official site https://logseq.com/ you will get the downloader
Yes - that’s what I’m after. Ok thanks - will try that.
Logseq og has the features I need and is based on Markdown. I’ll continue to use this version. Especially since the current DB version, “2.0.1 (Beta Testing),” seems experimental, unstable, and unfinished to me. I hope that the Logseq team will at least fix bugs and security vulnerabilities in Logseq og, as they’ve announced. However, I’d like to see them follow through on their promises:
The latest version was released on April 15, 2026—more than 5 months ago.
The last commit was made 4 months ago.
5 unpachted security vulnerabilities with CVE ( 5 unpachted security vulnerabilities with CVE? · Issue #12838 · logseq/logseq · GitHub ) - Still not fixed!
My question about the security vulnerabilities in this forum has not been commented on or answered by Tienson Qin or any other team member since August 17. My post has received four upvotes (hearts).
I haven’t given up hope yet. In the long run, I’d like to see a solution.
Is anyone able to fix the security vulnerabilities and bugs?
Can this be done in the current repository, or is it necessary to create a fork of Logseq?
It worked! Although I had to first close Logseq OG or the new download would just default to that program. Not being able to have both of them open will make backing up my work on the OG version a bit more difficult, but I’ll work something out. Looking forward to trying out a few projects on the DB version (I do research and community work).
I’m cautiously optimistic about the DB version. I’m glad the Logseq team has identified that they had an unsustainable maintenance burden, and I hope the DB refactor does truly fix that. However, I can’t switch until they at least add whiteboard support, because I have things in my whiteboards that I can’t afford to lose. I also want to wait until it’s stable enough that they don’t feel the need to disclaim that data loss may occur. Logseq is my core notes app where I store both personal and work projects. I can’t really afford to be using beta software for that.
I’m also not optimistic about the Logseq classic maintenance. There is a four year old bug that breaks footnotes starting with inline links. The fact that a feature in markdown rendering, the most basic feature of this app, has not been fixed in four years does not fill me with confidence in the team’s ability to triage and prioritize bugs that are impacting users. Two other basic rendering and parsing issues reported in 2023 and 2024 were auto-stale closed without a response from the team.
For now, I’m continuing to use the OG version. I hope the DB version will fix these basic issues. If the DB version doesn’t stabilize within a year or two, I will consider moving to Obsidian.
Sadly considering moving to obsidian if logseq OG no longer working in the future to keep the killing feature (for me): markdown files.
My ultimate goal is to be able to “read” my thoughts in 10, 20 years. The only way is human readable data without the access locked because of an application no longer maintained.
Database slowness or corruption or application “improvements” breaking compatibility with past capture, is something I can accept for a task list.. not for my personal notes.
In addition, AI era made markdown files and folders the new fashion, moving us back to the “GTD” principles: you just need list and folders. Database was a great idea, 4 years ago.. and seem now a little bit counter productive … until the new fashion ![]()