Logseq: A privacy-first, open-source platform for knowledge management.

Bad3r@lemmy.one to Free and Open Source Software@beehaw.org – 43 points –
GitHub - logseq/logseq: A privacy-first, open-source platform for knowledge management and collaboration. Download link:  http://github.com/logseq/logseq/releases. roadmap: http://trello.com/b/8txSM12G/roadmap
github.com

cross-posted from: https://lemmy.one/post/197223

With everything going on with Twitter and Reddit I feel like I have a new appreciation for having my own local knowledge base on Logseq.

15

(Oh hey, nice seeing you here!)

I've used Logseq in the past though I've not been using much recently. It's a really cool application.

Hey there! great to see you too. Hopefully, once the database version is released you will give it another shot!

I've tried using it, but it's not very user friendly and that's coming from someone who's using Emacs Org-roam. Like, I can't even find out how you use an alias for a note reference. Sometimes the name of the note doesn't fit the structure of the sentence I'm referencing it from.

If you use emacs, you have no right to call something unfriendly lol /s. Logseq supports both markdown and or-mode. I don't use orgmode, but to make an alias in Markdown, all you need to do is [alias]([[page name]])

I do agree that UX could use a lot of improvement.

Wait it supports org mode? Might have to give it a second chance then

Some of my colleagues swear by logseq, but I personally haven't used it. If the upcoming sync feature would be available to self-host, I might consider switching to it, as it would combine multiple services that we are currently using.

It seems to be file based, so wouldn't it be able to use other self-hosted sync-tools like the next cloud client (given you're hosting your own instance)?

Does this also work in a collaborative way, for example two people editing the same note? I would guess that file locking could be an issue.

Depends ok the cloud solution you use, but it definitely could be an issue. Probably not because of locking, but because the files probably aren't locked with the clientson there could be issues while merging the changes.