1. 3
  1. 2

    Let’s be clear on the premise of this argument: the code has a liberal license but the output of the code should not.

    I’m not sure this is a novel debate. Lingdong wants to restrict the code’s use in a commercial context. I’ve talked to other devs that longed to limit their code’s use in the context of state violence.

    As the article points out, there seems to be no solution here from the Open Source Initiative. But the OSI’s position is almost certainly the only rational one. Property right restrictions will continue to seem absurd absent of a functioning digital commons.

    1. 1

      I agree that as long as FLOSS licenses are basically a clever hack on copyright, you can’t really realistically get rid of Freedom Zero. But what this situation points to is what I think is becoming a growing distaste of the fundamentally exploitative nature of some open-source - a creator releases something to the world, and it is immediately harnessed to produce profit.

      The emergence of NTF enthusiasts[1] has merely closed the loop from months to days. Generative art is catnip to these people, as it enables them to produce any number of unique items to “mint”, without having to cut any profits to artists. The fact that they quickly backpedalled in the face of massive criticism is testament to the power of moral suasion, and the fact that the thin fig-leaf covering the naked greed of NFT purveyors is the fiction they’re helping artists. One does not kill the golden goose.

      [1] scientific name: nftardius parasiticus

      1. 1

        The emergence of NTF enthusiasts[1] has merely closed the loop from months to days.

        It’s an interesting idea that NFTs are making this exploitation more immediate. But it seems that the sort of contracts that could fix this could only come in the form of code.

        For example, many NFT contracts provide a mechanism to pay artists upon resale. This has a rich history throughout the 20th century, but it was really hard to make it ubiquitous and permanent. And now here we are.

        But the only way to prevent cut ’n paste jobs is to distribute a binary or couch it in a more complex (and hidden) system. This seems like its own nightmare.