Logseq --> Silverbullet
from Cyber@feddit.uk to selfhosted@lemmy.world on 26 Mar 23:53
https://feddit.uk/post/46493990

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…?

#selfhosted

threaded - newest

julianwgs@discuss.tchncs.de on 27 Mar 06:54 next collapse

It seams tempting, because Silverbullet does look nice, but unless you want to become a maintainer I would not recommend you adopting it. Every maintainer is always just one step away on losing interest. There can be external factors like job change or internal factors like another interesting project. Both you have no control over and both are totally fine, because the maintainer doesn‘t owe you anything. Also especially in web dev the next breaking update requiring a lot of rework is just around the corner.

TLDR;So try it out, may be have a look at the code, but don‘t make yourself dependent on it.

Prunebutt@slrpnk.net on 27 Mar 08:02 next collapse

There’s always org-roam. Wide adoption, plentiful documentation, ports for nvim, etc.

Haven’t tried it yet, but I’m playing with the idea of switching from Logseq to that and I at least the two-way linking works similar afaik.

probable_possum@leminal.space on 27 Mar 08:14 collapse

Same here. Silverbullet looks tempting, markdown files and roughly the same feature set as logseq. I tried it out for a few minutes but did not go further.

What holds me back

  • there is just one maintainer. What if…
  • migration would take some work
  • I’m lazy and haven’t tested it out yet

I use logseq and mainly the tagging/ backlink feature (frontmatter and inline) + the usual md language to structure my personal knowledge. Very few queries which I would have to rewrite.

I do not have a real reason to switch away from logseq. It works well enough. There is the occasional full text search search bug which can be circumvented with ripgrep or the like. It takes quite some time to start up - once or twice a day. Otherwise it works.

You say they plan to drop the md support in favour of a DB? Would you please provide a link? Thanks.

TimeWalker@piefed.foxden.party on 27 Mar 10:48 collapse

Here’s the thread about the db-version and the change log for the db-version branch

probable_possum@leminal.space on 27 Mar 11:58 collapse

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