Remove FTP uploader and make FTPv6 default

[Junction10]

Is there any need for the FTP uploader?

I'm seeing a lot of colleagues complaining to their mobile providers about not being able to FTP (I was one of them) and it turns out mobile providers are moving accounts over to IPv6 from IPv4 and we're finding out that we can't connect when tethered via a mobile device, to picture desk FTP servers..

Since FTPv6 supports both IPv4 AND IPv6 - surely the default FTP uploader is now redundant? Could it therefore be removed and just replaced with the FTPv6 uploader - OR - enable IPv6 support in the standard FTP uploader?

Thanks.

PS: A handy way of moving FTP connections over to FTPv6 connections would be a welcome addition!

[Bob M]

Please don't do this.

[Junction10]

Can I ask why?

Everything g is moving toward IPv6 anyway so it needs to be supported at some point…

[Kevin M. Cox]

Is there any documentation about what is different between the two FTP uploaders?

[Odd Skjaeveland]

Everything g is moving toward IPv6 anyway...

Allegedly since the turn of the century, but I'll bet IPV4 will be here for at least another two decades. I hope PM's FTP client is not being removed.

[Junction10]

There's no doubt IPv4 WILL still be here in a couple of decades.. but that doesn't mean that the majority of networks will still be using it..

The fact is, more and more mobile networks are making the switch to IPv6 NOW..  and that's causing compatibility issues with the default FTP uploader...

Since the FTP v6 uploader is backward compatible with IPv4 anyway, what's the point in keeping the old FTP uploader?

It's like people arguing against BluRay media because DVD's will still be around in 10 years, when you can play DVDs on a BluRay player but not DVDs.   

[Bob M]

Don't break my presets.

[Junction10]

Don't break my presets.

To be fair Bob, that is the only downside I know of for this request, which is a bummer - but I'm sure it would be simple enough for CameraBits to implement an option to port the FTP presets into the FTPv6 presets... Everything else is identical, afaik.

I did all mine manually when I switched over and yeah, it was a pain, but at least it got me working again when trying to file images remotely.

At some point, this switch is going to HAVE to happen anyway..

[Jan]

To be honest this might be true for the Internet but what about local networks? Here IPv4 will stay much longer and I know still some newspapers how also run internal FTP-Server because thiere Software is still old but working.

[Junction10]

The FTP V6 uploader still supports IPv4, so no issue there.

I mean - think about it..  aside from possibly having to manually re-enter the connections - if Camera Bits can’t implement a feature to automate that (it’s only a slightly different format of the config file so you can do it yourself if you can use a text editor!), there are NO downsides to making the FTP V6 uploader the default and deprecating the standard uploader..

FTP v6 uploader supports ipv4 AND ipv6, the standard one only supports ipv4..

What’s to lose?

[MNeipris]

A workaround suggestion:

File-->Upload... (Command-Control-U on MacOS or Control-Alt-U on Windows) will open the previously used uploader template in the File Uploader window.

So if you:

1. Open the File Uploader window
2. Set the "Selected Uploader:" to FTPv6
3. Select the Close button

The next time you use Command-Control-U on MacOS or Control-Alt-U on Windows, the File Uploader window will open to the FTPv6 uploader template.

The right click(Control-click on MacOS)-->Upload option in the Contact Sheet and the "Save, Upload, and Advance" button in the Metadata (IPTC) Info window also open the File Uploader window to the previously used uploader template.

[bfeinzimer]

I've had problems FTP'ing from the back of multiple Canon cameras over FTP when hotspotting to an iOS device on T-Mobile in Los Angeles, it was explained that it was due to the network being IPv6. On that same token, FTP (legacy) uploader has still worked on that hotspot T-Mobile connection. Where did you see it not working?