Slashdot Mirror

Open Letter To Steve Jobs: Please Build The Missing Mac

If they build this product then it is unlikely it would have any structural design flaws.

Open Letter To Steve Jobs: Please Build The Missing Mac

http://digg.com/politics/Obama_campaign_uses_dirty _tricks_to_stomp_on_volunteer_on_MySpace

http://blog.digg.com/?p=73

Digg will no longer remove posts containting those numbers, they even posted it themselves

http://digg.com/tech_news/Digg_This_09_f9_11_02_9d _74_e3_5b_d8_41_56_c5_63_56_88_c0_4

From the dig founder. http://blog.digg.com/?p=74

"You'd rather see Digg go down fighting than bow down to a bigger company."*

Isn't digg a Mac site?

[*] - http://blog.digg.com/?p=74

Bwahaha.

http://blog.digg.com/?p=74

One more page in the 295,000+ for the RIAA to send a DMCA takedown notice to.

Kind of reminds me of the end of Spartacus, except the bastards will run out of crosses this time.

He posted a second entry, where he states they changed their mind.

There is a second post from Kevin entitled: "Digg This: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0"

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.

The shirt with everyone's favorite number:

http://digg.com/tech_news/The_Shirt_2

You only need a machine's key to play back hd material, a huge lapse in judgment by the company who made the protection. Posting the code is practically the same thing as posting the key for a copyrighted dvd. The original cracker of the dvd's protection got in trouble for something similar.

http://blog.digg.com/?p=74?

The founder of digg himself decided to fly in the face of law, I'd like to see more "Digg this serial" posts for people's favorite applications or dvds, and continue this thread of fun. Happy Posting!

lol, yeah... it's me :)

perhaps the most famous troll in the history of digg (source: http://digg.com/offbeat_news/Digg_s_most_hated_mem ber_Some_of_Anicejews_most_stupid_comments)

Trolling is indeed a subtle art.

I have had so my IP bans from digg...

As a Slashdot, Digg and Reddit reader I feel like I am part of a crowd that owns these sites. While we may not own them in the typical sense we provide much of the content on these sites and without us they would not function. I think Digg was right in removing the story just because of the possible legal implications but their communication of the issue was terrible. There was no post of the takedown notice or any discussion of the problem, it just disappeared without real consultation. This is the fundamental difference between what has happened on Slashdot with the scientology takedown request and the takedown request in regards to Digg at the moment.

Whether there is a copy write infringement or not is immaterial. No one in their right mind would go up against a large corporation like the RIAA etc. Despite what many people might think the legal system is not about who is right and who is wrong, its about who has the most money. Even if Digg fought a good fight they would run out of money before the RIAA etc came close to spending their petty change. Digg would cease to exist from then on.

If Digg (Kevin Rose) had communicated to the Digg user base in a manner that let diggers feel that they were part of the decision and understood the reasons (2 paragraphs of crap doesn't count http://blog.digg.com/?p=73) then there would be no problem.

To the Digg team - get a communications specialist on your team or this is going to happen again and if there is a next time and Digg doesn't die you might just save yourself the embarrassment.

Furthermore, as of now the Digg's main page has been taken offline. Guess it was due to the fact it looked like this and "stories" popping up linking to pages such as this one.

http://diggriver.com/

This is the official digg mobile website, which is still working even though the main digg.com site is offline. Don't believe me?

Mod this up!

Interestingly enough, Digg just gave up trying to delete 09 f9 11 02 9d 74 e3 5b d8 41 56 c5 63 56 88 c0 related stories - probably about a day too late. It'll be amusing to see whether that white flag will repair their severely damaged credibility or not.

More likely than not their lawyers just figured out that the HDDVD lobby haven't a whelk's chance in a supernova of winning a legal battle, so they gave Mr. Rose the go ahead for Operation Cover-Our-Asses Mark II.

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.

Interestingly, the digg site is currently down with an "Out of Service" notice.

No homepage, but the RSS is still there - http://www.digg.com/rss/index.xml

Digg is currently down. This was the top of the page right before it went down.

http://blog.digg.com/?p=74 [digg.com]?

Digg This: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0
by Kevin Rose at 9pm, May 1st, 2007 in Digg Website

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

Looks like Kevin Rose has finally responded here.

Unfortunately he completely misses the point. People aren't upset just because some stories were deleted, they're upset because they were given absolutely no explanation and when the stories were resubmitted the users were banned. Then they continued to make matters worse by removing stories regarding the unexplained removal of stories and banning of accounts. They didn't bother to explain this either. It wasn't just some stupid number that brought this on and it's not too surprising to see how this got completely out of control.

A post from the blog of kevin rose:

Blog

Kevin Rose posts code and backs down here.

http://blog.digg.com/

This was just posted on Digg's official blog:

"Digg This: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0
by Kevin Rose at 9pm, May 1st, 2007 in Digg Website

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"

It looks like this may be a full reverse - the Digg is cowering before its users. Interesting twist.

Ryan Fenton

From the offical Digg blog, "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."

At this point it looks like look much like a PR move. In an attempt to make themselves look good, they're acting like they're decided to take a stand against The Man, when in fact they're just bowing to pressure. Besides the fact that they just literally couldn't continue enforcing the censorship without turning off the site, they seem to ignore the fact that they didn't just remove articles containing the hex code, but articles containing the story of their censorship!

Slashdot isn't making a big deal out of their lack of censorship, and they aren't issuing a war cry- but I can write F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 without having to worry about my account being deleted, and that means more to me than some half-assed excuse.

Digg is attempting to shift the blame and rally a cause away from it, when it should be admitting that they all made a mistake and apologizing. Now its too late for them to gain the respect of their user base without a lot of long, hard work (if even that will be enough).

Digg This: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0

by Kevin Rose at 9pm, May 1st, 2007 in Digg Website

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

http://blog.digg.com/?p=74 Classy, I love it. I just regained my respect for Kevin Rose.

http://blog.digg.com/?p=74

Digg This: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0
by Kevin Rose at 9pm, May 1st, 2007 in Digg Website

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

Actually they are no longer cencoring. http://blog.digg.com/?p=74
They have heard the community that a number can't be copyrighted and they will take a stand with the community against the abuse of the dmca.

Actually, Kevin Rose has clarified their position

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.

Kevin Rose's blog post
"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."

I bet this contest will throw up some interesting entries :)

Kevin Rose cries "Uncle," using a few more words: http://blog.digg.com/?p=73

http://blog.digg.com/?p=74?

"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"

"
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
"

http://blog.digg.com/?p=74

Kevin Rose responds and bows to digg pressure (aka saving the face).. They just blew it.. haha..

http://blog.digg.com/?p=74

Digg This: 09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0
by Kevin Rose at 9pm, May 1st, 2007 in Digg Website
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

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

After tons of bad press, they've reversed position..

Gee. Took them a while.

http://blog.digg.com/?p=74

"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"

One of the things I like about Slashdot is how they handled the Cult of Scientology thing. Slashdot complied with style. Cowards, by contrast, have no style.

Obviously, we need two slashdot articles linking to http://www.digg.com/tech_news/Slashdot_Digg_com_At tempts_To_Supress_HD_DVD_Revolt

Whoever did, used colours, just poor C0 dropped from the picture. Taken from a digg story.

Dugg already: http://www.digg.com/tech_news/Slashdot_Digg_com_At tempts_To_Supress_HD_DVD_Revolt

At any rate, this is a parody of Allan Sherman's tirade against all-digit dialing, "The Let's All Call Up AT&T And Protest To The President March". By staggering coincidence, the original was inspired by someone posting it in on USENET in the .mp3.comedy group. Weren't me, although my parents turned me onto Mr. Sherman's parodies by giving me their vinyl original that they'd owned since before I was born.

By even more coincidence, you can sing it as either: "Let's all post the Processing Key and fuck AACSLA" March, for rather obvious reasons, or the "Let's all post To D-I-G-G and say 'fark you' to Kevin Rose" March, (on account of every single story on digg.com's front page, as the original poster already linked to in TFA)

By utterly unsurprising coincidence, and like every filk I write here, this parody is in the public domain, and you can sing it however you like, although in this case it'll probably be funnier if you keep the numbers the way they was written.

AACS VERSION:

It's the "Let's all post the processing key and fuck AACSLA!" march!
Watch their lawyers worry and fidget,
Cease and DE-sisting sixteen hex digits!

So let's all post the processing key and fuck AACSLA, march!
So protest! (so protest!)
Do your best! (do your best!)
Let us show them that we post in unity.
If they won't (if they won't!),
Change the rules (change the rules!),
Let's buy our movies from another monopoly!

Let's all post the processing key and fuck AACSLA march.
Let us wake their landsharks from slumber,
Get a pencil, I'll give you their number.

It's Nine, Eff-nine, One-one, Two, Nine-D,
SevenTY-four, Eee-three, Five-B... (dash!)
Dee-eight, four-one, five-six, Cee-five,
Sixty-three, fifty-six, eight-eight... (hyphen!)
And now that you're on the right road,
Don't forget to end with Cee-0h!

Here's to freedom and fair use! 09F9! 1102s!
Watch your HD-DVD! 9D74! E35B!
Let's keep that 16-byte key alive!
D841! 56C5! AACS is totally broke! 6356! 88C0! Hooray!

To arnezami's mental fiber,
We'll erect a triumphal arch!
For the "let's all post the processing key and fuck AACSLA!" march.

And since we're long (about 2 and a half months!) past the point that a parody of the AACS key wouldn't be complete without the
DIGG VERSION:

It's the "Let's all post To D-I-G-G and say 'fark you' to Kevin Rose" march!
Watch him worry, watch as he fidgets,
As his users post sixteen hex digits!
So let's all post to D-I-G-G and say 'fuck you' to Kevin Rose march.
So protest! (so protest!)
Do your best! (do your best!)
Let us show him that we digg in unity.
If he won't (if he won't!),
Change the rules (change the rules!),
Let's take our pageviews to Slashdot's company!

Let's all post to D-I-G-G and say 'fuck you' to Kevin Rose march.
Let us wake him up in his slumber.
Get a pencil, I'll give you his number.

It's Nine, Eff-nine, One-one, Two, Nine-D,
SevenTY-four, Eee-three, Five-B... (dash!)
Dee-eight, four-one, five-six, Cee-five,
Sixty-three, fifty-six, eight-eight... (hyphen!)
And now that you're on the right road,
Don't forget to end with Cee-0h!

Here's to freedom and fair use! 09F9! 1102s!
Watch your HD-DVD! 9D74! E35B!
Let's keep that 16-byte key alive! D841! 56C5!
AACS is totally broke! 6356! 88C0! Hooray!

To arnezami's mental fiber,
We'll erect a triumphal arch!
For the let's all post to D-I-G-G and say 'fuck you' to Kevin Rose march.

And don't make me deal with this "Your comment has too few characters per line (currently 35.7)", because it's a long pair of

Digg actually posted a reply to the community on their blog here.

What I'm honestly curious about is this: Is this numeric string code copyrighted? Where is the copyright filed, if so? Or is it a trade secret? Do trade secrets need to be filed or declared somehow? Is a trade secret intellectual property that must be removed when a theatening (maybe DMCA) notice is sent?

I'm nowhere near understanding the complexities of the current intellectual property legal codes in the USA, let alone how they actually apply in this situation. All I see is hysteria.

Whether you agree or disagree with the policies of the intellectual property holders and consortiums, in order for Digg to survive, it must abide by the law. Diggs Terms of Use, and the terms of use of most popular sites, are required by law to include policies against the infringement of intellectual property.

http://www.digg.com/tech_news/DIGG_What_s_Happenin g_with_HD_DVD_Stories 18th comment has you covered

The link, however, was posted by Kevin Rose on digg. It is safe to assume that blog post reflects Kevin's view on this as well.

Amazingly enough it is not only articles that are being deleted. Digg comments explaining why it was a bad move by Digg are also being deleted! (Scroll down to a thread where users are saying their comments are being deleted because they explained how posting a number is not illegal)

Here is Kevin Rose's response as to why they have been deleting the stories over at Digg. Will Slashdot follow as well? If not why or why not?