Home Page
04.28.2008 (previous | next)
"Free" Culture: It's Not What "We in the West" Might Imagine

Today, I released the first in a series of papers that will focus on the so-called “Free Culture Movement,” which, as today’s paper explains, could be just as fairly called the “Costly, State-Controlled Culture Movement” because the meaning of these two phrases became synonymous in the works of Professor Lawrence Lessig, author of the book Free Culture.

Essentially, the paper tries to survey Lessig’s writings to try to understand how even the demagoguery-prone author of Free Culture could have ended up arguing that we should replace copyrights—exclusive rights granted to the authors of expressive works—with tax-funded art and pervasive federal surveillance of what law-abiding citizens do, read, hear, and watch in their own homes, cars and offices.

I don’t usually try to anticipate responses, but two seem sufficiently predictable to be worth noting in advance, in hopes of better focusing debate.

First, some may argue that if Free Culture promotes an “Orwellian” future for copyright, then the use of so-called filtering technologies at the ISP or application level is equally Orwellian.

No, it isn’t. As I use the term here, filtering technologies work like this: They automatically use an algorithm to analyze given files and generate a unique digital identifier that is then automatically checked against a reference database that contains the fingerprints of files not authorized for uploading/transmission. If there is a match, the upload or transmission is blocked, if not, it completes, and the algorithm moves on to the next file. Nothing in this process requires the system retain any information, or communicate it to any rightsholder, or service-provider/ISP.

No one who presently uses a file-sharing program can credibly claim to find this process objectionable. File-sharing programs like LimeWire already generate similar digital file identifiers for each shared file and then store databases of them on multiple, potentially insecure computers scattered across the Internet. Moreover, (see here at p. 59, n.93), most such programs will, by default, create such databases (and fileservers) on computers owned by program users’ ISPs. For users of such programs, any alleged concerns about filtering look much like thinly veiled excuses for piracy.

For others, it is important to note what such filtering technologies do not do: They do not identify the content of any file that does not match one in their reference database. In other words, the filtering system does not “know” anything about the activities of noninfringing users.

The scheme advocated by Lessig is frighteningly different: It involves the government collecting, retaining, and analyzing surveillance data recording events in your home, car and office. That data must be sufficiently detailed to yeild detailed information about what you read, watch, and hear. And thus, what you do.

Second, some will argue that Lessig and his ilk cannot be said to despise or reject property rights in general or copyrights in particular because they support Creative Commons and open-source licensing schemes that are predicated upon copyrights in particular.

This a non sequitur—it’s like saying someone must respect free speech because he supports the speech of those who agree with him. In the case of both property and speech rights, the key question is whether you support the right of others to exercise their right in ways that you disagree with.

The exclusive rights that we grant to property owners and the free-speech rights that we grant in the First Amendment both tend to be very broad. As a result, holders of such rights can exercise them in many ways—including ways that most of us would think unwise. A farmer growing apples could choose to let them rot on her trees. A law professor could chose to play a video that gratuitously mocks other people’s religion.

But in neither case do we grant such broad rights because we want to encourage inefficient or rude behavior. To the contrary: We grant very broad freedom to act because we doubt that we can divine, in advance, through some collective mechanism, what the optimal outcome would be as to every situation that might implicate those rights. We thus conclude that over the long run, we will be more likely to discover truth or efficiency through an ex post process of competition between people who can make different—even clashing—decisions about how to exercise their rights.

This freedom to act also ensures that—at any one moment—some people are exercising their rights inefficiently, in part, because people disagree about what the true or efficient solution is. From a static perspective, these are inefficiencies caused by freedom (as we in the West like to imagine it). From a dynamic perspective, these disagreements are the truth-seeking mechanism that gives systems of speech rights and property rights superior dynamic efficiency. Schumpeter makes this point: “A system—any system, economic or other—that at every given point in time fully utilizes its possibilities to the best advantage may yet in the long run be inferior to a system that does so at no given point in time, because the latter’s failure to do so may be a condition for the level or speed of long-run performance.”

So if the question is whether someone who creates works or writes code should be permitted to administer their works according to a Creative Commons or open-source license, the opinions of others about their wisdom of doing so should be irrelevant: By granting broad exclusive rights that can be waived in whole or in part, we seek to give creators of socially valuable resources broad freedom to disagree about how best to administer them. In other words, if you do think that open source is a superior development method, then the real question is whether you respect the rights of other software developers to disagree and use closed-source development methods.

Indeed, if the test for being “pro-property” is merely whether there are some implementations of property rights that you would support, then even Karl Marx passes. Notwithstanding the call in the Manifesto of the Communist Party for abolishing all property rights, Marx makes clear that the problem is not all property rights, but property rights being administered in a bourgeois manner; the Communists, Marx says, really “intended abolition of bourgeois property.”

posted by Thomas Sydnor @ 12:13 PM |

Link to this Entry | Printer-Friendly | Email a Comment | Post a Comment(2)


Comments

"In other words, if you do think that open source is a superior development method, then the real question is whether you respect the rights of other software developers to disagree and use closed-source development methods."

Don't confuse closed-source and commonly associated restrictive copyright licenses and dubious EULAs - closed-source is possible in the complete absence of copyright.

Actually, I for one have nothing against closed-source development methods in themselves - I just disagree with copyright. I think people should be free to release closed-source binary-only software if they want to, just not to restrict its redistribution post-release. Binaries should not be copyrightable. (I also disagree with anti-reverse-engineering provisions, mind).

We'd have uncopyrighted and uyncopyrightable binary-only software competing with uncopyrighted and uncopyrightable source-provided software in a truly free market. The real question is whether closed-sourcers would be willing to compete against open-sourcers in such a truly free market, stripped of their copyright and patent "protection" [rackets]. What's that? Software users would almost always prefer to have source given the choice, just in case? Yes, that's right. See, open source has that natural advantage in a free market.

Posted by: Spumco at April 30, 2008 7:15 PM

"No, it isn’t. As I use the term here, filtering technologies work like this: They automatically use an algorithm to analyze given files and generate a unique digital identifier that is then automatically checked against a reference database that contains the fingerprints of files not authorized for uploading/transmission. If there is a match, the upload or transmission is blocked, if not, it completes, and the algorithm moves on to the next file. Nothing in this process requires the system retain any information, or communicate it to any rightsholder, or service-provider/ISP."

Hmmm. well no one would ever deny you the right to run what ever type of filtering technology you want to run on your computer. So run all the filtering technology you want.

If, as I suspect, you want to force me to run filtering software on my own computer, you have just crossed the line into fascism. You just don't understand that freedom means freedom.

To say then that:

"For users of such programs, any alleged concerns about filtering look much like thinly veiled excuses for piracy."

I could respond like this:

Then, I suppose that a desire for privacy is just a thinly veiled excuse for breaking the law?

But I would rather simply note this:

Amendment 4
The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized.

"So if the question is whether someone who creates works or writes code should be permitted to administer their works according to a Creative Commons or open-source license, the opinions of others about their wisdom of doing so should be irrelevant: By granting broad exclusive rights that can be waived in whole or in part, we seek to give creators of socially valuable resources broad freedom to disagree about how best to administer them. In other words, if you do think that open source is a superior development method, then the real question is whether you respect the rights of other software developers to disagree and use closed-source development methods."

But this is exactly the opposite of what is observed, that is: those who oppose free software are constantly erecting legal barriers to the use and production of such software, i.e. DMCA, software patents.

In any case those who produce proprietary software seem to think they are entitled to a market for their goods. That is not at all what a market is about. Just read Schumpeter on creative destruction.


Posted by: enigma_foundry at May 7, 2008 12:20 AM








 
IPcentral WebLog

Blog Main

IPcentral Blogosphere Archives

Search the Blog

Recent Posts
  - The "Loud Minority" in the FOSS Movement
- "Free" Culture: It's Not What "We in the West" Might Imagine
- Linux Goes Corporate
- Bruce Everiss on video game piracy
- Reality Settles in on FOSS
- Red Hat Gets Realistic
- FOSS Adoption and Consumer Welfare
- Isn’t It Ironic: TechCrunch Blames the Music Industry for the Dangerous Ideas of Lessig and the Free Culture Movement
- Commercial Open Source Firms Get VC Money
- Differing Estimates of Patent Litigation Costs
Archives by Month
  - April 2008
- March 2008
- February 2008
- January 2008
  - (see all)
Archives by Subject
  - Academia
- Access: Commons, Fair Use, Orphan Works, Public Domain
- Accounting
- Analog Holes
- Antitrust
- Art
- Aspen
- Big Tent
- Biotech
- Books
- Comments from Readers
- Counterfeit
- Digital Americas
- Digital Europe
- Digital Europe 2006
- DMCA
- DRM & Watermarks, etc.
- Economics, Game Theory & Public Choice
- Enforcement & Remedies
- Free Culture Movement
- Games
- General
- Infrastructure
- International
- Internet: P2P, Search Engines...
- Legislation and Legislators
- Liberty and IP
- Markets: Business, Investment & Innovation
- Media: Video, Music...
- Patents
- Pharma
- Physical Property
- Prices, Terms, and Licensing
- Privacy and Security
- Radio
- Software
- Spectrum & Wireless
- Standards
- Supreme Court
- Tax-Funded IP
- Telecom
- Theft of Service
- Universities
Links
 

Site Feed

  - Atom
- RSS 1.0
- RSS 2.0
We welcome comments by email - look for a link to the author's email address in the byline of each post. Please let us know if we may publish your remarks.


 
Home Page