<?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: Was I too mean? (long, rambly, and techy)</title>
	<atom:link href="http://www.office-monkey.com/2008/11/05/was-i-too-mean-long-rambly-and-techy/feed/?http://www.office-monkey.com:80/office-monkey/2008/11/05/was-i-too-mean-long-rambly-and-techy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.office-monkey.com/2008/11/05/was-i-too-mean-long-rambly-and-techy/</link>
	<description>Everybody needs some monkey sometime...</description>
	<lastBuildDate>Fri, 23 Oct 2009 06:13:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Warth Publishing Inc</title>
		<link>http://www.office-monkey.com/2008/11/05/was-i-too-mean-long-rambly-and-techy/comment-page-1/#comment-8494</link>
		<dc:creator>Warth Publishing Inc</dc:creator>
		<pubDate>Sat, 08 Nov 2008 02:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.office-monkey.com/?p=530#comment-8494</guid>
		<description>You are one of the few people that i have come accross that is happy with 1and1. I don&#039;t have any beef with 1and1&#039;s web hosting. However, I curse the day I ever listed any domains with them. Check out Red Flag for some customer comments.
It should be a warning that when their phone is answered by a recording that tells you if you have gotten a notice from NCO, a collection agency, to press a certain number. If they are a reputable business, why do they have to send so many accounts to a collection agency?
The Eastern Pennsylvania /Washington DC Better Business Bureau have given 1and1 an “unsatisfactory” rating. It is my understanding that 1and1 gets a complaint almost every day. An investigative journalist, Kelli Jack has written a series of articles about them and has a pending law suit. She says: “1and1 Should Be Shut Down.”</description>
		<content:encoded><![CDATA[<p>You are one of the few people that i have come accross that is happy with 1and1. I don&#8217;t have any beef with 1and1&#8242;s web hosting. However, I curse the day I ever listed any domains with them. Check out Red Flag for some customer comments.<br />
It should be a warning that when their phone is answered by a recording that tells you if you have gotten a notice from NCO, a collection agency, to press a certain number. If they are a reputable business, why do they have to send so many accounts to a collection agency?<br />
The Eastern Pennsylvania /Washington DC Better Business Bureau have given 1and1 an “unsatisfactory” rating. It is my understanding that 1and1 gets a complaint almost every day. An investigative journalist, Kelli Jack has written a series of articles about them and has a pending law suit. She says: “1and1 Should Be Shut Down.”</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.office-monkey.com/2008/11/05/was-i-too-mean-long-rambly-and-techy/comment-page-1/#comment-8486</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 06 Nov 2008 21:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.office-monkey.com/?p=530#comment-8486</guid>
		<description>I had already been escalated -- and was everytime I replied, which seems silly; I had the same incident ID, but on every reply it needed to be re-escalated.

I finally spoke to a guy named &quot;Wayne&quot; on the phone. He was more explicit on why they couldn&#039;t commit to any patch schedule, but it still boils down to the same set of information. They need to verify the patch themselves before deploying; they need to batch the patches together to minimize down time; they need to evaluate the impact and appropriateness of the patch; and then they need to stagger installations across multiple groups of servers.

All true, but the conclusion was that they couldn&#039;t even confirm that the patch would eventually be considered for application, and if I want to remain with GoDaddy, I will have to alter every plugin and application written in PHP to remove the /office-monkey prefix, but only when it&#039;s present -- and different for each subdomain I&#039;m applying the application to.</description>
		<content:encoded><![CDATA[<p>I had already been escalated &#8212; and was everytime I replied, which seems silly; I had the same incident ID, but on every reply it needed to be re-escalated.</p>
<p>I finally spoke to a guy named &#8220;Wayne&#8221; on the phone. He was more explicit on why they couldn&#8217;t commit to any patch schedule, but it still boils down to the same set of information. They need to verify the patch themselves before deploying; they need to batch the patches together to minimize down time; they need to evaluate the impact and appropriateness of the patch; and then they need to stagger installations across multiple groups of servers.</p>
<p>All true, but the conclusion was that they couldn&#8217;t even confirm that the patch would eventually be considered for application, and if I want to remain with GoDaddy, I will have to alter every plugin and application written in PHP to remove the /office-monkey prefix, but only when it&#8217;s present &#8212; and different for each subdomain I&#8217;m applying the application to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sora</title>
		<link>http://www.office-monkey.com/2008/11/05/was-i-too-mean-long-rambly-and-techy/comment-page-1/#comment-8484</link>
		<dc:creator>Sora</dc:creator>
		<pubDate>Thu, 06 Nov 2008 18:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.office-monkey.com/?p=530#comment-8484</guid>
		<description>I&#039;m not surprised in the least at how they responded, frankly. Front-line support is, with relatively few exceptions for individual people, simply &lt;i&gt;not capable&lt;/i&gt; of understanding the base issue here. All they know is what they told you -- if you&#039;re lucky, they might file a case with their DEV team.

I think your email was perfect -- it makes it pretty damn clear that you know what you&#039;re talking about, and don&#039;t want to settle for their bullshit answer. It gives them the choice of either giving you the BS again (knowing it&#039;ll piss you off and possibly lose your business), or trying to escalate the issue up their chain. Which, tbh, is the best result you can realistically hope for.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not surprised in the least at how they responded, frankly. Front-line support is, with relatively few exceptions for individual people, simply <i>not capable</i> of understanding the base issue here. All they know is what they told you &#8212; if you&#8217;re lucky, they might file a case with their DEV team.</p>
<p>I think your email was perfect &#8212; it makes it pretty damn clear that you know what you&#8217;re talking about, and don&#8217;t want to settle for their bullshit answer. It gives them the choice of either giving you the BS again (knowing it&#8217;ll piss you off and possibly lose your business), or trying to escalate the issue up their chain. Which, tbh, is the best result you can realistically hope for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://www.office-monkey.com/2008/11/05/was-i-too-mean-long-rambly-and-techy/comment-page-1/#comment-8479</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 06 Nov 2008 01:17:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.office-monkey.com/?p=530#comment-8479</guid>
		<description>Mean?  Not in the slightest.  I am flabbergasted that they actually suggested you work around the issue by hand-editing all of your sources instead of offering to apply the hotfix (or, at the *very* least, promising a future application of said hotfix).  

Let us know how they respond to your missive.</description>
		<content:encoded><![CDATA[<p>Mean?  Not in the slightest.  I am flabbergasted that they actually suggested you work around the issue by hand-editing all of your sources instead of offering to apply the hotfix (or, at the *very* least, promising a future application of said hotfix).  </p>
<p>Let us know how they respond to your missive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

