Open M1L4 opened 7 years ago
[Idea Update] I looked a little into this. And after verifying the current implementation, another idea suggested itself. AccountManager already writes socks connections to file. If upgraded instead of holding a single socks object, Account could hold a socks list and maybe sort them according to how probable a connection is. The only open thing then, would be the test vs other accounts. That thought might be not fully well-conceived. I'll added it for discussion :)
I already whined a little about how difficult it is using proxies (see #89). There is an additional complexity to the problem. While not knowing how bot detection works in PRO, I had following scenario:
[scenarios]
[conclusion]
[feature | use case] So I would like to suggest a ProxyManager of some sorts:
[example] I currently use a text file to handle proxies. It's setup in a way that a parser could interpret. It looks like this:
Keeping them in the file and not removing them allows us to just throw a handful of new proxy adresses into the ||queue|| section: