Open DirkGaston opened 1 year ago
@DirkGaston Hmmm. Do your proxies require a username:password to authenticate? When I put this feature together it was built around my proxies which are IP based authentication.
This is what I have typically seen with username/pass auth type setups
protocol://username:password@hostname:port
eg http://user:pass@ip:port
Protocols: HTTP/HTTPS/SOCKS
I am not sure this is an issue or just lack of knowledge from my part, I rather suspect it is the latter, however, I am attempting to recover tweets from an account that has a couple of thousand deleted tweets. I eventually encounter a rate limit error as is to be expected. I saw the way to handle requests like these is to use a proxy file. Now I have a .txt file that I added inside the twayback folder with a list of proxies and formatted according to the guidelines:
url:port url:port url:port
and so on. I keep getting error for each proxy server so Im not sure if Im doing this right and what the issue could be. It will stay stuck at 0%, switch between proxies until it eventually just gives up with a "" error.
My request looks like this:
python3 twayback.py --proxy-file proxyfiles.txt -u USERNAME
Am I doing this correctly?