<, then >! HD-DVD/Blu-Ray hex hack pulled by digg; users protest; digg acquiesces
May 2, 2007 // No Comments
I find The Consumerist to be a really interesting source of news, and today one of the headlines that greeted me was “Digg Goes Ape$#@*!” [followed in time by “Liveblogging Digg’s $#@*!storm“].
The first story reports:
“A wide-scale user revolt is disrupting popular social news networking Digg. It’s a protest over Digg
acquiescing to MPAA pressure and deleting a 15,000+ dugg story about a crack for the HD-DVD/Blu-Ray DRM system.Now, every single story on the front page contains the cracked number in some way.
The madness began after not only was the initial story deleted, but the user’s account was deleted as well. Other people who submitted stories linking to the number also got their accounts deleted and their sites received takedown notices. Even people who submitted stories about the deleting of other accounts, stories which did not contain the number, also got deleted. That’s when things really got bonkers.
Users are hiding the number in all sorts ways. One story claimed that a new Jules Verne manuscript was found, entitled, “09:F9:11:02:9D:74:E3:5B:D8:… Leagues Under the Sea.” Others link to pictures of the number. A new one says Jesus has “the secret key.” Others coyly ask, “anyone know what this number is?” Diggers are digging the stories like crazy, trying to keep the number on the front page and thumb their nose at Digg and the MPAA.”
Hilarious!!!
Digg/Kevin Rose pulled not only the original post but also deleted the posting user’s account, thus setting Diggers afire.
The original dugg story was published February 13, 2007 and can be found at the Wired Blog Gadget Lab:
The New HD-DVD/Blu-Ray Hack: What It Might Mean For Us
“09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
That’s the so-called “Processing Key” that unlocks the heart of every HD-DVD disk to date. Happy Valentine’s day, AACS.”
A statement from Kevin Rose of Digg, eventually acquiescing to this pressure from Diggers:
“But now, after seeing hundreds of stories and reading thousands of comments, you’ve made it clear. You’d rather see Digg go down fighting than bow down to a bigger company. We hear you, and effective immediately we won’t delete stories or comments containing the code and will deal with whatever the consequences might be.”
Another statement reads:
DiggThis: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0
Today was an insane day. And as the founder of Digg, I just wanted to post my thoughts…
In building and shaping the site I’ve always tried to stay as hands on as possible. We’ve always given site moderation (digging/burying) power to the community. Occasionally we step in to remove stories that violate our terms of use (eg. linking to pornography, illegal downloads, racial hate sites, etc.). So today was a difficult day for us. We had to decide whether to remove stories containing a single code based on a cease and desist declaration. We had to make a call, and in our desire to avoid a scenario where Digg would be interrupted or shut down, we decided to comply and remove the stories with the code.
But now, after seeing hundreds of stories and reading thousands of comments, you’ve made it clear. You’d rather see Digg go down fighting than bow down to a bigger company. We hear you, and effective immediately we won’t delete stories or comments containing the code and will deal with whatever the consequences might be.
If we lose, then what the hell, at least we died trying.
Digg on,
Kevin
This moment has been brought to you by Greater Than. ![]()