Slashdot Mirror


Hamstersoft Ebook App Rips Off GPL3 Code, Say Calibre Devs

Nate the greatest submits news of a claim that a recently released ebook application from Hamstersoft is actually built from code lifted from calibre, the ebook library app. He writes "It turns out that one calibre contributor is now reporting that his code was pirated for Hamstersoft. You can find the full details over on John Schember's blog. It's technically complicated and quite long. You can also find a non-technical summary. The short-short version is that Hamstersoft needs to give away a complete source code for the Hamstersoft Ebook Converter because that app uses parts of calibre, which is licensed under GPL v3. John gave Hamstersoft a month to comply and they did not. Now that app is clearly a GPL violation."

283 comments

  1. Sigh... by MightyMartian · · Score: 2, Insightful

    Queue the GPL critics praising the BSD license. The short-short-short of it is that if these fuckers didn't want to have to abide by the GPL3 license, they shouldn't have been lazy pieces of worthless stealing shit and wrote their own fucking code.

    I hope they get sued into fucking oblivion.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
    1. Re:Sigh... by Anonymous Coward · · Score: 3, Insightful

      Um what? GPL, BSD, WTFPL whatever, it's still a license breach and GPL vs. BSD has nothing to do it. We argue that GPL doesn't achieve it's stated goals regarding freedom, how does that relate to someone breaching a license? That it wouldn't have occurred under BSD? So what? It's not BSD licensed and it's clear by picking the GPL that the author wants the things the GPL provides which the author has every right to do, even a BSD fanboi can't argue with that. You're post is flamebait.

    2. Re:Sigh... by Stiletto · · Score: 3, Informative

      "Queue" the GPL critics?

      Really? "Queue"?

    3. Re:Sigh... by aaaaaaargh! · · Score: 0, Flamebait

      Why is the above poster moded Flamebait? He's completely right. If you take GPL code you have to release your application under the GPL. What's so hard to understand about that? People accept the most ridiculous license terms for proprietary software but once it's about the GPL they start whining when they realize they can't use it for their proprietary shit software. Well, guess what, write your own fucking code!

      So let me chime in and say: Hopefully these assholes and all other GPL violators get sued into fucking oblivion!

    4. Re:Sigh... by demonlapin · · Score: 1

      It's an amusing bit of word play, even if it's probably not intentional.

    5. Re:Sigh... by hedwards · · Score: 1

      With the BSD license it would be a non-issue because people can do what they want with it.

      That's not to say that people like like the BSD license think it's OK to violate the licensing agreement.

    6. Re:Sigh... by Anonymous Coward · · Score: 0

      It's flame-bait because he's saying all us BSD'ers think it's just fine and dandy what they did. It's not. They broke the license and should pay the penalty. An author has every right to pick whatever license they like. I choose BSD. If someone else likes GPL, that's fine, and anyone using their code needs to respect that.

      The grandparent should likewise respect that others can prefer a different license without condoning other people breaking other licenses.

    7. Re:Sigh... by Anonymous Coward · · Score: 2, Insightful

      Unless you are on slashdot. Then it matters who you are. If you are a record company people should not respect any of your licenses, copyrights, etc. If you are Adobe, people should just take your stuff (break your copyright, etc.). If you are a GPL code author than anyone who breaks your copyright is evil incarnate and must be sued into oblivion. Let's just admit we have a double standard on this and move on.

    8. Re:Sigh... by hedwards · · Score: 4, Insightful

      There's a lot of libertarians around here. But most folks are just concerned with the abuses of power that the RIAA and MPAA engage in and the robbing of the public domain to profit an oligarchy.

      Few people here think that a person shouldn't be able to make a living creating copyright works, just that the time period needs to be balanced with the right of the people to own their culture.

    9. Re:Sigh... by obarthelemy · · Score: 4, Funny

      there's a lot of them !

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    10. Re:Sigh... by Anonymous Coward · · Score: 0

      You mean the original devs don't have their code anymore?

    11. Re:Sigh... by russotto · · Score: 1

      Unless you are on slashdot. Then it matters who you are. If you are a record company people should not respect any of your licenses, copyrights, etc.

      Absolutely. Record companies (at least RIAA and equivalent members) are the enemy and should be treated that way.

      If you are Adobe, people should just take your stuff (break your copyright, etc.).

      Adobe is a member of the BSA, an organization whose thuggishness knows little boundary. Not quite as bad as the RIAA (as they aren't writing new laws, though their predecessor organizations used to), but there's still a case for treating them as the enemy.

    12. Re:Sigh... by cheekyjohnson · · Score: 0

      I wonder how much code the original authors had stolen from them? It's gone forever unless they make Hamstersoft give it back!

      --
      Filthy, filthy copyrapists!
    13. Re:Sigh... by Anonymous Coward · · Score: 0

      Queue the GPL critics praising the BSD license. The short-short-short of it is that if these fuckers didn't want to have to abide by the GPL3 license, they shouldn't have been lazy pieces of worthless stealing shit and wrote their own fucking code.

      I hope they get sued into fucking oblivion.

      The GPL critics usually don't have a problem with the GPL by itself. The issue is rather that many GPL critics have a problem with people calling code released under GPL free. Both code released under GPL and under BSD license are open but only BSD is free.

    14. Re:Sigh... by Bert64 · · Score: 2

      Does society allow us to be "free"?

      The GPL works much like modern society, in that it takes away some individual freedoms that when exercised by the few, would be extremely detrimental to the many...

      In the case of society, there are laws against murder, slavery, etc... If you gave people absolute freedom then the strong would rapidly subjugate the weak, and then the weaker people would no longer have any freedoms at all.

      GPL works much the same way, by ensuring that everyone remains equal. With a BSD like license, the strong (large companies) will take the source code, close it up and ensure that future versions are no longer available under the same free terms. There are a large number of BSD derived products out there which are now closed source and often very expensive.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    15. Re:Sigh... by hsmith · · Score: 2

      Much better option than stacking them.

    16. Re:Sigh... by Anonymous Coward · · Score: 0

      Ha, fuck off. When does "GPL critics praising the BSD license" really happen? Oh, right, GPL guys are in such a minority, we oughta cut them some slack.

      What's more likely is GPL zealots ramming their views down everyone else's throats.

    17. Re:Sigh... by Anonymous Coward · · Score: 0

      Pocketbook is stealing code too.

    18. Re:Sigh... by Caesar+Tjalbo · · Score: 0

      First in, first post.

      --
      "I'm not much interested in interoperability. I want substitutability. I want to be able to throw your software out."
    19. Re:Sigh... by westlake · · Score: 1

      But most folks are just concerned with the abuses of power that the RIAA and MPAA engage in and the robbing of the public domain to profit an oligarchy.

      Let's be clear about something here.

      Disney's copyright on "Cinderella" and "Beauty and Beast" extends only to its unique take on these stories and to clearly derivative works.

      The Rogers and Hammerstein musical owes nothing to the Disney studio. Neither did Jim Henson's adaptation for the CBC and HBO.

      Search Amazon.com for "Beauty and the Beast" and you will find:

      503 Videos
      2,000 MP3s
      1,849 Books
      107 Titles For The Kindle
      612 Toys & Games
      353 CDs
      31 Video Games

      7,636 Products In All Categories.

      Search Amazon.com for "Robin Hood" and you will find 8,000 products in all catagories, for "Peter Pan," 10,000.

      What the geek seems to be lookig for is a Disney coloring book or a paint-by-number set. Because that is about as far as his own imagination or knowledge of popular culture can take him.

    20. Re:Sigh... by Gastrobot · · Score: 1

      It is of course true that if GPL code was used then the resultant product must be GPLed itself. I have no contention with you there. But as far as hoping that the company gets sued into oblivion, your indignation may be overzealous. The situation is not necessarily that simple. Imagine that you own a company. Maybe it's a large company or maybe it's a startup. You hire some developers to build a project for you. You invest in development, marketing, legal, production, etc. You may have put thousands of your own hours into meticulously guiding your beloved dream idea. Everyone does their job adequately except for one or two rogue developers who steal GPL code. Maybe your developers are incompetent and they steal to give the illusion of competence. Maybe they are ignorant about the terms of the GPL and they aren't ethical enough to bounce it off of the legal department before they take the code. In any case on a team of ten, dozens, or maybe hundreds a couple of guys download some code. Nobody knows about it. They project reaches prime-time. The owners of the copyright notice some similarities and investigate it. Now you, the owner of the company who has tried to do everything by-the-book, are suddenly accused of stealing code, you're flamed on the internet, you're under legal threat, and you're told that the hundreds of thousands or millions of dollars that you've invested are now potentially wasted because you need to give your software away for free. This could force you to breach other contracts and so it may not even be possible to legally satisfy everyone.

      I haven't read the article. I know nothing of this product or of this company. In any case, I think that the anger may be a little exaggerated because the owners of this company could be victims along with the owners of the GPLed code. It could come down to a couple of unethical and/or ignorant developers.

    21. Re:Sigh... by MightyMartian · · Score: 1

      That's a lovely sentiment, doubtless something to be reserved for closing arguments. But the fact is that company releases admitted to violating GPLv3, and then committed to amending their ways, and then stopped responding. If some dishonest subcontractor did the dirty deed, well their recourse is to sue that subcontractor. The holder of the copyright is not privy to how the company functions, all they know is that, in violation of the license they released their code under, it was used in another project.

      I say sue this company into oblivion.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    22. Re:Sigh... by dbIII · · Score: 1

      It's doubleplusgood American for cue, just like loose standing in for lose all the time. All that dumbing down is good for the environment since dictionaries only need to be one tenth of their former size.

      Yes I know it's an honest typo and we all know what they meant anyway, I just can't resist playing "I told you so" when something looks like damage from the education cuts since the 1980s.

    23. Re:Sigh... by sribe · · Score: 1

      Queue the GPL critics praising the BSD license. The short-short-short of it is that if these fuckers didn't want to have to abide by the GPL3 license, they shouldn't have been lazy pieces of worthless stealing shit and wrote their own fucking code.

      I hope they get sued into fucking oblivion.

      Let me speak as someone who generally much prefers the BSD license over the GPL, to your first point AGREED, and to your second point AGREED! I hope the author registered his copyright, so he can go for $250,000 per incident statutory damages instead of having to hash out actual damages. Sadly, that's probably not the case, but one can still hope...

    24. Re:Sigh... by teaserX · · Score: 1

      I understand what you're getting at here: cue vs. queue but this is one case where it doesn't really matter. I think the spirit of the OP is equally reflected whether we tell the critics to get in line to start or we give them the signal to start. Personally, I think "queue" is probably more relevant for the Slashdot crowd .

      --
      We really need your help
      http://www.gofundme.com/help-sherry
    25. Re:Sigh... by mwvdlee · · Score: 2

      It's probably modded flamebait because it tries to anger GPL critics for no apparent reason.
      Regardless what you think of GPL or BSD, a violation of GPL is still a violation of GPL.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    26. Re:Sigh... by metacell · · Score: 1

      I'm not sure what the GP meant, but "robbing of the public domain" can refer to the fact that Disney et al use public domain works to create their own films, such as the Jungle Book, Peter Pan, and so on, but start lobbying for copyright extensions as soon as their own works come close to falling into the public domain. That is, companies like Disney make use of the public domain without contributing anything themselves.

      It can also refer to the problem with "orphaned works", i.e, works that are no longer commercially available, but you can't obtain permission from the creator(s) to use them, so the works just rot away an archive somewhere. The vast majority of books, films, photographs and so on lose their commercial viability after a few years, but they're still protected by copyright for a century(*) just so the the media companies can continue to collect royalties on a few long-lived works. In other words, companies like Disney take an active role in destroying the public domain (even if it's just as a side effect of their commercial greed).

      (*) Depending on how long the author lives.

    27. Re:Sigh... by psmears · · Score: 1

      Actually Peter Pan was not in the public domain when Disney created their film - they had to license it. But the rest of your point stands nonetheless :)

    28. Re:Sigh... by Anonymous Coward · · Score: 0

      Right. Wanna go sue all of those GPL violators in the Android market too?

      Good luck.

    29. Re:Sigh... by tehcyder · · Score: 1

      Few people here think that a person shouldn't be able to make a living creating copyright works

      You must be reading a different slashdot than me then. Any time someone mentions musicians and copyright, it's always "they should earn their money from live gigs/selling t-shirts and give the music away for nothing".

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    30. Re:Sigh... by tehcyder · · Score: 1

      Record companies (at least RIAA and equivalent members) are the enemy and should be treated that way.

      So don't consume their products if they're that fucking horrible. I don't remember it becoming compulsory to listen to shitty chart music.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    31. Re:Sigh... by jellomizer · · Score: 1

      Well (Tongue in cheek) if you even think about money you are violating the GPL 3 code, with the unless you are IBM clause.
      That said most companies should avoid GPL Code like the plague, if they plan to redistribute anything based on it, as their business model is incompatible with the GPL code, and if they find a way to make it work chances are the next version of the GPL will find a way to block it.
      So yes Hamstersoft Ebook shouldn't have use the GPL 3 code, and they are wrong to do so.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    32. Re:Sigh... by TangoMargarine · · Score: 1

      The way I read it is more along the lines of "they should earn their money from gigs and t-shirts...because god knows they aren't going to have much luck prying their money out of the RIAA labels' fists."

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    33. Re:Sigh... by TangoMargarine · · Score: 1

      If some dishonest subcontractor did the dirty deed, well their recourse is to sue that subcontractor. The holder of the copyright is not privy to how the company functions, all they know is that, in violation of the license they released their code under, it was used in another project.

      I say sue this company into oblivion.

      And how would that actually help anything other than satisfying your sense of justice? They still have to release under the open-source license.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    34. Re:Sigh... by yurtinus · · Score: 1

      Don't be silly, this way they can both listen to the music they want to listen to without compensating the creators *and* feel good about it because doing so is their form of righteous political activism!

      --
      +1 Disagree
    35. Re:Sigh... by shutdown+-p+now · · Score: 1

      "Robbing PD" likely refers to repeated copyright term extensions largely lobbied by Disney. If not for them, early Disney works would have been in PD by now (just as those original stories were when Disney took them).

    36. Re:Sigh... by russotto · · Score: 1

      So don't consume their products if they're that fucking horrible. I don't remember it becoming compulsory to listen to shitty chart music.

      I actually don't listen to music (theirs or anyone else's). But they harm me anyway, with the laws they get passed. So since piracy apparently does them great harm (source: them), I'm all for it.

    37. Re:Sigh... by Gastrobot · · Score: 1

      I read more of the ensuing conversation and heard that they admitted in their EULA to using GPLed code. This company doesn't come across as being as innocent as my hypothetical organization.

      Back to a hypothetical - If you have tens of millions of dollars invested in a software application and it turns out that you're legally obligated to give that application away due to the inclusion of GPLed code by a freelance consultant then there is generally no way that by suing the consultant you're going to get back anything close to what was spent on development, and that's not considering the lost profits, market share, etc. I understand your position. By the letter of the law you may be correct in many cases (I'd say not necessarily all cases because you may still end up with a scenario where a project includes code under the GPL and other proprietary code that you're not legally allowed to release and then it's not clear cut since there is no solution that satisfies all licenses). I'm not suggesting that you're wrong by the letter, but rather the spirit of "sue them to oblivion" is a little harsh if applied broadly to all GPL violations. But I suppose that you were speaking specifically to this theft, and I can understand the outrage.

      I doubt, however, that suing them into oblivion has any reasonable chance of success, as I also read that they're a Russian company.

  2. Re:Infection. by nattt · · Score: 2, Insightful

    Surely the behaviour of a criminal, stealing code that they didn't intend to obey the licence of?

    --
    -- oldthinkers unbellyfeel ingsoc
  3. relocated subdomain s/stuff/store by Anonymous Coward · · Score: 1

    Dear submitter:
        They appear to have moved stuff.hamstersoft.com to store.hamstersoft.com to dodge search engine blocks.

  4. Re:Infection. by Stormthirst · · Score: 1

    This is the entire intent of the GPL (for good or bad). If Hampstersoft don't like it, they shouldn't have ripped off the code. Now I hope they get sued.

  5. man by nomadic · · Score: 0, Troll

    This is a perfect example of how intellectual property is morally bankrupt and lawyers are terrible people and how IP law holds back true innovation and ... oh wait, because the holder of the copyright released it under a license we like, then let's completely reverse our supposedly deeply held beliefs: nothing is wrong with intellectual property, the infringing party should be sued to smithereens, etc. etc.

    1. Re:man by Shyfer · · Score: 1

      IP laws (in general, not all of them do) currently DO hold innovation. But those guys knowingly violated GPL licensed software because they were too lazy to write their own. I don't support him the same way I wouldn't support someone stealing code from a closed project to use in their product.

    2. Re:man by RobinEggs · · Score: 3, Insightful

      It's not hypocritical to believe in GPL and simultaneously despise the way intellectual property works in modern life.

      I believe in intellectual property where it is public property, something distributed openly and protected from corporate schills who want to strangle the path of innovation lest it lead away from their business model. You can be anti-corporate and against 75 year copyright yet still believe in the value of short legal monopolies and in the good of clearly defining (and protecting) public property.

      I feel about long-lasting intellectual property restraints the way I feel about jet fighters: in public hands, yes. In private hands, break out the pitchforks.

    3. Re:man by TFAFalcon · · Score: 1

      The problem is the people who used this software then DIDN'T release under the GPL.

    4. Re:man by EsbenMoseHansen · · Score: 1

      I don't think anyone thinks that copyright hold back innovation... that would be patents.

      Even if they were, most people who find it ok to steal^Hcopy for their own personal use think it is not if you're going to publish-for-profit.

      Furthermore, there are a lot of readers and commentators on slashdot. Quite likely, they have different interests and opinions.

      Finally, most people have a least some double standards.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    5. Re:man by maxwell+demon · · Score: 1

      Of course those people didn't just copy. They plagiarized.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    6. Re:man by maxwell+demon · · Score: 1

      OK, I've now seen from other comments that they didn't actually plagiarize, but just didn't release their own parts, as required by the GPL. Sorry for the confusion.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    7. Re:man by amorsen · · Score: 1

      I don't think anyone thinks that copyright hold back innovation...

      You would be wrong then. At least one person thinks that copyright holds back innovation. Me.

      --
      Finally! A year of moderation! Ready for 2019?
    8. Re:man by cheekyjohnson · · Score: 1

      And everyone here thinks the exact same way.

      --
      Filthy, filthy copyrapists!
    9. Re:man by Lanteran · · Score: 1

      Licensing software under GPL would not hamper innovation or anything like that- you're free to use it however you like, as long as you keep it free. It's software patents, proprietary software and the like that slow innovation.

      --
      "People don't want to learn linux" hasn't been a valid excuse since '03.
    10. Re:man by garaged · · Score: 1

      Would hamstersoft be happy if anybody else sells their books or apps without paying them ?

      --
      I'm positive, don't belive me look at my karma
    11. Re:man by http · · Score: 1

      For jet fighters in public hands, you'll need SAMs, not pitchforks.

      --
      If opportunity came disguised as temptation, one knock would be enough.
      3^2 * 67^1 * 977^1
    12. Re:man by EsbenMoseHansen · · Score: 1

      I stand corrected, then. Eh. How, exactly?

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    13. Re:man by metacell · · Score: 1

      Copyright prevents reverse-engineering, since it's used to enforce the license agreement. Without copyright, you don't need a license, and therefore don't need to accept the license agreement.

    14. Re:man by amorsen · · Score: 1

      From Free as in Freedom

      After briefly introducing himself as a visitor from MIT, Stallman requested a copy of the laser-printer source code so that he could port it to the PDP-11. To his surprise, the professor refused to grant his request. "He told me that he had promised not to give me a copy," Stallman says.

      And so Stallman could not improve the printer. Perhaps a small innovation that time, but having to constantly reinvent the wheel is certainly holding the software industry back.

      --
      Finally! A year of moderation! Ready for 2019?
    15. Re:man by EsbenMoseHansen · · Score: 1

      Porting is hardly innovation. Besides, sometimes innovation comes from having to reinventing the wheel.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
  6. Hamstersoft Offers Code? by MatthiasF · · Score: 2, Informative

    It looks like they do offer the code for the product?

    http://ebook.hamstersoft.com/en/support

    Link to a ZIP file at the bottom of the page above.

    So, is this a non-issue or did the company throw the code up quickly to avoid the DMCA?

    1. Re:Hamstersoft Offers Code? by Nate+the+greatest · · Score: 4, Informative

      I'm told that it's not a complete set of source code. - signed, guy who submitted the story.

    2. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      In the long version they explain that Hamstersoft released an incomplete source tree, with only the source of the parts that directly interface with calibre. This is not enough according to the GLP, and they've been informed of it, with no response in a month.

    3. Re:Hamstersoft Offers Code? by Zocalo · · Score: 1

      Hamstersoft doesn't appear in the Wayback Machine, but Google's cached version is dated August 6th and includes the download link. Both the linked accusations are from the last couple of days, so it looks very much like while John Schember may have correctly accused Hamstersoft over a month ago he forgot to check the download page before publicly spouting off on his blog.

      --
      UNIX? They're not even circumcised! Savages!
    4. Re:Hamstersoft Offers Code? by Zocalo · · Score: 2

      Scratch that. You need to go to the original blog post to get the facts, but John's post claims Hamstersoft hasn't posted all the code, as required by GPL3. I guess that means it's torches and pitchforks after all.

      --
      UNIX? They're not even circumcised! Savages!
    5. Re:Hamstersoft Offers Code? by galaad2 · · Score: 1, Informative

      i think you're right, this is not a gpl violation, according to their server the source code zip archive was uploaded (and possibly also made available) on july 21. This includes the source code for that dll file.

      media.hamstersoft.com/hamster.ebookconverter.project.zip

      HTTP headers returned by media.hamstersoft.com:
      [...snip...]
      Content-Type: application/zip
      Content-Length: 64444164
      Last-Modified: Thu, 21 Jul 2011 07:53:35 GMT

      --
      root@127.0.0.1
    6. Re:Hamstersoft Offers Code? by galaad2 · · Score: 1

      actually...scratch that.. i looked through the zip file again, the source code for the UI dll (HamsterEbookConverterUI.dll) doesn't appear directly as a source file... maybe it's generated by another source file?

      --
      root@127.0.0.1
    7. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      I just looked through the source code located here:

      http://media.hamstersoft.com/hamster.ebookconverter.project.zip

      No license appears to be included in the package. The website also states the following:

      "Everybody may use Hamster Free eBook Converter on any computer at home, in business and government organizations without any restrictions and any amount of hosts. You don't need to register or pay for Hamster Free eBook Converter. No one needs to pay for any further updates and plugins."

      This gratis license contradicts the GPL3 (IANAL). If the code for Calibre is contained within the zip file (as a folder with the name indicates), then the authors of Calibre have a good case.

    8. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      Do you believe everything you're told or did you check it yourself?

    9. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      There is a big difference between putting up a file that says source.zip and actually putting source code in it. They included two binary blobs of calibre components. No calibre source. They put in a small amount of C# code and there is a reference to a linked binary component called HamsterEbookConverterUI.dll which doesn't appear anywhere but as a reference in the Visual Studio project file.

    10. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      Do you often submit stories accusing others of crimes without bothering to actually check if it's true first?

    11. Re:Hamstersoft Offers Code? by jo_ham · · Score: 0

      I'm told you beat your wife.

      Seems legit. Time to write a story!

    12. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      So, you of course then investigated to see if it was indeed abiding with the GPL correct?

      No?

      I'm guessing no actually.

      -K

    13. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      As stated in the blog, the zip file doesn't include all of the source and includes binary only DLLs of their changes. Not all of the source is there.

    14. Re:Hamstersoft Offers Code? by egr · · Score: 1

      Isn't it how news works nowadays? Post rumours -- check facts later.

    15. Re:Hamstersoft Offers Code? by Pikoro · · Score: 2

      I just downloaded that zip file, unpacked it, and opened the solution. It compiles right as it is and runs correctly. Story?

      --
      "Freedom in the USA is not the ability to do what you want. It is the ability to stop others from doing what THEY want"
    16. Re:Hamstersoft Offers Code? by Anonymous Coward · · Score: 0

      Hahaha, well done, you moron, you said "look, the source code's right there!", trusting the thieves without double checking that that's really the source code...

    17. Re:Hamstersoft Offers Code? by Omnifarious · · Score: 1

      I investigated, and no, the released 'source code' is not really source code at all, and certainly not what is required to be compliant with the GPLv3.

      So lambasting the OP for accepting the original authors word on this is a bit of an exercise in douchebaggery anyway, in this case you're also quite laugh worthy because the original author happens to be absolutely correct.

  7. Why Do We Care? by RobinEggs · · Score: 1, Insightful

    We all know you shouldn't steal public property for personal profit, and this theft wasn't unique or creative in any way. Where's the news?

    This isn't really any different than stories about random violent crimes or bad weather in other states. It's not relevant to your life, it doesn't teach you anything you didn't know already, and it's only purpose is to generate page views. It's not like I don't care about protecting GPL or preventing corporate malfeasance, I just question how this story tells me anything I didn't already know.

    I like news that tells me something...new.

    1. Re:Why Do We Care? by Shyfer · · Score: 2, Insightful

      Well this is still news, not really surprising or important but still news. Sometimes stories like this generate interesting discussions (along with troll and flamebait shitstorms), so I'm ok with it.

    2. Re:Why Do We Care? by ColdWetDog · · Score: 2

      I like news that tells me something...new.

      Son, I've got some bad news for you. This is Slashdot. We aren't into that sort of thing around here.

      But whatever floats your boat.

      --
      Faster! Faster! Faster would be better!
    3. Re:Why Do We Care? by elashish14 · · Score: 1

      It's important because, while we know that ripping off GPL software is a rampant practice, it is not always so easy to bring the people who do that back into compliance. We've had numerous stories posted on /. about people who know that their code is being stolen, but they don't have the legal and/or financial resources to fight back.

      What use is the GPL to people who don't have the resources to enforce it? That's why this is an important story.

      --
      I have left slashdot and am now on Soylent News. FUCK YOU DICE.
    4. Re:Why Do We Care? by ilsaloving · · Score: 1

      Because the only way to combat stuff like this is through vigilance, and you cannot be vigilant if you don't know it is happening.

      One of the reasons the world isn't better than it is, is because of people like you who think that if it doesn't have some kind of novel entertainment value, then it's not important. Maybe if people tried a little harder to care about things in between episodes of American Idol, our cities and countries wouldn't be ruled by obnoxious tools.

    5. Re:Why Do We Care? by RobinEggs · · Score: 1

      Oh shove off you self righteous little twit. I'm hardly demanding that news be entertaining. I'm simply saying that seeing the same damn story five times a week isn't necessary; I remember that license violations are rampant without slashdot shoving down my throat every god damn day.

    6. Re:Why Do We Care? by mysidia · · Score: 1

      This isn't really any different than stories about random violent crimes or bad weather in other states.

      Random crimes that are significant for the open source community are Slashdot news.

      There aren't that many so brazen GPL violations reported. There are a heck of a lot more violent crimes in the world than brazen GPL violations.

    7. Re:Why Do We Care? by teaserX · · Score: 1

      I remember that license violations are rampant without slashdot shoving down my throat every god damn day.

      No, you don't...and you certainly don't do anything about it.

      --
      We really need your help
      http://www.gofundme.com/help-sherry
    8. Re:Why Do We Care? by dredwerker · · Score: 1

      Because the only way to combat stuff like this is through vigilance, and you cannot be vigilant .

      I read that as combating through violence - i thought fair enough :)

      --
      On a long enough timeline. The survival rate for everyone drops to zero. Chuck Palahniuk, Fight Club, 1996
  8. Amazing observation by Anonymous Coward · · Score: 0

    Hope ./ readers see this one and realize the error of their ways!

    1. Re:Amazing observation by calmofthestorm · · Score: 1

      Stallman et al view the GPL as a transitional measure -- as long as copyrights exist, they need to use the system to protect themselves. Once it's gone (haha) they are well aware their GPL will be gone too. This is their plan.

      Now I think they're crazy, but I get mildly annoyed at people who can't see beyond the length of their own nose thinking that if you are against an institution like copyright or patent then you are somehow morally bankrupt if you also use it. Patents in particular, you need defensively if you want to do anything remotely new.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    2. Re:Amazing observation by man_of_mr_e · · Score: 1

      Actually, no. The only way to enforce code sharing is via the GPL, and thus copyright. Without copyright, nobody would be forced to share their code, even if they took it from someone else.

      Of course, you would be free to reverse engineer it, but it wouldn't be the same as what you get from the GPL. Basically, the entire concept of the FSF's idea of free software requires copyright in order to exist.

    3. Re:Amazing observation by HiThere · · Score: 3, Interesting

      I approve of the GPL, but the copyright period is FAR too long. Of course, that's not the doing of the FSF, so don't blame them, but they could have thrown the code into public domain after five years. Or maybe ten.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:Amazing observation by cheekyjohnson · · Score: 1

      Actually, no. The only way to enforce code sharing is via the GPL, and thus copyright. Without copyright, nobody would be forced to share their code, even if they took it from someone else.

      Technically, that's probably true, but if copyright was truly gone, there probably wouldn't be much point in not sharing the code to begin with.

      --
      Filthy, filthy copyrapists!
    5. Re:Amazing observation by man_of_mr_e · · Score: 1

      Huh? The same reasons would apply to not share the code. To make it harder for others to use your code to take money out of your pockets. If it becomes legal to reverse engineer and share the source code, then business will spend more effort protecting their code from reverse engineering.. making it even more obfuscated, encrypting it at multiple levels, etc...

    6. Re:Amazing observation by cheekyjohnson · · Score: 1

      Oh, right. I guess I was just assuming that if copyright was abolished, we probably wouldn't be using money anymore.

      --
      Filthy, filthy copyrapists!
    7. Re:Amazing observation by Anonymous Coward · · Score: 0

      ...I get mildly annoyed at people who can't see beyond the length of their own nose thinking that if you are against an institution like copyright or patent then you are somehow morally bankrupt if you also use it.

      Kind of like Michele Bachmann decrying Fannie and Freddie yet taking out a huge loan secured by them?

      Those programs need to go away. Really. After I'm done with them.

    8. Re:Amazing observation by Anonymous Coward · · Score: 0

      Without copyright, nobody would be able to profit from selling software. The only software developers remaining would either be altruistic or profiting from services related to the software. I imagine that in these circumstances, most non-service-related software would be released with source code.

    9. Re:Amazing observation by man_of_mr_e · · Score: 1

      Not true at all. People can profit from software the same way people profit from free software today.

      They can either charge a boat load for the first copy, or they can contractually obligate their purchasers to pay them large amounts of money if they give it to someone else.

      Or, they can make their money off support. If they don't give out source code, then nobody else can support it, thus they're the only source of support.

    10. Re:Amazing observation by shentino · · Score: 1

      Without copyright, you couldn't stop someone from sharing your code FOR you, either.

    11. Re:Amazing observation by tehcyder · · Score: 1

      Without copyright, nobody would be able to profit from selling software. The only software developers remaining would either be altruistic or profiting from services related to the software. I imagine that in these circumstances, most non-service-related software would be released with source code.

      Rubbish, you'd just get a lot of firms selling packages of "free" software inextricalbly bundled with support contracts. And you'd still have the existing laws to prevent things like passing off, so you wouldn't be able to take Microsoft's source code and use it to create your own "Windows" product.

      Now, as someone mentioned above, if this universal release of everything for free occurred because mankind had somehow found the key to infinite energy and materials and so could abolish the tedious concept of money and trading, then great. But in the meantime, society doesn't work like that.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  9. Re:Infection. by calmofthestorm · · Score: 1

    Or a software company. You can't use code from other company projects unless you release the modified code to the company's ownership.

    --
    93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
  10. Search Results by Fnord666 · · Score: 2
    In response to a DMCA takedown notification

    Yahoo was the first to respond. They said they get all of their search results from Microsoft via Bing and referred me to Microsoft. So no luck there.

    I don't care who they get their search results from. They are the site provider and are responsible for following the DMCA. Failure to do so will strip them of their safe harbor provisions and open them up to liability alongside Hamstersoft.

    --
    'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
    1. Re:Search Results by hedwards · · Score: 2

      Unless Yahoo is hosting the files, why on Earth should they be responsible for refusing to change their search results? The last thing we need is for search providers to drop results just because they're illegal.

    2. Re:Search Results by Anonymous Coward · · Score: 0

      Because US law considers linking to infringing content to be contributory infringement.

    3. Re:Search Results by hedwards · · Score: 1

      They're a search engine, the cases where that was found to be the case were dealing with specialist sites that specifically provided links to copyright materials rather than just a generalized search engine.

      Neither Yahoo nor MS has anyways of knowing whether any of the information is in violation of copyright law. I doubt very much that the courts are going to find otherwise should it come to that.

    4. Re:Search Results by Anonymous Coward · · Score: 0

      You mean like the PROTECT-IP act will force them to soon?

    5. Re:Search Results by Fnord666 · · Score: 1

      Unless Yahoo is hosting the files, why on Earth should they be responsible for refusing to change their search results? The last thing we need is for search providers to drop results just because they're illegal.

      Already rebutted here

      --
      'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
    6. Re:Search Results by Anonymous Coward · · Score: 0

      I was so outraged by Yahoo's response to you that i wrote an angry letter to Microsoft.
      They said that get all their search results from Google and referred to me to them. Still no luck.

  11. HamsterSoft Products by Anonymous Coward · · Score: 0

    It appears that nearly all of HamsterSoft's products are based substantially upon code released under versions of the GPL or LGPL. (There's also a 7ZIP-based archiving utility for which I can't find the relevant source code; and an FFMPEG-based video transcoding utility).

    I wonder if their CD burning application is based upon CDRecord/CDRTools, too...

  12. Source and Binary Release by SJ2000 · · Score: 0
    Hamstersoft's source-code release package (~65MB)

    It is not clear if they modified calibre because the binary builds are only part of calibre not the entire program as it is officially distributed.

    Why not just decompile the binary? It's written in C# .NET and things like .NET Reflector are fairly good at it.

    1. Re:Source and Binary Release by hedwards · · Score: 1

      You mean other than the fact that the GPL mandates that the source be provided? I don't personally agree that people should be forced to release their own code because they borrowed somebody elses code, but the GPL does require that and so they have to do it.

      If they don't want to, there are options, such as getting the license changed or not using the code. But, it is a violation of the terms of the license.

    2. Re:Source and Binary Release by man_of_mr_e · · Score: 1

      The GPL does not require all code in an application to be released, only when such code is considered a "derived work". There are lots of examples of how you can legally get around the GPL, such as by making the code into it's own executable and shelling out to it, or making it a web service, or any number of other physical seperations.

      There's even a lot of dissent within the community as to whether DLL's are considered derived works. The FSF thinks they are, but lots of other lawys think they're not.

    3. Re:Source and Binary Release by SJ2000 · · Score: 1

      I did not mean it as a means for license compliance but rather to check if modifications have been made.

    4. Re:Source and Binary Release by NoMaster · · Score: 1

      "... such as by making the code into it's own executable and shelling out to it ..."

      Which is what they did when they used ffmpeg & mencoder in one of their other products, Hamster Free Video Converter.

      In other words, they have a history of this type of thing...

      --
      What part of "a well regulated militia" do you not understand?
  13. A key weakness in the GPL... by AtlantaSteve · · Score: 0

    Unless the Calibre developer invests tens of thousands (or more) and a few years of his life, all into suing a company that is probably one guy working out of his apartment anyway, then this is just some online whining.

    The GPL is not a magical hall monitor shield, which forces people to show you their hall pass when you wave it. Rather, it simply gives you the right to sue if you have the resources to pursue that road. In this case, I don't know if the Calibre guy has those resources, or if the Hamster guy has enough resources to be worth suing anyway.

    1. Re:A key weakness in the GPL... by fuzzyfuzzyfungus · · Score: 1

      On the other hand, largely because of the efforts of team MPAA, even the vaguest hints of something resembling copyright infringement are your authorization to more or less auto-DMCA the target whenever they poke their heads up in parts of the internet under US jurisdiction...

    2. Re:A key weakness in the GPL... by kthreadd · · Score: 1

      At some point you have to trust people. Most criminal acts ends up being unnoticed, that doesn't mean that we shouldn't have a police force and sue when appropriate.

  14. Re:NOVEL IDEA !! HIRE AN MPAA LAWYER !! by Anonymous Coward · · Score: 0

    The ironing. Bitch and moan about them and turn around and bitch and moan about the other them. Such an ironing.

  15. Hamstersoft doesn't understand copyleft? by kwikrick · · Score: 5, Interesting

    From their EULA: (http://hamstersoft.com/eula)

    RESTRICTIONS

    The source code, design, and structure of HAMSTER free software are trade secrets except software licensed under GNU GPL 3.0, LGPL, MPL, BSD-licensed or Free components used to compile. You will not disassemble, decompile, or reverse engineer it, in whole except to the extent expressly permitted by law or except GNU GPL 3.0, LGPL, MPL, BSD-licensed or Free components used to compile HAMSTER free software. You will not use HAMSTER free software for illegal purposes. You will comply with all export laws. HAMSTER free software is licensed, not sold.

    ---

    Sorry guys, you can't have GPL'd code and trade secrets in one piece of software.

    --
    assignment != equality != identity
    1. Re:Hamstersoft doesn't understand copyleft? by Anonymous Coward · · Score: 0

      Of course you can you stoopid asshole. Look at google. If you don't like it don't use it. Seems obviously simple that even a moron like you should get that.

    2. Re:Hamstersoft doesn't understand copyleft? by Anonymous Coward · · Score: 0

      Well, you can, but not if it's GPLv3'd...

    3. Re:Hamstersoft doesn't understand copyleft? by Anonymous Coward · · Score: 0

      Sorry guys, you can't have GPL'd code and trade secrets in one piece of software.

      Yes you can assuming the proprietary piece of code and the GPL piece of code reside in separate executables. I expect a front-end / shell convertor is more likely to invoke another process to convert between two random book formats than link to it.

    4. Re:Hamstersoft doesn't understand copyleft? by sirsnork · · Score: 2

      Not to mention trade secrets have no protection under law, in fact that's why copyright exists in the first place

      --

      Normal people worry me!
    5. Re:Hamstersoft doesn't understand copyleft? by gnasher719 · · Score: 1

      Sorry guys, you can't have GPL'd code and trade secrets in one piece of software.

      AND distribute the software AND not commit copyright infringement. You can of course use GPL'd code to build software that you use only internally without distribution; there is no requirement to give the source code to anyone, so the source code could contain trade secrets. And you can of course keep the source code secret and distribute the application; the distribution is of course copyright infringement.

    6. Re:Hamstersoft doesn't understand copyleft? by Anonymous Coward · · Score: 0

      No. http://en.wikipedia.org/wiki/Uniform_Trade_Secrets_Act

    7. Re:Hamstersoft doesn't understand copyleft? by Anonymous Coward · · Score: 0

      "No protection under law" simply isn't true; there are plenty of European laws that do protect trade secrets.

      And besides, saying "X except where the law or GPL says otherwise" means that it's irrelevant whether X would violate the law or GPL terms. (However, that just means that the EULA doesn't violate the GPL. You'd still need to offer source code).

    8. Re:Hamstersoft doesn't understand copyleft? by Omnifarious · · Score: 1

      In this case significant portions of the converter are written in Python, and it's not clear (from their released bag of garbage masquerading as source code) that they don't 'link' to it (i.e. import the Python modules in their own code). Also, even if they did, they still have to provide the code for the version of the converter they're using, and they haven't even done that.

    9. Re:Hamstersoft doesn't understand copyleft? by hsa · · Score: 1

      I've done analysis on some of the lisences for my previous company. The thing it, you can actually have trade secrets in your code with for example BSD-style lisence, where you only need to provide the acknowledgement and changes to the original source code. Sometimes not even that much. We actually chose software based on the lisencing terms. Not all lisences are that restrictive (for commercial gain).

      Then again, with GPL you need to publish the full source code, so this is a moot point.

      If the lisence would have been LGPL, they could easily just keep their trade secrets..

    10. Re:Hamstersoft doesn't understand copyleft? by DavidTC · · Score: 1

      Uh, yes, they do.

      Trade secrets have no protection against someone independently reinventing them (Like patents do) nor do they have any protection against the company that holds them publishing them. (Like copyrights.)

      As long as you're within the law when you learn someone else's trade secret, as long as you don't violate someone's NDA or break into their safe or something, it's entirely legal to use that information however you want.

      But, if to learn that trade secret, you do break the law, or do violate an NDA, though, every state has some sort of 'trade secret law' where the original company can sue you for epic damages, and even force a gag on you so you can't spread the secret, with even more damages if you do so.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  16. Re:Infection. by Anonymous Coward · · Score: 0, Flamebait

    If Hampstersoft don't like it,

    Why is it that so many slashtards can't spell the word 'hamster' correctly? Especially when it's right in front of their fucking faces!

  17. Before anyone gets ahead of themselves... by zx2c4 · · Score: 5, Informative

    I'm a good friend of John, the blog post author, and have been working with him throughout this process in trying to unravel Hamstersoft's deceit. I want to make a few things pretty clear:

    Yes, they posted a zip of code on a hard-to-find link. But they did something sneaky. They included the very short and trivial C# wrapper around Calibre, but they only included a compiled (well, .NET dll) binary blob of the bulk of the application code -- the user interface. And of course, since all the heavy lifting is in Calibre itself, this code is the most important part of the application. They went through pains to extract the source of the UI components and only include it publicly as already compiled. They even packaged it up in a nice Visual Studio Solution so that you can load it up and hit "compile" and you get the software. It looks, at first, like they've complied. But then you dig into the source code actually provided, and it becomes obvious that they haven't provided the majority of the code at all, but only the wrapper code and a few call outs to the provided compiled DLL.

    Cheap trick.

    The other thing to take notice of in John's post is that in fact the search engines and Facebook have hardly complied -- there are still search results and Facebook pages for this company. Now, you can debate and troll and bikeshed and argue the validity and ethics of the DMCA all you want, but the fact of the matter is that when the big companies want to use it against the small, it seems to work, but when some OSS devs want to take the case up with giant companies, the response is exceedingly lackluster. (Likely, this being on /. will change things, we'd hope...)

    The final point to consider is what this all means for GPL and OSS. Hamstersoft is Russian, so good luck trying law suit or anything. But at the very least, shouldn't the OSS community have an army of lawyers willing to work probono, or financed by various foundations, for this kind of thing exactly? John mentioned he tried contacting one such organization, and was unsuccessful. He's told me that at another point, he got in contact with a lawyer from another place who didn't offer to do any work for him but vaguely suggested he send these notices to Google, Facebook, etc. That's pretty lackluster. I don't want to complain to loudly, but instead I just want to suggest that this issue call our attention to the bigger issue -- what institutions do we have in place to protect OSS software effectively as small OSS devs? Do such institutions work? In this case, thus far, they don't seem to be working.

    --
    ZX2C4
    1. Re:Before anyone gets ahead of themselves... by seandiggity · · Score: 1

      what institutions do we have in place to protect OSS software effectively as small OSS devs? Do such institutions work?

      Someone correct me if I'm wrong, but I thought this is why some projects assign their copyright to the FSF, so that there is a dedicated group that will pursue violations: http://www.gnu.org/licenses/gpl-violation.html

      At any rate, since this seems to be getting a lot of attention and could turn into a high-profile case, you may want to contact the FSF or SFLC or both.

      --
      Geeks like to think that they can ignore politics, you can leave politics alone, but politics won't leave you alone.-rms
    2. Re:Before anyone gets ahead of themselves... by man_of_mr_e · · Score: 3, Insightful

      This looks to me like the exact same situation of an application shelling out to a gpl'd app. This is allowed by the GPL, and is even explicitly allowed in the GPL faq IIRC.

      There is a huge debate in the open source legal community as to whether DLL's are considered "derived works", and there's lots of law on both sides to support their case. This probably won't be solved until a legal case decides the issue. So, until that time, it's just a case of everyone having an opinion, and it's not a clear cut case of violation.

    3. Re:Before anyone gets ahead of themselves... by filmotheklown · · Score: 1

      But at the very least, shouldn't the OSS community have an army of lawyers willing to work probono, or financed by various foundations, for this kind of thing exactly?

      Hah! Almost spit milk through my nose reading this line. Lawyers? Probono on commercial work? (even if it's unpaid, it's commercial work). Lawyers expect to get paid for work just as most software developers expect to get paid at their day jobs. Defending a license like GPL isn't something a lawyer can do with a few hours of labor on Saturday afternoon.

      And it would take an 'army' of them to fight these infractions. So unless everybody in the OSS community wants to pay dues to some foundation to fund a staff of 8 to 10 lawyers and their 16 to 20 support personnel this isn't likely to happen. Even EFF has only about 9 staff attorneys and they cover a huge mandate, not just FOSS software violations. http://www.eff.org/about/staff Their budget is close to 3.6 Million per year.

      So if you want an army of lawyers to defend GPL or other licenses, build a foundation and raise 4 million per year.

      Of course you can DIY the law yourself, you just have to spend your own time and money doing it.

      --
      Filmo The Klown
    4. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      The final point to consider is what this all means for GPL and OSS. Hamstersoft is Russian, so good luck trying law suit or anything. But at the very least, shouldn't the OSS community have an army of lawyers willing to work probono, or financed by various foundations, for this kind of thing exactly?

      While it would be nice for some foundation to offer to aid John no one is obligated to. The GPL is a license. It allows the copyright holder to take legal action should the license be breached. Whether third parties come to the aid of the copyright holder is outside the purview of the license.

      Should there be a foundation for this kind of thing? Maybe. There's nothing stopping you from forming a co-op where GPL projects could band together for legal issues. Another option for some people is to assign copyright to the FSF. I believe they enforce the licensing terms of their projects.

    5. Re:Before anyone gets ahead of themselves... by russotto · · Score: 1

      I don't want to complain to loudly, but instead I just want to suggest that this issue call our attention to the bigger issue -- what institutions do we have in place to protect OSS software effectively as small OSS devs? Do such institutions work? In this case, thus far, they don't seem to be working.

      They're the same institutions which protect copyrights in general. So the answer is an emphatic "NO"! What did you expect?

      You really want to get to them? Reverse-engineer their code and post the reconstructed source publicly. Of course, since they're Russian they may not feel the US institutions which protect copyrights will work for them, so they'll just have you killed.

      Using the DMCA to attempt to censor search engine results just makes you the bad guy.

    6. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      I know that this isn't what the issue is even about (yes, the code _should_ be provided), but if anybody really does want the source, it's easy enough to get. You'd figure with them being so reluctant to release it, that they'd at least have gone to the trouble of obfuscating it or something...

      Anyway, download their current 'source' archive, & then load HamsterEbookConverterUI.dll into ILSpy (http://wiki.sharpdevelop.net/ILSpy.ashx), hit "Save Code", and you have the full source of HamsterEbookConverterUI.dll. Apparently without so much as a single obfuscated variable name.

    7. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      The shelling issue is just one part of it. They're also distributing a modified binary version of calibre as part of their application. They're refusing to release source for their version calibre. This is a clear GPL violation.

    8. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      No, that's incorrect. Please RTFA.

      The source code that HamsterSoft uploaded was far from complete. It contains two non-complete binary builds of calibre. No mention if there are or not modifications. It is not clear if they modified calibre because the binary builds are only part of calibre not the entire program as it is officially distributed. No calibre source code, which they must supply (it’s not enough to point to the calibre project’s download page), was present.

      Of course, even if this were so, we know the FSF would still disagree that the program is in compliance. From the GPL FAQ:

      The difference between this and “incorporating” the GPL-covered software is partly a matter of substance and partly form. The substantive part is this: if the two programs are combined so that they become effectively two parts of one program, then you can't treat them as two separate programs. So the GPL has to cover the whole thing.

    9. Re:Before anyone gets ahead of themselves... by man_of_mr_e · · Score: 1

      My understanding is that the binary is Hamstersofts code, and that they are distributing the Calibre code, along with the wrapper code they wrote to interface it with their binary code.

      I have read nothing about a modified calibre binary.

    10. Re:Before anyone gets ahead of themselves... by Doppleganger · · Score: 1

      "in fact the search engines and Facebook have hardly complied -- there are still search results and Facebook pages for this company"

      The DMCA doesn't require that links to the company be removed - it requires that the service provider stop their distribution of a copyrighted work. From TFA, it sounds like only Facebook had a direct download link to the copyrighted work, and that they assisted in its removal. As someone else mentioned, to make the download completely unavailable you would need to send a DMCA notice to the hosting provider (Masterhost, according to RIPE) and hope that this Russian company respects U.S. copyright law.

      Getting search engines to delist entire companies isn't really what the law is intended for, even if it sometimes succeeds.

    11. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      It's right in TFA. They're distributing as part of their program a modified binary distribution of calibre without source code. The source code is only for their own shell.

    12. Re:Before anyone gets ahead of themselves... by ByteSlicer · · Score: 5, Interesting

      If Calibre was a library ditributed under the Lesser GPL then you would be right.

      But it's not, it is the normal GPL that applies here, and even v3, which was specifically designed to eliminate the grey areas from the v2.

      Hamstersoft has two options: either immediately cease all distribution of the infringing binaries, or provide the full sources under one of the methods specified in the GPL.

    13. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      Hamstersoft has two options: either immediately cease all distribution of the infringing binaries, or provide the full sources under one of the methods specified in the GPL.

      I bet they go with option 3 - they keep distributing as they like, because nobody can stop them.

    14. Re:Before anyone gets ahead of themselves... by man_of_mr_e · · Score: 1

      What the FSF believes the GPL means is not necessarily what a judge would interpret it to mean.

      The article says they don't know if the binary builds are modified or not, so the claim that they are seems to have no substance to it. And, I believe the source download does include the Calibre source code unmodified.

    15. Re:Before anyone gets ahead of themselves... by man_of_mr_e · · Score: 1

      The article says they don't know if the binaries are modified or not.

    16. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      And, I believe the source download does include the Calibre source code unmodified.

      No, it doesn't. TFA is right. Go ahead and download it, there's no calibre code at all that I can see. It's all .dll, .exe, or .pyd, which are all compiled binary forms.

    17. Re:Before anyone gets ahead of themselves... by Spacejock · · Score: 1

      One of my free (as in beer) desktop applications will create a calibre-friendly html export from a project. I leave it up to the user to download and install Calibre, and to manually import and convert this exported html file to their ebook of choice. It's not that hard to work things like this, even if it's another step for the user. (Exporting to ebook is a very minor feature in my software, and I'm planning a proper epub export soon in any case.)

    18. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      The dirty truth of it all is that if you lack lawyer enforcement, then none of it is real. The government won't sue anyone on your behalf; that's why dropping rape charges on crimes where the rapist expressed sorrow tends to leave them free even if there's an admission of guilt.

      There are exceptions if the crime involves deaths because the public at large would be unsafe even if the victim's family has [rarely] pardoned the killer. But the world of software is still mostly uncharted by law, so it's a Wild Wild West where shootout winners have the power to decide who the guilty party is... and he's already dead as a definition of "loser" ;). The shooters are the big corp lawyers, and they never work for free, let alone OSS brownie points. Even less across oceans, especially seeing how much the USA is hated by other countries.

      Sad, really. We have no choice but to join an umbrella of lawyers just to feel safe, and that comes with a price: keeping your sources closed.

    19. Re:Before anyone gets ahead of themselves... by pavon · · Score: 1

      Not necessarily. Copyright law gives copyright holders certain exclusive rights, and (being a pure copyright license, not a EULA) the GPL can only restrict people from doing those things. One them is creating derivative works, however it is the courts (not the GPL/LGPL) that draw the line between what constitutes a derivative work and what is fair use. Like many fair use situations, that line is pretty fuzzy. The general consensus within the tech community is:

      Incorporating a significant amount of source code: Certainly a derivative work
      Static linking a third-party library: Almost certainly a derivative work.
      Dynamically linking a library/plugin/etc: Probably a derivative work but debatable. Some people have varying opinions based on the context of the linking.
      Linking system libraries / system calls: Probably fair use, but explicitly allowed by GPL and other OS API/SDK licenses just to be safe.
      Communicating via proprietary network/IPC protocol: Almost certainly fair use, but some try to claim it isn't.
      Communicating via open network/IPC protocol: Certainly fair use.

      However, there is very little case law on this matter, so it is still possible that courts could decide that some uses of GPL code are acceptable, even thought they doesn't fit the rules of thumb above. If a judge were to rule that combining .NET assemblies was fair use in this case, then the most that Hamstersoft would have to do to be legal would be to distribute Calibre separately, and then users could legally run the combined application.

    20. Re:Before anyone gets ahead of themselves... by mysidia · · Score: 1

      Hamstersoft has two options: either immediately cease all distribution of the infringing binaries, or provide the full sources under one of the methods specified in the GPL.

      No.... Hamstersoft has two options that would please the open source community.

      Hamstersoft has a third option until forced to do otherwise: keep what they are doing; give it to their lawyers. Dispute any infringement claims or wait to be sued/ordered by a judge to do something different.

    21. Re:Before anyone gets ahead of themselves... by ByteSlicer · · Score: 1
      Derivative works is one of these grey areas that are improved in v3.
      Section 5.c of the GPL v3 states:

      c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.

      So even if you keep the original work in a separate DLL, the whole must still be released under the GPL3.

      Besides, if you remove the DLL the whole doesn't do anything usefull anymore, so it's clearly derived, even by v2 standards.

    22. Re:Before anyone gets ahead of themselves... by ByteSlicer · · Score: 1

      I meant two options to resolve the infringement, but yeah, there is that one too...

    23. Re:Before anyone gets ahead of themselves... by pavon · · Score: 1

      So even if you keep the original work in a separate DLL, the whole must still be released under the GPL3.

      ...assuming the new work is covered by the GPL3, in which case it is the whole for which the old code is a part. However, if something is determined to be fair use then you don't need any license to do so, and no license can trump your fair use rights (a contract/EULA sometimes can).

      This caveat is specifically spelled out in the definitions section of the GPL3:

      To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.

      If the adaptation does not require copyright permission (ie is fair use), then section 5 (actually the whole license), does not apply.

    24. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      No. This isn't relevant, but not for that reason. GPLv2 attempted to prohibit "linking" by non-GPL projects by asserting that projects that link to GPL code are "derivitave works", which copyright allows you to prohibit. This was always a very shaky theory.

      GPLv3 attempts to avoid this by simply making the license grant dependent on distributing any code which is "combined with (the GPL'd code) such as to form a larger program". So it's no longer asserting that the original copyright holder has rights over the work of someone who links to GPL'd code. It simply says that you loose your license if you distribute a program that links the GPL'd code under some other license terms.

    25. Re:Before anyone gets ahead of themselves... by swillden · · Score: 0

      Derivative works is one of these grey areas that are improved in v3. Section 5.c of the GPL v3 states:

      c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.

      So even if you keep the original work in a separate DLL, the whole must still be released under the GPL3. Besides, if you remove the DLL the whole doesn't do anything usefull anymore, so it's clearly derived, even by v2 standards.

      Except that the license doesn't get to define the meaning of "derivative work". If the GPL were a contract, it could define whatever limitations it wanted, but it's not, it's a uni-directional license that provides specific exemptions from the exclusive rights defined in copyright law. This means that if copyright law permits a given usage of copyrighted material, the GPL can't remove that permission.

      It's not clear whether or not copyright law considers dynamic linking to constitute creation of a derived work. If it does, then permission is required and the GPL can attach strings to that permission. If it doesn't, then no permission is required so Hamsersoft doesn't need the GPL's permission and therefore doesn't have to comply with its requirements.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    26. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      The distribution is missing files, it's been modified in some sense even if only in that.

      Regardless, it's missing source code, or any GPLv3-compliant offer for it.

    27. Re:Before anyone gets ahead of themselves... by Rakishi · · Score: 1

      Copyright law does not allow you to arbitrary distribute code created by others unless you are given permission to do so.

      In other words even if your part of the code is not legally a derivative work you cannot distribute the code that isn't your without permission. And if the GPL says you don't have that permission then you're down to copyright laws which pretty generally says you don't have permission.

    28. Re:Before anyone gets ahead of themselves... by ByteSlicer · · Score: 1

      Like Rakishi mentioned a bit lower, the license determines the terms under which the original work may be distributed. So you have two options:

      1. You do not agree with or abide by the license. In that case the license does not apply, and default copyright law comes into play. Which states that you cannot distribute a work without explicit approval of its author. There are a number of fair use cases that the law allows, but these are limited (educational, illustrational). So even though you can distribute your own executable that uses the DLL, you do not have permission to distribute the DLL unless you license the whole under the GPL.

      Notice that the grey area only lies in the question whether or not you are allowed to distribute your own executable (if it's considered derived, then only under the GPL).

      2. Your second option is to accept the terms of the GPL, and therefore license the whole under the GPL. This gives you a license that gives you the right to distribute the DLL.

      The intent, and the legal aspects of the GPL3 are very clear. Of course a judge may rule against it, but I wouldn't count on it (the GPL held up in all cases so far).

    29. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      So if I write software that makes any use of any GPLv3 library, I must disclose all my code?
      That can't be right, surely?

      If it is, we're going to have to stop using all GPL code and stop supporting any F/OSS projects using GPL. Nice.

    30. Re:Before anyone gets ahead of themselves... by JSBiff · · Score: 1

      Can someone clarify something for me: I'm having a hard time determining the nature of the alleged "infringement", but it sounds like the HamsterSoft people used a dll/so of the Calibre library, and dynamically linked linked that to HFEC? Or, perhaps they used a modified exe of the Calibre program, and modified it to load a non-GPL dll/so to provide some program functionality, while providing the source code only for the modification which caused the program to load the proprietary library?

      If that is the situation, then I'm with the grand-parent post (not that I'm a lawyer, and this is not legal advice - just an observation) - notwithstanding what the GPL itself says (because the GPL is not the final arbiter of law), it's not clear that such a situation legally constitutes infringing. It *might*, but the million dollar question is, *does dynamic linking create a derivative work*. I've heard a lot of people argue (not about this particular situation, but about the general situation of dynamic linking) that since such a program program wouldn't work without the linked library code, that must mean it's a derivative work, but the problem is, that has no actual basis in law. The legal definition of a "derivative work" is currently, well, ambiguous. In the most general case, it would seem that in order for one work to be a derivative of another, it must physically *contain* the other work - as a translation or adaptation to a different media (e.g. turning a book into a movie or play), or containing characters and ideas (think of writing your own 'Star Wars' book or movie - the work might generally be original, but if it claims to be continuing the story, and using the name 'star wars', I think it becomes a derivative).

      For the GPL, that last case about trying to create your own star wars or star trek or whatever, story, would probably be the best hope to hang its hat on, since by definition, a dynamic link library is separated from the programs that use it (although there is also an argument that a dll might cause some small inline functions to be included in the generated binary, which might trigger derivative status).

      So, the argument goes that the GPL can *only* impose restrictions on derivative works. *IF* (I'm not saying whether it is or isn't, it's just a question which, so far as I know, has never been addressed by courts or legislation) it's not legally creating a derivative work when you dynamically link a library, then even if the GPL says it's infringement to dynamically link, it's actually not since the GPL can only govern the works on which it holds copyright.

    31. Re:Before anyone gets ahead of themselves... by JSBiff · · Score: 1

      That still seems shaky to me. The GPL can only cover the distribution of the work for which the original author of the GPL'd work (and any actual derivative works) holds the copyright.

      Now, the clause which the parent mentions might qualify if you try to distribute the GPL'ed work together with a non-GPL'ed work - it would be similar to a license which says, "By using this software, I agree to give $49.99 to the author".

      The problem becomes, it seems to me, that maybe, perhaps, someone who wants to get around that, could just distribute them separately, as distinct acts of distribution - two download links, for example. In such a case, they might be able to claim that they complied with the terms of the GPL, and that this other program is completely distinct, and distributed under its own terms and license.

      After all, the GPL couldn't impose that all software in the world become subject to the GPL if anybody distributes a GPL'ed work - I think we all agree there are limits on the power of a copyright license to impose terms on users, and in particular, no copyright license can require terms on a completely separate work.

    32. Re:Before anyone gets ahead of themselves... by david_thornley · · Score: 1

      However, as another theory goes...

      Nothing gives me the right to redistribute GPLv3 code in general except the GPLv3. Therefore, to do that, I need to accept the GPLv3. There's a certain amount of logic in, therefore, requiring me to accept the GPLv3's definitions, since I have to accept the license as a whole. I think that (in the US) we need court rulings to know what the law is (or will be, or wioll haven be, depending on your philosophy of case law).

      I'm not a lawyer, this is not legal advice, and this should be taken as speculation from a guy wasting a day off by posting on Slashdot.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    33. Re:Before anyone gets ahead of themselves... by swillden · · Score: 1

      Copyright law does not allow you to arbitrary distribute code created by others unless you are given permission to do so.

      In other words even if your part of the code is not legally a derivative work you cannot distribute the code that isn't your without permission. And if the GPL says you don't have that permission then you're down to copyright laws which pretty generally says you don't have permission.

      But the GPL does provide blanket permission for arbitrary redistribution, with source, and Hamstersoft is providing source for the GPL code. The issue is that they're not providing source for other code that they dynamically link to GPL code. According to the GPL, that's not allowed... but it's not clear that copyright law considers combining via dynamic linking to be creation of a derivative work. If not (and I think it is, or should be, but it hasn't been determined), then Hamstersoft is able to use the GPL's permission to distribute the GPL'd code, with source, but has no legal obligation to avoid linking to their closed code.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    34. Re:Before anyone gets ahead of themselves... by the+saltydog · · Score: 1

      Cheap trick.

      Well, Ain't That a Shame?

      I think they should Surrender.

    35. Re:Before anyone gets ahead of themselves... by pavon · · Score: 1

      2. Your second option is to accept the terms of the GPL, and therefore license the whole under the GPL. This gives you a license that gives you the right to distribute the DLL.

      This wouldn't be necessary. Section 5 of the GPL only applies to "works based on the Program", and the GPL defines this as a modification that "requires copyright permission". Thus if linking DLLs were determined to be fair use, then then section 5 of GPL would not apply to the combined code, because it is not a "work based on the Program".

      Thus they would have a third option:

      3. Accept the terms of the license, understanding that your code is not a derivative work, and thus you only need to distribute the original source code according to the terms of the GPL.

      As an example, there are many applications in distributions shipping today that are basically GUIs (for system configuration, CD ripping, etc) that execute command-line applications to do the bulk of their work. It is widely agreed upon that using sysexec and pipes doesn't constitute a derivative work, and thus it is okay to distribute the GUI by itself (rather than with the command line tools as a whole), and under a different license than the GPL. If it were established that combining .NET assemblies also did not constitute a derivative work, then the same would apply in that situation.

      Finally, I didn't really make this clear, but I consider everything I've said to be legal nitpicking. I certainly wouldn't recommend that anyone go against the spirit of a license, including the general consensus of what constitutes a derivative work. I am personally of the opinion that linking DLLs, JARs and .NET assemblies does constitute a derivative work. I was just pointing that from a legal point of view it isn't a settled matter, and that the GPL was intentionally written as a copyright license not a contract, and thus relies on the court's definition of derivative work.

    36. Re:Before anyone gets ahead of themselves... by JSBiff · · Score: 1

      But you seem to be missing my point. The argument I'm making is that the people doing distribution, if they do it as two separate acts, can claim that when they distributed the GPLv3 code, they *did* comply with the terms and condition. Then, they did another distribution, completely separate, of a completely different package, which just happens to get combined on the users computer, by the end-user, not by the software developer.

      "Therefore, to do that, I need to accept the GPLv3. There's a certain amount of logic in, therefore, requiring me to accept the GPLv3's definitions,"

      No, no there's not. The definition of copyright is determined by statute and the courts. No license or contract can redefine what is or is not a derivative work. A copyright license, by definition, can only specify terms for the copyrighted work itself, or a derivative work. If another piece of software is not a derivative work, it has no authority over that other work.

      Do you think that the following copyright license on a e-book would hold up in court?

      "The author of the copyrighted work grants to you a license to make one copy of the copyrighted work. If you should read any other books (whether published on paper, or any other physical media [e.g. stone tablets, clay slabs, parchment, papyrii, cloth, etc], you agree that any other books read will constitute derivative works, and will be subject to the terms of this license."

      You can see an obvious problem - you might be declaring that copyrighted works NOT OWNED by your readers are defined as derivative works of your book, regardless of the fact that that you have no legitimate claim to those other works.

      I see it as being very much a similar situation with regards to dynamic link libraries/shared objects - they are separate works, for which there seems to be no right for the GPL copyright holder to claim any authority over them. I might be wrong, as far as the courts will determine, but that's how I see it.

    37. Re:Before anyone gets ahead of themselves... by DavidTC · · Score: 1

      No, you can't agree to a contract in one place, and then totally avoid it in another. If you're distributing GPL stuff, you have to follow the terms of the GPL in everything you do....you can't magically move actions into some other 'thing' and claim it's unrelated.

      Imagine how contracts would work otherwise. 'I agreed to give you money if you agreed to not do X. And then you did X!' 'Well, yes, but I didn't do X as part of the contract, I just did that randomly, unrelated to my agreement with you not to do X.'.

      This is plainly silly. And, yes, a license to distribute copyright work can, and often does, place limits on what else someone can do. (For example, TV stations that buy a license to distribute a TV show often have all sorts of rules about how they can advertise that show.)

      You're thinking of an EULA, which it would indeed be unreasonable for such terms, pretending EULAs were reasonable at all. But the GPL isn't an EULA. It's a distribution license, it's a real, actual, contract that gives benefits to both parties. If you agree to the GPL and do X, you are allowed to do Y. (As opposed to EULAs, which attempt to take away rights already granted under the law and give nothing in return.)

      However, yes, a loophole exists, in that one party could modify a GPL program into a DLL, and distribute it, entirely complying with the GPL...and another party could call that DLL, without distributing their own source.

      This has, in fact, actually happened a few times.

      But it requires at least two parties. You can't hack the program into DLL form and then yourself write another program to do that, because to distribute the DLL you have to agree to the GPL, including the parts that say calling such a DLL would be a derivative work.

      If you don't agree with that (Even if the court says it's legal.) you can't distribute GPL software. You can use it, yes, but not distribute it. The right to distribute it is predicated on agreeing with the GPL, and the GPL can, indeed, take away rights that are given under the law, in exchange for granting you the right to distribute the software. If the GPL demands you treat linked programs as a derivative work and release the code for them, you have to do that if you want to distribute the GPL software, even if the court says they aren't any such a thing.

      However, that loophole is totally irrelevant here. Distributing half-compiled blobs isn't complying with the GPL at all. Even if they want to make the argument that their 'viewer blob' is an actual DLL, and pretending that they (as opposed to someone else) can release such a DLL without releasing stuff that links to it...they haven't actually released the source to that blob either, the blob with actual literal GPL code in it, so that blob is utterly in violation of the GPL no matter how plausible this 'derivative work DLL loophole' is.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    38. Re:Before anyone gets ahead of themselves... by DavidTC · · Score: 1

      You don't need to make them do it manually, there's a command line calibre converter tool. (And no one claims that calling a command line is a derivative work.)

      --
      If corporations are people, aren't stockholders guilty of slavery?
    39. Re:Before anyone gets ahead of themselves... by Anonymous Coward · · Score: 0

      They could also negotiate a commercial license with the copyright holder...

    40. Re:Before anyone gets ahead of themselves... by ByteSlicer · · Score: 1

      For pure GPLv3-only code, yes, but only if you distribute your software. That's why they sometimes call the GPL a viral license.

      But libraries are usually released under the Lesser GPL license, which only applies to the library itself and not to the linked code. Dual/multi-licensed libraries are also common (in that case you can choose one of the licenses that suits you most).

    41. Re:Before anyone gets ahead of themselves... by Rakishi · · Score: 1

      But the GPL does provide blanket permission for arbitrary redistribution, with source, and Hamstersoft is providing source for the GPL code.

      Except it doesn't, it only gives you permission for redistribution if you follow the terms of the license. One of those terms is that if you use GPL code as part of a larger work then the whole work must be released as GPL. If you do not follow the terms then you do not have permission to redistribute GPL code.

    42. Re:Before anyone gets ahead of themselves... by david_thornley · · Score: 1

      The definition of copyright is determined by law, yes, and it says "Don't copy that!". If copyright is not involved, no version of the GPL applies.

      However, once you are doing something with GPLed software that's not normally permissible under copyright law, you have to accept the license, and its terms. You have the option of not doing whatever with the software, or complying with the license, or violating the law. If the GPL says you need to treat works with dynamic linking as derived works, or the authors of the GPL do (establishing intent), the courts may very well rule that way. If this bothers you, don't use the software or get some clarification from the copyright holder. Fundamentally, if your product needs to have the GPLed software, you have to abide by the rules.

      Your ebook example is irrelevant; it lays claim to works that contain none of the copyrighted material, while the GPL at worst extends your obligations to software that is linked with the GPLed software. Don't treat laws as if they were odd corners of the C++ standard. Don't attempt to push analogies to logical extremes, and don't make transparent attempts to violate the law by doing two things, neither of which violates the law by themselves, and claiming they're independent when they aren't.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    43. Re:Before anyone gets ahead of themselves... by JSBiff · · Score: 1

      You still do not seem to be understanding the issue. Yes, you're absolutely right that if the COURTS determine that dynamic linking creates a "larger work", then the GPL applies.

      What you don't seem to be grasping is the part where, if the court says it isn't a derivative work, then Hamstersoft *HAS* fully complied with the terms of the GPL and HAS PERMISSION to distribute the software by the terms of that self-same GPL.

      You don't get to determine whether a work is or is not infringing, and neither do I. Only the courts do. Licenses can say whatever they want, but it's the courts which ultimately get to interpret the license and tell you what is and is not "complying".

    44. Re:Before anyone gets ahead of themselves... by MikeBabcock · · Score: 1

      If the license isn't enforced, Hamstersoft has no rights at all due to Copyright.

      You can't have your cake and eat it too -- the GPL lets you do things that would otherwise be illegal. If you want to take your chances, ignore it and go to court.

      --
      - Michael T. Babcock (Yes, I blog)
  18. Ummm?? by neo8750 · · Score: 0

    LGPL Hamster Free eBook Converter made by HamsterSoft and based on Calibre-engine created by Kovid Goyal and inherits all GNU GPL 3.0 restrictions. NOTE PLEASE: Everybody may use Hamster Free eBook Converter on any computer at home, in business and government organizations without any restrictions and any amount of hosts. You don't need to register or pay for Hamster Free eBook Converter. No one needs to pay for any further updates and plugins. Source code

    http://media.hamstersoft.com/hamster.ebookconverter.project.zip thats the source got that from: http://ebook.hamstersoft.com/en/support

    1. Re:Ummm?? by Anonymous Coward · · Score: 0

      Yay, another retard who doesn't understand this. The quote suggests they change the license.

      But that's not it. It's not the full code, thus not compliant with the GPLv3. Did you even read the links/comments here? There's a bunch of idiots like you who said the same stupid thing.

      Now to sit back and await a flamewar. :D

    2. Re:Ummm?? by Anonymous Coward · · Score: 0

      Just read what others have written about that link/sourcecode

  19. Re:Infection. by darkshadow88 · · Score: 1

    It's because of Hampster Dance. 13 years later, people still think it's spelled "hampster".

  20. THEY DID NOT RELEASE BULK OF CODE by Anonymous Coward · · Score: 0

    Would someone mod down the parent post. If you would have read the article, you'd learn that they neglected to post the bulk of the source code, and instead released a compiled binary with some wrappers around it. An outright dirty trick.

  21. Without copyright, annotated disassemblies by tepples · · Score: 1

    Without copyright, nobody would be forced to share their code

    Without copyright, people would be making and openly trading thoroughly commented disassemblies of proprietary software.

    Of course, you would be free to reverse engineer it

    And students with more time than money would do just that.

    1. Re:Without copyright, annotated disassemblies by man_of_mr_e · · Score: 1

      I'm sorry, but a commented dissassembly does me almost no good if I don't know assembler (I do, but most people don't).

    2. Re:Without copyright, annotated disassemblies by tepples · · Score: 1

      Source code in any programming language doesn't do you good unless you know that language, and most people don't know any given language. I don't see how assembly language is any different.

    3. Re:Without copyright, annotated disassemblies by man_of_mr_e · · Score: 1

      Well, i would guess less than .01% of all software developers know assembly. So it's pretty rare, and it requires a lot more skill to master.

    4. Re:Without copyright, annotated disassemblies by zget · · Score: 1

      And it's still also pain in the ass, even if you know assembly. I do, but reading and perfectly understanding, and then commenting all that code is a really huge process. It doesn't even allow modifying it as easily as full source code, you have to make jumps to codecaves and you break stuff extremely easily. There's really no comparing the two, it's completely different league even for people who know it.

    5. Re:Without copyright, annotated disassemblies by 1729 · · Score: 2

      Well, i would guess less than .01% of all software developers know assembly. So it's pretty rare, and it requires a lot more skill to master.

      Don't CS programs still require assembly? I had to take a course in assembly as an undergrad, and also had to use assembly quite a bit in my compiler courses. 1 developer in 10,000 seems way too low. (For what it's worth, I've never met a really good developer who couldn't program in assembly. I don't mean that they recall all of the syntax of a particular assembly language; only that they can map high-level code to pseudo-assembly language.)

      As for skill, assembly is actually easy to write, though not that easy to read. It's just a combination of some simple primitives: load something into a register, or perform some arithmetic operation, or test a condition, or jump to another location in the code. Conceptually, it's much easier than a language like C++.

    6. Re:Without copyright, annotated disassemblies by man_of_mr_e · · Score: 1

      Considering that so many developers haven't gone through CS degrees, it's pretty easy to understand. There's lots of developers with no degree at all. There's lots of developers with degrees in other fields. There's lots of developers that too community college courses that don't provide a full CS discipline.

      It's very easy to expect 1 in 10,000 knows assembler. In fact, of the 40 or 50 programmers I know personnaly, i'm the only one that knows assembler.

    7. Re:Without copyright, annotated disassemblies by TangoMargarine · · Score: 1

      They require assembly at my university for the CS and SE majors, yes. That said, I shudder to imagine trying to actually make any modifications to the assembly version of any major-studio release, though. If you're somebody who can do that without losing your mind, my hat is off to you.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
  22. Re:Infection. by kthreadd · · Score: 1

    The behavior of a virus.

    No it's not. If I make a piece of software and releases it under closed proprietary license no one would accuse it of being a virus, however if I opened it up just a bit and said that other people are free to use it just as long as they do the same then it's virus? Don't want to comply? Don't use it.

  23. Re:NOVEL IDEA !! HIRE AN MPAA LAWYER !! by maxwell+demon · · Score: 1

    The ironing.

    I hope it's at least done with a steam iron. :-)

    --
    The Tao of math: The numbers you can count are not the real numbers.
  24. Re:Who gives a shit? by copsi · · Score: 1

    Different kinds of free though.

    Calibre developers chose (either consciously or through ignorance) the GPL licence, which means free as in free speech. Nobody should be able to distribute programs based on the Calibre code without also releasing the source. Hamstersoft software, however, is free as in free beer (since they don't distribute sources, claim there are trade secrets in their software etc.).

  25. He is abusing the DMCA. by pavon · · Score: 5, Insightful

    The DMCA take-down notices are to be sent to the providers that are hosting the content. The search engines are not hosting this content, and sending them take-down notices is a heavy-handed abuse of the law.

    So either John misunderstands the DMCA or is willfully abusing it. Either way it makes it a lot harder to sympathize with his attempt to address violation of copyright law, when he himself is willing to resort to the very behavior of other copyright abusers.

    But at the very least, shouldn't the OSS community have an army of lawyers willing to work probono, or financed by various foundations, for this kind of thing exactly?

    What exactly do you expect them to do? The offender is in Russia and is hosted in Russia. How is a small donation-funded organization supposed to enforce copyright in situations where even large well-funded companies like Microsoft have been unable to do so?

    People sometimes get away with breaking the law, especially far away countries. It sucks, but it's life and you have to learn to accept it. The people who won't are exactly the ones that drive us further and further into a police state in their unending drive to "decrease crime", not understanding the trade-off they are making.

    1. Re:He is abusing the DMCA. by Kjella · · Score: 2

      The DMCA take-down notices are to be sent to the providers that are hosting the content. The search engines are not hosting this content, and sending them take-down notices is a heavy-handed abuse of the law. So either John misunderstands the DMCA or is willfully abusing it.

      Or perhaps you're the one without a clue. DMCA takedowns apply to both hosting and search engines. Read it yourself here, I'll quote the most important bits:

      (d) Information Location Tools. -- A service provider shall not be liable (...) for infringement of copyright by reason of the provider referring or linking users to an online location containing infringing material or infringing activity (...) if the service provider (...) upon notification of claimed infringement (...) responds expeditiously to remove, or disable access to, the material that is claimed to be infringing or to be the subject of infringing activity (...)

      --
      Live today, because you never know what tomorrow brings
  26. Re:Infection. by e9th · · Score: 1

    From now on, thanks to your misspelling and their behavior, I'll just call them Dumpstersoft.

  27. Re:NOVEL IDEA !! HIRE AN MPAA LAWYER !! by chromas · · Score: 1

    If you iron it enough then it could definitely become irony.

  28. They can not be forced to disclose the source code by Cigaes · · Score: 2

    They can not be forced to disclose the source code. This is a common misconception about the GPL.

    If a GPL violation goes to court, the judge can order the infringing party to stop the distribution and pay damages to the copyright owner, but he will not order the disclosure of the source code. The disclosure of the source code is only a gesture that most FOSS developers will accept to drop the charges.

    Of course, if the software is only a thin layer of sugar around a core of GPL code, stopping the distribution means closing the business.

    On the other hand, the situation can be reverted: the GPL code may be just a small, non-essential part of the software. Think readline, for example: a software is more comfortable with line editing, but it is in no way necessary. In such situation, the violator may decide to pay the damages and remove the GPLed code from its software, to keep in business with its proprietary model.

  29. Re:Infection. by hairyfeet · · Score: 1

    But this makes me think of something I've been puzzling over for awhile now....WTF is wrong with BSD? Seriously, is it broken? Is it shit? Is it a hard to use incompatible mess, what?

    Because I just don't get why if you don't want to play the GPL game you'd even bother with GPL code when BSD is right there. hell it is good enough for Apple, it was good enough for MSFT when they needed a temporary TCP/IP stack to get the original WIN NT out the door on time, so WTF? If these companies don't want to play the GPL game then just don't mess with GPL code, is that so damned hard? To me it is almost like a klepto, that just can't be happy unless they are snatching something.

    Either use BSD or just buy off the developer so they'll give you a non GPL license to their code, is that really so hard to follow? It seems to me a hell of a lot more logical than all the hoop jumping and possible bad press when someone finds out they ripped GPL like in TFA.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  30. So what? Who's going to do anything about it? by jasenj1 · · Score: 0

    So some company is violating GPL v3, who is going to do anything about it? Who's going to hire the lawyer(s) to take them to court to get settlement money - the vast majority of which will likely to go the lawyers? Or do you report them to "the authorities" and some government funded lawyer chases them down?

    Even if you do go to court and get a judgement against the company, then what? Hamstersoft doesn't sound like a company with deep pockets. So they declare bankruptcy, and the officers open another company doing the same thing with a different name.

    Perhaps I'm overly cynical or naive, but I see the effort of enforcing the GPL to be greater than the harm done by violating it. Yes, perhaps the company deserves to be driven out of business for flagrantly violating GPL and stealing other peoples' work. But it will take a lot of effort & money to make that happen.

  31. Re:Infection. by Registered+Coward+v2 · · Score: 3, Insightful

    Surely the behaviour of a criminal, stealing code that they didn't intend to obey the licence of?

    They didn't steal anything - everyone still has the original code. No one lost anything. What they did was a copyright violation, not theft.

    Isn't that the standard /. argument when someone equates copyright violations with theft?

    Of course, this is the GPL so out come the pitchforks and torches...

    And this will be moded down by someone who disagrees or dislikes having /. hypocrisy pointed out...

    --
    I'm a consultant - I convert gibberish into cash-flow.
  32. Re:Infection. by badboy_tw2002 · · Score: 1

    Lets be fair, copyright violation is not theft, no matter who does it or what copyright is violated. Nothing was stolen, nothing was "lost" here. The original code is still safe and sound.

  33. Re:Infection. by Kielistic · · Score: 1

    BSD has pretty much nothing to do with Calibre would be the main reason. GPL != GNU/Linux.

  34. pedantry by nog_lorp · · Score: 1

    Now that app is clearly in violation of the GPL.

    FTFY. An app cannot be a violation, the violation was the act of noncompliance! /pedantry

  35. Re:They can not be forced to disclose the source c by bk2204 · · Score: 2

    It depends on what you sue for. There is a thing called "specific performance," which is basically forcing the defendant to comply with the terms of the license or contract in cases where there is no adequate remedy in monetary damages. An injunction is also possible, and even likely, in copyright infringement cases.

  36. Pirating BSD-licensed code is possible by Anonymous Coward · · Score: 0

    It is easy to pirate BSD-licensed code too. Not everyone includes the notices required by the BSD license when distributing such code as a part of some other software in binary-only form.

    For example, AVR libc is under BSD license. Many AVR microcontrollers are flashed with programs that have been compiled with AVR-GCC and contain some code from AVR libc. It's easy to skip including the BSD license text and copyright notices when shipping products that include microcontrollers with such code. It's especially easy because most people won't have any clue that there is a microcontroller in the product, let alone what code it might contain.

    1. Re:Pirating BSD-licensed code is possible by mysidia · · Score: 1

      For example, AVR libc is under BSD license. Many AVR microcontrollers are flashed with programs that have been compiled with AVR-GCC and contain some code from AVR libc.

      Bad example. Linking a C program against a libc does not include enough code to make the program a derivative work of the libc; they are not bound to distribute the final product under the BSD license despite using a BSD licensed compiler.

      Only the libc itself needs to be distributed in accordance with the terms of the license, if they also distribute a copy of the libc.

    2. Re:Pirating BSD-licensed code is possible by geminidomino · · Score: 1

      Linking a C program against a libc does not include enough code to make the program a derivative work of the libc; they are not bound to distribute the final product under the BSD license despite using a BSD licensed compiler.

      While these two clauses are both true, strictly speaking, they're also unrelated.

      The nice part about the BSD license is that it doesn't matter how much code you include, you're not obligated to distribute the final product under any given license.

    3. Re:Pirating BSD-licensed code is possible by Anonymous Coward · · Score: 0

      The license of the final product as a whole can be anything, of course. Since the example is about microcontrollers, they are linking statically against the libc and thus often distributing a significant part of the libc (depends on how many functions are used from it). Since they are distributing a (partial) binary copy of the libc, they must follow the terms of the BSD license for the libc part of the software (not the whole work):

      "Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution."

      Many people forget the above clause of the BSD license. The rest of the code can be under any license and the BSD license doesn't restrict that. But the copyright notice and the BSD license text must be included if you distribute a binary that includes BSD-licensed code.

    4. Re:Pirating BSD-licensed code is possible by TangoMargarine · · Score: 1

      So basically, if you change one line of code and recompile, you can put *that* under any license you please, right?

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    5. Re:Pirating BSD-licensed code is possible by Anonymous Coward · · Score: 0

      If you modify BSD-licensed code, you can put the modifications under any license (*). This doesn't allow you to remove the BSD license from the code unless you remove all parts that were under the BSD license. As long as the binary you distribute includes code derived from BSD-licensed software, you must include the relevant copyright notices and a copy of the BSD license text when you distribute the binary. You don't need to distribute any source code because the BSD license doesn't require it. The license of the work as a whole can be anything (the BSD license doesn't spread itself to the work as a whole).

      (*) The modification needs to be significant enough, which isn't a big requirement, but adding one line or changing the indentation of the code or renaming a few variables probably isn't enough.

  37. lolwut? by Anonymous Coward · · Score: 0

    It turns out that one calibre contributor is now reporting that his code was pirated for Hamstersoft.

    But piracy is people on the high seas hijacking vessels and stealing their cargo, right? Oh wait, this was GPL code we are talking about so we throw out all the "but it's not theft" or "it's not piracy" bullshit excuses that come up when it comes to proprietary software or movies/music/ebooks/etc.

    1. Re:lolwut? by Requiem18th · · Score: 1

      No, piracy is copying of content by RIAA or MPAA members or software from BSA members. Stealing GPL is good old American business sense unless you are a communist hippie terrorist child pornographer atheist.

      --
      But... the future refused to change.
    2. Re:lolwut? by Travelsonic · · Score: 1

      Yawn,.... another moronic false contradiction argument that wrongly presumes Slashdot as some sort of hive mind and not a community driven by a lot of individuals with many differing opinions.

      Really, every time these discussions come up, the same arguments are made - and I keep asking if the people making said arguments have any understanding of rudimentary logic.

      --
      If you believe in privacy, and believe you have "nothing to hide" at the same time, you're a goddammed idiot
  38. Re:Infection. by man_of_mr_e · · Score: 1

    Actually, it's a myth that Microsoft used BSDL code. It's true, they used code from the Berkeley Standard Distribution of Unix, but this code predates the BSDL license and Microsoft paid for the license.

    So, what they used was a non-BSDL licensed version of the code, and thus they did not have to conform to the BSDL license.

  39. Re:Infection. by man_of_mr_e · · Score: 1

    Copyright Infringement, not "copyright violation"

  40. Re:Infection. by Bert64 · · Score: 1

    Besides, how would a commercial software company react if someone incorporated portions of their source code into their own product without complying with whatever terms they demanded?

    What if someone took the source code to windows that was leaked a couple of years back, and used it to produce their own clone version? You don't think MS would go after then with every lawyer they could find for copyright infringement?

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  41. The legal protection of trade secrets. by westlake · · Score: 1

    Not to mention trade secrets have no protection under law, in fact that's why copyright law exists in the first place.

    Never say never.

    Approximately 40 states have adopted the model Uniform Trade Secrets Act (USTA). The USTA defines a trade secret as "information, including a formula, pattern, compilation, program device, method, technique, or process, that: (i) derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use, and (ii) is the subject of efforts that are reasonable under the circumstances to maintain its secrecy."

    The USTA specifies remedies for violation of trade secrets including injunctions, damages, and attorney's fees. It also gives courts the authority to grant protective orders to ensure the secrecy of a trade secret during the discovery phase of litigation, and prevents disclosure of confidential information by witnesses.

    Federal Protection for Trade Secrets

    The Economic Espionage Act of 1996 federally criminalizes the theft or misappropriation of trade secrets under two key provisions. The first makes it illegal to steal trade secrets for the benefit foreign powers; the second, makes it illegal to steal trade secrets for commercial or economic purposes regardless of who benefits.

    Trade Secrets

    The reverse engineering of software faces considerable legal challenges due to the enforcement of anti reverse engineering licensing provisions and the prohibition on the circumvention of technologies embedded within protection measures. By enforcing these legal mechanisms, courts are not required to examine the reverse engineering restrictions under federal intellectual property law. In circumstances involving anti reverse engineering licensing provisions, courts must first determine whether the enforcement of these provisions within contracts are preempted by federal intellectual property law considerations. Under DMCA claims involving the circumvention of technological protection systems, courts analyze whether or not the reverse engineering in question qualifies under any of the exemptions contained within the law.

    Frequently Asked Questions (and Answers) about Reverse Engineering

    1. Re:The legal protection of trade secrets. by dwater · · Score: 1

      Not to mention trade secrets have no protection under law, in fact that's why copyright law exists in the first place.

      Never say never.
       

      I don't think he did, did he?

      --
      Max.
  42. Re:Infection. by Tubal-Cain · · Score: 1

    Because I just don't get why if you don't want to play the GPL game you'd even bother with GPL code when BSD is right there.

    It is? Would you care to point out the BSD-licenced ebook program they could have used instead?

  43. Re:Infection. by Anonymous Coward · · Score: 0

    False, though there is a grain of truth to what you say. The BSDL dates from 1988, MS Winsock dates from 1990 and does in fact include BSD licensed code. However, you are correct in that MS paid to license the code. It's just that some of the code they licensed from Spider was built on BSD licensed code. By 1994 MS had rewritten Winsock from scratch and it no longer included BSD licensed code, however there was no reason to rewrite the associated utilities like ftp, rcp and rsh so to this day, MS still ships BSD licensed code.

  44. Re:Infection. by man_of_mr_e · · Score: 1

    Actually, you are also only partially correct. While you're correct that Microsoft licensed the code in 1990, the copyrights on the code (as found via a strings search) shows the copyright date on the code is 1983. This is the code that Spider licensed from Berkeley, and it predates the BSD license. Spider was licensed to resell the code.

  45. Re:Infection. by ByteSlicer · · Score: 1

    Everytime when we're discussing people pirating proprietary software or games (or movies and music for that matter), people are saying copyrights should be removed and that it's somehow justified to pirate.

    Not exactly. In general, the slashdot crowd is against software patents and DRM, which are a completely different matter. That, and the Disney copyright extension acts, which steal from the public domain.

  46. Re:Infection. by shentino · · Score: 1

    GPL only exists because of copyright in the first place, both as a source of necessity as well as where it gets its effectiveness from.

    Without copyright, the GPL would be both useless, and superfluous.

  47. Re:Infection. by Arker · · Score: 1

    I agree that it is just as stupid to refer to this as piracy as it is to refer to any other case of copyright infringement as piracy. Arr.

    That said, this does appear to be a very clear-cut case of copyright infringement, and it's a for profit company trying to extract money for someone elses work here, *precisely* the sort of case where copyright law is most defensible.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  48. protect OSS software effectively as small OSS devs by Anonymous Coward · · Score: 0

    - what institutions do we have in place to protect OSS software effectively as small OSS devs? Do such institutions work? In this case, thus far, they don't seem to be working.

    If you have given given the FSF the full copuright to the code, and make it GNU project, they go after the culprits. But if you guys are the sole owners, its your duty to protect your property.

  49. Re:Infection. by PopeRatzo · · Score: 1

    They didn't steal anything - everyone still has the original code. No one lost anything. What they did was a copyright violation, not theft.

    Before someone dislocates a shoulder throwing garlands of +1 Insightful mods at the above comment, take a moment and remember why GPL even exists. Because of copyright. This case is a very good example of why GPL is so important, and so worth preserving, because its purpose is to keep free software free.

    Hamstersoft has to be made into an example. There's no hypocrisy here.

    --
    You are welcome on my lawn.
  50. Re:They can not be forced to disclose the source c by mysidia · · Score: 1

    They may claim they never signed/agreed to the GPL, and therefore aren't bound by any requirements of it. Specific performance remedy is a type of equitable relief and requires a valid contract/agreement between the parties.

    In that case, the plaintiff would have little choice but to pursue a copyright infringement claim, and specific performance would be off the table.

    Without agreeing to the GPL, with the code copyrighted, and no license, there would be infringement... so the remedy options would basically be monetary/statutory damages or injuctions.

    Disclosure of source might be a settlement option, but it's not a thing the judge may order, any more than the judge could simply assign copyright of the product to the open source developer whose copyright was infringed.

  51. Re:They can not be forced to disclose the source c by rahvin112 · · Score: 2

    Without agreeing to the GPL they are in intentional violation of copyright. The means (under US law) max statutory damages of several hundred thousand dollars PER distribution (which if they even distributed it a dozen times could be several million dollars) and the court will probably award punitive damages of up to 9 times the statutory damages for intentional infringement. If they sold a hundred copies of the software they could conceivably be hit with a hundred million dollars in statutory damages and punitive awards.

    Although you are right they could claim they didn't agree to the GPL, but by doing so they would make the damages much much worse. This is the reason in nearly every single case where legal proceedings are started companies comply with the GPL, because not agreeing to the contract contained in the GPL is a far worse fate then complying with the terms. People forget that this is by design, Stallman deliberately used copyright law (and it's massive damages) to create a license that creates a situation where complying with the license is the least damaging result to an infringer.

    Now this is all hypothetical as the company in question is Russian and unless you are good friends with Putin nothing will happen to the people or companies involved..

  52. Re:Infection. by Anonymous Coward · · Score: 0

    Actually, you are also also wik.

    Wi not trei a holiday in Sweeden this yer ? See the loveli lakes. The wonderful telephone system. And mani interesting furry animals Including the majestic moose.

    A moose once bit my sister...

    No realli! She was Karving her initials on the moose with the sharpened end
    of an interspace toothbrush given her by Svenge - her brother-in-law - an Oslo dentist and star of many Norwegian movies: "The Hot Hands of an Oslo Dentist", "Fillings of Passion", "The Huge Molars of Horst Nordfink"...

    Mynd you, moose bites Kan be pretti nasti...

  53. Re:Infection. by The+Dawn+Of+Time · · Score: 1

    How could it be superfluous? What magical mechanism would make people give up their source code absent copyright? Seems more likely to me that it would be an even more closely guarded secret for many projects.

  54. Apparently resolved... by AliasMarlowe · · Score: 2

    The EULA for the free eBook converter now contains some extra stuff, such as:
    "The source code of Hamster Free eBook Converter inherits GNU GPL 3.0 rights from Calibre. You may all operations with it permitted by law. GNU GPL 3.0 restrictions must be met. You will not use Hamster Free eBook Converter for illegal purposes. You will comply with all export laws. Hamster Free eBook Converter is licensed, not sold."
    which looks like it was written hastily, and
    "GNU GPL 3.0
    Calibre source codes: http://code.google.com/p/calibre-ebook/downloads/list
    Hamster Free eBook Converter source codes: http://ebook.hamstersoft.com/en/support
    License GNU GPL 3.0: http://www.gnu.org/licenses/gpl.html"
    So, they've included the GPL in their license terms, and have published the source code for the eBook converter. Looks like yet another win for GPL.

    --
    Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    1. Re:Apparently resolved... by Anonymous Coward · · Score: 0

      You will not use Hamster Free eBook Converter for illegal purposes. You will comply with all export laws.

      So they went and added additional restrictions, AKA still in violation.

    2. Re:Apparently resolved... by boristhespider · · Score: 1

      Someone noted in the comments on the blog article that the "source" that HamsterSoft posted includes a binary blob for their UI. That may or may not be in violation of the GPL3 (I've honestly no idea; does GPL3 require you to publish your complete source code and not just those section based on or copied from GPL3 code?) but it's not quite posting source.

    3. Re:Apparently resolved... by tehcyder · · Score: 1

      You will not use Hamster Free eBook Converter for illegal purposes. You will comply with all export laws.

      So they went and added additional restrictions, AKA still in violation.

      How can requiring that someone obey the law be classified as a violation of the original licence?
      Anyway, illegal agreements are void. If I had an contract with a hit man, I couldn't sue him through the courts if he failed to carry out the murder.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    4. Re:Apparently resolved... by GooberToo · · Score: 1

      If the UI simple calls out and invokes the other code, it can very much be in compliance with their source obligation.

    5. Re:Apparently resolved... by boristhespider · · Score: 1

      Thanks. I was wondering if it was still like that - it was my understanding that GPL2 allows this kind of thing, though I could've been wrong on that, too....

    6. Re:Apparently resolved... by shutdown+-p+now · · Score: 1

      If you ask RMS, neither GPLv2 nor v3 allows this. What the law says is a different matter, and I don't know if there is any relevant precedent.

  55. Re:Infection. by camperslo · · Score: 1

    Surely the behaviour of a criminal...

    There is a notice at the bottom of the related web page acknowledging the license. Hopefully that's a sign that they're working towards complying.
    The app is free - so not a very hard core criminal unless there's malware?
    http://ebook.hamstersoft.com/

    "Hamster Free eBook Converter made by HamsterSoft and based on Calibre-engine created by Kovid Goyal and inherits all GNU GPL 3.0 restrictions."

    Hopefully there is no incompatible code in there from others. I looked at the binary with a text editor and saw a comment near the end that may be part of code signing:

    "thawte, Inc. Certification Services Division/(c) 2006 thawte, Inc. - For authorized use only" (I don't know for sure if that's a problem, I don't do windows. No Linux, OS X, or iOS versions visible)

    Maybe someone should see if there's FFMPEG or MPLAYER code in their video conversion utility?

  56. Re:Infection. by LingNoi · · Score: 1

    They broke the terms and conditions of using the source code they agreed to when distributing said code. The article summary however is incorrect.

    They can simply stop distributing said application (might not be 100% correct), they're not forced to redistribute their source code, however it's not like we'd gain anything from them distributing code which they just downloaded anyway. No need for them not to do it really.

  57. Re:Infection. by LingNoi · · Score: 1

    No one says that, however many people always mention the hypocrisy whenever there is a GPL violation. GPL haters gunna hate.

  58. Re:Infection. by metacell · · Score: 1

    Precisiely, it's a symbiote, not a virus.

  59. Re:Infection. by Anonymous Coward · · Score: 1

    Surely the behaviour of a criminal, stealing code that they didn't intend to obey the licence of?

    They didn't steal anything - everyone still has the original code. No one lost anything. What they did was a copyright violation, not theft.

    Isn't that the standard /. argument when someone equates copyright violations with theft?

    Of course, this is the GPL so out come the pitchforks and torches...

    And this will be moded down by someone who disagrees or dislikes having /. hypocrisy pointed out...

    Well, the difference is: people pirating movies aren't trying to make a profit out of it.
    (Whereas the GPL basically exists to stop people from making a profit out of something ;) )

  60. Re:Infection. by Sique · · Score: 1

    GPL wasn't created to abolish closed source. GPL was created to make sure that once free code stays free. When the MIT fixed some bugs in the original UNIX code and added some of the code themselves, UNIX Source labs suddenly stepped up, pointed at the source code license and claimed ownership for all the stuff MIT created. Additionally they took the code, incorporated it in the original UNIX and forbid MIT to provide their source code to others.
    That's when RMS came into play and created a license which guaranteed that this can't happen again.

    And if some people continue to claim the BSD license was so much more free and better, they should be told this little story and explain, how the BSD license would have avoided this problem.

    --
    .sig: Sique *sigh*
  61. Re:They can not be forced to disclose the source c by Gaygirlie · · Score: 1

    They may claim they never signed/agreed to the GPL

    That'd be the same as admitting to the court that they knew they were in breach of copyright law but decided to willfully continue anyway. NO sane company would tell that to the court!

  62. It appears to have gone by Ptolom · · Score: 1

    Looking at their website, all trace of the Ebook software seems to have vanished, I'm glad to say.

  63. TdR doesn't like it if you don't violate the licen by Anonymous Coward · · Score: 0

    TdR doesn't like it if you don't violate the license. If, for example, you take BSD code and GPL it, he goes completely librarian-poo. If it had been decently closed up, he wouldn't care: after all the original version is still available. But since the original version is still there when you relicense as GPL, this is a huge problem.

  64. Re:Infection. by Omnifarious · · Score: 1

    That's a really interesting question. And I think one of the few ways patents could be validly applied to software.

    Copyright and patent are supposed to be a trade, the public gives up a right in order to get a public good.

    In this case, the public good is the source code. The right we give might be something like copyright or patent. If you want some sort of protection against your software being treated as being in the public domain, then you will put the source code for that software on file, and it will be released in 5 years when your protection expires.

    That's a kind of grant of government monopoly I could actually get behind.

    Of course, it encourages the creation of trojan horses. Software that you _want_ to have distributed widely and freely so that you can infect as many computers as possible with code that does stuff the owners of those computers would be angry about if they knew before they installed it.

    I'm not sure how to protect against that. Maybe that would be a reason people would choose work under copyright or with available source over other stuff? I know that's a big part of the reason I have a huge preference for Open Source software.

  65. Re:Infection. by Omnifarious · · Score: 1

    Well, the difference is: people pirating movies aren't trying to make a profit out of it.
    (Whereas the GPL basically exists to stop people from making a profit out of something ;) )

    I wish that misconception would go away. I really wish, for example, that the Android marketplace would tell you when an app met the Open Source definition. I would feel much better about installing it then. And I would even pay for those apps from the Marketplace.

  66. Re:Infection. by Omnifarious · · Score: 1

    I'm one of the people who says that. And I agree with you. This isn't theft. It's a copyright violation.

    Just because I think calling copyright violation 'theft' is highly misleading doesn't mean that I don't think copyright should exist. And this case, someone repackaging someone else's work in order to make a profit, is a case I think is clearly wrong.

  67. Don't blame the "uneducated" by rubypossum · · Score: 1

    I never went to University for CS and I studied assembly. In fact, I wrote a CGI library for Linux x86 assembler that didn't link with libc. This allowed you to write a native CGI application in 120 bytes! Although it only supported GET requests and I only wrote atoi() of all the conversion functions in libc. Pretty sweet if you ask me. This time that I spent so long ago has paid for itself many times over. And even more as I transition into iOS programming. Contrast that with my buddy Daniel who graduated from a state school with a masters in CS and doesn't know ANY assembler. He learned Java byte code, but never native assembler. He and his professors espouse the "but you'll never need to know that" school. It's a waste of time because the JIT/compiler can write better assembler than you can. Pshaw, children these days, lawns needing vacated.

    --
    I have a theory that the truth is never told during the nine-to-five hours. - Hunter S. Thompson
  68. Told Russian Linux community about it by Anonymous Coward · · Score: 0

    Hope they will DDoS the hell out of hamstersoft.

  69. Re:Infection. by tehcyder · · Score: 1

    Copyright Infringement, not "copyright violation"

    Why? because it sounds less serious?

    --
    To have a right to do a thing is not at all the same as to be right in doing it
  70. Re:Infection. by tehcyder · · Score: 1

    Everytime when we're discussing people pirating proprietary software or games (or movies and music for that matter), people are saying copyrights should be removed and that it's somehow justified to pirate.

    Not exactly. In general, the slashdot crowd is against software patents and DRM, which are a completely different matter. That, and the Disney copyright extension acts, which steal from the public domain.

    No, the usual argument here is that because you are just digitally copying something and not stealing it, copyright infringement is not an offence at all

    The illogicality of saying this and then whining about people breaking the GPL is almost funny.

    --
    To have a right to do a thing is not at all the same as to be right in doing it
  71. Re:Infection. by tehcyder · · Score: 1

    I agree that it is just as stupid to refer to this as piracy as it is to refer to any other case of copyright infringement as piracy. Arr.

    That said, this does appear to be a very clear-cut case of copyright infringement, and it's a for profit company trying to extract money for someone elses work here, *precisely* the sort of case where copyright law is most defensible.

    Copyright law is either defensible or not. The status of the infringer is as irrelevant as the infringee. You can't say "copyright is wrong and illogical except when it involves free-as-in-beer participants".

    --
    To have a right to do a thing is not at all the same as to be right in doing it
  72. Re:Infection. by tehcyder · · Score: 1

    Well, the difference is: people pirating movies aren't trying to make a profit out of it.

    Some of them are. And what's the difference anyway?

    If Sid Student downloads Transformers 4 and doesn't buy it, and Pete Pirate downloads the same film and sells a copy, in both cases no money will go to the copyright holder. And the potential sale is lost to the copyright holder in either case.

    --
    To have a right to do a thing is not at all the same as to be right in doing it
  73. Re:Infection. by Anonymous Coward · · Score: 0

    Surely the behaviour of a criminal, stealing code that they didn't intend to obey the licence of?

    They didn't steal anything - everyone still has the original code. No one lost anything. What they did was a copyright violation, not theft.

    Isn't that the standard /. argument when someone equates copyright violations with theft?

    Of course, this is the GPL so out come the pitchforks and torches...

    And this will be moded down by someone who disagrees or dislikes having /. hypocrisy pointed out...

    Well, the difference is: people pirating movies aren't trying to make a profit out of it.
    (Whereas the GPL basically exists to stop people from making a profit out of something ;) )

    pay for movie $29.95

    download movie $0

    what's your definition of profit?

  74. Re:Infection. by Anonymous Coward · · Score: 0

    You're confusing two arguments here:

    1) code, music, movies are "just information" and information wants to be free

    and

    2) copying is not theft

    Regardless of the merits of either argument, I don't think anyone has argued that copyright infringement is "not an offense," but that it's a different offense than theft (which is true).

  75. The GPL is NOT a Contract by JSBiff · · Score: 1

    Even the FSF will tell you, the GPL is not a contract. It covers distribution of a specific copyrighted work, and does not cover independent works which the same party may happen to also distribute.

    1. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      Uh, no. A lot of people appear very confused about this.

      A contract is any agreement between two people that has consideration on both sides.

      The GPL allows one party to do one thing (make copies, which would otherwise be illegal) in return for the other party getting what they want (Forcing the first party to give out the source.)

      Ergo, the GPL is a form of license agreement that has consideration on both sides.

      Q.E.D., it is a contract.

      Now, there are forms of license agreements that don't have consideration on both sides. Some forms of the BSD license do not. Those are not contracts.

      But anything that says 'If I let you X, you also have to do Y' is a contract.

      A few people, include the FSF at times, have claimed the GPL not a contract because it doesn't get the author any reward...it's more 'pay it forward'. This is utter nonsense, legally. The courts don't care to whose benefit the contract is...I can write a contract saying 'If you donate $1000 to the Red Cross, I will paint your house.'. Or even 'I will paint some random person's house'. Contracts require 'consideration' on both sides, not 'actual gain'.

      If you allow someone to do something, in return for forcing them to do something else, whatever you force them to do is the 'consideration' on your part, no matter whom it seems to benefit.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    2. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      The GPL allows one party to do one thing (make copies, which would otherwise be illegal) in return for the other party getting what they want (Forcing the first party to give out the source.)
      Ergo, the GPL is a form of license agreement that has consideration on both sides.
      Q.E.D., it is a contract.

      Completely wrong. If you link your code with GPL'd code, it is a derived work and you do not own the copyright on it, ergo you don't get to choose how you can distribute it.

      The GPL says that if you distribute this derived work, you must distribute the entire thing including source code. It carves out an exception if you want to distribute the source separately (through download, or an included offer to provide it) but otherwise you don't have to "agree" to a damn thing.

      It's a license, not a contract.

    3. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      Completely wrong. If you link your code with GPL'd code, it is a derived work and you do not own the copyright on it, ergo you don't get to choose how you can distribute it.

      What the fuck are you yammering about? When did I say you could link your code with GPL code and then choose how to distribute it?

      You can only distribute a derivative work you made under permission from the original copyright holder. (And yourself, obviously.)

      The GPL says that if you distribute this derived work, you must distribute the entire thing including source code. It carves out an exception if you want to distribute the source separately (through download, or an included offer to provide it) but otherwise you don't have to "agree" to a damn thing.

      Read what you just wrote:

      The GPL says that if you distribute this derived work, you must distribute the entire thing including source code.

      In other words, you have to 'agree' to distribute the entire thing including source code. You are agreeing to distribute the code for your derivative work (And grant others the same rights) in return for the ability to distribute your compiled derivative work.

      That's what a contract is. One party agrees to X if and only if the other party agrees to Y.

      It's a license, not a contract.

      Saying 'It's a license, not a contract' is like saying 'It's a payment, not a contract'. Dude, lots of contracts have payments in them, and lots of contracts have licenses in them. Yes, you can have payments and licenses exist outside of contracts, also, but that doesn't make them opposites.

      A contract is an agree-upon mutual exchange, an license is granting someone the right to do something they otherwise would not have the right to do. Like produce copies of someone else's copyrighted work. (In this context, we're talking about non-government licenses, but driver's licenses and stuff like that fall into the same general concept.)

      Such a license is, obviously, is often granted as part of an aforementioned mutual exchange, aka, as part of a contract.

      In fact, most copyright licenses are inside contracts. For example, almost all music is licensed to a recording company by the artist, giving that record company permission to copy the artist-copyrighted music, via a contract that gives the artist a percentage of the profits on each CD sold.

      Seriously, I can see the argument that the GPL isn't a contract, on the grounds the original copyright holder gets nothing out of it, so the original copyright holder has no consideration. The FSF has argued this before. As I pointed out in my post, that's a misunderstanding of the fact contracts require 'consideration'...contracts that require you to do something for a third-party that has nothing to do with the contract are entirely valid. Or they can even require you to do random crap that benefits no one, like dance a jig every day at noon for ten minutes. As long as the contract requires each party to do something the other party wants, there is 'consideration', no matter how inane or pointless it is. Requiring people to distribute the source is, indeed, 'consideration'.

      But I can understand that misinformed argument.

      What I can't understand is the braindead idea that contracts and licenses cannot overlap. That's not even slightly correct. Almost all licenses are inside contracts in the real world!

      --
      If corporations are people, aren't stockholders guilty of slavery?
    4. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      What the fuck are you yammering about? When did I say you could link your code with GPL code and then choose how to distribute it?

      When you suggested that the GPL makes you agree to do something.

      In other words, you have to 'agree' to distribute the entire thing including source code. You are agreeing to distribute the code for your derivative work (And grant others the same rights) in return for the ability to distribute your compiled derivative work.

      No. WRONG. You MAY distribute the derived work under certain conditions, you don't have to AGREE to anything and the GPL does not FORCE you to do anything. What part of "you may" (i.e. you are licensed) don't you get?

      That's what a contract is. One party agrees to X if and only if the other party agrees to Y.

      If the GPL said you had to commit to distributing something, you'd be right. But it doesn't.

      A contract is an agree-upon mutual exchange, an license is granting someone the right to do something they otherwise would not have the right to do.

      True. You don't have to exchange anything with the copyright holder of a GPL'd work. The reason you MAY do so is because the rights to the derived work BELONG to the original copyright holder. Are you so dense that you don't get that?

      It's like you agree to add a den to my house, and you're saying I have to let you use the den. No, I don't - it's still my house, and I MAY grant you the right to use the den UNDER CERTAIN CONDITIONS for which you do not need to offer anything in return. You break the rules, you don't get to use the den.

    5. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      When you suggested that the GPL makes you agree to do something.

      How the hell can you be 'made' to agree to something? Are you even talking English?

      No. WRONG. You MAY distribute the derived work under certain conditions, you don't have to AGREE to anything and the GPL does not FORCE you to do anything. What part of "you may" (i.e. you are licensed) don't you get?

      You don't have to agree to contracts. That's why they're contracts instead of, I dunno, slavery.

      If the GPL said you had to commit to distributing something, you'd be right. But it doesn't.

      The GPL does say you have to commit to distribute something...if you do certain things. If you give out copies, you have to commit to the distribute copies of the source code to specific people during a certain time period. Committing to distribute something is, in fact, exactly what the GPL requires. (Of course, you can pre-emptively distribute the source when you distribute the software, and then you don't have to worry about it later. But it's still a requirement, it's just one you've already met.)

      True. You don't have to exchange anything with the copyright holder of a GPL'd work. The reason you MAY do so is because the rights to the derived work BELONG to the original copyright holder. Are you so dense that you don't get that?

      I don't understand what you think I said, but basically you seem to be under the impression that I said people have to agree to the GPL. I have no idea why you think I said that, or how the fuck that would even work. Gunpoint, perhaps?

      The GPL is a contract people can choose to agree to, or not. JUST LIKE ALL CONTRACTS. That's what contracts are. There's no such thing as non-optional contracts.

      If people choose to agree to it, it gives them a license to distribute a copyright work (and thus derivatives of that work), in exchange for requiring certain other things of them, like handing out source code to certain people. (Namely, those you distributed binaries to.)

      I don't know I can make that simpler, and I have no idea what sort of retarded argument you think you're having about the GPL 'required'. At no point have I suggested the GPL was required. The GPL is a contract that people can agree to, or not. (Of course, if they do not agree, and have no other license to distribute the work, they're in copyright violation if they hand out copies.) In fact, that concept is inherent in my statement it's a contract.

      I think you've decided that I think it's an EULA. As I pointed out way back there, EULAs are bogus. They attempt to 'grant rights' that people already have, and hence have no consideration. And I know you don't have to agree to the GPL to use GPL software, if that's the nonsensical problem you've invented in your head. (You don't have to agree to any license to use any software. Using software you legally possess a copy, even making the disk and memory copies required to use it, of is explicitly granted under copyright law.)

      The GPL is a contract, one side of which the original author has already agreed to, and the other side anyone can agree to. No one 'has to' agree to it, but, of course, they usually don't have any permission to make copies outside of that agreement.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    6. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      I think you're having trouble hearing yourself. You're saying "if I do this thing the GPL allows me to do, then I've agreed to do it and therefore it's a contract."

      Sorry, but all the GPL says about distributing to third parties is that if you do so, you may continue to distribute the work. It says nothing about what you MUST do, only what you MAY do.

      I think you're also confusing two meanings of "agree," one being "consent" and the other being "pledge/commit to an action."

    7. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      You're saying "if I do this thing the GPL allows me to do, then I've agreed to do it and therefore it's a contract."

      Uh, no, I haven't said anything like that at all. I am getting very angry that people are just MAKING UP things I say. I ask everyone to notice the lack of quotes of me.

      I said, you fucking imbecile, that the GPL is a contract. Just like any contract, you can agree to it, or not. Hey, look, I literally said that, 'The GPL is a contract people can choose to agree to, or not.'

      If you do not agree with it, though, you've got no license to distribute the work at all, so you'll look pretty silly when they take you to court for copyright violation.

      Sorry, but all the GPL says about distributing to third parties is that if you do so, you may continue to distribute the work. It says nothing about what you MUST do, only what you MAY do.

      What, did you forget to learn how to think in school? (Have you gotten to school yet?)

      Saying 'You can do X, but only if you do Y', is exactly the same thing as saying 'to do X, you must do Y'.

      The sentence '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....' is exactly the same as 'If you convey a covered work in object code form under the terms of sections 4 and 5, you must also convey the machine-readable Corresponding Source...'

      I think you're also confusing two meanings of "agree," one being "consent" and the other being "pledge/commit to an action."

      Uh, no, I didn't. The parent did that, by taking me saying 'people had to agree to the GPL' and pretending I meant 'people were required to sign the contract'. (Actually, that's a slightly different grammatical confusion based on 'had to'.)

      When of course I meant that 'contracts were things that people had to agree to or they were not bound by them'. To be a 'contract' requires agreement on both sides, and by 'requires agreement' I mean 'or the contract does not really exist', not 'everyone is forced to agree'.

      I will now repeat the actual positrons I actually have, not the goddamn made up one that people keep inventing. If you have an actual problem with these positions, you are invited to quote these positions, and we can have a discussion.

      If you do not quote part of my post after this paragraph in your reply, or have a problem with some other imaginary position, I will assume you are a troll and not respond. I will refrain from using 'agree':

      The GPL is a contract. This contract includes in it a license to distribute the software.

      Being a contract, you cannot be bound by it without deciding you are bound by it. You are not bound by it by using GPL software, and you are not bound by it by distributing GPL software.

      However, as the GPL is pretty much the only way to license the right to distribute the software, if you aren't bound by it when distributing the software, you're pretty much unarguably in violation of the copyright. (Which is why GPL violators tend to say they have decided to be bound by it, but lie and say what they are doing is compliant.)

      That is my position, that is all I have said in any of the posts above.

      It is entirely reasonable to argue with my positions. In fact, the FSF argues with my 'contract' statement, and I've been fucking prepared to argue that this entire time. They're wrong. The fact that licenses agreements have special treatment under the law does not mean they cannot be contracts, and in fact most are.

      But that is a reasonable argument. What is not reasonable, and I will no longer stand, is arguing with imaginary positions I supposedly hold.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    8. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      I said, you fucking imbecile, that the GPL is a contract. Just like any contract, you can agree to it, or not. Hey, look, I literally said that, 'The GPL is a contract people can choose to agree to, or not.'

      If you do not agree with it, though, you've got no license to distribute the work at all, so you'll look pretty silly when they take you to court for copyright violation.

      You're the imbecile if you think you have to AGREE to the license to do what it LETS you do.

      Moron. It's not a fucking contract, get over it.

    9. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      'Hey, you don't live here.'
      'Sure I do, the bank wrote up a contract that said I owned this house.'
      'Uh, yeah, but you didn't sign it.'
      'Well, no, I didn't agree to it, I didn't want to pay them all that money. But they still wrote I owned this house, so I do.'

      --
      If corporations are people, aren't stockholders guilty of slavery?
    10. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      Saying 'You can do X, but only if you do Y', is exactly the same thing as saying 'to do X, you must do Y'.

      No, here's why you're wrong.

      Saying "You can do X or (X and Y) but not Y alone" is not obligating you to do anything. It's granting permission to exert some rights but not others.

      Considering that X (distributing the source) and Y (distributing the binaries) are both things that you are not allowed to do under copyright law anyway without a license, it is completely up to the licensor to say whether you're allowed to do it and under what conditions.

      Being a contract, you cannot be bound by it without deciding you are bound by it.

      If it were a contract, you would offer something in return (the "bargain") - i.e. you would pledge to distribute something. You don't have any such obligation under GPL. You don't have to notify the author that you are distributing their software, or sign any agreement with the author.

      You are not bound by it by using GPL software, and you are not bound by it by distributing GPL software.

      Depends on what you mean by "bound," but if you mean you are in compliance with the terms of the license, then yes, you are "bound" to those terms when you distribute. Otherwise, you have no distribution rights.

      If it were a contract, you would have to sign and get approval from the author before you could even download a copy of the software.

      A EULA is more like a contract, in that you have to agree to the terms before you get the license. With GPL, you get the license automatically upon using or copying the software. That is why GPL is just a license and not a "contract that includes a license."

      A lot of hay has been made over GPL 2.0 section 3.b. which says you can distribute the binary if you "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..."

      Again, this is something you MAY do, but are not obligated to do. You have the option to just distribute source and binaries together. If there's any contractual agreement to be found here, it's between you and the aforementioned third parties, not between you and the author.

    11. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      If it were a contract, you would offer something in return (the "bargain") - i.e. you would pledge to distribute something. You don't have any such obligation under GPL.

      I don't understand why you have said this. You _do_ have an obligation. If you distribute the binaries, you must distribute the source.

      However, more to the point, there's another obligation you have: You must grant the people the rights to your modifications you distributed to the same license as the original.

      You can use some sort of weird logical jujitsu to argue that copyright holders can license, without a contract, only certain configurations of distribution, and you're right in theory. Although I will still argue that requiring future commitments would make it 'a contract'.

      But regardless of that, a unilateral license can't possibly require that you license your changes under their licenses.

      A license without a contract could only control what you did with their work, period. It could stop from from editing their work and distribute it without changes (This often happens, in fact. The text of the GPL is subject to this, in fact.), so it could stop you from adding stuff that is copyrighted by you. Or it could allow you to make changes. But something that is just 'a license' can't go around requiring to you make said modifications that are copyrighted by you available under a specific license. (How would a license magically cover the modifications that aren't yet licensed under it?)

      But the GPL is a contract. So you gained the license to make modifications to the original work, and distribute the modified version, in exchange for the requirement that you license those modifications in a specific way. That's a contract.

      Also, you have to show them a copy of the GPL. Again, that's not something a 'license' can make you do.

      And it gets even sillier than that with the GPL3. Under that, you also 'waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.'

      Yeah...once something tells you that you're disclaiming intentions to forbid third parties to do things...it's a contract.

      If there's any contractual agreement to be found here, it's between you and the aforementioned third parties, not between you and the author.

      Like I said, 'consideration' does not even vaguely have to benefit you for the contract to be valid. It is entirely possible to write a contract saying you will donate $1000 to the Red Cross if I donate $1000 to them.

      Likewise, it's entirely possible to write one that says I will donate $1000 to them if you mow my lawn. Or I will donate $1000 to them if you let me make copies of your software. Or I will let others have my modifications of your software if you let me make copies of your software.

      If it were a contract, you would have to sign and get approval from the author before you could even download a copy of the software.

      No you don't. It's entirely possible for an entity to agree to contracts that anyone else can walk up and agree to the other half of. (I'm a little confused as to how you think a EULA is a contract if you don't think this.)

      A EULA is more like a contract, in that you have to agree to the terms before you get the license.

      Uh, no. EULAs aren't even valid most of the time, as they give the end user no rights the end user does not already have. EULAs are contracts that give 'pretend licenses' to do things that people can already do because they own a copy of the program.

      With GPL, you get the license automatically upon using or copying the software.

      Firstly, you don't 'get' anything by using the

      --
      If corporations are people, aren't stockholders guilty of slavery?
    12. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      If it were a contract, you would offer something in return (the "bargain") - i.e. you would pledge to distribute something. You don't have any such obligation under GPL.

      I don't understand why you have said this. You _do_ have an obligation. If you distribute the binaries, you must distribute the source.

      I don't know where you get the idea that you have the option of distributing binaries without source. GPL doesn't allow it, so if you do it, you're infringing copyright. If you distribute binaries alone, you're breaking the law. The only obligation you have is to stop distributing illegally. GPL offers you a way out by getting in compliance, providing the source or an offer to provide the source. GPL doesn't require you to distribute anything at all.

      However, more to the point, there's another obligation you have: You must grant the people the rights to your modifications you distributed to the same license as the original.

      Wrong, because the modified code is a derivative work, and by default, copyright law restricts the rights. Furthermore, you don't have to distribute your modified version if you don't want to. What you can't do is distribute just the binaries, because GPL requires derivative works to also be under GPL. So again, you have an option to distribute legally or not at all.

      You can use some sort of weird logical jujitsu to argue that copyright holders can license, without a contract, only certain configurations of distribution, and you're right in theory. Although I will still argue that requiring future commitments would make it 'a contract'.

      There are no required future commitments in GPL. It grants exceptions for people who choose to make such commitments. As for restricting the work to certain configurations, a copyright holder can license the distribution, in whole or in part, of the original work plus derivative works, and that's what GPL does.

      Read GPL 2.0 section 5: "You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License."

      But regardless of that, a unilateral license can't possibly require that you license your changes under their licenses.

      Read section 2: "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works"

      If the code is yours, you can license it however you want. You can distribute it separately. If it's part of a derivative work, then you have to comply with the licensing of the parent work in order to distribute it. You get that? It's copyright law, not GPL, that restricts your rights to distribute the derivative work.

      But the GPL is a contract. So you gained the license to make modifications to the original work, and distribute the modified version, in exchange for the requirement that you license those modifications in a specific way. That's a contract.

      Wrong. You have no right to distribute the modified version by default. You can distribute your own code on your own terms, or the combined code on the terms of the original author. That's just copyright law. You don't have to exchange rights over anything.

      Also, you have to show them a copy of the GPL. Again, that's not something a 'license' can make you do.

      Exactly. They can't make you do it... but then you have no right to distribute the work. It's a condition of gaining distribution rights.

    13. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      You _do_ have an obligation. If you distribute the binaries, you must distribute the source.

      "If you (do illegal thing GPL doesn't allow) then you must (do legal thing GPL allows)." Doesn't make sense, does it? You can just stop doing the illegal thing.

      Your whole argument amounts to "GPL won't let me make others' work proprietary. It makes me agree to keep it open in order to distribute it, therefore it's a contract."

      Complete nonsense.

    14. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      Yes, you must agree to the license before you can distribute.

      Uh, no. You cannot 'agree' to just a license. This, I think, the entire point of confusion.

      The only way to 'agree' to something is if it is a contract.

      A license is a grant. It says 'You can do Y.". In the GPL's case, (under your theory that it's not a contract), it is a very complicated license, something like "You can punch me in the face while hopping on one leg and doing a bunch of other complicated stuff.". A license can, indeed, say that, I will not dispute that.

      But if it is just 'a license', then there is no reciprocal thing you must do, so there is nothing you can agree to. You don't 'agree' you will hop on one leg. You just have a grant to do punch me in the face while you hop on one leg. If you do it any other time, well, you didn't have any right to do that and I'll charge you with a crime.

      If, for a saner example, I put up a sign saying 'People can eat a picnic in my gated backyard from 11-4 while wearing a hat', no one has a contract with me, nor have they 'agreed' to anything. They just have been given a license to do something that would otherwise be trespassing, with some restrictions.

      A license is just a note saying 'You can do X.'. It can say 'subject to this other stuff', but it's not something you agree with or disagree with by itself...it's just a statement of permission of certain activities. (Which is why it is usually contained in a contract.)

      The problem is, with the GPL, there are things you have to agree to. Like providing the source later.

      There are no required future commitments in GPL. It grants exceptions for people who choose to make such commitments. As for restricting the work to certain configurations, a copyright holder can license the distribution, in whole or in part, of the original work plus derivative works, and that's what GPL does.

      I'm going to ask you a question, and I want you to think about it hard:

      If I distribute binaries with a note that I will distribute the source on request, and then I don't....what exactly have I done?

      Remember, there's no such thing as breaching 'a license', because there's no such thing as agreeing with one in the first place. You can violate copyright law by exceeding a license, or you can breach a contract.

      As you say there's no contract, you must assert I violated copyright law.

      But...um...how? You gave me permission to distribute the stuff. I even included the note I was supposed to. The copies I handed out appear to be exactly what you specified.

      ...then yes, I stopped following your rules, but I only needed to do that while I needed the licenses, aka, doing the act of making the copy.

      Now, if I'd agreed to a contract that had granted me a license to make copies, it would be an entirely different matter. I'd have to abide by that even after I was done making copies.

      However, luckily, it was apparently just a license that made me jump through weird hoops and make strange promises while producing copies. Luckily, once I stop making copies, I can stop doing whatever it said I had to do while making copies.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    15. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      Yes, you must agree to the license before you can distribute.

      Uh, no. You cannot 'agree' to just a license. This, I think, the entire point of confusion.

      The only way to 'agree' to something is if it is a contract.

      *sigh* fine. This is getting tiresome.

      Substitute "accept" for "agree to," which is what the license itself says anyway.

      If I distribute binaries with a note that I will distribute the source on request, and then I don't....what exactly have I done? Remember, there's no such thing as breaching 'a license', because there's no such thing as agreeing with one in the first place. You can violate copyright law by exceeding a license, or you can breach a contract. As you say there's no contract, you must assert I violated copyright law

      You get an exception to the requirement to provide source with binaries only if you offer to provide the source separately. If you don't provide the source, you are exerting a right that the GPL does not grant you, so your right to distribute is revoked. Then you are violating copyright by distributing the partial work.

      You get that? If you don't abide by the terms of the license, you have no distribution rights. Ergo your binary-only distribution is illegal.

    16. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      A license is just a note saying 'You can do X.'. It can say 'subject to this other stuff', but it's not something you agree with or disagree with by itself...it's just a statement of permission of certain activities. (Which is why it is usually contained in a contract.)

      ...if it is just 'a license', then there is no reciprocal thing you must do, so there is nothing you can agree to.

      The problem is, with the GPL, there are things you have to agree to. Like providing the source later.

      Jesus, you can't understand fucking English, can you?

      You DON'T HAVE TO agree to provide source later. You can distribute the binary with the source or with an offer to provide source later - but THIS IS AN OPTION, you ARE NOT REQUIRED TO DISTRIBUTE ANYTHING. You MAY distribute binaries with the offer to provide source later.

      Fuck, how many times do you have to be told that the license LETS you distribute in some ways and PROHIBITS others?

      What I find hilarious is that you're presuming to "educate" us on how the thing works and you yourself have no fucking clue! Good luck suing a GPL author for "breach of contract," dipshit!

    17. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      Substitute "accept" for "agree to," which is what the license itself says anyway.

      The really tiresome part is that you apparently think you can 'accept' a license.

      You cannot accept, or reject, or agree to, or whatever the hell words you want to say, a license. A license is just a statement that you can do something.

      It matters whether or not you say 'Okay' or 'No!'. You still have a license to do that thing.

      Here, watch, a license: I give people permission to quote this comment in replies to this comment.

      Now the entire world, like it or not, has permission to quote this in replies to me. (Not that they needed it.) They cannot accept or reject this, it just is.

      OTOH, I should probably mention this again, random licenses can be revoked for any reason at all. (In a contract, of course, trying to do so would be breech of contract.) That is an interesting position for someone to take about the GPL.

      If you don't abide by the terms of the license, you have no distribution rights. Ergo your binary-only distribution is illegal.

      What, it's retroactively illegal? That's a neat trick.

      You did not address my actual situation, which is doing what the license said while you needed a license, aka, providing a note promising the source while you were making copies.

      Which would then be followed up by a failure to meet that obligation, which cannot possibly be a violation of copyright. (Because you are not currently making any damn copies.)

      Licenses do not bound people to things. Licenses are not accepted or agreed to or anything like that. A license is a statement saying 'This specific thing is allowed'.

      Anything where people are 'accepting' that they have to do future stuff...that's a contract.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    18. Re:The GPL is NOT a Contract by DavidTC · · Score: 1

      I like the fact you think all contracts have to 'require' people to do things.

      You do know that plenty of contract, including most contracts with license agreements, require fuck-all from the party getting the license? They're along the lines of 'You can put this song of mine in the movie you're making(Which is the license part), and if you do, you have to pay me X (Which makes it a contract)'.

      If one party doesn't put the song in, they just don't pay the money. A lot of licensing contracts work that way.

      You can distribute the binary with the source or with an offer to provide source later - but THIS IS AN OPTION, you ARE NOT REQUIRED TO DISTRIBUTE ANYTHING.

      So let's see if I've gotten this right. A license, which apparently you have to 'agree' to (This is not correct, but let's pretend), says that I can make copies, which would otherwise be a violation of copyright law. I can make these copies if I also copy the source, or provide a note saying I will give them a copy of the source later.

      I choose the latter.

      Later, someone comes along wanting a copy of the source. I, because I have no contractual obligation at all, decide at this point I'm going to 'stop' agreeing to the license.

      After all, I only needed the license to make copies. Standing around not making copies isn't a violation of copyright law, even if people have notes promising I will do that.

      So at that point, what exactly am I doing illegal? I can't break copyright by not making copies. The other post tried to suggest my original copying was retroactively illegal, which is quite literally insane and utterly unsupported by law. You cannot retroactively lose permission to do things you did.

      Now, if I had some sort of contract I had agreed to which had given me the license to make copies in exchange for me doing things in the future, that would be another thing entirely. I'd be in breech of contract. But apparently I just had a license, which cannot create any obligations on me at all...if I make copies in the form it describes, I'm fine, no matter what the hell it tries to imply I have to do later.

      Seriously, you can't stand around asserting that something that can create future obligations isn't a 'contract', you utter nimrod. It doesn't matter if that's just an 'option' or not. It's an option whether or not filmmakers pay for a song in their movie, too. They can either choose to include it, or not. If they choose to include it, they have to pay for it in the future. If someone chooses to distribute binaries with a note, they have to provide the source in the future.

      A license can say 'You can do X with certain constrains on X', aka, it can say 'You can copy this copyrighted work only if you keep the entire work intact and do not modify it.'. Licenses do not have to allow you to do anything you want.

      But If it is of the form 'If you do X, then you have to do Y', it's a fucking contract. The GPL says 'If you provide the binary and note to provide the source later, then you have to provide the source later'. Hey, look, a contractual obligation.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    19. Re:The GPL is NOT a Contract by Anonymous Coward · · Score: 0

      But If it is of the form 'If you do X, then you have to do Y', it's a fucking contract.

      For the last time, GPL DOES NOT SAY THAT.

      It's written in the form "You can do X or (X and Y) but not Y alone."

      "Ah, but what if I do Y with a promise to do X later?"

      "Okay, you have permission to do that."

      "Ha! Fooled you! I did Y without doing X."

      "You don't have permission to do that. Your rights under this license are revoked."

      Doing Y in no way obligates you to do X. Doing Y alone is not permitted, so even if you promise to do X, you're not obligated to do anything. You aren't even obligated to promise to do X. Your only obligation is STOP DOING Y. If you can't see that, you're beyond hope.

  76. Re:Infection. by Arker · · Score: 1

    I can say whatever I want to say. Just try and stop me :P

    When copyright laws were invented, printing presses were very expensive things that few owned. Copyright laws were therefore de facto restrictions on businesses that had little to no affect on private individuals as a result. Over time as technology has progressed, the technology has improved, and the price of the equipment needed to effectively violate a copyright has decreased dramatically, so that copyright laws now affect a great many people that would never have had to worry about them when they were invented. It is not illogical to make a distinction between application of copyright law to businesses who are violating copyright for a profit, and individual 'infringers' whose activity is of a noticeably different nature.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  77. Re:Infection. by Registered+Coward+v2 · · Score: 1

    I'm one of the people who says that. And I agree with you. This isn't theft. It's a copyright violation.

    Just because I think calling copyright violation 'theft' is highly misleading doesn't mean that I don't think copyright should exist. And this case, someone repackaging someone else's work in order to make a profit, is a case I think is clearly wrong.

    I think we in agreement on this; without copyright the GPL would be useless. I just find the arguments that some, not necessarily you but others on /.,make to rationalize copyright violations when pirating movies, music, or software while vociferously attacking anyone who commits, or is believed to have committed, a GPL violation. I find that hypocritical, despite the long winded rationals some make. You can't have the GPL and worship at the alter of "I should be free tio use copyrighted material in any way I want even if the owner of the copyright doesn't give me permission to do so."

    In this case, the software may not even violate the GPL (once the GPL's code is made available); because, as I understand it, it is permissible to wrap non-GPL code around GPL'd code if you don't actually incorporate the GPL'd code. You could, for example, create software that puts a GUI on it and even add features provided you pass the information to separate GPL'd code rather than adding it to yours. Some may disagree with that interpretation but that's as much a philosophical argument rather than a licensing one.

    Interestingly, the GPL places no restrictions on reusing and charging; as long as you comply with the requirements to make the source available, you can charge what you want.

    --
    I'm a consultant - I convert gibberish into cash-flow.
  78. A VERY bold name for a company. by vovick · · Score: 2

    In Russian "hamster" is an internet slang word for a "mindless, unwary and predictable consumer of popular novelty items", a "lemming". Definitely not the kind of name people would trust (as long they know what it means)!

  79. Re:Infection. by Omnifarious · · Score: 1

    Interestingly, the GPL places no restrictions on reusing and charging; as long as you comply with the requirements to make the source available, you can charge what you want.

    I wish more software under the GPL had a pay-for-download option. Especially software in the Android marketplace. I would like to help the authors continue to make improvements and more good software. But almost invariably software that actually complies with the Open Source definition (and especially GPL software) is only available for free.

  80. Re:Infection. by Registered+Coward+v2 · · Score: 1

    Interestingly, the GPL places no restrictions on reusing and charging; as long as you comply with the requirements to make the source available, you can charge what you want.

    I wish more software under the GPL had a pay-for-download option. Especially software in the Android marketplace. I would like to help the authors continue to make improvements and more good software. But almost invariably software that actually complies with the Open Source definition (and especially GPL software) is only available for free.

    I agree. The issue is anyone can take the code and charge a bit less, making your model difficult to implement. I think Apple's walled garden actually offers the best way to do what you describe. An org such as EFF could act as the custodian and put apps on the app store. They would collect the fees and reimburse the developers. Apple would not host other instances of the same code. Granted, this works best for code from one or two developers but it could be a start to making OSS software better.

    --
    I'm a consultant - I convert gibberish into cash-flow.