There is a health app that is very important to sufferers of a specific disease and it is freemium and I find this detestable. I am doing a clean room rewrite of it in its entirety and plan to release it on fdroid. Is there a license that prevents some ghoul from forking it to profit from people’s misfortunes? I am trying to avoid legal issues by being clean room but will try to keep my publishing of the app as anonymous as possible regardless. Thanks

  • Dessalines@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    1 day ago

    Is there a license that prevents some ghoul from forking it to profit from people’s misfortunes?

    The GPL-based licenses (GPLv3 and AGPLv3 if it uses a network), are the best options available for this, because it forces any downstream / forked projects to disclose their source code, and adopt the same license (as well as a few other conditions). The “softer” licenses don’t force forks to disclose their code, which is the main way companies can EEE or privatize our software. (Of course there are probably a lot of private companies abusing this, but since their source code is private, we can’t make legal cases against them until a whistleblower leaks their code).

    While the GPL doesn’t explicitly state things like no ads and no telemetry, in practice those things are rarely added, because the downstream project would then need to publish its use of those, and few people (especially code contributers) would prefer a fork with telemetry added.

    https://choosealicense.com/licenses/

      • Dessalines@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        3 hours ago

        I’m skeptical of it, mainly because of a lot of criticisms people have of the FUTO org in general. Its a private company with some shady history, that doesn’t just fund open source, but also takes them under its control, and has them use their own license.

        Very few of these licenses have actually been tested in court cases, but the GPL is one of them.

      • hirihit640@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 hours ago

        Not the person you’re replying to, but I think the issue is that other people can still re-package your app with ads/telemetry, and publish the source code to adhere to GPL requirements, and still capture users if they use the right marketing keywords to appear at the top. I believe this was the issue FUTO/Grayjay ran into: lots of copycat apps on the app store that got lots of installs, while the real app was buried.

  • Guiorgy@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    22 hours ago

    Firstly, not legal advice here, I’m not a lawyer.

    A license is just a set of terms that dictate what you can and cannot do, so you can write whatever you want there (though I’d advise the help of a lawyer if you do so). However , only those licenses that satisfy certain requirements can officially be called and considered Open Source_, among which, one of the most important ones is that you cannot control how and for what the downstream users use the code, so a if you use a true open source license, you can prohibit someone from forking, adding ads and such to it and distributing wherever they want. If you want such clause, your license can’t be “open source”, but if you are fine with that, it’s your choice, so do whatever you want.

    PS. Note that the license is only important as long as it is actually enforced, so doesn’t matter what it says if everyone ignores it. For example, uBlock Origin is licensed under GPLv3, so any derivative should provide the modified source code to the users, but most commercial ad blocking browser extensions are based on it and violate this clause, but the uBlock creators stopped caring about it since the legal headaches are not worth it.

  • thingsiplay@lemmy.ml
    link
    fedilink
    arrow-up
    9
    ·
    2 days ago

    If you have such requirements like “cannot contain ads, telemetry or freemium features”, then its no longer Open Source. What you want is a custom license with the terms you define like that.

  • hirihit640@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 day ago

    Maybe FUTO’s Source First license? Afaik it was created specifically to prevent others from re-packaging open source apps and selling them on the app store.

    Users must be allowed to modify the software they are running for their own use and have the right to redistribute it for non-commercial purposes. This does not include the right to strip out payment links or use trademarks in modified versions of software.

    It’s pretty controversial because it isn’t technically open source, but it does seem to have reasonable principles behind it.

    • marcie (she/her)@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      This is interesting. I personally would like it to be a little more permissible than this but its kinda close to what I want

  • justme@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    1
    ·
    1 day ago

    i finally got mod to look up what means Cleanroom software engineering. reading through the Wikipedia article, I would have just called it real programming (in contrast to vibe coding or slopping). but ok, considering the state of a lot of software, it’s valid to give serious software development its own name.

  • vagrancyand@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    29
    ·
    3 days ago

    None. You’d need a custom license. All open source licenses follow the Open Source definition, of which:

    Rule 1: Free Redistribution The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.

    Rule 6: No Discrimination Against Fields of Endeavor The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.

    And really rule 4: Integrity of The Author’s Source Code The license may restrict source-code from being distributed in modified form only if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.

    Now anyone that does fork it to add such unwanted features still must follow the other parts of your open source license, so GPL is still best since people can just strip out the added-on features later since they’d be, theoretically, obligated to open source their fork… but the entire framework of open source software is built on the concept of ‘I make a thing, whatever you do with it is your problem as long as you agree to that same term.’

  • terabyterex@lemmy.world
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Decompilation is not clean room. Ckean room is when one group of people write a spec of functionality of an existing product and the other group in the clean room have no access or functional knowledge of existing app.

    Also foss is about fresom not restrictions.

    That being said. There are licenses that require forks to also be open source

  • grue@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    3 days ago

    There isn’t one, for multiple reasons.

    First of all, as @vagrancyand already mentioned, the restrictions you want violate the rules of Open Source (or Free Software, for that matter).

    Second, there is no such thing as a “clean room decompilation.” That’s still a derivative work of the closed-source thing you’re “decompiling,” which means it’s just copyright infringement with extra steps. You don’t have the right to relicense it in the first place.

    Using AI to “free” proprietary software may look like a popular thing to do right now because tech moves faster than the lawyers do, but all these projects are going to get sued out of existence sooner or later.

    • Guiorgy@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      22 hours ago

      Technically, if you skip the reverse engineering step and just clone app functionality yourself, or everyone agrees that LLM written code is fine here (which is still up for debate), then it should be fine (unless they have a patent on the functionality, but that’s a separate thing). I don’t know whether the projects you mentioned did any reverse engineering, but if they didn’t, they have hope of avoiding legal issues if LLM code generation is deemed by court as non-infringing in at least one case.

      • grue@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        21 hours ago

        On top of what I previously mentioned, there’s also the argument that LLM output is a derivative work of its training data (or at least, can potentially be if it outputs identifiable chunks), which means that all generated code is copyright infringement because the LLM was trained on sources with incompatible licenses.

        • Guiorgy@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          11 hours ago

          Again, even if I personally agree with that, it’s yet to be tested in court, hence, “they still have hope”.

  • it_depends_man@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    3 days ago

    No.

    At least I don’t think that’s how licenses work.

    And there are no licenses that prevent selling open source code as far as I know. The only limit is that if the software is sold, they still have to provide a license and a copy of the source code. But I don’t think a license that would prevent people from extending whatever, for example with ads, would work.

    And I should add, people use the popular licenses like MIT, GPL, because they’re proven and there have already been court cases ruling on obligations of people who took this or that piece of source code. You are free to write your own license, but if it holds up in court is then completely your problem.

    Same as TOS, you can write anything you want into them, ultimately it’s a court that decides if it’s a valid thing or not. But only if there is a lawsuit.

  • TootSweet@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 days ago

    Some folks are saying that decompiling violates copyright law. I can’t speak to any jurisdictions other than the U.S… (And for that matter, IANAL and this isn’t legal advice, so really I can’t speak with any authority to U.S. copyright law. I’ve read a bit on the topic, but that’s the most I can say.) But I think that’s at best an oversimplification.

    A court case that dealt fairly directly with the question of whether decompiling violates copyright law was Sega v. Accolade. Just to hedge further, court cases are very fact specific and a lot of caution should be exercised when applying that ruling to a different case. Also, it’s possible that in the future, a court could simply overturn the previous ruling. However, in that case, the courts found that:

    We conclude that where disassembly is the only way to gain access to the ideas and functional elements embodied in a copyrighted computer program and where there is a legitimate reason for seeking such access, disassembly is a fair use of the copyrighted work, as a matter of law.

    (Yes, it uses the term “disassembly” there, but the Wikipedia page appears to interpret that to include decompilation. As the Wikipedia page says: “Accolade’s decompilation of the Sega software constituted fair use.”)

    All that is not necessarily to say that “decompiling is legal”. There are other parts of law which in one specific circumstance or another might make decompilation “illegal”. For instance, an EULA might forbid decompilation. (A lot of EULA’s do just that.)

    So, I guess the moral of the story is: to find out whether decompilation is legal or not in a given case, seek legal advice from a lawyer.

    Sorry that didn’t really speak to your actual question, but I believe the folks who are saying that what you’re describing couldn’t qualify as an Open Source license are correct.

    • Ferk@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      1 day ago

      “disassembly” is pretty much a synonym with “decompiling”.

      I think the ambiguity is in the extent of “the only way to gain access to the ideas and functional elements” (are we sure there’s no other way to re-implement the ideas behind the software without dissasembling it?) and what counts as a “legitimate reason for seeking such access”.

      • TootSweet@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Yeah, for sure there’s a lot of complexity in evaluating the specific case at issue.

        The “the only way to gain access to the ideas and functional elements” bit kindof goes back to the legal theory that copyright gives protections to “expression”, not “ideas”. (For instance, Baker v. Selden. To oversimplify, Selden came up with an original way to do bookkeeping and wrote a book about it, Baker learned the method from Selden’s book and wrote his own book about the same method, and Selden sued Baker. The courts said that since all Baker “copied” was the “ideas” and not the “expression”, there was no copyright infringement, so Selden didn’t get any damages or anything.) And “functional elements” basically count as “ideas” more than “expression”. So, they’re kindof saying that (again, oversimplifying, IANAL, seek legal council, etc) if your method of keeping people from understanding your algorithms is just the difficulty barrier involved in decompiling, then copyright won’t say that decompiling isn’t allowed. Which is still open to a lot of interpretation, don’t get me wrong.

        The “legitimate reason for seeking such access” in this case was understanding the Sega Genesis scheme for preventing unlicensed games from working on their systems and the algorithms involved. Accolade did that specifically in order to defeat Sega’s “DRM” and create games that would run on the Genesis. So I guess that counted as “legitimate reason” in the 9th circuit court’s estimation at the time.

        Of course, that was before the DMCA, which… who knows how Genesis v. Accolade would have gone had the DMCA “circumvention” thing been in the mix. It probably would have to have been considered, but who knows if it would have changed the actual ruling.

        Anyway. Yeah. This stuff fascinates me.

        My knowledge basically comes from reading through that whole IP caselaw textbook that I linked in my previous comment. But it’s cool to have a little insight into some of the legal theory involved in such things as copyright licenses and such.