Slashdot Mirror


DMCA Hurts Copyright Holders, Too

adam613 writes: "Further proof that the DMCA is designed to protect corporations rather than copyright holders: ZDNet is reporting that an author who published e-books that an AOL user posted on Usenet can not hold AOL legally responsible. While AOL is an ISP and ISPs can not feasibly censor their users, AOL is also a content provider, just like Napster. In the end, the copyright holder who the DMCA is supposed to protect got screwed. Things could start to get interesting here...any lawyers ready to make judges start scratching their heads?"

23 of 47 comments (clear)

  1. Because AOL is an ISP by outlier · · Score: 4, Insightful

    Just because AOL is a content provider, doesn't mean they shouldn't be protected when they act as an ISP.

    Yes, the DMCA sucks huge amounts of ass. Yes, the DMCA was designed to protect big content providers and not copyright holders. Yes, AOL is a big (evil?) corporation.

    BUT, one of the few sane aspects of the DMCA is that it doesn't hold ISPs liable if they remove infringing material. This allows ISPs to react to claims in a reasonable manner (note, that doesn't guarantee they will, it only enables them to). If ISPs could be held liable for everything their users did, how long before AOL and others began enforcing even more draconian restrictions preempting their users' behaviors...

    The DMCA sucks, is evil, etc... But this provision isn't the reason.

    1. Re:Because AOL is an ISP by Dyolf+Knip · · Score: 2

      Of course this case is bullshit. Homegrown, freshly squeezed, ripe on the vine, bullshit, I agree. But it's no more so than any of the others that have come by, which, golly gee, always seem to end in favor of the side with deeper pockets. Can 2600 or Google actually be held responsible for what people might do with content that isn't even on their servers but happens to be linked to on their site? The courts say, "Hell yes!". Can AOL/TW actually be held responsible for what people might do with content that isn't even on their servers but happens to be linked to on their site? The courts say, "Well, of course not". It's ridiculously hypocritical and we have yet to see the DMCA come down on the side of the people it's proponents claimed it would protect.

      --
      Dyolf Knip
  2. Political Ignorance by Vodak · · Score: 2, Insightful

    While I do not agree with term limitations for congressional office this is what you get when you have career politicians in office unchallenged for all many years. If your congress person doesn't understand the subject he/she is voting on then get rid of him/her. All people including the readers of Slashdot need to stop voting someone into office because they believe in a single issue.

  3. Re:This has to be good... by Rick+the+Red · · Score: 4, Insightful
    I don't understand your reasoning. You say this ruling is good because "If this doesn't prove that the DMCA should be repealed, I don't know what will." I disagree. What this proves is that the DMCA works as designed: AOL was protected, and the individual (in this case Harlan Ellison) got screwed.

    This case might make industry think twice about the DMCA if the copyright work in question were owned by, say, Bertelsmann or another AOL-Time-Warner competitor. But as the suit was brought by some puny individual (no offense, Mr. Ellison, but you're not a mega-media conglomerate) and the Right Side won, this won't change the opinions of Anyone That Matters.

    --
    If all this should have a reason, we would be the last to know.
  4. This part of DMCA isn't bad by Sloppy · · Score: 2

    I hate DMCA as much as anybody, but protecting common carriers when one of their users infringes, is a good thing. Slashdot shouldn't ever be liable for something that its users post, especially if they delete it (like what happened with the cultist trade secret).

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    1. Re:This part of DMCA isn't bad by President+Chimp+Toe · · Score: 2

      please, i know this is widely offtopic:

      but what is this "cultist trade secret" incident?

      I'm intrigued....

    2. Re:This part of DMCA isn't bad by PD · · Score: 2, Informative

      I think it was a posting of Scientology's OT-III. Apparently they were afraid that too many people would find out that it's just a really bad science fiction story.

    3. Re:This part of DMCA isn't bad by Dyolf+Knip · · Score: 2
      protecting common carriers when one of their users infringes, is a good thing

      And most everyone will agree with you. The carrier should be no more held accountable for my actions while using their services than a random bystander. The problem demonstrated here is the double standard the courts have been displaying; AOL as an carrier is immune from prosectution, but Google, 2600, Napster, and even Slashdot as carriers are not. Why?

      --
      Dyolf Knip
  5. Re:This has to be good... by Rick+the+Red · · Score: 2
    Yes, but didn't we know that before this case?

    --
    If all this should have a reason, we would be the last to know.
  6. Nothing new here. by troyboy · · Score: 2

    ISPs have almost always been protected from contributory copyright infringement suits. Even before this one aspect of the DMCA gave a "safe harbor" to ISPs, some courts looked like they would do the same thing (e.g. the Netcom case).

    This provision of the DMCA is good because it protects the people who provide the pipes from copyright suits. Other provisions of the DMCA such as the anti-circumvention provisions (see the DeCSS case) and overbearing notice-and-take-down rules (closely related to the ISP safe harbor) are what people should worry about, not the whole DMCA.

  7. Say what? by anthony_dipierro · · Score: 2

    Further proof that the DMCA is designed to protect corporations rather than copyright holders

    Huh? Aren't most copyrights held by corporations?

    1. Re:Say what? by Dyolf+Knip · · Score: 2

      Regardless of whether they do or not, the problem is that corporate copyright holders win nearly every time but an individual copyright holder will lose. The 2600/DeCSS case is similar to this in so very many ways (being held responsible for linking to content on other people's servers), yet AOL got the case against them thrown out before it got off the ground.

      --
      Dyolf Knip
  8. Re:Is AOL guilty here? I don't think so. by CaptJay · · Score: 2

    "if they remove offending content after they are notified"

    There lies the problem with this particular provision: to avoid liability, ISPs have to shut down the allegedly offending content before it is determined wether it is illegal or not. When faced with potential liability, somehow I don't think ISPs think twice before simply removing the content before hearing out what their customer has to say. The burden is then on the user to prove that the content does not infringe on any copyright.

    Sentence first, judgement later. Guilty until proven innocent, with a twist: if the "judge" (in this case, the ISP) did not immediately condemn the user who in the end did something wrong, they open themselves up to litigation. From a pure justice point of view, this sucks.

    --
    "I remember Y1K, every abacus had to get another bead"
  9. No, they don't ever delete by melquiades · · Score: 2

    They will only mod to -1. Here it is from the proverbial horse's mouth -- when I wrote in about a threatening post which included a guy's home address, this is all that Taco wrote back:


    From: "Rob \"CmdrTaco\" Malda"
    Date: Mon Oct 08, 2001 08:18:20 US/Central
    To: Paul `Order in Chaos` Cantrell
    Subject: Re: Abusive and possibly dangerous post

    We don't remove comments. It sucks, but people did this to my girlfriend for
    awhile too. She had to get an answering machine and screen her calls.


    And it's a reasonable policy if they stick to it -- they won't touch comments, they're not responsible, and there's no liability. They just modded the abusive post down (I presume it was the editors) to -1 ("offtopic", interestingly, and not "troll").

    Can you confirm that Slashdot really broke their own policy for the Scientologists? Or is this just hearsay?

  10. We don't want it both ways. by Fat+Casper · · Score: 4, Insightful
    AOL is just as "responcible" for the content that its users make publicly available as the old Napster was. When the company is a little guy, it gets crucified. When the company is AOL-TW, the same logic used to reach an anti-Napster verdict gets thrown out the window. This case highlights the intellectual dishonesty in both the DMCA and its enforcement. It is not about protecting copyright holders, as the enforcers claim. If the reasoning in this case were applied to the Napster case, then Napster would be back to the way it used to be.

    --
    I spent a year in Iraq looking for WMD and all I found was this lousy sig.
    1. Re:We don't want it both ways. by TheAwfulTruth · · Score: 2

      Not *quite*. This has already been hashed to death, but you probably weren't listening. Napster advertised the fact that they were in the buisness of trading copyrighted material for free. That's what got them in trouble. AOL is a general purpose transport, like your phone or the mail. If someone were to set up a system for phoning free music to you and that's all it did and they advertised that, then they would go down while ma bell stayed up. The term "Primary and overriding purpose" is the phrase on which such laws turn.

      --
      Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
    2. Re:We don't want it both ways. by arkanes · · Score: 2

      You mean kinda like how Google is a general purpose search engine, and shouldn't be held liable for the content it indexes and caches? If Google can be held liable under the DMCA for it's content, then so can AOL.

    3. Re:We don't want it both ways. by Dyolf+Knip · · Score: 2
      Except Napster wan't even hosting anything. There was nothing for them to 'take down' since there was nothing 'put up' in the first place. They were essentially a search engine.

      From the article, AOL "lobbied for exemptions that would prevent them from having to spend all their time policing their networks". But then they turn around and say, "Napster must not allow the media to be listed in the first place." Why does Napster have to act first while AOL need only react to alleged copyright violations? The difference sounds small but it's basically saying that the big guys can do anything that is not forbidden, but the little ones can only do what is explicitly permitted.

      --
      Dyolf Knip
  11. AOL DMCA "safe harbor" by russotto · · Score: 2, Informative

    AOL wasn't granted dismissal based on 17 USC 512(c), which is the part with all the notification and counternotification. That's the nasty private-gag-order provision of the DMCA which many (including myself) object to.

    Rather, they were also claiming protection under 17 USC 512(a), "transitory digital network communications", and it is on that provision they obtained summary judgement. This doesn't include ANY takedown provision, and if this decision is affirmed by higher courts, it effectively exempts Usenet providers from liability for posts not made by their own customers.

    IMO, this is a good thing, and Harlan Ellison can change his "KICK" campaign to "KICK ME". Note that he's also suing AOL for merely developing Gnutella!

  12. Re:Is AOL guilty here? I don't think so. by arkanes · · Score: 2

    No, the proper way, and the way it worked pre-DMCA is that the content stays up until it's proved to be infringing (or a court orders it taken down pre-trial). The ISP, assuming the correctness of the common carrier argument, has nothing to do with it at all. The ISP provisions are there so they can control content posted by people anonymously, or out of the country. It's an open argument as to whether or not this power is worth making ISPs reposonsible to content, but it's apparent which way the legislation went.

  13. Re:Is AOL guilty here? I don't think so. by Dyolf+Knip · · Score: 2

    So, what, I'm not allowed to say anything until it has been deemed acceptable to a copyright holder somewhere? How about I say what I want, then you prove in a court, not just send a nastygram, that it is unacceptable, then and only then does the ISP have to take it down.

    --
    Dyolf Knip
  14. Re:Hypocrites, plain and simple by Dyolf+Knip · · Score: 2

    The hypocrites are not the /.ers but the courts. MPAA sues 2600 for linking to naughty content and wins. Ellison sues AOL/TW for not only linking to but actually hosting naughty content and the case gets dismissed. The whole ISP non-liability thing has a horrible double standard here.

    --
    Dyolf Knip
  15. Clambake didn't want to submit to US rent-a-court by yerricde · · Score: 2

    If Google can be held liable under the DMCA for it's content, then so can AOL.

    Operation Clambake didn't file a counter-notification letter because it didn't want to subject itself to a rent-a-court of Co$'s choosing.

    --
    Will I retire or break 10K?