3 ms·

I as a user on the other hand don’t want a browser to host “applications” that have arbitrary access to a folder on my file system. I’m okay with it having imp

I as a user on the other hand don’t want a browser to host “applications” that have arbitrary access to a folder on my file system. I’m okay with it having implicit access to locked down folder if the operating system makes it impossible for any file in that folder to be an executable and if when you double click on that file, it can only launch the web page that saved it. The latter is to prevent web apps from saving files like bash scripts, macros, etc that can be easily executed.

apatheticonion 4y ago
Of course, and that's sensible. It's just about drawing a balance of safety and utility. Implicit persistent file system storage based on origin is fine, given scripts cannot automatically execute things there. Could use it to store sqlite databases or whatever. Access to folders and such (like through the filesystem API) also makes sense because it's via a user prompt. Giving the browser more powers would eliminate the demand for platforms like Electron - which are basically inefficient unsandboxed PWAs