Comment

probable_possum@leminal.space ⁨1⁩ ⁨week⁩ ago

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.

source

Sort:hotnew top

TimeWalker@piefed.foxden.party ⁨1⁩ ⁨week⁩ ago
Here’s the thread about the db-version and the change log for the db-version branch

source
- probable_possum@leminal.space ⁨1⁩ ⁨week⁩ 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).
  
  source