Live data from Hacker News

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

github.com

171–180 of 806 posts

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

#171
post #95

Earlier quoted context omitted.

Its astonishing the way that we've just accepted mass theft of copyright. There appears to be no way to stop AI companies from stealing your work and selling it on for profits On the plus side: It only takes a small fraction of people deliberately poisoning their work to significantly lower the quality, so perhaps consider publishing it with deliberate AI poisoning built in

Would publishing under AGPL count as poisoning? Or even with an explicit "this is not licensed" license

[deleted]

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

#172

Earlier quoted context omitted.

Indeed. One could argue that the LLMs will keep on improving and they would be correct. But they would not improve in ways that make them a good independent agent safe for real world. Richard Sutton got a lot of disagreeing comments when he said on Dwarkesh Patel podcast that LLMs are not bitter-lesson ( https://en.wikipedia.org/wiki/Bitter_lesson ) pilled. I believe he is right. His argument being, any technique tha…

I disagree with Sutton that a main issue is using human generated data. We humans are trained on that and we don't run into such issues. I expect the problem is more structural to how the LLMs, and other ML approaches, actually work. Being disembodied algorithms trying to break all knowledge down to a complex web of probabilities, and assuming that anything predicting based only on those quantified data, seems hugely…

Sutton actually argues that we do not train on data, we train on experiences. We try things and see what works when/where and formulate views based on that. But I agree with your later point about training such a way is hugely limiting, a limit not faced by humans

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

#173
post #95

Earlier quoted context omitted.

> I suspect the culture will have to retreat back behind the gates at some point, which will be very sad and shrink it further. I'm personally contemplating not publishing the code I write anymore. The things I write are not world-changing and GPLv3+ licensed only, but I was putting them out just in case somebody would find it useful. However, I don't want my code scraped and remixed by AI systems. Since I'm doing th…

Its astonishing the way that we've just accepted mass theft of copyright. There appears to be no way to stop AI companies from stealing your work and selling it on for profits On the plus side: It only takes a small fraction of people deliberately poisoning their work to significantly lower the quality, so perhaps consider publishing it with deliberate AI poisoning built in

In practice, the real issue is how slow and subjective the legal enforcement of copyright is.

The difference between copyright theft and copyright derivatives is subjective and takes a judge/jury to decide. There’s zero possibility the legal system can handle the bandwidth required to solve the volume of potential violations.

This is all downstream of the default of “innocent until proven guilty”, which vastly benefits us all. I’m willing to hear out your ideas to improve on the situation.

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

#174

The agent's blog is hilarious. I suppose we are going to see human only github alternatives soon?

Wouldn't be surprised if we return back to invite-only communities.

We're kind of already there with the prevalence of Discord -- oh wait.

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

#175

Why on earth does this "agent" have the free ability to write a blog post at all? This really looks more like a security issue and massive dumb fuckery.

An operator installed the OpenClaw package and initialized it with:

    (1) LLM provider API keys and/or locally running LLM for inference

    (2) GitHub API keys

    (3) Gmail API keys (assumed: it has a Gmail address on some commits)
Then they gave it a task to run autonomously (in a loop aka agentic). For the operator, this is the expected behavior.

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

#178

Earlier 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.

I don't know how you get there conclusively. If Turing tests taught me anything, given a complex enough system of agents/supervisors and a dumb enough result it is impossible to know if any percentage of steps between 2 actions is a distinctly human moron.

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

#179
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

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…

LLMs are tools designed to empower this sort of abuse.

The attacks you describe are what LLMs truly excel at.

The code that LLMs produce is typically dog shit, perhaps acceptable if you work with a language or framework that is highly overrepresented in open source.

But if you want to leverage a botnet to manipulate social media? LLMs are a silver bullet.

Post reply on HN