<?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 for Josiah Cole; Technologist and Web Hacker Extraordinaire</title>
	<atom:link href="http://www.josiahcole.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.josiahcole.com</link>
	<description>Internet tech blog covering web design, development, marketing and general tech news.</description>
	<lastBuildDate>Sun, 05 Feb 2012 21:27:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by Consejos de seguridad en wordpress &#124; fanesvag, el blog de Paco Anes</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-2397</link>
		<dc:creator>Consejos de seguridad en wordpress &#124; fanesvag, el blog de Paco Anes</dc:creator>
		<pubDate>Sun, 05 Feb 2012 21:27:09 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-2397</guid>
		<description>[...] El proceso es sencillo: se  hace una copia de tu .htaccess, se abre con un editor de texto como Notepad (no lo vayáis a editar con Word) y se pegan los códigos oportunos. Os dejo estos fragmentos de código pero podéis poner muchos otros a vuestro gusto. Para ello os invito a que visitéis un artículo de cómo sería el .htaccess perfecto. [...]</description>
		<content:encoded><![CDATA[<p>[...] El proceso es sencillo: se  hace una copia de tu .htaccess, se abre con un editor de texto como Notepad (no lo vayáis a editar con Word) y se pegan los códigos oportunos. Os dejo estos fragmentos de código pero podéis poner muchos otros a vuestro gusto. Para ello os invito a que visitéis un artículo de cómo sería el .htaccess perfecto. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 19 Things NOT To Do When Building a Website by kapow by hobbestobias - Pearltrees</title>
		<link>http://www.josiahcole.com/2007/02/14/a-webmasters-19-commandments/comment-page-5/#comment-2326</link>
		<dc:creator>kapow by hobbestobias - Pearltrees</dc:creator>
		<pubDate>Fri, 13 Jan 2012 12:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=34#comment-2326</guid>
		<description>[...] Sorry, no posts matched your criteria. Josiah Cole » 19 Things NOT To Do When Building a Website [...]</description>
		<content:encoded><![CDATA[<p>[...] Sorry, no posts matched your criteria. Josiah Cole » 19 Things NOT To Do When Building a Website [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by What the heck is a .htaccess file (and why is my blog messed up?) &#171; COM585</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-1045</link>
		<dc:creator>What the heck is a .htaccess file (and why is my blog messed up?) &#171; COM585</dc:creator>
		<pubDate>Wed, 14 Sep 2011 01:27:56 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-1045</guid>
		<description>[...] in creating a more robust .htaccess file for your site (and know more about coding than I do), this guy has a tutorial. Otherwise, hope you&#8217;re not too [...]</description>
		<content:encoded><![CDATA[<p>[...] in creating a more robust .htaccess file for your site (and know more about coding than I do), this guy has a tutorial. Otherwise, hope you&#8217;re not too [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by How To Secure WordPress configuration file - Wordpress Arena</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-894</link>
		<dc:creator>How To Secure WordPress configuration file - Wordpress Arena</dc:creator>
		<pubDate>Sat, 06 Aug 2011 04:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-894</guid>
		<description>[...] Josiah Cole wrote a nice htaccess tutorial on modifying your .htaccess to protect the wp-config. [...]</description>
		<content:encoded><![CDATA[<p>[...] Josiah Cole wrote a nice htaccess tutorial on modifying your .htaccess to protect the wp-config. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by Securing a new WordPress installation, part 1: wp-config.php</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-890</link>
		<dc:creator>Securing a new WordPress installation, part 1: wp-config.php</dc:creator>
		<pubDate>Thu, 04 Aug 2011 19:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-890</guid>
		<description>[...] security can be achieved by configuring Apache to forbid direct access to the wp-config.php file. This is done through the hidden .htaccess file on the blog [...]</description>
		<content:encoded><![CDATA[<p>[...] security can be achieved by configuring Apache to forbid direct access to the wp-config.php file. This is done through the hidden .htaccess file on the blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by Jail break Iphone 4.3.3</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-887</link>
		<dc:creator>Jail break Iphone 4.3.3</dc:creator>
		<pubDate>Thu, 04 Aug 2011 10:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-887</guid>
		<description>&lt;strong&gt;Jailbreak iOS 4.3.3 Untethered on iPhone 4, 3GS, iPad, iPod touch ......&lt;/strong&gt;

Today iPhone Dev Team has released PwnageTool 4.3.3 for Mac users which will bring untethered jailbreak for iOS 4.3.3 to iPhone 4, ......</description>
		<content:encoded><![CDATA[<p><strong>Jailbreak iOS 4.3.3 Untethered on iPhone 4, 3GS, iPad, iPod touch &#8230;&#8230;</strong></p>
<p>Today iPhone Dev Team has released PwnageTool 4.3.3 for Mac users which will bring untethered jailbreak for iOS 4.3.3 to iPhone 4, &#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 19 Things NOT To Do When Building a Website by Design</title>
		<link>http://www.josiahcole.com/2007/02/14/a-webmasters-19-commandments/comment-page-5/#comment-884</link>
		<dc:creator>Design</dc:creator>
		<pubDate>Wed, 03 Aug 2011 19:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=34#comment-884</guid>
		<description>&lt;strong&gt;Graphics...&lt;/strong&gt;

19 Things NOT To Do When Building a Website &#8212; Josiah Cole; Technologist and Web Hacker Extraordinaire...</description>
		<content:encoded><![CDATA[<p><strong>Graphics&#8230;</strong></p>
<p>19 Things NOT To Do When Building a Website &#8212; Josiah Cole; Technologist and Web Hacker Extraordinaire&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by .htaccess ideal para Wordpress &#124; Dbalbis.com</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-867</link>
		<dc:creator>.htaccess ideal para Wordpress &#124; Dbalbis.com</dc:creator>
		<pubDate>Tue, 26 Jul 2011 15:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-867</guid>
		<description>[...] Vía &#124; Josiahcole [...]</description>
		<content:encoded><![CDATA[<p>[...] Vía | Josiahcole [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 19 Things NOT To Do When Building a Website by Skip Intro &#124; SIMBUERGER IT</title>
		<link>http://www.josiahcole.com/2007/02/14/a-webmasters-19-commandments/comment-page-5/#comment-826</link>
		<dc:creator>Skip Intro &#124; SIMBUERGER IT</dc:creator>
		<pubDate>Fri, 08 Jul 2011 07:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=34#comment-826</guid>
		<description>[...] dieser Meinung stehe ich nicht alleine. Unter http://www.josiahcole.com/2007/02/14/a-webmasters-19-commandments/ finden Sie weitere NoGos für die [...]</description>
		<content:encoded><![CDATA[<p>[...] dieser Meinung stehe ich nicht alleine. Unter <a href="http://www.josiahcole.com/2007/02/14/a-webmasters-19-commandments/" rel="nofollow">http://www.josiahcole.com/2007/02/14/a-webmasters-19-commandments/</a> finden Sie weitere NoGos für die [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Almost Perfect htaccess File for WordPress Blogs by Rebuilding &#171; A day in the life II</title>
		<link>http://www.josiahcole.com/2007/07/11/almost-perfect-htaccess-file-for-wordpress-blogs/comment-page-2/#comment-820</link>
		<dc:creator>Rebuilding &#171; A day in the life II</dc:creator>
		<pubDate>Mon, 04 Jul 2011 16:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://josiahcole.coleblognetwork.com/?p=50#comment-820</guid>
		<description>[...] Move or hide your wp-config.php file: The wp-config.php file has lots of secret information in it and it lives in an internet browsable location by default. You can use an .htaccess file to restrict access to the file, you can sometimes move it out of the browsable directories entirely, or you can move the secret information out of harm&#8217;s way. These operations may require you to reapply the change (depending on how you do it) after each WordPress upgrade. For more information on how to do this, try this link. An even more geeky treatment is here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Move or hide your wp-config.php file: The wp-config.php file has lots of secret information in it and it lives in an internet browsable location by default. You can use an .htaccess file to restrict access to the file, you can sometimes move it out of the browsable directories entirely, or you can move the secret information out of harm&#8217;s way. These operations may require you to reapply the change (depending on how you do it) after each WordPress upgrade. For more information on how to do this, try this link. An even more geeky treatment is here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

