WEBVTT - 2018 Predictions Scorecard

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:14.080
<v Speaker 1>stuff Works dot Com. He there, and welcome to text Stuff.

0:00:14.120 --> 0:00:17.680
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:17.720 --> 0:00:20.759
<v Speaker 1>How Stuff Works, and I heart radio and I love

0:00:20.840 --> 0:00:23.919
<v Speaker 1>all things tech. And if you've been listening to my

0:00:24.040 --> 0:00:27.920
<v Speaker 1>show for more than twelve months, you know that every year,

0:00:29.040 --> 0:00:31.520
<v Speaker 1>with the exception of this next coming year, I make

0:00:31.560 --> 0:00:34.519
<v Speaker 1>predictions about what may or may not happen in the

0:00:34.560 --> 0:00:37.479
<v Speaker 1>tech world over the course of the following twelve months.

0:00:37.760 --> 0:00:40.159
<v Speaker 1>And then at the end of those twelve months, I

0:00:40.240 --> 0:00:42.440
<v Speaker 1>go back and I look at the predictions I had

0:00:42.479 --> 0:00:45.560
<v Speaker 1>made for the year previous and see how it all

0:00:45.600 --> 0:00:50.519
<v Speaker 1>turned out. Generally speaking, I do really poorly. So let's

0:00:50.520 --> 0:00:54.400
<v Speaker 1>see how I did for Here's what I predicted and

0:00:54.480 --> 0:00:57.840
<v Speaker 1>here's what actually happened. So the first prediction I made

0:00:58.400 --> 0:01:01.800
<v Speaker 1>was that VR headsets like Oculus, Rift, HTC, Vibe and

0:01:01.840 --> 0:01:05.240
<v Speaker 1>others will have another lackluster year. Now the result here

0:01:05.720 --> 0:01:09.040
<v Speaker 1>is somewhat mixed. I was certainly right for the first

0:01:09.040 --> 0:01:13.200
<v Speaker 1>half of those numbers were not doing well. Several news

0:01:13.240 --> 0:01:18.560
<v Speaker 1>outlets and analysis firms would release reports throughout they cited

0:01:18.560 --> 0:01:22.319
<v Speaker 1>declining sales for VR headsets in general throughout the year.

0:01:23.160 --> 0:01:25.720
<v Speaker 1>The Oculus Go was an exception in the first half

0:01:25.720 --> 0:01:28.039
<v Speaker 1>of the year. It saw some growth early on, but

0:01:28.160 --> 0:01:32.160
<v Speaker 1>still not a crazy amount. Reports have cautioned that this

0:01:32.280 --> 0:01:35.240
<v Speaker 1>does not mean VR is going to fizzle out again

0:01:35.400 --> 0:01:39.040
<v Speaker 1>the way it did in the mid nineties, but rather

0:01:39.600 --> 0:01:43.399
<v Speaker 1>that the market is still finding its foundation. It's still

0:01:43.800 --> 0:01:48.280
<v Speaker 1>figuring out where it is, and there was an upturn

0:01:48.440 --> 0:01:52.720
<v Speaker 1>in the third quarter in bolstered largely by holiday sales

0:01:52.960 --> 0:01:58.360
<v Speaker 1>and particularly the PlayStation VR headset. Things were even worse, however,

0:01:58.480 --> 0:02:01.120
<v Speaker 1>if we're talking about VR head sets that don't have

0:02:01.200 --> 0:02:04.000
<v Speaker 1>a screen, so in other words, i'm talking about the

0:02:04.000 --> 0:02:09.240
<v Speaker 1>headsets that you use in connection with a smartphone that

0:02:09.240 --> 0:02:13.280
<v Speaker 1>that's running a particular app. So Samsung's Gear VR headset

0:02:13.440 --> 0:02:17.120
<v Speaker 1>year over year sales were down by fifty eight point

0:02:17.320 --> 0:02:21.600
<v Speaker 1>six per cent. That's dreadful. Some of the more recent

0:02:21.680 --> 0:02:26.840
<v Speaker 1>Samsung smartphones don't even support that particular feature, which suggests

0:02:26.840 --> 0:02:30.680
<v Speaker 1>the company may be extricating itself from the VR market entirely.

0:02:30.760 --> 0:02:34.960
<v Speaker 1>So the only headsets that we're doing well, not even well,

0:02:35.000 --> 0:02:38.120
<v Speaker 1>but weren't losing ground like that were the tethered ones.

0:02:38.720 --> 0:02:41.440
<v Speaker 1>Back to that third quarter. As I said, the improvement

0:02:41.480 --> 0:02:45.120
<v Speaker 1>was largely due to the PlayStation VR headset. The Sony

0:02:45.200 --> 0:02:48.600
<v Speaker 1>headset helped reverse the declining trend in that third quarter

0:02:48.680 --> 0:02:51.800
<v Speaker 1>of and actually pushed the market up to an eight

0:02:51.880 --> 0:02:55.840
<v Speaker 1>point two percent growth year over year, or a quarter

0:02:55.880 --> 0:02:58.560
<v Speaker 1>over a quarter. I guess the p S VR headsets

0:02:58.600 --> 0:03:03.040
<v Speaker 1>sold four sixty eight thousand units total. That's an increase

0:03:03.040 --> 0:03:07.080
<v Speaker 1>of twenty six over the previous year. Oculus would follow

0:03:07.120 --> 0:03:10.240
<v Speaker 1>in second place, and HTC held up third place by

0:03:10.280 --> 0:03:12.640
<v Speaker 1>the end of the year. So the third quarter growth

0:03:12.720 --> 0:03:14.600
<v Speaker 1>was a nice thing to see, but that was after

0:03:14.760 --> 0:03:18.840
<v Speaker 1>four straight quarters of decline and it remains to be

0:03:18.919 --> 0:03:22.000
<v Speaker 1>seen if this is actually sustainable growth. So I'd say

0:03:22.440 --> 0:03:26.480
<v Speaker 1>mixed results on that. The whole year wasn't a loss,

0:03:26.919 --> 0:03:31.160
<v Speaker 1>but you had two quarters of decline followed by a

0:03:31.200 --> 0:03:35.920
<v Speaker 1>third quarter of modest gains. Eight point as good, but

0:03:36.000 --> 0:03:40.840
<v Speaker 1>it's not great, So I will give myself, you know,

0:03:40.920 --> 0:03:42.920
<v Speaker 1>a thumb in the middle here, not like thumb up

0:03:43.000 --> 0:03:47.400
<v Speaker 1>or thumb down. Prediction Number two was that Microsoft Mixed

0:03:47.440 --> 0:03:51.080
<v Speaker 1>reality headsets, being the relative new toy on the market,

0:03:51.080 --> 0:03:53.360
<v Speaker 1>will get some initial buzz in the early part of

0:03:54.400 --> 0:03:57.640
<v Speaker 1>but will largely suffer the same fate as VR, and

0:03:57.760 --> 0:04:00.720
<v Speaker 1>this one I was absolutely right about. Out. We saw

0:04:00.840 --> 0:04:05.000
<v Speaker 1>prices get marked down a couple of times in eighteen

0:04:05.120 --> 0:04:09.120
<v Speaker 1>for mixed reality headsets, and interest failed to build into

0:04:09.160 --> 0:04:11.000
<v Speaker 1>a lot of actual action. There weren't a lot of

0:04:11.040 --> 0:04:15.119
<v Speaker 1>sales even with the reduction in price. Now again, this

0:04:15.240 --> 0:04:17.760
<v Speaker 1>may just be a case of the technology not quite

0:04:17.880 --> 0:04:20.640
<v Speaker 1>being sophisticated enough to convince people to make the jump.

0:04:21.320 --> 0:04:25.760
<v Speaker 1>According to research firm I d C, augmented or mixed

0:04:25.800 --> 0:04:28.919
<v Speaker 1>reality sets only made up three percent of the market

0:04:29.160 --> 0:04:32.360
<v Speaker 1>for these types of things. The really advanced headsets, the

0:04:32.400 --> 0:04:36.600
<v Speaker 1>stuff like hollow lens or magic leaps new headset, those

0:04:36.680 --> 0:04:40.840
<v Speaker 1>cost thousands of dollars and they're primarily intended for professional

0:04:41.520 --> 0:04:44.640
<v Speaker 1>use or developer use, not for your average consumers. So

0:04:45.279 --> 0:04:48.320
<v Speaker 1>those sets aren't meant for you and me. We're not

0:04:48.360 --> 0:04:50.520
<v Speaker 1>meant to go out there to like a Best Buy

0:04:50.600 --> 0:04:52.680
<v Speaker 1>or something and pick one off the store shelves and

0:04:52.720 --> 0:04:55.279
<v Speaker 1>take it home and play games or use it for

0:04:55.320 --> 0:05:00.720
<v Speaker 1>other applications. They're meant either for industrial use things people

0:05:00.720 --> 0:05:03.279
<v Speaker 1>are using hollow lens in order to help train people

0:05:03.360 --> 0:05:07.360
<v Speaker 1>to work around equipment, make repairs that kind of stuff,

0:05:07.960 --> 0:05:11.159
<v Speaker 1>or They're meant for developers to get hold of the

0:05:11.200 --> 0:05:14.400
<v Speaker 1>hardware and start thinking about ways that they can, you know,

0:05:14.640 --> 0:05:17.000
<v Speaker 1>leverage that hardware, what kind of software can they build

0:05:17.000 --> 0:05:21.360
<v Speaker 1>for it, and then sometime down the road, presumably we'll

0:05:21.400 --> 0:05:24.840
<v Speaker 1>get a consumer version of those pieces of hardware. That's

0:05:24.880 --> 0:05:28.839
<v Speaker 1>kind of how Oculous came about as well. So, uh,

0:05:28.880 --> 0:05:31.920
<v Speaker 1>they absolutely right, big thumbs up on that one. Prediction

0:05:31.960 --> 0:05:35.200
<v Speaker 1>Number three was that we would see autonomous car service

0:05:35.279 --> 0:05:38.559
<v Speaker 1>rolled out for real, not just as a limited test case,

0:05:38.880 --> 0:05:41.520
<v Speaker 1>and at least one market in the United States before

0:05:41.560 --> 0:05:46.560
<v Speaker 1>the end of this was a pretty aggressive prediction that

0:05:46.640 --> 0:05:48.800
<v Speaker 1>I made. As it turns out, I think this is

0:05:48.839 --> 0:05:51.800
<v Speaker 1>another thumb in the middle situation. I would not give

0:05:51.839 --> 0:05:54.080
<v Speaker 1>myself a full thumbs up, but I don't think it's

0:05:54.080 --> 0:05:57.240
<v Speaker 1>a full thumbs down either, I think, if I'm being

0:05:57.279 --> 0:06:01.839
<v Speaker 1>totally honest, I just ba early missed this one because

0:06:01.920 --> 0:06:06.039
<v Speaker 1>Weymo one, which is a driverless car service from the

0:06:06.120 --> 0:06:11.080
<v Speaker 1>Google spin off Weymo, launched in Phoenix, Arizona, so that

0:06:11.120 --> 0:06:14.359
<v Speaker 1>did happen this year. However, as of the recording of

0:06:14.360 --> 0:06:17.279
<v Speaker 1>this podcast, it is a very limited launch. It is

0:06:17.320 --> 0:06:21.840
<v Speaker 1>not it's not widely available to anyone only people who

0:06:21.920 --> 0:06:25.000
<v Speaker 1>signed up to be quote unquote early riders with the

0:06:25.120 --> 0:06:28.320
<v Speaker 1>service are actually eligible to use it, and it works

0:06:28.360 --> 0:06:31.279
<v Speaker 1>pretty much like any ride hailing app and that users

0:06:31.279 --> 0:06:33.679
<v Speaker 1>would select a pickup point and a drop off point.

0:06:34.160 --> 0:06:35.920
<v Speaker 1>The only thing that's different is that the vehicle that

0:06:35.960 --> 0:06:38.160
<v Speaker 1>comes to pick them up is a driver less one,

0:06:38.200 --> 0:06:41.719
<v Speaker 1>although there is a safety operator behind the wheel, because

0:06:42.839 --> 0:06:45.600
<v Speaker 1>we're not quite at the point where I think any

0:06:45.640 --> 0:06:49.400
<v Speaker 1>company would be comfortable and having a truly driverless cargo

0:06:49.440 --> 0:06:53.039
<v Speaker 1>and pick people up and then potentially get into an

0:06:53.080 --> 0:06:55.799
<v Speaker 1>accident and then you've got an enormous lawsuit on your hands.

0:06:56.279 --> 0:06:58.400
<v Speaker 1>So we're not even at the point where it's a

0:06:58.480 --> 0:07:01.360
<v Speaker 1>real robot car when no human behind the wheel at all.

0:07:01.800 --> 0:07:05.279
<v Speaker 1>The Early writer program is limited to just four people,

0:07:05.680 --> 0:07:08.520
<v Speaker 1>and the area of service is also GEO fenced, which

0:07:08.680 --> 0:07:12.040
<v Speaker 1>means the cars will not go beyond certain designated areas.

0:07:12.120 --> 0:07:16.640
<v Speaker 1>They their services limited to specific regions. So it's a

0:07:16.760 --> 0:07:21.080
<v Speaker 1>very contained case and way Moose pitching it like it's

0:07:21.640 --> 0:07:25.160
<v Speaker 1>an actual launch, But really I would say this is

0:07:25.560 --> 0:07:29.680
<v Speaker 1>a pilot program, or maybe I should say a pilotless program.

0:07:30.280 --> 0:07:32.880
<v Speaker 1>So with all the qualifiers, I don't think it meets

0:07:32.920 --> 0:07:38.360
<v Speaker 1>the level that I had uh imagined when I made

0:07:38.400 --> 0:07:42.200
<v Speaker 1>that prediction last year, but still a lot further along

0:07:42.240 --> 0:07:45.480
<v Speaker 1>the what the more pessimistic version of me thought might happen.

0:07:45.560 --> 0:07:48.520
<v Speaker 1>The pessimist in me thought we won't even see this

0:07:48.760 --> 0:07:52.520
<v Speaker 1>much of a rollout, so to speak. Now, I think

0:07:52.560 --> 0:07:56.680
<v Speaker 1>it makes way more sense to do this deployment this

0:07:56.720 --> 0:08:01.640
<v Speaker 1>way rather than just try to jump in wholeheartedly. That

0:08:01.800 --> 0:08:04.520
<v Speaker 1>would to me seem to be irresponsible. So I think

0:08:04.560 --> 0:08:07.920
<v Speaker 1>this is the better choice. But it's really more of

0:08:07.960 --> 0:08:11.720
<v Speaker 1>a closed beta program. Okay, So that was a thumb

0:08:11.760 --> 0:08:14.560
<v Speaker 1>in the middle prediction. Number four. Congress will give the

0:08:14.640 --> 0:08:18.240
<v Speaker 1>nod to the Disney twenty first century Fox acquisition after

0:08:18.280 --> 0:08:21.240
<v Speaker 1>several months of discussion. Disney will hold a sixty percent

0:08:21.320 --> 0:08:23.760
<v Speaker 1>ownership of Hulu, but we'll still go ahead and developing

0:08:23.760 --> 0:08:26.640
<v Speaker 1>its own streaming service on top of that. Okay, the

0:08:26.800 --> 0:08:29.680
<v Speaker 1>big thumbs up for me. I mean, I would also

0:08:29.760 --> 0:08:33.360
<v Speaker 1>say this was not a particularly bold prediction, as pretty

0:08:33.440 --> 0:08:35.120
<v Speaker 1>much writing on the wall kind of stuff. I mean,

0:08:35.120 --> 0:08:38.000
<v Speaker 1>there there could have been pushed back from the US

0:08:38.080 --> 0:08:42.360
<v Speaker 1>government on the acquisition, but based upon who's in the

0:08:42.480 --> 0:08:46.000
<v Speaker 1>various branches of government, I thought that was unlikely largely

0:08:46.040 --> 0:08:50.120
<v Speaker 1>because they are pretty friendly to big business. So the

0:08:50.240 --> 0:08:53.520
<v Speaker 1>seventy one point three billion dollar acquisition was approved by

0:08:53.520 --> 0:08:59.040
<v Speaker 1>the United States government in June of and company shareholders

0:08:59.080 --> 0:09:03.480
<v Speaker 1>also approved did in July. So first the government said,

0:09:03.480 --> 0:09:05.520
<v Speaker 1>we don't have any problems with this. Then they went

0:09:05.559 --> 0:09:08.000
<v Speaker 1>to the shareholders and said, are you guys cool with this?

0:09:08.120 --> 0:09:11.240
<v Speaker 1>They said totes, and then it went on. So technically

0:09:11.280 --> 0:09:14.160
<v Speaker 1>the closing for this acquisition has not happened yet. It

0:09:14.160 --> 0:09:19.600
<v Speaker 1>will actually happen on January one, nineteen. And yes, Disney

0:09:19.640 --> 0:09:22.360
<v Speaker 1>does still plan to launch its own streaming service called

0:09:22.360 --> 0:09:26.439
<v Speaker 1>Disney Plus, and it will also oversee Hulu. It will

0:09:26.440 --> 0:09:32.400
<v Speaker 1>have controlling uh interest or controlling steak in Hulu. Meanwhile,

0:09:32.760 --> 0:09:37.720
<v Speaker 1>we watch as we sadly see various Netflix Marvel series

0:09:37.800 --> 0:09:41.360
<v Speaker 1>mysteriously get canceled, like you know, Daredevil and The Defenders,

0:09:42.000 --> 0:09:45.720
<v Speaker 1>despite critical and public acclaim which suggests that perhaps Disney

0:09:45.760 --> 0:09:49.600
<v Speaker 1>is preparing those to migrate over to a different streaming service,

0:09:49.640 --> 0:09:51.840
<v Speaker 1>perhaps for a total reboot, and may not even have

0:09:51.960 --> 0:09:56.000
<v Speaker 1>the same actors involved. We aren't quite sure what Hulu

0:09:56.040 --> 0:09:58.840
<v Speaker 1>is going to look like following this acquisition. Even now,

0:09:59.240 --> 0:10:03.199
<v Speaker 1>right now, before the acquisition is complete, Hulu technically has

0:10:03.320 --> 0:10:07.320
<v Speaker 1>three major owners. There's Disney, Fox, and Comcast. There are

0:10:07.360 --> 0:10:09.240
<v Speaker 1>also some other owners on top of that, but those

0:10:09.240 --> 0:10:12.200
<v Speaker 1>are the three big ones. So with the acquisition, Disney

0:10:12.240 --> 0:10:15.120
<v Speaker 1>will hold the majority stake, and that might mean that

0:10:15.240 --> 0:10:19.079
<v Speaker 1>Comcast and NBC will be less eager to form agreements

0:10:19.120 --> 0:10:21.880
<v Speaker 1>for the properties that they have to air on Hulu.

0:10:22.160 --> 0:10:24.280
<v Speaker 1>It may also mean we'll see the emergence of yet

0:10:24.320 --> 0:10:27.600
<v Speaker 1>another streaming service to cater to those properties. So yea,

0:10:28.520 --> 0:10:33.240
<v Speaker 1>it's getting worse than cable prediction number five. After numerous

0:10:33.240 --> 0:10:37.160
<v Speaker 1>heated discussions, Congress will overturn the fccs decision in December

0:10:38.240 --> 0:10:42.720
<v Speaker 1>to reverse the decision classifying broadband Internet as a public utility.

0:10:44.400 --> 0:10:48.920
<v Speaker 1>M hm now yet uh, FCC did overturn it in

0:10:49.200 --> 0:10:54.839
<v Speaker 1>um earlyen they announced the Restoring Internet Freedom Order, which

0:10:55.320 --> 0:10:58.320
<v Speaker 1>seems to be a bit of a comedic title for

0:10:58.400 --> 0:11:00.160
<v Speaker 1>what it is. It rolled back pretty much all the

0:11:00.240 --> 0:11:06.040
<v Speaker 1>changes that the previous FCC had made, and um, yeah,

0:11:06.280 --> 0:11:10.080
<v Speaker 1>I don't know that we're gonna see that get returned

0:11:11.240 --> 0:11:13.880
<v Speaker 1>super soon. There were a lot of discussions about net neutrality,

0:11:13.920 --> 0:11:20.160
<v Speaker 1>but still very much a unresolved question within the United States,

0:11:20.559 --> 0:11:23.120
<v Speaker 1>so thumbs down. On that one, I would say prediction

0:11:23.200 --> 0:11:25.839
<v Speaker 1>number six. By the end of twenty eighteen, the number

0:11:25.840 --> 0:11:28.679
<v Speaker 1>of cord cutters in the United States will hit thirty million.

0:11:29.400 --> 0:11:32.920
<v Speaker 1>In seventeen, it was twenty two point two million, which

0:11:32.960 --> 0:11:36.320
<v Speaker 1>was up from sixteen point seven million in twenty sixteen,

0:11:37.000 --> 0:11:38.800
<v Speaker 1>and I said that trend would not only continue, but

0:11:38.840 --> 0:11:42.120
<v Speaker 1>would accelerate as more people would turn to virtual subscriptions

0:11:42.559 --> 0:11:46.080
<v Speaker 1>using smart TVs, consoles, and other solutions to get access

0:11:46.120 --> 0:11:49.800
<v Speaker 1>to live TV while abandoning satellite or cable options. Big

0:11:49.840 --> 0:11:54.920
<v Speaker 1>thumbs up. In fact, I was being apparently conservative. Um

0:11:55.080 --> 0:11:58.800
<v Speaker 1>midway through eighteen, analysts had already projected that we would

0:11:58.880 --> 0:12:02.240
<v Speaker 1>hit thirty three million cord cutters by the end of

0:12:02.240 --> 0:12:07.680
<v Speaker 1>the year total, not thirty three million alone, but total

0:12:07.720 --> 0:12:10.360
<v Speaker 1>in the United States. So I was actually three million

0:12:10.360 --> 0:12:12.840
<v Speaker 1>people shy even though I thought, well, this is an

0:12:12.840 --> 0:12:16.000
<v Speaker 1>accelerated rate, I'm gonna go with it. It turns out

0:12:16.040 --> 0:12:18.760
<v Speaker 1>I was being too conservative. The reasons cited for the

0:12:18.800 --> 0:12:21.079
<v Speaker 1>increase we're pretty much what I have said. People are

0:12:21.080 --> 0:12:24.679
<v Speaker 1>focusing more on internet delivery services and less on television.

0:12:24.920 --> 0:12:27.599
<v Speaker 1>And while a lot of TV services were forming partnerships

0:12:27.640 --> 0:12:30.760
<v Speaker 1>with companies like Netflix, the takeaway seemed to be that

0:12:30.840 --> 0:12:34.840
<v Speaker 1>customers were interested in just getting those Internet entertainment services,

0:12:35.160 --> 0:12:39.280
<v Speaker 1>not television plus those services. Now, at this point, I've

0:12:39.280 --> 0:12:42.600
<v Speaker 1>seen analysts like Dan Robin Robbins predict that this trend

0:12:42.640 --> 0:12:45.400
<v Speaker 1>is only going to accelerate further in twenty nineteen, so

0:12:46.080 --> 0:12:49.040
<v Speaker 1>we may see an even a larger number of cord

0:12:49.080 --> 0:12:53.640
<v Speaker 1>cutters joined the fray in the following year. I have

0:12:53.720 --> 0:12:55.840
<v Speaker 1>more to say about the predictions I made at the

0:12:55.920 --> 0:12:58.800
<v Speaker 1>end of twenty seventeen, but first let's go take a

0:12:58.880 --> 0:13:10.079
<v Speaker 1>break to thank our answer prediction number seven. There will

0:13:10.120 --> 0:13:13.800
<v Speaker 1>be at least one, probably more security breaches on the

0:13:13.840 --> 0:13:17.760
<v Speaker 1>scale of the Equifax breach in ten, because while we

0:13:17.800 --> 0:13:20.240
<v Speaker 1>pay a lot of lip service towards security, it's way

0:13:20.240 --> 0:13:24.480
<v Speaker 1>easier to talk about being secure than actually doing it. Plus,

0:13:24.800 --> 0:13:28.040
<v Speaker 1>we're human beings and we're wackyo, So this is another

0:13:28.080 --> 0:13:32.480
<v Speaker 1>big thumbs up. Unfortunately, I wish it weren't, but we

0:13:32.520 --> 0:13:36.560
<v Speaker 1>had so many data breaches that happened in or were

0:13:36.640 --> 0:13:40.160
<v Speaker 1>made public in Some of the data breaches actually happened

0:13:40.240 --> 0:13:43.920
<v Speaker 1>years ago, but we didn't find out about them until

0:13:44.160 --> 0:13:46.600
<v Speaker 1>this year. So let's go over some of the big ones,

0:13:46.840 --> 0:13:49.720
<v Speaker 1>shall we I'm just going to concentrate on the ones

0:13:50.360 --> 0:13:54.600
<v Speaker 1>that were larger than Equifax's breach. That one affected an

0:13:54.760 --> 0:13:59.199
<v Speaker 1>estimated onety three million people. So while I'm gonna look

0:13:59.240 --> 0:14:01.360
<v Speaker 1>at some big ones, just know that there were also

0:14:01.920 --> 0:14:04.720
<v Speaker 1>a whole bunch of other ones. They just didn't hit

0:14:04.760 --> 0:14:09.280
<v Speaker 1>the hundred forty three million victim mark. So in February,

0:14:09.800 --> 0:14:12.920
<v Speaker 1>not even to the two months into the year, and

0:14:12.960 --> 0:14:17.800
<v Speaker 1>we hit one and unauthorized party and that's how they

0:14:17.880 --> 0:14:21.440
<v Speaker 1>defined it gained access to user information belonging to people

0:14:21.600 --> 0:14:25.480
<v Speaker 1>who had the My Fitness Pal app that that includes me.

0:14:26.720 --> 0:14:30.760
<v Speaker 1>And the data that the unauthorized party got access to

0:14:30.800 --> 0:14:35.600
<v Speaker 1>included encrypted passwords, email addresses, and user names. The estimated

0:14:35.640 --> 0:14:40.200
<v Speaker 1>number of people affected one hundred fifty million. A data

0:14:40.240 --> 0:14:44.600
<v Speaker 1>security expert was poking around on databases belonging to the

0:14:44.720 --> 0:14:49.520
<v Speaker 1>data broker Exactus, and they found a database that had

0:14:49.600 --> 0:14:54.400
<v Speaker 1>information on pretty much every US citizen in it. That

0:14:54.480 --> 0:14:57.560
<v Speaker 1>was actually a quote from a news article about this event.

0:14:58.240 --> 0:15:01.640
<v Speaker 1>It was publicly ex pessible. In other words, there was

0:15:01.680 --> 0:15:08.040
<v Speaker 1>an unprotected, unsecured database containing information about people. This is

0:15:08.080 --> 0:15:11.280
<v Speaker 1>beyond a breach. This is like leaving the vault door

0:15:11.400 --> 0:15:14.520
<v Speaker 1>open in the bank. The estimated number of people affected

0:15:14.600 --> 0:15:20.040
<v Speaker 1>is three hundred forty million people. Yikes. Then in September,

0:15:20.080 --> 0:15:23.560
<v Speaker 1>we learned about a data breach in the reservation database

0:15:23.640 --> 0:15:27.880
<v Speaker 1>for Marriott Starwood Hotels, which may have exposed the information

0:15:27.880 --> 0:15:33.160
<v Speaker 1>of five hundred million people half a billion people. And

0:15:33.200 --> 0:15:37.560
<v Speaker 1>that includes stuff like passport numbers, reservation dates, payment information,

0:15:37.560 --> 0:15:40.320
<v Speaker 1>and more. So there are a lot of not just

0:15:40.760 --> 0:15:45.120
<v Speaker 1>data security things, but privacy issues. Tons of problems there.

0:15:46.040 --> 0:15:49.480
<v Speaker 1>The largest was one that didn't get a whole lot

0:15:49.560 --> 0:15:52.800
<v Speaker 1>of coverage in the United States, but it was phenomenal

0:15:52.920 --> 0:15:56.400
<v Speaker 1>in its scope. It made the UH the hundred forty

0:15:56.440 --> 0:16:00.000
<v Speaker 1>three million people look like nothing in comparison. It affects

0:16:00.080 --> 0:16:04.400
<v Speaker 1>did India's government I D database, which in turn meant

0:16:04.840 --> 0:16:08.160
<v Speaker 1>that it affected the information of around one point one

0:16:08.560 --> 0:16:13.720
<v Speaker 1>billion people. That's billion with a B. It was all

0:16:13.760 --> 0:16:17.520
<v Speaker 1>made accessible. The fault lay with a state owned utility company.

0:16:18.040 --> 0:16:21.840
<v Speaker 1>They had an unsecured API which gave backdoor access to

0:16:22.040 --> 0:16:25.280
<v Speaker 1>all of this information. So if you got hold of

0:16:25.320 --> 0:16:27.440
<v Speaker 1>this API, which you should be able to do. It's

0:16:27.440 --> 0:16:31.000
<v Speaker 1>an application programming interface, you know, it's meant for developers

0:16:31.000 --> 0:16:34.000
<v Speaker 1>to get hold of. They could get this access to

0:16:34.080 --> 0:16:39.160
<v Speaker 1>all the information, including I D information, biometric information, information

0:16:39.160 --> 0:16:43.680
<v Speaker 1>on connected services like bank accounts. It's mind boggling in

0:16:43.800 --> 0:16:48.520
<v Speaker 1>scope and impact. One point one billion. So yeah, big

0:16:48.560 --> 0:16:53.520
<v Speaker 1>thumbs up on the prediction, Big thumbs down on how

0:16:53.800 --> 0:16:59.240
<v Speaker 1>bad all this is. Prediction number eight. Apple's next iPhone,

0:16:59.280 --> 0:17:02.640
<v Speaker 1>which I'm betting won't have a number associated with it,

0:17:02.640 --> 0:17:06.000
<v Speaker 1>will be an incremental upgrade to the iPhone X or

0:17:06.080 --> 0:17:10.240
<v Speaker 1>iPhone ten. Johnny Eys was once again taking has once

0:17:10.280 --> 0:17:12.480
<v Speaker 1>again taken the helm of design over at Apple, but

0:17:12.560 --> 0:17:14.960
<v Speaker 1>his influence isn't likely to be seen in products for

0:17:15.000 --> 0:17:17.720
<v Speaker 1>another generation or so because it takes more than a

0:17:17.800 --> 0:17:20.560
<v Speaker 1>year of work to produce one of these things. So,

0:17:20.760 --> 0:17:23.520
<v Speaker 1>in other words, when the iPhone ten debuted, the next

0:17:23.520 --> 0:17:27.200
<v Speaker 1>iPhone was already well in development at that stage, and

0:17:27.280 --> 0:17:30.560
<v Speaker 1>this was another one that was a gimme. I think

0:17:30.680 --> 0:17:33.320
<v Speaker 1>I got it absolutely right, So another thumbs up. But

0:17:33.520 --> 0:17:37.399
<v Speaker 1>again I don't think this wasn't necessarily a very uh

0:17:38.080 --> 0:17:44.000
<v Speaker 1>courageous or outgoing or crazy prediction. It was kind of

0:17:44.160 --> 0:17:46.240
<v Speaker 1>you could see the writing on the wall. So the

0:17:46.280 --> 0:17:51.040
<v Speaker 1>iPhone ten R and the iPhone ten S are incremental

0:17:51.080 --> 0:17:53.919
<v Speaker 1>evolutions of the previous models, or if you prefer x

0:17:54.080 --> 0:17:59.880
<v Speaker 1>R and excess. Apple has phased out those previous models

0:18:00.359 --> 0:18:03.280
<v Speaker 1>much earlier than it had done with older iPhone models,

0:18:03.280 --> 0:18:06.159
<v Speaker 1>which was interesting. I guess the biggest change in the

0:18:06.240 --> 0:18:09.119
<v Speaker 1>design was the notch. That's the section at the top

0:18:09.240 --> 0:18:11.040
<v Speaker 1>of the face of the phone where the camera and

0:18:11.119 --> 0:18:15.040
<v Speaker 1>sensors are. Other smartphones have since adopted that notch approach,

0:18:15.080 --> 0:18:18.119
<v Speaker 1>which can sometimes encroach a bit on the screen if

0:18:18.119 --> 0:18:21.600
<v Speaker 1>you're trying to watch something in wide screen format. But yeah,

0:18:21.840 --> 0:18:27.000
<v Speaker 1>no super revolutionary iPhones came out in Prediction number nine.

0:18:27.520 --> 0:18:29.760
<v Speaker 1>While we'll see a rise in cord cutting, which will

0:18:29.760 --> 0:18:32.560
<v Speaker 1>have a big effect on advertising, will also see a

0:18:32.720 --> 0:18:36.400
<v Speaker 1>rise in add blocking online. This will encourage more sites

0:18:36.480 --> 0:18:39.760
<v Speaker 1>to use ad blocker detectors, which will likely inspire more

0:18:39.760 --> 0:18:43.240
<v Speaker 1>people to file lawsuits against such practices. And it's going

0:18:43.320 --> 0:18:45.439
<v Speaker 1>to be a big mess, and it will bring the

0:18:45.520 --> 0:18:48.800
<v Speaker 1>question everyone is worried about closer to the foreground, which

0:18:48.840 --> 0:18:51.679
<v Speaker 1>is how do you make money creating content on the

0:18:51.680 --> 0:18:55.480
<v Speaker 1>Internet in a way that doesn't alienate your audience or

0:18:55.520 --> 0:19:00.399
<v Speaker 1>your customers. This one, I would say, I say my

0:19:00.440 --> 0:19:03.359
<v Speaker 1>thumb was pointing more down than up, maybe somewhere in

0:19:03.400 --> 0:19:07.600
<v Speaker 1>the middle, but kind of leaning downward. The trend has continued. Certainly.

0:19:07.800 --> 0:19:11.040
<v Speaker 1>Many sites are using what ad blocker services called ad

0:19:11.040 --> 0:19:14.520
<v Speaker 1>blocking walls, and that's lines of code that detect if

0:19:14.520 --> 0:19:17.800
<v Speaker 1>someone is using an ad blocker. That's an you know,

0:19:17.920 --> 0:19:21.040
<v Speaker 1>if they're using a browser they're trying to connect to

0:19:21.040 --> 0:19:26.240
<v Speaker 1>a web page, there's a detection that the client request,

0:19:26.680 --> 0:19:30.359
<v Speaker 1>that is, the browser is including an ad blocker, and

0:19:30.440 --> 0:19:33.080
<v Speaker 1>that means the server will send a pop up window

0:19:33.240 --> 0:19:36.560
<v Speaker 1>or something similar saying Mike, we see you're using an

0:19:36.560 --> 0:19:40.520
<v Speaker 1>ad blocker, could you you know, not do that or whatever,

0:19:40.960 --> 0:19:42.640
<v Speaker 1>or even going so far as to block you from

0:19:42.640 --> 0:19:45.119
<v Speaker 1>being able to see the site at all until you

0:19:45.240 --> 0:19:48.639
<v Speaker 1>disabled the ad blocker or white list the site. Now.

0:19:48.640 --> 0:19:51.639
<v Speaker 1>According to the team behind ad block Plus, which is

0:19:51.800 --> 0:19:56.920
<v Speaker 1>a fairly standard response here, they could block those messages,

0:19:57.520 --> 0:19:59.920
<v Speaker 1>but they choose not to because they feel it's important

0:20:00.160 --> 0:20:04.520
<v Speaker 1>that people understand that revenue has to come from somewhere,

0:20:04.960 --> 0:20:06.760
<v Speaker 1>you know, we have to find some way to pay

0:20:06.840 --> 0:20:10.119
<v Speaker 1>for the content we access or else everything falls apart

0:20:10.600 --> 0:20:12.280
<v Speaker 1>because if you don't have any money, like if you're

0:20:12.320 --> 0:20:14.960
<v Speaker 1>not making money from people coming to visit your content,

0:20:15.000 --> 0:20:16.640
<v Speaker 1>you have no way to pay the people who make

0:20:16.720 --> 0:20:22.080
<v Speaker 1>the content and most people are justifiably not super cool

0:20:22.119 --> 0:20:24.400
<v Speaker 1>with the idea of creating stuff for free, because, as

0:20:24.400 --> 0:20:27.359
<v Speaker 1>it turns out, you can't pay the rent that way.

0:20:27.760 --> 0:20:31.639
<v Speaker 1>You gotta make your living. I do this podcast. If

0:20:31.680 --> 0:20:35.080
<v Speaker 1>we didn't have advertising on this podcast, then this podcast

0:20:35.080 --> 0:20:38.440
<v Speaker 1>wouldn't make money, and then there'd be no no money

0:20:38.480 --> 0:20:42.359
<v Speaker 1>made to pay my salary, which means I wouldn't be

0:20:42.359 --> 0:20:44.560
<v Speaker 1>doing this. I wouldn't you know, I'd have to do

0:20:44.640 --> 0:20:46.280
<v Speaker 1>something else in order to make money so I can

0:20:46.400 --> 0:20:50.200
<v Speaker 1>make a living. So that's just the way the world works. Unfortunately,

0:20:50.280 --> 0:20:54.360
<v Speaker 1>there are a lot of advertisers that have created extremely

0:20:54.520 --> 0:20:59.760
<v Speaker 1>irritating and um intrusive ads, and also there have been

0:20:59.800 --> 0:21:04.760
<v Speaker 1>apples of malware posing as legitimate advertising or compromised ads

0:21:04.800 --> 0:21:09.240
<v Speaker 1>that harvest data without user knowledge or consent. So there

0:21:09.240 --> 0:21:12.080
<v Speaker 1>are legitimate uses for ad blockers in the context of

0:21:12.200 --> 0:21:16.159
<v Speaker 1>user privacy and security. You know, it's I can't blame

0:21:16.280 --> 0:21:19.440
<v Speaker 1>someone who says I use an ad blocker because I'm

0:21:19.480 --> 0:21:21.960
<v Speaker 1>scared that if I go to a website that has

0:21:22.000 --> 0:21:24.840
<v Speaker 1>one of these compromised ads on it, I could end

0:21:24.920 --> 0:21:27.520
<v Speaker 1>up with malware on my computer, or I could end

0:21:27.600 --> 0:21:31.720
<v Speaker 1>up with my information stolen without my knowledge, those are

0:21:31.800 --> 0:21:35.840
<v Speaker 1>legitimate concerns, and they're definitely things that have to be addressed.

0:21:36.680 --> 0:21:39.600
<v Speaker 1>I don't think any one party is totally in the

0:21:39.720 --> 0:21:42.520
<v Speaker 1>right here. I think that companies that want to make

0:21:42.560 --> 0:21:45.600
<v Speaker 1>money through advertising, I think that's legitimate. I think the

0:21:45.680 --> 0:21:49.720
<v Speaker 1>advertising companies that serve ads are for the most part legitimate.

0:21:50.240 --> 0:21:52.560
<v Speaker 1>Some of them might be a little more shady. And

0:21:52.600 --> 0:21:54.920
<v Speaker 1>I think the people who are installing ad blockers because

0:21:54.920 --> 0:21:58.040
<v Speaker 1>they want to protect themselves, I think that's a legitimate concern.

0:21:58.560 --> 0:22:01.600
<v Speaker 1>So this is a tough situation. It's there's not an

0:22:01.600 --> 0:22:04.800
<v Speaker 1>easy answer. It's more of a dilemma. Google Chrome version

0:22:04.800 --> 0:22:07.560
<v Speaker 1>seventy one, which came out just before I recorded this episode,

0:22:07.840 --> 0:22:10.680
<v Speaker 1>has an expanded ad blocker in it that's meant to

0:22:10.720 --> 0:22:14.760
<v Speaker 1>protect people from abusive AD experiences. This is significant largely

0:22:14.760 --> 0:22:18.119
<v Speaker 1>because Google makes his money through advertising, so it's a

0:22:18.160 --> 0:22:21.439
<v Speaker 1>company that both depends upon ads for revenue and recognizes

0:22:21.520 --> 0:22:25.400
<v Speaker 1>how they can be predatory nor that people can compromise them.

0:22:25.640 --> 0:22:29.760
<v Speaker 1>But there was no rash of lawsuits that popped up

0:22:29.800 --> 0:22:33.160
<v Speaker 1>around this, as I had predicted. Ad block Plus did

0:22:33.160 --> 0:22:35.760
<v Speaker 1>win a legal battle in Germany in April, but we

0:22:35.840 --> 0:22:38.080
<v Speaker 1>didn't see a ton of people take companies to court

0:22:38.119 --> 0:22:41.359
<v Speaker 1>for ad blocking walls. So I'd say this one again

0:22:41.480 --> 0:22:43.399
<v Speaker 1>is kind of a thumb in the middle, maybe leaning

0:22:43.440 --> 0:22:46.920
<v Speaker 1>downward a bit, because it wasn't It wasn't that rash

0:22:46.920 --> 0:22:49.400
<v Speaker 1>of lawsuits that I thought was going to happen. Prediction

0:22:49.480 --> 0:22:53.120
<v Speaker 1>number ten that we were headed toward a subscription service

0:22:53.200 --> 0:22:56.760
<v Speaker 1>crash in which we would see such a saturation in

0:22:56.800 --> 0:23:00.520
<v Speaker 1>the market for subscription based entertainment service is I'm talking

0:23:00.520 --> 0:23:04.159
<v Speaker 1>about stuff like Netflix, Hulu, YouTube Premium, that kind of

0:23:04.160 --> 0:23:07.720
<v Speaker 1>stuff that there would be a general backlash, And I said,

0:23:07.760 --> 0:23:11.000
<v Speaker 1>I think we'll get through before this happens. So it's

0:23:11.040 --> 0:23:13.879
<v Speaker 1>couching my bets here, but things will be heating up

0:23:13.920 --> 0:23:16.600
<v Speaker 1>towards the end of the year with more consumers disenchanted

0:23:16.600 --> 0:23:19.720
<v Speaker 1>with how many different competing services there are and what

0:23:19.880 --> 0:23:22.760
<v Speaker 1>they're expected to do to get all the content they want.

0:23:23.560 --> 0:23:28.000
<v Speaker 1>So I'd say I've got thumbs down mostly. I mean, yes,

0:23:28.040 --> 0:23:31.720
<v Speaker 1>there is some discussion about this. There are growing concerns

0:23:31.800 --> 0:23:35.480
<v Speaker 1>that with the huge number of services that are popping

0:23:35.560 --> 0:23:38.399
<v Speaker 1>up that if you wanted to get everything that you liked,

0:23:38.840 --> 0:23:41.879
<v Speaker 1>you'd be subscribing to, you know, half a dozen or

0:23:41.960 --> 0:23:44.920
<v Speaker 1>more services, and if you're talking about ten dollars a month,

0:23:44.960 --> 0:23:47.120
<v Speaker 1>that starts to add up pretty quickly. But we did

0:23:47.119 --> 0:23:51.360
<v Speaker 1>get through without some sort of reckoning. But I think

0:23:51.440 --> 0:23:55.440
<v Speaker 1>one is still coming. As of December twelve, there are

0:23:55.520 --> 0:23:58.879
<v Speaker 1>numerous new streaming services that are planned to join the

0:23:58.920 --> 0:24:02.120
<v Speaker 1>ones already out there are so right now we've got

0:24:02.119 --> 0:24:06.760
<v Speaker 1>stuff like Netflix, Hulu, Amazon Prime Video, YouTube Premium, but

0:24:06.880 --> 0:24:10.560
<v Speaker 1>now we're gonna also get Disney Plus. There's an unnamed

0:24:10.600 --> 0:24:14.359
<v Speaker 1>Apple streaming video service on the way. Warner Media under

0:24:14.400 --> 0:24:17.119
<v Speaker 1>a T and T, assuming the appeals court upholds the

0:24:17.200 --> 0:24:21.280
<v Speaker 1>legality of that acquisition, has one plan. There's probably more

0:24:21.359 --> 0:24:23.639
<v Speaker 1>that are going to launch in twenty nineteen, but the

0:24:23.640 --> 0:24:28.440
<v Speaker 1>crash hasn't happened yet. The backlash hasn't been widespread. I've

0:24:28.480 --> 0:24:31.720
<v Speaker 1>seen a few articles talking about this, but I haven't

0:24:31.800 --> 0:24:37.280
<v Speaker 1>seen a general like reaction or resistance to it. I

0:24:37.320 --> 0:24:39.639
<v Speaker 1>just I think it's still coming. So thumbs down on

0:24:39.640 --> 0:24:43.240
<v Speaker 1>that one prediction number eleven. This was a prediction about

0:24:43.280 --> 0:24:47.720
<v Speaker 1>dollars spent on e commerce versus retail stores. But I'm

0:24:47.720 --> 0:24:51.199
<v Speaker 1>not even gonna bother talking about what the specific prediction was,

0:24:51.240 --> 0:24:53.920
<v Speaker 1>because honestly, and this is just me having to come

0:24:53.960 --> 0:24:56.719
<v Speaker 1>forward and admit something. It was based off of me

0:24:56.800 --> 0:25:00.160
<v Speaker 1>being an idiot, at least that's my guess. I had

0:25:00.200 --> 0:25:02.119
<v Speaker 1>not looked at this prediction since I had made it,

0:25:02.400 --> 0:25:04.520
<v Speaker 1>so I don't know what frame of mind I was

0:25:04.560 --> 0:25:06.640
<v Speaker 1>in when I made it, but was clearly based off

0:25:06.680 --> 0:25:12.080
<v Speaker 1>of absolutely the wrong conclusions I was. I don't know

0:25:12.119 --> 0:25:15.360
<v Speaker 1>where I got the idea that e commerce had really

0:25:15.400 --> 0:25:17.879
<v Speaker 1>started to catch up to retail. That's not the case.

0:25:19.040 --> 0:25:22.000
<v Speaker 1>E Commerce is growing year over year, but it makes

0:25:22.080 --> 0:25:26.159
<v Speaker 1>up less than fifteen percent of all dollars spent UH

0:25:26.280 --> 0:25:30.840
<v Speaker 1>in that sense, like retail is still way way ahead.

0:25:32.040 --> 0:25:35.720
<v Speaker 1>Physical stores are in the lead, though the growth they

0:25:35.760 --> 0:25:38.600
<v Speaker 1>experience you over year is much lower than what online

0:25:38.760 --> 0:25:43.199
<v Speaker 1>online sales are experiencing. So both brick and mortar stores

0:25:43.640 --> 0:25:47.560
<v Speaker 1>and e commerce are seeing year over year growth, but

0:25:47.960 --> 0:25:50.000
<v Speaker 1>e commerce is seeing way more of it. So e

0:25:50.080 --> 0:25:54.080
<v Speaker 1>commerce is getting bigger, faster, but retail is still way ahead.

0:25:55.119 --> 0:25:57.120
<v Speaker 1>Maybe that was my mistake. Maybe I was looking at

0:25:57.160 --> 0:26:01.600
<v Speaker 1>growth figures rather than the overall figures, and that's a

0:26:01.600 --> 0:26:04.600
<v Speaker 1>good lesson for me to learn. E Commerce sales could

0:26:04.600 --> 0:26:08.960
<v Speaker 1>increase by at and retail sales could increase by just two.

0:26:09.600 --> 0:26:12.040
<v Speaker 1>And maybe that's what I was thinking, was that, you know,

0:26:12.080 --> 0:26:14.719
<v Speaker 1>because e commerce sales were increasing so fast by the way,

0:26:14.760 --> 0:26:16.879
<v Speaker 1>I was just making up those numbers. But let's e

0:26:17.000 --> 0:26:20.800
<v Speaker 1>commerce sales are increasing so fast, they're ahead. That's not

0:26:20.840 --> 0:26:23.720
<v Speaker 1>what that means. It just means they're growing faster. And

0:26:23.800 --> 0:26:26.640
<v Speaker 1>I know all you know that I'm reminding myself that

0:26:27.800 --> 0:26:30.840
<v Speaker 1>it's it's a weird mistake I made. I don't know

0:26:30.880 --> 0:26:34.960
<v Speaker 1>what I was thinking. So this prediction was so incredibly wrong.

0:26:36.080 --> 0:26:38.680
<v Speaker 1>That's not just thumbs down, it's everything down. I mean,

0:26:38.760 --> 0:26:42.680
<v Speaker 1>I was just I don't know, but it just reminds me.

0:26:42.760 --> 0:26:45.879
<v Speaker 1>I am human. I make mistakes. It's embarrassing, but I

0:26:45.960 --> 0:26:49.840
<v Speaker 1>decided I had to at least acknowledge it. Let's move on.

0:26:49.920 --> 0:26:52.600
<v Speaker 1>Before you know, I just throw myself at the wall.

0:26:53.520 --> 0:26:56.360
<v Speaker 1>So prediction number twelve. Google will start to roll out

0:26:56.440 --> 0:27:00.200
<v Speaker 1>WiFi based internet services to some cities, similar to how

0:27:00.200 --> 0:27:02.879
<v Speaker 1>it rolled out Google Fiber, but with the goal of

0:27:02.960 --> 0:27:07.080
<v Speaker 1>having faster deployment. The company will encounter similar issues involving

0:27:07.119 --> 0:27:09.680
<v Speaker 1>where they can set up their transmitters, you know, their towers,

0:27:10.080 --> 0:27:11.679
<v Speaker 1>but it won't be nearly as tough as it was

0:27:11.720 --> 0:27:14.760
<v Speaker 1>to get clearance for stuff like utility pole access. This

0:27:14.880 --> 0:27:18.400
<v Speaker 1>is another thumbs down. It did not happen. Google Fiber

0:27:18.600 --> 0:27:22.359
<v Speaker 1>is still sort of kind of a thing. In the

0:27:22.400 --> 0:27:26.120
<v Speaker 1>places where Google actually began to deploy Google Fiber, there's

0:27:26.119 --> 0:27:29.639
<v Speaker 1>still service there, although I read a report that a

0:27:29.680 --> 0:27:32.199
<v Speaker 1>lot of that service went out in Kansas City just

0:27:32.280 --> 0:27:35.359
<v Speaker 1>before the recording of this episode. But the company has

0:27:35.400 --> 0:27:38.080
<v Speaker 1>pretty much put a stop to doing more of that.

0:27:38.160 --> 0:27:40.200
<v Speaker 1>They they've said they're not going to deploy in any

0:27:40.240 --> 0:27:43.760
<v Speaker 1>other cities. Uh. They never did really fully deploy in

0:27:43.800 --> 0:27:47.320
<v Speaker 1>Atlanta at last I saw. They still say they're going

0:27:47.560 --> 0:27:50.440
<v Speaker 1>to get around to it, but I haven't heard anything

0:27:50.480 --> 0:27:53.520
<v Speaker 1>definitive about that. It hasn't Maine moves to build out

0:27:53.520 --> 0:27:57.840
<v Speaker 1>wireless services either. However, five G technology is right around

0:27:57.840 --> 0:28:01.480
<v Speaker 1>the corner. That's the next generation and of wireless data

0:28:01.520 --> 0:28:05.240
<v Speaker 1>transmission technology, so we might see many companies jump in

0:28:05.280 --> 0:28:08.840
<v Speaker 1>to provide wireless broadband connectivity and shake up the market.

0:28:08.920 --> 0:28:13.840
<v Speaker 1>They're already talks about laptops and other technologies having five

0:28:13.920 --> 0:28:17.520
<v Speaker 1>G capability baked into the systems. I'm sure i'll see

0:28:17.560 --> 0:28:19.359
<v Speaker 1>more of that when I go to c e S

0:28:19.400 --> 0:28:24.720
<v Speaker 1>in January. But don't hold your breath, because it's still

0:28:24.720 --> 0:28:28.040
<v Speaker 1>going to require building out the infrastructure to support all that.

0:28:28.440 --> 0:28:30.679
<v Speaker 1>We probably will see some of that coming online in

0:28:30.680 --> 0:28:33.240
<v Speaker 1>twenty nineteen, but I suspect most of it won't happen

0:28:33.320 --> 0:28:36.600
<v Speaker 1>until well. I've got a little bit more to say

0:28:36.960 --> 0:28:39.880
<v Speaker 1>about the predictions I made for but before I get

0:28:39.880 --> 0:28:43.160
<v Speaker 1>into that, let's take another quick break to thank our sponsor.

0:28:50.680 --> 0:28:55.360
<v Speaker 1>Prediction number thirteen. By the end of automation will have

0:28:55.400 --> 0:28:59.400
<v Speaker 1>eliminated more jobs than it creates. This isn't necessarily the endgame.

0:28:59.720 --> 0:29:02.280
<v Speaker 1>It will create more jobs along the way, and maybe

0:29:02.280 --> 0:29:05.160
<v Speaker 1>we'll see things even out or even see automation create

0:29:05.240 --> 0:29:08.360
<v Speaker 1>more jobs that displaces than the short term as in

0:29:08.440 --> 0:29:10.920
<v Speaker 1>the next few years, it's going to be pretty bleak

0:29:11.000 --> 0:29:13.800
<v Speaker 1>for a lot of people. Uh no, thumbs down. I

0:29:13.880 --> 0:29:16.960
<v Speaker 1>must have been watching episodes of Black Mirror before I

0:29:17.000 --> 0:29:21.560
<v Speaker 1>did that prediction. Automation did not eliminate more jobs than

0:29:21.600 --> 0:29:25.760
<v Speaker 1>it created, not by a long shot. There are increasing

0:29:25.800 --> 0:29:28.760
<v Speaker 1>concerns about the impact increased automation is going to have

0:29:28.920 --> 0:29:31.920
<v Speaker 1>over the next few years, not just from eliminating jobs,

0:29:31.960 --> 0:29:35.760
<v Speaker 1>but also in how automation will incorporate into jobs, whether

0:29:35.920 --> 0:29:38.200
<v Speaker 1>it will end up being more profitable to do that.

0:29:39.080 --> 0:29:42.280
<v Speaker 1>The effect it might have on things like unionization is

0:29:42.320 --> 0:29:44.800
<v Speaker 1>also a concern, and there are other concerns as well,

0:29:44.840 --> 0:29:48.440
<v Speaker 1>But it has not eliminated more jobs than it created.

0:29:48.480 --> 0:29:52.960
<v Speaker 1>That is, Gardner still predicts that by five one out

0:29:52.960 --> 0:29:55.600
<v Speaker 1>of every three jobs will be done by robots or

0:29:55.680 --> 0:29:59.640
<v Speaker 1>computers or some combination of those, but it also says

0:29:59.680 --> 0:30:03.320
<v Speaker 1>that's starting a I will be creating more jobs than

0:30:03.360 --> 0:30:07.880
<v Speaker 1>it eliminates. So while we will have a robot or

0:30:07.920 --> 0:30:11.760
<v Speaker 1>AI taking over one out of every three jobs, in general,

0:30:11.800 --> 0:30:14.280
<v Speaker 1>there will be more jobs for everyone, not just robots,

0:30:14.280 --> 0:30:17.320
<v Speaker 1>but for people, and that these technologies will be used

0:30:17.320 --> 0:30:20.200
<v Speaker 1>to help companies become more efficient and profitable, but not

0:30:20.280 --> 0:30:24.040
<v Speaker 1>necessarily at the expense of human employees. Rather, the machines

0:30:24.080 --> 0:30:27.480
<v Speaker 1>will help humans do their jobs, not make humans superfluous.

0:30:28.120 --> 0:30:31.440
<v Speaker 1>So that's great. That's a very optimistic view of what

0:30:31.880 --> 0:30:34.920
<v Speaker 1>automation will do, and it's very different from the fears

0:30:34.960 --> 0:30:36.920
<v Speaker 1>that have been talked about over the last couple of years.

0:30:37.000 --> 0:30:41.200
<v Speaker 1>Here's hoping the optimistic one is right. Prediction number fourteen.

0:30:41.920 --> 0:30:44.600
<v Speaker 1>The trend that started in twenty seen of women stepping

0:30:44.600 --> 0:30:47.360
<v Speaker 1>forward to reveal how they have been mistreated abused and

0:30:47.400 --> 0:30:51.200
<v Speaker 1>worse will sadly continue in twenty eighteen. I say sadly

0:30:51.280 --> 0:30:54.400
<v Speaker 1>not to suggest these women shouldn't come forward, but rather

0:30:54.480 --> 0:30:57.560
<v Speaker 1>that I suspect the problems they've experienced are deeply ingrained

0:30:57.600 --> 0:31:00.800
<v Speaker 1>in our society in general, anti tech world in particular.

0:31:01.080 --> 0:31:03.640
<v Speaker 1>I expect we'll see a dozen or more major stories

0:31:03.640 --> 0:31:08.240
<v Speaker 1>about harassment or worse in the technosphere. In My hope

0:31:08.280 --> 0:31:11.080
<v Speaker 1>is that though these stories are, through these stories, we

0:31:11.120 --> 0:31:13.720
<v Speaker 1>can shake things out to make a better environment for

0:31:13.760 --> 0:31:19.200
<v Speaker 1>everyone moving forward. It's going to be painful, but absolutely necessary. Yeah,

0:31:19.240 --> 0:31:21.920
<v Speaker 1>that definitely happened. That's another I hate to say thumbs

0:31:22.000 --> 0:31:24.840
<v Speaker 1>up because I didn't want this. This is another prediction

0:31:24.880 --> 0:31:27.880
<v Speaker 1>I didn't want to be true. I just felt pretty

0:31:27.880 --> 0:31:30.600
<v Speaker 1>certain it was true. And the Me Too movement really

0:31:30.640 --> 0:31:34.640
<v Speaker 1>took center stage in many arenas, not just the tech industry,

0:31:34.840 --> 0:31:37.760
<v Speaker 1>you know, the entertainment industry certainly had its share as well.

0:31:38.400 --> 0:31:43.040
<v Speaker 1>Uh not even the overall business industry was the only

0:31:43.040 --> 0:31:45.440
<v Speaker 1>place where this happened. We saw it everywhere, and it

0:31:45.520 --> 0:31:48.160
<v Speaker 1>absolutely should. I want to be clear about that, the

0:31:48.200 --> 0:31:52.880
<v Speaker 1>me too movement should take center stage because honestly, it

0:31:53.040 --> 0:31:56.960
<v Speaker 1>harms everybody if we don't address these problems, and that

0:31:57.040 --> 0:32:01.200
<v Speaker 1>includes just acknowledging that there are, in fact problems. If

0:32:01.240 --> 0:32:05.120
<v Speaker 1>we say no, there's no problem, we're making things worse

0:32:05.160 --> 0:32:10.680
<v Speaker 1>for everyone. By acknowledging the problems, by confronting the fact

0:32:10.720 --> 0:32:14.479
<v Speaker 1>that they exist, and then working to resolve them and

0:32:14.560 --> 0:32:18.320
<v Speaker 1>to prevent those things from happening in the future, we

0:32:18.480 --> 0:32:21.880
<v Speaker 1>can create a better environment for everyone, not just the

0:32:21.880 --> 0:32:24.800
<v Speaker 1>people who are being victimized, but the people who are

0:32:24.800 --> 0:32:27.480
<v Speaker 1>being victimized. If if things are better for them, then

0:32:27.520 --> 0:32:31.120
<v Speaker 1>they get to do better things, they get to contribute

0:32:31.120 --> 0:32:35.040
<v Speaker 1>more back to society, so we all benefit when we

0:32:35.120 --> 0:32:38.840
<v Speaker 1>improve things. This isn't just a you know, not all

0:32:38.920 --> 0:32:42.239
<v Speaker 1>men type of argument sort of thing, which is by

0:32:42.280 --> 0:32:45.960
<v Speaker 1>the way, I'm exhausted hearing about that. I think everyone

0:32:46.080 --> 0:32:50.959
<v Speaker 1>understands that not every person of the male gender is

0:32:52.120 --> 0:32:56.560
<v Speaker 1>constantly being a predator or anything like that, but rather

0:32:56.680 --> 0:32:59.640
<v Speaker 1>that we have enough of that, and enough of that

0:32:59.800 --> 0:33:07.440
<v Speaker 1>is baked in systemically and things like business, politics, general culture,

0:33:08.200 --> 0:33:10.840
<v Speaker 1>that we really need to address it. We really need

0:33:10.840 --> 0:33:14.920
<v Speaker 1>to acknowledge it and figure out how to fix things

0:33:15.280 --> 0:33:18.440
<v Speaker 1>to make the environment better for everyone, and again, we

0:33:18.520 --> 0:33:21.320
<v Speaker 1>all benefit from this. This is something we should be selfish.

0:33:21.360 --> 0:33:23.440
<v Speaker 1>We should all want this to happen so that we

0:33:23.480 --> 0:33:28.400
<v Speaker 1>get better stuff. Alright, Prediction number fifteen. No, wow, I

0:33:28.520 --> 0:33:31.240
<v Speaker 1>just read it again. Yeah, this one was dumb. Star

0:33:31.320 --> 0:33:35.160
<v Speaker 1>Sitisen will not emerge from beta, in which seems the

0:33:35.240 --> 0:33:38.960
<v Speaker 1>safest bet ever. A Star Citizen is a computer game.

0:33:39.160 --> 0:33:43.400
<v Speaker 1>It was kick started in tw It also has had

0:33:43.720 --> 0:33:46.160
<v Speaker 1>various ways of raising money. It raised more than a

0:33:46.240 --> 0:33:49.800
<v Speaker 1>hundred seventy million dollars. In fact, that number is old,

0:33:49.840 --> 0:33:52.320
<v Speaker 1>that's a year old number that was from when I

0:33:52.360 --> 0:33:56.480
<v Speaker 1>was making these predictions. But it's a persistent science fiction game.

0:33:57.080 --> 0:34:01.720
<v Speaker 1>Sold spaceships and the possibility of purchasing in game real

0:34:01.880 --> 0:34:05.400
<v Speaker 1>estate and also at facial capture technology so that you're

0:34:05.440 --> 0:34:08.200
<v Speaker 1>supposedly gonna be able to transmit your expressions onto your character.

0:34:08.320 --> 0:34:10.680
<v Speaker 1>That kind of stuff. This is kind of like predicting

0:34:10.719 --> 0:34:14.360
<v Speaker 1>water will continue to be wet. Star says, and is

0:34:14.360 --> 0:34:16.560
<v Speaker 1>still in development. It has not been released, so big

0:34:16.600 --> 0:34:18.920
<v Speaker 1>thumbs up here. However, I do want to say a

0:34:18.920 --> 0:34:22.680
<v Speaker 1>little more about it. The most recent version of Star Citizen,

0:34:22.719 --> 0:34:26.839
<v Speaker 1>which has parts of the game finished, has the designation

0:34:26.920 --> 0:34:29.440
<v Speaker 1>Alpha three point three, so it's not even in beta.

0:34:29.880 --> 0:34:32.200
<v Speaker 1>But while it's still in development. There are parts of

0:34:32.239 --> 0:34:35.560
<v Speaker 1>the game that are playable. People who supported it and

0:34:35.600 --> 0:34:38.040
<v Speaker 1>are in the alpha can actually play those parts of

0:34:38.040 --> 0:34:41.239
<v Speaker 1>the game. And I'm talking about stuff that's legitimately impressive.

0:34:41.360 --> 0:34:44.800
<v Speaker 1>This isn't like wire frames that just tell you, Okay,

0:34:44.800 --> 0:34:47.520
<v Speaker 1>well here's a placeholder. It's gonna look really awesome later on.

0:34:47.840 --> 0:34:49.680
<v Speaker 1>So I don't mean to say the game is never

0:34:49.719 --> 0:34:53.640
<v Speaker 1>coming out. I don't mean that the developers aren't working hard.

0:34:53.680 --> 0:34:57.680
<v Speaker 1>They clearly are. The evidence is there. It's a hugely

0:34:57.760 --> 0:35:02.680
<v Speaker 1>ambitious project. Hope fully it's a hugely ambitious project that

0:35:02.800 --> 0:35:05.799
<v Speaker 1>one day will be a full game, even if that

0:35:05.880 --> 0:35:09.000
<v Speaker 1>means a game that gets continuous updates and additional content,

0:35:09.520 --> 0:35:13.760
<v Speaker 1>Maybe the kind of game that releases and the full

0:35:13.840 --> 0:35:18.279
<v Speaker 1>game part continues down the road. I'm hoping for that.

0:35:18.840 --> 0:35:21.839
<v Speaker 1>Right now, it's still one of those things that people

0:35:21.880 --> 0:35:24.480
<v Speaker 1>are kind of worried will always be in development and

0:35:24.560 --> 0:35:28.719
<v Speaker 1>never be released. Prediction number sixteen. There will be a

0:35:28.760 --> 0:35:32.279
<v Speaker 1>bitcoin value crash in ten but it will recover at

0:35:32.360 --> 0:35:34.600
<v Speaker 1>least to the point where it returns to around ten

0:35:35.000 --> 0:35:37.920
<v Speaker 1>dollars per bitcoin, but at some point the value will

0:35:38.000 --> 0:35:41.319
<v Speaker 1>drop significantly. For a while, I was wrong about this,

0:35:41.360 --> 0:35:43.960
<v Speaker 1>I would say, um, I was wrong about the timing

0:35:44.000 --> 0:35:45.839
<v Speaker 1>and I was wrong about the recovery, so I'm gonna

0:35:45.840 --> 0:35:50.360
<v Speaker 1>give a thumbs down on this. However, the important note

0:35:50.360 --> 0:35:53.319
<v Speaker 1>to to really know here is that bitcoin's value did

0:35:53.640 --> 0:35:57.879
<v Speaker 1>drop drastically in twenty eighteen, but it did so over

0:35:57.920 --> 0:36:01.400
<v Speaker 1>the course of the entire year. It wasn't like a crash.

0:36:01.680 --> 0:36:05.759
<v Speaker 1>It wasn't a moment where the value plunged lower and

0:36:05.800 --> 0:36:09.080
<v Speaker 1>then never recovered or recovered up to ten thousand dollars,

0:36:09.120 --> 0:36:11.959
<v Speaker 1>because it hasn't done that yet. Instead, what we've seen

0:36:12.440 --> 0:36:16.640
<v Speaker 1>is this steady decline. The value UH started at around

0:36:16.680 --> 0:36:19.839
<v Speaker 1>fifteen thousand dollars at the beginning of the year, and

0:36:19.920 --> 0:36:22.760
<v Speaker 1>as I record this, the value is closer to three thousand,

0:36:22.840 --> 0:36:26.840
<v Speaker 1>four hundred dollars per bitcoin. So fifteen thousand to three thousand,

0:36:26.840 --> 0:36:30.880
<v Speaker 1>four hundred that's a huge drop. It's significant, But again,

0:36:30.920 --> 0:36:33.759
<v Speaker 1>it happened over the course of twelve months. There wasn't

0:36:33.760 --> 0:36:37.439
<v Speaker 1>a sudden crash. There were some pronounced dips throughout the year,

0:36:37.960 --> 0:36:40.960
<v Speaker 1>and by that I mean there were some pronounced drops

0:36:40.960 --> 0:36:44.839
<v Speaker 1>in value, not there were pronounced idiots. I'm sure there

0:36:44.880 --> 0:36:48.160
<v Speaker 1>were those two, but not necessarily connected to bitcoin. One

0:36:48.160 --> 0:36:51.440
<v Speaker 1>of them is talking into a microphone right now. Prediction

0:36:51.520 --> 0:36:55.040
<v Speaker 1>number seventeen. We're going to see a big, serious push

0:36:55.040 --> 0:37:00.360
<v Speaker 1>and podcasting. This is fuel from successes like S Town

0:37:01.239 --> 0:37:04.120
<v Speaker 1>in the serial series, as well as some of the

0:37:04.120 --> 0:37:06.719
<v Speaker 1>old standards that have stuck around for years. Cough, tech

0:37:06.760 --> 0:37:10.360
<v Speaker 1>stuff cough. Expect to see a flood of new shows,

0:37:10.440 --> 0:37:12.680
<v Speaker 1>some of which are limited series with a set number

0:37:12.719 --> 0:37:15.520
<v Speaker 1>of episodes, others that are open ended and will publish

0:37:15.560 --> 0:37:18.640
<v Speaker 1>until people stop listening or the hosts decide to do

0:37:18.719 --> 0:37:21.360
<v Speaker 1>something else. But we are going to see more development

0:37:21.400 --> 0:37:23.640
<v Speaker 1>of programming in this space as if it were more

0:37:23.680 --> 0:37:28.080
<v Speaker 1>akin to radio or TV series. Big thumbs up here,

0:37:28.400 --> 0:37:32.440
<v Speaker 1>It's absolutely true. And remember I made this prediction before

0:37:32.600 --> 0:37:37.120
<v Speaker 1>I Heart Radio came in and acquired our company. We

0:37:37.200 --> 0:37:42.960
<v Speaker 1>saw tons of new podcasts debut in, including mini series,

0:37:43.440 --> 0:37:46.640
<v Speaker 1>and I feel like maybe half of them came out

0:37:46.680 --> 0:37:48.840
<v Speaker 1>of our office. But at the time I made this prediction,

0:37:48.880 --> 0:37:50.920
<v Speaker 1>I didn't know that was gonna happen. But yeah, we

0:37:51.000 --> 0:37:54.399
<v Speaker 1>put out a lot of podcasts. Um nothing quite got

0:37:54.440 --> 0:37:56.520
<v Speaker 1>the buzz of S Town. I feel I don't think

0:37:56.560 --> 0:38:01.160
<v Speaker 1>anything quite captured the public. Uh, you know, like the

0:38:01.239 --> 0:38:04.520
<v Speaker 1>water cooler talk like s Town did, but people still

0:38:04.920 --> 0:38:07.800
<v Speaker 1>were listening. There were numerous shows that debuted in twenty eighteen.

0:38:08.040 --> 0:38:12.200
<v Speaker 1>They included high profile podcasts, celebrity hosted shows. A lot

0:38:12.600 --> 0:38:16.000
<v Speaker 1>of true true crime shows came out in ten and

0:38:16.120 --> 0:38:21.640
<v Speaker 1>more Prediction number eighteen. More bots, whether it's voice activated assistants,

0:38:21.719 --> 0:38:25.680
<v Speaker 1>automated customer service representatives, or some other implementation, will see

0:38:25.680 --> 0:38:27.680
<v Speaker 1>a growth in the use of boats as a point

0:38:27.719 --> 0:38:31.400
<v Speaker 1>of service. Thumbs up. We saw a ton of this,

0:38:31.680 --> 0:38:35.440
<v Speaker 1>and we saw a hint of the future, like Google Duplex,

0:38:35.520 --> 0:38:40.000
<v Speaker 1>which was equally impressive and unsettling. That's when Google would

0:38:40.000 --> 0:38:43.640
<v Speaker 1>show off this uh, this artificial intelligent assistant. During the

0:38:43.680 --> 0:38:49.840
<v Speaker 1>IO event Um, they had someone tell the Google Assistant

0:38:50.400 --> 0:38:55.200
<v Speaker 1>make a make a hair appointment for me at such

0:38:55.239 --> 0:38:59.480
<v Speaker 1>and such a place around noon. The assistant made a

0:38:59.520 --> 0:39:01.920
<v Speaker 1>phone call to a real human being at a hair

0:39:01.960 --> 0:39:04.520
<v Speaker 1>salon and actual we got to listen to the recording

0:39:04.560 --> 0:39:08.480
<v Speaker 1>of the phone call and the assistant, this artificial intelligent

0:39:08.680 --> 0:39:15.600
<v Speaker 1>assistant made the arrangements and it sounded almost human like.

0:39:15.719 --> 0:39:20.239
<v Speaker 1>The assistant actually said things like uh um while responding

0:39:20.560 --> 0:39:23.759
<v Speaker 1>like a human would, like we don't have anything in noon?

0:39:23.760 --> 0:39:27.600
<v Speaker 1>Would one o'clockwork, Um, do you have anything between ten

0:39:27.680 --> 0:39:29.840
<v Speaker 1>am and noon? That was an actual thing that the

0:39:29.880 --> 0:39:35.319
<v Speaker 1>assistant said. So that was impressive and a little unsettling,

0:39:35.840 --> 0:39:38.040
<v Speaker 1>but it gave us a hint at what might be

0:39:38.080 --> 0:39:41.400
<v Speaker 1>to come. There have actually been discussions since then that

0:39:41.719 --> 0:39:46.680
<v Speaker 1>such an assistant should identify itself at the beginning of

0:39:46.680 --> 0:39:50.080
<v Speaker 1>a call that it is in fact an AI assistant

0:39:50.120 --> 0:39:53.319
<v Speaker 1>and not a human being, because there's a worry that

0:39:53.360 --> 0:39:57.160
<v Speaker 1>it would feel deceptive and creepy otherwise. So how do

0:39:57.160 --> 0:39:58.959
<v Speaker 1>you think I did. I think I had a better

0:39:58.960 --> 0:40:01.240
<v Speaker 1>success rate this year than and I did most years,

0:40:01.600 --> 0:40:05.200
<v Speaker 1>apart from that ludicrous mistake I made about online sales

0:40:05.280 --> 0:40:08.160
<v Speaker 1>versus retail. I still don't know where I got information

0:40:08.200 --> 0:40:11.319
<v Speaker 1>that made me think something that was so far from

0:40:11.360 --> 0:40:15.319
<v Speaker 1>the truth was accurate. It blows my mind. It would

0:40:15.320 --> 0:40:17.520
<v Speaker 1>have been like saying we're gonna find out in twenty

0:40:17.600 --> 0:40:22.160
<v Speaker 1>nineteen that the Earth is flat. It just seems ridiculous. Now. Anyway,

0:40:22.440 --> 0:40:26.640
<v Speaker 1>those were my predictions for I will not be making

0:40:26.640 --> 0:40:30.359
<v Speaker 1>predictions for twenty nineteen. I've decided this year to do

0:40:30.440 --> 0:40:33.800
<v Speaker 1>something different. I'm going to make a wish list. So

0:40:34.040 --> 0:40:36.800
<v Speaker 1>in our next episode, you will hear what I'm wishing

0:40:36.880 --> 0:40:40.560
<v Speaker 1>for for twenty nineteen, and I'll explain more on that episode.

0:40:40.920 --> 0:40:43.960
<v Speaker 1>But it has been a heck of a year, a

0:40:44.080 --> 0:40:47.040
<v Speaker 1>year where for six months of the year I was

0:40:47.120 --> 0:40:51.279
<v Speaker 1>doing five episodes a week and we're back down to

0:40:51.400 --> 0:40:55.160
<v Speaker 1>doing three episodes a week now. It's two new ones

0:40:55.200 --> 0:40:57.839
<v Speaker 1>in one classic, and that's going to give me a

0:40:57.840 --> 0:41:01.640
<v Speaker 1>lot more opportunity to really focus on individual shows and

0:41:01.680 --> 0:41:04.000
<v Speaker 1>make them the best I can. So I'm very happy

0:41:04.000 --> 0:41:05.719
<v Speaker 1>about that. Plus I'm gonna be working on some other

0:41:05.719 --> 0:41:08.120
<v Speaker 1>stuff outside of Tech Stuff, so keep an ear out

0:41:08.160 --> 0:41:11.120
<v Speaker 1>for that. If you guys have any suggestions for future

0:41:11.160 --> 0:41:14.240
<v Speaker 1>episodes of tech Stuff, because it's gonna keep on going,

0:41:15.080 --> 0:41:17.520
<v Speaker 1>send me an email. The addresses tech Stuff at how

0:41:17.560 --> 0:41:20.040
<v Speaker 1>stuff works dot com. Make sure you pop on over

0:41:20.080 --> 0:41:23.440
<v Speaker 1>to our website that's over at tech stuff podcast dot com.

0:41:23.520 --> 0:41:25.719
<v Speaker 1>That's where you can find ways to contact me on

0:41:25.719 --> 0:41:31.439
<v Speaker 1>Facebook or Twitter, and don't forget to visit our merchandise

0:41:31.600 --> 0:41:34.560
<v Speaker 1>stores over at t public dot com slash tech Stuff.

0:41:34.600 --> 0:41:37.360
<v Speaker 1>I'm just watching try try and guess what I'm gonna

0:41:37.400 --> 0:41:40.520
<v Speaker 1>say next. She thinks that I do this exactly the

0:41:40.600 --> 0:41:44.200
<v Speaker 1>same way at the end of every episode, and she's wrong,

0:41:44.239 --> 0:41:47.480
<v Speaker 1>I tell you, but seriously, go to our merchandise store

0:41:47.480 --> 0:41:49.560
<v Speaker 1>because if you buy stuff, it helps our show and

0:41:49.600 --> 0:41:54.000
<v Speaker 1>we greatly appreciate it. I'll see you guys in twenty nineteen,

0:41:55.160 --> 0:42:03.839
<v Speaker 1>and I'll talk to you again really soon. For more

0:42:03.880 --> 0:42:06.200
<v Speaker 1>on this and thousands of other topics, is it how

0:42:06.239 --> 0:42:17.080
<v Speaker 1>stuff works dot com