WEBVTT - TechStuff Remembers 2014, Part One 0:00:04.200 --> 0:00:08.119 Get in touch with technology with tex Stuff from com 0:00:12.039 --> 0:00:15.080 Hey there, and welcome to tex Stuff. I'm Jonathan Strickland, 0:00:15.160 --> 0:00:18.800 and today joining me in the studio is Joe McCormick. Joe, 0:00:18.840 --> 0:00:21.959 welcome back, Thanks for having me back. Thank thank you. 0:00:22.200 --> 0:00:24.320 It was kind of a last minute jump in. It 0:00:24.440 --> 0:00:27.480 was it was originally Lauren Vogelbaum was going to sit 0:00:27.520 --> 0:00:29.320 in on this one, but Lauren's feeling a little under 0:00:29.320 --> 0:00:31.680 the weather and we just wanted to look back at 0:00:31.680 --> 0:00:34.320 the year two thousand fourteen. Some of the big stories 0:00:34.360 --> 0:00:37.280 that happened, stuff that I didn't cover in the Predictions 0:00:37.280 --> 0:00:40.360 episode because we didn't know it's going to happen, and 0:00:40.360 --> 0:00:43.000 then it happened. That's kind of the way that tends 0:00:43.000 --> 0:00:46.200 to work. I think your crystal ball is faulty. Yeah, 0:00:46.240 --> 0:00:49.120 it turns out that I was actually just staring into 0:00:49.120 --> 0:00:51.839 a magic eight ball, and uh, that was it. I 0:00:51.880 --> 0:00:55.240 think the problem is that you're not actually using crystal 0:00:55.400 --> 0:00:59.240 You're you've been peering into a plutonium core. That would 0:00:59.280 --> 0:01:03.320 also explained the laws and teeth. So at any rate, 0:01:03.360 --> 0:01:06.360 let's talk about some of the big stories in two 0:01:06.360 --> 0:01:09.320 thousand and fourteen, some of the stuff that happened throughout 0:01:09.360 --> 0:01:11.080 the year. Now we're just going to be kind of 0:01:11.120 --> 0:01:15.960 covering some interesting things, not and not everything obviously the 0:01:16.040 --> 0:01:19.400 highlights in the low lights. Yeah, nothing, nothing like every 0:01:19.400 --> 0:01:22.720 story what happened in it would take us way too long, 0:01:22.800 --> 0:01:25.760 you know. I think has been a really interesting year 0:01:25.800 --> 0:01:28.920 for tech and one of the most interesting things about 0:01:28.920 --> 0:01:31.000 it to me is that it seems like this has 0:01:31.040 --> 0:01:35.319 really been the year of the hack. That is absolutely 0:01:35.640 --> 0:01:37.640 the way I would put it. Yeah, I mean there 0:01:37.680 --> 0:01:41.160 have been big hacks and security breaches in the past. 0:01:42.520 --> 0:01:45.480 There were so many of them and with such far 0:01:45.760 --> 0:01:48.640 ranging impact that I think it was the year where 0:01:48.680 --> 0:01:51.960 the average person out there, the person who doesn't really 0:01:52.040 --> 0:01:56.320 follow technology news, is really starting to understand that a 0:01:56.400 --> 0:01:59.520 lot of the conflicts that are looming large in our 0:01:59.520 --> 0:02:04.120 future gonna be technology and cybersecurity related conflicts. Yeah. You know, 0:02:04.200 --> 0:02:08.239 we've heard stories in the past, everything from uh discovery 0:02:08.440 --> 0:02:13.919 of code in infrastructure things like utility infrastructure that that 0:02:13.960 --> 0:02:19.040 showed that there was possible Chinese incursions into our infrastructure. 0:02:19.880 --> 0:02:22.080 You know, those stories have come and gone, and but 0:02:22.200 --> 0:02:24.320 this year really has displayed it. I mean, there's been 0:02:24.360 --> 0:02:28.280 a lot that have directly impacted consumers of course, in 0:02:29.400 --> 0:02:32.760 there was the target um hack, the one that stole 0:02:32.800 --> 0:02:34.880 a whole bunch of credit card information as well as 0:02:34.919 --> 0:02:37.959 other stuff from Target, and the fallout of that continued 0:02:37.960 --> 0:02:40.880 into But there are a lot of other stories we're 0:02:40.880 --> 0:02:44.880 gonna touch on, some of them that involve hackers hitting 0:02:44.960 --> 0:02:48.440 different sites. Yeah. Well, in fact, maybe we should just 0:02:48.520 --> 0:02:51.320 go through all the stories of their chronologically, because it 0:02:51.360 --> 0:02:53.799 looks like in your notes, Jonathan, the very first thing 0:02:53.840 --> 0:02:55.960 you have is about a hack. No, it is, in fact, 0:02:56.000 --> 0:02:59.720 that was that hackers who posted data about Snapchat users 0:03:00.160 --> 0:03:03.960 claim they did so to show that Snapchat security wasn't sufficient. 0:03:04.960 --> 0:03:08.280 In January of this, Yeries, it was. This is the 0:03:08.320 --> 0:03:10.920 first story we have. So this the hack itself had 0:03:10.919 --> 0:03:13.920 happened towards the tail end of but this was where 0:03:13.960 --> 0:03:17.920 we started getting information about what the hackers say their 0:03:17.919 --> 0:03:21.560 motivation happened to be. So, you know, there are different 0:03:21.560 --> 0:03:23.920 types of hackers, and I've talked about this before. There 0:03:23.919 --> 0:03:26.840 are hackers who what they're interested in is just learning 0:03:26.880 --> 0:03:29.960 how a system works and then how to modify that system. 0:03:30.160 --> 0:03:33.040 Has nothing to do with breaching security, right, It's just 0:03:33.600 --> 0:03:36.080 learning how something works being able to build it yourself. 0:03:36.160 --> 0:03:38.640 Maybe modify it, maybe make it do something it wasn't 0:03:38.680 --> 0:03:43.440 intended to do, but it has nothing necessarily nefarious about it. 0:03:43.720 --> 0:03:46.960 Then you've got things like white hack hat hackers versus 0:03:47.000 --> 0:03:49.960 black hat hackers. White hat hackers are the ones who 0:03:50.040 --> 0:03:53.920 work with companies to test their security, and they'll try 0:03:53.960 --> 0:03:57.320 to breach that security and then explain to the company 0:03:57.360 --> 0:03:58.920 how they were able to do it so that they 0:03:58.920 --> 0:04:02.520 can patch that vulnerar ability. Black hat had hackers are 0:04:02.560 --> 0:04:04.520 the ones that are trying to do it for some 0:04:04.600 --> 0:04:08.560 sort of gain, either an ideological gain where they are 0:04:08.600 --> 0:04:14.360 bringing down a company or organization that has a philosophy 0:04:14.360 --> 0:04:17.360 that doesn't agree with their own philosophy, or monetary gain 0:04:17.400 --> 0:04:20.960 where they're stealing stuff, either to directly benefit themselves or 0:04:21.000 --> 0:04:23.800 to sell off to other people. So in this case, 0:04:23.800 --> 0:04:26.080 the hackers were saying, we were just trying to prove 0:04:26.160 --> 0:04:28.960 that this company that says it has your privacy at 0:04:29.000 --> 0:04:32.080 heart doesn't really protect your privacy. That's all we were 0:04:32.120 --> 0:04:34.720 trying to do. But the way they did it was 0:04:35.240 --> 0:04:37.800 perhaps a little more on the black hat side than 0:04:37.839 --> 0:04:40.920 the white hack It's not like they alerted Snapchat and said, hey, 0:04:40.920 --> 0:04:43.680 by the way, we discovered this vulnerability, you need to 0:04:43.720 --> 0:04:49.360 address it instead. They they actually attacked. So all related 0:04:49.440 --> 0:04:52.640 to the fact that Snapchat. I think it was Snapchat 0:04:52.720 --> 0:04:55.800 that they were claiming that they delete all of your messages, 0:04:55.920 --> 0:04:59.279 but they actually don't. Yeah, there were a lot of 0:04:59.320 --> 0:05:02.000 issues with that Snapchat because again, yet, like you were 0:05:02.000 --> 0:05:05.919 pointing out, snapchat is all about sending someone a message 0:05:05.960 --> 0:05:09.040 that's supposed to have kind of a self destruct element 0:05:09.080 --> 0:05:11.240 to it, so that that's supposed to be ephemeral and 0:05:11.360 --> 0:05:14.640 not leave a trail for future generations to come discover 0:05:14.760 --> 0:05:18.800 what you know, Grandma and Grandpa were sending to each 0:05:18.800 --> 0:05:21.599 other on their phones, right, And it doesn't necessarily have 0:05:21.760 --> 0:05:25.200 to be you know, salacious. It often is, but it 0:05:25.240 --> 0:05:27.679 doesn't have to be. It could just be I don't 0:05:27.680 --> 0:05:31.000 want this to live anywhere because it's just a goofy 0:05:31.040 --> 0:05:33.840 picture and I just thought it was funny and that's all. 0:05:34.600 --> 0:05:39.000 But yeah, it turned out that they're they're promises of 0:05:39.040 --> 0:05:42.120 things being deleted exactly when you expected them to be 0:05:42.240 --> 0:05:45.839 were not completely true. The next story in January is 0:05:45.839 --> 0:05:49.160 that the US Appeals Court struck down the FCCS two 0:05:49.240 --> 0:05:53.640 thousand eleven regulations that demanded Internet providers treat all traffic 0:05:53.760 --> 0:05:57.479 equally because the court said the FCC lacked the authority 0:05:57.520 --> 0:06:00.880 to enact the regulations in the first place. It sounds 0:06:00.920 --> 0:06:02.440 like this is going to lead to some more net 0:06:02.440 --> 0:06:06.360 neutrality squabbles. Yeah, this was a big, big deal, I mean, 0:06:06.560 --> 0:06:08.280 and a lot of people were pointing out that this 0:06:08.360 --> 0:06:12.280 was a potential issue at the very beginning, saying it's 0:06:12.279 --> 0:06:15.080 not that I like people were saying, I don't disagree 0:06:15.200 --> 0:06:17.960 that we need to have net neutrality rules in place. 0:06:18.240 --> 0:06:21.440 The problem is that the FCC is trying to uh 0:06:21.480 --> 0:06:25.279 to exert authority over something it doesn't have authority over, 0:06:25.480 --> 0:06:28.839 and it was because of the classification of Internet communications. 0:06:29.200 --> 0:06:31.200 Will come back to the story towards the end of 0:06:31.200 --> 0:06:33.640 two thousand and fourteen. But yeah, that was a big, 0:06:33.680 --> 0:06:37.360 big news item early on. Also in January, Lenovo bought 0:06:37.480 --> 0:06:42.680 Motorola Mobility from Google for three billion dollars, and meanwhile 0:06:42.720 --> 0:06:46.680 Google bought Nest for three point two billion. Nest is 0:06:46.720 --> 0:06:51.719 the company that made yeah, also did smoke detectors, which 0:06:52.000 --> 0:06:54.520 in fourteen it ended up having to recall because of 0:06:54.560 --> 0:06:58.159 some issues. Wait, no, okay, one sentence explanation. How is 0:06:58.200 --> 0:07:03.600 the next thermostat actually special? Well, it It learns your behaviors. 0:07:03.640 --> 0:07:07.240 So if you like to have your house nice and 0:07:07.320 --> 0:07:09.800 cool in the evening and warm and toasty in the morning, 0:07:10.200 --> 0:07:12.600 it learns that and then starts to preset things so 0:07:12.680 --> 0:07:14.880 you don't have to ever program it to do so. 0:07:15.000 --> 0:07:17.800 It just learns what you want and can even do 0:07:17.880 --> 0:07:20.400 things like when it realizes there's no one in the house, 0:07:20.440 --> 0:07:22.640 it can start to turn things off so that way 0:07:22.640 --> 0:07:25.600 you're not wasting energy heating a house that has no 0:07:25.600 --> 0:07:29.160 one in it. And the final story of January two 0:07:29.200 --> 0:07:33.440 thou fourteen was that the Apple Mac turned thirty. What 0:07:33.640 --> 0:07:39.520 year were you born, Joe? Oh? The old okay, so 0:07:39.640 --> 0:07:43.160 that mac is older than you are. Uh, the Apple Mac? 0:07:43.400 --> 0:07:46.480 I remember the I remember in night when the commercial 0:07:46.520 --> 0:07:49.280 for the Apple Mac came out. That was the Orwellian one. 0:07:49.320 --> 0:07:55.520 You probably have seen it even yea and chatters the 0:07:55.520 --> 0:07:58.120 screen right Whose faces it up on the screen? Is 0:07:58.120 --> 0:08:01.200 it like John Hurd or somebody? Uh yeah, something like that. 0:08:01.520 --> 0:08:03.720 You know, although it was John Hurt, it might not 0:08:03.760 --> 0:08:06.280 actually be a famous persons say if it was John Hurt, 0:08:06.280 --> 0:08:09.920 that John Hurt hasn't has has remained old man age 0:08:10.120 --> 0:08:13.560 since nineteen four and hasn't changed since it's not that 0:08:13.600 --> 0:08:16.320 he stayed young, he's just stayed just as old. Actually, 0:08:16.400 --> 0:08:18.600 you know, I think I'm thinking of him as the 0:08:18.880 --> 0:08:23.440 big totalitarian face on the screen in uh oh, what's 0:08:23.480 --> 0:08:28.000 the movie? Oh all right, yeah, John Hurt. I think 0:08:28.000 --> 0:08:31.080 you're right. And I have never seen the Vendetta. It's 0:08:31.120 --> 0:08:33.079 kind of odd, right, because I mean, that's well, it's 0:08:33.080 --> 0:08:35.440 got a from what I recall, it's got John Hurt 0:08:35.640 --> 0:08:38.400 talking into a big screen and you know, spittles coming 0:08:38.440 --> 0:08:40.360 out of his mouth. He looks very angry about something. 0:08:40.400 --> 0:08:43.520 He's being the big brother type character. Yeah. Well, in 0:08:43.640 --> 0:08:46.240 February two thousand and fourteen, that was when we got 0:08:46.360 --> 0:08:49.960 a big news item where Microsoft finally announced its new CEO. 0:08:50.520 --> 0:08:55.040 So Balmer had stepped down as CEO. No, yeah, that 0:08:55.679 --> 0:08:59.280 spoiler alert. Balmber stepped down the CEO Developers, Developers, I'm gone. 0:08:59.760 --> 0:09:04.360 And then Satya Nadela became the new CEO of Microsoft, 0:09:04.400 --> 0:09:06.240 and he was a veteran of the company. He had 0:09:06.280 --> 0:09:10.280 been there for twenty two years. Bill Gates meanwhile transition 0:09:10.360 --> 0:09:12.760 from chairman of the Microsoft Board to the role of 0:09:12.800 --> 0:09:20.560 technology advisor. UH. Microsoft's competitor Sony announced five thousand job 0:09:20.640 --> 0:09:22.600 cuts and that they were going to split the TV 0:09:22.760 --> 0:09:26.640 division into a wholly owned subsidiary and to sell off 0:09:26.760 --> 0:09:30.440 its PC business. So this was a big news and 0:09:30.480 --> 0:09:34.199 not the last time we'll talk about Sony in this podcast. Obviously, 0:09:34.679 --> 0:09:37.440 anyone who's aware of current news knows that we're gonna 0:09:37.480 --> 0:09:39.319 have to come back around to Sony by the end 0:09:40.240 --> 0:09:45.560 um Also in that month, February, the Lawrence Livermore National 0:09:45.640 --> 0:09:49.280 Laboratory an nounced they had produced fusion power using high 0:09:49.360 --> 0:09:52.360 powered lasers. And only that, but they got more energy 0:09:52.440 --> 0:09:55.640 out of the fusion fuel than was put into the 0:09:55.679 --> 0:09:58.560 fusion fuel. That's a big deal. Well, that would certainly 0:09:58.600 --> 0:10:00.560 be the goal if you're going to try to generate 0:10:01.200 --> 0:10:05.679 municipal energy of fusion exactly. And that was a tough goal, right. 0:10:05.679 --> 0:10:08.080 It was one of those things where we can achieve fusion, 0:10:08.120 --> 0:10:10.440 but we're pouring so much energy to make the reaction 0:10:10.480 --> 0:10:13.839 happen that we're on a losing end of the proposition. Now, 0:10:13.880 --> 0:10:15.640 one thing to keep in mind, this does not mean 0:10:15.640 --> 0:10:18.559 that we're suddenly gonna have fusion power plants everywhere, because 0:10:18.880 --> 0:10:22.040 the laser only reached about one percent of the fuel. 0:10:22.520 --> 0:10:24.679 So this is still a long way from becoming a 0:10:24.679 --> 0:10:27.360 new way of generating electricity. You got more energy out 0:10:27.400 --> 0:10:29.719 of it, but you were only able to consume a 0:10:29.760 --> 0:10:32.040 tiny portion of the actual fuel. So it's not an 0:10:32.080 --> 0:10:37.880 efficient system yet, but it's very encouraging. Now in March 0:10:38.160 --> 0:10:43.400 two fourteen, we get some another hacking story. Uh, Mount 0:10:43.480 --> 0:10:49.240 Cox U g X. You know why it's called Mount Cox, right, 0:10:49.280 --> 0:10:53.000 you know what the story is behind that? So Mount Cox. 0:10:53.040 --> 0:10:55.240 If you were to spell out the first three letters, 0:10:55.280 --> 0:10:59.120 you've got MT for Mount and then big upper case 0:10:59.240 --> 0:11:06.840 G for Cox. Magic the Gathering. I know, I thought 0:11:06.880 --> 0:11:10.840 you would enjoy that, Joe. It's so magical. So wait, 0:11:10.960 --> 0:11:13.520 hold on, what does that have to do with bitcoin? Well, 0:11:13.559 --> 0:11:18.520 it's it was. It was the world's largest bitcoin exchange. Now, no, no, no, 0:11:18.559 --> 0:11:20.600 I mean, what does Magic the Gathering have to do 0:11:20.679 --> 0:11:23.360 with it? You can buy a crap ton of Magic 0:11:23.400 --> 0:11:26.640 the Gathering Cards with some bitcoin. My friend, Um, are 0:11:26.679 --> 0:11:28.800 you going to tell me that Magic the Gathering Cards 0:11:28.800 --> 0:11:31.840 are going to be the successor to Bitcoin is the 0:11:31.880 --> 0:11:35.160 next cryptocurrency? I would say that there was definitely a 0:11:35.200 --> 0:11:37.880 bartering system with Magic the Gathering Cards for a good 0:11:37.880 --> 0:11:41.079 long while before bitcoin came around. But obviously Magic the 0:11:41.080 --> 0:11:43.320 gathering is not a digital format. Hold on, you were 0:11:43.320 --> 0:11:45.600 going to tell me an event what happened to Mount goss. 0:11:45.760 --> 0:11:49.160 It's got hacked, dude, another hack. Yeah, in this case, 0:11:49.200 --> 0:11:51.319 this was a true hack. This was not a d 0:11:51.440 --> 0:11:54.760 d O S attack. This was the real deal. And 0:11:55.040 --> 0:11:59.920 the exchange completely collapsed because seven hundred fifty thousand bitcoin 0:12:00.120 --> 0:12:03.079 belonging to mountdocs customers, as well as a hundred thousand 0:12:03.120 --> 0:12:07.600 bitcoins belonging to the exchange itself, we're stolen in that. 0:12:09.200 --> 0:12:12.200 I may be misremembering, but I thought that the idea 0:12:12.200 --> 0:12:17.559 of bitcoin was sold as an unhackable solution. You are correct, sir. Uh. 0:12:17.600 --> 0:12:20.520 The idea was that it was it had security measures 0:12:20.559 --> 0:12:22.960 in place that would prevent you from being able to 0:12:23.000 --> 0:12:26.120 do something like spend the same bitcoin more than once, 0:12:26.520 --> 0:12:30.360 because that's obviously a concern with any digital format. Obviously, 0:12:30.400 --> 0:12:33.319 if I give you a digital file, let's say it's 0:12:33.440 --> 0:12:36.640 music file, and you think this the song is pretty awesome, 0:12:36.679 --> 0:12:38.400 I'd like to share this with all my friends. You 0:12:38.440 --> 0:12:40.600 could copy it as many times as you wanted and 0:12:40.640 --> 0:12:43.480 send as many copies as you wanted to everyone, or 0:12:43.559 --> 0:12:46.280 you could upload a copy and everyone else could end 0:12:46.360 --> 0:12:48.640 up grabbing that copy from the cloud, and they all 0:12:48.679 --> 0:12:50.959 have a copy of that song. What happens when your 0:12:50.960 --> 0:12:53.839 money is in this format? But bitcoin is supposed to 0:12:53.880 --> 0:12:56.120 be made in such a way that it's impossible to steal. 0:12:56.160 --> 0:13:00.280 It's impossible to to spend more than one bitcoin. Are 0:13:00.320 --> 0:13:03.000 it's impossible to spend the same bitcoin more than once 0:13:03.120 --> 0:13:05.400 at a time, I mean, unless it eventually made its 0:13:05.400 --> 0:13:07.440 way back to you. But it's a little complex the 0:13:07.480 --> 0:13:12.240 way the bitcoin transactions work at any rate. Um. The 0:13:13.080 --> 0:13:16.160 people behind bitcoin were saying this was due to faulty 0:13:16.240 --> 0:13:18.520 security at Mount Cox. It had nothing to do with 0:13:18.600 --> 0:13:22.720 the format of the bitcoins themselves. They were it was 0:13:22.760 --> 0:13:26.000 like saying, you can't fault a dollar for being stolen 0:13:26.040 --> 0:13:29.680 from a bank. Like if if if thieves come into 0:13:29.679 --> 0:13:32.280 a bank and they breach a bank security, it's not 0:13:32.360 --> 0:13:36.040 the fault of the currency within it. Well then, I 0:13:36.080 --> 0:13:39.200 mean that doesn't really matter to the average person using bitcoin. 0:13:39.840 --> 0:13:42.959 Stuff can still be hacked. Yeah, that was the problem. 0:13:43.000 --> 0:13:47.000 Was that the issue. The bottom issue is that this 0:13:47.320 --> 0:13:51.320 exchange still collapsed, and another one, a smaller one called 0:13:51.320 --> 0:13:55.000 flex Coin, just a week later also went billy up 0:13:55.040 --> 0:13:58.960 after after being targeted and thieves attacked them and stole 0:13:59.160 --> 0:14:02.800 bitcoins from them. So for a while people were wondering 0:14:02.800 --> 0:14:04.280 if this was going to be the beginning of the 0:14:04.400 --> 0:14:09.280 end of the cryptocurrency, but it's stuck around, So spoiler 0:14:09.280 --> 0:14:12.200 alert for later in the year. Also in March, Edwards 0:14:12.240 --> 0:14:16.400 Snowdon addressed the south By Southwest Interactive Conference via streaming 0:14:16.640 --> 0:14:20.400 because he's still a wanted man UH to talk about 0:14:20.400 --> 0:14:22.720 the need for better encryption systems in the era of 0:14:22.760 --> 0:14:26.720 digital surveillance. Yeah, he's saying, hey, look, here's the deal. 0:14:26.920 --> 0:14:29.040 People are spying on you one way or the other. 0:14:29.120 --> 0:14:32.000 Maybe it's a company, maybe it's a government, maybe it's hackers, 0:14:32.520 --> 0:14:34.640 but people are looking at your stuff. They might not 0:14:34.720 --> 0:14:37.680 be actively looking at your stuff. They might be gathering 0:14:37.760 --> 0:14:40.000 your stuff and then one day down the road they 0:14:40.040 --> 0:14:43.360 might look at exactly. It could be one of those 0:14:43.360 --> 0:14:47.160 things where someone gets this notion to search for a 0:14:47.200 --> 0:14:50.720 particular search term and it pulls up all interactions between 0:14:50.760 --> 0:14:54.040 people who use that search term in some way. Maybe 0:14:54.080 --> 0:14:56.560 you're one of those people. So maybe what we need 0:14:56.600 --> 0:14:58.480 to do is really look at some good ways to 0:14:58.640 --> 0:15:02.920 encrypt communications so only the person who who only the 0:15:02.920 --> 0:15:06.520 people communicating are the ones who have access to that info. Um, 0:15:06.720 --> 0:15:09.080 so it was a very interesting thing that he was 0:15:09.120 --> 0:15:14.520 actually virtually At south By Southwest also in March, IBM 0:15:14.560 --> 0:15:17.760 showed off the power of artificial intelligence at south By 0:15:17.760 --> 0:15:20.960 Southwest using a food truck in which the cooks prepared 0:15:21.000 --> 0:15:25.040 food based off recipes made by an artificially intelligent program. 0:15:25.960 --> 0:15:28.920 Huh yeah, users would put in did not read about 0:15:28.960 --> 0:15:30.880 this at the time. It's kind of silly, but users 0:15:30.920 --> 0:15:33.240 would put in a few preferences about what they liked 0:15:33.480 --> 0:15:36.880 as food. The program would then essentially had a database 0:15:36.920 --> 0:15:40.920 of recipes and based upon your preferences, would suggest, uh, 0:15:41.000 --> 0:15:45.000 something interesting based on that, and then the cooks, the 0:15:45.080 --> 0:15:48.400 human cooks inside the food truck, would actually make your meals. 0:15:48.400 --> 0:15:50.520 So it's not like a robot was cooking your food. 0:15:50.680 --> 0:15:52.160 It was just choosing what it was you were going 0:15:52.200 --> 0:15:55.040 to eat, and obviously couldn't be I would love to 0:15:55.080 --> 0:15:57.720 see all the ways that went wrong. Yeah, I don't know, 0:15:58.360 --> 0:16:01.440 I don't know how el why did you put cinnamon 0:16:01.520 --> 0:16:05.360 sticks on this piech Yeah? All right? Uh. There was 0:16:05.400 --> 0:16:08.320 certainly not an unlimited choice. Obviously, they were limited to 0:16:08.360 --> 0:16:11.120 whatever things they could prepare in that food truck. But 0:16:11.120 --> 0:16:14.600 it was an interesting approach um and you know, just 0:16:14.880 --> 0:16:18.120 showing that Watson can win at Jeopardy as well as 0:16:18.200 --> 0:16:22.200 cook you a decent meal. Uh. The United States government 0:16:22.240 --> 0:16:25.840 in March asked the Internet Corporation for assigned names numbers 0:16:25.840 --> 0:16:29.320 that's called I CAN to come up with a transition 0:16:29.360 --> 0:16:32.080 plan for the US to relinquish control of the Internet. 0:16:32.400 --> 0:16:34.760 So this was essentially saying, when I say control of 0:16:34.760 --> 0:16:39.080 the Internet, I really mean, uh, the whole naming convention 0:16:39.160 --> 0:16:40.920 being in charge of all that kind of stuff that 0:16:40.960 --> 0:16:43.400 all fell under the purview of the US. Does that 0:16:43.440 --> 0:16:46.560 originally go back to DARPA? Yeah, yeah, I mean I 0:16:46.600 --> 0:16:49.800 know the Internet does, but the naming conventions, well, well yeah, 0:16:49.840 --> 0:16:53.080 because it was the it was the founders of Essentially, 0:16:53.080 --> 0:16:55.240 it was the people working on our ponnet who came 0:16:55.280 --> 0:16:58.160 up with the protocols that the Internet would end up following, 0:16:58.680 --> 0:17:02.400 and it was through their work that, uh, the rules 0:17:02.520 --> 0:17:05.960 were set like this is how we named things, and 0:17:06.359 --> 0:17:09.080 uh it kind of evolved from there. So it's more 0:17:09.160 --> 0:17:12.480 like the roots of this can be traced back to DARPA. 0:17:12.680 --> 0:17:15.440 Maybe not direct, not a direct line in the sense 0:17:15.520 --> 0:17:18.240 of it was exactly the same way, but yes, it 0:17:18.320 --> 0:17:21.719 certainly does go back there. Uh. And in March that's 0:17:21.760 --> 0:17:25.320 when Sony announced Project Morpheus, which is a VR headset 0:17:25.400 --> 0:17:28.359 kind of a competitor to the Oculus Rift, although the 0:17:28.359 --> 0:17:31.879 Oculus Rift has been uh is being developed just for 0:17:31.960 --> 0:17:36.000 computer systems, not for consoles, whereas the Morpheus would presumably 0:17:36.040 --> 0:17:38.760 work with the PlayStation. Now, wait a minute, did Sony 0:17:38.760 --> 0:17:42.520 by the Oculus Rift? No? Facebook did. Facebook. That's right. 0:17:43.480 --> 0:17:46.960 Facebook bought Oculus, which was a big you know, that's 0:17:46.960 --> 0:17:48.880 a big head scratcher for a lot of people saying, well, 0:17:48.880 --> 0:17:51.239 this is kind of weird, and uh, it was one 0:17:51.280 --> 0:17:54.479 of those things that experienced three hundred and sixty degrees 0:17:54.520 --> 0:17:57.000 of annoying people on your news feed. It was also 0:17:57.080 --> 0:18:01.880 what caused uh the mo Yang found a Remojang founder, Notch, 0:18:01.920 --> 0:18:04.880 the guy who created Minecraft, to say, well, that means 0:18:04.880 --> 0:18:08.480 Minecraft is not coming to the Oculus Rift because he 0:18:08.520 --> 0:18:11.560 didn't like Facebook at all. He later said that maybe 0:18:11.600 --> 0:18:14.480 he was being a little reactionary, but he was just like, 0:18:14.600 --> 0:18:17.440 I don't like Facebook's privacy policies, I don't like how 0:18:17.720 --> 0:18:21.199 they make you know, they make people their product, and 0:18:21.240 --> 0:18:24.159 I'm not not crazy about developing Minecraft for them. So 0:18:25.240 --> 0:18:27.120 not that not that that matters, but we'll get to that. 0:18:27.840 --> 0:18:32.080 So we've we've got another next generation VR headset in 0:18:32.119 --> 0:18:35.640 the works. Yeah, yeah, and uh, have you has anybody 0:18:35.680 --> 0:18:37.960 tried these out yet? I haven't read I've tried the 0:18:37.960 --> 0:18:40.879 Oculus No, no, no, I mean the Morpheus. Oh no, 0:18:41.040 --> 0:18:43.399 it hasn't it's still I think in the pro type stage. 0:18:44.000 --> 0:18:47.320 It hasn't been released yet. Have you tried a VR headset, 0:18:47.359 --> 0:18:49.960 like a recent one, not a recent one. I tried 0:18:50.000 --> 0:18:53.640 one in the nineties, which when they were pretty funny. Yeah, 0:18:53.720 --> 0:18:57.520 the the polygon pterodactyls and stuff. Yeah, and I I 0:18:57.600 --> 0:19:00.680 did that too. I tried an Oculus Rift the first time. 0:19:00.720 --> 0:19:02.840 I've got a friend who works for Google and he 0:19:02.880 --> 0:19:05.360 had an Oculus Rift developer kit. So I went over 0:19:05.400 --> 0:19:08.800 to his house and tried it out and was almost 0:19:08.800 --> 0:19:13.400 immediately completely disoriented and feeling sick to my stife. So 0:19:13.440 --> 0:19:15.000 I said, all right, I'm done with this. He's like, 0:19:15.040 --> 0:19:16.959 don't you want to try? And this was this was 0:19:17.119 --> 0:19:20.240 the programming gaming was literally you're walking around a villa 0:19:21.240 --> 0:19:23.920 and like it's like a it's like a virtual villa 0:19:24.000 --> 0:19:27.520 in Italy, So so you think, like then there's nothing 0:19:27.520 --> 0:19:31.560 going on, It's just you're just just walking through a villa, 0:19:31.760 --> 0:19:34.119 like there's no mafia hits going on in the lawn, 0:19:34.200 --> 0:19:37.320 nothing like that. And um and so I did that, 0:19:37.400 --> 0:19:39.440 and just that alone was enough to make me feel 0:19:39.440 --> 0:19:43.200 a little like I'm feeling a little swimmy lucy goosey weird. 0:19:43.480 --> 0:19:45.320 And part of it was because the control scheme right, 0:19:45.480 --> 0:19:47.520 like I could move my head and that would change 0:19:47.520 --> 0:19:49.720 my perspective, but I still had to use a controller 0:19:49.760 --> 0:19:52.560 to move around, and it was that disconnect that was 0:19:52.640 --> 0:19:55.240 causing some issues. Maybe if you had it with a 0:19:55.640 --> 0:19:59.240 one of those in place treadmills, the gaming treadmill, sure 0:19:59.359 --> 0:20:01.520 that might that might have helped a little bit. But 0:20:01.560 --> 0:20:03.000 it was funny because he said, don't you want to 0:20:03.040 --> 0:20:06.879 try the space ship game that I have that you 0:20:06.880 --> 0:20:09.440 can run. I'm like, no, do you want your computer 0:20:09.480 --> 0:20:12.120 to be covered and my lunch? Because that's what's gonna 0:20:12.119 --> 0:20:15.080 happen if we try that. So but moving on, We've 0:20:15.080 --> 0:20:18.520 got another hacker story for April two thousand fourteen. That's 0:20:18.520 --> 0:20:22.040 when the heart bleed bug is discovered in certain versions 0:20:22.160 --> 0:20:25.919 of the open s s L software, which is a 0:20:25.960 --> 0:20:29.800 secure socket layer software. It's meant to provide that secure 0:20:29.960 --> 0:20:33.480 or what you assume is a secure connection between your 0:20:33.600 --> 0:20:36.639 browser and some other websites. So things like banking sites 0:20:37.000 --> 0:20:39.480 use this. Lots of sites use this. I mean you know, 0:20:39.520 --> 0:20:43.679 if you see like HTTPS, that's a type of the 0:20:43.800 --> 0:20:48.040 secure software. Not everyone uses the specific type to to 0:20:48.240 --> 0:20:50.680 do that, but it is one of the very popular ones. 0:20:51.160 --> 0:20:53.280 They discovered that in one version of it, there was 0:20:53.320 --> 0:20:57.800 this bug that could potentially allow attackers to access information 0:20:57.840 --> 0:21:00.639 that could include sensitive material. It all was information that 0:21:00.680 --> 0:21:05.920 was stored in UM random access memory, so it wasn't everything. 0:21:06.000 --> 0:21:08.080 It was just a certain number of characters in the 0:21:08.080 --> 0:21:11.840 way it worked was that, uh, if I send you 0:21:12.080 --> 0:21:14.560 let's let's say that that we're gonna represent Joe, you 0:21:14.640 --> 0:21:17.840 and I what happened with his heart lead bug. Okay, 0:21:17.880 --> 0:21:21.119 I'm so I'm going to send out a message just 0:21:21.320 --> 0:21:24.640 to make sure you are listening to me, and you 0:21:24.680 --> 0:21:27.640 have to repeat back that message to me in order 0:21:27.680 --> 0:21:29.560 to prove that you are listening to me, and then 0:21:29.600 --> 0:21:32.560 everything's cool and we can keep on going. So when 0:21:32.560 --> 0:21:35.320 I send out that message to you, it is a 0:21:35.320 --> 0:21:38.640 certain number of characters long. Let's say it's twenty characters long. 0:21:38.920 --> 0:21:40.800 So you get it and you see this twenty characters long. 0:21:40.840 --> 0:21:42.480 So you know that's how long the message has to be. 0:21:42.720 --> 0:21:45.120 So you repeat the message, it's twenty characters long, send 0:21:45.119 --> 0:21:47.679 it back to me. Now, let's say I send you 0:21:47.720 --> 0:21:51.920 a message and it's twenty characters long, but the package 0:21:51.960 --> 0:21:56.040 says it's actually five characters long. Now, you, being a 0:21:56.119 --> 0:21:59.479 dumb dumb can't tell the difference between twenty and five hundred. 0:21:59.480 --> 0:22:02.440 You you see the twenty characters that are the beginning 0:22:02.520 --> 0:22:06.840 of this supposed character message. But now there's all this 0:22:06.880 --> 0:22:10.560