CoreCodec Apologizes For CoreAVC Takedown
I Don't Believe in Imaginary Property writes "In a follow-up to the previous story, CoreCodec has apologized for the incorrect DMCA Takedown notice that took the CoreAVC project offline. There's also a public statement by co-founder Dan Marlin saying in part, 'I'd like to publicly apologize to Alan [CoreAVC project lead] for the disconnect between him and us as well as the disruption to the project as there was no ill will intended and we were already working on a resolution with him before this went public.' They've also created a new policy for sending out DMCA Takedown notices, so that they won't misuse them in the future."
It's already back up, you know. http://code.google.com/p/coreavc-for-linux/
And CoreCodec. The company that _seriously_ demanded online activation for a $10 video codec. Including dongeling it to your current hardware config.
HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
While I always admire when a company admits they were wrong about something, I have to think that this is just massive damage control. Imagine what their inboxes looked like over this fiasco :-)
Can anyone tell me why you would possibly want to plug CoreAVC into MPlayer and Xine or GStreamer based applications when these already have native H.264 playback?
For decoding, ffmpeg (Which has a code base used throughout a tonne of the Free Software world) already has a decent decoder, and for encoding we have x264 (Developed by the folks behind VLC)...
I know that CoreAVC claims to be super optimised, but is it really that much better? I have always assumed that they were just milking those Windows users that didn't know of ffdshow.
At least this segment of it, I'm not sure what else it contains.
1. If you post material online, someone can send a DMCA notice and have it instantly taken down. They must though state that legally and in good faith they have strong reason to believe they are copyright owners.
2. If you challenge it, you send a DMCA counternotice and the material is put back up. You must though state that legally and in good faith you either are the copyrightholder or its in public domain. By doing this you also have to reveal your name. Obviously if you are not willing to reveal your name, you can't counternotice.
(the only potential misuse I could see is if people have a good reason to post anonymously, like whistleblowers - anyone know of any use like that? Obviously this would however confirm that any material taken down is not falsified or the company could not claim copyright)
3. If both parties are in good faith, then obviously let the lawsuits commence. If one of the party was not in good faith - well, they can be smacked down very hard quite easily. It looks like CoreCodec just discovered they were not actually in good faith and are doing damage control.
the only potential misuse I could see is if people have a good reason to post anonymously, like whistleblowers - anyone know of any use like that?
Scientology critics?
If one of the party was not in good faith - well, they can be smacked down very hard quite easily.
Inconceivable!
It looks like CoreCodec just discovered they were not actually in good faith and are doing damage control.
I think that's what they said, yes. Their message is basically "we fucked up, sorry, we're making sure we can't fuck up that way again".
Voluntarily admitting they fucked up when they fuck up, let alone bothering to figure out how they can avoid fucking up again, is unfortunately rare enough for organizations that it's actually impressive to see one do it without having to be dragged through a lawsuit first. I don't think you're giving them enough credit.
So which is it? Is it "sorry we did this", or "sorry we got caught?"
What, because Google complied with a legally worded (albeit faulty) DMCA takedown notice, as they are legally obliged to do?
IIRC, it's down to the project owner to then turn around and say "There's nothing the matter with it, you shouldn't have been served the takedown notice". Google is only a middleman here.
But the real question is, is there any such thing as bad publicity?
This whole drama seems manufactured to get attention for another *yawn* codec.
-1 Uncomfortable Truth
After that, it's up to the courts, if either party wants to take it that far.
There are even sites out there to generate your own DMCA counterclaim quick and fast.
One such is: http://www.cs.cmu.edu/~dst/Terrorism/form-letter.html or here: http://www.ucmo.edu/dmca/counter.html
People unfortunately probably go to lawyers first, a little bit of knowledge goes a long way.
However, DMCA misuse is something that can be sued for and withdrawing the already DMCA'd request doesn't lift that vulnerability in court...there is a provision for DMCA misuse.
So according to this, the CEO has legally stated that his company downloaded the software and confirmed the violation. But today, he says it was just an overzealous legal department, and no such download happened. In that case, he signed a letter making legal statements that he knew were false.
If I ran this project, I would not be satisfied by an apology posted in a forum. They sent a legal statement and that requires a legal reply. I would continue as the DMCA stipulates, stating that the project does not infringe. I think I'd also be looking for a few lawyers to get fired. And the CEO needs to be quaking in his boots with the fact that his signature is on a legal notice that is a complete lie.
Why so harsh? They apologized, right? Because these stories happen all the time and I'm sick of companies getting away with it. If you send a legally binding letter with your signature on it, forcing someone to take down their web site, invoking a legal process - then you damn well better be sure that you were in the right. If we let this go, then the procedure becomes:
1. Company sends take down notice
2. Alleged infringer has to prove that they aren't infringing
3. Company allows them to put the project back up
That's not fair. That means any corporation can take down any site, any time, anywhere, with no fear of legal reprisal. That's not how the DMCA works and we need to stop them from using it that way. The DMCA is not carte-blanche to shut down web sites.