This is what apps like photoshop.adobe.com and vscode.dev use to let you edit local files - with a fallback of single file access with input/type="file".
I hope Firefox and Safari support this API soon. The alternative of installing native executables isn't any more secure.
from the caniuse data, it looks like Safari might actually be working on this?
Which is both hugely surprising and deeply concerning, given their track record with both implementing APIs and the stability/reliability of them.... The tinfoil hat me in says they might fuck it up to justify the apple ecosystem stance of app store or nothing.
Put down the tinfoil, the WebKit team has been on a tear recently and very actively hiring to keep that momentum and very actively seeking feedback. Regardless of Apple’s priorities, Safari is very much on an improvement track
I think a more justified and nuanced criticism is that Apple is harming the web by tying Safari updates to macOS and iOS updates, which makes the criticism of Safari being the new IE a lot more justified (now that IE has been replaced by the evergreen cross-platform Edge). Safari might get more frequent and broader updates but that's no use when people are still using older versions of macOS and iOS and might be stuck with it (especially with fresh memory of Apple intentionally slowing down iOS devices to encourage buying new hardware).
Safari on macOS is supported two major OSes releases back. The latest iOS is supported on iPhones launched in 2015 and later. How many users on older versions of Safari are limited by OS version?
To some extent this is a fair criticism, and I certainly wish Safari were less tied to OS releases. That said, iOS users tend to update about as quickly as you could hope for (and update hardware often enough that being left behind is uncommon), and macOS users who lag behind tend to use Chrome anyway.
I remember some time ago Firefox denied all the local access as a security issue - despite all the dialogs that asked for rights. Had to find some other ways to access simple txt file - via link.
They didn't even want to give extensions that kind of capabilities (and in the process significantly crippled mass downloaders like DownThemAll and others), so yeah…
I was refering to ability to manipulate local files from Firefox, that existed 6 - maybe 8 years ago - long long time ago, when this filesystem API did not exist.
Most (>80%) of users are highly computer illiterate. Even among younger folks. There has recently been a story on hn about zoomers not "understanding" how file systems work.
Statistically they have a lesser understanding of hierarchical filesystems, because Apple and to a lesser degree Google have been going out of their way to hide that on mobile OSes for some reason that was never really clear to me. They still understand files though.
And at the end of the day there's only so much you can do. The same kind of people that will click yes on any dialog will also click yes on "do you want to run this exe you just downloaded", and that'll get you file system access just fine too.
Yeah hierarchical file systems are not the one true way to organize your data.
But from my understanding, the user grants access via this API on a directory based level when the website asks for access to one directory. If you have no concept of directories, or you put everything directly into one directory, it's tough to make this restriction useful. So in this instance, knowledge of hierarchical file systems is relevant, even if new operating systems make this knowledge increasingly obsolete.
> Yeah hierarchical file systems are not the one true way to organize your data.
It's the way nearly all computers, mobile or not, organize data. Some hide this fact to because they either think they know better than the user (Apple) or they want to make it really painful to not store all of your data in their backend (Google).
> But from my understanding, the user grants access via this API on a directory based level when the website asks for access to one directory. If you have no concept of directories, or you put everything directly into one directory, it's tough to make this restriction useful. So in this instance, knowledge of hierarchical file systems is relevant, even if new operating systems make this knowledge increasingly obsolete.
I think that illiteracy here has more to do with the advent of mobile OSes and people only exposed to mobile devices. Filesystem access isn't supported on mobile browsers at all so there isn't really a problem there (except for mobile Safari, which also doesn't expose folders to users, being on Apple's direct control).
If you’re concerned about users having literally no floor to their technical understanding or awareness, then those users are already vulnerable to websites with a form that says “type your Gmail address and password here.”
Note that, unlike Chrome, Safari only supports “origin private” files which means it cannot be used to access files already on your system (e.g. no vscode.dev, photoshop.adobe.com opening of local files).
The main selling point to me for the file system access api is the ability to write directly to the file system on the device but from what I could understand in that blog post is that the 'files' that you write to don't actually map to the device's fs itself. Has anyone used it to write to an existing directory or is it just an alternative and more familiar interface to indexedDB?
I have been using it to provide ability to read existing markdown notes in a users directory see [1]. So far it works great but browser support is limited to chrome and edge.
I hope Firefox and Safari support this API soon. The alternative of installing native executables isn't any more secure.