LWN.net Logo

Relicensing and rebasing LibreOffice

Relicensing and rebasing LibreOffice

Posted Jun 2, 2012 1:55 UTC (Sat) by giraffedata (subscriber, #1954)
In reply to: Relicensing and rebasing LibreOffice by dlang
Parent article: Relicensing and rebasing LibreOffice

If it is legal for the final recipient to have the bits, does it really matter the exact method that that user got the bits?

If you mean legally, than it pretty clearly does matter. It matters mainly because copyright law is based on traditional hardware copying, and legislators have been slow to adapt it to the complex world of software.

This causes some crazy results, but a) courts are bound by law even if it's crazy; and b) it's hard to come up with laws that avoid the crazy outcomes without also avoiding the intended ones. It's a complicated area.

I read about a company that runs a building with hundreds of little antennas in it, providing a separate feed of TV broadcasts to each of its customers. This was because some smart lawyers determined that would be legal where simply splitting the signal from one antenna would be a copyright violation.

I also read about a service where customers make fair use copies of their music CDs and transmit the data to a company which stores the data for backup and other fair uses. I suppose the company kept a thousand identical copies of the same album because smart lawyers determined that was legal where having one shared copy isn't. And I wonder if it makes a difference if they store them in a modern compressing storage system that stores those thousand copies with pointers to the same area on a disk platter.

But you don't have to get that weird to see copyright law doing the wrong thing in an individual case. Just look at the simple case of a teenager copying a music album that he absolutely would not have bought himself. Nothing really wrong with that, but clearly illegal.

Worse: a company spends $20K independently developing some code that someone else already wrote, because that other person refused to license it. What a waste.

But all good rules come with collateral damage.


(Log in to post comments)

Relicensing and rebasing LibreOffice

Posted Jun 4, 2012 12:46 UTC (Mon) by nix (subscriber, #2304) [Link]

Of course, all bad rules *also* come with collateral damage. You cannot use the presence of unintended side-effects to argue that a rule is good.

Relicensing and rebasing LibreOffice

Posted Jun 4, 2012 15:55 UTC (Mon) by giraffedata (subscriber, #1954) [Link]

You cannot use the presence of unintended side-effects to argue that a rule is good

Well nobody could argue with that, but how is that germane to the current discussion? Did someone say copyright law is good because it sometimes does the wrong thing?

By the way, the term "unintended side effect" may be ambiguous. To a lot of people, that refers to something unanticipated, but it could also be something that was fully expected, but just not a goal. Here, I believe legislators and judges were fully briefed on most of copyright law's shortcomings and accepted them as a tradeoff, so in a sense they intended them to exist.

Totally Off-topic!

Posted Jun 4, 2012 17:18 UTC (Mon) by hummassa (subscriber, #307) [Link]

BWAHAHAHAHAHAH!

> Here, I believe legislators and judges were fully briefed on most of copyright law's shortcomings and accepted them as a tradeoff, so in a sense they intended them to exist.

Sorry for the OT post, but this made me LOL and all my coworkers are looking at me right now.

Disclaimer: I work at a state legislative house, and for the last fifteen years I have been married to a district attorney.

Laws are like programs... but the "machine" that will interpret those programs are the lawyers, attorneys, juries, judges, and justices. And each machine interpret the program as they damn well please. And what we call "The Law" is actually some kind of "mean value" of the many runnings of the program (i. e., the program self-modifies each time it is "run"). And for a single execution of the program (a "lawsuit"), the result always depend on when and where the program is being run.

So, no: most probably nobody has briefed nobody on those shortcomings, and probably nobody even saw they existed.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds