WEBVTT - What the Tech Happened? Part One 

0:00:04.480 --> 0:00:12.520
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.520 --> 0:00:16.160
<v Speaker 1>and welcome to tech Stuff. I'm your host, jonvan Strickland.

0:00:16.160 --> 0:00:19.560
<v Speaker 1>I'm an executive producer with iHeart Podcasts and How the

0:00:19.720 --> 0:00:24.439
<v Speaker 1>Tech Are you. Welcome to my last Friday as the

0:00:24.560 --> 0:00:28.120
<v Speaker 1>host of tech Stuff. You've almost made it. I've almost

0:00:28.120 --> 0:00:31.000
<v Speaker 1>made it. It's really exciting. I thought it could be

0:00:31.080 --> 0:00:35.040
<v Speaker 1>fun to look back on kind of like a big

0:00:35.200 --> 0:00:39.120
<v Speaker 1>tech story from each year since I've been a host

0:00:39.320 --> 0:00:43.040
<v Speaker 1>of tech Stuff. So that's from mid two thousand and

0:00:43.080 --> 0:00:47.000
<v Speaker 1>eight to this year or this past year twenty twenty four.

0:00:47.200 --> 0:00:49.280
<v Speaker 1>It's weird for me to say this past year because

0:00:49.280 --> 0:00:52.160
<v Speaker 1>I'm actually putting this together when it has not yet

0:00:52.320 --> 0:00:56.080
<v Speaker 1>turned to twenty twenty five. I also figured this would

0:00:56.080 --> 0:00:58.000
<v Speaker 1>take up a couple of episodes because I'm a chatty

0:00:58.080 --> 0:01:00.120
<v Speaker 1>Cathy and a lot has gone on since mid two

0:01:00.160 --> 0:01:02.720
<v Speaker 1>thousand and eight. So this is part one, and in

0:01:02.760 --> 0:01:06.000
<v Speaker 1>part two we will pick up and continue on. That's

0:01:07.120 --> 0:01:10.399
<v Speaker 1>how parts work now. To be clear, the entries I

0:01:10.480 --> 0:01:14.520
<v Speaker 1>submit to you, these are not necessarily the biggest or

0:01:14.560 --> 0:01:17.920
<v Speaker 1>even the most important techt stories of each year. Instead,

0:01:17.920 --> 0:01:21.160
<v Speaker 1>it's a story I picked for whatever capricious reason. Entered

0:01:21.160 --> 0:01:24.440
<v Speaker 1>into my head as I was looking back over everything

0:01:24.480 --> 0:01:27.000
<v Speaker 1>that's happened over the last sixteen and a half years

0:01:27.000 --> 0:01:30.400
<v Speaker 1>in the world of tech. So we started off tech

0:01:30.440 --> 0:01:33.720
<v Speaker 1>Stuff in early June of two thousand and eight. For

0:01:33.760 --> 0:01:36.200
<v Speaker 1>that reason, I went to look at the back half

0:01:36.280 --> 0:01:38.679
<v Speaker 1>of two thousand and eight for the tech story to

0:01:38.680 --> 0:01:42.319
<v Speaker 1>talk about, So I ignored anything that happened up until June.

0:01:42.760 --> 0:01:47.960
<v Speaker 1>And that brings us to Apple launching the iPhone app Store. Now,

0:01:48.000 --> 0:01:51.000
<v Speaker 1>the iPhone had come out the year before, but the

0:01:51.040 --> 0:01:55.040
<v Speaker 1>app store would end up becoming a thing one month

0:01:55.240 --> 0:01:58.559
<v Speaker 1>after we started tech Stuff in July of two thousand

0:01:58.600 --> 0:02:01.280
<v Speaker 1>and eight. That's when that app store came online. Now,

0:02:01.280 --> 0:02:04.920
<v Speaker 1>before that, iPhone users had to be content with the

0:02:04.960 --> 0:02:08.000
<v Speaker 1>apps that Apple made available on the iPhone that were

0:02:08.000 --> 0:02:12.320
<v Speaker 1>preloaded on the device. Third party choices were not actually

0:02:12.360 --> 0:02:16.600
<v Speaker 1>an option yet. Apple had spent a year, well more

0:02:16.639 --> 0:02:19.080
<v Speaker 1>than a year technically, but a year since the iPhone

0:02:19.120 --> 0:02:23.360
<v Speaker 1>had come out, just coming up with a way to

0:02:23.400 --> 0:02:25.919
<v Speaker 1>create an app store, Like, what was the strategy there?

0:02:25.960 --> 0:02:27.960
<v Speaker 1>They didn't want it to just be a fire hose

0:02:28.600 --> 0:02:32.120
<v Speaker 1>of content because then the store would get flooded with

0:02:32.400 --> 0:02:36.000
<v Speaker 1>all sorts of apps, many of which would be pretty terrible.

0:02:36.680 --> 0:02:41.000
<v Speaker 1>So their plan included a vetting process for apps, and

0:02:41.160 --> 0:02:43.920
<v Speaker 1>at the best of times, this process was rather opaque

0:02:43.960 --> 0:02:48.000
<v Speaker 1>and obtuse. Sometimes a developer could get an app approved

0:02:48.040 --> 0:02:51.040
<v Speaker 1>and in the store right away without any real revisions.

0:02:51.160 --> 0:02:55.000
<v Speaker 1>Other times developers would get pushedback from Apple and they

0:02:55.040 --> 0:02:57.640
<v Speaker 1>would have to tweak their apps for one reason or another,

0:02:58.520 --> 0:03:01.600
<v Speaker 1>and that was not always clear, like it wasn't always

0:03:02.280 --> 0:03:06.359
<v Speaker 1>apparent why one app would be accepted and another app

0:03:06.440 --> 0:03:10.320
<v Speaker 1>rejected when they were, at least on the surface, very

0:03:10.360 --> 0:03:13.040
<v Speaker 1>similar to one another. So it raised a lot of

0:03:13.160 --> 0:03:17.160
<v Speaker 1>questions and confusion. And because Apple didn't allow for side loading,

0:03:17.440 --> 0:03:21.320
<v Speaker 1>which is when users can install apps from outside an

0:03:21.360 --> 0:03:25.639
<v Speaker 1>official app store, this meant that developers had no alternative

0:03:25.639 --> 0:03:29.240
<v Speaker 1>pathway to get to their customer base. It was either

0:03:29.400 --> 0:03:33.240
<v Speaker 1>played by Apple's rules or get shut out entirely. Now,

0:03:33.280 --> 0:03:37.040
<v Speaker 1>the app store would have a huge impact on tech

0:03:37.120 --> 0:03:39.560
<v Speaker 1>and how we interact with it, which is putting it lightly.

0:03:40.080 --> 0:03:42.720
<v Speaker 1>Not to mention it would help propel Apple's revenue into

0:03:42.760 --> 0:03:45.680
<v Speaker 1>the stratosphere. The company would take a chunk out of

0:03:45.800 --> 0:03:49.480
<v Speaker 1>every purchase made through an app. Now that could also

0:03:49.560 --> 0:03:52.760
<v Speaker 1>include if the app was one where customers had to

0:03:52.760 --> 0:03:55.080
<v Speaker 1>pay to download the app, like if it wasn't a

0:03:55.080 --> 0:03:58.200
<v Speaker 1>free app, if it costs five or ten bucks or whatever,

0:03:58.880 --> 0:04:01.560
<v Speaker 1>Apple got a chunk that, But they also got a

0:04:01.640 --> 0:04:05.160
<v Speaker 1>percentage of all in app purchasing options, assuming it wasn't

0:04:05.160 --> 0:04:08.440
<v Speaker 1>an app like ordering a physical thing, like if you

0:04:08.480 --> 0:04:11.120
<v Speaker 1>were using an app to order food from a restaurant,

0:04:11.200 --> 0:04:13.560
<v Speaker 1>Apple wouldn't get a chunk of that. But if you

0:04:13.560 --> 0:04:15.960
<v Speaker 1>were using an app and the app had features that

0:04:16.000 --> 0:04:18.960
<v Speaker 1>were locked behind a paywall and you paid to get

0:04:18.960 --> 0:04:22.040
<v Speaker 1>to those features, Apple got a cut. So developers were

0:04:22.080 --> 0:04:25.800
<v Speaker 1>obliged to use Apple's own payment processing features, they couldn't

0:04:25.800 --> 0:04:28.719
<v Speaker 1>introduce their own, and Apple took, like I said, a

0:04:28.720 --> 0:04:31.120
<v Speaker 1>percentage with every transaction. And it was that sort of

0:04:31.160 --> 0:04:34.279
<v Speaker 1>policy that would eventually land Apple in hot water with

0:04:34.400 --> 0:04:37.680
<v Speaker 1>antitrust regulators who would argue that the company was using

0:04:37.720 --> 0:04:41.800
<v Speaker 1>its dominant position to deny competition in the space. And

0:04:41.839 --> 0:04:44.560
<v Speaker 1>that's something that still plays out to this day, Like

0:04:44.720 --> 0:04:48.480
<v Speaker 1>there's still court cases going on that go one way

0:04:48.560 --> 0:04:51.200
<v Speaker 1>or the other. Some have been kind of an Apple's favor,

0:04:51.400 --> 0:04:55.479
<v Speaker 1>some have been against, but it's an ongoing thing. But

0:04:55.600 --> 0:04:57.400
<v Speaker 1>on top of all that, the app store would bring

0:04:57.440 --> 0:05:00.640
<v Speaker 1>about an era in which everyone and their doll began

0:05:00.680 --> 0:05:04.120
<v Speaker 1>to develop apps for the web content creators out there.

0:05:04.400 --> 0:05:06.919
<v Speaker 1>This became a real headache because it wasn't enough to

0:05:07.080 --> 0:05:09.719
<v Speaker 1>just optimize your website so that it would look good

0:05:09.760 --> 0:05:13.360
<v Speaker 1>on mobile devices. That was absolutely a necessity, because trends

0:05:13.400 --> 0:05:15.479
<v Speaker 1>were showing that more people were starting to rely on

0:05:15.560 --> 0:05:19.120
<v Speaker 1>mobile devices to access the web every single year, but

0:05:19.279 --> 0:05:22.480
<v Speaker 1>you also had to go and make your own bespoke app,

0:05:22.560 --> 0:05:26.720
<v Speaker 1>or at least that that was the philosophy. Countless apps followed.

0:05:27.080 --> 0:05:29.640
<v Speaker 1>Some of these would stand the test of time, but

0:05:29.760 --> 0:05:32.520
<v Speaker 1>a lot of them ultimately withered and died. I am

0:05:32.600 --> 0:05:35.240
<v Speaker 1>reminded of the house Stuff Works app, which we actually

0:05:35.279 --> 0:05:37.760
<v Speaker 1>mentioned in a recent episode when I had the boys

0:05:37.800 --> 0:05:39.679
<v Speaker 1>of Stuff They Don't Want You to Know on the show.

0:05:40.240 --> 0:05:43.400
<v Speaker 1>The House Stuff Works app served up articles and quizzes

0:05:43.400 --> 0:05:46.279
<v Speaker 1>and such to users, but it was tough to convince

0:05:46.279 --> 0:05:48.280
<v Speaker 1>people to download it. I mean, a lot of folks

0:05:48.320 --> 0:05:51.560
<v Speaker 1>would just go to how Stuff Works if Google pointed

0:05:51.600 --> 0:05:53.719
<v Speaker 1>them that way when they had the question about something.

0:05:54.400 --> 0:05:58.200
<v Speaker 1>And it was also really tough to monetize apps. Optimizing

0:05:58.279 --> 0:06:01.240
<v Speaker 1>articles to display in an app meant that you might

0:06:01.320 --> 0:06:04.240
<v Speaker 1>have to issue advertising, So like, if they went to

0:06:04.279 --> 0:06:06.600
<v Speaker 1>the web version of the article, they would get the

0:06:06.640 --> 0:06:09.159
<v Speaker 1>ads and you would get the impressions and that would

0:06:09.160 --> 0:06:11.719
<v Speaker 1>count against whatever the ad deal was. But if it

0:06:11.760 --> 0:06:15.040
<v Speaker 1>was an app, you might not get that. And ads

0:06:15.080 --> 0:06:17.479
<v Speaker 1>were a top revenue driver for a lot of companies,

0:06:17.480 --> 0:06:21.920
<v Speaker 1>including How Stuff Works. So how do you both serve

0:06:22.040 --> 0:06:25.480
<v Speaker 1>content up to people in a streamlined way via an

0:06:25.520 --> 0:06:28.480
<v Speaker 1>app and how do you make money off of that

0:06:29.000 --> 0:06:31.200
<v Speaker 1>as its sponsorships? As that what? A lot of people

0:06:31.279 --> 0:06:34.320
<v Speaker 1>hadn't figured that out, and a lot of other outlets

0:06:34.400 --> 0:06:37.240
<v Speaker 1>encountered similar issues to what we saw How Stuff Works.

0:06:37.440 --> 0:06:40.480
<v Speaker 1>For a while, apps were seen as a possible lifeline

0:06:40.480 --> 0:06:44.640
<v Speaker 1>for content companies that were struggling with the old business model.

0:06:44.880 --> 0:06:48.360
<v Speaker 1>You know, maybe you could convince people to subscribe through

0:06:48.400 --> 0:06:52.000
<v Speaker 1>an app and put content behind a paywall. That would

0:06:52.040 --> 0:06:54.520
<v Speaker 1>help push back against the myriad of ways content could

0:06:54.520 --> 0:06:58.359
<v Speaker 1>be shared outside of just visiting the website itself. Sure,

0:06:58.440 --> 0:07:01.880
<v Speaker 1>stuff like social media could let you find more readers,

0:07:02.160 --> 0:07:05.640
<v Speaker 1>so a lot of content companies embrace social media early on,

0:07:06.920 --> 0:07:10.080
<v Speaker 1>But then people started just skimming content through social media

0:07:10.160 --> 0:07:13.480
<v Speaker 1>and never bothered to click through to visit the home website,

0:07:13.680 --> 0:07:17.920
<v Speaker 1>which meant again, you weren't actually monetizing any of that traffic.

0:07:18.080 --> 0:07:20.800
<v Speaker 1>All the traffic was going to the social network, not

0:07:20.960 --> 0:07:24.280
<v Speaker 1>to you. Anyway, the App store made a truly huge

0:07:24.400 --> 0:07:28.600
<v Speaker 1>change on the tech sector. Entire companies built around apps

0:07:28.640 --> 0:07:33.200
<v Speaker 1>were made possible by Apple's move. And while Google would

0:07:33.280 --> 0:07:36.640
<v Speaker 1>launch the Android operating system in two thousand and eight,

0:07:37.080 --> 0:07:39.600
<v Speaker 1>I don't think even the most hardcore Android fan out

0:07:39.600 --> 0:07:41.320
<v Speaker 1>there would be able to stay with a straight face

0:07:41.360 --> 0:07:43.840
<v Speaker 1>that Google would have accomplished the same thing that Apple

0:07:43.920 --> 0:07:47.920
<v Speaker 1>managed to do. Google did some great things and continues

0:07:47.960 --> 0:07:49.680
<v Speaker 1>to do some great things along with some not so

0:07:49.760 --> 0:07:53.000
<v Speaker 1>great things. But honestly, without Apple, I don't think that

0:07:53.040 --> 0:07:56.240
<v Speaker 1>this ecosystem really takes off. Now, let us move on

0:07:56.280 --> 0:07:58.480
<v Speaker 1>to two thousand and nine, and we've got a whole

0:07:58.560 --> 0:08:00.840
<v Speaker 1>year to play with this time, just half a year.

0:08:00.920 --> 0:08:03.560
<v Speaker 1>So what tech story caught my eye? Well, there were

0:08:03.600 --> 0:08:06.440
<v Speaker 1>a couple of contenders. One is a very sad one.

0:08:06.760 --> 0:08:10.200
<v Speaker 1>Steve Jobs's health was in serious decline. And whatever you

0:08:10.280 --> 0:08:12.880
<v Speaker 1>might have thought of Steve Jobs as a person or

0:08:12.920 --> 0:08:17.840
<v Speaker 1>a boss, still hard to talk about someone's health deteriorating,

0:08:18.160 --> 0:08:21.920
<v Speaker 1>at least it is for me. And journalists were swarming

0:08:21.960 --> 0:08:23.680
<v Speaker 1>to find out the truth of what was going on

0:08:23.760 --> 0:08:27.280
<v Speaker 1>with Steve Jobs, which was kind of achy. He initially

0:08:27.280 --> 0:08:30.960
<v Speaker 1>said he was experiencing a quote unquote hormonal imbalance, but

0:08:31.000 --> 0:08:33.920
<v Speaker 1>it later turned out that he had secretly had a

0:08:34.000 --> 0:08:37.600
<v Speaker 1>liver transplant, and part of me is frustrated that he

0:08:37.679 --> 0:08:40.280
<v Speaker 1>actually had to deal with journalists who were prying at

0:08:40.360 --> 0:08:43.400
<v Speaker 1>his personal life at all. But then I also understand

0:08:43.440 --> 0:08:46.120
<v Speaker 1>that since he was CEO of Apple at the time,

0:08:46.880 --> 0:08:50.120
<v Speaker 1>there were reasons people needed to know about his health

0:08:50.480 --> 0:08:54.600
<v Speaker 1>because if his well being impacted the company, well that's

0:08:54.600 --> 0:08:58.280
<v Speaker 1>a huge thing, and it impacts thousands of other people.

0:08:58.720 --> 0:09:00.480
<v Speaker 1>So I guess that's one of the trade offs you

0:09:00.520 --> 0:09:02.000
<v Speaker 1>have to accept when you become the head of a

0:09:02.040 --> 0:09:06.000
<v Speaker 1>supremely profitable company. And obviously, while his health was big

0:09:06.000 --> 0:09:08.760
<v Speaker 1>news in two thousand and nine, his passing two years

0:09:08.840 --> 0:09:12.480
<v Speaker 1>later would eclipse that. Another big story in two thousand

0:09:12.520 --> 0:09:15.440
<v Speaker 1>and nine was that Microsoft released Windows seven, which would

0:09:15.480 --> 0:09:17.720
<v Speaker 1>go on to be one of the more popular versions

0:09:17.760 --> 0:09:21.600
<v Speaker 1>of the operating system. Microsoft has had an inconsistent track

0:09:21.679 --> 0:09:25.839
<v Speaker 1>record in that regard. People loved Windows XP, but they

0:09:25.840 --> 0:09:29.760
<v Speaker 1>weren't fans of Vista. For example. People liked Windows seven,

0:09:30.280 --> 0:09:33.439
<v Speaker 1>but they wouldn't very much care for Windows eight and

0:09:33.520 --> 0:09:36.240
<v Speaker 1>so on. But I feel the story I should really

0:09:36.280 --> 0:09:39.479
<v Speaker 1>touch on is that in two thousand and nine, Facebook

0:09:39.520 --> 0:09:43.440
<v Speaker 1>officially passed MySpace as far as the number of visitors

0:09:43.559 --> 0:09:47.760
<v Speaker 1>going to each site per month within the United States

0:09:48.160 --> 0:09:51.280
<v Speaker 1>is concerned. It is wild to me that tech Stuff

0:09:51.400 --> 0:09:55.320
<v Speaker 1>was around back when MySpace wasn't just a thing, it

0:09:55.360 --> 0:09:58.079
<v Speaker 1>was the dominant thing in the social network space here

0:09:58.120 --> 0:10:00.400
<v Speaker 1>in the States. Of course, by the time time tech

0:10:00.400 --> 0:10:03.320
<v Speaker 1>Stuff got started, MySpace was already getting into trouble and

0:10:03.440 --> 0:10:06.160
<v Speaker 1>Facebook's star was on the rise. In fact, if we

0:10:06.200 --> 0:10:10.680
<v Speaker 1>look at global numbers, Facebook had already surpassed MySpace in

0:10:10.800 --> 0:10:14.400
<v Speaker 1>unique visitors worldwide back in April two thousand and eight,

0:10:14.400 --> 0:10:17.200
<v Speaker 1>which was a couple of months before tech Stuff even launched. But,

0:10:17.280 --> 0:10:19.960
<v Speaker 1>as I'm sure you all know, here in the United States,

0:10:19.960 --> 0:10:23.520
<v Speaker 1>folks essentially behave as though nothing matters unless it happens here.

0:10:24.040 --> 0:10:26.160
<v Speaker 1>I'm not saying that's right. In fact, I'm saying it's

0:10:26.160 --> 0:10:29.040
<v Speaker 1>outright myopic and dumb, but it's still how a lot

0:10:29.120 --> 0:10:32.280
<v Speaker 1>of people behave here in the United States. So the

0:10:32.320 --> 0:10:36.520
<v Speaker 1>trajectory Facebook was on would propel the company to incredible

0:10:36.520 --> 0:10:40.560
<v Speaker 1>heights as well as set itself up for scrutiny and criticism.

0:10:40.880 --> 0:10:44.280
<v Speaker 1>In two thousand and nine, Facebook changed its terms of use.

0:10:44.640 --> 0:10:47.480
<v Speaker 1>The new terms had a concerning clause in them that read,

0:10:47.600 --> 0:10:49.040
<v Speaker 1>and this is a long one, but I'm going to

0:10:49.080 --> 0:10:54.880
<v Speaker 1>quote it. Quote you here. By grant Facebook and irrevocable, perpetual,

0:10:55.240 --> 0:11:00.480
<v Speaker 1>non exclusive, transferable, fully paid worldwide license would right to

0:11:00.600 --> 0:11:06.520
<v Speaker 1>sub license to a use, copy, publish, stream, store, retain, publicly,

0:11:06.559 --> 0:11:14.160
<v Speaker 1>perform or display, transmit, scan, reformat, modify, edit, frame, translate, excerpt, adapt,

0:11:14.440 --> 0:11:19.040
<v Speaker 1>create derivative works, and distribute through multiple tiers. Any user

0:11:19.120 --> 0:11:23.760
<v Speaker 1>content you lowercase I post on or in connection with

0:11:23.800 --> 0:11:27.000
<v Speaker 1>the Facebook service or the promotion thereof, subject only to

0:11:27.080 --> 0:11:32.000
<v Speaker 1>your privacy settings. Or I enable a user to post,

0:11:32.160 --> 0:11:35.160
<v Speaker 1>including by offering a share link on your website, and

0:11:35.480 --> 0:11:38.720
<v Speaker 1>lowercase B to use your name, likeness, and image for

0:11:38.800 --> 0:11:43.000
<v Speaker 1>any purpose, including commercial or advertising, each of lowercase A

0:11:43.760 --> 0:11:47.320
<v Speaker 1>and lowercase B on or in connection with the Facebook

0:11:47.360 --> 0:11:52.760
<v Speaker 1>service or the promotion thereof. End quote. Whew, Okay, that's

0:11:52.800 --> 0:11:55.160
<v Speaker 1>a mouthful. I should have just said the headline of

0:11:55.320 --> 0:11:58.920
<v Speaker 1>the consumerist piece about this particular change, which was quote

0:11:59.000 --> 0:12:01.760
<v Speaker 1>Facebook's new term of service. We can do anything we

0:12:01.800 --> 0:12:05.200
<v Speaker 1>want with your content forever. End quote. It's actually it's

0:12:05.240 --> 0:12:08.600
<v Speaker 1>a great article. So there was a pretty swift and

0:12:08.640 --> 0:12:12.960
<v Speaker 1>negative reaction to this policy change, understandably, and ultimately Facebook

0:12:13.000 --> 0:12:16.720
<v Speaker 1>walked it back, putting up changes to vote among the

0:12:16.800 --> 0:12:18.840
<v Speaker 1>user base, saying, hey, you should be able to have

0:12:18.840 --> 0:12:20.679
<v Speaker 1>a say in this because it's going to impact you,

0:12:21.320 --> 0:12:24.960
<v Speaker 1>and a very tiny percentage of users actually bothered to vote,

0:12:25.240 --> 0:12:29.319
<v Speaker 1>but critics applauded Facebook's move to at least take user

0:12:29.360 --> 0:12:33.880
<v Speaker 1>concerns into consideration. The honeymoon would not last very long, however.

0:12:34.200 --> 0:12:37.160
<v Speaker 1>In twenty ten, Zuckerberg would claim that privacy was no

0:12:37.280 --> 0:12:40.040
<v Speaker 1>longer a social norm, which I infer as a blanket

0:12:40.080 --> 0:12:42.560
<v Speaker 1>excuse for Facebook to collect as much data from as

0:12:42.600 --> 0:12:45.880
<v Speaker 1>many people and profit as much as possible. And obviously,

0:12:46.120 --> 0:12:48.800
<v Speaker 1>in later years, Facebook would be held accountable for all

0:12:48.840 --> 0:12:52.439
<v Speaker 1>sorts of problems it caused or facilitated. But yeah, two

0:12:52.480 --> 0:12:54.520
<v Speaker 1>thousand and nine is a good year to point to

0:12:54.559 --> 0:12:59.000
<v Speaker 1>and say, here's where Facebook's journey to becoming a huge company,

0:12:59.360 --> 0:13:04.319
<v Speaker 1>one of the big five in tech really began. Okay,

0:13:04.360 --> 0:13:06.920
<v Speaker 1>we're up to twenty ten. That's the year we'd get

0:13:06.960 --> 0:13:09.760
<v Speaker 1>the iPad, which I thought would be a flop because

0:13:09.760 --> 0:13:11.840
<v Speaker 1>no one had managed to make a tablet computer a

0:13:11.960 --> 0:13:15.560
<v Speaker 1>viable consumer product up to that point. It's also the

0:13:15.640 --> 0:13:19.760
<v Speaker 1>year of Antennagate. You might not remember Antennagate because we've

0:13:19.760 --> 0:13:23.280
<v Speaker 1>had so many iPhones since then, but Antennagate was when

0:13:23.320 --> 0:13:26.400
<v Speaker 1>folks were complaining about connectivity issues with the brand new

0:13:26.559 --> 0:13:31.520
<v Speaker 1>iPhone four, and upon closer inspection, it looked like the

0:13:31.559 --> 0:13:35.960
<v Speaker 1>issue was the internal antenna of the iPhone was placed

0:13:35.960 --> 0:13:37.840
<v Speaker 1>in such a way that if you held the phone

0:13:37.920 --> 0:13:40.320
<v Speaker 1>like you know, like a human being holding a phone,

0:13:40.679 --> 0:13:44.000
<v Speaker 1>you could end up blocking the antenna from getting a

0:13:44.000 --> 0:13:48.160
<v Speaker 1>solid signal. And we were all essentially told, you're holding

0:13:48.160 --> 0:13:52.440
<v Speaker 1>it wrong. Thus, Apple pushed the blame onto consumers rather

0:13:52.520 --> 0:13:54.600
<v Speaker 1>than owning up to the fact that the iPhone four

0:13:54.679 --> 0:13:57.520
<v Speaker 1>had a design flaw. But the story that really jumped

0:13:57.520 --> 0:14:00.360
<v Speaker 1>out at me in twenty ten was that the world

0:14:00.600 --> 0:14:05.200
<v Speaker 1>learned of stucks net at stux and e T that

0:14:05.360 --> 0:14:09.240
<v Speaker 1>was malware designed for a very specific purpose, specifically to

0:14:09.320 --> 0:14:14.480
<v Speaker 1>sabotage nuclear centrifuges that were part of Iran's nuclear program.

0:14:14.960 --> 0:14:18.560
<v Speaker 1>So in order to create a uranium based nuclear power plant,

0:14:18.720 --> 0:14:22.920
<v Speaker 1>or indeed a uranium based nuclear weapon, you first have

0:14:23.040 --> 0:14:25.880
<v Speaker 1>to get hold of the right kind of uranium, which

0:14:25.920 --> 0:14:30.360
<v Speaker 1>is the isotope U two thirty five. Trouble is, that

0:14:30.520 --> 0:14:33.080
<v Speaker 1>is really rare stuff. It makes up less than a

0:14:33.120 --> 0:14:36.880
<v Speaker 1>percentage of the uranium we actually mind like zero point

0:14:36.960 --> 0:14:41.000
<v Speaker 1>seven percent. But you need a concentration somewhere between three

0:14:41.080 --> 0:14:43.760
<v Speaker 1>to five percent of uranium two thirty five in your

0:14:43.920 --> 0:14:47.800
<v Speaker 1>uranium mix to have viable material. So we have to

0:14:48.200 --> 0:14:51.520
<v Speaker 1>enrich the uranium. We have to get the right concentration.

0:14:52.000 --> 0:14:55.600
<v Speaker 1>Part of that process typically involves using centrifuges to separate

0:14:55.680 --> 0:15:00.160
<v Speaker 1>out you two thirty five from you know, the other stuff. Well,

0:15:00.160 --> 0:15:02.240
<v Speaker 1>the stucks Neat virus would do a few things. One

0:15:02.280 --> 0:15:04.480
<v Speaker 1>thing it would do is that it hit itself once

0:15:04.520 --> 0:15:06.840
<v Speaker 1>it was installed in a target computer, so that you

0:15:06.880 --> 0:15:10.360
<v Speaker 1>couldn't easily see that malware was on the device. These

0:15:10.360 --> 0:15:13.520
<v Speaker 1>particular computers were not connected to the Internet, a very

0:15:13.560 --> 0:15:16.800
<v Speaker 1>wise decision. They had what we would call an air gap,

0:15:17.160 --> 0:15:20.040
<v Speaker 1>as in no connectivity to an outside network. So in

0:15:20.120 --> 0:15:21.680
<v Speaker 1>order to get the virus on the computer in the

0:15:21.680 --> 0:15:24.560
<v Speaker 1>first place, the malware makers would put this code on

0:15:24.720 --> 0:15:28.320
<v Speaker 1>USB drives like little thumb drives, and then they tricked

0:15:28.400 --> 0:15:31.880
<v Speaker 1>Iranian plant workers to install the malware on these air

0:15:31.960 --> 0:15:37.760
<v Speaker 1>gapped machines, so human beings mostly unknowingly carried this and

0:15:38.200 --> 0:15:41.560
<v Speaker 1>ended up installing them on the computers. The code would

0:15:41.600 --> 0:15:46.720
<v Speaker 1>send commands to centrifuges and cause the centrifuges to rotate

0:15:46.760 --> 0:15:49.200
<v Speaker 1>faster than what they were rated for, and the intent

0:15:49.320 --> 0:15:53.600
<v Speaker 1>was to break the machinery and sabotage e Iron's nuclear program,

0:15:53.720 --> 0:15:55.840
<v Speaker 1>and it worked. This was not your run of the

0:15:55.840 --> 0:15:59.400
<v Speaker 1>mill hacker attack. Of course. While it's never been officially acknowledged,

0:15:59.400 --> 0:16:02.000
<v Speaker 1>at least as far as I know, the generally accepted

0:16:02.040 --> 0:16:05.320
<v Speaker 1>stories that Israel and the United States collaborated on this

0:16:05.360 --> 0:16:08.960
<v Speaker 1>attack for several years before deploying it, and it made

0:16:09.000 --> 0:16:11.600
<v Speaker 1>history by being the first major malware attack connected with

0:16:11.800 --> 0:16:15.560
<v Speaker 1>industrial sabotage. That's a heck of a story for twenty ten.

0:16:16.280 --> 0:16:18.080
<v Speaker 1>We got a lot more, but it's time for us

0:16:18.080 --> 0:16:30.880
<v Speaker 1>to take a quick break to thank our sponsors. We're

0:16:31.040 --> 0:16:34.640
<v Speaker 1>back and now we're moving on to twenty eleven. Now.

0:16:34.720 --> 0:16:37.680
<v Speaker 1>As I mentioned earlier in this episode, twenty eleven was

0:16:37.760 --> 0:16:41.120
<v Speaker 1>the year that Steve Jobs passed away. By the time

0:16:41.120 --> 0:16:44.080
<v Speaker 1>of his passing, Tim Cook was acting as the new

0:16:44.200 --> 0:16:47.040
<v Speaker 1>CEO of Apple. That's a position he holds to this

0:16:47.200 --> 0:16:51.440
<v Speaker 1>very day. And obviously Steve Jobs's passing was huge news.

0:16:51.480 --> 0:16:55.120
<v Speaker 1>Like the tech news cycle and really the mainstream news

0:16:55.160 --> 0:16:59.520
<v Speaker 1>cycle was dominated by that at the time, Steve Jobs

0:16:59.720 --> 0:17:02.360
<v Speaker 1>was kind of he was the face of Apple like

0:17:02.400 --> 0:17:04.280
<v Speaker 1>he was the guy who was a co founder of

0:17:04.320 --> 0:17:08.960
<v Speaker 1>the company. He famously was banished from the company in

0:17:09.000 --> 0:17:13.359
<v Speaker 1>the early mid eighties, left Apple, went and did his

0:17:13.400 --> 0:17:16.000
<v Speaker 1>own thing for a while, came back to Apple as

0:17:16.119 --> 0:17:21.520
<v Speaker 1>a consultant in the mid to late nineties, eventually reassumed

0:17:21.560 --> 0:17:24.919
<v Speaker 1>control of Apple, turned it around from a company that

0:17:25.000 --> 0:17:29.040
<v Speaker 1>was on the brink of potentially bankruptcy it was doing

0:17:29.080 --> 0:17:32.760
<v Speaker 1>so poorly to becoming one of the most successful tech

0:17:32.840 --> 0:17:37.760
<v Speaker 1>companies in the world, propelled by successes like the iMac

0:17:37.880 --> 0:17:40.760
<v Speaker 1>and the iPod and of course, later on the iPhone,

0:17:41.200 --> 0:17:44.359
<v Speaker 1>largely helped by Johnny Ive, the incredible designer who helped

0:17:44.400 --> 0:17:47.639
<v Speaker 1>create the new look of Apple Like. It is a

0:17:47.680 --> 0:17:50.400
<v Speaker 1>huge story that he passed away. He was also famous

0:17:50.440 --> 0:17:53.840
<v Speaker 1>for being a really tough boss and sometimes a really

0:17:53.920 --> 0:17:59.480
<v Speaker 1>really unkind boss. There are some pretty scary stories about

0:17:59.560 --> 0:18:03.920
<v Speaker 1>encounter between employees and Steve Jobs. But while his passing

0:18:04.040 --> 0:18:07.920
<v Speaker 1>was huge, news that wasn't the story I really wanted

0:18:07.960 --> 0:18:10.760
<v Speaker 1>to focus on. Another big one that unfolded in twenty

0:18:10.800 --> 0:18:13.840
<v Speaker 1>eleven was how protesters and countries across the Middle East

0:18:14.160 --> 0:18:17.440
<v Speaker 1>took to social media to argue for massive social changes

0:18:18.119 --> 0:18:21.320
<v Speaker 1>that technically actually started in late twenty ten, but the

0:18:21.359 --> 0:18:25.000
<v Speaker 1>majority of the activity was really spread across twenty eleven.

0:18:25.480 --> 0:18:29.360
<v Speaker 1>This became known as the Arab Spring, and there were,

0:18:29.800 --> 0:18:33.199
<v Speaker 1>you know, variable degrees of success for social change throughout

0:18:33.400 --> 0:18:36.800
<v Speaker 1>the nations that were part of the Arab Spring. But

0:18:36.880 --> 0:18:41.320
<v Speaker 1>what that really did was it highlighted how important platforms

0:18:42.080 --> 0:18:45.320
<v Speaker 1>like Twitter and other social networks at the time really

0:18:45.400 --> 0:18:48.080
<v Speaker 1>are for the purposes of social change. Like we can

0:18:48.119 --> 0:18:50.919
<v Speaker 1>forget that because we often will, or at least I

0:18:51.000 --> 0:18:54.639
<v Speaker 1>will forget that because I will often focus on things

0:18:54.640 --> 0:18:57.479
<v Speaker 1>that are happening, like at the corporate level, where the

0:18:57.480 --> 0:19:01.080
<v Speaker 1>people in charge of those platforms are making questionable decisions

0:19:01.160 --> 0:19:04.879
<v Speaker 1>or ones that I find ethically troubling, but the people

0:19:04.920 --> 0:19:08.639
<v Speaker 1>actually using the platforms can often do so in ways

0:19:08.680 --> 0:19:15.040
<v Speaker 1>that evoke positive social change. Also twenty eleven, Google launched

0:19:15.040 --> 0:19:18.240
<v Speaker 1>Google Plus that year, but that network had shut down

0:19:18.280 --> 0:19:20.960
<v Speaker 1>by twenty nineteen, so it barely merits mentioned it was

0:19:21.040 --> 0:19:24.920
<v Speaker 1>just Google making another attempt to creating a social network

0:19:25.080 --> 0:19:28.719
<v Speaker 1>similar to that of Facebook or MySpace before it, and

0:19:28.800 --> 0:19:34.280
<v Speaker 1>Google just never really nailed that. They tried several times,

0:19:34.359 --> 0:19:37.000
<v Speaker 1>and I'm sure they'll try again at some point, but

0:19:37.160 --> 0:19:40.040
<v Speaker 1>it is just never stuck. Now, the story I really

0:19:40.040 --> 0:19:42.840
<v Speaker 1>wanted to focus on is one that, at least on

0:19:42.880 --> 0:19:45.240
<v Speaker 1>the face of it, seems like more of a novelty

0:19:45.520 --> 0:19:48.080
<v Speaker 1>and not that important. But I argue it is important,

0:19:48.520 --> 0:19:53.000
<v Speaker 1>and that is IBM's Watson AI computer famously took on

0:19:53.200 --> 0:19:58.399
<v Speaker 1>two returning Jeopardy champions the game show Jeopardy in a

0:19:58.440 --> 0:20:01.760
<v Speaker 1>display of natural language process sing an artificial intelligence powered

0:20:01.840 --> 0:20:07.600
<v Speaker 1>problem solving. So Watson played against Ken Jennings and Brad Rudder,

0:20:07.680 --> 0:20:10.919
<v Speaker 1>to former champions on Jeopardy. They played a game of

0:20:11.000 --> 0:20:13.720
<v Speaker 1>Jeopardy and Watson came out the winner. Watson was able

0:20:13.760 --> 0:20:18.520
<v Speaker 1>to navigate clues that incorporated wordplay and you know, references

0:20:18.560 --> 0:20:21.440
<v Speaker 1>and pop culture and history, all without having an external

0:20:21.440 --> 0:20:24.639
<v Speaker 1>connection to the Internet. So Watson did have access to

0:20:24.680 --> 0:20:27.840
<v Speaker 1>a rather massive database of information that was connected to

0:20:27.880 --> 0:20:30.719
<v Speaker 1>the computer, but it could not you know, dial out

0:20:30.840 --> 0:20:35.440
<v Speaker 1>of the studio for example, to get information from the Internet. Itself.

0:20:35.800 --> 0:20:39.520
<v Speaker 1>Watson essentially would buzz in if it calculated that the

0:20:39.560 --> 0:20:43.960
<v Speaker 1>probability of its answer being the right answer was above

0:20:44.000 --> 0:20:47.720
<v Speaker 1>a certain threshold. And that's interesting too, writ Like, it's

0:20:47.720 --> 0:20:50.600
<v Speaker 1>not that it quote unquote knew the right answer. It

0:20:50.680 --> 0:20:54.080
<v Speaker 1>had an answer. It would analyze the likelihood of that

0:20:54.119 --> 0:20:56.920
<v Speaker 1>answer being the correct one, and if the likelihood were

0:20:56.960 --> 0:21:00.359
<v Speaker 1>high enough, Watson would buzz in. Now, the reason I

0:21:00.400 --> 0:21:02.840
<v Speaker 1>bring it up here is not because a machine beat

0:21:02.920 --> 0:21:06.200
<v Speaker 1>humans in a game, because that's a story we've heard

0:21:06.359 --> 0:21:09.880
<v Speaker 1>many times, like the famous one being Gary Kasparov when

0:21:09.960 --> 0:21:14.920
<v Speaker 1>he faced off against IBM's Deep Blue in various chess matches.

0:21:15.960 --> 0:21:17.960
<v Speaker 1>IBM has a long history of doing this kind of

0:21:17.960 --> 0:21:21.280
<v Speaker 1>stuff too. Instead, the reason I wanted to talk about

0:21:21.280 --> 0:21:23.480
<v Speaker 1>it is because in twenty eleven we would get a

0:21:23.600 --> 0:21:28.439
<v Speaker 1>hint of where artificial intelligence, particularly AI that has natural

0:21:28.520 --> 0:21:33.000
<v Speaker 1>language processing capabilities, would be headed. I would say that

0:21:33.080 --> 0:21:37.159
<v Speaker 1>today's generative AI resembles Watson in many ways that we

0:21:37.280 --> 0:21:40.880
<v Speaker 1>do have to remember that artificial intelligence isn't always right

0:21:41.040 --> 0:21:45.240
<v Speaker 1>or trustworthy. So just as a reminder, you know, this year,

0:21:45.280 --> 0:21:48.280
<v Speaker 1>this past year, back in twenty twenty four, I gotta

0:21:48.280 --> 0:21:50.960
<v Speaker 1>say twenty twenty four. I'm recording in twenty twenty four.

0:21:51.720 --> 0:21:56.120
<v Speaker 1>But I once had AI quote unquote write an episode

0:21:56.160 --> 0:21:59.200
<v Speaker 1>of tech Stuff, and then I did kind of director's

0:21:59.240 --> 0:22:03.920
<v Speaker 1>commentary on that. I suppose the AI ended up inventing

0:22:04.080 --> 0:22:09.000
<v Speaker 1>supposed experts who didn't actually exist and was quoting them

0:22:09.320 --> 0:22:13.400
<v Speaker 1>as support for the arguments being made in the episode.

0:22:13.840 --> 0:22:17.200
<v Speaker 1>And that's just not cool. I mean, like any any

0:22:17.359 --> 0:22:20.600
<v Speaker 1>teacher could tell you if you are if your students

0:22:20.640 --> 0:22:25.240
<v Speaker 1>are rating essays and they're quoting made up experts, that's

0:22:25.520 --> 0:22:27.919
<v Speaker 1>unethical and it's going to get you a failing grade.

0:22:27.920 --> 0:22:30.720
<v Speaker 1>But AI was doing it when I asked it to

0:22:30.760 --> 0:22:34.920
<v Speaker 1>create an episode. That's not great. But let's now move

0:22:35.000 --> 0:22:40.840
<v Speaker 1>on to two thy twelve. Microsoft pushed Windows eight out

0:22:40.920 --> 0:22:43.960
<v Speaker 1>the door. It was redesigned to work in a world

0:22:44.200 --> 0:22:47.480
<v Speaker 1>that was now filling up with touch screens. But while

0:22:47.480 --> 0:22:51.920
<v Speaker 1>the touch screen layout may have, you know, really made

0:22:51.960 --> 0:22:55.560
<v Speaker 1>sense for people who are on mobile devices, those who

0:22:55.600 --> 0:22:59.160
<v Speaker 1>are still working on laptops and desktops were less enchanted

0:22:59.200 --> 0:23:03.600
<v Speaker 1>by that user interface. Lots of people preferred sticking with

0:23:03.680 --> 0:23:06.359
<v Speaker 1>Windows seven, even though there was a version of Windows

0:23:06.359 --> 0:23:11.400
<v Speaker 1>eight you could activate that was less tile based. That's

0:23:11.440 --> 0:23:15.639
<v Speaker 1>what Windows eight called the various little icons that you

0:23:15.680 --> 0:23:19.080
<v Speaker 1>would navigate through the UI. So this was kind of

0:23:19.080 --> 0:23:22.240
<v Speaker 1>another case of Windows Vista all over again, where people

0:23:22.880 --> 0:23:27.639
<v Speaker 1>largely rejected the advancements that Microsoft had made and whether

0:23:28.040 --> 0:23:31.720
<v Speaker 1>those advancements actually made sense or not. Users didn't like them,

0:23:32.280 --> 0:23:37.240
<v Speaker 1>and so there was a resistance to adopting Windows eight

0:23:37.359 --> 0:23:40.800
<v Speaker 1>in large part because of these issues I just mentioned.

0:23:41.800 --> 0:23:46.479
<v Speaker 1>Apple also introduced Apple Maps that year. Apple Maps quickly

0:23:46.560 --> 0:23:50.120
<v Speaker 1>became the subject of ridicule. You might not remember this

0:23:50.240 --> 0:23:53.399
<v Speaker 1>because it's sense gotten much better, but when it was

0:23:53.400 --> 0:23:57.800
<v Speaker 1>first released, Apple Maps was pretty bad. Users noted several

0:23:57.840 --> 0:24:00.520
<v Speaker 1>deficiencies in the mapping features, you know, like guiding you

0:24:00.600 --> 0:24:04.280
<v Speaker 1>to the wrong location or suggesting that you take a

0:24:04.359 --> 0:24:08.200
<v Speaker 1>river instead of the highway. In all seriousness, it was bad.

0:24:08.720 --> 0:24:10.560
<v Speaker 1>Maybe it wasn't like the worst thing in the world,

0:24:10.560 --> 0:24:12.919
<v Speaker 1>but it was bad enough that Tim Cook was actually

0:24:12.920 --> 0:24:16.000
<v Speaker 1>prompted to apologize for it. That's not a good look.

0:24:16.040 --> 0:24:18.720
<v Speaker 1>That's not something that Apple would typically do. I don't

0:24:18.760 --> 0:24:22.280
<v Speaker 1>know that Steve Jobs would have done that, even with

0:24:22.440 --> 0:24:25.480
<v Speaker 1>the negative reaction that there was to Apple Maps. He

0:24:25.560 --> 0:24:27.879
<v Speaker 1>might have said, you know, we were too enthusiastic and

0:24:27.920 --> 0:24:29.679
<v Speaker 1>we released it too early, but I'm not sure he

0:24:29.680 --> 0:24:34.200
<v Speaker 1>would apologize. No way of knowing. But no, the story

0:24:34.240 --> 0:24:38.359
<v Speaker 1>I want to talk about is about Marissa Meyer. So

0:24:38.760 --> 0:24:41.320
<v Speaker 1>she was one of the early employees at Google. She

0:24:41.400 --> 0:24:46.200
<v Speaker 1>was actually employee number twenty way back in nineteen ninety nine.

0:24:46.480 --> 0:24:50.640
<v Speaker 1>But in twenty twelve she had a huge career change.

0:24:50.680 --> 0:24:54.560
<v Speaker 1>She left Google behind and became the president and CEO

0:24:54.800 --> 0:24:57.400
<v Speaker 1>of Yahoo. She also scored a seat on the board

0:24:57.400 --> 0:25:01.879
<v Speaker 1>of directors in the process. Old stomping grounds of Google

0:25:01.960 --> 0:25:05.040
<v Speaker 1>had been kind of stomping on Yahoo for around the year,

0:25:05.400 --> 0:25:08.120
<v Speaker 1>and so Meyer's appointment was intended to shake things up

0:25:08.520 --> 0:25:11.600
<v Speaker 1>at the old search engine and web portal, and Yahoo

0:25:11.600 --> 0:25:14.399
<v Speaker 1>had been through some pretty tough times. From two thousand

0:25:14.400 --> 0:25:18.159
<v Speaker 1>and nine to twenty eleven, Carol Bart's was CEO, and

0:25:18.240 --> 0:25:21.359
<v Speaker 1>her tenure was marked with making some really big replacements

0:25:21.400 --> 0:25:24.360
<v Speaker 1>in the executive ranks, as well as a struggle over

0:25:24.480 --> 0:25:29.080
<v Speaker 1>Yahoo's very identity. Was it a media company or was

0:25:29.119 --> 0:25:32.160
<v Speaker 1>it a tech company? Because Yahoo was really getting into

0:25:32.200 --> 0:25:36.200
<v Speaker 1>content creation as well, and it just felt like the

0:25:36.960 --> 0:25:40.800
<v Speaker 1>attention of the company was divided and it wasn't doing

0:25:40.920 --> 0:25:45.640
<v Speaker 1>either thing particularly well. Eventually, Yahoo's board of Director's lost

0:25:45.720 --> 0:25:49.439
<v Speaker 1>patients with Carol Bart's and fired her over the phone

0:25:50.240 --> 0:25:55.760
<v Speaker 1>Yike's not classy. Then, in early twenty twelve, and embarrassing

0:25:55.800 --> 0:25:58.479
<v Speaker 1>situation reared its ugly head when it was discovered that

0:25:58.560 --> 0:26:03.159
<v Speaker 1>Barts's replacement as CEO, a guy named Scott Thompson, not

0:26:03.320 --> 0:26:06.240
<v Speaker 1>the guy from Kids in the Hall, that he had

0:26:06.280 --> 0:26:09.679
<v Speaker 1>fibbed on his resume, that he had made up some

0:26:09.800 --> 0:26:12.000
<v Speaker 1>information that was on his resume, And this was a

0:26:12.000 --> 0:26:14.600
<v Speaker 1>bit of a black eye situation, and Thompson was very

0:26:14.680 --> 0:26:17.920
<v Speaker 1>quickly given his walking papers just a few months after

0:26:17.960 --> 0:26:21.120
<v Speaker 1>he took the job. Meyer would come in as the

0:26:21.160 --> 0:26:24.359
<v Speaker 1>new head of Yahoo. She said in an interview with

0:26:24.440 --> 0:26:29.240
<v Speaker 1>Wired's Virginia Hefferman that Yahoo as a business constituted all

0:26:29.280 --> 0:26:32.040
<v Speaker 1>the different areas in tech that she had worked within

0:26:32.240 --> 0:26:34.680
<v Speaker 1>over her years at Google, and she thought she might

0:26:34.720 --> 0:26:37.040
<v Speaker 1>be able to bring her skill set to help a

0:26:37.080 --> 0:26:41.359
<v Speaker 1>company that was clearly in need. So Meyer had a

0:26:41.400 --> 0:26:44.479
<v Speaker 1>lot of work to do. Yahoo was in a pretty

0:26:44.480 --> 0:26:47.720
<v Speaker 1>weird space. Morale was shaky, the company had lacked a

0:26:47.760 --> 0:26:50.840
<v Speaker 1>solid sense of direction, and the board was eager to

0:26:50.880 --> 0:26:54.240
<v Speaker 1>see change. On top of that, there was this ongoing

0:26:54.280 --> 0:26:57.480
<v Speaker 1>problem that Yahoo would fail to address. This shift of

0:26:57.640 --> 0:27:02.200
<v Speaker 1>user habits to a more mobile center online experience. While

0:27:02.240 --> 0:27:05.840
<v Speaker 1>other services and sites were adapting to mobile, Yahoo had

0:27:05.880 --> 0:27:08.679
<v Speaker 1>lagged behind, and according to that interview I mentioned a

0:27:08.680 --> 0:27:11.920
<v Speaker 1>second ago, Meyer felt that the move to mobile happened

0:27:11.960 --> 0:27:15.119
<v Speaker 1>far too late, like eight years too late, she had said.

0:27:15.560 --> 0:27:17.600
<v Speaker 1>While she says she's proud of the work she did

0:27:17.600 --> 0:27:20.439
<v Speaker 1>at Yahoo, ultimately it would prove to be too little,

0:27:20.680 --> 0:27:23.200
<v Speaker 1>too late, and later on the board of directors would

0:27:23.240 --> 0:27:26.800
<v Speaker 1>decide to sell Yahoo to Verizon, at which point Meyer

0:27:26.880 --> 0:27:30.439
<v Speaker 1>would resign from her position. Meyer's tenure at Yahoo was

0:27:30.440 --> 0:27:33.000
<v Speaker 1>marked by many attempts to right the wrongs that had

0:27:33.040 --> 0:27:36.480
<v Speaker 1>plagued Yahoo over the previous few years, but without the

0:27:36.480 --> 0:27:39.280
<v Speaker 1>support of the board, it was pretty much a doomed endeavor.

0:27:39.840 --> 0:27:44.240
<v Speaker 1>Would it have worked otherwise? Well, I guess we're never

0:27:44.280 --> 0:27:47.480
<v Speaker 1>gonna know. All right, now, we're up to twenty thirteen,

0:27:47.560 --> 0:27:50.600
<v Speaker 1>and a lot of stuff happened that year. Twitter became

0:27:50.680 --> 0:27:54.160
<v Speaker 1>a publicly traded company in twenty thirteen and would remain

0:27:54.240 --> 0:27:57.119
<v Speaker 1>so until Elon Musk would announce he was going to

0:27:57.160 --> 0:27:59.239
<v Speaker 1>buy it, try to back out of buying it, and

0:27:59.280 --> 0:28:03.119
<v Speaker 1>then was forced to buy it. Many years later. Bitcoin's

0:28:03.200 --> 0:28:05.880
<v Speaker 1>value took off for the first time in twenty thirteen.

0:28:05.920 --> 0:28:08.840
<v Speaker 1>It would later crash and then rise and crash again.

0:28:08.920 --> 0:28:13.399
<v Speaker 1>We've seen that happen numerous times. New consoles like the

0:28:13.560 --> 0:28:16.440
<v Speaker 1>Xbox One and the PlayStation four would hit the market

0:28:16.480 --> 0:28:20.640
<v Speaker 1>in twenty thirteen. But the big story, at least here

0:28:20.640 --> 0:28:24.840
<v Speaker 1>in the United States, was a huge scandal about how

0:28:24.920 --> 0:28:29.960
<v Speaker 1>an intelligence agency, or actually a few intelligence agencies here

0:28:30.000 --> 0:28:33.879
<v Speaker 1>in the States, had been collecting enormous amounts of information

0:28:33.960 --> 0:28:37.760
<v Speaker 1>about what were otherwise considered to be private activities of

0:28:37.960 --> 0:28:43.600
<v Speaker 1>US citizens and others, and that would end up making

0:28:44.040 --> 0:28:47.840
<v Speaker 1>world news. We'll talk about that more in just a moment,

0:28:47.840 --> 0:28:50.080
<v Speaker 1>but we're going to take another quick break to think

0:28:50.120 --> 0:29:04.400
<v Speaker 1>our sponsors. All right. Before the break, I alluded to

0:29:04.920 --> 0:29:11.280
<v Speaker 1>this scandalous revelation of how intelligence agencies within the United

0:29:11.320 --> 0:29:16.240
<v Speaker 1>States were apparently collecting truly huge amounts of data. So

0:29:16.320 --> 0:29:19.480
<v Speaker 1>the story is a contractor with the NSA, A guy

0:29:19.560 --> 0:29:23.560
<v Speaker 1>named Edward Snowden blew the whistle on these programs that

0:29:23.600 --> 0:29:26.720
<v Speaker 1>seemed to be a massive breach of constitutional protections or

0:29:26.760 --> 0:29:31.280
<v Speaker 1>at the very least a disturbing example of overly intrusive surveillance.

0:29:31.760 --> 0:29:36.480
<v Speaker 1>Snowden revealed the existence of a program called PRISM. Now

0:29:36.720 --> 0:29:42.200
<v Speaker 1>that's PRISM. Essentially, this described a sweeping program in which

0:29:42.240 --> 0:29:45.800
<v Speaker 1>the NSA had, as the Guardian would put it, quote,

0:29:45.960 --> 0:29:50.320
<v Speaker 1>direct access to the systems of Google, Facebook, Apple and

0:29:50.560 --> 0:29:56.840
<v Speaker 1>other US Internet giants end quote. And that alone was alarming.

0:29:57.280 --> 0:30:00.840
<v Speaker 1>So what sort of data did the NSA have access to? Well, again,

0:30:00.880 --> 0:30:04.320
<v Speaker 1>according to the Guardian, it was pretty much everything. I mean,

0:30:04.360 --> 0:30:09.200
<v Speaker 1>it was everything from search histories to emails, to file transfers,

0:30:09.600 --> 0:30:15.920
<v Speaker 1>voiceover Internet Protocol calls. Beyond all this information came directly

0:30:16.040 --> 0:30:20.160
<v Speaker 1>from the provider's servers. Apparently, the documents that Snowden shared

0:30:20.200 --> 0:30:23.200
<v Speaker 1>claimed that the NSA had cooperation of the various companies

0:30:23.200 --> 0:30:26.719
<v Speaker 1>in this endeavor, although when The Guardian reached out for comment,

0:30:26.920 --> 0:30:31.400
<v Speaker 1>representatives from the various companies denied knowing about PRISM. Curiouser

0:30:31.560 --> 0:30:35.400
<v Speaker 1>and curiouser, as it would turn out, this was top

0:30:35.440 --> 0:30:40.840
<v Speaker 1>secret stuff and companies weren't allowed to reveal that they

0:30:40.840 --> 0:30:42.280
<v Speaker 1>were part of it. It was all part of the

0:30:42.320 --> 0:30:47.120
<v Speaker 1>clandestine nature. So were they lying that they didn't know

0:30:47.160 --> 0:30:49.240
<v Speaker 1>about it? I guess it depends on who was actually

0:30:49.280 --> 0:30:51.800
<v Speaker 1>making the statement, because there were probably people who didn't

0:30:51.840 --> 0:30:53.520
<v Speaker 1>know about it who were told hey, you got to

0:30:53.520 --> 0:30:55.800
<v Speaker 1>tell them we don't know anything about this, and others

0:30:55.840 --> 0:30:58.000
<v Speaker 1>who may maybe they did know about it, but they

0:30:58.040 --> 0:31:00.640
<v Speaker 1>still had to say they didn't. Later documents would show

0:31:00.680 --> 0:31:04.240
<v Speaker 1>that the intelligence community was actually paying millions of dollars

0:31:04.600 --> 0:31:09.760
<v Speaker 1>collectively to these various platforms, and the program originated with

0:31:09.960 --> 0:31:12.800
<v Speaker 1>a couple of pieces of legislation that were signed into

0:31:12.880 --> 0:31:17.080
<v Speaker 1>law years earlier, namely the Protect America Act, which was

0:31:17.120 --> 0:31:19.440
<v Speaker 1>signed into law in two thousand and seven and the

0:31:19.480 --> 0:31:22.440
<v Speaker 1>FISA Amendments Act of two thousand and eight. Both of

0:31:22.480 --> 0:31:26.120
<v Speaker 1>those were signed into law by former President George W. Bush,

0:31:26.160 --> 0:31:28.720
<v Speaker 1>And it would turn out that the NSA didn't exactly

0:31:29.120 --> 0:31:32.600
<v Speaker 1>have its own backdoor access to all these different platforms.

0:31:32.600 --> 0:31:34.680
<v Speaker 1>So it wasn't like, you know, it's a slow day

0:31:34.720 --> 0:31:36.640
<v Speaker 1>at the NSA. Let's go see what people have been

0:31:36.640 --> 0:31:40.760
<v Speaker 1>posting on Facebook to each other in private messages. It

0:31:40.800 --> 0:31:44.080
<v Speaker 1>wasn't quite like that. Instead, the way it works from

0:31:44.120 --> 0:31:48.800
<v Speaker 1>a very very high level is that you send a

0:31:48.840 --> 0:31:52.640
<v Speaker 1>request to the FBI. The FBI sends a directive to

0:31:53.160 --> 0:31:57.000
<v Speaker 1>various Internet service providers, and by law, those providers have

0:31:57.080 --> 0:32:01.680
<v Speaker 1>to hand over essentially raw communications data, and you just

0:32:01.720 --> 0:32:06.200
<v Speaker 1>get this a massive amount of information that encompasses all

0:32:06.240 --> 0:32:09.320
<v Speaker 1>the data sent an over a given amount of time.

0:32:09.760 --> 0:32:12.200
<v Speaker 1>The FBI then sends this huge amount of information to

0:32:12.240 --> 0:32:17.920
<v Speaker 1>THESA stores it on various databases. And presumably the reason

0:32:17.920 --> 0:32:19.880
<v Speaker 1>there is that you have all this data that you

0:32:19.920 --> 0:32:24.640
<v Speaker 1>can then sift through and search and look for clues

0:32:24.720 --> 0:32:29.200
<v Speaker 1>for stuff that potentially threatened national security. So we're talking

0:32:29.200 --> 0:32:32.920
<v Speaker 1>about things like terrorist plans, that kind of thing. The

0:32:33.200 --> 0:32:38.520
<v Speaker 1>NSSA may try to decrypt encrypted information that can take

0:32:38.640 --> 0:32:41.720
<v Speaker 1>quite some time, depending upon the level of encryption. But

0:32:42.080 --> 0:32:46.120
<v Speaker 1>in theory, any investigation would first need to secure a

0:32:46.240 --> 0:32:50.360
<v Speaker 1>warrant from a court before anyone would be allowed to

0:32:50.440 --> 0:32:54.640
<v Speaker 1>search through all that communications data. However, in practice, well

0:32:54.720 --> 0:32:59.080
<v Speaker 1>journalist Glenn Greenwald argued that analysts at the NSA can

0:33:00.000 --> 0:33:04.040
<v Speaker 1>how much access communications anytime they like without securing any

0:33:04.080 --> 0:33:05.920
<v Speaker 1>kind of warrant first, Like they could just you know,

0:33:06.040 --> 0:33:09.280
<v Speaker 1>scan through it if they want to. They have that capability.

0:33:09.280 --> 0:33:12.200
<v Speaker 1>There's nothing preventing them from doing this. And in fact

0:33:12.240 --> 0:33:15.120
<v Speaker 1>that this is something that was and perhaps still is

0:33:15.160 --> 0:33:19.560
<v Speaker 1>happening at the NSA. This is according again to Glenn Greenwald,

0:33:19.840 --> 0:33:22.840
<v Speaker 1>and you know, people are people, there are people who

0:33:22.840 --> 0:33:26.760
<v Speaker 1>will do dumb stuff, even though they might be burdened

0:33:26.800 --> 0:33:31.480
<v Speaker 1>with great responsibility. So there have certainly been examples of

0:33:31.560 --> 0:33:35.880
<v Speaker 1>people within the intelligence community making use of official tools

0:33:36.160 --> 0:33:40.000
<v Speaker 1>for more personal reasons, like checking up on what an

0:33:40.040 --> 0:33:43.320
<v Speaker 1>ex partner has been doing since a messy breakup, for example.

0:33:43.640 --> 0:33:47.920
<v Speaker 1>That kind of stuff. Like you give someone the keys

0:33:48.000 --> 0:33:51.280
<v Speaker 1>to a really powerful tool like that, I suppose the

0:33:51.320 --> 0:33:56.240
<v Speaker 1>temptation to misuse it must be pretty great. Prism has

0:33:56.320 --> 0:34:00.000
<v Speaker 1>not gone away now. I would say that one lesson

0:34:00.120 --> 0:34:04.120
<v Speaker 1>to take home is that encryption is your friend. It

0:34:04.160 --> 0:34:07.560
<v Speaker 1>doesn't guarantee that the communications you participate in will be

0:34:07.640 --> 0:34:10.120
<v Speaker 1>hidden away, but it makes it much harder for folks

0:34:10.200 --> 0:34:13.640
<v Speaker 1>to just snoop on you. Of course, we're rapidly approaching

0:34:13.719 --> 0:34:17.440
<v Speaker 1>a quantum computing future in which all previously reliable methods

0:34:17.440 --> 0:34:21.040
<v Speaker 1>of encryption could potentially just become child's play to unravel.

0:34:21.760 --> 0:34:24.480
<v Speaker 1>But that's the future. Our concern today right now is

0:34:24.880 --> 0:34:30.560
<v Speaker 1>the past. So yeah, Snowden obviously his story still ongoing.

0:34:30.600 --> 0:34:36.239
<v Speaker 1>He's been living in exile for the last decade, and

0:34:36.719 --> 0:34:43.120
<v Speaker 1>some view him as a important whistleblower who alerted citizens

0:34:43.200 --> 0:34:47.800
<v Speaker 1>to a program that appears to have a crazy amount

0:34:48.040 --> 0:34:55.000
<v Speaker 1>of depth in surveillance, even if you accept the statements

0:34:55.040 --> 0:34:58.359
<v Speaker 1>of the intelligence community that oh, sure we're collecting all

0:34:58.360 --> 0:35:00.160
<v Speaker 1>of it, but we're not searching it, so we don't

0:35:00.160 --> 0:35:02.239
<v Speaker 1>even know what we have, so you have nothing to

0:35:02.239 --> 0:35:06.080
<v Speaker 1>worry about. That's not very That doesn't make me feel better.

0:35:06.320 --> 0:35:09.080
<v Speaker 1>But not only have we had that, like, he's also

0:35:09.200 --> 0:35:13.320
<v Speaker 1>obviously had to deal with finding a totally new life

0:35:13.840 --> 0:35:16.600
<v Speaker 1>outside of the United States because there's some people who

0:35:16.680 --> 0:35:19.640
<v Speaker 1>view him as a traitor to the country and he

0:35:19.760 --> 0:35:24.520
<v Speaker 1>could face serious repercussions were he ever to return. So, yeah,

0:35:24.760 --> 0:35:29.279
<v Speaker 1>a pretty dramatic story in tech. In twenty fourteen, we

0:35:29.320 --> 0:35:32.160
<v Speaker 1>had a whole year of corporate changes happening in tech.

0:35:32.239 --> 0:35:35.880
<v Speaker 1>Steve Balmer, who had led Microsoft as the CEO for

0:35:35.960 --> 0:35:39.359
<v Speaker 1>fourteen years at that point, stepped down to make way

0:35:39.400 --> 0:35:44.040
<v Speaker 1>for Satya Nadella to take over. Google bought Nest Labs.

0:35:44.320 --> 0:35:48.239
<v Speaker 1>They're the makers of the smart thermostat, and had just

0:35:48.480 --> 0:35:51.920
<v Speaker 1>at the end of twenty thirteen, had acquired Boston Dynamics.

0:35:51.920 --> 0:35:56.600
<v Speaker 1>That's the robotics company that makes adorably terrifying four legged robots,

0:35:56.600 --> 0:36:01.239
<v Speaker 1>among other things. Google would later divest itself of Boston Dynamics.

0:36:01.239 --> 0:36:04.960
<v Speaker 1>They did so fairly recently found a new home at Hyundai.

0:36:05.840 --> 0:36:09.960
<v Speaker 1>Apple announced it would acquire Beats Electronics for a whopping

0:36:10.080 --> 0:36:14.520
<v Speaker 1>three billion With a B dollars, Facebook would make even

0:36:14.640 --> 0:36:17.399
<v Speaker 1>larger purchases. Well, they made one that was smaller. They

0:36:17.400 --> 0:36:21.879
<v Speaker 1>bought Oculus VR for two billion, but they bought wattsapp

0:36:22.040 --> 0:36:26.640
<v Speaker 1>for twenty two billion dollars. At this stage, I think

0:36:26.719 --> 0:36:30.279
<v Speaker 1>Facebook was still looking to solidify everything around the tent

0:36:30.440 --> 0:36:35.880
<v Speaker 1>pole Facebook social network platform. Like Facebook itself, the platform

0:36:36.040 --> 0:36:39.640
<v Speaker 1>was the core of its strategy. But in future years

0:36:39.640 --> 0:36:42.759
<v Speaker 1>the company, especially once it changed its name to Meta,

0:36:42.880 --> 0:36:45.920
<v Speaker 1>would take a less focused approach to creating what it

0:36:46.000 --> 0:36:49.400
<v Speaker 1>hopes will be the future of online life. They're like, well,

0:36:49.880 --> 0:36:52.880
<v Speaker 1>Facebook is just one part of our strategy as opposed

0:36:52.920 --> 0:36:56.120
<v Speaker 1>to the central part. However, the story I want to

0:36:56.120 --> 0:36:59.759
<v Speaker 1>focus on from twenty fourteen is the Sony Pictures hack.

0:37:00.000 --> 0:37:02.520
<v Speaker 1>This was a big one, partly because of the sheer

0:37:02.520 --> 0:37:05.600
<v Speaker 1>amount of data that was lifted during the hack, partly

0:37:05.640 --> 0:37:09.200
<v Speaker 1>because of the sensitive nature of that information, which included

0:37:09.239 --> 0:37:13.640
<v Speaker 1>everything from personal information about Sony employees, including stuff like

0:37:13.719 --> 0:37:17.600
<v Speaker 1>salary information, all the way up to data about and

0:37:17.719 --> 0:37:22.480
<v Speaker 1>even digital prints of unreleased Sony pictures films, but also

0:37:22.600 --> 0:37:26.240
<v Speaker 1>the hack would end up becoming a case study in cybersecurity,

0:37:26.600 --> 0:37:31.680
<v Speaker 1>with numerous researchers publishing papers on everything from how organizations

0:37:31.719 --> 0:37:35.400
<v Speaker 1>can better protect themselves from intrusions two works detailing the

0:37:35.440 --> 0:37:39.600
<v Speaker 1>appropriate way to address a crisis once it happens. Because

0:37:39.640 --> 0:37:43.480
<v Speaker 1>Sony did a lot of things poorly, So what actually

0:37:43.480 --> 0:37:47.240
<v Speaker 1>did happen? Well? In twenty fourteen, Sony Pictures was preparing

0:37:47.280 --> 0:37:50.840
<v Speaker 1>to release a film titled The Interview. In this film,

0:37:50.960 --> 0:37:55.080
<v Speaker 1>a pair of dufices, a celebrity interview show host and

0:37:55.280 --> 0:37:58.719
<v Speaker 1>his producer are recruited by the CIA to use an

0:37:58.760 --> 0:38:02.439
<v Speaker 1>opportunity to inter view North Korea's leader Kim Jong un

0:38:02.880 --> 0:38:06.600
<v Speaker 1>and then assassinate him. So this is a satire. It

0:38:06.719 --> 0:38:10.239
<v Speaker 1>makes fun of Kim Jong Un a lot. It also

0:38:10.480 --> 0:38:13.920
<v Speaker 1>comments on the nation of North Korea in general and

0:38:13.960 --> 0:38:18.080
<v Speaker 1>its government in particular, and apparently all that was enough

0:38:18.120 --> 0:38:22.319
<v Speaker 1>to prompt North Korea to direct state backed hackers to

0:38:22.719 --> 0:38:28.080
<v Speaker 1>attack Sony Pictures. Now. I say apparently because definitive evidence

0:38:28.120 --> 0:38:31.080
<v Speaker 1>pointing to North Korea has never actually been made public.

0:38:31.840 --> 0:38:35.120
<v Speaker 1>That doesn't mean the evidence doesn't exist. It doesn't mean

0:38:35.560 --> 0:38:39.399
<v Speaker 1>that there are any other prime suspects that we could

0:38:39.400 --> 0:38:42.000
<v Speaker 1>point at right like, there's there's no one who looks

0:38:42.120 --> 0:38:47.240
<v Speaker 1>as good as North Korea in this. North Korea certainly

0:38:47.320 --> 0:38:50.200
<v Speaker 1>had the capability to pull something like this off. The

0:38:50.239 --> 0:38:54.640
<v Speaker 1>country has been implicated in other state backed cyber attacks. So,

0:38:55.320 --> 0:38:56.719
<v Speaker 1>but I do want to make it clear that the

0:38:56.760 --> 0:39:00.239
<v Speaker 1>working assumption is that North Korea was responsible, but there

0:39:00.320 --> 0:39:03.799
<v Speaker 1>is a little bit of ambiguity there. A group called

0:39:03.840 --> 0:39:09.080
<v Speaker 1>the Guardians of Peace ultimately claimed responsibility and claimed that

0:39:09.120 --> 0:39:12.640
<v Speaker 1>this was not in direct connection with North Korea's government,

0:39:12.680 --> 0:39:16.839
<v Speaker 1>but rather on behalf of North Korea. That is a

0:39:16.880 --> 0:39:22.000
<v Speaker 1>claim that I think most security experts have dismissed as

0:39:22.040 --> 0:39:24.600
<v Speaker 1>being unlikely. They think it really is more of a

0:39:24.640 --> 0:39:29.280
<v Speaker 1>state backed attack. But muddying the waters further is Sony's

0:39:29.320 --> 0:39:33.680
<v Speaker 1>own history with cybersecurity, which hasn't been great so Earlier

0:39:33.719 --> 0:39:36.280
<v Speaker 1>in the two thousands, the company got into hot water

0:39:36.360 --> 0:39:39.240
<v Speaker 1>when it was found that the music division within Sony

0:39:39.600 --> 0:39:43.320
<v Speaker 1>had been using a digital rights management or DRM strategy

0:39:43.640 --> 0:39:47.160
<v Speaker 1>on their compact discs. And the idea was that if

0:39:47.200 --> 0:39:49.720
<v Speaker 1>you took a compact disc and you put it into

0:39:49.880 --> 0:39:53.840
<v Speaker 1>the optical drive of a computer, because children back in

0:39:53.880 --> 0:39:57.440
<v Speaker 1>those days, our computers had optical drives, meaning that you

0:39:57.440 --> 0:40:00.440
<v Speaker 1>would put a disc in the drive. I know that

0:40:00.440 --> 0:40:02.520
<v Speaker 1>that sounds strange, but that's how we used to do

0:40:02.600 --> 0:40:04.960
<v Speaker 1>things before that. It was floppy disks. But I don't

0:40:05.000 --> 0:40:08.080
<v Speaker 1>want to take you into prehistory anyway. If you were

0:40:08.120 --> 0:40:09.680
<v Speaker 1>to do this, you might do it so that you

0:40:09.680 --> 0:40:12.759
<v Speaker 1>could rip the music and make a digital copy for

0:40:12.800 --> 0:40:16.120
<v Speaker 1>the purposes of, say, putting it on like an iPod

0:40:16.239 --> 0:40:19.600
<v Speaker 1>or something. And you might also do it so that

0:40:19.640 --> 0:40:24.640
<v Speaker 1>you could burn new CDs with the music that you

0:40:24.800 --> 0:40:27.759
<v Speaker 1>just got from the one you bought. So Sony wanted

0:40:27.800 --> 0:40:31.120
<v Speaker 1>to prevent people from doing that second thing. They didn't

0:40:31.160 --> 0:40:34.879
<v Speaker 1>want people to make unauthorized copies of music. Never mind

0:40:34.880 --> 0:40:36.760
<v Speaker 1>the fact that, at least here in the United States,

0:40:37.080 --> 0:40:40.400
<v Speaker 1>you are legally allowed to make a copy of a

0:40:40.440 --> 0:40:43.800
<v Speaker 1>CD for the purposes of a personal backup. That's completely

0:40:43.840 --> 0:40:47.239
<v Speaker 1>within your rights. So if you bought a CD and

0:40:47.440 --> 0:40:49.200
<v Speaker 1>you made a copy of it so that you could

0:40:49.239 --> 0:40:51.920
<v Speaker 1>listen to it in case your original CD gets scratched

0:40:52.000 --> 0:40:56.320
<v Speaker 1>or stolen or broken or something, that's fine. Oddly enough, however,

0:40:56.560 --> 0:40:59.719
<v Speaker 1>it is against the law to try and circumvent the

0:41:00.000 --> 0:41:04.280
<v Speaker 1>detective measures that people might place on things like CDs

0:41:04.280 --> 0:41:06.600
<v Speaker 1>to prevent you from doing that. So, yeah, you have

0:41:06.640 --> 0:41:08.600
<v Speaker 1>the right to make a copy, but you don't have

0:41:08.680 --> 0:41:12.919
<v Speaker 1>the right to break the copy protection on a disc.

0:41:13.560 --> 0:41:18.520
<v Speaker 1>It's odd, right, A's a catch twenty two situation. Anyway,

0:41:18.760 --> 0:41:24.879
<v Speaker 1>Sony did a thing that really shook people up. They

0:41:24.960 --> 0:41:28.759
<v Speaker 1>had installed DRM that would put in essentially a rootkit

0:41:29.400 --> 0:41:32.960
<v Speaker 1>on your computer and allow someone to get remote access

0:41:33.120 --> 0:41:36.920
<v Speaker 1>to your computer through the Internet. That obviously was a

0:41:36.920 --> 0:41:39.080
<v Speaker 1>big no no. It did not go well, and later

0:41:39.120 --> 0:41:41.680
<v Speaker 1>on in twenty eleven, Sony found itself the target of

0:41:41.719 --> 0:41:45.239
<v Speaker 1>several cyber attacks, when networks being breached more than twenty

0:41:45.280 --> 0:41:49.040
<v Speaker 1>times that year, and the company then declared a war

0:41:49.239 --> 0:41:52.960
<v Speaker 1>on hackers, which I think mini hackers viewed as both

0:41:53.000 --> 0:41:57.080
<v Speaker 1>amusing and potentially a personal challenge. And so there's an

0:41:57.200 --> 0:41:59.960
<v Speaker 1>argument to be made that Sony's own approach to cyber

0:42:00.080 --> 0:42:04.439
<v Speaker 1>security was one that incited hackers to find new ways

0:42:04.480 --> 0:42:07.200
<v Speaker 1>to exploit the company's systems. Meanwhile, Sony was not doing

0:42:07.200 --> 0:42:12.200
<v Speaker 1>a very good job at all in actually improving their security.

0:42:13.040 --> 0:42:15.759
<v Speaker 1>The attacks ended up locking employees out of their computers

0:42:15.800 --> 0:42:19.520
<v Speaker 1>at least temporarily, and the hackers stole truly huge amounts

0:42:19.560 --> 0:42:23.360
<v Speaker 1>of data. They then released that information online, and that

0:42:23.440 --> 0:42:27.120
<v Speaker 1>info included stuff like executive salaries, which is pretty sensitive

0:42:27.120 --> 0:42:30.440
<v Speaker 1>information that companies typically don't want out in the open.

0:42:31.239 --> 0:42:33.840
<v Speaker 1>And investigation showed that the hackers didn't have to do

0:42:33.880 --> 0:42:37.080
<v Speaker 1>anything particularly spectacular to pull all this off, because again,

0:42:37.160 --> 0:42:39.439
<v Speaker 1>Sony Pictures was not exactly up to date with good

0:42:39.440 --> 0:42:43.520
<v Speaker 1>security hygiene, and employees had not been properly trained and

0:42:43.560 --> 0:42:47.560
<v Speaker 1>they weren't really vigilant. The lack of multi factor authentication

0:42:47.760 --> 0:42:50.040
<v Speaker 1>made it much easier for the hackers to find a

0:42:50.120 --> 0:42:54.200
<v Speaker 1>compromise log in for systems without having to worry about

0:42:54.200 --> 0:42:57.520
<v Speaker 1>additional layers of security. The hackers apparently tricked a few

0:42:57.520 --> 0:43:00.880
<v Speaker 1>select employees with a fake Apple ID login page to

0:43:00.880 --> 0:43:04.000
<v Speaker 1>get hold of their credentials. Then it was just off

0:43:04.040 --> 0:43:06.800
<v Speaker 1>to the races, so this was kind of an example

0:43:06.840 --> 0:43:11.680
<v Speaker 1>of spear fishing. Sony was obviously deeply embarrassed by this

0:43:11.880 --> 0:43:15.120
<v Speaker 1>whole thing, and it was impossible for the company to

0:43:15.200 --> 0:43:17.799
<v Speaker 1>cover it up. The hackers had dumped a ton of

0:43:17.840 --> 0:43:22.360
<v Speaker 1>proprietary and private information online and the mess costs Sony

0:43:22.960 --> 0:43:25.839
<v Speaker 1>a whole lot of money, though determining just how much

0:43:25.840 --> 0:43:29.759
<v Speaker 1>money is actually pretty tricky. On the low end of things,

0:43:29.880 --> 0:43:34.720
<v Speaker 1>Sony set aside around fifteen million dollars to address security concerns,

0:43:34.760 --> 0:43:37.280
<v Speaker 1>which is not much at all in the grand scheme

0:43:37.280 --> 0:43:40.600
<v Speaker 1>of things. Later on, the company also had to agree

0:43:40.640 --> 0:43:43.279
<v Speaker 1>to pay around eight million dollars in response to a

0:43:43.320 --> 0:43:46.000
<v Speaker 1>class action lawsuit that was brought against the company by

0:43:46.080 --> 0:43:48.759
<v Speaker 1>employees who have been affected by this. You know, their

0:43:48.800 --> 0:43:51.160
<v Speaker 1>personal information had been stolen as part of this hack.

0:43:52.160 --> 0:43:54.920
<v Speaker 1>But because of the nature of what happened with all

0:43:54.960 --> 0:43:59.120
<v Speaker 1>that proprietary information leaked and then shared online, it's actually

0:43:59.160 --> 0:44:02.200
<v Speaker 1>really hard to put a figure on, ultimately how much

0:44:02.200 --> 0:44:05.920
<v Speaker 1>it costs. I've seen estimates that have a wild range

0:44:05.960 --> 0:44:08.759
<v Speaker 1>from around thirty five million dollars on the low end

0:44:08.800 --> 0:44:13.120
<v Speaker 1>to almost two hundred million on the high end. It's

0:44:13.440 --> 0:44:16.160
<v Speaker 1>I honestly don't know how much it costs. But it

0:44:16.320 --> 0:44:19.640
<v Speaker 1>was embarrassing for Sony, and it was a real wake

0:44:19.719 --> 0:44:22.680
<v Speaker 1>up call. I think for a lot of companies and

0:44:22.800 --> 0:44:29.040
<v Speaker 1>organizations that they have to take cybersecurity seriously because something

0:44:29.080 --> 0:44:34.520
<v Speaker 1>as small as a perceived slight might prompt a nation

0:44:34.800 --> 0:44:39.080
<v Speaker 1>backed group of hackers to try and reach your systems.

0:44:39.600 --> 0:44:42.360
<v Speaker 1>I mean, in this case, like I said, the straw

0:44:42.400 --> 0:44:46.400
<v Speaker 1>that appears to have broken the proverbial camel's back was

0:44:46.480 --> 0:44:48.800
<v Speaker 1>the fact that Sony Pictures was going to really release

0:44:48.840 --> 0:44:52.359
<v Speaker 1>the interview, which y'all, in my opinion, was not even

0:44:52.440 --> 0:44:55.120
<v Speaker 1>that funny of a comedy, no grit. That's me. I

0:44:55.200 --> 0:44:56.680
<v Speaker 1>think there were a lot of funny people in it,

0:44:57.120 --> 0:45:01.040
<v Speaker 1>but I didn't personally find it that entertaining. Then again,

0:45:01.120 --> 0:45:03.160
<v Speaker 1>I'm probably the wrong audience. I'm such a stick in

0:45:03.200 --> 0:45:06.600
<v Speaker 1>the mud. But that is our first part of our

0:45:06.640 --> 0:45:09.279
<v Speaker 1>look back on some of the big tech stories that

0:45:09.360 --> 0:45:12.520
<v Speaker 1>have unfolded since we launched tech Stuff in June two

0:45:12.560 --> 0:45:15.480
<v Speaker 1>thousand and eight. Part two will be coming up next week,

0:45:15.680 --> 0:45:18.239
<v Speaker 1>and then my final episode of tech Stuff host will

0:45:18.440 --> 0:45:21.360
<v Speaker 1>follow that. So will I still have a chance to

0:45:21.400 --> 0:45:30.680
<v Speaker 1>say this? I'll talk to you again really soon. Tech

0:45:30.760 --> 0:45:35.320
<v Speaker 1>Stuff is an iHeartRadio production. For more podcasts from iHeartRadio,

0:45:35.640 --> 0:45:39.360
<v Speaker 1>visit the iHeartRadio app, Apple Podcasts, or wherever you listen

0:45:39.360 --> 0:45:43.719
<v Speaker 1>to your favorite shows.