September 29, 2022

Aussie Judge Tweaks Kazaa Design

A judge in Australia has found Kazaa and associated parties liable for indirect copyright infringement, and has tentatively imposed a partial remedy that requires Kazaa to institute keyword-based filtering.

The liability finding is based on a conclusion that Kazaa improperly “authorized” infringement. This is roughly equivalent to a finding of indirect (i.e. contributory or vicarious) infringement under U.S. law. I’m not an expert in Australian law, so on this point I’ll refer you to Kim Weatherall’s recap.

As a remedy, the Kazaa parties will have to pay the 90% of the copyright owners’ trial expenses, and will have to pay damages for infringement, in an amount to be determined by future proceedings. (According to Kim Weatherall, Australian law does not allow the copyright owners to reap automatic statutory damages as in the U.S. Instead, they must prove actual damages, although the damages are boosted somehow for infringements that are “flagrant”.)

More interestingly, the judge has ordered Kazaa to change the design of their product, by incorporating keyword-based filtering. Kazaa allows users to search for files corresponding to certain artist names and song titles. The required change would disallow search terms containing certain forbidden patterns.

Designing such a filter is much harder than it sounds, because there are so many artist names and song names. These two namespaces are so crowded that a great many common names given to non-infringing recordings are likely to contain forbidden patterns.

The judge’s order uses the example of the band Powderfinger. Presumably the modified version of Kazaa would ban searches with “Powderfinger” as part of the artist name. This is all well and good when the artist name is so distinctive. But what if the artist name is a character string that occurs frequently in names, such as “beck”, “smiths”, or “x”? (All are names of artists with copyrighted recordings.) Surely there will be false positives.

It’s even worse for song names. You would have to ban simple words and phrases, like “Birthday”, “Crazy”, “Morning”, “Sailing”, and “Los Angeles”, to name just a few. (All are titles of copyrighted recordings.)

The judge’s order asks the parties to agree on the details of how a filter will work. If they can’t agree on the details, the judge will decide. Given the enormous number of artist and song names, and the crowded namespace, there are a great many details to decide, balancing over- and under-inclusiveness. It’s hard to see how the parties can agree on all of the details, or how the judge can impose a detailed design. The only hope is to appoint some kind of independent arbiter to make these decisions.

Ultimately, I think the tradeoff between over- and under-inclusiveness will prove too difficult – the filters will either fail to block many infringing files, or will block many non-infringing files, or both.

This is the same kind of filtering that Judge Patel ordered Napster to use, after she found Napster liable for indirect infringement. It didn’t work for Napster. Users just changed the spelling of artist and song names, adopting standard misspellings (e.g., “Metallica” changed to “Metalica” or “MetalIGNOREica” or the Pig Latin “Itallicamay”), or encoding the titles somehow. Napster updated its filters to compansate, but was always one step behind. And Napster’s job was easier, because the filtering was done on Napster’s own computers. Kazaa will have to try to download updates to users’ computers every time it changes its filters.

To the judge’s credit, he acknowledges that filtering will be imprecise and might even fail miserably. So he orders only that Kazaa must use filtering, but not that the filtering must succeed in stopping infringement. As long as Kazaa makes its best effort to make the agreed-upon (or ordered) filtering scheme work, it will have have satisfied the order, even if infringement goes on.

Kim Weatherall calls the judge’s decision “brave”, because it wades into technical design and imposes a remedy that requires an ongoing engagement between the parties, two things that courts normally try to avoid. I’m not optimistic about this remedy – it will impose costs on both sides and won’t do much to stop infringement. But at least the judge didn’t just order Kazaa to stop all infringement, an order with which no general-purpose communication technology could ever hope to comply.

In the end, the redesign may be moot, as the prospect of financial damages may kill Kazaa before the redesign must occur. Kazaa is probably dying anyway, as users switch to newer services. From now on, the purpose of Kazaa, in the words of the classic poster, may be to serve as a warning to others.


  1. It will sound great to users: “Download the newest version for reduced functionality”… Regardless, over time, the new client will spread.

    On the other hand, anyone using Kazaa Lite doesn’t have to even care about it, at least until there are so many people using filtered clients that no one is sharing files with the correct names any more.

    Cyphrpunk, it won’t kill filesharing in general, is the point. Filtering will make Kazaa more cumbersome, but then so does the RIAA flooding the network with fake copies. The worst case scenario is that Kazaa becomes so encumbered that it basically dies and everyone just starts using some other filesharing tool. In the end, very little will be accomplished. Therefore, filtering really isn’t an effective way to stop filesharing.

  2. How are they going to get the updated software out? Who would willingly install it?

  3. I remember using Napster in the old days, and then after they put in keyword filters. It did make the system much harder to use. There was no standardization or convention for how names would be obfuscated. You’d have to try different misspellings and see if you got lucky. This measure went a long way towards killing Napster.

    Of course that just led to the birth of new services. Sounds like the same thing will happen to Kazaa.

    I see that you have already prepared the groundwork for sticking to your claim that filtering is useless to stop illegal file sharing, by saying that Kazaa is going to die anyway. I disagree. Filtering will be effective, it will make the service much harder to use, and it will kill the service as people switch to others that are easier to use. I don’t see what is so hard to accept about this process except that it flies in the face of the accepted dogma that no technical measure can stop illegal file sharing.

  4. As far as I can tell, the judge did not have an expert working directly for him. He did hear testimony from expert witnesses regarding the viability of filtering. He singled out two experts, one from each side, for praise, and he seems to have taken their testimony into account in designing his filtering order.

    If I were the judge, I would not have issued this redesign order. But I recognize that the judge, having decided to order this kind of filtering, has taken steps to make the order more reasonable. Those steps, I think, reflect his caution, and the influence of skeptical expert testimony.

    It seems to me that he would benefit from the advice of a court-appointed expert in administering the redesign order. (I assume that is feasible procedurally.)

  5. Does the judge have some kind of expert backing up this decision? If not, then it seems incredibly out of line. Nobody would ever accept a judge ordering specific design decisions in a lawsuit that involved airplanes without an expert aerospace engineer behind the recommendations, yet people think that tinkering with software’s design can be done by any bozo with some bright ideas, even though the complexity is comparable (even if the potential threats to public safety are not).