<?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: Issue with the DiggClick Plugin.</title>
	<atom:link href="http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/</link>
	<description>Meanderings of a coder</description>
	<pubDate>Sun, 20 May 2012 05:32:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Leafyhost (aka Aetheri Hosting) Update.-- Digital Meanderings</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-516</link>
		<dc:creator>Leafyhost (aka Aetheri Hosting) Update.-- Digital Meanderings</dc:creator>
		<pubDate>Mon, 07 May 2007 05:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-516</guid>
		<description>[...] It seems that Leafyhost is still proving to be a bad hosting choice. I just received and email from Jon H, a current Leafyhost subscriber. It turns out that they are still up to their old tricks. Below you will find the contents of his email. I&#8217;ve also added this email as a comment to the original post. [...]</description>
		<content:encoded><![CDATA[<p>[...] It seems that Leafyhost is still proving to be a bad hosting choice. I just received and email from Jon H, a current Leafyhost subscriber. It turns out that they are still up to their old tricks. Below you will find the contents of his email. I&#8217;ve also added this email as a comment to the original post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zechariahs</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-515</link>
		<dc:creator>zechariahs</dc:creator>
		<pubDate>Mon, 07 May 2007 04:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-515</guid>
		<description>This comment was provided by John H. and posted with his permission.

"I have been a customer with LeafyHost since June of 2004 (back when they were Aetheri) and at this point I'm very fed up with them. I had great patience with them when they had their hard drive failure last year because they had been a very good host for my site. I use my domain largely for e-mail and hosting images, so downtime wasn't really an issue for me. Also, Christopher and I had been posting on the same forum (not Ars) for something like six years and he hooked me up with a free hosting package after my prior host ( vectorstar.net) had massive downtime issues because they refused to replace a failing network card (absurd, I know). They had been prompt in handling what few support issues I brought to their attention and all was well. Things have changed for the worse since the drive failure. At this point LeafyHost is on yet another server because "our current colocation provider has been having problems with their upstream bandwidth providers, and combined with the issues with securing more power in the past that they've had, they are moving out of the data center where we are currently located." This was handled with few hiccups with the exception of my site being a 404 even after all the dust had settled, but as far as I can tell that wasn't their fault. The issue had resolved itself by the time I fired off an e-mail to them.

The problem I have with them at this point is that I have two support tickets that have been open for several months. No updated information for the tickets has been supplied in about as long as the tickets have been open. The first ticket is a real minor issue that I just brought to their attention since it was affecting all users (DSPAM died). I was told on 2/22/07 that "It looks like we have a fix, but we need to test it out through our dev server first. Once that looks to be stable, I'll move it over to Uffish and update this ticket." Nothing since. It's a minor issue since Thunderbird has done a superb job of filtering out most of the junk mail I receive, but I am frustrated with the lack of *any* information since February.

The second ticket is a much more severe issue for me: I can receive mail, but am unable to send mail. The last piece of information I received on this issue was when Sam told me he was passing the issue over to Chris and that he would look into it. I haven't heard a thing from either Chris or Sam on the issue since that day. I have sent several e-mails to them over the last two months asking if any progress has been made on the issue and have not had a single reply to any of them. No "Hey, we're still looking into it," or a "We're working on fixing it now," or even a "Fuck off." Nothing. Complete and total silence. After the migration to their third server the whole ticket system is down. You go to the page and get a page saying that they need to install the Zend optimizer on the server before the page can be displayed.

This is complete and utter bullshit. A web hosting company should respond to a user's requests for information pertaining to the quality of services being provided. They should respond in a prompt manner with as much information as is available at the time. Before the site went down with the migration a few other users had been complaining in the LeafyHost forum about the lack of communication from Chris and Sam, or if they got a reply it was slow in coming. At this point I have to wonder if Chris and Sam even care about their hosting service at all. Have they decided that since things appear to be spiraling down the toilet they might as well piss off their customers? Have they decided that no news is good news? Are they playing NetHack all day?

These guys need to start taking their business much more seriously if they hope to make it through 2007."</description>
		<content:encoded><![CDATA[<p>This comment was provided by John H. and posted with his permission.</p>
<p>&#8220;I have been a customer with LeafyHost since June of 2004 (back when they were Aetheri) and at this point I&#8217;m very fed up with them. I had great patience with them when they had their hard drive failure last year because they had been a very good host for my site. I use my domain largely for e-mail and hosting images, so downtime wasn&#8217;t really an issue for me. Also, Christopher and I had been posting on the same forum (not Ars) for something like six years and he hooked me up with a free hosting package after my prior host ( vectorstar.net) had massive downtime issues because they refused to replace a failing network card (absurd, I know). They had been prompt in handling what few support issues I brought to their attention and all was well. Things have changed for the worse since the drive failure. At this point LeafyHost is on yet another server because &#8220;our current colocation provider has been having problems with their upstream bandwidth providers, and combined with the issues with securing more power in the past that they&#8217;ve had, they are moving out of the data center where we are currently located.&#8221; This was handled with few hiccups with the exception of my site being a 404 even after all the dust had settled, but as far as I can tell that wasn&#8217;t their fault. The issue had resolved itself by the time I fired off an e-mail to them.</p>
<p>The problem I have with them at this point is that I have two support tickets that have been open for several months. No updated information for the tickets has been supplied in about as long as the tickets have been open. The first ticket is a real minor issue that I just brought to their attention since it was affecting all users (DSPAM died). I was told on 2/22/07 that &#8220;It looks like we have a fix, but we need to test it out through our dev server first. Once that looks to be stable, I&#8217;ll move it over to Uffish and update this ticket.&#8221; Nothing since. It&#8217;s a minor issue since Thunderbird has done a superb job of filtering out most of the junk mail I receive, but I am frustrated with the lack of *any* information since February.</p>
<p>The second ticket is a much more severe issue for me: I can receive mail, but am unable to send mail. The last piece of information I received on this issue was when Sam told me he was passing the issue over to Chris and that he would look into it. I haven&#8217;t heard a thing from either Chris or Sam on the issue since that day. I have sent several e-mails to them over the last two months asking if any progress has been made on the issue and have not had a single reply to any of them. No &#8220;Hey, we&#8217;re still looking into it,&#8221; or a &#8220;We&#8217;re working on fixing it now,&#8221; or even a &#8220;Fuck off.&#8221; Nothing. Complete and total silence. After the migration to their third server the whole ticket system is down. You go to the page and get a page saying that they need to install the Zend optimizer on the server before the page can be displayed.</p>
<p>This is complete and utter bullshit. A web hosting company should respond to a user&#8217;s requests for information pertaining to the quality of services being provided. They should respond in a prompt manner with as much information as is available at the time. Before the site went down with the migration a few other users had been complaining in the LeafyHost forum about the lack of communication from Chris and Sam, or if they got a reply it was slow in coming. At this point I have to wonder if Chris and Sam even care about their hosting service at all. Have they decided that since things appear to be spiraling down the toilet they might as well piss off their customers? Have they decided that no news is good news? Are they playing NetHack all day?</p>
<p>These guys need to start taking their business much more seriously if they hope to make it through 2007.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-248</link>
		<dc:creator>Zack</dc:creator>
		<pubDate>Sun, 04 Feb 2007 18:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-248</guid>
		<description>Katie -

I am not instantly discrediting them.  This post was made after months of false promises.  If they would've admitted that they messed up and then fixed the issues, things would have turned out differently.  

Unfortunately they chose to handle the situation by pretending to fix the problems, then running away for a few days.  Some time later they would come back and the whole process would start over again.

&lt;i&gt;(Note:  Sorry for the delay in getting your comment up.  I was away for a couple of days and didn't get a chance to approve it.)&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>Katie -</p>
<p>I am not instantly discrediting them.  This post was made after months of false promises.  If they would&#8217;ve admitted that they messed up and then fixed the issues, things would have turned out differently.  </p>
<p>Unfortunately they chose to handle the situation by pretending to fix the problems, then running away for a few days.  Some time later they would come back and the whole process would start over again.</p>
<p><i>(Note:  Sorry for the delay in getting your comment up.  I was away for a couple of days and didn&#8217;t get a chance to approve it.)</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-244</link>
		<dc:creator>Katie</dc:creator>
		<pubDate>Thu, 01 Feb 2007 21:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-244</guid>
		<description>Although LeafyHost has made mistakes, it seems unfair to instantly discredit them.  They did the best the could and admit that they made mistakes, which they will now never make again.
I would suggest showing support for these guys rather than trying to make worse.  They are genuine, nice, hard-working people who would never screw anyone over intentionally.  They just happened upon a series of unfortunate events.

On another note, what WOULD be a suitable backup?  I don't know anything about hosting, so I'm just curious.</description>
		<content:encoded><![CDATA[<p>Although LeafyHost has made mistakes, it seems unfair to instantly discredit them.  They did the best the could and admit that they made mistakes, which they will now never make again.<br />
I would suggest showing support for these guys rather than trying to make worse.  They are genuine, nice, hard-working people who would never screw anyone over intentionally.  They just happened upon a series of unfortunate events.</p>
<p>On another note, what WOULD be a suitable backup?  I don&#8217;t know anything about hosting, so I&#8217;m just curious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bog</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-215</link>
		<dc:creator>Bog</dc:creator>
		<pubDate>Wed, 13 Dec 2006 04:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-215</guid>
		<description>Another host to avoid is steadfast.net.  Unbelievably bad.  Good luck with the leafies...</description>
		<content:encoded><![CDATA[<p>Another host to avoid is steadfast.net.  Unbelievably bad.  Good luck with the leafies&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Switch-Case / Blog Archive / &#38;#187; LeafyHost</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-213</link>
		<dc:creator>Switch-Case / Blog Archive / &#38;#187; LeafyHost</dc:creator>
		<pubDate>Fri, 08 Dec 2006 18:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-213</guid>
		<description>[...] If you own your own business or have explored running your own business, it would do you well to read this synopsis of a business in the progress of a meltdown. LeafyHost really screwed over their customers, so read this and find out how you can better improve communication with yours. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you own your own business or have explored running your own business, it would do you well to read this synopsis of a business in the progress of a meltdown. LeafyHost really screwed over their customers, so read this and find out how you can better improve communication with yours. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tm</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-212</link>
		<dc:creator>tm</dc:creator>
		<pubDate>Thu, 07 Dec 2006 22:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-212</guid>
		<description>"Lesson learned? Keep a drive or tape in a safe."

Bzzt.  Wrong.  Please try again.</description>
		<content:encoded><![CDATA[<p>&#8220;Lesson learned? Keep a drive or tape in a safe.&#8221;</p>
<p>Bzzt.  Wrong.  Please try again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: continuum</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-211</link>
		<dc:creator>continuum</dc:creator>
		<pubDate>Thu, 07 Dec 2006 17:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-211</guid>
		<description>What hurts Aetheri/Leafyhost most is that their customers now don't believe a word they say...</description>
		<content:encoded><![CDATA[<p>What hurts Aetheri/Leafyhost most is that their customers now don&#8217;t believe a word they say&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-210</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Thu, 07 Dec 2006 13:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-210</guid>
		<description>Thanks Samuel, I do appreciate you clearing things up a bit.</description>
		<content:encoded><![CDATA[<p>Thanks Samuel, I do appreciate you clearing things up a bit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-209</link>
		<dc:creator>Zack</dc:creator>
		<pubDate>Thu, 07 Dec 2006 12:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-209</guid>
		<description>So basically there where no backups.  

Drive one.  The one that went bad.

Drive two - "Since we weren’t syncing deltas and instead were just copying the data from one drive to the others, once the IO errors started the other drive copied over its corrupted data."  Therefore this wasn't a valid backup.

Drive three - "The initial power outages knocked that out."  Therefore it too was not a valid backup.</description>
		<content:encoded><![CDATA[<p>So basically there where no backups.  </p>
<p>Drive one.  The one that went bad.</p>
<p>Drive two - &#8220;Since we weren’t syncing deltas and instead were just copying the data from one drive to the others, once the IO errors started the other drive copied over its corrupted data.&#8221;  Therefore this wasn&#8217;t a valid backup.</p>
<p>Drive three - &#8220;The initial power outages knocked that out.&#8221;  Therefore it too was not a valid backup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-208</link>
		<dc:creator>Christopher</dc:creator>
		<pubDate>Thu, 07 Dec 2006 11:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-208</guid>
		<description>"Apparently this has helped a little but not all the data has been recovered."

The truth is, 90% of our users had their data recovered immediately and suffered several days of downtime, which never, ever, should have happened.

The other 10%? That's the 10% we really screwed up with, and our initial hope was to make things as secure and stable as possible for that 90% so that the majority wouldn't suffer because of an issue with the minority. That's the largest lesson to learn, and now that we have, we're doing our best to make happy the 10% as well, and to recover as much data as possible.

"Although they advertised multiple backups it become very obvious that they were a false promise. There were no backups."

That's absolutely not true and it's unfortunate you're passing it off as a truth. We had three hard drives, one of them live, one of them mounted in the server, mirroring the first, and one of them remotely available. Since we weren't syncing deltas and instead were just copying the data from one drive to the others, once the IO errors started the other drive copied over its corrupted data. 

As for the second drive in the server? The initial power outages knocked that out, believe us, we tried to recover from backups, it just wasn't an option, and not for lack of hard drive redundancies. Lesson learned? Keep a drive or tape in a safe.</description>
		<content:encoded><![CDATA[<p>&#8220;Apparently this has helped a little but not all the data has been recovered.&#8221;</p>
<p>The truth is, 90% of our users had their data recovered immediately and suffered several days of downtime, which never, ever, should have happened.</p>
<p>The other 10%? That&#8217;s the 10% we really screwed up with, and our initial hope was to make things as secure and stable as possible for that 90% so that the majority wouldn&#8217;t suffer because of an issue with the minority. That&#8217;s the largest lesson to learn, and now that we have, we&#8217;re doing our best to make happy the 10% as well, and to recover as much data as possible.</p>
<p>&#8220;Although they advertised multiple backups it become very obvious that they were a false promise. There were no backups.&#8221;</p>
<p>That&#8217;s absolutely not true and it&#8217;s unfortunate you&#8217;re passing it off as a truth. We had three hard drives, one of them live, one of them mounted in the server, mirroring the first, and one of them remotely available. Since we weren&#8217;t syncing deltas and instead were just copying the data from one drive to the others, once the IO errors started the other drive copied over its corrupted data. </p>
<p>As for the second drive in the server? The initial power outages knocked that out, believe us, we tried to recover from backups, it just wasn&#8217;t an option, and not for lack of hard drive redundancies. Lesson learned? Keep a drive or tape in a safe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samuel Fine</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-207</link>
		<dc:creator>Samuel Fine</dc:creator>
		<pubDate>Thu, 07 Dec 2006 08:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-207</guid>
		<description>To clear up the confusion about Helpspot, cross posted from the original thread:

We had a trial license and were considering Helpspot when the server had it's explosion, so we stuck with it. A few weeks after The Event, the trial license expired. We asked for an extension, and were granted one. Recently, that license ran out, and now we are considering our options. The guy behind Helpspot has been incredibly gracious with us, we are just looking in to all possibilities right now. Helpspot is definitely still one of them.</description>
		<content:encoded><![CDATA[<p>To clear up the confusion about Helpspot, cross posted from the original thread:</p>
<p>We had a trial license and were considering Helpspot when the server had it&#8217;s explosion, so we stuck with it. A few weeks after The Event, the trial license expired. We asked for an extension, and were granted one. Recently, that license ran out, and now we are considering our options. The guy behind Helpspot has been incredibly gracious with us, we are just looking in to all possibilities right now. Helpspot is definitely still one of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-206</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Thu, 07 Dec 2006 01:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-206</guid>
		<description>BTW, just to be clear I would never name any of our customers but since they publicly announced themselves as HelpSpot users I'm not disclosing anything not already public here.</description>
		<content:encoded><![CDATA[<p>BTW, just to be clear I would never name any of our customers but since they publicly announced themselves as HelpSpot users I&#8217;m not disclosing anything not already public here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-205</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Thu, 07 Dec 2006 01:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-205</guid>
		<description>Nope Dave, no company named Aetheri has a HelpSpot license.</description>
		<content:encoded><![CDATA[<p>Nope Dave, no company named Aetheri has a HelpSpot license.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://zechariahs.org/blog/2006/11/22/issue-with-the-diggclick-plugin/comment-page-1/#comment-204</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 06 Dec 2006 23:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://schwenkconsulting.com/zechariahs/blog/?p=81#comment-204</guid>
		<description>Ian, just out of curiosity could you check Aetheri too? That was their original name.</description>
		<content:encoded><![CDATA[<p>Ian, just out of curiosity could you check Aetheri too? That was their original name.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

