ok genuine crisis of faith here. I've got two games I've been working on, both are intended to be fully open source. One is nearly ready for a public release, the other is probably realistically a year or two out. I feel it is important for the source to be available for the former, and it might not yet be part of any training sets because it only has 17 stars on github, but I'm assuming it probably is already.

The latter is largely not online at all, because I simply haven't built it yet...

I was ambivalent about my code going into training sets, but now for a variety of exciting reasons I am no longer ambivalent. So here's the conflict: the only way I can think of to realistically prevent it from ever going into the plagiarism machine is to simply never make the source available. There we go. That's the crisis of faith.
This is all possible because we had a healthy commons and so that's the reward for building a healthy commons: enclosure by billionaires who are promising the end of everyone's ability to make a living in a creative field. If that really will come to pass, we'd have been better off if we never shared anything on the internet and that really hurts.

@aeva they cannot really take the commons, though. BSD still exists, despite their permissive licence.

The enclosure happens where they take on key roles in key projects, and steer development in the direction they want, that is constant effort and cannot be automated.

@GyrosGeier yeah I used to also think that I can ignore the problem and it will go away, but I now understand that anything I make that ends up in the slop training set directly contributes to the credibility of these thieves, and so by continuing to ignore the problem you are very indirectly contributing to perpetuating it.
@GyrosGeier and there are some significant consequences to allowing the problem to metastasize, and some of them we are seeing already. the one weighing on my conscience the most at this particular moment is these tools being used by the military to pick random targets to bomb.
@GyrosGeier I think there is also a very real possibility that if these tools may get to the point where they are able to consistently generate passably functional garbage, and we're just going to be wallowing through an endless sea of liquid shit for the rest of our lives. You don't need "AGI" for that to happen, you just need the cost/benefit scale to tip far enough in one direction. You also wont have a career in tech anymore that isn't cleaning up superfund sites.
@GyrosGeier and that liquid shit will leak into your precious BSD. maybe the funding will dry up and that will be the only way to keep development going. or maybe it'll just die too.