@elementary tl;dr I support your objectives, and kudos on the goal, but I think you should monitor this new policy for unexpected negative outcomes. I take about 9k characters to explain why, but I’m not criticizing your intent.

While I am much more pragmatic about my stance on #aicoding this was previously a long-running issue of contention on the #StackExchange network that was never really effectively resolved outside of a few clearly egregious cases.

The triple-net is that when it comes to certain parts of software—think of the SCO copyright trials over header files from a few decades back—in many cases, obvious code will be, well…obvious. That “the simplest thing that could possibly work” was produced by an AI instead of a person is difficult to prove using existing tools, and false accusations of plagiarism have been a huge problem that has caused a number of people real #reputationalharm over the last couple of years.

That said, I don’t disagree with the stance that #vibecoding is not worth the pixels that it takes up on a screen. From a more pragmatic standpoint, though, it may be more useful to address the underlying principle that #plagiarism is unacceptable from a community standards or copyright perspective rather than making it a tool-specific policy issue.

I’m a firm believer that people have the right to run their community projects in whatever way best serves their community members. I’m only pointing out the pragmatic issues of setting forth a policy where the likelihood of false positives is quite high, and the level of pragmatic enforceability may be quite low. That is something that could lead to reputational harm to people and the project, or to community in-fighting down the road, when the real policy you’re promoting (as I understand it) is just a fundamental expectation of “original human contributions” to the project.

Because I work in #riskmanagement and #cybersecurity I see this a lot. This is an issue that comes up more often than you might think. Again, I fully support your objectives, but just wanted to offer an alternative viewpoint that your project might want to revisit down the road if the current policy doesn’t achieve the results that you’re hoping for.

In the meantime, I certainly wish you every possible success! You’re taking a #thoughtleadership stance on an important #AIgovernance policy issue that is important to society and to #FOSS right now. I think that’s terrific!

@wigol Not in the `~/.authinfo.gpg`

Incidentally I've just posted on #emacs #stackexchange with more information

https://emacs.stackexchange.com/questions/82584/pulling-issues-using-forge-fails

@neilk@xoxo.zone I exclusively do take-home math tests and my colleagues keep telling me I should be afraid of students using LLMs to cheat.

For a low level class I do have to think about writing the questions in a way that can't be answered by WolframAlpha. For a proof-based class I have to think about students searching stack exchange and finding the exact question or something very close.

On the other hand, I do not write my test questions with LLMs in mind. When I finish writing the questions I do feed them into Google Gemini and Microsoft ChatGPT just to check, and both LLMs consistently fail to earn even partial credit.

I don't believe students using LLMs to "cheat" on math assignments is a real issue, at least not at the college level.

#ITeachMath #LLM #WolframAlpha #StackExchange #TakeHomeTest