this post was submitted on 27 Aug 2026
44 points (100.0% liked)

Technology

43468 readers
233 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] tangeli@piefed.social 2 points 2 hours ago (1 children)

Even if AI generated code can't be detected reliably, it is good to have a clear policy to guide projects and contributors. At least those contributors acting in good faith and honestly will do the right thing, and projects will have a basis for rejecting contributions from people that are found to willfully or negligently violate the policy. Blocking all malicious actors will be an ongoing effort, whatever the policy.

[–] radioactivefunguy@piefed.ca 1 points 22 minutes ago (1 children)

For me, if a PR looks good, and I can reach out to the contributor and they can competently discuss their work, then its fine with me if they used AI to code it.

I think a sensible policy would be: use whatever tools you like to contribute, but own the contribution. Obvious slop code is rejected.

[–] tangeli@piefed.social 1 points 10 minutes ago

I agree as far as responding to questions and issues that arise from the contribution but my understanding is that from a legal, copyright perspective, if AI generated the code then the contributor can't own the copyright, nor assign it. So my preference would be: no AI generated code. Other use of AI tools (e.g. finding vulnerabilities) might be OK but there are still the environmental and ethical issues to be concerned with, so I remain ambivalent. It will be interesting to see the decision of the Debian community.