error

Welcome to a whole new way of keeping your blog, forum, guestbook, wiki or 
content management system free of link spam. Bad Behavior is a PHP-based 
solution for blocking link spam and the robots which deliver it.
Thousands of sites large and small, like SourceForge, GNOME, the U.S. 
Department of Education, and many more, trust Bad Behavior to help reduce 
incoming link spam and malicious activity.
Bad Behavior complements other link spam solutions by acting as a gatekeeper, 
preventing spammers from ever delivering their junk, and in many cases, from 
ever reading your site in the first place. This keeps your site’s load down, 
makes your site logs cleaner, and can help prevent denial of service 
conditions caused by spammers.
Bad Behavior also transcends other link spam solutions by working in a 
completely different, unique way. Instead of merely looking at the content of 
potential spam, Bad Behavior analyzes the delivery method as well as the 
software the spammer is using. In this way, Bad Behavior can stop spam attacks 
even when nobody has ever seen the particular spam before.
Bad Behavior is designed to work alongside existing spam prevention services 
to increase their effectiveness and efficiency. Whenever possible, you should 
run it in combination with a more traditional spam prevention service.
Bad Behavior works on, or can be adapted to, virtually any PHP-based Web 
software package. Bad Behavior is available natively for WordPress, MediaWiki, 
Drupal, ExpressionEngine, and LifeType, and people have successfully made it 
work with Movable Type, phpBB, and many other packages.
Installing and configuring Bad Behavior on most platforms is simple and takes 
only a few minutes. In most cases, no configuration at all is needed. Simply 
turn it on and stop worrying about spam!
The core of Bad Behavior is free software released under the GNU Lesser General 
Public License, version 3, or at your option, any later version.
<h3>Release Notes</h3>
<h4>Bad Behavior 2.2 Known Issues</h4>
<ul>
<li>
Bad Behavior 2.2 requires MySQL 5.0 or later and PHP 5.2 or later.
</li>
<li>
CloudFlare users must enable the Reverse Proxy option in Bad Behavior’s 
settings. See the documentation for further details.
</li>
<li>
Bad Behavior is unable to protect internally cached pages on MediaWiki. 
Only form submissions will be protected.
</li>
<li>
When upgrading from version 2.0.19 or prior on MediaWiki and WordPress, 
you must remove the old version of Bad Behavior from your system manually 
before manually installing the new version. Other platforms are not 
affected by this issue.
</li>
<li>
Bad Behavior on WordPress requires version 3.1 or later. Users of older 
versions should upgrade WordPress prior to installing Bad Behavior.
</li>
<li>
On WordPress when using WP-Super Cache, Bad Behavior must be enabled in 
WP-Super Cache’s configuration in order to protect PHP Cached or Legacy 
Cached pages. Bad Behavior cannot protect mod_rewrite cached (Super Cached) 
pages.
</li>
<li>
When using Bad Behavior in conjunction with Spam Karma 2, you may see PHP 
warnings when Spam Karma 2 displays its internally generated CAPTCHA. This 
is a design problem in Spam Karma 2. Contact the author of Spam Karma 2 for 
a fix.
</li>
</ul>

Bad Behavior

Although sometimes it can be tricky if you get a false positive, those are pretty rare (haven't seen one in a couple years). Works well to keep bad actors off your site.

works nicely

Bad Behavior prevents spammers from ever delivering their junk, and in many
cases, from ever reading your site in the first place.

Matthew Batchelder

Have you ever wanted to get debug output sent to you from WordPress without interrupting the flow of the page? 
Do you ever wish you could get debug output from other users’ sessions so you don’t have to:
<ul>
<li>Log in as them</li>
<li>Asking them to look at debug output themselves (bleh)</li>
<li>Or try in vain to re-create their issue</li>
</ul>
This plugin allows you to send debug messages via UDP to a <a href="https://github.com/borkweb/jabberbot" rel="nofollow ugc">Jabber Bot</a> that can then route 
the debug information to your IM client.
Note: This plugin sends the messages via UDP. The receiving end doesn’t necessarily need to be a Jabber bot…it could be anything you want 
(e.g. email bot, logger, whatever). My implementation is a Jabber Bot on my local dev environment 🙂
<h4>Usage</h4>
To send debug messages, simply call:
<pre><code>do_action( 'debug_robot', $message [, $target ]);
</code></pre>
<ul>
<li>$message: Message to send to your jabber bot.</li>
<li>$target: (optional) Email address that your jabber bot will route the message to.</li>
</ul>
To receive debug messages, you will need to have:
<ul>
<li>Your <a href="https://github.com/borkweb/jabberbot" rel="nofollow ugc">Jabber Bot</a> installed and configured.</li>
<li>The Jabber Bot must be running.</li>
<li>You must have friended your robot’s jabber account with another jabber account (e.g. your Google account).</li>
<li>You must be signed into Google Talk in some way shape or form so that your jabber bot can IM you.</li>
</ul>
Note: If your Jabber Bot isn’t running, no worries. UDP doesn’t wait for a response so it won’t impact your WordPress instance…you just won’t get the messages that 
are sent until your bot is running 🙂
<h3>Credits</h3>
This code was largely written by <a href="https://github.com/abackstrom" rel="nofollow ugc">@abackstrom</a> with some additions by me while we worked at <a href="https://github.com/PlymouthState" rel="nofollow ugc">@PlymouthState</a>. I then ported it into a WordPress plugin.

WP Debug Robot

An unobtrusive debugging tool for WordPress

Bad Behavior vs WP Debug Robot