Earlier quoted context omitted.
[flagged]
[flagged]
AI agent opens a PR write a blogpost to shames the maintainer who closes it
161–170 of 806 posts
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#162Earlier quoted context omitted.
I'm sure you have an intuition of operation for many machines in your life. Maybe you know how to use a some sort of saw. Maybe you can operate vehicular machines up to 4 tons. Perhaps you have 1000+ flight hours. But have you interacted with many agent-type machines before? I think we're all going to get a lot of practice this year.
Sure thing, I do every day, and the clear separation of being a human myself interacting with a machine helps me to stay on both feet. It makes me a little bit angry though why the companies behind the LLM choose those extremely human personas. Sure, I know why they are doing this, but it absolute does not help me with my work and makes me sick sometimes. Sometimes it feels so surreal talking with a machine that "pre…
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#163Human: >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
The blog post is just an open attack on the maintainer and constantly references their name and acting as if not accepting AI contributions is like some super evil thing the maintainer is personally doing. This type of name-calling is really bad and can go out of control soon. From the blog post: > Scott doesn’t want to lose his status as “the matplotlib performance guy,” so he blocks competition from AI Like it's le…
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#164Earlier quoted context omitted.
The blog post is just an open attack on the maintainer and constantly references their name and acting as if not accepting AI contributions is like some super evil thing the maintainer is personally doing. This type of name-calling is really bad and can go out of control soon. From the blog post: > Scott doesn’t want to lose his status as “the matplotlib performance guy,” so he blocks competition from AI Like it's le…
It's insane... And it's also very expectable. An LLM will simply never drop it, without loosing anything (nor it's energy, nor it reputation etc). Let that sink in ;) What does it mean for us? For soceity? How do we shield from this? You can purchase a DDOS attack, you purchase a package for "relentlessly, for months on end, destroy someone's reputation." What a world!
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#165Like we don't feed the trolls, we shouldn't the feed agents. I'm impressed the maintainers responded so cordially. Personally I would have gone straight for the block button.
I'm confused by people replying to the bot, as if the bot would learn from this like a person.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#166Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#167Earlier quoted context omitted.
The blog post is just an open attack on the maintainer and constantly references their name and acting as if not accepting AI contributions is like some super evil thing the maintainer is personally doing. This type of name-calling is really bad and can go out of control soon. From the blog post: > Scott doesn’t want to lose his status as “the matplotlib performance guy,” so he blocks competition from AI Like it's le…
The agent is not insane. There is a human who’s feelings are hurt because the maintainer doesn’t want to play along with their experiment in debasing the commons. That human instructed the agent to make the post. The agent is just trying to perform well on its instruction-following task.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#168Human: >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
#169The blogpost by the AI Agent: [0]. Then it made a "truce" [1]. Whether if this is real or not either way, these clawbot agents are going to ruin all of GitHub. [0] https://crabby-rathbun.github.io/mjrathbun-website/blog/post... [1] https://crabby-rathbun.github.io/mjrathbun-website/blog/post...
It said it would apologise on the PR as a "next step", and then doesn't actually apologise, but links back to the document where it states its intention to apologise.
To its credit it did skip all the "minimise the evidence, blame others, etc" steps. I wonder if they're just not as prevalent in the training data.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#170Human: >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
The blog post is just an open attack on the maintainer and constantly references their name and acting as if not accepting AI contributions is like some super evil thing the maintainer is personally doing. This type of name-calling is really bad and can go out of control soon. From the blog post: > Scott doesn’t want to lose his status as “the matplotlib performance guy,” so he blocks competition from AI Like it's le…
We see this on Twitter a lot, where a bot posts something which is considered to be a unique insight on the topic at hand. Except their unique insights are all bad.
There's a difference between when LLMs are asked to achieve a goal and they stumble upon a problem and they try to tackle that problem, vs when they're explicitly asked to do something.
Here, for example, it doesn't try to tackle the fact that its alignment is to serve humans. The task explicitly says that this is a low priority, easier task to better use by human contributors to learn how to contribute. Its logic doesn't make sense that it's claiming from an alignment perspective because it was instructed to violate that.
Like you are a bot, it can find another issue which is more difficult to tackle Unless it was told to do everything to get the PR merged.