Not bothered by this. No one should be running FTP in 2019. It sends passwords in plain text for christ's sake.
SFTP? Not to be confused with FTPS.
Google Plans to Deprecate FTP URL Support in Chrome
11–20 of 350 posts
Re: Google Plans to Deprecate FTP URL Support in Chrome
#12Not bothered by this. No one should be running FTP in 2019. It sends passwords in plain text for christ's sake.
The same could be said for HTTP... FTPS and SFTP do exist.
That said, I agree that its outmoded today.
Re: Google Plans to Deprecate FTP URL Support in Chrome
#13Google don't want users, they want pliant consumers. The idea that young people know more about tech than their parents will become less and less true in the future.
Both of those may be true, but does it have anything to do with ftp going away? It's a pretty bad protocol that's rarely used, why should browsers still support it?
Re: Google Plans to Deprecate FTP URL Support in Chrome
#14Isn't it clear to everyone now that HTTP is the new IP and TCP? That all future protocols will subsist on a web tech substrate? Is that such a bad thing? The vocabulary of URLs and cookies is much richer and less centralized than the vocabulary of port numbers and connection tuples.
Why should we keep FTP or other legacy non-HTTP protocols around? What are we buying? Slightly lower connection setup byte counts?
Re: Google Plans to Deprecate FTP URL Support in Chrome
#15Google don't want users, they want pliant consumers. The idea that young people know more about tech than their parents will become less and less true in the future.
Why do we need a separate legacy protocol for file transfers? What’s the benefit in keeping protocols for the sake of it?
We need a protocol for file transfers because having a protocol makes it more standardized and interoperable than if everyone rolls their own solution.
Do we need browser support for it? It still happens now and then that a link will have an ftp target. That could be handled in the browser or it could open a separate url-handling application, as e.g. email or magnet urls do.
Re: Google Plans to Deprecate FTP URL Support in Chrome
#16Not bothered by this. No one should be running FTP in 2019. It sends passwords in plain text for christ's sake.
No one really uses FTP to transmit anything secret or confidential. Most of the time the password to that FTP server is just "guest" and the same file can also be retrieved by HTTP without authentication.
You would think that no one would, in 2019. I hope that you never have to witness otherwise.
Re: Google Plans to Deprecate FTP URL Support in Chrome
#17Google don't want users, they want pliant consumers. The idea that young people know more about tech than their parents will become less and less true in the future.
Use a proper client like Filezilla for this and go over SFTP, no reason for FTP these days and even less so in a browser.
Re: Google Plans to Deprecate FTP URL Support in Chrome
#18After this change, will Chrome still be able to support FTP through extensions?
Re: Google Plans to Deprecate FTP URL Support in Chrome
#19Not bothered by this. No one should be running FTP in 2019. It sends passwords in plain text for christ's sake.
No one really uses FTP to transmit anything secret or confidential. Most of the time the password to that FTP server is just "guest" and the same file can also be retrieved by HTTP without authentication.
I work at a bank (opinions my own) and nearly everything we do (including modernization, but especially partnership communications) is FTP-based. It's just about the only real standard available when the code is older than most of the devs. We do use modern encryption and mutual TLS to authenticate and encrypt everything, including before password transmission when that's even an option, but FTP is still the backbone of a ton of big older businesses.
Re: Google Plans to Deprecate FTP URL Support in Chrome
#20chrome is a joke