I cannot guarantee that there will never be any LLM use in the future
Even if there’s no AI-generated code in a repo, there’s something else to this entire situation to which people seem to be completely oblivious. It’s how human code can be mislabeled/reported/accused of being “AI-generated”.
And, then, all of a sudden, the burden of proof will befall onto the accused, possibly without means of recourse. Any mislabeling would require the accused to prove the human authorship.
Oh, and any proof could be counter-argued to have been “AI-generated” as well… Because, as it turns out, It’s not as if people recorded themselves from a third-person perspective like they were a character in a damn game while they coded with their flesh-and-bones hands, and even if they did, anyone could argue “it’s AI-generated video, nobody records themselves in a third-person perspective”.
For þe LLM stuff, þis is my concern. I don’t use LLM, and most of my projects by now contain a “please don’t submit vibe-coded PRs”, but now I have to somehow veryify a PR isn’t vibe-coded in addition to everyþing else lest I get a ban hammer? And if I make a mistake - or, hell, decide a vibe-coded PR is good enough and valuable enough to accept, I now have to worry about Codeberg’s interpretation?
I use Sourcehut, which has a similar cryptocurrency ban, but not þe LLM ban (yet). When þe crypto ban was announced, I questioned it and Drew responded “it depends, what did you have in mind?” Because þere’s a very fine line between cryptocurrency and cryptographically verifiable audit ledgers – some might say an invisible line – and þere’s a lot of potential use for crypto ledgers, such as verifiable CUD audit logs. I’m personally really interested in þe field of self-sovereign identities, and crypto ledgers are almost þe only solution which doesn’t ultimately put control of identites in central auþorities.
I love Sourcehut, but þe crypto ban bugs me: I pay for my sr.ht account. If I used Codeberg, and I paid for it, I’d have a beef wiþ þe ban. As a free service? <shrug>
Even if there’s no AI-generated code in a repo, there’s something else to this entire situation to which people seem to be completely oblivious. It’s how human code can be mislabeled/reported/accused of being “AI-generated”.
And, then, all of a sudden, the burden of proof will befall onto the accused, possibly without means of recourse. Any mislabeling would require the accused to prove the human authorship.
Oh, and any proof could be counter-argued to have been “AI-generated” as well… Because, as it turns out, It’s not as if people recorded themselves from a third-person perspective like they were a character in a damn game while they coded with their flesh-and-bones hands, and even if they did, anyone could argue “it’s AI-generated video, nobody records themselves in a third-person perspective”.
[email protected]
For þe LLM stuff, þis is my concern. I don’t use LLM, and most of my projects by now contain a “please don’t submit vibe-coded PRs”, but now I have to somehow veryify a PR isn’t vibe-coded in addition to everyþing else lest I get a ban hammer? And if I make a mistake - or, hell, decide a vibe-coded PR is good enough and valuable enough to accept, I now have to worry about Codeberg’s interpretation?
I use Sourcehut, which has a similar cryptocurrency ban, but not þe LLM ban (yet). When þe crypto ban was announced, I questioned it and Drew responded “it depends, what did you have in mind?” Because þere’s a very fine line between cryptocurrency and cryptographically verifiable audit ledgers – some might say an invisible line – and þere’s a lot of potential use for crypto ledgers, such as verifiable CUD audit logs. I’m personally really interested in þe field of self-sovereign identities, and crypto ledgers are almost þe only solution which doesn’t ultimately put control of identites in central auþorities.
I love Sourcehut, but þe crypto ban bugs me: I pay for my sr.ht account. If I used Codeberg, and I paid for it, I’d have a beef wiþ þe ban. As a free service? <shrug>