Use .ssh instead of .ssh-sync-data. Perhaps add a 'safe' mode

[therealpaulgg]

By 'safe' mode, if the user has keys currently in the directory, provide some kind of interface for the user to allow the user to prevent ssh-sync from overwriting keys.

This may apply to both 'upload' and 'download'

[therealpaulgg]

We should review .ssh-sync-data and make sure that we aren't explicitly deleting files. It would be bad to overwrite files without the user knowing...

Perhaps prompt the user and let them know if a key will be overwritten and the contents are different from what is stored on remote?

Is the config ordered the same each time it is generated, or does the order vary?

Let's use sha256sum to compare current files to new ones & warn