jammycakes

This plugin extends the comment closing functionality in WordPress to allow 
you to extend the discussion time when older posts have recent comments 
accepted, or to override the comment closing time on a post by post basis.
Note: PHP 4 is no longer supported. As of version 2.1, Comment Timeout requires PHP 5.2 or later. 
If you are still using PHP 4, you should use Comment Timeout 2.0.1.
<h3>Configuration</h3>
You can change various settings globally on the “Comment Timeout” page under the 
“Options” tab on the WordPress dashboard. Most of the options are fairly 
self-explanatory.
You can also change options on a per-post basis by looking for the 
“Comment Timeout” section in the sidebar of the post or page editor.
<h3>Template tags</h3>
Comment Timeout 2.1 introduces two new functions that you can use in your theme:
<pre><code>get_comment_timeout()
</code></pre>
Returns the UTC time, as a Unix timestamp, when comments will be closed for the current post.
<pre><code>the_comment_timeout($relative, $dateformat, $before, $after, $moderated)
</code></pre>
Formats and displays the date and time after which comments will no longer be 
accepted on this post. Parameters are:
<ul>
<li>$relative: Set this to <code>true</code> if you want to display the date in terms of the time remaining 
(for instance “in 3 weeks”). Set it to <code>false</code> to display it as an absolute date.</li>
<li>$dateformat: The format in which the date should be displayed, as used by the PHP 
date() function. If you set this to <code>false</code>, it will use the date format that you have configured 
globally for your WordPress installation.
<ul>
<li>If <code>$relative</code> is set to <code>true</code>, this parameter is ignored.</li>
</ul>
</li>
<li>$before: The HTML to insert before the date that comments will be closed.</li>
<li>$after: The HTML to insert after the date that comments will be closed.</li>
<li>$moderated: The HTML to display when late comments are being sent to the moderation queue 
rather than being rejected outright.</li>
</ul>
<h3>Development and reporting bugs</h3>
When reporting bugs, please provide me with the following information:
<ol>
<li>Which version of Comment Timeout you are using;</li>
<li>Which version of WordPress you are using;</li>
<li>The URL of your blog;</li>
<li>Which platform (Windows/IIS/PHP or Linux/Apache/MySQL/PHP) your server 
is running, and which versions of Apache and PHP you are using, if you 
know them;</li>
<li>The steps that need to be taken to reproduce the bug.</li>
</ol>
If you wish to get hold of the latest development version, or to contribute 
bug fixes or new features, you can clone the project on GitHub:
<pre><code>git clone git@github.com:jammycakes/comment-timeout.git<h3>Redistribution</h3>
</code></pre>
Copyright (c) 2007-2013 James McKay 
http://jamesmckay.net/
Permission is hereby granted, free of charge, to any person obtaining a copy 
of this software and associated documentation files (the “Software”), to deal 
in the Software without restriction, including without limitation the rights 
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
copies of the Software, and to permit persons to whom the Software is 
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
<h3>For more information</h3>
For more information, please visit the plugin’s home page:
https://github.com/jammycakes/comment-timeout

Comment Timeout

Closes comments on blog entries after a user-configurable period of time, with an option to make allowances for active discussions.

webvitaly

kudlav

This is fork of successful Anti-spam plugin v5.5 written by webvitalii, for more info visit <a href="https://github.com/kudlav/anti-spam/" rel="nofollow ugc">GitHub Fork</a>. 
From version 5.6 maintained by kudlav.
<ul>
<li><a href="https://github.com/kudlav/anti-spam/" rel="nofollow ugc">GitHub</a></li>
</ul>
Anti-spam Reloaded plugin blocks 100% of automatic spam messages in comments section and also blocks all trackbacks.No captcha required.
Plugin is simple and easy to use: just install it and it just works.
Blocked comments can be stored in the Spam area and converted to regular comments if needed.
Anti-spam Reloaded plugin is GDPR compliant and does not store any other user data except of the behaviour mentioned above.
Plugin blocks spam only in comments section.. 
Plugin does not block manual spam (submitted by spammers manually via browser).
<h3>Compatibility</h3>
All modern browsers and IE11+ are supported. 
Anti-spam Reloaded plugin works with disabled JavaScript. Users with disabled JavaScript should manually fill current year before submitting the comment.
Server compatibility:
<ul>
<li>WordPress 3.3 – 6.5</li>
<li>PHP 5.6 – 8.2</li>
<li>Doesn’t use jQuery</li>
</ul>
Plugin is incompatible with:
<ul>
<li>Disqus</li>
<li>Jetpack Comments</li>
<li>AJAX Comment Form</li>
<li>bbPress</li>
</ul>
If site has caching plugin enabled and cache is not cleared or if theme does not use ‘comment_form’ action 
and there is no plugin inputs in comments form – plugin tries to add hidden fields automatically using JavaScript.
<h3>How does it work?</h3>
The blocking algorithm is based on 2 methods: ‘invisible js-captcha’ and ‘invisible input trap’ (aka honeypot technique).
<h4>‘invisible js-captcha’</h4>
The ‘invisible js-captcha’ method is based on fact that bots does not have JavaScript on their user-agents. 
Extra hidden field is added to comments form. 
It is the question about the current year. 
If the user visits site, than this field is answered automatically with JavaScript, is hidden by JavaScript and CSS and invisible for the user. 
If the spammer will fill year-field incorrectly – the comment will be blocked because it is spam.
<h4>‘invisible input trap’</h4>
The ‘invisible input trap’ method is based on fact that almost all the bots will fill inputs with name ’email’ or ‘url’. 
Extra hidden field is added to comments form. 
This field is hidden for the user and user will not fill it. 
But this field is visible for the spammer. 
If the spammer will fill this trap-field with anything – the comment will be blocked because it is spam.

Comment Timeout vs Anti-spam Reloaded