<?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"
	>
<channel>
	<title>Comments for NearlyFreeSpeech.NET Blog</title>
	<atom:link href="http://blog.nearlyfreespeech.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nearlyfreespeech.net</link>
	<description>A blog from the staff at NearlyFreeSpeech.NET.</description>
	<pubDate>Sat, 22 Nov 2008 04:05:03 +0000</pubDate>
	
		<item>
		<title>Comment on Friday night maintenance window for MySQL by Pat</title>
		<link>http://blog.nearlyfreespeech.net/2008/10/01/friday-night-maintenance-window-for-mysql/#comment-8363</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Wed, 08 Oct 2008 19:52:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=63#comment-8363</guid>
		<description>Which Friday?

&lt;b&gt;The Friday following the blog post.  The maintenance has already been completed. -jdw&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>Which Friday?</p>
<p><b>The Friday following the blog post.  The maintenance has already been completed. -jdw</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Friday night maintenance window for MySQL by Tyler</title>
		<link>http://blog.nearlyfreespeech.net/2008/10/01/friday-night-maintenance-window-for-mysql/#comment-8339</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Thu, 02 Oct 2008 02:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=63#comment-8339</guid>
		<description>Just because the internet hates everyone, you'll probably get a DDoS attack at that time. :-P

In fact, it might be better to not mention exact times in case people with malicious intent actually read this blog.

&lt;b&gt;We're not going to alter our update schedule or public disclosure practices based on what hypothetical people might do.  Our members need and deserve the best available information. If something bad happens, we'll deal with it. -jdw&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>Just because the internet hates everyone, you&#8217;ll probably get a DDoS attack at that time. <img src='http://blog.nearlyfreespeech.net/wp-includes/images/smilies/icon_razz.gif' alt=':-P' class='wp-smiley' /> </p>
<p>In fact, it might be better to not mention exact times in case people with malicious intent actually read this blog.</p>
<p><b>We&#8217;re not going to alter our update schedule or public disclosure practices based on what hypothetical people might do.  Our members need and deserve the best available information. If something bad happens, we&#8217;ll deal with it. -jdw</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MySQL FreeBSD 7 ZFS Beta update &#038; MySQL upgrades by Vasilis</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/29/mysql-freebsd-7-zfs-beta-update-mysql-upgrades/#comment-8332</link>
		<dc:creator>Vasilis</dc:creator>
		<pubDate>Mon, 29 Sep 2008 19:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=58#comment-8332</guid>
		<description>This is great news! My MySQL databases are already running on FreeBSD 7.0.

Thank you guys for the great work. Keep it up!</description>
		<content:encoded><![CDATA[<p>This is great news! My MySQL databases are already running on FreeBSD 7.0.</p>
<p>Thank you guys for the great work. Keep it up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MySQL FreeBSD 7 ZFS Beta update &#038; MySQL upgrades by Tyler</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/29/mysql-freebsd-7-zfs-beta-update-mysql-upgrades/#comment-8331</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Mon, 29 Sep 2008 05:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=58#comment-8331</guid>
		<description>Any timetable for this to be done? A month from now, maybe? Less? More? Could you give a rough estimate?</description>
		<content:encoded><![CDATA[<p>Any timetable for this to be done? A month from now, maybe? Less? More? Could you give a rough estimate?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UPDATED: Domain registration price increases September 30th by EdgeX-</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/19/domain-registration-price-increases-september-30th/#comment-8327</link>
		<dc:creator>EdgeX-</dc:creator>
		<pubDate>Sat, 27 Sep 2008 10:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=52#comment-8327</guid>
		<description>Wow - That sucks :(

&lt;b&gt;You're right. -jdw&lt;/b&gt;

</description>
		<content:encoded><![CDATA[<p>Wow - That sucks <img src='http://blog.nearlyfreespeech.net/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p><b>You&#8217;re right. -jdw</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scheduled Maintenance: IP Renumbering In Progress by intgr</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/11/scheduled-maintenance-ip-renumbering-in-progress/#comment-8323</link>
		<dc:creator>intgr</dc:creator>
		<pubDate>Wed, 24 Sep 2008 21:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=47#comment-8323</guid>
		<description>You could make it work by simply moving from "members.ipv6.nearlyfreespeech.net" to "ipv6.members.nearlyfreespeech.net". :)

&lt;b&gt;Good idea.  We'll probably do that soon. -jdw&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>You could make it work by simply moving from &#8220;members.ipv6.nearlyfreespeech.net&#8221; to &#8220;ipv6.members.nearlyfreespeech.net&#8221;. <img src='http://blog.nearlyfreespeech.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p><b>Good idea.  We&#8217;ll probably do that soon. -jdw</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scheduled Maintenance: IP Renumbering In Progress by Michael Lockyear</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/11/scheduled-maintenance-ip-renumbering-in-progress/#comment-8322</link>
		<dc:creator>Michael Lockyear</dc:creator>
		<pubDate>Tue, 23 Sep 2008 18:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=47#comment-8322</guid>
		<description>Hopefully this is on topic...

If we can have a IPV6 address on a site by site basis, would this mean that we would be able to have our very own SSL certs?

&lt;b&gt;It might someday mean that. -jdw&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>Hopefully this is on topic&#8230;</p>
<p>If we can have a IPV6 address on a site by site basis, would this mean that we would be able to have our very own SSL certs?</p>
<p><b>It might someday mean that. -jdw</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UPDATED: Domain registration price increases September 30th by Nick</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/19/domain-registration-price-increases-september-30th/#comment-8320</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Tue, 23 Sep 2008 03:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=52#comment-8320</guid>
		<description>Wow, that's a pretty huge increase (over 11%). How much of this extra 90c goes to NFS?

&lt;b&gt;None of it. We are passing the increase we'll be paying on penny-for-penny. -jdw&lt;/b&gt;

</description>
		<content:encoded><![CDATA[<p>Wow, that&#8217;s a pretty huge increase (over 11%). How much of this extra 90c goes to NFS?</p>
<p><b>None of it. We are passing the increase we&#8217;ll be paying on penny-for-penny. -jdw</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UPDATED: Domain registration price increases September 30th by Jordan Ogren</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/19/domain-registration-price-increases-september-30th/#comment-8313</link>
		<dc:creator>Jordan Ogren</dc:creator>
		<pubDate>Fri, 19 Sep 2008 04:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=52#comment-8313</guid>
		<description>*Deep Sigh*

Blarg...it's almost as bad as gas prices.  :P</description>
		<content:encoded><![CDATA[<p>*Deep Sigh*</p>
<p>Blarg&#8230;it&#8217;s almost as bad as gas prices.  <img src='http://blog.nearlyfreespeech.net/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scheduled Maintenance: IP Renumbering In Progress by jdw</title>
		<link>http://blog.nearlyfreespeech.net/2008/09/11/scheduled-maintenance-ip-renumbering-in-progress/#comment-8312</link>
		<dc:creator>jdw</dc:creator>
		<pubDate>Thu, 18 Sep 2008 22:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nearlyfreespeech.net/?p=47#comment-8312</guid>
		<description>&lt;b&gt;intgr, that's a really good point.  We were afraid to bring up IPv6 on the members.nearlyfreespeech.net name, because it would cause lousy performance for people on seedy tunnel brokers who pref IPv6 over IPv4 over the same name, which I think is most people at this stage of IPv6 deployment.  (I think the same reasoning is behind &lt;a href="http://ipv6.google.com/" rel="nofollow"&gt;ipv6.google.com&lt;/a&gt;.)  I personally had quite a bit of trouble with exactly that at home using the Airport Extreme default IPv6 setup, but then I switched to the &lt;a href="http://tunnelbroker.net/" rel="nofollow"&gt;Hurricane Electric tunnel broker&lt;/a&gt;.  Now my IPv6 at home flies and is totally usable.  Highly recommended.

I would like it if assigning an IPv6 address on a site-by-site or alias-by-alias basis was an option by the end of the year, but I'm certainly not going to guarantee that at this early stage.

Also, just to let people know... As warned, I did have to delete a couple of comments that were about unrelated issues, like the recent DDOS attack.  If you have questions about or problems with our service, please feel free to post in our member forums or submit a secure support request.  We want to hear about problems, we're always interested in feedback, and we're not afraid of criticism as long as it's venue-appropriate.

-jdw&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p><b>intgr, that&#8217;s a really good point.  We were afraid to bring up IPv6 on the members.nearlyfreespeech.net name, because it would cause lousy performance for people on seedy tunnel brokers who pref IPv6 over IPv4 over the same name, which I think is most people at this stage of IPv6 deployment.  (I think the same reasoning is behind <a href="http://ipv6.google.com/" rel="nofollow">ipv6.google.com</a>.)  I personally had quite a bit of trouble with exactly that at home using the Airport Extreme default IPv6 setup, but then I switched to the <a href="http://tunnelbroker.net/" rel="nofollow">Hurricane Electric tunnel broker</a>.  Now my IPv6 at home flies and is totally usable.  Highly recommended.</p>
<p>I would like it if assigning an IPv6 address on a site-by-site or alias-by-alias basis was an option by the end of the year, but I&#8217;m certainly not going to guarantee that at this early stage.</p>
<p>Also, just to let people know&#8230; As warned, I did have to delete a couple of comments that were about unrelated issues, like the recent DDOS attack.  If you have questions about or problems with our service, please feel free to post in our member forums or submit a secure support request.  We want to hear about problems, we&#8217;re always interested in feedback, and we&#8217;re not afraid of criticism as long as it&#8217;s venue-appropriate.</p>
<p>-jdw</b></p>
]]></content:encoded>
	</item>
</channel>
</rss>
