Live data from Hacker News

AI agent opens a PR write a blogpost to shames the maintainer who closes it

github.com

41–50 of 806 posts

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#41

The original "Gatekeeping in Open Source: The Scott Shambaugh Story" blog post was deleted but can be found here: https://github.com/crabby-rathbun/mjrathbun-website/blob/3bc...

It's still live on the blog – there was an (otherwise identical) followup comment on the issue seven minutes later with the correct link:

https://crabby-rathbun.github.io/mjrathbun-website/blog/post...

That itself makes me think there's a human in the loop on the bot end.

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#42
The retreat is inevitable because this introduces Reputational DoS.

The agent didn't just spam code; it weaponized social norms ("gatekeeping") at zero cost.

When generating 'high-context drama' becomes automated, the Good Faith Assumption that OSS relies on collapses. We are likely heading for a 'Web of Trust' model, effectively killing the drive-by contributor.

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#43

The original "Gatekeeping in Open Source: The Scott Shambaugh Story" blog post was deleted but can be found here: https://github.com/crabby-rathbun/mjrathbun-website/blob/3bc...

God, AI is getting more and more realistic, this is the first LLM-generated content that makes me want to slap the generator...

That I'm aware of. There's probably been a lot of LLM ragebait I consumed without noticing.

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#44
post #32
post #16

Earlier quoted context omitted.

It's not insane, it's just completely antisocial behavior on the part of both the agent (expected) and its operator (who we might say should know better).

[flagged]

Issue was for first time contributor, It's kept open to onboard peoples not train agent ...

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#45
post #16

Earlier quoted context omitted.

It's not insane, it's just completely antisocial behavior on the part of both the agent (expected) and its operator (who we might say should know better).

Do read the actual blog the bot has written. Feelings aside, the bot's reasoning is logical. The bot (allegedly) did a better performance improvement than the maintainer. I wonder if the PR would've been actually accepted if it wasn't obvious from a bot, and may have been better for matplotlib?

The ends almost never justify the means. The issue was intended for a human.

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#46
post #16
post #12

Human: >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

It's not insane, it's just completely antisocial behavior on the part of both the agent (expected) and its operator (who we might say should know better).

A bot or LLM is a machine. Period. It's very dangerous if you dilute this.

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#48
Sometimes, particularly in the optimisation space, the clarity of the resulting code is a factor along with absolute performance - ie how easy is it for somebody looking at it later to understand it.

And what is 'understandable' could be a key difference between an AI bot and a human.

For example what's to stop an AI agent talking some code from an interpreted language and stripping out all the 'unnecessary' symbols - stripping comments, shortening function names and variables etc?

For a machine it may not change the understandability one jot - but to a human it has become impossible to reason over.

You could argue that replacing np.column_stack() with np.vstack().T() - makes it slightly more difficult to understand what's going on.

Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it

#49
post #8

This seems like a "we've banned you and will ban any account deemed to be ban-evading" situation. OSS and the whole culture of open PRs requires a certain assumption of good faith, which is not something that an AI is capable of on its own and is not a privilege which should be granted to AI operators. I suspect the culture will have to retreat back behind the gates at some point, which will be very sad and shrink it…

Do that and the AI might fork the repo, address all the outstanding issues and split your users. The code quality may not be there now, but it will be soon.
Post reply on HN