<?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: Just in case your blog is Top Sekrit</title>
	<atom:link href="http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/</link>
	<description>The idle musings of John B</description>
	<lastBuildDate>Wed, 08 Sep 2010 17:17:43 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Neil</title>
		<link>http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/comment-page-1/#comment-24645</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Mon, 10 Dec 2007 12:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/#comment-24645</guid>
		<description>Future proofing, innit - just because a protocol hasn&#039;t been invented yet, doesn&#039;t mean you might not want your comment to link to it.

And you don&#039;t want to be looping over a hard-coded list of protocols either, better to check for xxxx: at the start and assume it&#039;s http:// if that is not there.

^[a-z0-9+.-]*: would be the regex to use.

(Do I win a prize for geekery above and beyond the call of duty?)</description>
		<content:encoded><![CDATA[<p>Future proofing, innit &#8211; just because a protocol hasn&#8217;t been invented yet, doesn&#8217;t mean you might not want your comment to link to it.</p>
<p>And you don&#8217;t want to be looping over a hard-coded list of protocols either, better to check for xxxx: at the start and assume it&#8217;s http:// if that is not there.</p>
<p>^[a-z0-9+.-]*: would be the regex to use.</p>
<p>(Do I win a prize for geekery above and beyond the call of duty?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Bliss</title>
		<link>http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/comment-page-1/#comment-24428</link>
		<dc:creator>Jim Bliss</dc:creator>
		<pubDate>Fri, 07 Dec 2007 01:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/#comment-24428</guid>
		<description>My first blog was self-built. Coldfusion (rather than ASP) and Access. I had a short script that checked to see if a URL started with a recognised protocol (there&#039;s not a huge number of protocols, so putting them into a list and looping through it doesn&#039;t involve much additional processing when it comes to validating form entry, above and beyond whatever regular validation you do). If no protocol existed, it prepended &quot;http://&quot; and Bob was my uncle. I&#039;ve never understood why so many developers don&#039;t take a little more time to sort out form entry and validation. For the few extra minutes it takes, you address 90% of the problems people will have, in practice, with your site.</description>
		<content:encoded><![CDATA[<p>My first blog was self-built. Coldfusion (rather than ASP) and Access. I had a short script that checked to see if a URL started with a recognised protocol (there&#8217;s not a huge number of protocols, so putting them into a list and looping through it doesn&#8217;t involve much additional processing when it comes to validating form entry, above and beyond whatever regular validation you do). If no protocol existed, it prepended &#8220;http://&#8221; and Bob was my uncle. I&#8217;ve never understood why so many developers don&#8217;t take a little more time to sort out form entry and validation. For the few extra minutes it takes, you address 90% of the problems people will have, in practice, with your site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/comment-page-1/#comment-24237</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 04 Dec 2007 20:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/#comment-24237</guid>
		<description>The CIA&#039;s website is all https, so if they ever did set up that internal blogging platform I recall hearing about, your https blogs are right there.</description>
		<content:encoded><![CDATA[<p>The CIA&#8217;s website is all https, so if they ever did set up that internal blogging platform I recall hearing about, your https blogs are right there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John B</title>
		<link>http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/comment-page-1/#comment-24219</link>
		<dc:creator>John B</dc:creator>
		<pubDate>Tue, 04 Dec 2007 16:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/#comment-24219</guid>
		<description>Yes - I think it might have been the only blog ever to have been based on Access and ASP [actually, there are probably some corporate blogs at IIS shops that do the same. Poor misguided fools...]. And I wrote a script that added an &quot;http://&quot; when appropriate, which I /think/ worked OK...</description>
		<content:encoded><![CDATA[<p>Yes &#8211; I think it might have been the only blog ever to have been based on Access and ASP [actually, there are probably some corporate blogs at IIS shops that do the same. Poor misguided fools...]. And I wrote a script that added an &#8220;http://&#8221; when appropriate, which I /think/ worked OK&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Newton</title>
		<link>http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/comment-page-1/#comment-24217</link>
		<dc:creator>Stephen Newton</dc:creator>
		<pubDate>Tue, 04 Dec 2007 16:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnband.org/blog/2007/12/04/just-in-case-your-blog-is-top-sekrit/#comment-24217</guid>
		<description>I&#039;ve also suffered this problem in WordPress and have an instruction to include http:// when including a web address with a comment. I did delve in the code and try adding it, but for some reason ended up getting http://http:// or http://http://http:// or http://http://http://http://

Wasn&#039;t SBBS your own creation?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also suffered this problem in WordPress and have an instruction to include http:// when including a web address with a comment. I did delve in the code and try adding it, but for some reason ended up getting <a href="http://http://" rel="nofollow">http://http://</a> or <a href="http://http://http://" rel="nofollow">http://http://http://</a> or <a href="http://http://http://http://" rel="nofollow">http://http://http://http://</a></p>
<p>Wasn&#8217;t SBBS your own creation?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
