Wow super fast response, thanks Tony!
So In my learning and feeling out, I think I experienced a side-effect of this which you referenced above. I have a Mac Pro which uses the Photo app to collect all of my pictures from phones, tablets, etc etc. Since apple is apple, they do not have native hooks into Photo for anything but iCloud. So I highlighted all of my albums and exported them to the "Amazon Drive" folder, that is, the native client. Well that was terrible, and it was uploading one picture at a time. So, I decided to stop that sync, and I was going to then move them into the odrive Amazon Cloud drive landing point. Well in between the stop and the move, stuff started to get deleted, so only part that didn't get deleted by the native app moved to Odrive. Then, Odrive started to sync and it deleted a bunch of stub folders to make it look like what I believe it truly had locally to sync.
I didn't do much in the way of investigating this. I just re-exported the entire photo library to the odrive landing point and hoped it knew what to do with duplicates...
but I guess the question I have is, when I unsync I have the .cloudf files in place. this means that there is only a stub and the real source file is gone. Now, what happens then the .cloudf file is deleted, since this is what was loaded up in the odrive trash bin? are only local stubs deleted, or are those deletes taking place in amazon cloud drive?
Photos is a good example of how I want to use cloud. My files are already structured in a sense by an application, but I can't natively hook into that app. So, if I wanted to export 2 new photo albums from photo into odrive, it would write the files locally, but once that happens I want the local copies gone. It seems like when I manually issue a sync, like you said, its a full. so yes, it does push everything up that wasn't there but it also pulls everything down that I cleaned off... I'm guessing the backup functionality is going to be my solution to this, because I literally want to lift and shift the data. if I have stubs pointing back, thats all I need, but I don't want to mirror the whole picture library back and forth (Comcast meters now...)