Logseq --> Silverbullet
2026-03-26 23:53 UTC
Replies (5)
-
@julianwgs@discuss.tchncs.de 2026-03-27 06:54
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.
-
@probable_possum@leminal.space 2026-03-27 08:14
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.
-
@Nibodhika@lemmy.world 2026-03-27 23:12
Hey, I've been using silverbullet for a year or so. The first thing that I will say is that if you don't care for client/server I would suggest just keep markdown files in a folder, that's very portable and there are tons of plugins for editors to track that, that's what I was doing before Silverbullet, and way before that it was org-mode which I still miss a few features sometimes. I've never used LogSeq, for any extended period so can't talk about specifics there. From my experience these are the things I like about Silverbullet: * It's mostly markdown, this means that if I ever have an issue with SB I can just access the files directly * Client/Server means I can add quick things from my phone/tablet/different computer very easily * Sync mode means I can edit even when offline and have it sync later * It is extremely hackable, if you can program you can make it do what you want and it can be amazing at times And these are some things I dislike about it: * Syntax doesn't seem to be stable. I have some old files that don't draw tables anymore because something changed in the extra syntax they have for queries. * It is very bare-bones, it doesn't have the bells and whistles of other larger products and it never will, it's not what it's about. At the end of the day I think it's a great tool for what it does, but you should understand what it is. If you're expecting charts, diagrams or similar you will be sorely disappointed. If you expect a solid note taking app I think you'll be very happy with it.
-
@Prunebutt@slrpnk.net 2026-03-27 08:02
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.
-
@xep@discuss.online 2026-03-28 02:39
I've been using foam with vscode. It's not programmable like Silverbullet is, though, I don't think.