☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 2 months agofiles.md is an open source alternative to Obsidiangithub.comexternal-linkmessage-square40linkfedilinkarrow-up11
arrow-up11external-linkfiles.md is an open source alternative to Obsidiangithub.com☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 2 months agomessage-square40linkfedilink
minus-squaregirsaysdoom@sh.itjust.workslinkfedilinkarrow-up0·2 months agoLogseq 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.
minus-squareflandish@lemmy.worldlinkfedilinkarrow-up0·2 months agogotcha. 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!
minus-squaresunstoned@lemmus.orglinkfedilinkEnglisharrow-up0·2 months agoLogseq still supports plain .md files (“Logseq OG”) in addition to the new DB backend., so a convoluted import isn’t necessary.
minus-squarebrisk@aussie.zonelinkfedilinkarrow-up0·2 months agoIt’s fine for input, but Logseq “.md” files are only suitable for import back into Logseq (at least if they have any links)
Logseq 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.
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!
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)