One part of the Client Tool makes uploads easier if you’re willing to type a commandline; and if you’re not, a batch file is present to reduce that obstacle (but still no GUI).

In order to reduce the doubtful situation of having an upload without confirmation (for example, in cases where an aborted upload looks just like a completed upload: no checksum either way), the upload functionality now sends the checksum before the actual file. I swapped the uploading of the payload file (-u) and the .sum checksum so that the ~.sum file is present before the payload; in truncated/aborted/chopped uploads, this provides a checksum to validate and prove an inaccurate upload rather than assume meaning from a missing .sum file. Aborted/truncated uploads will still fail to validate against the checksum so look the same as any corrupted upload: incorrect. In either case, the reaction is “ask for a re-upload”, so the reaction to a checksum mismatch remains an immediate re-upload.