WebDAV isn't dead yet

Summary

I should have titled this post "I hate S3". 📢 What is the status quo? FTP is dead (yay), SFTP is too dependent on SSH and unix authentication. AWS made S3 pervasive and now every webapp that needs to store files assumes you'll be able to connect it S3. This is good for Amazon, but painful for everyone else. 📢 But who is WebDAV useful for? Most people working on personal projects, self-hosting, or just need filesystem-over-HTTP-ish capabilities do not need S3, they just need a place for their files behind some form of authentication. I stopped reaching for S3 and started running from S3 a while ago and I think you should consider doing the same. Here are my core requirements: authentication write files efficiently sync files ensure those files aren't publicly accessible by default relatively easy to make those files public Here's what I don't need: advanced ACLs and roles signed URLs versioning (the V in WebDAV is actually versioning, but still...) tiered storage lifecycle rules quotas, but could be done at the filesystem level (e.g., ZFS) many things I can't think of right now This list probably resonates with you as well. I just don't think we should be encouraging people to run Openstack Swift, CEPH, Minio, or unfinished projects like Garage just to achieve file-storage-over-HTTP. And with Minio recently killing off most of their admin UI and making people suffer through crafting JSON policy files and uploading them with the mc tool... just let it go. It's not worth your time. How would you access WebDAV to manage files if you've never tried before? Lots of tools support it: MacOS Finder (Go->Connect to Server... enter https://...) and iOS Files Windows Explorer (Map Network Drive, Connect to a Web site...) rclone curl Popular things like CyberDuck, WinSCP, Filezilla... It's broadly available as you can see even though it's considered by many to be archaic or obsolete. Your webserver that you're running probably already supports it and you just need to integrate a...