Further thoughts pursuant to adapting this to Estel's use case:

- there needs to be a functioning network connection, which we should check before blithely issuing upload commands. If there isn't we ideally should be able to do nothing and fix it opportunistically later.

- ideally, we should be able to cope with a retrospective upload of multiple files if a transfer has failed, or not been attempted due to lack of connectivity. This would strongly favour using rsync, possibly against all photos with today's date. If the images exist on the receiving side, no problem, if they don't then we catch up as many photos as we took today but haven't uploaded yet.

- use of rsync would also permit deletion-on-upload of images, using the --remove-source-file flag. Combining the two would mean "every time a photo is taken, upload and delete from phone any photos having today's date", which might be nice for security-sensitive photography.

- use of rsync over SSH provides encryption and widespread compatibility with most Linux machines, probably easier to use than setting up WebDAV or FTP

- for Joe Average, users need to be warned as to what this will do to their bandwidth if they turn it on and take a hundred photos...