What I’d like to see the dev path of this to go towards is including built in non-enumated/non-mounted files system read/write access to ones cloud providers like google drive, drop box, onedrive and all the others, where there is a particular common protocol use that, but where the protocol use the published web-API of the various providers. Reason a light weight ransomware protective backup solution… also add VSS usage for files that are open in other programs rather than creating a sharing violation or demanding the files be unused during operation… make it something worth the $19 price tag.
Also add the ability to have multiple tabs of multi-copy tasks and definable triggers for activating a particular multi-copy task like installing a callback on a file or folder to call back when the file is modified and trigger the copy process and have an optional number of copies to be held at the destinations so one cannot be caught out by a files ransomware encryption modification triggering the overwrite of the only copy on the cloud storage… The problem with this is purpose? if you define why you are trying to do the multi-copy there are already programs out there that do that purpose better already and just blindly copying to local file system locations is not doing the purpose very well… as there is no integrity check that what you created is still a bit for bit copy of the original and ACL’s are preserved and attributes remain identical to the original etc. verifying has to be done manually externally same for fixing ACLs and files attributes like creation time etc.