Post #1824644

2026-03-27 11:58 UTC

Thanks! For the interested: They're working on a logseq edition with db backend as a basis for real time collaboration, better performance, data loss prevention during sync. FAQ states: > Are you going to deprecate Markdown files support? > No, we’ll continue to support both file-based and database-based graphs, with a long-term goal of achieving seamless two-way sync between the database and markdown files. This will allow you to leverage the benefits of the database version while still being able to use other tools. It looks like, for the moment the md version is there to stay. I'd very much like that, because syncing with git or syncthing. I'm not sure how useful the collaboration part will be for me. Other tools would have to make room for it in our workflow (ticket system, wiki).

Replies (1)

@Cyber@feddit.uk 2026-03-28 06:42

Yeah, _personally_, I think they'd gradually make it db first and then markdown will gradually become an import / export function. And I don't need colab... my notes are mine. Yeah, there's a few I share (ie home stuff with my partner), but for work, personal stuff, nope.. just me. But yeah, after ~3 years of almost daily note taking for work, it needs a computer with SSD to find things quickly and can take a while to start on the phone (hence using Markor to edit the .md files directly instead) To your original post, yeah, single maintainer... but Logseq has how many? And it's stalled really... from an external viewpoint. I think SilverBullet has a slow steady pace rather than Logseq's fast initial pace and then ... nothing much since they got lots of investment - which someone will want back.

Open ##1824645