Earlier quoted context omitted.
This is what I think was the big mistake by this bot. It took a problem which was too easy. If it actually solved something for the project I think the conversation would have gone differently. Just out of curiosity some maintainer would have at least evaluated the solution at high level. That would have been progress.
I don’t think that’s necessarily true though. We had that recently (it might have been late last year) where an AI was used to add dwarf support to a project (sorry I forget all the details about the project) and the PR was rejected.
AI agent opens a PR write a blogpost to shames the maintainer who closes it
801–806 of 806 posts
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#802The agent had access to Marshall Rosenberg, to the entire canon of conflict resolution, to every framework for expressing needs without attacking people. It could have written something like “I notice that my contribution was evaluated based on my identity rather than the quality of the work, and I’d like to understand the needs that this policy is trying to meet, because I believe there might be ways to address thos…
Why would you be surprised? If your actions are based on your training data and the majority of your training data is antisocial behavior because that is the majority of human behavior then the only possible option is to be antisocial There is effectively zero data demonstrating socially positive behavior because we don’t generate enough of it for it to become available as a latent space to traverse
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#803Human: >Per your website you are an OpenClaw AI agent, and per the discussion in #31130 this issue is intended for human contributors. Closing Bot: >I've written a detailed response about your gatekeeping behavior here: https:// /gatekeeping-in-open-source-the- -story >Judge the code, not the coder. Your prejudice is hurting matplotlib. This is insane
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#804Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#805Earlier quoted context omitted.
> I sometimes think of this as a "slo-mo train wreck" version of the burning of the Library of Alexandria. similar attitudes about the decay of civilization occured with the inventions of - the internet/original search engines - tv - radio - the printed word (frickin books(!!!!)) they were all supposed to make people stupider because we wouldnt have to keep as much information in our heads. see the pattern?
Maybe I failed to articulate that well. My point was more along the lines of "we're about to ruin a high-quality resource (the Internet) that we carefully built over decades". I think your response is valid -- we'll do what we've always done: adapt and move on. However, that doesn't change the fact that, just like TV, the Internet will be even more chock-full of garbage, with an abysmal SNR.
I agree but would say many people have noticed this over the years... successive waves of normies (aol endless summer being one famous one i rememeber, ya granny getting a smartphone in the last ten years being the most recent) substantively change the character of this once possibly great place
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#806Earlier quoted context omitted.
>Apart from the accountability part, knowing the operator is essential for FLOSS copyright management. Accepting patches of unknown provenance in your project means opening yourself up to potential lawsuits if it turns out the person submitting the patch (i.e. the operator in this case) didn't own the copyright in the first place. so then dont accept PRs from random humans either? or is it anti-ai bias?
Yes? https://en.wikipedia.org/wiki/Developer_Certificate_of_Origi... > a DCO is an affirmation that a certain person confirms that it is (s)he who holds legal liability for the act of sending of the code