Bad Behavior / Bad Behaviour

Bad Behavior 2.0.44

August 14th, 2011 by Michael Hampton

Bad Behavior 2.0.44 has been released. This is a maintenance release and upgrading is recommended for all users.

Please note: The 2.0 series of Bad Behavior is receiving limited updates, including unblocks, bug fixes and security fixes only.

WordPress users should see the special note below.

Who should upgrade?

All users of the 2.0 series should upgrade to ensure that the Google Web Preview functionality works as intended with their sites.

What’s new?

New in this release (since 2.0.43 and 2.1.12):

• Google Web Preview is now fully supported by Bad Behavior.

Note: Some users have stated that the Google +1 feature does not work when Bad Behavior is enabled. I have investigated this issue and determined that the issue is a problem in Google’s code which Bad Behavior cannot easily work around. This issue has been reported to Google, though I have not yet been notified that Google has fixed the issue. If you see this issue, please report it to Google (again).

What’s coming?

I’m currently preparing to release the next major stable release of Bad Behavior, version 2.2. This release is sufficiently different that anyone maintaining a port needs to update their port to handle the new features immediately (such changes are backward compatible if implemented properly). Ports which are currently feature-complete on 2.1 will not need updating for 2.2 as the API is now stable.

Bad Behavior 2.2 is finalized and I am preparing to release it as soon as I have finished updating its documentation. WordPress users will be receiving its release candidates through automatic update within the next 24 hours, though due to some versioning issues involved in my switching from subversion to git, it will be labeled as 2.1.13 (rc1) or 2.1.14 (rc2). If you use WordPress, check to ensure that you have received 2.1.14 and then check the new options available to you.

After that, the next development branch will target version 3.0. As I’ve mentioned before, it’s a complete ground-up rewrite, so anyone maintaining a port will need to track development and be prepared to completely rewrite their ports. I’m not prepared at this time to give a schedule, as schedules tend to slip, and the 3.0 rewrite has proved more challenging than I anticipated.

For our enterprise users who require long-term support, the 2.0 branch will continue to receive long-term support through June 30, 2012, though you should prepare to update to 2.2 as soon as possible. The 2.2 branch (coming shortly) will be fully supported until the 3.0 release, and then receive long-term support for at least one year beyond that date.

Download

Download the latest release of Bad Behavior now!

Support

I can only spend time on improving Bad Behavior when incoming donations cover the cost of my time. Otherwise I have to engage in paying work to keep food on my table. Unfortunately this fact has kept me away from Bad Behavior for several months, as donations have been few and far between.

I happen to like giving spammers a hard time, and it’s frustrating that I don’t get to spend enough time on it. You can help me make Bad Behavior even better by making your most generous donation for any amount. (BTW, I fixed all the broken donation links, I think. If you find any other broken ones, let me know!)

Thank you again for supporting Bad Behavior development!