A careful read of the post turns up very little actual information. There’s indignation over the story, indignation over us not giving them a heads up, and a statement that it’s impossible for data to be sent to CBS without Garrett’s knowledge. They also say “Any suggestion that we were complicit in transferring user data to any third party is incorrect.”
We need more than that.
Isn't it the accuser's job to prove that someone is guilty, rather than the defendant's job to prove his innocence? TechCrunch is still publishing this based on only a couple sources. I realize that it is hard to get even a couple sources, but what if even one of those sources is fake? Since we can't know anything about them, we have no way of validating what TechCrunch is saying.
This is pretty serious; if true, they just lost a lot of credibility. A mistake people can understand, lying or intentionally misleading people is burning bridges you can't easily get back... I gave the benefit of the doubt, if it turns out this is what they did i'm deleting my account...
I actually deleted mine when I first heard this story, then heard their denials, wasn't sure, and spent a period of time thinking "well, that was kind of dumb, look before you leap next time" because my account dated back to the audioscrobbler days and had a lot of data. Now I feel somewhat vindicated but even more disappointed.
> We’d like to provide you with legal counsel at our cost.
You know, I don't always see eye to eye with Michael Arrington, but that is a remarkable offer, and I applaud his honorable deed. (I hope I don't end up eating my words after some sort of scandal.)
1) Whistleblower statutes generally only apply when exposing criminal contract, not a civil liability (as with a violation of a company's Privacy Policy).
2) I wouldn't want to figure out which state or states' laws apply - you'd probably want counsel in at least DE, NY, and CA (and maybe DC as well)
3) Third party payments may weaken attorney-client privilege
4) The interests of TechCrunch and the fired employee may not necessarily be aligned, although that's hard to predict through what would ostensibly be years of litigation.
5) If it takes years, TechCrunch's appetite to continue to pay counsel could weaken
Look, I appreciate the sentiment, but I wouldn't take that offer if I were the fired employee. If Arrington wanted to help the guy, he'd give him a job.
[EDIT: Arrington is a lawyer, although non-practicing, so I'm going to hope that he's thought through all this and that I'm wrong on some of the facts. He's, at the very least, smart enough not to represent TC himself. A fool for a client and all that.]
It is absolutely in TechCrunch's best interest to protect their sources or fewer of them will contact TechCrunch with tips because they're afraid of retribution.
If TC offers to protect them somewhat, then it helps mitigate the concern future whistle-blowers will have telling TechCrunch.
I think the other points in this thread about the law not protecting civil cases is interesting-- but I suspect TC is really just doing this to make future leak providers less fearful. "We'll stand behind you against your company if you give us the dirt."
Well, 401 of us don't... But just because we voted it up doesn't mean we sided with last.fm. Sometimes, I vote things up because I think they are of interest. That reply was clearly of great interest - as is this article.
It would help if somewhere in there they actually said they didn't do it.
edit (from the comments):
>They'd still have to ask for the data linking scrobblers to IP addresses, which they have not done. Asking for that data would raise red flags on my end...
oddly enough, if RIAA sues everyone who scrobbled pre-release stuff on last.fm, they don't gain anything. it won't stop file sharing, it'll just stop scrobbling, leading to a less representative statistical sample of people's listening habits. that'll hurt last.fm and RIAA more than anyone else.
Companies with VC money have to be acquired - by another company or the public (via IPO). The VCs must have their exit - their funds are not for long term investment.
I'm surprised he shows a screenshot of the email. Is a screenshot at all better than a verbal account, given how easy to fake the screenshot in question would be?
I am kind of ashamed that the company I work at is part of CBS Interactive. I like the people that I work with. At least our group is in no way affiliated with what's going on here.
The implications from requesting ip addresses appears to be attempting to find the original leak source, ie the earliest scrobbles not accountable to journalists, execs. (This is a guess, not something I know)
Wrong on a technicality, but not wrong enough. last.fm may not have directly handed anything over, but they unintentionally collaborated in handing it over, and then (I consider this the key point) they attempted to deny that the handover happened.
I believe the phrase he used was "materially correct". Which it was. User data that originated at last.fm was given to the RIAA. It's hard to say the original story was flat wrong.
I wonder how easy it would be to prove that one of the users whose data was leaked was a citizen of the EU or the state of California, which have pretty strong data privacy laws if I'm not mistaken. I smell a lawsuit.
[+] [-] palish|17 years ago|reply
We need more than that.
Isn't it the accuser's job to prove that someone is guilty, rather than the defendant's job to prove his innocence? TechCrunch is still publishing this based on only a couple sources. I realize that it is hard to get even a couple sources, but what if even one of those sources is fake? Since we can't know anything about them, we have no way of validating what TechCrunch is saying.
[+] [-] dantheman|17 years ago|reply
[+] [-] smhinsey|17 years ago|reply
[+] [-] j2d2|17 years ago|reply
[+] [-] smhinsey|17 years ago|reply
You know, I don't always see eye to eye with Michael Arrington, but that is a remarkable offer, and I applaud his honorable deed. (I hope I don't end up eating my words after some sort of scandal.)
[+] [-] sachinag|17 years ago|reply
1) Whistleblower statutes generally only apply when exposing criminal contract, not a civil liability (as with a violation of a company's Privacy Policy). 2) I wouldn't want to figure out which state or states' laws apply - you'd probably want counsel in at least DE, NY, and CA (and maybe DC as well) 3) Third party payments may weaken attorney-client privilege 4) The interests of TechCrunch and the fired employee may not necessarily be aligned, although that's hard to predict through what would ostensibly be years of litigation. 5) If it takes years, TechCrunch's appetite to continue to pay counsel could weaken
Look, I appreciate the sentiment, but I wouldn't take that offer if I were the fired employee. If Arrington wanted to help the guy, he'd give him a job.
[EDIT: Arrington is a lawyer, although non-practicing, so I'm going to hope that he's thought through all this and that I'm wrong on some of the facts. He's, at the very least, smart enough not to represent TC himself. A fool for a client and all that.]
[+] [-] thorax|17 years ago|reply
It is absolutely in TechCrunch's best interest to protect their sources or fewer of them will contact TechCrunch with tips because they're afraid of retribution.
If TC offers to protect them somewhat, then it helps mitigate the concern future whistle-blowers will have telling TechCrunch.
I think the other points in this thread about the law not protecting civil cases is interesting-- but I suspect TC is really just doing this to make future leak providers less fearful. "We'll stand behind you against your company if you give us the dirt."
[+] [-] pg|17 years ago|reply
http://news.ycombinator.com/item?id=491750
I'm happy to say that I personally see an uparrow next to that item.
[+] [-] swombat|17 years ago|reply
[+] [-] unknown|17 years ago|reply
[deleted]
[+] [-] sounddust|17 years ago|reply
http://www.last.fm/forum/21717/_/535934/_/9521312
[+] [-] radu_floricica|17 years ago|reply
edit (from the comments):
>They'd still have to ask for the data linking scrobblers to IP addresses, which they have not done. Asking for that data would raise red flags on my end...
[+] [-] wallflower|17 years ago|reply
"Is this the same exceptionally good source that told you that Last.fm handed user data over to the RIAA?"
Reply by Michael Arrington (@arrington) - May 22nd, 2009 at 12:40 pm PDT
last fm story was right. continues to be right.
[+] [-] staticshock|17 years ago|reply
[+] [-] danw|17 years ago|reply
[+] [-] alexfarran|17 years ago|reply
[+] [-] geirfreysson|17 years ago|reply
[+] [-] ableal|17 years ago|reply
[+] [-] Dilpil|17 years ago|reply
[+] [-] trickjarrett|17 years ago|reply
[+] [-] knightinblue|17 years ago|reply
Is there a reason for the timing? Other than coincidence of course.
[+] [-] jkincaid|17 years ago|reply
[+] [-] alexfarran|17 years ago|reply
[+] [-] ciscoriordan|17 years ago|reply
[+] [-] geuis|17 years ago|reply
[+] [-] llimllib|17 years ago|reply
[+] [-] froo|17 years ago|reply
[+] [-] zimbabwe|17 years ago|reply
[+] [-] samlittlewood|17 years ago|reply
[+] [-] danw|17 years ago|reply
[+] [-] tsally|17 years ago|reply
[+] [-] tvon|17 years ago|reply
So the original story was was admittedly wrong?
[+] [-] philh|17 years ago|reply
[+] [-] chairface|17 years ago|reply
[+] [-] rabidsnail|17 years ago|reply
[+] [-] unknown|17 years ago|reply
[deleted]
[+] [-] danw|17 years ago|reply
[+] [-] vaksel|17 years ago|reply
[+] [-] unknown|17 years ago|reply
[deleted]
[+] [-] kleevr|17 years ago|reply
feels like a fair mention, so I'll push the point and a-void your convention.