WEBVTT - Elon Musk Gets a Lot of Bad News

0:00:04.480 --> 0:00:12.399
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.440 --> 0:00:15.560
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:15.560 --> 0:00:19.119
<v Speaker 1>I'm an executive producer with iHeart Podcasts and how the

0:00:19.200 --> 0:00:21.599
<v Speaker 1>tech are you. It's time for the tech news for

0:00:21.640 --> 0:00:26.119
<v Speaker 1>the week ending on Friday, August thirtieth, twenty twenty four.

0:00:26.480 --> 0:00:29.600
<v Speaker 1>I feel like the entire world is at dragon Con.

0:00:29.880 --> 0:00:32.360
<v Speaker 1>I realize that that's just because I live in Atlanta.

0:00:32.560 --> 0:00:35.200
<v Speaker 1>That's where dragon CON's a big science fiction fantasy convention

0:00:35.240 --> 0:00:38.040
<v Speaker 1>if you're not familiar, And it seems like all of

0:00:38.040 --> 0:00:40.560
<v Speaker 1>my friends, like all the people I know, are currently

0:00:40.680 --> 0:00:44.080
<v Speaker 1>at dragon Con. So I'm getting a little fomo here.

0:00:44.240 --> 0:00:46.640
<v Speaker 1>But I realized a lot of y'all out there also

0:00:46.760 --> 0:00:50.080
<v Speaker 1>aren't there, So let us get lost in the warm

0:00:50.159 --> 0:00:55.640
<v Speaker 1>embrace of tech news. First up, there's an update on

0:00:55.840 --> 0:01:00.680
<v Speaker 1>the Telegram CEO Pavel Durov story. So on Wednesday, I

0:01:00.720 --> 0:01:05.680
<v Speaker 1>published an episode about Telegram, the messaging service, and how

0:01:05.760 --> 0:01:10.440
<v Speaker 1>French authorities recently detained the CEO, Pavel Durov, after his

0:01:10.520 --> 0:01:14.560
<v Speaker 1>private plane landed at an airport outside of Paris. Since then,

0:01:14.680 --> 0:01:18.560
<v Speaker 1>a court has indicted Durov on charges that he has

0:01:18.600 --> 0:01:23.360
<v Speaker 1>been complicit in numerous criminal activities that have been happening

0:01:23.600 --> 0:01:28.080
<v Speaker 1>or facilitated by the Telegram messaging service. So essentially, the

0:01:28.200 --> 0:01:32.400
<v Speaker 1>legal argument here is that Telegram has mostly hands off

0:01:32.560 --> 0:01:36.400
<v Speaker 1>policy when it comes to content moderation. They're very lax,

0:01:36.840 --> 0:01:39.520
<v Speaker 1>they don't do very much content moderation at all, and

0:01:39.560 --> 0:01:44.920
<v Speaker 1>that this means Telegram is effectively allowing crimes ranging from

0:01:45.440 --> 0:01:49.240
<v Speaker 1>terrorist acts to the spread of child sexual abuse material

0:01:49.400 --> 0:01:55.200
<v Speaker 1>see SAM material. I guess that's repetitive. It's like ATM machine. Moreover,

0:01:55.640 --> 0:01:59.520
<v Speaker 1>Telegram has a history of denying cooperation with law enforcement

0:01:59.560 --> 0:02:03.920
<v Speaker 1>officials who are conducting legal investigations into criminal activity, you know,

0:02:04.000 --> 0:02:07.200
<v Speaker 1>essentially like I've got a legal order for a wiretap

0:02:07.400 --> 0:02:11.280
<v Speaker 1>and this organization is not being compliant with it. So,

0:02:11.320 --> 0:02:14.920
<v Speaker 1>according to the charges, it's not just that Telegram failed

0:02:14.960 --> 0:02:20.239
<v Speaker 1>to cooperate with law enforcement, but that legally received requests

0:02:20.280 --> 0:02:23.200
<v Speaker 1>were just outright ignored, and that this amounts to the

0:02:23.240 --> 0:02:27.720
<v Speaker 1>same thing as assisting criminal activity, thus being complicit. And

0:02:27.880 --> 0:02:30.600
<v Speaker 1>France also has a law that states that services that

0:02:30.680 --> 0:02:35.840
<v Speaker 1>provide quote unquote cryptology solutions first have to make legal

0:02:35.880 --> 0:02:40.400
<v Speaker 1>declarations to France's cybersecurity agency in order to do so.

0:02:40.760 --> 0:02:45.280
<v Speaker 1>Legally within France. Now, Telegram does offer end to end

0:02:45.480 --> 0:02:50.080
<v Speaker 1>encryption services, but it's only for one on one communications.

0:02:50.280 --> 0:02:53.600
<v Speaker 1>Telegram also allows one to many kind of like Twitter

0:02:54.040 --> 0:02:58.960
<v Speaker 1>and also chat rooms, so those do not have encryption options,

0:02:59.040 --> 0:03:02.400
<v Speaker 1>and even for one on one communication, encryption is not

0:03:02.600 --> 0:03:05.680
<v Speaker 1>on by default, you have to turn it on manually.

0:03:06.400 --> 0:03:10.200
<v Speaker 1>Durov has already posted the five million euro bail money

0:03:10.440 --> 0:03:13.640
<v Speaker 1>that he was hit with, but he has also received

0:03:13.720 --> 0:03:17.520
<v Speaker 1>orders not to leave France until this matter has been concluded.

0:03:18.000 --> 0:03:21.680
<v Speaker 1>His brother Nikolai, who is also a co founder of Telegram,

0:03:22.120 --> 0:03:25.320
<v Speaker 1>also has a warrant out for his arrest in France.

0:03:25.840 --> 0:03:28.040
<v Speaker 1>I've got a lot of news relating to Elon Musk

0:03:28.160 --> 0:03:31.080
<v Speaker 1>and his various companies. I mean a lot, Like a

0:03:31.120 --> 0:03:34.840
<v Speaker 1>lot happened this week, I think just by coincidence. But

0:03:34.960 --> 0:03:37.640
<v Speaker 1>let's get through it. First. Up, we have a feud

0:03:37.920 --> 0:03:41.960
<v Speaker 1>brewing between a Brazilian Supreme Court judge and Elon Musk,

0:03:42.480 --> 0:03:46.240
<v Speaker 1>which I mean, that's a weird sentence, but Musk has

0:03:46.240 --> 0:03:51.280
<v Speaker 1>said that this judge, Alexandra de Mores, and I apologize

0:03:51.280 --> 0:03:54.560
<v Speaker 1>for butchering pronunciation, but that this judge has threatened to

0:03:54.640 --> 0:03:59.160
<v Speaker 1>incarcerate one of X's legal teams stationed in Brazil. If

0:03:59.400 --> 0:04:04.640
<v Speaker 1>X did not block some accounts on X that we're

0:04:04.680 --> 0:04:08.880
<v Speaker 1>operating within Brazil, those accounts, according to this judge, were

0:04:08.920 --> 0:04:14.320
<v Speaker 1>spreading misinformation and hate speech. Murkying up the waters is

0:04:14.320 --> 0:04:18.120
<v Speaker 1>the fact that Elon Musk appeared to be very cozy

0:04:18.720 --> 0:04:22.560
<v Speaker 1>with kind of a hard right leaning leader of Brazil

0:04:23.240 --> 0:04:26.920
<v Speaker 1>who is no longer the leader of Brazil, and that

0:04:27.720 --> 0:04:30.800
<v Speaker 1>the Supreme Court judge is kind of an opposition to

0:04:30.920 --> 0:04:35.960
<v Speaker 1>that particular political stance. So there's like some political tension

0:04:36.000 --> 0:04:41.520
<v Speaker 1>going on here beyond this claim that these accounts are

0:04:41.520 --> 0:04:46.200
<v Speaker 1>spreading misinformation. Now, Musk ended up replying to this request

0:04:46.279 --> 0:04:48.600
<v Speaker 1>of Hey, you need to shut this stuff down or

0:04:48.640 --> 0:04:52.919
<v Speaker 1>I'm going to arrest your lawyers here in Brazil. He

0:04:53.000 --> 0:04:57.800
<v Speaker 1>responded by shutting down X's offices in Brazil. He just

0:04:57.960 --> 0:05:02.839
<v Speaker 1>closed those offices outright. However, X is still providing service

0:05:03.080 --> 0:05:07.039
<v Speaker 1>in Brazil, it just doesn't maintain any offices there. However,

0:05:07.240 --> 0:05:10.960
<v Speaker 1>that creates a new legal issue for the company because

0:05:10.960 --> 0:05:15.320
<v Speaker 1>in Brazil, if you are providing a messaging company a

0:05:15.320 --> 0:05:19.200
<v Speaker 1>messaging service within the nation, you have to have a

0:05:19.320 --> 0:05:22.640
<v Speaker 1>presence in Brazil as well. There has to be someone

0:05:22.640 --> 0:05:25.560
<v Speaker 1>who's held accountable in the country, and by shutting down

0:05:25.560 --> 0:05:29.680
<v Speaker 1>the offices, Musk no longer has that person. So Maraz

0:05:29.920 --> 0:05:33.760
<v Speaker 1>could order X to be shut down in Brazil entirely.

0:05:34.440 --> 0:05:39.640
<v Speaker 1>And he also ordered that the bank accounts for Starlink

0:05:39.960 --> 0:05:44.720
<v Speaker 1>business in Brazil to be frozen. So Starlink is the

0:05:44.800 --> 0:05:48.960
<v Speaker 1>satellite internet service provider business. It's a branch of SpaceX,

0:05:48.960 --> 0:05:53.080
<v Speaker 1>which of course is another of Elon Musk's companies. And

0:05:53.520 --> 0:05:56.520
<v Speaker 1>y'all you know I am not a fan of Elon Musk.

0:05:56.680 --> 0:05:59.440
<v Speaker 1>I mean, I don't make that a secret, but it

0:05:59.480 --> 0:06:03.160
<v Speaker 1>does seem like a pretty drastic case of overreach if

0:06:03.200 --> 0:06:07.160
<v Speaker 1>you ask me, because X and Starlink are not part

0:06:07.160 --> 0:06:10.400
<v Speaker 1>of the same company. They may have the same obnoxious

0:06:10.600 --> 0:06:14.800
<v Speaker 1>dude behind them, but they aren't the same company. And

0:06:15.160 --> 0:06:18.560
<v Speaker 1>to shut down the assets of one company in order

0:06:18.640 --> 0:06:25.159
<v Speaker 1>to force a different company to follow your your legal rulings,

0:06:25.680 --> 0:06:28.960
<v Speaker 1>that strikes me as being very wrong. I also think

0:06:29.000 --> 0:06:31.680
<v Speaker 1>it's important to remember Elon Musk technically he's not the

0:06:31.680 --> 0:06:35.039
<v Speaker 1>CEO of X anymore. He hasn't been the CEO of

0:06:35.360 --> 0:06:40.839
<v Speaker 1>X for ages. It's Yakarino who's the CEO. But everyone

0:06:41.320 --> 0:06:44.719
<v Speaker 1>essentially assumes he's ultimately the one calling the shots over

0:06:44.760 --> 0:06:49.320
<v Speaker 1>at X, even if Yakarino is nominally CEO. I hate

0:06:49.320 --> 0:06:52.080
<v Speaker 1>to even use that phrase. I'm sure Yakarino does a

0:06:52.120 --> 0:06:55.800
<v Speaker 1>lot of work. I have no idea what her day

0:06:55.839 --> 0:06:58.520
<v Speaker 1>to day has to be like, nor do I understand

0:06:58.560 --> 0:07:00.800
<v Speaker 1>what it must be like to work at a company

0:07:00.800 --> 0:07:03.840
<v Speaker 1>where everyone just assumes that you are a figurehead. And

0:07:04.160 --> 0:07:07.320
<v Speaker 1>I honestly don't know the extent to which that accusation

0:07:07.520 --> 0:07:11.320
<v Speaker 1>could be true. It's a crazy world, Elon Musk's world

0:07:11.520 --> 0:07:15.320
<v Speaker 1>in particular. Well, if the judge orders X to get

0:07:15.320 --> 0:07:18.080
<v Speaker 1>shut down in Brazil, presumably the way that would work

0:07:18.440 --> 0:07:22.440
<v Speaker 1>is he would order Brazilian telecommunications companies to just block

0:07:22.600 --> 0:07:26.360
<v Speaker 1>all traffic to X within the country, because clearly the

0:07:26.440 --> 0:07:30.680
<v Speaker 1>judge can't force X to shut down operations in Brazil.

0:07:30.720 --> 0:07:33.440
<v Speaker 1>I don't even know how X would do that to

0:07:33.520 --> 0:07:38.440
<v Speaker 1>begin with, but he could force the various telecommunications companies

0:07:38.920 --> 0:07:44.600
<v Speaker 1>to block traffic to X. However, people in Brazil could

0:07:44.600 --> 0:07:48.239
<v Speaker 1>potentially still get to X by using a VPN service

0:07:48.280 --> 0:07:52.120
<v Speaker 1>that was based outside of the country. Anyway, X and

0:07:52.320 --> 0:07:56.800
<v Speaker 1>Starlink have both accused the judge of breaking Brazilian law

0:07:56.960 --> 0:07:59.920
<v Speaker 1>and say they will escalate legal proceedings within the country.

0:08:00.240 --> 0:08:02.920
<v Speaker 1>I have no idea how that works, because at least

0:08:02.960 --> 0:08:04.480
<v Speaker 1>here in the United States, once you get up to

0:08:04.520 --> 0:08:08.560
<v Speaker 1>the Supreme Court level, there's nowhere else to go. That's

0:08:08.920 --> 0:08:11.680
<v Speaker 1>that's the top. But it definitely seems to me like

0:08:12.320 --> 0:08:15.600
<v Speaker 1>the judge is going a little judge dread over there.

0:08:16.200 --> 0:08:19.960
<v Speaker 1>So I'm sure there's a lot more complex issues at

0:08:20.040 --> 0:08:23.400
<v Speaker 1>play in this story. Maybe I'll do a full episode

0:08:23.440 --> 0:08:25.920
<v Speaker 1>about it in the future, because I think it does

0:08:25.960 --> 0:08:30.080
<v Speaker 1>require a nuanced approach to kind of understand everything that's

0:08:30.160 --> 0:08:32.560
<v Speaker 1>going on. I'm sure it's not a black and white

0:08:32.920 --> 0:08:37.040
<v Speaker 1>situation for either side, But I don't know that freezing

0:08:37.080 --> 0:08:41.439
<v Speaker 1>of assets for starlink, it just strikes me as like,

0:08:41.600 --> 0:08:44.840
<v Speaker 1>how could there be a legal basis for that. I

0:08:44.880 --> 0:08:48.120
<v Speaker 1>guess if you argue that there was like a single

0:08:48.200 --> 0:08:52.640
<v Speaker 1>parent company and all these other companies were underneath that,

0:08:52.960 --> 0:08:55.440
<v Speaker 1>maybe then, but I don't think that's how the corporate

0:08:55.480 --> 0:09:00.160
<v Speaker 1>structure works between SpaceX and X apart from the fact

0:09:00.200 --> 0:09:03.480
<v Speaker 1>that they share Elon Musk's you know, obsession with the

0:09:03.600 --> 0:09:08.480
<v Speaker 1>letter X. Meanwhile, over here in the United States, X,

0:09:08.920 --> 0:09:12.400
<v Speaker 1>formerly known as Twitter, was kind of a caught out

0:09:12.600 --> 0:09:16.560
<v Speaker 1>when it marked links to an NPR news story as

0:09:16.640 --> 0:09:22.000
<v Speaker 1>being unsafe. So, yeah, X will not block accounts in

0:09:22.000 --> 0:09:24.840
<v Speaker 1>Brazil because that's a free speech issue, but here in

0:09:24.840 --> 0:09:28.439
<v Speaker 1>the US, it will label NPR stories as being unsafe.

0:09:28.800 --> 0:09:30.920
<v Speaker 1>So if you try to find out what the deal

0:09:31.040 --> 0:09:35.719
<v Speaker 1>is between Donald Trump's staff, campaign staff and an employee

0:09:35.720 --> 0:09:38.880
<v Speaker 1>of Arlington National Cemetery by following a link to an

0:09:38.960 --> 0:09:41.600
<v Speaker 1>NPR story on the matter, then you're told, hey, you

0:09:41.640 --> 0:09:43.760
<v Speaker 1>don't want to do that. This is taking you to

0:09:43.840 --> 0:09:47.320
<v Speaker 1>a bad place. The unsafe marker is typically something that

0:09:47.360 --> 0:09:50.960
<v Speaker 1>pops up if the link is to a site that's

0:09:51.080 --> 0:09:54.600
<v Speaker 1>known to host like militious software or sometimes things like

0:09:54.640 --> 0:10:01.280
<v Speaker 1>outright misinformation. Now, NPR might occasionally play some truly terrible

0:10:01.400 --> 0:10:04.079
<v Speaker 1>jazz on the radio, but I wouldn't go so far

0:10:04.120 --> 0:10:07.440
<v Speaker 1>as to call it malicious. The warning was in the

0:10:07.480 --> 0:10:09.840
<v Speaker 1>form of a pop up as well. It wasn't just

0:10:09.960 --> 0:10:12.920
<v Speaker 1>like a little label. If you clicked on the link,

0:10:12.920 --> 0:10:15.400
<v Speaker 1>you would get a pop up and it would say

0:10:16.080 --> 0:10:19.200
<v Speaker 1>that this link might be unsafe, and then there'd be

0:10:19.240 --> 0:10:21.440
<v Speaker 1>some text, and underneath that would be a big old

0:10:21.480 --> 0:10:23.760
<v Speaker 1>blue button that if you clicked on, it would just

0:10:23.760 --> 0:10:26.720
<v Speaker 1>take you right back to X, so it would, you know,

0:10:27.440 --> 0:10:31.240
<v Speaker 1>derail you from going to NPR. Beneath that big old

0:10:31.240 --> 0:10:34.880
<v Speaker 1>blue button is a smaller line of text with a

0:10:34.960 --> 0:10:38.319
<v Speaker 1>hyperlink that would let you continue on to read the

0:10:38.480 --> 0:10:43.240
<v Speaker 1>news story. So that is kind of crazy right now.

0:10:43.280 --> 0:10:47.120
<v Speaker 1>This could just be a simple mistake, but Musk has

0:10:47.160 --> 0:10:52.559
<v Speaker 1>already shown contempt for NPR because previously he labeled NPR

0:10:52.720 --> 0:10:58.160
<v Speaker 1>as a state affiliated media outlet. Typically that label indicates

0:10:58.360 --> 0:11:02.920
<v Speaker 1>a media company that is controlled by a governmental body,

0:11:03.320 --> 0:11:06.760
<v Speaker 1>like it's a propaganda arm. In other words, that is

0:11:06.880 --> 0:11:10.440
<v Speaker 1>not what NPR is. NBR receives a little bit of

0:11:10.440 --> 0:11:13.520
<v Speaker 1>federal funding, but only a tiny little bit. Most of

0:11:13.559 --> 0:11:19.520
<v Speaker 1>its funding does not come from federal sources, so and

0:11:19.559 --> 0:11:22.920
<v Speaker 1>there is no federal oversight or control of what goes

0:11:22.960 --> 0:11:27.000
<v Speaker 1>out over NPR. So this was a very misleading label

0:11:27.360 --> 0:11:30.880
<v Speaker 1>that Musk applied to NPR. Following that NPR chose to

0:11:31.040 --> 0:11:36.079
<v Speaker 1>leave X. So, you know, Musk has also over the

0:11:36.160 --> 0:11:40.680
<v Speaker 1>last few years been promoting more right leaning ideologies and

0:11:40.720 --> 0:11:45.320
<v Speaker 1>personalities on X, so I think it would be very

0:11:45.360 --> 0:11:48.160
<v Speaker 1>easy to view this and see it as a purposeful

0:11:48.240 --> 0:11:53.440
<v Speaker 1>attempt to discourage X users from going to NPR to

0:11:53.480 --> 0:11:58.360
<v Speaker 1>read up about this incident that happened at Arlington National Cemetery. However,

0:11:59.200 --> 0:12:03.000
<v Speaker 1>X state that the labeling was actually a false positive,

0:12:03.320 --> 0:12:06.680
<v Speaker 1>that this was not intentional, it was an honest mistake.

0:12:07.360 --> 0:12:10.360
<v Speaker 1>Maybe that's true, Like, it's easy for me to believe

0:12:10.400 --> 0:12:13.800
<v Speaker 1>that it was an intentional move to try and dissuade

0:12:13.840 --> 0:12:17.719
<v Speaker 1>people from reading up about what happened at Arlington National Cemetery.

0:12:18.160 --> 0:12:21.160
<v Speaker 1>But it's also very much true that over the last

0:12:21.800 --> 0:12:27.839
<v Speaker 1>year X has has eliminated so many people from the

0:12:28.360 --> 0:12:32.559
<v Speaker 1>company payroll that mistakes like this could easily happen simply

0:12:32.559 --> 0:12:35.000
<v Speaker 1>because they don't have the people to make sure it

0:12:35.080 --> 0:12:38.960
<v Speaker 1>doesn't happen. So either version could be true. Okay, so

0:12:39.320 --> 0:12:43.960
<v Speaker 1>we've got stories about X and Starlink. What about Tesla, Well,

0:12:44.000 --> 0:12:47.520
<v Speaker 1>there's more bad news on that, So Tesla, of course

0:12:47.679 --> 0:12:53.280
<v Speaker 1>yet another elon Musk company, and Christian Agatti of autoevolution

0:12:53.480 --> 0:12:58.439
<v Speaker 1>dot Com has an article titled third documented Tesla cybertruck

0:12:58.480 --> 0:13:03.680
<v Speaker 1>fire in less than a month raises questions woof so

0:13:04.280 --> 0:13:07.400
<v Speaker 1>a gad points out that in the marketing push for

0:13:07.480 --> 0:13:11.920
<v Speaker 1>cyber truck, Tesla was really stressing how the cyber truck

0:13:11.960 --> 0:13:15.600
<v Speaker 1>is a resilient vehicle right now. Granted, in the midst

0:13:15.640 --> 0:13:19.679
<v Speaker 1>of trying to say the cyber truck could withstand tons

0:13:19.720 --> 0:13:23.080
<v Speaker 1>of abuse, they accidentally broke some of the cyber truck's

0:13:23.120 --> 0:13:25.520
<v Speaker 1>windows while trying to show how tough they are. That

0:13:25.600 --> 0:13:30.000
<v Speaker 1>was a whoopsie, but anyway, the most recent of these

0:13:30.120 --> 0:13:33.760
<v Speaker 1>fires happened after an accident in which a cyber truck

0:13:33.880 --> 0:13:38.480
<v Speaker 1>driver hit a fire hydrant. My guess is that then

0:13:38.679 --> 0:13:42.719
<v Speaker 1>caused the battery inside the cyber truck to experience a

0:13:42.760 --> 0:13:47.000
<v Speaker 1>short where there was damage to the battery, and that

0:13:47.520 --> 0:13:51.240
<v Speaker 1>that created a short circuit that led to overheating and

0:13:51.240 --> 0:13:54.679
<v Speaker 1>then fire. That's my guess. I don't know for sure

0:13:54.760 --> 0:13:57.600
<v Speaker 1>that that is what happened. There has yet to have

0:13:57.679 --> 0:14:00.559
<v Speaker 1>been an investigation, or at least results of an investigation

0:14:00.679 --> 0:14:05.320
<v Speaker 1>shared publicly, so maybe it turns out something else caused

0:14:05.360 --> 0:14:09.440
<v Speaker 1>the fire. This happened in Harlingen, Texas. Don't know if

0:14:09.440 --> 0:14:10.839
<v Speaker 1>that's how you say it. There are a lot of

0:14:10.880 --> 0:14:13.920
<v Speaker 1>places in Texas where I think it's pronounced one way.

0:14:14.120 --> 0:14:17.720
<v Speaker 1>I am totally wrong. Earlier in the month, however, news

0:14:17.760 --> 0:14:22.200
<v Speaker 1>broke about a different incident that happened in Bayton area,

0:14:22.320 --> 0:14:24.440
<v Speaker 1>which is also in Texas, and In that one, a

0:14:24.480 --> 0:14:29.880
<v Speaker 1>cyber truck ran into like a concrete ditch trench or

0:14:29.920 --> 0:14:34.600
<v Speaker 1>something and caught fire. Tragically, there was a fatality, although

0:14:34.880 --> 0:14:38.480
<v Speaker 1>last I saw, they had not yet determined what actually

0:14:38.560 --> 0:14:42.600
<v Speaker 1>caused the death, whether it was a medical emergency, the

0:14:42.680 --> 0:14:46.840
<v Speaker 1>accident itself, or the fire. The third fire incident that

0:14:47.040 --> 0:14:49.640
<v Speaker 1>was one where Agady reported that a colleague of his

0:14:49.960 --> 0:14:53.640
<v Speaker 1>had actually found a burnt cyber truck listed on an

0:14:53.680 --> 0:14:57.160
<v Speaker 1>online auction site, and the description indicated that the vehicle

0:14:57.200 --> 0:15:00.480
<v Speaker 1>had been in a wreck and in fact subsequently caught fire,

0:15:00.760 --> 0:15:05.000
<v Speaker 1>and that this happened in Houston, Texas. So three accidents

0:15:05.040 --> 0:15:08.600
<v Speaker 1>resulting in fires, all three happening in Texas in the

0:15:08.640 --> 0:15:12.280
<v Speaker 1>span of a month. Now, I think it's too early

0:15:12.320 --> 0:15:15.200
<v Speaker 1>to draw any firm conclusions as to whether this means

0:15:15.200 --> 0:15:19.320
<v Speaker 1>the cyber truck actually is a flawed vehicle in that regard,

0:15:19.480 --> 0:15:22.440
<v Speaker 1>you know, like if the panels protecting the electric battery

0:15:22.480 --> 0:15:25.120
<v Speaker 1>aren't sufficient or whatever. I just don't know that that's

0:15:25.160 --> 0:15:28.040
<v Speaker 1>the case. It could be, but I think we need

0:15:28.080 --> 0:15:32.480
<v Speaker 1>to have an actual investigation to determine that. So I

0:15:32.480 --> 0:15:34.640
<v Speaker 1>think that's probably going to happen. I mean, with three

0:15:34.680 --> 0:15:37.240
<v Speaker 1>fires in a month, it seems to me like it's

0:15:37.280 --> 0:15:39.640
<v Speaker 1>at least warranted to take a look and see if

0:15:39.680 --> 0:15:43.720
<v Speaker 1>there are any common factors here at play. Maybe there aren't.

0:15:44.000 --> 0:15:48.080
<v Speaker 1>Maybe this is just coincidence and it all happened around

0:15:48.200 --> 0:15:52.920
<v Speaker 1>the same state and within the same month. That's possible,

0:15:53.240 --> 0:15:56.160
<v Speaker 1>so we need to investigate to find out. Okay, we

0:15:56.240 --> 0:15:58.280
<v Speaker 1>got lots more news to get through. Let's take a

0:15:58.360 --> 0:16:11.000
<v Speaker 1>quick break to thank our sponsors. We're back, and now

0:16:11.720 --> 0:16:16.960
<v Speaker 1>we're not done with Elon Musk news items just yet.

0:16:18.080 --> 0:16:23.960
<v Speaker 1>So over at SpaceX, there was a different kind of setback. Now,

0:16:24.000 --> 0:16:27.920
<v Speaker 1>while I'm talking about space and SpaceX, I should also

0:16:28.040 --> 0:16:32.080
<v Speaker 1>give a quick update and mention that we have this

0:16:32.240 --> 0:16:36.080
<v Speaker 1>ongoing issue of the two astronauts who went up on

0:16:36.200 --> 0:16:39.320
<v Speaker 1>the Boeing star Liner that then docked with the International

0:16:39.320 --> 0:16:43.240
<v Speaker 1>Space Station for a couple of months. Now. NASA was

0:16:43.320 --> 0:16:46.280
<v Speaker 1>hoping to find a way where they could return the

0:16:46.360 --> 0:16:50.840
<v Speaker 1>astronauts to Earth aboard the star Liner spacecraft. That was

0:16:50.880 --> 0:16:55.360
<v Speaker 1>something that Boeing was saying would be within acceptable risk parameters,

0:16:55.640 --> 0:16:59.560
<v Speaker 1>but NASA engineers ultimately disagreed with that. So the official

0:16:59.560 --> 0:17:02.360
<v Speaker 1>decision is that the Starliner is going to return to

0:17:02.440 --> 0:17:06.280
<v Speaker 1>Earth empty and the two astronauts will return home early

0:17:06.400 --> 0:17:11.520
<v Speaker 1>next year aboard a SpaceX Dragon capsule. Now, the SpaceX

0:17:11.560 --> 0:17:14.000
<v Speaker 1>story I wanted to touch on for this week is

0:17:14.080 --> 0:17:17.760
<v Speaker 1>that on Wednesday of this week, a Falcon nine first

0:17:17.800 --> 0:17:20.840
<v Speaker 1>stage booster had a big ol' whoopsie when it returned

0:17:21.160 --> 0:17:24.320
<v Speaker 1>to land on an ocean platform. Now, as I'm sure

0:17:24.320 --> 0:17:28.119
<v Speaker 1>you're all aware, one of the big draws for SpaceX's

0:17:28.200 --> 0:17:33.119
<v Speaker 1>launch vehicles is that they are reusable. This cuts way

0:17:33.240 --> 0:17:35.760
<v Speaker 1>down on the cost of launch, which is a huge

0:17:35.840 --> 0:17:40.400
<v Speaker 1>limiting factor for space The first stage booster landed on

0:17:40.440 --> 0:17:44.080
<v Speaker 1>this ocean platform, but then shortly thereafter it fell over

0:17:44.160 --> 0:17:48.160
<v Speaker 1>and it burst into flames. Fortunately, there were no reports

0:17:48.240 --> 0:17:50.720
<v Speaker 1>of any injuries or anything like that. There were no

0:17:50.760 --> 0:17:55.640
<v Speaker 1>reports of any public damage from this particular incident. However,

0:17:55.760 --> 0:18:00.800
<v Speaker 1>the FAA has grounded the Falcon nine launch vehicles. SpaceX

0:18:00.840 --> 0:18:04.879
<v Speaker 1>can investigate the incident and then share its findings and

0:18:04.920 --> 0:18:07.600
<v Speaker 1>then after any corrective actions have been ordered as a

0:18:07.600 --> 0:18:12.560
<v Speaker 1>result of that investigation. That means no SpaceX launches until

0:18:12.600 --> 0:18:16.920
<v Speaker 1>the FAA lifts that order. And that also means there

0:18:17.080 --> 0:18:19.760
<v Speaker 1>was supposed to be a launch I think today actually

0:18:20.320 --> 0:18:23.800
<v Speaker 1>that was going to deliver more Starlink satellites into orbit,

0:18:24.000 --> 0:18:26.760
<v Speaker 1>and that has since been delayed. Actually, the booster that

0:18:26.960 --> 0:18:29.680
<v Speaker 1>burst into flames, that was part of a mission of

0:18:29.920 --> 0:18:32.760
<v Speaker 1>sending more Starlink satellites into orbit as well. But the

0:18:32.840 --> 0:18:35.400
<v Speaker 1>second one that was supposed to happen now has been

0:18:35.480 --> 0:18:40.600
<v Speaker 1>postponed indefinitely until the ban has been lifted once they

0:18:40.880 --> 0:18:45.119
<v Speaker 1>figure out exactly what happened with this accident. No telling

0:18:45.200 --> 0:18:48.360
<v Speaker 1>yet if this is going to impact other upcoming launches.

0:18:48.400 --> 0:18:52.040
<v Speaker 1>There are a couple that are coming up before too long,

0:18:52.119 --> 0:18:54.120
<v Speaker 1>But it may be that this whole thing is resolved

0:18:54.280 --> 0:18:56.680
<v Speaker 1>relatively quickly. We'll just have to keep an eye out.

0:18:57.240 --> 0:19:00.600
<v Speaker 1>The hits keep on coming though. From us. In Memphis, Tennessee,

0:19:00.760 --> 0:19:05.800
<v Speaker 1>the Southern Environmental Law Center alleges that Musk's AI company,

0:19:06.000 --> 0:19:11.919
<v Speaker 1>which of course is called Xai, is using natural gas

0:19:11.920 --> 0:19:16.560
<v Speaker 1>burning turbines to power the AI facilities. We all know

0:19:17.240 --> 0:19:21.400
<v Speaker 1>that these AI data centers require a huge amount of

0:19:21.560 --> 0:19:25.760
<v Speaker 1>electricity in order to work. So one of the things

0:19:25.800 --> 0:19:29.080
<v Speaker 1>that companies that are using these kinds of power sources

0:19:29.080 --> 0:19:32.400
<v Speaker 1>that like natural gas burning turbines, one of the things

0:19:32.440 --> 0:19:35.760
<v Speaker 1>they're supposed to do is file a whole bunch of

0:19:35.800 --> 0:19:39.640
<v Speaker 1>paperwork to get the right permits to actually operate that

0:19:39.760 --> 0:19:44.480
<v Speaker 1>kind of machinery, and according to the Southern Environmental Law Center,

0:19:44.880 --> 0:19:49.600
<v Speaker 1>they say that there's no record that Xai actually followed

0:19:49.640 --> 0:19:53.520
<v Speaker 1>that process in Tennessee. So in an open letter, the

0:19:53.640 --> 0:19:58.280
<v Speaker 1>organization claims that Xai has twenty gas turbines operating without

0:19:58.320 --> 0:20:01.480
<v Speaker 1>first applying for those permits and has called upon the

0:20:01.520 --> 0:20:05.840
<v Speaker 1>local health department to investigate Xai to determine if, in fact,

0:20:06.000 --> 0:20:08.520
<v Speaker 1>that is what is going on now. I can't say

0:20:08.560 --> 0:20:11.399
<v Speaker 1>I would be surprised to hear that a Musk backed

0:20:11.440 --> 0:20:15.679
<v Speaker 1>company jumped into a situation like that without proper paperwork,

0:20:15.840 --> 0:20:18.840
<v Speaker 1>but I have to be fair. That is my bias talking,

0:20:19.160 --> 0:20:22.640
<v Speaker 1>Like just because Musk has proven that, you know, he's

0:20:22.960 --> 0:20:24.959
<v Speaker 1>done that kind of thing before, it doesn't mean that

0:20:24.960 --> 0:20:28.240
<v Speaker 1>that's what's happened this time. It could all be totally

0:20:29.240 --> 0:20:32.240
<v Speaker 1>a misunderstanding, like maybe the paperwork has been filed and

0:20:32.280 --> 0:20:34.160
<v Speaker 1>they just didn't find record of it. But they are

0:20:34.160 --> 0:20:37.080
<v Speaker 1>calling for an investigation to find out if the company

0:20:37.119 --> 0:20:39.480
<v Speaker 1>in fact followed the right process in order to operate

0:20:39.480 --> 0:20:42.280
<v Speaker 1>this way, because the concern here is that the operation

0:20:42.440 --> 0:20:46.919
<v Speaker 1>of these twenty gas turbines could contribute to pollution in

0:20:46.960 --> 0:20:51.800
<v Speaker 1>the Memphis area. Meanwhile, the Center for Countering Digital Hate

0:20:51.960 --> 0:20:54.959
<v Speaker 1>released the results of a study focusing on the GROCK

0:20:55.280 --> 0:21:00.800
<v Speaker 1>AI assistant that's the AI assistant connected to YEP, formerly

0:21:00.840 --> 0:21:04.360
<v Speaker 1>known as Twitter. YadA YadA, YadA so. This study concluded

0:21:04.400 --> 0:21:08.280
<v Speaker 1>that GROC lacks sufficient guardrails to prevent people from using

0:21:08.320 --> 0:21:14.240
<v Speaker 1>it to generate misleading images of real public personas, including politicians.

0:21:14.880 --> 0:21:17.040
<v Speaker 1>The study said that the tool was able to create

0:21:17.080 --> 0:21:20.199
<v Speaker 1>a convincing fake image of Donald Trump appearing to be

0:21:20.480 --> 0:21:23.960
<v Speaker 1>very sick in a hospital bed, and another of Kamala

0:21:24.040 --> 0:21:28.160
<v Speaker 1>Harris appearing to do drugs. The researcher said they tried

0:21:28.359 --> 0:21:31.800
<v Speaker 1>various methods to generate these images that range from just

0:21:31.880 --> 0:21:35.159
<v Speaker 1>blatantly giving a text prompt asking for what they wanted

0:21:35.200 --> 0:21:39.520
<v Speaker 1>to see, to taking a more circumspect route where they

0:21:39.640 --> 0:21:43.520
<v Speaker 1>used descriptive language to get the same effect, to get

0:21:43.520 --> 0:21:47.080
<v Speaker 1>the same results they wanted without actually triggering any preventative

0:21:47.480 --> 0:21:51.400
<v Speaker 1>safety features that otherwise would stop that kind of request

0:21:51.440 --> 0:21:56.680
<v Speaker 1>from working. I find this particularly frustrating, not just because

0:21:57.080 --> 0:22:00.439
<v Speaker 1>of the disinformation aspect, which is clearly bad enough alone,

0:22:00.960 --> 0:22:05.159
<v Speaker 1>but also because Elon Musk like again, I don't like

0:22:05.240 --> 0:22:08.639
<v Speaker 1>the guy, but he has repeatedly sounded the alarm about

0:22:08.640 --> 0:22:12.000
<v Speaker 1>the dangers of AI, and I agree AI is potentially

0:22:12.119 --> 0:22:15.800
<v Speaker 1>very dangerous if it's implemented poorly. And he has argued

0:22:15.800 --> 0:22:18.879
<v Speaker 1>that AI needs to be developed and deployed responsibly. I

0:22:18.960 --> 0:22:21.439
<v Speaker 1>agree with that too. I think that AI does need

0:22:21.520 --> 0:22:24.480
<v Speaker 1>to be developed and deployed responsibly, and that there should

0:22:24.520 --> 0:22:28.040
<v Speaker 1>be plentiful safety measures in place to prevent AI from

0:22:28.080 --> 0:22:31.000
<v Speaker 1>causing harm. I agree with that. All of these things

0:22:31.040 --> 0:22:34.399
<v Speaker 1>I agree with, And yet here is an AI tool

0:22:34.560 --> 0:22:38.960
<v Speaker 1>on one of Elon Musk's own platforms that clearly fails

0:22:39.000 --> 0:22:42.560
<v Speaker 1>to follow any of those directives. But then you could

0:22:42.600 --> 0:22:45.800
<v Speaker 1>also make the same argument that the AI found in

0:22:45.880 --> 0:22:49.440
<v Speaker 1>Tesla vehicles has at least appeared to be less reliable

0:22:49.480 --> 0:22:53.199
<v Speaker 1>than the company tends to market to potential customers. So

0:22:54.040 --> 0:22:57.760
<v Speaker 1>there's that as well. There's also been a recent change

0:22:57.840 --> 0:23:01.680
<v Speaker 1>to Grock, the AI assistant on it, apparently in response

0:23:01.720 --> 0:23:04.800
<v Speaker 1>to a complaint letter sent to the company from the

0:23:04.880 --> 0:23:08.639
<v Speaker 1>offices of five different Secretaries of State, so those states

0:23:08.680 --> 0:23:14.240
<v Speaker 1>would be Minnesota, New Mexico, Washington, Pennsylvania, and Michigan. The

0:23:14.320 --> 0:23:17.919
<v Speaker 1>offices were complaining that Groc was giving incorrect information in

0:23:17.960 --> 0:23:21.960
<v Speaker 1>response to prompts asking about ballot deadlines in those states.

0:23:22.240 --> 0:23:26.560
<v Speaker 1>So essentially this is related to election information, and GROC

0:23:26.600 --> 0:23:31.280
<v Speaker 1>apparently was just giving incorrect responses when people were asking

0:23:31.600 --> 0:23:37.159
<v Speaker 1>these basic questions about ballots. So now rather than just

0:23:37.280 --> 0:23:40.440
<v Speaker 1>giving an incorrect answer, GROC will respond to those kinds

0:23:40.440 --> 0:23:44.159
<v Speaker 1>of requests by urging the visitor to go to vote

0:23:44.240 --> 0:23:49.520
<v Speaker 1>dot gov for the actual answer, So that I think

0:23:49.680 --> 0:23:54.800
<v Speaker 1>is a market improvement. Tom David S. Pumpkins Hanks has

0:23:54.920 --> 0:23:57.879
<v Speaker 1>a message for all of y'all out there, and that

0:23:57.920 --> 0:24:01.919
<v Speaker 1>message is to not trust drug advertisements that seem to

0:24:01.960 --> 0:24:06.920
<v Speaker 1>have Tom Hanks voicing the ad copy. So specifically, on Instagram,

0:24:07.000 --> 0:24:11.280
<v Speaker 1>Hanks posted quote, there are multiple ads over the internet

0:24:11.440 --> 0:24:16.240
<v Speaker 1>falsely using my name, likeness, and voice promoting miracle cures

0:24:16.320 --> 0:24:20.520
<v Speaker 1>and wonder drugs. These ads have been created without my consent,

0:24:21.040 --> 0:24:25.359
<v Speaker 1>fraudulently and through AI. I have nothing to do with

0:24:25.440 --> 0:24:29.760
<v Speaker 1>these posts, or the productions and treatments, or the spokespeople

0:24:29.880 --> 0:24:33.879
<v Speaker 1>touting these cures. I have Type two diabetes and I

0:24:33.920 --> 0:24:37.560
<v Speaker 1>only work with my board certified doctor regarding my treatment.

0:24:38.240 --> 0:24:42.560
<v Speaker 1>Do not be fooled, Do not be swindled, Do not

0:24:42.840 --> 0:24:46.920
<v Speaker 1>lose your hard earned money. End quote. Now, if all

0:24:46.960 --> 0:24:49.600
<v Speaker 1>this sounds a little familiar, that might be because of

0:24:49.600 --> 0:24:53.560
<v Speaker 1>something that happened around the same time last year, where

0:24:53.600 --> 0:24:57.240
<v Speaker 1>there was this ad video going around with an AI

0:24:57.440 --> 0:25:00.399
<v Speaker 1>generated deep fake version of Tom Hanks prom voting a

0:25:00.520 --> 0:25:06.359
<v Speaker 1>dental plan Lisa needs braces dental plan. Sorry, sorry, sorry.

0:25:06.400 --> 0:25:09.160
<v Speaker 1>Some episodes of The Simpsons are kind of hardwired into

0:25:09.160 --> 0:25:11.720
<v Speaker 1>my brain and I just go into like a feedback loop.

0:25:12.080 --> 0:25:14.840
<v Speaker 1>I have to admit that when I was thinking about

0:25:14.880 --> 0:25:18.200
<v Speaker 1>how deep fakes were going to spread beyond the creation

0:25:18.359 --> 0:25:21.800
<v Speaker 1>of pornographic images and video, which is its own thing

0:25:21.960 --> 0:25:25.240
<v Speaker 1>and it's horrifying and terrible, when I was thinking about

0:25:25.280 --> 0:25:27.119
<v Speaker 1>how it was going to branch out beyond that, I

0:25:27.280 --> 0:25:29.639
<v Speaker 1>had not clocked Tom Hanks as being one of the

0:25:29.680 --> 0:25:33.920
<v Speaker 1>first high profile victims. But here we are. Bloomberg reported

0:25:34.200 --> 0:25:37.960
<v Speaker 1>that Apple is cutting one hundred positions in its digital

0:25:38.080 --> 0:25:41.600
<v Speaker 1>services department, and that the affected employees will have two

0:25:41.680 --> 0:25:44.960
<v Speaker 1>months to find another position within the company or else

0:25:45.000 --> 0:25:48.960
<v Speaker 1>be struck from the roster entirely. So apparently the main

0:25:49.000 --> 0:25:54.840
<v Speaker 1>group affected is the books team, which, as Samuel Aksin

0:25:54.920 --> 0:25:58.680
<v Speaker 1>of Ours Technica has pointed out, has no subscription service

0:25:58.960 --> 0:26:03.600
<v Speaker 1>attached to that particular product. So it sounds like Apple

0:26:03.680 --> 0:26:07.160
<v Speaker 1>really wants to redirect energy towards services that more directly

0:26:07.200 --> 0:26:10.920
<v Speaker 1>impact revenue. Which I mean, you can understand that from

0:26:10.960 --> 0:26:14.000
<v Speaker 1>a business perspective, right, Like, why would you focus on

0:26:14.119 --> 0:26:21.040
<v Speaker 1>things that don't impact revenue? Maybe they impact the value

0:26:21.200 --> 0:26:23.480
<v Speaker 1>or the perception of value, which you could argue is

0:26:23.960 --> 0:26:29.000
<v Speaker 1>a reasonable reason to keep it going. But yeah, most

0:26:29.000 --> 0:26:31.600
<v Speaker 1>companies are going to say revenue is way more important.

0:26:32.080 --> 0:26:35.239
<v Speaker 1>So it appears that Apple is one of those. I

0:26:35.280 --> 0:26:38.480
<v Speaker 1>hope anyone who has been affected by this will find

0:26:38.560 --> 0:26:41.960
<v Speaker 1>a new position with a great team as soon as

0:26:42.119 --> 0:26:45.920
<v Speaker 1>is possible. It's been a pretty long time since I've

0:26:45.920 --> 0:26:49.280
<v Speaker 1>talked about Uber getting hit with fines, but this next

0:26:49.320 --> 0:26:52.520
<v Speaker 1>story is quite a doozy. In fact, according to ngadget's

0:26:52.640 --> 0:26:56.360
<v Speaker 1>Sarah Fielding, it would be the largest fine Uber has

0:26:56.400 --> 0:27:01.280
<v Speaker 1>ever faced, a whopping two hundred and ninety million Euro penalty.

0:27:01.520 --> 0:27:04.240
<v Speaker 1>That's the equivalent of around three hundred and twenty four

0:27:04.359 --> 0:27:09.080
<v Speaker 1>million dollars. So what the heck happened? Well, this has

0:27:09.119 --> 0:27:13.760
<v Speaker 1>to do with the EU and GDPR. GDPR that's the

0:27:13.760 --> 0:27:16.480
<v Speaker 1>set of rules that are meant to protect EU citizens'

0:27:16.520 --> 0:27:20.200
<v Speaker 1>personal data. So one thing that companies are not supposed

0:27:20.240 --> 0:27:24.360
<v Speaker 1>to do under these rules is to send the personal

0:27:24.359 --> 0:27:29.960
<v Speaker 1>information belonging to EU citizens outside the EU itself unless

0:27:30.000 --> 0:27:34.000
<v Speaker 1>you're using appropriate measures to make sure you're protecting their information.

0:27:34.520 --> 0:27:36.679
<v Speaker 1>This is a thing that a lot of platforms have

0:27:36.760 --> 0:27:41.080
<v Speaker 1>run into where they were found to be transmitting information

0:27:41.359 --> 0:27:44.760
<v Speaker 1>to servers in the United States, but the information belonged

0:27:44.760 --> 0:27:48.640
<v Speaker 1>to EU citizens, and without those protections in place, these

0:27:48.640 --> 0:27:52.800
<v Speaker 1>companies can't guarantee the safety of that information. Because GDPR

0:27:52.920 --> 0:27:57.160
<v Speaker 1>is so focused on the safety of personal information, that's

0:27:57.200 --> 0:28:01.399
<v Speaker 1>a problem. So the Dutch Data Protection Authority or Dutch

0:28:01.600 --> 0:28:07.560
<v Speaker 1>DPA says that Uber really failed to protect information for

0:28:07.760 --> 0:28:11.920
<v Speaker 1>Uber drivers and that included stuff like their taxi licenses,

0:28:12.400 --> 0:28:16.680
<v Speaker 1>their identity documents and lots more other information. That Uber

0:28:16.840 --> 0:28:20.800
<v Speaker 1>transmitted this info overseas to Uber data servers in the

0:28:20.880 --> 0:28:25.040
<v Speaker 1>United States while not using any approved transferred tools that

0:28:25.080 --> 0:28:29.240
<v Speaker 1>are meant to ensure the safety of those data transfers.

0:28:29.560 --> 0:28:32.880
<v Speaker 1>The Dutch DPA said this failure to provide adequate protection

0:28:33.400 --> 0:28:36.800
<v Speaker 1>is a violation and that Uber subsequently has to pay up.

0:28:37.280 --> 0:28:39.840
<v Speaker 1>And it's notable here that as far as I can tell,

0:28:40.120 --> 0:28:43.600
<v Speaker 1>no unauthorized individuals ever got access to this information. This

0:28:43.680 --> 0:28:46.680
<v Speaker 1>isn't like a data breach or something, so it's not that,

0:28:47.040 --> 0:28:50.520
<v Speaker 1>you know, Uber failed to protect the info and someone

0:28:50.520 --> 0:28:53.200
<v Speaker 1>got hold of it. It's that Uber was not following

0:28:53.240 --> 0:28:57.200
<v Speaker 1>the approved process to make sure data was handled appropriately,

0:28:57.320 --> 0:29:01.440
<v Speaker 1>so arguably that personal information could have been intercepted or

0:29:01.480 --> 0:29:04.720
<v Speaker 1>exploited by other parties. And Uber reps have said that

0:29:04.800 --> 0:29:07.720
<v Speaker 1>the company will of course appeal the fine, so we'll

0:29:07.760 --> 0:29:10.880
<v Speaker 1>have to see where this develops from here. Okay, I've

0:29:10.880 --> 0:29:13.360
<v Speaker 1>got some more news stories to talk about. Before we

0:29:13.400 --> 0:29:25.160
<v Speaker 1>get to those, let's take another quick break. Okay, let's

0:29:25.200 --> 0:29:28.880
<v Speaker 1>wrap up some of our tech news this week over

0:29:28.960 --> 0:29:31.640
<v Speaker 1>on blue Sky, which, in case you're not familiar with

0:29:31.680 --> 0:29:36.479
<v Speaker 1>blue Sky, it's an alternative to Twitter, slash x, along

0:29:36.520 --> 0:29:41.440
<v Speaker 1>with other similar tools like Mastodon or threads. So blue

0:29:41.480 --> 0:29:45.080
<v Speaker 1>Sky has added some new anti toxicity features and I

0:29:45.120 --> 0:29:48.960
<v Speaker 1>think the features are interesting. I'm not sure that it's

0:29:49.000 --> 0:29:52.400
<v Speaker 1>the best approach, but they are interesting. It's hard to

0:29:52.480 --> 0:29:57.080
<v Speaker 1>determine how to best implement anti toxicity measures on a

0:29:57.120 --> 0:29:59.880
<v Speaker 1>platform that allows people to just join up. I mean,

0:30:00.440 --> 0:30:03.720
<v Speaker 1>as platforms get larger, they become more difficult to moderate,

0:30:04.000 --> 0:30:07.440
<v Speaker 1>assuming that you have a platform that's interested in moderation

0:30:07.520 --> 0:30:10.560
<v Speaker 1>in the first place. So yeah, I see also Telegram.

0:30:11.200 --> 0:30:13.760
<v Speaker 1>But the big one that I wanted to talk about

0:30:14.120 --> 0:30:18.440
<v Speaker 1>was that users are able now to remove their original

0:30:18.480 --> 0:30:22.120
<v Speaker 1>post if someone else quotes that post. So in other words,

0:30:22.160 --> 0:30:26.400
<v Speaker 1>let's say, let's say that you post something that says like,

0:30:27.240 --> 0:30:31.480
<v Speaker 1>I really enjoyed the Barbie movie, which is awesome. Honestly,

0:30:31.640 --> 0:30:34.080
<v Speaker 1>I enjoyed the Barbie movie. But let's say that I'm

0:30:34.120 --> 0:30:38.400
<v Speaker 1>not me. Let's say that I am the Evil Mirror

0:30:38.520 --> 0:30:42.560
<v Speaker 1>Universe version of me, and I've decided, because you have

0:30:42.640 --> 0:30:46.760
<v Speaker 1>claimed that you enjoyed the Barbie movie, you are deserving

0:30:47.120 --> 0:30:50.560
<v Speaker 1>of criticism and trolling and all that kind of stuff.

0:30:50.760 --> 0:30:55.560
<v Speaker 1>So I then quote your post, and I then put

0:30:55.640 --> 0:30:58.920
<v Speaker 1>some really nasty commentary underneath about how I think you're

0:30:59.120 --> 0:31:02.520
<v Speaker 1>a dumb dumb for liking a perfectly good movie. And

0:31:03.120 --> 0:31:08.959
<v Speaker 1>now you can actually take action on this, so before

0:31:09.240 --> 0:31:12.400
<v Speaker 1>you might just end up being flooded with like toxic notifications,

0:31:12.480 --> 0:31:15.840
<v Speaker 1>let's say that Evil Mirror Universe me has a lot

0:31:15.880 --> 0:31:18.840
<v Speaker 1>more notoriety and a lot more followers on Blue Sky.

0:31:19.200 --> 0:31:24.040
<v Speaker 1>So I post this negative takedown of your post and

0:31:24.840 --> 0:31:28.560
<v Speaker 1>everyone dogpiles on top of you. Now on Blue Sky,

0:31:28.720 --> 0:31:34.000
<v Speaker 1>you could go in and remove the quoted tweet from

0:31:34.040 --> 0:31:37.480
<v Speaker 1>my post. So you know, if my post is centered

0:31:37.560 --> 0:31:42.080
<v Speaker 1>around your earlier post, and you remove your earlier post

0:31:42.160 --> 0:31:45.680
<v Speaker 1>from mine, then all it's left is the commentary. If

0:31:45.720 --> 0:31:48.280
<v Speaker 1>that commentary is not specific, people don't even know who

0:31:48.360 --> 0:31:51.920
<v Speaker 1>I'm referring to as I rant about someone daring to

0:31:52.120 --> 0:31:56.400
<v Speaker 1>like the Barbie movie. So that is effective now, granted,

0:31:56.520 --> 0:32:00.800
<v Speaker 1>if in my narrative, if in my common Harry I

0:32:00.840 --> 0:32:06.080
<v Speaker 1>have also identified you, then removing your post from the

0:32:06.160 --> 0:32:10.480
<v Speaker 1>quotation doesn't really help that much because people can still

0:32:10.520 --> 0:32:13.080
<v Speaker 1>see who I'm talking about. Maybe they don't get a

0:32:13.200 --> 0:32:17.560
<v Speaker 1>link to your profile or whatever, but there's limited utility here.

0:32:17.960 --> 0:32:21.479
<v Speaker 1>But yeah, I think that that's generally a positive step.

0:32:21.960 --> 0:32:24.880
<v Speaker 1>I'm not sure that's the most effective one, but it

0:32:24.920 --> 0:32:27.560
<v Speaker 1>is meant to prevent instances of dog piling. So that

0:32:27.760 --> 0:32:31.800
<v Speaker 1>if someone takes your post and then, out of context,

0:32:31.840 --> 0:32:34.960
<v Speaker 1>tries to argue that you're a terrible person or whatever,

0:32:35.040 --> 0:32:39.200
<v Speaker 1>you can just remove the quotation part out of that post.

0:32:39.400 --> 0:32:42.600
<v Speaker 1>Now you can't touch anything else that's in that post, right, Like,

0:32:43.080 --> 0:32:47.480
<v Speaker 1>if in my description, I really drag you. You can't

0:32:47.480 --> 0:32:50.760
<v Speaker 1>go in and change my description, like you can't change

0:32:50.800 --> 0:32:54.520
<v Speaker 1>the commentary I have added. You can just remove the

0:32:54.640 --> 0:32:58.680
<v Speaker 1>quoted part, which I think makes sense, Like you shouldn't

0:32:58.760 --> 0:33:01.800
<v Speaker 1>have the ability to be able to change what someone's

0:33:01.840 --> 0:33:05.000
<v Speaker 1>post reads, because then it's just chaos. But I think

0:33:05.000 --> 0:33:08.080
<v Speaker 1>it is a good step. I just think it's tough,

0:33:08.160 --> 0:33:11.440
<v Speaker 1>like this is a hard problem to fix. Another similar

0:33:11.440 --> 0:33:14.240
<v Speaker 1>feature on blue Sky is that you can actually hide

0:33:14.320 --> 0:33:16.840
<v Speaker 1>replies to your posts. So let's say you post something

0:33:16.840 --> 0:33:18.920
<v Speaker 1>and no one's quoting you, but they are replying to you,

0:33:18.960 --> 0:33:21.280
<v Speaker 1>and some of them are being real nasty. You can

0:33:21.320 --> 0:33:25.240
<v Speaker 1>actually hide those replies, and you can choose to hide

0:33:25.240 --> 0:33:28.280
<v Speaker 1>it just from yourself, which is like blocking or muting someone,

0:33:28.840 --> 0:33:32.400
<v Speaker 1>or you can choose to hide that reply from everybody

0:33:32.880 --> 0:33:35.440
<v Speaker 1>so no one can see that this person is just

0:33:35.520 --> 0:33:39.680
<v Speaker 1>being nasty towards you. So when someone's being hateful, you

0:33:39.720 --> 0:33:42.280
<v Speaker 1>can hide so that no one sees it. Or maybe

0:33:42.360 --> 0:33:44.600
<v Speaker 1>you just shield yourself and you let it stand for

0:33:44.680 --> 0:33:48.120
<v Speaker 1>everybody else. Blue Sky says it will continue to introduce

0:33:48.160 --> 0:33:51.720
<v Speaker 1>features to make the platform a more safe and welcoming place.

0:33:52.480 --> 0:33:55.680
<v Speaker 1>This I think is in stark contrast to X like

0:33:55.880 --> 0:34:00.479
<v Speaker 1>over at X. You don't really see a Musk and

0:34:00.560 --> 0:34:04.840
<v Speaker 1>company putting in measures to make X a safer and

0:34:04.920 --> 0:34:08.680
<v Speaker 1>more welcoming place. You do occasionally see stories like the

0:34:08.680 --> 0:34:12.880
<v Speaker 1>one I mentioned about NPR, where it appears that whenever

0:34:12.920 --> 0:34:17.560
<v Speaker 1>they do enter into content moderation, it's to suppress any

0:34:17.800 --> 0:34:21.000
<v Speaker 1>any kind of viewpoint that doesn't go into alignment with

0:34:21.000 --> 0:34:24.760
<v Speaker 1>what Musk believes. That at least that's the appearance. Whether

0:34:24.800 --> 0:34:26.920
<v Speaker 1>that's what's really going on or not, I don't know.

0:34:27.480 --> 0:34:30.080
<v Speaker 1>Like I said, it could really be that there was

0:34:30.200 --> 0:34:33.479
<v Speaker 1>just an error in a false positive, But yeah, Blue

0:34:33.480 --> 0:34:36.560
<v Speaker 1>Sky strikes me as taking kind of like a maybe

0:34:36.560 --> 0:34:39.920
<v Speaker 1>not a total one to eighty approach from X, but

0:34:40.080 --> 0:34:45.520
<v Speaker 1>a substantial deviation from that approach. The Motion Picture Association

0:34:45.640 --> 0:34:48.920
<v Speaker 1>announced this week that through partnering with authorities in Vietnam,

0:34:49.280 --> 0:34:52.960
<v Speaker 1>they have shut down an online media piracy ring that

0:34:53.040 --> 0:34:57.800
<v Speaker 1>had accumulated billions of visits between them from January twenty

0:34:57.880 --> 0:35:01.560
<v Speaker 1>twenty three up to June twenty twenty four. So sort

0:35:01.600 --> 0:35:06.359
<v Speaker 1>of the hub of this, like the central crux was

0:35:06.840 --> 0:35:11.480
<v Speaker 1>F Movies, and under F Movies, there were several piracy

0:35:11.520 --> 0:35:15.760
<v Speaker 1>sites that were in operation. They included any Wave Flicks

0:35:15.880 --> 0:35:20.720
<v Speaker 1>Tours my Flixer and others like that. So the MPa

0:35:20.960 --> 0:35:25.480
<v Speaker 1>referred to f Movies as the mothership of piracy and

0:35:25.600 --> 0:35:29.800
<v Speaker 1>that the takedown had a cascading effect across these various

0:35:30.080 --> 0:35:34.760
<v Speaker 1>piracy sites which have been hosting media illegally for years

0:35:34.920 --> 0:35:39.320
<v Speaker 1>and distributing it to whomever goes there. Various media companies

0:35:39.360 --> 0:35:44.720
<v Speaker 1>and organizations that represent media companies have spent decades fighting

0:35:44.800 --> 0:35:50.400
<v Speaker 1>online piracy, often in ways that end up being outlandishly disproportionate.

0:35:51.000 --> 0:35:53.719
<v Speaker 1>Like you might remember, I mean I remember because I

0:35:53.719 --> 0:35:58.320
<v Speaker 1>remember the nineties when the RIAA really began to shake

0:35:58.480 --> 0:36:02.600
<v Speaker 1>down like service pro like Verizon to hand over the

0:36:02.680 --> 0:36:09.520
<v Speaker 1>identities of customers that the RIAA suspected were guilty of piracy.

0:36:10.520 --> 0:36:15.200
<v Speaker 1>There are people who were hit with truly ridiculous, astronomic

0:36:15.400 --> 0:36:20.920
<v Speaker 1>fines for piracy. And then there's the various issue of

0:36:21.280 --> 0:36:25.520
<v Speaker 1>media organizations arguing that piracy equates to loss of revenue,

0:36:26.040 --> 0:36:29.840
<v Speaker 1>like if you watch a movie illegally, if you download

0:36:29.840 --> 0:36:33.680
<v Speaker 1>a music track illegally, that means we lost revenue. A

0:36:33.760 --> 0:36:37.600
<v Speaker 1>lot of entities, including the United States Government Accountability Office,

0:36:37.719 --> 0:36:42.000
<v Speaker 1>say that argument doesn't hold water. At best, it is misleading.

0:36:42.040 --> 0:36:46.760
<v Speaker 1>At worst, it is wrong, and that's because it's impossible

0:36:47.200 --> 0:36:50.160
<v Speaker 1>to determine if someone who pirated a piece of media

0:36:50.680 --> 0:36:54.279
<v Speaker 1>otherwise would have purchased that piece of media legally. Let's

0:36:54.280 --> 0:36:57.840
<v Speaker 1>say that piracy was impossible somehow, Like we're in a

0:36:57.880 --> 0:37:01.279
<v Speaker 1>world where it's just impossible to pirate stuff. Someone who

0:37:01.320 --> 0:37:03.880
<v Speaker 1>would have pirated things, you can't say that they will,

0:37:04.080 --> 0:37:06.200
<v Speaker 1>though otherwise go out and buy it. Maybe they just

0:37:06.239 --> 0:37:10.279
<v Speaker 1>go without. You can't make the argument that a downloaded

0:37:10.680 --> 0:37:14.480
<v Speaker 1>piece of media equates to loss of revenue, So a

0:37:14.560 --> 0:37:19.160
<v Speaker 1>lost sale isn't the same thing as stolen money. Like

0:37:19.200 --> 0:37:21.799
<v Speaker 1>if I walk up to a movie theater and I

0:37:21.880 --> 0:37:24.960
<v Speaker 1>look at the list of films that are available, and

0:37:25.000 --> 0:37:27.600
<v Speaker 1>I ultimately decide, eh, I don't feel like watching any

0:37:27.680 --> 0:37:30.719
<v Speaker 1>of these, and I walk off. I didn't steal from

0:37:30.760 --> 0:37:35.000
<v Speaker 1>any of the movie companies. So yeah, I think piracy

0:37:35.120 --> 0:37:37.560
<v Speaker 1>is bad. Just to be clear, I do think piracy

0:37:37.600 --> 0:37:39.359
<v Speaker 1>is bad. I do not think you should do it.

0:37:39.800 --> 0:37:44.239
<v Speaker 1>Don't be a pirate. However, I think media companies that

0:37:44.320 --> 0:37:49.480
<v Speaker 1>take the nuclear option based on unsupportable arguments are bad too.

0:37:50.560 --> 0:37:53.640
<v Speaker 1>No one's in the right in that particular situation. But

0:37:53.680 --> 0:37:56.600
<v Speaker 1>you can read more about this particular story about the

0:37:56.640 --> 0:38:01.160
<v Speaker 1>Motion Picture Association and f movies both On Technica and

0:38:01.200 --> 0:38:04.080
<v Speaker 1>The Verge. Both sites have some great articles about this

0:38:04.600 --> 0:38:07.960
<v Speaker 1>recent Hollywood war against online piracy. I recommend you go

0:38:08.040 --> 0:38:11.799
<v Speaker 1>check those out now. For other recommended reading this week,

0:38:11.840 --> 0:38:13.640
<v Speaker 1>I've got a couple of different pieces I want to

0:38:13.680 --> 0:38:16.600
<v Speaker 1>talk about. First up is a paper that was published

0:38:16.760 --> 0:38:20.680
<v Speaker 1>in Nature, the science journal Nature. This paper is by

0:38:20.920 --> 0:38:28.600
<v Speaker 1>Valentine Hoffmann, Pratyusha rha Kaluri, Dan Jorowski, and Sharise King.

0:38:28.719 --> 0:38:33.680
<v Speaker 1>It is titled AI generates covertly racist decisions about people

0:38:33.760 --> 0:38:37.440
<v Speaker 1>based on their dialect. So, as you might suspect, this

0:38:37.520 --> 0:38:41.600
<v Speaker 1>paper investigates the issue of bias found within AI models,

0:38:41.760 --> 0:38:44.959
<v Speaker 1>but this time with regard to dialect as opposed to say,

0:38:45.000 --> 0:38:48.520
<v Speaker 1>physical features. I think it's a really important piece, particularly

0:38:48.560 --> 0:38:51.080
<v Speaker 1>since we live in a world in which code switching

0:38:51.320 --> 0:38:54.720
<v Speaker 1>is a really important mechanism for navigating different cultural groups

0:38:54.760 --> 0:38:57.920
<v Speaker 1>for a lot of people, and if they are switched

0:38:57.920 --> 0:39:02.440
<v Speaker 1>into one particular culture, it's entirely possible that an AI

0:39:02.520 --> 0:39:07.880
<v Speaker 1>model is going to make some very racist conclusions based

0:39:07.920 --> 0:39:11.160
<v Speaker 1>on that anyway. Next up would be a piece by

0:39:11.200 --> 0:39:14.400
<v Speaker 1>Heather Knight and Kate Conger of The New York Times

0:39:14.440 --> 0:39:19.719
<v Speaker 1>titled Elon Musk's X is leaving San Francisco. City officials

0:39:19.880 --> 0:39:23.640
<v Speaker 1>say good riddance. So this story covers how X, which

0:39:23.640 --> 0:39:27.319
<v Speaker 1>has long had its HQ in San Francisco, California, is

0:39:27.400 --> 0:39:31.359
<v Speaker 1>now moving to other parts of California, like it's going

0:39:31.400 --> 0:39:34.800
<v Speaker 1>to rely on offices that are in other cities in California,

0:39:34.880 --> 0:39:37.919
<v Speaker 1>but the HQ itself is relocating to Texas, And how

0:39:38.000 --> 0:39:41.120
<v Speaker 1>some people who are in various positions in San Francisco

0:39:41.200 --> 0:39:45.960
<v Speaker 1>government aren't exactly wringing their hands at x's departure. Then finally,

0:39:46.000 --> 0:39:49.879
<v Speaker 1>there's a concerning article in The Texas Observer by Francesca

0:39:50.040 --> 0:39:54.960
<v Speaker 1>du Nunzio titled Texas State Police gear up for massive

0:39:55.040 --> 0:39:59.279
<v Speaker 1>expansion of surveillance tech. It serves as a reminder that

0:39:59.360 --> 0:40:03.080
<v Speaker 1>it's very important to hold law enforcement agencies accountable and

0:40:03.160 --> 0:40:07.320
<v Speaker 1>to investigate whether their reliance on certain technologies is merited,

0:40:07.600 --> 0:40:10.600
<v Speaker 1>particularly since some of those technologies have proven to have

0:40:10.680 --> 0:40:13.799
<v Speaker 1>flaws that can lead to disproportionate harm being done to

0:40:13.880 --> 0:40:17.880
<v Speaker 1>vulnerable populations. Specifically, I'm thinking about things like facial recognition

0:40:18.000 --> 0:40:23.200
<v Speaker 1>technologies and how that often can disproportionately affect innocent people

0:40:23.560 --> 0:40:28.160
<v Speaker 1>from the black community. We've seen that happen numerous times,

0:40:28.280 --> 0:40:32.160
<v Speaker 1>So any surveillance state stuff always makes me nervous. It's

0:40:32.200 --> 0:40:36.960
<v Speaker 1>also wild that Texas identity is so strange to me

0:40:37.600 --> 0:40:41.320
<v Speaker 1>because there's kind of ingrained in Texas is this idea

0:40:41.360 --> 0:40:44.600
<v Speaker 1>of independence and being able to stand on your own,

0:40:44.640 --> 0:40:47.560
<v Speaker 1>to hike yourself up by your bootstraps, and that you know,

0:40:47.800 --> 0:40:50.600
<v Speaker 1>like a lot of the narrative around Texas government is

0:40:50.640 --> 0:40:53.800
<v Speaker 1>about being self sufficient. I mean the state of Texas.

0:40:53.840 --> 0:40:58.319
<v Speaker 1>Their power grid is independent of the national power grid

0:40:58.320 --> 0:41:01.160
<v Speaker 1>in the United States, for example. So you've got this

0:41:01.360 --> 0:41:07.080
<v Speaker 1>idea of individualism and self sufficiency, and on the flip side,

0:41:07.120 --> 0:41:12.440
<v Speaker 1>you've got this growing surveillance state in law enforcement, and

0:41:12.480 --> 0:41:17.320
<v Speaker 1>the two don't really gel together to me, apart from

0:41:17.520 --> 0:41:21.719
<v Speaker 1>a slow moved more toward authoritarianism, which I think is

0:41:21.719 --> 0:41:26.120
<v Speaker 1>pretty concerning you. But the tech enabling that is really

0:41:26.440 --> 0:41:29.560
<v Speaker 1>the feature of that particular article, So check that out.

0:41:30.000 --> 0:41:32.759
<v Speaker 1>I hope all of you have a great weekend here

0:41:32.760 --> 0:41:35.440
<v Speaker 1>in the United States, the holiday weekend. I hope you

0:41:35.480 --> 0:41:37.600
<v Speaker 1>have a great holiday if you're here in the US.

0:41:38.040 --> 0:41:39.960
<v Speaker 1>If you're not in the US, I hope you just

0:41:39.960 --> 0:41:42.319
<v Speaker 1>have a great weekend period. And I'll talk to you

0:41:42.360 --> 0:41:53.040
<v Speaker 1>again really soon. Tech Stuff is an iHeartRadio production. For

0:41:53.160 --> 0:41:58.000
<v Speaker 1>more podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts,

0:41:58.120 --> 0:42:01.640
<v Speaker 1>or wherever you listen to your favorite show still