14
exerceo
2y

Firefox and Chrome removing FTP support in 2021 was a terrible decision.

Web browsers were simply the more convenient FTP browsers, more than file managers, due to browsers' built-in multimedia capabilities like photo viewing and opening documents, distinct purple highlighting of already opened directories and files, browsing history, familiar mouse shortcuts like middle click for new tab, and no possibility of accidental writes due to a botched drag-and-drop operation or similar.

If I wanted to browse an FTP server in "read-only mode", web browsers used to be the preferred choice.

Comments
  • 4
    I sorta get it though. They are already huge projects to begin with.
  • 2
    If you're using it in read-only mode a FTP is way beyond the actual needs imo.
  • 2
    @Demolishun I have to agree with @zlice on that.

    FTP is a standard protocol that hasn't changed THAT much in 45 years.

    I think it's more along the lines of they can't find developers in their salary wishlist that understand transfer protocols.
  • 7
    Removing FTP was the right thing to do because blasting passwords over the net in clear text is bad, and even anonymous FTP sucks because it opens for MitM attacks on downloaded data, e.g. for inserting malware. FTP should not be used anymore, and download via HTTPS is just as good.

    Removing that crap from browsers at least creates an incentive for content providers to offer HTTPS downloads instead of FTP.
  • 6
    Anyone who likes FTP Support should try and implement a FTP reader.

    The protocol is a nut job - especially nowadays.

    It should be dead.
  • 4
    I like the idea of deprecating FTP. There are much better alternatives. Apaches directory listing is the easier and bettet alternative imo, since that does effectively the same, is easier to set up and also works over HTTPS almost out of the box (letsencrypt).
  • 6
    @zlice that FTP remains unchanged does not mean that the code does not need to be maintained and tested as it is not standalone. It is actually integrated in the browser. And these browsers change a lot. Plus the security things mentioned by @Fast-Nop and on top of that security of the browsers themselves it is yet another attack surface with very little benefit.
  • 1
    @hjk101 Do you suppose the anonymous usage stats told them very few people are actually using FTP? I used to use it all the time. Haven't used it in years.
  • 1
    @Demolishun don't know, have seen a few manuals hosted trough FTP but by far https is the more popular protocol and an alternative for these usecases. When in a pinch my os has a cli client installed already and there are plenty of gui clients available if you really need it. Can probably even add a protocol handler for it in the browser so it opens in it by default.
  • 0
    @McSebi It should have been retained for local use, like creating an FTP server on a smartphone to transfer files. Android applications for this have existed since over a decade. It is widely established.
  • 1
    @joewilliams007 It is widely established, especially on Android OS. Many third-party file managers have integrated FTP servers.

    FTP also needs no built-in user interface like HTTP does. The client software has the user interface.
  • 1
    @exerceo oh im so stupid i knew i was wrong.. i was thinking about tcp which was a nightmare.. let me delete my comment^^
Add Comment