- From: Olli Pettay <olli@pettay.fi>
- Date: Thu, 6 Oct 2016 12:05:38 +0300
- To: Feross Aboukhadijeh <feross@feross.org>, "public-webapps@w3.org" <public-webapps@w3.org>
On 10/06/2016 07:41 AM, Feross Aboukhadijeh wrote: > Looks like there is also https://github.com/wicg/writable-files -- this looks quite nice! What's the status of that spec? > That is just an idea. There is no spec yet. > Feross > Blog <http://feross.org/> |WebTorrent <https://webtorrent.io/>|Study Notes <https://www.apstudynotes.org/> > > On Wed, Oct 5, 2016 at 9:21 PM, Feross Aboukhadijeh <feross@feross.org <mailto:feross@feross.org>> wrote: > > The web really needs a proper filesystem to properly compete with native apps. I'd love to make WebTorrent (https://webtorrent.io) use the disk > instead of in-memory storage, but there's no clear cross-browser solution. So, in the meantime, torrent data is stored in memory and lost when the > user navigates to another page. > > Is there an active effort to make this happen? These are the specs I'm currently aware of: > > 1. File API (https://w3c.github.io/FileAPI/ <https://w3c.github.io/FileAPI/>): widely implemented, 92% support > 2. File API (Directories and System) (https://www.w3.org/TR/file-system-api/ <https://www.w3.org/TR/file-system-api/>): Chrome only, deprecated, > 51% support > 3. FileSystem API (http://w3c.github.io/filesystem-api/ <http://w3c.github.io/filesystem-api/>): Meant to replace previous deprecated effort, > Browser support unclear, spec status unclear to me > > Spec #1 is quite good, but it doesn't spec an entire filesystem. Spec #2 would have been sufficient for our use case, but is deprecated. Spec #3 > seems like the best hope. Is that being worked on? > > Feross > Blog <http://feross.org/> |WebTorrent <https://webtorrent.io/>|Study Notes <https://www.apstudynotes.org/> > >
Received on Thursday, 6 October 2016 09:06:12 UTC