February 24, 2018

Archives for October 2007

Grokster Case Lumbers On; Judge To Issue Permanent Injunction

Remember the Grokster case? In which the Supreme Court found the filesharing companies Grokster and StreamCast liable for indirect copyright infringement, for “inducing” infringement by their users? You might have thought that case ended back in 2005. But it’s still going on, and the original judge just issued an interesting ruling. (Jason Schultz has a two part summary of the ruling.)

The issue now before the judge is what relief to grant the copyright-owner plaintiffs against StreamCast, which is the only defendant still standing. It’s apparently a given that the judge will eventually assess monetary damages against StreamCast. And you’d think these damages would be enough to kill StreamCast, so it’s not clear why StreamCast hasn’t just thrown in the towel, shut its doors, and handed over all its assets to the plaintiffs. Instead, StreamCast fought on, so the judge had to decide what kind of injunction, if any, to impose on StreamCast – that is, what rules would govern StreamCast’s future behavior.

The judge first considered the question of whether he could impose on StreamCast obligations (beyond payment of damages) that go beyond what the law requires of ordinary companies. Would he just award money damages and sternly command StreamCast not to break the law again; or would he go further and impose a permanent injunction? After a detailed legal analysis, he concluded that a permanent injunction was appropriate. StreamCast had actively promoted itself as a haven for infringement and “that bell cannot be unrung”.

The copyright-owner plaintiffs had asked for an injunction requiring StreamCast to apply all feasible anti-infringement technologies and to stop all infringment. StreamCast had built its own filtering technology which it said was effective enough, and much cheaper and more practical than commercially available alternatives.

The judge first rejected the plaintiff’s proposal that StreamCast be required to stop all infringement using its software. He recognized, correctly, that that would be impossible, so that such an injunction would be a death sentence for StreamCast.

Instead, the judge will require StreamCast to set up a filtering system that reasonably balances effectiveness and cost, with the strong emphasis on effectiveness. The precise details will be worked out with the help of a special master: an independent technical expert to be appointed by the judge. Which means yet more legal process to choose the special master, wait for the special master’s advice, and then order specific action from StreamCast.

All of this may be proper from a legal standpoint, but it seems unlikely to matter in practice. It’s hard to see how StreamCast can sustain a business given the legal and financial strain they must be under, and the likely ruinous monetary damages they’re still facing. I can understand why the plaintiffs might want to keep StreamCast on life support, in the hope of getting legal rulings that prove helpful elsewhere. But why does StreamCast keep fighting?

Online Symposium: Future of Scholarly Communication

Today we’re kicking off an online symposium on The Future of Scholarly Communication, run by the Center for Information Technology Policy at Princeton. An “online symposium” is a kind of short-term group blog, focusing on a specific topic. Panelists (besides me) include Ira Fuchs, Paul DiMaggio, Peter Suber, Stan Katz, and David Robinson. (See the symposium site for more information on the panelists.)

I started the symposium with an “introductory post. Peter Suber has already chimed in, and we’re looking forward to contributions from the other panelists.

We’ll be running more online symposia on various topics in the future, so this might be a good time to bookmark the symposium site, or subscribe to its RSS feed.

attack of the context-sensitive blog spam?

I love spammers, really I do. Some of you may recall my earlier post here about freezing your credit report. In the past week, I’ve deleted two comments that were clearly spam and that made it through Freedom to Tinker’s Akismet filter. Both had generic, modestly complementary language and a link to some kind of credit card application processing site. What’s interesting about this? One of two things.

  1. Akismet is letting those spams through because their content is “related” to the post.
  2. Or more ominously, the spammer in question is trolling the blogosphere for “relevant” threads and is then inserting “relevant” comment spam.

If it’s the former, then one can certainly imagine that Akismet and other such filters will eventually improve to the point where the problem goes away (i.e., even if it’s “relevant” to a thread here, if it’s posted widely then it must be spam). If it’s the latter, then we’re in trouble. How is an automated spam catcher going to detect “relevant” spam that’s (statistically) on-topic with the discussion where it’s posted and is never posted anywhere else?