WEBVTT - Tech News: The Death of Physical Media

0:00:04.480 --> 0:00:12.520
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.560 --> 0:00:16.360
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jovin Strickland.

0:00:16.360 --> 0:00:19.520
<v Speaker 1>I'm an executive producer with iHeart Podcasts and how the

0:00:19.600 --> 0:00:22.040
<v Speaker 1>tech are you. It's time for the tech news for

0:00:22.120 --> 0:00:26.920
<v Speaker 1>the week ending July twelfth, two thy twenty four. There

0:00:27.040 --> 0:00:30.400
<v Speaker 1>was actually a ton of news this week. I guess

0:00:30.400 --> 0:00:35.159
<v Speaker 1>making up for last week, so I'm just covering like

0:00:35.360 --> 0:00:37.840
<v Speaker 1>half of it because there was so much, I had

0:00:37.840 --> 0:00:40.640
<v Speaker 1>to choose which stories I was going to include. As

0:00:40.640 --> 0:00:42.080
<v Speaker 1>it stands, this is going to be a long one,

0:00:42.159 --> 0:00:45.400
<v Speaker 1>so let's get to it. Last week, the German newspaper

0:00:45.479 --> 0:00:49.239
<v Speaker 1>Der Spiegel and a Russian independent news site called The

0:00:49.400 --> 0:00:55.120
<v Speaker 1>Insider revealed that Russia's Foreign Intelligence Service aka the SVR

0:00:55.520 --> 0:00:59.280
<v Speaker 1>has a program that they call Project Kailo. I don't

0:00:59.280 --> 0:01:02.200
<v Speaker 1>know if that's name after Kylo Renn from the Star

0:01:02.240 --> 0:01:05.640
<v Speaker 1>Wars films. Anyway, this project's aim is to spread misinformation

0:01:05.720 --> 0:01:09.840
<v Speaker 1>and propaganda in support of Russia's goals, particularly with regard

0:01:10.080 --> 0:01:12.920
<v Speaker 1>to the ongoing war with Ukraine. And I find it

0:01:12.959 --> 0:01:15.720
<v Speaker 1>interesting that a lot of media sites reference this as

0:01:15.760 --> 0:01:20.479
<v Speaker 1>a bombshell report, linking Russia to these efforts. I think

0:01:20.520 --> 0:01:23.880
<v Speaker 1>it's surprising, not because I don't think it's important. I

0:01:23.920 --> 0:01:26.400
<v Speaker 1>do think it's important. I just figured we were all

0:01:26.440 --> 0:01:30.640
<v Speaker 1>working under the assumption that this was in fact happening already.

0:01:30.880 --> 0:01:34.200
<v Speaker 1>I guess the appearance of confirmation is really the story

0:01:34.240 --> 0:01:39.080
<v Speaker 1>here anyway. The report says that the svr's playbook involves

0:01:39.200 --> 0:01:43.319
<v Speaker 1>establishing fake news websites and then flooding these websites with

0:01:43.480 --> 0:01:47.800
<v Speaker 1>misleading content, often boosted through the use of generative AI.

0:01:48.000 --> 0:01:50.040
<v Speaker 1>You can write a whole lot of stuff if you

0:01:50.160 --> 0:01:52.920
<v Speaker 1>offload it to AI, and if you're not really concerned

0:01:52.960 --> 0:01:56.040
<v Speaker 1>about the accuracy of it, I mean, if your goal

0:01:56.120 --> 0:02:00.760
<v Speaker 1>is to create misinformation, accuracy really isn't in your top concerns.

0:02:01.600 --> 0:02:04.720
<v Speaker 1>The agency also made heavy use of social networking and

0:02:04.800 --> 0:02:09.800
<v Speaker 1>media platforms to spread these messages, so establishing a place

0:02:09.840 --> 0:02:12.440
<v Speaker 1>to post everything and then a distribution method for getting

0:02:12.440 --> 0:02:14.880
<v Speaker 1>it out in front as many eyeballs as possible. So,

0:02:14.919 --> 0:02:18.160
<v Speaker 1>according to these newspapers, the agency went to the trouble

0:02:18.240 --> 0:02:21.960
<v Speaker 1>of actually hiring real world people to pose as protesters

0:02:22.040 --> 0:02:26.680
<v Speaker 1>in various Western countries in an effort to amplify messaging,

0:02:27.000 --> 0:02:32.320
<v Speaker 1>and then beyond that, they helped distribute video footage of

0:02:32.400 --> 0:02:36.600
<v Speaker 1>these protests in order to get a wider release of

0:02:36.639 --> 0:02:39.840
<v Speaker 1>that messaging. This is interesting because here in the United States,

0:02:39.840 --> 0:02:42.480
<v Speaker 1>actually not too far from the state where I live,

0:02:43.080 --> 0:02:48.840
<v Speaker 1>there was a notable white supremacist march that took place

0:02:49.040 --> 0:02:53.560
<v Speaker 1>in Nashville, Tennessee. And I'm curious as to whether or

0:02:53.639 --> 0:02:58.959
<v Speaker 1>not that march was amplified by efforts like this, where

0:02:59.000 --> 0:03:03.680
<v Speaker 1>people were specific brought in to boost the numbers and

0:03:03.760 --> 0:03:08.399
<v Speaker 1>make them larger. And then obviously that video footage of

0:03:08.480 --> 0:03:12.760
<v Speaker 1>that that particular march got pretty wide circulation. And I

0:03:12.800 --> 0:03:14.519
<v Speaker 1>mean it may not be at all related to the

0:03:15.240 --> 0:03:17.320
<v Speaker 1>Russian efforts. I want to make that clear. This could

0:03:17.400 --> 0:03:20.600
<v Speaker 1>be completely independent of that, but it does sort of

0:03:20.919 --> 0:03:26.040
<v Speaker 1>fall in line with that same strategy. Also last week,

0:03:26.280 --> 0:03:29.880
<v Speaker 1>Cowlan McGee and I apologize for butchering the name, but

0:03:29.960 --> 0:03:32.400
<v Speaker 1>McGee wrote a piece for I News, which is an

0:03:32.440 --> 0:03:36.400
<v Speaker 1>English news site, and in that piece, McGee writes that

0:03:36.440 --> 0:03:41.200
<v Speaker 1>French officials identified Russian propaganda as pushing French citizens to

0:03:41.360 --> 0:03:46.200
<v Speaker 1>support far right candidates during their parliamentary elections. Those took

0:03:46.200 --> 0:03:50.000
<v Speaker 1>place just this past Sunday. Now, those efforts ultimately fell

0:03:50.160 --> 0:03:53.040
<v Speaker 1>a little short. The far right did win quite a

0:03:53.080 --> 0:03:56.040
<v Speaker 1>few seats, like one hundred and forty two seats in parliament,

0:03:56.440 --> 0:03:59.000
<v Speaker 1>but that puts them in third place, behind the Left

0:03:59.040 --> 0:04:01.920
<v Speaker 1>wing Party, which won one hundred eighty eight seats and

0:04:02.000 --> 0:04:06.240
<v Speaker 1>the Centrist Party, which won one hundred and sixty one seats. However,

0:04:06.680 --> 0:04:09.960
<v Speaker 1>no single party secured two hundred and eighty nine or

0:04:10.000 --> 0:04:14.400
<v Speaker 1>more seats, which means France's president now faces the tough

0:04:14.480 --> 0:04:18.040
<v Speaker 1>challenge of appointing a prime minister because with they don't

0:04:18.080 --> 0:04:23.240
<v Speaker 1>have the support of a single parliamentary party. Right, there's

0:04:23.320 --> 0:04:27.000
<v Speaker 1>no party that holds a majority, and if the prime

0:04:27.000 --> 0:04:29.960
<v Speaker 1>minister doesn't have the support of parliament, then the government

0:04:30.040 --> 0:04:32.479
<v Speaker 1>kind of stops working. So what I'm saying is that

0:04:32.600 --> 0:04:36.000
<v Speaker 1>Russia's campaign, assuming that it actually had an impact on

0:04:36.560 --> 0:04:40.279
<v Speaker 1>the French elections at all, was not a total failure. Yeah,

0:04:40.279 --> 0:04:43.440
<v Speaker 1>they didn't secure a majority, but if you're thinking it's

0:04:43.520 --> 0:04:47.480
<v Speaker 1>more in an effort to disrupt politics and to add

0:04:47.520 --> 0:04:52.000
<v Speaker 1>some instability to Western governments, then there was success here,

0:04:52.440 --> 0:04:55.480
<v Speaker 1>or at least it's in alignment with Russia's goals. Whether

0:04:55.600 --> 0:04:58.599
<v Speaker 1>or not the efforts moved the needle at all, that's

0:04:59.040 --> 0:05:03.560
<v Speaker 1>that's another question. McGee's piece in IEWS lists out numerous

0:05:03.600 --> 0:05:08.640
<v Speaker 1>examples of Russian attempts to misinform, from bought controlled social

0:05:08.640 --> 0:05:11.679
<v Speaker 1>accounts to fake news sites pushing lies to the public,

0:05:11.839 --> 0:05:15.719
<v Speaker 1>and obviously France is just one nation that's targeted by Russia.

0:05:15.839 --> 0:05:19.320
<v Speaker 1>The convergence of tools like AI and social networks, on

0:05:19.440 --> 0:05:22.760
<v Speaker 1>top of how easy it is to just launch a website,

0:05:22.839 --> 0:05:25.279
<v Speaker 1>has really created a perfect storm for the creation and

0:05:25.320 --> 0:05:29.440
<v Speaker 1>distribution of propaganda. So, as always, I recommend viewing media

0:05:29.560 --> 0:05:32.520
<v Speaker 1>through the lens of critical thinking. It's not a guarantee

0:05:32.520 --> 0:05:35.760
<v Speaker 1>that you still won't get misled. That can still happen,

0:05:36.040 --> 0:05:39.760
<v Speaker 1>but using critical thinking really helps cut down on the

0:05:40.080 --> 0:05:43.800
<v Speaker 1>frequency at which that can happen. Make sure you're paying

0:05:43.839 --> 0:05:46.760
<v Speaker 1>attention to the source of that information and what their

0:05:46.839 --> 0:05:51.240
<v Speaker 1>sources are, because if we're all looking at news that's

0:05:51.279 --> 0:05:54.320
<v Speaker 1>all drawing its information from a single source, and that

0:05:54.480 --> 0:05:57.920
<v Speaker 1>source is compromised, well then we can't trust any of

0:05:57.960 --> 0:06:00.240
<v Speaker 1>the news that was reported from it. We're in the

0:06:00.320 --> 0:06:03.200
<v Speaker 1>United States, the Department of Justice announced just this past

0:06:03.200 --> 0:06:07.000
<v Speaker 1>Tuesday that it had identified and disrupted a Russian operation

0:06:07.320 --> 0:06:11.320
<v Speaker 1>making use of bots and misinformation to sew discord here

0:06:11.320 --> 0:06:14.440
<v Speaker 1>in the states, which just as a point of reference, y'all,

0:06:14.480 --> 0:06:17.479
<v Speaker 1>we do not need outside help on that. We're really

0:06:17.520 --> 0:06:22.880
<v Speaker 1>good at sowing discord amongst ourselves. Anyway, the DOJ seized

0:06:23.000 --> 0:06:26.279
<v Speaker 1>two domains in around one thousand social accounts believed to

0:06:26.279 --> 0:06:29.920
<v Speaker 1>be part of this Russian operation. The associated accounts received

0:06:29.920 --> 0:06:32.680
<v Speaker 1>a ban on x formerly known as Twitter, and they

0:06:32.720 --> 0:06:36.440
<v Speaker 1>had a history of posting content with a pro Kremlin perspective.

0:06:37.000 --> 0:06:41.279
<v Speaker 1>Apart from using AI to undermine governments and societies, it

0:06:41.279 --> 0:06:44.080
<v Speaker 1>seems like there's not really enough of a use case

0:06:44.080 --> 0:06:47.640
<v Speaker 1>for artificial intelligence to justify the truly insane amount of

0:06:47.680 --> 0:06:51.320
<v Speaker 1>investment that's going into it. Now that's not just my opinion,

0:06:51.640 --> 0:06:55.159
<v Speaker 1>although it is my opinion. Goldman Sachs released a newsletter

0:06:55.200 --> 0:06:59.600
<v Speaker 1>warning that told businesses there there just might be this crazy,

0:06:59.680 --> 0:07:03.200
<v Speaker 1>uns sustainable bubble forming around AI. But to be clear,

0:07:03.279 --> 0:07:05.479
<v Speaker 1>I am applying my own point of view to what

0:07:05.640 --> 0:07:09.080
<v Speaker 1>Goldman Sachs found. They didn't use words like crazy, and

0:07:09.080 --> 0:07:11.760
<v Speaker 1>in fact, they were pretty light with the use of

0:07:11.800 --> 0:07:14.600
<v Speaker 1>the word bubble, although at least one Goldman sax rep

0:07:14.680 --> 0:07:19.040
<v Speaker 1>did refer to it as a potential bubble, not definitively

0:07:19.080 --> 0:07:22.720
<v Speaker 1>a bubble, but it could be so. The report revealed

0:07:22.760 --> 0:07:26.320
<v Speaker 1>that around a trillion dollars is on track to pour

0:07:26.520 --> 0:07:30.440
<v Speaker 1>into the generative AI space, and that includes stuff like

0:07:30.880 --> 0:07:34.800
<v Speaker 1>building out and outfitting data centers, you know, the purchase

0:07:34.840 --> 0:07:38.720
<v Speaker 1>of new hardware, research and development, all this kind of stuff.

0:07:38.920 --> 0:07:44.040
<v Speaker 1>Goldman Sachs says, there's also no killer application for AI

0:07:44.240 --> 0:07:48.480
<v Speaker 1>that kind of justifies this crazy expenditure. So, in other words,

0:07:48.680 --> 0:07:52.160
<v Speaker 1>the research newsletter says, companies are rushing into the AI

0:07:52.280 --> 0:07:56.320
<v Speaker 1>space without really a clear goal or any assurance that

0:07:56.360 --> 0:07:59.000
<v Speaker 1>the investment they're making is going to pay off down

0:07:59.080 --> 0:08:02.640
<v Speaker 1>the road. It could be that the companies that are

0:08:02.680 --> 0:08:07.200
<v Speaker 1>spending billions of dollars in the AI generative AI specifically

0:08:07.240 --> 0:08:10.480
<v Speaker 1>in that field, that they're setting huge piles of cash

0:08:10.520 --> 0:08:13.440
<v Speaker 1>on fire. Alah, the joker in that Dark Night movie.

0:08:13.760 --> 0:08:17.800
<v Speaker 1>Jim Cavello, the head of Goldman Sachs's Global equity research,

0:08:17.960 --> 0:08:22.560
<v Speaker 1>put it this way, quote, what one trillion dollar problem

0:08:22.800 --> 0:08:28.040
<v Speaker 1>will AI solve? Replacing low wage jobs with tremendously costly

0:08:28.120 --> 0:08:32.400
<v Speaker 1>technology is basically the polar opposite of the prior technology

0:08:32.440 --> 0:08:36.079
<v Speaker 1>transitions I've witnessed in my thirty years of closely following

0:08:36.120 --> 0:08:39.360
<v Speaker 1>the tech industry end quote. So what he's saying is

0:08:39.679 --> 0:08:43.360
<v Speaker 1>there's not a clear problem that AI is solving, especially

0:08:43.360 --> 0:08:46.880
<v Speaker 1>not one that amounts to a one trillion dollar problem,

0:08:47.040 --> 0:08:50.280
<v Speaker 1>and that the ways we are seeing AI being applied

0:08:50.360 --> 0:08:54.280
<v Speaker 1>right now are low cost things. And in fact, it

0:08:54.320 --> 0:08:57.040
<v Speaker 1>could mean that you're spending more money with AI than

0:08:57.040 --> 0:09:01.040
<v Speaker 1>you were with human beings, so you're actually costing yourself

0:09:01.080 --> 0:09:05.400
<v Speaker 1>more money and you're funding that whole process. So it

0:09:05.400 --> 0:09:08.000
<v Speaker 1>really sounds like shots fired across the ballot companies that

0:09:08.080 --> 0:09:11.360
<v Speaker 1>have been downsizing staff in favor of relying more on

0:09:11.520 --> 0:09:15.319
<v Speaker 1>generative AI, such as oh I don't know HowStuffWorks dot

0:09:15.360 --> 0:09:18.720
<v Speaker 1>Com my former employer. We'll have more about the issue

0:09:18.760 --> 0:09:21.800
<v Speaker 1>of AI displacing creatives later in this episode, but yeah,

0:09:21.840 --> 0:09:24.320
<v Speaker 1>I'm still obviously salty about that, even though I wasn't

0:09:24.360 --> 0:09:26.959
<v Speaker 1>directly affected, right, I had already moved on from how

0:09:27.000 --> 0:09:30.040
<v Speaker 1>stuff works, or really my part of the company moved

0:09:30.080 --> 0:09:33.240
<v Speaker 1>on from How Stuff Works. But I'm still upset that

0:09:33.440 --> 0:09:37.520
<v Speaker 1>site ended up laying off the editorial staff in favor

0:09:37.559 --> 0:09:42.160
<v Speaker 1>of AI generated articles. I think that was an enormous mistake.

0:09:42.480 --> 0:09:44.640
<v Speaker 1>I plan on doing an episode in the near future

0:09:44.960 --> 0:09:47.160
<v Speaker 1>about one of the many reasons I think that's a

0:09:47.440 --> 0:09:52.640
<v Speaker 1>massive mistake, because it's not just that very talented, dedicated

0:09:52.720 --> 0:09:55.920
<v Speaker 1>people lost their jobs over it. That's a big part

0:09:55.920 --> 0:09:58.679
<v Speaker 1>of it. I mean, there's an emotional attachment, don't get

0:09:58.679 --> 0:10:01.000
<v Speaker 1>me wrong. But I also think that there is a

0:10:01.640 --> 0:10:06.199
<v Speaker 1>technological mistake that's being made, and I'm not the only one.

0:10:06.760 --> 0:10:10.000
<v Speaker 1>It involves things like model collapse, as in large language

0:10:10.000 --> 0:10:13.320
<v Speaker 1>model collapse, but we'll talk about that in a future

0:10:13.360 --> 0:10:17.680
<v Speaker 1>episode not too long from now. Anyway, the report warns

0:10:17.720 --> 0:10:21.760
<v Speaker 1>that any returns on investment are likely to be many

0:10:21.960 --> 0:10:24.800
<v Speaker 1>years down the road because it's going to take time

0:10:24.920 --> 0:10:30.160
<v Speaker 1>to build the AI infrastructure that actually creates meaningful improvements

0:10:30.240 --> 0:10:33.720
<v Speaker 1>in stuff like business performance and costs. So in the

0:10:33.760 --> 0:10:36.800
<v Speaker 1>short term, it's far more likely that running AI operations

0:10:36.840 --> 0:10:40.280
<v Speaker 1>is actually going to cost more than going the alternative route.

0:10:40.360 --> 0:10:43.200
<v Speaker 1>And all of that obviously becomes dangerous for companies that

0:10:43.240 --> 0:10:46.320
<v Speaker 1>are currently investing heavily in the space. They might find

0:10:46.360 --> 0:10:49.679
<v Speaker 1>themselves either in need of a severe course correction or

0:10:49.720 --> 0:10:53.120
<v Speaker 1>they might have to convince stakeholders to you know, patiently

0:10:53.160 --> 0:10:55.000
<v Speaker 1>wait for things to pay off in the future. That's

0:10:55.080 --> 0:10:57.760
<v Speaker 1>kind of what Meta has been doing, particularly in the

0:10:58.160 --> 0:11:03.080
<v Speaker 1>Reality Labs division, and metaverse stuff. Zuckerberg has to keep saying,

0:11:03.520 --> 0:11:05.760
<v Speaker 1>this is going to cost us a lot of money

0:11:05.760 --> 0:11:07.720
<v Speaker 1>in the short term, but in the long term, we

0:11:07.800 --> 0:11:12.200
<v Speaker 1>believe it's the future of our business. I remain unconvinced

0:11:12.520 --> 0:11:14.679
<v Speaker 1>that that's going to be the case, but that's the

0:11:14.800 --> 0:11:18.319
<v Speaker 1>argument Zuckerberg has to make two investors pretty much every

0:11:18.360 --> 0:11:21.440
<v Speaker 1>earnings called because they have to grapple with the fact

0:11:21.480 --> 0:11:24.760
<v Speaker 1>that they're spending billions of dollars in this division and

0:11:24.800 --> 0:11:27.439
<v Speaker 1>they don't have a lot to show for it yet,

0:11:27.679 --> 0:11:31.720
<v Speaker 1>and the stuff they have shown has not really created

0:11:31.840 --> 0:11:36.719
<v Speaker 1>an amazing response among consumers or investors. I expect we're

0:11:36.720 --> 0:11:39.520
<v Speaker 1>going to see very similar stories play out in the

0:11:39.559 --> 0:11:44.200
<v Speaker 1>AI space. Speaking of AI displacing jobs, into It, a

0:11:44.320 --> 0:11:49.280
<v Speaker 1>company that specializes in tax preparation software announced a reorganization

0:11:49.400 --> 0:11:52.120
<v Speaker 1>this week and that's going to result in downsizing staff

0:11:52.120 --> 0:11:55.200
<v Speaker 1>by around ten percent of the company. Company reps say

0:11:55.280 --> 0:11:57.600
<v Speaker 1>this is part of the long term strategy in which

0:11:57.720 --> 0:12:00.560
<v Speaker 1>into It will hire at least that same number of

0:12:00.679 --> 0:12:03.320
<v Speaker 1>people that they're laying off this year. So they're saying,

0:12:03.320 --> 0:12:06.400
<v Speaker 1>like next year they're going to hire as many or

0:12:06.480 --> 0:12:09.120
<v Speaker 1>more people as what they are laying off right now.

0:12:09.280 --> 0:12:12.960
<v Speaker 1>That number is around one eight hundred staff and that

0:12:13.120 --> 0:12:18.360
<v Speaker 1>this long term plan also involves incorporating artificial intelligence in

0:12:18.360 --> 0:12:22.040
<v Speaker 1>into its offerings. No big surprise there that they're saying

0:12:22.080 --> 0:12:24.120
<v Speaker 1>AI is going to be a big part of their

0:12:24.440 --> 0:12:28.400
<v Speaker 1>ongoing strategy. That is kind of the messaging we're hearing

0:12:28.600 --> 0:12:32.680
<v Speaker 1>across all industries right now. So into Its CEO further

0:12:32.760 --> 0:12:35.839
<v Speaker 1>said that more than half of those one eight hundred

0:12:35.880 --> 0:12:39.079
<v Speaker 1>employees who are being let go were selected because they

0:12:39.080 --> 0:12:42.600
<v Speaker 1>failed to meet company expectations, which is a big old yikes.

0:12:42.960 --> 0:12:47.400
<v Speaker 1>Like when you know arguably around five percent or more

0:12:47.480 --> 0:12:51.760
<v Speaker 1>of your company isn't meeting expectations, that's to me, that's

0:12:51.760 --> 0:12:55.760
<v Speaker 1>a management problem. That means that managers are not doing

0:12:55.800 --> 0:12:59.120
<v Speaker 1>their job in making sure that employees have what they

0:12:59.200 --> 0:13:02.360
<v Speaker 1>need and understand what they need to do in order

0:13:02.360 --> 0:13:05.080
<v Speaker 1>to meet expectations. But I mean, what do I know.

0:13:05.360 --> 0:13:08.440
<v Speaker 1>I'm not an expert in business or anything like that.

0:13:08.640 --> 0:13:11.440
<v Speaker 1>It just it just seems that way to me. So

0:13:12.400 --> 0:13:15.560
<v Speaker 1>I do think for the record that AI will have

0:13:15.880 --> 0:13:18.640
<v Speaker 1>its place. I'm not totally against AI. I know I

0:13:18.679 --> 0:13:22.080
<v Speaker 1>come down hard on AI a lot on this show.

0:13:22.520 --> 0:13:24.920
<v Speaker 1>I do think there will be ways to integrate AI

0:13:25.080 --> 0:13:29.040
<v Speaker 1>into business strategies that will be overall beneficial and not

0:13:29.120 --> 0:13:31.520
<v Speaker 1>just beneficial to the bottom line, which is kind of

0:13:31.520 --> 0:13:33.920
<v Speaker 1>the cynical way of looking at it right now, but

0:13:34.080 --> 0:13:36.880
<v Speaker 1>to people who are actually working at those companies. I

0:13:36.920 --> 0:13:40.560
<v Speaker 1>do think there are ways to use AI to enhance

0:13:41.000 --> 0:13:45.600
<v Speaker 1>people's work so that they can focus on the things

0:13:45.640 --> 0:13:49.000
<v Speaker 1>that really matter, while AI handles little details that are

0:13:49.040 --> 0:13:53.800
<v Speaker 1>important but are not necessary for humans to handle personally.

0:13:54.240 --> 0:13:57.040
<v Speaker 1>I just think there's also a ton of company executives

0:13:57.040 --> 0:14:00.840
<v Speaker 1>out there who are rushing into integrating AI without fully

0:14:00.880 --> 0:14:04.120
<v Speaker 1>thinking about the consequences they're going to encounter and the

0:14:04.240 --> 0:14:08.480
<v Speaker 1>lives are going to impact. They're doing it quickly without

0:14:09.000 --> 0:14:12.760
<v Speaker 1>fully thinking it through, and that's what leads to really

0:14:12.840 --> 0:14:16.560
<v Speaker 1>big messes. Okay, speaking of a big mess, I just

0:14:16.800 --> 0:14:18.960
<v Speaker 1>made one by spelling my coffee. We're going to take

0:14:19.000 --> 0:14:31.400
<v Speaker 1>a quick break and I'll be right back. Okay, we're back.

0:14:32.320 --> 0:14:37.200
<v Speaker 1>Coffee spillage has been contained. Cleaning efforts are ongoing, but

0:14:37.280 --> 0:14:41.320
<v Speaker 1>let's get back into the episode. So, a hacker group

0:14:41.480 --> 0:14:47.920
<v Speaker 1>called sieged Sec. Sie ged Sec says it has breached

0:14:47.920 --> 0:14:51.720
<v Speaker 1>the systems of an organization called the Heritage Foundation and

0:14:51.800 --> 0:14:55.480
<v Speaker 1>stolen a large amount of data and subsequently released that

0:14:55.560 --> 0:14:59.920
<v Speaker 1>data online. The Heritage Foundation is a conservative political or

0:15:00.040 --> 0:15:04.160
<v Speaker 1>organization and think tank. It is credited with being responsible

0:15:04.200 --> 0:15:09.200
<v Speaker 1>for a broad platform of policy proposals, collectively referenced as

0:15:09.400 --> 0:15:13.040
<v Speaker 1>Project twenty twenty five. Now, to go into Project twenty

0:15:13.080 --> 0:15:17.160
<v Speaker 1>twenty five is well beyond the scope of this podcast. However,

0:15:17.200 --> 0:15:19.640
<v Speaker 1>I can recommend you check out the June twenty eighth,

0:15:19.840 --> 0:15:22.440
<v Speaker 1>twenty twenty four episode of Stuff they Don't Want You

0:15:22.520 --> 0:15:26.280
<v Speaker 1>to Know. It is titled Project twenty twenty five. Should

0:15:26.280 --> 0:15:30.840
<v Speaker 1>we be concerned anyway? The sieged sec hackers carried out

0:15:30.880 --> 0:15:34.640
<v Speaker 1>the attack in part to ensure more quote transparency to

0:15:34.680 --> 0:15:39.200
<v Speaker 1>the public regarding who exactly is supporting Heritage end quote.

0:15:39.280 --> 0:15:41.840
<v Speaker 1>So that quote comes from a hacker who uses the

0:15:41.920 --> 0:15:46.000
<v Speaker 1>handle vo viio. This hacker spoke with the new site

0:15:46.040 --> 0:15:50.800
<v Speaker 1>Cyberscoop about the breach. That breach is mostly apparently a

0:15:50.880 --> 0:15:54.120
<v Speaker 1>list of names of people who have been involved with

0:15:54.280 --> 0:15:57.680
<v Speaker 1>or contributed to the Heritage Foundation. This is all part

0:15:57.720 --> 0:16:03.240
<v Speaker 1>of a quickly developing story regarding Project twenty twenty five,

0:16:03.480 --> 0:16:06.840
<v Speaker 1>and there's a lot of information and misinformation out about

0:16:06.880 --> 0:16:10.440
<v Speaker 1>that as well. So again, use critical thinking when you're

0:16:10.480 --> 0:16:14.320
<v Speaker 1>looking into this stuff. I do think personally that it's

0:16:14.360 --> 0:16:19.760
<v Speaker 1>something to be concerned about, and that it is. There

0:16:19.760 --> 0:16:23.480
<v Speaker 1>are elements of it that are pretty darn scary if

0:16:23.520 --> 0:16:28.160
<v Speaker 1>you if you care about stuff like say LGBTQ rights,

0:16:28.520 --> 0:16:32.880
<v Speaker 1>it's very scary, or women's autonomy rights, that kind of stuff.

0:16:33.040 --> 0:16:36.440
<v Speaker 1>It gets pretty frightening. But I recommend everyone do their

0:16:36.480 --> 0:16:39.680
<v Speaker 1>research and learn about it, and you know, mind where

0:16:39.680 --> 0:16:43.880
<v Speaker 1>you're getting your information, so that you're you've got a

0:16:43.920 --> 0:16:48.160
<v Speaker 1>reasonable handle on what's going on, because it's always important

0:16:48.280 --> 0:16:50.760
<v Speaker 1>to keep that in mind when you're engaging with material,

0:16:50.840 --> 0:16:55.000
<v Speaker 1>particularly material that might be confirming any biases you happen

0:16:55.080 --> 0:16:57.960
<v Speaker 1>to have. I have to remind myself of that all

0:16:58.000 --> 0:17:02.480
<v Speaker 1>the time. Marco Risol of hackerdose dot com has an

0:17:02.600 --> 0:17:06.200
<v Speaker 1>article titled hackers may use Telegram video to gain full

0:17:06.240 --> 0:17:09.880
<v Speaker 1>control of your phone. That is a heck of a headline.

0:17:10.080 --> 0:17:13.800
<v Speaker 1>So first off, in case you are not familiar with Telegram,

0:17:14.240 --> 0:17:18.840
<v Speaker 1>that's a smartphone based messaging app. It's also cloud based

0:17:18.920 --> 0:17:22.760
<v Speaker 1>messaging and it offers end to end encryption. You can

0:17:22.800 --> 0:17:26.960
<v Speaker 1>do voice calls, video calls, text messages. It has become

0:17:27.000 --> 0:17:30.359
<v Speaker 1>a favored messaging app among those who value their privacy

0:17:30.400 --> 0:17:35.360
<v Speaker 1>and they don't want their communications to be snoopable. They

0:17:35.359 --> 0:17:37.919
<v Speaker 1>want to do end to end encryption. But an X

0:17:38.400 --> 0:17:41.360
<v Speaker 1>or Twitter user, depending on how you want to call

0:17:41.400 --> 0:17:47.240
<v Speaker 1>that service called. Today cyber News posted that a vulnerability

0:17:47.240 --> 0:17:51.800
<v Speaker 1>in the Android version of Telegram allows an on ramp

0:17:51.960 --> 0:17:56.640
<v Speaker 1>for malware. So the alleged exploit involves the target receiving

0:17:56.640 --> 0:17:59.440
<v Speaker 1>a link to a video that if the target tries

0:17:59.480 --> 0:18:02.800
<v Speaker 1>to launch, the video, prompts a pop up message, and

0:18:02.840 --> 0:18:07.400
<v Speaker 1>that message says that Telegram's native video player is unable

0:18:07.440 --> 0:18:11.080
<v Speaker 1>to play the media file in question, So don't worry,

0:18:11.359 --> 0:18:15.359
<v Speaker 1>because you will be prompted to go toward a site

0:18:15.800 --> 0:18:18.720
<v Speaker 1>that is claimed to be a third party video service

0:18:19.000 --> 0:18:21.520
<v Speaker 1>that then will play the video. So it's saying, oh,

0:18:21.680 --> 0:18:24.200
<v Speaker 1>Telegram can't play this, but just click this link, you'll

0:18:24.240 --> 0:18:26.960
<v Speaker 1>go to a site that will play the video. Except

0:18:26.960 --> 0:18:29.440
<v Speaker 1>it's all a ploy to trick the target into unknowingly

0:18:29.560 --> 0:18:34.000
<v Speaker 1>consenting to downloading malware. The malware infects the phone and

0:18:34.040 --> 0:18:38.040
<v Speaker 1>effectively hands control over to a remote operator who has

0:18:38.680 --> 0:18:42.320
<v Speaker 1>essentially full administrative access to the device. At that point,

0:18:42.640 --> 0:18:46.240
<v Speaker 1>they can access the camera on the phone, the microphones

0:18:46.400 --> 0:18:48.840
<v Speaker 1>call logs, they can see all the apps that are

0:18:49.520 --> 0:18:52.000
<v Speaker 1>saved to the phone, all that kind of stuff, all

0:18:52.040 --> 0:18:55.399
<v Speaker 1>of that allegedly becomes available to the hackers. That is,

0:18:55.640 --> 0:18:59.400
<v Speaker 1>if these claims are in fact true, and they might

0:18:59.520 --> 0:19:03.639
<v Speaker 1>not be so. The tweet included a video demonstration of

0:19:03.680 --> 0:19:07.040
<v Speaker 1>this exploit in action. However, the resolution of the video

0:19:07.240 --> 0:19:10.760
<v Speaker 1>was not great, and thus it was difficult to verify

0:19:11.160 --> 0:19:15.520
<v Speaker 1>that this is a legitimate video of an actual exploit.

0:19:15.880 --> 0:19:20.480
<v Speaker 1>Earlier this year, Telegram actually debunked a different vulnerability claim

0:19:20.560 --> 0:19:24.080
<v Speaker 1>that was made against it. So there's already precedent for

0:19:24.280 --> 0:19:28.119
<v Speaker 1>false claims against Telegram, and it could turn out that

0:19:28.200 --> 0:19:31.640
<v Speaker 1>this new allegation is also a hoax. But I would

0:19:31.720 --> 0:19:35.600
<v Speaker 1>suggest to anyone who's using Telegram, or really any messaging

0:19:35.680 --> 0:19:38.479
<v Speaker 1>service for that matter, to think twice before clicking on

0:19:38.560 --> 0:19:41.520
<v Speaker 1>links to stuff, particularly if it is in relation to

0:19:41.760 --> 0:19:44.440
<v Speaker 1>a message that has a clickbaity kind of vibe to it,

0:19:44.680 --> 0:19:48.240
<v Speaker 1>right Like, if you get a video that's appealing to

0:19:48.480 --> 0:19:52.840
<v Speaker 1>either your paranoia, right like it's a video saying, hey,

0:19:52.960 --> 0:19:56.200
<v Speaker 1>is this you and this video? Or if it's something

0:19:56.240 --> 0:20:00.280
<v Speaker 1>that's very it's like appealing to a salacious sign of

0:20:00.359 --> 0:20:04.240
<v Speaker 1>human nature. Anything like that that should raise red flags.

0:20:04.240 --> 0:20:07.040
<v Speaker 1>And you should be very cautious before following any links

0:20:07.080 --> 0:20:09.679
<v Speaker 1>because it's a tried and true method to trick people

0:20:09.720 --> 0:20:12.359
<v Speaker 1>into a trap. If you were an AT and T

0:20:12.520 --> 0:20:16.520
<v Speaker 1>cellular customer between May and November in twenty twenty two,

0:20:16.720 --> 0:20:20.480
<v Speaker 1>I have some bad news. There's a really good chance

0:20:20.520 --> 0:20:25.000
<v Speaker 1>that your phone number and some information about who you

0:20:25.200 --> 0:20:29.280
<v Speaker 1>texted and called has been leaked in a massive data breach.

0:20:29.359 --> 0:20:33.359
<v Speaker 1>So AT and T says that essentially all cellular customers

0:20:33.640 --> 0:20:36.680
<v Speaker 1>at that time period were involved in this data leak,

0:20:36.760 --> 0:20:39.520
<v Speaker 1>in which some third party was able to download the

0:20:39.600 --> 0:20:43.119
<v Speaker 1>information off of a cloud platform that AT and T uses.

0:20:43.200 --> 0:20:46.280
<v Speaker 1>So this is another case where a hackers target not

0:20:47.040 --> 0:20:50.800
<v Speaker 1>the company itself, not AT and T, but a business

0:20:50.840 --> 0:20:54.840
<v Speaker 1>to business operator that AT and T uses. You know,

0:20:54.880 --> 0:20:58.520
<v Speaker 1>it's a provider that has this cloud services platform, and

0:20:58.560 --> 0:21:02.320
<v Speaker 1>the hackers targeted that provider. AT and T says that

0:21:02.560 --> 0:21:05.119
<v Speaker 1>names were not included in this data leak. It was

0:21:05.240 --> 0:21:09.240
<v Speaker 1>just numbers and then metadata about the text messages and

0:21:09.320 --> 0:21:12.520
<v Speaker 1>phone calls those numbers were engaged in. However, AT and

0:21:12.560 --> 0:21:16.000
<v Speaker 1>T also says it can be rather trivial to match

0:21:16.119 --> 0:21:18.479
<v Speaker 1>a name with a phone number. There are a lot

0:21:18.520 --> 0:21:22.600
<v Speaker 1>of databases out there that have information about phone numbers

0:21:22.600 --> 0:21:25.800
<v Speaker 1>and who those numbers belong to. So all that info

0:21:26.320 --> 0:21:29.199
<v Speaker 1>may already be out in the wild, and just with

0:21:29.280 --> 0:21:31.960
<v Speaker 1>a little cross referencing, a hacker can figure out who

0:21:32.080 --> 0:21:34.800
<v Speaker 1>this number belongs to. Some of the call and texting

0:21:34.880 --> 0:21:37.919
<v Speaker 1>data related to some of the numbers was part of

0:21:37.920 --> 0:21:41.320
<v Speaker 1>this attack, as I've mentioned, So it's not the contents

0:21:41.359 --> 0:21:43.960
<v Speaker 1>of those phone calls or the texts. It's not like

0:21:44.000 --> 0:21:47.720
<v Speaker 1>the hackers can read what someone has texted to someone else. Instead,

0:21:47.880 --> 0:21:50.520
<v Speaker 1>it's a call log or a text log, so you

0:21:50.560 --> 0:21:54.600
<v Speaker 1>can see which numbers have communicated with one another. According

0:21:54.680 --> 0:21:58.080
<v Speaker 1>to AT and T spokesperson Alex Byers, this breach is

0:21:58.200 --> 0:22:01.960
<v Speaker 1>unrelated to a different incident that the company acknowledged back

0:22:02.000 --> 0:22:04.639
<v Speaker 1>in March. So AT and T has been the target

0:22:04.720 --> 0:22:08.840
<v Speaker 1>of two massive hacker attacks and data breaches. Not great,

0:22:09.240 --> 0:22:13.640
<v Speaker 1>Apple has assuaged the concerns of EU regulators, at least

0:22:13.640 --> 0:22:18.479
<v Speaker 1>for now, regarding the company's Tap to Pay iPhone payment system.

0:22:18.760 --> 0:22:22.600
<v Speaker 1>So regulators in the EU had accused Apple of jealously

0:22:22.760 --> 0:22:26.240
<v Speaker 1>guarding that Tap to pay system in order to maintain

0:22:26.359 --> 0:22:30.800
<v Speaker 1>a monopoly over payment processing through the iPhone, and if

0:22:30.840 --> 0:22:34.439
<v Speaker 1>Apple did not open that up to third parties, to

0:22:34.560 --> 0:22:38.119
<v Speaker 1>other like payment processing companies and such, Apple could face

0:22:38.200 --> 0:22:41.200
<v Speaker 1>a pretty sizable fine, which is putting it lightly. By

0:22:41.240 --> 0:22:46.359
<v Speaker 1>pretty sizable, I mean ten percent of the company's global revenue.

0:22:46.720 --> 0:22:50.919
<v Speaker 1>Apple is a three trillion dollar company, so that is

0:22:51.280 --> 0:22:55.719
<v Speaker 1>like billions of euros or billions of dollars worth of

0:22:55.840 --> 0:23:00.320
<v Speaker 1>money if Apple failed to comply to these regular later

0:23:00.359 --> 0:23:02.840
<v Speaker 1>demands or the company would have to cease operations in

0:23:02.880 --> 0:23:07.000
<v Speaker 1>the EU to avoid it. So the services that Apple

0:23:07.440 --> 0:23:10.119
<v Speaker 1>is opening things up like Apple has committed to doing

0:23:10.160 --> 0:23:14.120
<v Speaker 1>this include third parties that might have their own mobile

0:23:14.400 --> 0:23:18.640
<v Speaker 1>wallet features as well as their own payment processing services,

0:23:18.680 --> 0:23:21.840
<v Speaker 1>but it could also include things like using your mobile

0:23:21.880 --> 0:23:24.919
<v Speaker 1>phone to do stuff for all sorts of transactions, like

0:23:25.119 --> 0:23:28.800
<v Speaker 1>as a hotel key or as a ticket to an event,

0:23:29.080 --> 0:23:31.720
<v Speaker 1>or as a corporate badge to get into a building.

0:23:31.800 --> 0:23:34.760
<v Speaker 1>That kind of stuff. It all uses NFC or near

0:23:34.880 --> 0:23:40.280
<v Speaker 1>field communications technologies. So Apple appeers to have committed to this.

0:23:41.160 --> 0:23:45.200
<v Speaker 1>They have a deadline of July twenty fifth to open

0:23:45.280 --> 0:23:47.560
<v Speaker 1>up their system to other companies. If they do so,

0:23:48.000 --> 0:23:50.520
<v Speaker 1>there'll be no further problems. If they don't, then they

0:23:50.600 --> 0:23:55.119
<v Speaker 1>are facing the potential of a massive fine. Apple is

0:23:55.160 --> 0:23:57.640
<v Speaker 1>not the only tech company that has had to contend

0:23:57.640 --> 0:24:01.640
<v Speaker 1>with EU regulations recently. You know, the app formerly known

0:24:01.640 --> 0:24:05.200
<v Speaker 1>as Twitter has been called to task for breaching online

0:24:05.320 --> 0:24:09.840
<v Speaker 1>content rules under the EU's Digital Services Act or DSA.

0:24:10.160 --> 0:24:14.280
<v Speaker 1>So EU regulators investigated X for seven months and found

0:24:14.280 --> 0:24:17.960
<v Speaker 1>the company failed to comply with various rules requiring it

0:24:18.040 --> 0:24:21.480
<v Speaker 1>to make available a searchable advertising repository so that the

0:24:21.560 --> 0:24:25.240
<v Speaker 1>regulators can ensure that the advertising policies on the platform

0:24:25.359 --> 0:24:29.639
<v Speaker 1>are within EU's laws. Worst, the regulators accuse X of

0:24:29.680 --> 0:24:33.480
<v Speaker 1>denying them access to public data that they're supposed to

0:24:33.520 --> 0:24:36.600
<v Speaker 1>be able to review. In addition, the regulators found that

0:24:36.880 --> 0:24:40.440
<v Speaker 1>X's blue check mark system, which previously was all about

0:24:40.560 --> 0:24:43.760
<v Speaker 1>verifying an account, but now it just means that you've

0:24:43.880 --> 0:24:49.080
<v Speaker 1>paid for that service. They're now in opposition to industry practice, and,

0:24:49.200 --> 0:24:53.520
<v Speaker 1>as Reuter's reporter Thu Yung Chi puts it, quote, negatively

0:24:53.600 --> 0:24:57.400
<v Speaker 1>affect user's ability to make free and informed decisions about

0:24:57.440 --> 0:25:01.720
<v Speaker 1>the authenticity of the accounts they interact with. End quote.

0:25:02.320 --> 0:25:04.479
<v Speaker 1>X could face a fine of up to six percent

0:25:04.600 --> 0:25:07.520
<v Speaker 1>of its annual global revenue. That would definitely be a

0:25:07.600 --> 0:25:10.040
<v Speaker 1>huge blow to the company. I mean, it's a company

0:25:10.080 --> 0:25:12.800
<v Speaker 1>that has continued to struggle in an effort to keep

0:25:12.920 --> 0:25:17.760
<v Speaker 1>advertisers on board. Like revenue for Twitter, Slash, X has

0:25:17.800 --> 0:25:21.200
<v Speaker 1>been a real sticky subject over the last couple of years.

0:25:21.520 --> 0:25:23.840
<v Speaker 1>X will have a chance to defend itself. So this

0:25:23.920 --> 0:25:27.840
<v Speaker 1>is not a cut and dried decision yet. X can

0:25:28.040 --> 0:25:31.760
<v Speaker 1>come forward and attempt to either defend itself or make changes.

0:25:32.000 --> 0:25:34.600
<v Speaker 1>But the European Commission says that if the findings of

0:25:34.640 --> 0:25:38.160
<v Speaker 1>the investigation hold up to scrutiny, X will be fined

0:25:38.240 --> 0:25:41.680
<v Speaker 1>and forced to change should it continue to operate within

0:25:41.720 --> 0:25:46.320
<v Speaker 1>the EU. So yeah, tough news for X. Moving on

0:25:46.440 --> 0:25:49.960
<v Speaker 1>to a different Elon Musk led company, According to Bloomberg,

0:25:50.119 --> 0:25:53.280
<v Speaker 1>Tesla has had to make an adjustment to its schedule,

0:25:53.440 --> 0:25:56.920
<v Speaker 1>which doesn't surprise me even a little bit. So several

0:25:56.920 --> 0:26:00.280
<v Speaker 1>months ago, back in April, Elon Musk gave August eighth

0:26:00.520 --> 0:26:03.760
<v Speaker 1>as a date at which time Tesla would unveil its

0:26:03.960 --> 0:26:07.560
<v Speaker 1>Robotaxi business. Now, this was during the same earnings call

0:26:07.600 --> 0:26:11.280
<v Speaker 1>in which Musk also told everybody that Tesla would no

0:26:11.359 --> 0:26:14.760
<v Speaker 1>longer work toward releasing a low cost electric vehicle, which

0:26:14.840 --> 0:26:17.840
<v Speaker 1>was a big blow. But you know, the Robotaxi thing

0:26:17.920 --> 0:26:20.919
<v Speaker 1>was meant to kind of shift focus, I think, and

0:26:21.040 --> 0:26:25.240
<v Speaker 1>to reframe Tesla as being more than an electric vehicle company.

0:26:25.320 --> 0:26:27.560
<v Speaker 1>Like Musk has said that you should think of Tesla

0:26:27.600 --> 0:26:31.800
<v Speaker 1>as an AI and robotics company. Now Tesla says it

0:26:31.840 --> 0:26:35.520
<v Speaker 1>has had to delay the event and push it back

0:26:35.600 --> 0:26:39.240
<v Speaker 1>to October because it turns out building autonomous taxis is

0:26:39.280 --> 0:26:42.080
<v Speaker 1>actually really hard, which is something I think most people

0:26:42.160 --> 0:26:45.399
<v Speaker 1>already understood. I mean, we've heard plenty of stories about

0:26:45.400 --> 0:26:49.560
<v Speaker 1>how other robotaxi services have encountered issues, and goodness knows,

0:26:49.560 --> 0:26:54.200
<v Speaker 1>there's no shortage of issues with Tesla's own autonomous offerings.

0:26:54.200 --> 0:26:58.520
<v Speaker 1>I'm speaking specifically about autopilot and full self driving mode.

0:26:58.680 --> 0:27:02.119
<v Speaker 1>So I wish to throw no shade at the engineers

0:27:02.160 --> 0:27:04.640
<v Speaker 1>over at Tesla who've been working on this. I think

0:27:04.720 --> 0:27:07.439
<v Speaker 1>instead this is more of a case of Elon Musk

0:27:07.680 --> 0:27:12.840
<v Speaker 1>proposing an overly aggressive time table for a launch, something

0:27:12.880 --> 0:27:15.760
<v Speaker 1>he's done a few times in the past, possibly as

0:27:15.800 --> 0:27:18.679
<v Speaker 1>an effort to soften the blow of harder news, in

0:27:18.720 --> 0:27:21.520
<v Speaker 1>this case canceling a low cost EV that was something

0:27:21.520 --> 0:27:24.760
<v Speaker 1>that investors thought would really help push Tesla to the

0:27:24.760 --> 0:27:28.800
<v Speaker 1>next level, and it clearly is not gonna happen. So

0:27:29.880 --> 0:27:31.880
<v Speaker 1>it could be that you could argue the August eighth

0:27:31.880 --> 0:27:33.920
<v Speaker 1>thing was kind of a hail Mary pass to get

0:27:33.960 --> 0:27:38.159
<v Speaker 1>attention away from the low cost ev setback, and that

0:27:38.480 --> 0:27:42.919
<v Speaker 1>now we're just seeing that naturally that was too aggressive

0:27:43.880 --> 0:27:48.199
<v Speaker 1>a timetable, or it might be much more innocent than that.

0:27:48.440 --> 0:27:51.639
<v Speaker 1>I don't know. Well, we're going to take another quick break.

0:27:51.920 --> 0:28:04.240
<v Speaker 1>We will be back with some more tech news. Okay,

0:28:04.280 --> 0:28:09.280
<v Speaker 1>I'm back, so Kyle Barr of Gizmoto reports that analysts

0:28:09.320 --> 0:28:13.320
<v Speaker 1>are ringing the death knell for Apple Vision Pro sales.

0:28:13.440 --> 0:28:18.200
<v Speaker 1>That's Apple's mixed reality headset that they introduced earlier this year.

0:28:18.720 --> 0:28:21.560
<v Speaker 1>The analysts are saying that pretty much everyone who was

0:28:21.680 --> 0:28:23.920
<v Speaker 1>willing to fork over the cash for one of those

0:28:23.960 --> 0:28:28.320
<v Speaker 1>three five hundred dollars headsets now has one, and that

0:28:28.520 --> 0:28:31.639
<v Speaker 1>there just aren't other people who are willing to do that. So,

0:28:31.680 --> 0:28:34.840
<v Speaker 1>according to the analysts that bar sites, sales for the

0:28:34.840 --> 0:28:37.680
<v Speaker 1>rest of twenty twenty four are likely to be pretty

0:28:38.240 --> 0:28:42.200
<v Speaker 1>darn low that by August you're looking at a seventy

0:28:42.240 --> 0:28:46.600
<v Speaker 1>five percent drop off in sales. An analyst firm called

0:28:46.760 --> 0:28:50.400
<v Speaker 1>IDC reports that Apple has not yet sold one hundred

0:28:50.440 --> 0:28:54.280
<v Speaker 1>thousand units of the ding dang darn thing. Current estimations

0:28:54.320 --> 0:28:56.920
<v Speaker 1>say that's not really going to change for the rest

0:28:57.000 --> 0:29:00.480
<v Speaker 1>of this year, and in my opinion, the issue is twofold.

0:29:00.760 --> 0:29:04.760
<v Speaker 1>They are two main problems Apple faces with the Apple

0:29:04.840 --> 0:29:10.080
<v Speaker 1>Vision pro First off, it is undeniably really expensive, and

0:29:10.600 --> 0:29:13.880
<v Speaker 1>that is a big bar for entry, right like, not

0:29:13.960 --> 0:29:16.720
<v Speaker 1>a lot of people have thirty five hundred dollars to

0:29:16.880 --> 0:29:20.680
<v Speaker 1>drop on a tech toy. Let's be honest, it is

0:29:20.960 --> 0:29:23.960
<v Speaker 1>a toy right now. Because that brings us to problem

0:29:24.040 --> 0:29:27.680
<v Speaker 1>number two. There are a limited number of applications for

0:29:27.800 --> 0:29:31.320
<v Speaker 1>this technology as it stands right now. Now, I personally

0:29:31.360 --> 0:29:33.800
<v Speaker 1>have not had the chance to try out a headset.

0:29:34.040 --> 0:29:37.560
<v Speaker 1>From what I hear, it's a really impressive experience. The

0:29:37.640 --> 0:29:39.600
<v Speaker 1>problem is there's just not a whole lot you get

0:29:39.680 --> 0:29:43.640
<v Speaker 1>to do. The things it does are allegedly really incredible,

0:29:43.960 --> 0:29:47.560
<v Speaker 1>but they're also limited in number. Very few applications have

0:29:47.600 --> 0:29:51.800
<v Speaker 1>actually been developed for the platform itself. That actually makes

0:29:51.840 --> 0:29:54.920
<v Speaker 1>sense because they're such a small user base. Now I've

0:29:54.920 --> 0:29:58.360
<v Speaker 1>said this many times before, but if you are a developer,

0:29:58.720 --> 0:30:01.760
<v Speaker 1>you have to choose which platforms you're going to develop

0:30:02.000 --> 0:30:05.880
<v Speaker 1>four and from a financial standpoint, it only makes sense

0:30:05.920 --> 0:30:08.120
<v Speaker 1>to aim at platforms that are likely to see a

0:30:08.160 --> 0:30:11.560
<v Speaker 1>good return on investment. You want all that time and

0:30:11.720 --> 0:30:15.920
<v Speaker 1>effort that you're pouring into this development process to pay off.

0:30:16.240 --> 0:30:18.440
<v Speaker 1>So with that in mind, you want your work to

0:30:18.480 --> 0:30:22.360
<v Speaker 1>reach as many potential customers as possible, or a group

0:30:22.400 --> 0:30:26.200
<v Speaker 1>of customers who are more likely to spend money on

0:30:26.280 --> 0:30:29.040
<v Speaker 1>the thing you have made. That's not really a thing

0:30:29.120 --> 0:30:31.560
<v Speaker 1>if fewer than one hundred thousand people have even bought

0:30:31.600 --> 0:30:35.000
<v Speaker 1>into the platform. Apple is reportedly working on a lower

0:30:35.040 --> 0:30:39.280
<v Speaker 1>cost headset that would launch late next year. That could

0:30:39.360 --> 0:30:42.240
<v Speaker 1>potentially change things, but the cost needs to reach a

0:30:42.360 --> 0:30:46.360
<v Speaker 1>level where more curious people can actually afford it. So

0:30:46.640 --> 0:30:49.680
<v Speaker 1>even if you cut the price in half, that's really

0:30:49.680 --> 0:30:52.760
<v Speaker 1>not enough, right, Like, that's still like seventeen hundred dollars.

0:30:53.360 --> 0:30:55.760
<v Speaker 1>That's still a lot of money. So even cutting the

0:30:55.800 --> 0:30:58.800
<v Speaker 1>price in half is not likely to see a huge

0:30:59.320 --> 0:31:01.760
<v Speaker 1>rush of custom I mean, you'll probably see more than

0:31:01.800 --> 0:31:04.280
<v Speaker 1>you did with thirty five hundred, but I don't know.

0:31:05.080 --> 0:31:08.080
<v Speaker 1>But this might be enough to be a tipping point

0:31:08.080 --> 0:31:11.200
<v Speaker 1>for developers. We might see more developers willing to spend

0:31:11.200 --> 0:31:14.720
<v Speaker 1>the time and effort it takes to create things, specifically

0:31:14.760 --> 0:31:18.880
<v Speaker 1>for the Vision platform, and maybe then we'll see some

0:31:18.920 --> 0:31:22.920
<v Speaker 1>really innovative uses of augmented reality and virtual reality and

0:31:23.040 --> 0:31:25.280
<v Speaker 1>have those find their way to the headset. I would

0:31:25.280 --> 0:31:27.840
<v Speaker 1>actually love to see that happen, because as much as

0:31:27.920 --> 0:31:30.560
<v Speaker 1>I have dogged on Apple for the Vision pro, I

0:31:30.680 --> 0:31:35.080
<v Speaker 1>do think AR could be super cool if it's done correctly.

0:31:35.400 --> 0:31:38.600
<v Speaker 1>It's just really hard to do because typically it means

0:31:38.640 --> 0:31:42.080
<v Speaker 1>that people have to wear a bulky, power hungry headset

0:31:42.080 --> 0:31:45.280
<v Speaker 1>on their face, and that's a big ask, Like that's

0:31:45.280 --> 0:31:47.680
<v Speaker 1>asking a lot of folks to do that, and as

0:31:47.680 --> 0:31:51.120
<v Speaker 1>we've seen time and again, people are rarely willing to

0:31:51.240 --> 0:31:54.480
<v Speaker 1>do that unless it's for something very specific like gaming.

0:31:54.720 --> 0:31:58.280
<v Speaker 1>Right VR gaming is an exception, but most people, like

0:31:58.320 --> 0:32:00.760
<v Speaker 1>when it came to three D television, they weren't willing

0:32:00.840 --> 0:32:03.360
<v Speaker 1>to take that step. So it's going to take some

0:32:03.480 --> 0:32:08.360
<v Speaker 1>pretty compelling applications, I think, to win people over beyond

0:32:09.080 --> 0:32:13.080
<v Speaker 1>just you know, your pool of bleeding edge adopters. And

0:32:13.120 --> 0:32:16.160
<v Speaker 1>now for the cantankerous old coot section of our show,

0:32:16.520 --> 0:32:19.600
<v Speaker 1>I bring you my physical media is dying and I'm

0:32:19.680 --> 0:32:23.480
<v Speaker 1>mad about it. Rant I'm not the only one doing

0:32:23.520 --> 0:32:25.920
<v Speaker 1>the sort of ranting, by the way, Sharon Harding of

0:32:25.960 --> 0:32:29.320
<v Speaker 1>Ours Technica has a piece titled DVDs are dying right

0:32:29.400 --> 0:32:32.960
<v Speaker 1>as streaming has made them appealing again, and that piece

0:32:33.000 --> 0:32:35.920
<v Speaker 1>really goes into this so, as Harding points out, the

0:32:35.960 --> 0:32:39.560
<v Speaker 1>streaming landscape actually can make it harder if you are

0:32:39.600 --> 0:32:44.040
<v Speaker 1>a fan of specific stuff apart from original titles that

0:32:44.520 --> 0:32:47.880
<v Speaker 1>spawned out of these streaming platforms. It can be hard

0:32:47.880 --> 0:32:50.440
<v Speaker 1>to predict where stuff is going to end up. So

0:32:50.520 --> 0:32:53.800
<v Speaker 1>you might start watching, you know, a series on one

0:32:53.880 --> 0:32:57.120
<v Speaker 1>streaming platform and then it jumps ship to a different

0:32:57.120 --> 0:33:00.440
<v Speaker 1>streaming platform. If you're not a subscriber to this other service,

0:33:00.480 --> 0:33:02.560
<v Speaker 1>you're out of luck. This has happened to me on

0:33:02.680 --> 0:33:06.920
<v Speaker 1>multiple occasions. Worse yet, you can have a licensing agreement

0:33:07.120 --> 0:33:10.800
<v Speaker 1>expire and no one has the thing you wanted to watch.

0:33:11.120 --> 0:33:14.680
<v Speaker 1>So maybe you start a series, the licensing agreement expires,

0:33:14.920 --> 0:33:18.040
<v Speaker 1>the series disappears from that platform, no one else has

0:33:18.040 --> 0:33:20.280
<v Speaker 1>picked it up, and you're just left without being able

0:33:20.320 --> 0:33:25.040
<v Speaker 1>to watch it. That's really frustrating. Buying digital copies isn't

0:33:25.080 --> 0:33:27.640
<v Speaker 1>a guarantee to fix this, right, because there's always the

0:33:27.720 --> 0:33:32.120
<v Speaker 1>chance that the provider will stop supporting the service or

0:33:32.120 --> 0:33:34.880
<v Speaker 1>even go out of business. Then you're left without the

0:33:34.920 --> 0:33:37.280
<v Speaker 1>media that you have purchased, or rather the media that

0:33:37.320 --> 0:33:40.360
<v Speaker 1>you've paid to watch. I always think about that too,

0:33:40.480 --> 0:33:43.280
<v Speaker 1>like I have libraries of digital films that I like

0:33:43.480 --> 0:33:45.880
<v Speaker 1>to go to every now and again, but there's always

0:33:45.880 --> 0:33:49.080
<v Speaker 1>the chance that the company will just stop supporting that service,

0:33:49.240 --> 0:33:52.720
<v Speaker 1>and even though I have paid to access that media,

0:33:53.360 --> 0:33:56.200
<v Speaker 1>the service no longer will work and I won't be

0:33:56.200 --> 0:33:58.680
<v Speaker 1>able to watch the thing I paid for. So you

0:33:58.800 --> 0:34:02.720
<v Speaker 1>might turn to the solid of physical media like Blu

0:34:02.880 --> 0:34:05.840
<v Speaker 1>rays and DVDs, because then you can keep a copy

0:34:06.040 --> 0:34:08.719
<v Speaker 1>for yourself and no one is going to take that

0:34:08.840 --> 0:34:12.040
<v Speaker 1>away from you, except that physical media is dying out

0:34:12.080 --> 0:34:15.520
<v Speaker 1>too harding details how red Box, which is a DVD

0:34:15.680 --> 0:34:20.360
<v Speaker 1>rental service that operated red kiosks filled with DVDs across

0:34:20.400 --> 0:34:23.879
<v Speaker 1>the United States. Red Box is shutting down. It went

0:34:23.920 --> 0:34:27.360
<v Speaker 1>into bankruptcy initially went into chapter eleven. Now it's shifting

0:34:27.400 --> 0:34:31.279
<v Speaker 1>to chapter seven, which includes liquidation of all assets. I'm

0:34:31.280 --> 0:34:34.160
<v Speaker 1>sure Mike of Red Letter Media is distressed to really

0:34:34.160 --> 0:34:36.120
<v Speaker 1>hear about this one, because red Box is kind of

0:34:36.160 --> 0:34:41.040
<v Speaker 1>his go to for really trashy movies. The closure means

0:34:41.040 --> 0:34:45.280
<v Speaker 1>that twenty four thousand kiosks are shutting down, as will

0:34:45.400 --> 0:34:49.600
<v Speaker 1>the services that were operated by Redbox's parent company, Chicken Soup.

0:34:49.640 --> 0:34:54.360
<v Speaker 1>For the soul entertainment that includes services like Crackle and

0:34:54.480 --> 0:34:57.640
<v Speaker 1>Popcorn Flicks, they're also going bye by. So it's not

0:34:57.719 --> 0:35:00.520
<v Speaker 1>just the physical media. Some streaming media s business are

0:35:00.560 --> 0:35:04.640
<v Speaker 1>going way too. Meanwhile, big box stores are cutting back

0:35:04.680 --> 0:35:08.800
<v Speaker 1>on DVD sales and repurposing that floor space for other products.

0:35:09.000 --> 0:35:11.800
<v Speaker 1>Like Target, for example, is going to shift to a

0:35:11.840 --> 0:35:16.000
<v Speaker 1>strategy where they only offer DVDs seasonally and then the

0:35:16.040 --> 0:35:17.960
<v Speaker 1>rest of the time that space will be meant for

0:35:18.040 --> 0:35:21.640
<v Speaker 1>something else. Sony has announced it's going to stop producing

0:35:21.760 --> 0:35:25.280
<v Speaker 1>recordable Blu ray discs in the near future, and Harding

0:35:25.280 --> 0:35:28.080
<v Speaker 1>does a really great job of explaining the reasoning behind

0:35:28.160 --> 0:35:31.520
<v Speaker 1>why all these shifts are happening, Because the numbers don't

0:35:31.560 --> 0:35:35.439
<v Speaker 1>lie and physical media is far less profitable these days.

0:35:35.440 --> 0:35:39.320
<v Speaker 1>There's just fewer people buying physical media, but considering the

0:35:39.440 --> 0:35:42.600
<v Speaker 1>chaos that is streaming, this means consumers will have fewer

0:35:42.640 --> 0:35:45.840
<v Speaker 1>options when it comes to ensuring that they have access

0:35:45.840 --> 0:35:48.520
<v Speaker 1>to the media they love. Heck, over the last couple

0:35:48.560 --> 0:35:51.560
<v Speaker 1>of years, I've actually started collecting physical media again. I

0:35:51.640 --> 0:35:54.600
<v Speaker 1>had kind of shifted away from that for quite some time,

0:35:54.880 --> 0:35:57.320
<v Speaker 1>but I'm back to it now and it's largely because

0:35:57.360 --> 0:36:00.520
<v Speaker 1>of this issue. I even belong to a monthly horror

0:36:00.560 --> 0:36:04.319
<v Speaker 1>movie club where I get four discs per month. And

0:36:04.360 --> 0:36:07.200
<v Speaker 1>for folks like me, this trend is pretty sad and

0:36:07.280 --> 0:36:10.640
<v Speaker 1>also frustrating. It's also totally understandable. It's not like I

0:36:10.880 --> 0:36:14.840
<v Speaker 1>fault the companies for doing this. I don't expect companies

0:36:14.880 --> 0:36:18.400
<v Speaker 1>to continue to manufacture physical discs at a loss, but

0:36:18.600 --> 0:36:21.520
<v Speaker 1>the fact is we're seeing this move away from physical

0:36:21.560 --> 0:36:26.880
<v Speaker 1>media entirely while simultaneously dealing with the constantly shifting landscape

0:36:26.920 --> 0:36:31.080
<v Speaker 1>of streaming, and that stinks. Speaking of physical media, the

0:36:31.160 --> 0:36:34.759
<v Speaker 1>German Navy is looking to phase out a legacy technology

0:36:34.800 --> 0:36:38.360
<v Speaker 1>for its fleet of anti submarine frigates. See. These ships

0:36:38.400 --> 0:36:41.400
<v Speaker 1>currently rely on the storage system that saves data to

0:36:41.880 --> 0:36:46.439
<v Speaker 1>eight inch floppy discs. Yeah, floppy discs. I wager there's

0:36:46.440 --> 0:36:49.920
<v Speaker 1>some of y'all out there who have never even used

0:36:50.000 --> 0:36:52.920
<v Speaker 1>floppy discs. I grew up using five and a quarter

0:36:53.000 --> 0:36:55.719
<v Speaker 1>and then later three and a half inch floppies. There

0:36:55.760 --> 0:37:00.000
<v Speaker 1>are people older than me who used much larger floppy discs.

0:37:00.120 --> 0:37:03.320
<v Speaker 1>Apart from an escape room that I participated in recently.

0:37:03.360 --> 0:37:06.160
<v Speaker 1>I haven't touched a floppy disk in years. It's kind

0:37:06.200 --> 0:37:08.560
<v Speaker 1>of crazy to think that the German Navy is still

0:37:08.600 --> 0:37:12.480
<v Speaker 1>running equipment that relies on this legacy technology. Some would

0:37:12.520 --> 0:37:15.839
<v Speaker 1>call it an obsolete technology, but here we are moving

0:37:15.880 --> 0:37:20.120
<v Speaker 1>stuff to a new system. Isn't easy. Modernizing hardware requires

0:37:20.200 --> 0:37:23.680
<v Speaker 1>a lot of considerations because changing one thing can sometimes

0:37:23.719 --> 0:37:27.600
<v Speaker 1>break something else. According to the site Tom's Hardware, the

0:37:27.680 --> 0:37:30.680
<v Speaker 1>German Navy is looking at an emulator to provide the

0:37:30.760 --> 0:37:34.239
<v Speaker 1>same kind of storage and data retrieval services as the

0:37:34.280 --> 0:37:37.880
<v Speaker 1>floppy disk system did, and that means the Navy won't

0:37:37.920 --> 0:37:41.319
<v Speaker 1>have to retool their entire process. The emulator would serve

0:37:41.360 --> 0:37:44.279
<v Speaker 1>as a substitute for the floppy drive, but otherwise things

0:37:44.320 --> 0:37:47.160
<v Speaker 1>would largely operate the same way they have for years.

0:37:47.560 --> 0:37:50.279
<v Speaker 1>Kind of wild that we're into twenty twenty four and

0:37:50.320 --> 0:37:54.680
<v Speaker 1>this is finally being addressed. Hurricane Beryl packed a heck

0:37:54.760 --> 0:37:57.760
<v Speaker 1>of a wallop when it landed in Texas earlier this week.

0:37:58.000 --> 0:38:00.640
<v Speaker 1>The storm knocked out power for nearly two two million

0:38:00.719 --> 0:38:05.160
<v Speaker 1>Houston residents. Meanwhile, a massive heat wave created really dangerous

0:38:05.160 --> 0:38:08.200
<v Speaker 1>situations for folks living in the Houston area. Not only

0:38:08.200 --> 0:38:11.200
<v Speaker 1>did they have to deal with flooding and other damage

0:38:11.200 --> 0:38:14.880
<v Speaker 1>from the hurricane, but the temperatures and humidity meant that

0:38:15.040 --> 0:38:18.440
<v Speaker 1>going without power and access to air conditioning was like

0:38:18.520 --> 0:38:22.560
<v Speaker 1>a real health hazard, making matters more complicated than necessary

0:38:22.800 --> 0:38:25.840
<v Speaker 1>would be. Center Point Energy, a utility company in the

0:38:25.880 --> 0:38:30.000
<v Speaker 1>Houston area, Texas, famously is not part of the US

0:38:30.120 --> 0:38:34.240
<v Speaker 1>National Power Grid. Texas opted to go at lone wolf style,

0:38:34.440 --> 0:38:37.360
<v Speaker 1>which frequently does not work out so great for the

0:38:37.440 --> 0:38:40.680
<v Speaker 1>residents of Texas, but it seems to make business executives

0:38:40.680 --> 0:38:44.480
<v Speaker 1>and local politicians a whole lot of money anyway. Center

0:38:44.560 --> 0:38:48.440
<v Speaker 1>Point Energy doesn't have a dedicated app, so Houston citizens

0:38:48.480 --> 0:38:50.760
<v Speaker 1>began to turn to a different app in an effort

0:38:51.000 --> 0:38:54.759
<v Speaker 1>to get information about where power outages currently are in

0:38:54.800 --> 0:38:57.560
<v Speaker 1>the city. That app happens to belong to the fast

0:38:57.600 --> 0:39:02.200
<v Speaker 1>food chain WAA Burger. Waaburger's app includes a map that

0:39:02.280 --> 0:39:06.400
<v Speaker 1>shows all local Waterburger locations within the Houston area, and

0:39:06.480 --> 0:39:09.040
<v Speaker 1>there's an icon that indicates whether or not the store

0:39:09.200 --> 0:39:12.280
<v Speaker 1>is open. So by opening up the map and seeing

0:39:12.320 --> 0:39:16.000
<v Speaker 1>where stores are closed and where they're open, Houston citizens

0:39:16.000 --> 0:39:18.600
<v Speaker 1>could actually figure out which regions were still affected by

0:39:18.600 --> 0:39:22.120
<v Speaker 1>power allagies because the ones that have power allagies. Clearly

0:39:22.200 --> 0:39:25.240
<v Speaker 1>those restaurants aren't going to be open. So users shared

0:39:25.280 --> 0:39:29.000
<v Speaker 1>this discovery on x and subsequently Waaburger's app saw a

0:39:29.080 --> 0:39:33.120
<v Speaker 1>flurry of downloads. It went from being fortieth on iOS's

0:39:33.160 --> 0:39:38.440
<v Speaker 1>app store to sixteenth. Necessity is the Mother of Invention. Waaburger,

0:39:38.480 --> 0:39:42.120
<v Speaker 1>for its part, has responded by saying they never intended

0:39:42.120 --> 0:39:43.960
<v Speaker 1>their app to be used this way, and they really

0:39:44.040 --> 0:39:47.440
<v Speaker 1>hope that people are safe. Like they're not objecting to

0:39:47.440 --> 0:39:50.120
<v Speaker 1>the app being used this way, they're showing their concern

0:39:50.280 --> 0:39:54.600
<v Speaker 1>for the community. Researchers have created a urine processing system

0:39:54.640 --> 0:39:57.440
<v Speaker 1>meant for space suits, similar to this still suits in

0:39:57.480 --> 0:40:01.239
<v Speaker 1>the science fiction series Doom. The researchers have created a

0:40:01.280 --> 0:40:05.960
<v Speaker 1>system that includes a quote vacuum based external catheter leading

0:40:06.000 --> 0:40:10.000
<v Speaker 1>to a combined forward reverse osmosis unit end quote in

0:40:10.080 --> 0:40:13.720
<v Speaker 1>order to take an astronaut's urine, remove all the yucky bits,

0:40:13.960 --> 0:40:16.920
<v Speaker 1>and purify it into drinkable water. And it's said to

0:40:16.960 --> 0:40:19.880
<v Speaker 1>be eighty seven percent efficient, so I assume that means

0:40:20.120 --> 0:40:22.920
<v Speaker 1>it can reclaim about eighty seven percent of the water

0:40:23.080 --> 0:40:25.960
<v Speaker 1>content in urine. That means you can pee and in

0:40:26.000 --> 0:40:29.640
<v Speaker 1>about five minutes enjoy a refreshing beverage made from your pee.

0:40:30.080 --> 0:40:32.600
<v Speaker 1>I'm being a little cheeky about this because we all

0:40:32.640 --> 0:40:35.600
<v Speaker 1>need to remember all the water of our planet has

0:40:35.680 --> 0:40:39.840
<v Speaker 1>been here for millions of years, hundreds of millions of years.

0:40:40.040 --> 0:40:42.239
<v Speaker 1>For us, water is kind of like the force. It

0:40:42.320 --> 0:40:46.120
<v Speaker 1>binds us and penetrates us and moves through us. Sometimes

0:40:46.160 --> 0:40:47.879
<v Speaker 1>it moves through us in the middle of a Peter

0:40:48.000 --> 0:40:50.120
<v Speaker 1>Jackson movie. He really needs to make his films less

0:40:50.120 --> 0:40:53.120
<v Speaker 1>than four hours long. Anyway. I think most folks are

0:40:53.160 --> 0:40:56.520
<v Speaker 1>aware that water purification is a thing. We depend on

0:40:56.600 --> 0:41:01.080
<v Speaker 1>water purification already, right, like we process waste water so

0:41:01.120 --> 0:41:04.840
<v Speaker 1>that we can then purify it and make it drinkable

0:41:04.880 --> 0:41:07.359
<v Speaker 1>and usable. Again, it's just a little freaky to think

0:41:07.400 --> 0:41:11.239
<v Speaker 1>of it as a miniaturized system that's wearable and that

0:41:11.320 --> 0:41:14.720
<v Speaker 1>you could complete this purification process in less than ten minutes.

0:41:15.000 --> 0:41:17.840
<v Speaker 1>The system will undoubtedly be handy if we ever do

0:41:17.960 --> 0:41:20.840
<v Speaker 1>figure out a safe way to send astronauts on longer

0:41:20.880 --> 0:41:24.080
<v Speaker 1>space missions like to Mars and such. This kind of

0:41:24.080 --> 0:41:26.520
<v Speaker 1>thing will be necessary in order to be able to

0:41:26.560 --> 0:41:29.680
<v Speaker 1>process the water that is brought on board and to

0:41:29.800 --> 0:41:33.560
<v Speaker 1>maximize it to use it as long as is possible.

0:41:33.920 --> 0:41:37.600
<v Speaker 1>Because every bit of weight that you add to a

0:41:37.680 --> 0:41:41.839
<v Speaker 1>space mission requires more energy to get that thing off

0:41:41.920 --> 0:41:46.319
<v Speaker 1>the planet. So these considerations are challenging. You have to

0:41:46.360 --> 0:41:48.840
<v Speaker 1>have ways to be able to process this stuff, and

0:41:48.880 --> 0:41:52.919
<v Speaker 1>to do so while it's worked within a suit means

0:41:52.920 --> 0:41:55.040
<v Speaker 1>that you can do it even if someone has gone

0:41:55.160 --> 0:41:58.640
<v Speaker 1>out on a spacewalk mission. You know, when you're on

0:41:58.719 --> 0:42:01.799
<v Speaker 1>board a spacecraft or in the space station using the

0:42:01.880 --> 0:42:04.879
<v Speaker 1>onboard facilities whenever you need to use the bathroom that

0:42:05.360 --> 0:42:09.520
<v Speaker 1>has these sort of reclamation systems built into it already.

0:42:10.120 --> 0:42:13.120
<v Speaker 1>But if you're doing something that's just in the suit,

0:42:13.600 --> 0:42:17.840
<v Speaker 1>then typically what you're really relying upon is essentially a diaper.

0:42:18.239 --> 0:42:22.480
<v Speaker 1>So this kind of system opens up the capacity for

0:42:22.920 --> 0:42:27.520
<v Speaker 1>recapturing water from waste even when you're out on a

0:42:27.560 --> 0:42:31.319
<v Speaker 1>spacewalk and you're not inside a spacecraft. Okay, I've got

0:42:31.360 --> 0:42:33.680
<v Speaker 1>a couple of article recommendations for you all this week.

0:42:33.719 --> 0:42:37.080
<v Speaker 1>First up is Samuel Aksen's piece for Ours Technica. It

0:42:37.160 --> 0:42:41.800
<v Speaker 1>is titled shady company relaunches popular old tech blogs steals

0:42:41.920 --> 0:42:49.000
<v Speaker 1>writer's identities yuck. Okay, so apparently this web advertising company

0:42:49.280 --> 0:42:53.439
<v Speaker 1>has resurrected some dead blogs blogs that used to be

0:42:53.560 --> 0:42:56.440
<v Speaker 1>active on the Internet but haven't been for years, and

0:42:56.719 --> 0:43:00.680
<v Speaker 1>are using AI to pose as the people who originally

0:43:00.680 --> 0:43:05.160
<v Speaker 1>contributed to those blogs, and thus churning out garbage articles

0:43:05.400 --> 0:43:11.200
<v Speaker 1>with the bylines of people who aren't actually creating that work. Clearly,

0:43:11.680 --> 0:43:15.520
<v Speaker 1>this is unethical, Like, there's no question this is unethical.

0:43:15.800 --> 0:43:17.960
<v Speaker 1>If you were one of those writers and you started

0:43:17.960 --> 0:43:20.920
<v Speaker 1>to see junk getting pushed out with your name attached

0:43:20.920 --> 0:43:23.560
<v Speaker 1>to it, that would be bad because imagine that you're

0:43:23.600 --> 0:43:26.880
<v Speaker 1>applying for a job and your potential employer has researched

0:43:26.920 --> 0:43:30.600
<v Speaker 1>you and just found all these articles that are just terrible.

0:43:30.680 --> 0:43:33.799
<v Speaker 1>They're subpar, and they have your name attached to it,

0:43:34.000 --> 0:43:37.040
<v Speaker 1>but it wasn't written by you. That would be really awful.

0:43:37.280 --> 0:43:39.759
<v Speaker 1>As someone who used to write for a website, you know,

0:43:39.760 --> 0:43:42.760
<v Speaker 1>a website that notably dumped its editorial staff in favor

0:43:42.800 --> 0:43:46.200
<v Speaker 1>of AI generated pieces, I definitely have concerns about this

0:43:46.320 --> 0:43:48.600
<v Speaker 1>kind of thing. So yeah, I think it's well worth

0:43:48.640 --> 0:43:51.760
<v Speaker 1>a read. Next up, there's a piece by Sky Jacobs

0:43:51.800 --> 0:43:54.319
<v Speaker 1>of tech Spot. It is titled why you should be

0:43:54.360 --> 0:43:59.319
<v Speaker 1>Suspicious of that verified Amazon customer review. It examined something

0:43:59.360 --> 0:44:01.839
<v Speaker 1>I think a lot of people had already suspected that

0:44:02.000 --> 0:44:05.080
<v Speaker 1>those reviews you see on Amazon listings, even from supposed

0:44:05.160 --> 0:44:09.120
<v Speaker 1>trusted consumers, are sometimes just bought and paid for by

0:44:09.200 --> 0:44:12.760
<v Speaker 1>various merchants, meaning you can't trust the reviews, which strikes

0:44:12.840 --> 0:44:16.280
<v Speaker 1>right at the heart of one of Amazon's most valuable contributions.

0:44:16.280 --> 0:44:18.960
<v Speaker 1>In fact, I think customer reviews are part of what

0:44:19.120 --> 0:44:22.480
<v Speaker 1>helped Amazon navigate the dot com bubble crisis in the

0:44:22.520 --> 0:44:26.600
<v Speaker 1>early two thousands. Anyway, both of those articles are well

0:44:26.640 --> 0:44:29.760
<v Speaker 1>worth your time and you should check those out. That's

0:44:29.800 --> 0:44:32.440
<v Speaker 1>it for the news this week. I'll chat with you

0:44:32.480 --> 0:44:37.120
<v Speaker 1>next week, probably about large language model collapse and how

0:44:37.239 --> 0:44:41.319
<v Speaker 1>AI training itself on other AI ultimately leads to a

0:44:41.880 --> 0:44:46.600
<v Speaker 1>desolate landscape of garbage content that's fun to talk about.

0:44:46.719 --> 0:44:48.480
<v Speaker 1>We'll chat about that next week, as well as some

0:44:48.520 --> 0:44:51.640
<v Speaker 1>other stuff. And I hope you have a fantastic weekend,

0:44:51.880 --> 0:45:01.160
<v Speaker 1>and I'll talk to you again really soon. Tech Stuff

0:45:01.239 --> 0:45:05.800
<v Speaker 1>is an iHeartRadio production. For more podcasts from iHeartRadio, visit

0:45:05.800 --> 0:45:09.360
<v Speaker 1>the iHeartRadio app, Apple Podcasts, or wherever you listen to

0:45:09.400 --> 0:45:10.360
<v Speaker 1>your favorite shows.