To continue this thread from GitHub, crawfordlong said:
… the current model is not optimal. …
To summarize: self-hosted, browser-based logseq ftw.
It took a while, but I finally twigged this is just not how Logseq works. However IMHO this should be the primary way it works.
Please correct me if I’m wrong, but my understanding is that logseq is a browser app that uses File System API to access data locally. This means each copy of the app is stuck in a silo on one machine with kludgy, slow and unreliable syncing if you want to use it anywhere else.
This is probably ok for the (rare?) person who only wants it in one place, but we all have multiple devices nowadays. I need to be able to have a thought and reach for the nearest device to jot it down. This is what, say, Roam does for me.
Hosting Logseq this way nukes all the sync issues in one fell swoop!
Storing the files on the server means that self-hosted Logseq can be a direct competitor to Roam (and a lot of the others), but with all the upsides of open-source, active development and local control.
As a Logseq fan willing to self host I’d switch from Roam in a heartbeat if I could host it this way. Without it Logseq is just too much hassle for me to make it seamless.