Hi gizmore,
First of all, thank you for creating such a great challenge.
However, since this is labeled as a "Training" problem, I wonder if it really needs to be this difficult.
Unless the goal is to reduce the number of people who solve it by making it overly hard, how about increasing the usleep time a bit to reduce the impact of network noise?
To be honest, I’ve been running scripts for quite a long time just to solve this.
Statistically, it seems like I need to call each character over 200 times to get meaningful results.
So, if it's a 12-character password with only uppercase and lowercase letters, that’s 56 × 200 × 12 = 134,400 tests needed.
Of course, I could reduce the time using multiple threads, but it still requires a lot of resources.
I’m trying to solve all the training challenges first before moving on to others,
but I’m spending a lot of time on this one, and it feels like it’s more about using resources than actual problem-solving, which seems a bit wasteful.
Even if the usleep time is increased, I don't think it would be a big issue in the context of a "Training" problem.
Actually, I’m also worried that sending continuous requests to solve this might be putting a burden on the WeChall server.
Anyway, I hope you’ll consider it!