I enjoy Digg. Very useful. Unfortunately, it seems that more often then not once a story link is good enough for the front page it quickly suffers from the 'Digg Effect' (similar in every respect to the famed 'Slashdot Effect'--the host cannot handle all of the requests coming in for the website, so now no one can access the site).
I propose a simple solution to this dilemma. The Coral Content Distribution Network. See the link for the particulars if you are not familiar with this technology. It's wonderfully simple to take advantage of it. You just append ".nyud.net:8090 to the hostname of any URL, and your request for that URL is handled by Coral!"
Take Groklaw at http://groklaw.net/ for example. Very popular blog, sometimes too popular to even access. If it's getting slammed and you can't reach it, Coralize it. The address you would enter in your browser would be http://www.groklaw.net.nyud.net:8090. That's all you do, and it's added to the Coral Cache.
Easy, right? There is even a FireFox extension that lets you Coralize any link with a click of the mouse...
My proposal would be extremely easy to implement in the case of Digg. They simply add code to the site so that a story link would automatically get Coralized as soon as it hit the Digg frontpage (the most popular stories/links). No more 'Digg Effect'--the linked site remains up for all to enjoy. Now, this really needs to happen as soon as the link hits the Digg homepage because it has been my experience (and I am sure I am not alone) that if you try to Coralize a link after it is already getting pounded with requests, it's too late because Coral cannot cache it if it can't access the site or link. It ends up in the same predicament as the rest of us.
Automatically Coralizing a story link when it hits frontpage status on Digg would be the ideal solution for all of us, IMO.
Tags: CoralCDN Digg