4 ms·

Yes, people seriously underestimate the damage done by carrying over the near-absolute monopolies granted by copyright, which were originally intended for super

Yes, people seriously underestimate the damage done by carrying over the near-absolute monopolies granted by copyright, which were originally intended for superfluous creative works. A good compromise may be that software is only eligible for legal protections like copyright if it's source is registered with the Copyright Office, and then the scope of that copyright would limit the commercial resell for 10 years, but would not limit individual or hobbyist use or distribution. Whatever we do, with core components of basically everything falling under copyright protection due to software, we badly need to revise the law. There is a large body of law where we have just sloppily slapped a physical metaphor on top of the relevant technology and pretended like that was OK. We need to acknowledge that there are differences and that we need a first-class body of law to address these issues, not just loosely applied law that never could have anticipated the world as it is today. One example: copies of content kept in RAM qualify as infringing copies under the Copyright Act. Judges have been lamenting that in their decisions since the first one, but they feel the law must be interpreted that way. This has a lot of complicated consequences, and it's just a single example of how our technology law is badly damaged and needs repair. The biggest reason we don't get this sorely-needed legal renovation is that big companies don't want to even the playing field. They like using the law to bully small innovators.

jasonkostempski 10y ago
Just a thought experiment: what if copyright could only be assigned to individuals and not companies?
- Arizhel 10y ago
  I'd like to do the same with patents.
tzs 10y ago
> Yes, people seriously underestimate the damage done by carrying over the near-absolute monopolies granted by copyright, which were originally intended for superfluous creative works. Explain the use of "superfluous" in that sentence, please. > One example: copies of content kept in RAM qualify as infringing copies under the Copyright Act. Judges have been lamenting that in their decisions since the first one, but they feel the law must be interpreted that way. This has a lot of complicated consequences, and it's just a single example of how our technology law is badly damaged and needs repair. Can you give some examples of judges lamenting that? I don't see why you think this particular thing needs repair. Generally programmers and engineers do consider a program loaded into RAM to be a copy of the program. Copyright law uses a fairly simple, common sense definition of "copy" which generally includes things that most people would consider copies. So, we end up with programs in RAM being copies of the program on disk from which they were loaded. But we don't want running a program that you have a legitimate authorized copy of on your disk to require extra permission from the copyright owner, so we need to find a way to make doing so not count as a violation of the copyright owner's copying right. There are two ways to do that. One way would be to change the definition of "copy" so as to not include it. Another way would be to add a specific limitation on the copyright owner's exclusive rights that says they are not applicable in this case. The first approach, changing the definition of "copy", is bad. First of all, it makes the legal term "copy" further diverge from the English term "copy", and in this particular case from what programmers and engineers mean when they say "copy". Second, nearly everything in copyright law depends on knowing what a copy is, so adding complexity to the definition to deal with one special case complicates almost everything. The second approach addresses the particular problem at hand, and does not leak complexity into other parts of the law. We went with the second approach. See 17 USC 117, "Limitations on exclusive rights: Computer programs" for details. That's the approach for most special cases in the Copyright Act. Section 101 gives broad definitions, usually reasonably well aligned to the common understanding of the terms. Section 106 gives the copyright owner certain exclusive rights. Then there are a bunch of sections that reign in those rights somewhat, for example with fair use in section 107, library use in 108, and first sale in 109. If we tried to handle all of that by diddling with the definition of "copy" to make doing those things not involve copies the law would end up ridiculously complicated.
- cookiecaper 10y ago
  Early disclaimer: IANAL. >Explain the use of "superfluous" in that sentence, please. Meaning works that were thought to enhance culture, or, as the Constitution puts it "Science and the Useful Arts", but which were not strictly necessary for anything to function. Patents were the separate mechanism of intellectual property intended to protect inventions. Patents are correspondingly much weaker and required a disclosure of the invention's mechanisms. In cyberspace, unfortunately, all of our inventions qualify for copyright (as well as patents) because they're expressed through the "creative work" of software code. This has left us in a situation where a critical component that we depend on every day may stop functioning, and there's nothing anyone can do about it, since practically just thinking about something is a copyright violation these days. We should update the law so that software is eligible for IP protection only when its source code has been published, similar to the mechanism in place for patents, which requires the mechanisms of the invention to be disclosed. >Can you give some examples of judges lamenting that? You're right that I overstated the critical reception of the RAM copy doctrine. I was referring to this section of the judgment which put it forth in MAI v. Peak: >However, it is generally accepted that the loading of software into a computer constitutes the creation of a copy under the Copyright Act. We recognize that these authorities are somewhat troubling since they do not specify that a copy is created regardless of whether the software is loaded into the RAM, the hard disk or the read only memory (“ROM”). However, since we find that the copy created in the RAM can be “perceived, reproduced, or otherwise communicated,” we hold that the loading of software into the RAM creates a copy under the Copyright Act. The Court acknowledges that the concept of when the copy materializes was not well established and calls this "somewhat troubling", but eventually determines that due to the possibility of the content being "communicated" whilst stored in RAM, it should qualify as a copy. For background, MAI v. Peak was a case about whether a technician had made an infringing copy by running a program installed on a user's PC in the course of maintenance. The Court ruled that since loading a program into RAM is a copy, he had created an infringing copy. The exception added for computer programs arose from this case, but did not address the RAM copy doctrine. It makes an explicit exemption for "(c)Machine Maintenance or Repair." only. If you're not maintaining or repairing your friend's machine, but you still load up a game he's installed, you've technically made an infringing copy, just as this computer tech had, because you are not doing it for "maintenance or repair". The RAM copy doctrine is inherently offensive. It makes equal sense to say that the copy created in your brain from the image reflected onto your retinas is an infringing copy, and there's actually a strong case that the image in your human memory is an infringing copy because it is stored in a fixed medium that can be communicated (after proper transformation, i.e., conversion into a sketch; just as a RAM copy requires transformation from numbers-in-memory into something that is displayed on a screen). The RAM copy is no different, except that a computer's "eyes" are not respected; what should matter is what happens with the copies that exist outside of RAM in an actually fixed or tangible form, the end result of the transitory memory "copy". Neither RAM nor optical nor memorial copies should qualify for infringement on their own due to their transitory nature; you can even make this argument under current law, which requires copies to be fixed and permanent. A clarification is badly needed, correcting the Ninth Circuit's poor judgment in this case. The real-world outcome is that the precedent set in Feist v. Rural Telco is no longer effective in cyberspace. It's impossible to open a web page and copy the bare, uncopyrightable facts out of it, because the necessary pre-requisite of downloading the exact compilation of facts, which is copyrightable, creates an infringing copy, which you could be successfully sued over even if your end product was not sufficiently derivative to be a derived work under copyright law, and even if the "white pages" never touch your disk; just using your computer to look at/read them without consent is illegal, since the act of loading content into a computer creates a copy. Another contrived example under RAM copy doctrine: if you've downloaded a song illegally, you are not on the hook for only the copy on your hard disk, but the number of plays, since each one is a distinct infringing copy created by your computer loading the music into its memory repeatedly. Follow-up question: if the program loads and unloads an unlicensed resource several times in the course of its operation, is each instance a new infringing copy? There have been several scholarly articles written by actually qualified people (I'm not a lawyer) about how to resolve the issues incumbent in the RAM copy doctrine, so they can cover it. But this is just one example of several legal problems limiting participation and competition in the virtual market. We need to add law to fix this and similar problems.

jasonkostempski 10y ago

Just a thought experiment: what if copyright could only be assigned to individuals and not companies?

Arizhel 10y ago
I'd like to do the same with patents.

tzs 10y ago

> Yes, people seriously underestimate the damage done by carrying over the near-absolute monopolies granted by copyright, which were originally intended for superfluous creative works. Explain the use of "superfluous" in that sentence, please. > One example: copies of content kept in RAM qualify as infringing copies under the Copyright Act. Judges have been lamenting that in their decisions since the first one, but they feel the law must be interpreted that way. This has a lot of complicated consequences, and it's just a single example of how our technology law is badly damaged and needs repair. Can you give some examples of judges lamenting that? I don't see why you think this particular thing needs repair. Generally programmers and engineers do consider a program loaded into RAM to be a copy of the program. Copyright law uses a fairly simple, common sense definition of "copy" which generally includes things that most people would consider copies. So, we end up with programs in RAM being copies of the program on disk from which they were loaded. But we don't want running a program that you have a legitimate authorized copy of on your disk to require extra permission from the copyright owner, so we need to find a way to make doing so not count as a violation of the copyright owner's copying right. There are two ways to do that. One way would be to change the definition of "copy" so as to not include it. Another way would be to add a specific limitation on the copyright owner's exclusive rights that says they are not applicable in this case. The first approach, changing the definition of "copy", is bad. First of all, it makes the legal term "copy" further diverge from the English term "copy", and in this particular case from what programmers and engineers mean when they say "copy". Second, nearly everything in copyright law depends on knowing what a copy is, so adding complexity to the definition to deal with one special case complicates almost everything. The second approach addresses the particular problem at hand, and does not leak complexity into other parts of the law. We went with the second approach. See 17 USC 117, "Limitations on exclusive rights: Computer programs" for details. That's the approach for most special cases in the Copyright Act. Section 101 gives broad definitions, usually reasonably well aligned to the common understanding of the terms. Section 106 gives the copyright owner certain exclusive rights. Then there are a bunch of sections that reign in those rights somewhat, for example with fair use in section 107, library use in 108, and first sale in 109. If we tried to handle all of that by diddling with the definition of "copy" to make doing those things not involve copies the law would end up ridiculously complicated.

cookiecaper 10y ago
Early disclaimer: IANAL. >Explain the use of "superfluous" in that sentence, please. Meaning works that were thought to enhance culture, or, as the Constitution puts it "Science and the Useful Arts", but which were not strictly necessary for anything to function. Patents were the separate mechanism of intellectual property intended to protect inventions. Patents are correspondingly much weaker and required a disclosure of the invention's mechanisms. In cyberspace, unfortunately, all of our inventions qualify for copyright (as well as patents) because they're expressed through the "creative work" of software code. This has left us in a situation where a critical component that we depend on every day may stop functioning, and there's nothing anyone can do about it, since practically just thinking about something is a copyright violation these days. We should update the law so that software is eligible for IP protection only when its source code has been published, similar to the mechanism in place for patents, which requires the mechanisms of the invention to be disclosed. >Can you give some examples of judges lamenting that? You're right that I overstated the critical reception of the RAM copy doctrine. I was referring to this section of the judgment which put it forth in MAI v. Peak: >However, it is generally accepted that the loading of software into a computer constitutes the creation of a copy under the Copyright Act. We recognize that these authorities are somewhat troubling since they do not specify that a copy is created regardless of whether the software is loaded into the RAM, the hard disk or the read only memory (“ROM”). However, since we find that the copy created in the RAM can be “perceived, reproduced, or otherwise communicated,” we hold that the loading of software into the RAM creates a copy under the Copyright Act. The Court acknowledges that the concept of when the copy materializes was not well established and calls this "somewhat troubling", but eventually determines that due to the possibility of the content being "communicated" whilst stored in RAM, it should qualify as a copy. For background, MAI v. Peak was a case about whether a technician had made an infringing copy by running a program installed on a user's PC in the course of maintenance. The Court ruled that since loading a program into RAM is a copy, he had created an infringing copy. The exception added for computer programs arose from this case, but did not address the RAM copy doctrine. It makes an explicit exemption for "(c)Machine Maintenance or Repair." only. If you're not maintaining or repairing your friend's machine, but you still load up a game he's installed, you've technically made an infringing copy, just as this computer tech had, because you are not doing it for "maintenance or repair". The RAM copy doctrine is inherently offensive. It makes equal sense to say that the copy created in your brain from the image reflected onto your retinas is an infringing copy, and there's actually a strong case that the image in your human memory is an infringing copy because it is stored in a fixed medium that can be communicated (after proper transformation, i.e., conversion into a sketch; just as a RAM copy requires transformation from numbers-in-memory into something that is displayed on a screen). The RAM copy is no different, except that a computer's "eyes" are not respected; what should matter is what happens with the copies that exist outside of RAM in an actually fixed or tangible form, the end result of the transitory memory "copy". Neither RAM nor optical nor memorial copies should qualify for infringement on their own due to their transitory nature; you can even make this argument under current law, which requires copies to be fixed and permanent. A clarification is badly needed, correcting the Ninth Circuit's poor judgment in this case. The real-world outcome is that the precedent set in Feist v. Rural Telco is no longer effective in cyberspace. It's impossible to open a web page and copy the bare, uncopyrightable facts out of it, because the necessary pre-requisite of downloading the exact compilation of facts, which is copyrightable, creates an infringing copy, which you could be successfully sued over even if your end product was not sufficiently derivative to be a derived work under copyright law, and even if the "white pages" never touch your disk; just using your computer to look at/read them without consent is illegal, since the act of loading content into a computer creates a copy. Another contrived example under RAM copy doctrine: if you've downloaded a song illegally, you are not on the hook for only the copy on your hard disk, but the number of plays, since each one is a distinct infringing copy created by your computer loading the music into its memory repeatedly. Follow-up question: if the program loads and unloads an unlicensed resource several times in the course of its operation, is each instance a new infringing copy? There have been several scholarly articles written by actually qualified people (I'm not a lawyer) about how to resolve the issues incumbent in the RAM copy doctrine, so they can cover it. But this is just one example of several legal problems limiting participation and competition in the virtual market. We need to add law to fix this and similar problems.