If you have spam comment this may be because you allow unhautenticated anonymous users to post comments.
1/ Disallow comment for unhautenticated anonymous users. But you probably don't want to do that.
2/ If this is not the case and if the bots are not black bots that pretend themselves to be Mozilla or whatever, an elegant way would be to only tweak the .htaccess file http://en.linuxreviews.org/HOWTO_stop_automated_spam-bots_using_.htaccess
3/ There are other advanced methods, but you'd have to dig into the code, some suggestions there
Just thought about a more elegant approach of the "honey pot" principle which would be - if your server environment allows it - to have a Web Application Firewall, namelly Mod Security, to handle the false submission (honey pot), instead of putting the load on Q2A for this.
This way you would have very minimal core code hack to do.
More on this here (not tested by myself, but no reason it shouldn't work nicelly)
Welcome to the Q&A site for Question2Answer.
If you have a question about Q2A, please ask here, in English.
To report a bug, please create a new issue on Github or ask a question here with the bug tag.
If you just want to try Q2A, please use the demo site.