<?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: Dreamhost Sucks</title>
	<atom:link href="http://www.shabooty.com/2008/09/05/dreamhost-sucks.php/feed" rel="self" type="application/rss+xml" />
	<link>http://www.shabooty.com/2008/09/05/dreamhost-sucks.php</link>
	<description>Howard Stern, Hip-Hop, and Booty</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:57:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: nerkn</title>
		<link>http://www.shabooty.com/2008/09/05/dreamhost-sucks.php/comment-page-1#comment-17497</link>
		<dc:creator>nerkn</dc:creator>
		<pubDate>Fri, 23 Jul 2010 10:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.shabooty.com/?p=4493#comment-17497</guid>
		<description>I created a internal_error.html file in the base directory of domain. When error occurs it writes
&quot;hata oldu! error occured! dreamhost sucks! &quot;.

I got these errors from phpmyadmin that they provide! I&#039;m on the edge of hatism</description>
		<content:encoded><![CDATA[<p>I created a internal_error.html file in the base directory of domain. When error occurs it writes<br />
&#8220;hata oldu! error occured! dreamhost sucks! &#8220;.</p>
<p>I got these errors from phpmyadmin that they provide! I&#8217;m on the edge of hatism</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shabooty</title>
		<link>http://www.shabooty.com/2008/09/05/dreamhost-sucks.php/comment-page-1#comment-6138</link>
		<dc:creator>shabooty</dc:creator>
		<pubDate>Sun, 15 Mar 2009 19:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.shabooty.com/?p=4493#comment-6138</guid>
		<description>i still effing get those errors to this day... 
wp-super cache doesnt play nice.
so i disabled it.</description>
		<content:encoded><![CDATA[<p>i still effing get those errors to this day&#8230;<br />
wp-super cache doesnt play nice.<br />
so i disabled it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://www.shabooty.com/2008/09/05/dreamhost-sucks.php/comment-page-1#comment-6137</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Sun, 15 Mar 2009 19:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.shabooty.com/?p=4493#comment-6137</guid>
		<description>Usually you get those 500 internal server errors when you have incorrect permissions or ownership issues. How did you fix it?

I use &lt;a href=&quot;http://www.uptimehost.com&quot; rel=&quot;nofollow&quot;&gt;Uptimehost.com&lt;/a&gt; and they answer very quickly to requests. Maybe dreamhost was swamped that day or something?</description>
		<content:encoded><![CDATA[<p>Usually you get those 500 internal server errors when you have incorrect permissions or ownership issues. How did you fix it?</p>
<p>I use <a href="http://www.uptimehost.com" rel="nofollow">Uptimehost.com</a> and they answer very quickly to requests. Maybe dreamhost was swamped that day or something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T</title>
		<link>http://www.shabooty.com/2008/09/05/dreamhost-sucks.php/comment-page-1#comment-4576</link>
		<dc:creator>T</dc:creator>
		<pubDate>Thu, 30 Oct 2008 02:43:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.shabooty.com/?p=4493#comment-4576</guid>
		<description>This guy (dhsux) is spamming blogs all over the net (just do a Google search) I recommend you delete his comments as spam.</description>
		<content:encoded><![CDATA[<p>This guy (dhsux) is spamming blogs all over the net (just do a Google search) I recommend you delete his comments as spam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dhsux</title>
		<link>http://www.shabooty.com/2008/09/05/dreamhost-sucks.php/comment-page-1#comment-4480</link>
		<dc:creator>dhsux</dc:creator>
		<pubDate>Sat, 11 Oct 2008 21:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.shabooty.com/?p=4493#comment-4480</guid>
		<description>DreamHost&#039;s poor customer service has led to a serious privacy invasion. When my client attempted to sign up for an account, the transaction hung halfway through. When customer service (which can only be reached by tedious email exchanges) &quot;fixed&quot; the problem, the pay by credit card option was no longer available. The customer service representative insisted that we use Google Payments. I proceeded, and then my client realized his financial information is now in the Google system. The worst possible scenario then came true. Instead of completing the transaction, Google called my client&#039;s bank for &quot;preapproval&quot;. This was not to complete the transaction (which was never completed), but to gather information for Google&#039;s marketing. My client is furious, reviewing everyone&#039;s privacy policy,  and is looking into ways to bring this problem up at the political, and possibly the legal, level. 

Throughout this whole situation, Dreamhost has been nothing but pig-headed. Every customer service representative ignores the case history and either refers us back to Google Payments or says patronizing things like we could have paid with the original credit card system. I offered them a solution where I quietly pay for the account using Google transactions, and they won&#039;t even let me help bail them out!!!

I will never refer another client to dreamhost. Right now I&#039;m looking for the best place to air this complaint publicly in as many places as possible. People have to know that when Dreamhost pushes people into using Google Payments, Google then has their financial information to aggregate and deploy for their own purposes. 

Addendum: Dreamhost customer service reps hurl abuse at complainers on their forums. One of them accidentally used his forum ID in an email with the customer service issue header on it. Any other company would fire employees who did that, but abusing customers instead of fixing problems is probably part of Dreamhost&#039;s official policy.</description>
		<content:encoded><![CDATA[<p>DreamHost&#8217;s poor customer service has led to a serious privacy invasion. When my client attempted to sign up for an account, the transaction hung halfway through. When customer service (which can only be reached by tedious email exchanges) &#8220;fixed&#8221; the problem, the pay by credit card option was no longer available. The customer service representative insisted that we use Google Payments. I proceeded, and then my client realized his financial information is now in the Google system. The worst possible scenario then came true. Instead of completing the transaction, Google called my client&#8217;s bank for &#8220;preapproval&#8221;. This was not to complete the transaction (which was never completed), but to gather information for Google&#8217;s marketing. My client is furious, reviewing everyone&#8217;s privacy policy,  and is looking into ways to bring this problem up at the political, and possibly the legal, level. </p>
<p>Throughout this whole situation, Dreamhost has been nothing but pig-headed. Every customer service representative ignores the case history and either refers us back to Google Payments or says patronizing things like we could have paid with the original credit card system. I offered them a solution where I quietly pay for the account using Google transactions, and they won&#8217;t even let me help bail them out!!!</p>
<p>I will never refer another client to dreamhost. Right now I&#8217;m looking for the best place to air this complaint publicly in as many places as possible. People have to know that when Dreamhost pushes people into using Google Payments, Google then has their financial information to aggregate and deploy for their own purposes. </p>
<p>Addendum: Dreamhost customer service reps hurl abuse at complainers on their forums. One of them accidentally used his forum ID in an email with the customer service issue header on it. Any other company would fire employees who did that, but abusing customers instead of fixing problems is probably part of Dreamhost&#8217;s official policy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

