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.

Milan Dinić

Ryan Hellyer

Bjørn Johansen

Brian Layman

Stops automated spam while remaining as unobtrusive as possible to regular commenters. <a href="https://geek.hellyer.kiwi/products/spam-destroyer/" rel="nofollow ugc">The Spam Destroyer plugin</a> is intended to be effortless to use. Simply install, and enjoy a spam free website 🙂
<h3>Credits</h3>
<ul>
<li><a href="https://wordpress.org/support/users/omahoung/" rel="ugc">omahoung</a> – Bug reporting</li>
<li><a href="https://wordpress.org/support/profile/stromhalm" rel="ugc">Stromhalm</a> – Bug reporting</li>
<li><a href="http://ocaoimh.ie/" rel="nofollow ugc">Donncha O Caoimh</a> – Developer of Cookies for Comments, functionality of which is incorporated into Spam Destroyer</li>
<li><a href="http://elliottback.com/" rel="nofollow ugc">Elliot Back</a> – Developer of WP Hashcash, functionality of which is incorporated into Spam Destroyer</li>
<li><a href="http://nettsett.no/" rel="nofollow ugc">Marte Sollund and Ingvild Evje</a> – Bug reporting</li>
<li><a href="http://eHermitsInc.com/" rel="nofollow ugc">Brian Layman</a> – Code advice</li>
<li><a href="http://ronalfy.com/" rel="nofollow ugc">Ronald Huereca</a> – JS advice</li>
<li><a href="https://twitter.com/shawngaffney" rel="nofollow ugc">Shawn Gaffney</a> – Bug reporting</li>
<li><a href="http://konstruktors.com/" rel="nofollow ugc">Kaspars Dambis</a> – Bug reporting</li>
<li><a href="http://www.wanderingjon.com/" rel="nofollow ugc">Jon Brown</a> – Added error message filter</li>
</ul>

Spam Destroyer

Kills spam dead in it's tracks. Be gone evil demon spam!

Comment Timeout vs Spam Destroyer