I use WASM extensively in my OSS work with Filestash (https://github.com/mickael-kerjean/filestash ) in 3 main areas:

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

Articles like this shitting on WebDAV really rubs me the wrong way as I've seen first hand discussion that goes like: "internet say WebDAV is hell, what's the better alternative? S3 or course!" And now every cloud provider instead of providing a webdav interface provide an S3 one and it's worse by every possible way, you can't rename a file / folder because S3 does not support that, you can't support a classic username / password authentication mode but are force to use an uggly access_key_id and secret_access_key, can't bash your way around with a simple curl command to do anything because generating the signature requires a proper programming language and you have to trust Amazon to do the right thing instead of going through the RFC process except they've already shown a few months ago their complete lack of care for any s3 compliant server by introducing a breaking change that literally broke the entire ecosystem of "S3 compliant" implementations overnight and without any prior warning.

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, ...

In section 6: "tar files ... of the Linux kernel sources ... version ... 1.99.10 ... are approximately 24MB in size ... Out of the 2441 files in the 2.0.0 release 291 files had changed"

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

because it is "web scale"

ref: https://www.youtube.com/watch?v=b2F-DItXtZs

is there some open source product who can leverage this or this just assume you have to use Microsoft stuff?

The SMB Direct support mentioned here is in the kernel for client & server from 5.15+. After that it's just a mount point any application can access. No Microsoft stuff needed on either side.

This was probably added by/for Tuxera to increase Tuxera Fusion SMB performance.

I think it got added by Samsung / someone employed by Samsung at the time https://www.phoronix.com/news/KSMBD-Lands-In-Linux-5.15

I launched Filestash [1] as my response to the infamous “Dropbox should just be FTP” comment. Once I had a decent FTP experience, I kept going: adding support for pretty much every storage protocol, plugins to expose Dropbox (or anything else) over FTP, SFTP, MCP, or S3, and all the features I wished Dropbox had, with plugins to customize everything.

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] https://github.com/mickael-kerjean/filestash

Where is the dropbox-part in this? This seems to be a filemanager for remote storages, which is kinda the opposite of dropbox, which is mainly a local service for syncing data. Or did the documentation missed explaining the sync-function?

What a blast from the past. I attempted to build a file-sharing tool for my team when we had video and images strewn across the org. I prototyped embedding filestash for the frontend.

It was basically a backend for generating STS credentials on the fly using a more ergonomic interface. It never went anywhere and I haven't thought about it in years, but I still believe it was a good idea that I just didn't have the organizational clout or time to push forward.

Edit: apparently I contributed at some point too? I *barely* remember that. Glad to see the project is still succeeding!

[1] https://github.com/subdavis/workspaces-io

This could probably be more profitable for you with better tagline/explanation!

I have the context for what "that comment" was, might even be in the target audience, yet from the landing page I'm still not entirely sure what it actually does. Might be worth trying a few "it's like X but with Y" or "imagine if dropbox could Z" and other formulations on uninitiated people in your target audience?

I found a typo: "Apply fined grained access control to keep your shared content under control." should be "fine-grained access control".

There: https://www.filestash.app/smb-client.html

The faux screenshot of HN tickled me.

The benefit is "Distribution". If your users are there, you want to address them wherever they already are, this is why apple store / play store / amazon store ... are so popular. Becoming a platform / ecosystem is the common playbook to go from being a one product company to an ecosystem / platform worth a lot more

Can a small business succeed in that game?

I had a X250 who died less than a month after the warranty, now got a E14 since ~2 years and it got keyboard issues

Is this some sort of supabase but with sqlite and without the operational complexity?

Yes that is what it is.