filestash

Having a path for a shared filesystem to be used by agents with strict access control is something I've been working on with my oss work: https://github.com/mickael-kerjean/fdrive, and https://github.com/mickael-kerjean/filestash

I have been working on exactly this with Filestash (https://github.com/mickael-kerjean/filestash), out of millions of users, 99% of them don't seem to care so much about the malleability, it gets very usefull when a company ask for something that 99.99% of people don't care without having to add yet another setting toggle. A recent example was when supporting gobd compliance deployment which required us to sign logs via a vendor who can deliver a qualified electronic signature for which nobody outside Europe would care about

Malleability is a great answer to avoid the death by a thousand feature where you bloat your software because a company asked for something 99% of your users don't care about. That's the path I went with for my open source work with plugins that can run from a wasm runtime to prevent those from doing crazy things [1]. Unsurprisingly plugins represent more than 10x the code than what the core provides. [1] https://github.com/mickael-kerjean/filestash

Filestash (https://github.com/mickael-kerjean/filestash) has a s3 gateway plugin that I made. It proxy the S3 traffic to any downstream storage: SFTP, FTP, another S3, SMB, NFS, IPFS, ...

That's the path I've been on with my Dropbox alternative [1]. The 80% is the fast core that focus on file management, the remaining 20% is coming via plugins which implement one of core interfaces so you can handle your own storage, authorisation, authentication, custom apps to handle file types, ... Fun fact, there is 10x more code in the various plugins [2] catering to everything than the core code that was supposed to be the 80%, unsurprisingly everyone needed a different 20%. Plus I find it cool that the guy who needed a gobd compliant log system that have ton of properties to keep auditors happy enforcing hash chained signed with rfc3161 does not contribute to making the system shittier for everyone else [1] https://github.com/mickael-kerjean/filestash https://github.com/mickael-kerjean/fdrive [2] https://www.filestash.app/docs/plugi

I am working on making the Dropbox launch first comment a reality: https://github.com/mickael-kerjean/filestash It gives you the Dropbox experience on any storage you want inclusive of FTP but also let you access your Dropbox storage via FTP, SFTP, S3, ...

Same as op, I rewrote away from react my Dropbox alternative (https://github.com/mickael-kerjean/filestash) in vanilla js a couple years back around the idea that components are plain exported functions like this: export default function component(render) { const $dom = xxxx render($dom); } example: https://github.com/mickael-kerjean/filestash/blob/master/pub... the only library in there is rxjs to manipulate events in a functional fashion with no imperative code and everything is composed from those simple component functions. The wasm is used mostly as an interface for plugins to both run apps to display various file types like RAW, PSD, TIFF, CDR, .... as those tend to have better support in C than other languages, and on the server side to have a safe environment to execute plugin code.

> From Windows or Mac, this FTP account could be accessed through built-in software. This is exactly what I've done: https://github.com/mickael-kerjean/fdrive https://github.com/mickael-kerjean/filestash

The premise of the article that "Dropbox was .. a feature, not a Product" is complete nonsense. Remember the infamous FTP guy's top comment during their launch? I have spent almost 10 years working on making that vision a reality [1], and there are entire industries built around some variation of it: digital asset management, managed file transfer, digital preservation software, electronic document management systems, ... [1] https://github.com/mickael-kerjean/fdrive | https://github.com/mickael-kerjean/filestash

A Drobpox like app that works with FTP and every other storage protocol along gateways to access your Dropbox over FTP, SFTP, S3: - the desktop client: https://github.com/mickael-kerjean/fdrive - the web client: https://github.com/mickael-kerjean/filestash

> dropbox clone get off the ground Thats exactly what Im working on: - web client: https://github.com/mickael-kerjean/filestash - desktop sync: https://github.com/mickael-kerjean/fdrive In line with the infamous top comment during their launch, it does of course support FTP as a storage, and the other way around exposing your Dropbox as a FTP server, while supporting theme so you have a similar look and feel as well: https://www.filestash.app/img/screenshots/theme_dropbox.png + tons of stuff Dropbox never did

Yes, it is still PHP. Sync speed is mostly fine though, most of the 'slowness' which Nextcloud is known for comes from the sometimes sluggish web interface. Point a fast WebDAV-compatible file manager [1] at a Nextcloud instance to get a better impression of backend speed. Point it at an image directory and you'll see as many php-fpm processes launched as there are thumbnails to process. [1] https://github.com/mickael-kerjean/filestash is a good web-based example of such a thing, ignore all the guff about needing docker since you can just run the whole thing from a single self-compiled binary. By default it sends some telemetry to the mothership, you can remove that by commenting out the relevant code in server/middleware/index.go, look for the init() function and comment out the endless loop containing telemetry.Flush()

I've got one set aside to play with v4l2m2m. Once that's working, it should improve video encoding support in my OSS project (https://github.com/mickael-kerjean/filestash)

I did work on a plugin system for Filestash leveraging wasm. Plugins made with tinygo were 10x slower than the same code in rust or c compiled to wasm [1] https://github.com/mickael-kerjean/filestash/blob/master/ser...

> even most of Go that way and your code will still run in 20 years While reading this, I was literally working on patching my open source go app [1] because this is what came out of the stdlib in the last few months: CVE-2025-30204, CVE-2026-33487, CVE-2026-25679, CVE-2026-27137, CVE-2026-32280, CVE-2026-32281, CVE-2026-32283, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-39820, CVE-2026-39836, CVE-2026-42499 ref: https://github.com/mickael-kerjean/filestash