Google Plans to Deprecate FTP URL Support in Chrome

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.

Re: Google Plans to Deprecate FTP URL Support in Chrome

#7

Post by chungy » Sat, Aug 17, 2019, 3:20 AM UTC

TylerE wrote: post #5

Not bothered by this. No one should be running FTP in 2019. It sends passwords in plain text for christ's sake.

It's kind of ok for anonymous downloads, but then, HTTP is even better for the purpose.

Re: Google Plans to Deprecate FTP URL Support in Chrome

#8

Post by morpheuskafka » Sat, Aug 17, 2019, 3:23 AM UTC

I'm personally fine with this. FTP is a different protocol, just like BitTorrent. It's not part of the modern web, so it's just another loose end to tie up. Even though it will be around for a while, it's not relevant to Chrome's user audience/usecase.

Re: Google Plans to Deprecate FTP URL Support in Chrome

#9

Post by georgebarnett » Sat, Aug 17, 2019, 3:23 AM UTC

subsubsub wrote: post #4

Google 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?

Re: Google Plans to Deprecate FTP URL Support in Chrome

#10

Post by jedisct1 » Sat, Aug 17, 2019, 3:23 AM UTC

TylerE wrote: post #5

Not bothered by this. No one should be running FTP in 2019. It sends passwords in plain text for christ's sake.

All modern FTP servers support TLS.