WEBVTT - What is Section 230?

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to text Stuff, a production from I Heart Radio.

0:00:12.240 --> 0:00:14.880
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:15.000 --> 0:00:18.200
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio

0:00:18.280 --> 0:00:23.000
<v Speaker 1>and I love all things tech And what if websites

0:00:23.040 --> 0:00:27.160
<v Speaker 1>were held responsible for the content that other people post

0:00:27.400 --> 0:00:31.200
<v Speaker 1>to those websites. What if after a customer left a

0:00:31.360 --> 0:00:35.440
<v Speaker 1>bad review for a product online, the company that makes

0:00:35.560 --> 0:00:40.960
<v Speaker 1>that product would sue Amazon for hosting the review. What

0:00:41.159 --> 0:00:44.319
<v Speaker 1>if that company that makes the thing, what if they

0:00:44.400 --> 0:00:47.720
<v Speaker 1>won that lawsuit. What if Facebook were liable for the

0:00:47.760 --> 0:00:52.800
<v Speaker 1>posts made by its two billion users worldwide. If sites

0:00:52.840 --> 0:00:56.440
<v Speaker 1>were held accountable for the content that users and third

0:00:56.480 --> 0:01:00.320
<v Speaker 1>parties posted to them, we would not have the ornet

0:01:00.360 --> 0:01:07.840
<v Speaker 1>we have today. In fact, companies and organizations like Wikipedia, Amazon, Facebook, Twitter,

0:01:07.920 --> 0:01:11.479
<v Speaker 1>even Google wouldn't exist, or at least they wouldn't exist

0:01:11.520 --> 0:01:14.720
<v Speaker 1>in the forms they do today if that were the case. Now,

0:01:14.760 --> 0:01:17.000
<v Speaker 1>if you live in the United States, you might have

0:01:17.040 --> 0:01:21.000
<v Speaker 1>heard a bit about a section to thirty. Even if

0:01:21.000 --> 0:01:23.480
<v Speaker 1>you're outside the United States, you might have heard some

0:01:23.520 --> 0:01:26.840
<v Speaker 1>references to it. Now, if you're only casually following the

0:01:26.880 --> 0:01:30.240
<v Speaker 1>news or you just here section to thirty in passing,

0:01:30.920 --> 0:01:34.120
<v Speaker 1>it's probably pretty confusing. It clearly has something to do

0:01:34.200 --> 0:01:39.440
<v Speaker 1>with technology and liability and communication. President Donald Trump called

0:01:39.520 --> 0:01:43.280
<v Speaker 1>upon Congress to revoke it several times now, even threatening

0:01:43.319 --> 0:01:47.360
<v Speaker 1>to veto the funding of the National Defense Authorization Act

0:01:47.800 --> 0:01:52.520
<v Speaker 1>unless Congress repealed Section to thirty. But Trump is not

0:01:52.600 --> 0:01:56.880
<v Speaker 1>the only politician to call out this legislation. Representatives from

0:01:56.920 --> 0:02:00.640
<v Speaker 1>both the Republican and Democrat parties have proposed those changes

0:02:00.720 --> 0:02:03.400
<v Speaker 1>or even the outright elimination of Section to thirty over

0:02:03.400 --> 0:02:07.240
<v Speaker 1>the years. Heck, President elect Joe Biden has also called

0:02:07.360 --> 0:02:10.120
<v Speaker 1>upon the need to revoke to thirty. And if you

0:02:10.200 --> 0:02:13.240
<v Speaker 1>live in America, you might be surprised to hear that

0:02:13.280 --> 0:02:16.880
<v Speaker 1>Trump and Biden have agreed on something, though I guess

0:02:16.919 --> 0:02:20.760
<v Speaker 1>it's fair to point out they agree on the end result,

0:02:20.840 --> 0:02:24.720
<v Speaker 1>but for very different motivations. So in today's episode, I

0:02:24.760 --> 0:02:28.320
<v Speaker 1>want to talk about what Section to thirty is, where

0:02:28.320 --> 0:02:31.880
<v Speaker 1>it came from, what its purpose was and is, and

0:02:31.919 --> 0:02:35.040
<v Speaker 1>why there's so much discussion about the need to change

0:02:35.240 --> 0:02:38.560
<v Speaker 1>or get rid of it from various viewpoints across the

0:02:38.560 --> 0:02:42.800
<v Speaker 1>political spectrum. And I'll do my best to avoid any

0:02:42.800 --> 0:02:45.680
<v Speaker 1>political commentary, but I do want to say that the

0:02:45.760 --> 0:02:50.080
<v Speaker 1>motivations behind these various calls for change. They very a

0:02:50.200 --> 0:02:53.079
<v Speaker 1>great deal. I think a lot of folks in politics

0:02:53.120 --> 0:02:56.720
<v Speaker 1>agree that section to thy needs some attention, but they

0:02:56.760 --> 0:02:59.600
<v Speaker 1>don't all agree as to the reasons why or how

0:02:59.639 --> 0:03:01.880
<v Speaker 1>it should be done. So we're gonna get into all

0:03:01.919 --> 0:03:04.240
<v Speaker 1>of that. And before we jump in, I want to

0:03:04.280 --> 0:03:08.800
<v Speaker 1>recommend an amazing resource. It's a book by Jeff Kossa

0:03:09.040 --> 0:03:13.000
<v Speaker 1>titled The Twenty six Words That Created the Internet, and

0:03:13.080 --> 0:03:16.760
<v Speaker 1>it's all about section to thirty, from the genesis of

0:03:16.800 --> 0:03:20.920
<v Speaker 1>the idea to the implementation of Section two thirty in

0:03:21.000 --> 0:03:23.919
<v Speaker 1>court cases. And it's also a really good read, which

0:03:23.960 --> 0:03:26.800
<v Speaker 1>is a weird thing to say about a book centering

0:03:26.840 --> 0:03:30.200
<v Speaker 1>on a subsection of a huge telecommunications bill. I should

0:03:30.280 --> 0:03:34.480
<v Speaker 1>also add as a trigger warning that book discusses some

0:03:34.600 --> 0:03:39.600
<v Speaker 1>cases that deal with some really heavy, dark stuff. To

0:03:39.840 --> 0:03:45.240
<v Speaker 1>thirty has been tested in some really emotionally charged cases

0:03:45.720 --> 0:03:50.680
<v Speaker 1>that include truly awful things that have happened to people,

0:03:50.760 --> 0:03:53.880
<v Speaker 1>So fair warning if you do want to check that

0:03:53.880 --> 0:03:56.240
<v Speaker 1>book out and give it a read. Now. At the

0:03:56.320 --> 0:03:59.960
<v Speaker 1>heart of all of this are concepts like free speed,

0:04:00.000 --> 0:04:05.520
<v Speaker 1>each which has very wide protection in America, and liability

0:04:05.680 --> 0:04:10.880
<v Speaker 1>that is being held accountable legally accountable for something. Because

0:04:11.080 --> 0:04:14.280
<v Speaker 1>while there are broad protections for freedom of speech, it

0:04:14.400 --> 0:04:17.320
<v Speaker 1>is not absolute. There are some forms of speech and

0:04:17.440 --> 0:04:21.640
<v Speaker 1>expression that are not protected under the First Amendment. And

0:04:21.880 --> 0:04:26.240
<v Speaker 1>that's because free speech sometimes bumps up against other important

0:04:26.279 --> 0:04:30.120
<v Speaker 1>things like security or privacy, that kind of thing. So

0:04:31.520 --> 0:04:33.760
<v Speaker 1>it's one of those things where it's not pure black

0:04:33.800 --> 0:04:37.719
<v Speaker 1>and white. There's some shades of gray. Now, let's find

0:04:37.720 --> 0:04:41.120
<v Speaker 1>out what section to thirty is. And it's called Section

0:04:41.200 --> 0:04:44.360
<v Speaker 1>two thirty, so that suggests it's part of something bigger. Right,

0:04:44.400 --> 0:04:47.520
<v Speaker 1>it's a section of something. Well that it's a section

0:04:47.520 --> 0:04:50.160
<v Speaker 1>of a larger piece of legislation, and that piece was

0:04:50.240 --> 0:04:55.000
<v Speaker 1>the Communications Decency Act. So let's turn back the hands

0:04:55.040 --> 0:04:58.440
<v Speaker 1>of the clock a bit. Heck, maybe i'll maybe I'll

0:04:58.520 --> 0:05:01.400
<v Speaker 1>dust off the old text of time Machine for this one.

0:05:01.440 --> 0:05:06.000
<v Speaker 1>I don't think we've actually used it in years. Fortunately,

0:05:06.080 --> 0:05:08.760
<v Speaker 1>I did bring it home with me when our office

0:05:08.760 --> 0:05:12.480
<v Speaker 1>went into lockdown, so it's really just taking up space

0:05:12.520 --> 0:05:14.800
<v Speaker 1>in the corner. Hang on, hang on a second. I'm

0:05:14.800 --> 0:05:16.320
<v Speaker 1>just gonna get it out. I gotta move a couple

0:05:16.320 --> 0:05:29.360
<v Speaker 1>of things. Be right back. Alright, alright, so I've got it. Now,

0:05:29.760 --> 0:05:33.200
<v Speaker 1>let me set the dial back to uh, let's see

0:05:34.160 --> 0:05:37.960
<v Speaker 1>nineteen all right, Okay, here we go, everybody in, come on,

0:05:38.040 --> 0:05:41.200
<v Speaker 1>let's all get into the time machine. All right, Ready,

0:05:41.960 --> 0:05:57.440
<v Speaker 1>push the button, Frank, and here we are. It's The

0:05:57.560 --> 0:05:59.760
<v Speaker 1>number one hit single of the year is hold On

0:06:00.080 --> 0:06:03.080
<v Speaker 1>by Wilson Phillips, a song I'm not ashamed to say

0:06:03.120 --> 0:06:06.520
<v Speaker 1>I absolutely loved at the time, shows like Cheers, A

0:06:06.600 --> 0:06:09.680
<v Speaker 1>Different World and Murphy Brown, or on television that the

0:06:09.720 --> 0:06:12.960
<v Speaker 1>box office, the film Ghost comes out on top, with

0:06:13.080 --> 0:06:16.479
<v Speaker 1>Home Alone not far behind. But we're not here to

0:06:16.520 --> 0:06:20.120
<v Speaker 1>see the awkward transition of the nineteen eighties transform into

0:06:20.160 --> 0:06:23.480
<v Speaker 1>the nineteen nineties. Now, we're here to learn about how

0:06:23.720 --> 0:06:27.360
<v Speaker 1>US law would view the role of online platforms now

0:06:27.440 --> 0:06:31.920
<v Speaker 1>back in where we are now, the Internet isn't really

0:06:32.000 --> 0:06:34.599
<v Speaker 1>a thing as far as the mainstream public is concerned.

0:06:35.120 --> 0:06:38.680
<v Speaker 1>It exists, but hardly anyone knows very much about it

0:06:38.880 --> 0:06:43.760
<v Speaker 1>Outside of research facilities and government offices. There's no such

0:06:43.800 --> 0:06:47.920
<v Speaker 1>thing as the Worldwide Web. Yet, However, there are a

0:06:47.960 --> 0:06:52.240
<v Speaker 1>few big online service providers or OSPs. Now these are

0:06:52.279 --> 0:06:56.479
<v Speaker 1>sort of the predecessors to Internet Service providers or I

0:06:56.760 --> 0:06:59.200
<v Speaker 1>s p s, and OSP is kind of like its

0:06:59.240 --> 0:07:03.039
<v Speaker 1>own micro internet, though really, we would just kind of

0:07:03.080 --> 0:07:04.719
<v Speaker 1>call it a network. So think of it as a

0:07:04.760 --> 0:07:09.039
<v Speaker 1>self contained collection of servers that hosts stuff like forums

0:07:09.080 --> 0:07:12.040
<v Speaker 1>and newsletters and articles and files, and you're on the

0:07:12.120 --> 0:07:15.440
<v Speaker 1>right track, and they don't necessarily talk to each other,

0:07:15.720 --> 0:07:18.080
<v Speaker 1>so they're kind of self contained. Well, one of those

0:07:18.120 --> 0:07:22.000
<v Speaker 1>big OSPs is compu Serve, and it's going to get

0:07:22.040 --> 0:07:24.760
<v Speaker 1>taken to court. At the heart of the matter is

0:07:24.800 --> 0:07:29.800
<v Speaker 1>an accusation of libel that is, uh, a misinformation with

0:07:29.920 --> 0:07:34.200
<v Speaker 1>the intent to cause harm that's in print. The plaintiffs,

0:07:34.320 --> 0:07:38.440
<v Speaker 1>Robert Blanchard and a company called Cubby Incorporated, have developed

0:07:38.440 --> 0:07:43.160
<v Speaker 1>a news and rumors service called scuttle Butt, which focuses

0:07:43.240 --> 0:07:47.600
<v Speaker 1>on the radio and TV industries. Now, according to the plaintiffs,

0:07:47.640 --> 0:07:51.880
<v Speaker 1>a newsletter that is also that's called Rumorville USA, which

0:07:52.200 --> 0:07:55.880
<v Speaker 1>also covers rumors in the TV and radio spaces, has

0:07:55.960 --> 0:08:00.680
<v Speaker 1>published untrue and harmful things about scuttle Butt, and Rumorville

0:08:01.080 --> 0:08:05.160
<v Speaker 1>is available on compu Serve. So the plaintiffs targeted not

0:08:05.280 --> 0:08:08.720
<v Speaker 1>just Rumorville, but compu Serve in their lawsuits. So they

0:08:08.720 --> 0:08:13.480
<v Speaker 1>say compu Serve is responsible because it allows the distribution

0:08:13.520 --> 0:08:17.920
<v Speaker 1>of Rumorville, which in turn has published libelous content about

0:08:17.920 --> 0:08:22.560
<v Speaker 1>scuttle butt. So the lawyers representing Company Serve argue that

0:08:22.640 --> 0:08:26.120
<v Speaker 1>the service has no connection to Rumorville other than as

0:08:26.120 --> 0:08:28.160
<v Speaker 1>serving as a way for people to get the newsletter.

0:08:28.160 --> 0:08:32.199
<v Speaker 1>In other words, compu Service saying, hey, we don't write that.

0:08:32.760 --> 0:08:35.680
<v Speaker 1>We just have it on our service, but we don't

0:08:35.760 --> 0:08:40.400
<v Speaker 1>write it. There's no there's no employment here to generate

0:08:40.440 --> 0:08:44.760
<v Speaker 1>that newsletter. Compu Serve isn't involved editorially in the newsletter

0:08:44.800 --> 0:08:47.439
<v Speaker 1>at all. It just comes from another company. That company

0:08:47.480 --> 0:08:52.400
<v Speaker 1>is Don Fitzpatrick Associates of San Francisco, and it's referred

0:08:52.440 --> 0:08:55.560
<v Speaker 1>to in the court documents as d f A. Compu

0:08:55.679 --> 0:08:59.560
<v Speaker 1>Serve did not employ this company or pay for this

0:08:59.679 --> 0:09:03.000
<v Speaker 1>news letter. And moreover, according to the agreement between compy

0:09:03.040 --> 0:09:05.960
<v Speaker 1>Serve and d f A, d f A accepts full

0:09:05.960 --> 0:09:09.800
<v Speaker 1>responsibility for the contents of its newsletter. So compy serves

0:09:09.880 --> 0:09:12.559
<v Speaker 1>lawyers go and make a motion for a summary judgment,

0:09:12.720 --> 0:09:17.280
<v Speaker 1>which in this case was to dismiss the the the charges,

0:09:17.400 --> 0:09:20.200
<v Speaker 1>just for the court to make a decision on behalf

0:09:20.240 --> 0:09:23.640
<v Speaker 1>of one party against another party without the need to

0:09:23.679 --> 0:09:26.640
<v Speaker 1>go to a full trial. And the judge grants this

0:09:26.800 --> 0:09:30.559
<v Speaker 1>to Compy Serve. And the judge agrees that compu Serve

0:09:30.640 --> 0:09:34.000
<v Speaker 1>did not bear responsibility for the contents of this newsletter.

0:09:34.400 --> 0:09:36.760
<v Speaker 1>The judge says that compu Serve is kind of like

0:09:36.760 --> 0:09:41.080
<v Speaker 1>a bookstore, and you wouldn't hold a bookstore responsible for

0:09:41.160 --> 0:09:43.760
<v Speaker 1>the contents of a book that was published by a

0:09:43.840 --> 0:09:47.000
<v Speaker 1>third party just because it happens to be in that bookstore.

0:09:47.320 --> 0:09:50.440
<v Speaker 1>The bookstore is just that's where customers can buy books.

0:09:50.480 --> 0:09:54.560
<v Speaker 1>The store did not put the actual content into the books,

0:09:54.640 --> 0:09:57.120
<v Speaker 1>and this becomes a precedent that would serve as a

0:09:57.160 --> 0:10:02.599
<v Speaker 1>foundational building block for section to thirty later. All right, everyone, um,

0:10:02.679 --> 0:10:05.080
<v Speaker 1>we're done here. Let's all jump back in the time machine.

0:10:05.280 --> 0:10:06.920
<v Speaker 1>Come out, no stragglers. I don't want to have to

0:10:06.920 --> 0:10:10.520
<v Speaker 1>come back to lived through it. Once we're done. We

0:10:10.600 --> 0:10:12.440
<v Speaker 1>got a hop forward a couple of years. Okay, ready

0:10:13.360 --> 0:10:29.160
<v Speaker 1>push the button. All right, now we're in. So now

0:10:29.240 --> 0:10:31.640
<v Speaker 1>the number one song in America would be Ace of

0:10:31.760 --> 0:10:34.840
<v Speaker 1>Bases the Sign which I don't know about you, but

0:10:34.920 --> 0:10:38.520
<v Speaker 1>it opened up my eyes. I'm happy now. Seinfeld is

0:10:38.600 --> 0:10:41.840
<v Speaker 1>dominating TV ratings and the big movies at the box

0:10:41.840 --> 0:10:45.319
<v Speaker 1>office are The Lion King and Forest Gumps. So what

0:10:45.360 --> 0:10:48.280
<v Speaker 1>are we doing here? And now, well, this time we've

0:10:48.280 --> 0:10:51.760
<v Speaker 1>got another lawsuit, but this is one that's against a

0:10:51.880 --> 0:10:57.920
<v Speaker 1>different osp called Prodigy. Now. Like compu Serve, Prodigy hosts

0:10:58.000 --> 0:11:02.280
<v Speaker 1>stuff like forums and articles and their services on one forum,

0:11:02.480 --> 0:11:07.040
<v Speaker 1>and anonymous user alleged that a securities firm named Stratton

0:11:07.080 --> 0:11:12.920
<v Speaker 1>Oakmont was committing fraud in a stock offering and Stratton

0:11:13.040 --> 0:11:17.959
<v Speaker 1>Stratton Oakmont would sue Prodigy for liabel. Now, Prodigies lawyers

0:11:18.000 --> 0:11:22.120
<v Speaker 1>said that we shouldn't be held responsible for the content

0:11:22.280 --> 0:11:25.199
<v Speaker 1>that's posted by a third party by a Prodigy user,

0:11:25.600 --> 0:11:28.720
<v Speaker 1>and they cited the CompuServe ruling that came back a

0:11:28.760 --> 0:11:32.920
<v Speaker 1>few years earlier. But the judge in this case disagrees

0:11:33.520 --> 0:11:38.599
<v Speaker 1>with Prodigies lawyers. They rule against the service, and the

0:11:38.679 --> 0:11:43.080
<v Speaker 1>judge says that Prodigy exercised editorial control over the forums.

0:11:43.280 --> 0:11:47.600
<v Speaker 1>The service could and did remove material that was objectionable.

0:11:47.720 --> 0:11:51.560
<v Speaker 1>Unlike CompuServe, which had taken largely a hands off approach

0:11:51.679 --> 0:11:55.480
<v Speaker 1>to the stuff that was published on CompuServe, Prodigy got

0:11:55.520 --> 0:11:59.400
<v Speaker 1>more involved and would remove things that were in violation

0:12:00.040 --> 0:12:04.400
<v Speaker 1>of you know, community standards, and therefore that made Prodigy

0:12:04.640 --> 0:12:07.440
<v Speaker 1>not like a bookstore and made them more like a

0:12:07.480 --> 0:12:11.560
<v Speaker 1>publication like a newspaper, and the editorial control means that

0:12:11.600 --> 0:12:14.800
<v Speaker 1>Prodigy would have to assume responsibility for stuff that appeared

0:12:14.800 --> 0:12:18.280
<v Speaker 1>on the service. After all, if Prodigy intervenes in some cases,

0:12:18.559 --> 0:12:22.160
<v Speaker 1>it means it could and should have intervened in other cases,

0:12:22.320 --> 0:12:27.280
<v Speaker 1>like with Strattonoqumont. So we have that nine one decision

0:12:27.520 --> 0:12:31.160
<v Speaker 1>that says a platform is not responsible for third party

0:12:31.240 --> 0:12:34.719
<v Speaker 1>content published on that platform. But then we have a

0:12:34.840 --> 0:12:39.960
<v Speaker 1>nineteen five decision that seems to contradict that if the

0:12:40.000 --> 0:12:45.000
<v Speaker 1>platform exercised any sort of content management, that means that

0:12:45.080 --> 0:12:47.520
<v Speaker 1>they can be held liable. And I know we traveled

0:12:47.559 --> 0:12:51.640
<v Speaker 1>to nine respectively, but court cases can take a really

0:12:51.640 --> 0:12:54.600
<v Speaker 1>long time. So the decisions were actually handed down a

0:12:54.679 --> 0:12:57.840
<v Speaker 1>year after the initial lawsuits started. I'm sorry that we

0:12:57.840 --> 0:13:00.360
<v Speaker 1>all had to wait around so long for that. Well,

0:13:00.400 --> 0:13:06.600
<v Speaker 1>this created a precarious situation for online companies because the

0:13:06.640 --> 0:13:09.080
<v Speaker 1>message seemed to be that if you provided a space

0:13:09.120 --> 0:13:12.440
<v Speaker 1>for users and third parties to post stuff, it would

0:13:12.480 --> 0:13:15.080
<v Speaker 1>best suit you if you just never ever interfered with that,

0:13:15.600 --> 0:13:19.440
<v Speaker 1>regardless of what gets posted to the platform, because intervening

0:13:19.440 --> 0:13:22.200
<v Speaker 1>would be a slippery slope if you start removing content,

0:13:22.640 --> 0:13:27.520
<v Speaker 1>even stuff that clearly should not be there, like videos

0:13:27.559 --> 0:13:32.640
<v Speaker 1>of violence, or pornography, or death threats, or or personal

0:13:32.640 --> 0:13:35.680
<v Speaker 1>information of other users, whatever it might be. If you

0:13:35.720 --> 0:13:40.040
<v Speaker 1>remove it, no matter how obviously awful it is, you

0:13:40.120 --> 0:13:42.720
<v Speaker 1>create a precedent in which you are acting in an

0:13:42.840 --> 0:13:46.000
<v Speaker 1>editorial capacity. And if you can do that, then are

0:13:46.040 --> 0:13:49.280
<v Speaker 1>you really free of liability when someone posts something that's

0:13:49.520 --> 0:13:54.120
<v Speaker 1>libelous or otherwise illegal. And remember this is the mid nineties.

0:13:54.160 --> 0:13:58.000
<v Speaker 1>The online world hadn't even really started to take off yet,

0:13:58.240 --> 0:14:01.080
<v Speaker 1>so there was a real concern that we would see

0:14:01.120 --> 0:14:05.680
<v Speaker 1>a big negative impact, a chilling effect on the founding

0:14:05.720 --> 0:14:09.959
<v Speaker 1>and evolution of online businesses. Considering that people had generally

0:14:10.000 --> 0:14:12.200
<v Speaker 1>come to the belief that the internet was going to

0:14:12.240 --> 0:14:14.720
<v Speaker 1>be the future of business, or at least an important

0:14:14.720 --> 0:14:18.600
<v Speaker 1>component of business, this was a bad thing. Now, if

0:14:18.600 --> 0:14:21.480
<v Speaker 1>you guys pay attention out there, you probably know that

0:14:21.560 --> 0:14:27.840
<v Speaker 1>politicians typically lag behind big issues and technology. Technology changes

0:14:28.000 --> 0:14:31.400
<v Speaker 1>much faster than policies do. And a lot of politicians

0:14:31.440 --> 0:14:34.680
<v Speaker 1>in this country are in the United States, Um, how

0:14:34.680 --> 0:14:39.120
<v Speaker 1>do I put this delicately? They're old, Like a lot

0:14:39.160 --> 0:14:43.760
<v Speaker 1>of them are really old. The average age, the average

0:14:43.800 --> 0:14:48.240
<v Speaker 1>age of a congress person is twenty years older than

0:14:48.280 --> 0:14:53.080
<v Speaker 1>the average American in the average age of a representative

0:14:53.480 --> 0:14:58.000
<v Speaker 1>is fifty seven. For senators it's sixty one. And generally speaking,

0:14:58.200 --> 0:15:01.320
<v Speaker 1>older generations are a little a slower to pick up

0:15:01.360 --> 0:15:05.160
<v Speaker 1>on technological advances than younger ones. Now there are exceptions

0:15:05.160 --> 0:15:07.040
<v Speaker 1>to this, don't get me wrong, I'm not trying to

0:15:07.080 --> 0:15:11.520
<v Speaker 1>be agist here, but as a general rule, older people

0:15:11.760 --> 0:15:15.120
<v Speaker 1>are less up to speed on emerging technologies. I think

0:15:15.120 --> 0:15:19.000
<v Speaker 1>that rule applies double when it comes to politicians from

0:15:19.000 --> 0:15:23.240
<v Speaker 1>my own anecdotal experience, which I get isn't really evidence.

0:15:23.760 --> 0:15:27.600
<v Speaker 1>So while this was a growing concern within the tech world,

0:15:27.880 --> 0:15:30.640
<v Speaker 1>only a couple of politicians really picked up on how

0:15:30.680 --> 0:15:34.440
<v Speaker 1>these court decisions could create an issue and impede the

0:15:34.480 --> 0:15:37.880
<v Speaker 1>growth of online services in those early days. Now, that

0:15:38.000 --> 0:15:42.359
<v Speaker 1>pair included a Democrat named Ron Wyden and a Republican

0:15:42.440 --> 0:15:46.920
<v Speaker 1>named Chris Cox, who wanted to create legislation full stop.

0:15:47.760 --> 0:15:49.880
<v Speaker 1>They both wanted to make their mark, they wanted to

0:15:49.920 --> 0:15:53.720
<v Speaker 1>pass some laws, but at this particular time in American

0:15:53.760 --> 0:15:56.880
<v Speaker 1>history where it was really hard to do that because

0:15:57.280 --> 0:16:02.360
<v Speaker 1>partisan politics were any vicious at the time. I think

0:16:02.440 --> 0:16:06.480
<v Speaker 1>they were gentle as a kitten compared to today's politics,

0:16:06.520 --> 0:16:09.600
<v Speaker 1>but at the time it was considered pretty brutal, and

0:16:09.640 --> 0:16:12.280
<v Speaker 1>that meant there was very little chance to get agreement

0:16:12.400 --> 0:16:16.160
<v Speaker 1>across the aisle. Republicans at the time controlled both the

0:16:16.240 --> 0:16:19.680
<v Speaker 1>House and the Senate. In Congress in the United States

0:16:20.080 --> 0:16:23.000
<v Speaker 1>are our Congress is divided up into two branches, the

0:16:23.040 --> 0:16:27.680
<v Speaker 1>House of Representatives and the Senate. And a Democrat was president,

0:16:27.840 --> 0:16:32.120
<v Speaker 1>so president and a Republican Congress, and they figured. These

0:16:32.160 --> 0:16:34.520
<v Speaker 1>two people figured that their best chance at making an

0:16:34.560 --> 0:16:37.000
<v Speaker 1>impact was to find a topic that was so new,

0:16:37.160 --> 0:16:40.840
<v Speaker 1>so cutting edge that neither party had actually formed an

0:16:40.840 --> 0:16:44.920
<v Speaker 1>opinion about it. Yet the Internet was a perfect target.

0:16:45.080 --> 0:16:49.520
<v Speaker 1>And this, my friends, drives me bonkers because it points

0:16:49.800 --> 0:16:52.480
<v Speaker 1>out that the writing of section to thirty didn't begin

0:16:53.120 --> 0:16:56.200
<v Speaker 1>with politicians identifying an issue and then finding a way

0:16:56.280 --> 0:16:59.320
<v Speaker 1>to solve it. Instead, it was a case of a

0:16:59.400 --> 0:17:04.400
<v Speaker 1>couple of politicians trying to figure out what sort of problem,

0:17:04.480 --> 0:17:07.600
<v Speaker 1>any problem, could they find where they could potentially tackle

0:17:07.640 --> 0:17:10.280
<v Speaker 1>it and get their names on some legislation. Uh. It's

0:17:10.280 --> 0:17:13.199
<v Speaker 1>probably being a little unfair, but it is sort of

0:17:13.200 --> 0:17:16.080
<v Speaker 1>the reality of politics, and from a practical standpoint, I

0:17:16.119 --> 0:17:18.480
<v Speaker 1>get it. But it's also kind of disillusioning to me.

0:17:18.920 --> 0:17:22.280
<v Speaker 1>The pair determined that they would have a decent chance

0:17:22.359 --> 0:17:26.120
<v Speaker 1>at proposing legislation that would protect online services from being

0:17:26.200 --> 0:17:29.199
<v Speaker 1>sued for the content that other people were posting to

0:17:29.240 --> 0:17:33.359
<v Speaker 1>those services, plus give the services the freedom to moderate

0:17:33.480 --> 0:17:37.679
<v Speaker 1>content without fear of being sued for that. Either. The

0:17:37.680 --> 0:17:40.919
<v Speaker 1>Internet was so new and the potential was so huge

0:17:41.200 --> 0:17:42.960
<v Speaker 1>that they felt that this was a pretty good bet,

0:17:43.240 --> 0:17:46.399
<v Speaker 1>so they drafted out a proposed piece of legislation that

0:17:46.440 --> 0:17:50.920
<v Speaker 1>they called the Internet Freedom and Family Empowerment Act. It

0:17:51.000 --> 0:17:55.400
<v Speaker 1>would ultimately have as its core principle the following quote.

0:17:56.160 --> 0:18:00.120
<v Speaker 1>No provider or user of an interactive computer service shall

0:18:00.119 --> 0:18:03.639
<v Speaker 1>be treated as the publisher or speaker of any information

0:18:03.680 --> 0:18:08.960
<v Speaker 1>provided by another information content provider. End quote. Now. In addition,

0:18:09.400 --> 0:18:12.480
<v Speaker 1>the piece has what has been called the good faith section,

0:18:12.800 --> 0:18:15.240
<v Speaker 1>which states that platforms will not be held liable for

0:18:15.560 --> 0:18:20.400
<v Speaker 1>quote any action voluntarily taken in good faith to restrict

0:18:20.440 --> 0:18:24.600
<v Speaker 1>access to or availability of material that the provider or

0:18:24.840 --> 0:18:31.679
<v Speaker 1>user considers to be obscene, lewd, lascivious, filthy, excessively violent, harassing,

0:18:31.920 --> 0:18:36.879
<v Speaker 1>or otherwise objectionable, whether or not such material is constitutionally protected.

0:18:37.240 --> 0:18:40.040
<v Speaker 1>End quote. Now when we come back, we'll learn more

0:18:40.040 --> 0:18:42.960
<v Speaker 1>about what this actually means from a practical sense. But

0:18:43.080 --> 0:18:54.120
<v Speaker 1>first let's take a quick break. So on the face

0:18:54.160 --> 0:18:58.400
<v Speaker 1>of it, Section two thirty is fairly simple. You cannot

0:18:58.440 --> 0:19:02.040
<v Speaker 1>hold someone or thing, in the case of a platform,

0:19:02.080 --> 0:19:06.120
<v Speaker 1>as the person responsible for what someone else or something

0:19:06.200 --> 0:19:11.000
<v Speaker 1>else says on that platform. So that applies to the

0:19:11.080 --> 0:19:13.960
<v Speaker 1>services and the users. If I'm on a forum and

0:19:14.000 --> 0:19:16.480
<v Speaker 1>I'm making an argument for a certain point of view

0:19:16.680 --> 0:19:20.000
<v Speaker 1>and someone else joins them with libelious accusations about a

0:19:20.160 --> 0:19:23.760
<v Speaker 1>third person, it would be unreasonable to hold me accountable

0:19:23.960 --> 0:19:26.639
<v Speaker 1>for that other person's words. Right, I didn't say the

0:19:26.680 --> 0:19:30.000
<v Speaker 1>libelous thing, why would I be responsible for it. I

0:19:30.080 --> 0:19:33.040
<v Speaker 1>might have started the discussion thread, I might have initiated

0:19:33.080 --> 0:19:36.359
<v Speaker 1>the conversation, But if I didn't actually say anything libelous,

0:19:36.440 --> 0:19:40.000
<v Speaker 1>then I shouldn't be held responsible. Right. Well, that same protection,

0:19:40.160 --> 0:19:45.200
<v Speaker 1>according to this legislation, would apply to online platforms. In addition,

0:19:45.520 --> 0:19:48.719
<v Speaker 1>the platforms would be able to make their own moderation

0:19:48.840 --> 0:19:52.480
<v Speaker 1>policies and not be held liable if the platform removed

0:19:52.640 --> 0:19:56.920
<v Speaker 1>something that would otherwise be constitutionally protected. So, in other words,

0:19:57.200 --> 0:20:01.760
<v Speaker 1>if Facebook removed a post because it violated a Facebook standard,

0:20:01.960 --> 0:20:05.920
<v Speaker 1>even if that post would otherwise be protected constitutionally, Facebook

0:20:05.920 --> 0:20:08.560
<v Speaker 1>would not be held liable as long as that removal

0:20:08.640 --> 0:20:12.760
<v Speaker 1>was done in good faith. Now, in at the time

0:20:12.800 --> 0:20:15.480
<v Speaker 1>that Cox and Widen were putting together their proposal in

0:20:15.560 --> 0:20:19.320
<v Speaker 1>the House of Representatives, there was another piece of legislation

0:20:19.400 --> 0:20:23.280
<v Speaker 1>under consideration that aimed at the issue of pornography online.

0:20:23.760 --> 0:20:26.400
<v Speaker 1>But that was taking place over in the US Senate,

0:20:26.840 --> 0:20:29.639
<v Speaker 1>and this piece tried to treat online content in a

0:20:29.680 --> 0:20:33.080
<v Speaker 1>way similar to how the US government regulates content on

0:20:33.320 --> 0:20:37.200
<v Speaker 1>TV and on radio broadcasts. There was a growing concern

0:20:37.600 --> 0:20:42.160
<v Speaker 1>about the availability the accessibility of pornographic and obscene material.

0:20:42.880 --> 0:20:46.879
<v Speaker 1>Obscenity in this case would fall under a pretty conservative definition,

0:20:47.119 --> 0:20:49.840
<v Speaker 1>like you know, kind of like beauty, obscenity is in

0:20:49.840 --> 0:20:51.960
<v Speaker 1>the eye of the beholder. It's one of those things

0:20:51.960 --> 0:20:53.919
<v Speaker 1>that you know it when you see it. That's kind

0:20:53.920 --> 0:20:56.960
<v Speaker 1>of the famous quote in US history. But the proposed

0:20:57.119 --> 0:21:02.000
<v Speaker 1>legislation would criminalize the act of exposing those under eighteen

0:21:02.040 --> 0:21:05.639
<v Speaker 1>to obscene or pornographic materials online. Now, I should say

0:21:05.800 --> 0:21:08.760
<v Speaker 1>it covered instances in which the age of the recipient

0:21:09.200 --> 0:21:13.199
<v Speaker 1>or at least they're under eighteen status would have to

0:21:13.200 --> 0:21:15.640
<v Speaker 1>be known to the person or entity sending the material

0:21:15.680 --> 0:21:19.560
<v Speaker 1>for this to be relevant. The proposed legislation went a

0:21:19.560 --> 0:21:22.959
<v Speaker 1>bit further than that too, with sections related to speech

0:21:23.000 --> 0:21:27.720
<v Speaker 1>that is indecent but not obscene. Again, really weird gray

0:21:27.760 --> 0:21:31.480
<v Speaker 1>area territory here, but the language raised some concerns among

0:21:31.680 --> 0:21:35.600
<v Speaker 1>civil liberties organizations, so people made some pretty strong arguments

0:21:35.640 --> 0:21:40.359
<v Speaker 1>against this Senate version of the idea. For example, in

0:21:40.400 --> 0:21:44.359
<v Speaker 1>the medical industry, there's terminology that some people might define

0:21:44.400 --> 0:21:49.399
<v Speaker 1>as indecent that's absolutely critical for legitimate medical communication in

0:21:49.440 --> 0:21:53.679
<v Speaker 1>clear terms, So sites that provide useful information for sensitive

0:21:53.680 --> 0:21:58.800
<v Speaker 1>topics like educating people about sexually transmitted diseases or resources

0:21:58.800 --> 0:22:00.920
<v Speaker 1>for people who are in the g b t Q

0:22:01.200 --> 0:22:05.080
<v Speaker 1>plus communities, all that could be at risk if you

0:22:06.280 --> 0:22:09.680
<v Speaker 1>allowed this kind of legislation to go forward. So Ron

0:22:09.720 --> 0:22:12.480
<v Speaker 1>Wyden and Chris Cox were positioning their proposal in the

0:22:12.520 --> 0:22:15.320
<v Speaker 1>House of Representatives as kind of an alternative to the

0:22:15.359 --> 0:22:18.760
<v Speaker 1>approach that was being talked about in the Senate. They

0:22:18.800 --> 0:22:22.440
<v Speaker 1>suggested that online platforms have the ability to moderate content

0:22:22.560 --> 0:22:25.080
<v Speaker 1>on their sites without the risk of being held liable

0:22:25.119 --> 0:22:27.760
<v Speaker 1>for the stuff that people and other parties were posting

0:22:27.800 --> 0:22:31.840
<v Speaker 1>to those sites, And according to Kasaf, their idea met

0:22:31.840 --> 0:22:37.040
<v Speaker 1>with no resistance. In fact, barely anyone even noticed. In

0:22:37.119 --> 0:22:41.280
<v Speaker 1>the United States, the way Congress creates new laws requires

0:22:41.320 --> 0:22:44.840
<v Speaker 1>both the House of Representatives and the Senate to vote

0:22:45.000 --> 0:22:48.840
<v Speaker 1>on the legislation and approve it before sending that piece

0:22:48.880 --> 0:22:51.720
<v Speaker 1>on to the President to be signed into law or

0:22:51.840 --> 0:22:55.159
<v Speaker 1>potentially vetoed. In a case where both the House and

0:22:55.200 --> 0:22:58.719
<v Speaker 1>the Senate are working on something similar but distinct as

0:22:58.800 --> 0:23:01.959
<v Speaker 1>far as legislation goes, those two versions have to be

0:23:02.040 --> 0:23:05.080
<v Speaker 1>hashed out in committee to create a more unified approach.

0:23:05.640 --> 0:23:09.120
<v Speaker 1>Both the Communications Decency Act out of the Senate and

0:23:09.280 --> 0:23:11.600
<v Speaker 1>what would become Section to thirty in the House of

0:23:11.640 --> 0:23:15.879
<v Speaker 1>Representatives would ultimately be lumped in with the overall discussions

0:23:15.920 --> 0:23:20.879
<v Speaker 1>of what would become the Telecommunications Act of NIX. Most

0:23:21.040 --> 0:23:24.600
<v Speaker 1>of Congress was really focused on the other elements of

0:23:24.640 --> 0:23:28.520
<v Speaker 1>the Telecommunications Act. The stuff that related to telephone companies

0:23:28.840 --> 0:23:33.120
<v Speaker 1>and telephone infrastructure and cable companies and the Internet portions

0:23:33.160 --> 0:23:35.520
<v Speaker 1>were more of an afterthought. It was so new that

0:23:35.600 --> 0:23:37.400
<v Speaker 1>a lot of people weren't really thinking about that. They

0:23:37.400 --> 0:23:39.600
<v Speaker 1>were thinking, no, the futures and long distance phone calls,

0:23:39.640 --> 0:23:42.560
<v Speaker 1>Gosh darn't it. And so both the c d A

0:23:42.920 --> 0:23:45.199
<v Speaker 1>which had support due to it being positioned as a

0:23:45.200 --> 0:23:49.560
<v Speaker 1>piece of legislation that was advocating for family values, which, boy,

0:23:49.640 --> 0:23:52.400
<v Speaker 1>was that a big, big point of discussion in the nineties.

0:23:52.640 --> 0:23:55.400
<v Speaker 1>And then Section to thirty, which was positioned as protecting

0:23:55.520 --> 0:23:59.840
<v Speaker 1>new and a vulnerable industry. Both of them made it through.

0:24:00.480 --> 0:24:03.399
<v Speaker 1>So in the end, the language that would become Section

0:24:03.440 --> 0:24:06.800
<v Speaker 1>to thirty and the alternative proposal which would become the

0:24:06.880 --> 0:24:10.680
<v Speaker 1>online portions of the Communications Decency Act would be bound

0:24:10.680 --> 0:24:13.679
<v Speaker 1>together to form kind of a vultron like construction of

0:24:13.760 --> 0:24:18.920
<v Speaker 1>online policy. Now, the Telecommunications Act is enormous. It's a

0:24:18.960 --> 0:24:22.879
<v Speaker 1>beast of a law, covering stuff like telephone lines, cable television,

0:24:22.880 --> 0:24:25.800
<v Speaker 1>and more. Section to thirty is just a tiny part

0:24:25.840 --> 0:24:30.280
<v Speaker 1>of that beast. Interestingly, the anti obscenity measures in the

0:24:30.320 --> 0:24:34.080
<v Speaker 1>Communications Decency Act would not stand the test of time.

0:24:34.160 --> 0:24:37.560
<v Speaker 1>Judges would strike down large portions of it, citing issues

0:24:37.600 --> 0:24:43.360
<v Speaker 1>such as vague terminology like indecent and offensive without firm definitions.

0:24:43.400 --> 0:24:46.840
<v Speaker 1>That legislation was open to far too much subjective interpretation

0:24:46.920 --> 0:24:49.639
<v Speaker 1>to be useful. But while a lot of the c

0:24:49.760 --> 0:24:54.040
<v Speaker 1>d A would go by by Section to thirty remained intact,

0:24:54.320 --> 0:24:58.320
<v Speaker 1>so all that obscenity and decency stuff was gone, but

0:24:58.440 --> 0:25:01.359
<v Speaker 1>that section to thirty I idea from Widen and Cox

0:25:01.440 --> 0:25:03.840
<v Speaker 1>was still there. It wasn't brought into question in the

0:25:03.880 --> 0:25:05.800
<v Speaker 1>courts the way the parts of the c d A

0:25:05.840 --> 0:25:09.800
<v Speaker 1>that specifically dealt with indecency online did. But Section to

0:25:09.960 --> 0:25:13.919
<v Speaker 1>thirty went untouched and it was a doozy. So with

0:25:13.960 --> 0:25:19.080
<v Speaker 1>Section to thirty, online services received immunization from liability regarding

0:25:19.200 --> 0:25:22.639
<v Speaker 1>what their users and third parties published. Section to thirty

0:25:22.720 --> 0:25:28.439
<v Speaker 1>means that these entities things like Facebook, Twitter, Amazon, Google,

0:25:28.920 --> 0:25:33.880
<v Speaker 1>they cannot be held legally responsible for user generated content,

0:25:35.040 --> 0:25:39.480
<v Speaker 1>with only the most minute exceptions, and those most of

0:25:39.480 --> 0:25:42.680
<v Speaker 1>those would come much much later. It's sort of a

0:25:42.760 --> 0:25:45.200
<v Speaker 1>get out of jail free card. Especially in the early

0:25:45.280 --> 0:25:49.199
<v Speaker 1>days when drafting the language, Widen and Cox were careful

0:25:49.240 --> 0:25:52.760
<v Speaker 1>to avoid being too broad. Uh. The idea was that

0:25:52.840 --> 0:25:56.800
<v Speaker 1>outright criminal activities and stuff like copyright infringement wouldn't receive

0:25:56.880 --> 0:26:00.440
<v Speaker 1>full protection under too thirty, but pretty much anything else

0:26:00.600 --> 0:26:03.720
<v Speaker 1>was at least that was the potential for it. Now

0:26:03.760 --> 0:26:07.680
<v Speaker 1>here's the thing about laws. They get tested in the courts.

0:26:08.400 --> 0:26:12.600
<v Speaker 1>Courts are left to interpret and enforce laws. So Congress

0:26:13.119 --> 0:26:16.399
<v Speaker 1>writes the laws. The President approves the laws, but the

0:26:16.480 --> 0:26:19.919
<v Speaker 1>laws are interpreted and enforced in the court system, in

0:26:19.960 --> 0:26:23.160
<v Speaker 1>the judicial system, So the fact that the courts could

0:26:23.160 --> 0:26:26.760
<v Speaker 1>interpret this meant that there was still a question as

0:26:26.800 --> 0:26:30.560
<v Speaker 1>to whether the court would say that Section to thirty

0:26:30.640 --> 0:26:34.360
<v Speaker 1>would mean that online services would have a conditional shield,

0:26:34.440 --> 0:26:38.200
<v Speaker 1>a conditional immunity to liability as long as they did

0:26:38.280 --> 0:26:41.280
<v Speaker 1>operate in good faith, you know, kind of like if

0:26:41.280 --> 0:26:45.200
<v Speaker 1>they were told to remove something because it was illegal

0:26:45.280 --> 0:26:47.480
<v Speaker 1>or harmful, that they then went and did so, and

0:26:47.520 --> 0:26:50.560
<v Speaker 1>then they'd be fine. Or the courts could interpret a

0:26:50.560 --> 0:26:52.840
<v Speaker 1>different way. They could say that the protections are more

0:26:52.920 --> 0:26:56.920
<v Speaker 1>broad and they could give online services complete freedom from

0:26:56.960 --> 0:27:00.760
<v Speaker 1>liability unless an exception were to be applied. And as

0:27:00.760 --> 0:27:04.120
<v Speaker 1>it turned out, the court system leaned toward option number two,

0:27:04.400 --> 0:27:08.840
<v Speaker 1>that broad application approach, and it wasn't done lightly or easily.

0:27:09.080 --> 0:27:10.840
<v Speaker 1>I would love to go into this more, but it

0:27:10.840 --> 0:27:12.800
<v Speaker 1>would take up way too much time, and trust me,

0:27:12.880 --> 0:27:14.640
<v Speaker 1>this episode is going to be a long one. So

0:27:15.040 --> 0:27:17.359
<v Speaker 1>if you want to learn about the legal decisions that

0:27:17.359 --> 0:27:20.560
<v Speaker 1>would codify the extent to which Section to thirty protects

0:27:20.600 --> 0:27:24.960
<v Speaker 1>online services, read Jeff Kossoff's book that I mentioned earlier now.

0:27:24.960 --> 0:27:29.280
<v Speaker 1>When Widen and Cox put this plan together, their concept

0:27:29.760 --> 0:27:33.760
<v Speaker 1>was that these service providers, protected by immunity to legal

0:27:33.800 --> 0:27:38.400
<v Speaker 1>repercussions as far as user generated content is concerned, would

0:27:38.440 --> 0:27:42.399
<v Speaker 1>be freed up to moderate that user generated content as

0:27:42.560 --> 0:27:44.920
<v Speaker 1>much as they needed to. The goal was to create

0:27:44.960 --> 0:27:49.359
<v Speaker 1>a safety structure so that Prodigy or America Online or

0:27:49.600 --> 0:27:53.399
<v Speaker 1>much later, Amazon or Facebook or Google would have the

0:27:53.520 --> 0:27:58.280
<v Speaker 1>freedom to exercise objectionable material off the site without risking

0:27:58.720 --> 0:28:03.080
<v Speaker 1>being seen as a published that has liability like Prodigy

0:28:03.359 --> 0:28:06.639
<v Speaker 1>was a few years earlier. And I've seen this described

0:28:06.720 --> 0:28:11.200
<v Speaker 1>as the sword and shield approach. The shield is that immunity,

0:28:11.280 --> 0:28:15.080
<v Speaker 1>and the sword is that editorial capacity to intervene without

0:28:15.280 --> 0:28:19.520
<v Speaker 1>fear of retribution. But there was a problem. Platforms began

0:28:19.600 --> 0:28:23.160
<v Speaker 1>to adopt a tendency to just rely on the shield part.

0:28:23.800 --> 0:28:28.040
<v Speaker 1>Frequently they did very little to editorialize or to moderate.

0:28:28.640 --> 0:28:31.520
<v Speaker 1>Now this might sound familiar to you. Over the past

0:28:31.520 --> 0:28:34.480
<v Speaker 1>few years, Twitter, for example, has come under fire for

0:28:34.560 --> 0:28:38.120
<v Speaker 1>being reticent when it comes to applying the company's own

0:28:38.280 --> 0:28:41.440
<v Speaker 1>terms of service as far as content goes. Time and again,

0:28:41.480 --> 0:28:45.520
<v Speaker 1>people have cited tweets from various users and asked Twitter's

0:28:45.560 --> 0:28:50.000
<v Speaker 1>management why such examples are allowed to stay on Twitter when,

0:28:50.520 --> 0:28:54.960
<v Speaker 1>but at least what is arguably a reasonable interpretation, those

0:28:54.960 --> 0:28:58.719
<v Speaker 1>tweets violate the code that Twitter says it has in place.

0:28:59.280 --> 0:29:02.600
<v Speaker 1>We've seen this a hunt with certain politicians in particular,

0:29:02.960 --> 0:29:05.440
<v Speaker 1>and it was only recently that Twitter would even flag

0:29:05.520 --> 0:29:10.600
<v Speaker 1>posts from prominent politicians like the President as containing misleading

0:29:10.640 --> 0:29:14.960
<v Speaker 1>information or untruths, and Twitter in no way rushed to

0:29:15.040 --> 0:29:19.440
<v Speaker 1>address this problem. I'll get to why they ultimately did later,

0:29:20.040 --> 0:29:22.920
<v Speaker 1>but spoiler alert, it doesn't really have anything to do

0:29:22.960 --> 0:29:25.760
<v Speaker 1>with Section to thirty. Now. I don't mean to just

0:29:26.040 --> 0:29:29.240
<v Speaker 1>single out Twitter and ignore everyone else, because, as I said,

0:29:29.680 --> 0:29:32.720
<v Speaker 1>it was far more common across the board for platforms

0:29:32.760 --> 0:29:35.360
<v Speaker 1>to take a very hands off approach when it came

0:29:35.400 --> 0:29:40.240
<v Speaker 1>to moderating content. Typically, they only stepped in during particularly

0:29:40.320 --> 0:29:44.160
<v Speaker 1>extreme or blatant abuses of the platform's policies, and not

0:29:44.240 --> 0:29:48.640
<v Speaker 1>always even then. All of this despite that immunity granted

0:29:48.680 --> 0:29:51.840
<v Speaker 1>by Section to thirty. There were a couple of reasons

0:29:51.840 --> 0:29:54.360
<v Speaker 1>for this. One is that, as I mentioned in the

0:29:54.400 --> 0:29:58.840
<v Speaker 1>Facebook algorithm episode that published last week, companies like Facebook

0:29:59.160 --> 0:30:04.040
<v Speaker 1>benefit financially from people being active on their platforms and

0:30:04.240 --> 0:30:09.920
<v Speaker 1>controversial posts generate a lot of action, so you could argue, hey,

0:30:09.960 --> 0:30:12.520
<v Speaker 1>that bad stuff that we would rather not have on

0:30:12.560 --> 0:30:15.520
<v Speaker 1>these platforms, that's making the platforms a lot of money,

0:30:15.680 --> 0:30:17.880
<v Speaker 1>so there's not a lot of financial incentive for them

0:30:17.920 --> 0:30:21.760
<v Speaker 1>to act against it. Second, over the past few years,

0:30:21.880 --> 0:30:25.520
<v Speaker 1>several platforms have emerged that seek to encourage trolling and

0:30:25.560 --> 0:30:29.240
<v Speaker 1>malicious behaviors. Like they're not just hosting it, their whole

0:30:29.320 --> 0:30:33.040
<v Speaker 1>purpose is to be a hot spot for that, and

0:30:33.080 --> 0:30:36.080
<v Speaker 1>they rely on Section to thirty to shield them from

0:30:36.080 --> 0:30:40.480
<v Speaker 1>repercussions because that immunity, at least at first, extended so

0:30:40.560 --> 0:30:43.680
<v Speaker 1>far that even if platform were to distribute or perhaps

0:30:43.680 --> 0:30:48.080
<v Speaker 1>even encourage the distribution of malicious content, it was still

0:30:48.080 --> 0:30:52.400
<v Speaker 1>protected as long as it was not generating the content.

0:30:52.600 --> 0:30:54.920
<v Speaker 1>If it was someone else was using their platform to

0:30:55.040 --> 0:30:58.240
<v Speaker 1>spread terrible stuff, they were still in the clear because

0:30:58.280 --> 0:31:01.040
<v Speaker 1>Section to thirty gave them that protect action. There were

0:31:01.080 --> 0:31:04.440
<v Speaker 1>numerous court cases that challenge this in different ways, including

0:31:04.480 --> 0:31:08.240
<v Speaker 1>ones that would see plaintiffs sup platforms for negligence for

0:31:08.320 --> 0:31:11.360
<v Speaker 1>failing to take down a harmful post after being told

0:31:11.400 --> 0:31:14.440
<v Speaker 1>about it, But early on courts and decided that if

0:31:14.440 --> 0:31:17.920
<v Speaker 1>they found in favor of plaintiffs in these cases, it

0:31:17.920 --> 0:31:21.280
<v Speaker 1>would just represent a work around for Section two thirty,

0:31:21.400 --> 0:31:24.920
<v Speaker 1>and it would essentially invalidate the protections entirely, because all

0:31:24.920 --> 0:31:27.600
<v Speaker 1>it would do is send the message of don't sue

0:31:28.000 --> 0:31:32.600
<v Speaker 1>Twitter for libel, for example, suthe them for negligence. So

0:31:33.600 --> 0:31:36.880
<v Speaker 1>that would mean that you would just have a different

0:31:36.880 --> 0:31:40.280
<v Speaker 1>pathway to go after these platforms, and Section to thirty

0:31:40.360 --> 0:31:42.960
<v Speaker 1>would be meaningless. So the courts decided that was unacceptable,

0:31:43.440 --> 0:31:46.720
<v Speaker 1>and they ruled early on that immunity from liability extended

0:31:46.800 --> 0:31:50.800
<v Speaker 1>beyond stuff like libel. In fact, some of the rulings

0:31:50.800 --> 0:31:54.360
<v Speaker 1>appeared to give online companies even more protection than Chris Cox,

0:31:54.440 --> 0:31:56.800
<v Speaker 1>one of the two original drafters of the law, had

0:31:56.840 --> 0:31:59.440
<v Speaker 1>in mind. He said, it may be that this was

0:31:59.480 --> 0:32:04.480
<v Speaker 1>applied more broadly than we had intended for malicious websites

0:32:04.520 --> 0:32:06.800
<v Speaker 1>and forums. This could mean that if you have a

0:32:06.840 --> 0:32:11.240
<v Speaker 1>particular agenda and a means to launch an online platform,

0:32:11.400 --> 0:32:14.480
<v Speaker 1>you can push your agenda even if it causes harm

0:32:14.560 --> 0:32:18.040
<v Speaker 1>to other people by giving sympathizers. You know people who

0:32:18.080 --> 0:32:21.200
<v Speaker 1>share your philosophy if you give them a place to

0:32:21.200 --> 0:32:24.920
<v Speaker 1>promote their ideology your ideology, as long as you're careful

0:32:24.960 --> 0:32:27.800
<v Speaker 1>not to do it. Yourself, because you're really just providing

0:32:27.800 --> 0:32:30.160
<v Speaker 1>a place for third parties to do it. If you

0:32:30.160 --> 0:32:32.320
<v Speaker 1>start to publish your own words, you no longer have

0:32:32.400 --> 0:32:35.080
<v Speaker 1>protection because you're not acting as a distributor for a

0:32:35.160 --> 0:32:39.680
<v Speaker 1>third party's content, and and that would be fine. So

0:32:39.800 --> 0:32:42.200
<v Speaker 1>we saw it happen a lot. We still do. And

0:32:42.200 --> 0:32:45.880
<v Speaker 1>then third, over the years, the government has steadily chipped

0:32:45.920 --> 0:32:50.160
<v Speaker 1>away bit by bit at that protective shield, with various

0:32:50.160 --> 0:32:55.320
<v Speaker 1>court cases leading judges to interpret exemptions for that immunity

0:32:55.560 --> 0:32:58.680
<v Speaker 1>to liability. And that makes platforms a little less keen

0:32:58.760 --> 0:33:03.280
<v Speaker 1>on editorializing fear of being pulled into one of those exceptions. Now,

0:33:03.280 --> 0:33:05.960
<v Speaker 1>when we come back, I'll talk a bit more about

0:33:06.000 --> 0:33:08.720
<v Speaker 1>the ways that courts have eroded Section to thirty from

0:33:08.760 --> 0:33:12.720
<v Speaker 1>its original and arguably o P status. But first, let's

0:33:12.760 --> 0:33:22.920
<v Speaker 1>take another quick break. All right, guys, you know what,

0:33:23.000 --> 0:33:25.400
<v Speaker 1>I guess it's about time we kind of jumped back

0:33:25.440 --> 0:33:28.120
<v Speaker 1>into the present. So the nineties were fun and all,

0:33:28.160 --> 0:33:33.440
<v Speaker 1>but take off the flannel, stop listening to grunge, forget

0:33:33.440 --> 0:33:35.520
<v Speaker 1>about my so called life for a minute, and let's

0:33:35.520 --> 0:33:37.240
<v Speaker 1>all get back in the time. Everyone back in the

0:33:37.280 --> 0:33:42.280
<v Speaker 1>time machine, you two, all right, I'll push the button

0:33:52.640 --> 0:33:56.040
<v Speaker 1>for the first decade of its existence. Section to thirty

0:33:56.120 --> 0:33:59.000
<v Speaker 1>was kind of like a bulletproof vest for online platforms

0:33:59.000 --> 0:34:01.760
<v Speaker 1>when it came to liability linked to user and third

0:34:01.800 --> 0:34:07.400
<v Speaker 1>party content. There are numerous incredible court cases featuring some

0:34:07.560 --> 0:34:12.879
<v Speaker 1>really sympathetic plaintiffs, you know, people who inarguably suffered hardships

0:34:13.000 --> 0:34:17.520
<v Speaker 1>because of someone sharing harmful or abuse of materials online.

0:34:18.400 --> 0:34:20.920
<v Speaker 1>And the message seemed to be that, at least in

0:34:21.000 --> 0:34:25.399
<v Speaker 1>some cases, there was no real legal recourse for these

0:34:25.400 --> 0:34:29.799
<v Speaker 1>people to seek out justice. If the perpetrator who's publishing

0:34:30.200 --> 0:34:35.480
<v Speaker 1>this harmful information is anonymous, it can be really hard

0:34:35.560 --> 0:34:38.080
<v Speaker 1>to track that person down and hold them accountable for

0:34:38.160 --> 0:34:42.359
<v Speaker 1>what they said online. There are lots of ways that

0:34:42.400 --> 0:34:46.120
<v Speaker 1>people can hide their identity, including ways to hide their

0:34:46.120 --> 0:34:50.200
<v Speaker 1>IP address, which means that in some cases it would

0:34:50.239 --> 0:34:53.279
<v Speaker 1>just be impossible to figure out who was ultimately responsible.

0:34:53.360 --> 0:34:57.120
<v Speaker 1>And Section to thirty would shield the platforms from legal action,

0:34:57.400 --> 0:35:00.800
<v Speaker 1>which meant that the victim would have no real options

0:35:01.320 --> 0:35:04.239
<v Speaker 1>and that rubbed a lot of people the wrong way. Now,

0:35:04.280 --> 0:35:06.560
<v Speaker 1>before I get into details, I do want to say

0:35:06.600 --> 0:35:10.360
<v Speaker 1>that I acknowledged this is a very tricky situation. On

0:35:10.400 --> 0:35:13.600
<v Speaker 1>the one hand, it seems unreasonable to hold a platform

0:35:13.680 --> 0:35:18.040
<v Speaker 1>accountable for something that it didn't generate. It wasn't responsible

0:35:18.080 --> 0:35:20.839
<v Speaker 1>for creating it. So if I pop onto Twitter and

0:35:20.920 --> 0:35:24.800
<v Speaker 1>I post harmful lies about you, it's not Twitter's fault

0:35:24.960 --> 0:35:27.920
<v Speaker 1>that I did that, right, It's my fault, and Twitter

0:35:28.200 --> 0:35:31.600
<v Speaker 1>should be protected from being unfairly lumped in with me

0:35:31.960 --> 0:35:36.640
<v Speaker 1>on that matter. Online platforms serve millions or even billions

0:35:36.680 --> 0:35:39.279
<v Speaker 1>of people, and there's just no way to filter every

0:35:39.280 --> 0:35:42.319
<v Speaker 1>single post from every single person to make sure that

0:35:42.400 --> 0:35:46.479
<v Speaker 1>there's nothing harmful there. But on the other hand, let's

0:35:46.480 --> 0:35:50.800
<v Speaker 1>say I post something that is demonstrably false and harmful

0:35:51.080 --> 0:35:54.880
<v Speaker 1>directed towards you, and you alert the platform I've used

0:35:55.040 --> 0:35:58.480
<v Speaker 1>to this problem. If the platform fails to act to

0:35:58.600 --> 0:36:01.920
<v Speaker 1>take down that post or perhaps even go further, maybe

0:36:01.960 --> 0:36:05.400
<v Speaker 1>ban me from using the service, then doesn't that suggest

0:36:05.400 --> 0:36:08.399
<v Speaker 1>the platform itself should be held accountable. I mean, it's

0:36:08.440 --> 0:36:12.680
<v Speaker 1>allowing a wrong to continue. Is there no responsibility to

0:36:12.719 --> 0:36:16.560
<v Speaker 1>prevent harm? And if there isn't, what makes the Internet

0:36:16.600 --> 0:36:20.880
<v Speaker 1>different from other things that law covers Because other areas

0:36:20.920 --> 0:36:23.400
<v Speaker 1>of the world that you know, in the legal world

0:36:23.400 --> 0:36:26.560
<v Speaker 1>in the United States, they don't enjoy this protection. But

0:36:26.640 --> 0:36:29.399
<v Speaker 1>it's a really complex issue, and it reminds us that

0:36:29.520 --> 0:36:32.440
<v Speaker 1>you can have a lot of things that are really important,

0:36:32.480 --> 0:36:35.040
<v Speaker 1>like freedom of speech or a right to privacy or

0:36:35.080 --> 0:36:38.040
<v Speaker 1>an expectation of security, and you can have those come

0:36:38.040 --> 0:36:40.960
<v Speaker 1>into conflict with one another, and it ultimately means that

0:36:41.239 --> 0:36:44.239
<v Speaker 1>whatever decision you make, it's not going to be satisfying

0:36:44.280 --> 0:36:48.440
<v Speaker 1>to everybody. Starting it. Around two thousand eight, courts began

0:36:48.520 --> 0:36:51.360
<v Speaker 1>to rule that Section two thirty wasn't a perfect force

0:36:51.440 --> 0:36:56.520
<v Speaker 1>field protecting online services from all liability. In California, a

0:36:56.560 --> 0:37:01.080
<v Speaker 1>pair of fair housing nonprofit organizations brought a lawsuit against

0:37:01.120 --> 0:37:04.680
<v Speaker 1>a website called roommates dot Com. They said that the

0:37:04.719 --> 0:37:08.560
<v Speaker 1>site was encouraging users to post and sort housing opportunities

0:37:08.880 --> 0:37:13.440
<v Speaker 1>in a discriminatory way, and that violated federal and state law.

0:37:13.920 --> 0:37:17.040
<v Speaker 1>It is illegal to advertise housing with a language that

0:37:17.080 --> 0:37:23.080
<v Speaker 1>indicates preference, limitation, or discrimination based on race, sex, familial status,

0:37:23.080 --> 0:37:25.880
<v Speaker 1>and that kind of thing. But roommates dot Com allowed

0:37:25.960 --> 0:37:29.160
<v Speaker 1>users to fill out fields on all that kind of stuff.

0:37:28.880 --> 0:37:32.960
<v Speaker 1>You could create a profile where you included things like

0:37:33.360 --> 0:37:38.000
<v Speaker 1>your gender, your familial you know status, your sexual orientation,

0:37:38.000 --> 0:37:40.200
<v Speaker 1>all this kind of stuff, and some people on the

0:37:40.200 --> 0:37:45.120
<v Speaker 1>site started posting discriminatory notices saying things like, you know,

0:37:45.239 --> 0:37:48.480
<v Speaker 1>essentially only white people need to apply that kind of stuff.

0:37:48.800 --> 0:37:52.120
<v Speaker 1>Terrible stuff. Now, the lawyer for roommates dot Com argued

0:37:52.239 --> 0:37:55.319
<v Speaker 1>that the site was protected under Section to thirty, but

0:37:55.440 --> 0:37:59.040
<v Speaker 1>the plaintiffs lawyer said, hang on roommates is totally setting

0:37:59.080 --> 0:38:02.040
<v Speaker 1>all this up because it has people fill in that

0:38:02.120 --> 0:38:05.439
<v Speaker 1>information in the first place. It asks people to give

0:38:05.480 --> 0:38:09.560
<v Speaker 1>that that those details. Now, the case was initially dismissed

0:38:09.560 --> 0:38:13.000
<v Speaker 1>in a lower court, but an appeals court would take

0:38:13.040 --> 0:38:17.000
<v Speaker 1>it into further consideration, and that three judge court ultimately

0:38:17.040 --> 0:38:21.040
<v Speaker 1>decided that with a very narrow focus, roommates dot Com

0:38:21.160 --> 0:38:26.160
<v Speaker 1>was liable for asking questions that were allegedly discriminatory, but

0:38:26.320 --> 0:38:29.720
<v Speaker 1>that it was not liable for the content that users

0:38:29.719 --> 0:38:33.759
<v Speaker 1>were writing in the site, like under additional comments. And

0:38:33.840 --> 0:38:38.000
<v Speaker 1>it's a fine distinction, but it marked a small weakness

0:38:38.040 --> 0:38:42.200
<v Speaker 1>in two thirties armor. Moreover, a subsequent hearing found that

0:38:42.320 --> 0:38:46.759
<v Speaker 1>a website develops content if it quote contributes materially to

0:38:46.800 --> 0:38:51.040
<v Speaker 1>the alleged illegality of the conduct end quote, which would

0:38:51.080 --> 0:38:53.840
<v Speaker 1>mean in those cases the service would no longer be

0:38:53.960 --> 0:38:58.040
<v Speaker 1>a simple publisher or distributor. It would be a developer

0:38:58.160 --> 0:39:01.640
<v Speaker 1>of content, and thus to thirty protection would not apply.

0:39:02.560 --> 0:39:06.680
<v Speaker 1>Subsequent court cases reinforce the idea that if a website

0:39:06.800 --> 0:39:11.680
<v Speaker 1>quote unquote materially contributes to the illegality of material posted

0:39:11.719 --> 0:39:14.960
<v Speaker 1>to that site by third parties, it would not or

0:39:15.040 --> 0:39:18.520
<v Speaker 1>may not qualify for Section to thirty immunity. So the

0:39:18.560 --> 0:39:21.880
<v Speaker 1>parameters of protection began to change a little bit. Should

0:39:21.880 --> 0:39:24.360
<v Speaker 1>a court find that a site had not just allowed

0:39:24.480 --> 0:39:27.400
<v Speaker 1>users to post a legal material, but to somehow be

0:39:27.840 --> 0:39:31.759
<v Speaker 1>active in that process beyond just being a publication platform,

0:39:32.200 --> 0:39:34.839
<v Speaker 1>then it could be held accountable. But while there were

0:39:34.840 --> 0:39:39.279
<v Speaker 1>new parameters, they weren't strictly defined, and courts would have

0:39:39.360 --> 0:39:43.200
<v Speaker 1>to interpret specific cases within the context of this kind

0:39:43.200 --> 0:39:47.640
<v Speaker 1>of vague notion of restrictions to immunity. A subsequent case

0:39:47.680 --> 0:39:52.120
<v Speaker 1>brought against Yahoo by a woman named Cecilia Barnes would

0:39:52.160 --> 0:39:57.000
<v Speaker 1>further complicate matters. Barnes's ex boyfriend created a fake profile

0:39:57.160 --> 0:40:01.759
<v Speaker 1>on Yahoo, claiming that the profile will longed to Cecilia,

0:40:01.840 --> 0:40:05.040
<v Speaker 1>and he included nude pictures of Barnes that he had

0:40:05.080 --> 0:40:10.279
<v Speaker 1>taken without her consent, which is truly horrifying. And then

0:40:10.320 --> 0:40:14.760
<v Speaker 1>he also included her work contact information and before long

0:40:15.480 --> 0:40:18.319
<v Speaker 1>men were showing up and trying to contact Cecilia, and

0:40:18.360 --> 0:40:19.960
<v Speaker 1>that must have come as a real shock to her.

0:40:20.000 --> 0:40:23.640
<v Speaker 1>I can't imagine how disruptive that had to have been

0:40:23.680 --> 0:40:27.360
<v Speaker 1>to her life. Cecilia found a link on Yahoo that

0:40:27.480 --> 0:40:31.160
<v Speaker 1>explained what people should do in the event that they

0:40:31.160 --> 0:40:35.400
<v Speaker 1>wanted to claim a profile that purported to represent them

0:40:35.640 --> 0:40:38.360
<v Speaker 1>was in fact a fake, and it involves sending an

0:40:38.400 --> 0:40:41.880
<v Speaker 1>assigned statement and a copy of their ID to Yahoo

0:40:42.239 --> 0:40:47.319
<v Speaker 1>via snail mail. So not exactly the fastest or most

0:40:47.360 --> 0:40:50.600
<v Speaker 1>streamlined of processes, but Barnes went ahead and did it,

0:40:51.560 --> 0:40:54.440
<v Speaker 1>but the Yahoo profile stayed up. Barnes had heard nothing

0:40:54.480 --> 0:40:57.880
<v Speaker 1>back from Yahoo, so she tried it again a couple

0:40:57.920 --> 0:41:01.719
<v Speaker 1>of times and still didn't receive any reply. Then she

0:41:01.840 --> 0:41:05.320
<v Speaker 1>was scheduled to give an interview on local television and

0:41:05.840 --> 0:41:09.800
<v Speaker 1>talk about her experience, when miraculously, a Yahoo representative actually

0:41:09.800 --> 0:41:12.880
<v Speaker 1>reached out to her. Now that representative was the director

0:41:12.920 --> 0:41:17.200
<v Speaker 1>of communications at Yahoo, and the director of communications promised

0:41:17.239 --> 0:41:22.960
<v Speaker 1>Cecilia that she would take a fact request from Cecilia

0:41:23.160 --> 0:41:26.920
<v Speaker 1>over to the proper division by hand and make certain

0:41:26.960 --> 0:41:30.520
<v Speaker 1>that the profile was removed. And the profile was not

0:41:30.680 --> 0:41:33.640
<v Speaker 1>removed it stayed up for another couple of months. So

0:41:34.040 --> 0:41:37.000
<v Speaker 1>Barnes goes and sues Yahoo. Now I'm going to skip

0:41:37.040 --> 0:41:40.440
<v Speaker 1>most of the court process, But ultimately the case hinged

0:41:40.480 --> 0:41:44.040
<v Speaker 1>on the fact that a Yahoo representative had made a

0:41:44.120 --> 0:41:48.879
<v Speaker 1>promise to do something but then didn't do it, and

0:41:49.000 --> 0:41:52.840
<v Speaker 1>that the court found was outside the protections of section

0:41:52.920 --> 0:41:57.359
<v Speaker 1>two thirty. Ironically, if Yahoo had not reached out at all,

0:41:57.440 --> 0:41:59.640
<v Speaker 1>if the company had just allowed things to keep on

0:41:59.680 --> 0:42:01.839
<v Speaker 1>going as they were going with the fake profile up

0:42:01.880 --> 0:42:05.880
<v Speaker 1>and they just never replied to Barnes, Section to thirty

0:42:05.920 --> 0:42:09.000
<v Speaker 1>would still have applied to Yahoo. It was only because

0:42:09.239 --> 0:42:12.520
<v Speaker 1>the representative had promised to do something and did not

0:42:12.680 --> 0:42:16.480
<v Speaker 1>follow through that the company was found liable. Now, if

0:42:16.560 --> 0:42:19.839
<v Speaker 1>y'all who had actually pulled down that profile, there also

0:42:19.880 --> 0:42:21.480
<v Speaker 1>would have been nothing to talk about here. So if

0:42:21.520 --> 0:42:23.520
<v Speaker 1>they had done what they said they were going to do,

0:42:23.880 --> 0:42:26.560
<v Speaker 1>there also wouldn't have been a problem. So literally, Yah,

0:42:26.560 --> 0:42:29.080
<v Speaker 1>who went down the one pathway where there still would

0:42:29.120 --> 0:42:33.480
<v Speaker 1>be liability. Barnes actually ultimately withdrew her lawsuit before it

0:42:33.480 --> 0:42:36.440
<v Speaker 1>would go through the entire court process, but that earlier

0:42:36.560 --> 0:42:41.320
<v Speaker 1>finding in court would hold and it would oddly discourage

0:42:41.360 --> 0:42:45.240
<v Speaker 1>platforms from taking a more active role in moderation, because

0:42:45.520 --> 0:42:49.120
<v Speaker 1>if a site did promise to remove something and then

0:42:49.160 --> 0:42:51.960
<v Speaker 1>they didn't do it in a timely enough manner, they

0:42:52.000 --> 0:42:55.360
<v Speaker 1>could be held liable for that because they didn't carry

0:42:55.360 --> 0:42:58.200
<v Speaker 1>through on a promise. If they did nothing at all,

0:42:58.400 --> 0:43:01.560
<v Speaker 1>they wouldn't be liable. They beat protected under section to thirty.

0:43:01.640 --> 0:43:04.680
<v Speaker 1>And I don't know about you, but doing nothing tends

0:43:04.719 --> 0:43:07.520
<v Speaker 1>to be easier than doing something. I mean, it's even

0:43:07.560 --> 0:43:10.600
<v Speaker 1>easier than promising to do something but not doing it.

0:43:10.719 --> 0:43:13.160
<v Speaker 1>Just not doing anything at all, it's still the easiest

0:43:13.160 --> 0:43:15.960
<v Speaker 1>thing to do. So in a way, these rulings that

0:43:16.080 --> 0:43:20.160
<v Speaker 1>found limitations to two thirty reinforce the behaviors of companies

0:43:20.200 --> 0:43:23.799
<v Speaker 1>that were reluctant to moderate the content on their platforms.

0:43:24.280 --> 0:43:28.280
<v Speaker 1>More recently, cases have been brought to light that section

0:43:28.320 --> 0:43:31.680
<v Speaker 1>to can play a role in suppressing voices of marginalized

0:43:31.680 --> 0:43:34.840
<v Speaker 1>and vulnerable population. So, in other words, a piece of

0:43:34.920 --> 0:43:39.040
<v Speaker 1>legislation tied to the spirit of free speech could in

0:43:39.120 --> 0:43:43.400
<v Speaker 1>itself be suppressing the free speech of others. For example,

0:43:43.640 --> 0:43:48.000
<v Speaker 1>while there are plenty of cases of online harassment campaigns

0:43:48.040 --> 0:43:52.280
<v Speaker 1>for all sorts of people, women represent a disproportionate number

0:43:52.640 --> 0:43:57.800
<v Speaker 1>of victims of online harassment. Women, particularly young women, encounter

0:43:57.920 --> 0:44:02.520
<v Speaker 1>sexualized online abuse are more frequently than men do, and

0:44:02.600 --> 0:44:05.560
<v Speaker 1>so there is a real issue of Section to thirty

0:44:05.600 --> 0:44:10.919
<v Speaker 1>providing immunity to platforms that house communities who are perpetuating

0:44:10.960 --> 0:44:13.880
<v Speaker 1>an abusive set of behaviors, which is not great and

0:44:13.960 --> 0:44:17.000
<v Speaker 1>other vulnerable populations face this too. We see it in

0:44:17.080 --> 0:44:22.239
<v Speaker 1>terms of race and sexual orientation, religious affiliations, political affiliations,

0:44:22.280 --> 0:44:25.600
<v Speaker 1>and more. And that harassment can have the effect of

0:44:25.719 --> 0:44:29.239
<v Speaker 1>silencing the people who are being harassed, So it is

0:44:29.280 --> 0:44:34.080
<v Speaker 1>a form of suppression of the freedom of speech. So

0:44:34.440 --> 0:44:37.719
<v Speaker 1>courts have whittled back a bit of the Section to

0:44:37.920 --> 0:44:40.880
<v Speaker 1>thirty protection and we have seen a bit more of

0:44:40.920 --> 0:44:45.799
<v Speaker 1>a move towards moderating content on platforms. However, this is

0:44:45.840 --> 0:44:49.279
<v Speaker 1>not out of a fear of legal liability. Instead, it's

0:44:49.320 --> 0:44:53.680
<v Speaker 1>because of consumer demand. We've seen platforms like Facebook and

0:44:53.719 --> 0:44:58.279
<v Speaker 1>YouTube and Twitter get more involved in content moderation, not

0:44:58.400 --> 0:45:02.680
<v Speaker 1>because the government was, you know, not going to provide

0:45:02.719 --> 0:45:05.879
<v Speaker 1>them immunity. The immunity, the illegal immunity was still there.

0:45:06.480 --> 0:45:09.719
<v Speaker 1>It's because users were demanding it and a failure to

0:45:10.040 --> 0:45:14.400
<v Speaker 1>act could have resulted in users dumping the services. And

0:45:14.440 --> 0:45:17.640
<v Speaker 1>these companies could still operate with an incredible amount of

0:45:17.760 --> 0:45:20.759
<v Speaker 1>legal protection, but that doesn't save them from the consequences

0:45:20.760 --> 0:45:25.200
<v Speaker 1>of people abandoning their their business. They need those customers.

0:45:25.560 --> 0:45:30.280
<v Speaker 1>And then in Congress passed a bill that amended section

0:45:30.560 --> 0:45:34.640
<v Speaker 1>to thirty. It removed protections for any site that knowingly

0:45:34.719 --> 0:45:38.960
<v Speaker 1>contributes to or supports sex trafficking. While the goal of

0:45:39.000 --> 0:45:42.319
<v Speaker 1>eliminating the support of sex trafficking is a really good one,

0:45:42.320 --> 0:45:46.560
<v Speaker 1>it's one we absolutely need to focus on. The actual

0:45:46.640 --> 0:45:50.920
<v Speaker 1>bill itself would receive some criticism, not for its purpose

0:45:51.000 --> 0:45:53.960
<v Speaker 1>but in its creation, like in its wording. So law

0:45:54.000 --> 0:45:58.439
<v Speaker 1>professor Eric Goldman wrote that quote As a result, liability

0:45:58.520 --> 0:46:02.600
<v Speaker 1>based on knowledge pushes internet companies to adopt one of

0:46:02.760 --> 0:46:08.200
<v Speaker 1>two extreme positions moderate all content perfectly and accept the

0:46:08.280 --> 0:46:12.720
<v Speaker 1>legal risk for any errors, or don't moderate content at all,

0:46:12.760 --> 0:46:16.719
<v Speaker 1>as a way of negating knowledge. So when you think

0:46:16.760 --> 0:46:20.399
<v Speaker 1>of it that way, if if the law says if

0:46:20.440 --> 0:46:23.839
<v Speaker 1>you know that this is happening, you're obligated to stop it,

0:46:23.960 --> 0:46:26.880
<v Speaker 1>or if not, you're going to be held liable, then

0:46:28.040 --> 0:46:31.040
<v Speaker 1>that also opens up the opportunity to quote unquote not

0:46:31.280 --> 0:46:35.120
<v Speaker 1>know it is happening. It creates an incentive to not

0:46:35.320 --> 0:46:39.560
<v Speaker 1>get involved, which is like the earlier problems that I

0:46:39.600 --> 0:46:42.759
<v Speaker 1>mentioned in this episode. But you know more, but any

0:46:42.800 --> 0:46:45.440
<v Speaker 1>system designed by humans is going to be imperfect, right,

0:46:45.840 --> 0:46:48.600
<v Speaker 1>And that brings us up to this year where we're

0:46:48.600 --> 0:46:51.840
<v Speaker 1>seeing various politicians and others calling for an end or

0:46:51.880 --> 0:46:56.160
<v Speaker 1>at least an amendment to Section to thirty. President Trump

0:46:56.360 --> 0:47:00.080
<v Speaker 1>appears angry that Twitter, for example, has flagged many of

0:47:00.120 --> 0:47:03.799
<v Speaker 1>his tweets as containing misleading information. He has gone so

0:47:03.840 --> 0:47:06.040
<v Speaker 1>far as to call Section to thirty a threat to

0:47:06.120 --> 0:47:09.919
<v Speaker 1>national security, which echoes something that was actually argued back

0:47:09.920 --> 0:47:13.279
<v Speaker 1>in the nineteen seventies that related to the publication of

0:47:13.320 --> 0:47:16.919
<v Speaker 1>the Pentagon papers. Uh, that tactic didn't work then, and

0:47:16.960 --> 0:47:19.480
<v Speaker 1>I don't think it's really gonna work now. And it

0:47:19.520 --> 0:47:23.880
<v Speaker 1>doesn't help that the root of the problem, which is misinformation,

0:47:24.280 --> 0:47:28.600
<v Speaker 1>is really to blame here. There's also and a misinterpretation

0:47:28.640 --> 0:47:31.120
<v Speaker 1>of Section to thirty going on here because Trump has

0:47:31.200 --> 0:47:35.279
<v Speaker 1>argued that platforms must be neutral in their approach, which

0:47:35.400 --> 0:47:38.520
<v Speaker 1>just isn't true. It's not part of the original law

0:47:38.600 --> 0:47:41.600
<v Speaker 1>at all, Nor is that an interpretation that's been supported

0:47:41.640 --> 0:47:45.160
<v Speaker 1>in the numerous court cases that have shaped the practice

0:47:45.280 --> 0:47:48.360
<v Speaker 1>of Section two thirty. Nowhere does it state that a

0:47:48.400 --> 0:47:50.960
<v Speaker 1>platform has to be neutral. In fact, in some of

0:47:51.000 --> 0:47:54.520
<v Speaker 1>the most famous cases in which Section to thirty protections

0:47:54.520 --> 0:47:59.000
<v Speaker 1>were upheld, it involved content platforms that were most assuredly

0:47:59.440 --> 0:48:02.160
<v Speaker 1>not new neutral, and in at least a few cases,

0:48:02.160 --> 0:48:06.400
<v Speaker 1>they were arguably downright maliciously biased. Now last year, in

0:48:06.440 --> 0:48:11.200
<v Speaker 1>twenty nineteen, Senator Josh Holly, a Republican from Missouri, introduced

0:48:11.280 --> 0:48:14.680
<v Speaker 1>legislation that would require any online service with more than

0:48:14.760 --> 0:48:19.359
<v Speaker 1>thirty million US users or three million users globally, or

0:48:19.360 --> 0:48:21.800
<v Speaker 1>with a revenue of at least five hundred million dollars

0:48:22.080 --> 0:48:25.759
<v Speaker 1>would be required to take a politically neutral stance when

0:48:25.760 --> 0:48:29.400
<v Speaker 1>it came to moderating content in order to qualify for

0:48:29.520 --> 0:48:33.279
<v Speaker 1>Section to thirty protection. So the implication here is that

0:48:33.360 --> 0:48:37.560
<v Speaker 1>the platforms have a bias against a particular political philosophy.

0:48:37.600 --> 0:48:42.760
<v Speaker 1>In this case, he's arguing that they are biased against conservatives,

0:48:43.000 --> 0:48:47.719
<v Speaker 1>and therefore when these platforms moderate content, they tend to

0:48:47.760 --> 0:48:52.319
<v Speaker 1>do so disproportionately to the detriment of conservative voices. Not

0:48:52.480 --> 0:48:55.719
<v Speaker 1>many people are taking this particular proposal seriously because it

0:48:55.719 --> 0:48:59.000
<v Speaker 1>would probably get torn to shreds under First Amendment arguments

0:48:59.000 --> 0:49:01.600
<v Speaker 1>in court. It wouldn't hold up to scrutiny at all.

0:49:02.280 --> 0:49:05.439
<v Speaker 1>Other proposals aimed to follow the path of the teen

0:49:05.480 --> 0:49:09.000
<v Speaker 1>Amendment that covered sex trafficking, with the idea that you

0:49:09.040 --> 0:49:13.000
<v Speaker 1>could do the same thing with other exceptions to the

0:49:13.120 --> 0:49:16.160
<v Speaker 1>section to thirty protection. But one potential problem with that

0:49:16.200 --> 0:49:18.759
<v Speaker 1>approach is that it creates a real mess as far

0:49:18.800 --> 0:49:22.680
<v Speaker 1>as what to thirty does and doesn't apply to, and

0:49:22.719 --> 0:49:25.359
<v Speaker 1>it could potentially reach a point where it's harder to

0:49:25.400 --> 0:49:30.480
<v Speaker 1>tell under what conditions platforms have protection versus the conditions

0:49:30.520 --> 0:49:32.880
<v Speaker 1>where they don't, and it would place a very heavy

0:49:32.920 --> 0:49:36.840
<v Speaker 1>burden on the court system to determine through various lawsuits

0:49:37.160 --> 0:49:40.480
<v Speaker 1>if the defendants, that being the platforms, had met the

0:49:40.600 --> 0:49:43.440
<v Speaker 1>legal burden to qualify for two thirty protection. So, in

0:49:43.440 --> 0:49:47.520
<v Speaker 1>other words, that's not ideal. Either. Then there's the possibility

0:49:47.800 --> 0:49:51.520
<v Speaker 1>that Congress will just repeal TO thirty totally, which would

0:49:51.640 --> 0:49:54.080
<v Speaker 1>have been terrifying to companies back in the nineties when

0:49:54.080 --> 0:49:57.800
<v Speaker 1>they were still trying to establish themselves. But frankly, to

0:49:58.000 --> 0:50:02.000
<v Speaker 1>thirty protection is an im American thing. In other places

0:50:02.040 --> 0:50:06.000
<v Speaker 1>like Europe, these broad protections don't exist in that form,

0:50:06.040 --> 0:50:10.320
<v Speaker 1>and yet social networking platforms forums that kind of stuff.

0:50:10.360 --> 0:50:13.000
<v Speaker 1>They still operate in those places now, granted they have

0:50:13.040 --> 0:50:15.600
<v Speaker 1>to do so while following a more strict set of rules,

0:50:16.040 --> 0:50:18.479
<v Speaker 1>and it's a pain in the butt. But we should

0:50:18.520 --> 0:50:21.719
<v Speaker 1>also remember that the big tech companies that this would

0:50:21.719 --> 0:50:26.120
<v Speaker 1>affect are also heavily involved in mobbying efforts in politics.

0:50:26.160 --> 0:50:28.719
<v Speaker 1>So how likely is it that we're going to see

0:50:28.800 --> 0:50:32.799
<v Speaker 1>section to thirty completely repealed? I honestly don't know, but

0:50:32.840 --> 0:50:35.400
<v Speaker 1>I think it would be a steep, uphill battle because

0:50:35.400 --> 0:50:37.640
<v Speaker 1>you've got a lot of money from these tech companies

0:50:38.040 --> 0:50:41.680
<v Speaker 1>influencing a lot of politicians. According to a great piece

0:50:41.680 --> 0:50:45.120
<v Speaker 1>in Ours Technica titled Section to thirty, the Internet Law

0:50:45.200 --> 0:50:48.800
<v Speaker 1>Politicians Love to hate, explained a law professor at the

0:50:48.880 --> 0:50:53.440
<v Speaker 1>University of Maryland named Danielle Citron, and researcher Ben Wits

0:50:53.600 --> 0:50:57.239
<v Speaker 1>from the Brookings Institution suggests that two thirty should be

0:50:57.239 --> 0:51:00.560
<v Speaker 1>amended so that the platforms receive immunity only if they

0:51:00.640 --> 0:51:05.080
<v Speaker 1>ensure quote reasonable steps to prevent or address unlawful uses

0:51:05.160 --> 0:51:07.960
<v Speaker 1>of its services end quote, leaving a lot of that

0:51:08.040 --> 0:51:11.280
<v Speaker 1>language up for interpretation in the courts. So the idea

0:51:11.360 --> 0:51:14.520
<v Speaker 1>being that you should be fine, you should be immune

0:51:14.640 --> 0:51:19.040
<v Speaker 1>as long as you can prove that whenever bad stuff

0:51:19.080 --> 0:51:21.200
<v Speaker 1>is happening on your platform, you're doing your best to

0:51:21.560 --> 0:51:27.160
<v Speaker 1>stop it. Um So, in cases where a platform was notified, hey,

0:51:27.760 --> 0:51:31.440
<v Speaker 1>some other user has published my private information on your

0:51:31.440 --> 0:51:34.480
<v Speaker 1>platform without my permission. Take it down, they would actually

0:51:34.520 --> 0:51:38.040
<v Speaker 1>go and take it down right now. Section to applies

0:51:38.080 --> 0:51:40.560
<v Speaker 1>to those companies, whether they take anything down or not,

0:51:41.120 --> 0:51:44.920
<v Speaker 1>and that has led to some pretty tragic circumstances in

0:51:44.960 --> 0:51:49.080
<v Speaker 1>the lives of people who have been affected by malicious

0:51:49.200 --> 0:51:53.760
<v Speaker 1>users of various services out there. Now, as I said,

0:51:54.360 --> 0:51:58.720
<v Speaker 1>this is a complicated subject. There is a real need

0:51:58.800 --> 0:52:03.640
<v Speaker 1>to protect freedom of speech because without it, if companies

0:52:03.680 --> 0:52:06.520
<v Speaker 1>can be held liable for everything that users right, we're

0:52:06.520 --> 0:52:09.799
<v Speaker 1>gonna see a disappearance of all of those things that

0:52:09.840 --> 0:52:12.839
<v Speaker 1>we take for granted. Now, I mean, social networks would

0:52:12.840 --> 0:52:15.720
<v Speaker 1>be totally different. We wouldn't be able to leave reviews

0:52:15.760 --> 0:52:19.120
<v Speaker 1>because any company that didn't like a review could end

0:52:19.200 --> 0:52:24.479
<v Speaker 1>up suing the marketplace for hosting that review. It would

0:52:24.480 --> 0:52:27.880
<v Speaker 1>be a huge mess. So we do need something there.

0:52:27.920 --> 0:52:32.120
<v Speaker 1>At the same time, we have to address that the

0:52:32.239 --> 0:52:37.360
<v Speaker 1>rules as they state right now do disproportionately affect vulnerable

0:52:37.360 --> 0:52:40.799
<v Speaker 1>populations in a negative way. And we need to fix that,

0:52:41.920 --> 0:52:44.640
<v Speaker 1>and we've got to figure out how to give more

0:52:44.680 --> 0:52:48.880
<v Speaker 1>incentives for platforms to take an active role in moderating

0:52:48.920 --> 0:52:53.160
<v Speaker 1>the content that appear on those platforms. And to me,

0:52:53.239 --> 0:52:57.000
<v Speaker 1>that's that's a tough tough nut to crack because there's

0:52:57.040 --> 0:52:59.680
<v Speaker 1>not a whole lot of financial incentive to do it unless,

0:53:00.080 --> 0:53:03.400
<v Speaker 1>as we've seen in there's a thread of people leaving

0:53:03.640 --> 0:53:08.120
<v Speaker 1>those platforms. Otherwise there's more of a financial incentive to

0:53:08.200 --> 0:53:11.600
<v Speaker 1>keep it up there. So it's a complicated situation. But

0:53:11.719 --> 0:53:14.840
<v Speaker 1>I hope that this helps you have an understanding of

0:53:14.880 --> 0:53:17.440
<v Speaker 1>what section to thirty is, what it was intended to do,

0:53:17.560 --> 0:53:20.719
<v Speaker 1>and what it actually has done, because, as we know,

0:53:21.600 --> 0:53:26.120
<v Speaker 1>often we will create a construct planning for it to

0:53:26.160 --> 0:53:29.040
<v Speaker 1>do one thing, only to see it go off and

0:53:29.160 --> 0:53:32.160
<v Speaker 1>rampage through the village and you know, throw a little

0:53:32.160 --> 0:53:35.120
<v Speaker 1>girl in the river. That's a Frankenstein reference, although I

0:53:35.120 --> 0:53:36.560
<v Speaker 1>think it might have been a little boy in the book.

0:53:36.600 --> 0:53:38.880
<v Speaker 1>I don't remember. I haven't writen a long time. Anyway.

0:53:38.920 --> 0:53:42.600
<v Speaker 1>That wraps up this discussion of section to thirty on

0:53:42.680 --> 0:53:45.719
<v Speaker 1>tech stuff. Hope you guys learn something. I hope you

0:53:45.800 --> 0:53:48.040
<v Speaker 1>have heard my dog shaking his head in the background.

0:53:48.400 --> 0:53:51.560
<v Speaker 1>If you have any suggestions for future topics of tech stuff,

0:53:51.600 --> 0:53:54.160
<v Speaker 1>reach out to me. You can do so on Twitter,

0:53:54.560 --> 0:53:58.640
<v Speaker 1>where unless they start moderating your comments, I'll see it

0:53:59.120 --> 0:54:02.320
<v Speaker 1>and they handle for that is text stuff H s W.

0:54:02.920 --> 0:54:11.000
<v Speaker 1>I'll talk to you again really soon. Y. Text Stuff

0:54:11.080 --> 0:54:14.200
<v Speaker 1>is an I Heart Radio production. For more podcasts from

0:54:14.239 --> 0:54:18.040
<v Speaker 1>I Heart Radio, visit the I Heart Radio app, Apple Podcasts,

0:54:18.160 --> 0:54:20.160
<v Speaker 1>or wherever you listen to your favorite shows.