this post was submitted on 18 May 2026
89 points (96.8% liked)
Open Source
46939 readers
203 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I tried logseq for a while but I couldn’t get over the fact that all ones were bulletpoints.
I settled on obsidian with selfhosted live-sync and it’s been rock solid for a year now.
i want to get back to logseq but … i wonder how it will work with my obsidian lib; it’s just dirs and files. with links. mostly just todo lists by project and some code snippets for reference.
is logseq compatible?
In the past I migrated my notes from Obsidian to Logseq. Both have a bit different approach, but basically the move was to modify
dir/file.mdto bedir__file.mdLogseq leverages centrally hosted databases while obsidian works directly from files and directory structures. There should be a way to import individual files but I'm not sure if it will parse your entire vault.
Logseq still supports plain .md files ("Logseq OG") in addition to the new DB backend., so a convoluted import isn't necessary.
It's fine for input, but Logseq ".md" files are only suitable for import back into Logseq (at least if they have any links)
gotcha. thanks! i kinda like the idea that the place is just a series of md files, in obsidian to be honest but will give logseq another look!