Slashdot Mirror


Beware of "Backspaceware"

SubLevel writes "Since conception in 2004, Paint.NET has been generously been offering the software community the taste of successful freeware, by allowing anyone to download and decipher the entire working of their extremely popular photo editing program. As posted in the Official Paint.NET blog by Rick Brewster, "Backspaceware" as he has so coined has become a tremendous issue. "Paint.NET's license is very generous, and I even release the source code. All free of charge. Unfortunately it gets taken advantage of every once in awhile by scum who are trying to profit from the work of others. I like to call this backspaceware*. They download the source code for something, load it up in to Visual Studio (or whatever), hit the backspace key over the software's name and credits, type in a new name and author, and re-release it. They send it to all the download mirror sites, and don't always do a good job covering up their tracks.""

60 of 257 comments (clear)

  1. Proofreading by kmac06 · · Score: 4, Funny

    I been have been good at proofreading.

  2. Let me introduce you by 0xdeadbeef · · Score: 5, Insightful

    to the solution to your problems.

    1. Re:Let me introduce you by pkadd · · Score: 4, Interesting

      Regardless of the lisence, people still breach it by making backspacewar eof it. I've seen it happend to alot of my work, which is why i avoid making it opensource unless people ask for it, or when it's a project i don't really care about. I don't make much commercial software, although i like to keep my name on my work to receive credit where credit is due.

    2. Re:Let me introduce you by JesterXXV · · Score: 5, Insightful

      If you RTFA, you'll see that this guy violated Paint.NET's current license, so putting a different license in there would solve absolutely nothing.

      --
      Yo mama so fake, she failed the Turing Test.
    3. Re:Let me introduce you by ucblockhead · · Score: 2, Informative

      If he were to GPL it, he could assign the rights to the FSF, which has things like lawyers and such whose job it is to go sue people for violating licenses.

      --
      The cake is a pie
    4. Re:Let me introduce you by TopherC · · Score: 5, Interesting

      If you RTFA, you'll see that this guy violated Paint.NET's current license, so putting a different license in there would solve absolutely nothing.

      But the GPL has been "tested" in court, while Paint.NET's current license has, I assume, not been yet. Also there are organizations that will help you in court if it's a GPL violation. So in part it's a matter of practicality, not principle.

      Also Paint.NET should consider exactly how they want legitimately derived works to happen. If the GPL prevents certain kinds of derived works that they might like to see others create, then it's not the right license on principle.

      Hmm, currently they're using the MIT license, which is extremely permissive. I don't even see a prohibition against re-branding and re-crediting in the license. So it's not obvious to me that the current license is being violated. Perhaps it is and I'm just not seeing it because IANAL. Anyway, consider that the current license provides next to nothing in terms of protection, and that's what the authors chose. The GPL provides substantial protection against abuses, and if paint.net wants to whine, they should "sublicense" (which is explicitly permissible under the MIT license) first to demonstrate that they really don't want this stuff to happen. The MIT license looks to me like a big "kick me" sign.

    5. Re:Let me introduce you by 0xdeadbeef · · Score: 2, Insightful

      Except the GPL has a posse, and GPL violations generate far more publicity than just some guy getting ripped off. Corporations are scared of it for a reason.

      Copyright clauses are hardly a license. If he cares so much about plagiarism that he's now crippling the source, maybe community ownership is preferable to controlling a string with his name in it.

    6. Re:Let me introduce you by Albanach · · Score: 2, Interesting

      Umm.. no. The GPL has not been tested in court. At least, not in the way you are implying
      I'm sure some courts would disagree, as would those who have won compensation in court for GPL violations.
    7. Re:Let me introduce you by Anonymous Coward · · Score: 4, Funny

      What, so stallman can take the credit and get the benefits? In Stallmanland, Backspace brings up online help because that's the most intuitive thing it can do - everyone knows C-h should bring up help. Your keyboard is broken and you should throw it way and get a different one. The software in the article should have been called Deleteware or better still delete-backward-charware to avoid any ambiguity. Get your terms straight next time.
    8. Re:Let me introduce you by AJWM · · Score: 2, Informative

      The reason for that is that the GPL is a license which lets you make copies.

      If somebody infringes it, the copyright holder sues the copier, and the copier's only defense is the license granted by the GPL, otherwise he has no license to copy and is in violation of copyright laws. The GPL hasn't been "tested in court" because if the case goes to court, it is in the defendant's interest to show that the GPL is valid and that he's been following it. (The only other option would be to somehow try to prove that the GPL is equivalent to putting something in the public domain, and that argument just won't fly.)

      Usually it doesn't take long for the plaintiff's lawyers to point this out to the defendant's lawyers, and the defentdant's lawyers to point this out to the defendant, and for them all to quickly come to some settlement.

      And actually, the GPL has been tested in court in Germany, and found to be perfectly valid.

      --
      -- Alastair
    9. Re:Let me introduce you by moosesocks · · Score: 2, Insightful

      But the GPL has been "tested" in court, while Paint.NET's current license has, I assume, not been yet. Also there are organizations that will help you in court if it's a GPL violation. So in part it's a matter of practicality, not principle.


      That, my friend, is FUD. Even though it's a tactic generally condemned by the Free Software, RMS and his FSF cronies occasionally drag it out to promote their cause.

      Free and Open-Source software is fantastic, although too-liberal licenses can often leave developers with a somewhat bad taste in their mouths for reasons such as this. The Paint.Net source code was released expressly for academic purposes, and it's a shame to see the license being abused in such a manner.

      I'd love if some sort of creative commons license for source code could be developed so that developers could easily choose how they would like their software to be used/modified/redistributed. Although a completely free license is "perfect", developers have more than a few reasons not to go the whole way....
      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
  3. It's copyright infringement by tepples · · Score: 4, Insightful

    The majority of copyright licenses used for popular free software applications require people who redistribute the software to preserve the original author's copyright notice. Failure to do so is plagiarism, and the license treats plagiarism as copyright infringement.

    1. Re:It's copyright infringement by webmaster404 · · Score: 2, Insightful

      Yes, thats wrong, but does it hurt you that much? Not hardly at all. Sure its not nice but the real question is, did you lose any money or users that would contribute and such. I highly doubt that. This probobly happens to almost all F/OSS software at one point in time, but the people who do that don't have the coding talent to keep up with releases. I am not saying that it is not bad, but for a title of "beware of backspaceware" is kind of overstating that.

      --
      There is no "disagree" moderation, and troll, flamebait and overrated are not valid substitutes
    2. Re:It's copyright infringement by pipatron · · Score: 4, Insightful

      but the real question is, did you lose any money or users that would contribute and such

      Fortunately, for most people, money is not everything, nor even that important. A big reason for working on free software is simply to get your name out there. To be recognized. This is exactly what the person robs you of, doing this.

      --
      c++; /* this makes c bigger but returns the old value */
    3. Re:It's copyright infringement by rucs_hack · · Score: 5, Insightful

      It certainly didn't hurt Microsoft when they ripped off FreeBSD's TCP/IP networking stack and called it their own, no? /sigh

      Here we go again.

      Microsoft did not rip off the BSC TCP/IP stack. They, and every other OS vendor were *expected* (almost required I think) to use it, AND they left the copyright notices in, as required. The idea was that everyone would be on the same page, as it were. OK Microsoft buggered it a bit with their darn silly extensions, but even these did not stop network connections from other OS's from working properly.

    4. Re:It's copyright infringement by Kjella · · Score: 2, Insightful

      His copyright notices yes, but the "About" box is not a copyright notice. You can replace any about box with "Backspacesoftware Deluxe, (c) Backspacecorporation Inc. This software contains code licensed from third parties, click link below for details". All you need to do is to notify people is to obfuscate yet still technically inform people it's under the GPL and have a source file available and you're home free. Example would be to hide it behind a separate page "License details", and during installation not mention the intent of the license or the name, just that this is a licensing agreement you need to click through like other closed source software.

      Technically there's nothing the GPL can or should do about this, for example because Debian had some trouble with the Firefox trademark requirements, they released iceweasel. Iceweasel is in pretty much every form of definition "backspaceware", even though there's nothing malevolent about it. Nor is "backspaceware" really distinguishable from a fork in its infancy. The good guys of course give credit and say "this is baed on..." but the bad guys don't. But trying to make that a formal requirement would probably lead of pages of everything all your software and libraries once upon a time was based on.

      --
      Live today, because you never know what tomorrow brings
    5. Re:It's copyright infringement by rucs_hack · · Score: 2, Insightful

      Wow, way to have blinkered vision.

      FYI they were under no obligation whatsoever to include the copyright notice. They did though. Also, so what if it was in a DLL? Is that important?

      I do so tire of people claiming it was ripped off though. As I said, they were supposed to take it, that was the whole idea. It was why BSD was asked toi implement it in the first place, to avoid each vendor having their own implementation and buggering up TCP/IP. Microsoft didn't actually have to, and I believe they were using their own stack to begin with, but as soon as possible they switched.

  4. Obfuscated C by Bios_Hakr · · Score: 5, Funny

    This is a good reason to implement obfuscated C for things like the program name and author.

    --
    I'd rather you do it wrong, than for me to have to do it at all.
  5. Closing the source? by Richard+W.M.+Jones · · Score: 4, Insightful

    His "solution" to this seems to be to close the source for parts of the program, which is a major overreaction to this joker.

    I don't think he should be worried - as long as his (the "genuine") program appears higher up in Google for the name and the important search terms, people will ignore the plagiarist.

    Rich.

    1. Re:Closing the source? by Threni · · Score: 2, Insightful

      > His "solution" to this seems to be to close the source for parts of the program, which is a major overreaction to this joker.

      Exactly. It's a free program. Why should anyone care? Is this an ego thing?

    2. Re:Closing the source? by mysticgoat · · Score: 3, Interesting

      OTOH, his behavior is consistent with having first decided to close the source, and then coming up with this as an acceptable excuse to lay out before his user base.

      Perhaps the people at his day job, at Microsoft, have offered to buy his copyright. There would be a need to close the source in a way that would not offend potential purchasers of any Microsoft product that would be marketed as a follow-on to the users of his original work.

      Either the author of TFA is incredibly naive about the software community, or he is attempting to do something clever in the way of marketdroid spin. I doubt very much that he could have gained sufficient experience to write a major piece of software without losing his naivety along the way. OTOH, he works in an environment that values cleverness in exploiting markets and marks above honesty, ethics, or legalities.

      Just saying.

    3. Re:Closing the source? by bcrowell · · Score: 4, Insightful

      Yeah. I think this is an interesting example of how underdeveloped and pathetic the OSS scene on Windows is. It's like going back in a time machine to 1988, when nobody had ever heard of the Gnu Project, nobody had ever heard of copyleft, and "free" software meant a mixture of illegally copied closed-source software and legally downloaded closed-source nagware, tipware, and crippleware. I sympathize with the author of Paint.NET, but he's fighting against a culture where most people have no idea what OSS is, and where all the social mechanisms the Linux/BSD community has developed don't exist. It's as though some British banker showed up in the Trobriand Islands in 1880 and announced that he was going to build a stock exchange. This whole thing would be a nonissue if this was Linux rather than Windows. Paint.NET is apparently a very popular piece of software with an active user community, so if it was Linux software, it would certainly have been packaged for Debian by now. People would be getting the latest version by doing an "apt-get install paint-dot-net." Imagine if someone made a backspaceware version of The Gimp -- obviously it just wouldn't work.

      I used to be interested in the idea of spreading the word about OSS by making cross-platform apps available on both Windows and Linux -- the kind of thing that theopencd.org used to do. I had a a GUI app I'd written for my own use on Linux, and while I was at it, I made sure it ran on Windows. On the one hand, it was surprisingly successful. Judging by the emails I was getting, the vast majority of my users were on Windows. On the other hand, it was a huge amount of work to support those Windows users, and I started to question whether I was really accomplishing anything useful. When you write OSS that runs on Linux, you get that warm fuzzy feeling of belonging to a community and building something big and exciting. When you write OSS that runs on Windows, the users are not a community that has the same philosophical goals and is working toward the same ends; the users are people who typically couldn't care less about OSS (that's why they run Windows) but who simply want something for free. I ended up putting a notice on the web site saying that I would no longer provide support for Windows users; the source is still open, and they're welcome to try running it, but if it doesn't work, I don't have any motivation anymore to put in time helping a community that doesn't care about the things I care about. I don't think I'm alone in having this kind of experience. For instance, theopencd.org's site now says they're no longer actively developing the CD, and just has links to ubuntu, etc.

      What's sad about the Paint.NET story is that the author seems genuinely pained and bewildered by the situation he's in, and since he doesn't seem to care about free information per se, it's like he doesn't have a compass to guide him. He runs up against this issue, and his reaction is, "oh well, I'll take the software closed-source." That's what the whole Windows OSS scene is like -- a bunch of people wandering around without any common vision of what they're trying to accompish. It's like watching the Israelites wandering around in the desert without Moses.

    4. Re:Closing the source? by bcrowell · · Score: 2, Interesting

      Why yes, because linux and bsd code have never been ripped off.
      I didn't say that linux and bsd code had never been ripped off.

      Nor does the author talk about taking the software closed source; if you read the article he talks about distributing part of the project as a binary, the bits that people can easily use to just change the copyright messages, the installer and other small bits. The removal of the current source is a stopgap until he decides which option to take.
      Here I agree that you have more of a point. However, if you cripple the source code distribution so that it's no longer possible to compile the whole thing from source, to me that indicates that the software is no longer open source. Pick any high-profile OSS project such as the Gimp or gcc, and ask yourself what would happen if the leaders annouced that they were taking just a little of the code closed source. Nobody would say, "Oh, that's all right, gcc is still 90% open source." They would say, "That's ridiculous -- I'm switching to llvm," or maybe "That's ridiculous, I'm forking the fully open-source version."

    5. Re:Closing the source? by Anonymous Coward · · Score: 2, Insightful

      Every single time I see this kind of bullshit it's Windows software.

      I think Windows, on top of the occasional technical or other necessity of using it, attracts the sort of people I saw in a Pound Shop today.

      In the Pound Shop everything costs £1 exactly. The people I saw were buying branded orange squash in 1 litre bottles. Here's the problem, in any supermarket, or large grocery store those bottles cost less. In you're buying several bottles (as some customers were) you can get 3 for £1.80 in a store just five minutes walk from the Pound Shop. That's a 40% saving.

      The Pound Shop's brand positioning is that it's a discount store, everything is cheap, volumes are high, staff knowledge is zero, aisles are narrow, it's intended to give the impression that overheads have been cut to the bone in order to reduce prices. The reality is that only a few products are ever discounted to the point where other stores can't match them. Everything else is actually selected on very simple criteria - it should not have a visible price indication and it should have a retail value of close to but less than £1.

      That's what this backspaceware is all about. It's the hunt for people who are so stupid, that if you say "Here's a dollar bill, I usually sell these for $5, but today I'll do a special offer, three for $10" they'd actually buy it.

    6. Re:Closing the source? by sumdumass · · Score: 2, Insightful

      Well, why I just don't like the term Backspaceware, I can see the point of labeling it something. It is a piece of code or a program that someone merely changed the credits for. I mean it isn't as if the code in itself were changed and someone else wanted credit too, it is that they just deleted the credit and placed their names in there for whatever reason.

      I think that should be distinguished from someone who actually improves the code and wanting credit. I don't think it really matters what license it is under, or if it is allowed, there is a certain amount of respect for the type of person doing it that should not be displayed. I think that should be differentiated from someone who actually touched the code in some meaningful even if insignificant ways other then removing copyright credits.

    7. Re:Closing the source? by a_nonamiss · · Score: 2, Interesting

      As a Windows IT professional, I am offended by your comment. I love the open-source community. I support it as much as I can as often as I can. I'm becoming more and more proficient at Linux, too, but there's an element of snobbery in the Linux community that drives intelligent people away. It's unfortunate, too, because I think that those elitists are in the minority.

      --
      -Arthur
      Cave ne ante ullas catapultas ambules
  6. Shady business practices by drspliff · · Score: 4, Interesting

    I've seen this a number of times, shady people who only want to make a quick buck or have entirely unrealistic expectations of what software development costs or how it's done. At the root of this problem are either the shady people trying to make a quick buck, or the shady freelancers trying to meet the requirements on a non-existant budget.

    Lets take the average scenario:
    - Shady person sees a piece of software and thinks they can make some money if they made their own.
    - Shady person has no programming knowledge, so posts on rentacoder or similar.
    - Because they have no idea of what software development entails, or in order to make money it must cost next to nothing.
    - Shady freelancer or outsourcing business wins the bid.
    - Shady freelancer re-brands an existing piece of software in a day and the job's complete.

    Quite a few times this is down to freelancers knowing they can just re-brand an existing open-source project, or even the shady business knowing they can get it cheap if freelancers do that.

    Some times they get lucky and their "product" gets more success than the original project, but it's origins are now hidden and will be forever because you can't just come clean 6-12 months down the line when it's making money.

    I've long called this pump and dump software, companies or individuals trying to build up a large portfolio of software under a common brand covering the widest market possible in the remote hope that they'll profit from some.

  7. Not all GPL violations get handled as smoothly by tepples · · Score: 4, Informative

    to the solution to your problems. Years ago, I dealt with somebody who backspaced my freepuzzlearena package, which was distributed under GNU GPL version 2 or later. Specifically, he did not "includ[e] an appropriate copyright notice" on the title screen. We cleared it up amicably: he agreed to stop distributing the backspaced version. But not all GPL violations get handled as smoothly as this one was.
    1. Re:Not all GPL violations get handled as smoothly by j-pimp · · Score: 3, Informative

      You can sign over your copyright to the EFF (correct me if I'm wrong) and they will defend your code vigorously.

      I know the FSF provides this service. I did not know the EFF did.

      --
      --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
    2. Re:Not all GPL violations get handled as smoothly by garbletext · · Score: 2, Funny

      I like how you backed your premise with anecdotal evidence to the contrary there.

  8. Re:Operation as normal by BlueParrot · · Score: 5, Insightful

    Welcome to capitalism. If one can get away with it, one can make as much money as they want


    That isn't a feature of capitalism, it's a feature of human nature. Yes, it does mean you can't blindly trust a capitalist system from sorting everything out, but it is the very same principles which causes communist countries to go corrupt, and it is also why extreme liberalism will be taken advantage of by those who have the power/influence/money whatever to game the system.

    Corruption isn't a matter of how governance is organised or how you set prices in your economy, it is a matter of transparency, openness and people being held responsible for their actions. If that does not apply it matters fuck all what economic system you use, you will just get different people screwing you over.

    Now before people start suggesting direct democracy or some far-fetched ideal about having every company democratically controlled by the workers, you need to take into consideration that for democracy to work you need a transparent electoral system you can trust. Thus it still boils down to government transparency and people being slapped when they break the rules. There is no way around that.

  9. Statutory damages by tepples · · Score: 3, Interesting

    Yes, thats wrong, but does it hurt you that much? Under United States law, whether it hurts the author does not matter, except in the narrow reckoning of fair use (17 USC 107). Some free software maintainers are smart enough to register major releases of the software with the United States Copyright Office. If such a release gets backspaced, a jury may award the author $750 to $30,000 in statutory damages (17 USC 504(c)) despite that the author cannot prove economic harm.
    1. Re:Statutory damages by kryptkpr · · Score: 4, Insightful

      I've had this happen to projects I lead. Adware/spyware is almost always bundled (it's distribution is the primary motivation for Backspaceware), and this definitely causes harm. Fortunately, sites like download.com have a review process and they found my email address buried in the 'about' dialog, I guess the backspacers missed one...

      --
      DJ kRYPT's Free MP3s!
    2. Re:Statutory damages by zakkie · · Score: 5, Insightful

      Sometimes there is a direct loss when work is plagiarised. Also, Google has odd algorithms for determining how high one should place in their rankings. I release all my data under the GPL and often legitimate copies and absolute ripoffs both rank higher than I do for most search terms I would expect people to find my site with. Monetary loss aside, the fact that someone is trying to pass off another's hard work as their own is simply despicable.

    3. Re:Statutory damages by BorgCopyeditor · · Score: 2, Insightful

      You're the nitwit. The GP mentions the law, but the focus of the comment was on harm, which the GGP keeps insisting is what is relevant instead of the law.

      --
      Shop as usual. And avoid panic buying.
    4. Re:Statutory damages by Xaositecte · · Score: 5, Insightful

      Here's the thing:

      1. Various people in this thread cannot see the harm in distributing software without giving credit for it.

      2. The Author of the software sees this practice as harmful, whether as a material loss, a potential to lose copyright by not defending it, The principle of the thing or any number of other reasons. The only thing that matters is the author believes he has been harmed by this copyright infringement.

      3. These are contradictory viewpoints, and amount to little more than opinion when placed in a vacuum. The rational, logical discussion you think you're looking for is impossible. We are forced to look at how disputes like this have been settled in the past, an appeal to the majority in the form of looking at established laws.

      Therefore, the law IS relevant, and is pretty clear cut in this circumstance. Society judges harm has occured.

      If you want to make an arguement without considering established law, all you're doing is intellectual masturbation. If you want to make an arguement about how the law should be changed, by all means, make it.

    5. Re:Statutory damages by joe+155 · · Score: 2, Insightful

      "If you want to make an arguement without considering established law, all you're doing is intellectual masturbation. If you want to make an arguement about how the law should be changed, by all means, make it."

      Well, I would have to say that I disagree here. If we can discuss what justice requires in a situation without using current law then we end up having a very strong argument for change (assuming that what is and what should be differ). Normative arguments don't have to lack force so long as they are sufficiently consistent.

      --
      *''I can't believe it's not a hyperlink.''
    6. Re:Statutory damages by ehrichweiss · · Score: 2, Informative

      There is no "potential to lose copyright by not defending it" at least in the U.S. You are thinking of "trademark".

      --
      0x09F911029D74E35BD84156C5635688C0
  10. Re:So, whats the big deal? by Anonymous Coward · · Score: 5, Insightful

    As a freeware author, reputation is all you can expect to get in return for your work. It's bad enough that so many ad-laden download sites exist which make users jump through hoops to get the actual file or find a link to the homepage, all the while bombarding them with banners and popups. Never mind that the file is usually available from the well-sorted homepage without a hitch. But now some people even rip you off for the attribution. Quite frankly, be thankful for every piece of freeware that is still out there, because most authors wouldn't take that kind of shit if they got paid for it.

  11. Perception of copyright by michaelmalak · · Score: 3, Insightful

    This is of course no different than what can be done with a hex editor on a binary. Somehow, being able to see the source code gives a lot of people the sense that they can do whatever they want with it. There has always been that mistaken notion that source code is the keys to the kingdom; for example, companies take great pains from letting their source code leak out, especially to their competitors. There are rarely secrets contained in source code (except for Microsoft's NSA backdoors), and if a competitor got it, more power to them wasting their time trying to reverse engineer it.

    But there's something new contributing to this perception, which is the general disdain for copyrights these days. It's the record companies' fault, of course, for withholding sales of digital audio during the entire dot-com boom. Now they're struggling to sell singles for a fourth the price they were selling for 25 years ago, adjusting for inflation.

    People think they have an entitlement to commercial music, and they think catching a glimpse of the source code gives them full rights.

    1. Re:Perception of copyright by doshell · · Score: 3, Insightful

      There has always been that mistaken notion that source code is the keys to the kingdom; for example, companies take great pains from letting their source code leak out, especially to their competitors. There are rarely secrets contained in source code (except for Microsoft's NSA backdoors), and if a competitor got it, more power to them wasting their time trying to reverse engineer it.

      It is orders of magnitude easier to reverse-engineer source code in a high-level language than it is to reverse-engineer machine code or even assembly code (especially when you have software at your disposal that can obfuscate the compiled machine code). That's why leaaking out source code is much more dangerous from the point of view of the proprietary software company.

      --
      Score: i, Imaginary
  12. Re:Operation as normal by Anonymous Coward · · Score: 5, Funny

    WRONG! The MARKET solves ALL problems! Communist!

  13. Source code defined by tepples · · Score: 4, Informative

    This is a good reason to implement obfuscated C for things like the program name and author. But obfuscated code is arguably not "source code" as many common copyleft licenses define it. For example, the source code for a work under the GNU General Public License is "the preferred form of the work for making modifications to it". GNU manuals are distributed under the GNU Free Documentation License, which addresses obfuscation more directly: A "Transparent" copy of a document "is suitable for revising the document straightforwardly with generic" software, and "A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent."
    1. Re:Source code defined by QuantumFTL · · Score: 2, Funny

      "A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent."
      If that's the case, why hasn't the EFF sued Larry Wall and his followers long ago?
  14. CentOS = backspaceware? by MeanMF · · Score: 4, Funny

    Better not give that prominent North American Enterprise Linux vendor any ideas. They might try to put CentOS out of business.

    1. Re:CentOS = backspaceware? by caseih · · Score: 3, Insightful

      Glad to see the moderators correctly marking your post as funny. On a serious note, though, this "prominent North American Enterprice Linux vendor" doesn't own the copyright on most of the software they distribute to begin with. Both they and CentOS properly attribute the copyright owners. And despite the removal of trademarks (done at this "prominent North American Enterprice Linux" vendor's request), they do still attribute copyright to RedHat on programs and scripts that RH created.

  15. Re:WTF? by dosius · · Score: 2, Interesting

    Nah, it's worse (imho) than copyright infringement.

    Most of us who casually infringe copyright don't delete the existing copyright notices and claim the stuff to be our own. These people do, making it plagiarism, which to me is copyright infringement compounded by *fraud*. I could care less about copyright infringement myself, but woe betide anyone who takes my work and calls it theirs!

    -uso.

    --
    What you hear in the ear, preach from the rooftop Matthew 10.27b
  16. What's the problem? by Waffle+Iron · · Score: 2, Funny

    He's entitled to statutory damages of something like $150,000 per copy. He hit the jackpot.

  17. this happened to me by drtsystems · · Score: 5, Interesting

    I spend a lot of time writing a PHP script for myself and decided to release it to the public. I think I threw a GPL notice on it but the source was included either way due to it being PHP. Well I put it up on my website and a few months later go back to update it. I search online and find someone selling it for $50. He refused to take it down when I asked him to which really added insult to injury. (He claimed he downloaded it from limewire therefore its fair game? wtf?) Considering he was actively advertised "his program" (mine with my name and stuff backspaced) he got a lot more people to download it then I did even though mine was free. I eventually got him to take it down by sending a cease and desist notice. (Thanks for the template RIAA)

    1. Re:this happened to me by psychiccyberfreak · · Score: 3, Informative

      4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. So in other words you can modify it and sell it, but if it's copywriten under your name and he removed that, then it's breaking the GPL and you can sue him.

    2. Re:this happened to me by drtsystems · · Score: 4, Interesting

      well he completely got rid of any GPL notices. The fact that it was a PHP script meant that the source was there but he was trying to sell "licenses." I would have no problem with someone adding features to my script and releasing it as a derivative work. I'm obviously not trying to make money off of this seeing as I released it for free in the first place. Its the fact that he pretended it was his, gave me no credit, and tried to make money off of it without doing anything besides backspacing a few lines in the code.

    3. Re:this happened to me by Anonymous Coward · · Score: 3, Funny

      I eventually got him to take it down by sending a cease and desist notice. (Thanks for the template RIAA)
      "This is RIAA. It has come to our notion that you used our copyrighted cease and desist notice text without our permission..."
  18. Re:So, whats the big deal? by Neoprofin · · Score: 2, Insightful

    I think rather than the problem be "I am not getting my due recognition and payment (if applicable)" is that someone else is taking all the time an effort of someone else which allows them to get the recognition and potentially payments if they incorporate a program they got for free and simply slap a $5 price tag on it.

  19. Backspaced comments by Xocet_00 · · Score: 2, Funny

    Tell me about it. I post some really insightful comment in slashdot and somescum cut and paste it and post it as their own insight in other fora and blogs.

    Certified that this comment is not a cut and paste of another poster's comment. Well, as far as I know. And I don't know much.

  20. Re:And why do I care? by Mr2001 · · Score: 4, Insightful

    I am a Slashdot participant. Information wants to be free. I can download other people's music and movies, and share them with millions of my friends via the Internet. Why can't somebody else do the same with software? You're trolling, of course, but here's an answer anyway. The objection is not that the software is being shared -- Paint.NET is freeware anyway, it's supposed to be shared -- but that someone else is taking credit for the real author's work.

    That's fraud: the "backspacer" is lying to every person who downloads the modified software from him (and probably infecting them with spyware too). Many Slashdot participants, like myself, believe that copying and redistribution should be legal with or without the author's permission, but that doesn't mean we approve of fraud. Sharing copies of Star Wars is not the same as telling everyone you're George Lucas.
    --
    Visual IRC: Fast. Powerful. Free.
  21. The solutions easy by rucs_hack · · Score: 2, Insightful

    Just have a project so obscure or specialised that no bugger's going to think its worthwhile nicking in the first place. Like mine for instance /sob.

    Actually licensing is the way to go. True no license will stop someone stealing it, but it will give you the right to send 'cease and desist' notices to any site hosting the offending code. Its very hard to spread a usurped version of a program if reputable download locations won't host it.

  22. Moral rights by frenchbedroom · · Score: 2, Informative

    This discussion makes me wonder if there is such a thing as "moral rights" in the US law. Let me explain : in France, the law gives you two sets of rights to protect your works. One is the "author rights" (droits d'auteur) and is the equivalent to US copyright law, ie, it expires some time after your death. The other set of rights is the "moral rights" (droits moraux), which are _inalienable_, and state that YOU are the sole author of the work and should be credited for it. So basically if you put your work in the public domain, and if someone distributes it and claims it as his own, under French law you can sue him. Is there such a protection in the US ?

  23. Re:Operation as normal by skeeto · · Score: 2, Insightful

    If you can be scammed expect to be scammed

    The only scam here is the removal the copyright notices, not the profit. The Paint.NET guys gave permission for anyone in the world to make money selling their software. Legally, this is simple copyright infringement. Nothing new here.

    Unfortunately it gets taken advantage of every once in awhile by scum who are trying to profit from the work of others

    Looks like Rick Brewster doesn't understand the MIT license, under which Paint.NET is distributed. Besides it not being "freeware" as stated in TFA, the MIT license allows anyone to sell the software and re-brand it however they want (while preserving copyright notices). I believe there is a name for "scum" who do this: Red Hat.

  24. Sugar Public License by lullabud · · Score: 2, Interesting

    Incidentally, this is exactly why SugarCRM left GPL v2 to move to a proprietary license called the Sugar Public License which had an attribution clause in it. The community gave Sugar mad shit because they weren't "true" open source, but low and behold GPL v3 included that type of protection and all the sudden Sugar is back within the good graces of "true" open source software.

  25. Re:So, whats the big deal? by sgtrock · · Score: 2

    You explain /exactly/ why my first stop for Windows "freeware" solutions is SourceForge, my second stop is Freshmeat, and my third is Google to look for an original author's site. Heck, I haven't even looked at Tucows in a couple of years. Problem solved. :)