3 ms·
Thank you. I could've phrased it better, but it was serious. Everyone knows it's unencrypted and HTTP is faster for simple file serving. Right?
by j2d2j2d2 16y ago
Thank you. I could've phrased it better, but it was serious.
Everyone knows it's unencrypted and HTTP is faster for simple file serving. Right?
- kree10 16y agoI wish everyone knew. I also thought FTP was a 20th century relic, until I started doing freelance web development full-time. It turns out FTP is still the preferred (and often only) way to manage web sites with the cheap shared hosting plans that small businesses gravitate to. I started a group on Facebook called "7 Billion Strong Against FTP" to cope. 6,999,999,993 more to go. http://www.facebook.com/group.php?gid=130658460303379 http://www.facebook.com/group.php?gid=130658460303379
- roel_v 16y agoI wish... Part of the problem is that FTP is still built into today's browsers, so many people don't even know that they're using FTP, it's just a link they click. Luckily IE removed support for password in FTP links a few releases ago, but still. HTTP is ok for small files, but I'm often on unreliable links with big files to up/download, and browsers implement 'resume', ehm, let's just say 'not so well' (it's a server thing too, to be honest). Anyway I've used scp for years myself, and I've tried getting others to use it, too; I mean winscp isn't harder than any ftp client. Some would grudgingly accept if I made them, others would just say 'I can't up/download the files'. So I've given up on that part of trying to improve the internet :(