WEBVTT - TechStuff Classic: The Internet of Things

0:00:04.120 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.200 --> 0:00:13.680
<v Speaker 1>stuff works dot com. Hey there, and welcome to tech Stuff.

0:00:13.720 --> 0:00:16.720
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:16.760 --> 0:00:18.759
<v Speaker 1>how Stuff Works, and I heart radio and I love

0:00:18.880 --> 0:00:22.520
<v Speaker 1>all things tech. And today it's time for another classic

0:00:22.560 --> 0:00:26.800
<v Speaker 1>episode of tech Stuff. This episode originally published on May nine,

0:00:26.800 --> 0:00:30.880
<v Speaker 1>two thousand twelve. And boy howdy, this is gonna be

0:00:30.960 --> 0:00:33.680
<v Speaker 1>a doozy of one to listen to. It is the

0:00:33.720 --> 0:00:39.720
<v Speaker 1>Internet of Things episode, so that's changed a lot since

0:00:39.760 --> 0:00:43.879
<v Speaker 1>two thousand twelve. I think it will be quaint to

0:00:44.120 --> 0:00:47.839
<v Speaker 1>hear how Chris and I interpreted the Internet of Things

0:00:48.080 --> 0:00:51.920
<v Speaker 1>seven years ago. Hope you guys enjoy. Let's listen in

0:00:52.320 --> 0:00:56.480
<v Speaker 1>a while ago about maybe almost twenty years ago. Is

0:00:56.600 --> 0:01:02.640
<v Speaker 1>is mid nineties? Yeah, Uh, listened to the founder of

0:01:02.760 --> 0:01:06.240
<v Speaker 1>mind Spring Enterprises, which was an Internet service provider here

0:01:06.280 --> 0:01:08.240
<v Speaker 1>in the United States. His name is Charles Brewer, and

0:01:08.240 --> 0:01:12.800
<v Speaker 1>he was talking about how in the future, um, and

0:01:12.840 --> 0:01:15.600
<v Speaker 1>he wasn't talking distant future, you know, he was talking

0:01:15.760 --> 0:01:18.960
<v Speaker 1>realistically in the next few years. He was saying in

0:01:19.000 --> 0:01:22.880
<v Speaker 1>the mid nineties, uh, that you would have stuff in

0:01:22.880 --> 0:01:25.319
<v Speaker 1>your house. It wouldn't just be you connecting to the

0:01:25.360 --> 0:01:29.720
<v Speaker 1>Internet to use email or the web. He said, in

0:01:29.840 --> 0:01:32.640
<v Speaker 1>the next few years, your stuff is going to be

0:01:32.680 --> 0:01:34.640
<v Speaker 1>connected to the Internet and it's going to talk to

0:01:34.680 --> 0:01:38.240
<v Speaker 1>one another. And you know, he was talking about appliances

0:01:38.280 --> 0:01:40.759
<v Speaker 1>and things, and I thought, well, that's kind of weird.

0:01:41.000 --> 0:01:44.080
<v Speaker 1>I mean, how would you do that. Um, of course,

0:01:44.160 --> 0:01:47.200
<v Speaker 1>at the time, we were still in a very dial

0:01:47.319 --> 0:01:49.840
<v Speaker 1>up world where you had to have a modem attached

0:01:49.880 --> 0:01:52.160
<v Speaker 1>to your computer or built into your computer that dialed

0:01:53.080 --> 0:01:55.760
<v Speaker 1>over the phone line and would you know, connect to

0:01:55.760 --> 0:01:58.000
<v Speaker 1>the Internet. And it was very slow and it was

0:01:58.080 --> 0:02:01.280
<v Speaker 1>very spotty, and you know, it worked pretty well. But

0:02:02.160 --> 0:02:04.200
<v Speaker 1>I thought, well that that would be kind of cool,

0:02:05.000 --> 0:02:07.560
<v Speaker 1>and it seemed, uh, you know, of course it's not

0:02:07.680 --> 0:02:11.320
<v Speaker 1>jet jet packs and uh, hoverboards, but it was at

0:02:11.320 --> 0:02:13.280
<v Speaker 1>the same time, you know, kind of far off in

0:02:13.320 --> 0:02:16.480
<v Speaker 1>my head because I was thinking, I don't you know,

0:02:16.680 --> 0:02:18.680
<v Speaker 1>I guess people would adopt that. I don't know, it

0:02:18.680 --> 0:02:21.280
<v Speaker 1>seems kind of cool to me. Well, as it turns out,

0:02:21.560 --> 0:02:24.959
<v Speaker 1>we really have moved on to that kind of a model,

0:02:24.960 --> 0:02:29.079
<v Speaker 1>although we're not quite there yet. But this is what

0:02:29.120 --> 0:02:34.320
<v Speaker 1>people call the Internet of Things. And the reason we're

0:02:34.320 --> 0:02:38.840
<v Speaker 1>talking about this is that actually was contacted by a

0:02:38.840 --> 0:02:43.639
<v Speaker 1>alien intelligence Yes, but that is not what I was

0:02:43.680 --> 0:02:46.720
<v Speaker 1>going to mention. You know, now they have to visit

0:02:46.760 --> 0:02:48.799
<v Speaker 1>me again, Chris, thank you so much, because I had

0:02:48.800 --> 0:02:54.000
<v Speaker 1>plans this weekend anyway. No, I was also contacted by

0:02:53.400 --> 0:02:58.640
<v Speaker 1>a tech conference to have a panel discussion about this

0:02:58.760 --> 0:03:01.640
<v Speaker 1>very topic, the Internet of Things. I thought, well, heck,

0:03:01.639 --> 0:03:03.720
<v Speaker 1>I'm I'm already preparing for that. Why don't we make

0:03:03.760 --> 0:03:06.720
<v Speaker 1>that a podcast as well? And here we are, so

0:03:07.120 --> 0:03:10.440
<v Speaker 1>let's talk a little bit about where we are right now. So, um,

0:03:10.440 --> 0:03:13.360
<v Speaker 1>we're still not at a point where everything is talking

0:03:13.400 --> 0:03:15.480
<v Speaker 1>to everything else, and there are a few different reasons

0:03:15.480 --> 0:03:18.880
<v Speaker 1>for that. I think one of the reasons is, uh,

0:03:19.080 --> 0:03:23.200
<v Speaker 1>like Chris was saying, you know, broadband rollout was probably

0:03:23.320 --> 0:03:27.040
<v Speaker 1>a little more gradual than we had anticipated when the

0:03:27.080 --> 0:03:30.360
<v Speaker 1>futurists were first starting to think about the possibilities of

0:03:30.400 --> 0:03:33.400
<v Speaker 1>the Internet of things. But that that's less of a

0:03:33.480 --> 0:03:37.080
<v Speaker 1>problem now for a good percentage of the population of

0:03:37.080 --> 0:03:39.920
<v Speaker 1>the United States, as well as for many other countries.

0:03:40.360 --> 0:03:44.160
<v Speaker 1>Clearly it's still a problem. Not everyone has broadband internet

0:03:44.160 --> 0:03:48.000
<v Speaker 1>access now. In some cases, the information that these different

0:03:48.200 --> 0:03:51.680
<v Speaker 1>products would be sending back and forth would be very

0:03:51.760 --> 0:03:56.920
<v Speaker 1>small packets of data, so perhaps broadband access isn't as important.

0:03:57.720 --> 0:04:03.440
<v Speaker 1>I remember because nostalgic cast a slight as a slight tangent.

0:04:03.720 --> 0:04:07.320
<v Speaker 1>I remember buying uh. You may remember this to the

0:04:07.320 --> 0:04:11.240
<v Speaker 1>the age of when, um there were publications like Yahoo

0:04:11.280 --> 0:04:14.720
<v Speaker 1>Internet Life back in the nineties when and there were

0:04:14.760 --> 0:04:18.560
<v Speaker 1>books too with Internet sites on them, and you would go, Okay,

0:04:18.640 --> 0:04:20.120
<v Speaker 1>so I got this Internet thing, what am I going

0:04:20.160 --> 0:04:22.680
<v Speaker 1>to do with it? One of the things I've had

0:04:22.680 --> 0:04:27.080
<v Speaker 1>in a book was this uh drink machine that was

0:04:27.120 --> 0:04:29.960
<v Speaker 1>hooked up to the Internet and you could and this

0:04:30.080 --> 0:04:32.760
<v Speaker 1>was all text. This is not you know, pretty worldwide

0:04:32.760 --> 0:04:35.479
<v Speaker 1>web stuff. This was you would ping the machine and

0:04:35.520 --> 0:04:37.440
<v Speaker 1>it would tell you how many of each drink it

0:04:37.480 --> 0:04:40.800
<v Speaker 1>had sold that day. And I was thinking, so you

0:04:40.839 --> 0:04:44.120
<v Speaker 1>can figure out how many people within the population of

0:04:44.160 --> 0:04:47.480
<v Speaker 1>that region had diabetes? Well it was a it was

0:04:47.520 --> 0:04:50.320
<v Speaker 1>a college campus. Now, okay, so all of them. But yeah,

0:04:50.400 --> 0:04:54.839
<v Speaker 1>so we're we're talking about remember when we've talked about

0:04:54.960 --> 0:04:57.960
<v Speaker 1>the early Internet, the the places that were wired, we're

0:04:57.960 --> 0:05:03.840
<v Speaker 1>basically government facility and um educational institutions. So yes, they

0:05:04.240 --> 0:05:08.360
<v Speaker 1>broad base facilities exactly. They had broadband people in the

0:05:08.360 --> 0:05:10.680
<v Speaker 1>the Computer Science Department and why are their drink machine?

0:05:11.120 --> 0:05:13.200
<v Speaker 1>And you could pin it, you know, because why not?

0:05:14.240 --> 0:05:16.200
<v Speaker 1>That's more or less to deal And that was why

0:05:16.200 --> 0:05:19.880
<v Speaker 1>it was interesting, because why not? But yeah, I mean,

0:05:19.960 --> 0:05:23.480
<v Speaker 1>and and it can be useful looking at it today

0:05:23.680 --> 0:05:25.680
<v Speaker 1>you can have a vendor looking at it. Okay, well

0:05:25.720 --> 0:05:28.400
<v Speaker 1>we don't need to restock this one today, we don't

0:05:28.400 --> 0:05:31.840
<v Speaker 1>have to send out there. Yeah you can, you could consolidate,

0:05:32.000 --> 0:05:34.239
<v Speaker 1>but back then it was just for fun. Right today

0:05:34.279 --> 0:05:35.880
<v Speaker 1>it makes a lot of sense. Like if you own

0:05:35.920 --> 0:05:39.000
<v Speaker 1>a vending machine company and you stock those vending machines

0:05:39.400 --> 0:05:40.960
<v Speaker 1>and you are able to look at a glance and

0:05:41.040 --> 0:05:44.320
<v Speaker 1>see where you need to send a delivery person in

0:05:44.440 --> 0:05:47.640
<v Speaker 1>order to restock those machines, then you may not need

0:05:47.680 --> 0:05:51.000
<v Speaker 1>as many delivery people on your staff because you don't

0:05:51.040 --> 0:05:53.400
<v Speaker 1>have to have someone go out and physically check each machine.

0:05:53.839 --> 0:05:56.760
<v Speaker 1>And and if the machines can alert you if something's wrong,

0:05:57.160 --> 0:05:59.359
<v Speaker 1>then you know to send someone out to repair it.

0:06:00.120 --> 0:06:01.279
<v Speaker 1>There are a lot of you know, you don't have

0:06:01.320 --> 0:06:04.800
<v Speaker 1>to wait for a call from a client or happen

0:06:05.360 --> 0:06:07.279
<v Speaker 1>or for your maintenance guy to happen upon it on

0:06:07.360 --> 0:06:10.720
<v Speaker 1>a on a scheduled series of rounds. Uh yeah, there

0:06:10.720 --> 0:06:12.800
<v Speaker 1>are a lot of different reasons for it. And then

0:06:13.120 --> 0:06:16.000
<v Speaker 1>we have the consumer side, like actual consumer products, not

0:06:16.080 --> 0:06:19.960
<v Speaker 1>just you know, commercial products, huh, and the possibilities that

0:06:19.960 --> 0:06:22.839
<v Speaker 1>that holds. And they're already products out on the market

0:06:22.960 --> 0:06:27.680
<v Speaker 1>right now that have some form of network capability. Um,

0:06:28.120 --> 0:06:33.240
<v Speaker 1>they don't tend to all work together necessarily, like you

0:06:33.320 --> 0:06:38.560
<v Speaker 1>might have a bunch of independent networks within your home network.

0:06:39.080 --> 0:06:43.880
<v Speaker 1>Right So for example, you could have a you can

0:06:43.920 --> 0:06:47.760
<v Speaker 1>be purchasing your appliances from a single company and you

0:06:47.800 --> 0:06:50.159
<v Speaker 1>get a washer and a dryer, and they have this

0:06:50.200 --> 0:06:54.279
<v Speaker 1>connectivity ability so that the washer and the dryer share

0:06:54.320 --> 0:06:57.560
<v Speaker 1>information with each other. So when you put a load

0:06:57.600 --> 0:07:01.000
<v Speaker 1>of laundry in the washer and you set it to

0:07:01.040 --> 0:07:03.520
<v Speaker 1>a particular kind of setting, like let's say it's permanent press,

0:07:04.600 --> 0:07:06.320
<v Speaker 1>it sends that information to the dryer, so that the

0:07:06.400 --> 0:07:09.880
<v Speaker 1>dryer already has the proper settings ready to go when

0:07:09.880 --> 0:07:12.720
<v Speaker 1>you transfer the wash from the washer dryer, so that

0:07:12.760 --> 0:07:15.200
<v Speaker 1>way you don't have to reset the dryer settings. It's

0:07:15.240 --> 0:07:18.720
<v Speaker 1>already taken care of. Uh. It might also even send

0:07:18.760 --> 0:07:23.040
<v Speaker 1>you an alert somehow through through the internet, so that

0:07:23.080 --> 0:07:26.000
<v Speaker 1>you know when your loads laundry are done. So you

0:07:26.080 --> 0:07:28.800
<v Speaker 1>might get a ping on a smartphone or a tablet,

0:07:28.920 --> 0:07:32.280
<v Speaker 1>or your computer, or if we're going to look into

0:07:32.320 --> 0:07:35.160
<v Speaker 1>the future a little bit, your television. Because you've got

0:07:35.200 --> 0:07:38.240
<v Speaker 1>internet connected televisions out there. It's only a matter of

0:07:38.280 --> 0:07:40.239
<v Speaker 1>time before we get to a point where these internet

0:07:40.240 --> 0:07:45.440
<v Speaker 1>connected televisions have a the ability to show alerts that

0:07:45.480 --> 0:07:47.720
<v Speaker 1>are related to other appliances that are in your house.

0:07:47.720 --> 0:07:51.160
<v Speaker 1>We're not quite there yet, but that's mainly because the

0:07:51.200 --> 0:07:56.000
<v Speaker 1>approach most companies are taking is to create a proprietary

0:07:56.040 --> 0:08:02.080
<v Speaker 1>communication protocol for their products. Right so Company A's products

0:08:02.400 --> 0:08:06.640
<v Speaker 1>do not communicate with Company bees products. So unless you're

0:08:06.640 --> 0:08:11.240
<v Speaker 1>buying everything from the same company, then the the communication

0:08:11.280 --> 0:08:14.960
<v Speaker 1>protocols aren't compatible and they don't understand each other. They

0:08:14.960 --> 0:08:17.520
<v Speaker 1>can't communicate. You need to C three PO right there

0:08:17.560 --> 0:08:20.600
<v Speaker 1>in the middle, because they can speak over six million

0:08:20.640 --> 0:08:26.320
<v Speaker 1>different languages, including vaporators. One of their first jobs was anyway, um,

0:08:27.080 --> 0:08:29.040
<v Speaker 1>the point being that you know, the odds of you

0:08:29.160 --> 0:08:32.640
<v Speaker 1>finishing that quote or yeah, never tell me the odds

0:08:32.679 --> 0:08:35.240
<v Speaker 1>Many both died to bring us this podcast. So the

0:08:36.360 --> 0:08:39.640
<v Speaker 1>the the different the different networks can't really communicate with

0:08:39.640 --> 0:08:41.600
<v Speaker 1>one another. So that's kind of where we are right now.

0:08:41.679 --> 0:08:43.840
<v Speaker 1>But we do have lots of products out there, including

0:08:43.880 --> 0:08:47.960
<v Speaker 1>ones like refrigerators that can talk to stoves and ovens.

0:08:48.000 --> 0:08:50.880
<v Speaker 1>So you've got again from the same company. So you

0:08:50.960 --> 0:08:53.520
<v Speaker 1>might have a refrigerator that's Internet connected and you think, well,

0:08:53.520 --> 0:08:56.040
<v Speaker 1>why would I want that? Well, if you have a

0:08:56.360 --> 0:08:59.319
<v Speaker 1>fridge that connects to the internet and it actually is

0:08:59.400 --> 0:09:02.360
<v Speaker 1>able to keep an inventory of the stuff that you

0:09:02.440 --> 0:09:05.600
<v Speaker 1>put within that fridge, you know, if there's some method

0:09:06.320 --> 0:09:08.840
<v Speaker 1>whether you know you want it to be as seamless

0:09:08.880 --> 0:09:11.440
<v Speaker 1>as possible, Ideally you would have a method in there

0:09:11.480 --> 0:09:14.440
<v Speaker 1>where when you put something in the fridge, it automatically

0:09:14.480 --> 0:09:17.520
<v Speaker 1>detected its presence, knew what it was, and logged it

0:09:18.480 --> 0:09:21.440
<v Speaker 1>so it would know when you put it in there, uh,

0:09:21.480 --> 0:09:24.440
<v Speaker 1>and it would know what it was, and even in

0:09:24.480 --> 0:09:27.800
<v Speaker 1>a real ideal situation, it would know when that product expires,

0:09:28.240 --> 0:09:30.000
<v Speaker 1>so it could tell you like, hey, you've got some

0:09:30.040 --> 0:09:31.880
<v Speaker 1>milk in the fridge. It's about to go bad because

0:09:31.880 --> 0:09:34.240
<v Speaker 1>it's muscling up to the potato salad, So you want

0:09:34.240 --> 0:09:37.000
<v Speaker 1>to make sure you're gonna go ahead and drink that. Um,

0:09:37.040 --> 0:09:39.560
<v Speaker 1>So just don't walk in on the mayonnaise. It's dressing.

0:09:39.640 --> 0:09:43.400
<v Speaker 1>That's right, boy. We were definitely punchy. We recorded an

0:09:43.400 --> 0:09:46.440
<v Speaker 1>episode that had more bloopers in it than the previous

0:09:46.920 --> 0:09:51.160
<v Speaker 1>the previous three years of recording combined, so we're all

0:09:51.240 --> 0:09:54.320
<v Speaker 1>punchy now. But anyway, Yeah, the fridge would be able

0:09:54.360 --> 0:09:56.880
<v Speaker 1>to keep you alert on what you have in your fridge.

0:09:56.920 --> 0:10:00.920
<v Speaker 1>It could even give you recipes for off that you

0:10:00.960 --> 0:10:03.760
<v Speaker 1>can make based upon what is in the refrigerator right now.

0:10:03.840 --> 0:10:06.040
<v Speaker 1>So for example, you might think, well, why am I

0:10:06.040 --> 0:10:07.760
<v Speaker 1>gonna have for dinner tonight and you could ask You

0:10:07.760 --> 0:10:10.320
<v Speaker 1>could ask your refrigerator and they could say, well, based

0:10:10.360 --> 0:10:12.760
<v Speaker 1>upon what you've got in the fridge, this is the

0:10:12.800 --> 0:10:15.120
<v Speaker 1>kind of stuff you can make. Or it may say

0:10:15.200 --> 0:10:17.720
<v Speaker 1>you could have this meal. You just need to go

0:10:17.760 --> 0:10:22.120
<v Speaker 1>out and buy this, this, and this, so the ingredients

0:10:22.120 --> 0:10:26.600
<v Speaker 1>are complete. And and with the possibility of purchasing stuff online,

0:10:27.360 --> 0:10:31.600
<v Speaker 1>you could even get to a point where you you

0:10:31.600 --> 0:10:35.839
<v Speaker 1>you authorize through your fridge purchases. Well, and and that's

0:10:35.880 --> 0:10:39.120
<v Speaker 1>the the Well, there are two sort of things that

0:10:39.160 --> 0:10:41.839
<v Speaker 1>are occurring to me to sort of funny things. Um.

0:10:41.960 --> 0:10:44.000
<v Speaker 1>One of which is there's no reason we can't do

0:10:44.040 --> 0:10:46.520
<v Speaker 1>this right now or or really a couple of years ago.

0:10:46.640 --> 0:10:50.400
<v Speaker 1>It's just we haven't UM, so it's not it's not

0:10:50.480 --> 0:10:54.800
<v Speaker 1>a technology that we're waiting for it to develop. Um.

0:10:54.840 --> 0:10:57.000
<v Speaker 1>This is all pretty simple stuff really when you get

0:10:57.080 --> 0:10:59.280
<v Speaker 1>right down to it. UM. The other the other promise,

0:10:59.600 --> 0:11:02.920
<v Speaker 1>I mean, this really could be a very convenient thing

0:11:02.960 --> 0:11:06.160
<v Speaker 1>if they go forward with it, because it's the kind

0:11:06.160 --> 0:11:07.920
<v Speaker 1>of thing that you're you're talking about that would make

0:11:08.120 --> 0:11:11.480
<v Speaker 1>life really easy if you have the money to buy

0:11:11.520 --> 0:11:14.040
<v Speaker 1>this kind of stuff and the services available to you.

0:11:14.080 --> 0:11:17.920
<v Speaker 1>So let's say you have, UM, your internet connected fridge

0:11:18.080 --> 0:11:21.800
<v Speaker 1>and the services necessary to complete this conversation. So you

0:11:21.920 --> 0:11:23.920
<v Speaker 1>got stuff in the fridge and some of it's starting

0:11:23.960 --> 0:11:26.960
<v Speaker 1>to expire, and you've used some of it. So uh,

0:11:27.000 --> 0:11:30.440
<v Speaker 1>there are f I D tags radio frequency identification tags

0:11:30.520 --> 0:11:35.120
<v Speaker 1>on your things. So you have UM milk and uh,

0:11:35.480 --> 0:11:38.280
<v Speaker 1>you have cheese and things like that, and as you

0:11:38.400 --> 0:11:41.240
<v Speaker 1>use it up, the fridge realizes, hey, it's no longer

0:11:41.280 --> 0:11:45.320
<v Speaker 1>in the fridge. UM, So I'm going to Uh. Jonathan

0:11:45.320 --> 0:11:47.640
<v Speaker 1>has already said that he wants more milk as soon

0:11:47.679 --> 0:11:49.240
<v Speaker 1>as he runs out of milk. So I'm going to

0:11:49.360 --> 0:11:53.160
<v Speaker 1>place an order with the local shopping delivery company and

0:11:53.160 --> 0:11:55.720
<v Speaker 1>they're just gonna bring Jonathan more milk. And they're gonna

0:11:55.720 --> 0:11:57.400
<v Speaker 1>build it to his card, so he gets a regular

0:11:57.440 --> 0:12:02.400
<v Speaker 1>delivery of milk because he's out and uh, the fridge

0:12:02.400 --> 0:12:06.480
<v Speaker 1>has automatically told his local delivery company, Hey, uh, he

0:12:06.559 --> 0:12:09.600
<v Speaker 1>needs milk and celery and other stuff you know that

0:12:09.640 --> 0:12:11.920
<v Speaker 1>he's run out of or he wants to make this

0:12:11.920 --> 0:12:15.960
<v Speaker 1>this meal. Um. So really this could be ultra convenient

0:12:16.000 --> 0:12:18.600
<v Speaker 1>because you could just have stuff show up, go ahead

0:12:18.600 --> 0:12:20.679
<v Speaker 1>and put it in the fridge, and it just runs

0:12:20.679 --> 0:12:22.320
<v Speaker 1>on a normal cycle like that, so you don't have

0:12:22.360 --> 0:12:24.920
<v Speaker 1>to make shopping trips and uh, you don't have to

0:12:24.920 --> 0:12:27.280
<v Speaker 1>look through the fridge to identify what you're gonna eat.

0:12:27.520 --> 0:12:30.600
<v Speaker 1>But that's all sort of well what if, because in

0:12:30.679 --> 0:12:34.480
<v Speaker 1>the in the nineties, when um, these types of delivery

0:12:34.520 --> 0:12:38.360
<v Speaker 1>services we're starting to take off, it was kind of

0:12:38.360 --> 0:12:41.240
<v Speaker 1>early for them to do so. And I think it's

0:12:41.240 --> 0:12:43.160
<v Speaker 1>scared a lot of people, which is why you don't

0:12:43.320 --> 0:12:45.240
<v Speaker 1>they're they're sort of hit or missed. They're in some

0:12:45.320 --> 0:12:47.600
<v Speaker 1>places but not another's. They're in the neighborhood down the street,

0:12:47.600 --> 0:12:52.040
<v Speaker 1>but they won't deliver to your house. Back in the day,

0:12:52.080 --> 0:12:55.480
<v Speaker 1>they expanded too quickly. They got they got so large

0:12:55.520 --> 0:12:59.400
<v Speaker 1>that they weren't able to uh to handle their own

0:12:59.800 --> 0:13:02.480
<v Speaker 1>the they weren't able to administrate the size of the

0:13:02.520 --> 0:13:05.320
<v Speaker 1>company and so as a result, they eventually collapsed in

0:13:05.480 --> 0:13:08.000
<v Speaker 1>on themselves. Because it's not a cheap business to be in.

0:13:08.600 --> 0:13:10.560
<v Speaker 1>You know, it's a lot of warehouse management, a lot

0:13:10.559 --> 0:13:15.240
<v Speaker 1>of deliveries. Uh, it's it's a tricky business. But also

0:13:15.559 --> 0:13:18.320
<v Speaker 1>I was going to mention that the other possibilities, So

0:13:18.320 --> 0:13:20.640
<v Speaker 1>we would talk you mainly about just the fridge interacting

0:13:20.640 --> 0:13:22.760
<v Speaker 1>with the Internet, but it could also interact with the

0:13:22.800 --> 0:13:26.720
<v Speaker 1>other appliances in your home, for example, your stove. So

0:13:27.080 --> 0:13:28.920
<v Speaker 1>let's say that you have determined that you know, the

0:13:28.920 --> 0:13:32.160
<v Speaker 1>fridge is suggested, Hey you've got the right ingredients here

0:13:32.160 --> 0:13:36.440
<v Speaker 1>for a pot roast. Uh, and heck, you can even

0:13:36.440 --> 0:13:40.120
<v Speaker 1>have a crock pot that has Internet connectivity. And so

0:13:40.720 --> 0:13:43.560
<v Speaker 1>it starts the it starts the croc pot heating up

0:13:43.600 --> 0:13:45.439
<v Speaker 1>at the right time so that you just all you

0:13:45.480 --> 0:13:48.320
<v Speaker 1>do is dump them the ingredients into it and you

0:13:48.440 --> 0:13:52.440
<v Speaker 1>and you walk away. Um, or you have you wanna

0:13:52.600 --> 0:13:56.680
<v Speaker 1>you wanna end up like baking something, and so it

0:13:56.800 --> 0:13:59.600
<v Speaker 1>ends up sending that information to the oven when you're prepared,

0:14:00.120 --> 0:14:02.559
<v Speaker 1>so that way the oven starts to preheat while you're

0:14:02.559 --> 0:14:04.559
<v Speaker 1>actually getting your ingredients together, and you never had to

0:14:04.600 --> 0:14:08.120
<v Speaker 1>go and turn anything on yourself. It's all controlled because

0:14:08.840 --> 0:14:11.559
<v Speaker 1>the devices themselves are aware of what it is you're

0:14:11.559 --> 0:14:14.439
<v Speaker 1>trying to do. So this is sort of the promise

0:14:14.520 --> 0:14:16.800
<v Speaker 1>of the Internet of things in general. But you know

0:14:16.840 --> 0:14:18.800
<v Speaker 1>what we're talking about appliance is that the reason why

0:14:18.840 --> 0:14:21.040
<v Speaker 1>we're talking about that is because those are things that

0:14:21.080 --> 0:14:23.240
<v Speaker 1>exist on the market right now. The same sort of

0:14:23.280 --> 0:14:27.360
<v Speaker 1>thing is true for experiences. If you have, say a smartphone,

0:14:27.400 --> 0:14:31.240
<v Speaker 1>a tablet, and maybe even a video game console or

0:14:31.280 --> 0:14:34.360
<v Speaker 1>set top box. Uh, you can have these sort of

0:14:34.400 --> 0:14:38.160
<v Speaker 1>experiences right now within a separate kind of network. So

0:14:38.320 --> 0:14:41.480
<v Speaker 1>let's use Netflix as an example. All right, Let's say

0:14:41.480 --> 0:14:43.600
<v Speaker 1>have a Netflix account, and I have access to a

0:14:43.600 --> 0:14:48.240
<v Speaker 1>Netflix film or television show on my smartphone, and I'm

0:14:48.280 --> 0:14:50.440
<v Speaker 1>watching it, and then I stop, you know, I pause

0:14:50.480 --> 0:14:52.840
<v Speaker 1>in the middle, and then a little bit later, I

0:14:52.840 --> 0:14:54.720
<v Speaker 1>pick up my tablet and I watch a little bit

0:14:54.720 --> 0:14:56.640
<v Speaker 1>more of it. It picks up right where it left off,

0:14:56.800 --> 0:14:58.600
<v Speaker 1>and then I pause. And then when I get home,

0:14:58.800 --> 0:15:00.800
<v Speaker 1>I turn on my TV and set top box that

0:15:00.800 --> 0:15:03.320
<v Speaker 1>happens to have Netflix capability, and I start and it

0:15:03.320 --> 0:15:05.600
<v Speaker 1>picks up again. Right where I left off, and so

0:15:05.640 --> 0:15:09.240
<v Speaker 1>this is an experience that continues and it doesn't matter

0:15:09.280 --> 0:15:13.200
<v Speaker 1>what the context is. It follows me. It's context independent,

0:15:13.600 --> 0:15:16.240
<v Speaker 1>so I don't have to worry about fast forwarding to

0:15:16.400 --> 0:15:18.560
<v Speaker 1>get to the right section, so I can pick up

0:15:18.560 --> 0:15:20.760
<v Speaker 1>where I left off. It's going to just do that automatically.

0:15:21.280 --> 0:15:24.840
<v Speaker 1>This is a really valuable experience to consumers, and it's

0:15:24.840 --> 0:15:28.680
<v Speaker 1>the sort of thing that the Internet of Things really promises,

0:15:28.760 --> 0:15:32.360
<v Speaker 1>is this idea of a seamless experience where you go

0:15:32.480 --> 0:15:35.880
<v Speaker 1>from environment to environment and the environment adjusts to you

0:15:36.240 --> 0:15:39.400
<v Speaker 1>and gives you the experience you want um based upon

0:15:39.560 --> 0:15:42.000
<v Speaker 1>whatever your preferences are, and it may be that you

0:15:42.120 --> 0:15:47.400
<v Speaker 1>have to express those preferences in a very um ordered way.

0:15:47.920 --> 0:15:50.360
<v Speaker 1>And in fact, I would guess that the early early

0:15:50.520 --> 0:15:52.840
<v Speaker 1>versions of this technology are going to require a lot

0:15:52.880 --> 0:15:55.320
<v Speaker 1>of input on our part to be to work correctly.

0:15:55.960 --> 0:15:59.120
<v Speaker 1>But future systems will have a lot of learning behaviors

0:15:59.120 --> 0:16:02.720
<v Speaker 1>built into them so that based upon your behaviors in

0:16:02.760 --> 0:16:05.600
<v Speaker 1>the past and the things that you've already done, they

0:16:05.640 --> 0:16:08.760
<v Speaker 1>can anticipate what you want in the future and start

0:16:08.800 --> 0:16:11.640
<v Speaker 1>to set things up so that they will be ideal

0:16:11.680 --> 0:16:14.600
<v Speaker 1>for you before you even are necessarily conscious of it

0:16:15.280 --> 0:16:17.320
<v Speaker 1>and UH and we're seeing some of that too, Like

0:16:17.360 --> 0:16:20.440
<v Speaker 1>the Nest thermostat is a good example. So Nest thermostat

0:16:20.560 --> 0:16:25.480
<v Speaker 1>is a programmable thermostat that has some learning algorithms in

0:16:25.520 --> 0:16:29.280
<v Speaker 1>it that can, you know, based upon the way you

0:16:29.320 --> 0:16:33.440
<v Speaker 1>adjust the thermostat throughout the day, can start to automatically

0:16:33.560 --> 0:16:37.480
<v Speaker 1>make those adjustments for you. And you can also at

0:16:37.480 --> 0:16:40.720
<v Speaker 1>any time going and manually change it, either in the

0:16:40.760 --> 0:16:43.480
<v Speaker 1>house or building yourself, or you can even access it

0:16:43.560 --> 0:16:48.320
<v Speaker 1>over the internet. So there are opportunities there for other

0:16:48.360 --> 0:16:51.640
<v Speaker 1>appliances that do similar things to to do that. And

0:16:51.680 --> 0:16:56.880
<v Speaker 1>then we've got other possibilities as well. For example, that

0:16:56.920 --> 0:16:59.720
<v Speaker 1>you you're watching TV and you see a product on

0:16:59.760 --> 0:17:02.920
<v Speaker 1>tell Vision and you know you are the ultimate impulse

0:17:02.920 --> 0:17:06.280
<v Speaker 1>buyer and you think, I want that. Well, with the

0:17:06.320 --> 0:17:08.240
<v Speaker 1>Internet of Things, you can get to a point where

0:17:08.240 --> 0:17:10.000
<v Speaker 1>and a lot of companies have been trying to do this,

0:17:10.160 --> 0:17:12.000
<v Speaker 1>figure out a way where you can if you see

0:17:12.040 --> 0:17:14.600
<v Speaker 1>something on the screen that you want, you can indicate

0:17:14.680 --> 0:17:17.760
<v Speaker 1>I want that and then go and purchase it, UH

0:17:17.920 --> 0:17:21.200
<v Speaker 1>in a very easy, seamless way so that you don't

0:17:21.240 --> 0:17:24.919
<v Speaker 1>have to open up a tablet or or smartphone application

0:17:25.160 --> 0:17:28.760
<v Speaker 1>or pop open a computer in order to say this

0:17:28.840 --> 0:17:33.320
<v Speaker 1>thing I saw on TV, I want that make that mine. Um,

0:17:33.760 --> 0:17:37.160
<v Speaker 1>my TV provider already does that to some extent. Yeah, yeah,

0:17:37.200 --> 0:17:39.480
<v Speaker 1>there's there's some of that built in. It's it's still

0:17:39.560 --> 0:17:43.480
<v Speaker 1>not widespread and it's still not truly seamless, but it's

0:17:43.480 --> 0:17:46.720
<v Speaker 1>getting better. And that's another thing where we expect to see.

0:17:47.040 --> 0:17:49.679
<v Speaker 1>But when we talk about the Internet of things, you

0:17:49.720 --> 0:17:52.439
<v Speaker 1>have to think bigger than that. Like we're still talking

0:17:52.520 --> 0:17:56.560
<v Speaker 1>appliances and and you know, entertainment centers and stuff, so

0:17:56.720 --> 0:17:59.160
<v Speaker 1>radio's TVs and computers and all that. But but this

0:17:59.200 --> 0:18:02.800
<v Speaker 1>is really about putting computers and sensors and actuators in

0:18:03.240 --> 0:18:05.920
<v Speaker 1>lots of things. We have a lot more to say

0:18:05.960 --> 0:18:08.480
<v Speaker 1>about the Internet of things, but first let's take a

0:18:08.560 --> 0:18:18.600
<v Speaker 1>quick break to thank our sponsor. Well, one of the

0:18:19.480 --> 0:18:22.719
<v Speaker 1>I would say one of the most mature Internet of

0:18:22.760 --> 0:18:27.320
<v Speaker 1>things environments is the smart home, where you've got uh,

0:18:27.359 --> 0:18:32.280
<v Speaker 1>you know, your lights, your climate control, your garage door, um,

0:18:32.280 --> 0:18:35.120
<v Speaker 1>your the locks on your front door. Sh leg link

0:18:35.200 --> 0:18:37.919
<v Speaker 1>system that you uh you wrote on that for the

0:18:38.320 --> 0:18:40.960
<v Speaker 1>for the website. I'm not there's a you know, there's

0:18:41.040 --> 0:18:44.639
<v Speaker 1>a a schleg lock article I wrote, and it was

0:18:44.680 --> 0:18:47.080
<v Speaker 1>a few years ago about a system because it was

0:18:47.119 --> 0:18:49.159
<v Speaker 1>something I saw at c e S where you could

0:18:49.800 --> 0:18:53.240
<v Speaker 1>access the lock on your front door from the internet

0:18:53.359 --> 0:18:56.159
<v Speaker 1>and from a smartphone, you could unlock your door. So

0:18:56.359 --> 0:18:59.080
<v Speaker 1>let's say that you have a repairman showing up at

0:18:59.080 --> 0:19:02.119
<v Speaker 1>a certain time, Uh, you could, uh, you can unlock

0:19:02.160 --> 0:19:03.720
<v Speaker 1>the door for that person. You can also do things

0:19:03.720 --> 0:19:06.880
<v Speaker 1>like set up pass codes, temporary pass codes that would

0:19:06.920 --> 0:19:09.480
<v Speaker 1>only work within a certain block of time and outside

0:19:09.520 --> 0:19:11.280
<v Speaker 1>of that they would no longer work. So that way,

0:19:11.320 --> 0:19:13.679
<v Speaker 1>you could give a pass code to someone so that

0:19:13.680 --> 0:19:15.480
<v Speaker 1>they could, you know, maybe walk your dogs or what

0:19:15.560 --> 0:19:17.640
<v Speaker 1>are your plants or whatever it is, and then as

0:19:17.640 --> 0:19:21.160
<v Speaker 1>soon as as soon as that time expand, it is over,

0:19:21.600 --> 0:19:25.000
<v Speaker 1>it'll just automatically lock again. So yeah, I mean that's

0:19:25.040 --> 0:19:27.119
<v Speaker 1>that's the sort of stuff that you can see in

0:19:27.119 --> 0:19:30.160
<v Speaker 1>a smart home. That and alarm systems things like that

0:19:30.200 --> 0:19:33.119
<v Speaker 1>you can you can watch um uh it's easy to

0:19:33.280 --> 0:19:35.360
<v Speaker 1>if you have the camera setup, you can see what's

0:19:35.400 --> 0:19:38.719
<v Speaker 1>going on at your home. Um. If if you're like

0:19:38.840 --> 0:19:41.359
<v Speaker 1>me and you go, did I turn on the alarm?

0:19:41.400 --> 0:19:43.760
<v Speaker 1>Did I lock the door? You can do you can

0:19:43.800 --> 0:19:45.760
<v Speaker 1>take care of it. You know, if you get down

0:19:45.840 --> 0:19:47.719
<v Speaker 1>the road, you can pull over and get on your

0:19:47.720 --> 0:19:49.399
<v Speaker 1>smartphone and make sure that you lock your door and

0:19:49.400 --> 0:19:51.560
<v Speaker 1>make sure that you turn the alarm on, UM and

0:19:51.640 --> 0:19:54.840
<v Speaker 1>maybe the stove off, you know, those kinds of things.

0:19:54.880 --> 0:19:58.360
<v Speaker 1>And that's something that that is already pretty well established

0:19:58.400 --> 0:20:01.120
<v Speaker 1>in the market. Also, U the smart meters that they've

0:20:01.160 --> 0:20:03.560
<v Speaker 1>been putting in a lot of cities where um, they

0:20:03.600 --> 0:20:05.800
<v Speaker 1>don't have to send out a meter reader to your

0:20:05.920 --> 0:20:09.240
<v Speaker 1>to check your electricity. They can check that from AFAR.

0:20:09.400 --> 0:20:12.000
<v Speaker 1>And what what's funny to me is that it didn't

0:20:12.000 --> 0:20:14.640
<v Speaker 1>move quickly enough for Google and Microsoft, who have now

0:20:14.680 --> 0:20:17.399
<v Speaker 1>shut down their services. Well, I think that was mostly

0:20:17.400 --> 0:20:20.800
<v Speaker 1>because the uh, the companies that installed the smart meters

0:20:20.800 --> 0:20:25.240
<v Speaker 1>were not willing to share with Google and Microsoft um,

0:20:25.320 --> 0:20:27.480
<v Speaker 1>and the two companies were just saying, you know what,

0:20:27.520 --> 0:20:29.920
<v Speaker 1>if you guys aren't gonna help us out, we're gonna

0:20:29.920 --> 0:20:31.680
<v Speaker 1>shot these down and we're not going to mess with

0:20:31.720 --> 0:20:34.920
<v Speaker 1>it anymore. But I think that will eventually come back.

0:20:35.640 --> 0:20:39.479
<v Speaker 1>But cars too, are our online in ways that they

0:20:39.520 --> 0:20:41.920
<v Speaker 1>hadn't been before. And and again, if we're talking about

0:20:41.920 --> 0:20:45.560
<v Speaker 1>the future, you can imagine a system, a system where

0:20:45.600 --> 0:20:50.560
<v Speaker 1>cars all have technology UH installed, whether it's retrofitted or

0:20:50.760 --> 0:20:55.840
<v Speaker 1>just off the assembly line where there are there can

0:20:55.880 --> 0:20:59.360
<v Speaker 1>be sensors like collision detection sensors and alarm systems. There

0:20:59.359 --> 0:21:03.040
<v Speaker 1>can even be override systems where UH the you know,

0:21:03.160 --> 0:21:05.679
<v Speaker 1>we've seen this with like Google self driving cars. You

0:21:05.680 --> 0:21:08.560
<v Speaker 1>can you can imagine that being incorporated into vehicles off

0:21:08.560 --> 0:21:11.640
<v Speaker 1>the line where UM if you wanted to, you could

0:21:11.680 --> 0:21:14.560
<v Speaker 1>engage it so that the car drives itself and because

0:21:14.640 --> 0:21:19.880
<v Speaker 1>as these other UH sensors, it can navigate through traffic

0:21:19.960 --> 0:21:22.960
<v Speaker 1>without there being a danger of a collision, especially if

0:21:23.000 --> 0:21:25.560
<v Speaker 1>all the other cars are also on the same system.

0:21:25.960 --> 0:21:29.040
<v Speaker 1>Then you've got a computer that can manage everything so

0:21:29.119 --> 0:21:31.640
<v Speaker 1>that you get to where you're going in the most

0:21:31.680 --> 0:21:36.080
<v Speaker 1>efficient manner possible, which would be a huge relief. You know,

0:21:36.320 --> 0:21:40.359
<v Speaker 1>theoretically you could avoid traffic jams because a lot of

0:21:40.359 --> 0:21:44.640
<v Speaker 1>traffic jams depend upon human behavior and not necessarily something

0:21:45.320 --> 0:21:48.920
<v Speaker 1>UH that's actually actively blocking the street, although that could

0:21:49.000 --> 0:21:51.280
<v Speaker 1>happen too if there were if there were an incident

0:21:51.320 --> 0:21:55.720
<v Speaker 1>where something was blocking the street, then obviously that would

0:21:55.720 --> 0:21:59.320
<v Speaker 1>still be a problem, although a really robust system could

0:21:59.440 --> 0:22:04.000
<v Speaker 1>potentially navigate around that so that the the the impact

0:22:04.080 --> 0:22:07.760
<v Speaker 1>would be minimal on traffic. Uh. And you could also

0:22:07.800 --> 0:22:11.800
<v Speaker 1>see sensors being built into the infrastructure itself, so not

0:22:11.880 --> 0:22:16.320
<v Speaker 1>just the cars, but in streets uh and in the

0:22:16.880 --> 0:22:19.840
<v Speaker 1>you know, signs, things like that, so that it could

0:22:20.240 --> 0:22:24.320
<v Speaker 1>uh there, the system itself could maintain how much traffic

0:22:24.400 --> 0:22:28.399
<v Speaker 1>is going across it on a given day, help change

0:22:28.400 --> 0:22:31.720
<v Speaker 1>things like traffic light patterns. Um. So you're talking about

0:22:32.000 --> 0:22:34.040
<v Speaker 1>a system that's much more flexible and can change on

0:22:34.080 --> 0:22:40.480
<v Speaker 1>the fly. Uh and possibly possibly helps cities like Atlanta

0:22:41.160 --> 0:22:46.720
<v Speaker 1>with their horrible, horrible traffic problems. Atlanta's way up there, guys,

0:22:46.840 --> 0:22:51.119
<v Speaker 1>Los Angeles, Atlanta. I mean, we're we're hurting, and we

0:22:51.240 --> 0:22:53.320
<v Speaker 1>we could we could use the help. So so I

0:22:53.359 --> 0:22:56.400
<v Speaker 1>had some statistics. Let me read you them all right? UM.

0:22:56.960 --> 0:22:59.239
<v Speaker 1>Actually was if you if you're interested in reading more

0:22:59.240 --> 0:23:02.080
<v Speaker 1>about the Internet Things, I would also recommend um read

0:23:02.200 --> 0:23:05.240
<v Speaker 1>right Web, which is one of my favorite tech sites anyway.

0:23:05.280 --> 0:23:08.120
<v Speaker 1>But they have a whole section on Internet of Things articles.

0:23:08.720 --> 0:23:13.000
<v Speaker 1>UM and uh they had one where they quoted statistics

0:23:13.000 --> 0:23:15.480
<v Speaker 1>from the g s M A of All People. UM.

0:23:15.560 --> 0:23:18.360
<v Speaker 1>This is an organization. Uh you might know from our

0:23:18.359 --> 0:23:22.360
<v Speaker 1>other podcasts about cell phones. Um, but they're studying how

0:23:22.400 --> 0:23:25.280
<v Speaker 1>well connected things are because well, an internet of things

0:23:25.680 --> 0:23:29.720
<v Speaker 1>would be beneficial for them because they are the kinds

0:23:29.720 --> 0:23:32.440
<v Speaker 1>of things that you would manage through a smartphone. So

0:23:32.760 --> 0:23:35.359
<v Speaker 1>it's it's definitely something that they're interested in. Um. They

0:23:35.400 --> 0:23:38.080
<v Speaker 1>said that, uh, in twenty eleven, there were about nine

0:23:38.200 --> 0:23:41.680
<v Speaker 1>billion devices connected to the internet around the world. About

0:23:41.720 --> 0:23:44.399
<v Speaker 1>six billion of them are are something that you can

0:23:44.440 --> 0:23:48.400
<v Speaker 1>carry with you. But by they expected uh twenty four

0:23:48.440 --> 0:23:53.040
<v Speaker 1>billion connected devices and about half of those would be mobile. UM.

0:23:53.240 --> 0:23:59.000
<v Speaker 1>So it's definitely something that is that is growing exponentially. UM.

0:23:59.040 --> 0:24:02.119
<v Speaker 1>But it's at the same time, it's it's one of

0:24:02.160 --> 0:24:05.159
<v Speaker 1>those things that they're they're you know, as long as

0:24:05.200 --> 0:24:07.280
<v Speaker 1>everything is working the way it's supposed to and people

0:24:07.320 --> 0:24:11.320
<v Speaker 1>are behaving themselves, it's great because it can be real

0:24:11.400 --> 0:24:14.199
<v Speaker 1>time saving. UM. It can give you opportunities to to

0:24:14.480 --> 0:24:16.960
<v Speaker 1>do other things with your time and with your money

0:24:16.960 --> 0:24:22.120
<v Speaker 1>and really improve efficiency and turn things off that don't

0:24:22.119 --> 0:24:25.399
<v Speaker 1>need to be powered on electricity. You could improve your

0:24:25.480 --> 0:24:28.960
<v Speaker 1>quality of life to all kinds of people. Yeah, and

0:24:29.119 --> 0:24:31.680
<v Speaker 1>uh so yeah, there are a lot of potential benefits.

0:24:31.720 --> 0:24:34.959
<v Speaker 1>I mean, and we're still not even finished with all

0:24:35.000 --> 0:24:38.080
<v Speaker 1>the possibilities. I mean, there could be sensors built into

0:24:38.160 --> 0:24:42.520
<v Speaker 1>clothing should tell the clothing when it's dirty and when

0:24:42.520 --> 0:24:44.680
<v Speaker 1>it needs to be washed, and it could well what

0:24:44.840 --> 0:24:46.800
<v Speaker 1>would work great until you wash it and then you

0:24:46.840 --> 0:24:48.840
<v Speaker 1>know short circuits. Well, yeah, you got you have to

0:24:48.880 --> 0:24:50.639
<v Speaker 1>build in the right kind of fabrics so that you

0:24:50.680 --> 0:24:53.000
<v Speaker 1>can wash it. But we could get to a point

0:24:53.000 --> 0:24:55.199
<v Speaker 1>where sensors are built into clothing so that when you

0:24:55.240 --> 0:24:58.240
<v Speaker 1>put them in the washer, the washer detects from the

0:24:58.280 --> 0:25:00.439
<v Speaker 1>sensors what kind of clothing they are, what kind of

0:25:00.480 --> 0:25:02.680
<v Speaker 1>cycle it needs to go through. So then you get

0:25:02.680 --> 0:25:05.480
<v Speaker 1>to a point where you know, you just need a

0:25:05.600 --> 0:25:08.119
<v Speaker 1>robot to disrobe you and put it into the washer

0:25:08.280 --> 0:25:12.040
<v Speaker 1>and other and then you don't have to do anything else. Thanks, yeah,

0:25:13.160 --> 0:25:17.280
<v Speaker 1>she needs a bonus. So the yeah, there's there are

0:25:17.280 --> 0:25:20.840
<v Speaker 1>a lot of different things that could happen. And and uh,

0:25:20.880 --> 0:25:23.520
<v Speaker 1>you know, we're talking about a point where these sensors

0:25:23.560 --> 0:25:26.399
<v Speaker 1>and these computer systems are pervasive. They need to be

0:25:26.480 --> 0:25:30.159
<v Speaker 1>both pervasive and transparent. And by that I mean for

0:25:30.200 --> 0:25:32.840
<v Speaker 1>this system to be something that works seamlessly. You don't

0:25:32.880 --> 0:25:35.000
<v Speaker 1>want to you don't want to see all the wires

0:25:35.359 --> 0:25:38.600
<v Speaker 1>what I'm getting at, So uh and and there are

0:25:38.600 --> 0:25:41.680
<v Speaker 1>a lot of companies working to kind of tackle that problem. Now,

0:25:42.080 --> 0:25:47.520
<v Speaker 1>there is another major concern that arises out of this

0:25:47.640 --> 0:25:50.760
<v Speaker 1>world of the future. Well, one of the concerns I

0:25:50.800 --> 0:25:53.080
<v Speaker 1>was thinking of. And I think it's not the one

0:25:53.080 --> 0:25:55.600
<v Speaker 1>that you're about to say, um, because I think the

0:25:55.600 --> 0:25:57.720
<v Speaker 1>other one that you're about to say is bigger. But

0:25:57.760 --> 0:26:00.800
<v Speaker 1>I mean it's, um, taking down the Internet at that

0:26:00.840 --> 0:26:05.080
<v Speaker 1>point becomes a much bigger deal, because I mean, you

0:26:05.119 --> 0:26:08.240
<v Speaker 1>see that all the time in uh, in corporate America.

0:26:08.520 --> 0:26:10.720
<v Speaker 1>You know, everybody has a computer on their desk now,

0:26:11.520 --> 0:26:14.600
<v Speaker 1>and then when something happens at the network, nobody gets

0:26:14.600 --> 0:26:17.800
<v Speaker 1>anything done. And that's going to happen when everybody gets

0:26:17.880 --> 0:26:20.560
<v Speaker 1>used to the Internet of things and suddenly there's a

0:26:20.560 --> 0:26:23.560
<v Speaker 1>network outage or power outage. I can't cook my fridge

0:26:23.560 --> 0:26:26.640
<v Speaker 1>won't tell me what to make exactly. And and yes

0:26:26.680 --> 0:26:30.320
<v Speaker 1>it's a joke, but people, once you get reliant on

0:26:30.320 --> 0:26:34.399
<v Speaker 1>that technology, when there is a glitch or a network

0:26:34.440 --> 0:26:38.120
<v Speaker 1>problem or something like that, it it throws us off. Um.

0:26:38.160 --> 0:26:40.360
<v Speaker 1>And it could you know, We've got all our traffic

0:26:40.440 --> 0:26:44.080
<v Speaker 1>lights and everything, all our traffic systems online, and oh

0:26:44.600 --> 0:26:48.000
<v Speaker 1>the power grid is overwhelmed and it shut down. Now

0:26:48.000 --> 0:26:50.879
<v Speaker 1>the internet out. That's the smart grid. See when you

0:26:50.920 --> 0:26:53.360
<v Speaker 1>have the smart grid than the power grid's fine, No, no, no,

0:26:53.400 --> 0:26:55.280
<v Speaker 1>you're you're totally right. And and of course a lot

0:26:55.320 --> 0:26:58.560
<v Speaker 1>of these systems, especially the ones that are related to infrastructure,

0:26:58.960 --> 0:27:03.440
<v Speaker 1>would bind a necessity require redundant systems that are even

0:27:03.520 --> 0:27:07.720
<v Speaker 1>if they are the old preconnected systems, there would be

0:27:07.800 --> 0:27:12.399
<v Speaker 1>necessary So for example, your smart grid traffic light system

0:27:12.480 --> 0:27:16.080
<v Speaker 1>may revert back to a pre smart grid version so

0:27:16.119 --> 0:27:18.560
<v Speaker 1>that it's still working. You know, it's still working, it's

0:27:18.560 --> 0:27:22.320
<v Speaker 1>just not it's just not flexible like it used to be. Um.

0:27:22.440 --> 0:27:24.240
<v Speaker 1>Or at least you get maybe the flashing red lights

0:27:24.280 --> 0:27:28.360
<v Speaker 1>and hopefully people treated like a four way stop in Atlanta.

0:27:28.440 --> 0:27:30.440
<v Speaker 1>That's a that's a hope that you make in Vain.

0:27:30.800 --> 0:27:33.720
<v Speaker 1>I'm to the point now where I'm not flexible like

0:27:33.760 --> 0:27:36.560
<v Speaker 1>I used to be either. No, I can't even put

0:27:36.560 --> 0:27:38.919
<v Speaker 1>on my own shoes anymore. Um. It also would be

0:27:38.920 --> 0:27:42.160
<v Speaker 1>a tantalizing target for a terrorist. And not just saying

0:27:42.160 --> 0:27:44.680
<v Speaker 1>that because it's alliterative, but it's the kind of thing

0:27:44.720 --> 0:27:47.560
<v Speaker 1>that that you know, if you're looking for a way

0:27:47.560 --> 0:27:52.680
<v Speaker 1>to disrupt people's lives and cause panic, that could do it, yeah,

0:27:52.720 --> 0:27:55.520
<v Speaker 1>if you're Yeah. Now, part of the part of the

0:27:55.560 --> 0:27:58.320
<v Speaker 1>defense of that is that the Internet is pretty darn

0:27:58.440 --> 0:28:01.600
<v Speaker 1>robust and and there are a lot of different ways

0:28:01.600 --> 0:28:04.240
<v Speaker 1>of working around problems. But if you were able to

0:28:04.240 --> 0:28:07.880
<v Speaker 1>find a way to, I don't know, inflict a widespread

0:28:08.040 --> 0:28:12.080
<v Speaker 1>virus that could, uh could come up the works, and

0:28:12.119 --> 0:28:14.679
<v Speaker 1>that could be enough to really make an impact. But

0:28:14.840 --> 0:28:16.960
<v Speaker 1>you know, trying to actually take down the Internet in

0:28:16.960 --> 0:28:20.399
<v Speaker 1>the sense of I want to target the Internet because

0:28:20.440 --> 0:28:22.560
<v Speaker 1>everyone's connected to it and if I if I shut

0:28:22.600 --> 0:28:25.679
<v Speaker 1>it down, then it's going to cause chaos. That's a

0:28:25.760 --> 0:28:28.640
<v Speaker 1>huge endeavor. I mean, that's not something that's easily done.

0:28:29.160 --> 0:28:32.160
<v Speaker 1>You know, the Internet is all around us and something

0:28:32.200 --> 0:28:35.480
<v Speaker 1>else that's all around us our ads. So we're gonna

0:28:35.480 --> 0:28:46.240
<v Speaker 1>listen to some. But yeah, the other big concern, the

0:28:46.280 --> 0:28:49.160
<v Speaker 1>major one that I think a lot of consumers should

0:28:49.200 --> 0:28:52.000
<v Speaker 1>keep in mind is privacy issues. So if you've got

0:28:52.000 --> 0:28:54.640
<v Speaker 1>an Internet of things, you've got all these sensors around you,

0:28:55.080 --> 0:28:58.280
<v Speaker 1>and you've and on you potentially um in the various

0:28:58.280 --> 0:29:01.160
<v Speaker 1>things that you're carrying or possibly even airing, well then

0:29:01.560 --> 0:29:04.600
<v Speaker 1>you could be you know, worried about your privacy because

0:29:04.640 --> 0:29:07.800
<v Speaker 1>because the same systems that can make the environment so

0:29:07.920 --> 0:29:11.280
<v Speaker 1>pleasant for us and to customize our experience in such

0:29:11.280 --> 0:29:16.240
<v Speaker 1>a way that we have the best sort of experience possible.

0:29:16.240 --> 0:29:21.800
<v Speaker 1>I mean, imagine walking through a building that automatically is

0:29:22.120 --> 0:29:25.360
<v Speaker 1>adjusting to your preferences so that the lighting is just

0:29:25.480 --> 0:29:28.200
<v Speaker 1>the way you would like it and the the ambient

0:29:28.280 --> 0:29:31.800
<v Speaker 1>noise is just what you would want. That's that's a

0:29:31.880 --> 0:29:34.880
<v Speaker 1>neat vision of the future. But it also means that

0:29:34.920 --> 0:29:37.880
<v Speaker 1>there's a system that knows that you are there. They

0:29:37.920 --> 0:29:40.080
<v Speaker 1>know when you're there, they know how long you're there,

0:29:40.120 --> 0:29:41.960
<v Speaker 1>they know when you arrived, they know where you came from,

0:29:42.000 --> 0:29:44.760
<v Speaker 1>they know where you went to. Because it's a If

0:29:44.760 --> 0:29:47.160
<v Speaker 1>it's a big system that's keeping track of all of this,

0:29:47.520 --> 0:29:50.400
<v Speaker 1>then it's keeping track of you. And as you move

0:29:50.440 --> 0:29:53.920
<v Speaker 1>around and interact with the various environments around you, there

0:29:54.000 --> 0:29:56.600
<v Speaker 1>is a record there. You are leaving a digital footprint

0:29:56.720 --> 0:30:00.480
<v Speaker 1>everywhere you go, and by necessity, that foot print has

0:30:00.520 --> 0:30:03.520
<v Speaker 1>to be identified with you on some level. It might

0:30:03.520 --> 0:30:06.160
<v Speaker 1>be a superficial level, but it has to be identified

0:30:06.200 --> 0:30:10.120
<v Speaker 1>with you because otherwise your experience isn't customized. That's the

0:30:10.160 --> 0:30:12.120
<v Speaker 1>point of doing it. Yeah, the whole point of doing

0:30:12.120 --> 0:30:15.280
<v Speaker 1>it is so that I Jonathan Strickland, as I walk

0:30:15.320 --> 0:30:18.600
<v Speaker 1>around in my life experience the best sort of outcomes

0:30:18.640 --> 0:30:23.240
<v Speaker 1>possible considering my preferences. Well, if they you know, if

0:30:23.280 --> 0:30:26.080
<v Speaker 1>if nothing is connected to me, then there's no that

0:30:26.280 --> 0:30:29.280
<v Speaker 1>all it's to use is tracking that there that someone

0:30:29.400 --> 0:30:32.240
<v Speaker 1>is moving around, but it doesn't know how to adjust

0:30:32.800 --> 0:30:35.520
<v Speaker 1>you know, the settings were anything to make it ideal

0:30:35.560 --> 0:30:39.400
<v Speaker 1>for me. So that's the trade off is do we

0:30:39.720 --> 0:30:43.200
<v Speaker 1>go with this world where we have this custom experience

0:30:43.240 --> 0:30:45.760
<v Speaker 1>to life? This the sort of idea where we have

0:30:45.800 --> 0:30:49.440
<v Speaker 1>truly manipulated our environment to the fullest extent possible so

0:30:49.480 --> 0:30:53.080
<v Speaker 1>that every person is getting as ideal and experience as

0:30:53.120 --> 0:30:56.680
<v Speaker 1>we can hope to achieve. But on the flip side,

0:30:57.160 --> 0:31:00.040
<v Speaker 1>every single movement you make is essentially and everything a

0:31:00.200 --> 0:31:02.880
<v Speaker 1>thing you do is essentially tracked. Now, there are a

0:31:02.920 --> 0:31:04.800
<v Speaker 1>lot of different ways to approach this, where you build

0:31:04.800 --> 0:31:08.240
<v Speaker 1>in security systems so that everything is encrypted so that yes,

0:31:08.480 --> 0:31:11.960
<v Speaker 1>everything is tracked, but it's not easy for anyone outside

0:31:12.000 --> 0:31:15.360
<v Speaker 1>to see what you did. Win, But there are big concerns.

0:31:15.360 --> 0:31:18.520
<v Speaker 1>I mean, what if you happen to be in an

0:31:18.560 --> 0:31:22.200
<v Speaker 1>area where a crime is committed and you don't even

0:31:22.200 --> 0:31:24.800
<v Speaker 1>witness it. You're not you're not a witness to this crime.

0:31:24.960 --> 0:31:27.200
<v Speaker 1>You were unaware that the crime had happened. And the

0:31:27.240 --> 0:31:30.680
<v Speaker 1>crime could be anything. Let's say it's robbery. So you

0:31:30.720 --> 0:31:32.720
<v Speaker 1>happen to be in the same place at the same

0:31:32.760 --> 0:31:34.760
<v Speaker 1>time as a robbery, but you're not in the exact

0:31:34.800 --> 0:31:39.280
<v Speaker 1>same area, but but it's tracked you there, and then

0:31:39.520 --> 0:31:43.080
<v Speaker 1>you happen to be late to something, so you make

0:31:43.520 --> 0:31:47.360
<v Speaker 1>a faster than normal egress from the area in order

0:31:47.360 --> 0:31:50.600
<v Speaker 1>to make your next appointment. And uh, it could very

0:31:50.600 --> 0:31:53.720
<v Speaker 1>well be the law enforcement when looking and reviewing records.

0:31:53.800 --> 0:31:56.160
<v Speaker 1>If you're leaving a digital footprint that can be traced

0:31:56.160 --> 0:31:58.360
<v Speaker 1>back to you could say, hey, this is a person

0:31:58.360 --> 0:32:01.800
<v Speaker 1>of interest because look, they were there at this particular time,

0:32:01.840 --> 0:32:04.720
<v Speaker 1>and then they left in a real hurry at at

0:32:04.760 --> 0:32:07.840
<v Speaker 1>that you know, shortly after the robbery took place. And

0:32:07.880 --> 0:32:10.200
<v Speaker 1>then next thing you know, you're being hassled about something

0:32:10.200 --> 0:32:14.120
<v Speaker 1>that you had no knowledge of. Or let's say that

0:32:14.200 --> 0:32:18.920
<v Speaker 1>you are doing something naughty, something that is frowned upon,

0:32:19.000 --> 0:32:21.720
<v Speaker 1>whether it's illegal or an ethical or whatever. Well, now

0:32:21.760 --> 0:32:25.440
<v Speaker 1>you've got a record of it everywhere. So some of

0:32:25.520 --> 0:32:29.400
<v Speaker 1>us who consider ourselves to be fairly ethical people might say,

0:32:29.880 --> 0:32:34.320
<v Speaker 1>you know, I understand, but I don't really do anything terrible,

0:32:34.480 --> 0:32:36.960
<v Speaker 1>so I don't see what that's a concern. Some people

0:32:36.960 --> 0:32:41.160
<v Speaker 1>who are truly ethical people will be saying, this is

0:32:41.200 --> 0:32:45.400
<v Speaker 1>an awful idea. I mean, whether I do anything wrong

0:32:45.560 --> 0:32:48.760
<v Speaker 1>is immaterial. I don't want there to be a system

0:32:48.800 --> 0:32:51.320
<v Speaker 1>that tracks everything I do all the time. I want

0:32:51.480 --> 0:32:55.600
<v Speaker 1>I want privacy in my life. And uh so that

0:32:55.600 --> 0:32:58.160
<v Speaker 1>that is a huge hurdle. I mean, do we do

0:32:58.200 --> 0:33:02.240
<v Speaker 1>we adopt this world to the future where we can

0:33:02.320 --> 0:33:06.120
<v Speaker 1>have this kind of experience, or do we shy away

0:33:06.160 --> 0:33:10.160
<v Speaker 1>from it because we don't want to have a living

0:33:10.280 --> 0:33:14.480
<v Speaker 1>record of everything we do every day until we're you know,

0:33:15.760 --> 0:33:19.640
<v Speaker 1>part of the environment as opposed to experiencing it. Yeah. Well,

0:33:19.680 --> 0:33:22.320
<v Speaker 1>and and that's, um, you know, that's one of those

0:33:22.320 --> 0:33:28.560
<v Speaker 1>conflicts that's difficult because the the um the benefits of

0:33:28.600 --> 0:33:32.720
<v Speaker 1>some of this technology are pretty obvious, and you say, well,

0:33:32.760 --> 0:33:34.720
<v Speaker 1>you know, I really like this stuff. I wish I

0:33:34.720 --> 0:33:37.880
<v Speaker 1>could do that, but I'm just not comfortable with giving

0:33:37.960 --> 0:33:42.120
<v Speaker 1>up my privacy. Um. I'm one of those people. Um So, yeah,

0:33:42.160 --> 0:33:44.120
<v Speaker 1>I mean I could, I could tell you from personal

0:33:44.160 --> 0:33:49.600
<v Speaker 1>experience that it's not it's not a simple question to answer. Um,

0:33:49.680 --> 0:33:51.840
<v Speaker 1>A lot of these technologies are are things that we

0:33:51.880 --> 0:33:55.600
<v Speaker 1>can implement without having to give up too much your privacy. UM.

0:33:55.840 --> 0:33:59.240
<v Speaker 1>And then others you know, uh, you have to go, well,

0:33:59.280 --> 0:34:01.080
<v Speaker 1>I'm gonna have to make a decision here one way

0:34:01.160 --> 0:34:05.440
<v Speaker 1>or the other. Yes, yeah, it's UM, it's it's definitely

0:34:05.520 --> 0:34:08.960
<v Speaker 1>an exciting time to see these developments take place. And

0:34:09.800 --> 0:34:13.440
<v Speaker 1>I think, you know, we we are looking at possibilities,

0:34:13.440 --> 0:34:15.840
<v Speaker 1>but we also have to remember that this is not

0:34:15.920 --> 0:34:20.600
<v Speaker 1>going to be a super fast transition and some stuff

0:34:20.640 --> 0:34:24.080
<v Speaker 1>probably just won't work. Because you can build the best

0:34:24.200 --> 0:34:26.120
<v Speaker 1>system in the world, but if people don't use it

0:34:26.160 --> 0:34:27.719
<v Speaker 1>the way you thought they were going to use it,

0:34:27.800 --> 0:34:31.239
<v Speaker 1>then it becomes a problem. And and that's one of

0:34:31.239 --> 0:34:34.200
<v Speaker 1>the things is that it's hard to predict user behavior

0:34:34.880 --> 0:34:37.680
<v Speaker 1>when you're first designing a system. I think a lot

0:34:37.760 --> 0:34:41.840
<v Speaker 1>of people were very skeptical of smartphone apps when smartphones

0:34:41.880 --> 0:34:43.560
<v Speaker 1>because a lot of the smartphone apps that first came

0:34:43.560 --> 0:34:47.600
<v Speaker 1>out were very much curiosities. They weren't necessarily that useful.

0:34:47.920 --> 0:34:51.680
<v Speaker 1>But now mobile apps, that is that is the thing.

0:34:51.760 --> 0:34:54.640
<v Speaker 1>I mean, that's the huge craze in tech right. I mean,

0:34:55.400 --> 0:34:58.920
<v Speaker 1>we're seeing big companies scoop up small mobile app companies

0:34:58.920 --> 0:35:02.520
<v Speaker 1>for billions of dollars because it's a big deal. So

0:35:02.880 --> 0:35:06.120
<v Speaker 1>if the Internet of Things takes a route similar to

0:35:06.160 --> 0:35:09.800
<v Speaker 1>the way smartphones and mobile technology and apps have, then

0:35:10.239 --> 0:35:14.640
<v Speaker 1>it's definitely gonna become something pervasive and hopefully more useful

0:35:14.680 --> 0:35:19.399
<v Speaker 1>than problematic. But it's also possible that the first few

0:35:19.400 --> 0:35:23.160
<v Speaker 1>implementations of this kind of technology could fall flat, that

0:35:23.239 --> 0:35:25.480
<v Speaker 1>they just don't work the way they were anticipated to.

0:35:25.680 --> 0:35:29.759
<v Speaker 1>And if it's if it's a big enough failure, it

0:35:29.880 --> 0:35:32.520
<v Speaker 1>may mean that we don't see this Internet of things

0:35:32.600 --> 0:35:36.160
<v Speaker 1>truly emerge because companies may shy away from it. Yeah. Well,

0:35:36.200 --> 0:35:39.400
<v Speaker 1>I mean, like like I was saying earlier, I mean,

0:35:39.440 --> 0:35:41.680
<v Speaker 1>there are some things that are already there. We're already

0:35:41.719 --> 0:35:44.000
<v Speaker 1>in the world. The thing is, there's I think it's

0:35:44.000 --> 0:35:46.720
<v Speaker 1>going to end up being a situation where consumer demand

0:35:46.840 --> 0:35:50.000
<v Speaker 1>drives a lot of things like the washer and dryer.

0:35:50.120 --> 0:35:53.680
<v Speaker 1>That situation where you know, the washer wood communicated, the dryer, Hey,

0:35:53.760 --> 0:35:57.799
<v Speaker 1>expect a load of permanent press it's coming. Um, you know,

0:35:57.880 --> 0:36:01.160
<v Speaker 1>that may not necessarily take off. You know, if it's

0:36:01.160 --> 0:36:04.040
<v Speaker 1>a five option and people go, I don't I'm not

0:36:04.040 --> 0:36:06.360
<v Speaker 1>going to spend it on that. Now, having an email

0:36:06.400 --> 0:36:07.880
<v Speaker 1>sent to you to tell you, hey, it's time to

0:36:07.960 --> 0:36:10.920
<v Speaker 1>change the clothes over sticking in the in the dryer. Um,

0:36:10.960 --> 0:36:13.040
<v Speaker 1>now that would be useful. So I think it's people

0:36:13.080 --> 0:36:14.680
<v Speaker 1>are gonna say why I want that? But I don't.

0:36:14.719 --> 0:36:17.080
<v Speaker 1>I mean, why would I want this? It may also

0:36:17.160 --> 0:36:18.919
<v Speaker 1>be one of those things where a lot of these

0:36:18.920 --> 0:36:22.840
<v Speaker 1>features end up getting built into all models. Eventually, like

0:36:22.880 --> 0:36:25.200
<v Speaker 1>it filters down so it no longer becomes like a

0:36:25.239 --> 0:36:29.239
<v Speaker 1>premium model of a particular appliance. It just becomes a

0:36:29.320 --> 0:36:32.760
<v Speaker 1>standard feature that you find across all models of that appliance.

0:36:33.200 --> 0:36:36.279
<v Speaker 1>And uh and in that case, um, you might end

0:36:36.360 --> 0:36:40.600
<v Speaker 1>up slowly adopting it, but uh, there are other times

0:36:40.600 --> 0:36:43.799
<v Speaker 1>where you might see companies just abandoned it. Another good

0:36:43.800 --> 0:36:46.480
<v Speaker 1>example of this is like three D television. You know,

0:36:47.160 --> 0:36:49.120
<v Speaker 1>there's there are a lot of television sets out there

0:36:49.160 --> 0:36:51.799
<v Speaker 1>that have three D built into them, but they're not

0:36:51.840 --> 0:36:57.000
<v Speaker 1>necessarily um marketed as three D TVs. Well, that that

0:36:57.080 --> 0:36:58.880
<v Speaker 1>might be what we see in the future with these

0:36:59.000 --> 0:37:02.840
<v Speaker 1>internet connected appliances, that it's just one of the features

0:37:02.880 --> 0:37:05.719
<v Speaker 1>of the appliance and it's not the selling feature, and

0:37:05.800 --> 0:37:09.400
<v Speaker 1>that it's not necessarily priced higher because of it. Um,

0:37:09.440 --> 0:37:12.080
<v Speaker 1>it's just one of the many things that comes with

0:37:12.120 --> 0:37:14.920
<v Speaker 1>that particular appliance. And the other thing that we'll have

0:37:15.040 --> 0:37:18.919
<v Speaker 1>to have is some sort of universal standard of communication

0:37:19.000 --> 0:37:21.759
<v Speaker 1>for this to truly work, or you're going to see

0:37:21.800 --> 0:37:26.799
<v Speaker 1>third party companies pop up and their specialty is creating

0:37:26.920 --> 0:37:31.800
<v Speaker 1>some sort of communication hub where different protocols can actually

0:37:31.840 --> 0:37:36.120
<v Speaker 1>work together with one another, at least on a superficial level. Uh.

0:37:36.160 --> 0:37:39.480
<v Speaker 1>And so my point there is that if manufacturers don't

0:37:39.640 --> 0:37:44.000
<v Speaker 1>start looking into ways where their technologies can talk to

0:37:44.040 --> 0:37:47.080
<v Speaker 1>other companies technologies, a third party is going to find

0:37:47.080 --> 0:37:48.880
<v Speaker 1>a way to make it happen, and then they're gonna

0:37:48.960 --> 0:37:52.880
<v Speaker 1>just explode. And that wraps up another classic episode of

0:37:52.920 --> 0:37:55.640
<v Speaker 1>tech stuff. I hope you guys enjoyed it. This is

0:37:55.640 --> 0:37:57.359
<v Speaker 1>what I was talking about if you listened a few

0:37:57.360 --> 0:37:58.880
<v Speaker 1>weeks ago, I mentioned that there were going to be

0:37:58.920 --> 0:38:01.680
<v Speaker 1>some upcoming classic epis zodes that would be a little

0:38:01.800 --> 0:38:05.200
<v Speaker 1>amusing to listen to in light of the years that

0:38:05.280 --> 0:38:09.160
<v Speaker 1>have passed. That's the challenging thing about picking classic episodes

0:38:09.200 --> 0:38:12.920
<v Speaker 1>of a technology podcast. Things change so quickly. But then

0:38:12.960 --> 0:38:15.319
<v Speaker 1>I thought, you know what, it's also an opportunity to

0:38:15.400 --> 0:38:18.520
<v Speaker 1>kind of reflect back on what are thinking was like

0:38:19.080 --> 0:38:22.200
<v Speaker 1>a few years ago and see how things have developed

0:38:22.280 --> 0:38:26.239
<v Speaker 1>differently than the way we anticipated, or sometimes how we

0:38:26.400 --> 0:38:30.080
<v Speaker 1>managed to actually hit upon how things are going to evolve.

0:38:30.760 --> 0:38:33.040
<v Speaker 1>I think we miss more frequently than we hit. There's

0:38:33.080 --> 0:38:35.960
<v Speaker 1>just too much that's unpredictable out there, but it's still

0:38:36.000 --> 0:38:38.080
<v Speaker 1>interesting to go back there. If you guys have any

0:38:38.120 --> 0:38:41.080
<v Speaker 1>suggestions for future episodes of tech Stuff, send me a message.

0:38:41.080 --> 0:38:44.680
<v Speaker 1>The address is tech stuff at how stuff works dot com,

0:38:44.840 --> 0:38:47.160
<v Speaker 1>or pop on over to our website that's tech stuff

0:38:47.200 --> 0:38:50.120
<v Speaker 1>podcast dot com, where you'll find links to the social media,

0:38:50.520 --> 0:38:53.919
<v Speaker 1>you'll find all the archived podcasts. You'll find a link

0:38:53.960 --> 0:38:56.799
<v Speaker 1>to our online store. Check all that out and I'll

0:38:56.800 --> 0:39:05.520
<v Speaker 1>talk to you again really soon for more on this

0:39:05.719 --> 0:39:08.239
<v Speaker 1>and thousands of other topics. Is that how stuff works

0:39:08.239 --> 0:39:18.440
<v Speaker 1>dot com.