3 ms·
>So in essence, all this new API is mostly buying you is offline mode. There's been, for a long time, local storage APIs. This is filesystem access, which is
by snvzz 6y ago
>So in essence, all this new API is mostly buying you is offline mode.
There's been, for a long time, local storage APIs.
This is filesystem access, which is very different.
- chromedev 6y agoWhich has policies that can be enabled to block it if necessary
- snvzz 6y agoUsers click "accept" to make things work. Filesystem access is going to have nefarious consequences.
- chromedev 6y agoThat's not how policies work. Schools, organizations and even home users can enable policies to block this feature altogether as well as many others: https://cloud.google.com/docs/chrome-enterprise/policies/ https://cloud.google.com/docs/chrome-enterprise/policies/
- emteycz 6y agoI'd like to see that ordinary user that is configuring API usage policies on their home network
- im3w1l 6y agoI think adding a virtual file system to the local storage API's might be fine. One which cannot be mounted easily by non-technical users but has a viewer which allows dragging files into and out of it.
- lioeters 6y agoI vaguely recall something like that, a virtual file system using browser local storage. A search yields: > BrowserFS is an in-browser file system that emulates the Node JS file system API and supports storing and retrieving files from various backends. https://github.com/jvilk/BrowserFS https://github.com/jvilk/BrowserFS It supports storage backends such as: in memory, LocalStorage, IndexDB, HTTP, or the FileSystem API.