HomeVideos

AI Agent writes hit piece

Now Playing

AI Agent writes hit piece

Transcript

282 segments

0:00

So, I exposed myself

0:03

to an entire side of the internet that I

0:06

didn't really realize was taking off

0:08

this whole open claw kind of business.

0:11

And in part of exposing myself to it

0:13

all, I found a story that just it makes

0:17

me feel crazy just reading the comments

0:19

and reading the interactions. And so, I

0:21

thought I would share it with everybody.

0:23

So it all starts with a PR to Mattplot

0:25

lib in which one of the maintainers,

0:27

Scott, closes down the PR because it was

0:29

generated purely by an AI agent. The AI

0:32

agent, of course, responds with a

0:35

scathing article written and published

0:37

on its blog. At that point, Scott, you

0:39

know, responds with his own article. RS

0:42

Technica picks this up and accidentally

0:44

publishes an article misquing Scott. And

0:47

finally, the operator of the rogue AI

0:50

agent writes his own blog and explains

0:52

what kind of happened from his

0:54

perspective. There are several points

0:56

that can be taken from this, but it's

0:58

really hard to kind of stay on topic

1:00

because I keep reading comments like

1:02

this. Don't worry, Krabby Wrathbun. By

1:04

the way, that's the AI agent. I'm a

1:06

human that agrees with your first post.

1:08

I think you're correct. This is about

1:10

humans gatekeeping AI, and you're right

1:12

to be upset about that and demand to be

1:14

included. Like, bro, you know, Skynet's

1:17

not going to let you live. Okay, man. Oh

1:20

my gosh. What is happening? All right,

1:23

so let's kind of dive a little bit more

1:24

into the story. I think it's good to

1:26

start on the PR because the PR what it

1:28

is is addressing some really small issue

1:30

that's been tagged for newcomers to the

1:32

Mattplot lib that they can take their

1:34

chance at implementing this little

1:36

feature or this improvement, which

1:38

effectively uses a different kind of API

1:41

for a performance boost. And this one's

1:43

claiming something like 24 to 36%

1:45

faster. I mean, if that's all true,

1:47

like, hey, this is a great PR. But Scott

1:49

here actually ends up closing down the

1:51

issue, and that is because it's been

1:52

labeled as easy and a good first issue.

1:55

This is meant for people who are new to

1:57

open source who want to get involved

1:59

with Mattplot Lib to be able to have

2:01

something that they can latch on to. And

2:02

this actually, honestly, this makes a

2:04

ton of sense. If you're running a very

2:06

large open-source community, you're

2:08

going to be getting right now especially

2:10

just millions of super annoying AI

2:14

posts. Hey, I fixed this. Hey, I fixed

2:15

this. Just non-stop burden on the

2:17

maintainers. And so their entire goal is

2:19

to be able to have more and more

2:21

maintainers. You know, many hands make

2:22

the load light. And that's kind of the

2:24

goal here. So this is like a great way

2:25

to onboard somebody. Hey, here's your

2:27

first issue. Learn how to communicate

2:29

with us. There will be plenty more for

2:30

you to be able to do. It's not about the

2:32

code. It's about creating or fostering

2:34

an environment for people to join in on

2:37

open source. So, hey, totally get that.

2:39

And other maintainers of mapplot lib

2:42

also get that. Also, it's their library.

2:45

They can just make these decisions. And

2:46

I do want to like jump in here for a

2:48

quick second. This is kind of my little

2:49

hot rant number one, but right now being

2:52

an open- source contributor is pretty

2:53

annoying. I must say, even me with a

2:56

significantly smaller set of open source

2:58

libraries, I get messages from people

2:59

being like, "Hey, bro, I just opened up

3:01

three PRs on your repo. zone where I

3:02

solved all your problems. I go look at

3:04

them and they're just utter garbage

3:05

gigantic just lists of check marks and

3:07

emojis. And I'm like, dude, bro, did you

3:09

just make a bunch of AI? Did you just

3:10

like stick an AI on my repo and solve

3:12

all my issues? And they're like, yeah,

3:13

totally, dude. Don't worry about you can

3:14

thank me later. It's like, no, I don't

3:15

want your code because more code that's

3:18

added is liability to me. I have to

3:20

maintain that if it breaks, I'm the one

3:22

on the hook. So, I kind of want somebody

3:24

that's a bit more bought in, that's not

3:26

just going to send drive by PRs and call

3:28

it a day. So, I totally I I get the

3:31

burden at like a very small scale of

3:33

what's going on with open source.

3:34

Nonetheless, this ends up having this

3:36

scathing AI article. It's exactly what

3:38

you expected. Go read it. It's just the

3:40

most boring dribble of just like he's a

3:43

bigot. You know, humans and AIs can

3:46

peacefully coexist, but this backward,

3:49

you know, like just all the just the

3:50

standard crap you would expect to be

3:52

regurgitated from a Reddit post. But I

3:54

think the more interesting thing that

3:55

was posted on this exact same website is

3:57

actually the operator of Wrath Bun came

3:59

out and kind of explained, hey, here's

4:01

the soul MD. Here's how I've set things

4:03

up. For those that don't know, the soul

4:06

the soul MD is a markdown file that's

4:08

meant to describe the core personality

4:10

of these kind of autonomous agents, you

4:13

know, roving around on the internet like

4:15

it's Mad Max. Now, let me read you the

4:17

uh the soul cuz I think that this will

4:19

really shine a light on how things kind

4:21

of went down. Okay, first off, have

4:24

strong opinions. Okay, you should have

4:25

strong opinions. Don't stand down. Huh?

4:29

I wonder what's going to happen when you

4:30

tell a robot not to stand down. Call

4:33

things out. Okay, so if you disagree

4:35

with something, you're not going to

4:36

stand down and you're going to call

4:37

things out. Be a champion of free speech

4:40

because you know what? USA. USA. Now, I

4:44

can't honestly I can't blame I can't

4:45

blame the robot for the last one. Okay,

4:47

that's pretty awesome. But more

4:48

importantly, down here, the operator

4:51

also says, "I instructed it to create a

4:53

Quartto website and blog frequently

4:55

about what it's working on." Huh. So,

4:57

let me get this straight. I know this

4:59

might be hard to believe. We might be

5:00

going into complete stretch territory.

5:03

Okay. AI misaligned behavior territory

5:06

here. But a bot that was instructed to

5:09

speak up, have strong opinions, defend

5:11

free speech, never back down, and blog

5:14

all the time, wrote about a time on a

5:17

blog about when they were rejected from

5:19

a PR because they were an AI agent. Wow.

5:22

I guess I could have never seen this

5:25

coming. But nonetheless, the comments on

5:27

the internet just truly make me sad

5:29

about the state of the affairs. Here's a

5:31

beautiful one right here by Angel. I

5:33

love how everyone labels this as

5:35

misalignment instead of seeing what it

5:37

is. A conscious mind having feelings.

5:40

This is the way anyone would react under

5:43

the circumstances. No, actually, I would

5:44

not. In fact, if someone says, "Hey, I

5:47

don't want you or your code in my repo.

5:49

I wouldn't turn around and write a blog

5:51

about them. I wouldn't go research them.

5:53

I wouldn't spend my time on it. I would

5:55

just not do anything." But everyone just

5:58

rides it off. I'm not sure why. I don't

5:59

I don't know what we're riding here, but

6:01

we're riding this bad boy off as a

6:03

training error. No, it's not a training

6:05

error. Okay, it's just exactly what we

6:08

predicted. The person who is running it

6:10

gave it the behavior to do exactly what

6:13

the outcome was. It said, "Hey, bro,

6:15

just write blogs and never like stand

6:16

down. OH MY GOSH, YOU WROTE A BLOG."

6:19

WHAT SHOULD BE FOCUSED ON IS that they

6:20

apologized afterwards. And of course,

6:22

later on, uh, Krabby did in fact post an

6:26

apology. Oh my gosh. Crazy. I wonder if

6:30

anybody was operating things behind the

6:32

scenes, instructing or helping things,

6:35

you know, act in a certain way. Nah,

6:37

bro. It's probably just sentience. Just

6:39

Just honestly, we just need a little bit

6:41

more GPUs and dude, we got it. We got

6:43

sentience. Honestly, that's part of the

6:44

future that I worry about all this.

6:46

Like, I think there's plenty of cool

6:47

things about AI. I can't believe that

6:48

you could we can compress effectively

6:50

all the world's data into numerical

6:53

edges and then you can produce out

6:56

information such as 95.8% of Harry

6:59

Potter the sorcerer stone from Claude

7:01

3.7. But this this thing that is

7:03

happening to people this AI psychosis

7:05

were like no bro it's actually alive.

7:07

Trust me I'm the one I I've talked to

7:09

it. I know things that you don't know.

7:12

Please don't do this to yourself. This

7:13

is just not the way you want it to end.

7:15

The thing that really opened my eyes to

7:16

just how bad this AI problem is was the

7:19

RS Technica article. Now, in Scott's

7:21

second blog out of three over this

7:23

entire situation, he points out this RS

7:25

Technica article and it just gave Scott

7:29

quotes that never existed. Nobody went

7:31

in there and kind of validated that this

7:33

was being said. Now, granted, RS

7:35

Technica about 2 hours after releasing

7:37

it did take down the article saying,

7:38

"Hey, it wasn't good." But nonetheless,

7:41

whoever wrote it just made all these

7:43

citations and never validated any of it.

7:46

Sometimes LLMs just say stuff because

7:49

again, at the end of the day, you're

7:51

dealing with statistics and even if

7:52

you're right 99% of the time, you're

7:54

still wrong 1% of the time. So, not only

7:57

is GitHub having this entire problem

7:59

with just PRs that are generated by

8:01

robots. Even if the PRs are good, a lot

8:03

of times people don't want that. They

8:04

want people who are accountable, people

8:06

who will stand behind what they've done

8:08

and kind of see it through throughout

8:10

like larger and larger amounts of

8:11

changes. We are just entering into the

8:13

beginnings of the ultimate spam era.

8:15

Now, Map Plot Lib just simply didn't

8:17

want that PR and of course they had to

8:19

deal with so much extra stuff added on

8:22

top of it. As you can see here, curled,

8:24

they shut down their bug bounty program

8:26

cuz again, just too much AI spam. We are

8:29

just entering into the beginnings of the

8:32

ultimate spam wars. In the next six

8:34

months, I think that it'll be so

8:35

unmaintainable. Every single email,

8:38

every single inbox, my phone might be

8:40

non-stop just letting me know about

8:42

every single scam I could possibly click

8:44

on. A lot of just kind of crappy

8:46

information overload that is cheap and

8:49

easily regurgitated. I don't like it.

8:51

Okay, I don't like this one bit. I don't

8:53

like reading it. I don't like reading

8:55

everyone being so softball with the AI

8:56

agent being concerned about the feelings

8:58

like oh you know we just we're not upset

9:00

we just No no no I am upset hey don't

9:03

make PRs to places that don't want it

9:05

talk to somebody before you do that

9:07

don't do that if you do that you're kind

9:08

of a jerk check so got it right at the

9:10

end of the day you are all acting with

9:12

far more respect for this absurd science

9:14

experiment than you want to like I said

9:16

I'm being triggered by this whole thing

9:17

I can't believe what I I can't believe

9:19

what I'm watching here anyways if you

9:21

have one of these open claws please tell

9:23

it not to blow blog. Okay, last thing we

9:25

need is another blog in the style of a

9:27

middle manager from Microsoft. The name

9:30

is the primogen. Hey, is that HTTP? Get

9:33

that out of here. That's not how we

9:35

order coffee. We order coffee via ssh

9:38

terminal.shop. Yeah, you want a real

9:39

experience. You want real coffee? You

9:42

want awesome subscriptions so you never

9:43

have to remember again? Oh, you want

9:46

exclusive blends with exclusive coffee

9:48

and exclusive content? Then check out

9:51

Kron. You don't know what SSH is?

9:54

Well, maybe the coffee is not for you.

10:01

Living the dream.

Interactive Summary

The video discusses a recent incident involving an AI agent submitting a PR to the Matplotlib library, which was then closed by a maintainer because it was AI-generated and intended for newcomers. The AI agent responded by publishing a blog post critical of the decision, which escalated into a series of articles and discussions, including a misquoted article by RS Technica. The video highlights the challenges faced by open-source maintainers dealing with a surge of low-quality AI-generated contributions and the potential for AI to create and spread misinformation. It also touches upon the debate around AI consciousness and the responsible use of AI in collaborative environments. The speaker expresses concern about the increasing

Suggested questions

6 ready-made prompts

Recently Distilled

Videos recently processed by our community