<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Weblog Tools Collection &#187; Comment_Spam</title>
	<atom:link href="http://weblogtoolscollection.com/archives/tag/comment_spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<lastBuildDate>Mon, 13 Feb 2012 13:00:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Are You Spamming Comments Inadvertently?</title>
		<link>http://weblogtoolscollection.com/archives/2010/01/24/are-you-spamming-comments-inadvertently/</link>
		<comments>http://weblogtoolscollection.com/archives/2010/01/24/are-you-spamming-comments-inadvertently/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 23:54:30 +0000</pubDate>
		<dc:creator>Mark Ghosh</dc:creator>
				<category><![CDATA[Blogging Essays]]></category>
		<category><![CDATA[Business of Blogging]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Blog_Spam]]></category>
		<category><![CDATA[Comment_Spam]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=7603</guid>
		<description><![CDATA[In a blog post titles &#8220;6 Steps to Kill Your Community&#8220;, Matt listed &#8220;Allow Spam Through&#8221; as the second step and &#8220;Don&#8217;t Participate in Comments&#8221; as the fourth step to killing your community. We treat comments and reader participation very seriously at Weblog Tools Collection. We highlight commenters, try to identify the frequent comments who participate willingly and heuristically remove nofollow tags from the links of commenters who participate in the community. I have personally chosen and thanked frequent commenter by providing them deeper access and rights to the various portals, elevating and applauding their presence within the community and have chosen most of my co-authors based on their participation and passion within the communities that I purvey. In short, I agree with Matt in that relevant comments and passionate participation are the lifeblood of any community. But our little blog gets a lot of attention from spammers. We are [...]]]></description>
			<content:encoded><![CDATA[<p>In a blog post titles &#8220;<a href="http://ma.tt/2009/08/kill-your-community/">6 Steps to Kill Your Community</a>&#8220;, Matt listed &#8220;Allow Spam Through&#8221; as the second step and &#8220;Don&#8217;t Participate in Comments&#8221; as the fourth step to killing your community. We treat comments and reader participation very seriously at Weblog Tools Collection. We highlight commenters, try to identify the frequent comments who participate willingly and heuristically remove nofollow tags from the links of commenters who participate in the community. I have personally chosen and thanked frequent commenter by providing them deeper access and rights to the various portals, elevating and applauding their presence within the community and have chosen most of my co-authors based on their participation and passion within the communities that I purvey. In short, I agree with Matt in that relevant comments and passionate participation are the lifeblood of any community.</p>
<p>But our little blog gets a <a href="http://blog.akismet.com/2006/05/15/second-most-spammed-man-in-the-world/">lot of attention from spammers</a>. We are listed on web pages that pin point nofollow blogs for spamming, splogs regularly repost our content and send us trackbacks and well disguised comments are often adorned with links to completely unrelated sites. Moderating comments takes a lot of effort from all of us (we are working on making this process simpler, stay tuned) and even then, some weirdness and mistakes slip past us. We have recently started noticing a lot of comments that seem mildly relevant but link to SEO sites or completely unrelated content that keeps changing.</p>
<p>Do you change your commenters&#8217; URI often when posting comments? Are you under the impression that leaving comments with different links will give those links more exposure? Do you <a href="http://weblogtoolscollection.com/archives/2010/01/13/shorturl-comment-spam-problem/">use Short URLs</a> to get around comment spam restrictions? More importantly, how many of you force yourself to comment to just spread your links around? Have you ever left a comment just to increase your comment count? Are you an SEO professional who regularly comments on blogs for SEO purposes? You might be doing yourself (and us) more harm than good.</p>
<p>While we try our best to allow any and all relevant comments to be posted, we do actively remove suspicious comments. We make spam/spammer judgment calls every day, but spam is annoying and nasty and in my opinion, spam is like a leech that sucks off the goodness and leaves the host with nothing in return. It often clogs up the conversation and reduces relevancy. Just look at the latest comments on any old(er) blog with a popular post that has not been pruned and taken care of.</p>
<p>We do however, actively promote, reward and encourage passionate comments. If you feel that we have missed a comment that should have been posted, please contact us. However, if you are changing your link on every comment and linking to various websites around the internet who have paid you for your SEO services, please do not send us an email asking us to approve them. Mostly, dont be evil <em>and</em> smug!</p>
<p><em>How do you treat suspicious comments that have not been caught by Akismet? </em>We manually visit every comment waiting for moderation and actively remove suspicious comments and any older ones that might be related. It takes time but it is worth it.</p>
<p><em>How do you reward your commenters? </em>We use <a href="http://rmarsh.com/plugins/highlight-comments/">Highlight Author Comments</a> and hacked up versions of various plugins for heuristics.</p>
<p><em>Do you import comments from other places on the web? </em>No. We do not import comments from anywhere. The conversation is much more focused and we concentrate on quality versus quantity. We hope that our content, subject and demeanor encourage and crystallize commenting and participation. Other conversations about our posts on apps such as Digg, StumbleUpon and Twitter add nothing but noise wherein the real conversation in live comments get drowned out. I used to think that Trackbacks belonged in the comment flow. I have since changed my opinion after dealing with some posts with hundreds of comments.</p>
<p><em>Do you turn off comments on old posts?</em> No. Old posts are gems. Conversations can get started on old topics and need to be allowed.</p>
<p>What do you do?</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2010/01/24/are-you-spamming-comments-inadvertently/feed/</wfw:commentRss>
		<slash:comments>67</slash:comments>
		</item>
		<item>
		<title>Plugin Review: Yawasp</title>
		<link>http://weblogtoolscollection.com/archives/2009/02/15/plugin-review-yawasp/</link>
		<comments>http://weblogtoolscollection.com/archives/2009/02/15/plugin-review-yawasp/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 18:20:09 +0000</pubDate>
		<dc:creator>Ajay</dc:creator>
				<category><![CDATA[Weekly Plugin Review]]></category>
		<category><![CDATA[WordPress Plugins]]></category>
		<category><![CDATA[Comment_Spam]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=5183</guid>
		<description><![CDATA[Who doesn&#8217;t hate spam? Ever since blogs became common place, one thing that we have to worry about is spammers. It is like the constant battle of good vs. evil with the good folks finding means to defend themselves and others and the bad ones finding better means to attack the innocent ones! Yawasp (Yet Another WordPress Anti-Spam Plugin) is one such plugin that uses an innovative approach to battle comment spam. Description Most anti-comment-spambot-plugins focus on user interaction, e.g. captcha or math comment spam protection. Yawasp focuses on handling comment-spam-protection within WordPress. It replaces the names of the comment form fields with random names, protecting your blog from spambots that aim at the default comment field names. Furthermore it adds a blank field, hidden from the user, that needs to be left empty. In addition, the random field names are changed every 24 hours, giving a spambot no chance [...]]]></description>
			<content:encoded><![CDATA[<p>Who doesn&#8217;t hate spam? Ever since blogs became common place, one thing that we have to worry about is spammers. It is like the constant battle of good vs. evil with the good folks finding means to defend themselves and others and the bad ones finding better means to attack the innocent ones!</p>
<p><a href="http://www.svenkubiak.de/yawasp-en/">Yawasp (Yet Another WordPress Anti-Spam Plugin)</a> is one such plugin that uses an innovative approach to battle comment spam.</p>
<h3>Description</h3>
<p>Most anti-comment-spambot-plugins focus on user interaction, e.g. captcha or math comment spam protection. Yawasp focuses on handling comment-spam-protection within WordPress. It replaces the names of the comment form fields with random names, protecting your blog from spambots that aim at the default comment field names. Furthermore it adds a blank field, hidden from the user, that needs to be left empty. In addition, the random field names are changed every 24 hours, giving a spambot no chance to adapt to the comment form.</p>
<h3>Features</h3>
<ul>
<li>Does not require JavaScript, Cookies or Sessions</li>
<li>No extra field for user input (e.g. Captcha) required</li>
<li>False-positives are nearly impossible</li>
<li>No need to manage spam comments anymore</li>
<li>Easy installation (automatic or manual)</li>
</ul>
<h3>Installation</h3>
<p>The installation is more complicated than other plugins as it requires deal of manual intervention (in case the automatic editing fails). Upload the plugin and activate it.</p>
<p>Make the necessary changes in your theme files if necessary and you&#8217;re good to go.</p>
<p>The plugin will display the number of spambots blocked on the dashboard.</p>
<p><img style="display: inline" title="yawasp" src="http://weblogtoolscollection.com/b2-img/2009/02/yawasp.png" alt="yawasp" width="510" height="211" /></p>
<h3>Review</h3>
<p>This plugin is another attempt to protect your blog from spam. However, I still don&#8217;t think that this is the first and last stop for protecting your blog.</p>
<p>For one, it only attempts to stop automated spambots attacking your comment form.</p>
<p>And it cannot protect you against manual comment spammers and trackback/pingback spam. Hence, you&#8217;d require another plugin like Akismet to form your secondary defense.</p>
<p>I recommend using this plugin if you have been able to identify that your primary amount of spam is spambots attacking your site. By installing this plugin, you&#8217;ll notice that with these spambots blocked, you&#8217;ll be required to take a look at a much smaller amount of spam in your spam queue.</p>
<p>What I would like to see is what spam is actually blocked by the plugin. The plugin does store which spambots are blocked over a 24 hour period, which works well. However, you won&#8217;t see any of the comments blocked.</p>
<p>In case your visitors start to report being blocked, you&#8217;ll need to check your <em>comments.php</em> to see if the code is properly installed. I suggest making a few test comments as well getting a few friends to test it out. From my experience, a lot of commenters will just not bother informing you in case they face problems commenting on your site.</p>
<p>So, which antispam plugins do you use? If you&#8217;re already using Yawasp, what has been your experience so far? What features would you like to see added?</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2009/02/15/plugin-review-yawasp/feed/</wfw:commentRss>
		<slash:comments>22</slash:comments>
		</item>
		<item>
		<title>WP plugin: Bad Behavior 2</title>
		<link>http://weblogtoolscollection.com/archives/2006/07/08/wp-plugin-bad-behavior-2/</link>
		<comments>http://weblogtoolscollection.com/archives/2006/07/08/wp-plugin-bad-behavior-2/#comments</comments>
		<pubDate>Sat, 08 Jul 2006 13:06:53 +0000</pubDate>
		<dc:creator>Mark Ghosh</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Weblog tools blog tools blogging tools]]></category>
		<category><![CDATA[WordPress Plugins]]></category>
		<category><![CDATA[bad_behaviour]]></category>
		<category><![CDATA[Comment_Spam]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress_plugin]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/07/08/wp-plugin-bad-behavior-2/</guid>
		<description><![CDATA[WP plugin: Bad Behavior 2 This new version of Bad Behavior has a bunch of new features including faster code, variable strictness of traffic filtering, lesser usage of the database (which is really important for higher traffic sites) and a new wrapper API. Bad Behavior is now also available for ExpressionEngine, MediaWiki and generic non-database mode for any PHP script, forum, guestbook, Movable Type, etc. Thanks Michael va email.]]></description>
			<content:encoded><![CDATA[<p><a href="http://error.wordpress.com/2006/07/04/bad-behavior-2/">WP plugin: Bad Behavior 2</a> This new version of Bad Behavior has a bunch of new features including faster code, variable strictness of traffic filtering, lesser usage of the database (which is really important for higher traffic sites) and a new wrapper API. Bad Behavior is now also available for  ExpressionEngine, MediaWiki and generic non-database mode for any PHP script, forum, guestbook, Movable Type, etc.  Thanks <a href="http://ioerror.us">Michael</a> va email.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2006/07/08/wp-plugin-bad-behavior-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOW-TO: Protecting your Blog from Spam</title>
		<link>http://weblogtoolscollection.com/archives/2005/11/11/how-to-protecting-your-blog-from-spam/</link>
		<comments>http://weblogtoolscollection.com/archives/2005/11/11/how-to-protecting-your-blog-from-spam/#comments</comments>
		<pubDate>Fri, 11 Nov 2005 14:46:24 +0000</pubDate>
		<dc:creator>Ajay</dc:creator>
				<category><![CDATA[HOW-TO]]></category>
		<category><![CDATA[LinkyLoo]]></category>
		<category><![CDATA[Akismet]]></category>
		<category><![CDATA[Blog_Spam]]></category>
		<category><![CDATA[Comment_Spam]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2005/11/11/how-to-protecting-your-blog-from-spam/</guid>
		<description><![CDATA[HOW-TO: Protecting your Blog from Spam: Read up on various methods to protect your WordPress blog from spam. More information at the WordPress Codex on comment spam.]]></description>
			<content:encoded><![CDATA[<p><a href="http://ajaydsouza.com/archives/2006/08/05/a-comprehensive-guide-to-protecting-your-blog-from-spam/">HOW-TO: Protecting your Blog from Spam</a>: Read up on various methods to protect your WordPress blog from spam. More information at the <a href="http://codex.wordpress.org/Combat_Comment_Spam">WordPress Codex on comment spam</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2005/11/11/how-to-protecting-your-blog-from-spam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  weblogtoolscollection.com/archives/tag/comment_spam/feed/ ) in 0.56472 seconds, on Feb 14th, 2012 at 9:32 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 14th, 2012 at 10:32 am UTC -->
