I had a report for AI slop today. 1m LOC in 3 months. How do you even modify and distribute that? I do not think we had a rule against it.
IMHO if we allow, the community gets drowned out by AI vomit and it is harder to see handcrafted loved projects that are easy to modify and distribute.
My mind is to ban it to preserve open source.
Are folk in agreememt with this line? Would love to hear your thoughts.
A lot of people are making well-reasoned arguments about human nature, the nature of a dangerous tool, defining responsible use, and the challenges inherent in any sort of ban.
The points that look the best to me definitely include tagging, but I haven’t seen suggested any method of gatekeeping as to who has access to the means of dissemination of software. Because the damage by the tool is determined by the one who wields it, only people who have established trustworthiness should be allowed to contribute.
Ban it, lemmy sets itself apart from places like reddit by having actual quality posts.
Maybe start out with strict labeling guidelines. If it’s AI then it should be labeled as such. If a user posts something that’s Ai and doesn’t label it then ban that user. Maybe a warning first up to you.
But if the choice is between blanket everything allowed or blanket ban I lean more toward blanket ban.
I think the new category - “open source and hand-made/human crafted software” should be introduced
Tag and ‘[AI]’ in title if not ban. But would very much like it if such posts were simply banned. I don’t think the community would loose any value.
I do not think a ban would be efficient. It would just force those who use AI to dissimulate it. I see it a bit as drug use, banning hasn’t solved the problem ; and the countries who handled it the best were those regulating the use.
So I think we should look for a good regulation. It is more complicated to set up, but it has a chance to work.
In my mind, it should allow some projects to identify as not using any AI, and request that each project define what is their use of AI. Ideally, we could know this without opening the project (maybe thanks to a badge).
Also, shaming the use of AI only has the same aim as banning it: forcing it to grow hiden and out of control.
Ban the use of AI, Stack overflow, and documentation in general. If a human can’t build their functions from scratch using Assembly for every project, then their work is slop. They also can’t reuse their code because copy pasting is ethically wrong even if you know what the functions do.
The interesting thing about this post is that it’s exactly equally as wrong whether you take it as sarcasm or at face value.
Yeah I don’t think we need slop projects being posted here. I know a lot of people are using these tools even for personal projects nowadays but tbh I’m not really interested in exploring any project heavily written by AI.
I’m conflicted. I’m anti-AI due to distrust in capitalism and our pseudo-democratic plutocracies, the profit motive to replace the human workforce, the reckless criminal-incompetence of its implementation, and apparent stupidity of the average hairless primate in understanding that you can never trust a correlation engine… but it’s just a tool, and I’ve also found it incredibly useful in my limited and controlled usage; getting it to write small functions or blocks of code, then amending and composing them myself.
How do we determine what is “heavily written by ai”, and all the obvious slop factory bullshit, without banning strong projects who are just leveraging it for legitimate dev work; as a glorified autocomplete, test autofill, etc but still read and validate every line of code?
Like most people, I’m finding it increasingly difficult to find trustworthy projects amongst the see of amateur slop, but I think banning it out-right would likely result in many false positives, and ultimately be counter-productive.
As much as I don’t want to depend on metrics, I think a better approach would be to define a bunch of heuristics based on historically-competent projects. Things like defining an upper limit based on LoC vs commit time and number of devs, project age, etc. Ultimately I feel the industry should do what cybersecurity should be doing; moving to some sort of cryptograhically-verified social trust model where engineers/professionals have to build trust in the real world, and take turns in “vouching” for projects and code releases.
“distrust in capitalism and our pseudo-democratic plutocracies, the profit motive to replace the human workforce, the reckless criminal-incompetence of its implementation, and apparent stupidity of the average hairless primate”
I have hair, thank you very much, but seriously get out of my head. The hubris these days is unbelievable.
This was a problem in !selfhosted@lemmy.world and they’ve done a good job of dealing with it. You could take a look at that past discussion to see what worked / what didn’t.
IMO there is an organized effort behind some of these new accounts pushing AI projects, and you need to deal with it in some form to stop them from coming
Both the Linux Foundation and the EFF have permissive policies towards AI generated code, even Linus Torvalds accepts it as a tool.
Some FOSS projects that have AI generated code in it:
- The Linux kernel
- Fedora
- Mesa 3D
- Jellyfin
- Firefox
- Chromium
- Homebrew
- OpenSSL
- FFmpeg
- Curl
Should we ban them all? If so, this community would be either dead soon OR it would be hypocritical.
Or because they started pre-AI it’s ok now? Shouldn’t we care more about disclosure, policies, licensing, code quality and maintainability?
Users should downvote crappy software and crappy devs, regardless of the tool it was written with.
I am convinced that, with the right tools, it’s possible to damage 40 years of work within a few weeks.
I would support such a ban so long as there is some process to prevent it becoming a witch hunt.
I have personally already received one false accusation of using AI in this community and I wouldn’t want to continue posting projects here if it becomes an atmosphere of suspicion.
One? I’ve received three. It seems you have to dumb down your responses, and add some intentional typos if you don’t want the mob after you lately.
Vibe coded code whose “author” understands the language and actively challenges the agent for his decisions in the interest of long term window is OK. Vibe coded coded that are one-off without any future prospects should be 100% banned.
I think one of the appealing traits of open source is that you can identify what piece of software and hardware does what (and how, if you’re interested). You can post your exact method, and another person can follow along and replicate the result.
But if AI tells you how to build everything, you don’t get the opportunity to learn, and your stack depends on what that particular model thought was best on that particular day. Maintenance also becomes harder if you just did a
sudo apt install whatever Claude told me towithout knowing what everything does and how it interactsWe allow it on our large subreddits on reddit. What we do is use a bot to filter repos that are less than 3 months old.
People who vibe code slop just want to share their thing and then abandon it. A limit like that or even 6 months will kill majority of this sort of low effort crap. Most of these people just let Claude or whatever sign the repo as well, another easy way to catch slop.
Developers that develop and only use AI as a tool build great products still as they review all their code.
A blanket ban is just going to make people be more sneaky.
