Does the upcoming database version retain browser-based functionality?
If so, does the database version (and specifically the database version) support a centralized database on a self-hosted private server?
Like many, I have no use for collaboration features and the local-first mindset only creates hassle, as I then need to sync. Logseq sync works fine, but it is simply an unnecessary point of failure for my use case. I have a private server that I use for many other tools, and my ideal use-case would be a self-hosted, browser-based logseq (this has been discussed many times before, including by me). The app-based model is untenable because of strict administrative limits on installing local software in certain environments–I can use the machine to take notes and access external resources at work as long as I don’t collect certain types of content in my notes, but we are strictly prohibited from installing software.
I understand this conflicts with at least one and possibly two revenue channels for logseq, but I am a sponsor and will continue to be.
I don’t have any specific answers to your questions, but I do think both would be possible with minimal modification to the project.
Currently, the DB version’s browser-based functionality works extremely well. Presumably they wouldn’t intentionally gut that just to provide the app.
Since the Graph in the DB version is primarily just a SQlite database file, it’s possible for Logseq to include a feature to allow you to since your SQlite database with another host, whether directly or through their cloud. I doubt Logseq’s developers will implement this directly, since as you said it would take away a revenue stream, but is should be entirely possible through a plug-in. More importantly, though, I’d imagine you could stand up a Logseq instance on a host at home, make it accessible (obviously using some authentication implementation in front), then have it open your Graph on the “server” side, so that your changes aren’t maintained on the local machine but instead updates on your home device that’s hosting the web UI.
This seems like it would meet your needs of
No local software installation
Data accessible across multiple devices
Again, I don’t know enough about the inner workings or desired endstate of Logseq’s development to give a definitive answer, but I’m hopeful it will work this way as well!