Earlier quoted context omitted.
It's the only standard for file transfer we have, and it can be secure. Why does it have to die? (NOTE: WebDav has even more issues but that's the only other standard.)
> It's the only standard for file transfer we have No, its not. > Why does it have to die? Because its problematic in a whole lot of ways, and FTPS doesn't help much for most of them. [1] identifies a lot of them (in the context of implementing a MacFUSE filesystem, but the issues apply to most applications.) > (NOTE: WebDav has even more issues but that's the only other standard.) You keep using that word "only"; I…
What I'm saying is, that doesn't matter. It's still the most common and easiest to set up for a novice user. Trust me, I don't enjoy reading obscure RFCs on FTP's UTF8 encoding.
I'm using FTP/FTP-SSL because it's the easiest and most common for the end user. FileZilla Server does not support SFTP.
The goal of the project is simple: Let the average tech-savvy person use their own private server to sync. So it needs to be simple and free: FileZilla Server backend (runs on Windows or Linux) and IQBox front-end. I'm open to ideas but I think that's the easiest option.
Even a QNAP will support FTP out-of-the-box.
HTTP-1.0 was a mess. POP3 was a mess. All these protocols were insecure and evolved because software makers put up with their madness and made great software.