WEBVTT - The Big Tech Stories of 2022: The World vs Big Tech

0:00:04.440 --> 0:00:07.840
<v Speaker 1>Welcome to text Stuff, a production from I Heart Radio.

0:00:11.880 --> 0:00:15.160
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:15.360 --> 0:00:19.440
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio.

0:00:19.760 --> 0:00:24.959
<v Speaker 1>And how the tech are you? Well? We made it mostly.

0:00:25.320 --> 0:00:28.280
<v Speaker 1>Now that we're creeping up to the very end of

0:00:28.360 --> 0:00:32.280
<v Speaker 1>twenty two, it is time to look back over the

0:00:32.280 --> 0:00:35.080
<v Speaker 1>past year and reflect on some of the big tech

0:00:35.280 --> 0:00:40.840
<v Speaker 1>news stories that unfolded over the previous twelve months. And gosh,

0:00:41.240 --> 0:00:44.839
<v Speaker 1>there were a ton of them. So when I started

0:00:45.280 --> 0:00:49.280
<v Speaker 1>just putting together a bullet list of stories that I

0:00:49.320 --> 0:00:53.760
<v Speaker 1>felt were particularly important, that list quickly stretched to a

0:00:53.760 --> 0:00:56.959
<v Speaker 1>couple of pages. And this was just a bullet list, right,

0:00:57.000 --> 0:01:01.440
<v Speaker 1>I didn't give like context or anything. So this week

0:01:01.880 --> 0:01:05.000
<v Speaker 1>we're going to look back and talk about what happened

0:01:05.040 --> 0:01:08.440
<v Speaker 1>in two and why it was important, both in the

0:01:08.520 --> 0:01:12.760
<v Speaker 1>text sphere and beyond. So this is just the first

0:01:12.800 --> 0:01:16.160
<v Speaker 1>of those episodes. I'm taking a little more time to

0:01:16.280 --> 0:01:18.480
<v Speaker 1>kind of cover these and not just say, hey, look

0:01:18.520 --> 0:01:21.319
<v Speaker 1>at this headline now before I jump into it. I

0:01:21.360 --> 0:01:25.520
<v Speaker 1>also want to say I am not organizing these episodes chronologically,

0:01:26.160 --> 0:01:29.679
<v Speaker 1>so it's not like we're gonna start in January and

0:01:29.920 --> 0:01:32.759
<v Speaker 1>end up in December at the end of them. Instead,

0:01:32.800 --> 0:01:37.720
<v Speaker 1>I grouped stories kind of thematically, so that way we can,

0:01:37.920 --> 0:01:41.160
<v Speaker 1>you know, look at things that were unfolding that we're

0:01:41.200 --> 0:01:45.120
<v Speaker 1>maybe not directly related to each other, but kind of

0:01:45.160 --> 0:01:49.560
<v Speaker 1>give an indication of general trends that sort of thing.

0:01:50.000 --> 0:01:52.600
<v Speaker 1>Now that being said, our first story does happen to

0:01:52.720 --> 0:01:57.960
<v Speaker 1>be one that began early in two and that story

0:01:58.800 --> 0:02:05.760
<v Speaker 1>is Microsoft's bid to acquire Activision Blizzard, the video game company. Now,

0:02:05.800 --> 0:02:09.640
<v Speaker 1>first off, Microsoft is perhaps best known for the Windows

0:02:09.639 --> 0:02:16.000
<v Speaker 1>operating system, more arguably the Office suite of products. Among gamers,

0:02:16.360 --> 0:02:19.480
<v Speaker 1>it is widely known as the company behind Xbox and

0:02:19.800 --> 0:02:24.280
<v Speaker 1>Xbox Game Pass, and Activision Blizzard is a video game

0:02:24.280 --> 0:02:27.280
<v Speaker 1>company that traces its lineage all the way back to

0:02:27.520 --> 0:02:32.000
<v Speaker 1>nineteen seventy nine. In fact, Activision got started just four

0:02:32.160 --> 0:02:36.880
<v Speaker 1>years after Microsoft launched, and that whole history is fascinating

0:02:36.919 --> 0:02:40.320
<v Speaker 1>because Activision was a splinter group off of Atari. But

0:02:41.320 --> 0:02:45.920
<v Speaker 1>the history of Activision Blizzard gets super complicated and has

0:02:45.960 --> 0:02:48.720
<v Speaker 1>a lot of hairpin turns and dead ends, and honestly,

0:02:48.800 --> 0:02:51.040
<v Speaker 1>I've done episodes about it in the past, so we

0:02:51.120 --> 0:02:54.080
<v Speaker 1>won't go into a ton of detail. But then we

0:02:54.160 --> 0:02:57.840
<v Speaker 1>also have to talk about Blizzard Entertainment, a much younger

0:02:58.120 --> 0:03:01.560
<v Speaker 1>game company compared to Activision. It had been founded in

0:03:01.760 --> 0:03:07.079
<v Speaker 1>nine and Activision acquired Blizzard in two thousand and eight,

0:03:07.120 --> 0:03:10.960
<v Speaker 1>and the consolidated power of these companies allowed it to

0:03:11.000 --> 0:03:15.160
<v Speaker 1>perform quite well. In fact, depending upon how you want

0:03:15.200 --> 0:03:17.720
<v Speaker 1>to measure it, Activision Blizzard is one of the top

0:03:17.960 --> 0:03:21.920
<v Speaker 1>five largest video game companies in the world. But again

0:03:22.520 --> 0:03:26.600
<v Speaker 1>this depends on how you measure largest, right. Do you

0:03:26.680 --> 0:03:31.440
<v Speaker 1>measure it by revenue? Do you measure it by market capitalization?

0:03:32.160 --> 0:03:36.680
<v Speaker 1>But no matter how you look at it, Activision Blizzard

0:03:36.880 --> 0:03:42.360
<v Speaker 1>is a very big, influential company in the video game space. Now,

0:03:42.400 --> 0:03:46.880
<v Speaker 1>we first heard of Microsoft's plan to purchase Activision Blizzard

0:03:47.040 --> 0:03:51.560
<v Speaker 1>in mid January twenty two. Microsoft's offer was to buy

0:03:51.560 --> 0:03:55.280
<v Speaker 1>out Activision Blizzard for nine dollars per share in an

0:03:55.320 --> 0:03:59.360
<v Speaker 1>all cash transaction, and that would amount to around sixty

0:03:59.400 --> 0:04:03.320
<v Speaker 1>eight point seven billion dollars billion with a B. That's

0:04:03.320 --> 0:04:07.080
<v Speaker 1>a yawlsa right there. This was actually a hefty premium

0:04:07.080 --> 0:04:10.240
<v Speaker 1>on Activision Blizzard stock, which over the last year hit

0:04:10.280 --> 0:04:13.720
<v Speaker 1>a high of eighty six dollars ninety cents and a

0:04:13.880 --> 0:04:17.960
<v Speaker 1>low of sixty dollars sixty cents, so bucks per share

0:04:18.600 --> 0:04:22.840
<v Speaker 1>pretty attractive price, right, So you tell shareholders, hey, we're

0:04:22.839 --> 0:04:27.119
<v Speaker 1>gonna pay you a premium on every single share you own.

0:04:28.080 --> 0:04:30.359
<v Speaker 1>You just have to less know if you're cool with it.

0:04:30.440 --> 0:04:32.840
<v Speaker 1>And the shareholders were like, we're totally cool with it.

0:04:33.600 --> 0:04:36.719
<v Speaker 1>But let's get a little more backstory, because this whole

0:04:36.800 --> 0:04:39.760
<v Speaker 1>thing has a lot of complications. So first up, in

0:04:40.640 --> 0:04:44.720
<v Speaker 1>one last year, several former and some current employees at

0:04:44.760 --> 0:04:49.000
<v Speaker 1>Activision Blizzard came forward with accusations that the company was

0:04:49.080 --> 0:04:53.640
<v Speaker 1>fostering a culture that allowed for sexual harassment, pay disparity,

0:04:53.680 --> 0:04:59.159
<v Speaker 1>and discrimination. Further, that the CEO of the company, Bobby Codek,

0:04:59.640 --> 0:05:02.880
<v Speaker 1>had been aware of these problems for years and had

0:05:02.920 --> 0:05:07.080
<v Speaker 1>failed to do anything about them. We heard many stories

0:05:07.120 --> 0:05:09.760
<v Speaker 1>that were familiar to anyone who was paying attention during

0:05:09.800 --> 0:05:13.160
<v Speaker 1>the Me too movement that the company's HR department was

0:05:13.200 --> 0:05:17.680
<v Speaker 1>serving more as a shield for the company than as

0:05:17.920 --> 0:05:21.240
<v Speaker 1>a department looking out for employees. That's something that the

0:05:21.240 --> 0:05:24.320
<v Speaker 1>more cynical folks out there will say is the real

0:05:24.360 --> 0:05:27.680
<v Speaker 1>reason HR exists in the first place, not to protect employees,

0:05:28.040 --> 0:05:31.919
<v Speaker 1>but to protect the company. Now in retrospect, it was

0:05:32.000 --> 0:05:35.760
<v Speaker 1>clear that this Microsoft deal was moving behind the scenes

0:05:36.240 --> 0:05:39.640
<v Speaker 1>while this Activision Blizzard scandal story was unfolding back in

0:05:41.000 --> 0:05:45.239
<v Speaker 1>but while the scandal was unfolding, folks were wondering why

0:05:45.640 --> 0:05:48.400
<v Speaker 1>the company was being so reluctant to address the concerns

0:05:48.400 --> 0:05:52.480
<v Speaker 1>that were being brought forth. Meanwhile, Activision Blizzard was also

0:05:52.520 --> 0:05:56.200
<v Speaker 1>accused of trying to discourage employees from unionizing. There were

0:05:56.240 --> 0:05:59.359
<v Speaker 1>pockets of employees in the company who wanted to organize

0:05:59.400 --> 0:06:01.919
<v Speaker 1>into a union and in order to negotiate better working

0:06:01.920 --> 0:06:05.640
<v Speaker 1>conditions and compensation. It's illegal in the United States for

0:06:05.680 --> 0:06:08.840
<v Speaker 1>a company to try and prevent that from happening, so

0:06:09.160 --> 0:06:13.440
<v Speaker 1>that was also unfolding at the time. Microsoft's announcement was

0:06:13.480 --> 0:06:17.320
<v Speaker 1>a bit of a relief for some people. The reaction

0:06:17.680 --> 0:06:20.840
<v Speaker 1>among certain folks was that Microsoft was probably going to

0:06:20.920 --> 0:06:23.760
<v Speaker 1>clean house if it took possession of Activision Blizzard, that

0:06:23.839 --> 0:06:27.280
<v Speaker 1>it would do what the leadership at Activision Blizzard had

0:06:27.320 --> 0:06:30.720
<v Speaker 1>seemed reluctant to do. But others worried that this would

0:06:30.760 --> 0:06:33.600
<v Speaker 1>just mean employees would have an even harder time organizing

0:06:33.640 --> 0:06:38.479
<v Speaker 1>because Microsoft was not exactly known for championing the rights

0:06:38.520 --> 0:06:42.040
<v Speaker 1>of workers. And then there were questions about whether or

0:06:42.080 --> 0:06:47.839
<v Speaker 1>not various regulatory bodies around the world would resist this acquisition.

0:06:48.400 --> 0:06:52.839
<v Speaker 1>After all, Microsoft and Activision Blizzard are both involved in

0:06:52.880 --> 0:06:55.920
<v Speaker 1>the video game business, and you could argue, well, yeah,

0:06:55.960 --> 0:06:58.880
<v Speaker 1>that's just one part of Microsoft's overall business. It's not

0:06:58.960 --> 0:07:03.520
<v Speaker 1>their primary foecus. But it's still a major company in

0:07:03.560 --> 0:07:07.520
<v Speaker 1>the video game industry. So would regulators view the acquisition

0:07:08.080 --> 0:07:12.600
<v Speaker 1>as a reduction in overall competition within the market? Would

0:07:12.600 --> 0:07:16.640
<v Speaker 1>they worry that this newly merged entity would end up

0:07:16.760 --> 0:07:21.320
<v Speaker 1>hurting consumers down the line and discouraging competition. Now, over

0:07:21.360 --> 0:07:27.240
<v Speaker 1>the course of these concerns started bubbling up. Now he

0:07:27.400 --> 0:07:30.840
<v Speaker 1>first really started seeing some resistance in the European Union.

0:07:31.200 --> 0:07:34.320
<v Speaker 1>There were reports that Sony, another big player in the

0:07:34.400 --> 0:07:38.520
<v Speaker 1>video game space, was bending the ear of regulators in

0:07:38.560 --> 0:07:42.080
<v Speaker 1>the EU and the UK. That there were concerns that

0:07:42.400 --> 0:07:46.640
<v Speaker 1>these merged companies would hold certain popular titles like Call

0:07:46.680 --> 0:07:51.800
<v Speaker 1>of Duty and not publish them to Sony's PlayStation platform. Now,

0:07:51.880 --> 0:07:55.560
<v Speaker 1>Microsoft representatives said repeatedly that there were no such plans

0:07:55.600 --> 0:07:59.520
<v Speaker 1>to withhold titles from Sony players. They were arguing that

0:07:59.600 --> 0:08:01.400
<v Speaker 1>if they were to do that, they would be leaving

0:08:01.400 --> 0:08:03.600
<v Speaker 1>money on the table and that it would make no

0:08:03.680 --> 0:08:07.480
<v Speaker 1>sense financially to prevent them from going to to the PlayStation.

0:08:08.400 --> 0:08:11.040
<v Speaker 1>But then over here in the United States, the Federal

0:08:11.080 --> 0:08:15.760
<v Speaker 1>Trade Commission or f TC, got involved. It has brought

0:08:15.840 --> 0:08:19.360
<v Speaker 1>a case against Microsoft an Activision Blizzard to prevent the merger,

0:08:19.600 --> 0:08:23.760
<v Speaker 1>and the analysts that I follow say that the cases,

0:08:23.840 --> 0:08:27.720
<v Speaker 1>in their opinion, a fairly weak one, that while Microsoft

0:08:27.720 --> 0:08:32.040
<v Speaker 1>and Activision Blizzard our competitors, that this merger does not

0:08:32.160 --> 0:08:36.200
<v Speaker 1>necessarily indicate a reduction in competition for the overall market.

0:08:36.760 --> 0:08:40.040
<v Speaker 1>It seems to me that the general consensus is this

0:08:40.160 --> 0:08:43.840
<v Speaker 1>deal will go through, but it will take longer than

0:08:43.880 --> 0:08:47.360
<v Speaker 1>what Microsoft had hoped for originally. Now I say it

0:08:47.480 --> 0:08:50.440
<v Speaker 1>seems because I just don't know. It may very well

0:08:50.480 --> 0:08:55.760
<v Speaker 1>be that Microsoft will abandon its deal because on a

0:08:55.800 --> 0:08:59.960
<v Speaker 1>similar note, this past year we saw one proposed merger

0:09:00.280 --> 0:09:04.600
<v Speaker 1>fall through in the tech space due to regulatory obstruction.

0:09:05.320 --> 0:09:08.720
<v Speaker 1>In Video, the chip making company that's best known for

0:09:08.840 --> 0:09:13.640
<v Speaker 1>its graphics processing cards, had announced way back in that

0:09:13.800 --> 0:09:18.760
<v Speaker 1>it intended to purchase the British semiconductor company ARM, best

0:09:18.760 --> 0:09:22.200
<v Speaker 1>known as the company that designs arms CPUs. So what

0:09:22.400 --> 0:09:26.280
<v Speaker 1>ARM usually does is it designs the CPU architecture and

0:09:26.320 --> 0:09:30.880
<v Speaker 1>then license that design out to fabricators that actually make

0:09:31.200 --> 0:09:36.520
<v Speaker 1>the chips well. Way back in a Japanese conglomerate, soft Bank,

0:09:36.880 --> 0:09:41.640
<v Speaker 1>which is a truly enormous company, purchased ARM for lots

0:09:41.679 --> 0:09:46.000
<v Speaker 1>and lots of money, like many billions of dollars. So

0:09:46.120 --> 0:09:50.120
<v Speaker 1>in Nvidia was going to buy ARM from soft Bank

0:09:50.480 --> 0:09:57.640
<v Speaker 1>for forty billion dollars, pending regulatory approval. That approval did

0:09:57.640 --> 0:10:02.079
<v Speaker 1>not come. UK regulators were concerned that ARMS operations are

0:10:02.120 --> 0:10:04.760
<v Speaker 1>a matter of national security. Keep in mind, ARM is

0:10:04.880 --> 0:10:09.880
<v Speaker 1>a British company. Obviously, this is already complicated by the

0:10:09.880 --> 0:10:13.720
<v Speaker 1>fact that ARMS current owner is a Japanese company, so

0:10:14.400 --> 0:10:17.679
<v Speaker 1>it's interesting that national security became a big concern for

0:10:17.760 --> 0:10:22.760
<v Speaker 1>this particular transaction. Uh I will say that soft Bank

0:10:22.880 --> 0:10:29.240
<v Speaker 1>reportedly is preparing ARM for a public offering next year,

0:10:29.480 --> 0:10:32.640
<v Speaker 1>so in other words, ARM will again become a a

0:10:32.800 --> 0:10:36.160
<v Speaker 1>traded company on the stock market like it was before

0:10:36.200 --> 0:10:41.000
<v Speaker 1>soft Bank took possession of the company back in. Meanwhile,

0:10:41.720 --> 0:10:46.200
<v Speaker 1>companies that rely on ARM processors, which include competitors to

0:10:46.400 --> 0:10:50.559
<v Speaker 1>in Vidia, we're worried that in Video's acquisition of ARM

0:10:50.600 --> 0:10:53.600
<v Speaker 1>means that they would get cut off from access to

0:10:53.760 --> 0:10:58.000
<v Speaker 1>those ARM processors, or that they would see a big

0:10:58.080 --> 0:11:01.640
<v Speaker 1>price hike, and thus this would be bad for competition.

0:11:01.760 --> 0:11:06.400
<v Speaker 1>So those companies were objecting to this proposed merger, and

0:11:06.440 --> 0:11:09.840
<v Speaker 1>the myriad of concerns from different sources ultimately led to

0:11:10.000 --> 0:11:13.760
<v Speaker 1>Nvidia and ARM walking away from this deal that happened

0:11:14.000 --> 0:11:18.160
<v Speaker 1>way back in February twenty two. By my reckoning, that

0:11:18.280 --> 0:11:23.640
<v Speaker 1>was fifty years ago. It might just feel like that now.

0:11:24.320 --> 0:11:28.120
<v Speaker 1>Some may point to this failed merger as one of

0:11:28.160 --> 0:11:31.000
<v Speaker 1>the signs that the world in general is starting to

0:11:31.040 --> 0:11:34.520
<v Speaker 1>push back against big tech, and I'm going to talk

0:11:34.640 --> 0:11:38.160
<v Speaker 1>more about that in just a second. But the Nvidia

0:11:38.240 --> 0:11:42.359
<v Speaker 1>and ARM deal had a lot of complicating and unique factors,

0:11:42.800 --> 0:11:46.839
<v Speaker 1>from concerns about competition to that national security angle, which

0:11:47.000 --> 0:11:51.520
<v Speaker 1>you know most mergers in tech don't involve. And then

0:11:51.559 --> 0:11:54.320
<v Speaker 1>there was a further monkey wrench thrown into the works

0:11:54.440 --> 0:11:58.120
<v Speaker 1>in the form of a Chinese subsidiary of ARM, Armed

0:11:58.200 --> 0:12:01.680
<v Speaker 1>China that really did not want to see the parent

0:12:01.760 --> 0:12:05.560
<v Speaker 1>company change hands to an American owner. So you actually

0:12:05.600 --> 0:12:10.840
<v Speaker 1>had a part of ARM itself that was objecting to

0:12:11.040 --> 0:12:16.079
<v Speaker 1>this merger. So, in other words, this Nvidio ARM deal

0:12:16.440 --> 0:12:20.160
<v Speaker 1>had a lot of factors that I don't think translate

0:12:20.400 --> 0:12:24.360
<v Speaker 1>to the industry at large. They were unique for that

0:12:24.559 --> 0:12:29.120
<v Speaker 1>specific set of circumstances. But all that being said, twenty

0:12:29.240 --> 0:12:34.360
<v Speaker 1>two undeniably was a year in which we saw growing

0:12:34.440 --> 0:12:39.080
<v Speaker 1>scrutiny and resistance to so called big tech around the world.

0:12:39.400 --> 0:12:42.160
<v Speaker 1>By the way, big tech that's just a phrase that

0:12:42.200 --> 0:12:46.360
<v Speaker 1>refers to obviously the largest, most influential companies within the

0:12:46.360 --> 0:12:50.400
<v Speaker 1>tech space. And sometimes people who use big tech are

0:12:50.520 --> 0:12:54.120
<v Speaker 1>really being more precise in that they're being imprecise in

0:12:54.120 --> 0:12:58.680
<v Speaker 1>their language, but they're specifically referencing four or five companies,

0:12:58.720 --> 0:13:04.600
<v Speaker 1>in particular Apple, Meta, Google, Amazon, and if they're referring

0:13:04.600 --> 0:13:08.280
<v Speaker 1>to five, they throw Microsoft in there too. But big

0:13:08.280 --> 0:13:12.960
<v Speaker 1>tech can also refer to other influential companies like Nvidia,

0:13:13.240 --> 0:13:17.240
<v Speaker 1>or Oracle, or or ten Cent or Intel, those kind

0:13:17.240 --> 0:13:20.840
<v Speaker 1>of things. So when you read the phrase big tech,

0:13:20.920 --> 0:13:24.320
<v Speaker 1>just keep in mind a lot of journalists use that

0:13:24.360 --> 0:13:27.840
<v Speaker 1>as shorthand for those five companies I first mentioned. Others

0:13:27.920 --> 0:13:33.240
<v Speaker 1>will use it to just reference big, powerful, influential tech

0:13:33.320 --> 0:13:36.080
<v Speaker 1>companies in general. And here in the United States we

0:13:36.120 --> 0:13:39.600
<v Speaker 1>saw some progressives but into positions of authority with regard

0:13:39.679 --> 0:13:43.600
<v Speaker 1>to ensuring that markets stay fair and competitive, which was

0:13:43.679 --> 0:13:47.320
<v Speaker 1>a real change of pace from the last I don't know,

0:13:47.400 --> 0:13:51.000
<v Speaker 1>like forty years. So they include Lena Kahn, who is

0:13:51.040 --> 0:13:53.559
<v Speaker 1>the chair of the Federal Trade Commission or f TC,

0:13:53.800 --> 0:13:57.200
<v Speaker 1>so she's the one leading the US charge against Microsoft

0:13:57.280 --> 0:14:02.240
<v Speaker 1>and the Activision Blizzard merger. And there's also Jonathan Canter,

0:14:02.559 --> 0:14:06.520
<v Speaker 1>who leads the Antitrust Division at the Justice Department. Figures

0:14:06.559 --> 0:14:09.640
<v Speaker 1>like these are starting to throw roadblocks in the way

0:14:09.760 --> 0:14:12.800
<v Speaker 1>of large tech companies which have long been used to

0:14:12.840 --> 0:14:16.800
<v Speaker 1>being able to get their own way. For example Meta.

0:14:16.960 --> 0:14:20.120
<v Speaker 1>Now we're going to talk way more about Meta later

0:14:20.200 --> 0:14:22.600
<v Speaker 1>on in this series of episodes about the big stories

0:14:22.600 --> 0:14:27.240
<v Speaker 1>of two, but within this context, regulators have moved to

0:14:27.280 --> 0:14:30.800
<v Speaker 1>block Meta from acquiring a tiny little VR company called

0:14:30.880 --> 0:14:36.680
<v Speaker 1>Within Unlimited and it's fitness app called Supernatural. They're saying

0:14:36.720 --> 0:14:40.040
<v Speaker 1>that because the VR industry in general is a pretty

0:14:40.080 --> 0:14:42.560
<v Speaker 1>small one, there are not that many players in the

0:14:42.640 --> 0:14:48.479
<v Speaker 1>VR space, that Meta acquiring another VR company reduces competition

0:14:48.640 --> 0:14:52.400
<v Speaker 1>in that space, and that this would be bad for

0:14:52.640 --> 0:14:57.000
<v Speaker 1>VR moving forward. If VR and Meta becomes synonymous with

0:14:57.040 --> 0:15:01.520
<v Speaker 1>one another, that could mean a reduction in competition and innovation,

0:15:02.040 --> 0:15:05.160
<v Speaker 1>and that's a bad thing. Now, we've also heard politicians

0:15:05.200 --> 0:15:07.720
<v Speaker 1>float the idea of forcing Meta to break up into

0:15:07.760 --> 0:15:10.840
<v Speaker 1>smaller companies, similar to how the US government broke up

0:15:10.880 --> 0:15:13.480
<v Speaker 1>a T and T many years ago. Though I should

0:15:13.480 --> 0:15:16.480
<v Speaker 1>point out a T and T kind of recombined over

0:15:16.520 --> 0:15:19.360
<v Speaker 1>the years, like Terminator one thousand style, like all those

0:15:19.400 --> 0:15:24.680
<v Speaker 1>little drops of mercury. So we'll see if that happens. Okay,

0:15:24.880 --> 0:15:27.120
<v Speaker 1>We've got a lot more to talk about with this

0:15:27.320 --> 0:15:30.960
<v Speaker 1>line of tech stories from two, but before we do that,

0:15:31.040 --> 0:15:45.400
<v Speaker 1>let's take a quick break. We're back, Okay. So we

0:15:45.400 --> 0:15:49.160
<v Speaker 1>were talking about regulations and the tech industry and sort

0:15:49.160 --> 0:15:53.680
<v Speaker 1>of a pushback on big tech. Well we really saw

0:15:53.720 --> 0:15:57.600
<v Speaker 1>that take form over the European Union. Uh, they have

0:15:57.680 --> 0:16:00.640
<v Speaker 1>been pushing back against big tech quite a bit this year,

0:16:00.680 --> 0:16:05.600
<v Speaker 1>including Meta. At the end of this year, in two,

0:16:05.640 --> 0:16:08.800
<v Speaker 1>a story that's unfolding as I'm recording this, the European

0:16:08.840 --> 0:16:13.600
<v Speaker 1>Commission launched an antitrust investigation into Meta, specifically over how

0:16:13.640 --> 0:16:18.479
<v Speaker 1>the company handles classified ads on Facebook. So the regulators

0:16:18.480 --> 0:16:22.200
<v Speaker 1>are arguing that Meta gives preferential treatment to its own

0:16:22.320 --> 0:16:27.440
<v Speaker 1>Facebook marketplace classified ads over other types of classified ads

0:16:27.520 --> 0:16:30.680
<v Speaker 1>that could be posted to Facebook. This aligns with a

0:16:30.680 --> 0:16:34.360
<v Speaker 1>similar case against Meta brought by the Competition and Markets Authority,

0:16:34.640 --> 0:16:40.640
<v Speaker 1>which is the regulatory authority in the UK. Similarly, we

0:16:40.680 --> 0:16:45.560
<v Speaker 1>saw more arguments against Apple and also Google's policies of

0:16:45.600 --> 0:16:49.560
<v Speaker 1>taking a cut of all in app purchases made in

0:16:49.680 --> 0:16:54.840
<v Speaker 1>iOS or Android apps, respectively. Now Apple tends to get

0:16:54.880 --> 0:16:59.480
<v Speaker 1>a lot more focus about this, perhaps because until very recently,

0:16:59.720 --> 0:17:05.439
<v Speaker 1>the company was strictly focused on only allowing users to

0:17:05.480 --> 0:17:09.960
<v Speaker 1>download apps through the official Apple App Store, whereas Google

0:17:10.440 --> 0:17:15.560
<v Speaker 1>via Android has allowed sideloading since the very beginning. Uh

0:17:15.640 --> 0:17:18.760
<v Speaker 1>Android sideloading is when you are able to load an

0:17:18.800 --> 0:17:23.119
<v Speaker 1>app that's not in the official app store, and while

0:17:23.160 --> 0:17:26.320
<v Speaker 1>Google makes it possible, the company does warn users that

0:17:26.680 --> 0:17:31.240
<v Speaker 1>this particular ability could lead to problems because you might

0:17:31.359 --> 0:17:35.960
<v Speaker 1>end up downloading an app that is malicious, so there

0:17:36.000 --> 0:17:39.320
<v Speaker 1>are risks involved. But Google says, hey, you're adults, you

0:17:39.359 --> 0:17:43.400
<v Speaker 1>can make these decisions for yourself. Apple says, you know what,

0:17:43.640 --> 0:17:45.159
<v Speaker 1>you don't know what's good for you. We're going to

0:17:45.280 --> 0:17:47.520
<v Speaker 1>prevent that from happening, so you can only get them

0:17:47.520 --> 0:17:50.400
<v Speaker 1>through the app store there too. I'm being a little

0:17:50.400 --> 0:17:52.640
<v Speaker 1>facetious with this, but they are These are two fundamentally

0:17:52.680 --> 0:17:56.320
<v Speaker 1>different approaches to how you allow your customers to get

0:17:56.359 --> 0:17:59.320
<v Speaker 1>access to apps to run your devices. Apple wants a

0:17:59.400 --> 0:18:04.400
<v Speaker 1>much more con trold ecosystem that's not likely to run

0:18:04.400 --> 0:18:09.960
<v Speaker 1>a foul of Apple's other policies and procedures. So at

0:18:10.000 --> 0:18:12.680
<v Speaker 1>the end of two we learned that Apple is now

0:18:12.720 --> 0:18:16.040
<v Speaker 1>preparing to change this policy. It's going to open up

0:18:16.040 --> 0:18:18.960
<v Speaker 1>iOS devices to third party app stores in order to

0:18:19.000 --> 0:18:22.840
<v Speaker 1>be compliant with EUS Digital Markets Act, which I'll talk

0:18:22.880 --> 0:18:25.520
<v Speaker 1>about later in this episode. So this is not going

0:18:25.560 --> 0:18:28.320
<v Speaker 1>to happen immediately, but it should become a reality next year,

0:18:28.359 --> 0:18:31.800
<v Speaker 1>which is a good thing because this particular EU requirement

0:18:32.160 --> 0:18:36.480
<v Speaker 1>will go into effect in T four. Now, you might

0:18:36.520 --> 0:18:39.879
<v Speaker 1>remember that this issue really made headlines. The issue of

0:18:40.000 --> 0:18:43.320
<v Speaker 1>in app payments really made headlines when Epic Games, the

0:18:43.359 --> 0:18:48.200
<v Speaker 1>company behind the massively popular title Fortnite, attempted to circumvent

0:18:48.280 --> 0:18:53.480
<v Speaker 1>Apple's ecosystem by allowing players who play Fortnite on iOS

0:18:53.520 --> 0:18:56.600
<v Speaker 1>devices to kind of have a work around so that

0:18:56.680 --> 0:18:59.280
<v Speaker 1>they can make purchases within the game, but not through

0:18:59.320 --> 0:19:03.879
<v Speaker 1>Apple's official in app payment system. This was back in

0:19:05.080 --> 0:19:07.919
<v Speaker 1>and then you had this massive battle between Apple and

0:19:07.960 --> 0:19:11.320
<v Speaker 1>Epic that stretched into several court cases and lasted more

0:19:11.320 --> 0:19:15.280
<v Speaker 1>than a year. Neither side was totally victorious by the

0:19:15.400 --> 0:19:17.880
<v Speaker 1>end of it, but it's snowballed in. Over the last

0:19:17.880 --> 0:19:20.880
<v Speaker 1>two years, we've seen growing resistance to this in app

0:19:20.920 --> 0:19:25.040
<v Speaker 1>payment policy, though apparently it was news to Elon Musk,

0:19:25.119 --> 0:19:27.320
<v Speaker 1>as he made a big stink over it while pushing

0:19:27.359 --> 0:19:32.360
<v Speaker 1>Twitter's subscription tier Twitter Blue. But we'll talk way more

0:19:32.400 --> 0:19:36.200
<v Speaker 1>about Elon Musk and Twitter in another episode, not this one.

0:19:36.520 --> 0:19:39.200
<v Speaker 1>I just don't have it in me. Plus, there's an

0:19:39.240 --> 0:19:42.879
<v Speaker 1>ongoing story that is unfolding as I'm recording these, so

0:19:43.440 --> 0:19:46.640
<v Speaker 1>I kind of want to see how it turns out anyway.

0:19:46.880 --> 0:19:50.040
<v Speaker 1>To be clear, the issue isn't so much that Apple

0:19:50.080 --> 0:19:53.440
<v Speaker 1>and Google take a cut of every in app transaction.

0:19:53.680 --> 0:19:57.560
<v Speaker 1>That's not really the problem. I mean payment processors as

0:19:57.600 --> 0:20:00.119
<v Speaker 1>a rule take a cut of every transaction. That's how

0:20:00.160 --> 0:20:03.879
<v Speaker 1>they make money. The problem is that Apple and Google

0:20:04.000 --> 0:20:08.919
<v Speaker 1>prevent any alternative in app payment systems on their platforms.

0:20:08.960 --> 0:20:11.320
<v Speaker 1>So the argument is that when there are no alternatives,

0:20:11.359 --> 0:20:14.359
<v Speaker 1>there's no competition. And Apple tried to kind of be

0:20:14.400 --> 0:20:17.760
<v Speaker 1>a little cheeky about this earlier this year and allowed

0:20:18.040 --> 0:20:21.399
<v Speaker 1>some third party payment systems for certain types of apps,

0:20:21.720 --> 0:20:26.360
<v Speaker 1>but they also charged a premium for merchants to use

0:20:26.400 --> 0:20:30.520
<v Speaker 1>these alternatives. So that meant that the app developer would

0:20:30.520 --> 0:20:34.399
<v Speaker 1>actually see even more money diverted away from them and

0:20:34.600 --> 0:20:38.480
<v Speaker 1>to the payment processor and to Apple, and would receive

0:20:38.560 --> 0:20:41.480
<v Speaker 1>even less of every single transaction if they went with

0:20:41.560 --> 0:20:45.080
<v Speaker 1>an alternative to Apples in app payment system. And you

0:20:45.119 --> 0:20:47.600
<v Speaker 1>can bet that move did not go over well. Everyone

0:20:47.640 --> 0:20:50.360
<v Speaker 1>said like, hey, we totally see what you're doing. Apple,

0:20:50.880 --> 0:20:53.400
<v Speaker 1>cut it out now. It will be interesting to see

0:20:53.400 --> 0:20:55.879
<v Speaker 1>how these stories unfold next year. The EU and the

0:20:56.000 --> 0:20:59.399
<v Speaker 1>UK in particular are taking a really tough stance. The

0:20:59.520 --> 0:21:03.520
<v Speaker 1>US also is, but the US has had, like I said,

0:21:03.600 --> 0:21:09.520
<v Speaker 1>decades of being very hands off, very uh almost lassa

0:21:09.640 --> 0:21:14.000
<v Speaker 1>fair about how how companies have been able to conduct

0:21:14.040 --> 0:21:18.560
<v Speaker 1>themselves and to consolidate. So this is like trying to

0:21:18.600 --> 0:21:21.480
<v Speaker 1>act against a lot of momentum that had been building

0:21:21.560 --> 0:21:23.200
<v Speaker 1>up for for years and years and years. In the

0:21:23.240 --> 0:21:26.119
<v Speaker 1>United States, it's a little different here all right. Now,

0:21:26.200 --> 0:21:29.960
<v Speaker 1>let's talk about the Use Digital Services Act and the

0:21:30.040 --> 0:21:34.000
<v Speaker 1>Digital Markets Act. These are two pieces of legislation that

0:21:34.080 --> 0:21:36.760
<v Speaker 1>are shaking things up for tech in general, and both

0:21:36.840 --> 0:21:40.800
<v Speaker 1>of them were put into effect this year, or at

0:21:40.840 --> 0:21:45.000
<v Speaker 1>least enacted this year. The the actual rules end up

0:21:45.000 --> 0:21:49.560
<v Speaker 1>having kind of a rolling effect on when they come

0:21:49.600 --> 0:21:53.359
<v Speaker 1>into full power, so there will be time for the

0:21:53.359 --> 0:21:56.480
<v Speaker 1>tech industry to comply with all the different rules. The

0:21:56.520 --> 0:22:01.080
<v Speaker 1>European Commission to the European Parliament proposed both of legislation

0:22:01.600 --> 0:22:04.960
<v Speaker 1>way back in December, so it wasn't until this year

0:22:05.000 --> 0:22:08.640
<v Speaker 1>that they were both passed into law after receiving lots

0:22:08.640 --> 0:22:11.960
<v Speaker 1>of revisions and tweaks and whatnot. Now, in both cases,

0:22:12.400 --> 0:22:15.439
<v Speaker 1>the acts helped bring into alignment the laws that the

0:22:15.600 --> 0:22:18.800
<v Speaker 1>various member countries of the European Union have had in

0:22:18.880 --> 0:22:23.760
<v Speaker 1>place relating to specific Internet matters. So what the heck

0:22:23.800 --> 0:22:27.480
<v Speaker 1>did these laws say? Well, the Digital Services Act or

0:22:27.600 --> 0:22:32.000
<v Speaker 1>d s A is primarily focused on illegal content on

0:22:32.040 --> 0:22:36.879
<v Speaker 1>the Internet and IT and related issues like content moderation policies.

0:22:37.520 --> 0:22:40.280
<v Speaker 1>Now there are some policies that are going to sound

0:22:40.400 --> 0:22:43.680
<v Speaker 1>very familiar to my fellow Americans. At least, my fellow

0:22:43.720 --> 0:22:46.960
<v Speaker 1>Americans are up to speed on concepts like safe Harbor

0:22:47.080 --> 0:22:51.760
<v Speaker 1>and section to thirty of the Communications Decency Act, namely

0:22:52.560 --> 0:22:57.520
<v Speaker 1>that a platform or an intermediary as the EU calls them,

0:22:57.720 --> 0:23:01.359
<v Speaker 1>is not liable for the content that users post to

0:23:01.520 --> 0:23:05.040
<v Speaker 1>that platform, meaning a platform is not to be held

0:23:05.480 --> 0:23:09.200
<v Speaker 1>as the responsible party for a user posting something illegal

0:23:09.240 --> 0:23:13.280
<v Speaker 1>to that platform. So, for example, if I were to

0:23:13.480 --> 0:23:17.880
<v Speaker 1>post illegal drug information like maybe I'm trying to sell

0:23:18.040 --> 0:23:21.359
<v Speaker 1>drugs on Facebook, and I post that to Facebook in

0:23:21.400 --> 0:23:25.000
<v Speaker 1>the EU, and it's against the law that Facebook would

0:23:25.040 --> 0:23:27.600
<v Speaker 1>not be held accountable for the fact that I did that,

0:23:28.320 --> 0:23:32.760
<v Speaker 1>except that this protection does have strict limits. Namely, once

0:23:32.760 --> 0:23:37.359
<v Speaker 1>a platform becomes aware of the illegal material, it has

0:23:37.400 --> 0:23:42.400
<v Speaker 1>to act to remove that material. Failure to act means

0:23:42.440 --> 0:23:45.040
<v Speaker 1>the platform will be held responsible for allowing the illegal

0:23:45.080 --> 0:23:47.919
<v Speaker 1>material to stay up online and they can face some

0:23:48.160 --> 0:23:53.720
<v Speaker 1>really hefty fines like ten of their overall revenue in

0:23:53.760 --> 0:23:59.200
<v Speaker 1>the EU. That's massive. So also, because the EU is

0:23:59.240 --> 0:24:01.920
<v Speaker 1>applying these rules to sites and services that have more

0:24:01.960 --> 0:24:06.480
<v Speaker 1>than forty five million EU users, it's pretty clear that

0:24:06.520 --> 0:24:11.159
<v Speaker 1>regulators are really aiming this at big tech. This is

0:24:11.960 --> 0:24:14.960
<v Speaker 1>a more strict stance than what we see here in

0:24:15.000 --> 0:24:18.359
<v Speaker 1>the US with Section to thirty of the Communications Decency Act.

0:24:19.080 --> 0:24:22.040
<v Speaker 1>The Digital Services Act also aims to strip away the

0:24:22.080 --> 0:24:25.960
<v Speaker 1>mystery behind how sites and services like Facebook and TikTok

0:24:26.040 --> 0:24:31.399
<v Speaker 1>and YouTube work algorithmically. So essentially, the d s A

0:24:31.520 --> 0:24:35.080
<v Speaker 1>says companies have to be able to explain how their

0:24:35.080 --> 0:24:39.560
<v Speaker 1>recommendation algorithms work and and to do so, you know,

0:24:39.920 --> 0:24:42.879
<v Speaker 1>beyond just hey, it just suggests things that things you'll like.

0:24:43.720 --> 0:24:46.200
<v Speaker 1>So they have to explain how the algorithms pick and

0:24:46.720 --> 0:24:50.479
<v Speaker 1>choose what contents is served up to users. They also

0:24:50.920 --> 0:24:53.679
<v Speaker 1>have to be clear on how the company decides what

0:24:53.920 --> 0:24:58.159
<v Speaker 1>content to remove and when to remove it. So for

0:24:58.359 --> 0:25:02.320
<v Speaker 1>companies that have policies they will remove certain types of material,

0:25:02.359 --> 0:25:04.720
<v Speaker 1>they have to be very transparent in how they make

0:25:04.760 --> 0:25:09.040
<v Speaker 1>these determinations. The d s A requires companies to explain

0:25:09.119 --> 0:25:12.439
<v Speaker 1>how they match advertisers to users, you know, and what

0:25:12.600 --> 0:25:15.639
<v Speaker 1>goes into targeted advertising, what kind of data gets pulled

0:25:15.680 --> 0:25:19.160
<v Speaker 1>and used for that purpose. Now, considering the e use

0:25:19.200 --> 0:25:24.159
<v Speaker 1>protective stance around citizen data in the European Union, I

0:25:24.200 --> 0:25:26.520
<v Speaker 1>suspect that last bit is going to end up shaking

0:25:26.520 --> 0:25:29.800
<v Speaker 1>things up considerably for companies that depend heavily on ad

0:25:29.840 --> 0:25:33.840
<v Speaker 1>revenue like Meta and Google. All right, well, let's switch

0:25:33.880 --> 0:25:37.359
<v Speaker 1>over to the Digital Markets Act or d m A.

0:25:37.880 --> 0:25:40.280
<v Speaker 1>So while the d s A is focused on illegal

0:25:40.359 --> 0:25:44.119
<v Speaker 1>content online, the d m A aims to make e

0:25:44.400 --> 0:25:48.320
<v Speaker 1>commerce more fair and equitable. As such, it is aimed

0:25:48.320 --> 0:25:53.600
<v Speaker 1>to encourage competition and to prevent monopolies and anti competitive practices.

0:25:53.920 --> 0:25:55.679
<v Speaker 1>So the goal of the d m A is to

0:25:55.720 --> 0:25:59.400
<v Speaker 1>put a check on big text so that the larger,

0:25:59.520 --> 0:26:03.200
<v Speaker 1>morris ablished companies can't just push around, or gobble up

0:26:03.320 --> 0:26:08.720
<v Speaker 1>or stamp out smaller companies. Now, considering that several tech

0:26:08.760 --> 0:26:12.920
<v Speaker 1>companies got to where they are largely through numerous acquisitions,

0:26:12.960 --> 0:26:16.560
<v Speaker 1>this could also be a huge blow to certain corporations

0:26:16.560 --> 0:26:19.320
<v Speaker 1>out there. Uh. If you were to search any of

0:26:19.400 --> 0:26:24.320
<v Speaker 1>the Big Tech five and include the word acquisitions or mergers,

0:26:24.800 --> 0:26:28.320
<v Speaker 1>you'd probably end up with a pretty lengthy list. Over

0:26:28.359 --> 0:26:32.119
<v Speaker 1>the years, Meta in particular has a reputation for acquiring

0:26:32.160 --> 0:26:36.320
<v Speaker 1>companies that would otherwise pull attention away from metas platforms.

0:26:36.640 --> 0:26:39.840
<v Speaker 1>The company is known for either buying up potential competitors

0:26:39.920 --> 0:26:43.080
<v Speaker 1>or attempting to copy them in an effort to minimize

0:26:43.200 --> 0:26:47.520
<v Speaker 1>their ability to pull Meta users away to other platforms.

0:26:48.080 --> 0:26:50.679
<v Speaker 1>It is, by no means the only company to follow

0:26:50.680 --> 0:26:55.400
<v Speaker 1>this philosophy, I should add, it's just notorious for doing it.

0:26:55.400 --> 0:26:58.720
<v Speaker 1>It's pretty obvious that Meta is in the crosshairs in

0:26:58.760 --> 0:27:02.359
<v Speaker 1>particular with the d m A. One of the acts

0:27:02.359 --> 0:27:04.760
<v Speaker 1>measures is to make it illegal for any company that

0:27:04.800 --> 0:27:09.000
<v Speaker 1>owns more than one platform from combining data from the

0:27:09.119 --> 0:27:12.240
<v Speaker 1>two or more platforms about the same users. So, in

0:27:12.280 --> 0:27:16.880
<v Speaker 1>other words, if you're Meta and you have users on

0:27:16.920 --> 0:27:20.640
<v Speaker 1>Facebook and on Instagram and they live in the EU,

0:27:20.920 --> 0:27:24.440
<v Speaker 1>you cannot take the data of those users from Facebook

0:27:24.560 --> 0:27:27.720
<v Speaker 1>and the data from those users on Instagram and combine

0:27:27.760 --> 0:27:33.400
<v Speaker 1>them into one big database of information about those specific people. Right.

0:27:33.480 --> 0:27:38.359
<v Speaker 1>You can't combine these sources, and it's likely going to

0:27:38.440 --> 0:27:41.960
<v Speaker 1>cause some technical challenges for some of these companies, which

0:27:42.080 --> 0:27:47.400
<v Speaker 1>presumably have kind of developed into being an enormous data funnel,

0:27:47.480 --> 0:27:50.840
<v Speaker 1>just gobbling up all the information from every outlet and

0:27:50.880 --> 0:27:55.480
<v Speaker 1>combining it into like a a tasty data stew. The

0:27:55.560 --> 0:27:59.520
<v Speaker 1>d m A concerns itself with gatekeepers. These are tech

0:27:59.600 --> 0:28:03.200
<v Speaker 1>company that dominate in one or more areas within the

0:28:03.200 --> 0:28:09.080
<v Speaker 1>tech industry in general. So, for example, Google is indisputably

0:28:09.440 --> 0:28:13.439
<v Speaker 1>the dominant force in Internet search, and as such it

0:28:13.640 --> 0:28:18.000
<v Speaker 1>is a gatekeeper in that respect. Apple is a gatekeeper

0:28:18.080 --> 0:28:23.040
<v Speaker 1>for payment services on iOS. Meta is a gatekeeper for

0:28:23.160 --> 0:28:28.159
<v Speaker 1>social networking. These are the kind of ideas Amazon also

0:28:28.440 --> 0:28:32.040
<v Speaker 1>big gatekeeper for online shopping. So the d m A

0:28:32.200 --> 0:28:36.159
<v Speaker 1>says it is against the rules for any gatekeeper in

0:28:36.520 --> 0:28:40.080
<v Speaker 1>whichever realm of tech they're looking at, to give its

0:28:40.080 --> 0:28:46.040
<v Speaker 1>own services preferential treatment over competitors. Amazon has been accused

0:28:46.080 --> 0:28:49.560
<v Speaker 1>of doing this sort of thing in multiple places around

0:28:49.560 --> 0:28:52.760
<v Speaker 1>the world, in India here in the United States. So

0:28:52.840 --> 0:28:56.760
<v Speaker 1>the accusation is that Amazon tends to promote Amazon owned

0:28:56.920 --> 0:29:02.280
<v Speaker 1>or Amazon affiliated brands over the belonging to competitors. So

0:29:02.560 --> 0:29:05.800
<v Speaker 1>the d m A is saying, hey, you can't do that.

0:29:05.800 --> 0:29:08.120
<v Speaker 1>That's not fair. It would be kind of like if

0:29:08.120 --> 0:29:10.840
<v Speaker 1>you were to go into a grocery store and all

0:29:10.960 --> 0:29:16.000
<v Speaker 1>the store owned products are prominently displayed and they're easy

0:29:16.040 --> 0:29:19.120
<v Speaker 1>to reach, and then all the other brands from anyone

0:29:19.160 --> 0:29:21.680
<v Speaker 1>else are tucked out of the way and they're like

0:29:21.960 --> 0:29:25.520
<v Speaker 1>place really high up on the shelves or whatever. That's

0:29:25.560 --> 0:29:28.640
<v Speaker 1>an unfair practice, and that's what the d m A

0:29:28.840 --> 0:29:31.840
<v Speaker 1>is looking to prevent in the future. The d m

0:29:31.840 --> 0:29:34.280
<v Speaker 1>A and the d s A have a lot more

0:29:34.360 --> 0:29:37.880
<v Speaker 1>in them, but I am probably gonna do full episodes

0:29:37.920 --> 0:29:41.560
<v Speaker 1>about each of them. The important thing for this episode

0:29:41.720 --> 0:29:45.760
<v Speaker 1>is that these two massive pieces of legislation unify the

0:29:46.000 --> 0:29:49.360
<v Speaker 1>use approach to online content and business, and they send

0:29:49.360 --> 0:29:53.000
<v Speaker 1>a message to the big tech companies that they aren't

0:29:53.040 --> 0:29:55.640
<v Speaker 1>going to have quite as much freedom to do whatever

0:29:55.680 --> 0:30:01.040
<v Speaker 1>they please moving forward. Okay, still got some more stories

0:30:01.080 --> 0:30:04.000
<v Speaker 1>to cover before we conclude this particular episode, But first

0:30:04.520 --> 0:30:18.400
<v Speaker 1>let's take another quick break. We're back, and you know what,

0:30:18.440 --> 0:30:20.600
<v Speaker 1>We're still going to talk about the EU. But now

0:30:20.680 --> 0:30:23.080
<v Speaker 1>let's talk about another measure that has forced one of

0:30:23.120 --> 0:30:26.840
<v Speaker 1>the big tech companies to make some pretty significant changes

0:30:26.920 --> 0:30:30.520
<v Speaker 1>in the near future. The European Parliament passed a measure

0:30:30.680 --> 0:30:35.040
<v Speaker 1>that will require all mobile devices, including phones and cameras

0:30:35.080 --> 0:30:38.320
<v Speaker 1>and things like that, to adopt the us B C

0:30:38.800 --> 0:30:42.640
<v Speaker 1>charging port by the end of so In other words,

0:30:42.960 --> 0:30:45.160
<v Speaker 1>if you make a mobile device and you want to

0:30:45.200 --> 0:30:47.840
<v Speaker 1>sell it in the EU, it has to have a

0:30:47.960 --> 0:30:53.280
<v Speaker 1>USBC charging port equipped by It's also going to apply

0:30:53.400 --> 0:30:59.760
<v Speaker 1>to laptop computers. Now, this law passed by overwhelming majority,

0:31:00.080 --> 0:31:04.040
<v Speaker 1>her six hundred and two votes in favor of the measure.

0:31:04.400 --> 0:31:07.880
<v Speaker 1>There were only thirteen votes against it, and then there

0:31:07.880 --> 0:31:11.480
<v Speaker 1>were eight members that abstained from the voting. And this

0:31:11.520 --> 0:31:14.080
<v Speaker 1>measure means that one company in particular has to make

0:31:14.080 --> 0:31:18.400
<v Speaker 1>a big change. In that company is Apple. Now, Apple

0:31:18.480 --> 0:31:22.360
<v Speaker 1>has long leaned on proprietary charging ports and cables for

0:31:22.480 --> 0:31:27.000
<v Speaker 1>many of its products since Apple iPhones as well as

0:31:27.040 --> 0:31:30.400
<v Speaker 1>several other Apple products have used what Apple calls the

0:31:30.600 --> 0:31:35.200
<v Speaker 1>lightning connector. By using a proprietary approach, Apple could achieve

0:31:35.440 --> 0:31:38.960
<v Speaker 1>a few goals. For one, the company could actually design

0:31:39.040 --> 0:31:42.520
<v Speaker 1>ports and cables that had features that the USB standard

0:31:42.720 --> 0:31:47.000
<v Speaker 1>didn't at the time anyway, So that includes the ability

0:31:47.040 --> 0:31:51.280
<v Speaker 1>to plug a lightning cable into a charging port in

0:31:51.320 --> 0:31:54.600
<v Speaker 1>either direction. In other words, there's no right side up

0:31:54.680 --> 0:31:57.840
<v Speaker 1>or anything like that. That's a good thing for consumers.

0:31:57.840 --> 0:32:00.640
<v Speaker 1>It makes it easier to use the the cables. I

0:32:00.680 --> 0:32:04.120
<v Speaker 1>don't know how many times I've had like a USB

0:32:04.200 --> 0:32:07.720
<v Speaker 1>micro or USB Mini cable and I spent the first

0:32:08.120 --> 0:32:10.920
<v Speaker 1>minute trying to figure out if I was trying to

0:32:10.920 --> 0:32:14.360
<v Speaker 1>plug it in upside down or not. So, yeah, plugging

0:32:14.360 --> 0:32:16.560
<v Speaker 1>an older USB cables can be kind of a pain.

0:32:16.640 --> 0:32:19.600
<v Speaker 1>So this was a good thing. But Apple had other

0:32:19.640 --> 0:32:23.280
<v Speaker 1>reasons for doing this approach. Whether we're a lot more

0:32:23.320 --> 0:32:27.240
<v Speaker 1>self serving. So a proprietary approach gives Apple more control

0:32:27.280 --> 0:32:31.000
<v Speaker 1>over the supply chain, right and any company that wanted

0:32:31.000 --> 0:32:33.960
<v Speaker 1>to make its own lightning cables would have to pay

0:32:34.000 --> 0:32:36.400
<v Speaker 1>Apple a licensing fee in order to do it, so,

0:32:36.440 --> 0:32:41.160
<v Speaker 1>in other words, locking down the ecosystem created revenue streams

0:32:41.360 --> 0:32:44.360
<v Speaker 1>for Apple. You couldn't just go and buy a generic

0:32:44.480 --> 0:32:47.719
<v Speaker 1>lightning cable and Apple gets no cut. Apple would get

0:32:47.760 --> 0:32:49.840
<v Speaker 1>a cut no matter what, whether it came from Apple

0:32:50.440 --> 0:32:51.960
<v Speaker 1>or it came from a company that was paying a

0:32:52.040 --> 0:32:55.960
<v Speaker 1>licensing fee to Apple. Now it might be more convenient

0:32:56.000 --> 0:33:00.160
<v Speaker 1>for Apple users if their tech worked with industry standard cables,

0:33:00.240 --> 0:33:01.920
<v Speaker 1>right like if it worked with the same cables that

0:33:01.960 --> 0:33:04.720
<v Speaker 1>everything else works with. But that would mean Apple would

0:33:04.760 --> 0:33:08.360
<v Speaker 1>be leaving money on the table. So Apple had resisted

0:33:08.360 --> 0:33:11.920
<v Speaker 1>this for quite some time. Let the use regulations now

0:33:11.920 --> 0:33:15.120
<v Speaker 1>require Apple to play ball. The EU regulators said that

0:33:15.160 --> 0:33:18.200
<v Speaker 1>by adopting the standard, there will be a reduction of

0:33:18.320 --> 0:33:23.560
<v Speaker 1>E waste. People won't need to keep different incompatible cables

0:33:23.600 --> 0:33:26.800
<v Speaker 1>in like a junk drawer, and then when one cable

0:33:26.800 --> 0:33:28.560
<v Speaker 1>wears out, they have to go and hunt for the

0:33:28.680 --> 0:33:32.320
<v Speaker 1>right one in order to have a replacement. Now they'll

0:33:32.320 --> 0:33:35.280
<v Speaker 1>be able to grab any USBC cable they happen to have,

0:33:35.840 --> 0:33:39.240
<v Speaker 1>and that will work just fine. Apple has said that

0:33:39.280 --> 0:33:41.960
<v Speaker 1>forcing the company to adopt the standard is going to

0:33:42.040 --> 0:33:45.560
<v Speaker 1>hurt consumers, But I don't think that very many people

0:33:45.640 --> 0:33:49.560
<v Speaker 1>took those arguments seriously. And so Apple looks like it's

0:33:49.560 --> 0:33:52.480
<v Speaker 1>going to conform to the US wishes, which also means

0:33:52.920 --> 0:33:56.560
<v Speaker 1>that we will likely see the same thing happen worldwide,

0:33:57.040 --> 0:33:59.200
<v Speaker 1>though who knows. Maybe Apple will try to keep two

0:33:59.200 --> 0:34:02.600
<v Speaker 1>separate line some products going where it keeps the lightning

0:34:02.640 --> 0:34:07.000
<v Speaker 1>port everywhere else and it just does USBC for the EU.

0:34:07.440 --> 0:34:10.360
<v Speaker 1>We'll have to see. I don't think that would happen,

0:34:10.440 --> 0:34:13.600
<v Speaker 1>just because I would imagine that that really complicates the

0:34:13.640 --> 0:34:17.480
<v Speaker 1>supply chain and the manufacturing process, and it's just easier

0:34:17.520 --> 0:34:21.040
<v Speaker 1>to adopt it worldwide. But we'll have to see. Okay,

0:34:21.120 --> 0:34:26.240
<v Speaker 1>let's talk about another technological battle between government agencies and

0:34:26.440 --> 0:34:30.080
<v Speaker 1>industries and tech companies. And this time, really we're looking

0:34:30.120 --> 0:34:33.080
<v Speaker 1>at two tech industries that are in a battle with

0:34:33.120 --> 0:34:37.279
<v Speaker 1>one another. That would be the telecommunications industry and the

0:34:37.360 --> 0:34:42.000
<v Speaker 1>aviation industry. So the United States Federal Aviation Administration or

0:34:42.120 --> 0:34:45.680
<v Speaker 1>f a A is involved in this as well. Now,

0:34:46.080 --> 0:34:50.920
<v Speaker 1>this all has to do with five G wireless communication,

0:34:51.080 --> 0:34:55.160
<v Speaker 1>and this requires a bit of explanation. First of all,

0:34:55.239 --> 0:34:59.680
<v Speaker 1>let's demystify five G for a second. It's very easy

0:35:00.000 --> 0:35:03.280
<v Speaker 1>to refer to five G as being this super fast

0:35:03.400 --> 0:35:09.200
<v Speaker 1>wireless internet connectivity solution, but really that's kind of misleading.

0:35:09.480 --> 0:35:13.440
<v Speaker 1>For one thing, we're not so much talking about data speed,

0:35:13.480 --> 0:35:16.560
<v Speaker 1>we're talking about bandwidth. So in other words, it's not

0:35:16.640 --> 0:35:20.200
<v Speaker 1>how fast the zeros and ones are zooming around. Rather,

0:35:20.320 --> 0:35:23.319
<v Speaker 1>it's how many zeros and ones can zoom around at

0:35:23.360 --> 0:35:26.480
<v Speaker 1>the same time and be accepted by your device or

0:35:26.520 --> 0:35:31.080
<v Speaker 1>sent from your device. There's also the matter of latency,

0:35:31.320 --> 0:35:35.719
<v Speaker 1>that's the delay between an action and its reaction. Now,

0:35:35.760 --> 0:35:39.440
<v Speaker 1>you want latency to be really low for certain operations. Actually,

0:35:39.480 --> 0:35:42.040
<v Speaker 1>really you typically want latency to be low for everything

0:35:42.080 --> 0:35:46.360
<v Speaker 1>because we've really grown impatient. We hate watching delays. But

0:35:46.840 --> 0:35:50.759
<v Speaker 1>some operations low latency is absolutely critical, and one of

0:35:50.800 --> 0:35:55.319
<v Speaker 1>five G s promises is a reduction in latency. But

0:35:56.280 --> 0:35:59.799
<v Speaker 1>five G itself actually comes in a few different flavors.

0:36:00.239 --> 0:36:03.960
<v Speaker 1>To be more accurate, there are a few different frequency

0:36:04.080 --> 0:36:08.719
<v Speaker 1>bands within the electromagnetic spectrum that are called five G,

0:36:09.440 --> 0:36:14.040
<v Speaker 1>and at the lower frequencies, five G isn't super duper fast,

0:36:14.200 --> 0:36:19.000
<v Speaker 1>or rather doesn't have this enormous bandwidth, but it can

0:36:19.120 --> 0:36:22.840
<v Speaker 1>work over long distances, has a longer transmission range. Not

0:36:23.080 --> 0:36:28.600
<v Speaker 1>the highest of five GS frequencies. You've got incredible bandwidth,

0:36:29.160 --> 0:36:32.560
<v Speaker 1>but you have a very short range of transmission. Plus

0:36:33.280 --> 0:36:37.080
<v Speaker 1>at the very high frequencies, the waves have trouble penetrating

0:36:37.120 --> 0:36:40.440
<v Speaker 1>solid surfaces. So if there happens to be a wall

0:36:40.560 --> 0:36:43.239
<v Speaker 1>or a ceiling or something like that between you and

0:36:43.280 --> 0:36:46.360
<v Speaker 1>the transmitter, you're not going to be able to enjoy

0:36:46.360 --> 0:36:51.799
<v Speaker 1>those fibro light connections on your device through that particular transmitter. Now,

0:36:51.840 --> 0:36:54.040
<v Speaker 1>the reason I say all this is because the marketing

0:36:54.040 --> 0:36:57.400
<v Speaker 1>of five G can leave out some of these details,

0:36:57.480 --> 0:37:00.120
<v Speaker 1>and so the basic consumer might expect to have an

0:37:00.200 --> 0:37:05.080
<v Speaker 1>incredible wireless connection on their five G device, but in reality,

0:37:05.239 --> 0:37:07.760
<v Speaker 1>when they actually use their device, they find the speed

0:37:07.800 --> 0:37:12.920
<v Speaker 1>that they're enjoying isn't necessarily that much more impressive than

0:37:12.960 --> 0:37:16.319
<v Speaker 1>what they had with LTE. But anyway, not all five

0:37:16.400 --> 0:37:20.080
<v Speaker 1>G is equal. That's kind of what I'm getting at now.

0:37:20.320 --> 0:37:23.480
<v Speaker 1>The bit about five G that's important for this story

0:37:23.760 --> 0:37:27.920
<v Speaker 1>is that high power, high frequency five G has the

0:37:27.920 --> 0:37:33.320
<v Speaker 1>potential to interfere with specific older aviation equipment, in particular

0:37:34.040 --> 0:37:38.480
<v Speaker 1>radio altimeters. These are used by aircraft to determine altitude,

0:37:38.840 --> 0:37:42.839
<v Speaker 1>in other words, how far from the ground the plane is,

0:37:43.440 --> 0:37:47.600
<v Speaker 1>and as you can imagine, that data is pretty darn important,

0:37:47.640 --> 0:37:53.600
<v Speaker 1>particularly for takeoffs and landings in low visibility situations specifically,

0:37:53.920 --> 0:37:56.520
<v Speaker 1>so pilots kind of need to know how close they

0:37:56.520 --> 0:37:59.840
<v Speaker 1>are to the ground in those situations. So then you

0:38:00.040 --> 0:38:03.000
<v Speaker 1>have the us f a A, which is looking out

0:38:03.040 --> 0:38:06.279
<v Speaker 1>for airlines and airports and such, essentially looking up for

0:38:06.320 --> 0:38:09.239
<v Speaker 1>the aviation industry. Then on the other side, you had

0:38:09.280 --> 0:38:12.320
<v Speaker 1>the telecommunications companies like A, T and T and Verizon.

0:38:12.719 --> 0:38:17.800
<v Speaker 1>They were looking to expand five G C band services

0:38:17.840 --> 0:38:22.399
<v Speaker 1>across the country, including in areas that are around airports,

0:38:22.840 --> 0:38:26.719
<v Speaker 1>and that's where you get our initial conflict. You had

0:38:26.800 --> 0:38:29.839
<v Speaker 1>the telecommunications companies that were looking to tap into more

0:38:29.920 --> 0:38:34.200
<v Speaker 1>customers selling them five G services, and you had the

0:38:34.280 --> 0:38:37.920
<v Speaker 1>airline industry concerned that these services could potentially interfere in

0:38:38.000 --> 0:38:42.480
<v Speaker 1>aircraft operations. Now, the solution to this problem is actually

0:38:43.000 --> 0:38:49.600
<v Speaker 1>fairly straightforward. Aircraft need a retrofit to shield radio altimeters

0:38:50.000 --> 0:38:54.080
<v Speaker 1>from five G interference. Essentially, they need to swap out apart.

0:38:54.360 --> 0:38:57.000
<v Speaker 1>They need the old radio altimeters to be pulled out

0:38:57.520 --> 0:39:00.160
<v Speaker 1>and new and improved radio altimeters that are resist sent

0:39:00.280 --> 0:39:04.040
<v Speaker 1>to this kind of interference to be installed. That's the solution.

0:39:04.640 --> 0:39:08.600
<v Speaker 1>So it's literally about updating equipment to avoid the problem.

0:39:08.680 --> 0:39:12.279
<v Speaker 1>But here's the thing. That equipment is wicked expensive. We're

0:39:12.320 --> 0:39:16.440
<v Speaker 1>talking like twenty grand per instance. And then when you

0:39:16.480 --> 0:39:20.319
<v Speaker 1>think about the fleets of aircraft across different airlines or

0:39:20.680 --> 0:39:24.239
<v Speaker 1>the number of aircraft that specific companies like Boeing sell,

0:39:25.360 --> 0:39:29.280
<v Speaker 1>that mounts up really quickly. So there was another matter

0:39:29.360 --> 0:39:32.880
<v Speaker 1>that needed to be settled. Who is going to pay

0:39:32.960 --> 0:39:36.480
<v Speaker 1>for it? Now? As you can imagine, neither the aviation

0:39:36.560 --> 0:39:41.080
<v Speaker 1>industry nor the telecommunications industry wanted to be responsible for

0:39:41.160 --> 0:39:43.160
<v Speaker 1>holding the bag when it came time to pay for

0:39:43.200 --> 0:39:47.120
<v Speaker 1>these upgrades. The telecommunications industry was like, hey, this is

0:39:47.160 --> 0:39:50.560
<v Speaker 1>your technology, it's your responsibility to do the upgrades. The

0:39:50.600 --> 0:39:54.360
<v Speaker 1>aviation industry was like, hey, we wouldn't need to upgrade

0:39:54.400 --> 0:39:58.080
<v Speaker 1>if you didn't start blasting interference near airports, so you

0:39:58.120 --> 0:40:01.799
<v Speaker 1>should pay for the changes and early. That's what this

0:40:02.200 --> 0:40:05.640
<v Speaker 1>mostly boiled down to. So there was this kind of

0:40:05.680 --> 0:40:10.400
<v Speaker 1>standoff between the telecommunications companies that were putting into place

0:40:10.520 --> 0:40:13.920
<v Speaker 1>plans to launch these five G services around airports, and

0:40:13.920 --> 0:40:17.239
<v Speaker 1>then you had the aviation industry that was saying, hey,

0:40:17.280 --> 0:40:19.840
<v Speaker 1>if you do that, you're going to cause delays and worse,

0:40:19.880 --> 0:40:22.600
<v Speaker 1>and it will be on your head. It was kind

0:40:22.640 --> 0:40:25.080
<v Speaker 1>of like they were playing chicken with each other, and

0:40:25.160 --> 0:40:27.359
<v Speaker 1>once you understood what was going on, it got a

0:40:27.440 --> 0:40:33.200
<v Speaker 1>little frustrating. In January of twenty two, the telecommunications companies

0:40:33.320 --> 0:40:36.719
<v Speaker 1>reduced the transmission power of five G towers that were

0:40:36.760 --> 0:40:40.399
<v Speaker 1>near certain very busy airports in the United States. This

0:40:40.480 --> 0:40:44.399
<v Speaker 1>was a concession to avoid safety problems, particularly in low

0:40:44.480 --> 0:40:49.200
<v Speaker 1>visibility situations. While everyone started to work on a more

0:40:49.280 --> 0:40:53.440
<v Speaker 1>permanent solution, the deployment of five G around airports in

0:40:53.480 --> 0:40:57.480
<v Speaker 1>certain markets has been on hold in the meantime. This

0:40:57.640 --> 0:41:02.440
<v Speaker 1>also has an impact on some populations that typically are

0:41:02.560 --> 0:41:07.640
<v Speaker 1>underserved or sometimes unserved, because a lot of the neighborhoods

0:41:07.640 --> 0:41:10.719
<v Speaker 1>around airports tend to be for you know, lower income

0:41:10.920 --> 0:41:14.000
<v Speaker 1>areas of cities, and so part of the argument is

0:41:14.040 --> 0:41:18.160
<v Speaker 1>that by delaying this, it is hurting those populations who

0:41:18.239 --> 0:41:20.680
<v Speaker 1>don't have access to the technology they need in order

0:41:20.680 --> 0:41:24.480
<v Speaker 1>to be connected productive members of society, which, you know,

0:41:24.560 --> 0:41:28.920
<v Speaker 1>there's some validity to that argument. Things are supposed to

0:41:29.000 --> 0:41:32.040
<v Speaker 1>be on track next year, because that's when A. T

0:41:32.160 --> 0:41:36.440
<v Speaker 1>and T and Verizon are gonna lift their self imposed

0:41:36.440 --> 0:41:40.960
<v Speaker 1>restrictions that they've placed on themselves in order to you know,

0:41:41.440 --> 0:41:45.880
<v Speaker 1>comply with the needs of the aviation industry, but recently

0:41:45.960 --> 0:41:51.320
<v Speaker 1>Boeing asked federal regulators to delay that to to essentially

0:41:51.360 --> 0:41:54.560
<v Speaker 1>force A ten too and Verizon to hold off on

0:41:54.760 --> 0:41:58.600
<v Speaker 1>rolling those technologies out because they still need more time

0:41:58.760 --> 0:42:01.839
<v Speaker 1>to upgrade systems on planes to make sure that they

0:42:01.840 --> 0:42:05.640
<v Speaker 1>are resistant to five G interference. So this is an

0:42:05.680 --> 0:42:11.760
<v Speaker 1>ongoing struggle. Interestingly, meanwhile, in the EU, there are plans

0:42:11.760 --> 0:42:15.359
<v Speaker 1>to allow passengers to use five G devices while they're

0:42:15.360 --> 0:42:18.920
<v Speaker 1>actually on a flight. So here in the States the

0:42:19.000 --> 0:42:22.359
<v Speaker 1>issue involves five G cell towers near airports. Like, we're

0:42:22.360 --> 0:42:25.480
<v Speaker 1>not even talking about people in airplanes right now, we're

0:42:25.480 --> 0:42:31.160
<v Speaker 1>talking about the actual physical infrastructure around airports. Meanwhile, in

0:42:31.239 --> 0:42:34.319
<v Speaker 1>the EU, next year, passengers will be able to use

0:42:34.360 --> 0:42:37.719
<v Speaker 1>their cellular phones while flying through the air. And you

0:42:37.800 --> 0:42:40.480
<v Speaker 1>might wonder what makes it safe to do that in

0:42:40.520 --> 0:42:44.040
<v Speaker 1>the EU, But it's unsafe in the United States. And

0:42:44.080 --> 0:42:46.160
<v Speaker 1>a big part of that hearkens back to what I

0:42:46.200 --> 0:42:49.640
<v Speaker 1>said earlier about there being different flavors of five G

0:42:50.160 --> 0:42:52.640
<v Speaker 1>in the United States. The matter is about the so

0:42:52.719 --> 0:42:56.560
<v Speaker 1>called C band of five G frequencies, these higher frequency,

0:42:56.640 --> 0:43:01.720
<v Speaker 1>higher power UH transmissions than what you find in the EU.

0:43:02.760 --> 0:43:06.840
<v Speaker 1>The EU uses lower five G frequencies than what we

0:43:06.920 --> 0:43:11.000
<v Speaker 1>see around the United States, so it's not an Apple's

0:43:11.040 --> 0:43:15.080
<v Speaker 1>Apples thing. Five G is not five G depending upon

0:43:15.120 --> 0:43:17.160
<v Speaker 1>where you are, or at least it's not the same

0:43:17.200 --> 0:43:21.160
<v Speaker 1>five G. Now, all that being said, I'm not sure

0:43:21.200 --> 0:43:23.480
<v Speaker 1>the average person is going to get great reception on

0:43:23.600 --> 0:43:26.239
<v Speaker 1>flights in the EU, even if they are allowed to

0:43:26.360 --> 0:43:30.439
<v Speaker 1>use five G devices. Cell towers have a limited transmission range.

0:43:30.840 --> 0:43:32.880
<v Speaker 1>This is why we need a lot of cell towers,

0:43:33.120 --> 0:43:35.759
<v Speaker 1>because what happens is one cell tower will hand off

0:43:35.800 --> 0:43:38.680
<v Speaker 1>service to the next, So as you move toward the

0:43:38.880 --> 0:43:43.319
<v Speaker 1>edge of cell tower a's range of service, it can

0:43:43.400 --> 0:43:46.400
<v Speaker 1>hand you off to cell tower B and your service

0:43:46.520 --> 0:43:48.920
<v Speaker 1>isn't interrupted. But when you're way up in the sky,

0:43:49.040 --> 0:43:52.720
<v Speaker 1>there's a distinct shortage of cellular towers around you, so

0:43:53.320 --> 0:43:56.640
<v Speaker 1>you might not be able to get any signal anyway

0:43:56.719 --> 0:43:59.280
<v Speaker 1>because you'll be at too high in altitude to do it.

0:43:59.280 --> 0:44:02.040
<v Speaker 1>It would be passe sable to actually outfit planes with

0:44:02.520 --> 0:44:06.439
<v Speaker 1>pico cell towers, essentially these tiny little cell towers, and

0:44:06.520 --> 0:44:09.480
<v Speaker 1>they would be able to cover the range of the

0:44:09.840 --> 0:44:13.319
<v Speaker 1>aircraft with cell signals and then it would beam a

0:44:13.400 --> 0:44:19.080
<v Speaker 1>concentrated data stream at terrestrial towers on the ground, but

0:44:19.160 --> 0:44:22.640
<v Speaker 1>that would require even more equipment updates to planes, and

0:44:22.680 --> 0:44:26.239
<v Speaker 1>we're seeing how that's going so far. So all right,

0:44:26.560 --> 0:44:29.160
<v Speaker 1>that is enough for this first episode about some of

0:44:29.160 --> 0:44:33.920
<v Speaker 1>the big tech stories of two, and we're just getting started.

0:44:34.000 --> 0:44:36.360
<v Speaker 1>We're gonna have a bunch more of these episodes because

0:44:36.880 --> 0:44:40.080
<v Speaker 1>there's so much to talk about. I mean, Elon Musk

0:44:40.120 --> 0:44:42.160
<v Speaker 1>and Twitter alone, I have a feeling is going to

0:44:42.239 --> 0:44:45.279
<v Speaker 1>be at least half an episode. We'll see. I don't

0:44:45.280 --> 0:44:47.960
<v Speaker 1>know how much my tolerance can handle at this point

0:44:48.320 --> 0:44:51.560
<v Speaker 1>because it's been such a crazy story this whole year,

0:44:51.719 --> 0:44:55.640
<v Speaker 1>and that's the story that's currently unfolding as I record this.

0:44:55.920 --> 0:44:57.759
<v Speaker 1>We're all waiting to find out if Elon Musk is

0:44:57.760 --> 0:45:00.160
<v Speaker 1>actually going to step down as CEO, because he all

0:45:00.160 --> 0:45:04.560
<v Speaker 1>the poll about it and asked his his followers should

0:45:04.560 --> 0:45:07.200
<v Speaker 1>he step down or not, and the majority said yes

0:45:07.239 --> 0:45:11.759
<v Speaker 1>you should. So we're waiting to hear what that amounts to.

0:45:12.239 --> 0:45:16.200
<v Speaker 1>I'm sure i'll talk about that and later on this week. Anyway,

0:45:16.239 --> 0:45:19.840
<v Speaker 1>I hope you're all well. I hope your two was

0:45:19.880 --> 0:45:23.560
<v Speaker 1>a good one. I hope three is even better, and

0:45:23.600 --> 0:45:33.960
<v Speaker 1>I'll talk to you again really soon. Tech stuff is

0:45:33.960 --> 0:45:37.239
<v Speaker 1>an i heart Radio production. For more podcasts from my

0:45:37.400 --> 0:45:41.000
<v Speaker 1>heart Radio, visit the i heart Radio app, Apple Podcasts,

0:45:41.120 --> 0:45:43.080
<v Speaker 1>or wherever you listen to your favorite shows.