4 ms·
I'd switch if they would support the File System Access API. It's a really convenient API and IMO as someone who has worked with it extensively, is very secure.
by slaymaker1907 3y ago
I'd switch if they would support the File System Access API. It's a really convenient API and IMO as someone who has worked with it extensively, is very secure. It supposedly has privacy concerns, but I think it would primarily be used for FOSS and hobby projects since Bigco likes to store all the data on their servers anyways, that's a feature and not a bug for them. In fact, I think it would be a security/privacy improvement since it would encourage storing data locally (privacy) and is way more secure than asking users to install a native app (which has access to pretty much everything on the device and not just the directory/file a user gives it access to).
- Andrews54757 3y agoThis! It is frustrating that web apps like draw.io can't save to file directly using Firefox. It gets old having to save a new file every time you make a change. Beyond that, the File System API would also allow for streamed downloads directly from the web-app. This would allow for web-apps to generate large download files without having to store a copy on a database (external server or IndexedDB), which is a privacy improvement. The only way to do this now is by using convoluted techniques to essentially do a MITM to a fake endpoint [1]. [1] https://github.com/jimmywarting/StreamSaver.js https://github.com/jimmywarting/StreamSaver.js
- squigz 3y ago> It supposedly has privacy concerns, but I think it would primarily be used for FOSS and hobby projects since Bigco likes to store all the data on their servers anyways Privacy concerns don't only apply for entities of a particular size