[Smaug] FW: EFF alert on SSSCA

David A. Gatwood dgatwood at gatwood.net
Mon, 11 Mar 2002 11:24:43 -0800 (PST)


On Mon, 11 Mar 2002, John Callaway wrote:

>    I hope you're right about copy protection not being commercially viable.  
> But recorded music and movies represents a whole lot more money than Apple ][ 
> software ever did!  The RIAA already killed one potential format, DAT 
> (digital audio tape) in the '80s and they're doing their damndest to kill 
> .mp3 now and replace it with a "secure" format like W*nd*ws Media.

Actually, they didn't kill DAT.  The hardware manufacturers proved with
DCC (Digital Compact Cassette) that the public won't buy a digital tape
medium en masses.  The copy protection in DAT was really irrelevant, since
CD players didn't have digital output to dump to DAT anyway.  DAT still
hasn't come down to the price point where it's useful for the masses, and
even at its introduction, it was cheaper to use a computer, if you ignore
the cost of disk storage.  DAT was dead from the beginning.


>    Regarding code as speech, you claim that code deserves to be recognized as 
> "an artistic work," but then go on to say that there is exactly one way to 
> code a given problem (at sufficiently small granularity).  This seems like a 
> bit of a contradiction to me.  

An artistic work as a whole, but algorithmic at a low level.  The final
work is an artistic work.  The individual pieces of it are not, in much
the same way that the layout of the newspaper is an artistic work, but the
news itself is not.  Very subtle point.


> Since I write software for a living, I prefer 
> the artistic interpretation!  And the courts traditionally have granted any 
> type of speech/expression that's recognized by society as an art form greater 
> protection from censorship.

That is true.  However, preventing use of technology to duplicate music
isn't censorship.  It's preventing the use of material in violation of the
law.  If code were speech, the burden of proof would be on the record
industry to prove the potential for damage and to plead their case if they
wanted to prevent something from being released.

However, once something is released, it is trivial to require a retraction
if printed material is libelous, incites illegal activity, etc.  In short,
it's basically status quo.  In this regard, it's already being treated as
speech.  I haven't seen anyone ever get an injunction on the initial
release of an open source project.  The day that happens, there would be
benefit to treating code as speech.


>    As far as "time, place, and manner" restrictions, I'm personally a staunch 
> libertarian, and don't believe in restricting expression except for the most 
> narrow, compelling reasons (incitement to riot, etc).  In my personal utopia 
> there would be no movie rating system (which is actually extra-governmental 
> as it exists now), and porn stores would be welcome to open across the street 
> from schools.

Good luck convincing the Republican administration....  Heck, good luck
convincing those goofballs about much of anything.  :-)


>    Source code can be published in books and read aloud.  If that's not 
> speech I don't know what is.  I don't think there's really a choice here.  
> And first amemdment protections are, in my opinion, the best way to prevent 
> ugly spectacles like the Sklyarov, Felten, and 2600 cases.

They Skylarov case was an embarrassment.  It was an attempt to apply U.S.
laws to a foreign national, which is illegal to begin with....  I could
spend a week just ripping our brain-damaged court system a new one over
it....

First amendment protections may help some of the most egregious
bastardizations of the law, but they definitely add at least as many
problems as they solve.  My favorite thing would be the "borrowing small
pieces of code" thing.  Some other issues would be the right to quote
arbitrary amounts of code for criticism.  If you're running a closed
source project, all of a sudden someone leaks a piece of code and the
media can then legally print the whole thing, even if it's your entire
project, so long as they add comments to the code.

Of course, these problems really only hurt closed source programming, but
they can hit pretty hard if appropriate restrictions aren't made.  It
would require a whole new body of law that would evolve over time to set
restrictions on the use of such speech.  It's a major undertaking, and
something not to be taken lightly.  Maybe it will happen, maybe it won't.
The point really is that it opens up a can of worms that's at least as
big, and it's likely to take years before things settle down to something
resembling common sense.  ;-)


Later,
David

---------------------------------------------------------------------
                    Check out my weekly web comic:
                     http://www.techmagazine.org