4 ms·
I think this is a bad idea - many URLs are encoded as ftp still, e.g. when downloading tarballs, zips and such - does this mean clicking on an FTP URL now will
by martin1975 5y ago
I think this is a bad idea - many URLs are encoded as ftp still, e.g. when downloading tarballs, zips and such - does this mean clicking on an FTP URL now will require launching an external ftp app instead of downloading the file? I'm ok if FTP browsing is suspended through the browser, but abandoning FTP altogether in the browser is a bad idea. It's an old protocol and still very useful, albeit not in its unencrypted state maybe, but it does do a good job of what it's supposed to - namely, transfer files.
- 542458 5y agoI’m not sure I buy that there are that many links encoded as FTP that you’d hit during normal browsing. Chrome dropped support a year or so ago, so any website depended on FTP already has required a separate FTP client for 85% of users. It also doesn't really do a good job of transferring files - the protocol is slow and is incompatible with lots of firewall setups.