<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>louisgray.com - Latest Comments in louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://louisgray.disqus.com/</link><description>A Silicon Valley Blog for Early Adopters and Tech Geeks</description><atom:link href="https://louisgray.disqus.com/louisgraycom_disqus_downtime_reminds_us_of_woes_for_data_in_the_cloud/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 16 Jan 2010 09:58:03 -0000</lastBuildDate><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-30041273</link><description>&lt;p&gt;Given that you are still using Disqus, does that mean the pain outweighs the benefit (I'm considering putting Disqus on my own site).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">krypted</dc:creator><pubDate>Sat, 16 Jan 2010 09:58:03 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-20660366</link><description>&lt;p&gt;I am happy to say that since this issue occurred, nothing as catastrophic has occurred again.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sagar</dc:creator><pubDate>Tue, 20 Oct 2009 19:37:13 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-6130926</link><description>&lt;p&gt;I am new to disqus, is there a way to periodically backup the comments to your hardisk?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">glasswool</dc:creator><pubDate>Mon, 09 Feb 2009 23:04:52 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-5539301</link><description>&lt;p&gt;Apparently, comments are back. Hopefully an official update from Disqus is forthcoming!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">SEO Updates</dc:creator><pubDate>Sun, 25 Jan 2009 19:08:49 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-2646112</link><description>&lt;p&gt;I agree with you!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul</dc:creator><pubDate>Fri, 26 Sep 2008 15:31:46 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-616514</link><description>&lt;p&gt;This is not a "Disqus" problem, per se. Disqus is a great product with good leadership. Data is moving to the cloud. But when the cloud fails us, short term or long term, it makes me think about how we can protect our data. I regularly back up my FTP sites locally to be sure I can move from host to host, and I don't think it'd be a bad idea to see if DIsqus' data could be similarly saved. Why not have something like a hybrid two-way post, one to the blogger's local/FTP share and one to the central Disqus host? Just thinking...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Louis Gray</dc:creator><pubDate>Sun, 08 Jun 2008 02:09:03 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-616511</link><description>&lt;p&gt;I don't personally worry much about data in the cloud. For the most part, I trust my data to be in the hands of a 3rd party than on my laptop. But where there are options to have multiple copies, locally or on the Web, that is advantageous. Disqus' downtime was a surprise for me, due to them being so solid from day one, and it made me think about how some do have concerns there.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Louis Gray</dc:creator><pubDate>Sun, 08 Jun 2008 02:05:44 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-616027</link><description>&lt;p&gt;It's a bit funny to read this post in light of the Amazon outage on the same day. .. if anything reminds us of "woes for data in the cloud", it has to be Amazon...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Zoli Erdos</dc:creator><pubDate>Sat, 07 Jun 2008 21:54:08 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-615979</link><description>&lt;p&gt;Ah memes. I love 'em. I must admit though that the meme of the day, worries over data stored in the cloud, is getting on my nerves. The cloud has always been here. All these services that people are referring to as the cloud are only one small part of the cloud. The cloud is built into the design of the web. Almost all websites are hosted by one company or another. By using services like Disqus we are merely storing different parts in different places. This is not a new idea. This is not a bad idea.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">w.d.watson aka megalar</dc:creator><pubDate>Sat, 07 Jun 2008 21:36:27 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-615945</link><description>&lt;p&gt;i think it's worth pointing out that if you blog at &lt;a href="http://wordpress.org" rel="nofollow noopener" target="_blank" title="wordpress.org"&gt;wordpress.org&lt;/a&gt;, typepad, blogger, or tumblr, not only your comments but your posts as well are in "the cloud"&lt;/p&gt;&lt;p&gt;this is not a disqus or intense debate issue.&lt;/p&gt;&lt;p&gt;this is the world we live in and it's only going to get more so&lt;/p&gt;&lt;p&gt;fred&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Sat, 07 Jun 2008 21:24:08 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-615887</link><description>&lt;p&gt;There should, no, there must be an open specification for sharing comments and keeping comments attached/showing on the original post.&lt;/p&gt;&lt;p&gt;But it must start somewhere right?  SezWho+DISQUS+FriendFeed maybe?  If it works, then on to the next phase, getting everybody else to the interconnection party.&lt;/p&gt;&lt;p&gt;Not because people are all into "SDF" combo does it mean we're shunning out the other services ;)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yohan Yukiya 사요한 謝雪矢</dc:creator><pubDate>Sat, 07 Jun 2008 21:04:29 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-615878</link><description>&lt;p&gt;Yep, noticed that myself, but nah it is fine hehe.  I'd start packing up my comments if they don't experience spikes, downtimes, and problems.  Too perfect to be true.  :p  And besides the point, it means no one is using it :p&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yohan Yukiya 사요한 謝雪矢</dc:creator><pubDate>Sat, 07 Jun 2008 21:00:12 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-614812</link><description>&lt;p&gt;one thing is for sure, after using discuss, as a commenting person, any blog with blogger, or even simply with a linear comment thread, feels crippling&lt;/p&gt;&lt;p&gt;keep cooking   ...  and don't make me choose between intense debate, disqus, etc... &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gregory</dc:creator><pubDate>Sat, 07 Jun 2008 15:13:01 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-610035</link><description>&lt;p&gt;We updated our blog with &lt;a href="http://blog.disqus.net/2008/06/06/issues-this-morning-what-why-and-what-now/" rel="nofollow noopener" target="_blank" title="http://blog.disqus.net/2008/06/06/issues-this-morning-what-why-and-what-now/"&gt;more information&lt;/a&gt; on this morning's issues.&lt;/p&gt;&lt;p&gt;The entire team is still focused on this right now. We know what went wrong and are fixing it now.&lt;/p&gt;&lt;p&gt;Sorry again guys, and thanks for being ridiculously understanding.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">obscurelyfamous</dc:creator><pubDate>Fri, 06 Jun 2008 16:38:39 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-609972</link><description>&lt;p&gt;I can understand that; I don't want it to seem like I'm criticizing you for taking that stance.&lt;/p&gt;&lt;p&gt;I look forward to using Shyftr more and the future integration to come.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shey</dc:creator><pubDate>Fri, 06 Jun 2008 16:29:21 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-609883</link><description>&lt;p&gt;For us to team up with Disqus/ID would only pressure more bloggers who might not want to install Disqus/ID.  We are not interested in creating an atmosphere of pressure on the bloggers. Many bloggers have seen the benefit of installing one of these awesome services, and many more are sure to come... but not everyone will take part when all is said and done. In fact, some of the biggest blogs out there would not come close to either of these services, they simply have too much to lose and would never loose the reigns on that aspect of their blog. Where does that leave the comments for those blogs?&lt;/p&gt;&lt;p&gt;I am a big fan of Disqus, and I think ID has some compelling offerings in their effort as well... both services are competing in a really cool and exciting space.  But I do not see one-on-one "team ups" as being the solution for the users. I would rather not endorse any one service professionally, but rather encourage all services to work together to bring a universal solution to the table quickly. Partnerships today will lead to an open initiative being stifled tomorrow.  So while the notion that "something is better than nothing" is easy to say, it's a harder to live down once a limited process is entrenched.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Shaulis</dc:creator><pubDate>Fri, 06 Jun 2008 16:16:54 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-609481</link><description>&lt;p&gt;You're right, having a common standard only makes sense.  But until then, I think teaming up now with a Disqus or IntenseDebate is better than the status quo.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shey</dc:creator><pubDate>Fri, 06 Jun 2008 15:33:50 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-609409</link><description>&lt;p&gt;Louis and Daniel:&lt;/p&gt;&lt;p&gt;This sounds a lot like what happened to me a week or so ago. From all of my points of view, Disqus was completely down and the rest of the net was fine. No one else noticed this and no record of it was recorded, other than a couple of tweets about it.&lt;/p&gt;&lt;p&gt;Goofy.&lt;/p&gt;&lt;p&gt;As an aside, uptime issues don't outweigh all of the benefits I personally get from Disqus.  It's a great service and removes a ton of the comment issues I've had in the past.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">lilbyrdie</dc:creator><pubDate>Fri, 06 Jun 2008 15:25:02 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-608449</link><description>&lt;p&gt;Well, I'm talking about invoicing 2.0, hosted business apps, real bottom line stuff. It's just a matter of time till some bad thing happens that wipes a few businesses out. The sector of SAAS wont collapse, but such failures could give rise to a shake out, and perhaps, standards for reliability or third party certification.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">awilensky</dc:creator><pubDate>Fri, 06 Jun 2008 13:40:10 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-608420</link><description>&lt;p&gt;Then again... "mission critical" is a realtive term.&lt;/p&gt;&lt;p&gt;There are plenty of people to whom "Comments" are critical... and I'm sure Daniel can attest to the fact that these hiccups are not exactly "tolerated", in the traditional sense of the word. Just a hunch.&lt;/p&gt;&lt;p&gt;Have I mentioned yet that I think Disqus is awesome? Cuz I do... I never want to come across as feeling any other way.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Shaulis</dc:creator><pubDate>Fri, 06 Jun 2008 13:36:41 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-608341</link><description>&lt;p&gt;Me? I picked on Daniel? hehehe... let's not forget what blog post these comments live under and all the great things i said in my comment.  ;)  lol.  I was just teasing him, ribbing him a little... nothing like getting blasted in the face first thing on a Friday morning. I know that feeling too well. :)&lt;/p&gt;&lt;p&gt;p.s.  I am getting notified of all my replies.  :-P&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Shaulis</dc:creator><pubDate>Fri, 06 Jun 2008 13:28:00 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-608336</link><description>&lt;p&gt;Shey, we want to let comments travel back to blogs and other services like FriendFeed. Although, I can't say when this will happen. It's not an issue of whether or not we support the portability of comments. We support data portability, especially letting comments get pulled back to the blog. That being said, it's unfair to assume that the solution is about finding a platform to support. If we said today that we supported Disqus, that only means it's beneficial for a finite number of people that use Disqus. Everyone that uses Intense Debate, Wordpress Sezwho, and any other competing platform that pops up in the future would be left out in the cold. The answer to data portability of discussions should not be about supporting and integrating with 3rd party solutions. It should be about creating an open standard where everyone that has a vested interest can take advantage. A standard that everyone can use. A standard that doesn't require web services to tackle APIs from multiple platforms. A standard that doesn't require bloggers to rely on 3rd party solutions if they don't want to. Everyone that wants should have a right to participate in the data portability of comments. If we have an open standard in place, everyone will be able to support this standard without feeling tied into a specific solution. Discussion's are and will continue to be woven into the fabric of social media. Establishing an open standard for handling, sharing, and passing off these discussions to others is a no brainer in my mind.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Stanley</dc:creator><pubDate>Fri, 06 Jun 2008 13:27:43 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-608309</link><description>&lt;p&gt;This is the kind of question I like to hear!  :)  We are working on getting a workgroup going with the goals of coming to terms on an open specification for "passing" comments around the social landscape (per the behest of the user, of course).&lt;/p&gt;&lt;p&gt;We would like to enable our users to send their Shyftr comments to FriendFeed or any other life-streaming service, the blog where the article being commented on originated, twitter or any other micro-blogging service, etc...&lt;/p&gt;&lt;p&gt;We started these efforts very recently and are rather eager to start getting some participation from other service providers who believe in the benefit of having an industry standard identification scheme for giving and receiving user comments. We have already got some participation and we, as an open workgroup, are eager for more! The more diverse representation the workgroup has the more thorough the solution will be, plain and simple.&lt;/p&gt;&lt;p&gt;I do encourage participation from every angle... I think, together, we can all come to terms on a solution that works and benefits everyone.  It is important to me that the methods become open for use by everyone to encourage the fastest and widest possible adoption.&lt;/p&gt;&lt;p&gt;I would rather put my efforts toward this concept than developing a proprietary API to shoot comments back to blogs and integrate with FriendFeed, Twitter, and other vastly different APIs on a one by one basis. Such a system would be under the constant threat of changes in blog software and service providers' alterations to their own public APIs.  A standard would alleviate this threat by establishing a unwavering modus operandi for all of us to follow, giving the users the most flexibility in deciding where they want their comments to go.&lt;/p&gt;&lt;p&gt;If anyone is interested in participating in the discussion about this, then please check out the wiki ( &lt;a href="http://wiki.open-comments.org" rel="nofollow noopener" target="_blank" title="http://wiki.open-comments.org"&gt;http://wiki.open-comments.org&lt;/a&gt; ) and start discussing your ideas, concerns, and suggestions on the forum ( &lt;a href="http://forum.open-comments.org" rel="nofollow noopener" target="_blank" title="http://forum.open-comments.org"&gt;http://forum.open-comments.org&lt;/a&gt; ). Again, this is a new workgroup and at the moment we are interested in getting participation form a diverse group of people to ensure than any agreed upon specification will benefit everyone and not favor a particular service or group of services.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Shaulis</dc:creator><pubDate>Fri, 06 Jun 2008 13:25:32 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-608099</link><description>&lt;p&gt;We are only one or two major outages away from a user revolt when a major SAAS platform or data center comes tumbling down. Comments are one thing, but the new guard of mission critical platforms for business applications that are cloud hosted will not tolerate these disruptions. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">awilensky</dc:creator><pubDate>Fri, 06 Jun 2008 13:05:10 -0000</pubDate></item><item><title>Re: louisgray.com: Disqus' Downtime Reminds Us of Woes for Data In the Cloud</title><link>http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html#comment-607340</link><description>&lt;p&gt;How soon can we expect Shyftr comments to integrate with blogs and FriendFeed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shey</dc:creator><pubDate>Fri, 06 Jun 2008 11:43:21 -0000</pubDate></item></channel></rss>