<?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: When a Web Host Goes Bad</title>
	<atom:link href="http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/feed/" rel="self" type="application/rss+xml" />
	<link>http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/</link>
	<description>Linux and other Techie Stuff</description>
	<pubDate>Wed, 07 Jan 2009 05:25:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ScottW</title>
		<link>http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/comment-page-1/#comment-23</link>
		<dc:creator>ScottW</dc:creator>
		<pubDate>Wed, 16 Jan 2008 13:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://merlinsminute.com/2007/10/05/when-a-web-host-goes-bad/#comment-23</guid>
		<description>Wow! Never figured I'd ever need to update this old post but it seems that LP is now acting out of spite due to an incident over at DreamHost. Something about them having a billing error that caused over-charges to their customers.

Way to go LP! Taking that High Road, eh? Right. Acting as expected is more what I'd call it albeit, not totally "unexpected" considering the type of class act that you have going over there.

Here are the pertinent links:

DreamHost's Blog: http://blog.dreamhost.com/2008/01/15/um-whoops/

LP's Blog (gag): http://blog.lunarpages.com/2008/01/15/dreamhost-robbing-their-customers/

You'll notice that LP's comment is close to the top of DreamHost's post. This Tiara made darn sure she got her (LP's) stab in early. Not to mention that the title of LP's post concerning the sad error at DreamHost is somewhat "accusatory" in nature. I don't know that I'd post publicly a statement like that. That might be grounds for DreamHost to consult legal council. But then they'd be faced with that fantastic legal team that LP has. Oooh!

There does seem to be one bright individual in all of this mess though: HostGator's response to this on WebHostingTalk.com was admirable. They seem to know how to take the high road in all of this without beating DreamHost down any further nor tempting their customers away with offers of their own. Their post on this topic is here: http://www.webhostingtalk.com/showpost.php?p=4906999&#038;postcount=20

Like I said: Class act.</description>
		<content:encoded><![CDATA[<p>Wow! Never figured I&#8217;d ever need to update this old post but it seems that LP is now acting out of spite due to an incident over at DreamHost. Something about them having a billing error that caused over-charges to their customers.</p>
<p>Way to go LP! Taking that High Road, eh? Right. Acting as expected is more what I&#8217;d call it albeit, not totally &#8220;unexpected&#8221; considering the type of class act that you have going over there.</p>
<p>Here are the pertinent links:</p>
<p>DreamHost&#8217;s Blog: <a href="http://blog.dreamhost.com/2008/01/15/um-whoops/" rel="nofollow">http://blog.dreamhost.com/2008/01/15/um-whoops/</a></p>
<p>LP&#8217;s Blog (gag): <a href="http://blog.lunarpages.com/2008/01/15/dreamhost-robbing-their-customers/" rel="nofollow">http://blog.lunarpages.com/2008/01/15/dreamhost-robbing-their-customers/</a></p>
<p>You&#8217;ll notice that LP&#8217;s comment is close to the top of DreamHost&#8217;s post. This Tiara made darn sure she got her (LP&#8217;s) stab in early. Not to mention that the title of LP&#8217;s post concerning the sad error at DreamHost is somewhat &#8220;accusatory&#8221; in nature. I don&#8217;t know that I&#8217;d post publicly a statement like that. That might be grounds for DreamHost to consult legal council. But then they&#8217;d be faced with that fantastic legal team that LP has. Oooh!</p>
<p>There does seem to be one bright individual in all of this mess though: HostGator&#8217;s response to this on WebHostingTalk.com was admirable. They seem to know how to take the high road in all of this without beating DreamHost down any further nor tempting their customers away with offers of their own. Their post on this topic is here: <a href="http://www.webhostingtalk.com/showpost.php?p=4906999&#038;postcount=20" rel="nofollow">http://www.webhostingtalk.com/showpost.php?p=4906999&#038;postcount=20</a></p>
<p>Like I said: Class act.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bulletin News</title>
		<link>http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/comment-page-1/#comment-18</link>
		<dc:creator>Bulletin News</dc:creator>
		<pubDate>Tue, 23 Oct 2007 22:16:31 +0000</pubDate>
		<guid isPermaLink="false">http://merlinsminute.com/2007/10/05/when-a-web-host-goes-bad/#comment-18</guid>
		<description>Bodacious write up covering When a Web Host Goes Bad. I love your point of view!</description>
		<content:encoded><![CDATA[<p>Bodacious write up covering When a Web Host Goes Bad. I love your point of view!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unofficial DreamHost Blog</title>
		<link>http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/comment-page-1/#comment-21</link>
		<dc:creator>Unofficial DreamHost Blog</dc:creator>
		<pubDate>Tue, 23 Oct 2007 17:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://merlinsminute.com/2007/10/05/when-a-web-host-goes-bad/#comment-21</guid>
		<description>&lt;strong&gt;Free Hosting to Lunarpages Refugees&lt;/strong&gt;


Lunarpages has silently added a new 404 File Not Found page to all customer accounts. The page displays the domain name of the account holder, a search box which returns sponsored ad results and a number of links (dating, mortgage, ringtones, etc.) to...</description>
		<content:encoded><![CDATA[<p><strong>Free Hosting to Lunarpages Refugees</strong></p>
<p>Lunarpages has silently added a new 404 File Not Found page to all customer accounts. The page displays the domain name of the account holder, a search box which returns sponsored ad results and a number of links (dating, mortgage, ringtones, etc.) to&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why I Left Lunarpages Web Hosting &#124; Thu Tu&#8217;s Blog</title>
		<link>http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/comment-page-1/#comment-19</link>
		<dc:creator>Why I Left Lunarpages Web Hosting &#124; Thu Tu&#8217;s Blog</dc:creator>
		<pubDate>Tue, 23 Oct 2007 17:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://merlinsminute.com/2007/10/05/when-a-web-host-goes-bad/#comment-19</guid>
		<description>[...] Minute: When a Web Host Goes Bad. Particularly, check out a comment written by a Lunarpages employee, a.ka. LP Fan. It's not an [...]</description>
		<content:encoded><![CDATA[<p>[...] Minute: When a Web Host Goes Bad. Particularly, check out a comment written by a Lunarpages employee, a.ka. LP Fan. It&#8217;s not an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Former LP Fan</title>
		<link>http://themysticbird.com/2007/10/05/when-a-web-host-goes-bad/comment-page-1/#comment-22</link>
		<dc:creator>Former LP Fan</dc:creator>
		<pubDate>Wed, 17 Oct 2007 19:57:54 +0000</pubDate>
		<guid isPermaLink="false">http://merlinsminute.com/2007/10/05/when-a-web-host-goes-bad/#comment-22</guid>
		<description>@ LP Fan:

Well, I'm glad you are a fan of the company you work for. Several employees were customers before they got jobs working for LP, and continued to be customers even after leaving voluntarily. So, sure some might have been "former employees", but that misses the point.

I was never an employee and actually turned down a Mod position on the forums because I wanted to retain the right to call LP when they messed up on things. In this case, they definitely messed up big time. The majority of complaints I've seen are from customers who (as far as I know) were never employees of LP.

As for the so called "test", this is something they put in place with NO announcement to any customer. I think it was a "test" in the sense that they wanted to see if anyone noticed and/or complained. And boy did they get an answer to that one. There has still never been an official posting regarding this "test". The closest thing that I've seen were posts in the threads that have been removed from public viewing where they stated it was to help fund the free educational websites. This didn't appear until all hell had already broken loose and word was spreading around the internet about it like crazy. LP's solution? Move threads out of public view, ban users from the forum for discussing it, etc. Then, almost a week later, they apparently send out an INTERNAL memo saying that it was just a test and they wouldn't be implementing it.

Well, why not post that to the forums? Oh that's right, how can they announce that a "test" involving customer sites has ended when they never announced the test in the first place? All this would do is stir up more problems with people who never knew about the problem to begin with. My guess is that a lot of LP customers still don't know that this happened, even though they were directly impacted by it.

And I still don't think LP realizes the degree to which they have harmed their relationship with existing customers over this. I used to trust that LP had the best interest of its customers in mind when making decisions, but this shows that I was obviously wrong about that. I don't fault LP for technical issues that come up beyond their control and always felt they provided a reasonably good service. In many ways, I still think they provide a good service. The problem is that I can't trust them any more when it comes to policy and TOS changes that might not be in my best interest. I don't want to wake up one day to discover they've changed their TOS in a manner that has an even greater negative impact on my site/domain than this did. And, if I can't trust them in that area, I begin to loose trust in other areas as well.

To your credit though, at least you were honest in admitting you were an employee before posting the nonsense that you did...</description>
		<content:encoded><![CDATA[<p>@ LP Fan:</p>
<p>Well, I&#8217;m glad you are a fan of the company you work for. Several employees were customers before they got jobs working for LP, and continued to be customers even after leaving voluntarily. So, sure some might have been &#8220;former employees&#8221;, but that misses the point.</p>
<p>I was never an employee and actually turned down a Mod position on the forums because I wanted to retain the right to call LP when they messed up on things. In this case, they definitely messed up big time. The majority of complaints I&#8217;ve seen are from customers who (as far as I know) were never employees of LP.</p>
<p>As for the so called &#8220;test&#8221;, this is something they put in place with NO announcement to any customer. I think it was a &#8220;test&#8221; in the sense that they wanted to see if anyone noticed and/or complained. And boy did they get an answer to that one. There has still never been an official posting regarding this &#8220;test&#8221;. The closest thing that I&#8217;ve seen were posts in the threads that have been removed from public viewing where they stated it was to help fund the free educational websites. This didn&#8217;t appear until all hell had already broken loose and word was spreading around the internet about it like crazy. LP&#8217;s solution? Move threads out of public view, ban users from the forum for discussing it, etc. Then, almost a week later, they apparently send out an INTERNAL memo saying that it was just a test and they wouldn&#8217;t be implementing it.</p>
<p>Well, why not post that to the forums? Oh that&#8217;s right, how can they announce that a &#8220;test&#8221; involving customer sites has ended when they never announced the test in the first place? All this would do is stir up more problems with people who never knew about the problem to begin with. My guess is that a lot of LP customers still don&#8217;t know that this happened, even though they were directly impacted by it.</p>
<p>And I still don&#8217;t think LP realizes the degree to which they have harmed their relationship with existing customers over this. I used to trust that LP had the best interest of its customers in mind when making decisions, but this shows that I was obviously wrong about that. I don&#8217;t fault LP for technical issues that come up beyond their control and always felt they provided a reasonably good service. In many ways, I still think they provide a good service. The problem is that I can&#8217;t trust them any more when it comes to policy and TOS changes that might not be in my best interest. I don&#8217;t want to wake up one day to discover they&#8217;ve changed their TOS in a manner that has an even greater negative impact on my site/domain than this did. And, if I can&#8217;t trust them in that area, I begin to loose trust in other areas as well.</p>
<p>To your credit though, at least you were honest in admitting you were an employee before posting the nonsense that you did&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
