Quote:
Originally Posted by Llamatron
Ok. I'll make sure it works with #1 and #2 enabled, then test with them disabled to make sure the captcha-every-5-minutes spam is gone for the out-of-the-box default setup.
|
It looks like switching free accounts enables back-to-back downloads on the same IP.
I tested with #1 and #2 both
unchecked (before starting a ul.to download). So:
- uncheck #1 and #2, before the captcha got displayed for the next ul.to link (to make sure these options would be in effect for this download, to control behaviour at the end.)
- start a download of a 431MiB file
- download finishes after about 1:50, so I'd normally have a 1:10 wait time
- JD2 tries to download the next ul.to file right away: a captcha pops up
- I solve it (fairly sure I got it correct), but the DL doesn't start after the 30 sec countdown finishes. I think this captcha was for a download with the same account that just finished, as that explains being blocked.
- ANOTHER captcha pops up. (I assume from the other account)
- I solve it, and the download starts!
file timestamps to prove I started 2 downloads less than 3 hours apart:
stat file*
File: ‘file1’
...
Access: 2015-03-28 20:25:53.000000000 +0000
Modify: 2015-03-28 22:11:14.345000000 +0000
...
File: ‘file2.part’
Access: 2015-03-28 22:12:26.558114581 +0000
Modify: 2015-03-28 22:31:15.048090417 +0000 # now
...
Since I mount my filesystems with noatime, "Access" is set when the file was first created, and not changed after. "Modify" records the last write. For file1, which finished, the mod time is when the DL finished (the last write.)
And a log, in case anyone wants to check which account actually got used:
28.03.15 17.22.18to28.03.15 18.21.24 jdlog://2233917486241/
And yes, I'm 100% sure my IP did not change. Other downloads stayed running, and my IP right now is the same as it always is.
The plugin options/help should probably suggest making multiple ul.to free accounts, since it seems to work perfectly. Probably each account has its own 3h timer.
Also, I will test with only a single free account enabled, to see how bad the captcha spam is. With a single free account, the 3h from
start of previous download wait-time calculation should probably just be on by default, and not marked as experimental. I don't think switching between a free account and unregistered helped at all for ul.to.