<?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: TypePad Vs del.icio.us</title>
	<atom:link href="http://mobhappy.com/blog1/2005/12/20/typepad-vs-delicious/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobhappy.com/blog1/2005/12/20/typepad-vs-delicious/</link>
	<description>Russell Buckley and Carlo Longino on mobile technology.</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Russell Buckley</title>
		<link>http://mobhappy.com/blog1/2005/12/20/typepad-vs-delicious/comment-page-1/#comment-20</link>
		<dc:creator>Russell Buckley</dc:creator>
		<pubDate>Tue, 20 Dec 2005 20:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://p6.hostingprod.com/@mobhappy.com/blog1/?p=31#comment-20</guid>
		<description>Michael

Thanks for the comment.

As I said above, more information is certainly key.

But surely you should be proactive when you have a serious outrage? By that I mean it shouldn&#039;t be up to me to find out if there&#039;s an outrage, you should be telling *me*. An email alert system would seem the logical solution - albeit one people could opt out of. 

Russell
</description>
		<content:encoded><![CDATA[<p>Michael</p>
<p>Thanks for the comment.</p>
<p>As I said above, more information is certainly key.</p>
<p>But surely you should be proactive when you have a serious outrage? By that I mean it shouldn&#8217;t be up to me to find out if there&#8217;s an outrage, you should be telling *me*. An email alert system would seem the logical solution &#8211; albeit one people could opt out of. </p>
<p>Russell</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sippey</title>
		<link>http://mobhappy.com/blog1/2005/12/20/typepad-vs-delicious/comment-page-1/#comment-19</link>
		<dc:creator>Michael Sippey</dc:creator>
		<pubDate>Tue, 20 Dec 2005 19:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://p6.hostingprod.com/@mobhappy.com/blog1/?p=31#comment-19</guid>
		<description>Hi, Russell.  Thanks very much for your feedback.  First, let me say that we&#039;re very very sorry about Friday&#039;s outage, and apologize for the inconvenience it caused.  We know that we have to earn our customers&#039; trust, and are working hard to do that every day.

We also know we have some work to do to improve customer communication in times of crisis.  When we&#039;re faced with situations like Friday, we do our best to balance accuracy against speed, and make sure that we&#039;re able to communicate clearly to customers just what&#039;s happening, and to set expectations appropriately about the state of the service and their blogs.

As Mena posted last night &lt;a href=&quot;http://www.sixapart.com/about/corner/2005/12/outage_update_a.html&quot; rel=&quot;nofollow&quot;&gt;on her blog&lt;/a&gt;, we&#039;ve heard from our customers that we need make our communications channels simpler and easier to find.  During Friday&#039;s outage we pointed the error page that user&#039;s received when they tried to log into the application to &lt;a href=&quot;http://status.sixapart.com/&quot; rel=&quot;nofollow&quot;&gt;status.sixapart.com&lt;/a&gt;, and also used &lt;a href=&quot;http://www.sixapart.com/typepad/news/&quot; rel=&quot;nofollow&quot;&gt;Everything TypePad&lt;/a&gt; to post updates throughout the day about the status of the outage.  Yesterday afternoon we posted a &lt;a href=&quot;http://www.sixapart.com/typepad/news/2005/12/recap_of_friday_1.html&quot; rel=&quot;nofollow&quot;&gt;more detailed recap&lt;/a&gt; of what happened, and we&#039;ll be posting more information this week about how we plan to compensate customers for the outage.

Yet even with all this posting activity, we recognize that we need to do a better job of making that information easier to find.  We are evaluating the best way to do that, and I sincerely appreciate hearing ideas about how we can make it better!</description>
		<content:encoded><![CDATA[<p>Hi, Russell.  Thanks very much for your feedback.  First, let me say that we&#8217;re very very sorry about Friday&#8217;s outage, and apologize for the inconvenience it caused.  We know that we have to earn our customers&#8217; trust, and are working hard to do that every day.</p>
<p>We also know we have some work to do to improve customer communication in times of crisis.  When we&#8217;re faced with situations like Friday, we do our best to balance accuracy against speed, and make sure that we&#8217;re able to communicate clearly to customers just what&#8217;s happening, and to set expectations appropriately about the state of the service and their blogs.</p>
<p>As Mena posted last night <a href="http://www.sixapart.com/about/corner/2005/12/outage_update_a.html" rel="nofollow">on her blog</a>, we&#8217;ve heard from our customers that we need make our communications channels simpler and easier to find.  During Friday&#8217;s outage we pointed the error page that user&#8217;s received when they tried to log into the application to <a href="http://status.sixapart.com/" rel="nofollow">status.sixapart.com</a>, and also used <a href="http://www.sixapart.com/typepad/news/" rel="nofollow">Everything TypePad</a> to post updates throughout the day about the status of the outage.  Yesterday afternoon we posted a <a href="http://www.sixapart.com/typepad/news/2005/12/recap_of_friday_1.html" rel="nofollow">more detailed recap</a> of what happened, and we&#8217;ll be posting more information this week about how we plan to compensate customers for the outage.</p>
<p>Yet even with all this posting activity, we recognize that we need to do a better job of making that information easier to find.  We are evaluating the best way to do that, and I sincerely appreciate hearing ideas about how we can make it better!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

