-
Website
http://www.louisgray.com/live/ -
Original page
http://blog.louisgray.com/2008/06/disqus-downtime-reminds-us-of-woes-for.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
charlieanzman
61 comments · 11 points
-
Jesse Stay
221 comments · 71 points
-
Ari Herzog
43 comments · 23 points
-
ChangeForge | Ken Stewart
135 comments · 18 points
-
drewolanoff
64 comments · 54 points
-
-
Popular Threads
-
For All the Gloom Around RSS, Readers Continue to Climb in '09
20 hours ago · 19 comments
-
Growing Grumblings on Tech News Don't Answer Incentives Problems
4 days ago · 33 comments
-
iTunes, Sirius Seem Antiquated After Spotify iPhone Trial
5 days ago · 15 comments
-
FTC Disclosures Made Simple For Bloggers With Conflicts
2 weeks ago · 57 comments
-
My iPhone Data Consumption Workflow
4 days ago · 6 comments
-
For All the Gloom Around RSS, Readers Continue to Climb in '09
We'll update the blog with more information. Sorry about there being no updates for the first 30 minutes. I was asleep.
Outages aside (we all have them), I think you guys are doing great. Great product, great users... I am really excited to witness the evolution of this product!
I don't like forming responses as if coming from PR. But yes, I do appreciate the report and we have looked into it. No issues found yet but I'll update once I find out more.
p.s. I am getting notified of all my replies. :-P
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.
Goofy.
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.
I restate my belief that an open specification for sharing comments between services and back to the blog is the only way to go. Services like Disqus will experience downtime here and there, it's only natural. But the notion that, for example, FriendFeed working with Disqus will solve everyone's woes and get every social media comment back to the blog that is being talked about is baffling. I hope this brief outage will at least remind folks, as far as "comment fragmentation" goes, not to put all their eggs in one basket.
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...
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.
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.
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.
If anyone is interested in participating in the discussion about this, then please check out the wiki ( http://wiki.open-comments.org ) and start discussing your ideas, concerns, and suggestions on the forum ( http://forum.open-comments.org ). 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.
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.
I look forward to using Shyftr more and the future integration to come.
keep cooking ... and don't make me choose between intense debate, disqus, etc...
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.
Not because people are all into "SDF" combo does it mean we're shunning out the other services ;)
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.
Have I mentioned yet that I think Disqus is awesome? Cuz I do... I never want to come across as feeling any other way.
The entire team is still focused on this right now. We know what went wrong and are fixing it now.
Sorry again guys, and thanks for being ridiculously understanding.
this is not a disqus or intense debate issue.
this is the world we live in and it's only going to get more so
fred