<?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: So what does pfSense stand for/mean, anyway?</title>
	<atom:link href="http://blog.pfsense.org/?feed=rss2&#038;p=114" rel="self" type="application/rss+xml" />
	<link>http://blog.pfsense.org/?p=114</link>
	<description>News, reviews and more related to the pfSense firewall project</description>
	<lastBuildDate>Sun, 19 May 2013 21:07:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Russnixon</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-20542</link>
		<dc:creator>Russnixon</dc:creator>
		<pubDate>Mon, 04 Mar 2013 04:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-20542</guid>
		<description><![CDATA[Here we are, almost 6 years later, and now pfSense truly is a widely-recognized brand in network security.  Even a dope like myself can make sense of its complexity and make use of its brilliance. Taking something as complicated as packet filtering, and making sense of it, is no joke. Keep up the fantastic work.]]></description>
		<content:encoded><![CDATA[<p>Here we are, almost 6 years later, and now pfSense truly is a widely-recognized brand in network security.  Even a dope like myself can make sense of its complexity and make use of its brilliance. Taking something as complicated as packet filtering, and making sense of it, is no joke. Keep up the fantastic work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KeltecRFB</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-19736</link>
		<dc:creator>KeltecRFB</dc:creator>
		<pubDate>Tue, 29 Jan 2013 14:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-19736</guid>
		<description><![CDATA[I love the Plain F****** Sense name the best ... :-)]]></description>
		<content:encoded><![CDATA[<p>I love the Plain F****** Sense name the best &#8230; <img src='http://blog.pfsense.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iceman</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-18453</link>
		<dc:creator>iceman</dc:creator>
		<pubDate>Mon, 03 Dec 2012 08:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-18453</guid>
		<description><![CDATA[Great Name! Great Product! No sense in changing the name.]]></description>
		<content:encoded><![CDATA[<p>Great Name! Great Product! No sense in changing the name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Slick</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-18347</link>
		<dc:creator>Slick</dc:creator>
		<pubDate>Sat, 17 Nov 2012 02:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-18347</guid>
		<description><![CDATA[It&#039;s been pfsense for so long, why change it! I have used this router platform since around 1.2]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s been pfsense for so long, why change it! I have used this router platform since around 1.2</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bajo79</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-17620</link>
		<dc:creator>bajo79</dc:creator>
		<pubDate>Mon, 03 Sep 2012 08:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-17620</guid>
		<description><![CDATA[Keep the name and put &quot;From Zero to Hero&quot; as slogan. Also keep this great project running.]]></description>
		<content:encoded><![CDATA[<p>Keep the name and put &#8220;From Zero to Hero&#8221; as slogan. Also keep this great project running.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jugs 200</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-16521</link>
		<dc:creator>jugs 200</dc:creator>
		<pubDate>Fri, 06 Jul 2012 03:31:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-16521</guid>
		<description><![CDATA[just keep up the good work]]></description>
		<content:encoded><![CDATA[<p>just keep up the good work</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jugs 200</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-16520</link>
		<dc:creator>jugs 200</dc:creator>
		<pubDate>Fri, 06 Jul 2012 03:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-16520</guid>
		<description><![CDATA[yeah..... that name is very interesting, just keep it
cause many people already know and recognize that name]]></description>
		<content:encoded><![CDATA[<p>yeah&#8230;.. that name is very interesting, just keep it<br />
cause many people already know and recognize that name</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Buechler</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-15008</link>
		<dc:creator>Chris Buechler</dc:creator>
		<pubDate>Mon, 28 Nov 2011 11:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-15008</guid>
		<description><![CDATA[Kamel: apparently there isn&#039;t an &quot;invisible &#039;stay away&#039; barrier&quot;, given the significant installed base of the project. http://blog.pfsense.org/?p=625 and judging by Google Trends analysis as another measure, we&#039;re by far the most popular open source firewall. The only aversion I&#039;ve heard from people is just against open source in general, for those who have engrained in them that &quot;you get what you pay for&quot;, or the &quot;nobody ever got fired for buying &lt;insert big name vendor here&gt;&quot; mentality that&#039;s common in very large companies. I generally don&#039;t put a lot of effort into persuading those types of people, as they typically have no interest in seeing things differently. There are more than enough out there that have embraced open source, and those are who we focus our efforts on at least marketing-wise.]]></description>
		<content:encoded><![CDATA[<p>Kamel: apparently there isn&#8217;t an &#8220;invisible &#8216;stay away&#8217; barrier&#8221;, given the significant installed base of the project. <a href="http://blog.pfsense.org/?p=625" rel="nofollow">http://blog.pfsense.org/?p=625</a> and judging by Google Trends analysis as another measure, we&#8217;re by far the most popular open source firewall. The only aversion I&#8217;ve heard from people is just against open source in general, for those who have engrained in them that &#8220;you get what you pay for&#8221;, or the &#8220;nobody ever got fired for buying <insert big name vendor here>&#8221; mentality that&#8217;s common in very large companies. I generally don&#8217;t put a lot of effort into persuading those types of people, as they typically have no interest in seeing things differently. There are more than enough out there that have embraced open source, and those are who we focus our efforts on at least marketing-wise.</insert></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamel</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-14997</link>
		<dc:creator>Kamel</dc:creator>
		<pubDate>Sun, 27 Nov 2011 20:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-14997</guid>
		<description><![CDATA[I realize this is an old post, but wanted to add my input anyway. I am not necessarily against the name pfsense, but do believe a more descriptive name would help break the invisible &quot;stay away&quot; barrier that seems to currently exist with pfsense. Something that implies ease of use yet very powerful and configurable would be ideal.

Having said that, this really isn&#039;t a major concern, just saying that I do see some benefits to changing it.]]></description>
		<content:encoded><![CDATA[<p>I realize this is an old post, but wanted to add my input anyway. I am not necessarily against the name pfsense, but do believe a more descriptive name would help break the invisible &#8220;stay away&#8221; barrier that seems to currently exist with pfsense. Something that implies ease of use yet very powerful and configurable would be ideal.</p>
<p>Having said that, this really isn&#8217;t a major concern, just saying that I do see some benefits to changing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pfSense Digest &#187; Blog Archive &#187; 7 year anniversary of pfSense</title>
		<link>http://blog.pfsense.org/?p=114&#038;cpage=1#comment-14097</link>
		<dc:creator>pfSense Digest &#187; Blog Archive &#187; 7 year anniversary of pfSense</dc:creator>
		<pubDate>Sun, 06 Nov 2011 04:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=114#comment-14097</guid>
		<description><![CDATA[[...] years ago today, the name pfSense was settled on, and pfsense.org/com/net domains were registered. It&#8217;s grown from the volunteer efforts of a [...]]]></description>
		<content:encoded><![CDATA[<p>[...] years ago today, the name pfSense was settled on, and pfsense.org/com/net domains were registered. It&#8217;s grown from the volunteer efforts of a [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
