<?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: Partial TweetLater Outage Due To Twitter Denial Of Service Attack</title>
	<atom:link href="http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/</link>
	<description></description>
	<lastBuildDate>Mon, 09 Aug 2010 00:41:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Nathaniel Johnson</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-456</link>
		<dc:creator>Nathaniel Johnson</dc:creator>
		<pubDate>Sun, 30 Aug 2009 18:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-456</guid>
		<description>eh I wouldn&#039;t worry about this too much, I love your service and keep up the great work! </description>
		<content:encoded><![CDATA[<p>eh I wouldn&#039;t worry about this too much, I love your service and keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jerry</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-404</link>
		<dc:creator>jerry</dc:creator>
		<pubDate>Mon, 10 Aug 2009 04:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-404</guid>
		<description>Fair enough! Thank you for responding. Your open discussion policy is a breath a fresh air! I asked a tough question, and you published it publicly with a rational response.&lt;br&gt;&lt;br&gt;We are still seeing intermittent issues with TweetLater which we fully attribute to Twitter, but at least its working again. Given the fair cost of your pricing, your open communications, constant updates, and refreshing conduct of your business, I am very much a fan of your service. &lt;br&gt;&lt;br&gt;Thank you!</description>
		<content:encoded><![CDATA[<p>Fair enough! Thank you for responding. Your open discussion policy is a breath a fresh air! I asked a tough question, and you published it publicly with a rational response.</p>
<p>We are still seeing intermittent issues with TweetLater which we fully attribute to Twitter, but at least its working again. Given the fair cost of your pricing, your open communications, constant updates, and refreshing conduct of your business, I am very much a fan of your service. </p>
<p>Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: webgoddess</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-403</link>
		<dc:creator>webgoddess</dc:creator>
		<pubDate>Sun, 09 Aug 2009 19:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-403</guid>
		<description>I wouldn&#039;t be too sure about that.  YouTube has been going downhill fast and nobody has been able to come out with something better to replace them.</description>
		<content:encoded><![CDATA[<p>I wouldn&#39;t be too sure about that.  YouTube has been going downhill fast and nobody has been able to come out with something better to replace them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dewald Pretorius</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-402</link>
		<dc:creator>Dewald Pretorius</dc:creator>
		<pubDate>Sun, 09 Aug 2009 19:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-402</guid>
		<description>We gladly provide credits when we messed up. However, we will not be able to run a business if we had to provide credits every time that Twitter has an outage. Twitter is definitely not going to reimburse us for losses during an outage, which is not under our control or even within our sphere of influence.</description>
		<content:encoded><![CDATA[<p>We gladly provide credits when we messed up. However, we will not be able to run a business if we had to provide credits every time that Twitter has an outage. Twitter is definitely not going to reimburse us for losses during an outage, which is not under our control or even within our sphere of influence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: glider_rider65</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-399</link>
		<dc:creator>glider_rider65</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-399</guid>
		<description>Yes, unexpected benefits like realizing I hadn&#039;t picked the vegetable garden in several days... Keep up the great work sir.... Appreciate all you do.</description>
		<content:encoded><![CDATA[<p>Yes, unexpected benefits like realizing I hadn&#39;t picked the vegetable garden in several days&#8230; Keep up the great work sir&#8230;. Appreciate all you do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-401</link>
		<dc:creator>Jerry</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-401</guid>
		<description>Your situation is a difficult one. As you fully understand it is also difficult for us. When the service is returned do you have any plan to provide some discount for loss of service? I am not meaning this in any antagonistic way. I just think that its good business sense to offer some sort of relief. If Twitter was completely broken, then I would not ask. But currently we have shifted to posting manually and its working fine. I know that your App can&#039;t connect, but now I am incurring cost to handle this manually, and I am still paying you for a service your unable to provide (regardless of the reason). The price you charge is very small so this is not really an question of price, rather of principle. And again this is more a theoretical question based on an open discussion policy you promote. If you said NO I would not have a problem with that answer at all. &lt;br&gt;&lt;br&gt;Please advise.&lt;br&gt;&lt;br&gt;Thank you</description>
		<content:encoded><![CDATA[<p>Your situation is a difficult one. As you fully understand it is also difficult for us. When the service is returned do you have any plan to provide some discount for loss of service? I am not meaning this in any antagonistic way. I just think that its good business sense to offer some sort of relief. If Twitter was completely broken, then I would not ask. But currently we have shifted to posting manually and its working fine. I know that your App can&#39;t connect, but now I am incurring cost to handle this manually, and I am still paying you for a service your unable to provide (regardless of the reason). The price you charge is very small so this is not really an question of price, rather of principle. And again this is more a theoretical question based on an open discussion policy you promote. If you said NO I would not have a problem with that answer at all. </p>
<p>Please advise.</p>
<p>Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drd4U</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-398</link>
		<dc:creator>drd4U</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-398</guid>
		<description>Yessss...so true...but I really didn&#039;t want to discover the lawn mower...sigh...,,,</description>
		<content:encoded><![CDATA[<p>Yessss&#8230;so true&#8230;but I really didn&#39;t want to discover the lawn mower&#8230;sigh&#8230;,,,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drd4U</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-400</link>
		<dc:creator>drd4U</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-400</guid>
		<description>Appreciate the update 1:54 PM...thanks...They reallyl ought to be providing some ETR?</description>
		<content:encoded><![CDATA[<p>Appreciate the update 1:54 PM&#8230;thanks&#8230;They reallyl ought to be providing some ETR?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dewald Pretorius</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-397</link>
		<dc:creator>Dewald Pretorius</dc:creator>
		<pubDate>Sun, 09 Aug 2009 17:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-397</guid>
		<description>This Twitter outage has had unexpected benefits.&lt;br&gt;&lt;br&gt;I had time to mow the lawn, and I discovered my car, which I thought was stolen.</description>
		<content:encoded><![CDATA[<p>This Twitter outage has had unexpected benefits.</p>
<p>I had time to mow the lawn, and I discovered my car, which I thought was stolen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dewald Pretorius</title>
		<link>http://www.socialoomphblog.com/partial-tweetlater-outage-due-to-twitter-denial-of-service-attack/#comment-396</link>
		<dc:creator>Dewald Pretorius</dc:creator>
		<pubDate>Sun, 09 Aug 2009 17:30:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=357#comment-396</guid>
		<description>You need to look at the &quot;from&quot; source of the tweets in the Twitter web interface. Chris is making all his updates manually from Twitter desktop or phone clients.</description>
		<content:encoded><![CDATA[<p>You need to look at the &#8220;from&#8221; source of the tweets in the Twitter web interface. Chris is making all his updates manually from Twitter desktop or phone clients.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
