Codeberg/Community
60
387
Fork
You've already forked Community
12

Please consider a project- and platform-wide policy against AI slop #2458

Open
opened 2026年03月15日 18:00:57 +01:00 by hsza · 16 comments

Comment

Codeberg should establish a project- and platform-wide policy against use of "AI" to generate code, text or media.

It's clear at this point that technology is a detriment to the long-term maintainability and quality of software projects, while otherwise raising many ethical concerns, being developed by coporations that back war crimes, from data scraped without consent, at the expense of website operators and to the detriment of the enviroment, then serving to bury the web under mountains of soulless generated "content", delude audiences and deskill workers while attempting to devalue geniune labor.

Now is a time as good as any to take a clear political stance against it, ideally banning slop contributions from across the platform entirely.

### Comment Codeberg should establish a project- and platform-wide policy against use of "AI" to generate code, text or media. It's clear at this point that technology is a detriment to the long-term maintainability and quality of software projects, while otherwise raising many ethical concerns, being developed by coporations that back war crimes, from data scraped without consent, at the expense of website operators and to the detriment of the enviroment, then serving to bury the web under mountains of soulless generated "content", delude audiences and deskill workers while attempting to devalue geniune labor. Now is a time as good as any to take a clear political stance against it, ideally banning slop contributions from across the platform entirely.

I will prematurely point to #2184 (comment) - just like for the cryptocurrency stuff, go find a Codeberg e.V. member and get them to propose a vote on this so it actually can happen. I will point some e.V. members at this issue which might be interesting in taking this on.

I will prematurely point to https://codeberg.org/Codeberg/Community/issues/2184#issuecomment-7905679 - just like for the cryptocurrency stuff, go find a Codeberg e.V. member and get them to propose a vote on this so it actually can happen. I will point some e.V. members at this issue which might be interesting in taking this on.
Author
Copy link

@Gusted wrote in #2458 (comment):

I will prematurely point to #2184 (comment) - just like for the cryptocurrency stuff, go find a Codeberg e.V. member and get them to propose a vote on this so it actually can happen. I will point some e.V. members at this issue which might be interesting in taking this on.

thank you! from a quick look around, I don't think there's a public list of e.V. members anywhere out there? and I've no existing contacts with any. so, again, thanks for bringing this up internally, i appreciate it!

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2458#issuecomment-11674611: > I will prematurely point to #2184 (comment) - just like for the cryptocurrency stuff, go find a Codeberg e.V. member and get them to propose a vote on this so it actually can happen. I will point some e.V. members at this issue which might be interesting in taking this on. thank you! from a quick look around, I don't think there's a public list of e.V. members anywhere out there? and I've no existing contacts with any. so, again, thanks for bringing this up internally, i appreciate it!

@hsza wrote in #2458 (comment):

@Gusted wrote in #2458 (comment):

I will prematurely point to #2184 (comment) - just like for the cryptocurrency stuff, go find a Codeberg e.V. member and get them to propose a vote on this so it actually can happen. I will point some e.V. members at this issue which might be interesting in taking this on.

thank you! from a quick look around, I don't think there's a public list of e.V. members anywhere out there? and I've no existing contacts with any. so, again, thanks for bringing this up internally, i appreciate it!

I also don't see any information on https://join.codeberg.org about the minutes the members keep (https://codeberg.org/Codeberg/org/src/branch/main/en/bylaws.md), so maybe those are also private? I wonder if there is any other way to know whether an issue is being discussed and where it stands.

@hsza wrote in https://codeberg.org/Codeberg/Community/issues/2458#issuecomment-11674812: > @Gusted wrote in #2458 (comment): > > > I will prematurely point to #2184 (comment) - just like for the cryptocurrency stuff, go find a Codeberg e.V. member and get them to propose a vote on this so it actually can happen. I will point some e.V. members at this issue which might be interesting in taking this on. > > thank you! from a quick look around, I don't think there's a public list of e.V. members anywhere out there? and I've no existing contacts with any. so, again, thanks for bringing this up internally, i appreciate it! I also don't see any information on https://join.codeberg.org about the minutes the members keep (https://codeberg.org/Codeberg/org/src/branch/main/en/bylaws.md), so maybe those are also private? I wonder if there is any other way to know whether an issue is being discussed and where it stands.

The notes of the annual assembly of the association are indeed not public, but summaries are released on the blog, e.g. for 2025.

Generally, I'd when it comes to shaping the policies of Codeberg, it's probably easiest to become a member, as that way you get access to the internal organisational repos etc. where people work together on preparing motions to bring to the annual member assembly.

In case that's a perceived blocker: Membership in the association isn't limited to Germans/Europeans (afair, only some elected roles that come with particular legal responsibilities are limited due to the way German association law works).

The notes of the annual assembly of the association are indeed not public, but summaries are released on the blog, e.g. [for 2025](https://blog.codeberg.org/letter-from-codeberg-onwards-and-upwards.html). Generally, I'd when it comes to shaping the policies of Codeberg, it's probably easiest to become a member, as that way you get access to the internal organisational repos etc. where people work together on preparing motions to bring to the annual member assembly. In case that's a perceived blocker: Membership in the association isn't limited to Germans/Europeans (afair, only some elected roles that come with particular legal responsibilities are limited due to the way German association law works).

I would argue there is a nontrivial subset of people who are not willing to become a member but would like to be informed on what policies are being actively discussed/decided upon. I'm sure there is a good reason why Codeberg has decided to not cater to this group, but I cannot think of one. In any case, I am very grateful that Codeberg exists in the first place.

I would argue there is a nontrivial subset of people who are not willing to become a member but would like to be informed on what policies are being actively discussed/decided upon. I'm sure there is a good reason why Codeberg has decided to not cater to this group, but I cannot think of one. In any case, I am very grateful that Codeberg exists in the first place.
Author
Copy link

@ethanuppal wrote in #2458 (comment):

I would argue there is a nontrivial subset of people who are not willing to become a member but would like to be informed on what policies are being actively discussed/decided upon. I'm sure there is a good reason why Codeberg has decided to not cater to this group, but I cannot think of one. In any case, I am very grateful that Codeberg exists in the first place.

^^ what's the reason for the association to be so opaque?

@ethanuppal wrote in https://codeberg.org/Codeberg/Community/issues/2458#issuecomment-11769204: > I would argue there is a nontrivial subset of people who are not willing to become a member but would like to be informed on what policies are being actively discussed/decided upon. I'm sure there is a good reason why Codeberg has decided to not cater to this group, but I cannot think of one. In any case, I am very grateful that Codeberg exists in the first place. ^^ what's the reason for the association to be so opaque?

I can't speak for the eV officially, but: As for virtually all volunteer-driven associations, there's orders of magnitude more work than there are volunteers to do all the work, and as such efforts need to be prioritized. Given the current balance of work/volunteers, it mostly means that there's no resources to do extra effort to regularly push out information about discussions beyond the outputs that were voted on.

But starting at 12€/year you can join to get the privilege to volunteer your time to change that 😉

I can't speak for the eV officially, but: As for virtually all volunteer-driven associations, there's orders of magnitude more work than there are volunteers to do all the work, and as such efforts need to be prioritized. Given the current balance of work/volunteers, it mostly means that there's no resources to do extra effort to regularly push out information about discussions beyond the outputs that were voted on. But starting at 12€/year you can join to get the privilege to volunteer your time to change that 😉
Author
Copy link

why are the discussions not held out in the open in the first place?

why are the discussions not held out in the open in the first place?

before I start: i'm a member of the Presidium and I'd support restricting AI slop (i'm using "restricting" instead of "banning" because the "where the red line is and how is that red line is unambiguously defined" is still a topic to be determined).

You must only share content on Codeberg which you have the explicit right under copyright and other laws to share under the legal terms with which the content is made available on Codeberg.


why are the discussions not held out in the open in the first place?

but: why can you not read stephen king's draft manuscript for a new book? why can you not read a lawmaker's law the minute they start writing the first sentence in their word processor? we can philosophize about radical transparency and direct democracy and where the line is, but, depending on who you ask, one might say "it's ready when it's ready" and nothing is official before they are made official, and also: it depends on volunteer availability.

i think it's the first "official" (as in, visible, no "backchannel" talk) discussion that is being held that directly asks the question you asked, and it's a public one. it's an active topic of consideration; this was something that was disclosed fifteen minutes after you opened the issue. we can be opaque (sometimes more often than i'd like, but i'm working on it), but i don't think we're that opaque. we're currently working on improving our transparency in certain key areas such as finances (after a motion that passed, of which i was one of the people to put forward) and that takes a lot of resources, but we think it's going to be worth it.

terms of use changes and privacy policy changes are deemed as policies of the non-profit, and are voted for by the members per the bylaws. many of which said "i'll join codeberg" because they disliked copilot, btw. but even if this is "members' only"-type of business "officially", pull requests tend to be published under https://codeberg.org/Codeberg/org after they reach an advanced stage. but it's not like there is one singular group that knows everything and one that doesn't. even within the association itself, certain folks often opt to make working groups; as in, working with others towards a common result, then presenting them to the one thousand three hundred (1300) members (sometimes making public PRs), reaching consensus, getting it passed, finally communicating that to everyone... in other words: they first get something that is "ready" enough so that it's not "torn apart" during very early stages (either through bikeshedding or drive-by comments by people that are absolutely disinterested in meaningfully engaging with the process, keep reading). it's somewhat similar to lawmaking. we don't have something that is ready enough right now to show, just talk. people can also form proposals with others without me (or any of the presidium/board members) knowing about it until they feel ready putting them forward, and i think that's ok.

following a process can be very important so that people don't get overwhelmed early on or derailed by external pressure before any meaningful work happens (after all, there aren't many steps required for a democracy to turn into an ochlocracy - but there are also downsides to this, see next paragraph*), resulting in nothing happening (and merely trying to apply transparency is not a panacea for a lack of process): as there was no process when someone proposed that cryptocurrency should get banned when NFTs were still a popular grift, it got bikeshedded to death by people that had, let's say, "no skin in the game". that led to nobody doing anything about it. which kinda sucked. on the other hand, having e.g. concentrated groups work on proposals and get them gradually approved in stages and then presented to the public has worked for e.g. the recent ToU update. but that is not something that is set in stone: you are also more than free to propose a change yourself (e.g. to https://codeberg.org/Codeberg/org) and other members can take that into consideration, but it might succeed (or be used as a basis for another proposal) or it might not.

transparency is a medium that helps people make educated decisions. for example, with finances, it is important for us to be transparent about them so that people can make an educated decision as to whether they should donate, whether they're happy about how we're dealing with money, or whether they should use their money for something else something else. same principle applies to policies (for example, when choosing to move to codeberg). i hope it is understood that transparency in the context of very early discussions towards a group that does not actively have skin in the game (in the sense of being able to decide over policies) has lower priority. although i acknowledge that this might limit participation potential (whether that's more good than bad, as described above, i am not sure about it*), trying to tackle such problems from all angles is something that needs people. although @gedankenstuecke already tried to make a similar offer, i'll try again: if you want to show up and help us make this a better bastion that is unlike the hyperconsumerist internet of today, i'd be happy to help guide you ("member" or not; although non-profit policies are normally worked on by people participating in the non-profit). however: if you want to say "why something isn't happening the way i want it to", the answer is very often "because there's not enough people" or "they're focusing on something else" (such as creating a good proposal).

anyway, the time explaining this could've been spent into making a good, human-first proposal (that people will be pleased with, which won't 'bite us' at a later point in time), but i thought that providing a thoughtful explanation of the way i see these things might be enlightening. keep in mind that all of these are personal opinions.

before I start: i'm a member of the Presidium and I'd support restricting AI slop (i'm using "restricting" instead of "banning" because the "where the red line is and how is that red line is unambiguously defined" is still a topic to be determined). > You must only share content on Codeberg which you have the explicit right under copyright and other laws to share under the legal terms with which the content is made available on Codeberg. --- > why are the discussions not held out in the open in the first place? but: why can you not read stephen king's draft manuscript for a new book? why can you not read a lawmaker's law the minute they start writing the first sentence in their word processor? we can philosophize about radical transparency and direct democracy and where the line is, but, depending on who you ask, one might say "it's ready when it's ready" and nothing is official before they are made official, and also: it depends on volunteer availability. i think it's the first "official" (as in, visible, no "backchannel" talk) discussion that is being held that directly asks the question you asked, and it's a public one. it's an active topic of consideration; this was something that was disclosed fifteen minutes after you opened the issue. we can be *opaque* (sometimes more often than i'd like, but i'm working on it), but i don't think we're *that* opaque. we're currently working on improving our transparency in certain key areas such as finances (after a motion that passed, of which i was one of the people to put forward) and that takes a lot of resources, but we think it's going to be worth it. terms of use changes and privacy policy changes are deemed as policies of the non-profit, and are voted for by the members per the bylaws. many of which said "i'll join codeberg" because they disliked copilot, btw. but even if this is "members' only"-type of business "officially", pull requests tend to be published under https://codeberg.org/Codeberg/org after they reach an advanced stage. but it's not like there is one singular group that knows everything and one that doesn't. even within the association itself, certain folks often opt to make working groups; as in, working with others towards a common result, *then* presenting them to the one thousand three hundred (1300) members (sometimes making public PRs), reaching consensus, getting it passed, finally communicating that to everyone... in other words: they first get something that is "ready" enough so that it's not "torn apart" during very early stages (either through bikeshedding or drive-by comments by people that are absolutely disinterested in meaningfully engaging with the process, keep reading). it's somewhat similar to lawmaking. we don't have something that is ready enough right now to show, just talk. people can also form proposals with others without me (or any of the presidium/board members) knowing about it until they feel ready putting them forward, and i think that's ok. following a process *can be* very important so that people don't get overwhelmed early on or derailed by external pressure before any meaningful work happens (after all, there aren't many steps required for a democracy to turn into an ochlocracy - but there are also downsides to this, see next paragraph`*`), resulting in nothing happening (and merely trying to apply transparency is not a panacea for a lack of process): as there was no process when someone proposed that cryptocurrency should get banned when NFTs were still a popular grift, it got bikeshedded to death by people that had, let's say, "no skin in the game". that led to nobody doing anything about it. which kinda sucked. on the other hand, having e.g. concentrated groups work on proposals and get them gradually approved in stages and then presented to the public has worked for e.g. the recent ToU update. but that is *not* something that is set in stone: you are also more than free to propose a change yourself (e.g. to https://codeberg.org/Codeberg/org) and other members can take that into consideration, but it might succeed (or be used as a basis for another proposal) or it might not. transparency is a medium that helps people make educated decisions. for example, with finances, it is important for us to be transparent about them so that people can make an educated decision as to whether they should donate, whether they're happy about how we're dealing with money, or whether they should use their money for something else something else. same principle applies to policies (for example, when choosing to move to codeberg). i hope it is understood that transparency in the context of *very early discussions* towards a group that does not actively have skin in the game (in the sense of being able to decide over policies) has lower priority. although i acknowledge that this might limit participation potential (whether that's more good than bad, as described above, i am not sure about it`*`), trying to tackle such problems from all angles is something that needs people. although @gedankenstuecke already tried to make a similar offer, i'll try again: if you want to show up and help us make this a better bastion that is unlike the hyperconsumerist internet of today, i'd be happy to help guide you ("member" or not; although non-profit policies are normally worked on by people participating in the non-profit). however: if you want to say "why something isn't happening the way i want it to", the answer is very often "because there's not enough people" or "they're focusing on something else" (such as creating a good proposal). anyway, the time explaining this could've been spent into making a good, human-first proposal (that people will be pleased with, which won't 'bite us' at a later point in time), but i thought that providing a thoughtful explanation of the way i see these things might be enlightening. keep in mind that all of these are personal opinions.
Author
Copy link

thanks for the insight! and yeah, making a proposal would've been a better use of that time, but i appreciate the explanation

thanks for the insight! and yeah, making a proposal would've been a better use of that time, but i appreciate the explanation

I was a bit concerned that the volume might overwhelm but decided to just go for it anyway (sunken cost fallacy), glad it didn't. Sometimes, I write long texts so that I can back-reference them if questions of similar nature are asked in the future anyway; didn't mean to come across as passive aggressive.

I was a bit concerned that the volume might overwhelm but decided to just go for it anyway (sunken cost fallacy), glad it didn't. Sometimes, I write long texts so that I can back-reference them if questions of similar nature are asked in the future anyway; didn't mean to come across as passive aggressive.

I'm not really sure what the problem is I think this falls down to another case of minding your own business If you're writing good apps and good code then people are going to choose your apps so I'm not sure exactly what you're getting at. Consider the purpose of a repository I mean there are repositories that don't even have an intent of releasing code It's just a personal project but in any case I don't see where it matters really to anybody who wrote the code as long as the code works and does what it's supposed to do I mean there are people out there that don't use AI but all they do through the entire project is copy snippets off the web until they put something together The code either works or it doesn't It doesn't matter how it got there that's the bottom line. Next thing you know people will want to ban code that was written by people with magnifying glasses on We should probably ban large type too and high contrast as well because the Lord help anyone that might need a little bit of help we certainly can't have them functioning in this great world of ours.

I'm not really sure what the problem is I think this falls down to another case of minding your own business If you're writing good apps and good code then people are going to choose your apps so I'm not sure exactly what you're getting at. Consider the purpose of a repository I mean there are repositories that don't even have an intent of releasing code It's just a personal project but in any case I don't see where it matters really to anybody who wrote the code as long as the code works and does what it's supposed to do I mean there are people out there that don't use AI but all they do through the entire project is copy snippets off the web until they put something together The code either works or it doesn't It doesn't matter how it got there that's the bottom line. Next thing you know people will want to ban code that was written by people with magnifying glasses on We should probably ban large type too and high contrast as well because the Lord help anyone that might need a little bit of help we certainly can't have them functioning in this great world of ours.

There is currently an official Codeberg association member’s voting ongoing concerning this question for disallowing AI slop in Codeberg’s Terms of Use. Thus, there will be an official update on this topic soon! Stay tuned ;)

There is currently an official Codeberg association member’s voting ongoing concerning this question for disallowing AI slop in Codeberg’s Terms of Use. Thus, there will be an official update on this topic soon! Stay tuned ;)
Author
Copy link

@callihn wrote in #2458 (comment):

I'm not really sure what the problem is I think this falls down to another case of minding your own business If you're writing good apps and good code then people are going to choose your apps so I'm not sure exactly what you're getting at. Consider the purpose of a repository I mean there are repositories that don't even have an intent of releasing code It's just a personal project but in any case I don't see where it matters really to anybody who wrote the code as long as the code works and does what it's supposed to do I mean there are people out there that don't use AI but all they do through the entire project is copy snippets off the web until they put something together The code either works or it doesn't It doesn't matter how it got there that's the bottom line. Next thing you know people will want to ban code that was written by people with magnifying glasses on We should probably ban large type too and high contrast as well because the Lord help anyone that might need a little bit of help we certainly can't have them functioning in this great world of ours.

taking an unapologetially political stance against a fascist (on many fronts) technology is the right thing to do. do not refer to it as a neutral means to an end, it is not "just a tool", allowing it is as much of a statement as banning it.

banning generative ai sends a message that a project values people's authentic labor and the learning and quality that come with it. allowing it is the polar opposite and a sign of ethical rot. i am not speculating, the effects of each choice are well-known by now. it is a very simple matter of picking a side between good and evil, and maybe it is proponents of evil that need to mind their own business. so let's show sloperators the door!!

@callihn wrote in https://codeberg.org/Codeberg/Community/issues/2458#issuecomment-18894527: > I'm not really sure what the problem is I think this falls down to another case of minding your own business If you're writing good apps and good code then people are going to choose your apps so I'm not sure exactly what you're getting at. Consider the purpose of a repository I mean there are repositories that don't even have an intent of releasing code It's just a personal project but in any case I don't see where it matters really to anybody who wrote the code as long as the code works and does what it's supposed to do I mean there are people out there that don't use AI but all they do through the entire project is copy snippets off the web until they put something together The code either works or it doesn't It doesn't matter how it got there that's the bottom line. Next thing you know people will want to ban code that was written by people with magnifying glasses on We should probably ban large type too and high contrast as well because the Lord help anyone that might need a little bit of help we certainly can't have them functioning in this great world of ours. taking an unapologetially political stance against a fascist (on many fronts) technology is the right thing to do. do not refer to it as a neutral means to an end, it is not "just a tool", allowing it is as much of a statement as banning it. banning generative ai sends a message that a project values people's authentic labor and the learning and quality that come with it. allowing it is the polar opposite and a sign of ethical rot. i am not speculating, the effects of each choice are well-known by now. it is a very simple matter of picking a side between good and evil, and maybe it is proponents of evil that need to mind their own business. so let's show sloperators the door!!

@hsza wrote in #2458 (comment):

@callihn wrote in #2458 (comment):

I'm not really sure what the problem is I think this falls down to another case of minding your own business If you're writing good apps and good code then people are going to choose your apps so I'm not sure exactly what you're getting at. Consider the purpose of a repository I mean there are repositories that don't even have an intent of releasing code It's just a personal project but in any case I don't see where it matters really to anybody who wrote the code as long as the code works and does what it's supposed to do I mean there are people out there that don't use AI but all they do through the entire project is copy snippets off the web until they put something together The code either works or it doesn't It doesn't matter how it got there that's the bottom line. Next thing you know people will want to ban code that was written by people with magnifying glasses on We should probably ban large type too and high contrast as well because the Lord help anyone that might need a little bit of help we certainly can't have them functioning in this great world of ours.

taking an unapologetially political stance against a fascist (on many fronts) technology is the right thing to do. do not refer to it as a neutral means to an end, it is not "just a tool", allowing it is as much of a statement as banning it.

banning generative ai sends a message that a project values people's authentic labor and the learning and quality that come with it. allowing it is the polar opposite and a sign of ethical rot. i am not speculating, the effects of each choice are well-known by now. it is a very simple matter of picking a side between good and evil, and maybe it is proponents of evil that need to mind their own business. so let's show sloperators the door!!

I don't think there's anything evil about using a tool someone that would think such a thing would be someone that I would view as a person that apparently thinks that they know everything everybody doesn't have a human team everybody doesn't have a human that they can go to and say man I can't figure out why this code doesn't work I keep checking the docs It's supposed to work it's supposed to do this but it's just not working and get help everybody doesn't have someone that's going to say oh well you know why don't you try using this instead it'll give you the same effect and it'll work. Honestly I question the coding ability of someone who is afraid of it there I said it. It's simply a matter of just don't use it if it writes apps you don't like don't run them If we want to talk about wasted space we have to look at all the slop that humans right too and we have to ban slop. So if you have a public or even a private repository on here and all you have in it is worth a slop broken code non-running code then what's the difference?

Edit: Speaking of slob text to speech falls under that category a lot of times are we going to ban that to?

Attention everyone in the future all text must be typed All keys on the keyboard will have upward facing razor sharp thorns and users must bleed to communicate. No no If you want to write something from now on you need to get a stone and a chisel.

So here's the thing let's just get it out of the way let's just pull the curtain back okay I've got three apps that I wrote and the reason I wrote them is because everything else that does it either doesn't exist is broken and or cost too much, I feel such applications can benefit other people along with myself I'm not really charging for it though there is an option for a user to donate through the app if they like and it would be much appreciated but I used AI to help me with it especially every time I got stuck and using it enabled me to do it much faster but it's not simply you just tell it hey make me this app you have to play the project manager you have to play quality control so a number of skills are being learned by using someone else or something else to do it And because it's not perfect you're going to have to figure out a lot of things yourself which means you're going to have to learn you're going to have to see the way it done things you're going to have to do some research and figure out why it's not working because it can't fix it that's all it knows. So then you're saying I shouldn't share it with the world is what you're saying because I had to have a little help. You seem to think that I can just fire up AI and say hey I want you to write me a weather app and I'm going to have it done in like 10 minutes It doesn't work that way It's considerably faster particularly if you have it do parallel rights however you get particularly more bugs like that so it's not advisable It might cut the time down in half I think well considering all the errors I make when I type maybe even better than that.

@hsza wrote in https://codeberg.org/Codeberg/Community/issues/2458#issuecomment-18897593: > @callihn wrote in #2458 (comment): > > > I'm not really sure what the problem is I think this falls down to another case of minding your own business If you're writing good apps and good code then people are going to choose your apps so I'm not sure exactly what you're getting at. Consider the purpose of a repository I mean there are repositories that don't even have an intent of releasing code It's just a personal project but in any case I don't see where it matters really to anybody who wrote the code as long as the code works and does what it's supposed to do I mean there are people out there that don't use AI but all they do through the entire project is copy snippets off the web until they put something together The code either works or it doesn't It doesn't matter how it got there that's the bottom line. Next thing you know people will want to ban code that was written by people with magnifying glasses on We should probably ban large type too and high contrast as well because the Lord help anyone that might need a little bit of help we certainly can't have them functioning in this great world of ours. > > taking an unapologetially political stance against a fascist (on many fronts) technology is the right thing to do. do not refer to it as a neutral means to an end, it is not "just a tool", allowing it is as much of a statement as banning it. > > banning generative ai sends a message that a project values people's authentic labor and the learning and quality that come with it. allowing it is the polar opposite and a sign of ethical rot. i am not speculating, the effects of each choice are well-known by now. it is a very simple matter of picking a side between good and evil, and maybe it is proponents of evil that need to mind their own business. so let's show sloperators the door!! I don't think there's anything evil about using a tool someone that would think such a thing would be someone that I would view as a person that apparently thinks that they know everything everybody doesn't have a human team everybody doesn't have a human that they can go to and say man I can't figure out why this code doesn't work I keep checking the docs It's supposed to work it's supposed to do this but it's just not working and get help everybody doesn't have someone that's going to say oh well you know why don't you try using this instead it'll give you the same effect and it'll work. Honestly I question the coding ability of someone who is afraid of it there I said it. It's simply a matter of just don't use it if it writes apps you don't like don't run them If we want to talk about wasted space we have to look at all the slop that humans right too and we have to ban slop. So if you have a public or even a private repository on here and all you have in it is worth a slop broken code non-running code then what's the difference? Edit: Speaking of slob text to speech falls under that category a lot of times are we going to ban that to? Attention everyone in the future all text must be typed All keys on the keyboard will have upward facing razor sharp thorns and users must bleed to communicate. No no If you want to write something from now on you need to get a stone and a chisel. So here's the thing let's just get it out of the way let's just pull the curtain back okay I've got three apps that I wrote and the reason I wrote them is because everything else that does it either doesn't exist is broken and or cost too much, I feel such applications can benefit other people along with myself I'm not really charging for it though there is an option for a user to donate through the app if they like and it would be much appreciated but I used AI to help me with it especially every time I got stuck and using it enabled me to do it much faster but it's not simply you just tell it hey make me this app you have to play the project manager you have to play quality control so a number of skills are being learned by using someone else or something else to do it And because it's not perfect you're going to have to figure out a lot of things yourself which means you're going to have to learn you're going to have to see the way it done things you're going to have to do some research and figure out why it's not working because it can't fix it that's all it knows. So then you're saying I shouldn't share it with the world is what you're saying because I had to have a little help. You seem to think that I can just fire up AI and say hey I want you to write me a weather app and I'm going to have it done in like 10 minutes It doesn't work that way It's considerably faster particularly if you have it do parallel rights however you get particularly more bugs like that so it's not advisable It might cut the time down in half I think well considering all the errors I make when I type maybe even better than that.

@mahlzahn wrote in #2458 (comment):

There is currently an official Codeberg association member’s voting ongoing concerning this question for disallowing AI slop in Codeberg’s Terms of Use. Thus, there will be an official update on this topic soon! Stay tuned ;)

I'm sorry, but there's nothing to discuss here for non-e.V. members. As I've the feeling this will get heated and possibly having to moderate this discussion: Locked till this vote is over and there's a result to share.

@mahlzahn wrote in https://codeberg.org/Codeberg/Community/issues/2458#issuecomment-18894662: > There is currently an official Codeberg association member’s voting ongoing concerning this question for disallowing AI slop in Codeberg’s Terms of Use. Thus, there will be an official update on this topic soon! Stay tuned ;) I'm sorry, but there's nothing to discuss here for non-e.V. members. As I've the feeling this will get heated and possibly having to moderate this discussion: Locked till this vote is over and there's a result to share.
Gusted locked and limited conversation to collaborators 2026年07月09日 23:26:56 +02:00
This discussion has been locked. Commenting is limited to contributors.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2458
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?