ACD BAN/Alternatives discussion (error HTTP code 429)

I did not have much time, therefore it is ugly, but just works.

recursive sync directories:

find ~/odrive-agent-mount/ -type f -name "*.cloudf" -exec python "$HOME/.odrive-agent/bin/odrive.py" sync "{}" \;

Since this just syncs only one layer, you need to call this multiple times, until you have reached the max-depth of your directory structure.

Since I didn’t know and didn’t want to know about my depth or structure, I just went with the brute force approach.

this script: https://pastebin.com/KDB1XVYR

#!/bin/bash
find ~/odrive-agent-mount/ -type f -name “.cloudf" -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name "
.cloudf” -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name “.cloudf" -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name "
.cloudf” -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name “.cloudf" -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name "
.cloudf” -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name “.cloudf" -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name "
.cloudf” -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;
find ~/odrive-agent-mount/ -type f -name “*.cloudf” -exec python “$HOME/.odrive-agent/bin/odrive.py” sync “{}” ;

I had to call it twice. Once everything is synced find should not detect any “cloudf” files anymore and no output should be generated by the script anymore.

Now you have all directories with tons of “*.cloud” files, which represent your files.

I just launched screen and ran this call three times in parallel.

find ~/odrive-agent-mount/ -type f -name “*.cloud” -exec python “$HOME/.odrive-agent/bin/odrive.py” sync {} ;

Edit: It seems performance is a little bit flacky per file, since ACD stores them on different servers. Currently I am using 4 threads on eu-west-1c to get a more stable download stream.

At first it may complain about some cloud files missing, but once the three threads get out of sync enough, this should not be an issue anymore.

Once the three threads are finished, I am going to call it once again to get anything which may failed.

To verify everything is downloaded check for cloud and cloudf files when finished.

find ~/odrive-agent-mount/ -type f -name *.cloud
find ~/odrive-agent-mount/ -type f -name *.cloudf

Both should not report anything when you have finished syncing.

3 Likes