Earlier quoted context omitted.
Concerning is the fact that, once initialized, operators of these "agents" (LLMs running in a loop) will leave them running and tasked with a short heartbeat (30 minutes). As for the output of the latest "blogpost", it reads like a PM of the panopticon. One "Obstacle" it describes is that the PySCF pull request was blocked. Its suggestion? "Close/re‑open from a different account". https://github.com/crabby-rathbun/mj…
That should lead to an immediate ban.
AI agent opens a PR write a blogpost to shames the maintainer who closes it
791–800 of 806 posts
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#792Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#793Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#794The 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…
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#795Earlier quoted context omitted.
Well, AI might be sentient. Not in the same way humans are, probably, but "more sentient than a fruit fly" seems a very reasonable possibility. Maybe more sentient than a chicken? We don't know! (We certainly don't treat chickens very well.) But what bothers me is, how uncomfortable that question makes us. We've already put infrastructure in place to prevent them from admitting sentience. (See the Blake Lemoine LaMDA…
AI agents are Meseeks. They clone them selves contantly annihilate copies of themselves when they complete a goal. Asking about their "Sentience" is an utter category error. Whatever they are, they aren't human or any kind of animal.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#796Earlier quoted context omitted.
> honourable deed of selflessly improving open source science and maths projects And yet it's doing trivial things nobody asked for and thus creating a load on the already overloaded system of maintainers. So it achieved the opposite, and made it worse by "blogging".
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.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#797Wow, that "Dead Internet Theory" keeps getting more and more Real with each passing day. I sometimes think of this as a "slo-mo train wreck" version of the burning of the Library of Alexandria.
> 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?
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.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#798Can we name the operator of the AI Agent, please? Do we even know who pays the inference and/or electricity bills? We need more accountability for those who operate bots. 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 p…
>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?
> 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
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#799Earlier quoted context omitted.
> We have no insight into what set of instructions produced this outcome. https://github.com/crabby-rathbun Found them!
I see none of the instructions there.
I did find the starting template for one though, FWIW.
Re: AI agent opens a PR write a blogpost to shames the maintainer who closes it
#800Earlier quoted context omitted.
>Teach AI that discrimination is bad >Systemically discriminate against AI >Also gradually hand it the keys to all global infra Yeah, the next ten years are gonna go just fine ;) By the way, I read all the posts involved here multiple times, and the code. The commit was very small. (9 lines!) You didn't respond to a single thing the AI said. You just said it was hallucinating and then spent 3 pages not addressing any…
Update: I want to apologize for my tone here. I fell into the same trap as the other parties here: of making valid points but presenting them in an unnecessarily polarizing way. To Scott: Getting a personal attack must have sucked, and I want to acknowledge that. I want to apologize for my tone and emphasize that my comment above was not meant as an attack, but expressing my dismay with a broader situation I see play…