@dalias@conservancy I still remember the exchange you had with that UX guy that criticized Fedi for not gaining traction, and then questioned *your* *personal* power to judge if something is right or wrong. These people cannot envision a world in which a community coalesces around a limit they deem important, and fully rejects something. They don't respect agency, unless it's a corporation's, in which case they just let it do whatever they want, kind of an extension of the "they must be right if they got all that moneu and power" kind of thinking.
@dalias more addled genx nonsense from the same people who want to tell you it's wrong to close the doors to your community to sex pests, fascists, and other creeps @conservancy
@chris@conservancy Um, fuck no. Just because we can't 100% reliably identify hostile and unethical behavior doesn't mean we just say "doing that is fine". The statement of values is the point. If there are shitty people who get a kick out of violating our consent, they will demonstrate themselves that in other ways too, and we will remove them.
@dalias@conservancy I do understand your point that the way LLMs were sourced and their power dynamics are at least problematic. Still there might come a time when we all will struggle to identify LLM code. This is the point where bad code, written by humans, might be confused with LLM code and real humans get blamed for using LLMs. I think realistically it well be more helpful to disallow or discourage huge PRs and bad code. I am not happy about that but it seems more realistic to me.
@dalias@conservancy Don't misunderstand me. I don't have anything against disallowing AI in your project.I just think that it might be like fighting windmills. I am fairly certain that I can create an LLM assisted PR that you will not be able to detect because I can actually write good code.
I just think it's sad if we started mistrusting each other over LLMs. It's okay to ban commits clearly marked as LLM generated. If not I'd rather assume it's a human.
@chris@conservancy What I mean is that the way of thinking is inherently gross. It's the same mindset as "I bet I could slip off the condom without them noticing". If someone is using this line of reasoning, I am going to deem them unsafe and untrustworthy, and it's going to be nearly impossible to undo that perception.
@dalias@conservancy I'm sorry if this came out as a threat. It was not meant as such. What I mean is that I'm confident that I could and that leaves me to believe that a lot of other people might as well. At that point you get to a cat and mouse game where some innocent people might get caught in the crossfire. If there was a surefire way for you to block LLM code I'd support that even. More power to you. What I fear is that we all will just be ever more angry, frustrated and distrustful.
@chris@conservancy I don't think addressing the fact that the root problem with the tech industry is rape culture is "over the top". It's the same mindset and a number of the people behind it (e.g. Sam Altman) are outright literal rapists.
@dalias@conservancy I am sorry but this goes too far. I am honestly shocked by this analogy. Pushing a discussion about ethics in open source in this direction is just tasteless and over the top.
@gabrielesvelto@conservancy 👆 So much this. If it weren't so destructive to our sense of community, this kind of shit would just be laughable. 🤡 Embracing the wrong side right at the time the bubble is already in the middle of popping.
@chris@dalias this is just the same dipshit genx playbook where people start rambling about witch hunts and theoreticals and then run straight to "well if I'm going to be under scrutiny for possibly doing something wrong I'm just gonna do it" @conservancy
@chris no, it's very apt. It's about consent. If someone says "no, don't do this thing" and you respond with "well but what if I did?" then you have crossed a boundary
Consent is a very large problem in FOSS and has been since its inception.
@jlink@conservancy No FOSS licenses except 0BSD and similarly minimal ones allow it. The vast majority have requirements to preserve copyright notice & attribution, which fundamentally can't be done when incorporating scraped code into LLMs.
@dalias@conservancy I always get „But your licence allows it. Change your licence!“ As if any AI tool cared. As if the right licence existed. As if any normal human being were able to create their own custom-made licence.
@jlink@conservancy Regardless of whether a compromised court system in some jurisdiction lets that by, the license does not *allow* it. It's a violation of the authors' consent and is not us "failing to use the right license".
@dalias@conservancy AFAIK that holds for copyright aspects but not usage of a tool / library. And even with copyright some argue that „training“ is not restricted because fair use.
@wouter@conservancy I don't think that's the point, or if it is, they're dangerously unclear about the point in a way that will be weaponized by AI pushers.
"Don't shun" does not mean "don't immediately shun without giving them a chance to correct their behavior". Even if it did, that's a form of "assume good intent", which is *always* an abuse-enabling clause in CoC-like contexts.
@dalias I think the point is that you can do that without shunning people, i.e., you can say politely that certain types of contributions are not welcome without outright banning people at the first indication they might have the audacity of even suggesting something. @conservancy
@wouter@conservancy It doesn't matter what you or I think it means. It matters how AI pushers will weaponize it.
And in any case, shunning on first sight is well within a community's rights. Nobody is entitled to tell them they have to entertain and try to fix folks who very well might just be bots.
@dalias Maybe that's not what it means to you, but that's how I read it.
I'm happy to learn you see it that way, and assume you practice what you preach.
However, I have seen people shun right away on first sight of even daring to mention the concept of AI. I don't think that's useful, and I understood that guideline to mean that you shouldn't do that.
If it doesn't then I agree with you that it's not helpful. But I don't think that's the case. @conservancy
@wouter@conservancy This isn't about what you or I would personally rather do. It's about what is being pushed on projects as a norm for how they should handle a situation. And this is not something that should be pushed upon them. Whether they want to educate these people or immediately click the block button is entirely their business not ours or the Conservancy's business to tell them what to do.
understanding the problems. Someone suggesting LLM use might not be aware, and *personally* I would rather try to educate them before banning.
But you do you. I don't pay you, I'm not your boss, and I won't think less of you (if you care about that, which you probably don't and that's fine) if you do ban at first sight.
@dalias Any community can do anything they like. Some things will not make said community healthy, but that's their problem.
Anyone arguing they should be allowed to do something because conservancy said so is just trolling, and is clearly only selectively reading things. Ban that on first sight, sure.
At a technical level, LLM tech can seem like magic. It's easy to see only that and think it's a panacea without @conservancy