<?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: BlogRoll Update</title>
	<atom:link href="http://ironwil.net/blog/2008/01/01/blogroll-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://ironwil.net/blog/2008/01/01/blogroll-update/</link>
	<description>&#34;In matters of style, swim with the current; in matters of principle, stand like a rock.&#34; - Thomas Jefferson</description>
	<lastBuildDate>Sun, 21 Nov 2010 16:47:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SecurityCatalyst</title>
		<link>http://ironwil.net/blog/2008/01/01/blogroll-update/comment-page-1/#comment-39</link>
		<dc:creator>SecurityCatalyst</dc:creator>
		<pubDate>Wed, 02 Jan 2008 10:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://ironwil.net/blog/2008/01/01/blogroll-update/#comment-39</guid>
		<description>Happy New Year!

I&#039;m sorry to have been removed from your blogroll. I do agree that 2007 was a rough year for podcasting - travel and the book combined to create some pressure on my schedule.

I met with an audio engineer this weekend, and we&#039;re working out a process that will allow me to record one Security Round Table (SRT) podcast per month, along with one Security Catalyst Podcast per month -- starting in January.

I do hope that you&#039;ll consider taking a listen to both of these programs, as we&#039;ve spent a bit of time really trying to develop a format that is appealing and attainable/sustainable for me.

The book, Into the Breach, is nearing completion -- and I expect to share a lot of the ideas and insights from the book, and continue to build on my experiences.

In fact, I&#039;d love to understand what you look for in a podcast. Shoot me a note sometime and we can map it out.

In the meantime, keep up the good work and consider joining us in the Security Catalyst Community (www.securitycatalyst.org).

Michael
The Security Catalyst</description>
		<content:encoded><![CDATA[<p>Happy New Year!</p>
<p>I&#8217;m sorry to have been removed from your blogroll. I do agree that 2007 was a rough year for podcasting &#8211; travel and the book combined to create some pressure on my schedule.</p>
<p>I met with an audio engineer this weekend, and we&#8217;re working out a process that will allow me to record one Security Round Table (SRT) podcast per month, along with one Security Catalyst Podcast per month &#8212; starting in January.</p>
<p>I do hope that you&#8217;ll consider taking a listen to both of these programs, as we&#8217;ve spent a bit of time really trying to develop a format that is appealing and attainable/sustainable for me.</p>
<p>The book, Into the Breach, is nearing completion &#8212; and I expect to share a lot of the ideas and insights from the book, and continue to build on my experiences.</p>
<p>In fact, I&#8217;d love to understand what you look for in a podcast. Shoot me a note sometime and we can map it out.</p>
<p>In the meantime, keep up the good work and consider joining us in the Security Catalyst Community (www.securitycatalyst.org).</p>
<p>Michael<br />
The Security Catalyst</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SecurityCatalyst</title>
		<link>http://ironwil.net/blog/2008/01/01/blogroll-update/comment-page-1/#comment-698</link>
		<dc:creator>SecurityCatalyst</dc:creator>
		<pubDate>Wed, 02 Jan 2008 10:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://ironwil.net/blog/2008/01/01/blogroll-update/#comment-698</guid>
		<description>Happy New Year!

I&#039;m sorry to have been removed from your blogroll. I do agree that 2007 was a rough year for podcasting - travel and the book combined to create some pressure on my schedule.

I met with an audio engineer this weekend, and we&#039;re working out a process that will allow me to record one Security Round Table (SRT) podcast per month, along with one Security Catalyst Podcast per month -- starting in January.

I do hope that you&#039;ll consider taking a listen to both of these programs, as we&#039;ve spent a bit of time really trying to develop a format that is appealing and attainable/sustainable for me.

The book, Into the Breach, is nearing completion -- and I expect to share a lot of the ideas and insights from the book, and continue to build on my experiences.

In fact, I&#039;d love to understand what you look for in a podcast. Shoot me a note sometime and we can map it out.

In the meantime, keep up the good work and consider joining us in the Security Catalyst Community (www.securitycatalyst.org).

Michael
The Security Catalyst</description>
		<content:encoded><![CDATA[<p>Happy New Year!</p>
<p>I&#8217;m sorry to have been removed from your blogroll. I do agree that 2007 was a rough year for podcasting &#8211; travel and the book combined to create some pressure on my schedule.</p>
<p>I met with an audio engineer this weekend, and we&#8217;re working out a process that will allow me to record one Security Round Table (SRT) podcast per month, along with one Security Catalyst Podcast per month &#8212; starting in January.</p>
<p>I do hope that you&#8217;ll consider taking a listen to both of these programs, as we&#8217;ve spent a bit of time really trying to develop a format that is appealing and attainable/sustainable for me.</p>
<p>The book, Into the Breach, is nearing completion &#8212; and I expect to share a lot of the ideas and insights from the book, and continue to build on my experiences.</p>
<p>In fact, I&#8217;d love to understand what you look for in a podcast. Shoot me a note sometime and we can map it out.</p>
<p>In the meantime, keep up the good work and consider joining us in the Security Catalyst Community (www.securitycatalyst.org).</p>
<p>Michael<br />
The Security Catalyst</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.646 seconds -->

