Description
Apologies if this appears to be repeated but I made a couple of posts in 2 (long) threads yesterday that were closed overnight (without specifically addressing these), so I wanted to put these out there again.
(i) In one of the closed threads TigaNZ wrote:
No, the key assignment shouldn't matter. I had put it on something closer as well because hitting it manually was easier with a closer key, more or less the same as you. What I'm suggesting is missing those 1st recaptchas when you 1st login, even though they are often stupidly wrong... sets you up to get more on the appointment page...which will sabotage an opportunity.
I was just testing the F8 AutoHotKey script after running the 'npm start' (commandline) version of the script with the manual date inputs to the miq-assistance.js script and came across an issue that because the main script run from the cmd window keeps refreshing the MIQ page every 5s (or whatever interval you selected), if you haven't completed the Catchpa on the "Secure Allocation" page within 5 seconds, you miss out actually being able to click next as the Catchpa disappears (i.e. you will lose the spot). Is there some way of getting the script to stop doing the 5s refresh after you get a date hit that matches the dates you put in the miq-assistance.js script?
Apologies if it does actually work like that when it finds your date, I am just unable to test it on actual dates as they come up so seldom.
(ii) I was also wondering if it were possible to add a wee function to randomize the fixed refresh interval between an upper and lower limit so it was not always "exactly" 5s; e.g. if you set 4 and 6 seconds as these U/L bounds and it will (using some random generator), generate a number from 0 to 2 (to 2 sig figs e.g. 0.1, 1.5, 0.8) so that the refresh becomes slightly more random i.e. for those examples, 4.1, 5.5, 4.8 seconds) etc. Just a thought.
Thanks
k.