Three critiques: 1. Browser auto-completion of forms will break, because that typically uses the form name to identify the data that's expected, and this plugi

Three critiques: 1. Browser auto-completion of forms will break, because that typically uses the form name to identify the data that's expected, and this plugin hashes the form name. 2. The page would not be cacheable, because the hash key changes for each request. 3. The question of form-labels isn't addressed in the plugin. Perhaps the "real fields" do have labels - at least they should - but the negative-captcha fields don't? That would give a clear signal on fields to avoid. If they were to have labels, what label should be used? A dictionary word? That would have usability/accessibility implications.