[freedomben]

Having it edit local files might be a difficulty of having it work in a browser instead of electron app. That said though, Electron apps I've worked with in the past usually have a "dev" mode already that just serves locally and you hit it with your browser (i.e npm run dev), and that browser allows using the APIs normally not allowed so long as it's being served from localhost. Might be a good solution.

[hoakiet98]

> that just serves locally and you hit it with your browser

This is an interesting take. My interpretation: You can host this on a server, then expose a port remotely which will have all the access of the electron app, making it a pseudo SAAS?

I will need to test this out but this has some cool implications. The other worry is multiple client support but you can just provision a personal instance.

[freedomben]

Depending on which APIs you use, that could work. I tried it with Logseq because I really want to have my knowledge base on a VPS which I can access from anywhere via browser, and because of the APIs they use the browser will only allow it if the remote is localhost. You could maybe trick it with a hosts file hack or something, but that would break a lot of (other) stuff that expect localhost to resolve to 127.0.0.1.