• Aatube@kbin.social
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    9 months ago

    I mean, pretty sure legally that that’d be very bad for whoever makes contributions-

    This is the exact reason why I’ve released this [license] with GLWT license and I have no intention to spend my time discussing or change the license. Try to figure out how you can use it on your project. Or don’t use it at all. I don’t care. Good luck.
    —Ahmed Shamim, 2021

    • abhibeckert@lemmy.world
      link
      fedilink
      arrow-up
      9
      arrow-down
      4
      ·
      edit-2
      9 months ago

      The sentence “IN NO EVENT SHALL THE AUTHORS BE LIABLE” doesn’t fly where I live. You don’t get to choose wether or not you’re liable - the law decides who is liable. This thing is about as enforceable as those sovereign citizen license plates and would get the same reaction in a court room.

      Plenty of other commonly used licenses have the same issue unfortunately and and the biggest nightmare (at least in my country) is laws against “misleading” or “deceptive” conduct. Telling someone you’re not liable for anything is blatantly misleading/deceptive.

      Even if your software works perfectly, you are still breaking the law… a victimless crime that would normally fly under the radar or result in a “cut that shit out” order by the court… but it’ll really hurt your case if there is actually a victim (e.g. if your software has a bad security flaw that caused real damage).

      That’s why organisations with big legal teams tend to choose licenses like Apache 2.0. Ones with language like “unless required by applicable law (such as deliberate and grossly negligent acts)”.