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 I think “source available on good request” after a conf talk etc is often a good option. Not everything needs to be widely public, not anymore, but collaborative communities are vital.
@coral @aeva Agreed, and also I've seen that turn into de facto gatekeeping. This shit is really hard...
@xgranade @coral I think that will only delay the source going online not prevent it. Also given they've got bots now that email maintainers to harass them into accepting contributions, I think it wont be so simple.
@aeva @coral "bots to harass" is kind of their whole modus operandi, yeah. I hate this timeline.
@xgranade @aeva I would not consider a email to be enough evidence of collaborative intent on its own to share much. For me, the goals are to support good work whist sharing enough to interest specific external parties, like any researcher, and research-like norms can be used.
@coral @xgranade @aeva anecdotally not using github and adding a few nginx rules to blackhole obvious scrapers gets rid of the bot traffic
@coral @xgranade @aeva this is all you need