Slashdot Mirror


VX30 Ad-Stats Code Online

tmk writes "Drunkenblog has done it again. After deconstructing Maui X-Stream has GPL Violations with reproducable proof, he put a copy of the VX30 Ad-Stats source online. There is also a copy of the phpAdsNew source to compare. Drunkenbatman says 'This is a community problem, and it's pretty much up to you.'"

18 of 248 comments (clear)

  1. Gotta trackback... by BrynM · · Score: 5, Informative
    For those who don't RTFA, you should. The second trackback from the post on the 18th points to a post on Rakaz's blog (he's the author of phpAdsNew) from the 19th. They admit guilt and dig their hole deeper. Damn. They're SCOing themselves in the foot.

    MXS responds... round 2 from rakaz Totally out of the blue I received an e-mail from Jonathan Miller at Maui X-Stream. Okay, not totally out of the blue, but still a bit unexpected. In this email Jonathan concedes that VX30 Ad-Stats......
    Get this quote: "As I believe you are aware we do have a product called VX30 Ad-Stats that is based upon phpAdsNew." - Jonathan Miller of Maui X-Stream

    Darl must be beaming and handing out cigars by now...

    --
    US Democracy:The best person for the job (among These pre-selected choices...)
  2. Innovation by /ASCII · · Score: 4, Informative

    Maui does seem to have a new mode of operation here. Whenever somone proves that they stole some source code, they say 'Oh, that... Yeah that was just a bit of test code we borrowed. The new release is clean.' Then they release a new version which is identical to the old version, except maybe they altered some text strings to make the release appear to be different.

    --
    Try out fish, the friendly interactive shell.
    1. Re:Innovation by sosume · · Score: 4, Informative

      I compared the source code, and except for the copyright banners, they just did a global search-and-replace to change phpAds to AdStats.. pretty lame imo.

  3. What ELSE has Maui stolen? by Ritz_Just_Ritz · · Score: 5, Interesting

    OK, so they denied taking something and it was proven (at least to my satisfaction) that they did. Now Maui is "coming clean" that they "borrowed" GPL code and want to play nice. I guess they figure it's easier to ask forgiveness than permission. It makes me wonder if their other products have similar issues.
    A slippery slope.

  4. Re:The GPL isn't all that by El_Muerte_TDS · · Score: 5, Informative

    Here's not advice:
    Exchange your lawer for one that actually knows his trade.

    IANAL: but the GPL FAQ clearly states that output generated by a GPL program isn't covered by the GPL, so it's 100% safe to use programs like GCC for compiling your program.

    And another thing, pretty much all Open Source licenses only "restrict" you in one way when you distribute your creation. If it's kept in private you are not "restricted".

  5. Re:So.. by /ASCII · · Score: 5, Informative

    That question is pretty easy to answer. It is ok to use GPLed code in a beta of your closed source software to 'test stuff' so long as you don't distribute it.

    So by the first _public_ beta, that code had better be gone, before that it's all fair play.

    --
    Try out fish, the friendly interactive shell.
  6. Re:The GPL isn't all that by Marcion · · Score: 5, Insightful

    You are misinformed on many points. Get a better laywer I think.

    The GPL is not holding the GNU/Linux OS itself back, only people who want to hoard the code. If you use the software only in-house then there are some limited exceptions within the GPL, so you again should get a better lawyer.

    "no business will ever be able to use it. "

    Well IBM and many other companies have been able to get on with it. The GPL divides smart and innovative people from the cut and paste brigade. If you can't make a profit then it is your own stupid fault.

    "Its draconian requirements"

    You are clearly confused and are reading the situation backwards. A normal software license gives you no rights to use the code at all.

    The GPL however gives you all the rights but one: you do not have the right to remove the rights of others. You can use the code that has been created at much expense only if you do not attempt to make free software unfree.

    No one is forcing you to use GPL'd code. If you want to buy in code to save time then you have to pay for it. The cost for GPL'd software is that you have to share improvements.

    There is no such thing as a free lunch, stop crying about it and get on with your life.

  7. Re:READ THE LICENSE before you blog about it by drunkenbatman · · Score: 5, Interesting
    YES THEY DO HAVE TO MAKE IT AVAILABLE TO EVERYONE. The only way to avoid that is to ship the source with the binaries. Otherwise you have to give the source to anyone who asks ("any third party") for no more than a nominal fee.


    I was going by the GPL FAQ, which I've found to be very helpful but I could be misinterpreting something... Under "If I distribute GPL'd software for a fee, am I required to also make it available to the public without a charge?

    "No. However, if someone pays your fee and gets a copy, the GPL gives them the freedom to release it to the public, with or without a fee. For example, someone could pay your fee, and then put her copy on a web site for the general public."

    The GPL FAQ, under "What does this "written offer valid for any third party" mean? Does that mean everyone in the world can get the source to any GPL'ed program no matter what??" says:

    ""Valid for any third party" means that anyone who has the offer is entitled to take you up on it.
    If you commercially distribute binaries not accompanied with source code, the GPL says you must provide a written offer to distribute the source code later. When users non-commercially redistribute the binaries they received from you, they must pass along a copy of this written offer. This means that people who did not get the binaries directly from you can still receive copies of the source code, along with the written offer.

    The reason we require the offer to be valid for any third party is so that people who receive the binaries indirectly in that way can order the source code from you."

    It would appear someone would have to receive that 'offer' in some way (I.E., the company distributed it to them) in order to be entitled to ask for the source, with the 'third party' bit coming in once a fellow user distributes it to you. Basically, if the company or someone else hasn't given you the software, the company doesn't have to give you anything.

    Like I said, I could well be misinterpreting.
  8. Perhaps it's time... by Senor_Programmer · · Score: 4, Interesting

    for investigative and prosecutorial branches in the OSS legal community. It might well be self supported from awards and even generate some $ to put in developers pockets.

    1. Re:Perhaps it's time... by bheer · · Score: 5, Funny

      Yup, we could call ourselves the Open Source Association of America. The OSAA would would be a cartel of orgs big (IBM, Redhat, Novell, etc) and small, and we could go about auditing businesses' code for GPL violations.

      When PHBs see our 733T audits-required letters, they'll _finally_ take Open Source seriously, because everyone knows you're not a serious player in this biz unless you send threatening letters by the dozen.

  9. Re:The GPL isn't all that by jjleard · · Score: 5, Insightful

    ...and so one day me and my buddies stumble upon this remarkable tower which soared into the clouds. We talked to the natives who explained that local peasants had built the tower over a thousand years and that everyone was welcome inside. We were told we could even live in the tower, modify it or add to it if we wanted. Anywho, my buddies and I spent about three months adding a room to the top of the tower. That place was decked out too -- shag carpet, wall-to-wall speakers with a phat 8-track STEREO sound system, posters, a big fountain. I'm tell you, that place was the... well, it was quite nice. So one day we get a knock on the door. The local peasants want to come in and have a look at our addition. They said, "we often are inspired by the ideas of others and would like to see what you have done." Can you believe that?! Fucking pricks. Coming in to STEAL our ideas?! After all the work we had done even! Man, I just don't know about peasants sometime. I don't think they understand anything.

  10. Community problem? Business ethics! by winchester · · Score: 4, Insightful

    It's not a community problem... it's a business ethics problem. As long as companies can get away with using open source software in closed source products, they will continue to do so.

    Only when the first cases are brought before court, we might see an improvement. Until that moment, this will continue.

    1. Re:Community problem? Business ethics! by mpcooke3 · · Score: 4, Insightful

      You mean GPL'd software in closed source products. Open source = many licenses (including LGPL, MIT and BSD which can be used in closed source products.)

    2. Re:Community problem? Business ethics! by pcmanjon · · Score: 5, Insightful

      " You write a program and make it freely available, including source code.
      Someone takes that program, makes a few changes and releases it as their own.
      You take legal action against them for "GPL violation" all you're really doing is being a prick.
      "

      Actually they're being a prick.

      You see, they took the code but failed to open source it.

      We code our hearts out and open source something only to have someone steal it, enhance it, and then not release the code like we did?

      That's pretty prickish to me. That's like 'Hey, cool, nice code, lets fix this, there, and there, BUY OUR PRODUCT (source not included) PROFIT!!!'

      In this case, the original developers of the code can't apply the enhancements made to their code. That isn't fair, or morally acceptable.

      Threatoning to sue them if they don't open source their product under the GPL swiftly isn't being a prick, it's only fair.

    3. Re:Community problem? Business ethics! by greenrd · · Score: 4, Insightful
      You write a program and make it freely available, including source code. Someone takes that program, makes a few changes and releases it as their own. You take legal action against them for "GPL violation"

      Although *technically* you are justified for taking action, in reality, all you're really doing is being a prick.

      I think you missed the money aspect of it here. Personally, if someone's going to make money out of selling the product of my labour, I'm willing to let it go if they abide by the GPL - but if they don't abide by the GPL and they're making money out of it, I want to see some of that money. And/or I want them to stop.

      I think that people from most political ideologies - from free market to Marxist - can agree that for another person to take the product of your labour, and sell it without your permission, and give you nothing in recompense, is immoral. Who exactly is being a prick here?

      Also, the whole point of the GPL, the intention of it, is to stop things like this happening. Putting the GPL on something is like putting a big sign on it saying "DO NOT TURN THIS INTO PROPRIETARY SOFTWARE WITHOUT MY PERMISSION!"

      It's not a technicality. It's the whole point of the GPL!

  11. What ELSE has Maui stolen? by strider44 · · Score: 4, Informative
  12. I don't see it by kmortelite · · Score: 4, Funny

    The name of EVERY FUNCTION is completely different. All the ones in Maui software start with ADSTATS and in the so-called original, all the function names begin with PHPSTAT.

    How could this be copying code?

    And as for all the function bodies being exactly the same code, well, it's a miracle. I guess good programmers all format their code exactly the same, use the same comments, and even misspell the same comments. Uhm, I gotta go.

    Sincerely,
    Maui X^H^H^H^H^H^H Someone with no financial interest in the outcome of this situation

  13. GPL *AND* DMCA violation by FellowConspirator · · Score: 5, Insightful

    I looked into the Maui X stuff and checked, and yes, they are very cleraly violating the GPL. It strikes me, however, that by making it impossible to obtain the source code, they are circumventing the technological measure of access control (namely, the source code in ASCII form).

    The DMCA doesn't necessarily require an access control measure to lock someone out of access to a work (how it is typically employed). Specifically, a technical measure is:

    (B) a technological measure `effectively controls access to a work' if the measure, in the ordinary course of its operation, requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work.

    I'd argue that distributing source code so as to grant access to the work is an effective measure to do so, and that in the normal course of it's operation (communicating the structure of an application) that it requires the application of information (headers, expert knowledge, software analysis tools), a process or treatment (at the very least, a system tath can decode ASCII and render it as glyphs on a display or printed page), and the authority of the copyright owner (a license; namely the GPL).

    It seems to mee that if you contact their ISP you can have their site shut down. Further, you can complain to the FBI since it's now a federal criminal complaint:

    (a) VIOLATIONS REGARDING CIRCUMVENTION OF TECHNOLOGICAL MEASURES- (1)(A) No person shall circumvent a technological measure that effectively controls access to a work protected under this title. The prohibition contained in the preceding sentence shall take effect at the end of the 2-year period beginning on the date of the enactment of this chapter.