Nextcloud integration would be good. Currently, I find that editing an .md file breaks a Logseq journal file, as all
-headings are replaced with*. Could Logseq not accept*headings?
This is not a Logseq problem, but rather a Nextcloud problem. Their webapp editor breaks formats, it is only good for nextcloud use only. It is good because it is possible to do simultaneous editing. I’ve personally disabled it and will enable it when they will have made it not reformat everything.
As for Nextcloud syncing, it already works fine. It doesn’t work as well with mobile device. And that’s again a Nextcloud problem since their mobile Nextcloud client won’t sync like it syncs on desktop devices. So another route is needed.
Here’s my post on the subject:
FolderSync (there’s other things I’ve mentioned on the subject of syncing on this thread):
My conclusion is this ain’t a Logseq feature beside Webdav integration where it would allow using a webdav stored Logseq graph and perhaps also be able to use webdav file and video embeds. I remember trying to embed a video from Nextcloud but it failed.
So my recommendation would be to change this feature request for webdav integration. I also recommend taking a look at the above link to provide a self-hostable solution which could eventually provide collaboration features. I also recommend using a git (self-hosted, private or public, depending on your needs) repository when trying to sync with multiple solutions (for instance, Nextcloud and FolderSync) (remember to filter out the .git folder with FolderSync) to get a backup solution and be able to see if something was altered.
So far, I did not have any sync problem with Nextcloud and FolderSync, the only problem I see is when a page is simultaneously edited or if a page is edited on Desktop and mobile device (since there is a sync delays on mobiles with FolderSync).
Edit:
Here is the feature request for 2 way syncing Nextcloud client on mobile: