this post was submitted on 16 Jun 2024
1004 points (88.6% liked)

linuxmemes

21455 readers
1653 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    1004
    With GPL, you're programming Freedom. With MIT, you're programming for free. (lemmy.world)
    submitted 5 months ago by renzev to c/linuxmemes
    250 comments fedilink hide all child comments
     

    Context:

    Permissive licenses (commonly referred to as "cuck licenses") like the MIT license allow others to modify your software and release it under an unfree license. Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

    Andrew Tanenbaum developed MINIX, a modular operating system kernel. Intel went ahead and used it to build Management Engine, arguably one of the most widespread and invasive pieces of malware in the world, without even as much as telling him. There's nothing Tanenbaum could do, since the MIT license allows this.

    Erik Andersen is one of the developers of Busybox, a minimal implementation of that's suited for embedded systems. Many companies tried to steal his code and distribute it with their unfree products, but since it's protected under the GPL, Busybox developers were able to sue them and gain some money in the process.

    Interestingly enough, Tanenbaum doesn't seem to mind what intel did. But there are some examples out there of people regretting releasing their work under a permissive license.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] robigan 2 points 5 months ago (1 children)

    I like your idea about using permissive licenses as long as it helps people. But as you said, “if … that makes someone else’s life better or easier …”, what would you do if someone used it to hurt people instead? I’d personally feel like shit if my software were used for that, and as others said in this post, they’d prefer to have entities request an exemption rather than have their code used in ways they don’t approve of. So what say you?

    [–] [email protected] 1 points 5 months ago (1 children)

    what would you do if someone used it to hurt people instead? I’d personally feel like shit if my software were used for that, and as others said in this post, they’d prefer to have entities request an exemption rather than have their code used in ways they don’t approve of. So what say you?

    I've a few thoughts on this:

    • Anyone who wants to use anything that I release for harm, will probably do so regardless of license. Bad actors are going to act badly. Plus, chances are that they'd see no legal repercussions as underdogs winning in court is the exception, not the rule. The legal system is heavily stacked against the little guy.
    • I tend to specifically avoid working on things that are weaponizable to reduce the chance of ethical conflict.
    • The projects that I've released or plan to release tend to be pretty esoteric. The one that saw the most interest was years ago and it was an adapter between abandoned gallery plugin and an abandoned social media CMS thing. It would take some great creativity to hurt people with that, other than making them read my horrible code from that era. My current projects are more about FPGA and mixed reality stuff.
    • Once I've created something and shared it freely, it is no longer wholely mine. I cannot dictate how one uses it, anymore than a musician can dictate how someone listens to the radio. As long as one abstains from creating tools intended to harm (or that can be predictably turned to harm), I don't see legitimate ethical culpability. We only have control over ourselves.
    [–] robigan 2 points 5 months ago (1 children)

    Interesting, I see why you’re saying that who wants to do harm with your code can do so however they want. Although licenses are the rules of the system which gives a fighting chance to stop such abuse if I can. Not that the system works properly most of the time, but it doesn’t mean it never will.

    [–] [email protected] 1 points 5 months ago

    Exactly. Bad actors are going to act badly. Unfortunately, something that we have to accept as reality (and something that some political philosophies fail to plan for). Bad actors will break the rules and, if they are wealthy, they will more often than not get away with it in the current state of affairs.

    However, I would say that you bring an interesting point. It would be worthwhile, philosophically to have a "Pacifist MIT" license, being permissive but explicitly denying legal use to MIC.