1,586 karma · joined December 23, 2015
github: https://github.com/mickael-kerjean/filestash
link:
https://www.filestash.app/
https://github.com/mickael-kerjean/filestashupdate: done => https://github.com/mickael-kerjean/filestash/commit/d3380713...
As a Frenchman, this stings. I have been working since 2017 in creating an open source alternative to Dropbox (https://github.com/mickael-kerjean/filestash), the reality is out of 60 customers, only 2 are French and most contacts I've had with French entities only shown interest onto open source because they were not willing to spend a dime on anything.
Customers are mostly US entities and other countries in Europe. The gist is our technology is already working accross every possible storage technology and every identity provider, has a clean modern UI, has gateway capabilities to expose your data with open protocols like SFTP, FTP, S3, MCP, with virtual filesystem capabilities that enables a decentralized approach through federation and tons of other advanced setup, is deployed in production in places like US military, MIT, European Commission and many other othher high profile places.
We just launched https://www.filestash.eu a few days ago hoping to talk to people in France who are interested in translating the talk of data sovereignty onto actual actions. If anybody who is reading this is truly interested onto a sovereign Dropbox and is willing to put talks onto a concrete reality, reach out to me, I'd love to talk to you
If anyone involved in this transition read this, please contact us, we already got open source technology to replace box / Dropbox / OneDrive and Gdrive
when the specs for a data representation format evolved with XML bombs abilities, it has gone too far in trying to please everyone, and that is probably why JSON won in the long run, it's not perfect but stable and simple without crazy issues you have to worry about when parsing it. If XML had a Torvaldish kind of dictator who can afford to say no, I doubt JSON would have won
1. creating plugins that get executed in the browser to render files like Parquet, PSD, TIFF, SQLite, EPS, ZIP, TGZ, GIS related files and many more, where C libraries are almost always the reference implementations. There are almost a hundred supported file formats, most of which are supported through WASM
2. creating plugins that get executed in the server to generate your own endpoint or middleware while being sure you can't start exfiltrating data (which can be other people's files, and other sensitive stuff)
3. in the workflow engine to enable people to run their own sandboxed scripts without giving those a blank check to go crazy
1. to create web versions of applications that are traditionally desktop only to render things like Parquet, PSD, TIFF, SQLite, EPS, ZIP, TGZ, and many more, where C libraries are often the reference implementations. There are almost a hundred supported file formats, most of which are supported through WASM
2. to create plugins that extend the backend and add your own endpoint or middleware as a way to enforce the code run in a constrained environment without the ability to send people's file out
3. in the workflow engine to enable people to run their own sandboxed scripts without giving those a blank check to go crazy
(for those who don't know IPFS, I find the original paper fascinating: https://arxiv.org/pdf/1407.3561)
I've done exactly that with Filestash [1] using its virtual filesystem plugin [2], which exposes arbitrary systems as a filesystem. It turns out the filesystem abstraction works extremely well even for systems that are not filesystems at all. There are connector for literally every possible storage (SFTP, S3, GDrive, Dropbox, FTP, Sharepoint, GCP, Azure Cloud, IPFS....), but also things like MySQL and Postgres (where the first level folder represent the list of databases, the second level is tables that belong to a database, and each row is represented as a form file generated from the schema), LDAP (where tree nodes are represented as folders and leaf are form files), ....
The whole filesystem is available to agents via MCP [3] and has been published to the OpenAI marketplace since around Christmas, currently pending review.
ref:
[1]: https://github.com/mickael-kerjean/filestash
[2]: https://www.filestash.app/docs/guide/virtual-filesystem.html
[3]: https://www.filestash.app/docs/guide/mcp-gateway.html https://github.com/mickael-kerjean/filestash/tree/master/ser...
1. to create web versions of applications that are traditionally desktop only to render things like Parquet, PSD, TIFF, SQLite, EPS, ZIP, TGZ, and many more, where C libraries are often the reference implementations. There are almost a hundred supported file formats, most of which are supported through WASM: https://github.com/mickael-kerjean/filestash?tab=readme-ov-f...
2. to create plugins that extend the core application. As of today, you can add your own endpoint or middleware in Filestash, package it with its own manifest, and run server-side code in a constrained environment. For example, there is a libreoffice wasm edition that can run from your browser but requires a couple HTTP headers to be sent by the server to work so the plugin has this bit that run server side to add those HTTP headers: https://github.com/mickael-kerjean/filestash/blob/master/ser...
3. in the workflow engine to enable people to run their own code in actions while ensuring they can't fuck everything up
I hope WebDAV had a better reputation, it carries the original promise of s3 of being actually simple but S3 won the war with evangelism. I would much have preferred a world where new version of the webdav protocol are made to address the quirks exactly like what happened with protocols like http, oauth, ...
It never crossed my mind Linux at some point only had 2441 files and you could actually parse the code that went through a new version, that time has sailed
The base product is open-source and I make money from custom builds, additional plugins, paid support, and the occasional extra feature for companies with specific needs. It's a bit more than noodle profitable but quite under a normal salary.
1) find the command it uses with describe-keybinding, you find the command "save-buffer"
2) "describe-command save-buffer" brings you onto the lisp world where it is defined => "files.el"
3) want to know how a variable is define within files.el? "describe-variable buffer-file-name" and now you are in C territory
4) rinse and repeat with some describe-function when needed
5) get lost onto the beauty of emacs which in my opinion is its interactive / self documenting nature which unfortunatly is not more common in all the software we use