The Register: Not just deprecated, but deleted: Google finally strips File Transfer Protocol code from Chrome browser. “The Chromium team has finally done it – File Transfer Protocol (FTP) support is not just deprecated, but stripped from the codebase in the latest stable build of the Chrome browser, version 95.”
Ghacks: Firefox 90 won’t handle FTP sites anymore. “Mozilla announced today that Mozilla’s Firefox web browser won’t support the FTP protocol from Firefox 90 onward. It was clear that FTP support would be removed from the browser, but it was not clear until today when that would happen.”
The Register: Firefox to burn FTP out of its browser, starting slowly in version 77 due in April. “Firefox has decided it’s time to burn the browser’s FTP connections. In a March 19 post on the mozilla.dev.platform list, developer Michal Novotny announced ‘We plan to remove FTP protocol implementation from our code.’”
Ubergizmo: Chrome Will Soon Stop Supporting FTP Connections. “We’re not sure how many of you might remember, but back in the day, FTP servers were a popular way to host files online as well as to download them. These days, file hosting and downloading is done in a completely different manner, which is why it’s not surprising that Google has ultimately decided that they will soon stop supporting FTP connections in Chrome.”
Amit Agarwal, who is just on a roll this week: How to Keep your Folders on FTP Server and Google Drive in Sync. “The only issue with using a desktop application is that it needs to be run manually on your computer. Wouldn’t it be nice if you could set up a task that continuously monitors your Google Drive (or Dropbox or OneDrive) for new files and automatically copies them to a specified FTP server?”
Hongkiat: Free FTP Clients and Alternative Ways to Transfer via FTP. “When it comes to transferring large files over the internet, FTP/SFTP is what almost everyone prefers. Although there are a lot of paid FTP (File Transfer Protocol) applications that are highly reliable and do the job, it is always a good idea to keep a couple of free FTP services as an option.”
Naked Security: Chrome to brand FTP as “not secure”. “On 14 September, it was announced in a Chrome developers group that Chrome will mark FTP (File Transfer Protocol) resources in the address bar as ‘not secure.’ The change is expected to be made by the release of Chrome 63 in December 2017.” Good. It’s 2017, don’t use FTP. GoAnywhere’s got an overview on the differences between SFTP and FTPS.
From Six Revisions: The five best FTP clients. I’ve been using FileZilla for years, it’s good stuff.
The ResearchBuzz Firehose is regular RB content presented as individual posts.
For digest-type posts a couple of times a day, please visit ResearchBuzz.
Want to know how to best use the Firehose for content discovery?
Check out this handy article.