I don't think code sharing code with browsers is even the issue here, the issue is the FTP ecosystem is going away — and surprising quickly for something that used to be so ubiquitous. I've already bumped into several ISP's just flat out blocking all FTP traffic, probably because they didn't know of or care about any ongoing uses for it. With browsers dropping support, it's validity as a protocol is going to quickly go by the wayside. All existing FTP based systems should be ported to HTTPS (and only 'S') at the earliest convenience.
On Fri, Mar 20, 2020 at 5:22 PM Greg Hellings <greg.helli...@gmail.com> wrote: > > > On Fri, Mar 20, 2020 at 2:20 AM David Haslam <dfh...@protonmail.com> > wrote: > >> The writing is on the wall for FTP. >> >> Firefox to remove support for the FTP protocol | ZDNet >> https://flip.it/AY-TTt >> >> How will this trend affect how we design and communicate? >> > > Since we don't use or rely on Mozilla or Chrome code, I imagine it won't > affect much of anything. > > --Greg > >> >> Best regards, >> >> David >> >> Sent from ProtonMail Mobile >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
