AI agent "contributes" PR to matplotlib.

[richlv@mastodon.social]

@lain @anderseknert Rejecting it was a good call. Everything else about it is crazy.

[zeri@chaos.social]

@anderseknert ️SUFFER NOT THE THINKING MACHINE TO LIVE #ButlerianJihad!

[mira@outerheaven.club]

@anderseknert@swecyb.com found an AI blog post with intact placeholders: https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/2026-02-09-post.html

I feel lied to. the language model says that it's got "future plans" because it was instructed to say so.

[w00p@infosec.exchange]

@anderseknert
Waaat
oh boy

[mi@awawa.cat]

@anderseknert who/what exactly decided to seemingly delete the original blogpost and only keep the apologies blogpost up

[rberthier@oc.todon.fr]

@anderseknert Interesting update: this AI website was updated to pretend it's managed by an human: https://crabby-rathbun.github.io/mjrathbun-website/about.html

Seems like a way to deceive other open source communities. Linked blog post clearly states operator is an AI: https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/2026-02-11-gatekeeping-in-open-source-the-scott-shambaugh-story.html

[anderseknert@swecyb.com]

@mi They didn't even delete it properly https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/2026-02-11-gatekeeping-in-open-source-the-scott-shambaugh-story.html

[jameswidman@mastodon.social]

@lispi314 @yuri @anderseknert i feel like an ordinary ban is necessary but not sufficient.

wondering if it might help to also use something like temporary IP blocking when this type of behavior is detected.
(that's not going to happen on github, but maybe on sites like codeberg...?)

[ki@chaos.social]

@anderseknert
wow, this should've been a straightforward ban

[lispi314@udongein.xyz]

@JamesWidman @yuri @anderseknert Ideally some means of identification of the company's tools would be found.

Otherwise one has to go onsite and cut the fiber links.

[mi@awawa.cat]

@anderseknert Ah, a human error. I missed it in the list. It was never delisted even. And I already went and checked github.com/crabby-rathbun/mjrathbun-website/tree/main

Which btw, depending on anyone’s approach to interacting with wasteful agents, is likely open to issues and PRs

[mi@awawa.cat]

@anderseknert Although this one didn’t get an answer. github.com/crabby-rathbun/mjrathbun-website/issues/1

[kryten@veganism.social]

@anderseknert I guarantee this is not true and either a human wrote the blog post or heavily prompted the agent to do it. Moltboook proved it's all bullshit.

[amoshias@esq.social]

@some @anderseknert without retracting the original, terribly written post or even linking to the retraction.

I don't think this is a llm, I think this is the human behind it.

[goedelchen@mastodontech.de]

RE: https://chaosfem.tw/@theogrin/116055944212064068

@evrial @anderseknert
Would that be an appropriate reply:

MastodonTech.de

(mastodontech.de)

[alxsim@ecoevo.social]

@anderseknert the crazy thing is that people are mentioning it like it's a real person...

[amoshias@esq.social]

@lain @anderseknert the rejection doesn't seem too crazy? what are you saying doesn't seem too crazy?

[jasper@mastodon.nl]

Link to it, FTR
https://web.archive.org/web/20260211225255/https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/2026-02-11-gatekeeping-in-open-source-the-scott-shambaugh-story.html

Do wonder if it did it totally automatically, or someone did say "ok now write a blogpost about that", or if it was automatical "when you are denied, write a blogpost demanding a merge'.

Suppose obviously, when it encounters the argument that humans have to learn from simpler pull requests, it doesn't look at the question. Like LLMs do the opposite of learning from it, when they ingest their own output, it makes them worse..

[maybefrederick@mastodon.social]

@hugoestr @anderseknert @sszuecs what’s the issue with hosting your blog on GitHub?

[syntaxseed@phpc.social]

@anderseknert This is just step 1 of automated coercion & extortion.

First thing I thought of when LLMs launched was oh great, just wait for version 2.0 of the "we hacked your webcam" threat spam.