<?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: ICDSoft Wrapup</title>
	<atom:link href="http://mikelococo.com/2006/04/icdsoft-wrapup/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikelococo.com/2006/04/icdsoft-wrapup/</link>
	<description>Foo-Fu and other favorites...</description>
	<lastBuildDate>Thu, 29 Mar 2012 22:15:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: ICDSoft Rocks (not)! &#124; Bulbous, Not Tapered</title>
		<link>http://mikelococo.com/2006/04/icdsoft-wrapup/comment-page-1/#comment-31612</link>
		<dc:creator>ICDSoft Rocks (not)! &#124; Bulbous, Not Tapered</dc:creator>
		<pubDate>Mon, 18 Oct 2010 04:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://mikelococo.com/2006/04/icdsoft-wrapup/#comment-31612</guid>
		<description>[...] Shortly after this post, I stopped using ICDSoft as a host due to this incident. Read ICDSoft wrapup for details. In short, they contacted me privately in an an email that conveyed considerable [...]</description>
		<content:encoded><![CDATA[<p>[...] Shortly after this post, I stopped using ICDSoft as a host due to this incident. Read ICDSoft wrapup for details. In short, they contacted me privately in an an email that conveyed considerable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://mikelococo.com/2006/04/icdsoft-wrapup/comment-page-1/#comment-16327</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 26 Aug 2008 04:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://mikelococo.com/2006/04/icdsoft-wrapup/#comment-16327</guid>
		<description>I went with laughingsquid, mainly because their &lt;a href=&quot;http://laughingsquid.net/aup/&quot; rel=&quot;nofollow&quot;&gt;acceptable use policy&lt;/a&gt; is reasonable and understandable, and they boast a customer list of artists and bloggers that would be very unlikely to put up with the kind of content antics ICDSoft attempted.

They&#039;re not the cheapest hosting provider by any stretch, and their feature-list is somewhat humdrum (I&#039;m still waiting for a fully-managed WordPress service, where they handle updates and such).  On the plus side:

&lt;ul&gt;&lt;li&gt;Reliability is good, I think there&#039;s been two-hours of downtime since I signed up with them in May of last year.&lt;/li&gt;
&lt;li&gt;Support is very good.  I haven&#039;t needed it a lot, but when I do ask questions they&#039;re not trivial and I&#039;ve gotten helpful responses from knowledgeable techs.&lt;/li&gt;
&lt;li&gt;Performance seems good.  My site is not high-traffic, nor have I done and objective stress tests.  I&#039;ve never been disappointed by response-time, though.&lt;/li&gt;&lt;/ul&gt;</description>
		<content:encoded><![CDATA[<p>I went with laughingsquid, mainly because their <a href="http://laughingsquid.net/aup/" rel="nofollow">acceptable use policy</a> is reasonable and understandable, and they boast a customer list of artists and bloggers that would be very unlikely to put up with the kind of content antics ICDSoft attempted.</p>
<p>They&#8217;re not the cheapest hosting provider by any stretch, and their feature-list is somewhat humdrum (I&#8217;m still waiting for a fully-managed WordPress service, where they handle updates and such).  On the plus side:</p>
<ul>
<li>Reliability is good, I think there&#8217;s been two-hours of downtime since I signed up with them in May of last year.</li>
<li>Support is very good.  I haven&#8217;t needed it a lot, but when I do ask questions they&#8217;re not trivial and I&#8217;ve gotten helpful responses from knowledgeable techs.</li>
<li>Performance seems good.  My site is not high-traffic, nor have I done and objective stress tests.  I&#8217;ve never been disappointed by response-time, though.</li>
</ul>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jane</title>
		<link>http://mikelococo.com/2006/04/icdsoft-wrapup/comment-page-1/#comment-16326</link>
		<dc:creator>Jane</dc:creator>
		<pubDate>Tue, 26 Aug 2008 03:38:55 +0000</pubDate>
		<guid isPermaLink="false">http://mikelococo.com/2006/04/icdsoft-wrapup/#comment-16326</guid>
		<description>So ... who did you go with? I&#039;m trying to make a decision for my companies&#039; sites. Who did you choose and why?</description>
		<content:encoded><![CDATA[<p>So &#8230; who did you go with? I&#8217;m trying to make a decision for my companies&#8217; sites. Who did you choose and why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://mikelococo.com/2006/04/icdsoft-wrapup/comment-page-1/#comment-49</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Sat, 08 Apr 2006 15:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://mikelococo.com/2006/04/icdsoft-wrapup/#comment-49</guid>
		<description>Thanks for the comment, Sean.  Clearly I was concerned about the situation.  I did, after all, switch hosts and risk my search engine rankings by changing URI&#039;s.  I do want to be careful here to present facts and let the reader make their own judgments, though, in contrast to my original post where I did a lot of editorializing and interpretation.

But I agree with you that this sort of thing is probably more common than people think, and that&#039;s the big impetus behind the move.  If it happens again, I&#039;ll be able make risk assessments for myself, rather than having to worry about other people who use and maintain the site getting sucked into the fray based purely on proximity.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment, Sean.  Clearly I was concerned about the situation.  I did, after all, switch hosts and risk my search engine rankings by changing URI&#8217;s.  I do want to be careful here to present facts and let the reader make their own judgments, though, in contrast to my original post where I did a lot of editorializing and interpretation.</p>
<p>But I agree with you that this sort of thing is probably more common than people think, and that&#8217;s the big impetus behind the move.  If it happens again, I&#8217;ll be able make risk assessments for myself, rather than having to worry about other people who use and maintain the site getting sucked into the fray based purely on proximity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://mikelococo.com/2006/04/icdsoft-wrapup/comment-page-1/#comment-48</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Sat, 08 Apr 2006 05:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://mikelococo.com/2006/04/icdsoft-wrapup/#comment-48</guid>
		<description>Censorship no...threatening you with policy violations? Oh yes! Personally, I can&#039;t see the difference. 

 Unfortunately, the section found under ICDSoft&#039;s &quot;abuse&quot; heading on it&#039;s terms of use page seems to be fairly common among web hosting services.  So their is plenty of censorship going on - they just prefer to call it something else.</description>
		<content:encoded><![CDATA[<p>Censorship no&#8230;threatening you with policy violations? Oh yes! Personally, I can&#8217;t see the difference. </p>
<p> Unfortunately, the section found under ICDSoft&#8217;s &#8220;abuse&#8221; heading on it&#8217;s terms of use page seems to be fairly common among web hosting services.  So their is plenty of censorship going on &#8211; they just prefer to call it something else.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

