November 26, 2024

Lessons from the SCO/IBM Dispute

Conventional wisdom about the SCO/IBM dustup is that it demonstrates a serious flaw in the open-source model – an asserted lack of “quality control” on open-source code that leaves end users open to potential copyright and patent infringement suits. If any pimply-faced teenager can contribute code to open-source projects, how can you be sure that that code isn’t copyrighted or patented by somebody?

SCO charges that IBM took code from a SCO-owned version of Unix and copied it into the open-source Linux operating system, in violation of a contract between IBM and SCO. There is also some ambiguous evidence that SCO may own copyrights on some of the allegedly-copied code, in which case IBM might be liable for copyright infringement.

It may well turn out that SCO’s claims are hooey, in which case the only lesson to be learned is that we shouldn’t take the claims of desperate companies too seriously. But let’s assume, just for the sake of argument, that SCO is right, and that IBM, in violation of contracts and copyrights, did copy code without permission into Linux. What lesson do these (hypothetical) facts have to teach?

Assuming that SCO’s charges are correct, the moral of the story is not, as the conventional wisdom would have it, to avoid software that comes from pimply-faced teenagers. Quite the contrary. The moral is to be wary of software from big, established companies like IBM. In SCO’s story, the pimply-faced teenagers are bystanders – the gray-haired guys in expensive suits are the crooks.

More likely, though, the fact that SCO’s story involves their code ending up in an open-source IBM product, rather than a closed-source one, is just a red herring. IBM would have had just as large an incentive to copy code into a closed-source product, and doing so would have reduced the chance of getting caught. Nobody has offered a plausible reason why the open-source nature of the end product matters.

Now let’s turn to SCO’s argument that ordinary Linux users might be liable for infringing SCO’s copyrights, even if they didn’t know that Linux contained SCO’s code. It’s hard to see how the merits of this argument depend on the fact that Linux is open-source. SCO’s arguments would seem to apply just as well to customers who made copies of closed-source IBM products (presumably, with IBM’s permission but without SCO’s). Once again, the open-source issue seems to be irrelevant.

Now it may well be that open-source products are more prone to copyright infringement or patent infringement than closed-source products. That’s an important question; but I don’t see how the SCO/IBM dispute will help us answer it.

How To Annoy Your Mother-in-Law

Look up her age here. Then send her an email informing her that anyone on the Net can do the same.

UPDATE (9:00 PM): How to run up your mother-in-law’s AOL bill: tell her she can look up her friends’ ages.

Privacy, Blogging, and Conflict of Interest

Blogging can create the most interesting conflicts of interest. Here is a particularly juicy example:

William Safire’s column in today’s New York Times questions the motives of the new LifeLog program at DARPA. (DARPA, the Defense Advanced Research Projects Agency, is the part of the U.S. Department of Defense (DoD) that funds external research and development.)

LifeLog is a latter-day version of the Memex, which was proposed by Vannevar Bush in his famous 1945 Atlantic Monthly article, “As We May Think.” Bush foresaw the Memex as a sort of universal aid to memory that would help you remember everything you had seen and heard. If you couldn’t remember the name of that great Vietnamese restaurant your brother told you about last month, your Memex would know.

Bush realized that the technology to build a real Memex was far in the future, from his perspective in 1945. As of yet, nobody has built a real Memex, because the basic technology hasn’t been available. But that is about to change. Recording devices are getting cheaper and smaller, storage devices are getting cheaper and more capacious, and wireless communication is knitting devices together. Within a few years, it will be possible to build the first Memex. Inevitably, someone will do so.

The DARPA LifeLog program is trying to build a smart Memex. LifeLog is supposed to be smart, so that it can figure out the context of actions, so as to help you recall more accurately and naturally.

LifeLog makes Safire nervous:

But wouldn’t the ubiquitous partner be embarrassing at times? Relax, says the program description, presumably written by Dr. Doug Gage, who didn’t answer my calls, e-mails or frantic telepathy. “The goal of the data collection is to `see what I see’ rather than to `see me.’ Users are in complete control of their own data-collection efforts, decide when to turn the sensors on or off and decide who will share the data.”

That’s just dandy for the personal privacy of the “user,” who would be led to believe he controlled the only copy of his infinitely detailed profile. But what about the “use-ee” — the person that [LifeLog’s] user is looking at, listening to, sniffing or conspiring with to blow up the world?

The human user may have opt-in control of the wireless wire he is secretly wearing, but all the people who come in contact with [LifeLog] and its willing user-spy would be ill-used without their knowledge. Result: Everybody would be snooping on everybody else, taping and sharing that data with the government and the last media conglomerate left standing.

Now we come to the conflicts of interest. Safire laments his inability to talk to DARPA program manager Doug Gage. It so happens that I discussed this very topic with Dr. Gage on Monday – and that I have an audio recording of that conversation! One of my colleagues made the recording, with Dr. Gage’s consent, as a Memex-style aid to memory. [But was his consent really uncoerced, since it might look hypocritical for him to withhold consent under the circumstances? Discuss.]

I would be lying if I said that the thought of publishing the tape never crossed my mind. But it seems obvious that publishing the tape would be unfair to Dr. Gage. He clearly saw me as just another computer scientist. He probably didn’t know that as a blogger I sometimes wear the hat of a pseudo-journalist. It seems unfair to act like a journalist when he was treating me as a non-journalist.

At this point I should probably tell you that I was meeting with Dr. Gage because I’m considering applying to him for funding to do research on how to make LifeLog, and Memexes in general, more privacy-friendly. (The LifeLog announcement explicitly invites proposals for such privacy research.) Publishing the tape would not endear me to the man who will ultimately decide whether to fund my research, so my decision not to publish it cannot be entirely disinterested.

On the other hand, publishing the tape would provide a perfect illustration of the need for the very research I want to fund, by illustrating how one person’s Memex records information that another person considers private. This is exactly the problem that the research is supposed to address. Not publishing the tape just reinforces the counter-argument that the research is not necessary because people can be trusted to respect each others’ confidences.

[In case you’re wondering, there is nothing shocking on the tape. If anything, Mr. Safire would probably find its contents mildly reassuring.]

Clearly, the shrewdly self-interested course of action for me is to write about all of these angles, without actually publishing the tape, and to throw in a gratuitous link to one of my own relevant research papers. Fortunately I would never stoop to that level.

Petition for Public Domain Enhancement Act

Larry Lessig writes:

We have launched a petition to build support for the Public Domain Enhancement Act. That act would require American copyright holders to pay $1 fifty years after a work was published. If they pay the $1, the copyright continues. If they don’t, the work passes into the public domain. Historical estimates would suggest 98% of works would pass into the pubilc domain after 50 years. The Act would do a great deal to reclaim a public domain.

This proposal has received a great deal of support. It is now facing some important lobbyists’ opposition. We need a public way to begin to demonstrate who the lobbyists don’t speak for. This is the first step.

Regardless of your position on the proper length and breadth of copyright, I hope you will agree with me that there is no reason to maintain the copyright on works that are essentially abandoned. A great many old works are simply unusable, because it would cost too much to figure out who owns the copyrights on them. The Public Domain Enhancement Act would put only two tiny “burdens” on copyright owners: (1) pay a fee of one dollar to maintain their copyright on any old work, and (2) register their ownership of the copyrights on old works so that potential licensees can find their owners.

The beauty of this approach is that, while imposing essentially no cost on the owners of commercially valuable copyrights, it reclaims for the public domain that vast majority of works that have no remaining commercial value after fifty years. To enter the public domain, a work has to be so devoid of commercial value that the copyright owner isn’t willing to pay even one dollar to maintain its copyright. This seems like such a no-brainer that it’s hard to see how anyone who takes cultural progress seriously could oppose it.

If you agree with me, please sign the petition.

Software Infringement Rate Decreasing

The Business Software Alliance (BSA), a prominent industry group, has announced the results of its annual study of copyright compliance by business software users.

According to BSA, 39% of business application software, worldwide, was infringing in 2002. This is down from a high of 49% in 1994. The U.S. was the most law-abiding country, with an infringement rate of 23% in 2002.

These are interesting data for the debate about music and movie copyrights. For software at least, the infringement rate is going down, and the U.S. has the lowest infringement rate. The software industry must be doing something right.