<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Smackdown! &#187; customer service</title>
	<atom:link href="http://smackdown.blogsblogsblogs.com/category/customer-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://smackdown.blogsblogsblogs.com</link>
	<description>Smackdown!</description>
	<lastBuildDate>Tue, 22 Nov 2011 22:40:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Brandlink Communications, TheBloggess, PR Fails, and Fallout</title>
		<link>http://smackdown.blogsblogsblogs.com/2011/10/08/brandlink-communications-the-bloggess-pr-fails-and-fallout/</link>
		<comments>http://smackdown.blogsblogsblogs.com/2011/10/08/brandlink-communications-the-bloggess-pr-fails-and-fallout/#comments</comments>
		<pubDate>Sat, 08 Oct 2011 17:51:12 +0000</pubDate>
		<dc:creator>Michael VanDeMar</dc:creator>
				<category><![CDATA[blogthropology]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[freedom-of-speech]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[lackofmeds]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=1016</guid>
		<description><![CDATA[Before reading the rest of this post, if you are not already an avid fan of TheBloggess, and have not read about the PR company vice president who called her a &#8220;fucking bitch&#8221; due to him being clueless who it was his company was pitching, then you should start here first: Brandlink Communications. Go ahead [...]]]></description>
			<content:encoded><![CDATA[<p>Before reading the rest of this post, if you are not already an avid fan of TheBloggess, and have not read about the PR company vice president who called her a &#8220;fucking bitch&#8221; due to him being clueless who it was his company was pitching, then you should start here first: <a href="http://thebloggess.com/2011/10/and-then-the-pr-guy-called-me-a-fucking-bitch-i-cant-even-make-this-shit-up/" target="_blank">Brandlink Communications</a>. Go ahead and read it now, I will wait.</p>
<p>&#91;cue elevator music&#93; <span id="more-1016"></span></p>
<p>Ok, good, you&#8217;re back. If you followed some of the aftermath in the comments, on Twitter, and on various media outlets and celebrity blogs around the web (including <a href="http://gawker.com/5847724/pr-firm-calls-blogger-bitch-then-lectures-her-about-manners" target="_blank">Gawker</a> and <a href="http://wilwheaton.typepad.com/wwdnbackup/2011/10/please-stand-by-for-a-demonstration-of-relevancy.html" target="_blank">Wil Wheaton</a>), you can tell that Jenny obviously has a large amount of supporters who were less than pleased at <a href="http://brandlinkcommunications.com/who-we-are/" target="_blank">Jose Douche Canoe Martinez</a>. The outcry got just loud enough that Brandlink Communications actually started to play the <a href="http://twitter.com/#!/BrandlinkComm/status/122329024390365185" target="_blank">wounded bird</a> <a href="http://twitter.com/#!/BrandlinkComm/status/122360161854693378" target="_blank">card</a>:</p>
<p>&nbsp;</p>
<p><img src="/images/twitter-brandlinkvictim1.png" onmouseup="hl2l(event);" alt="Poor us, such the victim"></p>
<p>&nbsp;</p>
<p><img src="/images/twitter-brandlinkvictim2.png" onmouseup="hl2l(event);" alt="Why is everybody picking on me?"></p>
<p>&nbsp;</p>
<p>Apparently Jose Martinez felt so victimized from the whole experience, he actually decided that he needed to delete <a href="http://twitter.com/brandlinkjose" target="_blank">his entire Twitter account</a> (or, of course, it could be that he was trying to do the internet equivalent of burning the evidence of his douchiness).</p>
<p>Quick side note: <strong>if a PR company&#8217;s first instinct when they come under fire is to duck and run, and get defensive, as opposed to owning up, <em>making it right</em>, and the moving on, then odds are that same PR company would not hesitate to throw a client under the bus if they felt it was necessary for their own self preservation.</strong> Anyone who is researching this company with the possibility of hiring them should probably keep that in mind.</p>
<p>Either way, I guess Jenny didn&#8217;t realize quite how much support she would receive, so she wound up actually asking her followers to put away the pitch forks:</p>
<blockquote><p><strong>UPDATED:</strong> I love you people. Really. Thank you for always having my back and for being so supportive during this weirdness. Jose has apologized, and I’ve been assured by the woman in charge of the company that they are aware and are handling it the best way they know how, so let’s give them some air and let them have the chance to do that. *deep breath* &#8211; <em>Jenny Lawson, aka TheBloggess</em></p></blockquote>
<p>Ok, so, maybe Jenny is right. Maybe some of her fans did get abusive towards Jose in the process of defending her (which, btw, I did not see myself, but I am guessing not everyone was polite) and it is time for us to let cooler heads prevail. <em>However&#8230;</em> I also don&#8217;t think this should fall just into internet obscurity, either. People who are looking to hire this PR firm should be able to find out who it is they are dealing with, and the first line of defense when doing research on a company is, of course, Google. Currently when you do a search for [<a href="http://www.google.com/search?num=10&#038;q=brandlink+communications" target="_blank">brandlink communications</a>], someone else&#8217;s post about <a href="http://blog.chron.com/babysteps/2011/10/picking-a-fight-with-the-bloggess-and-other-big-pr-mistakes/" target="_blank">Brandlink and TheBloggess</a> is #1 (as a news story though, not as a regular listing), Brandlink Communications themselves show up next (which is actually the natural #1 listing, when no news stories show), and in the natural #10 spot is Jenny herself:</p>
<p>&nbsp;</p>
<p><a href="/images/brandlinkcommunications-search-20111008.png" target="_blank"><img src="/images/brandlinkcommunications-search-20111008-sm.png" onmouseup="hl2l(event);" alt="Search for [brandlink communications]"></a><br />
(<em>Click to enlarge</em>)</p>
<p>&nbsp;</p>
<p>The news piece is of course only there for a short period of time, as all news pieces should be, and the rankings Jenny&#8217;s site has currently are probably also due to what Google refers to as <a href="http://www.nytimes.com/2007/06/03/business/yourmoney/03google.html?pagewanted=print" target="_blank">QDF, or Query Deserves Freshness</a> (where a particular search might warrant different results due to topic being &#8220;hot&#8221; at the moment). However, I think that Jenny&#8217;s site <em>should</em> be in the top 10 when searching on that company, even after the buzz dies down&#8230; possibly even #1. Therefore, here is what I suggest, if you happen to support Jenny in this issue:</p>
<ol>
<li>Write a post showing your support for Jenny about the way she was treated. Don&#8217;t attack or &#8220;bully&#8221; anyone in the post, because despite them being in the wrong here Brandlink was right, bullying people is still wrong (although calling someone a douche canoe when they actually are one is just being descriptive imo)</li>
<li>In that post, link to Jenny&#8217;s blog post about the conversation, but use the phrase [brandlink communications] as the anchor text for the actual link.</li>
<li>If you link to the post more than once, make sure that link is the <a href="http://smackdown.blogsblogsblogs.com/2007/10/09/you-may-be-screwing-yourself-with-hyperlinked-headers/" target="_blank">first link</a> to the post.</li>
</ol>
<p>For those of you wondering why, it is because links are still the number one factor Google uses when determining rankings. If you want more information on it, you can Google [santorum] and do some research&#8230; just don&#8217;t click on the first link. <img src='http://smackdown.blogsblogsblogs.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Do I think this is too harsh? Perhaps if they weren&#8217;t a PR company boasting <a href="http://brandlinkcommunications.com/clients/" target="_blank">W Hotels and Chase</a> as their clients I might be more inclined to go easy on them. However, even if they weren&#8217;t big shots treating those they regard as the &#8220;little people&#8221; like shit, there is also the fact that this behavior is not new for Jose, and there is evidence of him treating people like this all the way back to <a href="http://gawker.com/153068/perez-hilton-makes-us-hate-ourselves" target="_blank">early 2006</a>. The fact that the same guy is still VP Media Director 5 1/2 years later, still behaving the same way, makes the promises from the company that is &#8220;handling it the best way they know how&#8221; somewhat hollow. So yes, with that in mind I think that a response like this is quite fitting. Vote with your links, people, as Google intended you to. <img src='http://smackdown.blogsblogsblogs.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://smackdown.blogsblogsblogs.com/2011/10/08/brandlink-communications-the-bloggess-pr-fails-and-fallout/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Hacked on GoDaddy? I&#8217;ll Migrate You To Hostgator For Free</title>
		<link>http://smackdown.blogsblogsblogs.com/2010/11/10/hacked-on-godaddy-ill-migrate-you-to-hostgator-for-free/</link>
		<comments>http://smackdown.blogsblogsblogs.com/2010/11/10/hacked-on-godaddy-ill-migrate-you-to-hostgator-for-free/#comments</comments>
		<pubDate>Wed, 10 Nov 2010 17:07:21 +0000</pubDate>
		<dc:creator>Michael VanDeMar</dc:creator>
				<category><![CDATA[blogthropology]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=852</guid>
		<description><![CDATA[Yet again, I am seeing a rising number of sites that are reporting getting hacked at GoDaddy. It is also no surprise to me that people are getting limited responses from them when they try and find out what is going on. The GoDaddy blog mentions nothing recently aside from when they were hacked 2 [...]]]></description>
			<content:encoded><![CDATA[<p>Yet again, I am seeing a rising number of sites that are reporting getting hacked at GoDaddy. It is also no surprise to me that people are getting limited responses from them when they try and find out what is going on. The GoDaddy blog mentions nothing recently aside from when they were <a href="http://community.godaddy.com/godaddy/halloween-eve-hacker-quickly-thwarted/" target="_blank">hacked 2 weeks ago on Halloween</a> (an attack that looks like it stemmed from GoDaddy not acting on a security advisory for 11 days). The thing is, I know from personal experience that they are aware of it, because I have seen cases where they are cleaning clients sites now automatically as a form of damage control, before the clients even know they were hacked, in an attempt to keep the buzz down about it. So they obviously know it is happening yet they are still keeping tight lipped about it, and being reactive instead of proactive, which is of course par for the course when it comes to <a href="http://smackdown.blogsblogsblogs.com/2010/05/13/hosting-with-godaddy-might-want-to-rethink-that-decision/" target="_blank">getting hacked on GoDaddy</a>.</p>
<p>Since this is an established pattern with them as a web host, and even though I still highly recommend them as registrars for domain names,<span id="more-852"></span> I have decided to make this offer to all clients who want to be done with getting their sites hacked. If you hire me to clean your hacked website(s), WordPress or otherwise (since pretty much any site on GoDaddy is subject to getting hacked), and are willing to switch to <a href="http://www.jdoqocy.com/nd115shqnhp48779B7A465965D68" target="_blank">Hostgator</a><img src="http://www.ftjcfx.com/6l98y7B-53PTSSUWSVPRQURQYRT" width="1" height="1" border="0"/> after I have you completely cleaned up (which is where this blog and many of my other sites are hosted, and a host that I highly recommend), then I will do the migration at no extra charge. </p>
<p>That&#8217;s right&#8230; I&#8217;ll move you to <a href="http://www.jdoqocy.com/nd115shqnhp48779B7A465965D68" target="_blank">Hostgator</a><img src="http://www.ftjcfx.com/6l98y7B-53PTSSUWSVPRQURQYRT" width="1" height="1" border="0"/>, for free.</p>
<p>Now, if you want to help me out a little with that, and use the affiliate links in this post or the banner in my sidebar to purchase your hosting, then great, I will get a commission from them for doing it. But that is in no way required for this offer, and not at all why I am making this deal. You can manually type in hostgator.com into your browser, or click on a friend&#8217;s banner, or whatever. I&#8217;ll still move you for free. Everyone should have safe hosting, period, and I am willing to help people get there.</p>
<p>The one caveat with this offer is if you have emails stored on the old server, and use either IMAP or their webmail, and you need those old emails (not the accounts, but the actual emails) moved off of GoDaddy and stored elsewhere, then it does take a few extra minutes per email account, depending on which solution you which to use. GoDaddy doesn&#8217;t give you direct access to download and move them, but there are a couple of workarounds available. Some you can do yourself if you like (like downloading all of the emails to your local computer using POP3), some I can do for you for a very small charge. Other than that for each site I clean I will move it to the new Hostgator account for you at no charge, and that includes the files, the databases, setting up the email accounts, and any ftp users you want to move.</p>
<p>If you are not currently hacked, and want to move to Hostgator anyway, I&#8217;ll still offer anyone who wants it a deal. If it does not need cleaning, I will migrate your entire site for only 30 minutes worth of labor, flat fee, again not counting the moving of the physical emails. If you have multiple sites that need moved, depending on the sizes of them, I can offer you further discounts on those as well. Hell, you don&#8217;t even have to be hosted at GoDaddy to take advantage of this offer. If you&#8217;re unhappy where you are at, just let me know.</p>
<p>Anyone who wants to have me get started on moving them to a better host should <a href="http://smackdown.blogsblogsblogs.com/contact-michael-vandemar/">contact me today</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://smackdown.blogsblogsblogs.com/2010/11/10/hacked-on-godaddy-ill-migrate-you-to-hostgator-for-free/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GoDaddy&#8217;s Suggestion For The Cause Of Their Hacks And Their Community Blog &#8211; Can You Smell The Irony?</title>
		<link>http://smackdown.blogsblogsblogs.com/2010/05/14/godaddys-suggestion-for-the-cause-of-their-hacks-and-their-community-blog-can-you-smell-the-irony/</link>
		<comments>http://smackdown.blogsblogsblogs.com/2010/05/14/godaddys-suggestion-for-the-cause-of-their-hacks-and-their-community-blog-can-you-smell-the-irony/#comments</comments>
		<pubDate>Fri, 14 May 2010 20:52:41 +0000</pubDate>
		<dc:creator>Michael VanDeMar</dc:creator>
				<category><![CDATA[blogthropology]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[lackofmeds]]></category>
		<category><![CDATA[nerdiness]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[WTF]]></category>

		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=680</guid>
		<description><![CDATA[Yesterday I blogged about the hacking situation with GoDaddy hosting and a customer service call I had with them concerning some evidence I had found. While it is true that as this has progressed GoDaddy has widened their scope in investigating what the underlying cause of these hacks are, initially they claimed that the issue [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday I blogged about the <a href="http://smackdown.blogsblogsblogs.com/2010/05/13/hosting-with-godaddy-might-want-to-rethink-that-decision/" target="_blank">hacking situation with GoDaddy hosting</a> and a customer service call I had with them concerning some evidence I had found. While it is true that as this has progressed GoDaddy has widened their scope in investigating what the underlying cause of these hacks are, initially they claimed that the issue was with their customers running outdated versions of WordPress. While being wrong about something like that is usually not <em>that</em> big of a deal, in this particular instance it proved to be beyond irksome, since a large portion of their customer base were told that it was their own fault that their sites got hacked (even in cases where the customer was up to date), and that GoDaddy <a href="http://wordpress.org/support/topic/391658#post-1498431" target="_blank">was in no way to blame</a>:</p>
<blockquote><p>WordPress is a-ok. Go Daddy is rock solid. Neither were &#8216;hacked,&#8217; as some have speculated.</p>
<p>After an extensive investigation, we can report there was a small group of customers negatively impacted. What happened? Those users had outdated versions of the popular blogging software, set up in a particular way. &#8211; <em>Alicia from GoDaddy</em></p></blockquote>
<p>From what I have read around the web customers were being told that it was not GoDaddy&#8217;s responsibility to fix the sites, that they only offered &#8220;limited support&#8221; in situations like this, leaving people with only the option of restoring from a backup (which would often not help even in outdated WordPress hack situations, since hacks can go undetected for months) or hiring outside help to clean things up.</p>
<p>You can see on the support page they have set up, <a href="http://community.godaddy.com/godaddy/whats-up-with-go-daddy-wordpress-php-exploits-and-malware/" target="_blank">What’s Up with Go Daddy, WordPress, PHP Exploits and Malware?</a> that they still claim that outdated scripts are part of the problem. Going to that page and viewing the source reveals something almost unbelievable:</p>
<p><a href="/images/godaddy-outdated-wordpress-lg.png" target="_blank"><img src="/images/godaddy-outdated-wordpress-sm.png" border="0" alt="GoDaddy outdated software...?" onmouseup="hl2l(event);"></a><br />
(<em>click to enlarge</em>)</p>
<p>That&#8217;s right, in a classic &#8220;do as I say, not as I do&#8221; twist it seems that GoDaddy is in fact running an older version of WordPress (WordPress MU, based on the version number, which has the same security holes as regular WordPress) for their community blog that they are using to tell people to upgrade their WordPress versions.</p>
<p>To be fair, simply having an older version of WordPress does not mean that it is automatically insecure&#8230; the security fixes in the more recent versions may be minor and the known vulnerabilities might have been manually patched. I can&#8217;t know without actually digging deeper and <em>looking</em> if in fact the installation was vulnerable.</p>
<p>Then again&#8230; neither can GoDaddy in the case of their customers.</p>
]]></content:encoded>
			<wfw:commentRss>http://smackdown.blogsblogsblogs.com/2010/05/14/godaddys-suggestion-for-the-cause-of-their-hacks-and-their-community-blog-can-you-smell-the-irony/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Hosting With GoDaddy? Might Want To Rethink That Decision.</title>
		<link>http://smackdown.blogsblogsblogs.com/2010/05/13/hosting-with-godaddy-might-want-to-rethink-that-decision/</link>
		<comments>http://smackdown.blogsblogsblogs.com/2010/05/13/hosting-with-godaddy-might-want-to-rethink-that-decision/#comments</comments>
		<pubDate>Thu, 13 May 2010 15:04:59 +0000</pubDate>
		<dc:creator>Michael VanDeMar</dc:creator>
				<category><![CDATA[blogthropology]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[WTF]]></category>

		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=671</guid>
		<description><![CDATA[One of the services I offer people is cleaning their WordPress installations of hacks and infections, mostly for those who might not have the time or technical expertise to follow my hacked WordPress cleaning guide. Therefore when something happens that increases the number of people getting hacked, such as when a new exploit is discovered, [...]]]></description>
			<content:encoded><![CDATA[<p>One of the services I offer people is cleaning their WordPress installations of hacks and infections, mostly for those who might not have the time or technical expertise to follow my <a href="http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/">hacked WordPress cleaning guide</a>. Therefore when something happens that increases the number of people getting hacked, such as when <a href="http://lorelle.wordpress.com/2009/09/04/old-wordpress-versions-under-attack/" target="_blank">a new exploit is discovered</a>, or a security hole in a large host starts getting exploited (like <a href="http://blog.networksolutions.com/2010/we-feel-your-pain-and-are-working-hard-to-fix-this/" target="_blank">what happened with Network Solutions last month</a>), I get an increase in the number of people requesting help cleaning things up. This month it started happening with a large number of <a href="http://www.godaddy.com/" target="_blank">GoDaddy</a> customers.</p>
<p>When it first started to happen I did some searching around, and noticed that there was some discussion going on about the heightened GoDaddy hacking activity, but at that time everything I read that stated the problem was with GoDaddy customers all had roots pointing back to a single post on a company blog that didn&#8217;t offer enough details for me to really see why it was happening there and not other places. Not that WordPress on other hosts weren&#8217;t still getting hacked, but there has definitely been a higher concentration of instances on GoDaddy. GoDaddy was definitely aware of the issue, and even replied in some threads on the <a href="http://wordpress.org/support/topic/391658" target="_blank">WordPress.org help forum</a>:</p>
<blockquote><p>GoDaddy.com did send out a notification to customers affected by this issue. Although I know you would prefer not to be linked, I want to avoid flooding the forum. For a step-by-step guide to update WordPress, please visit <a href="http://fwd4.me/NGN" target="_blank">http://fwd4.me/NGN</a> &#8211; <em>Alicia from GoDaddy.com</em></p></blockquote>
<p>The link to their &#8220;step-by-step guide&#8221; to updating WordPress turns out to be nothing more than than a link back to WordPress&#8217; own guide to upgrading, and links on how to back up your stuff on GoDaddy. Decidedly not step-by-step imo, and in this case not all that helpful. If the reason your site gets hacked is due to you running an older, insecure version of WordPress, once that happens simply upgrading will not fix the issue. This seems to me to be a bit of a lame response to a serious issue coming from a company that bills itself as the &#8220;World&#8217;s largest Hosting Provider&#8221;. </p>
<p>GoDaddy keeps <a href="http://community.godaddy.com/godaddy/wordpress-compromised-how-to-fix-it/" target="_blank">insisting that the problem is due to outdated WordPress installations</a>, and that staying up to date and site security is the responsibility of the customer, not of GoDaddy. In one sense I completely agree with them. If you run an older version of WordPress that has known security holes in it (ie. pretty much all versions aside from the most recent) then the odds are that you are going to get hacked. Most of the clients I cleaned from GoDaddy so far were up to date, running version 2.9.2, but this still didn&#8217;t mean that it was GoDaddy&#8217;s fault, since it is possible for a site to get hacked and no signs show up for months. This means that the sites I was cleaning could potentially have had the hack from an older version, and it only became apparent some time after they upgraded. </p>
<p>The problem is that after doing some <em>very</em> thorough clean up jobs (ie. wipe and reinstall), and making sure the clients were up to date, all passwords changed, all image files verified as actual images, clean WordPress, clean theme, clean plugins, and hand cleaning the database, I had clients <strong>still</strong> getting re-hacked.</p>
<p>One client I had was having issues with funky characters in his posts. He would make the post, everything would be fine, and then the next day they would be converted in a way that would make them display as unicode. This was well after I had done my cleaning, and no one should have made any changes to the database since then. My assumption was that GoDaddy themselves was making changes, possibly security upgrades related to the recent hacking waves, and I figured that calling them to see what they had done would be the best bet. In preparation for this I went ahead and logged into the client&#8217;s account, and ftp&#8217;d into the server just to make sure everything looked like it was in place still. As soon as I did I saw that about 30 minutes before a brand new, non-Wordpress, oddly named php file had been dropped into my client&#8217;s site.</p>
<p>I downloaded the file and looked at it. I suddenly realized that this was the source file for all of the hacks that were happening. It was named &#8220;plan_erich.php&#8221;, and had similar eval(base64_decode( instruction at the top of the file. I modified the code to be able to decrypt it safely, and looked through the output (which you can view <a href="/images/plan_erich_php.txt">here</a>). The script was designed to delete itself as soon as it ran:</p>
<p><code>$z=$_SERVER["SCRIPT_FILENAME"];
@unlink($z);</code></p>
<p>Finding this script before it was triggered and deleted itself was raw luck. Catching this file gave a great opportunity to actually track down how these hacks are occurring, and possibly would leave clues that GoDaddy could use to keep it from happening again. Looking at the owner/creator of the file, and matching that timestamp up with the various logs  (ftp, ssh, http, mysql, etc) could give GoDaddy the information needed to figure out how the file <em>really</em> got there, instead of just guessing that WordPress was the issue. I have never seen a file like this before, and searching Google for the name yielded no results, so there really was no other information out there available on this. Finding it there was a little like hitting the lottery in that respect, random and very, very good luck.</p>
<p><strong>The problem, however, is that GoDaddy didn&#8217;t seem to care.</strong> I called and explained to the woman I spoke with exactly what it was that I found and how it could be useful. I told her that matching up that file to the logs could yield some potentially valuable information. She did listen carefully, and I am pretty sure she understood what I was saying, because she asked if she could put me on hold to go talk with someone who might know more. She came back and informed me that <em>she didn&#8217;t have permission to look at those logs</em>.</p>
<p>I explained again, in a little more detail, why looking at the section of those logs was very important, and if she didn&#8217;t have permission could she please escalate the ticket to someone who did. Again, she put me on hold. This time she came back and told me that <em>they were uninterested in escalating it</em>. </p>
<p>At this point I was a teensy bit amazed at GoDaddy&#8217;s lack of concern with the issue. She very kindly informed me that the issue was that the client was running an older version of WordPress, and that we needed to upgrade. Wtf? I went and looked, and made sure that he was indeed still running the 2.9.2 version that I had installed over a week ago (and remember, he was running that version before I ever did anything), and he was. I told her that. She told me that no, she was looking at what the hosting control panel said, and that he was running version 2.6.</p>
<p>That was when it struck me&#8230; GoDaddy was claiming that this wave of WordPress hacks was due to clients not upgrading <em>without even bothering to really look at the clients sites</em>. The hosting control panel can only report what was installed via the hosting control panel itself. If a client pushes the button to upgrade WordPress from within the WordPress admin section then the hosting control panel will never know. </p>
<p>As amazing as it seems, apparently <strong><em>the entire GoDaddy technical support team is ignorant of this fact</em></strong>. That&#8217;s right&#8230; the  &#8220;World’s largest Hosting Provider&#8221; doesn&#8217;t understand the very basics of how the world&#8217;s largest blogging platform works.</p>
<p>Something, probably a hosting configuration, is allowing GoDaddy customers to have their sites hacked, and it isn&#8217;t file permissions, insecure passwords, or out of date software. Not being willing to even <em>look</em> when a developer calls to tell you that they found something is completely unacceptable. My suggestion to all GoDaddy hosting customers: bail now, before something happens to your site. This is not a WordPress issue only&#8230; although it seems to have targeted WordPress customers first, all sites that use php are at risk. Personally for shared hosting I recommend <a href="http://www.jdoqocy.com/nd115shqnhp48779B7A465965D68" target="_blank">Hostgator</a><img src="http://www.ftjcfx.com/6l98y7B-53PTSSUWSVPRQURQYRT" width="1" height="1" border="0"/>, because I love their tech support (and their servers are very robust), but there are plenty of hosts out there to choose from (Disclosure: I changed the previous link to an affiliate link, although if you&#8217;d rather purchase hosting from them without giving me credit that&#8217;s fine too, here is a clean link for you: <a href="http://www.hostgator.com/" target="_blank">HostGator</a>).</p>
<p><a href="http://www.bobparsons.me/" target="_blank">Bob Parsons</a>, I am sorry. Hot chicks and a strong tits and ass marketing campaign do <em>not</em> make up for apathy in matters of client security and well being.</p>
]]></content:encoded>
			<wfw:commentRss>http://smackdown.blogsblogsblogs.com/2010/05/13/hosting-with-godaddy-might-want-to-rethink-that-decision/feed/</wfw:commentRss>
		<slash:comments>159</slash:comments>
		</item>
		<item>
		<title>Amazon Confirms: Shortened URL&#8217;s *Are* Allowed On Facebook and Twitter</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/07/17/amazon-confirms-shortened-urls-are-allowed-on-facebook-and-twitter/</link>
		<comments>http://smackdown.blogsblogsblogs.com/2009/07/17/amazon-confirms-shortened-urls-are-allowed-on-facebook-and-twitter/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 21:10:12 +0000</pubDate>
		<dc:creator>Michael VanDeMar</dc:creator>
				<category><![CDATA[customer service]]></category>
		<category><![CDATA[how-to]]></category>
		<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=363</guid>
		<description><![CDATA[Last week there was some commotion over the fact that it was being reported that Amazon.com was refusing to pay affiliates if they used url shortening services to post affiliate links on social media sites such as Facebook or Twitter. This actually makes no sense from a business perspective, since it would discourage people from [...]]]></description>
			<content:encoded><![CDATA[<p>Last week there was some commotion over the fact that it was being reported that <a href="https://affiliate-program.amazon.com/" target="_blank">Amazon.com</a> was <a href="http://www.searchenginejournal.com/amazon-affiliates-social-media/11654/" target="_blank">refusing to pay affiliates</a> if they used url shortening services to post affiliate links on social media sites such as Facebook or <a href="http://twitter.com/mvandemar/" target="_blank">Twitter</a>. This actually makes no sense from a business perspective, since it would discourage people from sending traffic to Amazon using some of the most popular communication mediums that are out there today.</p>
<p>I decided to go through the <a href="https://affiliate-program.amazon.com/gp/associates/agreement" target="_blank">affiliate operating agreement</a> myself to see <span id="more-363"></span>if I could understand why they were doing this. I realized after I read it that they were <em>not</em> in fact saying any such thing. I wrote them to see what was up, and what the specific issues were. </p>
<p>It took 4 emails to them, with the first 3 coming back with the same answer, that they were not allowed because you are not allowed to use redirects. The problem is that the language of the agreement only mentions redirects in conjunction with either ppc traffic (you cannot link a ppc ad directly to Amazon, or via a redirect, it requires a click from your site to be valid), and with hijacking someone <em>else&#8217;s</em> traffic (no redirecting or interfering with someone else participating in the program). Eventually, however, I got someone who understood what I was saying and they agreed that it is indeed acceptable to do so. Here is there final reply:</p>
<blockquote class="eml"><p>
Dear Michael, </p>
<p>Thank you for writing back to us and I sincerely apologize for the delay in responding to your message.  I have carefully reviewed your correspondence with us.  As you mention, you would not be permitted to use a shortened URL to an Amazon.com page as the destination URL for paid search advertisements because Associates are not permitted to engage in keyword bidding or other paid search on Google, Yahoo, MSN, and other search engines, and their extended search networks, to send traffic to our site.  </p>
<p>However, you can use shortened URLs on your Facebook or Twitter accounts. You may be asked to provide the specific sites on which the shortened URLs are posted, which would mean that your Facebook and Twitter profiles would need to be publicly accessible for review if you used the URLs on those sites.</p>
<p>I apologize for the misunderstanding regarding your inquiry and I hope this information is helpful to you.  If you have further questions, please use the Contact Us form available on Associates Central or by following this link:</p>
<p><a href="https://affiliate-program.amazon.com/gp/associates/contact" target="_blank">https://affiliate-program.amazon.com/gp/associates/contact</a></p>
<p>Thank you for your participation in the Associates Program.</p>
<p>Best regards,</p>
<p>Richard &#8211; Associates Account Specialist</p>
<p>http://www.amazon.com</p>
</blockquote>
<p>Note that he did state that the specific sites where you intended to post the links needed to be provided, so if you are an Amazon affiliate and think you might possibly post a link on either Twitter or Facebook, you should probably submit those profiles to Amazon asap and go ahead and get them listed in your Amazon account. One of the other emails from them gave me these instructions for doing so:</p>
<blockquote class="eml"><p>
If you would like to add another website or multiple websites to your existing Associates account, we first need to view and approve the sites content before it can be added.</p>
<p>Please send us the URLs for the sites, and we will review them and let you know our decision. Once approved, we will send you instructions on how to add the URLs to your account. You can contact us back by using the secure form at the following specialized link:</p>
<p><a href="http://affiliate-program.amazon.com/gp/associates/contact/" target="_blank">http://affiliate-program.amazon.com/gp/associates/contact/</a></p>
<p>Keep in mind that if your Facebook page is set on private we will be unable to approve its addition to your account because we need to be able to view your site at any given time to make sure you are in compliance with our guidelines.
</p></blockquote>
<p>I have gone ahead and provided the entire conversation thread with Amazon <a href="/images/amazon-on-url-shorteners.txt" target="_blank">here</a>. I hope this helps anyone who might have had issues with this. <img src='http://smackdown.blogsblogsblogs.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://smackdown.blogsblogsblogs.com/2009/07/17/amazon-confirms-shortened-urls-are-allowed-on-facebook-and-twitter/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Google Lowers The Bar On Customer Service Yet Again</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/08/01/google-lowers-the-bar-on-customer-service-yet-again/</link>
		<comments>http://smackdown.blogsblogsblogs.com/2008/08/01/google-lowers-the-bar-on-customer-service-yet-again/#comments</comments>
		<pubDate>Fri, 01 Aug 2008 16:56:22 +0000</pubDate>
		<dc:creator>Michael VanDeMar</dc:creator>
				<category><![CDATA[blogthropology]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[lackofmeds]]></category>
		<category><![CDATA[On The Ball-ness]]></category>

		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=89</guid>
		<description><![CDATA[For the second year running Fortune magazine has named Google (GOOG) as the #1 place to work for in America. Their article last year states that Google &#8220;sets the standard for Silicon Valley: free meals, swimming spa, and free doctors onsite. Engineers can spend 20% of time on independent projects. No wonder Google gets 1,300 [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/images/google-switchboard.png" style="float:right;" alt="Can Google customer service get with the times?"  onmouseup="hl2l(event);"> For the second year running Fortune magazine has named <a href="http://money.cnn.com/quote/quote.html?symb=GOOG" target="_blank">Google</a> (GOOG) as <a href="http://money.cnn.com/magazines/fortune/bestcompanies/2007/snapshots/1.html" target="_blank">the #1 place to work for in America</a>. Their article last year states that Google <em>&#8220;sets the standard for Silicon Valley: free meals, swimming spa, and free doctors onsite. Engineers can spend 20% of time on independent projects. No wonder Google gets 1,300 résumés a day.&#8221;</em> Now, I don&#8217;t know about you, but to me numbers like that mean Google doesn&#8217;t have to simply <em>settle</em> when hiring employees&#8230; they literally can pick and choose from the cream of the crop who does and who does not work for them.</p>
<p>In fact, according to Google themselves, <span id="more-89"></span>their goal is to hire people who are &#8220;<a href="http://www.google.com/support/jobs/bin/static.py?page=about.html" target="_blank">as passionate about their lives as they are about their work</a>&#8220;:</p>
<blockquote><p>&#8230; regardless of where we are, we nurture an invigorating, positive environment by hiring talented, local people who share our commitment to creating search perfection and want to have a great time doing it. Googlers thrive in small, focused teams and high-energy environments, believe in the ability of technology to change the world, and are as passionate about their lives as they are about their work. &#8211; <em>Google Jobs</em></p></blockquote>
<p>So why is it a company that concerned about the quality of their employees can&#8217;t seem find anyone decent for their customer service department?</p>
<p>If we were discussing deep complicated technical questions then I could understand a bit of confusion here and there. However, in my experience the reps at Google AdSense and AdWords seem to have problems with some of the most basic concepts of communication. I wrote a post about a month and a half ago about another of my <a href="/2008/06/05/adsense-customer-service-on-new-new-feeds-look-it-up-yourself/" target="_blank">recent communications with AdSense reps that went nowhere</a> (wrote them again, btw, they are still ignoring me). This time, it&#8217;s AdWords.</p>
<p>Let me be clear on this, <em>the issue itself is not that important</em>. I am not losing copious amounts of money, the Internet will not come crashing down if the question isn&#8217;t answered, and no one&#8217;s life is at stake here. However, for a couple of years now the replies that Google customer service sends back have established a solid pattern of non-resolution <em>regardless</em> of how important the questions asked actually are. This week I received an email from AdWords that opened with the following:</p>
<blockquote><p>We noticed that you haven&#8217;t shown your AdWords ads in a while. The Google AdWords Team wants to help you make the most of your advertising dollars, so&#8230;</p></blockquote>
<p>Now, since I had just ran one of my AdWords campaigns not long ago, for my experiment having to do with the <a href="/2008/07/15/why-the-google-keyword-tool-is-useless-for-seo-even-with-exact-numbers/" target="_blank">Google keyword tool</a>, this concerned me a little. It hadn&#8217;t been &#8220;a while&#8221;, as they were claiming, it had only been 2 weeks. So, I wrote them back a one line reply, asking what they were talking about:</p>
<blockquote><p>What&#8217;s this about? I ran an AdWords campaign last week&#8230; &#8211; <em>Me</em></p></blockquote>
<p>They replied today. I looked at what they sent, got a little angry, and almost replied back immediately. However, I decided first to make sure that it wasn&#8217;t my fault, that I hadn&#8217;t somehow perhaps been unclear in what I was asking. I asked 3 friends what their interpretation of what my question had actually been, sort of an early morning IQ test. I showed each of them the same portion of the original email I showed above, as well as my question I replied back to AdWords with, and then asked, <em>&#8220;In your honest opinion, what was my question to them?&#8221;</em> The responses I got back were:</p>
<blockquote><p>wtf did you send me an email saying i haven&#8217;t advertised in a while, when i just did. &#8211; <em><a href="http://www.ebuzzcoach.com/" target="_blank">Donna Fontenot, Business Coach</a></em></p></blockquote>
<blockquote><p>why are you sending me this email, when i have run adwords recently? &#8211; <em><a href="http://www.searchmarketinggurus.com/" target="_blank">Li Evans, Director of Internet Marketing</a></em></p></blockquote>
<blockquote><p>Your question was why are [they] saying your account isn&#8217;t active, when it actually is. &#8211; <em><a href="http://www.statusfirm.com/" target="_blank">Melanie Nathan, Director of SEO/SEM/SMM</a></em></p></blockquote>
<p>As you can see clearly see, <em>none of them are trained Google AdWords customer service representatives</em>. They did not go through intensive schooling designed to teach how to answer complex questions on how AdWords is engineered to make the world a better place. Yet, despite their complete lack of employee orientation, each of them was in fact able to correctly interpret my short question. </p>
<p>The actual AdWords rep who replied, however, was apparently unable to do so:</p>
<blockquote><p>Thank you for your email. I understand you are concerned about an email that you received from AdWords support saying that your ads have not been shown on Google for some time. You received this email since all of your campaigns are either paused or deleted. Please note, your ads won&#8217;t show on Google if your campaigns have been paused or deleted. &#8211; <em>Neha Verma, The Google AdWords Team</em></p></blockquote>
<p>It&#8217;s as if Google wrote an <a href="http://www-ai.ijs.si/eliza/eliza.html" target="_blank">Eliza</a> style program to handle their customer service questions, and <em>almost</em> got it right. Pick out key phrases from the emails, and see if there is a matching canned response. The problem, of course, is that the reply actually came from a real person, hired by a company that professes to employ people who are &#8220;talented&#8221;, and are &#8220;passionate&#8230; about their work.&#8221; </p>
<p>I have had both MSN and Yahoo employees call me on the phone when I was having an issue before. GoDaddy has done that also, as has Hostgator. MSN has &#8220;How did I do?&#8221; type questionnaires that they ask you to fill out after having a question dealt with. Hostgator even has a rating system on their trouble tickets, asking you to rate the helpfulness of each and every answer. Maybe Google needs to seriously consider collecting individualized feedback on their customer service representatives. At 1,300 resumes a day, it really shouldn&#8217;t be that hard to find people who actually understand what the customers are asking.</p>
]]></content:encoded>
			<wfw:commentRss>http://smackdown.blogsblogsblogs.com/2008/08/01/google-lowers-the-bar-on-customer-service-yet-again/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
	</channel>
</rss>

