45
submitted 3 months ago by Cyber@feddit.uk to c/selfhosted@lemmy.world

TL:DR; Has anyone here successfully migrated their data & workflow from Logseq to Silverbullet?

... wall of text follows ...

I've been using Logseq for a few years and it has been a life saver at work, trying to track the stuff going on - honestly, I'd have burned out if I hadn't found it.

However, I still haven't quite got all the things organised and I feel Logseq's development is taking a different track that I don't want to go down (db, collab, etc)

SilverBullet.md appears to be developing into the solution I'm looking for... although I don't want a server-client architecture, so I'm running it standalone at the moment.

But, the learning curve feels so steep it's tending to curve back on itself... or... I'm just too busy to focus on learning it.

I see how the file structure works, but I don't understand how the templates, journals, etc work (really simple.in Logseq)

It appears to be 1 person developing this with lots of helpers who all seem happy to chip in with some AI generated code in the forum, but no meaty documentation, examples, etc.

If you've read this far... is it worth sticking with? Is there an FAQ I've missed? Any pointers or encouragement...?

you are viewing a single comment's thread
view the rest of the comments
[-] probable_possum@leminal.space 3 points 3 months ago* (last edited 3 months ago)

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).

[-] Cyber@feddit.uk 2 points 3 months ago* (last edited 3 months ago)

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.

[-] probable_possum@leminal.space 1 points 3 months ago* (last edited 3 months ago)

Logseq has how many? And it's stalled really... from an external viewpoint.

https://github.com/logseq/logseq/graphs/contributors

About 4. Plus the people who maintain plugins.

https://github.com/logseq/logseq/graphs/commit-activity

They didn't stop working on the code. But you're right, it doesn't feel like it UI wise. Which can be a good thing if the status quo is fine.

Markor

Promising. I will take a look.

Yeah, personally, I think they'd gradually make it db first and then markdown will gradually become an import / export function.

Can be. One of the reasons I like md - i'm not bound to one solution.

Still. At one point I will look at silverbullet.

this post was submitted on 26 Mar 2026
45 points (100.0% liked)

Selfhosted

60664 readers
872 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS