☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 1 month agofiles.md is an open source alternative to Obsidiangithub.comexternal-linkmessage-square45linkfedilinkarrow-up1135arrow-down18cross-posted to: opensource@programming.dev
arrow-up1127arrow-down1external-linkfiles.md is an open source alternative to Obsidiangithub.com☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 1 month agomessage-square45linkfedilinkcross-posted to: opensource@programming.dev
minus-squaregirsaysdoom@sh.itjust.workslinkfedilinkarrow-up2·1 month 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-squaresunstoned@lemmus.orglinkfedilinkEnglisharrow-up3·1 month 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-up1arrow-down1·1 month agoIt’s fine for input, but Logseq “.md” files are only suitable for import back into Logseq (at least if they have any links)
minus-squareflandish@lemmy.worldlinkfedilinkarrow-up2·1 month 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!
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.
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!