<?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: New Jungle Disk Support System</title>
	<atom:link href="http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/</link>
	<description>Reliable online storage powered by Rackspace and Amazon S3</description>
	<lastBuildDate>Tue, 31 Jan 2012 06:04:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nieri</title>
		<link>http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/comment-page-1/#comment-1663</link>
		<dc:creator>Nieri</dc:creator>
		<pubDate>Mon, 26 Jan 2009 05:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/#comment-1663</guid>
		<description>Having been on the other side with a company that went from tickets to trying to use the forum, I mostly agree with Jason Litka. Unless you have something very innovative, you are going to bottle up a lot of valuable issue history and steps that would otherwise be available to everyone through google / your search. KBs in my experience seem great in theory but in practice are not nearly as valuable as forums because they depend so much on active work on your part to make them worth looking at for customers.

Hopefully you have a plan to keep all the issue history, current hot issues, and intermediate steps available to your general user public?

I love jungledisk by the way and have been encouraging so many people to use it as well as being a user myself. Downloading the new version now....</description>
		<content:encoded><![CDATA[<p>Having been on the other side with a company that went from tickets to trying to use the forum, I mostly agree with Jason Litka. Unless you have something very innovative, you are going to bottle up a lot of valuable issue history and steps that would otherwise be available to everyone through google / your search. KBs in my experience seem great in theory but in practice are not nearly as valuable as forums because they depend so much on active work on your part to make them worth looking at for customers.</p>
<p>Hopefully you have a plan to keep all the issue history, current hot issues, and intermediate steps available to your general user public?</p>
<p>I love jungledisk by the way and have been encouraging so many people to use it as well as being a user myself. Downloading the new version now&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Litka</title>
		<link>http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/comment-page-1/#comment-1647</link>
		<dc:creator>Jason Litka</dc:creator>
		<pubDate>Thu, 22 Jan 2009 16:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/#comment-1647</guid>
		<description>Sorry, but I think this is a horrible idea.  It&#039;s one thing to offer paying clients the option of communicating directly to the developers with a support ticket system, but cutting off public support means that prospective customers can&#039;t get any info on the number of issues with the app and that existing customers can&#039;t learn from the issues already found by others.

I&#039;m a desktop customer at the moment but was planning on signing up for a dozen or so Workgroup accounts now that 2.5 is final.  This change just cost you that business.</description>
		<content:encoded><![CDATA[<p>Sorry, but I think this is a horrible idea.  It&#8217;s one thing to offer paying clients the option of communicating directly to the developers with a support ticket system, but cutting off public support means that prospective customers can&#8217;t get any info on the number of issues with the app and that existing customers can&#8217;t learn from the issues already found by others.</p>
<p>I&#8217;m a desktop customer at the moment but was planning on signing up for a dozen or so Workgroup accounts now that 2.5 is final.  This change just cost you that business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lois Jones</title>
		<link>http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/comment-page-1/#comment-1639</link>
		<dc:creator>Lois Jones</dc:creator>
		<pubDate>Thu, 22 Jan 2009 01:07:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jungledisk.com/2009/01/21/new-jungle-disk-support-system/#comment-1639</guid>
		<description>Tried to install update 2.50b over 2.50a.  Error &quot; cannot install service...cancel/retry&quot;  Retry did not work.  Could not reactivate service (&quot;marked for deletion&quot;).  Had to reboot and reinstall version 2.50a and reboot again.  2.50a is now working again.  Do I need version 2.50b, and if so, how do I get it to work?  System is SBS 2003, service pack 2.</description>
		<content:encoded><![CDATA[<p>Tried to install update 2.50b over 2.50a.  Error &#8221; cannot install service&#8230;cancel/retry&#8221;  Retry did not work.  Could not reactivate service (&#8220;marked for deletion&#8221;).  Had to reboot and reinstall version 2.50a and reboot again.  2.50a is now working again.  Do I need version 2.50b, and if so, how do I get it to work?  System is SBS 2003, service pack 2.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

