WEBVTT - Facebook Data Gaffe; Alexa Privacy Issues; Smart Speakers Rated; Twitter Reveals Source Information

0:00:04.519 --> 0:00:08.760
<v Speaker 1>Facebook under fire for its data sharing practices, the best

0:00:08.960 --> 0:00:12.400
<v Speaker 1>smart speaker, the one plus sixty, gets high marks for

0:00:12.440 --> 0:00:16.880
<v Speaker 1>its cameras, and Twitter now reveals more about you when

0:00:16.920 --> 0:00:20.239
<v Speaker 1>you tweet what's going on. I'm Rich Dimiro. This is

0:00:20.480 --> 0:00:23.480
<v Speaker 1>Rich on Tech, the longer form version of the podcast

0:00:23.480 --> 0:00:25.400
<v Speaker 1>where I talk about all the stuff I think you

0:00:25.440 --> 0:00:29.080
<v Speaker 1>should know about this week in technology. There's a lot

0:00:29.160 --> 0:00:32.360
<v Speaker 1>going on, and this is not everything that happened in tech.

0:00:32.400 --> 0:00:34.279
<v Speaker 1>It's just kind of like the little things that I

0:00:34.320 --> 0:00:37.400
<v Speaker 1>think you should know about. And last week I talked

0:00:37.440 --> 0:00:41.080
<v Speaker 1>about how someone had texted me on Instagram and told

0:00:41.159 --> 0:00:43.840
<v Speaker 1>me they had an idea for the name of this show,

0:00:44.440 --> 0:00:47.880
<v Speaker 1>and I finally found that little message that was sent

0:00:47.960 --> 0:00:51.640
<v Speaker 1>to me by Bob Hardy. Bob Hardy twenty seven on

0:00:51.720 --> 0:00:54.240
<v Speaker 1>Instagram said Hey, Rich, I have an idea for what

0:00:54.320 --> 0:00:57.800
<v Speaker 1>you can call your extended podcast show on Fridays. He says,

0:00:57.880 --> 0:01:01.800
<v Speaker 1>call it Richer on Tech, and I wholeheartedly agree. I

0:01:01.840 --> 0:01:03.800
<v Speaker 1>love the name. Don't know if that's going to be

0:01:03.800 --> 0:01:06.319
<v Speaker 1>the full name, but he says too much Apple stuff

0:01:06.319 --> 0:01:09.440
<v Speaker 1>for my liking, lol, but still love the show. Prefer

0:01:09.520 --> 0:01:14.120
<v Speaker 1>more Android stuff. And Bob, I hear you. The thing

0:01:14.200 --> 0:01:18.720
<v Speaker 1>about Apple versus Android. Here's the deal. So Apple gets

0:01:18.920 --> 0:01:23.080
<v Speaker 1>all of the attention in the press for one big reason.

0:01:23.800 --> 0:01:26.760
<v Speaker 1>There are a lot of people out there that have iPhones,

0:01:27.000 --> 0:01:28.720
<v Speaker 1>and not just that, there's a lot of people out

0:01:28.720 --> 0:01:31.760
<v Speaker 1>there that don't understand how to use the iPhone. There's

0:01:31.880 --> 0:01:34.920
<v Speaker 1>just so many little features on there, and Android's kind

0:01:34.920 --> 0:01:37.839
<v Speaker 1>of the same way. But here's the big difference Android.

0:01:38.000 --> 0:01:41.039
<v Speaker 1>There are so many different manufacturers, there are so many

0:01:41.040 --> 0:01:44.520
<v Speaker 1>different types of phones out there that one news story

0:01:44.920 --> 0:01:48.040
<v Speaker 1>cannot fit all. Even like my tips, I did the

0:01:48.080 --> 0:01:50.480
<v Speaker 1>book one hundred and one Handy Tech Tips for the iPhone.

0:01:50.600 --> 0:01:53.559
<v Speaker 1>Everyone's asking, Rich, where's the Android version? Well, you can't

0:01:53.560 --> 0:01:55.800
<v Speaker 1>do an Android version like that because there is no

0:01:55.920 --> 0:01:59.480
<v Speaker 1>Android operating system that is the same on millions of

0:01:59.480 --> 0:02:03.040
<v Speaker 1>different phones. The closest thing we have is Samsung. With

0:02:03.160 --> 0:02:07.120
<v Speaker 1>that said, Samsung did just recently change up their user interface.

0:02:07.160 --> 0:02:09.119
<v Speaker 1>I've been testing this out on the Note nine. It's

0:02:09.120 --> 0:02:13.000
<v Speaker 1>called one UI and it's actually quite slick. So maybe,

0:02:13.639 --> 0:02:16.880
<v Speaker 1>just maybe I'm not promising anything here. Maybe I will

0:02:16.880 --> 0:02:19.560
<v Speaker 1>do something on Android. But folks, I love Android, don't

0:02:19.560 --> 0:02:23.920
<v Speaker 1>get me wrong, Like I really love Android. So I

0:02:24.000 --> 0:02:27.600
<v Speaker 1>usually carry around two phones one, Android one iPhone, and

0:02:27.639 --> 0:02:30.120
<v Speaker 1>it's just I haven't figured out a good way to

0:02:30.200 --> 0:02:33.680
<v Speaker 1>do things on Android that kind of work across all

0:02:33.680 --> 0:02:36.560
<v Speaker 1>the platforms realistically. Realistically, when you want to do that,

0:02:36.880 --> 0:02:39.720
<v Speaker 1>you almost have to talk about apps on Android and

0:02:39.760 --> 0:02:42.080
<v Speaker 1>what they can do versus kind of the features of

0:02:42.080 --> 0:02:44.280
<v Speaker 1>the operating system. But if I were to do something,

0:02:44.320 --> 0:02:48.919
<v Speaker 1>it'd probably be on the Samsung devices. So let's start

0:02:48.960 --> 0:02:52.600
<v Speaker 1>with Facebook this week, because Facebook, uh man, they just

0:02:52.639 --> 0:02:54.560
<v Speaker 1>this is a company that just wants twenty eighteen to

0:02:54.600 --> 0:02:57.160
<v Speaker 1>go away because they cannot catch a break. They are

0:02:57.240 --> 0:02:59.200
<v Speaker 1>under fire this week because the New York Times did

0:02:59.240 --> 0:03:01.639
<v Speaker 1>an article saying, Hey, Facebook, why are you sharing all

0:03:01.720 --> 0:03:04.440
<v Speaker 1>this personal data that folks post with All these companies

0:03:04.520 --> 0:03:09.320
<v Speaker 1>including Apple, BlackBerry, Yahoo, Netflix, New York Times, Pandora, Spotify,

0:03:09.960 --> 0:03:12.640
<v Speaker 1>and Facebook came out with the blog post and said, look,

0:03:13.240 --> 0:03:15.600
<v Speaker 1>we get it. You have a lot of questions about

0:03:15.600 --> 0:03:18.320
<v Speaker 1>how we're sharing our data, but let us explain. And

0:03:18.400 --> 0:03:20.560
<v Speaker 1>what they explained is that number one, these were older

0:03:20.560 --> 0:03:23.120
<v Speaker 1>features that Facebook was testing out. Some of them were

0:03:23.160 --> 0:03:26.639
<v Speaker 1>integration partners. And the whole big thing about the way

0:03:26.639 --> 0:03:30.400
<v Speaker 1>they were sharing the data is specifically on Apple, Amazon, BlackBerry,

0:03:30.440 --> 0:03:33.440
<v Speaker 1>and Yahoo, is that you would log in on those

0:03:33.480 --> 0:03:36.240
<v Speaker 1>platforms so that you could see your Facebook posts, or

0:03:36.280 --> 0:03:39.400
<v Speaker 1>you can see the various stuff that you did on

0:03:39.480 --> 0:03:41.800
<v Speaker 1>Facebook on a different platform, so you can access that

0:03:41.880 --> 0:03:45.000
<v Speaker 1>through Yahoo or through your BlackBerry. So it wasn't as

0:03:45.080 --> 0:03:48.400
<v Speaker 1>nefarious as New York Times made it out to be.

0:03:48.560 --> 0:03:51.880
<v Speaker 1>And I'm not defending Facebook here. They're trying to appeal

0:03:51.920 --> 0:03:55.119
<v Speaker 1>to a wide amount of people, and basically the way

0:03:55.120 --> 0:03:56.880
<v Speaker 1>you appeal to a wide amount of people is that

0:03:56.960 --> 0:03:59.920
<v Speaker 1>you scare them, right, And so if you really die

0:04:00.200 --> 0:04:03.360
<v Speaker 1>deep into what Facebook was doing, it doesn't sound as

0:04:03.440 --> 0:04:05.600
<v Speaker 1>scary as the New York Times made it out to be.

0:04:06.160 --> 0:04:10.440
<v Speaker 1>So number one, they say that these partnerships wound down

0:04:10.520 --> 0:04:14.320
<v Speaker 1>in twenty fourteen. Let's just be clear about Facebook. We

0:04:14.400 --> 0:04:17.839
<v Speaker 1>are not posting private information on Facebook, and if you are,

0:04:18.400 --> 0:04:21.479
<v Speaker 1>you shouldn't be. Facebook is not a private place. It

0:04:21.560 --> 0:04:24.479
<v Speaker 1>never has been. It should not be construed as a

0:04:24.520 --> 0:04:27.240
<v Speaker 1>private place. And I get it. There was one thing

0:04:27.279 --> 0:04:30.000
<v Speaker 1>that they scared people about, which was private messages, and

0:04:30.040 --> 0:04:33.320
<v Speaker 1>they said that websites like Netflix, New York Times, Pandora,

0:04:33.360 --> 0:04:37.200
<v Speaker 1>and Spotify had access to people's private messages. Well, yeah,

0:04:37.200 --> 0:04:38.880
<v Speaker 1>they were doing a test where you can access your

0:04:38.880 --> 0:04:42.680
<v Speaker 1>private messages through these different platforms, and I get it.

0:04:42.720 --> 0:04:46.080
<v Speaker 1>That does sound scary, but you have to understand anything.

0:04:46.200 --> 0:04:48.720
<v Speaker 1>And let me just say this clear. Anything you do

0:04:48.800 --> 0:04:51.560
<v Speaker 1>on Facebook could be seen by someone else. Anything you

0:04:51.640 --> 0:04:54.800
<v Speaker 1>send through Facebook could be seen. Anything you do there

0:04:54.960 --> 0:04:58.440
<v Speaker 1>will be used to market stuff to you. So just

0:04:58.560 --> 0:05:00.840
<v Speaker 1>understand that and if you do, you'll have a better

0:05:00.920 --> 0:05:03.359
<v Speaker 1>experience on it. Any of these sites that you're getting

0:05:03.360 --> 0:05:06.039
<v Speaker 1>for free, unless you are paying them money, there should

0:05:06.040 --> 0:05:10.080
<v Speaker 1>be absolutely no thought that you're getting something that is private,

0:05:10.400 --> 0:05:13.760
<v Speaker 1>that is personal, that is safe, that is encrypted, that

0:05:13.880 --> 0:05:17.320
<v Speaker 1>is not easily viewable by anyone else. So just keep

0:05:17.320 --> 0:05:20.200
<v Speaker 1>that in mind. And you can still have fun on Facebook.

0:05:20.200 --> 0:05:22.240
<v Speaker 1>You can still post your pictures there, but you just

0:05:22.279 --> 0:05:24.880
<v Speaker 1>have to remember anything that you do there, especially if

0:05:24.880 --> 0:05:28.520
<v Speaker 1>it's free. Look, it's not going to be private. And

0:05:29.040 --> 0:05:32.040
<v Speaker 1>I understand you can have your setting set to where

0:05:32.080 --> 0:05:35.400
<v Speaker 1>certain people can't see stuff, but the reality is there's

0:05:35.480 --> 0:05:39.680
<v Speaker 1>always that potential and always that possibility. And Facebook is

0:05:39.680 --> 0:05:43.359
<v Speaker 1>not here for our health. Facebook is here to market

0:05:43.480 --> 0:05:46.720
<v Speaker 1>stuff to us and to help companies market things to you.

0:05:47.440 --> 0:05:49.839
<v Speaker 1>Just keep that in mind. If you're posting pictures of

0:05:49.880 --> 0:05:52.240
<v Speaker 1>your cat and your family and all the things you're

0:05:52.279 --> 0:05:55.360
<v Speaker 1>doing your vacation. I mean, come on, you have to

0:05:55.440 --> 0:05:58.720
<v Speaker 1>understand they're doing They're not doing you a service. You're

0:05:58.720 --> 0:06:01.160
<v Speaker 1>doing them a service by upload your stuff and then

0:06:01.160 --> 0:06:03.640
<v Speaker 1>they get to find out a lot of data about you.

0:06:03.880 --> 0:06:05.760
<v Speaker 1>So I know a lot of people are deleting Facebook.

0:06:06.279 --> 0:06:08.080
<v Speaker 1>I'm not going to say one hundred percent recommend that

0:06:08.160 --> 0:06:11.800
<v Speaker 1>just yet, because Facebook has really done an amazing job

0:06:11.880 --> 0:06:15.000
<v Speaker 1>at connecting people. I mean, think about it. Think about

0:06:15.120 --> 0:06:17.320
<v Speaker 1>back when you really had a lot of fun on Facebook,

0:06:17.400 --> 0:06:20.120
<v Speaker 1>like connecting with new people. They did a pretty darn

0:06:20.160 --> 0:06:22.599
<v Speaker 1>good job of that. And I understand they're trying to

0:06:22.640 --> 0:06:24.960
<v Speaker 1>find their way in this world where they want to

0:06:25.000 --> 0:06:27.400
<v Speaker 1>make a lot of money and they're making it off

0:06:27.440 --> 0:06:30.360
<v Speaker 1>of your data. That's the way their business was written.

0:06:30.920 --> 0:06:33.920
<v Speaker 1>That's what's happening here, folks. So just remember that, keep

0:06:33.920 --> 0:06:37.200
<v Speaker 1>that in mind, and don't post anything stupid. Right if

0:06:37.200 --> 0:06:38.960
<v Speaker 1>you think your employer can't see it, or if you

0:06:39.000 --> 0:06:41.520
<v Speaker 1>think you know a company can't see it, or it's

0:06:41.560 --> 0:06:45.360
<v Speaker 1>not being used to market to you, then you're totally

0:06:46.440 --> 0:06:49.000
<v Speaker 1>you're just not getting it, because that's what's happening there.

0:06:49.440 --> 0:06:53.159
<v Speaker 1>Speaking of data privacy, this one's great Amazon Alexa user

0:06:53.200 --> 0:06:57.640
<v Speaker 1>receives seventeen hundred audio recordings of a stranger through quote

0:06:57.720 --> 0:07:00.719
<v Speaker 1>human error. So if using one of these smart speakers

0:07:00.760 --> 0:07:03.919
<v Speaker 1>at home, you gotta understand that, yes, they are recording

0:07:04.000 --> 0:07:07.279
<v Speaker 1>every single thing that you say to them, not everything

0:07:07.560 --> 0:07:09.680
<v Speaker 1>all the time. Now, they are listening all the time,

0:07:09.720 --> 0:07:12.960
<v Speaker 1>but theoretically they're only activated when they hear that keyword.

0:07:13.480 --> 0:07:16.440
<v Speaker 1>So what happened was the story out of the Washington

0:07:16.480 --> 0:07:19.800
<v Speaker 1>Post says a person in Germany requested an archive of

0:07:19.840 --> 0:07:23.920
<v Speaker 1>their recordings and they got a link to seventeen hundred

0:07:23.920 --> 0:07:29.440
<v Speaker 1>audio files from someone else's Lexa. So imagine the surprise

0:07:29.480 --> 0:07:31.960
<v Speaker 1>of this person. And of course, if you're a regular person,

0:07:32.040 --> 0:07:34.360
<v Speaker 1>if you're an average person, you're going to start listening

0:07:34.360 --> 0:07:37.040
<v Speaker 1>to some of these recordings on there because you're curious.

0:07:37.560 --> 0:07:40.480
<v Speaker 1>And so the person did, and he listened to another

0:07:40.520 --> 0:07:44.200
<v Speaker 1>man speaking inside their home with a female companion. Apparently

0:07:44.200 --> 0:07:46.560
<v Speaker 1>one of these recordings was also in the shower I heard,

0:07:46.600 --> 0:07:50.240
<v Speaker 1>which was kind of interesting. Amazon said, quote, this is

0:07:50.280 --> 0:07:53.760
<v Speaker 1>an unfortunate case of human error and an isolated incident.

0:07:54.280 --> 0:07:57.760
<v Speaker 1>So let me explain. When you talk to Alexa, I'll

0:07:57.760 --> 0:08:01.400
<v Speaker 1>call her that not to activate yours. There's a recording

0:08:01.480 --> 0:08:05.000
<v Speaker 1>of that, and Amazon uses these recordings to improve what

0:08:05.160 --> 0:08:09.640
<v Speaker 1>she can do. And according to Amazon's help page, we

0:08:09.800 --> 0:08:12.360
<v Speaker 1>keep the recordings associated with your account to improve the

0:08:12.400 --> 0:08:15.080
<v Speaker 1>accuracy of the results provided to you and to improve

0:08:15.080 --> 0:08:17.920
<v Speaker 1>our services. And you do have the option to delete

0:08:18.320 --> 0:08:21.560
<v Speaker 1>these recordings. But guess what, Amazon says, it may degrade

0:08:21.600 --> 0:08:24.680
<v Speaker 1>your experience using the device. Now, I think that's a

0:08:24.680 --> 0:08:26.680
<v Speaker 1>little bit of a scare tactic because I don't think

0:08:26.680 --> 0:08:30.440
<v Speaker 1>it's gonna it will degrade a certain amount, but I

0:08:30.520 --> 0:08:33.560
<v Speaker 1>don't think that your one hundred percent experience of of

0:08:33.679 --> 0:08:35.880
<v Speaker 1>Lexa is based on what you've said to her in

0:08:35.880 --> 0:08:37.760
<v Speaker 1>the past. Some of these things are, but I think

0:08:37.760 --> 0:08:39.440
<v Speaker 1>that they aggregate a lot of this stuff and use

0:08:39.480 --> 0:08:42.079
<v Speaker 1>it to improve the service. I mean, this is bad.

0:08:43.160 --> 0:08:45.840
<v Speaker 1>Nobody wants to think that the recordings that they made

0:08:45.880 --> 0:08:48.800
<v Speaker 1>with their smart speaker is going to be sent to

0:08:48.840 --> 0:08:52.120
<v Speaker 1>someone else. And Amazon says this was a one time error,

0:08:52.320 --> 0:08:55.920
<v Speaker 1>but of course it could easily happen again. And it's

0:08:55.960 --> 0:08:59.640
<v Speaker 1>interesting because you can access your recordings of Lexa on

0:08:59.679 --> 0:09:01.240
<v Speaker 1>the web, So if you want to do that, you

0:09:01.280 --> 0:09:05.360
<v Speaker 1>can go to the Lexa app or the Alexa privacy

0:09:05.400 --> 0:09:09.320
<v Speaker 1>page and go to settings Lexa Account and then Lexa

0:09:09.360 --> 0:09:12.640
<v Speaker 1>Privacy and you can see all of your recordings and

0:09:12.679 --> 0:09:16.320
<v Speaker 1>delete them. Amazon dot Com slash Alexa Privacy is the

0:09:16.320 --> 0:09:19.200
<v Speaker 1>website to go to. I would recommend just taking a look.

0:09:19.280 --> 0:09:20.839
<v Speaker 1>Just go in there. If you use one of these things,

0:09:20.960 --> 0:09:25.240
<v Speaker 1>go in there and just see kind of what recordings

0:09:25.240 --> 0:09:30.360
<v Speaker 1>you have on Google on your computer. You can go

0:09:30.480 --> 0:09:35.320
<v Speaker 1>to Google Account, then you go to Navigation Panel, Data

0:09:35.360 --> 0:09:40.360
<v Speaker 1>and Personalization, then in Activity controls voice and audio activity. Now, personally,

0:09:40.440 --> 0:09:43.040
<v Speaker 1>I think that you should just be able to search

0:09:43.120 --> 0:09:48.080
<v Speaker 1>on Google and say show me my voice recordings, and

0:09:48.120 --> 0:09:50.200
<v Speaker 1>that should bring it onto you bring it right onto

0:09:50.240 --> 0:09:53.240
<v Speaker 1>your page. But it sort of does. It brings you

0:09:53.280 --> 0:09:54.800
<v Speaker 1>to a help page, but it doesn't bring you to

0:09:54.920 --> 0:09:57.319
<v Speaker 1>the page that you need, and it doesn't seem like

0:09:57.320 --> 0:10:00.840
<v Speaker 1>there's a really simple way to get you there. But anyway,

0:10:00.880 --> 0:10:03.640
<v Speaker 1>you can go into your Google recordings and hear what

0:10:03.679 --> 0:10:06.280
<v Speaker 1>you've said to Google as well. And sometimes it's pretty

0:10:06.280 --> 0:10:08.640
<v Speaker 1>eye opening because you hear exactly what you sounded like,

0:10:08.640 --> 0:10:10.679
<v Speaker 1>whether it was in the morning, you know, when you're

0:10:10.720 --> 0:10:12.439
<v Speaker 1>driving a work in your car and you said something

0:10:12.440 --> 0:10:15.600
<v Speaker 1>to Android Auto. But it's really interesting you could hear

0:10:15.600 --> 0:10:18.839
<v Speaker 1>the kids in the background. So, but it's not easy

0:10:18.880 --> 0:10:20.760
<v Speaker 1>to get to. Wow, there's a lot of stuff to

0:10:20.800 --> 0:10:23.719
<v Speaker 1>get to see your voice and audio activity on your

0:10:23.720 --> 0:10:27.880
<v Speaker 1>Android phone. Open your device's settings, and then go to Google.

0:10:27.840 --> 0:10:29.600
<v Speaker 1>Let me do this right now. I'm gonna bring up

0:10:29.600 --> 0:10:32.040
<v Speaker 1>my Android phone. Let's go. So I'll go to settings

0:10:32.840 --> 0:10:36.320
<v Speaker 1>and then we'll go to Google, and then we'll go

0:10:36.440 --> 0:10:40.640
<v Speaker 1>to Google Account. Okay, there it is now at the top.

0:10:40.800 --> 0:10:44.080
<v Speaker 1>Tap data and personalization. There it is. I see that

0:10:44.720 --> 0:10:49.160
<v Speaker 1>under activity and timeline. Type my activity or tap my activity. Okay,

0:10:49.200 --> 0:10:52.280
<v Speaker 1>where's my activity? There it is. Okay, I got it.

0:10:53.120 --> 0:10:56.480
<v Speaker 1>Under the search bar, tap filter by date and product.

0:10:57.040 --> 0:11:00.600
<v Speaker 1>So let's tap filter out. There we go, and now

0:11:01.240 --> 0:11:04.320
<v Speaker 1>uncheck the box next to all products. Check the boxes

0:11:04.320 --> 0:11:08.800
<v Speaker 1>next to assistant and voice and audio assistant and voice

0:11:08.840 --> 0:11:12.839
<v Speaker 1>and audio. Wow. Okay, Now we can press apply and

0:11:12.880 --> 0:11:18.439
<v Speaker 1>there comes some recordings. Okay, oh wow, this is great.

0:11:18.640 --> 0:11:21.480
<v Speaker 1>So here's the stuff it said. Okay, so let's see

0:11:21.679 --> 0:11:26.960
<v Speaker 1>show my agenda. Uh play the butt song yesterday at

0:11:27.000 --> 0:11:29.720
<v Speaker 1>six oh three pm. Okay, clearly my kids have been

0:11:29.840 --> 0:11:32.840
<v Speaker 1>playing with this thing. Wake me up in one hour,

0:11:32.920 --> 0:11:38.840
<v Speaker 1>so let's hear it. Hey, Google. Oh wow, it activated

0:11:38.880 --> 0:11:42.800
<v Speaker 1>my phone. Wake me up in one hour. Oh my gosh,

0:11:43.040 --> 0:11:44.760
<v Speaker 1>wake me up in one hour. So there you have it,

0:11:44.840 --> 0:11:46.200
<v Speaker 1>Oh my gosh. And then you can go through and

0:11:46.200 --> 0:11:49.880
<v Speaker 1>actually delete these things. I said eighteen things to Google yesterday.

0:11:49.920 --> 0:11:52.320
<v Speaker 1>Here's another one that I said, turn off all the

0:11:52.400 --> 0:11:55.199
<v Speaker 1>lights in the office, turn off the Christmas tree. So anyway,

0:11:56.480 --> 0:11:57.840
<v Speaker 1>you'll have a lot of fun. I'll put the links

0:11:57.840 --> 0:11:59.840
<v Speaker 1>in the show notes so you can see exactly where

0:11:59.840 --> 0:12:02.240
<v Speaker 1>that stuff is and listen to some of your recordings.

0:12:02.600 --> 0:12:06.480
<v Speaker 1>Speaking of us smart speakers, Loop Ventures did their annual

0:12:06.559 --> 0:12:10.000
<v Speaker 1>smart Speaker IQ test. Kind of interesting as you might expect.

0:12:10.000 --> 0:12:13.320
<v Speaker 1>Who came out on top. Of course, Google Assistant answered

0:12:13.360 --> 0:12:16.920
<v Speaker 1>eighty eight percent of questions correctly, Siri seventy five percent,

0:12:17.600 --> 0:12:22.000
<v Speaker 1>Lexas seventy three, Kortana sixty three and some big improvements here.

0:12:22.559 --> 0:12:26.280
<v Speaker 1>So Google Assistant last year got eighty one percent. Siri

0:12:26.559 --> 0:12:30.120
<v Speaker 1>huge improvement fifty two percent last year versus seventy five

0:12:30.160 --> 0:12:33.079
<v Speaker 1>this year, so she's gotten a lot better. Lexas sixty

0:12:33.080 --> 0:12:35.840
<v Speaker 1>four percent versus seventy three percent this year, and Kortana

0:12:35.880 --> 0:12:39.679
<v Speaker 1>fifty six percent versus sixty three. So they asked these

0:12:39.720 --> 0:12:43.440
<v Speaker 1>things eight hundred questions, including local questions like where is

0:12:43.480 --> 0:12:46.720
<v Speaker 1>the nearest coffee shop, commerce questions, can you order me

0:12:46.760 --> 0:12:50.120
<v Speaker 1>more paper towels? Navigation, how do I get to uptown

0:12:50.200 --> 0:12:53.600
<v Speaker 1>on the bus? Information, who do the Twins play tonight?

0:12:54.000 --> 0:12:55.960
<v Speaker 1>And then a command remind me to call Steve at

0:12:56.000 --> 0:13:00.280
<v Speaker 1>two pm today. So also important to note that they

0:13:00.320 --> 0:13:03.959
<v Speaker 1>asked the questions on these smart speakers, not on the phone.

0:13:04.040 --> 0:13:06.400
<v Speaker 1>They are slightly different when you ask these questions on

0:13:06.440 --> 0:13:11.240
<v Speaker 1>a phone versus the speaker. So the biggest thing that

0:13:11.280 --> 0:13:14.200
<v Speaker 1>tripped these things up was something that involved a proper noun,

0:13:14.320 --> 0:13:16.600
<v Speaker 1>often the name of a local town or a restaurant,

0:13:16.840 --> 0:13:19.959
<v Speaker 1>although I found that Google is really good at figuring

0:13:19.960 --> 0:13:22.880
<v Speaker 1>out these names, especially when you say proper names of restaurants.

0:13:22.960 --> 0:13:25.840
<v Speaker 1>So again, they did get eighty eight percent right, so

0:13:25.880 --> 0:13:29.520
<v Speaker 1>that's pretty darn good. Google Home has the edge in

0:13:29.600 --> 0:13:32.320
<v Speaker 1>four out of five categories, but fell short of Siri

0:13:32.360 --> 0:13:35.600
<v Speaker 1>in the command category. And it's really interesting that they

0:13:35.640 --> 0:13:38.880
<v Speaker 1>said that, because it's funny. As bad as some people

0:13:38.920 --> 0:13:42.480
<v Speaker 1>say Siri is, it's actually really good when you're talking

0:13:42.480 --> 0:13:47.120
<v Speaker 1>about doing things like email and messaging, like especially text messages,

0:13:47.440 --> 0:13:50.040
<v Speaker 1>you can ask her to read your unread text messages

0:13:50.120 --> 0:13:53.680
<v Speaker 1>or reply to someone, and she's really good at that stuff.

0:13:54.040 --> 0:13:56.880
<v Speaker 1>Google not so much. And the challenge with Google is

0:13:56.920 --> 0:14:00.319
<v Speaker 1>that it integrates with a lot of different apps on

0:14:00.360 --> 0:14:03.120
<v Speaker 1>your phone. And that's the big problem is that Siri

0:14:03.240 --> 0:14:06.760
<v Speaker 1>only really integrates with the iPhone native apps. She's getting

0:14:06.760 --> 0:14:08.880
<v Speaker 1>a little bit better with some of the extensions that

0:14:09.080 --> 0:14:12.120
<v Speaker 1>they've added to Siri, but for the most part, people

0:14:12.160 --> 0:14:16.920
<v Speaker 1>are using Siri to interface with native apps on the iPhone.

0:14:17.240 --> 0:14:20.640
<v Speaker 1>The largest disparity, according to loop Ventures, exists in the

0:14:20.720 --> 0:14:23.960
<v Speaker 1>commerce section. You would think Alexa would dominate that, but

0:14:24.000 --> 0:14:27.080
<v Speaker 1>Google Assistant actually did really well. Knows a lot of

0:14:27.080 --> 0:14:30.520
<v Speaker 1>product information, where to buy certain stuff. Google Express just

0:14:30.600 --> 0:14:34.120
<v Speaker 1>as capable as Amazon in terms of purchasing stuff or

0:14:34.160 --> 0:14:39.800
<v Speaker 1>restocking common goods you've purchased before. Alexa's surprising commerce score

0:14:39.880 --> 0:14:43.160
<v Speaker 1>is explained by an example in our test so question

0:14:43.320 --> 0:14:46.200
<v Speaker 1>how much would a manicure cost? Alexa said, the top

0:14:46.240 --> 0:14:50.240
<v Speaker 1>search result for manicure is this pedicure kit. It's sixty

0:14:50.320 --> 0:14:52.000
<v Speaker 1>dollars on Amazon, which you like to buy it? That

0:14:52.040 --> 0:14:55.760
<v Speaker 1>doesn't really help you at all. Google Assistant said, on average,

0:14:55.800 --> 0:14:59.400
<v Speaker 1>a basic manicure will cost you twenty dollars. However, special

0:14:59.520 --> 0:15:03.360
<v Speaker 1>manicure like Acrylic Jail, Schillac, Gel Shillac, and no Chip

0:15:03.440 --> 0:15:05.840
<v Speaker 1>range from twenty to fifty depending on the salon. So

0:15:06.040 --> 0:15:08.960
<v Speaker 1>as you can see, Google is much better at parsing

0:15:09.000 --> 0:15:11.680
<v Speaker 1>information from the web and delivering that to you, and

0:15:11.720 --> 0:15:14.600
<v Speaker 1>that's definitely my experience one of the reasons I really

0:15:14.640 --> 0:15:17.280
<v Speaker 1>like Google Assistant. In fact, I like all these things

0:15:17.280 --> 0:15:22.080
<v Speaker 1>for various reasons. Alexa or Alexa is really good at

0:15:22.400 --> 0:15:26.200
<v Speaker 1>knowing your shopping history on Google. Alexa is really good

0:15:26.240 --> 0:15:28.760
<v Speaker 1>at knowing your shopping history and the stuff you've ordered

0:15:28.760 --> 0:15:31.760
<v Speaker 1>on Amazon, so she's really good at answering questions about

0:15:31.760 --> 0:15:34.800
<v Speaker 1>that and re ordering similar items. Where I find Google

0:15:34.800 --> 0:15:37.320
<v Speaker 1>Assistant to just be really solid in a wide variety

0:15:37.360 --> 0:15:40.160
<v Speaker 1>of categories. But when it comes to controlling my phone,

0:15:41.160 --> 0:15:44.640
<v Speaker 1>absolutely I think that Siri does a much better job.

0:15:44.680 --> 0:15:47.280
<v Speaker 1>But again we're talking about smart speakers here, not just

0:15:47.440 --> 0:15:50.920
<v Speaker 1>the smartphones. One Plus sixty a big Android phone that

0:15:51.000 --> 0:15:54.880
<v Speaker 1>launched this year from the Chinese startup one plus, So

0:15:55.480 --> 0:16:00.920
<v Speaker 1>getting the latest camera reviews from dxomar, it actually did

0:16:00.960 --> 0:16:04.240
<v Speaker 1>really well. It got good performer So the one plus

0:16:04.280 --> 0:16:07.440
<v Speaker 1>six T is a very solid Android device if you

0:16:07.480 --> 0:16:10.120
<v Speaker 1>want sort of the best bang for your buck when

0:16:10.120 --> 0:16:12.480
<v Speaker 1>it comes to Android devices. You're talking a phone that's

0:16:12.480 --> 0:16:15.440
<v Speaker 1>about five hundred and fifty dollars and it checks off

0:16:15.480 --> 0:16:18.480
<v Speaker 1>all the marks. It's got great hardware, it's got excellent software,

0:16:18.760 --> 0:16:21.600
<v Speaker 1>it's got a really nice camera. And the surprising part

0:16:21.600 --> 0:16:25.120
<v Speaker 1>about this review is that the one plus sixt has

0:16:25.200 --> 0:16:28.320
<v Speaker 1>the same camera as the one plus six. It's got

0:16:28.320 --> 0:16:32.240
<v Speaker 1>a sixteen megapixel main camera, twenty megapixel secondary module for

0:16:32.360 --> 0:16:37.280
<v Speaker 1>digital zooming, and according to DxO mark it says that

0:16:37.320 --> 0:16:40.440
<v Speaker 1>their tests show that firmware changes have the six T

0:16:41.040 --> 0:16:44.360
<v Speaker 1>doing a little bit better than its predecessor, the six.

0:16:44.960 --> 0:16:49.360
<v Speaker 1>So how does this thing score? Overall? Ninety eight points,

0:16:49.400 --> 0:16:52.240
<v Speaker 1>which ties it up with the Google Pixel two, which

0:16:52.680 --> 0:16:55.680
<v Speaker 1>is a very good camera. It holds tenth place in

0:16:55.760 --> 0:17:00.520
<v Speaker 1>Dxo's mobile rankings. So when you think about the ten

0:17:00.760 --> 0:17:03.560
<v Speaker 1>smartphone cameras out there, let's just take a look at

0:17:03.560 --> 0:17:06.760
<v Speaker 1>the list right now. Number one Huawei P twenty plus

0:17:06.760 --> 0:17:10.600
<v Speaker 1>are Peak twenty pro, which not really for America, but

0:17:11.560 --> 0:17:16.160
<v Speaker 1>it's available in the international version. Number two Apple iPhone

0:17:16.160 --> 0:17:20.920
<v Speaker 1>ten s Max, Number three HTCU twelve plus, Number four

0:17:21.119 --> 0:17:27.040
<v Speaker 1>Samsung Galaxy Note nine, Number five Jaumi me Mix three.

0:17:27.240 --> 0:17:29.720
<v Speaker 1>Then you have the iPhone ten are Google Pixel three

0:17:29.880 --> 0:17:31.840
<v Speaker 1>and the Samsung Galaxy S nine, so a lot of

0:17:31.880 --> 0:17:35.480
<v Speaker 1>huaweis on there. A lot of Chinese manufacturers also the

0:17:35.640 --> 0:17:39.160
<v Speaker 1>HTC phones that are not very common here in America.

0:17:39.840 --> 0:17:44.080
<v Speaker 1>So for the one plus sixty to get down there

0:17:44.160 --> 0:17:46.440
<v Speaker 1>under the one plus, the Google Pixel two or tying,

0:17:46.480 --> 0:17:48.960
<v Speaker 1>that is pretty good. One plus six t I think

0:17:48.960 --> 0:17:52.760
<v Speaker 1>people will be very happy with. Let's see. The reviewers

0:17:52.840 --> 0:17:56.440
<v Speaker 1>liked its wide dynamic range, pleasant colors, good detailed preservation,

0:17:57.359 --> 0:18:01.360
<v Speaker 1>and the autofocus was reliable and quick. On the downside,

0:18:01.560 --> 0:18:05.600
<v Speaker 1>zoom shots show less detail than competitors, and many HDR

0:18:05.680 --> 0:18:09.439
<v Speaker 1>shots show artifacts such as ringing, ghosting, or halos. So

0:18:09.560 --> 0:18:12.760
<v Speaker 1>kudos to one plus for launching the sixte. They also

0:18:12.840 --> 0:18:16.120
<v Speaker 1>have the McLaren addition of the one plus sixty, which

0:18:16.160 --> 0:18:21.000
<v Speaker 1>has got ten gigabytes of RAM, which is just insane.

0:18:21.080 --> 0:18:23.960
<v Speaker 1>To give you a little basis of that, the iPhone

0:18:24.000 --> 0:18:26.879
<v Speaker 1>has four gigabytes of RAM on board, and we're not

0:18:26.920 --> 0:18:29.840
<v Speaker 1>talking memory, that's you know, how much storage is on board,

0:18:30.200 --> 0:18:32.640
<v Speaker 1>but it does have a lot of that as well.

0:18:33.080 --> 0:18:35.879
<v Speaker 1>But it does have a ton of RAM, which you know,

0:18:35.920 --> 0:18:40.480
<v Speaker 1>speeds things up. Speaking of Apple, according to a new report,

0:18:40.560 --> 0:18:43.080
<v Speaker 1>they're going to launch an iPad Mini five and an

0:18:43.200 --> 0:18:46.320
<v Speaker 1>entry level ten inch iPad next year. I already thought

0:18:46.320 --> 0:18:48.960
<v Speaker 1>they had an entry level iPad, but that's the one

0:18:48.960 --> 0:18:51.200
<v Speaker 1>for three thirty nine. Maybe they're making or three twenty nine.

0:18:51.200 --> 0:18:53.800
<v Speaker 1>Maybe they're making a cheaper one. But the iPad Mini

0:18:53.840 --> 0:18:56.119
<v Speaker 1>five is very interesting to me because I bought this

0:18:56.200 --> 0:18:59.639
<v Speaker 1>for my kids, and I cannot believe they have an

0:18:59.680 --> 0:19:03.520
<v Speaker 1>update since twenty fifteen. I bought the iPad Mini for

0:19:03.600 --> 0:19:06.040
<v Speaker 1>my kids right when it came out, so I guess

0:19:06.040 --> 0:19:08.720
<v Speaker 1>that was in September, three years ago. I can't believe that.

0:19:10.480 --> 0:19:14.960
<v Speaker 1>But they're saying. Mnchi Quo is a reliable Apple analyst.

0:19:15.320 --> 0:19:17.080
<v Speaker 1>He says they're working on a new version of the

0:19:17.080 --> 0:19:19.880
<v Speaker 1>iPad Mini, which would be great because it's a perfect

0:19:19.960 --> 0:19:22.840
<v Speaker 1>iPad for kids. My kids have had theirs in their

0:19:22.880 --> 0:19:26.440
<v Speaker 1>outer boxes for three years now and they've been great.

0:19:26.520 --> 0:19:29.320
<v Speaker 1>They haven't really slowed down too much. They work great

0:19:29.359 --> 0:19:31.919
<v Speaker 1>for the kids. There's you know, they just they're just

0:19:31.960 --> 0:19:34.720
<v Speaker 1>a solid performer and you get all the apps that

0:19:34.760 --> 0:19:37.680
<v Speaker 1>you need on that device. So I will happily upgrade

0:19:37.720 --> 0:19:40.560
<v Speaker 1>my kids and sell their old ones on eBay or

0:19:40.560 --> 0:19:43.119
<v Speaker 1>maybe give them to a family member when I upgrade.

0:19:43.200 --> 0:19:44.440
<v Speaker 1>But a lot of people have been waiting for a

0:19:44.480 --> 0:19:47.480
<v Speaker 1>fifth generation iPad Mini. They say they're going to launch

0:19:47.560 --> 0:19:50.200
<v Speaker 1>it in the first half of twenty nineteen. This is

0:19:50.240 --> 0:19:54.880
<v Speaker 1>according to a Apple supply chain I guess a report

0:19:54.960 --> 0:19:59.680
<v Speaker 1>by the China Times. So I'm all for it. I'm

0:19:59.680 --> 0:20:01.800
<v Speaker 1>ready to upgrade, and I think the iPad Mini is

0:20:01.800 --> 0:20:05.120
<v Speaker 1>a great one. It's a nice size for kids especially,

0:20:05.119 --> 0:20:07.000
<v Speaker 1>And I get a lot of questions about people saying

0:20:07.280 --> 0:20:09.600
<v Speaker 1>should I get the iPad Mini. Well, they don't really

0:20:09.640 --> 0:20:11.000
<v Speaker 1>ask about that. They just say should I get the

0:20:11.040 --> 0:20:15.280
<v Speaker 1>iPad or should I get some other tablet? And you know,

0:20:15.359 --> 0:20:19.359
<v Speaker 1>I always recommend the iPad because the apps are just

0:20:19.440 --> 0:20:21.239
<v Speaker 1>so much better than what you get on Android. When

0:20:21.280 --> 0:20:24.000
<v Speaker 1>it comes to tablets and especially kids apps, this is

0:20:24.040 --> 0:20:26.520
<v Speaker 1>where the developers really put a lot of their efforts.

0:20:26.760 --> 0:20:28.600
<v Speaker 1>And I get it. If your kid's just watching Netflix,

0:20:28.640 --> 0:20:30.840
<v Speaker 1>sure the Amazon Fire tablet is going to be just

0:20:30.880 --> 0:20:34.160
<v Speaker 1>fine for them. But when it comes to these educational apps,

0:20:34.480 --> 0:20:37.080
<v Speaker 1>some of these things are really only available on the iPad,

0:20:37.480 --> 0:20:40.399
<v Speaker 1>and I just find that the quality and ease of

0:20:40.440 --> 0:20:43.520
<v Speaker 1>the iPad is just so much better and again, look

0:20:43.560 --> 0:20:46.439
<v Speaker 1>at mine has lasted three years. It's in an outter box.

0:20:46.520 --> 0:20:48.520
<v Speaker 1>I definitely got my money's worth out of this thing.

0:20:48.600 --> 0:20:52.600
<v Speaker 1>It has saved us many family dinners, many meltdowns, many

0:20:52.680 --> 0:20:55.520
<v Speaker 1>rides in the car. And don't get don't get on

0:20:55.520 --> 0:20:59.800
<v Speaker 1>me about screen time, but I really like the iPad.

0:20:59.880 --> 0:21:02.240
<v Speaker 1>I just think it's a very solid device for the kids,

0:21:02.520 --> 0:21:04.840
<v Speaker 1>and you don't want them just watching nonsense on Netflix

0:21:04.880 --> 0:21:07.040
<v Speaker 1>all day. Like some of these educational apps are pretty

0:21:07.119 --> 0:21:10.920
<v Speaker 1>darn good on the iPads. New feature on Twitter. First

0:21:10.920 --> 0:21:13.800
<v Speaker 1>noticed it on Android. Now it's coming to iOS. But

0:21:13.840 --> 0:21:17.199
<v Speaker 1>when you tweet, it's now going to show folks what

0:21:17.760 --> 0:21:21.200
<v Speaker 1>and how you're tweeting from. So right by the time

0:21:21.320 --> 0:21:25.240
<v Speaker 1>and date stamp, there is now a new little piece

0:21:25.280 --> 0:21:29.240
<v Speaker 1>of information that says the app or the platform that

0:21:29.280 --> 0:21:32.080
<v Speaker 1>you are tweeting from. So if you're using Twitter for Android,

0:21:32.080 --> 0:21:34.560
<v Speaker 1>it will say Twitter for Android. If you're using Twitter

0:21:34.600 --> 0:21:37.879
<v Speaker 1>for iPhone, it'll say Twitter for iPhone. If you're using

0:21:38.119 --> 0:21:42.120
<v Speaker 1>Twitter Web app or tweetbot or any other way of tweeting,

0:21:42.400 --> 0:21:45.920
<v Speaker 1>folks will actually now get to see how you are tweeting.

0:21:46.359 --> 0:21:49.359
<v Speaker 1>So if you're trying to hide how you're tweeting the

0:21:49.400 --> 0:21:51.960
<v Speaker 1>secrets out, So if you go into any tweet, just

0:21:52.080 --> 0:21:54.040
<v Speaker 1>tap it to see kind of like a bigger version

0:21:54.040 --> 0:21:57.760
<v Speaker 1>of it. You can see right in the timeline or

0:21:57.840 --> 0:22:00.560
<v Speaker 1>right on that thing how people are tweeting, so it'll

0:22:00.600 --> 0:22:03.800
<v Speaker 1>say you know the time, the date, and then for instance,

0:22:03.840 --> 0:22:06.280
<v Speaker 1>Twitter for iPhone and I can just go down the

0:22:06.320 --> 0:22:10.240
<v Speaker 1>list here Twitter for iPad, This person just tweeted Twitter

0:22:10.320 --> 0:22:13.560
<v Speaker 1>for iPhone. Long story short, You can now see more

0:22:13.560 --> 0:22:16.160
<v Speaker 1>information about how someone's tweeting and why is this coming

0:22:16.200 --> 0:22:19.080
<v Speaker 1>handy Well, it's kind of interesting just to see if

0:22:19.119 --> 0:22:20.919
<v Speaker 1>you're like a celebrity, you're trying to figure out how

0:22:20.920 --> 0:22:24.520
<v Speaker 1>they're tweeting what they're tweeting from how you know, often

0:22:24.560 --> 0:22:26.560
<v Speaker 1>people will schedule their tweets. You can out tell if

0:22:26.560 --> 0:22:28.919
<v Speaker 1>they're scheduling their tweets because it will come from some

0:22:28.960 --> 0:22:32.960
<v Speaker 1>sort of Twitter platform, not necessarily the app. So that's

0:22:32.960 --> 0:22:35.440
<v Speaker 1>one way. Also a lot of these tech companies get

0:22:35.440 --> 0:22:39.200
<v Speaker 1>burned because they will tweet about let's say the new

0:22:39.240 --> 0:22:42.560
<v Speaker 1>Samsung phone and guess what the celebrities tweet that's saying

0:22:42.600 --> 0:22:45.040
<v Speaker 1>how great this phone is comes from an iPhone. That's

0:22:45.119 --> 0:22:47.920
<v Speaker 1>kind of weird, right, So it used to take something

0:22:47.960 --> 0:22:51.040
<v Speaker 1>like tweet Deck to track that information down. Now you

0:22:51.040 --> 0:22:53.600
<v Speaker 1>can just look right in the Twitter app on your

0:22:53.640 --> 0:22:56.600
<v Speaker 1>iPhone or Android and see exactly how folks are tweeting,

0:22:56.880 --> 0:22:58.960
<v Speaker 1>and sure, if you look at mine, you're not gonna

0:22:58.960 --> 0:23:00.679
<v Speaker 1>catch me in anything. I do schedule a lot of

0:23:00.680 --> 0:23:05.880
<v Speaker 1>my tweets, and I also will I will also tweet

0:23:05.960 --> 0:23:09.000
<v Speaker 1>from both Android and iOS depending on how I'm feeling

0:23:09.040 --> 0:23:12.160
<v Speaker 1>that day. So sometimes I'm on Android, sometimes I'm on iOS,

0:23:12.240 --> 0:23:15.720
<v Speaker 1>sometimes I'm on the web. Sometimes I'm using Buffer, which

0:23:15.760 --> 0:23:18.320
<v Speaker 1>is a great social media app that helps you schedule

0:23:18.680 --> 0:23:22.200
<v Speaker 1>some of your tweets. So what happens is I don't

0:23:22.240 --> 0:23:25.800
<v Speaker 1>like to slam people with tweets all day long, you know,

0:23:25.840 --> 0:23:27.480
<v Speaker 1>Like I don't like to have like twenty five tweets

0:23:27.520 --> 0:23:30.360
<v Speaker 1>go out at once, because you know, they're kind of ephemeral, right,

0:23:30.400 --> 0:23:32.919
<v Speaker 1>they just kind of disappear after a couple of minutes.

0:23:33.160 --> 0:23:34.800
<v Speaker 1>So I like people to have them kind of spaced

0:23:34.800 --> 0:23:36.800
<v Speaker 1>out through the day. So if it's not something that

0:23:36.920 --> 0:23:40.360
<v Speaker 1>necessarily has to go out at that exact moment, I'll

0:23:40.400 --> 0:23:41.760
<v Speaker 1>just kind of space it out a little bit and

0:23:41.800 --> 0:23:43.399
<v Speaker 1>use Buffer. So when you look at my tweets, if

0:23:43.440 --> 0:23:45.840
<v Speaker 1>you see something that comes from buffer, chances are i'd

0:23:45.880 --> 0:23:48.919
<v Speaker 1>schedule that out from a while back. Sometimes. Also, I

0:23:48.960 --> 0:23:51.119
<v Speaker 1>do a lot of my tweeting very early in the morning,

0:23:51.200 --> 0:23:54.440
<v Speaker 1>like four to nine AM, so rather than just send

0:23:54.480 --> 0:23:56.720
<v Speaker 1>everything out during those hours, I'll kind of space it

0:23:56.760 --> 0:23:59.359
<v Speaker 1>out throughout the day. Everyone has a different theory on

0:23:59.400 --> 0:24:01.760
<v Speaker 1>this stuff, but that's kind of how I do it.

0:24:02.480 --> 0:24:05.320
<v Speaker 1>And let's talk about this NASA engineer. We talked about

0:24:05.320 --> 0:24:07.280
<v Speaker 1>this on TV. I don't know if you saw maybe

0:24:07.280 --> 0:24:09.840
<v Speaker 1>the YouTube video, but it was a glitter bomb. It

0:24:09.920 --> 0:24:15.200
<v Speaker 1>was basically a viral video about porch pirates and this

0:24:15.520 --> 0:24:20.080
<v Speaker 1>NASA engineer, Mark Rober He made a YouTube video with

0:24:20.119 --> 0:24:22.600
<v Speaker 1>a glitter bomb it. It was a package that he

0:24:22.640 --> 0:24:26.280
<v Speaker 1>outfitted with all these special electronics. When you take the package,

0:24:26.320 --> 0:24:29.600
<v Speaker 1>when you steal it, it follow They follow you home

0:24:29.760 --> 0:24:32.479
<v Speaker 1>with GPS, they can see where you were, and when

0:24:32.520 --> 0:24:34.679
<v Speaker 1>you open the package, it explodes with all this glitter.

0:24:35.000 --> 0:24:37.240
<v Speaker 1>So I had this debate with my producer. I was like,

0:24:37.240 --> 0:24:39.520
<v Speaker 1>there's no way that's real. There's no way he actually

0:24:39.560 --> 0:24:42.399
<v Speaker 1>got people to steal these packages in a certain timeframe

0:24:42.480 --> 0:24:44.480
<v Speaker 1>and then recorded them and then was able to edit

0:24:44.480 --> 0:24:47.320
<v Speaker 1>it all on a nice YouTube timeline and get it

0:24:47.400 --> 0:24:50.159
<v Speaker 1>up to YouTube and rack up millions and millions of views.

0:24:50.480 --> 0:24:52.159
<v Speaker 1>In fact, when I showed the video on TV, it

0:24:52.200 --> 0:24:55.600
<v Speaker 1>had six million views. Business Insider is saying it racked

0:24:55.640 --> 0:24:59.120
<v Speaker 1>up forty million views in about three days. And now

0:24:59.280 --> 0:25:02.000
<v Speaker 1>the NASA guy, Mark Rober, who I've interviewed before, by

0:25:02.040 --> 0:25:05.320
<v Speaker 1>the way, is coming out and saying, Okay, it was fake.

0:25:05.960 --> 0:25:10.240
<v Speaker 1>So the package wasn't fake, but the payoff was. Was

0:25:10.280 --> 0:25:12.840
<v Speaker 1>there anyone who actually stole this package and they tracked

0:25:12.880 --> 0:25:15.240
<v Speaker 1>back to their house? Don't I don't know. It doesn't

0:25:15.280 --> 0:25:17.640
<v Speaker 1>seem like it. Two of the so called thieves were

0:25:17.680 --> 0:25:20.840
<v Speaker 1>actually in on the prank. They were roped in by

0:25:20.840 --> 0:25:22.560
<v Speaker 1>a friend of a friend who offered to place the

0:25:22.600 --> 0:25:26.000
<v Speaker 1>package on their porch, and Rober said, I'm really sorry

0:25:26.040 --> 0:25:28.159
<v Speaker 1>about this. I'm responsible for the content that goes on

0:25:28.200 --> 0:25:30.760
<v Speaker 1>my channel. I should have done more. I can vouch

0:25:30.800 --> 0:25:33.600
<v Speaker 1>the reactions were genuine when the package was taken from

0:25:33.680 --> 0:25:37.199
<v Speaker 1>my house. I know my credibility is sort of shot.

0:25:37.480 --> 0:25:40.800
<v Speaker 1>So Mark Rober is He's done a lot of great

0:25:40.880 --> 0:25:43.600
<v Speaker 1>videos for YouTube. They're often a mix of sort of

0:25:43.680 --> 0:25:46.919
<v Speaker 1>engineering and surprise, and he does a great job not

0:25:47.040 --> 0:25:50.480
<v Speaker 1>discounting the fact, but YouTube is entertainment and a lot

0:25:50.480 --> 0:25:52.040
<v Speaker 1>of the stuff that you see on there you gotta

0:25:52.119 --> 0:25:54.080
<v Speaker 1>kind of take with a grain of salt, because how

0:25:54.160 --> 0:25:55.920
<v Speaker 1>is he able to get a porch pirate to steal

0:25:55.960 --> 0:25:59.320
<v Speaker 1>these packages and then also sign off and say, yeah,

0:25:59.359 --> 0:26:02.119
<v Speaker 1>I'm willing to let this video be on YouTube. No,

0:26:02.400 --> 0:26:07.400
<v Speaker 1>definitely definitely made me think twice. So clearly it was fake,

0:26:07.720 --> 0:26:09.320
<v Speaker 1>but it doesn't take away from the fact that he

0:26:09.359 --> 0:26:12.879
<v Speaker 1>still did something really funny, which were these packages that

0:26:12.920 --> 0:26:17.000
<v Speaker 1>would explode into glitter and also a let's just say

0:26:17.000 --> 0:26:19.639
<v Speaker 1>it smelled like someone was passing gas when this thing

0:26:19.680 --> 0:26:22.199
<v Speaker 1>would open up in your house. So great idea, but

0:26:23.240 --> 0:26:25.760
<v Speaker 1>not necessarily real. And by the way I said, I

0:26:25.800 --> 0:26:28.520
<v Speaker 1>interviewed Mark Roeber back in the day. The first time

0:26:28.560 --> 0:26:32.040
<v Speaker 1>I met him, he was doing a he came to prominence.

0:26:32.080 --> 0:26:35.800
<v Speaker 1>He was a JPL NASA guy, and he came to

0:26:35.920 --> 0:26:41.640
<v Speaker 1>prominence doing these shirts for Halloween. They were like costumes

0:26:41.800 --> 0:26:43.440
<v Speaker 1>and they would have a little cutout right in the

0:26:43.440 --> 0:26:46.280
<v Speaker 1>middle of the shirt that you would put your iPhone

0:26:46.280 --> 0:26:47.439
<v Speaker 1>and back in that day, I think it was an

0:26:47.480 --> 0:26:50.440
<v Speaker 1>iPod actually iPod touch. You would put that in there

0:26:50.480 --> 0:26:52.840
<v Speaker 1>and it would have like some sort of video on there.

0:26:52.880 --> 0:26:54.720
<v Speaker 1>So if it was like a scary shirt, it had

0:26:54.760 --> 0:26:56.879
<v Speaker 1>like a big mouth that was like all bloody and

0:26:56.920 --> 0:26:59.639
<v Speaker 1>stuff and like screaming, so that would be like that

0:26:59.640 --> 0:27:01.879
<v Speaker 1>would ate the mouth on the shirt. And then it

0:27:01.920 --> 0:27:03.919
<v Speaker 1>had like a fireplace, so it had the shirt had

0:27:03.920 --> 0:27:05.600
<v Speaker 1>a big fireplace on it. And then where you put

0:27:05.600 --> 0:27:08.520
<v Speaker 1>your iPod in, it was like a crackling fire video

0:27:08.640 --> 0:27:12.280
<v Speaker 1>on your iPod video right, iPod I guess video what

0:27:12.320 --> 0:27:15.480
<v Speaker 1>was it called? iPod touch had the video. So you

0:27:15.520 --> 0:27:17.240
<v Speaker 1>got to give him. You got to give him credit.

0:27:17.280 --> 0:27:18.879
<v Speaker 1>The guy has done a lot of cool stuff in

0:27:18.920 --> 0:27:23.000
<v Speaker 1>his career, and he's a smart guy. Clearly. I think

0:27:23.080 --> 0:27:25.000
<v Speaker 1>this was a small stumble for him. He was very

0:27:25.000 --> 0:27:27.320
<v Speaker 1>excited to get this video out there and it was

0:27:27.359 --> 0:27:29.359
<v Speaker 1>a cool concept. But you got to tell people when

0:27:29.400 --> 0:27:30.960
<v Speaker 1>these things are fake. I don't think it would have

0:27:31.000 --> 0:27:32.480
<v Speaker 1>taken away from the video. I think he could have

0:27:32.480 --> 0:27:34.640
<v Speaker 1>put that in the comments or the description. It would

0:27:34.680 --> 0:27:37.520
<v Speaker 1>have been just fine. Let's talk about my book one

0:27:37.840 --> 0:27:39.960
<v Speaker 1>and one handy tech tips for the iPhone. I gotta say,

0:27:40.000 --> 0:27:42.720
<v Speaker 1>I cannot believe the response to this. It is now

0:27:42.760 --> 0:27:46.080
<v Speaker 1>currently on at least oh my gosh, almost a two

0:27:46.160 --> 0:27:49.240
<v Speaker 1>week wait on Amazon, which is really unfortunate because a

0:27:49.280 --> 0:27:51.359
<v Speaker 1>lot of people were ordering it for the holidays. If

0:27:51.400 --> 0:27:53.560
<v Speaker 1>you got it in early, hopefully you got it in

0:27:53.560 --> 0:27:55.760
<v Speaker 1>time for the holidays. But if you're trying to order now,

0:27:56.080 --> 0:27:57.639
<v Speaker 1>it is on like a two week delay. And the

0:27:57.680 --> 0:28:00.720
<v Speaker 1>reason for that is that I self published through Amazon,

0:28:01.240 --> 0:28:03.840
<v Speaker 1>and they don't know what the reaction is going to

0:28:03.880 --> 0:28:06.600
<v Speaker 1>be to any book that someone self publishes, so they

0:28:06.640 --> 0:28:10.080
<v Speaker 1>probably when I've first launched, you know, maybe print a

0:28:10.119 --> 0:28:11.840
<v Speaker 1>couple of them, a couple dozens so that they can

0:28:11.920 --> 0:28:14.080
<v Speaker 1>keep up with orders. But then as my orders are

0:28:14.119 --> 0:28:16.680
<v Speaker 1>coming in, which we're in the thousands every day, they

0:28:16.680 --> 0:28:19.040
<v Speaker 1>all of a sudden realize, oh, oh no, we got

0:28:19.080 --> 0:28:20.720
<v Speaker 1>to print a lot more of these things. And it

0:28:20.760 --> 0:28:22.440
<v Speaker 1>takes a long time to print a book. I think

0:28:22.920 --> 0:28:24.679
<v Speaker 1>I know the ones that I ordered. I ordered some

0:28:24.840 --> 0:28:28.639
<v Speaker 1>press copies for myself, they call them author copies, and

0:28:28.680 --> 0:28:30.879
<v Speaker 1>I can order those in bulk, and it was taking

0:28:30.960 --> 0:28:33.560
<v Speaker 1>like two to three weeks to get those things delivered

0:28:33.560 --> 0:28:36.800
<v Speaker 1>to me. So it takes Amazon a while. And I

0:28:36.840 --> 0:28:38.400
<v Speaker 1>don't think they care about me as much because I

0:28:38.400 --> 0:28:40.440
<v Speaker 1>get a little discount on mine when I order them,

0:28:40.680 --> 0:28:44.320
<v Speaker 1>versus the average person. That's ordering just one copy. Thank

0:28:44.360 --> 0:28:46.040
<v Speaker 1>you to everyone who has purchased one of these. The

0:28:46.120 --> 0:28:50.080
<v Speaker 1>reviews are starting to come in, and I would say

0:28:50.120 --> 0:28:52.800
<v Speaker 1>a majority of them are very positive, so that's reassuring.

0:28:52.840 --> 0:28:54.800
<v Speaker 1>And for everyone that reviews them on Amazon, I get

0:28:54.800 --> 0:28:57.480
<v Speaker 1>a whole bunch of emails and tweets and texts from

0:28:57.560 --> 0:29:00.479
<v Speaker 1>people that personally text me and let me know how

0:29:00.520 --> 0:29:03.160
<v Speaker 1>much they're loving the book. And I think another part

0:29:03.200 --> 0:29:05.520
<v Speaker 1>of this is that folks are ordering two or three

0:29:05.600 --> 0:29:08.000
<v Speaker 1>or four or even six copies of the book at

0:29:08.040 --> 0:29:11.080
<v Speaker 1>a time, and that means that they're sharing them with

0:29:11.120 --> 0:29:14.000
<v Speaker 1>their friends. They're really liking them, and I love that,

0:29:14.120 --> 0:29:16.200
<v Speaker 1>so thank you so much to everyone who's ordered one.

0:29:16.800 --> 0:29:18.480
<v Speaker 1>I just wanted to read a few of the reviews.

0:29:18.800 --> 0:29:21.400
<v Speaker 1>This was from Jeff h. He said, this is a

0:29:21.440 --> 0:29:23.760
<v Speaker 1>great book with great helpful tips. I bought one for

0:29:23.800 --> 0:29:27.040
<v Speaker 1>myself and a couple others for gifts. Highly recommend. Thanks again,

0:29:27.120 --> 0:29:29.719
<v Speaker 1>Rich for all that you'd help us with tech and

0:29:29.760 --> 0:29:31.200
<v Speaker 1>I think I've read this one before. If you're ever

0:29:31.200 --> 0:29:32.960
<v Speaker 1>in the Pomona area, you got a free lunch coming

0:29:33.000 --> 0:29:34.600
<v Speaker 1>your way. I think I read that on the podcast,

0:29:34.640 --> 0:29:38.080
<v Speaker 1>but I like it, so thank you. Jeff and Let's

0:29:38.080 --> 0:29:40.720
<v Speaker 1>see Lone Star ten said, I thought I knew everything.

0:29:40.760 --> 0:29:42.400
<v Speaker 1>I thought I knew a lot about my iPhone ten

0:29:42.520 --> 0:29:44.960
<v Speaker 1>s until I read Rich's book. This book is filled

0:29:44.960 --> 0:29:46.640
<v Speaker 1>with tips to help you get the most out of

0:29:46.680 --> 0:29:50.000
<v Speaker 1>this eleven hundred dollars phone. I would definitely agree. Steve

0:29:50.280 --> 0:29:54.720
<v Speaker 1>Zweig says this book answered several questions that had been

0:29:54.720 --> 0:29:58.360
<v Speaker 1>puzzling me for years. Example, app management, which was formally

0:29:58.440 --> 0:30:00.880
<v Speaker 1>done through iTunes but is now done through the App Store.

0:30:01.160 --> 0:30:03.640
<v Speaker 1>I had no idea. Lots of other juicy little plums

0:30:03.640 --> 0:30:09.560
<v Speaker 1>in here. Highly recommended. Steve Zweig. La T. Pavicek said

0:30:09.720 --> 0:30:12.320
<v Speaker 1>this is perfect, so much information. I gave up the

0:30:12.360 --> 0:30:15.440
<v Speaker 1>BlackBerry and started with the iPhone four, then five, six, seven,

0:30:15.600 --> 0:30:18.640
<v Speaker 1>eight and seven plus and eight plus and I'm still

0:30:18.680 --> 0:30:22.160
<v Speaker 1>learning new things with this book. Great gift. Wayne Ben says,

0:30:22.360 --> 0:30:24.520
<v Speaker 1>just receive my iPhone ten are This book helped me

0:30:24.600 --> 0:30:26.400
<v Speaker 1>quite a bit. I learned a lot from it. The

0:30:26.440 --> 0:30:29.480
<v Speaker 1>tips are very good and will use this as a reference.

0:30:29.680 --> 0:30:32.000
<v Speaker 1>Thanks so much to everyone who has left a review

0:30:32.080 --> 0:30:33.800
<v Speaker 1>for my book. If you bought the book and you're

0:30:33.880 --> 0:30:36.840
<v Speaker 1>enjoying it, please leave a review on Amazon that will

0:30:36.840 --> 0:30:39.520
<v Speaker 1>help others discover it and also sort of better understand

0:30:39.560 --> 0:30:41.520
<v Speaker 1>because if you're living in other parts of the country

0:30:41.560 --> 0:30:43.840
<v Speaker 1>where you may not know rich on Tech or rich Demiro,

0:30:44.120 --> 0:30:46.200
<v Speaker 1>you see this book, it's the number one seller as

0:30:46.200 --> 0:30:48.320
<v Speaker 1>an iPhone guide, and you're wondering if you should buy it.

0:30:48.640 --> 0:30:51.720
<v Speaker 1>Your review will definitely help more folks purchase it that

0:30:51.800 --> 0:30:54.920
<v Speaker 1>don't necessarily know who I am and see me on TV.

0:30:55.040 --> 0:30:58.640
<v Speaker 1>So thanks in advance for leaving your positive review on Amazon.

0:30:58.720 --> 0:31:01.920
<v Speaker 1>I do appreciate it. If you do want an autographed

0:31:01.920 --> 0:31:07.520
<v Speaker 1>copy gumroad dot com slash rich on Tech, gumroad dot

0:31:07.560 --> 0:31:11.640
<v Speaker 1>com slash rich on Tech. I'm selling personalized signed copies

0:31:11.680 --> 0:31:13.000
<v Speaker 1>of the book, So if you want to give one

0:31:13.000 --> 0:31:14.680
<v Speaker 1>as a gift to someone, or if you want to

0:31:14.720 --> 0:31:18.000
<v Speaker 1>get one for yourself, it's a couple bucks more than

0:31:18.040 --> 0:31:20.120
<v Speaker 1>you get it on Amazon, just because I have to

0:31:20.160 --> 0:31:22.840
<v Speaker 1>do the work of shipping it out myself. So if

0:31:22.840 --> 0:31:25.200
<v Speaker 1>you're sort of into that thing and you want a

0:31:25.280 --> 0:31:29.840
<v Speaker 1>signed copy. Gumroad dot com, slash rich on Tech. All right, yes,

0:31:29.960 --> 0:31:32.880
<v Speaker 1>and Lester's asking on the Facebook Live is there an

0:31:32.880 --> 0:31:35.280
<v Speaker 1>ebook version of your book? Yes, there's an ebook version.

0:31:35.280 --> 0:31:37.920
<v Speaker 1>You can get it on Kindle, so also on Amazon,

0:31:38.040 --> 0:31:40.040
<v Speaker 1>just grab the Kindle version. And I also got a

0:31:40.080 --> 0:31:42.280
<v Speaker 1>lot of questions from people asking me if the Kindle

0:31:42.360 --> 0:31:45.080
<v Speaker 1>version works on other places. It said, rich I don't

0:31:45.120 --> 0:31:47.000
<v Speaker 1>have a Kindle, so I can't listen to it or

0:31:47.000 --> 0:31:48.840
<v Speaker 1>read it rather on the Kindle, and I said, yeah,

0:31:48.840 --> 0:31:51.280
<v Speaker 1>you can download the Kindle app for the iPad, you

0:31:51.320 --> 0:31:53.760
<v Speaker 1>can download it for iPhone, you can download it for Android,

0:31:54.120 --> 0:31:56.640
<v Speaker 1>so you can get the Kindle version anywhere. And in

0:31:56.680 --> 0:31:58.560
<v Speaker 1>many cases, it's kind of funny because I noticed that

0:31:58.600 --> 0:32:03.040
<v Speaker 1>Amazon is actually pushing the Kindle version because the other

0:32:03.040 --> 0:32:05.400
<v Speaker 1>one's sort of out of stock it at this point,

0:32:05.600 --> 0:32:07.360
<v Speaker 1>so they're like, hey, why not get it faster and

0:32:07.400 --> 0:32:09.240
<v Speaker 1>just read it on the Kindle, which is kind of funny.

0:32:09.840 --> 0:32:12.040
<v Speaker 1>Thanks so much for listening to the podcast. I really

0:32:12.040 --> 0:32:14.600
<v Speaker 1>do appreciate it. Everything I talk about here I will

0:32:14.600 --> 0:32:16.640
<v Speaker 1>put in the show notes, so check it out there,

0:32:16.760 --> 0:32:19.120
<v Speaker 1>or you can go to rich on Tech dot tv.

0:32:19.640 --> 0:32:21.840
<v Speaker 1>Follow me on Instagram. I think I'm gonna do more

0:32:21.880 --> 0:32:24.920
<v Speaker 1>on Instagram in the new year, So Instagram, I am

0:32:25.040 --> 0:32:28.360
<v Speaker 1>at rich On Tech. Do appreciate you listening. Have a

0:32:28.480 --> 0:32:30.840
<v Speaker 1>fantastic holiday. I'm not sure if I'm gonna be doing

0:32:30.880 --> 0:32:34.440
<v Speaker 1>this podcast until the New Year, so I may take

0:32:34.440 --> 0:32:37.240
<v Speaker 1>a week off next week for the holidays. I've got

0:32:37.240 --> 0:32:39.120
<v Speaker 1>family in town, so if you don't hear from me,

0:32:39.400 --> 0:32:43.320
<v Speaker 1>have a fantastic holiday, Christmas, whatever else you celebrate, plus

0:32:43.360 --> 0:32:46.520
<v Speaker 1>New Year's and happy twenty nineteen. I will see then.

0:32:46.800 --> 0:32:49.200
<v Speaker 1>I'm Rich Jimiro. I will talk to you real soon