WEBVTT - A Look Back on 2021: Would Facebook Lie to You? (Probably)

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to Tech Stuff, a production from my Heart Radio.

0:00:12.000 --> 0:00:14.920
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host

0:00:15.080 --> 0:00:18.000
<v Speaker 1>job in Strickland. I'm an executive producer with I Heart Radio,

0:00:18.120 --> 0:00:21.479
<v Speaker 1>and I love all things tech. Though. I may just

0:00:21.600 --> 0:00:24.560
<v Speaker 1>need to come up with a new tagline, y'all, because

0:00:24.600 --> 0:00:26.799
<v Speaker 1>these episodes are really going to take it out of me,

0:00:26.880 --> 0:00:29.360
<v Speaker 1>because it's time to look back on some of the

0:00:29.360 --> 0:00:34.320
<v Speaker 1>biggest tech stories of the past year. Now, there is

0:00:34.320 --> 0:00:38.760
<v Speaker 1>no question that one was another rough one in a

0:00:38.880 --> 0:00:43.239
<v Speaker 1>series of rough years. The COVID nineteen pandemic and the

0:00:43.280 --> 0:00:47.000
<v Speaker 1>emergence of variants like Delta and Omicron have meant that

0:00:47.520 --> 0:00:52.360
<v Speaker 1>the tough conditions we found ourselves in during have continued.

0:00:52.880 --> 0:00:55.760
<v Speaker 1>And so that's going to weave in and out of

0:00:55.800 --> 0:00:58.080
<v Speaker 1>a lot of the stories we will be covering over

0:00:58.120 --> 0:01:01.840
<v Speaker 1>the next couple of episodes. And a lot happened, so

0:01:02.080 --> 0:01:04.080
<v Speaker 1>there will be several episodes. Also, a lot of this

0:01:04.240 --> 0:01:07.720
<v Speaker 1>is going to extend beyond tech in some ways, but

0:01:07.880 --> 0:01:13.160
<v Speaker 1>tech played a critical part in these stories. So one

0:01:13.200 --> 0:01:17.600
<v Speaker 1>really big story has been how tech companies like Apple, Google,

0:01:18.040 --> 0:01:24.000
<v Speaker 1>and Meta Slash, Facebook plus others have announced, postponed, and

0:01:24.040 --> 0:01:29.039
<v Speaker 1>in some cases indefinitely delayed a return to the office.

0:01:29.600 --> 0:01:34.320
<v Speaker 1>We've seen companies make these announcements several times throughout one

0:01:34.440 --> 0:01:38.000
<v Speaker 1>only to have to backtrack, like sometimes a few days

0:01:38.080 --> 0:01:39.839
<v Speaker 1>or a few weeks or a month or two later,

0:01:40.440 --> 0:01:45.400
<v Speaker 1>as things totally failed to get better. Maybe all the

0:01:45.480 --> 0:01:48.440
<v Speaker 1>optimism in the tech sector is a little bit on

0:01:48.480 --> 0:01:51.760
<v Speaker 1>the naive side. I think a lot of people start thinking, Hey,

0:01:51.800 --> 0:01:55.400
<v Speaker 1>just because we can seemingly do anything with tech means

0:01:55.440 --> 0:01:59.559
<v Speaker 1>that we can seemingly overcome any obstacle. Isn't necessarily true

0:01:59.720 --> 0:02:04.240
<v Speaker 1>see also paraos. But lots of companies originally planned a

0:02:04.360 --> 0:02:07.080
<v Speaker 1>return to the office, or at least a partial return

0:02:07.640 --> 0:02:10.280
<v Speaker 1>in which corporate employees were expected to come in at

0:02:10.360 --> 0:02:13.000
<v Speaker 1>least a few days out of each week. Uh And

0:02:13.160 --> 0:02:15.520
<v Speaker 1>a lot of that started in the late summer or

0:02:15.560 --> 0:02:19.840
<v Speaker 1>early fall of one. But then the Delta variant of

0:02:19.919 --> 0:02:23.280
<v Speaker 1>COVID nineteen changed things as Delta proved to be more

0:02:23.320 --> 0:02:27.560
<v Speaker 1>easily transmissible than other variants of COVID. And then you

0:02:27.600 --> 0:02:31.680
<v Speaker 1>started to hear plans of late fall or early winter

0:02:31.919 --> 0:02:34.959
<v Speaker 1>being the time to return, and a lot of those

0:02:35.000 --> 0:02:39.040
<v Speaker 1>have changed yet again. At the moment, plans generally look

0:02:39.160 --> 0:02:43.919
<v Speaker 1>at a January twenty twenty two return. Google had planned

0:02:44.120 --> 0:02:47.640
<v Speaker 1>to come back to the office for January ten, but

0:02:47.840 --> 0:02:51.600
<v Speaker 1>recently executives sent out an email indicating that employees would

0:02:51.600 --> 0:02:54.720
<v Speaker 1>not be required to comply and that the company will

0:02:54.800 --> 0:02:59.920
<v Speaker 1>reassess those plans early in the new year. Meta slash

0:03:00.120 --> 0:03:03.320
<v Speaker 1>Facebook is aiming for a return to office by January

0:03:03.400 --> 0:03:07.200
<v Speaker 1>thirty one, but has also offered a deferral program two

0:03:07.240 --> 0:03:10.000
<v Speaker 1>employees who can choose to push back their their return

0:03:10.120 --> 0:03:13.800
<v Speaker 1>date two between three and five months, So we might

0:03:13.840 --> 0:03:16.919
<v Speaker 1>be looking at the middle of twenty two, assuming things

0:03:17.639 --> 0:03:21.359
<v Speaker 1>are better by then, which based on the last year,

0:03:22.080 --> 0:03:25.520
<v Speaker 1>it's tough to make those kinds of assumptions. Apple, which

0:03:25.639 --> 0:03:28.919
<v Speaker 1>had aimed to get employees back in offices in early

0:03:29.000 --> 0:03:32.400
<v Speaker 1>February of next year, has now released a statement that

0:03:32.480 --> 0:03:35.280
<v Speaker 1>all return plans are currently on hold and that the

0:03:35.360 --> 0:03:38.920
<v Speaker 1>return date is yet to be determined. The pandemic has

0:03:38.920 --> 0:03:42.640
<v Speaker 1>really driven home the fact that making firm plans is

0:03:42.680 --> 0:03:45.680
<v Speaker 1>just really hard to do. The rise of new variants

0:03:45.680 --> 0:03:50.840
<v Speaker 1>requires changes in game plans. Meanwhile, employees are becoming accustomed

0:03:50.920 --> 0:03:54.200
<v Speaker 1>to being able to work from wherever they happen to be,

0:03:54.720 --> 0:03:57.560
<v Speaker 1>whether that's at home or on the road or whatever.

0:03:58.120 --> 0:04:01.280
<v Speaker 1>So we're seeing a trend of employees expressing reluctance to

0:04:01.320 --> 0:04:03.920
<v Speaker 1>go back to an office for lots of different reasons,

0:04:04.400 --> 0:04:08.840
<v Speaker 1>ranging from convenience to health and safety, to promoting a

0:04:08.840 --> 0:04:12.560
<v Speaker 1>different approach to you know, work life balance and uh.

0:04:12.680 --> 0:04:16.080
<v Speaker 1>One other big bonus to working remotely is that employees

0:04:16.120 --> 0:04:20.479
<v Speaker 1>don't necessarily have to live within commuting distance to their office.

0:04:20.960 --> 0:04:23.960
<v Speaker 1>So for employees who work at companies that are located

0:04:24.000 --> 0:04:28.560
<v Speaker 1>in really expensive markets like the San Francisco area, this

0:04:28.640 --> 0:04:32.240
<v Speaker 1>means they could potentially move away from San Francisco and

0:04:32.320 --> 0:04:35.320
<v Speaker 1>still work at that company. They're just doing so remotely,

0:04:35.640 --> 0:04:37.320
<v Speaker 1>and they can end up living in a place that

0:04:37.360 --> 0:04:40.680
<v Speaker 1>has a much lower cost of living, and that can

0:04:40.760 --> 0:04:44.760
<v Speaker 1>mean that they can afford a larger home or more

0:04:44.800 --> 0:04:49.280
<v Speaker 1>creature comforts, or put stuff towards savings. Plus they might

0:04:49.279 --> 0:04:52.520
<v Speaker 1>be dealing with a lot less hassle like city traffic.

0:04:53.200 --> 0:04:57.279
<v Speaker 1>Some employees have pushed back pretty hard against any move

0:04:57.360 --> 0:05:00.720
<v Speaker 1>to return to offices, at least pushing back against making

0:05:00.720 --> 0:05:05.839
<v Speaker 1>it mandatory. There have been numerous discussions about whether being

0:05:05.960 --> 0:05:10.920
<v Speaker 1>in an office is actually that important to you know,

0:05:11.000 --> 0:05:15.159
<v Speaker 1>getting work done. Um, there's some studies that seem to

0:05:15.160 --> 0:05:17.800
<v Speaker 1>suggest that we actually get more work done at home,

0:05:17.960 --> 0:05:24.039
<v Speaker 1>but things like innovation and forming bonds with coworkers really

0:05:24.080 --> 0:05:26.919
<v Speaker 1>suffers when we are not in the same place at

0:05:26.960 --> 0:05:32.359
<v Speaker 1>the same time. So there are these conflicting thoughts about

0:05:32.800 --> 0:05:36.640
<v Speaker 1>what it means to do work and productivity and the

0:05:36.720 --> 0:05:40.799
<v Speaker 1>benefit of doing work at home versus in the office.

0:05:40.880 --> 0:05:43.520
<v Speaker 1>These are big conversations that are continuing to move forward,

0:05:43.520 --> 0:05:46.360
<v Speaker 1>not just in tech, but we're seeing it play out

0:05:46.360 --> 0:05:49.600
<v Speaker 1>a lot in the text sphere in particular. Now. Whether

0:05:49.640 --> 0:05:52.920
<v Speaker 1>we're shifting toward a parliament approach to a hybrid work

0:05:53.040 --> 0:05:57.240
<v Speaker 1>strategy where people at least work partly from home or remotely,

0:05:57.839 --> 0:06:00.479
<v Speaker 1>that's hard to say right now, but it's certainly seems

0:06:00.560 --> 0:06:02.400
<v Speaker 1>as though a lot of companies are going to have

0:06:02.480 --> 0:06:05.040
<v Speaker 1>trouble convincing employees to come back to the office on

0:06:05.080 --> 0:06:08.760
<v Speaker 1>a regular basis. It may turn out the companies that

0:06:08.880 --> 0:06:13.120
<v Speaker 1>don't offer a hybrid or work from home approach, we'll

0:06:13.160 --> 0:06:17.640
<v Speaker 1>find it more difficult to attract and retain talent. And

0:06:18.360 --> 0:06:20.440
<v Speaker 1>that's a big deal in the tech sector, right Like

0:06:21.000 --> 0:06:24.680
<v Speaker 1>if it turns out that company A offers employees the

0:06:24.760 --> 0:06:28.559
<v Speaker 1>chance to work from wherever they happen to be and

0:06:28.839 --> 0:06:33.039
<v Speaker 1>still get all of their compensation and benefits and company

0:06:33.080 --> 0:06:36.560
<v Speaker 1>B doesn't. You're gonna see migrations from company B to

0:06:36.640 --> 0:06:39.280
<v Speaker 1>company A. I mean that just that's kind of how

0:06:39.320 --> 0:06:42.840
<v Speaker 1>it works in the tech sector in particular. And then

0:06:42.839 --> 0:06:44.680
<v Speaker 1>we also have to look at another side of this,

0:06:44.839 --> 0:06:49.599
<v Speaker 1>all that empty office space. Apple infamously spent around five

0:06:49.960 --> 0:06:54.880
<v Speaker 1>billion dollars that's billion with a B and eight years

0:06:54.920 --> 0:06:59.279
<v Speaker 1>of work to build their their quote unquote spaceship campus

0:07:00.240 --> 0:07:03.920
<v Speaker 1>that opened in seventeen and it's got like seven cafes

0:07:03.960 --> 0:07:07.880
<v Speaker 1>and a hundred thousand square foot fitness center, it's got

0:07:07.920 --> 0:07:12.840
<v Speaker 1>a thousand person theater, tons of office space, so understandably

0:07:13.440 --> 0:07:15.760
<v Speaker 1>having it mostly empty has got to be a source

0:07:15.760 --> 0:07:20.360
<v Speaker 1>of frustration and pain for Apple executives. Also, it's really

0:07:20.400 --> 0:07:22.960
<v Speaker 1>hard to keep an eye on what's going on when

0:07:23.000 --> 0:07:26.560
<v Speaker 1>your employees aren't like forced to be right there at

0:07:26.560 --> 0:07:30.200
<v Speaker 1>the office. It's also really hard to intimidate employees with

0:07:30.280 --> 0:07:34.200
<v Speaker 1>your presence if you can't be there. So I'm not

0:07:34.280 --> 0:07:40.160
<v Speaker 1>saying that that's necessarily Apple's modus operandi, but I'm not

0:07:40.160 --> 0:07:44.720
<v Speaker 1>not saying it either. So we've seen office occupancy dropped

0:07:44.800 --> 0:07:49.160
<v Speaker 1>below you know, between twenty five and across the United

0:07:49.200 --> 0:07:53.800
<v Speaker 1>States of what it was pre pandemic for most of

0:07:53.840 --> 0:07:56.800
<v Speaker 1>the last two years. Now in some cities like San Francisco,

0:07:56.960 --> 0:08:00.520
<v Speaker 1>that occupancy rate is actually lower, it's below fifteen percent.

0:08:01.320 --> 0:08:05.040
<v Speaker 1>There's still a trend in construction, so there's still like

0:08:05.640 --> 0:08:08.920
<v Speaker 1>a trend of building out new office space that's still happening.

0:08:09.560 --> 0:08:12.240
<v Speaker 1>So this raises the question who the heck is going

0:08:12.280 --> 0:08:16.040
<v Speaker 1>to be in all those office spaces moving forward. We

0:08:16.120 --> 0:08:21.400
<v Speaker 1>haven't seen companies abandoned their lease agreements on MOSS. It's

0:08:21.400 --> 0:08:23.840
<v Speaker 1>not like companies are saying, well, no need for us

0:08:23.840 --> 0:08:25.920
<v Speaker 1>to have offices anymore, We're all gonna work from home,

0:08:25.960 --> 0:08:28.920
<v Speaker 1>so let's get rid of those. That hasn't really happened,

0:08:28.920 --> 0:08:31.600
<v Speaker 1>at least not on a big scale. We have seen

0:08:31.680 --> 0:08:35.160
<v Speaker 1>some companies start to sublease some of their space, so

0:08:35.840 --> 0:08:39.160
<v Speaker 1>we might see some companies start to kind of slim

0:08:39.240 --> 0:08:42.040
<v Speaker 1>down as far as office space goes. They might reduce

0:08:42.080 --> 0:08:45.880
<v Speaker 1>the amount of office space that they maintain, especially if

0:08:45.920 --> 0:08:49.959
<v Speaker 1>they go to a hybrid approach where not all employees

0:08:50.000 --> 0:08:52.319
<v Speaker 1>will be in the office on every day, so people

0:08:52.400 --> 0:08:56.640
<v Speaker 1>might end up using shared employee spaces and thus you

0:08:56.679 --> 0:09:01.199
<v Speaker 1>don't need as many individual desk as you would if

0:09:01.240 --> 0:09:04.560
<v Speaker 1>everybody were there for every day. That's a possibility, but

0:09:05.040 --> 0:09:08.199
<v Speaker 1>it's still too early to really say that that's the

0:09:08.240 --> 0:09:11.120
<v Speaker 1>future of work. I expect we're going to see a

0:09:11.120 --> 0:09:14.160
<v Speaker 1>lot more innovation and products that target the hybrid or

0:09:14.320 --> 0:09:18.240
<v Speaker 1>work from home models in two We've already seen some

0:09:18.320 --> 0:09:21.520
<v Speaker 1>of those emerge. Uh, and we've also seen companies like

0:09:21.600 --> 0:09:25.199
<v Speaker 1>Slack and Zoom pivot a little bit to target that

0:09:25.440 --> 0:09:29.400
<v Speaker 1>use case more so not necessarily developing a lot of

0:09:29.720 --> 0:09:34.800
<v Speaker 1>products specifically geared towards that, but rather hey, this this

0:09:34.840 --> 0:09:37.640
<v Speaker 1>tool is also good if you aren't in the office,

0:09:37.720 --> 0:09:39.959
<v Speaker 1>that kind of thing. So I wouldn't be surprised to

0:09:40.000 --> 0:09:45.000
<v Speaker 1>see more of that introduced next year. Another pandemic issue

0:09:45.040 --> 0:09:48.960
<v Speaker 1>that started in and is going strong today is the

0:09:49.080 --> 0:09:53.240
<v Speaker 1>disruption of the supply chain. Now, this also goes well

0:09:53.280 --> 0:09:56.120
<v Speaker 1>beyond just tech. We're seeing it affect everything. Heck, I

0:09:56.160 --> 0:09:58.679
<v Speaker 1>see it at restaurants where they say, hey, we may

0:09:58.720 --> 0:10:01.520
<v Speaker 1>not have everything that's on the menu because of supply

0:10:01.640 --> 0:10:05.880
<v Speaker 1>chain issues. Um. So, supply chains are for pretty much

0:10:05.920 --> 0:10:08.720
<v Speaker 1>every sector are affected by this, but the tech space

0:10:08.760 --> 0:10:11.840
<v Speaker 1>has been hit really hard by it. Now we've all

0:10:11.920 --> 0:10:16.360
<v Speaker 1>heard about the semiconductor shortage, which has affected everything from

0:10:16.440 --> 0:10:20.800
<v Speaker 1>video game consoles to vehicles. And shortages mean that it's

0:10:20.840 --> 0:10:23.600
<v Speaker 1>really hard to find stuff like say a PS five

0:10:24.240 --> 0:10:27.440
<v Speaker 1>or It also means that car dealerships have less inventory

0:10:27.520 --> 0:10:30.320
<v Speaker 1>than what they typically have, and what they do have

0:10:30.760 --> 0:10:34.760
<v Speaker 1>ends up being way more expensive. Also means that some

0:10:34.840 --> 0:10:38.360
<v Speaker 1>car manufacturers are having to scale back on features and

0:10:38.440 --> 0:10:42.520
<v Speaker 1>options that they had introduced a few years ago because

0:10:42.520 --> 0:10:44.920
<v Speaker 1>now they just don't have the chips to continue offering

0:10:44.960 --> 0:10:48.760
<v Speaker 1>those features. You know that's BMW has done that with

0:10:48.840 --> 0:10:51.360
<v Speaker 1>a couple of its features, where things that you could

0:10:51.400 --> 0:10:53.840
<v Speaker 1>have purchased a couple of years ago now were no

0:10:53.880 --> 0:10:56.360
<v Speaker 1>longer available because they the company simply doesn't have the

0:10:56.480 --> 0:11:00.840
<v Speaker 1>chips to make those those components. So rather than go

0:11:00.960 --> 0:11:04.080
<v Speaker 1>without a car at all, the new ones just have

0:11:04.320 --> 0:11:08.040
<v Speaker 1>fewer features than older ones. That's a trend most companies

0:11:08.040 --> 0:11:12.360
<v Speaker 1>don't like to follow. Companies like Intel are working hard

0:11:12.600 --> 0:11:17.400
<v Speaker 1>to expand production for semiconductors and microchips. They're planning out

0:11:17.520 --> 0:11:20.920
<v Speaker 1>new manufacturing facilities all around the world, including within the

0:11:21.000 --> 0:11:23.800
<v Speaker 1>United States, but those plans are going to take a

0:11:23.800 --> 0:11:26.559
<v Speaker 1>few years to come to fruition, and in the meantime,

0:11:26.840 --> 0:11:30.520
<v Speaker 1>we've still got this shortage to deal with. Intel's CEO

0:11:30.720 --> 0:11:34.760
<v Speaker 1>has expressed doubt that the shortage will end before three

0:11:34.840 --> 0:11:38.080
<v Speaker 1>at the earliest, so we've got another year of this,

0:11:38.240 --> 0:11:42.360
<v Speaker 1>at least according to the CEO of Intel. There are

0:11:42.360 --> 0:11:47.120
<v Speaker 1>other leaders in tech who have slightly more optimistic prognoses,

0:11:47.679 --> 0:11:50.679
<v Speaker 1>but um, I'm not sure that those are realistic. I

0:11:50.720 --> 0:11:54.679
<v Speaker 1>hope they are. I'm just I'm not feeling it. Even

0:11:54.720 --> 0:11:57.560
<v Speaker 1>after building out new facilities, we still have issues with

0:11:57.640 --> 0:12:00.880
<v Speaker 1>the supply chain. So one of the really big problems

0:12:00.880 --> 0:12:05.160
<v Speaker 1>with the pandemic has been how port and shipping operations

0:12:05.160 --> 0:12:08.240
<v Speaker 1>have been affected. The pandemic has pulled back the curtain

0:12:08.280 --> 0:12:11.240
<v Speaker 1>on how much we depend upon a relatively small number

0:12:11.280 --> 0:12:15.840
<v Speaker 1>of professionals to keep the supply chain moving, and when

0:12:15.880 --> 0:12:20.240
<v Speaker 1>that gets disrupted, you have delays and bottlenecks and sort

0:12:20.240 --> 0:12:23.000
<v Speaker 1>of domino effects, and stuff starts to pile up at

0:12:23.040 --> 0:12:26.160
<v Speaker 1>one port while waiting to get loaded onto a ship,

0:12:26.679 --> 0:12:29.280
<v Speaker 1>and then the ship ends up getting in a bottleneck

0:12:29.320 --> 0:12:32.360
<v Speaker 1>waiting to dock at another port that's already backed up.

0:12:32.840 --> 0:12:36.439
<v Speaker 1>It becomes this sort of cascading effect across the entire industry,

0:12:36.720 --> 0:12:40.520
<v Speaker 1>and of course, the supply chain issue wasn't helped when

0:12:40.640 --> 0:12:44.800
<v Speaker 1>in March of this year, the cargo vessel named ever

0:12:45.000 --> 0:12:48.920
<v Speaker 1>Given got stuck in the Suez Canal. So for about

0:12:48.960 --> 0:12:53.320
<v Speaker 1>a week six days actually, the vessel was blocking a

0:12:53.440 --> 0:12:56.560
<v Speaker 1>key passage for cargo ships, and by a key passage,

0:12:56.600 --> 0:12:59.920
<v Speaker 1>I mean nearly a third of all container ship track

0:13:00.080 --> 0:13:04.080
<v Speaker 1>thick passes through the Suez Canal. Now, the Suez Canal

0:13:04.160 --> 0:13:08.800
<v Speaker 1>Authority took possession of the ship once it was finally dislodged,

0:13:09.440 --> 0:13:12.080
<v Speaker 1>and they held it for several months, finally releasing it

0:13:12.120 --> 0:13:16.199
<v Speaker 1>in July after demanding nearly one billion dollars in fines.

0:13:16.880 --> 0:13:20.720
<v Speaker 1>That amount was later reduced to around fifty million dollars.

0:13:21.440 --> 0:13:23.440
<v Speaker 1>And um, you know, if you've ever been stuck in

0:13:23.480 --> 0:13:26.120
<v Speaker 1>bumper to bumper traffic on a highway and you finally

0:13:26.160 --> 0:13:29.680
<v Speaker 1>get to a section that mysteriously clears up and there's

0:13:29.720 --> 0:13:32.720
<v Speaker 1>no obvious cause for what made the traffic jam happen

0:13:32.760 --> 0:13:35.520
<v Speaker 1>in the first place, then you've had some experience with

0:13:35.520 --> 0:13:40.200
<v Speaker 1>bottleneck issues. They can and do clear up, but it's

0:13:40.240 --> 0:13:44.560
<v Speaker 1>not instantaneous, and even as one element gets some breathing room,

0:13:44.679 --> 0:13:49.400
<v Speaker 1>others are lagging behind, so we're likely to continue feeling

0:13:49.440 --> 0:13:52.640
<v Speaker 1>the effects of the supply chain disruption for some time,

0:13:52.800 --> 0:13:55.800
<v Speaker 1>and not just in semiconductors. This also, by the way,

0:13:55.800 --> 0:14:00.280
<v Speaker 1>effects pricing, which means we consumers start to really feel

0:14:00.320 --> 0:14:02.360
<v Speaker 1>the pinch, as I'm sure all of you out there

0:14:02.400 --> 0:14:05.079
<v Speaker 1>listening have seen in some way or another, whether it's

0:14:05.080 --> 0:14:10.640
<v Speaker 1>in food prices, coffee prices, fuel prices, electronics, all of

0:14:10.640 --> 0:14:13.480
<v Speaker 1>these things, we're all kind of feeling it in different ways.

0:14:13.960 --> 0:14:16.840
<v Speaker 1>On a related note, one trend we saw increase in

0:14:17.679 --> 0:14:22.720
<v Speaker 1>one was in bought activity, specifically bots. That is, these

0:14:22.760 --> 0:14:28.160
<v Speaker 1>automated scripts that are designed to purchase certain goods um

0:14:28.320 --> 0:14:32.040
<v Speaker 1>like like video game consoles, you know, high value goods

0:14:32.120 --> 0:14:35.120
<v Speaker 1>that are in high demand. Now, the whole purpose of

0:14:35.160 --> 0:14:38.920
<v Speaker 1>these bots is just to corner a market on whatever

0:14:39.000 --> 0:14:43.480
<v Speaker 1>high end good they're focusing on, and then resell those

0:14:43.480 --> 0:14:48.880
<v Speaker 1>goods at crazy markups on sites like eBay. So gamers

0:14:48.920 --> 0:14:51.760
<v Speaker 1>out there who are desperate for a new console might

0:14:51.760 --> 0:14:54.080
<v Speaker 1>find that the only option available to them is to

0:14:54.200 --> 0:14:57.600
<v Speaker 1>go and pay through the nose at you know, eBay

0:14:57.720 --> 0:15:02.120
<v Speaker 1>or some other resales site. Essentially, it's scalping. It's the

0:15:02.160 --> 0:15:05.760
<v Speaker 1>same approach that you see with people who scalp tickets.

0:15:05.800 --> 0:15:09.160
<v Speaker 1>So the practice inspired several US politicians, all of whom

0:15:09.160 --> 0:15:12.840
<v Speaker 1>are Democrats, to reintroduce a piece of legislation called the

0:15:12.960 --> 0:15:17.120
<v Speaker 1>Stopping the grinch Bots Act. This would make the use

0:15:17.160 --> 0:15:21.640
<v Speaker 1>of automated tools to bypass online retail security measures uh

0:15:21.920 --> 0:15:25.840
<v Speaker 1>in the effort to purchase and resell products and services illegal.

0:15:25.920 --> 0:15:28.640
<v Speaker 1>It was just it would become against the law, and

0:15:28.760 --> 0:15:31.560
<v Speaker 1>it would give authority to the Federal Trade Commission or

0:15:31.680 --> 0:15:36.080
<v Speaker 1>f TC to enforce this law. Lawmakers introduced a similar

0:15:36.120 --> 0:15:38.680
<v Speaker 1>measure in two thousand eighteen, but it's stalled out in

0:15:38.840 --> 0:15:42.080
<v Speaker 1>committees and never really went to vote. And there's also

0:15:42.200 --> 0:15:47.520
<v Speaker 1>a Stop the Grinch Act proposed by the Senator from Utah.

0:15:47.680 --> 0:15:50.160
<v Speaker 1>That one actually is looking to alleviate some of the

0:15:50.200 --> 0:15:53.840
<v Speaker 1>congestion within the supply chain, you know, the stuff that

0:15:53.880 --> 0:15:56.000
<v Speaker 1>we were talking about a moment ago, at least within

0:15:56.040 --> 0:15:59.560
<v Speaker 1>the United States, to help alleviate some of those issues.

0:15:59.800 --> 0:16:03.840
<v Speaker 1>Of course, you know, it wouldn't necessarily fixed stuff overseas,

0:16:03.920 --> 0:16:06.680
<v Speaker 1>which is part of the problem. We're talking about global problems,

0:16:06.680 --> 0:16:10.040
<v Speaker 1>so local solutions are kind of only a band aid,

0:16:10.320 --> 0:16:13.480
<v Speaker 1>but it would still be you know, a step toward that. However,

0:16:13.800 --> 0:16:16.320
<v Speaker 1>that's a different act, so it gets a bit confusing

0:16:16.320 --> 0:16:18.640
<v Speaker 1>because there's a Stop the grinch Bots Act and a

0:16:18.840 --> 0:16:22.680
<v Speaker 1>Stopping the Grinch Act, so they have similar names. Um,

0:16:22.680 --> 0:16:25.680
<v Speaker 1>but there are two different things. Something else that didn't

0:16:25.760 --> 0:16:29.080
<v Speaker 1>originate in one but it cranked into a higher gear

0:16:30.080 --> 0:16:33.440
<v Speaker 1>was the spread of misinformation. Now that's going to be

0:16:33.480 --> 0:16:36.240
<v Speaker 1>a running theme in a lot of this episode. But

0:16:36.320 --> 0:16:39.520
<v Speaker 1>before I get into all of that, let's take a

0:16:39.640 --> 0:16:51.040
<v Speaker 1>quick break. All right, misinformation. Um, there's a lot to

0:16:51.120 --> 0:16:56.800
<v Speaker 1>cover here, but when it comes to misinformation one, I mean,

0:16:56.920 --> 0:16:59.320
<v Speaker 1>I've kind of feel like Marlon Brando and The Wild

0:16:59.360 --> 0:17:01.800
<v Speaker 1>One when he's asked like what are you rebelling against?

0:17:01.800 --> 0:17:04.399
<v Speaker 1>He's like, what have you got? Well, in this case,

0:17:04.680 --> 0:17:06.480
<v Speaker 1>it would be you know, what do you have to

0:17:06.480 --> 0:17:09.119
<v Speaker 1>say about misinformation? And a well, how much time do

0:17:09.160 --> 0:17:13.000
<v Speaker 1>you have? Because uh, we could literally do a week's

0:17:13.000 --> 0:17:17.920
<v Speaker 1>worth of episodes about misinformation just in one. But I'll

0:17:17.960 --> 0:17:22.800
<v Speaker 1>try and keep it somewhat succinct, you know, I'll try

0:17:22.840 --> 0:17:25.320
<v Speaker 1>to to keep all of that in this episode. I'm

0:17:25.359 --> 0:17:26.960
<v Speaker 1>sure some of it will spill out as I talk

0:17:27.040 --> 0:17:31.760
<v Speaker 1>about other other stories later this week. Um, Okay, A

0:17:31.760 --> 0:17:35.960
<v Speaker 1>lot of the misinformation is focused on the pandemic from

0:17:36.000 --> 0:17:40.040
<v Speaker 1>folks proclaiming that they knew with absolute certainty that the

0:17:40.080 --> 0:17:44.439
<v Speaker 1>origins of the virus were from this one place or

0:17:44.480 --> 0:17:48.440
<v Speaker 1>this other place, without actually providing any evidence to that.

0:17:48.760 --> 0:17:51.360
<v Speaker 1>You know, they're just claiming it. Or there were those

0:17:51.400 --> 0:17:54.439
<v Speaker 1>who were proclaiming vaccines to be harmful or even a

0:17:54.440 --> 0:17:57.040
<v Speaker 1>tool that governments were using to try and control or

0:17:57.119 --> 0:18:00.800
<v Speaker 1>track populations. And then there were just the right denials

0:18:00.800 --> 0:18:03.520
<v Speaker 1>that there's even a pandemic going on in the first place,

0:18:03.560 --> 0:18:06.520
<v Speaker 1>that that COVID itself is a hoax. The fact that

0:18:06.640 --> 0:18:12.280
<v Speaker 1>several high profile deniers have subsequently died after contracting COVID

0:18:12.880 --> 0:18:17.840
<v Speaker 1>doesn't seem to squash the spread of that dangerous misinformation,

0:18:17.880 --> 0:18:22.600
<v Speaker 1>those lies, which again crazy, right, you have people who

0:18:22.640 --> 0:18:26.520
<v Speaker 1>are saying COVID's not real, then they die of COVID,

0:18:26.960 --> 0:18:30.120
<v Speaker 1>but the people that they've told COVID's not real are

0:18:30.119 --> 0:18:34.359
<v Speaker 1>still saying COVID's not real. Listen, I also wish COVID

0:18:34.400 --> 0:18:39.080
<v Speaker 1>weren't real. But you know, if if if wishes were horses,

0:18:39.119 --> 0:18:43.560
<v Speaker 1>beggars would ride. And that's just not the case. As

0:18:43.560 --> 0:18:45.480
<v Speaker 1>for the tech angle, well, as we all know, a

0:18:45.560 --> 0:18:50.040
<v Speaker 1>lot of these messages spread via social networking platforms like Facebook,

0:18:50.240 --> 0:18:54.440
<v Speaker 1>and we're going to talk so much about Facebook within

0:18:54.520 --> 0:19:00.240
<v Speaker 1>the context of one. Volumes have been written recently about

0:19:00.280 --> 0:19:03.800
<v Speaker 1>how Facebook's algorithm has played a part in elevating messages

0:19:03.840 --> 0:19:09.200
<v Speaker 1>that spread harmful misinformation and how that ends up reinforcing falsehoods.

0:19:09.240 --> 0:19:12.240
<v Speaker 1>It amplifies the message, and it convinces people to do

0:19:12.400 --> 0:19:18.480
<v Speaker 1>stupid stuff like denounced vaccines or defy mask orders and more.

0:19:19.000 --> 0:19:21.960
<v Speaker 1>And I figure any reasonable person has to be left

0:19:21.960 --> 0:19:26.560
<v Speaker 1>wondering how many people have died because of those kinds

0:19:26.560 --> 0:19:30.240
<v Speaker 1>of messages. And keep in mind, the folks who die

0:19:30.760 --> 0:19:33.399
<v Speaker 1>are not necessarily the same ones who have bought into

0:19:33.400 --> 0:19:36.480
<v Speaker 1>the lie. Right. The folks who die might be friends

0:19:36.560 --> 0:19:39.120
<v Speaker 1>or family, or loved ones or co workers, or even

0:19:39.160 --> 0:19:42.000
<v Speaker 1>just strangers who just happened to be in the wrong

0:19:42.040 --> 0:19:46.040
<v Speaker 1>place at the wrong time, under the wrong circumstances and

0:19:46.080 --> 0:19:49.800
<v Speaker 1>they caught COVID as a result. This is why I

0:19:49.880 --> 0:19:52.320
<v Speaker 1>keep harping on this. I know I sound like a

0:19:52.359 --> 0:19:55.560
<v Speaker 1>broken record, but I'm not going to stop. I don't

0:19:55.640 --> 0:19:59.600
<v Speaker 1>want anyone to die. But even if I were super cynical,

0:20:00.040 --> 0:20:01.960
<v Speaker 1>that if I were one of those people who saying

0:20:02.320 --> 0:20:05.320
<v Speaker 1>this is Darwinian right, the idea that the people who

0:20:05.359 --> 0:20:07.480
<v Speaker 1>deny it are the ones who are dying off it

0:20:07.520 --> 0:20:09.840
<v Speaker 1>will it's a problem that takes care of itself. I

0:20:09.880 --> 0:20:13.280
<v Speaker 1>can't think that way because that's just writing people's lives off,

0:20:13.560 --> 0:20:18.159
<v Speaker 1>and that's fundamentally wrong to me. I cannot be that person.

0:20:19.000 --> 0:20:21.199
<v Speaker 1>But even if I were, I would still have to

0:20:21.240 --> 0:20:24.920
<v Speaker 1>acknowledge that it's not just the ignorant and the misled

0:20:25.000 --> 0:20:30.000
<v Speaker 1>who are suffering here due to misinformation campaigns. It's everyone. Now.

0:20:30.040 --> 0:20:34.160
<v Speaker 1>Some of the messaging spread in claim that vaccines could

0:20:34.200 --> 0:20:38.000
<v Speaker 1>do anything from magnetize you to introduce some sort of

0:20:38.040 --> 0:20:41.840
<v Speaker 1>tracking device into your body. It didn't matter that folks

0:20:41.840 --> 0:20:45.439
<v Speaker 1>pointed out that those relies like they would show that no,

0:20:45.760 --> 0:20:48.880
<v Speaker 1>there's no such thing that magnets, No, that's not happening,

0:20:48.960 --> 0:20:51.399
<v Speaker 1>or that all you have to do is own a

0:20:51.480 --> 0:20:55.320
<v Speaker 1>smartphone and that device alone is tracking everywhere you go

0:20:55.400 --> 0:20:59.080
<v Speaker 1>and everything you do. There's no need to inject a tracker,

0:20:59.160 --> 0:21:03.160
<v Speaker 1>and you you're already a willing participant in an ecosystem

0:21:03.320 --> 0:21:06.560
<v Speaker 1>that's tracking you all the time. None of that matters

0:21:06.800 --> 0:21:10.520
<v Speaker 1>when it comes to stopping misinformation. The best way to

0:21:10.520 --> 0:21:14.159
<v Speaker 1>stop misinformation really besides you know, sitting people down and

0:21:14.200 --> 0:21:17.199
<v Speaker 1>having one on ones and really getting to it is

0:21:17.280 --> 0:21:21.919
<v Speaker 1>not allowing for that amplification and that rapid spread in

0:21:21.960 --> 0:21:27.320
<v Speaker 1>the first place. All right, Uh, but not all the

0:21:27.359 --> 0:21:30.960
<v Speaker 1>misinformation had to do just with COVID. We will touch

0:21:31.000 --> 0:21:34.119
<v Speaker 1>back on that. There was something else that happened in

0:21:34.880 --> 0:21:38.720
<v Speaker 1>one where misinformation played a pivotal role, and let's get

0:21:38.760 --> 0:21:41.040
<v Speaker 1>to it. I mean, it feels like it happened a

0:21:41.080 --> 0:21:45.040
<v Speaker 1>billion years ago to me, But it was on January six,

0:21:45.359 --> 0:21:51.840
<v Speaker 1>twenty one, when there was a nearly successful insurrection in

0:21:51.920 --> 0:21:54.920
<v Speaker 1>the United States. That is the date when a group

0:21:55.000 --> 0:21:58.920
<v Speaker 1>of violent individuals stormed the US capital with the goal

0:21:59.040 --> 0:22:03.919
<v Speaker 1>of interfering with the ratification of the twenty twenty election. Now,

0:22:04.880 --> 0:22:07.360
<v Speaker 1>Congress was in the process of what is usually a

0:22:07.400 --> 0:22:12.359
<v Speaker 1>pretty ceremonial event where the states present and ratify their

0:22:12.400 --> 0:22:16.480
<v Speaker 1>elector results and the winner of the most recent election

0:22:16.840 --> 0:22:19.760
<v Speaker 1>is made official. Everyone knows who the winner is already,

0:22:19.800 --> 0:22:22.760
<v Speaker 1>by the way, because everyone already knows the outcome of

0:22:22.800 --> 0:22:27.320
<v Speaker 1>the election, but this is the process that officially recognizes

0:22:27.720 --> 0:22:33.480
<v Speaker 1>the winner. The rioters on January six, encouraged by then

0:22:33.680 --> 0:22:37.320
<v Speaker 1>President Donald Trump, were on a mission to disrupt this

0:22:37.760 --> 0:22:41.040
<v Speaker 1>process at any cost, with some going so far as

0:22:41.119 --> 0:22:44.240
<v Speaker 1>to advocate for the capture and execution of the then

0:22:44.359 --> 0:22:49.040
<v Speaker 1>Vice President Mike Pence, because it was Pence's ceremonial duty

0:22:49.119 --> 0:22:52.879
<v Speaker 1>to recognize the results, and he was not going to

0:22:53.040 --> 0:22:58.160
<v Speaker 1>overturn the recognized results despite what Trump wanted him to do.

0:22:58.560 --> 0:23:03.640
<v Speaker 1>So his followers, Trump followers, we're saying, Okay, let's kill

0:23:03.720 --> 0:23:10.840
<v Speaker 1>the vice president. A truly horridonous series of crazy, irrational

0:23:10.960 --> 0:23:15.480
<v Speaker 1>thoughts right now, y'all. This story is so outrageous that

0:23:15.600 --> 0:23:18.280
<v Speaker 1>it is hard to get my mind wrapped around it.

0:23:18.359 --> 0:23:21.840
<v Speaker 1>And perhaps even more outrageous is how so much of

0:23:21.880 --> 0:23:24.920
<v Speaker 1>the United States has just kind of accepted this as it's,

0:23:25.040 --> 0:23:28.439
<v Speaker 1>you know, just a thing that happened. It's bonkers to me.

0:23:28.720 --> 0:23:31.800
<v Speaker 1>But let's get back to the tech. Investigators looking into

0:23:31.800 --> 0:23:35.439
<v Speaker 1>the January six riots suspected that a lot of planning

0:23:35.520 --> 0:23:38.679
<v Speaker 1>for the event was carried out on various social network

0:23:38.760 --> 0:23:44.600
<v Speaker 1>platforms like Facebook, Twitter, and at the time, parlor or parlay.

0:23:44.640 --> 0:23:48.200
<v Speaker 1>I'm gonna call it parlor. This story continues to play

0:23:48.200 --> 0:23:51.240
<v Speaker 1>out today. By the way, there was a finding in

0:23:51.720 --> 0:23:55.320
<v Speaker 1>the FBI released in August of this year that said

0:23:55.600 --> 0:23:57.919
<v Speaker 1>that they found very little evidence that there was a

0:23:57.920 --> 0:24:01.480
<v Speaker 1>lot of planning going on on social networks at the

0:24:01.560 --> 0:24:04.720
<v Speaker 1>time leading up to the January six riots, But then

0:24:04.760 --> 0:24:07.159
<v Speaker 1>subsequently there have been others who have come for and

0:24:07.160 --> 0:24:10.560
<v Speaker 1>said no, we totally use social networks to help plan

0:24:10.720 --> 0:24:13.920
<v Speaker 1>this stuff out. So it's the story that has gone

0:24:13.960 --> 0:24:18.960
<v Speaker 1>back and forth many times throughout um. But there are

0:24:18.960 --> 0:24:21.040
<v Speaker 1>still people who are calling out for platforms to be

0:24:21.080 --> 0:24:25.919
<v Speaker 1>held accountable for amplifying misinformation campaigns that led to civil

0:24:26.040 --> 0:24:30.480
<v Speaker 1>unrest and violence, including the deaths of five people. Some

0:24:30.680 --> 0:24:34.280
<v Speaker 1>have been held more to account than others, so Parlor,

0:24:34.359 --> 0:24:36.760
<v Speaker 1>for instance, had a pretty rough go of it. Early

0:24:36.840 --> 0:24:39.639
<v Speaker 1>in the year. The site, which promoted itself as a

0:24:39.680 --> 0:24:42.680
<v Speaker 1>place where freedom of speech is valued above everything else,

0:24:43.240 --> 0:24:45.600
<v Speaker 1>was mostly known as being the home for far right

0:24:45.720 --> 0:24:51.880
<v Speaker 1>conservatives and conspiracy theorists. Parlor's site depended upon Amazon Web

0:24:52.000 --> 0:24:56.399
<v Speaker 1>Services for for hosting, and in the wake of the

0:24:56.480 --> 0:25:00.399
<v Speaker 1>January six insurrection, Google and Apple both were moved the

0:25:00.440 --> 0:25:03.640
<v Speaker 1>Parlor app from their respective stores, and a short time

0:25:03.760 --> 0:25:08.040
<v Speaker 1>later Amazon removed Parlor from a WS and the site

0:25:08.080 --> 0:25:13.680
<v Speaker 1>went dark. Parlor subsequently saw its CEO, John Matt's, fired

0:25:13.760 --> 0:25:17.800
<v Speaker 1>and replaced first by Mark Meckler and then by George Farmer.

0:25:18.240 --> 0:25:21.280
<v Speaker 1>The site returned to service in mid February, having moved

0:25:21.280 --> 0:25:24.560
<v Speaker 1>from AWS to a company called Epic, although it had

0:25:24.600 --> 0:25:30.320
<v Speaker 1>lost all posts that had been sent before the takedown,

0:25:30.800 --> 0:25:35.280
<v Speaker 1>so nothing from the earlier era of Parlor still existed.

0:25:36.400 --> 0:25:38.920
<v Speaker 1>So the site is still around today, though reportedly not

0:25:39.000 --> 0:25:41.119
<v Speaker 1>nearly as popular as it was leading up to the

0:25:41.119 --> 0:25:44.359
<v Speaker 1>twenty twenty election, A lot of people just migrated to

0:25:44.400 --> 0:25:48.520
<v Speaker 1>other platforms instead. As for other sites such as you know,

0:25:49.040 --> 0:25:53.280
<v Speaker 1>Facebook and Twitter, much of one and YouTube too, I

0:25:53.280 --> 0:25:57.600
<v Speaker 1>should say, but Much of One has featured investigations into

0:25:57.680 --> 0:26:01.440
<v Speaker 1>and statements from those various site and services regarding to

0:26:01.520 --> 0:26:05.120
<v Speaker 1>what extent they might or might not have played as

0:26:05.240 --> 0:26:08.679
<v Speaker 1>part of the January six attack on the Capitol. And

0:26:08.720 --> 0:26:11.280
<v Speaker 1>I guess that's as good a place for us to

0:26:11.359 --> 0:26:16.680
<v Speaker 1>start talking about Facebook in is any Because good Gully

0:26:16.720 --> 0:26:18.880
<v Speaker 1>is there a lot to talk about. In fact, there's

0:26:18.920 --> 0:26:21.320
<v Speaker 1>so much to talk about that I suspect it's going

0:26:21.359 --> 0:26:24.920
<v Speaker 1>to take up probably the rest of this episode. So

0:26:25.840 --> 0:26:28.720
<v Speaker 1>this is also going to involve some jumping around because

0:26:29.440 --> 0:26:31.840
<v Speaker 1>I tried originally to kind of sketch this out in

0:26:31.880 --> 0:26:36.439
<v Speaker 1>a strictly chronological retelling of Facebook's year, but that was

0:26:36.480 --> 0:26:40.240
<v Speaker 1>too messy, it was too tangled up. And that's largely

0:26:40.359 --> 0:26:44.840
<v Speaker 1>because a ton of stuff really that really applies to

0:26:44.960 --> 0:26:48.960
<v Speaker 1>the year that Facebook has had actually goes back several years,

0:26:49.000 --> 0:26:52.840
<v Speaker 1>but it only became public knowledge late this year when

0:26:52.960 --> 0:26:56.119
<v Speaker 1>Francis Hogan, who was a former product manager at Facebook,

0:26:56.600 --> 0:27:01.000
<v Speaker 1>came forward with thousands of internal Facebook document and shared

0:27:01.080 --> 0:27:05.560
<v Speaker 1>them with authorities and with journalists. And those documents prompted

0:27:05.680 --> 0:27:09.120
<v Speaker 1>hundreds of questions that lots of different people want answered,

0:27:09.640 --> 0:27:13.240
<v Speaker 1>and Facebook, or as the company is now known, Meta,

0:27:13.400 --> 0:27:17.960
<v Speaker 1>has slowly kind of been answering them, to varying degrees

0:27:18.000 --> 0:27:22.720
<v Speaker 1>of satisfaction. Some of the revelations that tied directly into

0:27:22.760 --> 0:27:26.520
<v Speaker 1>that January sixth event. For example, leading up to the

0:27:26.640 --> 0:27:31.479
<v Speaker 1>twenty election, Facebook had an internal group within the company

0:27:31.520 --> 0:27:34.919
<v Speaker 1>called the Civic Integrity Group, and the purpose of this

0:27:35.000 --> 0:27:40.240
<v Speaker 1>group was to monitor issues like misinformation relating to elections

0:27:40.240 --> 0:27:43.879
<v Speaker 1>and politics. Now, you could probably make a pretty decent

0:27:43.960 --> 0:27:48.200
<v Speaker 1>argument that this group was not capable of handling that task. Now,

0:27:48.840 --> 0:27:52.320
<v Speaker 1>I don't mean that the people who worked within the

0:27:52.359 --> 0:27:57.160
<v Speaker 1>Civic Integrity Group were inept or anything like that. Rather,

0:27:57.240 --> 0:28:00.639
<v Speaker 1>what I mean is that the scope of the problem

0:28:00.680 --> 0:28:03.520
<v Speaker 1>I think was well beyond their capabilities. It's just such

0:28:03.560 --> 0:28:07.520
<v Speaker 1>a huge issue. Also, you had problems with Facebook executives

0:28:07.800 --> 0:28:10.919
<v Speaker 1>who were kind of counteracting some of the suggestions that

0:28:10.960 --> 0:28:16.920
<v Speaker 1>people had to make changes that could potentially reduce Facebook's

0:28:17.560 --> 0:28:22.520
<v Speaker 1>uh role in amplifying this information. But setting all that aside,

0:28:22.600 --> 0:28:26.040
<v Speaker 1>Hogan told a U. S. Senate subcommittee that Facebook dissolved

0:28:26.160 --> 0:28:31.320
<v Speaker 1>the Civic Integrity Team shortly after the election. Now, Facebook

0:28:31.320 --> 0:28:34.800
<v Speaker 1>reps have since said that they didn't dissolve the Civic

0:28:34.840 --> 0:28:38.840
<v Speaker 1>Integrity team. Instead, they merged it with a larger Central

0:28:39.080 --> 0:28:43.959
<v Speaker 1>Integrity team, So they say Cecivic Integrity didn't really go away,

0:28:44.400 --> 0:28:47.120
<v Speaker 1>it just became part of something bigger than itself, and

0:28:47.160 --> 0:28:50.000
<v Speaker 1>the idea was to use the experience that the Civic

0:28:50.040 --> 0:28:55.200
<v Speaker 1>Integrity Team had to a larger scope. However, the concern

0:28:55.320 --> 0:28:59.320
<v Speaker 1>that US lawmakers have is that this movement Facebook was

0:28:59.720 --> 0:29:03.200
<v Speaker 1>even less prepared to deal with the surge in rhetoric

0:29:03.600 --> 0:29:07.520
<v Speaker 1>that preceded the January six riots earlier this year. So,

0:29:07.560 --> 0:29:11.080
<v Speaker 1>in other words, the timing of the decision to dissolve

0:29:11.200 --> 0:29:15.640
<v Speaker 1>or rather merge Civic Integrity with another group may have

0:29:15.720 --> 0:29:19.040
<v Speaker 1>been a contributing factor that there weren't as many eyeballs

0:29:19.080 --> 0:29:22.280
<v Speaker 1>on the issue out of critical time as there should

0:29:22.320 --> 0:29:27.400
<v Speaker 1>have been. Perhaps the spread of election misinformation, you know,

0:29:27.480 --> 0:29:32.120
<v Speaker 1>the whole stop the steel nonsense, drove more people towards extremism,

0:29:32.160 --> 0:29:34.840
<v Speaker 1>which in turn added fuel to the folks who ultimately

0:29:34.920 --> 0:29:40.000
<v Speaker 1>stormed the capital on January six. Now I'm writing this

0:29:40.120 --> 0:29:43.720
<v Speaker 1>and recording this on December twenty, two, thousand twenty one,

0:29:43.880 --> 0:29:48.200
<v Speaker 1>and it was just today that Engadget published a piece

0:29:48.280 --> 0:29:52.560
<v Speaker 1>about this very thing. So nearly a full year has

0:29:52.600 --> 0:29:57.040
<v Speaker 1>passed since that riot, and we're still, you know, writing

0:29:57.040 --> 0:30:02.240
<v Speaker 1>about discoveries made, uh leading up to the riot, igor

0:30:02.480 --> 0:30:06.320
<v Speaker 1>Bonifaceic and I apologize for butchering your name, Igore. He

0:30:06.360 --> 0:30:08.560
<v Speaker 1>wrote the piece, and he rightly points out that while

0:30:08.640 --> 0:30:13.040
<v Speaker 1>there's a lot of outrage being expressed about this, there's

0:30:13.080 --> 0:30:17.240
<v Speaker 1>not a lot of actual, you know, action being done

0:30:17.320 --> 0:30:20.000
<v Speaker 1>about it. And and part of that is because while

0:30:20.080 --> 0:30:24.720
<v Speaker 1>both Democrats and Republicans have an act to grind with Facebook,

0:30:25.200 --> 0:30:29.040
<v Speaker 1>the two parties fundamentally disagree on the nature of that

0:30:29.160 --> 0:30:33.440
<v Speaker 1>acts and how to grind it. I'll explain more after

0:30:33.520 --> 0:30:44.480
<v Speaker 1>we take this quick break. All right, I've left off

0:30:44.520 --> 0:30:48.480
<v Speaker 1>talking about how there's a general feeling that Facebook needs

0:30:48.480 --> 0:30:52.040
<v Speaker 1>to be called to task, but there's a fundamental difference

0:30:52.080 --> 0:30:56.640
<v Speaker 1>in ideology over why and how. So there's another ongoing

0:30:56.720 --> 0:31:01.320
<v Speaker 1>story that really was playing out in UH and it's

0:31:01.360 --> 0:31:04.040
<v Speaker 1>one that's not really supported by facts, but it's still

0:31:04.440 --> 0:31:07.720
<v Speaker 1>important because there were consequences. And it's that there's the

0:31:07.880 --> 0:31:11.680
<v Speaker 1>this narrative that Facebook and some other social networks have

0:31:11.840 --> 0:31:18.480
<v Speaker 1>a bias against conservative voices and therefore have a tendency

0:31:18.600 --> 0:31:22.920
<v Speaker 1>to suppress those voices, that these entities are working to

0:31:23.080 --> 0:31:27.680
<v Speaker 1>silence the conservative perspective. Those who argue this like to

0:31:27.720 --> 0:31:30.640
<v Speaker 1>point out stuff that you know, like Facebook, Twitter, and

0:31:30.720 --> 0:31:35.760
<v Speaker 1>YouTube eventually banned Donald Trump's accounts with those services, mostly

0:31:35.800 --> 0:31:38.360
<v Speaker 1>in the wake of the January six riots and the

0:31:38.400 --> 0:31:43.800
<v Speaker 1>perpetuation of election fraud claims, claims that are wholly unsupported

0:31:44.120 --> 0:31:49.760
<v Speaker 1>by actual evidence. See The platforms under intense pressure began

0:31:49.880 --> 0:31:55.280
<v Speaker 1>flagging posts that contained unsupported allegations and they tagged them

0:31:55.320 --> 0:32:00.400
<v Speaker 1>as misinformation, so alerting people, hey, the claim was being

0:32:00.440 --> 0:32:03.280
<v Speaker 1>made in this post are not supported by facts. That's

0:32:03.360 --> 0:32:06.760
<v Speaker 1>essentially what they were doing, saying, you know, essentially, don't

0:32:06.880 --> 0:32:10.320
<v Speaker 1>don't necessarily believe what you're reading here. Now that had

0:32:10.320 --> 0:32:14.320
<v Speaker 1>prompted some conservatives to argue that the platforms have a bias.

0:32:15.040 --> 0:32:17.240
<v Speaker 1>But you know, just a word on this. See, if

0:32:17.280 --> 0:32:21.040
<v Speaker 1>your claim is not supported by actual evidence, it doesn't

0:32:21.080 --> 0:32:26.400
<v Speaker 1>matter how loudly you want to shout it. It's still misinformation.

0:32:26.800 --> 0:32:30.479
<v Speaker 1>And if a site has a policy against the spread

0:32:30.520 --> 0:32:34.320
<v Speaker 1>of misinformation, that means you are violating the policy by

0:32:34.320 --> 0:32:36.600
<v Speaker 1>trying to spread it. And you know, just because you

0:32:36.640 --> 0:32:40.800
<v Speaker 1>want something to be true doesn't make it true. Trust me,

0:32:41.040 --> 0:32:44.960
<v Speaker 1>I know this because otherwise I would be a bazillionaire

0:32:45.360 --> 0:32:50.440
<v Speaker 1>because I want that to be true anyway, the narrative

0:32:50.880 --> 0:32:54.240
<v Speaker 1>you know that social networks are biased against conservatives and

0:32:54.280 --> 0:32:58.720
<v Speaker 1>are actively suppressing conservative speech. That has played into other

0:32:58.840 --> 0:33:03.160
<v Speaker 1>stories with face Book. Some of those internal documents revealed

0:33:03.200 --> 0:33:08.400
<v Speaker 1>that Facebook executives discouraged teams from clamping down on misinformation

0:33:08.440 --> 0:33:14.080
<v Speaker 1>campaigns or making tweaks to Facebook's algorithm to avoid amplifying

0:33:14.120 --> 0:33:17.360
<v Speaker 1>those claims, because they were concerned that if they made

0:33:17.360 --> 0:33:20.560
<v Speaker 1>those changes, it would add fuel to the fire and

0:33:20.600 --> 0:33:24.840
<v Speaker 1>give conservatives more quote unquote proof that the platform had

0:33:24.920 --> 0:33:29.960
<v Speaker 1>an anti conservative bias. Never mind that some of these

0:33:30.000 --> 0:33:33.960
<v Speaker 1>posts were getting amplified by the algorithm, such as posts

0:33:34.000 --> 0:33:38.600
<v Speaker 1>that included hateful rhetoric targeting vulnerable populations ranging from ethnic

0:33:38.640 --> 0:33:43.760
<v Speaker 1>minorities to the transgender community. These were all violating Facebook's

0:33:43.800 --> 0:33:48.240
<v Speaker 1>own rules, right, Facebook has actual rules about this. The

0:33:48.360 --> 0:33:54.560
<v Speaker 1>posts were definitely and definitively violating those rules, and yet

0:33:54.600 --> 0:33:58.000
<v Speaker 1>they were being amplified by Facebook's algorithm because they were

0:33:58.080 --> 0:34:02.040
<v Speaker 1>driving engagement. So the desire to avoid looking like a

0:34:02.080 --> 0:34:07.080
<v Speaker 1>biased platform in the executive's minds outweighed any desire to

0:34:07.200 --> 0:34:10.839
<v Speaker 1>avoid spreading harm. And yeah, this is borne out by

0:34:10.880 --> 0:34:14.480
<v Speaker 1>some of those internal documents that Hogan provided, So we've

0:34:14.480 --> 0:34:19.279
<v Speaker 1>actually seen the emails that the story plays out in.

0:34:20.200 --> 0:34:24.000
<v Speaker 1>But wait, there's more. One of the early stories prompted

0:34:24.040 --> 0:34:28.080
<v Speaker 1>by Hogan's whistle blowing activities focused on Instagram and the

0:34:28.120 --> 0:34:33.000
<v Speaker 1>possibility that Instagram could be harming people, particularly young women,

0:34:33.520 --> 0:34:36.839
<v Speaker 1>and that worse, folks on Instagram are fully aware of

0:34:36.880 --> 0:34:40.920
<v Speaker 1>this and yet continue to make things worse. And the

0:34:40.960 --> 0:34:43.759
<v Speaker 1>news broke right around the time that we started hearing

0:34:43.760 --> 0:34:47.000
<v Speaker 1>about a plan that would see an Instagram app targeting

0:34:47.160 --> 0:34:50.600
<v Speaker 1>young users, like those younger than the age of thirteen.

0:34:51.160 --> 0:34:54.920
<v Speaker 1>Not a great look. So this internal document cited some

0:34:55.040 --> 0:34:58.600
<v Speaker 1>research that you know, appeared to link a decline in

0:34:58.719 --> 0:35:02.680
<v Speaker 1>some users sell image or their mental health and their

0:35:02.840 --> 0:35:05.360
<v Speaker 1>use of Instagram, you know, saying that there appears to

0:35:05.400 --> 0:35:09.640
<v Speaker 1>be some sort of link between the two. Now Immediately,

0:35:09.760 --> 0:35:13.000
<v Speaker 1>lawmakers in the US showed concern, and I think we

0:35:13.080 --> 0:35:17.520
<v Speaker 1>all pretty much intuitively feel that overuse of platforms like

0:35:17.560 --> 0:35:22.680
<v Speaker 1>Instagram are probably harmful because the platform really promotes an

0:35:22.760 --> 0:35:26.759
<v Speaker 1>unrealistic view of people's lives. Right if you spend any

0:35:26.800 --> 0:35:29.640
<v Speaker 1>time on Instagram and you start scrolling through it, you're

0:35:29.719 --> 0:35:33.759
<v Speaker 1>likely to see posts of really attractive people appearing to

0:35:33.840 --> 0:35:38.319
<v Speaker 1>live out fantasy lives in incredible settings, and it's hard

0:35:38.360 --> 0:35:42.560
<v Speaker 1>not to feel inferior by comparison. But this internal research

0:35:42.920 --> 0:35:46.880
<v Speaker 1>seemed to show that this wasn't a bug in Instagram,

0:35:46.880 --> 0:35:50.520
<v Speaker 1>It's a feature, and that Instagram, far from being ignorant

0:35:50.520 --> 0:35:53.760
<v Speaker 1>of this effect, was well aware and was still pursuing

0:35:53.800 --> 0:35:57.000
<v Speaker 1>efforts to expand its user base to even younger people.

0:35:57.880 --> 0:36:02.680
<v Speaker 1>Now Facebook slash Instagram would try to refute this, saying

0:36:02.719 --> 0:36:06.160
<v Speaker 1>that the research only represents a tiny amount of information

0:36:06.560 --> 0:36:10.360
<v Speaker 1>and that these interpretations are wrong, and also that the

0:36:10.400 --> 0:36:14.080
<v Speaker 1>studies involved a very small sample size. But that also

0:36:14.160 --> 0:36:17.520
<v Speaker 1>prompts discussions about you know, how the company is under

0:36:17.560 --> 0:36:21.160
<v Speaker 1>Meta operate with a lack of transparency, and that's saying

0:36:21.520 --> 0:36:24.400
<v Speaker 1>this is just a tiny bit of information isn't really

0:36:24.440 --> 0:36:27.399
<v Speaker 1>a good argument because the company hasn't bothered to show

0:36:27.400 --> 0:36:31.440
<v Speaker 1>anything of the big picture that could actually contradict the

0:36:31.480 --> 0:36:35.560
<v Speaker 1>conclusions people have made based upon the quote unquote limited

0:36:35.719 --> 0:36:40.680
<v Speaker 1>information that they've had access to. So, you know it,

0:36:40.680 --> 0:36:43.279
<v Speaker 1>it's kind of like when you you're you're a kid

0:36:43.320 --> 0:36:45.759
<v Speaker 1>and you're playing a game like Cops and Robbers and

0:36:45.800 --> 0:36:47.680
<v Speaker 1>you say, bang, I shot you and the other kids

0:36:47.760 --> 0:36:51.279
<v Speaker 1>is no, you didn't. It's kind of like what Facebook saying.

0:36:51.280 --> 0:36:52.880
<v Speaker 1>It's like that, you know, they're saying this is the

0:36:52.920 --> 0:36:57.439
<v Speaker 1>study shows you know it's harmful, So no, it doesn't. Um, well,

0:36:57.600 --> 0:37:00.719
<v Speaker 1>that's not really a good refutation. I would say I

0:37:00.719 --> 0:37:03.200
<v Speaker 1>could probably do a very full episode or even a

0:37:03.239 --> 0:37:06.640
<v Speaker 1>series of episodes about the awful stories linked to Facebook

0:37:06.719 --> 0:37:09.960
<v Speaker 1>and Meta for this year, but instead, I'm going to

0:37:10.080 --> 0:37:12.640
<v Speaker 1>limit myself to a few highlights. So keep in mind,

0:37:13.239 --> 0:37:15.359
<v Speaker 1>I'm going to cover some stuff, some more stuff about

0:37:15.360 --> 0:37:18.440
<v Speaker 1>Facebook before we close out this episode. But it's a

0:37:18.520 --> 0:37:21.400
<v Speaker 1>drop in the bucket compared to all the different stories

0:37:21.440 --> 0:37:24.279
<v Speaker 1>that came out this past year about that company. So

0:37:25.560 --> 0:37:29.080
<v Speaker 1>there were concerns about misinformation that obviously extend well beyond

0:37:29.200 --> 0:37:33.480
<v Speaker 1>US politics. I mentioned COVID nineteen earlier. Uh, there were

0:37:33.520 --> 0:37:37.840
<v Speaker 1>a lot of concerns about Facebook's role in spreading and

0:37:37.880 --> 0:37:42.200
<v Speaker 1>amplifying misinformation about COVID nineteen. In fact, some people going

0:37:42.239 --> 0:37:45.920
<v Speaker 1>so far as to say that Facebook's role, uh, it

0:37:46.040 --> 0:37:49.040
<v Speaker 1>was actually leading to people getting sick and dying. I mean,

0:37:49.160 --> 0:37:53.040
<v Speaker 1>the United States President Joe Biden said as much. He

0:37:53.120 --> 0:37:57.040
<v Speaker 1>said the platform was quote killing people end quote. Now

0:37:57.120 --> 0:38:00.799
<v Speaker 1>later he backtracked a little bit, back pedaled and clarified

0:38:00.920 --> 0:38:03.800
<v Speaker 1>himself and said what he meant was that the misinformation

0:38:03.840 --> 0:38:08.560
<v Speaker 1>is what is killing people, not Facebook itself. However, when

0:38:08.600 --> 0:38:14.120
<v Speaker 1>Facebook's algorithm promotes misinformation because misinformation drives engagement, and as

0:38:14.160 --> 0:38:18.960
<v Speaker 1>I've said many many times, that is the end goal

0:38:19.160 --> 0:38:23.640
<v Speaker 1>of Facebook. It's keeping as many folks on Facebook for

0:38:23.880 --> 0:38:26.959
<v Speaker 1>as long as possible in order to serve as many

0:38:27.000 --> 0:38:30.719
<v Speaker 1>ads as possible. Doesn't really care what the content is,

0:38:30.760 --> 0:38:35.080
<v Speaker 1>as long as it keeps people there. Well, then tomato, tomato, right.

0:38:35.200 --> 0:38:38.040
<v Speaker 1>I mean, if that's the goal, is just keeping people there,

0:38:38.080 --> 0:38:40.600
<v Speaker 1>and if the thing that keeps people there is misinformation,

0:38:41.400 --> 0:38:43.680
<v Speaker 1>and if the misinformation is what is leading to people

0:38:43.680 --> 0:38:46.040
<v Speaker 1>getting sick and dying, I don't think it's that big

0:38:46.080 --> 0:38:48.880
<v Speaker 1>of a stretch to actually say something like, hey, Facebook,

0:38:48.920 --> 0:38:53.640
<v Speaker 1>you're killing people because it you know, it doesn't really

0:38:53.680 --> 0:38:59.000
<v Speaker 1>matter the semantics of that. It ultimately of Facebook's playing

0:38:59.000 --> 0:39:02.400
<v Speaker 1>a part in the ampleification and distribution of misinformation, and

0:39:02.440 --> 0:39:08.759
<v Speaker 1>that misinformation is killing people. You know, the logic concludes, right, Well,

0:39:08.800 --> 0:39:13.200
<v Speaker 1>then there's the story of the Rohinga in Myanmar. So

0:39:13.239 --> 0:39:16.040
<v Speaker 1>the Rohinga people are Muslim and they are also the

0:39:16.080 --> 0:39:19.560
<v Speaker 1>target of a genocidal campaign in Myanmar and have been

0:39:19.640 --> 0:39:24.239
<v Speaker 1>for a few years. Anti Rohinga posts flourished on Facebook

0:39:24.280 --> 0:39:28.200
<v Speaker 1>in Myanmar um, some of which were posted by the

0:39:28.239 --> 0:39:33.280
<v Speaker 1>government itself, and hate speech circulated frequently on the platform,

0:39:33.360 --> 0:39:36.399
<v Speaker 1>and it fueled the government's campaign to wipe out an

0:39:36.600 --> 0:39:40.839
<v Speaker 1>entire people. Now, some survivors have brought a pair of

0:39:40.840 --> 0:39:46.600
<v Speaker 1>class action lawsuits against Meta Slash Facebook, claiming that Facebook's

0:39:46.640 --> 0:39:51.240
<v Speaker 1>actions exacerbated a deadly situation Myanmar, and they are seeking

0:39:51.280 --> 0:39:55.280
<v Speaker 1>a hundred fifty billion dollars in damages as a result.

0:39:55.320 --> 0:39:58.640
<v Speaker 1>Now that's a fairly new story, so it hasn't played

0:39:58.680 --> 0:40:02.120
<v Speaker 1>out yet they spoke the company itself. As I've mentioned

0:40:02.120 --> 0:40:05.640
<v Speaker 1>a couple of times here, it officially rebranded as Meta

0:40:05.920 --> 0:40:08.920
<v Speaker 1>in October, in reference to the concept of a metaverse.

0:40:09.360 --> 0:40:11.920
<v Speaker 1>But I've covered that fairly recently, so we're not going

0:40:11.960 --> 0:40:14.400
<v Speaker 1>to dwell on it here except to say that the

0:40:14.440 --> 0:40:19.080
<v Speaker 1>metaverse as folks usually think of it, is probably pretty

0:40:19.120 --> 0:40:22.640
<v Speaker 1>far off the tech just eight there yet folks, and

0:40:22.760 --> 0:40:26.480
<v Speaker 1>the rebranding prompted a lot of cynics to suggest that

0:40:26.560 --> 0:40:28.920
<v Speaker 1>the timing was more about Facebook trying to make it

0:40:29.000 --> 0:40:32.600
<v Speaker 1>harder for folks to criticize the company or to link

0:40:32.719 --> 0:40:37.120
<v Speaker 1>Meta the company to Facebook the platform. I don't necessarily

0:40:37.160 --> 0:40:39.680
<v Speaker 1>think that's the case. If it is the case, I

0:40:39.680 --> 0:40:43.840
<v Speaker 1>don't think it's working very well. And discussions continue around

0:40:43.880 --> 0:40:47.200
<v Speaker 1>the world about the possibility of breaking Meta up into

0:40:47.239 --> 0:40:51.239
<v Speaker 1>smaller companies to make Meta divest itself of things like

0:40:51.400 --> 0:40:55.560
<v Speaker 1>Instagram and WhatsApp Meta slash. Facebook has been in the

0:40:55.560 --> 0:41:00.880
<v Speaker 1>spotlight during several talks about anti competitive practices. We haven't

0:41:00.880 --> 0:41:04.320
<v Speaker 1>seen much action on that front, and there are plenty

0:41:04.520 --> 0:41:08.279
<v Speaker 1>of folks who are skeptical that if Meta ever did

0:41:08.360 --> 0:41:11.800
<v Speaker 1>break up, which is already unlikely. According to these people,

0:41:12.239 --> 0:41:15.200
<v Speaker 1>that if it did break up, it wouldn't change very much.

0:41:16.280 --> 0:41:19.600
<v Speaker 1>That's entirely possible. It's outside my realm of expertise, so

0:41:19.640 --> 0:41:23.719
<v Speaker 1>I can't really comment on it. But yeah, that's uh,

0:41:23.840 --> 0:41:26.279
<v Speaker 1>that's kind of what I wanted to wrap up with

0:41:26.440 --> 0:41:30.920
<v Speaker 1>Facebook in one. Again, there's a lot more to say.

0:41:31.280 --> 0:41:35.279
<v Speaker 1>Those internal documents, they go so far and so deep,

0:41:35.320 --> 0:41:38.120
<v Speaker 1>and we still only have, you know, people like me,

0:41:38.280 --> 0:41:43.280
<v Speaker 1>We've I've only seen a fraction of what is actually there. Uh,

0:41:43.320 --> 0:41:46.560
<v Speaker 1>goodness knows what else is there that could lead to

0:41:46.760 --> 0:41:51.040
<v Speaker 1>some pretty tough conversations around Facebook and its role in

0:41:51.160 --> 0:41:56.880
<v Speaker 1>various social ills and the amplification of those. All right, um,

0:41:56.960 --> 0:41:58.640
<v Speaker 1>you know what, I've got a few minutes. Let's go

0:41:58.680 --> 0:42:02.320
<v Speaker 1>ahead and talk about one other thing before we conclude,

0:42:02.360 --> 0:42:05.200
<v Speaker 1>and that'll be n f T S. I mean, can

0:42:05.239 --> 0:42:08.480
<v Speaker 1>I interest you in n f T Uh That there's

0:42:08.520 --> 0:42:11.480
<v Speaker 1>what we also refer to as a non fungible token,

0:42:11.840 --> 0:42:14.200
<v Speaker 1>and it tells you it's the product of the future,

0:42:14.719 --> 0:42:17.920
<v Speaker 1>and and by product, I mean it's digital code linked

0:42:17.920 --> 0:42:21.000
<v Speaker 1>to a digital wallet, and arguably it don't mean much else.

0:42:21.200 --> 0:42:23.239
<v Speaker 1>But never mind that. Look at this shiny n f

0:42:23.440 --> 0:42:26.560
<v Speaker 1>T and by y'all, so Yeah, n f t s,

0:42:27.239 --> 0:42:31.440
<v Speaker 1>we're huge in one, or at least they got a

0:42:31.560 --> 0:42:35.319
<v Speaker 1>ton of attention early in one. Now, to be clear,

0:42:35.719 --> 0:42:38.520
<v Speaker 1>n f t s predate one. It's not like they

0:42:38.560 --> 0:42:40.919
<v Speaker 1>were suddenly invented this year. But I think it's safe

0:42:40.960 --> 0:42:43.840
<v Speaker 1>to say that a lot of us, including myself, hadn't

0:42:43.880 --> 0:42:47.400
<v Speaker 1>really heard about them before this year. So let's just

0:42:47.440 --> 0:42:49.239
<v Speaker 1>get to it. What the heck is an n f

0:42:49.280 --> 0:42:52.839
<v Speaker 1>T and what's all the fuss about? Well, I like

0:42:52.920 --> 0:42:55.279
<v Speaker 1>to call n f t s the equivalent of a

0:42:55.360 --> 0:43:01.160
<v Speaker 1>digital receipt. It's proof of ownership over some digital product.

0:43:01.719 --> 0:43:04.600
<v Speaker 1>That product could be an MP three file, it could

0:43:04.600 --> 0:43:07.520
<v Speaker 1>be a video, it could be a piece of digital artwork.

0:43:07.920 --> 0:43:10.160
<v Speaker 1>It could even be a tweet or just a line

0:43:10.200 --> 0:43:13.479
<v Speaker 1>of code. There are things that are hard to quote

0:43:13.560 --> 0:43:17.600
<v Speaker 1>unquote own in the traditional sense in the digital world,

0:43:17.719 --> 0:43:21.200
<v Speaker 1>Like you can't go out and purchase the original all

0:43:21.239 --> 0:43:24.560
<v Speaker 1>your base are belonged to us meme and then hang

0:43:24.640 --> 0:43:26.759
<v Speaker 1>it in your den, for example. It's not like a

0:43:26.800 --> 0:43:31.840
<v Speaker 1>physical piece of art where there's one single original work

0:43:31.880 --> 0:43:36.080
<v Speaker 1>of it and then lots of copies. It's a digital thing, right,

0:43:36.200 --> 0:43:39.280
<v Speaker 1>Folks can replicate and alter it to their hearts. Content,

0:43:39.840 --> 0:43:44.280
<v Speaker 1>and there's no way to differentiate a copy from the original. However,

0:43:45.160 --> 0:43:49.040
<v Speaker 1>and n f T can represent a specific instance of

0:43:49.280 --> 0:43:53.279
<v Speaker 1>a piece of digital information, and it can show that

0:43:53.280 --> 0:43:57.800
<v Speaker 1>that instance belongs to someone specific. So n f T

0:43:58.040 --> 0:44:00.759
<v Speaker 1>s are of these digital receipts, and they exist on

0:44:00.880 --> 0:44:06.319
<v Speaker 1>top of the Ethereum blockchain, the cryptocurrency Ethereum. Now that

0:44:06.360 --> 0:44:09.960
<v Speaker 1>means each transaction of an n f T is part

0:44:10.080 --> 0:44:13.880
<v Speaker 1>of the blockchain record. So just by referencing the ledger

0:44:14.080 --> 0:44:17.960
<v Speaker 1>for Ethereum, you can see who owns what. So I

0:44:18.000 --> 0:44:20.279
<v Speaker 1>can actually look at that ledger and say, oh, hey, look,

0:44:20.400 --> 0:44:23.000
<v Speaker 1>Josh Clark owns the n f T for the original

0:44:23.040 --> 0:44:26.800
<v Speaker 1>all your base meme. He doesn't. That's just an example,

0:44:27.000 --> 0:44:29.120
<v Speaker 1>or at least he doesn't to my knowledge. But that's

0:44:29.120 --> 0:44:33.280
<v Speaker 1>just an example. But what does that mean in practical terms?

0:44:34.239 --> 0:44:37.680
<v Speaker 1>That is harder to say, because while you've got proof

0:44:37.960 --> 0:44:42.240
<v Speaker 1>that you have ownership of that particular piece of digital work,

0:44:42.760 --> 0:44:45.600
<v Speaker 1>it doesn't change the fact that the digital item is,

0:44:46.280 --> 0:44:51.600
<v Speaker 1>you know, digital and thus replicable and such. There's proof

0:44:51.640 --> 0:44:54.520
<v Speaker 1>that you own it, and you can always sell or

0:44:54.640 --> 0:44:58.279
<v Speaker 1>trade that proof of ownership to someone else, and that

0:44:58.360 --> 0:45:01.680
<v Speaker 1>transaction will then enter the chain Ledger to show that

0:45:01.760 --> 0:45:05.799
<v Speaker 1>it has in fact changed hands, and there's been you know,

0:45:06.239 --> 0:45:08.359
<v Speaker 1>a lot of that. There's also a lot of speculation

0:45:08.400 --> 0:45:10.600
<v Speaker 1>around n f T s, the idea that these are

0:45:10.640 --> 0:45:13.960
<v Speaker 1>things that will increase in value. So we've seen a

0:45:13.960 --> 0:45:17.520
<v Speaker 1>lot of investors speculation, but a lot of those values

0:45:17.600 --> 0:45:21.680
<v Speaker 1>haven't really held over time. There's also this thought that

0:45:21.840 --> 0:45:23.880
<v Speaker 1>n f t s are going to become more important

0:45:23.880 --> 0:45:26.600
<v Speaker 1>in the future with a metaverse. The idea here is

0:45:26.640 --> 0:45:29.400
<v Speaker 1>that you could purchase n f t s that represent

0:45:29.480 --> 0:45:34.000
<v Speaker 1>ownership of certain digital goods, and that in theory, these

0:45:34.040 --> 0:45:38.040
<v Speaker 1>digital goods will be able to exist across multiple virtual

0:45:38.239 --> 0:45:42.080
<v Speaker 1>environments within the metaverse. So if you bought, say a

0:45:42.160 --> 0:45:46.000
<v Speaker 1>really cool avatar design in one virtual environment, and you

0:45:46.000 --> 0:45:48.000
<v Speaker 1>have the n f T for it, you could in

0:45:48.040 --> 0:45:52.520
<v Speaker 1>theory port that over to other digital environments. So to

0:45:52.600 --> 0:45:56.000
<v Speaker 1>use a video game analogy, imagine you're playing a game

0:45:56.080 --> 0:45:59.680
<v Speaker 1>like war Zone and you purchase a skin in the

0:45:59.719 --> 0:46:01.920
<v Speaker 1>game to make your character look like I don't know,

0:46:02.320 --> 0:46:04.640
<v Speaker 1>the ghost face killer in the screen movies, because that

0:46:04.680 --> 0:46:07.400
<v Speaker 1>actually exists in the war Zone game war Zone. If

0:46:07.400 --> 0:46:12.000
<v Speaker 1>you're not familiar first person shooter game and uh so, yeah,

0:46:12.040 --> 0:46:14.560
<v Speaker 1>you can buy a skin that makes you look like

0:46:14.920 --> 0:46:18.839
<v Speaker 1>the killer from the screen movies. Then you decide, Hey,

0:46:18.840 --> 0:46:21.399
<v Speaker 1>I want to start playing Minecraft, but I also would

0:46:21.480 --> 0:46:24.280
<v Speaker 1>love to use the skin I bought in war Zone

0:46:25.160 --> 0:46:28.160
<v Speaker 1>in Minecraft, so that if you see me in Minecraft,

0:46:28.360 --> 0:46:30.160
<v Speaker 1>I'm still wearing the same skin that I would be

0:46:30.160 --> 0:46:32.920
<v Speaker 1>wearing in war Zone. So no matter what game I'm in,

0:46:33.360 --> 0:46:36.200
<v Speaker 1>you can tell it's me because I'm wearing that skin. However,

0:46:36.719 --> 0:46:38.640
<v Speaker 1>you know we bought the skin in war Zone. That

0:46:38.719 --> 0:46:41.359
<v Speaker 1>means that you know we bought it in a game

0:46:41.360 --> 0:46:43.880
<v Speaker 1>that has no connection to Minecraft, so you can't just

0:46:44.000 --> 0:46:47.879
<v Speaker 1>poured it over right. Well, the metaverse, if it ever

0:46:47.920 --> 0:46:51.320
<v Speaker 1>actually comes to pass, is likely to consist of multiple

0:46:51.440 --> 0:46:55.960
<v Speaker 1>virtual environments that are created and maintained by different companies

0:46:55.960 --> 0:47:00.040
<v Speaker 1>and groups. Navigating from world to world will require a

0:47:00.040 --> 0:47:03.120
<v Speaker 1>lot of platform support, so the ideas that n f

0:47:03.160 --> 0:47:06.240
<v Speaker 1>t s could play a small part in this, providing

0:47:06.280 --> 0:47:09.360
<v Speaker 1>proof that a person has the right to use certain

0:47:09.400 --> 0:47:13.160
<v Speaker 1>designs as they navigate throughout the metaverse and pass from

0:47:13.239 --> 0:47:17.600
<v Speaker 1>environment to environment. However, that doesn't mean it's actually going

0:47:17.680 --> 0:47:21.520
<v Speaker 1>to happen. I mean, imagine if you could pour over

0:47:21.560 --> 0:47:24.440
<v Speaker 1>your skin from war Zone to Minecraft, let's say that

0:47:24.520 --> 0:47:29.720
<v Speaker 1>there actually was that capability. War Zone uses fairly realistic graphics,

0:47:29.719 --> 0:47:32.960
<v Speaker 1>like the people in war Zone look like people. Minecraft

0:47:33.080 --> 0:47:36.480
<v Speaker 1>is very cartoony and blocking, so a war Zone skin

0:47:37.160 --> 0:47:41.520
<v Speaker 1>would look very different when realized in Minecraft, and you

0:47:41.520 --> 0:47:43.000
<v Speaker 1>would have to have some way to deal with that

0:47:43.160 --> 0:47:47.000
<v Speaker 1>to actually make it work within the two very different environments.

0:47:47.040 --> 0:47:49.200
<v Speaker 1>So what I'm saying is that while n f T

0:47:49.360 --> 0:47:51.960
<v Speaker 1>s could theoretically play a part in the metaverse, it

0:47:52.000 --> 0:47:55.920
<v Speaker 1>will require a ton of cooperation behind the scenes. So

0:47:56.000 --> 0:48:00.560
<v Speaker 1>it's not like it's a foregone conclusion. Like, even even

0:48:00.600 --> 0:48:02.759
<v Speaker 1>as companies like Nike get into the n f T

0:48:02.960 --> 0:48:06.400
<v Speaker 1>game and they start offering up virtual versions of Nikes

0:48:06.840 --> 0:48:09.840
<v Speaker 1>as n f T s, it doesn't mean that, should

0:48:09.840 --> 0:48:12.839
<v Speaker 1>the metaverse actually become a thing, that you'll be able

0:48:12.880 --> 0:48:16.320
<v Speaker 1>to purchase a specific style of Nikes as an n

0:48:16.400 --> 0:48:20.320
<v Speaker 1>f T and wear it throughout all the metaverse, unless

0:48:20.360 --> 0:48:23.279
<v Speaker 1>it's something that's all self contained by one company, in

0:48:23.320 --> 0:48:26.000
<v Speaker 1>which case I would argue it's not really a metaverse

0:48:26.040 --> 0:48:30.600
<v Speaker 1>at all, But that's an episode for another time. Anyway,

0:48:30.920 --> 0:48:32.719
<v Speaker 1>the n f T craze really kind of hit a

0:48:32.719 --> 0:48:35.680
<v Speaker 1>peak in the early part of one and of course

0:48:35.680 --> 0:48:39.000
<v Speaker 1>you still hear about them now, but I feel like

0:48:39.680 --> 0:48:43.160
<v Speaker 1>a lot of folks, apart from the evangelists who are

0:48:43.160 --> 0:48:45.080
<v Speaker 1>hoping to get rich quick off n f t s,

0:48:45.320 --> 0:48:48.160
<v Speaker 1>have kind of cooled off of them for now, Like

0:48:48.280 --> 0:48:51.759
<v Speaker 1>people don't seem to be quite as jazzed about it

0:48:51.800 --> 0:48:55.160
<v Speaker 1>as when they were really being pushed in say like

0:48:55.320 --> 0:48:59.480
<v Speaker 1>March of this year. Okay, we've gone on pretty long.

0:48:59.520 --> 0:49:02.080
<v Speaker 1>We're gonna wrap this up now. We are going to

0:49:02.239 --> 0:49:04.279
<v Speaker 1>continue to do a few more episodes about some of

0:49:04.320 --> 0:49:07.120
<v Speaker 1>the tech stories of one because obviously a lot of

0:49:07.160 --> 0:49:11.440
<v Speaker 1>other stuff has happened. So when we return later this week,

0:49:11.880 --> 0:49:15.680
<v Speaker 1>we will keep on going until my psyche cracks under

0:49:15.719 --> 0:49:17.960
<v Speaker 1>all the things that have happened over the last year.

0:49:18.160 --> 0:49:23.200
<v Speaker 1>Like I said, years, these days feel like they've lasted

0:49:23.200 --> 0:49:26.239
<v Speaker 1>an eternity and at the same time like they're over

0:49:26.280 --> 0:49:31.640
<v Speaker 1>in an instant. It's it's a weird paradox where I think,

0:49:31.719 --> 0:49:34.160
<v Speaker 1>oh gosh, that happened this year. I could have sworn

0:49:34.200 --> 0:49:37.680
<v Speaker 1>that was like five years ago too. Oh wow, I

0:49:37.719 --> 0:49:42.560
<v Speaker 1>can't believe the years over already. Um, time is funny, y'all.

0:49:42.640 --> 0:49:45.480
<v Speaker 1>All right, Well, if you have suggestions for topics I

0:49:45.480 --> 0:49:48.960
<v Speaker 1>should cover in future episodes of tech Stuff. Please let

0:49:49.000 --> 0:49:51.120
<v Speaker 1>me know. Reach out to me on Twitter. It's the

0:49:51.120 --> 0:49:53.280
<v Speaker 1>best place to find me. The handle for the show

0:49:53.400 --> 0:49:56.640
<v Speaker 1>is text stuff H s W and I'll talk to

0:49:56.719 --> 0:50:06.359
<v Speaker 1>you again really soon. Text Stuff is an I Heart

0:50:06.440 --> 0:50:10.160
<v Speaker 1>Radio production. For more podcasts from I Heart Radio, visit

0:50:10.200 --> 0:50:13.319
<v Speaker 1>the i Heart Radio app, Apple Podcasts, or wherever you

0:50:13.360 --> 0:50:14.720
<v Speaker 1>listen to your favorite shows.