Clearly, the sheer abundance of my loyal revjim.net readers and their eagerness to test this new commenting system has overloaded the poor monkeys that power the Disqus servers as the entire site now seems to be down.
This presents the first problem with a centralized comment system. As a result of the combination of Disqus now being down and the way the Disqus plugin for my content engine (WordPress) has been written, my site, revjim.net, now also appears to the outside world to be down. I know it isn’t. I’m writing this post now using it. But it sure looks that way.
Feel free to discuss these circumstances… just as soon as Disqus comes back up (or I get tired of waiting and get rid of it).
We're back. :)
Tada!
Growing pains. Such fun.
Thanks for the notice.
Revjim, this is an issue with centralized systems…they introduce a single point of failure to your system…one you have no control over…
We at SezWho believe in distributed mashups to build robust best of the breed systems…Take a look and let me know what you think?
Thanks, Jitendra
Again, Thank you.
I understand this is an issue with centralized services. And I
understand that, for some applications, offloading anything to any
system that wasn't up ALL the time could be a bad idea. But that isn't
the case with me. I use Flickr, Twitter, Tumblr, LiveJournal, Askimet,
and many other hosted services. Adding comments into that mix doesn't
make too much of a difference to me.
hmmmm….. lots of bloggers reporting on this issue with disqus… growing pains.
Yeah. They took a little dive the other morning. Only being a user for a
few days, I don't know if this is a common occurrence or a rare case. I
guess we'll find out.
Just the once. Hadn't happened before, and shouldn't happen again. We know what we messed up on.
It shouldn't have ever happened and for that I apologize.
I understand fully. Everyone has growing pains. You guys were quick to
fix the problem, and also quite honest about what happened. If there's
going to be a problem, that's the best possibly way to see a resolution.
In my book, this isn't a problem unless it keeps happening. And it
hasn't. That's the kind of support I like to see. Let me know if you're
hiring. :)
Again, Thank you.
I understand this is an issue with centralized services. And I
understand that, for some applications, offloading anything to any
system that wasn't up ALL the time could be a bad idea. But that isn't
the case with me. I use Flickr, Twitter, Tumblr, LiveJournal, Askimet,
and many other hosted services. Adding comments into that mix doesn't
make too much of a difference to me.
Yeah. They took a little dive the other morning. Only being a user for a
few days, I don't know if this is a common occurrence or a rare case. I
guess we'll find out.
Just the once. Hadn't happened before, and shouldn't happen again. We know what we messed up on.
It shouldn't have ever happened and for that I apologize.
I understand fully. Everyone has growing pains. You guys were quick to
fix the problem, and also quite honest about what happened. If there's
going to be a problem, that's the best possibly way to see a resolution.
In my book, this isn't a problem unless it keeps happening. And it
hasn't. That's the kind of support I like to see. Let me know if you're
hiring. :)