Slashdot Mirror


German Court Convicts Skype For Breaching GPL

terber writes "A German court has once again upheld the GPLv2 and convicted Skype (based in Luxembourg) of violating the GPL by selling the Linux-based VoIP phone 'SMCWSKP 100' without proper source code access. (Original is in German, link is a Google translation.) Skype later added a flyer to the phones' packaging giving a URL where the sources could be obtained; but the court found this insufficient and in breach of GPL section 3. The plaintiff was once again Netfilter developer Harald Welte, who runs gpl-violations.org. The decision is available in German at www.ifross.de (Google translation here)."

309 comments

  1. Damn by Anonymous Coward · · Score: 4, Funny

    What a bunch of GPL Nazis.

    1. Re:Damn by MontyApollo · · Score: 2, Funny

      >>What a bunch of GPL Nazis.

      Sorry, I laughed.

    2. Re:Damn by HermMunster · · Score: 1

      It's not a conviction unless a contract/license violation is considered a crime in Germany. They simply lost the civil case and were found in violation. That's pretty much it. Hopefully we'll see more lawsuits against other companies such as TiVO.

      Hopefully there's some monetary reward in this and that it will teach Skype and others a big lesson.

      --
      You can lead a man with reason but you can't make him think.
    3. Re:Damn by Anonymous Coward · · Score: 0, Insightful

      When the niggers raped the women I remained silent because I wasn't a woman
      When the niggers raped the children I remained silent because I wasn't a child
      When the niggers raped the other niggers I remained silent because I wasn't a nigger
      When the niggers raped me, I couldn't speak because there were 4 black cocks in my mouth.

      Ow, my ass hurts and my jaw is broken.

    4. Re:Damn by Anonymous Coward · · Score: 1, Insightful

      "Hopefully there's some monetary reward in this and that it will teach Skype and others a big lesson."

      Sadly, I'm afraid, the only lesson they will learn is to not use Linux.

    5. Re:Damn by s_p_oneil · · Score: 2

      Yes, and that lesson is to use BSD.

    6. Re:Damn by mrsteveman1 · · Score: 1

      I wish that were a real option for anyone but highly motivated private companies.

      Anyone who just wants to USE one of these *nix systems is pretty much tied to Linux because thats where all the (working) drivers are for commodity hardware. And it's been my experience that as funny as this sounds, Linux is fairly user friendly as Unix clones go. Compared to Solaris, Linux is incredibly easy to use, and somewhat easier than Freebsd.

      Hopefully this will change and FreeBSD or similar development will advance, then Linux won't be the only real option for lots of cases.

    7. Re:Damn by s_p_oneil · · Score: 1

      I don't think BSD is less user-friendly than Linux. The installs are a lot worse (except for PC-BSD), but aside from that, I don't see a big difference in user-friendliness.

      I know BSD is behind Linux in drivers, but on all the PC's I've tried it on, it hasn't been any worse than Linux. Not even Ubuntu 7.04 works with my wifi card, which is a Gigabyte card with an rt2500 chipset, and has supposedly been supported by Linux for years.

    8. Re:Damn by xSauronx · · Score: 1

      i had an rt73 based adapter that would work on open networks, and with WEP, and naught else. i now have a thinkpad t40 with an intel 802.11b adapter and while it works with WPA2, its iffy.

      ive had daemonlog and syslog grow to almost 2gb each when the adapter was giving me a problem (they were limited by my / disk size) and it wont work with WPA2 with full ascii keys, just with alphanumeric keys. its better than WEP, but given the age and the support intel is supposed to have given for this....im not impressed. im glad it works, but i shouldnt have to be glad.

      hell, i shouldnt have to be impressed. its just aggravating.

      --
      By and large, language is a tool for concealing the truth. -- George Carlin
    9. Re:Damn by ravenshrike · · Score: 4, Interesting

      Let me get this straight. It's a net based phone application, which you need access to the internet to be able to use anyway, but yet an url where you can find the source code for the relevant part of the app isn't sufficient? Can someone help explain the insanity here, or am I not seeing something blindingly obvious?

    10. Re:Damn by Anonymous Coward · · Score: 0

      Can someone help explain the insanity here, or am I not seeing something blindingly obvious?

      The blindingly obvious is that the GPL, in particular section 3, doesn't allow you to do that. You are not in compliance with the license. There isn't a "Or you know, whatever. Try your hardest I guess." clause in there for lazy companies.

    11. Re:Damn by josephdrivein · · Score: 1

      I disagree. The lesson is: whatever software you use in your product, respect its license.

      Using BSD would make it easier to respect the license. Anyway complying with sect.3 of the GPL wasn't hard and the apparently didn't even try to.

      If you don't want to (or simply don't care), use BSD-licensed code or write your own code.

    12. Re:Damn by Tony+Hoyle · · Score: 1

      It does seem odd. To force people to actually distribute source of everything they use rather than simply point to it would be a huge burden.. I'd probably need a 1Tb fileserver!

    13. Re:Damn by Anonymous Coward · · Score: 3, Informative

      Section 6:

      "You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

      a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange."

      The thing is that Skype sold a physical produt (a phone), and according to the wording of the GPL the code needs to be distributed on a durable physical medium with this product.

    14. Re:Damn by s_p_oneil · · Score: 1

      That makes sense to me unless the software you're using is an OS, and you're planning to use it for an appliance that has closed source. An OS has an awful lot of pieces, each of which can be under a different version of a different license, and it may cost a company quite a bit to keep track of it all and ensure they're in compliance. If you have a sizable team of developers, the chances of someone forgetting something and changing the wrong code will be high. Some companies end up hiring a lawyer to cut through the confusion and help make sure that they comply. This doesn't just make BSD easier to comply with, it makes it cheaper to comply with, as well as safer.

      Another point to mention is that closed-source developers would benefit more from BSD growing than they would from Linux growing, and every closed source developer that chooses it helps it grow.

    15. Re:Damn by hawkinspeter · · Score: 1

      Surely if you make a mistake and forget to publish a piece of source code, you get the chance to rectify that mistake before the case goes to court. All it would take would be for the guilty party to upload a copy of the relevant source code onto a web site and then they would be compliant. What's so difficult about that?

      --
      You're a temporary arrangement of matter sliding towards oblivion in a cold, uncaring universe
    16. Re:Damn by maz2331 · · Score: 1

      GPL allows you to give a link to the source, BUT the link has to be on a system that you control. It's part of the "licensing fee" of the code. When it says "you" have to make the source available, it means "you", not "you can use someone else's system and bandwidth".

    17. Re:Damn by s_p_oneil · · Score: 1

      It's difficult if you can't publish those changes. They may include proprietary code you want to keep from your competitors or calls to a closed-source third-party library. Depending on the design, it may be a real pain to move those changes/calls somewhere safe while providing the same functionality.

      Not all developers are good developers, most developers don't want to have to figure out all the legal ins and outs of the tools/libraries they use, and even those that do make mistakes. On top of that, some are malicious, and may go out of their way to violate the GPL and hide it, using it as "insurance" in case they get fired or laid-off.

      I know the GPL defenders aren't out there to put companies out of business or take money from them in law suits like patent trolls. But from the perspective of a non-technical boss who doesn't fully understand everything that can go wrong, it's safer to avoid creating a Linux-based appliance if he wants to keep his product closed-source. The larger the project and development team is, the safer you'll be avoiding it.

    18. Re:Damn by Anonymous Coward · · Score: 0

      convey = gpl3 = just came out = not what this is about

        3. You may copy and distribute the Program (or a work based on it,
      under Section 2) in object code or executable form under the terms of
      Sections 1 and 2 above provided that you also do one of the following:

          a) Accompany it with the complete corresponding machine-readable
          source code, which must be distributed under the terms of Sections
          1 and 2 above on a medium customarily used for software
          interchange; or,

          b) Accompany it with a written offer, valid for at least three
          years, to give any third party, for a charge no more than your
          cost of physically performing source distribution, a complete
          machine-readable copy of the corresponding source code, to be
          distributed under the terms of Sections 1 and 2 above on a medium
          customarily used for software interchange; or,

          c) Accompany it with the information you received as to the offer
          to distribute corresponding source code.  (This alternative is
          allowed only for noncommercial distribution and only if you
          received the program in object code or executable form with such
          an offer, in accord with Subsection b above.)

      The source code for a work means the preferred form of the work for
      making modifications to it.  For an executable work, complete source
      code means all the source code for all modules it contains, plus any
      associated interface definition files, plus the scripts used to
      control compilation and installation of the executable.  However, as a
      special exception, the source code distributed need not include
      anything that is normally distributed (in either source or binary
      form) with the major components (compiler, kernel, and so on) of the
      operating system on which the executable runs, unless that component
      itself accompanies the executable.

      If distribution of executable or object code is made by offering
      access to copy from a designated place, then offering equivalent
      access to copy the source code from the same place counts as
      distribution of the source code, even though third parties are not
      compelled to copy the source along with the object code.

    19. Re:Damn by ardle · · Score: 1

      Maybe the need to save bandwidth might encourage developers not to copy-n-paste code. Wishful thinking ;-)
      The cool thing about the GPL is that it forces the developer (entity) to put their name to the code they supply (and, by extension, the product). This increases the likelihood of good quality code being used to build the product.
      It's amazing what people do with code when they think nobody's going to see it!

    20. Re:Damn by slowdive1979 · · Score: 1
      Check out the FAQ: http://www.fsf.org/licensing/licenses/gpl-faq.html #DistributeWithSourceOnInternet.

      Q: I want to distribute binaries via physical media without accompanying sources. Can I provide source code by FTP instead of by mail order?

      A: You're supposed to provide the source code by mail-order on a physical medium, if someone orders it. You are welcome to offer people a way to copy the corresponding source code by FTP, in addition to the mail-order option, but FTP access to the source is not sufficient to satisfy section 3 of the GPL.

      When a user orders the source, you have to make sure to get the source to that user. If a particular user can conveniently get the source from you by anonymous FTP, fine--that does the job. But not every user can do such a download. The rest of the users are just as entitled to get the source code from you, which means you must be prepared to send it to them by post.

      If the FTP access is convenient enough, perhaps no one will choose to mail-order a copy. If so, you will never have to ship one. But you cannot assume that.

      Of course, it's easiest to just send the source with the binary in the first place.

      If you distribute binaries via FTP, you should distribute source via FTP.

    21. Re:Damn by houghi · · Score: 1

      Netbased does not mean that you need a computer. It means that you need an internet connection

      --
      Don't fight for your country, if your country does not fight for you.
    22. Re:Damn by Ohreally_factor · · Score: 1

      I love it when religious zealots mod me down. It's further proof that they cannot address facts. Instead they use their mod points, call names, repeat the same logical fallacies ad naseum, misrepresent the facts, resort to discredited rhetorical tactics, or pull out the old story of "RMS and the Print Driver", as if that were the day that God revealed The Truth to RMS and the Spirit of The GPL entered into him.

      For the record, GPL 2 is a great license. OSS is a great methodology. Just leave the religion and spirituality out of it please. If I wanted that, I'd go to church or temple or a mosque or just get drunk and dance naked on the street corner under the full moon.

      --
      It's not offtopic, dumbass. It's orthogonal.
    23. Re:Damn by fuliginous · · Score: 1

      And the reason so many developers choose to put time into drivers for Linux could be the GPL, because they don't want free loading companies using without paying.

      I only ever dual license. GPL or you can pay me for favorable terms.

  2. Correct terminology by Akaihiryuu · · Score: 5, Informative

    Noone would be convicted of "breaching the GPL". The GPL is not an EULA. If you violate the terms of the GPL, you are (re)distributing without a license permitting you to do so (since the GPL, which you violated, is the only thing that gives you permission to do so), which is a copyright violation, not a GPL violation. I wish articles would get the specifics right.

    1. Re:Correct terminology by ikegami · · Score: 3, Insightful

      You said the GPL was violated in a post trying to explain why it's Copyright and not the GPL that was violated.

    2. Re:Correct terminology by Mr.+Underbridge · · Score: 4, Funny

      Noone would be convicted of "breaching the GPL". The GPL is not an EULA. If you violate the terms of the GPL, you are (re)distributing without a license permitting you to do so (since the GPL, which you violated, is the only thing that gives you permission to do so), which is a copyright violation, not a GPL violation. I wish articles would get the specifics right.

      You win today's "Pedant of the day award." Look for your certificate in the mail.

    3. Re:Correct terminology by Akaihiryuu · · Score: 4, Insightful

      You *can* violate the terms of the GPL, if you do you lose your rights to distribute (since it is what gives you the rights). However you would not be convicted of doing so. Instead, you would be convicted of distributing without a license in violation of copyright (since you had no license to distribute). It's a technicality I know, but I wish more people would understand the specifics.

    4. Re:Correct terminology by blhack · · Score: 3, Funny

      you get runner up for using the word "pedant".

      but you don't get a certificate. We're kindof assholes like that.

      --
      NewslilySocial News. No lolcats allowed.
    5. Re:Correct terminology by timster · · Score: 5, Insightful

      This is far from pedantry. Using terms suggesting that someone would be convicted or held liable for a "GPL violation" suggests that a court must uphold the GPL as valid for such a lawsuit to be successful. This makes people believe (erroneously) that the GPL is a questionable document that needs to be tested in court.

      On the contrary, a standard legal action against someone not in compliance with the terms of the GPL would be a simple copyright infringement case; the onus is on the defendant to show that they had a valid license (and met its terms).

      --
      I have seen the future, and it is inconvenient.
    6. Re:Correct terminology by mrchaotica · · Score: 5, Insightful

      Hey, we're having a legal discussion here -- pedantry is necessary!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    7. Re:Correct terminology by seebs · · Score: 1

      I think licensing is more complicated than that. If they point out that you were giving the software away, and let people copy it, then you do have to establish that you're allowed to impose conditions like this -- and a court could conceivably disagree.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    8. Re:Correct terminology by Linker3000 · · Score: 2, Insightful

      No, if you are having a legal discussion, stupidly large fees are usually necessary.

      --
      AT&ROFLMAO
    9. Re:Correct terminology by AKAImBatman · · Score: 5, Insightful

      Using terms suggesting that someone would be convicted or held liable for a "GPL violation" suggests that a court must uphold the GPL as valid for such a lawsuit to be successful.

      The court must "test" the GPL if the defendant claims that he accepted the terms. At that point the judge will attempt to decide whether the defendant did indeed keep up his half of the bargain, potentially restricting the power of the GPL agreement where local laws say otherwise.

      This makes people believe (erroneously) that the GPL is a questionable document that needs to be tested in court.

      The GPL is a fairly air-tight design, but there's nothing erroneous about its need for court testing. A judge can (and will!) strike various parts of the agreement if he finds them to be in conflict with either the law or the intent of the agreement. As a result, it's difficult to legally "prove" that a given type of agreement will hold up in court unless either that same agreement or a similar agreement is tested. The GPL has had sufficient legal testing to show that it will hold up in court.

      If I'm not mistaken, your confusion stems from section 5 of the GPL, which explicitly provides for the fact that no proof of an agreement takes place. According to the GPL, you don't have to accept it to use the software. It falls back on standard copyright law in that case. Thus when an infringer is identified, he faces a double-edged sword. Does he claim that he did not accept the GPL, in which case he's on the hook for copyright infringement? Or does he claim that he did indeed accept the terms of the GPL, in which case he's on the hook for (I'll phrase this carefully just to annoy the "contract vs. license" folks out there :P) "breach of the terms and conditions of the contract"?

      The GPL is an interesting experiment in using a legal loophole as the foundation for a distribution agreement. This case provides further evidence that the concept works as well in practice as it does in legal theory.
    10. Re:Correct terminology by 91degrees · · Score: 1

      You win today's "Pedant of the day award." Look for your certificate in the mail.

      Surely that should be '"Pedant of the Day" award'.

    11. Re:Correct terminology by sumdumass · · Score: 1

      Well, I don't read German so which is true here, Where they convicted of violating copyright or held to be in violation of a contract? If they accepted the GPL and failed to fulfill it's requirement's I would assume it would be the later.

    12. Re:Correct terminology by gad_zuki! · · Score: 2, Interesting

      >which is a copyright violation

      Right, we need to protect copyright at all costs! Maybe insert some DRM to protect us from evil capitalists!!

      I wonder how many slashdotters would agree that the idea to limit copyright to 12 years or so means that linux will be put in the public domain for anyone to do whatever they want, and to hell with the gpl.

      Not trying to troll, but its funny to see people quote copyright law line and verse when it serves them.

    13. Re:Correct terminology by cpt+kangarooski · · Score: 2, Insightful

      It sounds fine to me (though 12 years is a bit long for software -- it might be better to have a shorter term for it, and a longer term for other kinds of works). Linux is not that important in the grand scheme of things. If getting sane copyright laws meant that people could ignore the GPL for a 12 year old version of Linux (but not for any changes that had been introduced since then) I would very happy. Incidentally, how many people do you think are interested in running or making closed forks from Linux as it existed in 1995?

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    14. Re:Correct terminology by Spazmania · · Score: 1

      A judge can (and will!) strike various parts of the agreement if he finds them to be in conflict with either the law or the intent of the agreement.

      No, he won't. The GPL deliberately omits the severability clause commonly found in contracts. This means that if any part of it is contrary to local law, the entire thing is void in that jurisdiction.

      What a judge can do is clarify the contract. "I interpret this clause to mean X, not Y."

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    15. Re:Correct terminology by highspl · · Score: 1

      Necessary? Is it necessary I drink my own urine? No, but I do it anyway, because it's sterile and I like the taste of it.

      --
      It puts the lotion on it's skin, or else it gets the hose again.
    16. Re:Correct terminology by DragonWriter · · Score: 1

      Noone would be convicted of "breaching the GPL". The GPL is not an EULA. If you violate the terms of the GPL, you are (re)distributing without a license permitting you to do so (since the GPL, which you violated, is the only thing that gives you permission to do so), which is a copyright violation, not a GPL violation.


      This is a popular open-source myth, but doesn't seem true under the little US case law applying the GPL (consider Progress Software v. MySQL AB), or under the express terms of the GPLv2 (which make distribution, not merely compliant distribution, an acceptance of the GPL, which seem to constrain action for noncompliant distribution to action for breach of the license, not for a "bare" copyright violation.) It might be an accurate statement of German law, but I see no reason to believe that it is.

      I wish articles would get the specifics right.


      What evidence is that there article got the specifics wrong?
    17. Re:Correct terminology by DragonWriter · · Score: 1

      You *can* violate the terms of the GPL, if you do you lose your rights to distribute (since it is what gives you the rights).


      This may be true (under paragraph 4 of the GPLv2), though its questionable what legal effect it has (since the GPLv2 is an open offer that you receive anew every time you receive software distributed under the license, and which you may accept, under its express terms, simply by redistributing the software.)

      However you would not be convicted of doing so. Instead, you would be convicted of distributing without a license in violation of copyright (since you had no license to distribute).


      Actually, it seems more likely that a breach after (perhaps simultaneously, in the event the initial distribution is noncompliant) acceptance of the GPLv2 (under paragraph 5, by distribution), would be found by the court, that the court would (perhaps) apply the remedy for breach in paragraph 4 which terminates the license from the moment of the breach, and then possibly consider subsequent distribution as a copyright violation.

      OTOH, since under the GPLv2's own terms, the GPL is an offer, and one that one receives the GPL as a new offer everytime one received GPL licensed software, and can be accepted by distribution, its not entirely clear what affect termination has (certainly, the FSF has argued in various fora for it to constitute a permanent ban at least as regards the software improperly distributed, and providing the copyright holder doesn't "forgive" the past breach, but I don't think there is any case law supporting that view, and it is at least arguably contrary to the plain language of the license.)

      Certainly, the main case I've seen on the issue (Progress Software v. MySQL AB) approached the issue from the perspective of a GPL breach not a "bare" copyright violation as MySQL's cause of action, though it never reached (before settlement) whether there was a breach and what legal effect the breach had and what remedies were available.
    18. Re:Correct terminology by gnasher719 · · Score: 1

      '' I think licensing is more complicated than that. If they point out that you were giving the software away, and let people copy it, then you do have to establish that you're allowed to impose conditions like this -- and a court could conceivably disagree. ''

      Now that is stupid. The GPL doesn't say: "1. You can copy this code any way you like. 2. There are the following conditions..." It says "You may distribute copies of the code along with a copy of the GPL etc. etc. ". GPL'd software is _not_ given away.

    19. Re:Correct terminology by seebs · · Score: 1

      Courts have, in the past, read things like that, and concluded that they were entirely fictitious, and that there was no real contract or agreement, and that something was in fact being given away.

      I'm not saying that will happen to the GPL, but it's happened to other agreements or attempts to impose terms in the past.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    20. Re:Correct terminology by DragonWriter · · Score: 1

      This is far from pedantry. Using terms suggesting that someone would be convicted or held liable for a "GPL violation" suggests that a court must uphold the GPL as valid for such a lawsuit to be successful.


      Its very odd to argue about what somebody "would" be held liable for when we have a case in which someone was held liable, and if the reporting is wrong, reference to the actual case and its actual holding should fairly unequivocally resolve the issue. Arguing that something would not happen based on a legal theory (and one for which no authority is offered) as a rebuttal to a news article claiming that a court has, in fact, done the thing in question is, well, somewhat dubious.

      On the contrary, a standard legal action against someone not in compliance with the terms of the GPL would be a simple copyright infringement case


      Strange, then, that in Progress Software v. MySQL AB, MySQL AB alleged a breach of the GPL rather than a "bare" copyright violation. Can you cite any case in which only a bare copyright violation was alleged, or in which a court took the perspective that that was the right way to analyze the issue? Or are you referring to a "standard" that applies only in your imagination, not in the real world?

      It seems to me that the more usual case is to argue in the alternative, from the outset, that either no permission existed from the beginning, or that subsequent breach of the license giving permission terminated the permission (providing evidence that, if the agreement was formed, the defendants action did, in fact, violate it) and that subsequent distribution was a copyright violation, not to just allege a copyright violation without specific argument to breach of the license. IIRC, that's been the case in at least one of the German cases that have gone to final results, though, not reading German, I've only read third-party accounts and/or unofficial translations of material from those cases.
    21. Re:Correct terminology by DragonWriter · · Score: 1

      The GPL has had sufficient legal testing to show that it will hold up in court.


      As I recall, there are only a handful of cases in a variety of jurisdictions that have gone to a final result even in a trial court, even fewer, if any, appellate court decisions, and no final decisions at all in some important jurisdictions (like, any in the United States) on the validity of the GPL.

      That's a rather low bar for "sufficient legal testing".
    22. Re:Correct terminology by guruevi · · Score: 1

      1) What would be the point? Linux has much evolved since then, the kernel back then (1.2?) would probably not run nor support a lot of hardware found in computers nowadays.
      2) If you have problems with the length of time between copyright and pubic domain, you should take up Mickey Mouse for that (Disney) in many countries (including but not limited to the US)

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    23. Re:Correct terminology by Kjella · · Score: 1

      The kernel is a very bad example as it's very tightly linked to hardware... a better example would be say "How many would want to run Office 97 in 2009?" Among the non-pirates there's a few, from the sound of it. Remember that the PC isn't very old, general Internet access even younger... I think software will become quite a lot more durable. Why the hell should your basic applications be something that needs replacing every few years? I'll admit I have very little software from 1995 still running except retro games, but I think in 2019 I could easily still use some of my current software.

      --
      Live today, because you never know what tomorrow brings
    24. Re:Correct terminology by LionKimbro · · Score: 1

      The GPL is an interesting experiment in using a legal loophole as the foundation for a distribution agreement. This case provides further evidence that the concept works as well in practice as it does in legal theory.


      What do you mean by, "legal loophole?"
    25. Re:Correct terminology by DragonWriter · · Score: 1

      A judge can (and will!) strike various parts of the agreement if he finds them to be in conflict with either the law or the intent of the agreement.

      No, he won't.


      He can.

      The GPL deliberately omits the severability clause commonly found in contracts.


      The absence of a severability clause does not necessarily stop a court from altering the terms of a contract in all cases. However, there may be limits on how far a court can reform a contract without invalidating it, which having a severability clause (which is an express agreement of the parties to accept alterations, in effect) may extend, and a clause expressly voiding the contract if it its terms are unenforceable (a clause the GPLv2 also lacks) may restrict.

      This means that if any part of it is contrary to local law, the entire thing is void in that jurisdiction.


      No, though an express clause stating that if any term is unenforceable the entire agreement is void might have that effect. It might not, either, and even if it did some of the terms even if ineffective as contract terms might have lingering effects under other theories other than contract per se.
    26. Re:Correct terminology by SkoZombie · · Score: 1

      So when the media reports that a court convicts someone of shooting another person dead they're wrong too? They should be pedantic and ALWAYS specify the crime rather than the action that was criminal?

      You're convicted of an action resulting in a specific crime, shooting someone -> murder, Breach of GPL -> Breach of Copyright.

      If the courts DIDN'T find they'd breached the GPL then they wouldn't have breached copyright. Of course without the GPL their distribution would have been enough to convict them, but the judge had to rule that they lost their rights to distribute under the GPL for breach of it.

    27. Re:Correct terminology by MooUK · · Score: 1

      GPLv3's handling of license violations seems quite clear to me; it's quite explicit. I haven't read v2 recently, so I can't really comment on the situation there.

    28. Re:Correct terminology by DragonWriter · · Score: 1

      GPLv3's handling of license violations seems quite clear to me; it's quite explicit. I haven't read v2 recently, so I can't really comment on the situation there.


      The GPLv3 is more explicit, though some of the same ambiguities remain as regard the effect of automatic revocation under section 8 followed by receipt of the license again under section 10. Normally, if your rights under a contract are revoked, permanently or provisionally, per its terms, and you get an offer of the same contract terms from the same offeror again, you are free to accept it. Under Section 10 of GPL v3, you automatically get a license whenever you receive software under the GPL. That you previously had a license which was revoked to the same software (or an earlier version of it) that were terminated due to breach would seem not to prevent you from accepting the license offered (by modifying or propagating the work, see Section 9) and having full rights associated with the license.
    29. Re:Correct terminology by MooUK · · Score: 1

      I think what it means is that you automatically get a license unless you belong to that group of violators - in which case you're not being prevented from accepting, but instead you're not even being offered it. Small difference, big effect.

    30. Re:Correct terminology by DragonWriter · · Score: 1

      I think what it means is that you automatically get a license unless you belong to that group of violators


      It may intend that, but there is no such express restriction in Section 10. The problem is the license at sometimes seems to treat itself as a license agreement (a thing that is offered and accepted in particular transactions), and sometimes reads more as if it views itself as a kind of universal law under which people have rights independently of particular transactions, under which people have rights independent of particular transactions.

      This isn't entirely surprising since it comes from people who view its provisions essentially as reflecting universal moral principles that they seek to enforce by leveraging copyright and license law.
    31. Re:Correct terminology by CastrTroy · · Score: 1

      On the other hand, why should we all being paying MS $500 for a copy of MS office 2009 when MSOffice 97 fulfills all of our needs. Because they don't sell Office 97 anymore. So if you want a copy of MSOffice, you have to pay for a license for the newest version. Maintaining such long copyright on things that aren't even sold anymore is depriving the public of a product that could otherwise be put to good use. If the 12 year old software is good enough, why do they keep on making changes and charging for upgrades.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    32. Re:Correct terminology by Urza9814 · · Score: 1

      I wish more people would understand the specifics of quantum physics.

    33. Re:Correct terminology by Anonymous Coward · · Score: 0

      According to the GPL, you don't have to accept it to use the software. It falls back on standard copyright law in that case.

      The GPL is irrelevant as long as you just use it, as an individual or a corporate entity. The GPL comes into play only when you distribute the binaries of the software.

      Thus when an infringer is identified, he faces a double-edged sword. Does he claim that he did not accept the GPL, in which case he's on the hook for copyright infringement? Or does he claim that he did indeed accept the terms of the GPL, in which case he's on the hook for (I'll phrase this carefully just to annoy the "contract vs. license" folks out there :P) "breach of the terms and conditions of the contract"?

      A case of infringement occurs only after he starts distributing, not before. At that point, he must accept the terms of the license in order to distribute it. If he does not accept then he is forbidden to distribute the software. If he still distributes it then he is indeed violating copyright. I am not sure how he can claim to have "accepted" the terms of the license if he is violating it in practice. Just saying "I accepted the license, your honor, but I won't show the source code even if I distribute the binaries" is worthless double talk.

    34. Re:Correct terminology by sjf · · Score: 1

      I tried to understand the specifics once, but I found that the mere act of understooding one specific meant that I could no longer understand the other specific.

    35. Re:Correct terminology by sjf · · Score: 1

      understooding ? What the hell was I typing ? That'll be the past perfect progressive form of the verb....

    36. Re:Correct terminology by Eivind · · Score: 2

      True. The GPL was not followed. But here's the thing: It's not forbidden to ignore the GPL. Its not law, afterall.

      It's not that complicated.

      Normally, Copyrigth law says that you aren't allowed redistributing or copying creative works that someone else created.

      The GPL says, in effect: "We give you permission to do those things anyway, if you follow these rules ...."

      So, if you break those rules, you *don't* have permission, which means if you still copy, you're in violation of copyrigth law.

      This is why the GPL is not an contract. (or an EULA, and why programs such as OpenOffice that insist on "I agree" on installation are braindead)

      It doesn't matter if you "agreed" to it or not. Copyrigth-law says you need permission. GPL says you get it if you follow the rules.

    37. Re:Correct terminology by Eivind · · Score: 1

      Some jurisdictions have severability built-in to contract-law. In other words, if one point of a contract is counter to local law, the rest of the contract can still be considered valid, and a person following every part of the contract, except for the point that conflicts with local law, can be held to have upheld his side of the deal.

      For those jurisdictions that don't, however, such as the USA, you are correct.

    38. Re:Correct terminology by Anonymous Coward · · Score: 0

      Hey, we're having a legal discussion here -- pedantry is necessary!

      No, a lot of unqualified opinions are being expressed concerning a legal decision :)

    39. Re:Correct terminology by mav[LAG] · · Score: 1

      The absence of a severability clause does not necessarily stop a court from altering the terms of a contract in all cases. However, there may be limits on how far a court can reform a contract without invalidating it, which having a severability clause (which is an express agreement of the parties to accept alterations, in effect) may extend, and a clause expressly voiding the contract if it its terms are unenforceable (a clause the GPLv2 also lacks) may restrict.

      Convincing, well argued - and entirely irrelevant. The GPL is a license, not a contract. There are no mutually agreed terms, no goods or services exchanged for monies or in kind, no penalties for non-delivery, no exit clauses. It's just permission to do what you would normally not be allowed to do by law - in this case copy, modify and distribute someone else's copyrighted work with certain restrictions i.e. a license.

      --
      --- Hot Shot City is particularly good.
    40. Re:Correct terminology by julesh · · Score: 1

      Or does he claim that he did indeed accept the terms of the GPL, in which case he's on the hook for (I'll phrase this carefully just to annoy the "contract vs. license" folks out there :P) "breach of the terms and conditions of the contract"?

      The GPL is not a contract.

      Go and read it. No part of it is phrased as an obligation on behalf of the licensee. Every condition is a *condition that must be fulfilled for a license to be granted* not *a condition that must be followed after the license has been granted*. A contract is an exchange of promises. The GPL is a unilateral grant of rights.

      The implication of this is that you cannot breach its terms. You either follow them (and therefore get a license and are fine) or you don't follow them (and therefore don't have a license and are guilty of copyright infringement).

    41. Re:Correct terminology by Mr.+Underbridge · · Score: 1


      Surely that should be '"Pedant of the Day" award'.

      You get runner-up. And don't call me Shirley.

    42. Re:Correct terminology by ardle · · Score: 1

      I found that if I understood a specific, I couldn't remember it - or vice versa.

    43. Re:Correct terminology by DragonWriter · · Score: 1

      Convincing, well argued - and entirely irrelevant. The GPL is a license, not a contract.


      Actually, whether the GPL is generally a contract or a "pure" license is a matter about which there has been no small amount of debate in legal circles, and the answer in specific cases may depend not only on the jurisdiction whose law applies, but also the situation of the parties in a particular case. But, in any case, contract principles are often applied to a degree in the construction of agreements that are not contracts.

      There are no mutually agreed terms


      Yes, there are. Mutual agreement is established by acceptance of an offer. The GPL is expressly an offer, and expressly states how it may be accepted. The terms are, therefore, mutually agreed through offer and acceptance.

      no goods or services exchanged for monies or in kind, no penalties for non-delivery, no exit clauses.


      While the first of those items is a way to meet a requirement for a valid contract (consideration), none of those is categorically a requirement for a contract.

    44. Re:Correct terminology by mav[LAG] · · Score: 1

      Care to rebut this explanation?

      --
      --- Hot Shot City is particularly good.
    45. Re:Correct terminology by DragonWriter · · Score: 1

      That explanation is a fairly succinct recapitulation of the FSF position, mostly quoting and interpreting the FSF General Counsel's description. He's hardly the only lawyer that's written on the issue, and others have taken contrary views, or mixed views.

      The thing is, there isn't one set of law (even in the US) that applies to determining whether an agreement is a contract, there are different ones. And the content of the written instrument isn't the only thing relevant to make that determination. Its not an entirely simple question, and there are many ways in which the GPL skates along boundaries where general pronouncements that aren't applying specific laws may not hold generally.

      Its also important to note that if Moglen's position (which is highlight to rebut the idea that the GPL is risky because it might be specifically enforced to "pry open" proprietary code) is correct, the pledge by the copyright holder that the license is irrevocable may not itself by enforceable in all cases by a downstream distributor/developer, since the idea that it is rests largely on a contract foundation, since a gratuitous license (one not supported by consideration and therefore not a contract) is revocable at will in, at least, most US jurisdictions. The downstream developer/distributor might have some protection against action on revocation of the license through the doctrine of promissory estoppel, but that is not the kind of full protection that a contract obligation is.

      It may also be worth noting, on the issue of risks associated with the GPL as a pure license, that, expressly under US law, only a signed nonexclusive licenses prevails against a transfer of the underlying copyright (17 USC 205(e)).

  3. Meaning of plaintiff by Anonymous Coward · · Score: 0

    In case like me you weren't sure: The plaintiff initiates a lawsuit, Harald Welte was the accuser.

    1. Re:Meaning of plaintiff by The+Monster · · Score: 1

      plaintiff initiates a lawsuit
      Easy to keep straight: The person who brings a complaint to the court is the plaintiff. Then the person who responds to the complaint is the respondent
      --

      [100% ISO 646 Compliant]
      SVM, ERGO MONSTRO.

  4. Conflict and Chaos in the Hive Mind! by goldspider · · Score: 4, Funny

    Court upholding GPL - Good!
    Conviction for copyright violation - Bad!

    What's a loyal drone to believe anymore??

    --
    "Ask not what your country can do for you." --John F. Kennedy
    1. Re:Conflict and Chaos in the Hive Mind! by lixee · · Score: 1

      It's about info wanting to be free, you nimrod. Had Skype released the code, they wouldn't have been sued in the first place.

      --
      Res publica non dominetur
    2. Re:Conflict and Chaos in the Hive Mind! by mrchaotica · · Score: 4, Informative

      The GPL is permissive, and thus turns the usual function of copyright on it's head.

      In other words, usually when people violate copyright it's through an act that increases the spread of the information, and prosecuting them for it would restict that spread. In contrast, when people violate copyright by failing to abide by the GPL, they themselves are restricting the spread of the information and prosecuting them restores it.

      If one (e.g., a "loyal drone") consistently believes that spreading information is good and restricting it is bad, there is no contradiction.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    3. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      Whatever suits you now, just like the other side.

    4. Re:Conflict and Chaos in the Hive Mind! by goldspider · · Score: 2, Funny

      Are we talking beer, speech, or herpes?

      --
      "Ask not what your country can do for you." --John F. Kennedy
    5. Re:Conflict and Chaos in the Hive Mind! by plague3106 · · Score: 1

      They did provide a link to download the code though, but it seems that doesn't matter.

    6. Re:Conflict and Chaos in the Hive Mind! by UbuntuDupe · · Score: 1

      Here's what you have to believe to match ~70% of /.ers:

      1. Copyright in general is a good thing, but has too long of a term and his horribly misused today.
      2. Anyone who does anything whatsoever that would be necessary to catch and convict someone violating copyright over P2P is a horrible totalitarian Nazi.
      3. Copyright really only benefits the record companies, who are parasites.
      4. It's possible to make money as a musician without copyright or the evil record companies, and is therefore possible today. Ignore how, when given the choice, artists prefer to work with a record company.
      5. If record companies were just nicer, people would buy more stuff from them even though they can get it for free on P2P.
      6. From the fact that geeks know how to get music for free, it follows that everyone knows how to so we are seeing concrete evidence of copyright not being necessary.

      I think that about covers it.

    7. Re:Conflict and Chaos in the Hive Mind! by LWATCDR · · Score: 1

      Funny but that is a great case of newspeak.
      GPL is permissive... But it prevents you from distributing something with out making the source available...
      I happen to like GPL V2 but this statement is just not as slanted as the term Digital Rights Management.
      You find it permissive because it gives you permission to do something you want while preventing someone else from doing what they want.
      What I don't get is why is putting the source on the internet not good enough?

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:Conflict and Chaos in the Hive Mind! by Hatta · · Score: 2, Insightful

      GPL is permissive... But it prevents you from distributing something with out making the source available...

      The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others.

      What I don't get is why is putting the source on the internet not good enough?

      Not everyone has access to the internet. Had they included a written offer to send the source code by post for a reasonable shipping charge they'd probably have been fine.

      --
      Give me Classic Slashdot or give me death!
    9. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      GPLv3 allows putting the source code only on a server accessible via Internet, GPLv2 doesn't.

    10. Re:Conflict and Chaos in the Hive Mind! by LWATCDR · · Score: 1

      "Not everyone has access to the internet. Had they included a written offer to send the source code by post for a reasonable shipping charge they'd probably have been fine."
      WHAT!!! again I will say WHAT!!!
      The source is for a Skype VOIP PHONE! It doesn't work if you don't have the Internet!

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    11. Re:Conflict and Chaos in the Hive Mind! by hax0r_this · · Score: 1

      Who the hell is using skype but doesn't have access to the internet?

    12. Re:Conflict and Chaos in the Hive Mind! by The_DoubleU · · Score: 1

      Not everyone has access to the internet. Isn't this a case about software used in a Skype phone.
      And is Skype not VOIP?
      Who with no internet will be using Skype?
      I agree that they should have included the source on a CD with the phone, but your argument is just silly.
      --
      What power has law where only money rules.
    13. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      Not everyone has access to the internet. Well, an internet phone service would not be of much use to them, then, would it?
      D'oh!
    14. Re:Conflict and Chaos in the Hive Mind! by Jeff+DeMaagd · · Score: 1

      The problem is that for the GPL to be at all enforceable, you have to have copyright laws. All this about whether it's permissive or restrictive doesn't matter on that particular point.

    15. Re:Conflict and Chaos in the Hive Mind! by noahclem · · Score: 1

      There was a great article on Prince in the Times this weekend and how he operates in this world. He gives cd's for free in the London newspaper - pretty much follows the heavy touring Dead/BB King model, but with extra-expensive exclusive shows, and a punch for being much more prolific.

      Re your point #4 - this is a tournament model, where the vast majority of talented musicians don't make their money from records, but the hope of coming out on top and becoming the next [insert name here] is too alluring to pass up the chance when offered. I guess the question is whether the grass-roots myspace/youtube phenom will provide an attractive enough alternative for musicians that they will bypass record companies (Jake Shimabukuru - the incredible ukelele dude - certainly benefited from the youtube thing)

    16. Re:Conflict and Chaos in the Hive Mind! by hajus · · Score: 1

      m'eh. Theoretically, if you ran the server on which the src is kept, you could keep it down most of the time or not fix your router issues. If both the src and the bin are kept on the same machine, then the inaccessability would affect both instead of only the src.

    17. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      Doing a bit of extrapolation here, since I do not have full information. GPL is a general license, so has to cover lot of a usage scenario. At this particular case the violator happened to be a internet communication company. But the accused can well been a non-internet based company. I expect the code to have been licensed using GPL2 which was released in 1991, a time when the access to internet was really sparse.

    18. Re:Conflict and Chaos in the Hive Mind! by FooBarWidget · · Score: 2, Informative

      "The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others."

      No, because under copyright law, you never had that right in the first place. The GPL gives you *more* rights than you had, it just doesn't give you the right to not give the same rights to others.

    19. Re:Conflict and Chaos in the Hive Mind! by Dragonslicer · · Score: 1

      Not everyone has access to the internet. Had they included a written offer to send the source code by post for a reasonable shipping charge they'd probably have been fine. That leads to the potential problem of what's considered good enough. How many different ways would they need to offer? Can they put a generic "contact us at this address/phone number/e-mail address for arrangements" notice? I wouldn't be surprised if this was more of a mistake on the part of people at Skype than a malicious and deliberate attempt to violate the GPL.
    20. Re:Conflict and Chaos in the Hive Mind! by mpe · · Score: 1

      The source is for a Skype VOIP PHONE! It doesn't work if you don't have the Internet!

      Even if the Skype protocol is intended for Intenet usage it will probably work on any IP network. Possibly with more trouble than H.323, SIP or IAX2. IIRC Skype is ment to be peer to peer, or does the thing just fail if Skype's servers cannot be connected to?

    21. Re:Conflict and Chaos in the Hive Mind! by mpe · · Score: 1

      The problem is that for the GPL to be at all enforceable, you have to have copyright laws.

      The GPL would probably work just fine even if copyright terms were 5-10 years. Just because it needs copyright laws dosn't mean it needs the kind of effectivly infinite copyright laws we have now.

    22. Re:Conflict and Chaos in the Hive Mind! by DragonWriter · · Score: 1

      Perhaps one could believe that slashdot isn't a hive mind.

      Its strange that the most prominent accusation of Slashdot groupthink are from people alleging that the groupthink is self-contradictory.

    23. Re:Conflict and Chaos in the Hive Mind! by giminy · · Score: 0

      The GPL is permissive, and thus turns the usual function of copyright on it's head.

      Permissive is such a funny word here. The GPL is actually quite restrictive.

      * legalizing polygamy (permissive)
      * making a law that says everyone must be polyamorous (GPL)

      We're happy either way (trust me), but the latter is a lot more work if we just want to be lazy.

      --
      The Right Reverend K. Reid Wightman,
    24. Re:Conflict and Chaos in the Hive Mind! by mqduck · · Score: 0

      "The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others."

      No, because under copyright law, you never had that right in the first place. The GPL gives you *more* rights than you had, it just doesn't give you the right to not give the same rights to others. You know, you can argue about legal definitions to your hearts content, but it doesn't change the practical reality of the situation one tiny bit (with the possible exception of loopholes).
      --
      Property is theft.
    25. Re:Conflict and Chaos in the Hive Mind! by mrchaotica · · Score: 1

      If we didn't have copyright laws, we wouldn't need the GPL anyway!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    26. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      As posted by someone else above

      It is a legal REQUIREMENT to supply a copy of the GPL with the software. Sending just a link, or a postal address for the license isn't acceptable. It is acceptable for access to the source-code, but not the license.

    27. Re:Conflict and Chaos in the Hive Mind! by mrchaotica · · Score: 1

      That's a bad analogy, because you're still looking at it from the "forcing distributors to provide source code" perspective. Instead, you should see that it's permissive from the "allowing users to get source code" perspective.

      Prohibiting users to get the source code is restrictive. Forcing users to get the source code is restrictive. Allowing users to get the source code is permissive. The GPL does the third thing, so it is indeed permissive. And any restrictions on distributors are irrelevant.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    28. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others.

      Only if you accept RMS's asinine assertion that all users have a right to all the source code for any software they can acquire.
      You could just as well say that a license requiring you to suck off RMS is permissive because it prevents you from taking away his right to free head.

    29. Re:Conflict and Chaos in the Hive Mind! by Raenex · · Score: 1

      If we didn't have copyright laws, we wouldn't need the GPL anyway! Stallman created the GPL. He was driven to do so by not having access to source code for a printer driver. He had the binary, but not the source, and he wanted to hack the source. So he created the GPL to say you must provide the source. Without copyright the GPL has no teeth, and the printer driver can be binary only.

      No copyright, no GPL. People are free to create binary-only derivatives of your source code. A bitter pill for pro-GPL, anti-copyright advocates to swallow, isn't it?
    30. Re:Conflict and Chaos in the Hive Mind! by LittleBigLui · · Score: 1

      see sig.

      --
      Free as in mason.
    31. Re:Conflict and Chaos in the Hive Mind! by micpp · · Score: 1

      You do realize that no-one is forcing you to release anything under the GPL, or use any GPL-covered software.
      The GPL doesn't force everyone in the world to release source code, but it does require people who release products based on GPL code to release their modifications. It's no different than any other software, if you don't like the license then tough cookies, because that's what the developer released the code under.
      If anything, the people complaining about how they can't use GPL code in their product are the ones who think they have the right to all the source code they can acquire.

    32. Re:Conflict and Chaos in the Hive Mind! by mrchaotica · · Score: 1

      People are free to create binary-only derivatives of your source code.

      Ah, but you are free to legally decompile the source and do whatever you want with it. And, unlike current "reverse engineering," you don't have to have separate people deciphering the original and writing the new -- you can just copy.

      Besides, in a world without copyright, no business model that I can think of that depends on closed source would be viable anyway. All these closed-source vendors would go out of business because they'd only be able to sell a very small number of copies before somebody put it up on the Internet (and in a nice conspicuous place too, unlike today's situation where legal threats and shame limit it).

      Sure, it's a trade-off, but it's arguable that it would be a worthwhile one.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    33. Re:Conflict and Chaos in the Hive Mind! by LWATCDR · · Score: 1

      Yes you have to have access to the Skype servers for it to work. It is just wrong that posting the source on the internet isn't good enough. I wonder if I could demand that Gentoo.org or any number of Mirrors that have Linux distros on them mail me the source code for the cost of the media? But wait if I don't have the Internet maybe I don't have a DVD or CDR so they must send it to me on Floppies... Wait my computer doesn't have a floppy... Yes a print out for the cost of the media. Or maybe punch cards.
      Yea this will encourage people to support GPL. Sue them and them make them not just post the source on the Internet but to have a way to get it by mail!
      Didn't Linus say, "Real men don't back up their code. They upload it to an FTP server!"
      Nope the court was wrong. Including a URL to the source in the package is more then good enough.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    34. Re:Conflict and Chaos in the Hive Mind! by giminy · · Score: 1

      Prohibiting users to get the source code is restrictive. Forcing users to get the source code is restrictive. Allowing users to get the source code is permissive. The GPL does the third thing, so it is indeed permissive. And any restrictions on distributors are irrelevant.

      If you're really arguing that the GPL does not force distributors to provide source code, you don't understand the GPL. The GPL *does* force distributors to provide source code. In fact, the GPL does both: (1) Allowing users to get the source code and (2) Forcing distributors to provide source code. If distributors are not being forced to provide source code, then users are not allowed to get it.

      Your argument is trying to put spin on the agreement and only mentions one half of the equation. I would suggest that you try the FSF GPL quiz, particularly questions 1 and 2: link. They detail the requirements that a binary distributor *must* meet in order to meet the licensing requirements of the GPL.

      This means that the license is restrictive toward the distributor, and hence can be considered a restrictive license.

      Reid

      --
      The Right Reverend K. Reid Wightman,
    35. Re:Conflict and Chaos in the Hive Mind! by Raenex · · Score: 1

      Ah, but you are free to legally decompile the source and do whatever you want with it. But Stallman wanted the source.

      All these closed-source vendors would go out of business because they'd only be able to sell a very small number of copies before somebody put it up on the Internet What do you think GPL3, DRM, and "trusted computing" is all about? If the hardware is locked down tight enough you won't be able to get at the binary. Then there's the "software as a service model", which GPL3 won't even address because while combatting DRM was pushing the envelope, requiring server operators to release source would have been busting through it.

      Sure, it's a trade-off, but it's arguable that it would be a worthwhile one. Personally, I agree, though I'd probably just prefer drastic reform on copyright duration and a repeal of the DMCA. But if you're talking about the GPL, you have to be very clear about *your* beliefs vs Stallman's. The general claim is that the GPL needs copyright. Since Stallman created the GPL, it makes sense to default to his viewpoint, and ironically for Stallman and his followers, the claim is true.
    36. Re:Conflict and Chaos in the Hive Mind! by mrchaotica · · Score: 1

      If you're really arguing that the GPL does not force distributors to provide source code, you don't understand the GPL.

      No, I'm arguing that distributors are not important. They don't deserve freedom.

      Users are important, and the GPL provides freedom for users. Therefore, the GPL is permissive.

      Complaining that the GPL favors the rights of users over the bogus "freedom" of distributors is exactly like complaining that the law favors the rights of citizens not to be killed over the freedom of murderers to kill!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    37. Re:Conflict and Chaos in the Hive Mind! by Anonymous Coward · · Score: 0

      the people complaining about how they can't use GPL code in their product are the ones who think they have the right to all the source code they can acquire.

      Yes! That's the entire point of this thread.
      People against copyright think they should have a right to any source code (or other information) they can acquire.
      People who support the GPL presume that they can hold that right hostage using copyright to pursue their goal of making people distribute their source code under the GPL along with their object code.
      Therefore people who support the GPL but profess to be against copyright are hypocrites.

      This isn't rocket surgery folks!
    38. Re:Conflict and Chaos in the Hive Mind! by mqduck · · Score: 1

      Boy, I sure would love to meet whoever moderated paying attention to practical reality as "overrated."

      --
      Property is theft.
    39. Re:Conflict and Chaos in the Hive Mind! by micpp · · Score: 1

      It works the other way around too. People who don't respect the GPL and release code from it in a closed source product presumably wouldn't like it if people just downloaded that product instead of buying it. Thus they are hypocrites.
      And I was under the impression that the people supporting the GPL but are against copyright were using the logic that the GPL is a sufficient stopgap until copyright law can be reformed. If they're not using that logic, and are saying that people shouldn't violate the GPL but it's OK to torrent the latest version of Office or whatever, then yes, they are hypocrites.

  5. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 4, Funny

    Why not!

    In any case you have completely misrepresented peoples positions and conflated different groups.

    Don't look now but I think your strawman is on fire.

  6. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 4, Funny

    Yes we can. And do. You see, RIAA/MPAA are evil. The OSS guys are good. Haven't you seen Star Wars?

  7. Re:Slashdot Hypocrisy by mrchaotica · · Score: 4, Insightful

    What do you mean? Opposing the RIAA means supporting the user's freedom. Enforcing the GPL also means supporting the user's freedom. There is no contradiction.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  8. Re:Slashdot Hypocrisy by Wannabe+Code+Monkey · · Score: 1, Insightful

    Now we will see the same people who oppose RIAA/MPAA copyrights cheering the copyright action that enforces open source. Don't you see that you can't have it both ways?

    That's bullshit and you know it. On several occasions, pretty much every story about file trading and copyright I see posts from slashdotters saying that they believe current copyright for songs is out of touch with reality, but still wouldn't participate in illegal file trading because of the ethical issues. You don't give people enough credit.

    Plus, you're talking apples to oranges when you compare adhering to the GPL to adhering to what the RIAA wants with regards to songs. The GPL only lets you do more with the work than would otherwise be possible via copyright, the RIAA wants to restrict the rights of users even further than what current copyright does allow.

    --
    We always knew Comcast was corrupt, here's the proof: http://tech.slashdot.org/comments.pl?sid=1909890&cid=34545432
  9. Re:Slashdot Hypocrisy by another_fanboy · · Score: 0

    Don't you see that you can't have it both ways?

    The difference is that the GPL and BSD copywrites are meant to safeguard against eccessive copywriting by large companies. They are designed to protect us.

  10. Re:Slashdot Hypocrisy by newgalactic · · Score: 1

    While I do see a slight difference, his point is taken.

  11. Re:Slashdot Hypocrisy by butlerdi · · Score: 0

    Not at all. The people challenging the rights of free use have themselves been guilty of violation. Why is the film industry in California, what about Micky Mouse. These scummy folks have abused the system (payola) for years, have ripped off the artists and now scream shit ........ Fuck them. These folks are scum...... They represent themselves, not the artists whose works they live off... What about the drugs they have supplied to artists et al.... I spent 10 yers in the business and was utterly disgusted by the bullshit.

    --
    "If the King's English was good enough for Jesus, it's good enough for me!" -- "Ma" Ferguson, Governor of Texas (circa
  12. Slashdot Beatings. by Anonymous Coward · · Score: 0

    I much prefer the "you can abuse copyright holders anyway you please and they'll still produce the good stuff". Let's see if something similar applies to OSS programmers.

  13. Misleading or incomplete summary. by argent · · Score: 5, Informative

    The actual problem is that they did not include the text of the GPL with the phone. The summary here in Slashdot didn't mention that, and had me wondering what the problem with the provided URL was.

    1. Re:Misleading or incomplete summary. by onecheapgeek · · Score: 1

      I had a bit of trouble figuring that out myself, from the text provided...

        Skype because of GPL injury condemns
      Regional court Munich I: GPL must be kept accurately

      Once more confirmed a German court the validity of the GPLv2. The regional court Munich condemned Skype because of the injury of the GPL, which above all is interesting, because it concerns thereby a foreign enterprise.
      However the VoIP software of Skype was not the center of attention, on the contrary it concerned the VoIP telephone SMCWSKP 100 from SMC, which is sold Skype over its Website and which is delivered without the appropriate Linux source texts, was based it nevertheless on the free operating system. On the other hand Netfilter developer Harald Welte had complained, which holds at parts of the Linux Kernel copyright and with its project gpl-violations.org for years against GPL injury proceeds.

      Apart from the fact that the regional court Munich I (Az. The judgement condemned, does not turn off 7 O 5245/07, yet validly) with Skype a Luxemburger company also very clearly to an exact adherence to the GPL. A supplement was attached to the equipment later, which referred to the used GPL software and contained URL, where the source texts are callable - nevertheless this are sufficient the court in the available case, not. This possibility plans the GPL only for software, which is supplied over Internet. Besides the text of the GPL also on the supplement, which likewise offends against the license obligations, was missing.

      Beside the procedure against Skype at present also one legal proceedings are pending against the Vertreiber of the telephone, SMC network. Dr. Julia Küng on the sides Institut for legal questions of the free ones and open SOURCE software (ifrOSS) published, also to the attorney Dr. Till hunter belonged to details for the background of the procedure, that represented the plaintiff Harald Welte in the law case against Skype. (ji)

    2. Re:Misleading or incomplete summary. by freedumb2000 · · Score: 1

      Basically the judge also found that it is not sufficient to only refer to a URL to access the source code and license text . This would be fine if the software product itself was also distribited over the internet, but in any other case that is not sufficient. I am not sure if the court specified what would be a sufficient means to enable access to the source code. It really baffles me that a company is knowledeable enough to take a advantage of GPL software to develop their own product but tries to weasel out of provinding something as simple as the source code changes and give credit to the other developers. It is not like it's asking for much.

    3. Re:Misleading or incomplete summary. by crazybasenji · · Score: 1

      Under GPLv2, since the phone contains the covered binaries, Skype would have had to include: 1. the source code on "a medium customarily used for software interchange" (section 3a) or 2. a written offer to provide the source code (section 3b). A URL to the source code does not suffice when the work is distributed physically.

    4. Re:Misleading or incomplete summary. by Dragonslicer · · Score: 1

      2. a written offer to provide the source code (section 3b). A URL to the source code does not suffice when the work is distributed physically. Would a notice saying "go to this URL to download the source code" not be considered a written offer to provide the source code?
    5. Re:Misleading or incomplete summary. by MooUK · · Score: 1

      I don't think so. The language in that section is quite specific and downloads of that sort are covered elsewhere; as I recall a link like that would not satisfy the specific terms used.

    6. Re:Misleading or incomplete summary. by argent · · Score: 1

      Furrfu.

      The Internet is a "medium customarily used for software interchange". And a URL is a "written offer to provide the source code".

      And it's distributed on a device that needs an internet connection to work.

    7. Re:Misleading or incomplete summary. by argent · · Score: 1

      Basically the judge also found that it is not sufficient to only refer to a URL to access the source code and license text . This would be fine if the software product itself was also distribited over the internet, but in any other case that is not sufficient.

      Note text in boldface.

    8. Re:Misleading or incomplete summary. by Brandybuck · · Score: 1

      GPL: License to Sue.

      --
      Don't blame me, I didn't vote for either of them!
    9. Re:Misleading or incomplete summary. by Brandybuck · · Score: 1

      It is not like it's asking for much.

      It's asking a shitload.

      Fred: "Hey Larry, can I borrow your phone to make a call?"
      Larry: "Sure, here it is."
      Fred: "Hey! You didn't give me the source code!"
      Larry: "Get a life you twit, here's the URL for the source."
      Fred: "Not good enough! You gave me a physical phone, now I am demanding the physical source code!"
      Larry: "Give me my fucking phone back!"
      Fred: "Too late! You distributed it to me, now I will sue you ass in a German court!"

      --
      Don't blame me, I didn't vote for either of them!
    10. Re:Misleading or incomplete summary. by Tony+Hoyle · · Score: 1

      Next time I'm at a show and the debian guys are handing out copies of etch on CD..

      "Hey you bastard you didn't give me the source code! What to you mean it takes 13 DVDs and you don't have it. I'll see you in court."

    11. Re:Misleading or incomplete summary. by Brandybuck · · Score: 1

      Linux World Expo is in a couple of weeks. Maybe I'll just do that. Maybe I'll have my lawyer explain to them that "accompanied by" doesn't mean you can get away with merely putting a notice on the CD.

      But I won't. Why punish the good guys for the hyper-anal antics of a few maladjusted community members?

      --
      Don't blame me, I didn't vote for either of them!
    12. Re:Misleading or incomplete summary. by Ben+Hutchings · · Score: 1

      There's no requirement to distribute source at the same time. As an alternative, you can offer to distribute source using common media formats or protocols, which Debian does. Some DVD build configurations do include source though.

    13. Re:Misleading or incomplete summary. by crazybasenji · · Score: 1

      1. Unfortunately, per the GPL, the internet is not considered a customary medium when distributing the binaries physically, which you're doing when you distribute the phone. Obviously, if the binary is downloaded, then the source can also be downloaded. 2. Once again, a URL is not a written offer. The basis for the GPL obligation is derived from contract law.

  14. Re:Slashdot Hypocrisy by newgalactic · · Score: 1

    I agree with where your heart is. But I don't believe the law makes (or read "is supposed to make") a distinction between "us" and "them".

  15. Re:Slashdot Hypocrisy by langelgjm · · Score: 4, Insightful

    Now we will see the same people who oppose RIAA/MPAA copyrights cheering the copyright action that enforces open source. Don't you see that you can't have it both ways?

    In a perfect world, we wouldn't need the GPL, but we don't live in a perfect world. The GPL attempts to use the (imperfect) legal tools that do exist (read: copyright law) to accomplish its goal of access to source. The spirit behind it has little to do with copyright.

    --
    "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
  16. No. Public information access vs Corporate control by Anonymous Coward · · Score: 0

    This is not inconsistent with fighting for public access to information.

    We don't like RIAA suing College students, because it is a misuse of the legal system to protect an already overly protected monopoly.

    We like protection of the GPL, as with an extinct public domain, open-source/creative commons is all that remains.

  17. Re:Slashdot Hypocrisy by Volante3192 · · Score: 2, Insightful

    Umm, I think you'd find many people on /. would gladly let groups like the RIAA and MPAA hold onto copyrights if they didn't exert such a stranglehold on them and for so long.

    What we're opposed to are the draconian enforcement and perpetual lengthening of copyright expiration.

    So...no. I don't see where your argument has solid ground to stand on.

  18. Re:Slashdot Hypocrisy by shark72 · · Score: 1

    "Now we will see the same people who oppose RIAA/MPAA copyrights cheering the copyright action that enforces open source. Don't you see that you can't have it both ways?"

    And adding further humor, Skype was developed by the guys who developed Kazaa. They knew what Kazaa would be used for; they certainly weren't naive enough to think that it would be used only for Linux distros and Creative Commons materials.

    At any rate, it's perfectly justified to ask to have something both ways. For example, many people like to pirate music because it's a great way to enjoy music for free. But at the same time, we wouldn't want our term papers or graduate thesi shared with our schoolmates before we've turned them (the papers) in. It's other people's information that typically wants to be free.

    --
    Sitting in my day care, the art is decopainted.
  19. translation by LiquidMind · · Score: 1

    "nevertheless this are sufficient the court in the available case, not."

    sorry, i could not stop giggling when i read this...reminded me of Borat... "this is suit is black not"

    but on a serious note, this more aptly translates to "however, this was not sufficient to the court for the case in question"

    --
    This sig contains repetition and redundancy.
    1. Re:translation by Zontar_Thing_From_Ve · · Score: 1

      There's an old joke, probably from WWII (or maybe the Cold War era), about a German translator. A guy I used to work with who spoke fluent German told it to me. It goes like this:

      A translator is listening to a German radio broadcast and busily writing down what he hears. He says nothing for a long time, but keeps writing. A nearby woman is growing impatient for the translation.
      Woman: What are they saying? What are they saying?
      Translator: Just a minute, ma'am. I'm still waiting for the verb.

      German really seems to be like this. For what it's worth, Russian, also an inflected language, would not simply stick a negative at the end of a sentence to negative the information that preceded it. The negative would be right in front of the verb, just like in English.

    2. Re:translation by LiquidMind · · Score: 1

      when i started learning english (german is my native tongue) i was amazed by the same thing, just the other way around. I wondered how english sentences could possibly make sense with all the 'meaty' information in total dis-array.
      however, speaking both languages (mostly) fluently, i came to realize that it doesn't really matter that much.

      --
      This sig contains repetition and redundancy.
    3. Re:translation by nbert · · Score: 1

      To be fair online translations have gotten better over the years. I'm still smiling when I think about yahoo's translation of the clinton report. It was a totally differnt story in the German version, but quite entertaining: Monica Lewinsky performing "mouth-gender" (Mundgeschlecht - oral sex) and the involvement of a family called "Construction-Parts" (Familie Bauteile - no clue what the original said) are among the highlights I still remember.
      Computer translations are still full of mistakes, but it's getting better over the years. Those services really help nowadays in case nobody capable of translating is around.

    4. Re:translation by Anonymous Coward · · Score: 0

      As an interpreter, I can confirm this is not just a joke - in simultaneous interpreting from German into English (or Spanish or a number of other languages I don't speak, for that matter) it can be quite a pain to have to wait for the verb, which may not come for quite a while if it's stuck behind a convoluted heap of subordinate clauses. And the person listening to you through the headphones at a conference doesn't care you're still waiting for the verb, they get edgy if the headphones go silent.

      In practice, you either have to speak slower or waffle about so as to fill the gap, interpret any information that you can interpret without having the verb, or - and this is where it gets exciting - anticipate the verb. In standard phrases it's often quite obvious what the verb will be so you can use it and go on - but there's always the possibility you've guessed wrong and have to backtrack. Ah, the joys of German interpreting.

      As for the google translation, I'm pleasantly surprised, it does actually give you the gist of what's going on. Not feeling threatened yet though ;)

  20. Not Really by EMIce · · Score: 1

    The hardcore would question the validity of copyright entirely. If there were no copyright and patent laws, GPL wouldn't be so necessary as code would be leaked/distributed/re-used all the time, open source or not. Though would people make less innovative software if this happend? Or would all the code-reuse allow for innovation to flourish as it made more permutations of existing software technologies possible?

    1. Re:Not Really by goldspider · · Score: 1

      While I agree that freer code would allow more innovation, I still believe profit-motive drives innovation.

      Say what you will about the negatives of vendor lock-in (an argument with merit), cool gadgets mean big bucks. Take away profit, and where do iPhones come from?

      --
      "Ask not what your country can do for you." --John F. Kennedy
    2. Re:Not Really by dada21 · · Score: 2, Insightful

      I don't believe that copyright drives innovation -- innovation usually means providing a new direction or addition to a previous product that someone else likely designed, which was "innovated" from a previous product that another designed. New ideas based on old ideas, etc.

      What drives innovation is a desire to capture a particular market share for a demand, in effect providing a new supply stream for an existing demand, or hoping to create demand due to a new supply stream for a new product or feature.

      In my opinion, it is the combination of features, at a given price, backed by a given support structure, with promises to function at a given level of operation, that matter most. In this case, it isn't copyright that provides for a "winner" in that market of supply and demand, it is the person who releases the best combination of features+price+support+quality to a market that desires it, that wins, if that person markets the product properly.

      Copyright merely restricts competition from doing better than the originator of that particular product or service, and does the market a disservice by reducing the opportunity for other producers to do something one step better.

    3. Re:Not Really by Quila · · Score: 1
      Copyright merely restricts competition from doing better than the originator of that particular product or service, and does the market a disservice by reducing the opportunity for other producers to do something one step better.



      It doesn't restrict the others from doing better as long as they write their own stuff. It allows the originator to restrict them from taking his work and passing it off as their own long enough for the originator to make a profit. This worked well way back when the monopoly granted by copyright was of a sensible term.

  21. Re:Slashdot Hypocrisy by DaHat · · Score: 1

    > What we're opposed to are the draconian enforcement and perpetual lengthening of copyright expiration.

    Have you ever stop to consider when software covered under the GPL will actually become public domain and no longer be bound by the terms of the GPL?

    Like it are not, all those extensions that benefit the (MP|RI)AA also end up benefiting the open source world as well, only the benefits to FOSS will be a little later in coming in theory.

  22. Re:Slashdot Hypocrisy by Maniac-X · · Score: 1

    There's a difference here, though. First and foremost, the GPL is about sharing; the RIAA/MPAA are most certainly not. You do not have to pay to obtain GPL code, but the RIAA/MPAA want you to pay out the nose for every song and movie you ever watch.

    --
    (A)bort, (R)etry, (I)gnore?_
  23. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 0

    Thesi, really? Stop trying to sound pretentious and buy a dictionary. The plural is theses, the origin is Greek.

  24. Beginning of the end for open source? by Anonymous Coward · · Score: 0, Insightful

    If this catches on, support for open source will pretty much vanish. No one is going to risk having to give out the the proprietary code that makes their business profitable. The open source license will be far more of a financial liability than the cost of buying a license for a commercial product.

    1. Re:Beginning of the end for open source? by FunWithKnives · · Score: 4, Insightful

      You are mistaken. The only way that Open Source will die is if this type of thing doesn't happen. People like Harald are doing their best to uphold Open Source, as well as Free Software. If you want to allow corporations to fuck everyone else over and take without giving back, then you should really be looking at one of the BSD licenses.

      "Holy shit, someone's actually enforcing GPL v2! Open Source is going to die!" is, excuse my language, but fucking retarded. Find something else to blow up about. I hear the sky is falling.

      --
      "We may face a scorched and lifeless earth, but they're accountable to their shareholders first."
    2. Re:Beginning of the end for open source? by Billly+Gates · · Score: 1, Flamebait

      It already is.

      I have read here on /. that many employers ban GPL outright even when not bundling it with code. One had to ban ssh even though it wasn't gpl just because it made the banks lawyers nervous.

      This is why I support the BSD and MIT licenses. This creates fud for other more free licenses.

      But if I were developing software I would be very carefully on what I include or link to in my program. Its not worth losing your job to it.

      Yes, RMS some software is always going to be closed because teh MBAs and accountants do not care about freedom but rather profit and they make the decisions to open source something.

    3. Re:Beginning of the end for open source? by 91degrees · · Score: 2, Insightful

      Skype's business doesn't require secret proprietry code It's a service, and they givwe the client software away. They could rewrite from scratch at greater expense, and there may be a valid business reason to do so, but it's not goin to resuolt ina major impact for open source.

      Countless businesses use GPL software for all sorts of reasons - whether internally or for bespoke systems. Skype deciding not to isn't going to harm the cause. On the other hand, Skype getting away with not following the terms honourably will harm the free software movement - or at least the FSF's free software movement.

    4. Re:Beginning of the end for open source? by $1uck · · Score: 1

      This is nonsense. If you're business model is to develop, shrink wrap and sell software of course you are not going to choose to use GPL code. If however you are in the business of performing a service or producing real products and happen to need specialized software and develop your software in house, GPL is wonderful. The cost can't be beat.

    5. Re:Beginning of the end for open source? by wrook · · Score: 1

      Yes, RMS some software is always going to be closed because teh MBAs and accountants do not care about freedom but rather profit and they make the decisions to open source something.


      I'm not RMS, but I'll respond anyway. What you say is very true. Some people will probably always write proprietary software. The point to free software is that it is better for the customer. It gives them more options. Personally, I would *never* choose proprietary software for mission critical applications if I had any reasonable choice. In the event that such software does not end up meeting my needs (e.g., it fails, or my needs change) I basically have no options other than to hope that the vendor will kindly modify the software for me in the time frame I need. With free software, I have many other options.


      From my perspective, the task of education WRT to free software adoption is twofold: 1) Educate the users that they can obtain software that gives them important freedoms 2) Educate vendors that they can more easily/cheaply support their customers using free software business models.


      I have worked in companies whose bean counters cannot fathom the benefits of free software. In some cases, this ended up not being important since there were no established free software alternatives in the market. But I have also witnessed companies whose margin gets driven so low that they can not provide *any* support due to free software competition. These companies end up failing and the market becomes dominated by free software. A good example of this is in the SIP PBX space, which is completely dominated by Asterisk.


      The markets I've witnessed are generally those where enterprise sales are the most important. You can not (monetarily) compete against companies who give the software away and charge for support/customization.
      While free software solutions are generally not less expensive than proprietary, the customer ends up walking away with a lot more for their money (i.e., a fully customized system for their environment). Once the customers
      understand what they are getting, it makes competition against free software almost impossible.


      It is possible that markets oriented towards retail consumers might not work as well with current free software business models. The customer, after all, can't afford to pay for support/customization. However, pairing free software with a service (e.g., VOIP) creates a situation where free software becomes attractive again. Similarly, ad supported software (e.g., Mozilla's Google search tab) creates a situation where free software is again very attractive (due to the fact that distribution and advertising costs are very low and most revenue is pumped into R&D).


      In the end, I suspect that free software will eventually dominate almost all software production. Unless, of course, someone finds a way to make it practically illegal. This is where the real fight for free software is right now. But as long as a level playing field is maintained, I'm very happy to let the market decide for itself what it wants. If it turns out that I'm wrong, then I guess it means that the value of software freedom is less than I think it is. But I don't think that will be the case.


      BTW, I encourage you to write and distribute software under any free software license. They *all* provide the benefits that I believe are important to customers. However, in your own interest, you might want to take a look at the GPL again. I have found that the GPL provides benefits for me as an author that other licenses don't have. And I don't think that it seriously impacts my users' ability to gain benefit from the software. In fact, the "share-alike" nature of the GPL enforces a consortium-like development effort which should create a significant amount of benefit for most users. But if you don't want those extra benefits, then I agree licenses such as the new BSD license might be best.

    6. Re:Beginning of the end for open source? by Anonymous Coward · · Score: 0

      Under Sarbanes Oxley it becomes more complicated.

      For example what if the software needs to be used by a subsidary? Then you would have to give the full source code to the community and not just the subsidary. Under Oxley that would be hiding assets and your required to fully comply with the EULA.

      Its a gray area as no court has established an opinion on it. ALso what if the company is bought out? Then its a transfer and as such you need to oblige by the GPL and give it away. Internel apps should not be open sourced for obvious reasons.

  25. Re:Slashdot Hypocrisy by jbf · · Score: 1

    That's bullshit and you know it. On several occasions, pretty much every story about file trading and copyright I see posts from slashdotters saying that they believe current copyright for songs is out of touch with reality, but still wouldn't participate in illegal file trading because of the ethical issues. You don't give people enough credit. Perhaps you see those people, but you also see plenty of people with the refrain "fuck the {MP,RI}AA," I'll copy your songs/movies and there's nothing you can do about it.

    Plus, you're talking apples to oranges when you compare adhering to the GPL to adhering to what the RIAA wants with regards to songs. The GPL only lets you do more with the work than would otherwise be possible via copyright, the RIAA wants to restrict the rights of users even further than what current copyright does allow. This distinction is legally dubious. The GPL is a license, without which you couldn't even run the program in most cases (temporary copies in RAM fall under copyright law, see Lessig's "Code"), so clearly some license is necessary for all useful software. With copyright on songs/movies, you still can play them for private use from the original media that you purchased, and the {RI,MP}AA will not do anything to you for it. Beyond that, ripping, placeshifting, etc. is semi-protected by Sony v. Universal City 464 US 417 (1984). Despite the more broad-reaching intent of the {MP,RI}AA (e.g. lobbying for laws like the DMCA), the cause of action in their peer-to-peer enforcement actions is copyright infringement. Now I'm not a big fan of their litigation tactics, but I think that such suits (with better and more legal investigative techniques) are the right way to deal with file sharing. It's that same cause of action that allows the enforcement of the GPL.

    Note that I said "RIAA/MPAA copyrights," not tactics.

  26. I'm a millionaire by Anonymous Coward · · Score: 0, Insightful

    This morning I wrote on my garbage "If you collect this garbage, you must pay me $1 million dollars." and my garbage was collected!! They agreed to my license! I'm a millionaire!

    This is how the GPL works.

  27. Just out of curiosity by WindBourne · · Score: 3, Insightful

    Are you talking about American courts or German Courts. Because each country interprets the GPL, and copyrights, in very different fashion. Heck, in china, they ignore you until for some minor reason, you piss them off. Then you are shot. I think that is one of the VERY few countries that do that (for that reason).

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:Just out of curiosity by Chandon+Seldon · · Score: 1

      International differences are very important when dealing with legal questions, that's true. It's not relevant to this particular point though - the GPL text is the same everywhere, and that text operates as a copyright license.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    2. Re:Just out of curiosity by the+not-troll · · Score: 1

      Except that in Germany, being part of continental Europe, creator's right1 is used, not copyright. Of course, this doesn't really make a difference for the GPL, as creator's right is a superset of copyright. But the FSF ran into problems there, because the FSF requires assignment of copyright, but while anglo-saxon copyright can be assigned or sold, this isn't possible in the same way with creator's right (as the protection of the original author is stronger in that he can't just abdict all of his rights), thus requiring some kind of extended license.

      1 Wikipedia claims the correct translation to be moral rights, but moral rights encompass only part of creator's right, the other part being what is known as copyright. The problem with this is that the line between the inalienable rights of the creator and the rights to be sold is interpreted differently everywhere, the Berne convention nonwithstanding. Most notably, the US doesn't recognize all moral rights, thus neglecting the protection of the original creator and strenghtening the position of the distributor.

      --
      In Soviet Russia, government controls corporations.
      In Capitalist America, corporations control government.
    3. Re:Just out of curiosity by ardle · · Score: 1

      Don't worry, China will soon adopt the US system ;-)

    4. Re:Just out of curiosity by Anonymous Coward · · Score: 0

      The usual translation to English is "authors' rights", from the French droit d'auteur. This is the term used officially by the EU, but informally it is sometimes translated to "copyright", even though the common law notion of copyright isn't the same thing as the civil law notion of authors' rights: copyright includes similar pecuniary rights to authors' rights, but not any moral rights as such, though these are in some cases at least partially enforced in other legislation. In any case, I agree that translating Urheberrecht (or droit d'auteur) to "moral rights" is certainly wrong.

  28. English translation of the decision by g_adams27 · · Score: 1

    The story's link to the translated version of the decision doesn't work - probably because Google is only translating the <frameset> document, not the inner frames.

    This link should work, though

  29. Source Code by jshriverWVU · · Score: 4, Informative
    If anyone is looking for the source code it's here

    Can also check out this link for more info here

  30. Re:Slashdot Hypocrisy by WindBourne · · Score: 1

    It is our RIGHT to have that. In almost all countries, until recent times, the right of the individual to possess copyrighted material WAS enforced. What you can not do is distribute it without a license (which the GPL gives you (in fact, enforces)). How you got modded up is beyond me. Well, actually, no. I guess that I do know.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  31. You are all wrong by WindBourne · · Score: 1, Informative
    1. Copyrights are GOOD.
    2. GPL is GOOD.
    3. Skype is Good.
    4. Skype did a bad thing in trying to take something and then distribute it without meeting the LEGAL terms of it.

    This is opposed to items (say a CD) which says that you may not copy them, which is a lie since it is LEGAL to copy things for personal use. What you may not do, is to distribute them for your gains.
    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:You are all wrong by vux984 · · Score: 2, Informative

      What you may not do, is to distribute them for your gains.

      'for your gains' is not a required condition.

    2. Re:You are all wrong by L0rdJedi · · Score: 2, Informative

      The only thing Skype did wrong, which the summary doesn't mention but someone else did, is that they didn't include a copy of the GPL with the phone.

      The court said including a website address to where the source could be downloaded wasn't good enough. I'd like to know why that wasn't good enough. Is it only because the text of the GPL wasn't included?

      This doesn't look like a win for the GPL. This looks like a major pain in the ass. I didn't even know that distributing a copy of the GPL was a requirement. I've never read it fully, but I guess I just assumed that as long as you make the source code available, everything is fine.

    3. Re:You are all wrong by ericrost · · Score: 2, Informative

      Yes, the GPL says specifically that you must include a copy of the GPL to make sure the user knows his rights.

      Section 1:
      "You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you .... and give any other recipients of the Program a copy of this License along with the Program."

  32. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 0

    If copyright was restored to 14-28 years duration, the GPL software would be public domain after 14 years.
    Of course would you rather use 14 year old public domain software or GPL software?

    For the GPL to be effective, copyright duration needs only to be as long as the software is not obsolete.
    5-10 years in usual cases.

    A 95 year copyright does not benefit open source and more than a 1000 year copyright would.

  33. Re:Slashdot Hypocrisy by mrchaotica · · Score: 3, Insightful

    Like it are not, all those extensions that benefit the (MP|RI)AA also end up benefiting the open source world as well

    I assume you're talking about the benefit of copyleft (i.e., enforcing the sharing) versus plain permissive (e.g. Public Domain). The thing is, plain permissive really isn't all that much worse than copyleft. In contrast, (from the RIAA's perspective) public domain is very much worse than proprietary. So, having a longer copyleft term doesn't benefit the Free Software community nearly as much as having a longer copyright term benefits the RIAA.

    Besides, old music remains valuable to society. For the most part, old code doesn't.

    For both of those reasons, it is unnecessary for Free Software to have long copyright, and thus most Free Software advocates oppose copyright extensions. The fact that the RIAA et al. abuse copyright only confirms that position more.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  34. Stop this rubbish by rduke15 · · Score: 1

    Please refrain from posting meaningless google-translated rubbish. If you want to contribute and know German, write a decent translation or summary. Otherwise, shut up and let someone else do it. We don't need your help and can go to the stupid robot on our own, if we feel like it.

    1. Re:Stop this rubbish by Anonymous Coward · · Score: 0

      As an outsider, addressing a criticism of the summary by showing what the editor read isn't entirely irrelevant. Annoying, possibly, but probably not worthy of an overblown cry-fest.

    2. Re:Stop this rubbish by Anonymous Coward · · Score: 2, Funny

      Someone ist sehr crankisch.

    3. Re:Stop this rubbish by Anonymous Coward · · Score: 0

      Wow you're a dick. Need I remind you this isn't digg.com. Go play find the penis there.

  35. Server Error? by EmbeddedJanitor · · Score: 3, Funny

    My German is a bit rusty, but I'm pretty sure that "Server Error" is not a very good translation.

    --
    Engineering is the art of compromise.
  36. Holy Larva Batman! by fishthegeek · · Score: 2, Funny

    the case that also the program at the same place is offered for the Download: "If distribution OF executable or object code is larva by off ring ACCESS ton of CoPy from A designated place, then off ring equivalent ACCESS ton of CoPy the SOURCE code from the same place COUNTs as distribution OF the SOURCE code, even though third parties of acres emergency compelled tons of CoPy the SOURCE along with the object code." In all other cases of the software selling it is not sufficient to make the SOURCE code available only on-line one.

    It's a wonder why Microsoft hates the GPL, Balmer is afraid of GRUB(s)
    --
    load "$",8,1
  37. Fine is cheaper than this cost of advertising by coryupter · · Score: 1

    I imagine the legal penalties are small compared to the cost the advertising they would have had to pay in order to get this type of publicity for the Skype phone. To the Skype marketing team: Great work! LOL...

    1. Re:Fine is cheaper than this cost of advertising by Anonymous Coward · · Score: 0

      Are you joking? That's an appropriate thing to say about small, unknown companies who get involved in legal troubles. This is Skype. They already have an extremely strong brand name; it's not likely to be strengthened by a negative mention in tech news.

    2. Re:Fine is cheaper than this cost of advertising by martijnd · · Score: 1

      Since its SMC making these phones let me balance this marketing advantage a little.

      I actually own on of their phones ; bought it on a whim. The idea is neat -- a wireless Skype phone.

      But the battery is so bad that it basically needs to be plugged in to make a phonecall.

      And the user interface is very slow, making my 5 year old Nokia phone look like a speed freak.

      So, it attempts to look like a mobile phone -- it just lacks about 15 years of engineering by
      Ericsson / Nokia on energy saving and usability.

  38. The interesting part by jeti · · Score: 4, Interesting

    After a previous conviction, a sheet was included
    with the phone that contained URLs to the GPL-
    license and to the source code . The articles do
    not make any statement on whether the source code
    contained all modifications, but they do not claim
    otherwise.

    The court decided that providing only an URL to the
    license was not enough and that the whole license
    should have been included in printed form.

    So far, so good. Now the interesting part is that
    according to the judge, providing a link to the
    source code is only acceptable for software that
    is provided on the internet. For software that comes
    preinstalled, the source must also be delivered with
    the device.

    This decision seems extremely strange to me. It is
    not what I read in the GPL v2. Here is the relevant
    part:

    3. You may copy and distribute the Program (or a work based on it,
    under Section 2) in object code or executable form under the terms of
    Sections 1 and 2 above provided that you also do one of the
    following:

            a) ...
            b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your cost
    of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,
            c) ...

    1. Re:The interesting part by Todd+Knarr · · Score: 4, Insightful

      I think the judge looked at the paragraph a bit further on in that section where it talks about providing access to the source as a download from a server, and noted that that case is explicitly allowed only when the software itself is also distributed as a download. That led him to the conclusion that clause B that you quote, when it talks of "medium customarily used for software interchange", means exactly what it says: an actual copy on some storage medium, logic being that if it allowed downloads from servers then it wouldn't have been neccesary later to explicitly allow downloads from servers. Combine that with failing to include the license text when the license says plainly in section 1 that you must include a copy of it's text and the judge's decision doesn't seem unreasonable.

      And I know the issue of downloads of source has been discussed, and IIRC the FSF's position is that it's not acceptable on it's own. Network servers can be taken down, files on them can be removed, some recipients may not have Internet access but none of those cases lifts the obligation to provide source code. The only way a distributor can guarantee he'll always be able to meet that obligation is to be prepared to provide source on a physical medium. The case of providing downloadable source for downloadable software was actually viewed as falling under 3a, not 3b, that is source code being provided along with the software itself, which makes a world of difference in the distributor's obligations.

    2. Re:The interesting part by jeti · · Score: 1

      Well - my personal interpretation would be that providing
      a download link would be ok, but that you would be obliged
      to keep it valid over the next three years. It would be a
      violation if the link became invalid within those three
      years, but until then, no violation has occured.

      If this reasoning is not acceptable, you could still avoid
      to ship the code with the product, if you provide a note
      that you will ship it upon request. But isn't that just
      what you're doing with the URL? It's just another form of
      contact address to get your code shipped.

    3. Re:The interesting part by Todd+Knarr · · Score: 1

      And the recipient who doesn't have Internet access is supposed to use the URL how? As I noted, the FSF looked at this and concluded that just because the recipient doesn't have an Internet connection doesn't lift the distributor's obligation to provide them with source code. And a URL is unacceptable as a contact point for the same reason: it leaves recipients without an Internet connection with no usable contact point to request the source code as they're entitled to do.

    4. Re:The interesting part by Anonymous Coward · · Score: 0

      Skype was nailed for several reasons. One was that they didn't provide a copy of the GPL. Another was that they didn't provide the source code in a way in accordance with the GPL. The court apparently determined that just offering downloads for the source code of separately distributed binaries didn't cut it, and that offering downloads for the source code would only cut it if the binaries would also be distributed via downloads only. Maybe Skype could have been in the clear if they provided a written offer to ship the source code at a nominal fee, but apparently Skype missed that part of the GPL. A third issue was that the leaflet they had added to the product didn't make it clear when and for what the GPL and when the LGPL was applicable.

      Apparently a leaflet with some "BTW, there might be some GPL (huch?) and/or LGPL (wtf?) code in this product. Grap the code from here " doesn't cut it.

      Or in short, not exactly fulfilling your obligations word for word is not fulfilling your obligations at all.

    5. Re:The interesting part by jeti · · Score: 1

      Maybe that argument was valid a few years back, but
      it seems unconvincing now. I find it hard to imagine
      a person that is capable of compiling his software
      and does not have internet access.

      Also note that you can requiere the recipient to pay
      the cost of copying the source and shipping it on a
      physical medium. I can't imagine this to be cheaper
      than renting internet access.

    6. Re:The interesting part by jeti · · Score: 1

      This is all perfectly true. And I mostly agree with
      the judgement. However, I find it surprising that
      providing the source code as a download only is
      considered not to be satisfactory.

      AFAIK that is common practice. And it poses a legal
      risk even to distributors that are acting in good
      faith. I'm under the impression that the FSF acts
      very agressively on perceived GPL violations, even
      if it was not involved in this case.

    7. Re:The interesting part by Todd+Knarr · · Score: 1

      I know several off-hand. In some cases they're people I've gifted with computers but who can't afford the ongoing price of phone service. In others it's because they live in places where there simply is no Internet service. No, cel phones don't work, there's no towers in range. No, dial-up doesn't work, the phone lines don't run out that far. Yes, there are place like this around, a fair lot of them in fact.

      And even if that weren't the case, the FSF is still clear about it: you cannot place restrictions or limitations on the rights granted by the GPL. If the person simply doesn't want to get an Internet connection, they still are entitled to contact you and get source code from you. The GPL doesn't say they're only entitled to request source code if they have an Internet connection, if you attempt to add such a condition (explicitly or implicitly) then you're in violation of the GPL.

      And no, before you ask, a court won't find this particularly novel. Every company in the US, for example, is required to have a snail-mail address as an official corporate contact address for legal purposes. That requirement exists for the same reason: if you're in a position to need to serve legal papers on a company, the law doesn't require you to have telephone service to do so so the company can't require it either.

    8. Re:The interesting part by Anonymous Coward · · Score: 0

      Isn't there something in the terms which states that you may ask for the source in a physical medium?

      I'd say, let the customers mail Skype asking for a CD of the source, with changes. Also provide the URL, for convenience, but this way, anyone can at least verify that the source on the website is still valid (identical to the source on the disk).

      Requiring them to deliver a CD to everyone who buys a phone is a bit much, IMO -- put the source on a CD if you have to ship a CD anyway (for drivers, for example, or Windows software to talk to the phone), but otherwise I think the URL + the option to ask for a source CD is sufficient.

    9. Re:The interesting part by daft_one · · Score: 0

      One does wonder how many recipients of a Skype phone would be without 'net access, however ;-)

    10. Re:The interesting part by obeythefist · · Score: 2, Interesting

      Kicking a company in the nuts for violating the GPL is well and good, but when they are actively trying to make amends, isn't it bad for the FOSS community and PR in general to keep on kicking anyway?

      Using the same mechanism as the RIAA to uphold freedom is good.
      Using the same sore-winner attitude as the RIAA and punishing people for the heck of it is bad.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
    11. Re:The interesting part by Eivind · · Score: 1

      Certainly it'll be rare for someone with no internet-access to by a wifi-enabled skype-phone :-)

    12. Re:The interesting part by Anonymous Coward · · Score: 0

      Why do you find it surprising? The GPL is quite explicit on this point. You must either:

      a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

      or include a written offer to do so on request. It then goes on to say:

      If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

      The fact that the licence includes this specific paragraph would normally preclude interpreting the "medium customarily used" part of 3a) in such a way as to include internet download.

      Also, when it comes to downloads, take note of the "from the same place" restriction. If you provide binaries of GPL software on your web site, you have to also provide source code on your web site. You can't say "here's the binary, get the source from ftp.gnu.org". This is quite deliberate; it prevents large corporations from providing binaries to a million customers and dumping the source code provision onto a solitary, unpaid developer who is hosting the project on his personal web space.

    13. Re:The interesting part by itsdapead · · Score: 1

      And the recipient who doesn't have Internet access is supposed to use the URL how?

      Simply pop into a cybercafe - they'll need to go into town anyway to return their Skype VOIP phone now that they've found out what the "I" in "VOIP" stands for... :-)

      Meanwhile, what if a recipient doesn't have mains electricity? Obviously, the distributor should provide a portable generator along with the 200 5.25" floppy discs (if the recipient didn't have a CD-ROM) and an armed escort (the recipient's country doesn't have a secure postal system) with diplomatic immunity (the recipients country's goverment regards all computer discs as potential subversive literature). One hopes that GPLv3 has fixed this (in between Quixotic attempts to save the world from DRM and Patents).

      Seriously - when GPLv2 was written, internet access (at least, fast, always-on internet access) was only available to a lucky few and this argument held water. These days its available to everyb..., well, ok, a vastly larger proportion of the lucky few with access to computers.

      --
      In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
  39. Re:Slashdot Hypocrisy by jesdynf · · Score: 1

    Nope. I can. Because I'd rather see copyright destroyed -- tomorrow -- but if I can't have that? I guess I can wring some use of the stinking filth we call "intellectual property" legislation. Just 'cause I support the latter doesn't mean I wouldn't prefer the former.

    --
    Yahoo! Pipes are awesome. How awesome? http://pipes.yahoo.com/jesdynf/slashdot
  40. Only if copying is not fair use by tjstork · · Score: 1

    There's a minority opinion in US circles that suggests that copying an executable, in order to use it, constitutes fair use. So that, if I had a GPL "thing", and sought to use it, then, I could.

    --
    This is my sig.
    1. Re:Only if copying is not fair use by ThePiMan2003 · · Score: 3, Informative

      Thats actually just fine under the GPL, but when you hand that executable to someone else, thats when the GPL is invoked. If you grab some code change it and just use it for yourself you do not need to do anything, but when you distibute it, by putting it on phones you sell, or putting the binary up for download somewhere you must also include the source.

    2. Re:Only if copying is not fair use by Bogtha · · Score: 4, Informative

      There's a minority opinion in US circles that suggests that copying an executable, in order to use it, constitutes fair use.

      It's not fair use, because copies of software that are made for the purpose of using it are not covered by copyright in the first place. The law is explicit about this:

      Notwithstanding the provisions of section 106, it is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy or adaptation of that computer program provided: (1) that such a new copy or adaptation is created as an essential step in the utilization of the computer program in conjunction with a machine and that it is used in no other manner

      In short: It's not fair use (that's a different set of exemptions), but it is legal.

      --
      Bogtha Bogtha Bogtha
    3. Re:Only if copying is not fair use by MooUK · · Score: 2, Informative

      On top of that, the GPL itself specifically states that running the program is outside the license and is always permitted.

    4. Re:Only if copying is not fair use by Eivind · · Score: 1

      Yeah. And if that view wins, then it means EULAs are ignorable. (because if the copying from disk-to-ram and such which are required for normal operation aren't copyirigth-relevant, then you require no permission to use software however you please.)

      In the case of the GPL though, it's irrelevant. Because the GPL explicitly says:

      This License explicitly affirms your unlimited permission to run the unmodified Program. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.

      "Without conditions" shouldn't be all that hard to comply with, even if you *do* need to comply with it. (and if the minority-option wins trough, you can ignore even this, which makes no difference really)

    5. Re:Only if copying is not fair use by aztektum · · Score: 1

      Ok so I am not researching this, but I was under the impression, mostly from reading Slashdot stories, that you didn't have to offer up the source automatically with the binary. You do need to give it up if someone requests a copy. Is that diff in GPLv3?

      --
      :: aztek ::
      No sig for you!!
    6. Re:Only if copying is not fair use by ThePiMan2003 · · Score: 1

      You are correct. You only need to supply the source if someone asks for it. But it needs to be easy for them to get to, and in a format they prefer (IE you can't mail them a print out, or run an obfuscator over it first). However, once you have given them the source they are free to do anything they want with it, including posting it unmodified anywhere they want. As a result people generally host the source the same place as the binary, ecause it gets fewer complaints and you don't have to have someone shipping CD's or emailing or whatever.

  41. Umm I think they misread one part by Kjella · · Score: 2, Informative

    Zwar wurde dem Gerät später ein Beiblatt beigelegt, das auf die verwendete GPL-Software verwies und eine URL enthielt, wo die Quelltexte abrufbar sind - doch dies genügte dem Gericht im vorliegenden Fall nicht. Diese Möglichkeit sehe die GPL nur für Software vor, die über das Internet geliefert wird.

    Rough translation (but better than google):
    "Later a note was included with the device, which said it used GPL software and a URL where the source code is available - but this was not enough for the court. The GPL only permits this for software that is delivered over the Internet."

    Doesn't that get covered by 6 b) 2):
    "6. Conveying Non-Source Forms.

    You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
    (...)
    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (...) or (2) access to copy the Corresponding Source from a network server at no charge."

    Or maybe it didn't come as a permanent offer, in which case they might be talking about 6 d):
    "d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. (...)"

    --
    Live today, because you never know what tomorrow brings
    1. Re:Umm I think they misread one part by Anonymous Coward · · Score: 0

      Doesn't that get covered by 6 b) 2):
      It does - in GPLv3. That was one of the minor changes in GPLv3 to relax the GPLv2 requirement of a physical medium.
    2. Re:Umm I think they misread one part by againjj · · Score: 1

      It would have gotten covered, if version 3 existed when they made the decision. However, as mentioned in here, version 2 does not allow that.

  42. Re:Slashdot Hypocrisy by jbf · · Score: 1

    Irrelevant. In a perfect world you wouldn't need copyright, either. Each user would pay something between the incremental cost (close to 0) and their personal benefit, or they won't use the creative work.

    We're talking about the enforcement mechanism, and in particular, the law that allows both the netfilter author and the RIAA/MPAA to state a claim. Without copyright (or some similar idea written into a contract), there is no GPL. Period. See ESR's manifesto.

  43. Skype is good? by Cheesey · · Score: 1

    Skype is a closed network with a secret protocol. And Skype is scary. Who knows how many more security holes lurk under their many layers of obfuscation? You're taking quite a risk if you let Skype onto your network.

    I'm not saying this in order to troll, I'm just trying to correct widespread misperceptions about Skype, characterised by the belief that it's in some way better than yet another phone company. If you can, use a SIP-based IP phone instead. There are lots of SIP programs to choose from, they interoperate, if you want to dial out onto the PSTN there is a choice of providers, and you can get GPLv2 source code for the client. Far better than Skype's closed network and closed source monoculture.

    --
    >north
    You're an immobile computer, remember?
    1. Re:Skype is good? by Ricin · · Score: 1

      That blackhat link (warning: big pdf) is very interesting. So much obfuscation and encrypting, while there's no clear need for any in a piece of software like this. Scary indeed.

    2. Re:Skype is good? by hughk · · Score: 2, Informative

      Skype is hard to firewall. This means that if you can get to the internet with your PC, you can normally access Skype. I'm sure that hotels would like to stop it to force into using their expensive telephones. Mobiles aren't always an option when you are travelling overseas due to extortionate roaming rates. Skype has saved me a fortune on international calls.

      --
      See my journal, I write things there
  44. ... and also by ericrost · · Score: 1

    If you didn't read the license (I hope to God you're not distributing under it) and you use the software.. well that's at your own risk. You need to know your own obligations.

  45. Re:Slashdot Hypocrisy by Billly+Gates · · Score: 1

    Devils advocate here ...

    I would be pretty pissed if I spent 7 months writing a book with an agreement that I make some money on the sales only to have someone violate my copyright and take credit for my novel and I go broke. d

    Copyright needs to exist to make sure authors are recongized and yes, compensated for their work. If you do not agree to pay for it then dont buy it. There are creative commons licenses for creative works such as free books too. But copyright enforces credits on who writes what. Even if something is free it needs to be recognized by the author of that work.

    Many /. ers confuse copyright protection and patents. Patents are more debatable as they are given out like lolipops by the government.

  46. I wonder... by gillbates · · Score: 1

    If Microsoft will applaud the GPL developers for exercising their intellectual property rights...

    When you think about it, if Skype had misappropriated WinCE, they'd be looking at a lot more damage than just releasing their source code...

    --
    The society for a thought-free internet welcomes you.
  47. Re:Slashdot Hypocrisy by jbf · · Score: 1

    So do you only illegally distribute music that has been around for less than 5 years, or whatever you think the copyright term should be? My point is that the slashdot groupthink opposes all RIAA/MPAA copyrights, regardless of freshness. Even if you say that the legitimate copyright length is 5 years (which I could live with), then you should only cheer the enforcement of GPL for software less than 5 years old, and you should support RIAA/MPAA copyrights less than 5 years old. Since substantial P2P copyright violation consists of Top40 songs (see the ober dicta of MGM v. Grokster 545 U.S. 913 (2005)) which are almost exclusively less than 5 years old, my argument holds.

    BTW I don't think the slashdot groupthink only opposes the "draconian enforcement and perpetual lengthening of copyright expiration." I do too, and disagree with Eldred v. Ashcroft, 537 U.S. 186 (2003), but that has nothing to do with the copyright enforcements currently brought by the RIAA/MPAA. Furthermore, I don't agree with their litigation/investigation tactics, but that's not relevant to the copyright itself.

  48. Re:Slashdot Hypocrisy by Orange+Crush · · Score: 2, Insightful

    Have you ever stop to consider when software covered under the GPL will actually become public domain and no longer be bound by the terms of the GPL?

    Assuming Linus lives to at least 70 (born in 1969), the Linux kernel will not be released into the public domain for another 101 years or so. And that's only the parts he wrote. I think it's safe to say that the FOSS community will not be harmed by the release of what will then probably be an ancient and rather quaint bit of software from the turn of the last century.

  49. No conviction by hellfire · · Score: 2, Insightful

    Okay, it is Germany, and I'm going to use the definitions based under American law, but I'm 99% sure the same holds true in Germany.

    A conviction is for criminal court. Copywrite law falls under civil law. No one from Skype is going to jail and no one is going to pay a huge fine to the government. However, the organization that won this case could potentially get a tidy sum.

    Let's just pile onto the inaccuracies of the summary for this article. Let's hear it for inflamatory, add-pumping summaries!

    --

    "All great wisdom is contained in .signature files"

    1. Re:No conviction by howlingmadhowie · · Score: 1
      quoting eben moglen

      ...I decided that that instruction meant that I could begin every telephone conversation with a violator of the GPL with magic words: We don't want money. When I spoke those words, life got simpler. The next thing I said was, We don't want publicity. The third thing I said was, We want compliance. We won't settle for anything less than compliance, and that's all we want. (from the keynote address of the plone conference 2006 available here : http://www.geof.net/research/2006/moglen-notes )
  50. Re:Slashdot Hypocrisy by jbf · · Score: 1

    I wouldn't say patents are given out like lollipops. If you've ever been through a patent examination, you know that examiners are not the most skilled in the arts they examine, but they're not completely ignorant either. Patents are mainly a problem because judges are technically incapable of properly assessing Section 103 obviousness, and because 102(b)'s one-year clock is not short enough. KSR v. Teleflex should fix some of the obviousness problems. I don't know how to fix the 102(b) problem without abolishing tech patents, because technology moves too fast, and I think the time period is also too long for tech, for the same reason.

  51. Hooray for Harald! by PingXao · · Score: 2, Interesting

    This guy is waging a one-man show against GPL violators. Oh, the EFF is involved to some extent, but their effort is not Harald's. Harald, by the way, is the lead on the ipfilters project, something many /.'ers have probably heard of.

    He is swamped with submissions from folks claiming this company or that is in violation of the GPL. I submitted one myself about a year and a half ago. Nothing ever came of it. Not because the company is innocent, but because Harald has very few resources to go after the perpetrators of GPL license abuse. When a company gets reported he has to physically buy the item - most violators seem to be in the embedded Linux area - and verify the GPL violations before putting the lawyer(s) on them. He has scored some notable successes.

    But he is basically pissing into the wind. For every successful case he pursues there are 10 more that go unpunished. The real people who should be up in arms against commercial violators of the GPL are the authors who hold the copyright on the code being misused.

    Sadly, most of them can't be bothered and the violations go on. This will be the end of the GPL: developers who do not care to enforce their rights. Not v3 or v4, or Linus or Stallman or tiny paragraphs in section 1. At some point there will be a case where an evildoer will use the defense that since the copyright holder didn't pursue company X 5 years ago they should be prevented from trying to do it now. And poof! The copyright will vanish or be declared null and void and with it the GPL distribution license that goes along with it.

    Hooray for Harald! Watch out for the backspray, Harald.

    1. Re:Hooray for Harald! by Microlith · · Score: 2, Insightful

      Copyrights do not expire due to lack of enforcement, only trademarks.

      The case could easily be made that the violation was deliberately and intentionally obscured to make discovery difficult, and then the penalties could be even greater.

    2. Re:Hooray for Harald! by Kjella · · Score: 5, Informative

      At some point there will be a case where an evildoer will use the defense that since the copyright holder didn't pursue company X 5 years ago they should be prevented from trying to do it now. And poof! The copyright will vanish or be declared null and void and with it the GPL distribution license that goes along with it.

      Wow, did you drink some SCO FUD? Copyrights are never nullified because of lack of enforcement, and I dare you to find an example. Not enforcing them may limit your ability to collect damages, but at any time you can send an injunction to make them stop.

      What's needed is enforcement of copyright law:
      506. Criminal offenses
      (a) Criminal Infringement.
      (1) In general. Any person who willfully infringes a copyright shall be punished as provided under section 2319 of title 18, if the infringement was committed
      (A) for purposes of commercial advantage or private financial gain;

      2319. Criminal infringement of a copyright
      (a) Any person who violates section 506 (a) (relating to criminal offenses) of title 17 shall be punished as provided in subsections (b), (c), and (d) and such penalties shall be in addition to any other provisions of title 17 or any other law.
      (b) Any person who commits an offense under section 506 (a)(1)(A) of title 17
      (1) shall be imprisoned not more than 5 years, or fined in the amount set forth in this title, or both, if the offense consists of the reproduction or distribution, including by electronic means, during any 180-day period, of at least 10 copies or phonorecords, of 1 or more copyrighted works, which have a total retail value of more than $2,500;
      (2) shall be imprisoned not more than 10 years, or fined in the amount set forth in this title, or both, if the offense is a second or subsequent offense under paragraph (1); and
      (3) shall be imprisoned not more than 1 year, or fined in the amount set forth in this title, or both, in any other case.

      If you're using a substantial amount of GPL'd code beyond the rouge developer taking code, that should be enough to know you're willfully infringing. Being a for-profit company should be enough to prove "for commercial advantage". At which point they should be strung up on criminal charges and sent to jail like with SOX regulations. That's how it should be, note there's no minimum amount to make (3) go into effect and send them away for a year, even at a $0 "retail value" as long as you can prove *they* earned money on it.

      --
      Live today, because you never know what tomorrow brings
    3. Re:Hooray for Harald! by obeythefist · · Score: 1

      "At some point there will be a case where an evildoer will use the defense that since the copyright holder didn't pursue company X 5 years ago they should be prevented from trying to do it now. And poof! The copyright will vanish or be declared null and void and with it the GPL distribution license that goes along with it."

      That would be acceptable to me. Copyright expiring after 5 years because one person infringed it and didn't get caught?

      Awesome. Just awesome.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
    4. Re:Hooray for Harald! by arkhan_jg · · Score: 1

      Copyrights don't expire for lack of enforcement; you're thinking of trademarks becoming generic, i.e. if Hormel allow SPAM (allcaps) to become the same as spam, i.e. mass email marketing, they could lose the trademark on it, and anyone could sell spiced ham as SPAM! Just as hoover is a stand-in for vacuum cleaner in the UK as well as a specific brand, or kleenex is any tissue in the US.

      copyrights don't expire until they enter the public domain, which for software in germany is - I believe - 70 years from date of publication.

      The real people who should be up in arms against commercial violators of the GPL are the authors who hold the copyright on the code being misused.

      Well, harald is going after people distributing his own code, i.e. netfilter ;) But I know what you mean - the FSF should be much stronger going after commercial GPL violators for copyright infringement.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    5. Re:Hooray for Harald! by Eivind · · Score: 1

      Yeah. True. But I think it's a good deterrent. Over time it'll make enforcements easier. Companies aren't (generally) dumb.

      Presented with a polite letter that informs them they are in violation of copyrigth law, has references to half a dozen similar cases in the same jurisdiction, and a reasonable way of getting into compliance, most will, after a short conference with their lawyers, fold their deck and play along.

      It's a problem with international companies though. Harald does a good job of it in Germany (and deliberately doesn't publish details on companies that fold, that's part of the carrot: Fix this NOW, and we'll avoid public embarassment), but he has little deterring effect on companies in other parts of the world.

      We need similar warriors on every continent, preferably in every country.

    6. Re:Hooray for Harald! by Anonymous Coward · · Score: 0
      You (Grandparent to this post) are thinking of trademarks that need to be enforced, not copyright. That's why Linus has to to people using the Linux trademark.

      Copyright is different. For one, using a trademark is fairly obvious. Using Linux in some closed-source hardware such as a VOIP phone is not obvious - you'd have to do some technical analysis to fingerprint the OS remotely, or extract it and look for symbols/ strings that look familiar.

  52. Re:Correct terminology - probably a German speaker by Anonymous Coward · · Score: 0

    I think it is a *little* pedantic to say something like "I wish articles would get the specifics right" in this case as the poster is quite probably not a native English speaker.

  53. au contraire .... by Anonymous Coward · · Score: 1, Interesting

    Given the amount of spyware that comes along with Skype, I'm guessing they require secret proprietary code for their business (which is also a service).

  54. Re:Slashdot Hypocrisy by sumdumass · · Score: 4, Insightful

    I think your point is missing reality a little. We have a few things to keep straight.

    First and probably the most important is that not everyone who dislikes the **AAs voice their opinion for the GPL and vice versa. This means that you will see people vocal about one and not the other and when putting it all together, you see the static noise level to be about the same but totally neglect the fact that it is coming from different sources.

    Second, And probably just as important, Most of the anti **IA people I speak to are in the position because of the what and how RIAA and the MPAA are handling things not because of their right to handle them. When they run threats of legal action in order to extort a settlement from the people who would seem to have the most difficulty defending from it, something is wrong. It would seem that if protecting against copy right infringement would be important, it would be important to go after everyone doing it and not just the people who stand a chance of having a successful defense.

    I don't know of the GPL people going after widowed grandmothers who don't even own a computer and make them spend hundred if not thousands of dollars to prove that. I don't know of any GPL people falsely accusing people of infringement by infecting their computer and snooping around. I don't know of GPL people going around and writing virus and jamming networks with infect material in order to extract revenge on people and ruin their computer install because you used a legal service to do something legal.

    If and when they start doing stuff like this and everything else the **IAs are doing, I will be just as vocal against them as some are for the **IAs. As it is, I don't usually comment in the RIAAs or whatever unless it is something really bad. So don't confuse the noise level on both as being from the same people or for the same reasons, they aren't.

  55. Re:Slashdot Hypocrisy by Greyfox · · Score: 2, Insightful
    Nope, we'd cheer for an individual artist who won such a copyright case, too. The RIAA/MPAA are a bunch of ticks who live off the blood of those artists while infecting society in general with lyme disease. We like artists and programmers and copyright. We don't like ticks or lyme disease. Or Hillary Rosen, may her vagina be clogged with brillo pads. She creeps us out. We're pretty sure she's an automaton.

    We also (And I think I speak for everyone of favor of copyrights 'round here) would like to see copyrights for something made today expire sometime in our lifetime. The original copyright term was just about right. That shit was never meant to last forever. Sure that'd mean that the original windows and linux source would be going to the public domain right about now, but that's just more incentive to innovate on the part of the folks who wrote that stuff.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  56. Re:Slashdot Hypocrisy by mark-t · · Score: 1

    you also see plenty of people with the refrain "fuck the {MP,RI}AA," I'll copy your songs/movies and there's nothing you can do about it.

    Actually, there's one thing they can do about it: press copyright infringement charges. But I can almost guarantee that anyone who would even dream of saying such a refrain in front of a judge as their defense in such a case would find themselves in a bit of a pickle. So in actuality, people who would choose the path you describe are almost invariably hypocrites... as they will say one thing around their friends, but act differently if they are expected to really account for it. And really, how can you expect anyone take hypocrites seriously?

    This distinction is legally dubious. The GPL is a license, without which you couldn't even run the program in most cases (temporary copies in RAM fall under copyright law, see Lessig's "Code"), so clearly some license is necessary for all useful software.

    The copying of a copyrighted work to the extent necessary to use the work as it was intended is not an infringement of copyright.

  57. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 0

    You see the same people doing both? I doubt it. Name one. Before you answer, remember that Slashdot isn't some kind of Borg mind.

  58. Re:Slashdot Hypocrisy by Dachannien · · Score: 1

    1. The RIAA/MPAA don't hold copyrights on movies and music. Individual companies which are members of those cartels hold the copyrights.
    2. The RIAA/MPAA's member companies leverage copyrights and patents in contravention of fair use exceptions to obtain excessive control over the works in question.
    3. The RIAA/MPAA's member companies intentionally provide inequitable compensation to all but the top tier of performers, given the revenues received by those companies, all the while claiming that file sharing deprives artists of compensation.

    Many of us who oppose the RIAA and MPAA don't oppose copyright per se. We oppose the ways in which those organizations and their members abuse copyright to extract maximum profit from their customers and their artists. On the other hand, the GPL uses copyright to ensure continued free access to the efforts of programmers who give their time to provide the rest of us with useful resources, in many cases forgoing compensation altogether.

  59. Definitions... by ThosLives · · Score: 1

    Hrm. I just had an interesting thought which applies here but I'm sure folks have covered already. Somewhere.

    So, you can copyright source code, no problem. I know there is a bit of confusion about the meaning of the term "derivative work" and here's an example.

    Let's say I have a trivial program, say, "Hello World" or something like that. What exactly is the copyrighted bit here? Is it the source - that is, the exact language representation used - say, C++ or Pascal or Assembly? Or is it the instructions generated by that source? How many different source code versions of "hello world" can compile into the same executable? Does that mean they are all the same source code or not?

    The reason I'm not sure it's the "instructions generated by that source" is because that means that the copyright can extend to things that do not yet exist. Let's say I have a copyrighted bit of code. Then let's say that some guy comes along 3 years later and writes, for a brand-new architecture that didn't exist when I obtained my copyright, in a different language, some library that performs the functionality of my code and compiles it. Now let's say someone compiles my code on the new machine and the compiled version of my library is the same as the "independently developed" code (which is possible in certain cases).

    So here's the question - did the guy developing for the new architecture violate my original copyright or not?

    I honestly don't know how to answer that question.

    It's quite important, because if you can only copyright source code and not the binaries - then that is an interesting situation. If the copyright really applies to the compiled binaries that's another interesting situation. It seems, however, that the current take is that it applies to both things simultaneously.

    Another odd situation - what happens if I reverse-compile a copyrighted program and then distribute the reverse compilation. I generated a new, different work than the original source code and a different "work" than the compiled binary. Or did I? Is that different than me going to a museum and sketching The Scream? So did I violate a copyright there? Another tough question.

    The only conclusion I can make at this point is that the artificial constructs of copyright need some work. I wish I had an answer that would make everyone happy though (the only one I can come up with is a semi-popular one: that intellectual property, not being an economically scarce good, should not enjoy the status of "property" at all. For those curious, I think the things that are economically scarce are the ability to generate new information, the ability to transfer information, and the abilities to interpret and use information. I think those are the things on which our economy should be based, not the information itself.)

    --
    "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
    1. Re:Definitions... by Todd+Knarr · · Score: 1

      Ask yourself this. Suppose you wrote a book. Suppose I go and translate it into another language (without a license from you) and begin selling copies. Suppose I record someone reading it onto audio tape and begin selling copies. Suppose I run it through a scanner and turn the scanned images into a PDF and begin selling it. What does copyright law hold on those scenarios? Answer that and you've answered your questions.

      Short form, copyright applies to the source code. That copyright carries over into any derivative works such as a compiled binary.

    2. Re:Definitions... by ThosLives · · Score: 1

      The question is, do I deserve compensation for translating the work into a foreign language when I didn't do that translation?

      The way I see it, the translator created a new actual work by changing the language. Sure it has the same story or whatever as the original, but the value that guy added is the translation, not the idea.

      That's why I said the things of value are the creation of new ideas, the means to distribute them, and the ability to use them. The ideas themselves are not very valuable, so copying them - I don't care. I only start caring when I don't have a job because someone said they performed work that I actually did and they get hired instead of me.

      If I want to make money off publishing my ideas, that's a different story. Think of it this way: people don't pay money for the ideas in a book, they pay for a book because that's how they get "access" to the ideas. Regarding research: the "idea" probably exists in the physical universe but it's hard to get at, so people pay for the expediency in getting at it - not the idea itself.

      With the "communications age" or whatever we're in now, people will pay for network access or whatever to get at ideas; they won't pay for the ideas themselves. Yeah, you may think there's no difference, but I'd disagree. That's not saying either of us is correct; these are all opinions anyway.

      --
      "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
    3. Re:Definitions... by Todd+Knarr · · Score: 1

      Save for one problem: copyright law vests the sole right to create that new work in the original author. The translator had no right to create his new work regardless of how much effort went into it or how much value it created. It's the same thing as someone stealing money and using it to start a successful business. When all's said and done, he still stole the money and the law isn't going to leave the fruits of that crime in his hands.

    4. Re:Definitions... by DragonWriter · · Score: 2, Informative

      So, you can copyright source code, no problem. I know there is a bit of confusion about the meaning of the term "derivative work" and here's an example.

      Let's say I have a trivial program, say, "Hello World" or something like that. What exactly is the copyrighted bit here? Is it the source - that is, the exact language representation used - say, C++ or Pascal or Assembly?

      Certainly.

      Or is it the instructions generated by that source?

      Provided that you (the copyright holder) generate them (by running the compiler/linker/etc.), certainly, they are included as part of the original copyrighted work (or perhaps another copyrighted work, the distinction is probably unimportant in most cases, though for copyright time limits it may be important if the source is recompiled differently at a later time.)

      How many different source code versions of "hello world" can compile into the same executable?

      An infinitely large number. But copyrights aren't patents, so if someone else happens to generate the same executable from their own independently developed source that I developed from my copyrighted source, we could both have copyright on our own soure, and each have a independent copyright to the identical executable.

      The reason I'm not sure it's the "instructions generated by that source" is because that means that the copyright can extend to things that do not yet exist.

      Copyrights do extend to things that don't exist at the time the original work is created; all derivative works, for instance, by definition do not exist when the original work is created, yet are covered by copyright.

      Let's say I have a copyrighted bit of code. Then let's say that some guy comes along 3 years later and writes, for a brand-new architecture that didn't exist when I obtained my copyright, in a different language, some library that performs the functionality of my code and compiles it. Now let's say someone compiles my code on the new machine and the compiled version of my library is the same as the "independently developed" code (which is possible in certain cases).

      So here's the question - did the guy developing for the new architecture violate my original copyright or not?

      No, because while identical, the code is not in fact derived from your original expression. This is where copyrights differ from patents (aside from the kind of things they apply to), because the latter covers even independent inventions, while copyright only protects copies, not coincidences.

      It's quite important, because if you can only copyright source code and not the binaries - then that is an interesting situation. If the copyright really applies to the compiled binaries that's another interesting situation. It seems, however, that the current take is that it applies to both things simultaneously.

      It applies to both, but not to independently developed works, however similar (though proving that a work is independently developed may be a challenge if the similarities are so strong as to make coincidence seem unlikely.)

      Another odd situation - what happens if I reverse-compile a copyrighted program and then distribute the reverse compilation. I generated a new, different work than the original source code and a different "work" than the compiled binary. Or did I?

      You did create a new, different work. However, it is a derivative work, and thus probably violates copyright unless some special exception applies.

      Is that different than me going to a museum and sketching The Scream?

      No, not really.

      The only conclusion I can make at this point is that the artificial constructs of copyright need some work.

      Given your admitted ignorance of copyright,

    5. Re:Definitions... by countach · · Score: 1

      Ok, copyrights apply to derivative works. But how do you prove it is a derivative work if they won't tell you?

    6. Re:Definitions... by DragonWriter · · Score: 1

      Ok, copyrights apply to derivative works. But how do you prove it is a derivative work if they won't tell you?


      The same way you prove most things in a legal dispute, with evidence which tends to reinforce that conclusion even if it is isn't conclusive. Legal proof isn't the same thing as logical proof.
    7. Re:Definitions... by maz2331 · · Score: 1

      It's a little complicated, but here's a quick stab at it...

      First, remember that copyright only protects the "expressive content" of the work. "Functional" elements are not protectable. However, since it's almost impossible to separate the two, it almost always results in the entire work being copyrighted.

      Your case of the porting to a new archetecture is interesting. If he totally rewrote the code to do the same thing, and it's not substantially the same as yours, then he's in the clear. The "functionality" and "underlying facts" are what he used, not the "how I said it" of your code.

      It's kind of like the argument Lexmark made trying to tie their toner cartridges to the DMCA by setting up a little code snippet in the cartridge that had to be read in order for the printer to use the cartridge. The court rejected that and found Lexmark's little snippet was "functional" in nature, not "expressive", and tossed them out on their ear.

      One big thing the courts also recognize is that portions of the work that are dictated by outside standards and requirements are not protectable either.

    8. Re:Definitions... by ThosLives · · Score: 1

      Yes, but take away "the law" and what really prevents a person from making a copy?

      If I copy, (yes, this is a dead horse) the original copy remains; nothing is diminished and society has more copies of whatever. If I steal then the original is no longer available - I have removed the resource from some other place.

      The fundamental arguing point is whether things like "vested rights" are legitimate scarce goods or not: because there is nothing in the physical universe which actually makes them scarce; the scarcity is by social agreement only.

      The balance of the system is this: if I don't get compensation for generating new ideas, regardless of who or how many people copy them, I will stop generating those ideas and do something else.

      The problem with the current system is that it is capable of limiting innovation. Not so much in copyright but in patents, the patents are often so broad as to prevent all reasonable means of solving the same problem; this means that innovation is halted and resources are wasted because of artificial constructs. In an effort to attempt to guarantee "research cost recovery" the system - likely inadvertently - limits innovation in a like field because there are sometimes no ways to work around a patent.

      That's really the fundamental problem - things like music or video I don't really care about - the real value there, in my opinion, is in live performances anyway (which cannot be copied).

      Anyway, another basic point I have is that yes, we have a current set of laws, but nobody has ever said that the current law is "correct". That, however, is politics; I try to keep things as technical as I can...

      --
      "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
    9. Re:Definitions... by Todd+Knarr · · Score: 1

      Fallacy: that physically taking something is the only way to harm them. If someone steals your personal information (SSN and such) and uses it to take out a bunch of loans in your name, then defaults on them, they haven't taken anything from you but they've definitely harmed you nonetheless. They did the hard work, you want to make your profit based on that work without doing it yourself and without compensating them. Not kosher.

  60. Re:Slashdot Hypocrisy by enjo13 · · Score: 1

    Isn't that the problem with the GPL? It's not a 'free' license anymore than the most restrictive RIAA EULA. The GPL attempts to maximize the benefits of source for the community, the RIAA attempts to maximize benefits for it's member companies. At the end of the day, neither are particularly free.

    --
    Turn s60 photos into awesome videos with mScrapbook for all S60 3rd edition phones!
  61. Re:Slashdot Hypocrisy by cpt+kangarooski · · Score: 1

    The GPL is a license, without which you couldn't even run the program in most cases (temporary copies in RAM fall under copyright law, see Lessig's "Code"), so clearly some license is necessary for all useful software.

    That's not quite correct. When software is loaded into RAM, that RAM is a copy for copyright purposes (and making copies is the sort of thing that's generally prohibited). However, if you own the copy of the software you're starting from, then this is permitted under the law without a license by 17 USC 117. Ditto for making backups. But of course, those only apply to software, and only for copies that you own; not for any old thing that could be loaded into RAM.

    Indeed, the GPL makes it clear that it does not apply to mere use of the software. That would seem to fall under a combination of 117 and an implied license on the part of the copyright holder.

    --
    -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  62. Support your local GPL enforcer! by Anonymous Coward · · Score: 2, Informative

    Seriously, looking at http://gpl-violations.org/support.html everyone can see that Harald is asking for help in maintaining the site - and the site badly needs it.

    So, instead of talking about the GPL on /. why not help running gpl-violations.org?

  63. Copyrights are like guns... by langelgjm · · Score: 1

    Without copyright (or some similar idea written into a contract), there is no GPL.

    That's basically what I said. As for your original comment, I see nothing hypocritical or contradictory about opposing the MAFIAA's use of copyrights while supporting legal action that enforces the GPL - the two are worlds apart. What's irrelevant is the fact that they fall under the same legal rubric. The MAFIAA's extortion and blatant abuse of the legal system vs. enforcing the GPL with a properly filed suit against a party who is selling the product for commercial gain = apples and oranges.

    Besides, the principles for which each party is using copyright law are completely different. The MAFIAA want to exercise perfect control over their product to the great detriment of society at large, whereas the GPL attempts to benefit society at large by making the source code available, among other things. It's as if they're both using guns - supporting the use of a gun in one case doesn't mean you have to support its use in every case.

    --
    "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
  64. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 0

    I'm not sure what you mean by "recent times". Certainly in the US after the introduction of the copy machine, it was not legal to borrow a book from the library and copy every page. That isn't "fair use".

  65. Re:Slashdot Hypocrisy by Volante3192 · · Score: 1

    My point is that the slashdot groupthink opposes all RIAA/MPAA copyrights, regardless of freshness.

    That's not the general feeling I've gotten. It's the tactics they use that produce the most vitrol. Copyright on the whole is worth having, but not Life+75. ( http://science.slashdot.org/article.pl?sid=07/07/1 3/1233201 for one argument)

    Although, I'd grant of late there seems to be a further tipping against the RIAA but it's more as an application of copyright misuse than abolishing copyright right out.

  66. GPL blah blah blah by forgoil · · Score: 1

    When can I buy a Wifi phone without an OS? And then put whatever is out there on it? Perhaps... a linux distro with hardware support? THEN it would be a heck of a lot more interesting. Because whether or not they breach the license or not won't change anyone but the lawyers lives. I hardly think that anything in that skype phone is worth getting back to be honest.

    I want an open piece of hardware, because I quite frankly don't care about 1G, 2G, 3G, 4G, nor any-freakin'-G. I want Wifi, only, and sensible sync and everything else.

    Or they can just throw GSM/whatever-G out of the iPhone and fill it up with WiFi software instead of what you get from GSM (Call, SMS). That would work outside of the US, without the need to crack it, and make me happy :)

    1. Re:GPL blah blah blah by HatofPig · · Score: 2, Interesting

      You have read about the OpenMoko Neo 1973 open-platform cell-phone, right? The developer version (sans-wifi) is available now, and the consumer-ready version will ship in October. It's linux-based, and 100% open-source (both hardward and software) for a price comparable to the iPhone.

      --
      Silicon & Charybdis McLuhan Kildall Papert Kay
  67. Conflict and Chaos in the broadband Mind! by Anonymous Coward · · Score: 0

    "Not everyone has access to the internet."

    Are you certain? I could swear everyone's "new and improved business model that you should adopt or die" assumed everyone had high-speed internet?

  68. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 0

    At first it was not, Then later, they added a bit of money to each copy that was given to the publishers, and then it was considered fair use.

  69. Slashdot Youth. by Anonymous Coward · · Score: 0

    "Besides, old music remains valuable to society. For the most part, old code doesn't."

    The people running mainframes wouldn't agree with you.

    "For both of those reasons, it is unnecessary for Free Software to have long copyright, and thus most Free Software advocates oppose copyright extensions."

    So all that means is that under Queen Anne terms GCC would have been public domain in 2001, and Skype came out in 2003, just in time. Good thing there were no copyright extensions to spoil that GPL "spirit".

    1. Re:Slashdot Youth. by mrchaotica · · Score: 1

      So all that means is that under Queen Anne terms GCC would have been public domain in 2001, and Skype came out in 2003, just in time. Good thing there were no copyright extensions to spoil that GPL "spirit".

      No, the very first version of GCC would be public domain. Newer versions (i.e., ones created in 1993 or later) would still be under copyright (and the GPL).

      And that's good enough -- after all, why shouldn't old versions of GCC be Public Domain?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Slashdot Youth. by Anonymous Coward · · Score: 0

      "No, the very first version of GCC would be public domain. Newer versions (i.e., ones created in 1993 or later) would still be under copyright (and the GPL)."

      The '93 version would have expired this year. Remember NO extensions. That's why I said "Queen Anne".

      "And that's good enough -- after all, why shouldn't old versions of GCC be Public Domain?"

      Only if you think a fourteen year window is adequate enough to protect your GPL spirit?

    3. Re:Slashdot Youth. by mrchaotica · · Score: 1

      The '93 version would have expired this year.

      Whoops -- off-by-one error. s/"1993 or later"/"later than 1993"/g.

      Only if you think a fourteen year window is adequate enough to protect your GPL spirit?

      Sure, why not?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  70. Hm, no a german court did _not_ "upheld" the GPL by angel'o'sphere · · Score: 2, Interesting

    I started reading the threats but stopped after the first few *5* rated articles ;D

    What me rely wonders is this wording A German court has once again upheld the GPLv2 .

    No! A german court did not upheld the GPL. No court is interested in the GPL. the court honoured copyright law. The authors of the code in question are the copyright owners. The company distributing the code is not a copyright owner. The license is completely irrelevant.

    Notpicking mode on:
    A license could be void if it contained illegal terms, like: you agree to hand over your first born son, and his first born son and also his up to the 17th generation to follow to (insert your name here) ...
    In this case the license would be void. Not copyright! You still had no right whatsoever to distribute the code / IP of the legal owners.

    The court did not uphold the GPL. It only decided that Skype violated the GPL and in doing so violated copyright law If you violate a BSD or MIT license you violate copyright law as well.

    To uphold a license you would need to challenge the legal-ness of the license. So instead of suing Skype for breaking copyright law you would need to sue the author over using an illegal license. However there is no real applicable law here. You could construct a case probably by having a license that also encourages murder and rape ... like: by using this software you also a accept that the nazis did not committed a holocaust. In germany claiming in public that "the nazis did not commit the holocaust" is a legal offense. So having a license including legal offenses you had a license that would be void or tangible. But still you could not distribute the code of the copyright holder ... because your act of distribution has nothing to do with the license but only with copyright.

    angel'o'sphere

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  71. Slashdot Downloads. by Anonymous Coward · · Score: 0

    "But of course, those only apply to software, and only for copies that you own; not for any old thing that could be loaded into RAM."

    You left out the exception for web pages loaded into browsers.

    1. Re:Slashdot Downloads. by cpt+kangarooski · · Score: 2, Informative

      There isn't one. When you make a copy of a copyrighted web page in order to browse it, as you necessarily must, if only into RAM, you had better either have a license (either express or implied), or an applicable exception, or else you're infringing. So say the courts.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  72. WiFi Phones, got OS called "Limux" or something. by Anonymous Coward · · Score: 0
    How about:

    Nokia N800 - about $350

    Nokia 770 (a little older, slower, cheaper) - about $150

    Both run Linux. OK, there are some binary-only driver modules.

    Of course, if money is no object, you can always get yourself an $800 Zaurus, too.

  73. Re:Slashdot Hypocrisy by DavidTC · · Score: 1

    This distinction is legally dubious. The GPL is a license, without which you couldn't even run the program in most cases (temporary copies in RAM fall under copyright law, see Lessig's "Code"), so clearly some license is necessary for all useful software.

    You're a moron. Copyright law explicitly allows program copies made in memory, and thus you need no 'license' at all to use computer programs.

    --
    If corporations are people, aren't stockholders guilty of slavery?
  74. Re:Slashdot Hypocrisy by Mr2001 · · Score: 1

    I would be pretty pissed if I spent 7 months writing a book with an agreement that I make some money on the sales only to have someone violate my copyright and take credit for my novel and I go broke. Well, I'd be pretty pissed if my favorite sports team lost the Big Game, or if I found out my girlfriend was cheating on me. But "pissed" doesn't mean "I get to drag their ass to court".

    Also, taking credit for someone else's work is fraud. If I try to sell something you wrote by claiming I wrote it, then I'm lying to my customers, just as if I were trying to sell a magic rock by claiming it'd cure cancer. You don't need copyright laws in order to prosecute fraud - you just need laws against fraud.

    But copyright enforces credits on who writes what. It may serve that purpose now, but the purpose can be served just as well without copyright.
    --
    Visual IRC: Fast. Powerful. Free.
  75. Skype was NOT convicted by voltheir · · Score: 3, Informative

    RTFM
    They convicted SMC, who makes a Skype phone, of the GPL violation because they didn't include the source code with the phone. NOT skype

    how can every slashdot mod and user be completely wrong?

    1. Re:Skype was NOT convicted by ElvisGump · · Score: 1

      RTFM They convicted SMC, who makes a Skype phone, of the GPL violation because they didn't include the source code with the phone. NOT skype Wait, what? SMC? Isn't that the company that Richie Cunningham's dad shills for on late night TV?

      how can every slashdot mod and user be completely wrong? Because we don't care enough.
    2. Re:Skype was NOT convicted by BeeRockxs · · Score: 1

      No, they convicted Skype, who are selling the SMC phone, and hence distributing the GPL software included in it.

  76. Re:Beginning of the end for open source? No by WK2 · · Score: 1

    Yes, lots of companies have policies against using free software. The first word that comes to mind for them is "retarded." The second was "paranoid." But really, these people are just seriously confused. They may have assumed their whole lives that you can't get something for nothing. It's tough to fight deeply held beliefs like that, even using logic and reality.

    I've observed that these people, and companies are gradually phasing out. It's natural selection. The companies that learn how to cut costs, and the managers who implement good cost cutting polices, stay, while the companies who refuse, will die from lower margins, and the managers who never get a clue, will be fired.

    --
    Write your own Choose Your Own Adventure. http://www.freegameengines.org/gamebook-engine/
  77. Here I define "GPL violation" by tepples · · Score: 1

    On the contrary, a standard legal action against someone not in compliance with the terms of the GPL would be a simple copyright infringement case; the onus is on the defendant to show that they had a valid license (and met its terms). Then we define a "GPL violation case" as a copyright infringement case in which the alleged infringer's key defense is that the copyright owner permitted the alleged infringer's action under the GNU General Public License. Everyone knows what you mean.
  78. *clap* *clap* by Anonymous Coward · · Score: 0

    Good job Harold!

    The rest of you GPL coders who chest thump about how 'you are protected' - you lack the 'nads of Harold.

    You had a chance to stand up for your rights - back when Virgin was violating the GPL with the Virgin Webplayer.

  79. Support your local "Bits" enforcer! by Anonymous Coward · · Score: 0

    Sounds like a plan to me. Maybe Harold and a bunch of volunteers will have better luck controlling bits than the entire entertainment industry.

  80. 17 USC 117 is a U.S. law by tepples · · Score: 1

    However, if you own the copy of the software you're starting from, then this is permitted under the law without a license by 17 USC 117. In the United States. What corresponding exemption applies to the other 95 percent of the global population? In fact, section 28A of the British copyright law is bass-ackwards from 17 USC 117: it applies to almost everything except computer programs. Instead, section 50A permits necessary copying of computer programs by anyone who "has a right to use the program". I'd take a guess that this includes the owner of a copy, as in 17 USC 117, but I'd need someone more familiar with the wording of UK copyright law to confirm this.
  81. Re:Slashdot Hypocrisy by tepples · · Score: 1

    Without copyright (or some similar idea written into a contract), there is no GPL. Without copyright, there is no ban on trading commented disassemblies of formerly proprietary software on Usenet comp.sources.*.
  82. Freedom vs "Freedom" by Pfhorrest · · Score: 1

    In other words, usually when people violate copyright it's through an act that increases the spread of the information, and prosecuting them for it would restict that spread. In contrast, when people violate copyright by failing to abide by the GPL, they themselves are restricting the spread of the information and prosecuting them restores it. Skype is in no way restricting the spread of information - they simply aren't spreading it themselves. Skype distributing a compiled version of the code in question, but not distributing the source, does not prevent anyone who has the source from further distributing it.

    This argument is as old as the GPL itself, and while I know so many people hate it, I'm finding the analogy between the GPL and communism more apt all the time. The GPL is in the same boat as proprietary licenses in precisely the way that communism is in the same boat as merchantilism: both employ illiberal restrictions on people's freedom. The only thing that makes the GPL (or communism) any nobler than a proprietary license (or merchantilism) is the egalitarian nature of the ends it has in mind, but it hardly seems like sacrificing liberty for equality is any better than the converse.

    Nobody is entitled to see another's source code, any more than they are entitled to the products of another's labor; nor are they entitled to have others propagate their code for them. However, in a world without any "intellectual property" at all, there'd be little reason for anyone to ever withhold their code from someone who wanted it. So if you truly want freedom, of both people and code, you should want a world without copyright; and you can participate in (and help to create) such a world right now, by putting your code in the public domain.

    (For completeness' sake with the economic analogy, though it's getting a bit off topic here, I also believe that a [significantly modified] libertarian economy can create a situation free from any coercion or forced redistribution wherein people have little to no incentive to own more than they can make use of and so become inclined to sell it off instead, creating a buyer's market [high supply, ergo low prices] wherever you have many people with much more than they need, naturally redistributing wealth with no force or coercion. And I believe that this can be accomplished in the same way that truly free [not Stallman's "Free"] software can be: by having the government do *less*. Whereas for software freedom we need to abolish the validity of copyright, I believe that for true economic freedom, we need to abolish the validity of rent [and consequently interest] contracts. Either lend [not loan] something to someone gratis, or sell it to them [and maybe buy it back later]; but you can't give someone something, charge them money for it, and then expect to get it back later *and* still keep the money. Yes, I know all about the time value of money and how debtors and lessors are being compensated for their inability to use it while it's lent out, but if you can't afford to be without whatever you're loaning/renting out, then hang on to it, or sell it for enough to compensate you for your loss of it; and if you can afford to be without it, either let others use it if you feel like being nice, or sell it off for whatever the market will bear. Just having excess wealth already should not afford you a special ability to extract more wealth from those who have less).
    --
    -Forrest Cameranesi, Geek of all Trades
    "I am Sam. Sam I am. I do not like trolls, flames, or spam."
  83. Re:Slashdot Hypocrisy by tepples · · Score: 1

    Isn't that the problem with the GPL? It's not a 'free' license anymore than the most restrictive RIAA EULA. The GPL attempts to maximize the benefits of source for the community, the RIAA attempts to maximize benefits for it's member companies. At the end of the day, neither are particularly free. But "the community" can consist of more voters and taxpayers than "it's member companies".
  84. DirecTV needs a swift kick too by Zondar · · Score: 1

    Their HR20 receiver appears to use linux, yet nothing that even looks like it complies with the GPL...

  85. Does GPL copyright expires? by kunther · · Score: 1

    Does GPL copyright expires and becames real public domain, as happens with the other copyrights?

    1. Re:Does GPL copyright expires? by gd2shoe · · Score: 3, Insightful

      Of course it does. The only thing that makes the GPL enforceable is copyright; when the copyright expires, it passes into the public domain just like everything else.

      I take that partly back. It more completely passes into the public domain that a vast majority of software, because the source is easily available (copyright expiration wont make companies release the source).

      It will (of course) be many years before any software copyrights expire (here in the States at least).

      --
      I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
    2. Re:Does GPL copyright expires? by Corporate+Troll · · Score: 1

      Yes, it does.... If you've got, like 95 years after the autor dies or so... (Don't know the exact values)

    3. Re:Does GPL copyright expires? by lessermilton · · Score: 1

      Frankly, I find that hard to believe.

      Years? Decades maybe... centuries? probably

      --
      I wish I had a witty .sig
    4. Re:Does GPL copyright expires? by ardle · · Score: 1

      I suppose copyleft lasts as long as the software does ;-)

    5. Re:Does GPL copyright expires? by gd2shoe · · Score: 1

      "It will (of course) be many years before any software copyrights expire (here in the States at least)." As it stands right now, that means decades for most software.

      --
      I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
    6. Re:Does GPL copyright expires? by gd2shoe · · Score: 1

      More specificly, copyleft lasts as long as copyright does. :-)

      --
      I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  86. Tested by Tom · · Score: 1

    So much for the usual "the GPL has never been tested in court" argument.

    Since this is the 2nd time, I assume it now rests 12 feet under?

    --
    Assorted stuff I do sometimes: Lemuria.org
  87. Re:Slashdot Hypocrisy by SerpentMage · · Score: 1

    There is no difference in the RIAA/MPAA and the Free Software Foundation. You talk about fair use. If a company used fair use in their software would you find that acceptable? For example, let's say that Microsoft were to use parts of the scheduler in their Windows software. That could fall under fair use since the scheduler is a small piece in comparison to the everything else. How would you feel if companies do that?

    After all when you use fair use you are not giving all of the money that the copyright license could earn.

    My point has been since the Free Software Foundation dictates their terms using the copyright law, the RIAA/MPAA have the same right to dictate their terms. You might not agree with the RIAA/MPAA terms, and might agree with the FSF, but that is beside the point. The main argument is that if you support strong support of the GPL like the German courts did, then you have to support strong use by the RIAA/MPAA. Doing otherwise would be hypocritical.

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
  88. Never tested by Anonymous Coward · · Score: 0

    It's like the creationists. Whatever proof you have of court validation (or "missing link" fossil), it's never the RIGHT sort of test (or there's another gap). For one, it was that it wasn't tested in the US. Later they also mentioned that it didn't test the GPL but copyright.

  89. grammar nazi invokes Godwins law .. by rs232 · · Score: 1

    "The court did not uphold the GPL. It only decided that Skype violated the GPL and .."

    "You could construct a case probably by having a license that also encourages murder and rape ... like: by using this software you also a accept that the nazis did not committed a holocaust"

    was: Re:Hm, no a german court did _not_ "upheld" the GP

    --
    davecb5620@gmail.com
  90. MIAA/RIAA Goodness by Anonymous Coward · · Score: 0

    GPL is the very reason I will continue to stay away from open source. Stupidity at it's finest.

  91. Good! by maz2331 · · Score: 1

    It's always great to see the greedy bastard "PHB" types get blasted by the same "IP Protection" scheme they are trying to use against everybody else. There's a lot of these types out there who try to steal anyone else's work while attempting to protect and lock down their own. GPL code is absolutely NOT public domain. It's licensed, with the fee being to "play nice" with the developers and end users by releasing source. Anyone who doesn't like those terms is free to use a commercial offering instead. Just ignoring the terms is illegal, and it's great to see these copyright criminals getting busted for it. Either we have protection or we have open. What we can't have is open for corporations to use and protection for their works. One standard please. I have to admit a real admiration for Moglen and the rest of the guys who figured out this hack of the protectionist copyright laws. It's absolutely brilliant, and so far impenetrable.

  92. We need a new acronym... IASNAL by pjr.cc · · Score: 1

    I Am Soooooooooooooo No a Lawyer.

    Reading all the legal mumbo jumbo above cast my mind back a number of years ago when I way trying to figure out if and how a project i was working was being distributed legally given that I wanted to make it GPL. I made the software Free for all in the end because I read thru the gnu.org site that tries to explain the gpl and left feeling that I knew less then when I started.

    There was even a little quiz at the end to "test" your knowledge of the GPL and regrettably i cant find it now but I do remember I failed miserably.

  93. Re:Slashdot Hypocrisy by Dachannien · · Score: 1

    For example, let's say that Microsoft were to use parts of the scheduler in their Windows software. That could fall under fair use since the scheduler is a small piece in comparison to the everything else.

    Straw man. Your example of fair use isn't actually fair use.

    The main argument is that if you support strong support of the GPL like the German courts did, then you have to support strong use by the RIAA/MPAA.

    False dichotomy. Support of the GPL and opposition of the ??AA are not mutually exclusive.

  94. They didn't have to ship the source by jgoemat · · Score: 1
    They had two options (under GPL v2) when they distributed the object code with their phone:
    1. Accompany it with the source code
    2. Accompany it with a written offer (valid for at least three years) to distribute the source code for no more than the cost of physically performing the source distribution
    If they were only distributing their object code on internet however, they could have just made the source code available in the same place. That counts as distribution even if the user doesn't download the source code at the time. They could have downloaded the source code before the object code if they wished. If you do this, you can take the object code and source code off-line at any time and not be obligated to do anything further.
  95. Nice try by jgoemat · · Score: 1

    But you are not copying or distributing the Program. Either the doctrine of first sale or fair use would be in effect. In addition, Fred would have no standing to sue unless he was an author of some of the code. It's not the people receiving the phones that can sue, but the authors of the code that is being copied without adhering to the GPL.

    1. Re:Nice try by Brandybuck · · Score: 1

      But you are not copying or distributing the Program.

      But the program was on the phone! I've distributed it! That is what this case is about. In addition, this case was tried in Germany, where you can sue someone for violating the copyright of another.

      --
      Don't blame me, I didn't vote for either of them!
    2. Re:Nice try by jgoemat · · Score: 1

      But the program was on the phone! I've distributed it!
      Distribution isn't handing one object to someone. I think the relevant definition for copyright is:

      3. to promote, sell, and ship or deliver (an item or line of merchandise) to individual customers, esp. in a specified region or area.
      When I loan a book to a friend I am not distributing copyrighted content, I am loaning my copy of the book to a friend. Distribution requires multiple copies and handing them out to multiple parties or for delivery to multiple parties.
    3. Re:Nice try by Brandybuck · · Score: 1

      What part of "individual" in your definition don't you understand?

      --
      Don't blame me, I didn't vote for either of them!
    4. Re:Nice try by jgoemat · · Score: 1

      Hmmm... Do you not understand that the "s" on the end of customers makes it plural? It does not say an individual customer. Distribution is handing multiple copies out to multiple customers individually. That differentiates it from multiple copies going to a single customer. And what part of loaning your phone to a friend so that they can make a call includes promoting, selling and shipping or delivering? Handing your phone to someone or even selling it to them is not distribution. It is not copying either, as there is still only one copy of the copyrighted material.

  96. Amerikka by Anonymous Coward · · Score: 0

    Yeah, China and the USA. Except that in USA they don't shoot the people there.. They rather bomb the shit out of hundreds of thousands of Iraqi/Afghanistani/Vietnamese etc civilians. Boohoo.