<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Tips for protecting your blog</title>
	<atom:link href="http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/</link>
	<description>Web design, search engine optimization and Internet marketing</description>
	<lastBuildDate>Mon, 23 Jan 2012 20:52:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Diane Vigil</title>
		<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145772</link>
		<dc:creator>Diane Vigil</dc:creator>
		<pubDate>Sun, 01 Aug 2010 17:43:10 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145772</guid>
		<description>I quite agree. For blogs (WordPress blogs), I find a combination of Akismet and Conditional Captcha very effective in combatting comment spam (comments made for the purpose of adding links or &quot;sales&quot; information, etc., to a blog).

As to &lt;b&gt;email spam&lt;/b&gt;, that&#039;s a different subject. For that, I particularly like setting up separate emails addresses for different purposes --- such as an email address solely for Facebook, etc. --- so that, even if that email address starts getting a lot of spam, I can just change it.

Also, running a spam detection program on your web hosting account, such as Spam Assassin, is very useful. I get very little email spam in my inbox (although I suspect that my server blocks the bulk of it, so I never see it).</description>
		<content:encoded><![CDATA[<p>I quite agree. For blogs (WordPress blogs), I find a combination of Akismet and Conditional Captcha very effective in combatting comment spam (comments made for the purpose of adding links or "sales" information, etc., to a blog).</p>
<p>As to <b>email spam</b>, that's a different subject. For that, I particularly like setting up separate emails addresses for different purposes &#8212; such as an email address solely for Facebook, etc. &#8212; so that, even if that email address starts getting a lot of spam, I can just change it.</p>
<p>Also, running a spam detection program on your web hosting account, such as Spam Assassin, is very useful. I get very little email spam in my inbox (although I suspect that my server blocks the bulk of it, so I never see it).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oscar Turner</title>
		<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145771</link>
		<dc:creator>Oscar Turner</dc:creator>
		<pubDate>Sun, 01 Aug 2010 17:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145771</guid>
		<description>spam blockers are really needed these days because you will always get spam from e-mails and on your facebook account too.&#039;`&#039;</description>
		<content:encoded><![CDATA[<p>spam blockers are really needed these days because you will always get spam from e-mails and on your facebook account too.'`'</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane Vigil</title>
		<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145734</link>
		<dc:creator>Diane Vigil</dc:creator>
		<pubDate>Tue, 25 May 2010 02:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145734</guid>
		<description>For WordPress? I favor a combination of Askimet and &lt;a href=&quot;http://developedtraffic.com/2010/03/06/conditional-captcha-for-wordpress/&quot;&gt;Conditional Capcha&lt;/a&gt;. These have worked great for our blogs.

Unless you&#039;re asking about server spam blockers, or something else ...</description>
		<content:encoded><![CDATA[<p>For WordPress? I favor a combination of Askimet and <a href="http://developedtraffic.com/2010/03/06/conditional-captcha-for-wordpress/">Conditional Capcha</a>. These have worked great for our blogs.</p>
<p>Unless you're asking about server spam blockers, or something else &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emma Johnson</title>
		<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145733</link>
		<dc:creator>Emma Johnson</dc:creator>
		<pubDate>Tue, 25 May 2010 02:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-145733</guid>
		<description>What is the best freeware spamblocker on the internet ?;,*</description>
		<content:encoded><![CDATA[<p>What is the best freeware spamblocker on the internet ?;,*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane Vigil</title>
		<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-54710</link>
		<dc:creator>Diane Vigil</dc:creator>
		<pubDate>Sat, 14 Jun 2008 10:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-54710</guid>
		<description>Thanks. You&#039;ve named some of the items I mentioned, but they&#039;re good tips.

And your last sentence there says everything: &quot;Its all very well and good screaming about HTML validation and Web 2.0, but its more important to have standards on your server-side, because this is where you are going to get hacked.&quot;

Thanks.</description>
		<content:encoded><![CDATA[<p>Thanks. You've named some of the items I mentioned, but they're good tips.</p>
<p>And your last sentence there says everything: "Its all very well and good screaming about HTML validation and Web 2.0, but its more important to have standards on your server-side, because this is where you are going to get hacked."</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheEatons</title>
		<link>http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-50768</link>
		<dc:creator>TheEatons</dc:creator>
		<pubDate>Fri, 30 May 2008 11:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/03/28/tips-for-protecting-your-blog/#comment-50768</guid>
		<description>Thanks for the tips. We used to have a blog, but it was hacked and had loads of vi@gr@ and gambling links hidden in it. When I mean loads I mean 100s!

Some other things it is good to to are:

*Block access to the admin either by password protecting the directory or only allowing access to it from an IP.
*Block access to all folders that only hold server-side scripting.
*Remove &quot;Powered by Wordpress&quot; from the footer as hackers and spammers use this to harvest WP blogs from Yahoo.
*Also remove the generator tag from the WP feed which gives away your WP version.

However, the best thing to do would be to move away from WordPress. WP has a long history of security exploits and the guys who are making it are not only not keyed up on php, session and database security. They also have some of the worst programming standards I have seen since osCommerce. Its all very well and good screaming about HTML validation and Web 2.0, but its more important to have standards on your server-side, because this is where you are going to get hacked.</description>
		<content:encoded><![CDATA[<p>Thanks for the tips. We used to have a blog, but it was hacked and had loads of vi@gr@ and gambling links hidden in it. When I mean loads I mean 100s!</p>
<p>Some other things it is good to to are:</p>
<p>*Block access to the admin either by password protecting the directory or only allowing access to it from an IP.<br />
*Block access to all folders that only hold server-side scripting.<br />
*Remove "Powered by WordPress" from the footer as hackers and spammers use this to harvest WP blogs from Yahoo.<br />
*Also remove the generator tag from the WP feed which gives away your WP version.</p>
<p>However, the best thing to do would be to move away from WordPress. WP has a long history of security exploits and the guys who are making it are not only not keyed up on php, session and database security. They also have some of the worst programming standards I have seen since osCommerce. Its all very well and good screaming about HTML validation and Web 2.0, but its more important to have standards on your server-side, because this is where you are going to get hacked.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

