Well, like I said above, I can certainly see that it's not worth the trouble. But again, my point is that if it were a standard feature on every site then it *would* be worth the trouble, and someone would develop software to get around it. If you think of one program running, then a delay of 30 seconds or so per site seems like a big problem. But if you think of multiple threads or processes, or at least being flexible about the order in which things are done, I don't see it as a deal breaker.
But like I said, we'll have to agree to disagree, since the only way to settle it would be for me to develop a spambot, and I'm not going to do that.
Quote:
Originally Posted by Max Taxable
Perhaps it's my misunderstanding, but what's this plugin you have in it, then?
PHP Code:
Time Check - Add Form Hidden Fields register_form_complete
The code there looks like you're adding a false field?
|
I can see where you'd think that from the name of that plugin, but that refers to the hidden form fields used for the timing check. But it might serve the same purpose, since they contain values that have to be submitted with the form and can't be faked. One thing this mod does do (that's probably overkill) is that it generates a hash of the start time, the session id, and a secret string, and puts that in a hidden field. I thought this was an improvement over just putting the starting time, since a smart bot could adjust that to make the submission time seem longer.