Block List Updater
Few users are familiar with the comment block list built into WordPress. Located in the WordPress admin area under “Settings”—“Discussion”, that block list for incoming comments accepts values (words) to identify spam by. Additionally to plugins like Antispam Bee in order to fight spam successfully a curated comment block list is recommendable. You can either update the list manually, or utilize a very detailed global comment block list that gets updated on a regular basis. Block List Updater has been developed to keep your comment block list in your WordPress installation up to speed with the curated global list on GitHub. The plugin will check the global comment block list on GitHub multiple times a day. Whenever new anti-spam values have been added to the global list, Block List Updater will read the global list and update your WordPress database accordingly. While the check-up process will run several times a day, the plugin will only update the database when it detects an actual change of the global comment block list on GitHub. Support Community support via the support forums on wordpress.org We don’t handle support via e-mail, Twitter, GitHub issues etc. Contribute Active development of this plugin is handled on GitHub. Pull requests for documented bugs are highly appreciated. If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the support forums first. If you want to help us translate this plugin you can do so on WordPress Translate. Credits Author: Sergej Müller Maintainers: pluginkollektiv
Kama SpamBlock
Kama Spamblock blocks simple automated comment spam. It is invisible to normal visitors and does not use captchas. The plugin protects the standard WordPress comment endpoint, wp-comments-post.php. It adds a small check to the comment form. Direct requests that skip the form are blocked. This is a basic check, not proof that a person wrote the comment. Bots that load the page and run JavaScript can pass it. Kama Spamblock does not replace a full anti-spam service. It also checks pings and trackbacks for a link back to your site. Even if you are using an external comment system like Disqus, Kama Spamblock can add lightweight protection. Automated requests can be posted directly to the ‘wp-comments-post.php’ file, where the plugin can block basic bots. Simple and effective protection Kama Spamblock combines several small checks that are inexpensive for the site and invisible during normal commenting: The protective field name and its unique code rotate together every four hours. Ten recent pairs remain valid for pages served from full-page cache. Each marker is tied to the specific WordPress post, so a marker copied from another comment form is rejected. The form must remain open for at least three seconds before it can be accepted. Protective fields are added only after interaction with the comment submit button. If a valid comment is blocked, a JavaScript-only retry form preserves the entered data. The retry challenge changes its HTML structure to make basic scraping less reliable. Pingbacks and trackbacks must return a successful HTTP response, non-binary content, and a real backlink. These checks deliberately remain lightweight. A capable bot that loads the page, runs JavaScript, and reproduces normal browser behaviour can still pass them. Using Kama Spamblock with other anti-spam plugins Kama Spamblock can work with a full anti-spam plugin or service. It blocks simple direct spam requests first. The other tool can then check the comments that remain. For example, it can analyse comment text, reputation, or behaviour. The plugins complement each other. For this combination to work as intended: The other plugin should use the standard WordPress comment flow, or check comments after Kama Spamblock allows them. The site must show the standard comment form and allow the plugin’s JavaScript to run. Set the correct ID for the form’s submit button in the plugin settings. Test the setup if another plugin replaces the comment form, uses AJAX, or sends comments to its own endpoint. Kama Spamblock may need extra integration, or it may not check those comments.
