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.
right now my best answer is just... not open source anything. or at least, hang on to it for a few years, see what happens with this bubble. if it pops and takes down half the west coast tech industry, nothing was lost and source code can go online again. if it doesn't though, well, i guess go ask the god mommy machine to hallucinate an interactive video for you or something i'm sure it'll be just as good 🙄
@aeva
A few thoughts on this, short cuz I should be asleep but - you're far from the only person reacting this way right now unfortunately. There's a bunch of us that are witholding releases for sake of keeping it out of the sludge machines. But the good part here at least is that you can always release it later.
@aeva
Another thought though is licenses. This relies on an optimistic view that the law is/will be an ally to us but if you use a license with explicit carveouts preventing feeding into The Machine™️, they will ignore it and they will slurp up the codebase, but in doing so it will create a poison pill allowing a legal case to be made in the future, realistically as member of a class action. It's been... Hilariously easy to prove that your work has been added to datasets by replicating snippets
@aeva I don't blame anyone for having zero faith in the law as an ally on this one though, so don't feel bad if you're pessimistic about it.