Earlier quoted context omitted.
We made sure that the activation of the API is gated by: 1) User Activation checks 2) When access to the file system is requested, a File Picker is necessary 3) When the API is in use, there are plenty of indication that it's being used We put a lot of thought in Privacy and Security, as we do for all APIs.
> We put a lot of thought in Privacy and Security, as we do for all APIs. but somehow, data is heavily harvested thru browsers(chrome), apps(android). Do you even test your APIs with a sample audience, like real tech ignorant people and see how they are blind to all those and just click yes, and don't care?
The Native File System API allows web apps to save directly to files
61–70 of 155 posts
Re: The Native File System API allows web apps to save directly to files
#62Finally, we can have a local markdown editor with live preview. I just hope it can read files and folders in a particular directory as well, with permission of course.
Sounds like the plan is to make Chrome the OS. Native apps already do things like that.
Any solution that requires you to write a multipage doc for parents and kids, to go follow two different sets of rules depending on devices and install 2 dozen apps, just so they can take class at home, is a non-starter for school districts.
A link is all you need with the Web for most things. No install. No uninstall. No worry about OS.
Ever since the fanboyism between mobile platforms started, people have started worshipping at the church of the native app, which is say, before the Web once broke us away finally from Windows, and now we're back asking people to install heavyweight native apps for things like "Order a Burger" or "Pay a Parking Meter"
Re: The Native File System API allows web apps to save directly to files
#63I mean that was fun for a young budding developer, but I can see the major security issues with this. I really hope this has been thought through.
I can imagine this being another one of those popups that constantly appear on websites - are certain files protected like your hosts file or does it rely upon the access level of the user running the browser?
Re: The Native File System API allows web apps to save directly to files
#64In other words, granting this permission is effectively the same level of severity as downloading and running an app.
Am I missing some extra consideration here?
Re: The Native File System API allows web apps to save directly to files
#65Earlier quoted context omitted.
We made sure that the activation of the API is gated by: 1) User Activation checks 2) When access to the file system is requested, a File Picker is necessary 3) When the API is in use, there are plenty of indication that it's being used We put a lot of thought in Privacy and Security, as we do for all APIs.
If I disable the file system API, can an "is file system API available" check be used as a bit to fingerprint my browser?
Re: The Native File System API allows web apps to save directly to files
#66There is no way this isn't going to open up massive security holes. Even if the browser puts up alert after alert, people are just going to randomly click buttons and then all of a sudden wonder why some random web app is deleting all their files and adding malware. And the spec docs aren't exactly reassuring. This is an exact quote! "This API could be used by websites to try to store and/or execute malware on the us…
It won't work on iPhones, which means no one will use it, I hope.
Re: The Native File System API allows web apps to save directly to files
#67Earlier quoted context omitted.
It's important not to forget about drive-by DLL injection when making the "execution is the problem" argument. Lots of executables on Windows link to DLLs that are not protected by the "KnownDLLs" protection. This means that if you can save a malicious DLL next to that executable you can make a perfectly legitimate executable run malicious code. I haven't read into the API yet to determine how it protects against thi…
> This means that if you can save a malicious DLL next to that executable you can make a perfectly legitimate executable run malicious code. Some people install browsers onto a USB drive -- or even run a browser directly from their Downloads directory. Such people are easy targets for this type of thing.
Re: The Native File System API allows web apps to save directly to files
#68As much as they try to add security to this feature it inherently breaks out of the "sandbox" concept of the browser and scares me.
Re: The Native File System API allows web apps to save directly to files
#69Earlier quoted context omitted.
>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.
Which has policies that can be enabled to block it if necessary
Filesystem access is going to have nefarious consequences.
Re: The Native File System API allows web apps to save directly to files
#70Earlier quoted context omitted.
Sounds like the plan is to make Chrome the OS. Native apps already do things like that.
Native apps are really poor at collaboration and composition. School districts around the world are effortlessly doing distance learning by giving parents and kids URLs, which open Web based editors, science experiments, music and art 'web apps', etc all at one click, without worry about whether the kids own iPhones or Android, or desktops, and whether or not they can install it, or have it installed. Any solution th…
Modern native apps support links, by the way, they just need to be explicitly enabled.
https://developer.apple.com/documentation/xcode/allowing_app...
https://developer.android.com/training/app-links/deep-linkin...
https://docs.microsoft.com/en-us/windows/uwp/launch-resume/w...