Just a thought, if somehow you are implying this is the case:
https://support.jdownloader.org/Know...cked-by-google
I can assure you this in no way has any relationship with what is going on.
Unless using Google's public DNS (for IPV6, too) is what you meant by their "way" of detecting me. If that's the case the reason I do this is due to some websites being blocked by ISPs and this is how I "fix" that.
I went to my ISP modem to change the DNS to Google's, so ALL machines are relying on it.
OpenDNS and others are not worth because where I am they are slower than Google (articles say the same), no question about it (perhaps not too bad if you live close to them).
Still, that wouldn't account for this issue. Same for changing my MAC address.
It's funny to even suggest that, considering that JDW can download hundreds of gigabytes, except the links we are complaining.
And you seem to ignore the fact that other user is 100% different from me in every regard, starting with the IP address he uses it.
There's also this crucial detail: I always run CCleaner and erase every possible trace. I even do that in the Opera browser which had those cookies exported to JDW.
In fact, I just did this again half an hour ago. Restarted everything. Cleaned all devices this way. Had to log here again after.
Google couldn't possibly be detecting me through JDownloader. And if they were, you would suggest me to format this hard drive, because that would get rid of the "trace", too. Or check Java, anything of the sort.
So far you only said you believe in the evidence, not what you think is going on.
It defies logic that Google can make use of their resources to "detect and block automated tools" like yours, in this fashion.
The minute you change your dynamic IP and tries another link from another account this should never happen. Especially if it's the 1st attempt.
I was thinking you were going to suggest some modification in JDW's advanced settings. Which it wouldn't make sense, it would indicate default ones are not working for this goal.
What all of this looks like is that I and that user either have a very bad luck with * specific * Google links or your computer is the lucky one, capable of making this work.
I am going to stick with "Occam's Razor" principle which states that the simplest explanation is preferable to one that is more complex. Simple theories are easier to verify. In other words, we should avoid looking for excessively complex solutions to a problem, and focus on what works given the circumstances.
I suggest you try elsewhere and not in your own system because the only odd result here is yours saying these old/resourcekey links are working as they should.
Probably your computer is the one "rigged", not ours to affirm the plugin is broken. Your way of testing and checking is flawed.
One user says it could not download (and had no GD account configured in JDW), and I say the same even after ADDING one.
We can't be both wrong and you correct.