WEBVTT - Did AI Write This?

0:00:15.396 --> 0:00:33.356
<v Speaker 1>Pushkin. I'm Jacob Goldstein, and this is What's Your Problem?

0:00:33.616 --> 0:00:36.976
<v Speaker 1>My guest today is Max Spiro. He's the co-founder and

0:00:37.036 --> 0:00:40.936
<v Speaker 1>CEO of a company called Pangram. And Max's problem is this.

0:00:41.656 --> 0:00:44.566
<v Speaker 1>How do you build a tool that that reliably identifies

0:00:44.686 --> 0:00:47.826
<v Speaker 1>whether a piece of writing or an image was created

0:00:47.926 --> 0:00:51.706
<v Speaker 1>by AI. If you've heard about any of the recent

0:00:51.806 --> 0:00:56.376
<v Speaker 1>controversies over whether something was written by AI, whether it

0:00:56.436 --> 0:01:01.696
<v Speaker 1>was a prize-winning novel or an op-ed in a major newspaper,

0:01:02.296 --> 0:01:05.076
<v Speaker 1>there's a good chance that you've actually heard about Pangram,

0:01:05.216 --> 0:01:07.996
<v Speaker 1>whether you know it or not, because Pangram is the

0:01:08.036 --> 0:01:12.226
<v Speaker 1>tool people almost always cite in those cases. It is

0:01:12.306 --> 0:01:18.306
<v Speaker 1>generally viewed as the most reliable, widely available AI identification tool.

0:01:18.916 --> 0:01:21.316
<v Speaker 1>Max and I talked about a lot of different things

0:01:21.436 --> 0:01:25.376
<v Speaker 1>in our conversation. We talked about changing norms around when

0:01:25.416 --> 0:01:28.076
<v Speaker 1>it's OK to use AI and when it's not OK.

0:01:28.816 --> 0:01:31.996
<v Speaker 1>We talked about the risk of false positives, of PanGram

0:01:32.216 --> 0:01:35.976
<v Speaker 1>wrongly accusing people of using AI to write things. And

0:01:36.036 --> 0:01:39.056
<v Speaker 1>we talked about the new PanGram tool to detect whether

0:01:39.136 --> 0:01:42.656
<v Speaker 1>an image was AI generated. But to start, we talked

0:01:42.676 --> 0:01:45.996
<v Speaker 1>about two domains where PanGram is already in wide use,

0:01:46.676 --> 0:01:51.556
<v Speaker 1>education and publishing. Tell me about PanGram and sort of

0:01:51.696 --> 0:01:54.266
<v Speaker 1>where you are now. Who are your customers? Who's using it?

0:01:54.676 --> 0:01:58.536
<v Speaker 2>Our customers, a bunch of customers in education, higher ed,

0:01:58.576 --> 0:02:01.916
<v Speaker 2>and also like high schools, K-12, they want to know

0:02:02.096 --> 0:02:05.946
<v Speaker 2>whether their students are submitting AI-generated essays. They want a

0:02:05.966 --> 0:02:12.596
<v Speaker 2>way to teach writing or, like, have any writing-based assignments

0:02:13.136 --> 0:02:16.596
<v Speaker 2>without having it sort of just devolve into students using AI.

0:02:16.676 --> 0:02:20.346
<v Speaker 1>It seems like an extremely strong case. Like, you know,

0:02:20.466 --> 0:02:23.146
<v Speaker 1>writing is a way of thinking hard about things. I

0:02:23.226 --> 0:02:26.726
<v Speaker 1>buy that it is useful still for students to write.

0:02:27.906 --> 0:02:31.806
<v Speaker 1>My sense is that students are using AI a lot and,

0:02:32.046 --> 0:02:34.306
<v Speaker 1>you know, going to great lengths to sort of humanize

0:02:34.356 --> 0:02:36.536
<v Speaker 1>what the AI says, to sort of write through AI

0:02:37.096 --> 0:02:38.616
<v Speaker 1>or do what they have to do. Like, what is

0:02:38.656 --> 0:02:39.956
<v Speaker 1>your sense of how it is going?

0:02:40.316 --> 0:02:42.956
<v Speaker 2>Yeah, something like pangram here would be more of like,

0:02:43.366 --> 0:02:46.986
<v Speaker 2>we're adding friction to the process of cheating. And, you know,

0:02:47.466 --> 0:02:49.546
<v Speaker 2>it's going to make it less enticing if you have

0:02:49.606 --> 0:02:52.256
<v Speaker 2>to go start with AI bones and rewrite it.

0:02:52.426 --> 0:02:54.366
<v Speaker 1>Yes, you can't one-shot your assignment.

0:02:54.386 --> 0:02:54.886
<v Speaker 2>Exactly.

0:02:55.086 --> 0:02:55.846
<v Speaker 1>Yeah, yeah.

0:02:55.966 --> 0:02:59.426
<v Speaker 2>And that's helpful in some way. And, you know, you

0:02:59.466 --> 0:03:02.466
<v Speaker 2>can encourage students to, you know, start from scratch and

0:03:02.486 --> 0:03:03.346
<v Speaker 2>not use AI at all.

0:03:03.386 --> 0:03:06.436
<v Speaker 1>But I mean, certainly there are teachers who are requiring

0:03:06.496 --> 0:03:10.086
<v Speaker 1>students to do their writing in the room. Right? Like,

0:03:10.206 --> 0:03:13.066
<v Speaker 1>they're just going hard at, you have to sit here

0:03:13.106 --> 0:03:14.896
<v Speaker 1>in front of me. So what did somebody call it?

0:03:14.986 --> 0:03:16.906
<v Speaker 1>AI jail or something? You have to sit here in

0:03:16.956 --> 0:03:18.016
<v Speaker 1>front of me and write an essay.

0:03:18.076 --> 0:03:20.796
<v Speaker 2>It's kind of a bummer. Like, I feel like we

0:03:20.836 --> 0:03:24.336
<v Speaker 2>lose a lot here. We lose the in-class instruction. We

0:03:24.456 --> 0:03:29.496
<v Speaker 2>lose the ability to assign longer written pieces. It's true.

0:03:29.516 --> 0:03:31.136
<v Speaker 2>When I was in college, I wrote a lot of

0:03:31.156 --> 0:03:33.526
<v Speaker 2>like eight and 10, 12 page essays.

0:03:34.406 --> 0:03:34.706
<v Speaker 1>Yeah.

0:03:34.746 --> 0:03:37.146
<v Speaker 2>Like those, you can't do that in class. That takes

0:03:37.186 --> 0:03:37.706
<v Speaker 2>a lot of hours.

0:03:38.266 --> 0:03:40.546
<v Speaker 1>I mean, but that's just the nature of the world now, right? Like,

0:03:40.626 --> 0:03:41.766
<v Speaker 1>it sort of is what it is.

0:03:42.406 --> 0:03:45.876
<v Speaker 2>Yeah, and it's a little bit adversarial, as many of

0:03:46.116 --> 0:03:49.316
<v Speaker 2>our use cases are, where, like, the way that Pangram

0:03:49.336 --> 0:03:51.976
<v Speaker 2>is used is somebody is trying to get away with

0:03:52.016 --> 0:03:55.076
<v Speaker 2>AI writing in a way. And so there is this

0:03:55.196 --> 0:03:56.256
<v Speaker 2>adversarial component.

0:03:56.396 --> 0:03:58.936
<v Speaker 1>Yes. I mean, it's got to be mostly adversarial, right?

0:03:58.956 --> 0:04:02.206
<v Speaker 1>The weird non-adversarial one would be, I actually wrote this thing,

0:04:02.326 --> 0:04:04.266
<v Speaker 1>and I don't want people to think it's AI, so

0:04:04.286 --> 0:04:06.006
<v Speaker 1>I'm going to put it in Pangram, right? Like, that's

0:04:06.486 --> 0:04:10.686
<v Speaker 1>an edge case. Like, I've started using fewer em dashes, actually.

0:04:10.826 --> 0:04:12.806
<v Speaker 2>Oh, man. You got to use the em dashes.

0:04:13.306 --> 0:04:17.526
<v Speaker 1>Journalists love em dashes. And actually, maybe because I love them,

0:04:17.606 --> 0:04:21.076
<v Speaker 1>I didn't even notice it in AI pros. But once

0:04:21.116 --> 0:04:23.396
<v Speaker 1>everybody started talking about the em dash as a giveaway,

0:04:23.496 --> 0:04:27.056
<v Speaker 1>I just started doing, like, shorter independent clauses, basically.

0:04:27.176 --> 0:04:30.096
<v Speaker 2>Em dashes are, like, they're no longer an AI tell.

0:04:30.416 --> 0:04:34.426
<v Speaker 2>This was, like, a GPT-4 era thing. maybe like 4.0,

0:04:34.426 --> 0:04:37.286
<v Speaker 2>really overuse the em dash. We're over it now. Em

0:04:37.306 --> 0:04:38.626
<v Speaker 2>dashes are used a normal amount.

0:04:38.746 --> 0:04:40.616
<v Speaker 1>I can bring the em dash back? I can bring

0:04:40.676 --> 0:04:40.946
<v Speaker 1>it back?

0:04:40.976 --> 0:04:42.056
<v Speaker 2>Yes, you should bring it back.

0:04:42.496 --> 0:04:46.936
<v Speaker 1>Okay, great. So education is obviously a big use case.

0:04:47.556 --> 0:04:48.996
<v Speaker 2>I'll tell you about publishing as well.

0:04:49.376 --> 0:04:51.156
<v Speaker 1>Oh yeah, publishing. Well, so that one has been in

0:04:51.196 --> 0:04:53.616
<v Speaker 1>the news, right? There have been a couple of people,

0:04:53.776 --> 0:04:56.916
<v Speaker 1>one person lost a seven-figure book deal, right? Because, I

0:04:56.916 --> 0:04:59.536
<v Speaker 1>don't want to say because of you, but because they

0:04:59.576 --> 0:05:01.996
<v Speaker 1>were accused of using AI to write the book and

0:05:03.056 --> 0:05:04.176
<v Speaker 1>you were definitely involved in that.

0:05:04.636 --> 0:05:06.816
<v Speaker 2>Yeah, there have been a series of scandals this year

0:05:07.036 --> 0:05:10.696
<v Speaker 2>on AI use, either in books that are already published

0:05:10.836 --> 0:05:14.146
<v Speaker 2>or like big book deals. But kind of what it

0:05:14.436 --> 0:05:16.886
<v Speaker 2>comes down to is that a lot of people in

0:05:16.906 --> 0:05:19.466
<v Speaker 2>the industry are on the left side of the bell

0:05:19.506 --> 0:05:23.586
<v Speaker 2>curve where they're not heavy AI users. They're like, they're

0:05:23.786 --> 0:05:30.696
<v Speaker 2>book editors and publishers. They read like real books all day.

0:05:31.076 --> 0:05:34.636
<v Speaker 2>So they're not like, you know, talking to chat. So

0:05:34.896 --> 0:05:36.796
<v Speaker 2>I think like a lot of them, they like never

0:05:36.836 --> 0:05:39.476
<v Speaker 2>really built up this intuition in a way that like

0:05:39.556 --> 0:05:42.816
<v Speaker 2>all of a sudden, like AI getting good enough to

0:05:42.916 --> 0:05:46.616
<v Speaker 2>like produce publishable prose was like very surprising and kind

0:05:46.636 --> 0:05:47.636
<v Speaker 2>of caught them by surprise.

0:05:48.316 --> 0:05:53.566
<v Speaker 1>So recently, famous investor Stanley Druckenmiller wrote an op-ed in

0:05:53.586 --> 0:05:57.126
<v Speaker 1>the Wall Street Journal about the bond market. And everybody's like, wait,

0:05:57.306 --> 0:06:00.836
<v Speaker 1>AI wrote that. And then Druckenmiller was like, you're damn

0:06:00.876 --> 0:06:02.776
<v Speaker 1>right AI wrote that. I'm 80 years old and I

0:06:02.816 --> 0:06:05.696
<v Speaker 1>know how to use AI. And then maybe most interestingly,

0:06:06.356 --> 0:06:09.336
<v Speaker 1>the editor of the journal op-ed page was like, it's

0:06:09.376 --> 0:06:12.476
<v Speaker 1>fine that AI wrote it. Like Druckenmiller is a famous investor.

0:06:12.556 --> 0:06:15.966
<v Speaker 1>He really believes this. He stands behind it. Any famous

0:06:16.006 --> 0:06:19.046
<v Speaker 1>person writing an op-ed in the paper usually has somebody

0:06:19.066 --> 0:06:21.186
<v Speaker 1>else write it for him anyway. There's no problem here.

0:06:21.986 --> 0:06:23.846
<v Speaker 1>Sort of surprisingly, I might think I would have a

0:06:23.846 --> 0:06:26.386
<v Speaker 1>problem with it, but upon reflection, I don't. Do you

0:06:26.406 --> 0:06:27.026
<v Speaker 1>think it's bad?

0:06:27.806 --> 0:06:30.486
<v Speaker 2>I think the argument against is that it still does

0:06:30.926 --> 0:06:34.026
<v Speaker 2>a disservice to the readers. Like, if you read it, it's, like,

0:06:34.146 --> 0:06:36.066
<v Speaker 2>full of AI prose.

0:06:36.596 --> 0:06:39.056
<v Speaker 1>So your critique is as a piece of writing. It's

0:06:39.136 --> 0:06:41.256
<v Speaker 1>bad writing, and that is the criticism.

0:06:41.656 --> 0:06:44.976
<v Speaker 2>Yeah, and, like, the Wall Street Journal has great editors.

0:06:45.076 --> 0:06:47.236
<v Speaker 2>I'm sure, like, he could have just, like, written up

0:06:47.736 --> 0:06:51.816
<v Speaker 2>a draft himself that was, like, not particularly flowery or

0:06:51.836 --> 0:06:53.916
<v Speaker 2>whatever and then, you know, sent it to his editors and, like,

0:06:54.336 --> 0:06:58.476
<v Speaker 2>they help him work it into something that's, like, very readable.

0:06:58.916 --> 0:07:01.996
<v Speaker 1>You could also argue, like, it certainly would be less

0:07:02.036 --> 0:07:05.656
<v Speaker 1>objectionable if it just said at the bottom, this was

0:07:05.716 --> 0:07:08.696
<v Speaker 1>written with the assistance of AI, right? Like, that would

0:07:08.856 --> 0:07:11.516
<v Speaker 1>seem to, like, if you have any criticism, it's like, well,

0:07:11.536 --> 0:07:14.576
<v Speaker 1>you should tell me because it's weird. Yeah. Although you

0:07:14.616 --> 0:07:16.846
<v Speaker 1>could make the same argument for ghostwriters and, like, pretty

0:07:16.876 --> 0:07:21.266
<v Speaker 1>much anything you see written by a CEO, in most cases,

0:07:21.526 --> 0:07:23.866
<v Speaker 1>of a big company is going to be ghostwritten, right? Like,

0:07:23.886 --> 0:07:26.366
<v Speaker 1>there are people whose job is writing op-eds for CEOs.

0:07:26.666 --> 0:07:28.566
<v Speaker 2>I'm going to make this other argument now, which I

0:07:28.606 --> 0:07:31.226
<v Speaker 2>think is maybe more relevant. So I think there's like

0:07:31.286 --> 0:07:36.006
<v Speaker 2>two types of AI use and AI writing. There's basically

0:07:36.066 --> 0:07:39.466
<v Speaker 2>making something more concise or distilling. So for example, if

0:07:39.846 --> 0:07:42.726
<v Speaker 2>Druckenmiller's like, hey, I wrote like, you know, five pages,

0:07:42.786 --> 0:07:44.926
<v Speaker 2>here's all my research, here's all my thoughts. I need

0:07:45.026 --> 0:07:47.386
<v Speaker 2>AI to help me like make this concise and get

0:07:47.426 --> 0:07:49.946
<v Speaker 2>it into like op-ed size. And so I think typically

0:07:49.966 --> 0:07:53.786
<v Speaker 2>AI writing in this case ends up being quite helpful

0:07:53.826 --> 0:07:56.656
<v Speaker 2>because there's a lot to work with and it's distilling

0:07:56.696 --> 0:07:59.976
<v Speaker 2>it down to its core components. The other side of

0:07:59.996 --> 0:08:03.096
<v Speaker 2>AI writing that I see is expanding or padding, where

0:08:03.136 --> 0:08:07.156
<v Speaker 2>somebody's like, here's a few bullet points. Here's a few

0:08:07.196 --> 0:08:10.426
<v Speaker 2>things that I believe. Turn this into an email or

0:08:10.466 --> 0:08:14.006
<v Speaker 2>an op-ed. I think that's where it's really doing a

0:08:14.046 --> 0:08:17.416
<v Speaker 2>disservice to the readers because you're just putting more words

0:08:17.456 --> 0:08:19.396
<v Speaker 2>that are basically padding and don't mean that much.

0:08:19.416 --> 0:08:21.336
<v Speaker 1>Just publish the bullet points, bro.

0:08:21.376 --> 0:08:22.416
<v Speaker 2>Exactly, exactly.

0:08:22.436 --> 0:08:25.676
<v Speaker 1>Yeah, publish it in Axios. They love bullet points over there.

0:08:26.596 --> 0:08:29.416
<v Speaker 1>There's a broader thing that's interesting to me about the

0:08:30.016 --> 0:08:33.876
<v Speaker 1>Druckenmiller Wall Street Journal thing, and that is, like, it

0:08:33.956 --> 0:08:37.946
<v Speaker 1>does make me wonder to what extent we're right now

0:08:38.106 --> 0:08:42.566
<v Speaker 1>in a transitional moment where, you know, I could imagine

0:08:42.586 --> 0:08:44.006
<v Speaker 1>in a year, a few years.

0:08:45.456 --> 0:08:48.336
<v Speaker 1>In many settings, saying, did a person use AI to

0:08:48.356 --> 0:08:50.656
<v Speaker 1>write this, would be like today saying, did they use

0:08:50.736 --> 0:08:54.616
<v Speaker 1>the internet to do the research? Like, probably, and so

0:08:54.656 --> 0:08:59.216
<v Speaker 1>what are the answers? Does that seem plausible to you?

0:08:59.996 --> 0:09:03.226
<v Speaker 2>I think we're absolutely in this space or this time

0:09:03.236 --> 0:09:06.066
<v Speaker 2>period where the norms are completely up in the air

0:09:06.226 --> 0:09:09.586
<v Speaker 2>and people are so polarized on one side or the other,

0:09:09.606 --> 0:09:12.406
<v Speaker 2>or some people are like, I'm going to let AI

0:09:12.666 --> 0:09:15.666
<v Speaker 2>automate my entire online presence. And other people are swearing

0:09:15.986 --> 0:09:20.106
<v Speaker 2>they'll never use AI ever. And so we have this

0:09:20.146 --> 0:09:25.216
<v Speaker 2>really wide range of norms. Nobody's really settled on what

0:09:25.276 --> 0:09:29.896
<v Speaker 2>is acceptable versus unacceptable. I think AI and LLMs, they're

0:09:29.916 --> 0:09:33.216
<v Speaker 2>very powerful technology. They could do a lot of work

0:09:33.316 --> 0:09:36.096
<v Speaker 2>for me. They can go do research for me. They

0:09:36.116 --> 0:09:39.696
<v Speaker 2>can compile this into a spreadsheet for me to read

0:09:39.776 --> 0:09:40.746
<v Speaker 2>and peruse.

0:09:40.886 --> 0:09:43.676
<v Speaker 1>They can determine whether people are using AI to write.

0:09:44.696 --> 0:09:48.516
<v Speaker 2>Yeah. But yeah, I think the answer is we really

0:09:48.596 --> 0:09:53.276
<v Speaker 2>haven't settled on any norms societally. And the norms that

0:09:53.316 --> 0:09:56.196
<v Speaker 2>we will settle to are probably that some degree of

0:09:56.216 --> 0:09:59.806
<v Speaker 2>AI use is okay, but using AI to replace your

0:09:59.866 --> 0:10:03.966
<v Speaker 2>voice completely, especially in settings where it's going to be

0:10:04.046 --> 0:10:08.846
<v Speaker 2>read by thousands or millions, is probably less acceptable. Yeah.

0:10:08.986 --> 0:10:11.736
<v Speaker 1>Well, and disclosure. I do feel like disclosure can solve

0:10:11.776 --> 0:10:14.836
<v Speaker 1>a lot. It's also interesting to me. You see this

0:10:14.916 --> 0:10:17.986
<v Speaker 1>certainly on LinkedIn and on Twitter. There are a lot

0:10:18.016 --> 0:10:21.826
<v Speaker 1>of things that are so obviously AI. And initially, I

0:10:22.046 --> 0:10:24.526
<v Speaker 1>was like, don't people know? But now I think maybe

0:10:24.566 --> 0:10:27.446
<v Speaker 1>people know and don't care. Like, I don't know. It

0:10:27.486 --> 0:10:30.216
<v Speaker 1>does feel... I want to be clear, I don't like

0:10:30.376 --> 0:10:32.696
<v Speaker 1>AI prose. I'm not speaking of a moral objection, but

0:10:32.736 --> 0:10:36.756
<v Speaker 1>just as a matter of taste. And then there is

0:10:36.796 --> 0:10:38.916
<v Speaker 1>a little bit, like, it feels a little rude. It

0:10:38.956 --> 0:10:41.646
<v Speaker 1>feels a little spammy. Like, I'm reading this thing, and

0:10:41.666 --> 0:10:44.566
<v Speaker 1>this person didn't even take the time to lightly edit

0:10:44.626 --> 0:10:47.866
<v Speaker 1>it to get rid of the obvious AI-isms.

0:10:47.886 --> 0:10:50.576
<v Speaker 2>Yeah, or if you aren't going to take the time

0:10:50.616 --> 0:10:53.276
<v Speaker 2>to write it yourself, then I'm so much less inclined

0:10:53.346 --> 0:10:53.786
<v Speaker 2>to read it.

0:10:54.156 --> 0:10:56.646
<v Speaker 1>So the question I have is, do the people who

0:10:56.706 --> 0:10:59.526
<v Speaker 1>are posting that know that it is obviously AI and

0:10:59.546 --> 0:11:01.506
<v Speaker 1>they just don't care? I mean, I guess it varies,

0:11:01.586 --> 0:11:03.686
<v Speaker 1>but that's a weird one to me still.

0:11:03.766 --> 0:11:05.326
<v Speaker 2>I think there's a little bit of a bell curve.

0:11:05.716 --> 0:11:07.616
<v Speaker 2>There's a lot of people who are either new to

0:11:07.696 --> 0:11:11.076
<v Speaker 2>using AI or they haven't really used that much AI before,

0:11:11.116 --> 0:11:13.956
<v Speaker 2>and they can't really look at text and immediately grok

0:11:13.976 --> 0:11:17.676
<v Speaker 2>that it's AI-generated. They can't immediately tell. And so, yeah,

0:11:17.816 --> 0:11:19.906
<v Speaker 2>obviously you have the people who are just like, don't

0:11:19.986 --> 0:11:21.736
<v Speaker 2>use AI much. And then you also have the people

0:11:21.746 --> 0:11:25.016
<v Speaker 2>who like just discovered this technology and they're like, wow,

0:11:25.156 --> 0:11:27.236
<v Speaker 2>it like writes so well, this is amazing. And I

0:11:27.236 --> 0:11:31.396
<v Speaker 2>don't think they fully realized that like regular AI users

0:11:31.876 --> 0:11:35.156
<v Speaker 2>can read this and immediately smell that it's AI generated. Yeah. Then,

0:11:35.236 --> 0:11:36.566
<v Speaker 2>then you get to the middle of the bell curve

0:11:36.586 --> 0:11:39.846
<v Speaker 2>where it's like, yeah, like, like people who use AI

0:11:40.566 --> 0:11:42.846
<v Speaker 2>on a somewhat regular basis, they, they can kind of

0:11:42.866 --> 0:11:44.846
<v Speaker 2>just tell. And I think you get to the other

0:11:44.926 --> 0:11:46.926
<v Speaker 2>end where there's people who are like so deep in

0:11:47.026 --> 0:11:51.446
<v Speaker 2>AI psychosis that, that they also can't tell because like 90%

0:11:51.446 --> 0:11:54.466
<v Speaker 2>of what they're reading is like AI already. They talk

0:11:54.506 --> 0:11:56.686
<v Speaker 2>to chatbots more than other people and they just like

0:11:57.076 --> 0:12:00.376
<v Speaker 2>have lost this ability to differentiate. Uh-huh.

0:12:00.916 --> 0:12:02.936
<v Speaker 1>So maybe we'll all be at that far end of

0:12:02.976 --> 0:12:03.956
<v Speaker 1>the curve in a year.

0:12:04.196 --> 0:12:05.016
<v Speaker 2>I really hope not.

0:12:05.036 --> 0:12:10.446
<v Speaker 1>Yeah, I suppose I also hope not. So the companies

0:12:10.486 --> 0:12:17.146
<v Speaker 1>that are making frontier models, Anthropic, OpenAI, arguably Alphabet, Google,

0:12:17.886 --> 0:12:23.426
<v Speaker 1>are giant companies with wild amounts of money, full of geniuses.

0:12:23.946 --> 0:12:27.026
<v Speaker 1>You'd think those companies could just do what you're doing.

0:12:27.186 --> 0:12:31.246
<v Speaker 1>They could just build their own AI detectors. Why don't they?

0:12:31.726 --> 0:12:35.046
<v Speaker 2>I agree. I don't disagree here. But I also think

0:12:35.116 --> 0:12:39.296
<v Speaker 2>that this is just not in their top 10 priority list.

0:12:40.256 --> 0:12:43.736
<v Speaker 2>They're building AGI. They're automating white-collar work.

0:12:44.226 --> 0:12:47.326
<v Speaker 1>Probably the right answer. I mean, there's an answer, which

0:12:47.386 --> 0:12:52.006
<v Speaker 1>is like, is it contrary to their incentives to do

0:12:52.046 --> 0:12:56.036
<v Speaker 1>what you're doing, right? Is it in their interest for

0:12:56.096 --> 0:12:59.196
<v Speaker 1>people to be able to distinguish AI pros from human pros,

0:12:59.236 --> 0:13:00.756
<v Speaker 1>or is it contrary to their interest?

0:13:00.836 --> 0:13:02.956
<v Speaker 2>I think it is contrary to their interest. There was

0:13:02.976 --> 0:13:07.136
<v Speaker 2>an interesting article that I was exploring a couple of

0:13:07.156 --> 0:13:11.936
<v Speaker 2>years ago, actually, when OpenAI had watermarking technology, they'd built it,

0:13:12.336 --> 0:13:14.376
<v Speaker 2>but then they didn't want to release it. There was

0:13:14.396 --> 0:13:16.336
<v Speaker 2>a lot of internal politics on this, and this was

0:13:16.436 --> 0:13:20.316
<v Speaker 2>largely because they were afraid it would hurt their core

0:13:20.376 --> 0:13:23.436
<v Speaker 2>user base, which was at least a plurality of students

0:13:23.476 --> 0:13:23.956
<v Speaker 2>at this time.

0:13:24.416 --> 0:13:26.776
<v Speaker 1>They would get caught cheating if there was a watermark.

0:13:26.836 --> 0:13:27.796
<v Speaker 1>It's basically what you're saying.

0:13:27.836 --> 0:13:30.216
<v Speaker 2>They would get caught cheating, or they would churn to

0:13:30.716 --> 0:13:32.686
<v Speaker 2>a different AI service that didn't have a watermark.

0:13:33.036 --> 0:13:37.206
<v Speaker 1>So you brought up watermarks, so let's talk about watermarks.

0:13:37.806 --> 0:13:41.526
<v Speaker 1>The EU, as I understand, just passed a law requiring...

0:13:41.566 --> 0:13:45.066
<v Speaker 1>watermarks on text from language models. Is that true?

0:13:45.146 --> 0:13:49.006
<v Speaker 2>Yes, that's true. And OpenAI and Anthropic are both working

0:13:49.046 --> 0:13:51.526
<v Speaker 2>on this. Google already watermarks text outputs.

0:13:52.186 --> 0:13:53.426
<v Speaker 1>Is that bad for your business?

0:13:54.686 --> 0:13:56.826
<v Speaker 2>I think it's really good that people are taking this

0:13:56.866 --> 0:14:00.006
<v Speaker 2>problem seriously. It is competitive with us, but I think

0:14:00.106 --> 0:14:03.266
<v Speaker 2>Pangram has a lot of advantages that watermarks don't have,

0:14:03.486 --> 0:14:05.386
<v Speaker 2>which is that a watermark is just going to tell

0:14:05.406 --> 0:14:07.756
<v Speaker 2>you either Claude was here or not, and Pangram will

0:14:07.796 --> 0:14:10.196
<v Speaker 2>be able to tell you with higher granularity of like,

0:14:10.736 --> 0:14:12.716
<v Speaker 2>What was the degree of AI assistance? Was it just

0:14:12.896 --> 0:14:14.586
<v Speaker 2>helping or did it write the whole thing?

0:14:14.606 --> 0:14:20.946
<v Speaker 1>I mean, presumably, there's some universe where Claude outputs the

0:14:20.966 --> 0:14:24.326
<v Speaker 1>copy that's watermarked, and then you literally just retype it

0:14:24.406 --> 0:14:28.866
<v Speaker 1>into a Google Doc. I mean, naively, I would think

0:14:28.906 --> 0:14:31.386
<v Speaker 1>the watermark would not follow. Or is the watermark somehow

0:14:31.526 --> 0:14:34.096
<v Speaker 1>encoded in the prose so that if you retype it,

0:14:34.126 --> 0:14:34.706
<v Speaker 1>it's still there?

0:14:34.806 --> 0:14:40.026
<v Speaker 2>Yes, the watermark is statistically encoded in the word choices themselves.

0:14:40.046 --> 0:14:43.706
<v Speaker 1>Oh, that is rad. So even retyping it, the watermark

0:14:43.766 --> 0:14:44.326
<v Speaker 1>is still there.

0:14:44.806 --> 0:14:50.326
<v Speaker 2>Yes. With that said, you could run some automated paraphraser

0:14:50.406 --> 0:14:53.386
<v Speaker 2>to just paraphrase all the words, and that would erase

0:14:53.426 --> 0:14:53.966
<v Speaker 2>the watermark.

0:14:54.286 --> 0:14:57.786
<v Speaker 1>Yes. Well, so there are humanizers now, right? There are

0:14:59.066 --> 0:15:03.306
<v Speaker 1>things you can upload your language model pros into that

0:15:03.386 --> 0:15:07.086
<v Speaker 1>claim to evade detection. Although I will say I tried one,

0:15:07.106 --> 0:15:09.716
<v Speaker 1>I won't name it, but I tried one in preparing

0:15:09.736 --> 0:15:11.836
<v Speaker 1>for this interview, and you'll be glad to know it

0:15:11.856 --> 0:15:14.396
<v Speaker 1>didn't work. I had the language model output pros, I

0:15:14.436 --> 0:15:16.656
<v Speaker 1>ran it through a humanizer, put it into PanGram, and

0:15:16.676 --> 0:15:18.076
<v Speaker 1>PanGram said 100% AI.

0:15:18.236 --> 0:15:21.816
<v Speaker 2>Amazing. Yeah, I mean, this is part of the adversarial

0:15:21.876 --> 0:15:24.766
<v Speaker 2>nature of the business is We are also training on

0:15:24.866 --> 0:15:28.546
<v Speaker 2>humanizer outputs because we need to make sure that pangram

0:15:28.906 --> 0:15:33.246
<v Speaker 2>can detect anything that's been run through a humanizer. Otherwise,

0:15:33.306 --> 0:15:35.946
<v Speaker 2>it would kind of be trivial to evade pangram.

0:15:36.586 --> 0:15:39.546
<v Speaker 1>Why can't they beat you? I would think you could

0:15:39.586 --> 0:15:43.886
<v Speaker 1>be at a degree of randomness at the level of

0:15:44.486 --> 0:15:50.216
<v Speaker 1>word choice and syntax that would defeat you. Why can't they?

0:15:50.516 --> 0:15:52.836
<v Speaker 2>I think these are kind of like two, there's two

0:15:52.936 --> 0:15:57.136
<v Speaker 2>competing poles for text when you're humanizing. You want it

0:15:57.176 --> 0:16:02.776
<v Speaker 2>to be coherent and, you know, retain its logical flow.

0:16:02.996 --> 0:16:05.356
<v Speaker 2>And then on the other side, you want to just

0:16:05.436 --> 0:16:07.656
<v Speaker 2>degrade it or perturb it a little bit enough that

0:16:07.696 --> 0:16:11.266
<v Speaker 2>it is outside of the range of AI detectors. There

0:16:11.426 --> 0:16:15.226
<v Speaker 2>are humanizers that can beat pangram and you could do

0:16:15.266 --> 0:16:19.066
<v Speaker 2>this by just like perturbing the text way more just

0:16:19.186 --> 0:16:19.746
<v Speaker 2>a lot more.

0:16:19.966 --> 0:16:24.566
<v Speaker 1>Well, sure. I mean, there's a difference between degrading and perturbing, right? Like,

0:16:25.086 --> 0:16:28.266
<v Speaker 1>you can make it really bad, but that's obviously not useful.

0:16:28.426 --> 0:16:31.726
<v Speaker 2>Well, I think degrading is just a more extreme version

0:16:31.786 --> 0:16:32.386
<v Speaker 2>of perturbing.

0:16:32.966 --> 0:16:35.446
<v Speaker 1>Well, you could improve. You could perturb it a lot

0:16:35.486 --> 0:16:37.106
<v Speaker 1>and improve it. Oh, yeah, yeah.

0:16:37.126 --> 0:16:39.406
<v Speaker 2>But these humanizers, they don't have the resources to actually

0:16:39.476 --> 0:16:40.146
<v Speaker 2>do that, right?

0:16:40.216 --> 0:16:40.696
<v Speaker 1>Yeah.

0:16:41.016 --> 0:16:45.156
<v Speaker 2>Most of them are, like, one- to ten-person companies.

0:16:45.716 --> 0:16:48.216
<v Speaker 1>There's a more fundamental question here that is interesting to me,

0:16:48.236 --> 0:16:52.326
<v Speaker 1>and I don't really understand the answer, which is, like,

0:16:52.566 --> 0:16:55.526
<v Speaker 1>why does AI slop all sound the same? You know

0:16:55.546 --> 0:16:57.366
<v Speaker 1>what I mean? Like, that's the thing that's so annoying.

0:16:57.386 --> 0:17:00.706
<v Speaker 1>Why can't you just turn up the volume, not on, like,

0:17:00.926 --> 0:17:04.426
<v Speaker 1>make it bad, but just, like, don't use that same rhythm.

0:17:04.466 --> 0:17:06.886
<v Speaker 1>Don't do, like, the one sentence. Don't use these annoying

0:17:06.966 --> 0:17:10.306
<v Speaker 1>words that are AI words. Like, why is that at

0:17:10.386 --> 0:17:11.666
<v Speaker 1>a technical level?

0:17:12.046 --> 0:17:15.226
<v Speaker 2>It's really hard to say. I think... So there's a

0:17:15.246 --> 0:17:18.526
<v Speaker 2>concept in machine learning called mode collapse. And that means like,

0:17:18.906 --> 0:17:23.326
<v Speaker 2>you know, once an AI model learns what is best

0:17:23.626 --> 0:17:26.846
<v Speaker 2>or most common, which is the mode, then it will

0:17:27.126 --> 0:17:30.506
<v Speaker 2>kind of like collapse the edges of its distribution and

0:17:30.546 --> 0:17:32.666
<v Speaker 2>just output the mode much more often.

0:17:33.126 --> 0:17:36.526
<v Speaker 1>Yes. The mode being the modal word, the most common word.

0:17:36.546 --> 0:17:39.386
<v Speaker 2>Yeah, the most common word or phrase or sentence construction.

0:17:39.406 --> 0:17:42.266
<v Speaker 2>I think that's part of it. And I think also...

0:17:42.536 --> 0:17:45.706
<v Speaker 2>a lot of these labs, they do post-training. They'll create

0:17:45.806 --> 0:17:49.206
<v Speaker 2>a reward model and they'll give the language model a reward.

0:17:49.406 --> 0:17:52.846
<v Speaker 2>And so I can only suspect that there's somebody in

0:17:52.926 --> 0:17:57.096
<v Speaker 2>here who's saying there's some reward for, quote, like good writing.

0:17:57.956 --> 0:18:01.976
<v Speaker 2>And that might include, you know, writing with em dashes

0:18:02.136 --> 0:18:05.176
<v Speaker 2>is probably correlated with good writing in the pre-AI world.

0:18:05.736 --> 0:18:08.206
<v Speaker 2>Same thing with the like Like, it's not just X

0:18:08.246 --> 0:18:09.886
<v Speaker 2>but Y sort of metaphors.

0:18:10.006 --> 0:18:12.026
<v Speaker 1>Yes. That's another one that I have taken out of

0:18:12.086 --> 0:18:13.696
<v Speaker 1>my own writing, actually. Yeah, yeah.

0:18:13.756 --> 0:18:16.956
<v Speaker 2>Like, it's a very reasonable construction, but then you feed

0:18:16.976 --> 0:18:20.116
<v Speaker 2>it into the reward model, and then the AI learns

0:18:20.136 --> 0:18:21.656
<v Speaker 2>in its prose to turn that up to 11.

0:18:21.656 --> 0:18:23.176
<v Speaker 1>It likes it too much, yeah.

0:18:23.416 --> 0:18:26.436
<v Speaker 2>Yeah. So it just overuses what would have normally been

0:18:26.456 --> 0:18:27.876
<v Speaker 2>considered good writing.

0:18:31.476 --> 0:18:43.016
<v Speaker 1>We'll be back in just a minute. Okay, let's talk

0:18:43.056 --> 0:18:45.436
<v Speaker 1>about false positives, right? This is a thing people care

0:18:45.476 --> 0:18:48.176
<v Speaker 1>about and have written about. So obviously in any test,

0:18:48.196 --> 0:18:50.056
<v Speaker 1>you can have a false positive or a false negative.

0:18:50.096 --> 0:18:52.416
<v Speaker 1>A false negative, you're saying this is human generated and

0:18:52.456 --> 0:18:55.476
<v Speaker 1>actually it's AI. That one people don't get so upset about.

0:18:55.496 --> 0:18:59.156
<v Speaker 1>The one people are really afraid of is wrongly accused, right?

0:18:59.196 --> 0:19:02.776
<v Speaker 1>Pangram says it was AI. Actually, it was written by

0:19:02.816 --> 0:19:06.896
<v Speaker 1>a person. I've seen you say one in 10,000 is

0:19:07.196 --> 0:19:11.516
<v Speaker 1>the false positive rate. And I've also seen outside studies that,

0:19:12.066 --> 0:19:14.806
<v Speaker 1>find a very low false positive rate, a similar order

0:19:14.826 --> 0:19:16.966
<v Speaker 1>of magnitude, one from the University of Chicago I found

0:19:17.006 --> 0:19:20.876
<v Speaker 1>particularly compelling. But like, I don't know how many writing

0:19:20.916 --> 0:19:23.286
<v Speaker 1>assignments students have in high school and college, but it's

0:19:23.496 --> 0:19:27.716
<v Speaker 1>probably order of magnitude of hundreds, right? And so that

0:19:27.756 --> 0:19:29.876
<v Speaker 1>means that some share of students are going to be

0:19:29.936 --> 0:19:35.476
<v Speaker 1>wrongly accused, right? If it's 500 writing assignments, then it

0:19:35.496 --> 0:19:38.676
<v Speaker 1>would be 5% of students will be wrongly accused by

0:19:38.716 --> 0:19:41.316
<v Speaker 1>Pan Graham of using AI to write a thing that

0:19:41.336 --> 0:19:42.056
<v Speaker 1>they actually wrote?

0:19:42.416 --> 0:19:45.476
<v Speaker 2>Yeah, I do think like 1 in 10,000 is beyond

0:19:45.516 --> 0:19:48.996
<v Speaker 2>the threshold where like you can use this as a

0:19:49.016 --> 0:19:52.686
<v Speaker 2>tool and generally typically be confident that when it says

0:19:52.746 --> 0:19:53.866
<v Speaker 2>it's AI, it's correct.

0:19:54.186 --> 0:19:56.726
<v Speaker 1>It's true. That's definitely true. Like, I mean, I will

0:19:56.746 --> 0:19:59.656
<v Speaker 1>say just I was actually accused by a teacher in

0:19:59.696 --> 0:20:02.236
<v Speaker 1>high school of plagiarizing. That's the old school. And I

0:20:02.276 --> 0:20:05.676
<v Speaker 1>had not plagiarized, for the record. And so that is

0:20:05.736 --> 0:20:08.666
<v Speaker 1>the old school human version of this. And I'm sure

0:20:08.726 --> 0:20:12.846
<v Speaker 1>his error rate was higher than 1 in 10,000. But

0:20:12.906 --> 0:20:14.886
<v Speaker 1>I am sensitive to it. Like, that feeling of being

0:20:14.926 --> 0:20:17.046
<v Speaker 1>wrongly accused is a terrible feeling. Mm-hmm.

0:20:17.586 --> 0:20:19.896
<v Speaker 2>Yeah, so I think one thing that pangram helps with

0:20:19.996 --> 0:20:24.356
<v Speaker 2>actually is it's much better than like the average human intuition.

0:20:24.736 --> 0:20:27.666
<v Speaker 2>And it's also better than any other AI detector. So

0:20:27.746 --> 0:20:32.026
<v Speaker 2>because of that, the existence of pangram is, I truly

0:20:32.046 --> 0:20:35.826
<v Speaker 2>believe this, reducing the number of false accusations for AI

0:20:35.956 --> 0:20:38.156
<v Speaker 2>use in a scenario like education.

0:20:38.956 --> 0:20:42.036
<v Speaker 1>Yeah, that's fair. So like notionally, like, of course, teachers

0:20:42.076 --> 0:20:43.796
<v Speaker 1>are on the lookout for AI one way or the

0:20:43.876 --> 0:20:45.476
<v Speaker 1>other if they want students to write it.

0:20:45.496 --> 0:20:47.776
<v Speaker 2>Exactly. And then the other side, I think, which is

0:20:47.816 --> 0:20:53.036
<v Speaker 2>really important, is that it's not the only source of information.

0:20:53.556 --> 0:20:56.806
<v Speaker 2>Once Pangram says that something's AI, we can always go deeper.

0:20:56.886 --> 0:21:01.146
<v Speaker 2>We can either ask the student for drafts. If you

0:21:01.266 --> 0:21:04.666
<v Speaker 2>use Google Docs, Pangram actually has this Chrome extension where

0:21:04.686 --> 0:21:07.586
<v Speaker 2>you could see the full revision history, you could see

0:21:07.626 --> 0:21:09.006
<v Speaker 2>that the document being typed out.

0:21:09.186 --> 0:21:11.946
<v Speaker 1>And that history is available even without PanGram, right?

0:21:11.966 --> 0:21:12.366
<v Speaker 2>Exactly.

0:21:12.466 --> 0:21:14.476
<v Speaker 1>And if you're using Chrome, you can see the version

0:21:14.496 --> 0:21:15.316
<v Speaker 1>history and go back.

0:21:15.676 --> 0:21:19.216
<v Speaker 2>Exactly. Yes. Yeah. So that version history is there. But

0:21:19.596 --> 0:21:22.176
<v Speaker 2>I think PanGram is very important because you don't want

0:21:22.196 --> 0:21:24.516
<v Speaker 2>to go look at the version history for every single doc.

0:21:24.836 --> 0:21:27.506
<v Speaker 2>You only want to look into it once you suspect

0:21:27.586 --> 0:21:30.286
<v Speaker 2>that something was wrong or there are some AIUs there.

0:21:30.906 --> 0:21:33.066
<v Speaker 1>That's funny. I thought, well, you could automate looking at

0:21:33.106 --> 0:21:34.586
<v Speaker 1>the version history. And then I was like, oh, but

0:21:34.606 --> 0:21:37.306
<v Speaker 1>you could also automate a little script that would make

0:21:37.326 --> 0:21:40.066
<v Speaker 1>it look like you wrote it. It's the adversarial thing.

0:21:41.046 --> 0:21:42.746
<v Speaker 1>It is amazing. I was reading an article in New

0:21:42.786 --> 0:21:44.846
<v Speaker 1>York Magazine about students using AI to cheat. And one

0:21:44.866 --> 0:21:46.506
<v Speaker 1>of the things they pointed out is like how much

0:21:46.666 --> 0:21:50.966
<v Speaker 1>time students spend cheating, like trying to use AI and

0:21:51.006 --> 0:21:53.586
<v Speaker 1>not get caught. And like that amount of time you

0:21:53.626 --> 0:21:56.086
<v Speaker 1>could have written the paper, right? Which is a classic thing,

0:21:56.126 --> 0:21:57.666
<v Speaker 1>but maybe it's more fun to cheat. Well, yeah.

0:21:57.726 --> 0:22:00.196
<v Speaker 2>I mean, I think that's part of the like, friction,

0:22:00.316 --> 0:22:04.116
<v Speaker 2>like adding friction to this cheating process where fewer students

0:22:04.156 --> 0:22:06.836
<v Speaker 2>are going to do it if it is time consuming

0:22:06.876 --> 0:22:10.096
<v Speaker 2>to cheat. If it's just one prompt, I think that's

0:22:10.156 --> 0:22:14.216
<v Speaker 2>where like a lot of students and faculty, like everyone's

0:22:14.236 --> 0:22:16.776
<v Speaker 2>kind of been frustrated with this problem. It also sucks

0:22:16.796 --> 0:22:19.856
<v Speaker 2>when your peers are doing one sentence prompts and getting

0:22:19.896 --> 0:22:20.416
<v Speaker 2>away with it.

0:22:21.116 --> 0:22:24.946
<v Speaker 1>Right. That's a bad equilibrium. That's a really bad equilibrium. So, okay,

0:22:24.966 --> 0:22:27.846
<v Speaker 1>so out of every 10,000 times you say AI had

0:22:28.046 --> 0:22:30.266
<v Speaker 1>anything to do with it, you only get it wrong once.

0:22:30.506 --> 0:22:32.946
<v Speaker 2>Correct. It's a little bit more of a spectrum in

0:22:32.986 --> 0:22:38.876
<v Speaker 2>the middle when somebody believes that they had 50% input

0:22:38.996 --> 0:22:42.416
<v Speaker 2>into the document and AI had 50% input and then

0:22:42.456 --> 0:22:46.456
<v Speaker 2>Paragram said it's 100% AI. Like, this is sort of

0:22:46.496 --> 0:22:49.816
<v Speaker 2>the gray area where it's much harder to measure if

0:22:49.836 --> 0:22:50.516
<v Speaker 2>we're right or not.

0:22:50.616 --> 0:22:54.126
<v Speaker 1>Uh-huh. And so that's the area where you get it

0:22:54.166 --> 0:22:57.066
<v Speaker 1>wrong more is kind of at that margin. So it's like, no, no,

0:22:57.226 --> 0:22:59.696
<v Speaker 1>I wrote it and I got some edits from AI,

0:23:00.216 --> 0:23:04.256
<v Speaker 1>but PanGram returns 100% AI. Like that happens more often

0:23:04.296 --> 0:23:05.136
<v Speaker 1>than 1 in 10,000.

0:23:05.136 --> 0:23:09.276
<v Speaker 2>Yeah, that happens at least for like light AI assistants

0:23:09.336 --> 0:23:13.686
<v Speaker 2>or medium AI assistants. It's like a few percent of

0:23:13.726 --> 0:23:15.666
<v Speaker 2>the time where we say it's still like 100% AI.

0:23:17.336 --> 0:23:21.096
<v Speaker 1>So a few percent is orders of magnitude higher than

0:23:21.176 --> 0:23:23.996
<v Speaker 1>one in 10,000. It happens kind of a lot.

0:23:24.636 --> 0:23:27.196
<v Speaker 2>We try to be very transparent about all of our benchmarks.

0:23:27.836 --> 0:23:30.876
<v Speaker 2>I think this is also the area of greatest debate

0:23:31.016 --> 0:23:35.416
<v Speaker 2>where it's not actually so black and white. What the

0:23:35.456 --> 0:23:40.256
<v Speaker 2>degree of AI assistance was, people on average tend to under-disclose.

0:23:40.276 --> 0:23:42.776
<v Speaker 2>They're like, oh, I use AI to help me. I

0:23:42.816 --> 0:23:45.516
<v Speaker 2>talked to someone who's like, I used AI for copy edits.

0:23:45.676 --> 0:23:47.336
<v Speaker 2>And then you go through what that means. It's like

0:23:47.616 --> 0:23:51.596
<v Speaker 2>they actually, like, every word was produced by AI. And

0:23:52.696 --> 0:23:56.396
<v Speaker 2>it had gone through so many revisions with AI. And

0:23:56.436 --> 0:23:58.436
<v Speaker 2>so I think this is the biggest gray area where

0:23:59.016 --> 0:24:02.816
<v Speaker 2>Pangram is not going to be, like, a perfect oracle

0:24:02.936 --> 0:24:05.336
<v Speaker 2>and tell you this was the exact prompt and these

0:24:05.356 --> 0:24:08.076
<v Speaker 2>were the exact human edits. But I think it can, like,

0:24:08.096 --> 0:24:09.176
<v Speaker 2>get approximately there.

0:24:10.376 --> 0:24:14.346
<v Speaker 1>Are there... groups of people or kinds of speakers where

0:24:14.386 --> 0:24:18.426
<v Speaker 1>pangram is worse at detecting whether their writing is their

0:24:18.506 --> 0:24:20.086
<v Speaker 1>own or generated by AI?

0:24:20.776 --> 0:24:25.576
<v Speaker 2>So we've run this on three different groups. I think

0:24:25.596 --> 0:24:29.376
<v Speaker 2>there's been different studies in the past that have found

0:24:29.396 --> 0:24:35.706
<v Speaker 2>that AI detectors are biased against English as second language speakers.

0:24:36.406 --> 0:24:41.186
<v Speaker 2>There's also been questions of if AI detectors are biased

0:24:41.226 --> 0:24:47.366
<v Speaker 2>against autistic or neurodivergent speakers. And so what we've done

0:24:47.526 --> 0:24:51.776
<v Speaker 2>is we ran studies where we looked at 25,000 texts

0:24:52.936 --> 0:24:56.176
<v Speaker 2>by English as second language speakers and found that there's

0:24:56.356 --> 0:25:00.376
<v Speaker 2>no elevated false positive rate. We have one false positive

0:25:00.496 --> 0:25:05.316
<v Speaker 2>in the 25,000. And then so similarly, somebody else who

0:25:05.396 --> 0:25:09.666
<v Speaker 2>is not us asked for credits to run a similar

0:25:09.726 --> 0:25:14.306
<v Speaker 2>study for autistic speakers and they did a really great job.

0:25:14.366 --> 0:25:17.786
<v Speaker 2>They had like a 20 page report on their findings

0:25:17.846 --> 0:25:21.196
<v Speaker 2>and they also found no bias against autistic speakers, which

0:25:21.216 --> 0:25:25.296
<v Speaker 2>is really great. And then the third one that we've

0:25:25.336 --> 0:25:28.236
<v Speaker 2>looked at was just like race. Cause I think this

0:25:28.276 --> 0:25:31.906
<v Speaker 2>has also been a question and we again found no

0:25:32.336 --> 0:25:37.716
<v Speaker 2>statistically significant difference, which it was really cool to see. What?

0:25:37.856 --> 0:25:38.176
<v Speaker 1>Yes.

0:25:38.396 --> 0:25:38.616
<v Speaker 2>Yes.

0:25:38.736 --> 0:25:40.916
<v Speaker 1>One hopes that would not be a problem. You could

0:25:40.956 --> 0:25:43.636
<v Speaker 1>imagine how for someone who was not a native speaker,

0:25:43.696 --> 0:25:45.936
<v Speaker 1>for example, you might have a higher rate of false positives.

0:25:46.356 --> 0:25:48.826
<v Speaker 1>Was it a problem in the past? Like were earlier

0:25:48.886 --> 0:25:52.106
<v Speaker 1>versions of PanGram less reliable in that way?

0:25:52.526 --> 0:25:54.766
<v Speaker 2>I would say like PanGram 2, like definitely had a

0:25:54.766 --> 0:25:58.046
<v Speaker 2>bit of this issue. And then starting like PanGram 3,

0:25:58.046 --> 0:26:01.006
<v Speaker 2>we were taking it very seriously. But I think every,

0:26:02.076 --> 0:26:04.596
<v Speaker 2>we've had a lot of candidate models that were biased

0:26:04.696 --> 0:26:08.066
<v Speaker 2>against English second language speakers and And so because of that,

0:26:08.146 --> 0:26:10.416
<v Speaker 2>we kind of threw away the model and never released it.

0:26:11.226 --> 0:26:12.206
<v Speaker 1>And when was Pangram 2?

0:26:12.186 --> 0:26:16.506
<v Speaker 2>How long ago was that? Like a year and a

0:26:16.546 --> 0:26:20.896
<v Speaker 2>half ago. Even Pangram 2, like our false positive rate

0:26:20.916 --> 0:26:24.896
<v Speaker 2>was like much lower than the other AI detectors. But

0:26:25.236 --> 0:26:28.416
<v Speaker 2>I think it was still like compared to our baseline

0:26:28.436 --> 0:26:32.186
<v Speaker 2>false positive rate, it was elevated on ESL. And I

0:26:32.226 --> 0:26:35.646
<v Speaker 2>think like part of the difficulty here is going back

0:26:35.666 --> 0:26:38.236
<v Speaker 2>to the humanizers. a lot of them are trying to

0:26:38.356 --> 0:26:42.896
<v Speaker 2>inject spelling mistakes, grammar mistakes as a way to evade

0:26:42.996 --> 0:26:48.936
<v Speaker 2>AI detection. And so training on these naively will make

0:26:48.996 --> 0:26:53.696
<v Speaker 2>your model correlate these spelling and grammar mistakes with AI, actually,

0:26:53.776 --> 0:26:54.876
<v Speaker 2>which is not correct.

0:26:54.896 --> 0:26:57.736
<v Speaker 1>Well, only if those are occurring at a higher rate

0:26:57.776 --> 0:27:00.026
<v Speaker 1>in the humanizers than they are in the human texts

0:27:00.046 --> 0:27:01.626
<v Speaker 1>you're putting in, right? Yeah.

0:27:02.126 --> 0:27:05.926
<v Speaker 2>I think the humanizers, some of them are perturbing and

0:27:05.966 --> 0:27:09.416
<v Speaker 2>degrading the text more than your average human. So it's

0:27:09.436 --> 0:27:11.956
<v Speaker 2>taking it like all the way down to the other side. Yeah.

0:27:12.836 --> 0:27:15.356
<v Speaker 1>There have been a number of cases where, you know,

0:27:15.416 --> 0:27:17.856
<v Speaker 1>Pangram found a piece of writing to be AI generated.

0:27:17.896 --> 0:27:20.836
<v Speaker 1>The person said, no, it wasn't. I wrote it. Has

0:27:20.856 --> 0:27:22.876
<v Speaker 1>there been a case where the person was validated? A

0:27:23.096 --> 0:27:24.056
<v Speaker 1>high profile case?

0:27:24.676 --> 0:27:28.456
<v Speaker 2>Yeah. So there was like one case, Taylor Lorenz had

0:27:28.516 --> 0:27:31.706
<v Speaker 2>this like article in Vanity Fair. So Pangram has a

0:27:31.686 --> 0:27:37.826
<v Speaker 2>50 word minimum. Somebody selected a 54 word segment and

0:27:37.846 --> 0:27:40.846
<v Speaker 2>Pangram said this was AI generated. But what they did

0:27:40.866 --> 0:27:43.966
<v Speaker 2>was they just posted the like a hundred percent AI

0:27:44.386 --> 0:27:46.606
<v Speaker 2>for the 54 word segment. And so then I looked

0:27:46.766 --> 0:27:50.226
<v Speaker 2>into it. If I checked like the full Vandy fair article,

0:27:50.266 --> 0:27:53.306
<v Speaker 2>Pangram actually said a hundred percent human. And then, you know,

0:27:53.346 --> 0:27:56.606
<v Speaker 2>Taylor's like, Hey, like here's my edit history. Like we

0:27:56.636 --> 0:27:58.516
<v Speaker 2>went through a lot of provisions with, with an editor,

0:27:58.576 --> 0:28:01.096
<v Speaker 2>like this is all my writing. And so, yeah, like it's,

0:28:01.576 --> 0:28:05.316
<v Speaker 2>it was absolutely a false positive and, Yeah, partially because

0:28:05.356 --> 0:28:07.496
<v Speaker 2>it was a small piece of text and partially, I think,

0:28:07.536 --> 0:28:10.116
<v Speaker 2>because this person was kind of using pangram in an

0:28:10.256 --> 0:28:12.636
<v Speaker 2>inappropriate way of, like, I don't know, trying to go

0:28:12.676 --> 0:28:15.566
<v Speaker 2>for the gotcha rather than, like, going for the full story.

0:28:15.606 --> 0:28:19.146
<v Speaker 1>Well, that 1 in 10,000 false positive rate, is that

0:28:19.186 --> 0:28:21.466
<v Speaker 1>contingent on some minimum number of words? And if so,

0:28:21.486 --> 0:28:22.146
<v Speaker 1>what number of words?

0:28:23.166 --> 0:28:26.556
<v Speaker 2>This is aggregate over positive. all of our texts, but

0:28:26.936 --> 0:28:28.816
<v Speaker 2>it's a little bit higher for 50 words.

0:28:28.896 --> 0:28:31.076
<v Speaker 1>If you put in 50 words, is the false positive

0:28:31.116 --> 0:28:31.986
<v Speaker 1>rate notably higher?

0:28:32.126 --> 0:28:35.366
<v Speaker 2>Yes, it's closer to 1 in 5,000. Uh-huh.

0:28:36.586 --> 0:28:39.986
<v Speaker 1>I mean, maybe the person looked for the most AI-sounding 50.

0:28:39.586 --> 0:28:41.366
<v Speaker 2>Words, right? I mean, that's what they said, is they

0:28:41.386 --> 0:28:43.786
<v Speaker 2>said this sounded like AI to them. So it's a

0:28:43.826 --> 0:28:46.246
<v Speaker 2>false positive to them and also to PanGram.

0:28:46.766 --> 0:28:50.036
<v Speaker 1>Okay, let's talk about images. Images are new. I think

0:28:50.076 --> 0:28:51.996
<v Speaker 1>when we booked you, maybe, I don't even know if

0:28:52.036 --> 0:28:54.136
<v Speaker 1>the images thing was out, but tell me about your

0:28:54.156 --> 0:28:55.366
<v Speaker 1>image business. Yeah.

0:28:55.446 --> 0:28:59.526
<v Speaker 2>So it's a new model. We released it in July,

0:28:59.546 --> 0:29:03.986
<v Speaker 2>end of July, but it is state-of-the-art for AI image detection.

0:29:04.066 --> 0:29:06.826
<v Speaker 2>So what that means is you can put in an

0:29:06.926 --> 0:29:10.006
<v Speaker 2>image and we'll tell you, yes, this is AI generated

0:29:10.586 --> 0:29:14.916
<v Speaker 2>and it works on images from nano banana, like Gemini,

0:29:15.476 --> 0:29:20.276
<v Speaker 2>GPT image, mid journey, all of the major AI image models.

0:29:20.436 --> 0:29:22.516
<v Speaker 2>And so I think this is pretty cool because it

0:29:23.126 --> 0:29:24.766
<v Speaker 2>A couple of years ago, it was like really easy

0:29:24.806 --> 0:29:27.206
<v Speaker 2>to tell whether an image was AI generated. You just

0:29:27.226 --> 0:29:28.926
<v Speaker 2>like count the fingers and you look at the text.

0:29:28.946 --> 0:29:30.926
<v Speaker 1>Count the fingers, right. Or see if there's something that

0:29:30.966 --> 0:29:32.406
<v Speaker 1>defies the laws of physics, right?

0:29:32.426 --> 0:29:35.246
<v Speaker 2>Yeah. And today that happens a little bit, but like

0:29:35.526 --> 0:29:39.176
<v Speaker 2>you can get some really hyper-realistic AI images. It's scary.

0:29:39.356 --> 0:29:41.776
<v Speaker 2>And I think it's really hard to tell.

0:29:42.356 --> 0:29:44.836
<v Speaker 1>Certainly hard for people to tell. I mean, I certainly

0:29:44.916 --> 0:29:48.816
<v Speaker 1>buy that you are at the forefront of language detection.

0:29:49.266 --> 0:29:52.306
<v Speaker 1>What is the competitive landscape like for image detection?

0:29:52.916 --> 0:29:57.316
<v Speaker 2>There's a number of AI image detectors. I think many

0:29:57.376 --> 0:30:01.936
<v Speaker 2>of them are more focused on deepfakes and less focused

0:30:02.076 --> 0:30:03.636
<v Speaker 2>on AI images in general.

0:30:04.076 --> 0:30:07.386
<v Speaker 1>Yes, I talked to the head of Lodi. And they're

0:30:07.426 --> 0:30:10.026
<v Speaker 1>focused in particular on videos. Like his claim, at least,

0:30:10.066 --> 0:30:13.746
<v Speaker 1>was that they are good at understanding video, ingesting video

0:30:13.886 --> 0:30:15.026
<v Speaker 1>in a way that other people are not.

0:30:15.126 --> 0:30:15.646
<v Speaker 2>Oh, that's pretty cool.

0:30:15.666 --> 0:30:17.216
<v Speaker 1>Because video is hard.

0:30:17.246 --> 0:30:19.236
<v Speaker 2>Yeah. Yeah, we've been working a bit with video. So

0:30:19.276 --> 0:30:20.996
<v Speaker 2>if you put in a single frame from a video

0:30:21.016 --> 0:30:24.316
<v Speaker 2>into the AI image detector, it will do pretty well.

0:30:24.616 --> 0:30:28.296
<v Speaker 1>What kinds of businesses are natural customers for your image product?

0:30:28.316 --> 0:30:33.286
<v Speaker 2>Yeah, I think naturally it would be someone like Pinterest

0:30:33.726 --> 0:30:38.246
<v Speaker 2>or like any like stock photo company. image website, things

0:30:38.266 --> 0:30:41.666
<v Speaker 2>like that, where you want your users to have some

0:30:41.706 --> 0:30:43.936
<v Speaker 2>degree of trust that what they're seeing is real.

0:30:44.476 --> 0:30:47.256
<v Speaker 1>Dating apps or websites was the first one I thought of.

0:30:47.336 --> 0:30:51.356
<v Speaker 2>Yeah, I think dating apps, absolutely. You don't want AI-generated

0:30:51.876 --> 0:30:53.726
<v Speaker 2>people or AI catfishing.

0:30:54.386 --> 0:30:56.866
<v Speaker 1>Real estate apps was another one I thought. I mean,

0:30:56.926 --> 0:30:59.326
<v Speaker 1>I know they will explicitly sometimes be like, and here's

0:30:59.376 --> 0:31:01.716
<v Speaker 1>what it could look like. But like, they don't always

0:31:01.796 --> 0:31:03.716
<v Speaker 1>say that. I feel like a lot of the time,

0:31:04.216 --> 0:31:06.576
<v Speaker 1>like my neighborhood has all these old houses that people

0:31:06.596 --> 0:31:08.116
<v Speaker 1>have lived in for 50 years, but they sell for

0:31:08.136 --> 0:31:09.756
<v Speaker 1>a lot of money now, right? Which is the classic

0:31:09.796 --> 0:31:11.556
<v Speaker 1>thing where the realtor wants to be like, look, you

0:31:11.576 --> 0:31:13.116
<v Speaker 1>can pay a lot of money for this house because

0:31:13.176 --> 0:31:15.626
<v Speaker 1>it could look like this. But they don't show you

0:31:15.666 --> 0:31:17.366
<v Speaker 1>what it looks like now for a reason.

0:31:17.386 --> 0:31:18.706
<v Speaker 2>Oh, that's horrendous.

0:31:18.846 --> 0:31:19.286
<v Speaker 1>Yeah, yeah.

0:31:19.326 --> 0:31:21.486
<v Speaker 2>I mean, I think that sort of stuff, like it

0:31:21.506 --> 0:31:25.516
<v Speaker 2>should be illegal to... to put an AI photo instead

0:31:25.536 --> 0:31:26.996
<v Speaker 2>of the actual photo in your listing?

0:31:27.256 --> 0:31:28.876
<v Speaker 1>They may well say it. I don't want to be

0:31:28.916 --> 0:31:32.256
<v Speaker 1>accusing people of malice, but, like... No, I've.

0:31:32.136 --> 0:31:34.756
<v Speaker 2>Definitely seen it for apartment listings in New York. Yeah. Like,

0:31:34.896 --> 0:31:37.896
<v Speaker 2>where I show up, and it's like, huh, it looks

0:31:37.936 --> 0:31:39.436
<v Speaker 2>a little bit different than the photos. And I go

0:31:39.476 --> 0:31:41.476
<v Speaker 2>back to the photos, and, like, some of the details

0:31:41.516 --> 0:31:43.996
<v Speaker 2>are different. And I'm like, okay, I think... I'm, like,

0:31:44.216 --> 0:31:45.336
<v Speaker 2>pretty sure this was AI.

0:31:45.496 --> 0:31:48.636
<v Speaker 1>Wait, it's a shady apartment listing in New York? No,

0:31:48.796 --> 0:31:50.806
<v Speaker 1>I don't believe you. I.

0:31:51.416 --> 0:31:54.636
<v Speaker 2>Whenever it's too good to be true, half the time

0:31:54.656 --> 0:31:55.096
<v Speaker 2>it's AI.

0:31:55.116 --> 0:31:57.836
<v Speaker 1>One time I called for an apartment in New York

0:31:58.216 --> 0:32:00.176
<v Speaker 1>to go look at it, and the guy's first question was,

0:32:00.576 --> 0:32:03.496
<v Speaker 1>how tall are you? I was like, I'm out. I'm

0:32:03.516 --> 0:32:10.426
<v Speaker 1>not going to go look. We'll be back in a

0:32:10.446 --> 0:32:23.186
<v Speaker 1>minute with The Lightning Round. Okay, let's finish with the

0:32:23.206 --> 0:32:28.446
<v Speaker 1>lightning round. Cool. How has building PanGram changed the way

0:32:28.486 --> 0:32:29.746
<v Speaker 1>you think about language?

0:32:31.986 --> 0:32:33.426
<v Speaker 2>I don't know if I have an answer for this.

0:32:34.246 --> 0:32:35.626
<v Speaker 1>Maybe it hasn't. Maybe it hasn't.

0:32:35.646 --> 0:32:39.266
<v Speaker 2>No, I mean, I think some of the biggest learnings

0:32:39.306 --> 0:32:43.206
<v Speaker 2>for me were that, oh, like, these language models are

0:32:43.366 --> 0:32:47.466
<v Speaker 2>not at all as diverse as I thought. Yeah. When

0:32:47.506 --> 0:32:50.686
<v Speaker 2>I started, like, ChatGPT had come out, and we were

0:32:50.706 --> 0:32:54.406
<v Speaker 2>all like, this is amazing. incredible technology. And then spending

0:32:54.446 --> 0:32:56.546
<v Speaker 2>a little more time with it made me realize, oh, actually,

0:32:56.586 --> 0:32:58.826
<v Speaker 2>it's kind of just like saying the same thing every time.

0:32:59.106 --> 0:33:02.706
<v Speaker 2>It's quite mode collapse. And humans are much more diverse.

0:33:02.766 --> 0:33:04.726
<v Speaker 2>And I think that's valuable.

0:33:05.306 --> 0:33:06.966
<v Speaker 1>Well, what's the last thing you read that you loved?

0:33:08.046 --> 0:33:11.976
<v Speaker 2>I read this book called Sublimation by Isabel J. Kim.

0:33:11.996 --> 0:33:15.616
<v Speaker 2>It was about sort of this concept where if somebody immigrates,

0:33:15.716 --> 0:33:20.116
<v Speaker 2>they split into two people. And one person stays, one

0:33:20.136 --> 0:33:22.216
<v Speaker 2>person goes. It was very interesting. It's a good book.

0:33:22.376 --> 0:33:23.016
<v Speaker 1>It's a novel?

0:33:23.216 --> 0:33:23.696
<v Speaker 2>Novel, yeah.

0:33:24.256 --> 0:33:26.636
<v Speaker 1>You ever read anything by AI that you loved?

0:33:27.596 --> 0:33:30.916
<v Speaker 2>There's this kind of funny green text from an old

0:33:31.016 --> 0:33:36.536
<v Speaker 2>AI model about being a bottomless pit supervisor.

0:33:37.476 --> 0:33:39.796
<v Speaker 1>Wait, I don't know what green text is. What's green text?

0:33:40.376 --> 0:33:46.156
<v Speaker 2>Green text, it's this format of storytelling from 4chan where

0:33:46.836 --> 0:33:52.366
<v Speaker 2>it's basically describing a story in first person. Every line

0:33:52.426 --> 0:33:54.266
<v Speaker 2>starts with this carrot or this like.

0:33:54.306 --> 0:33:56.646
<v Speaker 1>I see. Kind of like looking at a command line

0:33:56.706 --> 0:33:57.146
<v Speaker 1>or something.

0:33:57.286 --> 0:33:59.266
<v Speaker 2>Yeah, like the command line thing. And then I think

0:33:59.766 --> 0:34:02.166
<v Speaker 2>because of that, like the formatting, it was green.

0:34:02.726 --> 0:34:04.846
<v Speaker 1>Okay, so go on. So you saw something that was

0:34:04.886 --> 0:34:05.946
<v Speaker 1>like this and it was about?

0:34:06.846 --> 0:34:08.846
<v Speaker 2>Yeah, it was kind of just like a joke story

0:34:08.906 --> 0:34:12.546
<v Speaker 2>about being a bottomless pit supervisor. And I was like, okay,

0:34:12.566 --> 0:34:14.046
<v Speaker 2>this is like, this is kind of funny. This is

0:34:14.066 --> 0:34:16.366
<v Speaker 2>the first time I've like laughed at something that was

0:34:16.846 --> 0:34:17.506
<v Speaker 2>AI generated.

0:34:18.026 --> 0:34:19.006
<v Speaker 1>How did you come across it?

0:34:19.696 --> 0:34:21.996
<v Speaker 2>It was posted on Twitter. I can read it for

0:34:22.016 --> 0:34:22.576
<v Speaker 2>you if you like.

0:34:23.136 --> 0:34:23.916
<v Speaker 1>Yeah, that'd be great.

0:34:24.016 --> 0:34:28.576
<v Speaker 2>Okay. So it starts with the human prompt is write

0:34:28.616 --> 0:34:32.726
<v Speaker 2>me a 4chan green text, be me bottomless pit supervisor.

0:34:33.396 --> 0:34:37.186
<v Speaker 2>And then AI continues this with in charge of making

0:34:37.226 --> 0:34:40.666
<v Speaker 2>sure the bottomless pit is in fact bottomless. Occasionally have

0:34:40.706 --> 0:34:42.546
<v Speaker 2>to go down there and check if the bottomless pit

0:34:42.586 --> 0:34:45.446
<v Speaker 2>is still bottomless. One day I go down there and

0:34:45.466 --> 0:34:48.376
<v Speaker 2>the bottomless pit is no longer bottomless and The bottom

0:34:48.396 --> 0:34:52.396
<v Speaker 2>of the bottomless pit is now just a regular pit. Distress.jpg.

0:34:53.056 --> 0:34:56.026
<v Speaker 2>Ask my boss what to do. He says, just make

0:34:56.066 --> 0:34:59.976
<v Speaker 2>it bottomless again. I say, how? He says, I don't know.

0:35:00.066 --> 0:35:05.026
<v Speaker 2>You're the supervisor. Rage.jpg. Quit my job. Become a regular

0:35:05.066 --> 0:35:08.206
<v Speaker 2>pit supervisor. First day on the job, go down to

0:35:08.246 --> 0:35:09.786
<v Speaker 2>the new hole. It's bottomless.

0:35:11.546 --> 0:35:17.866
<v Speaker 1>That's great. It also doesn't sound like AI. Yeah. To me,

0:35:17.986 --> 0:35:18.926
<v Speaker 1>to my ear, anyway.

0:35:19.446 --> 0:35:23.046
<v Speaker 2>Yeah, I think that's because this was, like, old AI.

0:35:23.146 --> 0:35:26.086
<v Speaker 2>I want to say it's, like, GPT-2 or 3.

0:35:26.086 --> 0:35:28.266
<v Speaker 1>I also wonder, like, it sounds like it's not a

0:35:28.336 --> 0:35:30.156
<v Speaker 1>form that I'm familiar with, but it sounds like it

0:35:30.196 --> 0:35:33.056
<v Speaker 1>is this very particular form of writing that exists in

0:35:33.096 --> 0:35:35.776
<v Speaker 1>the world. And so, just like if you say, write

0:35:35.816 --> 0:35:38.636
<v Speaker 1>a sonnet or whatever, I don't know, maybe Pangram can

0:35:38.676 --> 0:35:40.956
<v Speaker 1>tell an AI sonnet from a human-generated sonnet, or maybe

0:35:40.996 --> 0:35:45.406
<v Speaker 1>it's not enough words. But, like... When there is a form,

0:35:45.526 --> 0:35:48.486
<v Speaker 1>maybe we all sort of collapse. Humans collapse to the

0:35:48.546 --> 0:35:50.646
<v Speaker 1>form as well. And so the collapse of AI is

0:35:50.686 --> 0:35:51.886
<v Speaker 1>maybe less obvious. I don't know.

0:35:52.086 --> 0:35:54.356
<v Speaker 2>I think so. Yeah. The collapse of the form and

0:35:54.456 --> 0:35:59.816
<v Speaker 2>adherence to this structure is, I think, makes it interesting.

0:35:59.976 --> 0:36:01.936
<v Speaker 2>And it's very interesting that AI is able to adhere

0:36:01.976 --> 0:36:02.956
<v Speaker 2>to the structure so well.

0:36:03.456 --> 0:36:06.966
<v Speaker 1>And it gets the joke, right? Like bottomless pit supervisor

0:36:07.046 --> 0:36:11.296
<v Speaker 1>is an absurd premise, right? And it treats it just right.

0:36:11.356 --> 0:36:13.436
<v Speaker 1>Like it's a deaf comic touch, right?

0:36:14.236 --> 0:36:14.856
<v Speaker 2>Yeah, it was good.

0:36:15.796 --> 0:36:18.036
<v Speaker 1>Tell me about your Twitter game, your X game. You're

0:36:18.116 --> 0:36:20.196
<v Speaker 1>on a lot and you're kind of a poster. Like

0:36:20.796 --> 0:36:23.686
<v Speaker 1>your persona on Twitter is a little bit more, I

0:36:23.686 --> 0:36:25.866
<v Speaker 1>don't know if combative is too strong of a word,

0:36:26.246 --> 0:36:27.666
<v Speaker 1>than your persona in this interview.

0:36:28.926 --> 0:36:30.886
<v Speaker 2>I like to be on Twitter a lot. I post

0:36:31.086 --> 0:36:33.446
<v Speaker 2>all the time. I kind of just like post what

0:36:33.466 --> 0:36:36.146
<v Speaker 2>I think. I don't think too hard about it. But

0:36:36.266 --> 0:36:40.046
<v Speaker 2>I think Twitter is a really great community because... First off,

0:36:40.086 --> 0:36:43.446
<v Speaker 2>I like text. I'm not on TikTok. I'm not filming

0:36:43.486 --> 0:36:46.766
<v Speaker 2>videos of myself. I like just typing things out. So

0:36:46.846 --> 0:36:49.806
<v Speaker 2>I think it's a great place for me. And it's

0:36:49.866 --> 0:36:52.596
<v Speaker 2>also kind of like where all the AI happenings happen.

0:36:53.176 --> 0:36:55.676
<v Speaker 2>So a lot of the people I follow are people

0:36:55.696 --> 0:36:59.196
<v Speaker 2>who work in AI in various capacities, either AI researchers

0:36:59.556 --> 0:37:04.336
<v Speaker 2>or independent people doing cool things with AI. So I

0:37:04.376 --> 0:37:04.976
<v Speaker 2>post a lot.

0:37:05.696 --> 0:37:08.516
<v Speaker 1>Are you not more combative on Twitter? Am I misreading that?

0:37:09.666 --> 0:37:13.206
<v Speaker 2>Sometimes I think, so I often will get like, somebody

0:37:13.246 --> 0:37:15.766
<v Speaker 2>will say, you know, pangram was wrong on like so-and-so

0:37:15.826 --> 0:37:18.476
<v Speaker 2>and then I'll have to jump in and be like, Hey,

0:37:18.506 --> 0:37:20.256
<v Speaker 2>you know, can you send me the text? Like we

0:37:20.276 --> 0:37:22.596
<v Speaker 2>want to go like triage it and figure that out.

0:37:22.636 --> 0:37:22.836
<v Speaker 1>Yeah.

0:37:23.796 --> 0:37:28.116
<v Speaker 2>Uh, in terms of combativeness, I, I'm not like picking

0:37:28.176 --> 0:37:30.916
<v Speaker 2>fights all the time, but I, I mean, I think

0:37:30.956 --> 0:37:33.946
<v Speaker 2>maybe it's just a function of the platform and the

0:37:33.986 --> 0:37:36.446
<v Speaker 2>format where like, you know, here we're having such a

0:37:36.506 --> 0:37:40.366
<v Speaker 2>like nice, pleasant conversation. But, like, there's no pleasant conversations

0:37:40.446 --> 0:37:40.846
<v Speaker 2>on Twitter.

0:37:41.366 --> 0:37:45.206
<v Speaker 1>Yeah, it's interesting. I will occasionally get angry emails, as

0:37:45.306 --> 0:37:48.786
<v Speaker 1>one does. And almost every time, if I write back

0:37:48.826 --> 0:37:51.326
<v Speaker 1>in a polite way, the person apologizes. I don't even

0:37:51.466 --> 0:37:53.306
<v Speaker 1>ask them for an apology. I just say, yes, thank

0:37:53.326 --> 0:37:55.946
<v Speaker 1>you for pointing that out. Here is my thinking. And

0:37:57.006 --> 0:37:58.986
<v Speaker 1>more often than not, if I do that, the person

0:37:59.826 --> 0:38:06.336
<v Speaker 1>will write back apologetically, basically, or certainly gratefully. What's your

0:38:06.396 --> 0:38:07.496
<v Speaker 1>least favorite AI thing?

0:38:10.376 --> 0:38:14.756
<v Speaker 2>My least favorite is when it's like, and honestly. I'm

0:38:14.776 --> 0:38:15.756
<v Speaker 2>just like, that's horrible.

0:38:18.946 --> 0:38:21.546
<v Speaker 1>Load-bearing and doing the work are the two.

0:38:21.406 --> 0:38:24.946
<v Speaker 2>That, yeah, those make me cringe.

0:38:32.196 --> 0:38:36.696
<v Speaker 1>Max Biro is the co-founder and CEO of Pangram. Today's

0:38:36.736 --> 0:38:40.106
<v Speaker 1>show was produced by Gabriel Hunter Chang. It was engineered

0:38:40.146 --> 0:38:44.086
<v Speaker 1>by Sarah Bruguere. And our showrunner and editor is Jake Harper.

0:38:44.886 --> 0:38:47.136
<v Speaker 1>I'm Jacob Goldstein, and we'll be back next week with

0:38:47.196 --> 0:38:48.576
<v Speaker 1>another episode of What's Your Problem?