WEBVTT - Tech News: Twitter and Tesla and Elon, Oh My!

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to tech Stuff, a production from I Heart Radio.

0:00:11.840 --> 0:00:14.239
<v Speaker 1>Hey there, and welcome to tex Stuff. I'm your host,

0:00:14.360 --> 0:00:17.240
<v Speaker 1>Jothan Strickland. I'm an executive producer with iHeart Radio. And

0:00:17.280 --> 0:00:19.720
<v Speaker 1>how the tech are you. It's time for the tech

0:00:19.760 --> 0:00:23.479
<v Speaker 1>news for Tuesday, June seven, t d two, and I

0:00:23.520 --> 0:00:27.240
<v Speaker 1>am back after a short vacation. Let's get to the

0:00:27.240 --> 0:00:31.560
<v Speaker 1>news and we'll start off with an Elon update. We

0:00:31.560 --> 0:00:37.400
<v Speaker 1>should probably get a little jingle for that, and of

0:00:37.440 --> 0:00:41.120
<v Speaker 1>course I'm talking about Elon Musk, the world's richest man

0:00:41.280 --> 0:00:44.000
<v Speaker 1>who has mastered the art of staying in the headlines,

0:00:44.920 --> 0:00:49.400
<v Speaker 1>usually by being a borish jerk. First, an update on

0:00:49.440 --> 0:00:53.640
<v Speaker 1>the Twitter situation. In case you weren't aware, Elon Musk

0:00:53.680 --> 0:00:57.600
<v Speaker 1>announced his intention to acquire Twitter and signed a deal

0:00:58.440 --> 0:01:01.880
<v Speaker 1>valued that around forty four bill million dollars and has

0:01:01.920 --> 0:01:05.960
<v Speaker 1>been kind of weird about it ever since. So he's

0:01:05.959 --> 0:01:08.160
<v Speaker 1>been showing signs they wants to back out of this

0:01:08.240 --> 0:01:11.000
<v Speaker 1>deal to acquire Twitter. In fact, he's been doing that

0:01:11.040 --> 0:01:13.199
<v Speaker 1>for a couple of weeks now, but it's been getting

0:01:13.200 --> 0:01:17.880
<v Speaker 1>more dramatic with Ellen demanding that Twitter handover data proving

0:01:18.000 --> 0:01:21.520
<v Speaker 1>the company's assertion that fewer than five percent of all

0:01:21.560 --> 0:01:26.360
<v Speaker 1>monetize able accounts on the platform are actually boughts. Ellen

0:01:26.760 --> 0:01:30.520
<v Speaker 1>says it's much much higher, maybe as high as ninety

0:01:30.640 --> 0:01:33.720
<v Speaker 1>or ninety five percent, but come on, that just doesn't

0:01:33.760 --> 0:01:37.000
<v Speaker 1>seem possible. Though it's also admittedly hard for me to

0:01:37.040 --> 0:01:39.840
<v Speaker 1>believe the five percent number. I think it's probably somewhere

0:01:39.880 --> 0:01:43.120
<v Speaker 1>in between. Anyway, His legal team sent a letter to Twitter,

0:01:43.240 --> 0:01:45.880
<v Speaker 1>essentially saying that Ellen is prepared to drop the deal

0:01:46.360 --> 0:01:50.320
<v Speaker 1>because Twitter has not complied with his requests. Twitter has

0:01:50.400 --> 0:01:54.920
<v Speaker 1>stated repeatedly that it has handed Elan the data. Also,

0:01:55.000 --> 0:01:58.720
<v Speaker 1>the deal included Elon waving due diligence. Plus from the

0:01:58.800 --> 0:02:00.840
<v Speaker 1>very beginning, he said that one of his goals was

0:02:00.880 --> 0:02:05.600
<v Speaker 1>to weed out bots, so this argument seems off right, Like,

0:02:05.840 --> 0:02:07.960
<v Speaker 1>if one of the things Ellen wanted to do was

0:02:08.120 --> 0:02:12.399
<v Speaker 1>clean Twitter of bots, then it seems odd that he's

0:02:12.480 --> 0:02:15.120
<v Speaker 1>hung up on the number of bots. And a lot

0:02:15.160 --> 0:02:18.600
<v Speaker 1>of armchair analysts have suggested that Ellen has been having

0:02:18.680 --> 0:02:21.520
<v Speaker 1>lots of second thoughts about this deal and that the

0:02:21.639 --> 0:02:24.919
<v Speaker 1>forty four billion dollar price tag is way too high,

0:02:25.040 --> 0:02:28.600
<v Speaker 1>particularly since Twitter's stock prices dipped a couple of times

0:02:28.639 --> 0:02:32.639
<v Speaker 1>since the deal was announced, and moreover, Elon's own stock

0:02:32.639 --> 0:02:35.720
<v Speaker 1>in Tesla, where a lot of his wealth is has

0:02:35.760 --> 0:02:39.680
<v Speaker 1>been affected by another very dramatic drop in stock price.

0:02:40.240 --> 0:02:42.720
<v Speaker 1>Twitter appears to be set on this deal, however, and

0:02:42.800 --> 0:02:45.560
<v Speaker 1>I would not be surprised to see Twitter's own legal

0:02:45.560 --> 0:02:48.760
<v Speaker 1>team enter into litigation in an effort to force Ellen

0:02:48.919 --> 0:02:51.520
<v Speaker 1>to see it through. Right now, it sounds like the

0:02:51.560 --> 0:02:54.960
<v Speaker 1>deal is more likely to happen than not, despite the

0:02:55.000 --> 0:02:58.560
<v Speaker 1>appearance that Ellen wants out, because it's not that easy

0:02:58.639 --> 0:03:01.280
<v Speaker 1>to back out of these kinds of deals. We'll have

0:03:01.360 --> 0:03:04.920
<v Speaker 1>to see where this goes next. In related news, the

0:03:04.960 --> 0:03:07.560
<v Speaker 1>attorney general for the state of Texas has launched an

0:03:07.600 --> 0:03:12.080
<v Speaker 1>investigation into Twitter to look into the bought account issue.

0:03:12.760 --> 0:03:16.880
<v Speaker 1>Now you might wonder why the heck is the attorney

0:03:16.960 --> 0:03:19.960
<v Speaker 1>general of Texas doing this? What what is he doing?

0:03:20.760 --> 0:03:24.120
<v Speaker 1>Is it illegal to have bots on your platform? Well,

0:03:24.160 --> 0:03:26.240
<v Speaker 1>the answer to that second question is no, it's not

0:03:26.280 --> 0:03:28.840
<v Speaker 1>illegal to have bots in your platform. But Texas is

0:03:28.840 --> 0:03:32.120
<v Speaker 1>an attorney general whom I should point out faces charges

0:03:32.160 --> 0:03:35.800
<v Speaker 1>of securities fraud from seven years ago and has yet

0:03:35.840 --> 0:03:40.000
<v Speaker 1>to stand trial for that. He says that bots could

0:03:40.040 --> 0:03:43.760
<v Speaker 1>inflate Twitter's value, which could affect quote the costs of

0:03:43.800 --> 0:03:47.680
<v Speaker 1>doing business with it, thus directly harming consumers and businesses.

0:03:47.800 --> 0:03:51.120
<v Speaker 1>End quote. Now you might wonder if all this is

0:03:51.160 --> 0:03:54.560
<v Speaker 1>worth spending taxpayer money on an investigation, and I would

0:03:54.560 --> 0:03:58.960
<v Speaker 1>say I don't think so. But maybe Ellen is friendly

0:03:58.960 --> 0:04:03.000
<v Speaker 1>with the Attorney General's office. I just don't know. Meanwhile,

0:04:03.160 --> 0:04:07.640
<v Speaker 1>over at Tesla, there's been some confusion as to whether

0:04:07.920 --> 0:04:10.000
<v Speaker 1>or not the company is going to make some big

0:04:10.120 --> 0:04:14.600
<v Speaker 1>cuts in its employees. Reuters reported that Musk sent out

0:04:14.600 --> 0:04:18.160
<v Speaker 1>an email last week indicating that Tesla was instituting a

0:04:18.240 --> 0:04:20.680
<v Speaker 1>hiring freeze and that there would be a move to

0:04:20.720 --> 0:04:25.080
<v Speaker 1>cut staff by ten percent. A second email apparently indicated

0:04:25.120 --> 0:04:29.400
<v Speaker 1>that that ten percent cut would really just affect salaried employees,

0:04:29.880 --> 0:04:34.520
<v Speaker 1>not hourly workers. Then Musk tweeted that total head count

0:04:34.560 --> 0:04:38.560
<v Speaker 1>at Tesla would actually increase, but salaried employee numbers would

0:04:38.560 --> 0:04:43.240
<v Speaker 1>stay quote fairly flat end quote. So does that mean

0:04:43.279 --> 0:04:46.720
<v Speaker 1>there will not be a ten percent cut of salaried employees,

0:04:47.400 --> 0:04:50.440
<v Speaker 1>I honestly have no clue. Musk indicated that he felt

0:04:50.480 --> 0:04:53.680
<v Speaker 1>some areas of the company were overstaffed, which suggests that

0:04:53.720 --> 0:04:58.320
<v Speaker 1>he is going to make cuts and maybe cutting one

0:04:58.360 --> 0:05:02.159
<v Speaker 1>tenth of your salaried employees seems fairly flat to him,

0:05:02.480 --> 0:05:05.119
<v Speaker 1>It's hard to say. Also, this comes on the tail

0:05:05.320 --> 0:05:08.680
<v Speaker 1>of numerous messages from Musk indicating that he wants folks

0:05:08.720 --> 0:05:11.760
<v Speaker 1>back in the office full time and that people should

0:05:12.040 --> 0:05:14.520
<v Speaker 1>expect to work from home only after they've put in

0:05:14.600 --> 0:05:17.320
<v Speaker 1>forty hours of work at the office. And for those

0:05:17.320 --> 0:05:20.200
<v Speaker 1>of you who are unaware, forty hours is considered a

0:05:20.279 --> 0:05:24.240
<v Speaker 1>normal workload for a week in the United States. Anyway.

0:05:24.279 --> 0:05:27.120
<v Speaker 1>That led many of those same armchair analysts that I

0:05:27.160 --> 0:05:30.880
<v Speaker 1>mentioned earlier suggests that maybe Musk is trying to convince

0:05:30.920 --> 0:05:35.040
<v Speaker 1>salaried folks to quit, but possibly because maybe if they quit,

0:05:35.080 --> 0:05:37.280
<v Speaker 1>they won't get the same sort of severance deal that

0:05:37.320 --> 0:05:40.200
<v Speaker 1>they would be entitled to if they were instead laid off.

0:05:40.920 --> 0:05:43.360
<v Speaker 1>I don't know. That sounds pretty cynical to me, but

0:05:43.520 --> 0:05:46.800
<v Speaker 1>I mean it could be true. Yesterday, Apple held its

0:05:46.880 --> 0:05:52.080
<v Speaker 1>Worldwide Developers Conference, or w w d C. This event is,

0:05:52.160 --> 0:05:56.320
<v Speaker 1>as the name suggests, primarily directed towards app developers so

0:05:56.360 --> 0:05:58.480
<v Speaker 1>that they can see the sort of support and features

0:05:58.480 --> 0:06:01.240
<v Speaker 1>that they can expect while they're eating the next generation

0:06:01.279 --> 0:06:05.000
<v Speaker 1>of computer and mobile apps. But there's usually some nuggets

0:06:05.000 --> 0:06:07.520
<v Speaker 1>in there that are of interest to the end consumer

0:06:07.560 --> 0:06:10.600
<v Speaker 1>as well. This year we got to see a redesigned

0:06:10.640 --> 0:06:16.600
<v Speaker 1>MacBook Air, which features Apple's mto processor chip. The MacBook

0:06:16.640 --> 0:06:18.960
<v Speaker 1>Air weighs in at just two point seven pounds or

0:06:19.040 --> 0:06:23.479
<v Speaker 1>one point two kims, and it measures just eleven millimeters thick.

0:06:24.080 --> 0:06:26.840
<v Speaker 1>It's also cut some other nifty features, so folks who

0:06:26.839 --> 0:06:29.599
<v Speaker 1>won a super thin, super light Mac should be happy,

0:06:30.120 --> 0:06:32.840
<v Speaker 1>assuming they can shell out the twelve hundred bucks it'll

0:06:32.880 --> 0:06:37.000
<v Speaker 1>take to secure the base model. Other models are more expensive.

0:06:37.320 --> 0:06:41.080
<v Speaker 1>The company also introduced the MacBook Pro thirteen, also with

0:06:41.160 --> 0:06:44.640
<v Speaker 1>the M two chip and a new active cooling system.

0:06:44.880 --> 0:06:48.520
<v Speaker 1>The MacBook Pro their team starts at about hundred bucks

0:06:49.040 --> 0:06:52.159
<v Speaker 1>and to run on top of those computers. Apple showed

0:06:52.160 --> 0:06:55.880
<v Speaker 1>off the new Mac OS build called Ventura. So app

0:06:55.920 --> 0:07:00.440
<v Speaker 1>always names its OS builds off California landmarks anyway. Ventura

0:07:00.560 --> 0:07:04.360
<v Speaker 1>adds some new features, like an improved search function, which

0:07:04.360 --> 0:07:07.320
<v Speaker 1>can search not just the macs contents but also the web.

0:07:08.080 --> 0:07:10.720
<v Speaker 1>The OS also supports face i D and touch i D,

0:07:10.960 --> 0:07:14.480
<v Speaker 1>allowing users to create biometric logins rather than past words,

0:07:15.120 --> 0:07:19.160
<v Speaker 1>and there's also a feature called Continuity Camera that will

0:07:19.240 --> 0:07:22.160
<v Speaker 1>let Mac users with iPhones turn their iPhone into a

0:07:22.240 --> 0:07:26.960
<v Speaker 1>webcam while chatting on their Mac. iOS also got an update,

0:07:27.120 --> 0:07:30.720
<v Speaker 1>so we're up to iOS sixteen now. Apple showed off

0:07:30.760 --> 0:07:34.280
<v Speaker 1>an updated customizable lock screen for iPhones, which users can

0:07:34.280 --> 0:07:37.600
<v Speaker 1>tweak by changing up fonts and colors, And I wonder

0:07:37.640 --> 0:07:41.800
<v Speaker 1>how Sir Johnny Ives feels about all that. Folks who

0:07:41.920 --> 0:07:44.520
<v Speaker 1>use Apple's Messages app will be glad to see that

0:07:44.600 --> 0:07:47.160
<v Speaker 1>they can now edit messages that they've sent so they

0:07:47.160 --> 0:07:50.240
<v Speaker 1>can fix irritating typos or un send a message if

0:07:50.280 --> 0:07:53.680
<v Speaker 1>they like. Oh and Apple also added new safety check

0:07:53.760 --> 0:07:57.720
<v Speaker 1>features that lets users revoke data access from other people

0:07:58.200 --> 0:08:01.400
<v Speaker 1>so that those other people cannot snoop or stalk you,

0:08:01.520 --> 0:08:04.560
<v Speaker 1>which is a darn good edition in my mind. Likewise,

0:08:04.720 --> 0:08:07.520
<v Speaker 1>the iPad got some similar updates, plus a new app

0:08:07.560 --> 0:08:10.520
<v Speaker 1>for weather data, and the watch os is up to

0:08:10.640 --> 0:08:13.400
<v Speaker 1>version nine now and has more watch phases. You can

0:08:13.440 --> 0:08:15.600
<v Speaker 1>pen apps that you use a lot on the watches

0:08:15.640 --> 0:08:18.560
<v Speaker 1>face and things like that. There's a lot more than

0:08:18.600 --> 0:08:21.640
<v Speaker 1>they announced, but I figure anyone's super interested in Apple

0:08:21.680 --> 0:08:24.880
<v Speaker 1>announcements is either already well aware of this or is

0:08:24.880 --> 0:08:27.200
<v Speaker 1>going to look into it into further detail, so we'll

0:08:27.240 --> 0:08:30.560
<v Speaker 1>just move on. Earlier today, the EU gave Apple a

0:08:30.560 --> 0:08:33.760
<v Speaker 1>bit of a setback when it adopted a provisional agreement

0:08:33.800 --> 0:08:37.320
<v Speaker 1>that would require all smartphones and tablets to be compatible

0:08:37.320 --> 0:08:41.000
<v Speaker 1>with us b C chargers by late twenty four in

0:08:41.040 --> 0:08:43.840
<v Speaker 1>the EU. Now, this is not yet set in stone.

0:08:44.160 --> 0:08:46.800
<v Speaker 1>Twenty seven EU countries are going to have to agree

0:08:46.800 --> 0:08:49.559
<v Speaker 1>to this and the EU Parliament will have to pass

0:08:49.559 --> 0:08:53.000
<v Speaker 1>it into law. But if it does become law, Apple

0:08:53.040 --> 0:08:55.920
<v Speaker 1>will have no option but to include USB Sports on

0:08:56.000 --> 0:08:59.560
<v Speaker 1>its devices sold in the EU. So why is the

0:08:59.600 --> 0:09:04.160
<v Speaker 1>EU doing this? Well, having a common standard for chargers

0:09:04.559 --> 0:09:07.199
<v Speaker 1>gives consumers the option of using the same cables from

0:09:07.280 --> 0:09:10.040
<v Speaker 1>device to device, which can save them money and it

0:09:10.080 --> 0:09:13.640
<v Speaker 1>can also cut back on E waste. Apple had previously

0:09:13.800 --> 0:09:17.240
<v Speaker 1>argued that forcing the company to abandon its lightning port

0:09:17.640 --> 0:09:23.000
<v Speaker 1>and to convert over to USBC would hurt innovation. Now

0:09:23.040 --> 0:09:25.240
<v Speaker 1>I don't know if that's true or not. I do

0:09:25.320 --> 0:09:27.760
<v Speaker 1>know it would hurt Apple's ability to make more money

0:09:27.800 --> 0:09:32.480
<v Speaker 1>by selling lightning accessories. Anyway, I'll follow up on this

0:09:32.600 --> 0:09:36.640
<v Speaker 1>should the provisional Agreement become EU law. We've got a

0:09:36.640 --> 0:09:38.960
<v Speaker 1>few more stories to cover before we get to that.

0:09:39.400 --> 0:09:49.880
<v Speaker 1>Let's take a quick break. Mercedes Benz has issued a

0:09:49.920 --> 0:09:54.080
<v Speaker 1>recall that is affecting almost a million vehicles around the world.

0:09:54.600 --> 0:09:58.160
<v Speaker 1>So at issue are the break booster components in certain

0:09:58.240 --> 0:10:03.319
<v Speaker 1>Mercedes vehicles. They turn out to be prone to corrosion,

0:10:03.400 --> 0:10:06.560
<v Speaker 1>and that corrosion can be severe enough to cause break failure,

0:10:06.960 --> 0:10:09.960
<v Speaker 1>which is obviously something you would want to avoid. The

0:10:10.040 --> 0:10:13.360
<v Speaker 1>vehicles affected include the two thousand six to two thousand

0:10:13.440 --> 0:10:17.600
<v Speaker 1>twelve mL class and g L class SUVs, as well

0:10:17.679 --> 0:10:21.640
<v Speaker 1>as the R class minivan. The company warns that drivers

0:10:21.640 --> 0:10:24.520
<v Speaker 1>may notice that their brake pedal starts to feel a

0:10:24.559 --> 0:10:28.000
<v Speaker 1>bit soft, or that they might hear air noises like

0:10:28.040 --> 0:10:32.040
<v Speaker 1>wheezing or or squeaking through the breaking system, and that

0:10:32.320 --> 0:10:34.520
<v Speaker 1>if you do experience any of that, you should not

0:10:34.600 --> 0:10:38.120
<v Speaker 1>be driving your vehicle anymore until it can be inspected

0:10:38.200 --> 0:10:43.720
<v Speaker 1>and then subsequently repaired by an authorized dealership. Last week, Axon,

0:10:43.920 --> 0:10:46.960
<v Speaker 1>the company behind the Taser stun gun, announced that it

0:10:47.040 --> 0:10:50.520
<v Speaker 1>was developing a drone outfitted with a Taser, specifically to

0:10:50.600 --> 0:10:53.280
<v Speaker 1>deploy in situations where there is an active shooter or

0:10:53.360 --> 0:10:57.839
<v Speaker 1>a similar threat. However, Axon's ethics board subsequently released a

0:10:57.840 --> 0:11:02.520
<v Speaker 1>statement making it clear they were vehemently opposed to this idea.

0:11:02.840 --> 0:11:06.480
<v Speaker 1>The board revealed that Axon had previously suggested a more

0:11:06.520 --> 0:11:10.480
<v Speaker 1>scaled back version of this drone, and they had proposed

0:11:10.480 --> 0:11:13.880
<v Speaker 1>that a year ago, and the Ethics Board had even

0:11:14.000 --> 0:11:18.120
<v Speaker 1>voted that down, which was you know, less robust, you

0:11:18.200 --> 0:11:20.960
<v Speaker 1>might say. So it did come as quite a shock

0:11:21.040 --> 0:11:25.280
<v Speaker 1>when the company announced this, you know, full on Taser drone,

0:11:25.720 --> 0:11:28.559
<v Speaker 1>and that was enough to convince nine of the twelve

0:11:28.640 --> 0:11:31.959
<v Speaker 1>Ethics Board members to quit. So that brought a lot

0:11:32.000 --> 0:11:34.360
<v Speaker 1>more attention to the topic. ACS and then released a

0:11:34.400 --> 0:11:37.640
<v Speaker 1>subsequent statement revealing the company had decided to pause work

0:11:37.640 --> 0:11:41.320
<v Speaker 1>on the project and refocus quote to further engage with

0:11:41.440 --> 0:11:47.520
<v Speaker 1>key constituencies to fully explore the best path forward end quote, which,

0:11:47.880 --> 0:11:51.160
<v Speaker 1>uh is kind of a fancy way of saying, we

0:11:51.200 --> 0:11:55.760
<v Speaker 1>need to rethink this. Spiegel reports that Telegram, the messaging app,

0:11:56.160 --> 0:11:59.400
<v Speaker 1>has been sharing user data with the Federal Criminal Police

0:11:59.440 --> 0:12:03.239
<v Speaker 1>Office and Harmony in several cases. Now this is noteworthy

0:12:03.440 --> 0:12:07.120
<v Speaker 1>mainly because Telegram has long claimed that it would never

0:12:07.240 --> 0:12:12.080
<v Speaker 1>share user data with any third party, including governments. That

0:12:12.160 --> 0:12:15.200
<v Speaker 1>appears to no longer be the case. As for why

0:12:15.320 --> 0:12:17.720
<v Speaker 1>Telegrams shared this data in the first place, While the

0:12:17.760 --> 0:12:20.920
<v Speaker 1>cases in question were very serious ones, they ranged from

0:12:21.160 --> 0:12:26.120
<v Speaker 1>terrorism to child abuse. Now complicating matters is that far

0:12:26.280 --> 0:12:30.840
<v Speaker 1>right extremists have been taken to using Telegram precisely because

0:12:30.920 --> 0:12:33.920
<v Speaker 1>the service has said it will not hand data over

0:12:33.960 --> 0:12:38.720
<v Speaker 1>to authorities. The founder of Telegram, Pavel Durov, did announce

0:12:38.760 --> 0:12:41.400
<v Speaker 1>back in ten that the company would start to hand

0:12:41.400 --> 0:12:44.880
<v Speaker 1>over information like phone numbers and I P addresses if

0:12:44.920 --> 0:12:48.400
<v Speaker 1>it were so ordered by a court, but otherwise would

0:12:48.440 --> 0:12:51.560
<v Speaker 1>not share data, and the company added that at least

0:12:51.600 --> 0:12:53.800
<v Speaker 1>as of the last time it updated the information on

0:12:53.840 --> 0:12:57.360
<v Speaker 1>this web page, that it had never received any request

0:12:57.400 --> 0:12:59.760
<v Speaker 1>from a court like that, like an actual court order.

0:13:00.360 --> 0:13:03.160
<v Speaker 1>But apparently in February of this year, Durov and some

0:13:03.280 --> 0:13:06.400
<v Speaker 1>of his associates held a virtual meeting with Germany's Federal

0:13:06.440 --> 0:13:09.600
<v Speaker 1>Ministry of the Interior to set up a quote reliable

0:13:09.679 --> 0:13:13.080
<v Speaker 1>direct channel at the working level end quote. I am

0:13:13.120 --> 0:13:16.600
<v Speaker 1>actually not entirely sure what that entails. I don't know

0:13:16.760 --> 0:13:21.199
<v Speaker 1>what information the authorities actually have access to. But this

0:13:21.240 --> 0:13:25.079
<v Speaker 1>is another example of the very complicated dilemma of running

0:13:25.120 --> 0:13:28.280
<v Speaker 1>a messaging service. So on the one hand, you want

0:13:28.320 --> 0:13:31.040
<v Speaker 1>the service to be secure and private for users, so

0:13:31.080 --> 0:13:34.400
<v Speaker 1>that your users trust it and they use it, and

0:13:34.520 --> 0:13:38.240
<v Speaker 1>that they feel that they are safe from having authoritarian

0:13:38.320 --> 0:13:42.400
<v Speaker 1>governments turned the app into a kind of surveillance. But

0:13:42.480 --> 0:13:44.440
<v Speaker 1>on the other hand, you also want to limit the

0:13:44.480 --> 0:13:48.000
<v Speaker 1>spread of extremist ideology that you don't want to enable

0:13:48.080 --> 0:13:52.240
<v Speaker 1>hate groups. So it is a very complicated matter. I

0:13:52.280 --> 0:13:55.280
<v Speaker 1>expect we're gonna get a well, I'm sure, I'm sorry

0:13:55.720 --> 0:13:59.560
<v Speaker 1>from Canadian coffee chain Tim Horton's pretty soon. Turns out

0:13:59.640 --> 0:14:02.760
<v Speaker 1>that the mobile app for tim Horton's was snoreffing up

0:14:02.840 --> 0:14:07.199
<v Speaker 1>user data like location information faster than I can wolf

0:14:07.240 --> 0:14:10.400
<v Speaker 1>down a whole bag of tim bits. That's pretty darn fast.

0:14:10.880 --> 0:14:14.199
<v Speaker 1>According to Canadian investigators, the app was pulling down location

0:14:14.280 --> 0:14:18.520
<v Speaker 1>data every few minutes of every day up to through

0:14:19.840 --> 0:14:22.520
<v Speaker 1>and not only is that a massive breach of privacy,

0:14:22.720 --> 0:14:26.080
<v Speaker 1>it's also illegal, but it would also make your phone

0:14:26.080 --> 0:14:29.040
<v Speaker 1>work overtime and drain your battery faster. So, according to

0:14:29.040 --> 0:14:32.760
<v Speaker 1>the investigators, the app would alert users that it would

0:14:32.760 --> 0:14:35.960
<v Speaker 1>track their location, so it was asking permission to track location,

0:14:36.040 --> 0:14:39.360
<v Speaker 1>but the implication was that it was only going to

0:14:39.520 --> 0:14:43.160
<v Speaker 1>do that while the app was actively open, But in fact,

0:14:43.400 --> 0:14:46.320
<v Speaker 1>the app was tracking users even when the app wasn't

0:14:46.320 --> 0:14:48.640
<v Speaker 1>in use, and it would continue doing so as long

0:14:48.640 --> 0:14:52.040
<v Speaker 1>as the user's device remained on the company had been

0:14:52.080 --> 0:14:55.040
<v Speaker 1>planning to use the app for targeted advertising, which obviously

0:14:55.080 --> 0:14:57.920
<v Speaker 1>gets more targeted the more data you have about your customer.

0:14:58.320 --> 0:15:01.240
<v Speaker 1>And Tim Horton's actually stopped track users locations on a

0:15:01.320 --> 0:15:05.560
<v Speaker 1>continual basis back in, but maintained a contract with a

0:15:05.600 --> 0:15:09.280
<v Speaker 1>location data broker for a while and the company has

0:15:09.320 --> 0:15:12.880
<v Speaker 1>agreed to now bring all apps and processes within Canadian

0:15:12.920 --> 0:15:17.200
<v Speaker 1>compliance and in return it will not be punished because

0:15:17.200 --> 0:15:21.120
<v Speaker 1>setting the law on a coffee shop is just playing ludicrous.

0:15:21.160 --> 0:15:25.160
<v Speaker 1>I mean, you've probably seen all the cops hanging out

0:15:25.240 --> 0:15:27.840
<v Speaker 1>at the coffee shop. A few years ago, I talked

0:15:27.880 --> 0:15:31.560
<v Speaker 1>about how researchers were working on an autonomous ship that

0:15:31.560 --> 0:15:35.880
<v Speaker 1>would cross the Atlantic Ocean. It's called the Mayflower Autonomous

0:15:36.000 --> 0:15:38.640
<v Speaker 1>Ship or m AS, and it's named after the Mayflower

0:15:38.680 --> 0:15:42.160
<v Speaker 1>ship that brought settlers to North America. Well, the ship

0:15:42.240 --> 0:15:45.280
<v Speaker 1>has now crossed the Atlantic, but the crossing did not

0:15:45.400 --> 0:15:49.320
<v Speaker 1>go completely as planned. The m a S left the

0:15:49.440 --> 0:15:54.040
<v Speaker 1>UK on April nine, crewed only by its AI and

0:15:54.160 --> 0:15:57.720
<v Speaker 1>all of its sensors and and actuators, and it was

0:15:57.760 --> 0:16:00.560
<v Speaker 1>bound for Massachusetts, but at some point the ship began

0:16:00.640 --> 0:16:05.680
<v Speaker 1>encountering technical difficulties, so the researchers decided to divert the

0:16:05.720 --> 0:16:09.960
<v Speaker 1>ship so that it would instead arrive in Halifax, Nova Scotia.

0:16:10.480 --> 0:16:14.400
<v Speaker 1>That's a bit further north than east of Massachusetts. IBM,

0:16:14.400 --> 0:16:16.800
<v Speaker 1>which developed much of the technology on board the ship,

0:16:16.960 --> 0:16:19.240
<v Speaker 1>says the plan is for the m AS two later

0:16:19.280 --> 0:16:22.840
<v Speaker 1>continue its journey and head from Halifax to Plymouth, Massachusetts

0:16:23.360 --> 0:16:27.080
<v Speaker 1>and then on to Washington, d C. And that's it.

0:16:27.280 --> 0:16:31.240
<v Speaker 1>That's the news for Tuesday, June seven two. Hope you

0:16:31.280 --> 0:16:34.400
<v Speaker 1>are all well. If you would like to leave me

0:16:34.440 --> 0:16:37.280
<v Speaker 1>any comments, questions, maybe you've got a suggestion for a

0:16:37.280 --> 0:16:39.840
<v Speaker 1>future episode, you can reach out to me. One way

0:16:39.880 --> 0:16:42.320
<v Speaker 1>to do that is to use the I Heart Radio app.

0:16:42.640 --> 0:16:45.600
<v Speaker 1>Navigate over to the tech Stuff page on the Heart

0:16:45.680 --> 0:16:49.600
<v Speaker 1>Radio app, use that little microphone icon. You can record

0:16:49.640 --> 0:16:52.600
<v Speaker 1>a message of up to thirty seconds, and if you like,

0:16:52.720 --> 0:16:54.800
<v Speaker 1>you can let me know if you would wouldn't mind

0:16:54.840 --> 0:16:57.840
<v Speaker 1>me using the audio in a future episode. The other

0:16:57.840 --> 0:16:59.920
<v Speaker 1>way to reach me, of course, is to use Twitter

0:17:00.080 --> 0:17:02.240
<v Speaker 1>or The handle for the show is tech Stuff h

0:17:02.400 --> 0:17:07.119
<v Speaker 1>s W and I'll talk to you again really soon. Y.

0:17:11.400 --> 0:17:14.400
<v Speaker 1>Tech Stuff is an I Heart Radio production. For more

0:17:14.480 --> 0:17:17.840
<v Speaker 1>podcasts from my heart Radio, visit the i heart Radio app,

0:17:18.000 --> 0:17:21.159
<v Speaker 1>Apple podcasts, or wherever you listen to your favorite shows.