WEBVTT

NOTE
Transcription provided by Deepgram

00:00:00.799 --> 00:00:02.800
<v Speaker 0>Hello, and welcome to the Geek News Central

00:00:02.800 --> 00:00:06.720
<v Speaker 0>podcast episode eighteen fifty five. I'm tonight's host,

00:00:06.720 --> 00:00:08.960
<v Speaker 0>Ray Cochran. We've got a pretty great show

00:00:08.960 --> 00:00:11.920
<v Speaker 0>lined up for you folks tonight. Leading off,

00:00:11.920 --> 00:00:15.165
<v Speaker 0>a bombshell three year investigation from the Associated

00:00:15.305 --> 00:00:19.564
<v Speaker 0>Press reveals how Silicon Valley giants IBM, Intel,

00:00:19.945 --> 00:00:23.465
<v Speaker 0>NVIDIA, Oracle, and more spent decades selling the

00:00:23.465 --> 00:00:27.280
<v Speaker 0>technology that built tech China's surveillance state. We're

00:00:27.280 --> 00:00:30.980
<v Speaker 0>talking facial recognition, predictive policing, and the infrastructure

00:00:31.120 --> 00:00:35.600
<v Speaker 0>that enabled mass detention in Xinjiang. This one's

00:00:35.600 --> 00:00:39.300
<v Speaker 0>a gut punch, folks. Also on the show,

00:00:39.520 --> 00:00:43.295
<v Speaker 0>malicious Chrome extensions, stealing credentials from over a

00:00:43.295 --> 00:00:46.835
<v Speaker 0>hundred seventy sites, Microsoft's ambitious plan to eliminate

00:00:47.135 --> 00:00:49.295
<v Speaker 0>all c, c plus plus code by twenty

00:00:49.295 --> 00:00:53.295
<v Speaker 0>thirty. This one's speculative. And then China's combat

00:00:53.295 --> 00:00:56.415
<v Speaker 0>ready human robot humanoid robot that kicks its

00:00:56.415 --> 00:01:00.530
<v Speaker 0>CEO to prove it's real, and scientists running

00:01:00.530 --> 00:01:03.670
<v Speaker 0>the most detailed brain simulation ever on Japan's

00:01:04.130 --> 00:01:08.370
<v Speaker 0>supercomputer. Let's get into it. For the first

00:01:08.370 --> 00:01:11.784
<v Speaker 0>article from, the Associated Press, This one's written

00:01:11.784 --> 00:01:15.405
<v Speaker 0>by a few different, authors, David Goldman, Ing

00:01:15.865 --> 00:01:22.744
<v Speaker 0>Han Kuang, Felipe Dana, and, Dake Kang Dake

00:01:22.744 --> 00:01:25.065
<v Speaker 0>Kang. Thank you guys very much for the

00:01:25.065 --> 00:01:28.020
<v Speaker 0>article. But, it is a bit more of

00:01:28.020 --> 00:01:29.859
<v Speaker 0>a photo essay, so I definitely recommend you

00:01:29.859 --> 00:01:32.679
<v Speaker 0>guys tuning in to check this article out.

00:01:32.740 --> 00:01:35.380
<v Speaker 0>The images are, you know, mildly chilling, and

00:01:35.380 --> 00:01:39.955
<v Speaker 0>I understand that this maybe it's, seems a

00:01:39.955 --> 00:01:41.555
<v Speaker 0>lot more intense when you look at it

00:01:41.555 --> 00:01:44.755
<v Speaker 0>from this point of view, but it's crazy

00:01:44.755 --> 00:01:47.795
<v Speaker 0>to see the infrared dot images that are

00:01:47.795 --> 00:01:50.115
<v Speaker 0>scanning our faces every time we unlock our

00:01:50.115 --> 00:01:54.159
<v Speaker 0>phones. But, basically, over the last quarter century,

00:01:54.380 --> 00:01:57.420
<v Speaker 0>American technology companies have played a far greater

00:01:57.420 --> 00:01:59.979
<v Speaker 0>role than previously known in designing and building

00:01:59.979 --> 00:02:03.020
<v Speaker 0>China's surveillance state. The Associated Press conducted a

00:02:03.020 --> 00:02:05.500
<v Speaker 0>three year investigation based on tens of thousands

00:02:05.500 --> 00:02:08.144
<v Speaker 0>of leaked emails and databases from China's Chinese

00:02:08.144 --> 00:02:12.385
<v Speaker 0>surveillance companies, confidential corporate and government documents, public

00:02:12.385 --> 00:02:15.905
<v Speaker 0>marketing materials, procurement records, and interviews with over

00:02:15.905 --> 00:02:19.685
<v Speaker 0>a hundred current and former engineers, executive officials,

00:02:19.825 --> 00:02:23.610
<v Speaker 0>and police officers across three continents. The investigation

00:02:23.750 --> 00:02:28.890
<v Speaker 0>revealed that companies including IBM, Intel, NVIDIA, Oracle,

00:02:29.110 --> 00:02:33.350
<v Speaker 0>Dell, Microsoft, and Amazon Web Services, Thermo Fisher

00:02:33.350 --> 00:02:36.845
<v Speaker 0>Scientific, and others sold billions of dollars worth

00:02:36.845 --> 00:02:40.525
<v Speaker 0>of technology to Chinese police, government agencies, and

00:02:40.525 --> 00:02:43.965
<v Speaker 0>surveillance companies despite repeated warnings from congress and

00:02:43.965 --> 00:02:46.125
<v Speaker 0>media outlets about how these tools were being

00:02:46.125 --> 00:02:49.980
<v Speaker 0>used to quash dissent, persecute religious groups, and

00:02:49.980 --> 00:02:55.040
<v Speaker 0>target ethnic minorities. The foundation of Chinese surveillance

00:02:55.260 --> 00:02:57.980
<v Speaker 0>apparatus was built on American technology, particularly in

00:02:57.980 --> 00:03:01.055
<v Speaker 0>the far western region of Xinjiang, where it

00:03:01.055 --> 00:03:03.775
<v Speaker 0>enabled a brutal mass detention campaign targeting the

00:03:03.775 --> 00:03:10.015
<v Speaker 0>Uigh Uighur population. US companies brought predictive policing

00:03:10.015 --> 00:03:13.055
<v Speaker 0>technology to China, systems that analyze vast amounts

00:03:13.055 --> 00:03:17.400
<v Speaker 0>of data, including texts, calls, payments, videos, DNA,

00:03:17.540 --> 00:03:21.300
<v Speaker 0>and even utility usage to identify individuals deemed

00:03:21.300 --> 00:03:26.500
<v Speaker 0>suspicious and predict their movements. While the flood

00:03:26.500 --> 00:03:29.614
<v Speaker 0>of American technology slowed considerably starting in twenty

00:03:29.614 --> 00:03:33.155
<v Speaker 0>nineteen after international outrage and sanctions over atrocities

00:03:33.534 --> 00:03:36.915
<v Speaker 0>in Xinjiang, it had already laid the foundation

00:03:36.974 --> 00:03:39.295
<v Speaker 0>that Chinese companies have since built upon and,

00:03:39.295 --> 00:03:43.500
<v Speaker 0>in some cases, replaced. Even today, connections persist

00:03:43.500 --> 00:03:46.220
<v Speaker 0>between American tech and Chinese surveillance with companies

00:03:46.220 --> 00:03:49.019
<v Speaker 0>like Amazon Web Services offering cloud services to

00:03:49.019 --> 00:03:51.900
<v Speaker 0>Chinese surveillance giants despite them being on the

00:03:51.900 --> 00:03:55.885
<v Speaker 0>US commerce's US Commerce department's entity list for

00:03:55.885 --> 00:04:01.345
<v Speaker 0>national security and human rights concerns. Yeah. That

00:04:03.805 --> 00:04:06.205
<v Speaker 0>things the sick things that people do for

00:04:06.205 --> 00:04:10.710
<v Speaker 0>money. This this is just awful. The AP

00:04:10.710 --> 00:04:16.310
<v Speaker 0>investigation uncovered that these companies had basically supplied

00:04:16.310 --> 00:04:19.750
<v Speaker 0>critical infrastructure for China's digital police state. They

00:04:19.750 --> 00:04:24.535
<v Speaker 0>sold facial recognition system, AI powered cameras, predictive

00:04:24.595 --> 00:04:29.175
<v Speaker 0>policing software, cloud storage, DNA analysis kits, geographic

00:04:29.315 --> 00:04:32.355
<v Speaker 0>mapping tools specifically marketed for use by Chinese

00:04:32.355 --> 00:04:36.380
<v Speaker 0>police and surveillance agency. IBM, Dell, and Hitachi

00:04:36.520 --> 00:04:39.560
<v Speaker 0>promoted facial recognition for police use, while NVIDIA

00:04:39.560 --> 00:04:42.520
<v Speaker 0>and Intel partnered with China's three biggest surveillance

00:04:42.520 --> 00:04:45.479
<v Speaker 0>companies to add AI capabilities to camera systems

00:04:45.479 --> 00:04:49.100
<v Speaker 0>deployed across China, including in Xinjiang and Tibet.

00:04:50.065 --> 00:04:53.025
<v Speaker 0>Dell marketed a military grade AI powered laptop

00:04:53.025 --> 00:04:56.465
<v Speaker 0>with all race recognition capabilities to Chinese police

00:04:56.465 --> 00:05:00.305
<v Speaker 0>in twenty nineteen. Thermo Fisher Scientific marketed DNA

00:05:00.305 --> 00:05:02.705
<v Speaker 0>kits to Chinese police as designed for ethnic

00:05:02.705 --> 00:05:07.500
<v Speaker 0>minorities like Uyghurs and Tibetans. Oracle, HP, and

00:05:07.500 --> 00:05:10.880
<v Speaker 0>Esri sold geographic and mapping software allowing officers

00:05:10.940 --> 00:05:14.560
<v Speaker 0>to track when blacklisted individuals strayed from designated

00:05:15.100 --> 00:05:20.495
<v Speaker 0>areas. In Xinjiang specifically, this American technology enabled

00:05:20.495 --> 00:05:23.295
<v Speaker 0>the creation of a comprehensive surveillance system where

00:05:23.295 --> 00:05:26.515
<v Speaker 0>administrators assigned risk scores to residents with deductions

00:05:26.815 --> 00:05:29.695
<v Speaker 0>for factors like growing a beard, being between

00:05:29.695 --> 00:05:32.255
<v Speaker 0>fifteen and fifty five years old, or simply

00:05:32.255 --> 00:05:36.950
<v Speaker 0>being Uyghur. By twenty seventeen, the system flagged

00:05:37.010 --> 00:05:40.050
<v Speaker 0>twenty four thousand four hundred twelve people in

00:05:40.050 --> 00:05:42.710
<v Speaker 0>a single week, most of whom were detained.

00:05:43.330 --> 00:05:46.050
<v Speaker 0>Workers installed millions of cameras and wired over

00:05:46.050 --> 00:05:51.535
<v Speaker 0>seven thousand police outposts. The investigation also revealed

00:05:51.535 --> 00:05:55.535
<v Speaker 0>that across five presidential administrations, both Republican and

00:05:55.535 --> 00:05:59.055
<v Speaker 0>Democratic, the US government repeatedly allowed and even

00:05:59.055 --> 00:06:01.935
<v Speaker 0>actively helped American firms sell technology to Chinese

00:06:01.935 --> 00:06:05.350
<v Speaker 0>police and surveillance companies despite warnings about national

00:06:05.350 --> 00:06:08.790
<v Speaker 0>security and human rights abuses. The revelations have

00:06:08.790 --> 00:06:12.950
<v Speaker 0>prompted bipartisan calls from lawmakers, including senator Josh

00:06:12.950 --> 00:06:16.010
<v Speaker 0>Hawley, to subpoena tech companies and post stricter

00:06:16.390 --> 00:06:22.805
<v Speaker 0>export controls. Man, I'm sure for a lot

00:06:22.805 --> 00:06:24.824
<v Speaker 0>of you long time listeners to the show,

00:06:26.724 --> 00:06:29.065
<v Speaker 0>that have kind of been through some of

00:06:29.365 --> 00:06:32.965
<v Speaker 0>my dad's opinions, and maybe even align with

00:06:32.965 --> 00:06:35.479
<v Speaker 0>that. Yeah. You you might find this one

00:06:35.479 --> 00:06:43.080
<v Speaker 0>to be pretty crazy. It yeah. Well, maybe

00:06:43.080 --> 00:06:45.259
<v Speaker 0>not crazy. It's it's maybe it's something that

00:06:45.400 --> 00:06:47.580
<v Speaker 0>we do a little bit too often here.

00:06:50.215 --> 00:06:51.895
<v Speaker 0>Trying to get a a little bit extra

00:06:51.895 --> 00:06:54.315
<v Speaker 0>dough, I guess, here in the US. Jesus.

00:06:54.615 --> 00:06:59.655
<v Speaker 0>This is just but, you know, this this

00:06:59.655 --> 00:07:02.750
<v Speaker 0>kind of investigation raises critical questions about, like,

00:07:02.750 --> 00:07:06.030
<v Speaker 0>corporate responsibility, you know, global impact of, like,

00:07:06.030 --> 00:07:10.050
<v Speaker 0>technology sales. When American companies sell surveillance technology

00:07:10.110 --> 00:07:13.950
<v Speaker 0>to authoritarian regimes, aren't aren't aren't we becoming

00:07:13.950 --> 00:07:16.765
<v Speaker 0>complicit in those human rights abuses even if

00:07:16.765 --> 00:07:19.405
<v Speaker 0>the abuses occurred, like, across an ocean that's

00:07:19.405 --> 00:07:21.965
<v Speaker 0>on our continent? It's it's really easy to

00:07:21.965 --> 00:07:24.925
<v Speaker 0>take a blind eye to these to what's

00:07:24.925 --> 00:07:28.225
<v Speaker 0>happening when we're the ones enabling it realistically.

00:07:29.610 --> 00:07:31.770
<v Speaker 0>And I don't mean we by us personally,

00:07:31.770 --> 00:07:39.370
<v Speaker 0>but we, the American people. The technology for

00:07:39.370 --> 00:07:42.170
<v Speaker 0>market access bargain that Silicon Valley struck with

00:07:42.170 --> 00:07:46.245
<v Speaker 0>Beijing has had devastating real world consequences for

00:07:46.245 --> 00:07:51.125
<v Speaker 0>millions of peoples or people. Yeah. Especially the

00:07:51.125 --> 00:07:54.245
<v Speaker 0>Uyghur population. I think that's really tragic. I

00:07:54.245 --> 00:07:55.724
<v Speaker 0>think I a few years back, I saw

00:07:55.724 --> 00:07:58.620
<v Speaker 0>a lot of images of just, like, weird

00:07:58.620 --> 00:08:01.680
<v Speaker 0>people lined up, you know, on their knees,

00:08:01.980 --> 00:08:04.460
<v Speaker 0>on, like, like, just, like, concrete floor. It's

00:08:04.460 --> 00:08:09.680
<v Speaker 0>just like a horrible imagery, but I digress.

00:08:10.540 --> 00:08:12.540
<v Speaker 0>Sorry. It's a really heavy heavy one to

00:08:12.540 --> 00:08:16.514
<v Speaker 0>lead with, but I think it's pretty crazy

00:08:16.514 --> 00:08:17.955
<v Speaker 0>to think, you know, just like even over

00:08:17.955 --> 00:08:19.634
<v Speaker 0>just, like, the last quarter century, you know,

00:08:19.634 --> 00:08:23.955
<v Speaker 0>we we were the ones saying all these

00:08:23.955 --> 00:08:28.889
<v Speaker 0>bad things about how the surveillance over there

00:08:28.889 --> 00:08:32.970
<v Speaker 0>is too much, saying, you know, it's crazy

00:08:32.970 --> 00:08:34.970
<v Speaker 0>to have a social score, and yet we're

00:08:34.970 --> 00:08:37.630
<v Speaker 0>the ones enabling it. You know? Who knows?

00:08:37.850 --> 00:08:39.690
<v Speaker 0>We probably have all that here too, just

00:08:39.690 --> 00:08:44.135
<v Speaker 0>not not that we know of. Well, let's

00:08:44.135 --> 00:08:46.055
<v Speaker 0>move on. Let's, let's let's hit a little

00:08:46.055 --> 00:08:48.215
<v Speaker 0>bit of lighter note. I wanna do a

00:08:48.215 --> 00:08:49.655
<v Speaker 0>little bit bit of a shout out to

00:08:49.655 --> 00:08:54.055
<v Speaker 0>our incredible sponsor at GoDaddy. Score exclusive deals

00:08:54.055 --> 00:08:56.215
<v Speaker 0>and discounts right now at geek new central

00:08:56.215 --> 00:08:58.500
<v Speaker 0>dot com forward slash GoDaddy. And to all

00:08:58.500 --> 00:09:00.740
<v Speaker 0>of you guys, our listeners, you are truly

00:09:00.740 --> 00:09:03.060
<v Speaker 0>the heartbeat of the show. If you wanna

00:09:03.060 --> 00:09:05.060
<v Speaker 0>support Geek News Central directly, head over to

00:09:05.060 --> 00:09:07.540
<v Speaker 0>geek new central dot com forward slash insider

00:09:07.540 --> 00:09:11.235
<v Speaker 0>and become a GNC insider. Grab yourself a

00:09:11.235 --> 00:09:13.555
<v Speaker 0>modern podcast app at podcast apps dot com

00:09:13.555 --> 00:09:16.834
<v Speaker 0>for the full next gen podcast experience. Of

00:09:16.834 --> 00:09:18.435
<v Speaker 0>course, you can check out the entire Geek

00:09:18.435 --> 00:09:20.995
<v Speaker 0>News Central universe at geek news central dot

00:09:20.995 --> 00:09:22.995
<v Speaker 0>com, where you'll find all our partner shows

00:09:22.995 --> 00:09:25.154
<v Speaker 0>and tons of great content published every single

00:09:25.154 --> 00:09:28.270
<v Speaker 0>week. Stay in the loop. Follow or subscribe

00:09:28.270 --> 00:09:30.590
<v Speaker 0>in your favorite podcast app. Lately, I've been

00:09:30.590 --> 00:09:34.270
<v Speaker 0>using, PocketCasts. That one has been pretty good

00:09:34.270 --> 00:09:39.085
<v Speaker 0>to me. But, yeah, follow us in your

00:09:39.165 --> 00:09:40.845
<v Speaker 0>or subscribe to us in your favorite podcast

00:09:40.845 --> 00:09:42.125
<v Speaker 0>app, and don't forget to sign up for

00:09:42.125 --> 00:09:43.965
<v Speaker 0>our newsletter, which I have not been sending

00:09:43.965 --> 00:09:47.245
<v Speaker 0>out. So, that one's not so pressing. But

00:09:47.245 --> 00:09:49.005
<v Speaker 0>do sign up so that when I do

00:09:49.005 --> 00:09:52.145
<v Speaker 0>get that all set back up again, properly,

00:09:52.205 --> 00:09:54.290
<v Speaker 0>we can hit you guys with a fresh

00:09:54.290 --> 00:09:57.810
<v Speaker 0>newsletter every time we drop a show. And

00:09:57.810 --> 00:09:59.330
<v Speaker 0>then you can always reach us directly at

00:09:59.330 --> 00:10:02.210
<v Speaker 0>geek news at g mail dot com. If

00:10:02.210 --> 00:10:04.450
<v Speaker 0>you wanna, you know, directly get talk to

00:10:04.450 --> 00:10:07.735
<v Speaker 0>us, give us some feedback, or give us

00:10:07.735 --> 00:10:09.175
<v Speaker 0>your opinions about, you know, any of the

00:10:09.175 --> 00:10:10.694
<v Speaker 0>topics on the show. We'd love to hear

00:10:10.694 --> 00:10:13.814
<v Speaker 0>from you guys. Definitely makes me feel good

00:10:13.814 --> 00:10:15.415
<v Speaker 0>when I when I pop open an email

00:10:15.415 --> 00:10:16.774
<v Speaker 0>from one of you folks and read what

00:10:16.774 --> 00:10:17.894
<v Speaker 0>you have to say about one of the

00:10:17.894 --> 00:10:20.134
<v Speaker 0>articles I talked about in the previous show.

00:10:20.134 --> 00:10:22.394
<v Speaker 0>Thank you again for continuing to reach out.

00:10:24.350 --> 00:10:25.870
<v Speaker 0>But we wanna take a moment to thank

00:10:25.870 --> 00:10:28.990
<v Speaker 0>our sponsor, GoDaddy. They've been with us for

00:10:28.990 --> 00:10:31.070
<v Speaker 0>a long, long time, as long as I

00:10:31.070 --> 00:10:33.630
<v Speaker 0>personally can remember, and their incredible support of

00:10:33.630 --> 00:10:35.710
<v Speaker 0>this podcast is what makes it possible for

00:10:35.710 --> 00:10:37.650
<v Speaker 0>us to keep doing what we love, continuing

00:10:37.710 --> 00:10:40.644
<v Speaker 0>on our father's legacy, and for for you

00:10:40.644 --> 00:10:42.245
<v Speaker 0>guys to hear what you guys love every

00:10:42.245 --> 00:10:45.685
<v Speaker 0>single week, some great tech news. If you're

00:10:45.685 --> 00:10:47.204
<v Speaker 0>ready to start your own website or even

00:10:47.204 --> 00:10:49.764
<v Speaker 0>launch a podcast, GoDaddy has you covered. At

00:10:49.764 --> 00:10:52.105
<v Speaker 0>geek news central dot com forward slash GoDaddy,

00:10:52.380 --> 00:10:54.300
<v Speaker 0>you'll find special promo codes that make it

00:10:54.300 --> 00:10:56.780
<v Speaker 0>easy and affordable to get started. And these

00:10:56.780 --> 00:10:59.260
<v Speaker 0>promo codes are not expiring, so I verify

00:10:59.260 --> 00:11:01.500
<v Speaker 0>them every single day. They're all up and

00:11:01.500 --> 00:11:03.660
<v Speaker 0>running. I've got, links to each one. So

00:11:03.660 --> 00:11:06.525
<v Speaker 0>definitely check out the site, geek new central

00:11:06.525 --> 00:11:08.085
<v Speaker 0>dot com forward slash godaddy if you're trying

00:11:08.085 --> 00:11:10.365
<v Speaker 0>to start on a website. Here are some

00:11:10.365 --> 00:11:13.085
<v Speaker 0>of the deals we offer. Economy hosting is

00:11:13.085 --> 00:11:14.765
<v Speaker 0>just six ninety nine a month. It's a

00:11:14.765 --> 00:11:16.525
<v Speaker 0>full year of hosting with a free domain

00:11:16.525 --> 00:11:20.670
<v Speaker 0>name, professional email, and a SSL certificate. If

00:11:20.670 --> 00:11:23.090
<v Speaker 0>you're like us, and you you like WordPress,

00:11:23.630 --> 00:11:25.870
<v Speaker 0>WordPress hosting is only twelve ninety nine a

00:11:25.870 --> 00:11:28.510
<v Speaker 0>month, including that same free domain name, email,

00:11:28.510 --> 00:11:33.150
<v Speaker 0>and SSL certificate. WordPress, I I think the

00:11:33.150 --> 00:11:35.685
<v Speaker 0>more I use it, the more I like

00:11:35.685 --> 00:11:40.404
<v Speaker 0>it, to some degree. It is an awesome,

00:11:40.404 --> 00:11:43.524
<v Speaker 0>awesome ecosystem just to easily get something like

00:11:43.524 --> 00:11:45.764
<v Speaker 0>a blog up and running, have a great

00:11:45.764 --> 00:11:48.245
<v Speaker 0>personal site available for people to come visit,

00:11:48.245 --> 00:11:49.605
<v Speaker 0>see what's going on with you and your

00:11:49.605 --> 00:11:51.790
<v Speaker 0>family. So So definitely check it definitely check

00:11:51.790 --> 00:11:54.830
<v Speaker 0>it out. It's a lot more private than

00:11:54.830 --> 00:11:57.570
<v Speaker 0>posting to a social media site. You know?

00:11:59.710 --> 00:12:01.490
<v Speaker 0>And if you just need a domain name,

00:12:01.630 --> 00:12:02.910
<v Speaker 0>you think this is a cool idea, you

00:12:02.910 --> 00:12:04.270
<v Speaker 0>wanna do it in the future, you don't

00:12:04.270 --> 00:12:06.644
<v Speaker 0>know how right now, no no problem. Just

00:12:06.644 --> 00:12:08.565
<v Speaker 0>grab a domain domain name for eleven ninety

00:12:08.565 --> 00:12:11.045
<v Speaker 0>nine. And, you know, if you're not super

00:12:11.045 --> 00:12:13.765
<v Speaker 0>tech savvy, GoDaddy also has a website builder

00:12:13.765 --> 00:12:15.365
<v Speaker 0>where you can get a free thirty day

00:12:15.365 --> 00:12:18.245
<v Speaker 0>trial on business our personal business and business

00:12:18.245 --> 00:12:21.020
<v Speaker 0>plus plans and get your website online in

00:12:21.020 --> 00:12:23.180
<v Speaker 0>no time. Website really only needs to be

00:12:23.180 --> 00:12:27.180
<v Speaker 0>built once. Right? Now I use GoDaddy's products

00:12:27.180 --> 00:12:28.940
<v Speaker 0>and services myself, and I can tell you

00:12:28.940 --> 00:12:32.115
<v Speaker 0>that their reliability is the real deal. Your

00:12:32.115 --> 00:12:34.835
<v Speaker 0>support of GoDaddy directly supports the show. So

00:12:34.835 --> 00:12:36.755
<v Speaker 0>please use our codes, click and save, and

00:12:36.755 --> 00:12:39.875
<v Speaker 0>help keep this independent podcast going strong. Share

00:12:39.875 --> 00:12:41.795
<v Speaker 0>those friends with friends and or share those

00:12:41.795 --> 00:12:43.475
<v Speaker 0>links with friends and family. I can share

00:12:43.475 --> 00:12:45.480
<v Speaker 0>your friends with your friends and family too.

00:12:45.560 --> 00:12:47.800
<v Speaker 0>But, every time one's used, it's like writing

00:12:47.800 --> 00:12:50.199
<v Speaker 0>a check to the show. We truly thank

00:12:50.199 --> 00:12:51.880
<v Speaker 0>you for supporting us here at GoDaddy or

00:12:51.880 --> 00:12:53.639
<v Speaker 0>at Geek New Central. Wow. I'm just tripping

00:12:53.639 --> 00:12:55.399
<v Speaker 0>over my words tonight. Thank you so much

00:12:55.399 --> 00:12:57.880
<v Speaker 0>for supporting us at Geek New Central. Huge

00:12:57.880 --> 00:13:00.605
<v Speaker 0>thanks to GoDaddy, and thank you for believing

00:13:00.605 --> 00:13:02.605
<v Speaker 0>in independent creators like us here at Geek

00:13:02.605 --> 00:13:05.725
<v Speaker 0>News Central dot com. Let's move on. Let's

00:13:05.725 --> 00:13:07.565
<v Speaker 0>see if I can get through this show

00:13:07.565 --> 00:13:11.025
<v Speaker 0>with, without tripping over all my words. Jeez.

00:13:11.325 --> 00:13:12.605
<v Speaker 0>Maybe I need some water. I gotta get

00:13:12.605 --> 00:13:25.710
<v Speaker 0>some water. Alright. Jesus. Okay. Alright. Jeez. Hopefully,

00:13:25.710 --> 00:13:27.490
<v Speaker 0>you guys didn't have to hear all that.

00:13:28.025 --> 00:13:32.505
<v Speaker 0>Let's move on. I did mention this in

00:13:32.505 --> 00:13:35.065
<v Speaker 0>the intro, but speaking of security concerns a

00:13:35.065 --> 00:13:38.045
<v Speaker 0>little bit closer to home, two Chrome extensions

00:13:38.105 --> 00:13:41.145
<v Speaker 0>were caught secretly stealing credentials from over one

00:13:41.145 --> 00:13:44.920
<v Speaker 0>hundred seventy sites. This one's from Hacker News

00:13:44.920 --> 00:13:49.820
<v Speaker 0>written by Ravi Lakshmanan. Thank you very much,

00:13:50.920 --> 00:13:56.140
<v Speaker 0>Ravi. But browser extensions have become a significant

00:13:56.394 --> 00:13:58.815
<v Speaker 0>security threat in twenty twenty five with multiple

00:13:58.875 --> 00:14:02.795
<v Speaker 0>large scale campaigns exposing millions of users to

00:14:02.795 --> 00:14:06.555
<v Speaker 0>data theft and surveillance. The ecosystem's vulnerability stems

00:14:06.555 --> 00:14:09.890
<v Speaker 0>from several systemic issues. Ninety nine percent of

00:14:09.890 --> 00:14:13.649
<v Speaker 0>enterprise users have browser extensions installed with fifty

00:14:13.649 --> 00:14:16.769
<v Speaker 0>two percent running more than ten extensions. Up

00:14:16.769 --> 00:14:19.649
<v Speaker 0>to fifty three percent of extensions in enterprise

00:14:19.649 --> 00:14:23.204
<v Speaker 0>environments have high or critical risk permissions, allowing

00:14:23.204 --> 00:14:27.285
<v Speaker 0>access to sensitive data like cookies, passwords, browsing

00:14:27.285 --> 00:14:30.904
<v Speaker 0>history, and web page contents. Perhaps most concerning,

00:14:31.204 --> 00:14:34.264
<v Speaker 0>fifty four percent of extensions are published anonymously

00:14:34.565 --> 00:14:37.410
<v Speaker 0>via Gmail accounts with seventy nine percent from

00:14:37.410 --> 00:14:41.010
<v Speaker 0>publishers who have released only one extension, making

00:14:41.010 --> 00:14:45.670
<v Speaker 0>trust assessment really challenging, which I can totally

00:14:45.810 --> 00:14:48.209
<v Speaker 0>understand. Now for those of you that are

00:14:48.209 --> 00:14:52.555
<v Speaker 0>generally using plugins on your browsers, how are

00:14:52.555 --> 00:14:54.875
<v Speaker 0>you determining that they're safe to use? What

00:14:54.875 --> 00:14:58.014
<v Speaker 0>types of plugins are you guys using that,

00:14:59.194 --> 00:15:02.074
<v Speaker 0>that these types of concerns are are, you

00:15:02.074 --> 00:15:05.320
<v Speaker 0>know, are even coming up? It's honestly kind

00:15:05.700 --> 00:15:10.340
<v Speaker 0>of freaky. I don't know. You I think

00:15:10.340 --> 00:15:14.660
<v Speaker 0>all my, extensions are from trusted providers that

00:15:14.660 --> 00:15:17.560
<v Speaker 0>I'm familiar with. I've never downloaded an extension

00:15:17.620 --> 00:15:24.265
<v Speaker 0>from, you know, someone that only has the

00:15:24.265 --> 00:15:29.065
<v Speaker 0>single extension and is unknown. So, you know,

00:15:29.065 --> 00:15:30.825
<v Speaker 0>an unknown name. I feel like I've only

00:15:30.825 --> 00:15:34.810
<v Speaker 0>ever downloaded, like, browser extensions from, like, official

00:15:35.029 --> 00:15:38.170
<v Speaker 0>providers, like, you know, like, Chrome extension or,

00:15:38.470 --> 00:15:41.130
<v Speaker 0>you know, this one's being distributed by Android

00:15:41.269 --> 00:15:44.845
<v Speaker 0>or something. I I don't know. But these

00:15:44.845 --> 00:15:47.185
<v Speaker 0>recent incidents highlight the scale of the problem.

00:15:48.125 --> 00:15:51.645
<v Speaker 0>So, the shady panda campaign spent seven years

00:15:51.645 --> 00:15:55.165
<v Speaker 0>publishing or acquiring harmless extensions, letting them run

00:15:55.165 --> 00:15:57.645
<v Speaker 0>clean to build trust and gain millions of

00:15:57.645 --> 00:16:01.129
<v Speaker 0>installs, then suddenly flipping them into malware via

00:16:01.129 --> 00:16:05.310
<v Speaker 0>silent updates, ultimately affecting four point three million

00:16:05.370 --> 00:16:08.170
<v Speaker 0>Chrome and Edge users. In late twenty twenty

00:16:08.170 --> 00:16:10.730
<v Speaker 0>four and early twenty twenty five, a phishing

00:16:10.730 --> 00:16:13.725
<v Speaker 0>campaign compromised developer accounts for at least thirty

00:16:13.725 --> 00:16:17.725
<v Speaker 0>five legitimate Chrome extensions, allowing attackers to inject

00:16:17.725 --> 00:16:20.765
<v Speaker 0>malicious code that stole cookies and access tokens

00:16:20.765 --> 00:16:23.885
<v Speaker 0>from over two point six million users. These

00:16:23.885 --> 00:16:27.245
<v Speaker 0>incidents demonstrate how attackers exploit the sleeper agent

00:16:27.245 --> 00:16:30.990
<v Speaker 0>strategy, maintaining legitimate extensions for years before weaponizing

00:16:31.130 --> 00:16:33.450
<v Speaker 0>them through updates that auto install across the

00:16:33.450 --> 00:16:36.170
<v Speaker 0>entire user base. That is brutal. How do

00:16:36.170 --> 00:16:40.589
<v Speaker 0>you even defend against that? It's actually brutal.

00:16:41.165 --> 00:16:43.884
<v Speaker 0>Security researchers at socket dot dev discovered two

00:16:43.884 --> 00:16:47.324
<v Speaker 0>malicious Chrome extensions, both named Phantom Shuttle, that

00:16:47.324 --> 00:16:49.504
<v Speaker 0>have been operating since at least twenty seventeen,

00:16:49.725 --> 00:16:53.279
<v Speaker 0>marketed as VPN and network testing tools while

00:16:53.279 --> 00:16:56.160
<v Speaker 0>secretly stealing credentials from over one hundred seventy

00:16:56.160 --> 00:17:00.160
<v Speaker 0>targeted websites. Extensions published by the same threat

00:17:00.160 --> 00:17:05.535
<v Speaker 0>actor using the email, the new one, the

00:17:05.535 --> 00:17:08.015
<v Speaker 0>new as in I knew, the new one

00:17:08.015 --> 00:17:14.175
<v Speaker 0>dot com at Gmail dot com, have have

00:17:14.175 --> 00:17:17.715
<v Speaker 0>accumulated over two thousand one hundred eighty users

00:17:18.220 --> 00:17:21.820
<v Speaker 0>who paid subscriptions ranging from nine point nine

00:17:21.820 --> 00:17:24.820
<v Speaker 0>to ninety five point nine Chinese yuan. So

00:17:24.820 --> 00:17:27.660
<v Speaker 0>a dollar forty or thirteen fifty USD, believing

00:17:27.660 --> 00:17:34.934
<v Speaker 0>they were purchasing legitimate VPN services. I don't

00:17:34.934 --> 00:17:40.054
<v Speaker 0>understand you people. The malicious code is cleverly

00:17:40.054 --> 00:17:43.575
<v Speaker 0>hidden by prepended to the legitimate hidden by

00:17:43.575 --> 00:17:47.070
<v Speaker 0>being prepended to the legitimate jQuery library, making

00:17:47.070 --> 00:17:52.590
<v Speaker 0>detection more difficult. Dude, these people are so

00:17:52.590 --> 00:17:55.470
<v Speaker 0>clever. It's it's insane. The attack operates through

00:17:55.470 --> 00:17:59.470
<v Speaker 0>sophisticated traffic interception. The extensions automatically inject hard

00:17:59.470 --> 00:18:03.675
<v Speaker 0>coded proxy credentials. Username top fanny, password nine

00:18:03.675 --> 00:18:06.655
<v Speaker 0>six three eight five two way, into every

00:18:06.795 --> 00:18:10.555
<v Speaker 0>HTTP authentication request without user knowledge, running all

00:18:10.555 --> 00:18:13.755
<v Speaker 0>browsing traffic through attacker controlled proxy servers hosted

00:18:13.755 --> 00:18:16.380
<v Speaker 0>on Alibaba Cloud. This creates a man in

00:18:16.380 --> 00:18:19.040
<v Speaker 0>the middle position allowing attackers to capture unencrypted

00:18:19.180 --> 00:18:23.340
<v Speaker 0>data, including passwords, form data, session cookies, and

00:18:23.340 --> 00:18:27.420
<v Speaker 0>browsing history. The hundred seventy domain target list

00:18:27.420 --> 00:18:31.705
<v Speaker 0>specifically focuses on high value development tools, Docker,

00:18:32.005 --> 00:18:37.145
<v Speaker 0>NPM registries, enterprise platforms like Cisco, IBM, VMware,

00:18:37.605 --> 00:18:41.045
<v Speaker 0>and social media sites. The extensions maintain a

00:18:41.045 --> 00:18:43.365
<v Speaker 0>sixty second heartbeat to their command and control

00:18:43.365 --> 00:18:47.160
<v Speaker 0>server at phantom shuttle dot space, continuously exfiltrating

00:18:47.300 --> 00:18:50.820
<v Speaker 0>user data. Most alarmingly, every five minutes, the

00:18:50.820 --> 00:18:54.500
<v Speaker 0>extensions send user email addresses and passwords in

00:18:54.500 --> 00:18:57.940
<v Speaker 0>plain text to the attacker infrastructure. As of

00:18:57.940 --> 00:19:00.945
<v Speaker 0>December twenty twenty three twenty twenty five, the

00:19:00.945 --> 00:19:05.125
<v Speaker 0>extensions remain operational in the Chrome Web Store

00:19:05.345 --> 00:19:07.985
<v Speaker 0>through though socket dot dev has submitted takedown

00:19:07.985 --> 00:19:17.170
<v Speaker 0>requests to Google's security team. What? Yeah. How

00:19:17.170 --> 00:19:19.010
<v Speaker 0>do you defend against something like this? You

00:19:19.010 --> 00:19:21.330
<v Speaker 0>know what I mean? How do you defend

00:19:21.330 --> 00:19:25.090
<v Speaker 0>against something like this? This incident kinda reveals

00:19:25.090 --> 00:19:27.330
<v Speaker 0>how browser extensions have evolved to the one

00:19:27.330 --> 00:19:30.165
<v Speaker 0>of the most dangerous attack vectors in modern

00:19:30.165 --> 00:19:34.645
<v Speaker 0>cybersecurity, particularly for developers and enterprise users. The

00:19:34.645 --> 00:19:37.285
<v Speaker 0>targeting of developer flat platforms and cloud consoles

00:19:37.285 --> 00:19:40.965
<v Speaker 0>is especially concerning because compromised developer credentials enable

00:19:40.965 --> 00:19:44.220
<v Speaker 0>supply chain attacks. When attackers gain access to

00:19:44.220 --> 00:19:47.980
<v Speaker 0>GitHub accounts, Docker registries, or MPM packages, they

00:19:47.980 --> 00:19:50.620
<v Speaker 0>can inject malicious code that proc propagates to

00:19:50.620 --> 00:19:53.820
<v Speaker 0>thousands or millions of downstream users. The fact

00:19:53.820 --> 00:19:57.260
<v Speaker 0>that these extensions operated undetected for potentially eight

00:19:57.260 --> 00:20:00.535
<v Speaker 0>years demonstrates a massive blind spot in both

00:20:00.535 --> 00:20:06.135
<v Speaker 0>individual security practices and platform oversight mechanisms. For

00:20:06.135 --> 00:20:08.715
<v Speaker 0>the average person, you know, this might illustrate

00:20:08.775 --> 00:20:10.934
<v Speaker 0>to you why the traditional just be careful

00:20:10.934 --> 00:20:14.110
<v Speaker 0>what you install advice is literally insufficient because,

00:20:14.110 --> 00:20:15.870
<v Speaker 0>you know, I was talking to Mac here

00:20:15.870 --> 00:20:17.549
<v Speaker 0>at the beginning, but then turns out that

00:20:17.549 --> 00:20:20.610
<v Speaker 0>they were, you know, that you're using sleepers

00:20:20.990 --> 00:20:24.110
<v Speaker 0>sleeper agent strategies. So, you know, these could

00:20:24.110 --> 00:20:26.830
<v Speaker 0>be apps that you see them on the

00:20:26.830 --> 00:20:29.295
<v Speaker 0>the the Chrome extension store and you see

00:20:29.535 --> 00:20:32.015
<v Speaker 0>thousands and thousands of people have installed it,

00:20:32.015 --> 00:20:35.215
<v Speaker 0>you inherently trust the the extension a little

00:20:35.215 --> 00:20:39.295
<v Speaker 0>bit more. So I'm sure I'm sure there's

00:20:39.295 --> 00:20:41.870
<v Speaker 0>at least one where, you know, it got

00:20:41.870 --> 00:20:48.210
<v Speaker 0>flipped on its head. Who knows? But, definitely

00:20:48.350 --> 00:20:54.030
<v Speaker 0>be careful installing extensions on your, browsers nowadays.

00:20:54.030 --> 00:20:55.870
<v Speaker 0>You know, you really wanna only have the

00:20:55.870 --> 00:20:59.045
<v Speaker 0>ones that are by trusted providers. And I

00:20:59.045 --> 00:21:03.045
<v Speaker 0>know that's easy to say, but but, I

00:21:03.045 --> 00:21:05.845
<v Speaker 0>mean, come on. They were these people were

00:21:05.845 --> 00:21:14.970
<v Speaker 0>already literally paying you on to someone. It's

00:21:14.970 --> 00:21:17.450
<v Speaker 0>like, it's out of country. You don't need

00:21:17.690 --> 00:21:19.370
<v Speaker 0>like, how can you trust any of the

00:21:19.370 --> 00:21:24.115
<v Speaker 0>services that are being sold there? So I

00:21:24.115 --> 00:21:26.115
<v Speaker 0>don't know. It's an interesting thing. It's it's

00:21:26.115 --> 00:21:29.174
<v Speaker 0>really hard to be able to diagnose whether

00:21:29.235 --> 00:21:31.794
<v Speaker 0>a business is trustable in the in the

00:21:31.794 --> 00:21:34.135
<v Speaker 0>scope of being able to handle your data.

00:21:34.275 --> 00:21:38.610
<v Speaker 0>And I think this is a big example

00:21:38.670 --> 00:21:40.110
<v Speaker 0>of why you should be careful of where

00:21:40.110 --> 00:21:42.050
<v Speaker 0>you sign up or what kind of extensions

00:21:42.190 --> 00:21:44.590
<v Speaker 0>you pay into, you know, the types of

00:21:44.590 --> 00:21:50.455
<v Speaker 0>sites you're paying into. Yeah. I don't know.

00:21:50.455 --> 00:21:52.535
<v Speaker 0>Even just going through some of my, you

00:21:52.535 --> 00:21:55.335
<v Speaker 0>know, my dad's, you know, subscriptions that he

00:21:55.335 --> 00:22:00.715
<v Speaker 0>did, you know, just, obviously, like, a casual

00:22:00.775 --> 00:22:05.470
<v Speaker 0>bourbon or whiskey enjoyer, but still, like, I

00:22:05.470 --> 00:22:07.470
<v Speaker 0>I don't know. It just confused me that,

00:22:07.470 --> 00:22:08.990
<v Speaker 0>you know, there were all all these types

00:22:08.990 --> 00:22:11.710
<v Speaker 0>of random subscriptions to these random sites available

00:22:11.710 --> 00:22:14.190
<v Speaker 0>online. But I definitely check this out from

00:22:14.190 --> 00:22:17.870
<v Speaker 0>Hacker News. Thank you again, Ravi Lakshmanan for

00:22:17.870 --> 00:22:24.424
<v Speaker 0>the article. Let's move on. This is a

00:22:24.424 --> 00:22:27.945
<v Speaker 0>pretty cool, change if it's actually true. This

00:22:27.945 --> 00:22:30.424
<v Speaker 0>is from thurratt dot com written by Paul

00:22:30.424 --> 00:22:32.445
<v Speaker 0>thurratt. So I guess this is his personal,

00:22:34.169 --> 00:22:39.049
<v Speaker 0>But so thanks, Paul. But Microsoft replaced all

00:22:39.049 --> 00:22:41.529
<v Speaker 0>CC plus plus code with Rust by twenty

00:22:41.529 --> 00:22:47.289
<v Speaker 0>thirty, and this is a big modernization, of

00:22:47.289 --> 00:22:50.495
<v Speaker 0>a code base, which I'm not against. I

00:22:50.975 --> 00:22:53.135
<v Speaker 0>for those of you who know me, I'm

00:22:53.135 --> 00:22:54.815
<v Speaker 0>a huge fan of Rust. I think it's

00:22:54.815 --> 00:23:00.675
<v Speaker 0>a fantastic language, very beautifully handles memory management,

00:23:02.669 --> 00:23:06.450
<v Speaker 0>but I digress. Let's get into the article.

00:23:07.309 --> 00:23:09.470
<v Speaker 0>For over a decade, Microsoft has been grappling

00:23:09.470 --> 00:23:12.429
<v Speaker 0>with a persistent security challenge. Roughly seventy percent

00:23:12.429 --> 00:23:16.085
<v Speaker 0>of the company's patches have addressed memory safety

00:23:16.145 --> 00:23:18.625
<v Speaker 0>issues stemming from c and c plus plus

00:23:18.625 --> 00:23:22.705
<v Speaker 0>code. These vulnerabilities include buffer overflows and use

00:23:22.705 --> 00:23:25.585
<v Speaker 0>after free bugs represent an entire class of

00:23:25.585 --> 00:23:28.725
<v Speaker 0>exploits that are endemic to these legacy languages.

00:23:29.480 --> 00:23:32.280
<v Speaker 0>In response, Microsoft began exploring Rust as a

00:23:32.280 --> 00:23:35.000
<v Speaker 0>safer alternative in twenty twenty three when Azure

00:23:35.000 --> 00:23:39.240
<v Speaker 0>CTO, Mark Russ Russinovic forbid developers from starting

00:23:39.240 --> 00:23:41.740
<v Speaker 0>new c c slash c plus plus projects

00:23:42.115 --> 00:23:44.195
<v Speaker 0>and man mandated the use of Rust instead.

00:23:44.195 --> 00:23:45.955
<v Speaker 0>Is that true? I didn't know that. The

00:23:45.955 --> 00:23:47.635
<v Speaker 0>company has already started rewriting parts of the

00:23:47.635 --> 00:23:50.115
<v Speaker 0>window kernel in Rust with early results showing

00:23:50.115 --> 00:23:54.115
<v Speaker 0>improved performance and fewer exploitable faults. The broader

00:23:54.115 --> 00:23:56.034
<v Speaker 0>software industry has been moving in the same

00:23:56.034 --> 00:24:00.530
<v Speaker 0>direction. Google, Amazon, Dropbox, and CloudFlare now make

00:24:00.530 --> 00:24:03.250
<v Speaker 0>extensive use of Rust for critical infrastructure, and

00:24:03.250 --> 00:24:05.730
<v Speaker 0>the Linux kernel officially adopted Rust in twenty

00:24:05.730 --> 00:24:08.770
<v Speaker 0>twenty five. Google even invested a million dollars

00:24:08.770 --> 00:24:11.765
<v Speaker 0>in the Rust Foundation to improve interoperability between

00:24:11.765 --> 00:24:14.165
<v Speaker 0>c plus plus and Rust, recognizing that the

00:24:14.165 --> 00:24:16.965
<v Speaker 0>transition will require coexistence between the two languages

00:24:16.965 --> 00:24:20.565
<v Speaker 0>during migration. According to JetBrains, two point three

00:24:20.565 --> 00:24:23.365
<v Speaker 0>million developers now use Rust with enterprise adoption,

00:24:23.365 --> 00:24:27.840
<v Speaker 0>increasing by sixty eight point seventy five percent.

00:24:27.980 --> 00:24:30.700
<v Speaker 0>This industry wide shift underscores the urgency of

00:24:30.700 --> 00:24:34.000
<v Speaker 0>addressing memory safe memory safety and systems programming.

00:24:35.899 --> 00:24:37.820
<v Speaker 0>Hey. That's cool. I am a huge fan

00:24:37.820 --> 00:24:40.620
<v Speaker 0>of Rust. I have a little tiny, TUI

00:24:40.620 --> 00:24:43.205
<v Speaker 0>tool that I've put together using Rust that

00:24:43.205 --> 00:24:45.365
<v Speaker 0>is quick and fast and efficient. I love

00:24:45.365 --> 00:24:48.265
<v Speaker 0>it. It does all sorts of, you know,

00:24:48.565 --> 00:24:51.525
<v Speaker 0>knick knack type of stuff, but, obviously, that's,

00:24:51.525 --> 00:24:54.325
<v Speaker 0>like, not really the best use for that

00:24:54.325 --> 00:24:58.100
<v Speaker 0>type of tool. But still, I think it's

00:24:58.480 --> 00:25:00.880
<v Speaker 0>a fantastic language. I'm glad to see this

00:25:00.880 --> 00:25:04.640
<v Speaker 0>change coming into place, especially if it's gonna

00:25:04.640 --> 00:25:06.720
<v Speaker 0>cut out a lot of the patches related

00:25:06.720 --> 00:25:10.965
<v Speaker 0>to memory issues. That is the big thing

00:25:10.965 --> 00:25:12.805
<v Speaker 0>with c and c plus plus memory, memory,

00:25:12.805 --> 00:25:15.765
<v Speaker 0>memory, memory, memory. This is not so bad

00:25:15.765 --> 00:25:18.805
<v Speaker 0>now with a lot of the smart pointers

00:25:18.805 --> 00:25:23.129
<v Speaker 0>and whatnot in c plus plus, but, you

00:25:23.129 --> 00:25:24.570
<v Speaker 0>know, I'm sure that they have a lot

00:25:24.570 --> 00:25:26.730
<v Speaker 0>of legacy code that they're unwilling to change

00:25:26.730 --> 00:25:30.830
<v Speaker 0>because it, you know, it works. So Microsoft

00:25:30.889 --> 00:25:34.509
<v Speaker 0>distinguished engineer Galen Hunt announced an ambitious goal

00:25:34.804 --> 00:25:36.965
<v Speaker 0>to eliminate every line of c in c

00:25:36.965 --> 00:25:39.385
<v Speaker 0>plus plus code from Microsoft by twenty thirty,

00:25:39.445 --> 00:25:42.085
<v Speaker 0>replacing it with Rust using AI assisted large

00:25:42.085 --> 00:25:46.965
<v Speaker 0>scale refactoring. Now this AI refactoring is crazy.

00:25:46.965 --> 00:25:48.990
<v Speaker 0>I've seen some videos on it. My god.

00:25:48.990 --> 00:25:52.430
<v Speaker 0>It can make something ugly turn beautiful. The

00:25:52.430 --> 00:25:56.030
<v Speaker 0>company's strategy combines algorithmic program analysis with AI

00:25:56.030 --> 00:25:59.070
<v Speaker 0>agents to rewrite code bases at scale, targeting

00:25:59.070 --> 00:26:03.135
<v Speaker 0>a productivity metric of one engineer, one month,

00:26:03.434 --> 00:26:06.235
<v Speaker 0>one million lines of code. Jesus. That's too

00:26:06.235 --> 00:26:09.755
<v Speaker 0>many lines of code. Microsoft is building infrastructure

00:26:09.755 --> 00:26:11.995
<v Speaker 0>that creates queryable graphs of source code for

00:26:11.995 --> 00:26:15.515
<v Speaker 0>deterministic reasoning while deploying AI models to perform

00:26:15.515 --> 00:26:20.780
<v Speaker 0>translation, refactoring, and specification in in inference tasks

00:26:20.780 --> 00:26:25.820
<v Speaker 0>under algorithmic supervision. However, an important update clarified

00:26:25.820 --> 00:26:28.300
<v Speaker 0>that this is currently a research project rather

00:26:28.300 --> 00:26:31.020
<v Speaker 0>than an official goal for Windows eleven, twelve,

00:26:31.020 --> 00:26:33.715
<v Speaker 0>or future versions. So yes. So okay. Yeah.

00:26:34.095 --> 00:26:35.135
<v Speaker 0>This this is why I said it was

00:26:35.135 --> 00:26:40.175
<v Speaker 0>speculative earlier, because I did see a, like,

00:26:40.175 --> 00:26:43.535
<v Speaker 0>a, an article that was saying the opposite,

00:26:43.535 --> 00:26:45.135
<v Speaker 0>that I had said that this was just

00:26:45.135 --> 00:26:50.080
<v Speaker 0>a speculative. But the initiative is is is

00:26:50.320 --> 00:26:52.899
<v Speaker 0>the initiative is driven by Rust's compelling advantage.

00:26:53.120 --> 00:26:55.380
<v Speaker 0>It offers c, c plus plus level performance

00:26:55.440 --> 00:26:58.259
<v Speaker 0>while providing memory safety and thread safety guarantees

00:26:58.320 --> 00:27:01.965
<v Speaker 0>built into the language itself. Rust's ownership, borrowing,

00:27:01.965 --> 00:27:05.165
<v Speaker 0>and lifetime model eliminates buffer overflows, use after

00:27:05.165 --> 00:27:08.125
<v Speaker 0>free bugs, and other memory corruption vulnerabilities without

00:27:08.125 --> 00:27:11.565
<v Speaker 0>imposing garbage collector overhead on low latency system

00:27:11.565 --> 00:27:16.570
<v Speaker 0>code. Early conversions such as the Direct Write

00:27:16.570 --> 00:27:19.770
<v Speaker 0>subsystem have demonstrated these benefits with Rust based

00:27:19.770 --> 00:27:24.030
<v Speaker 0>kernel trials converting potentially AI generated code to

00:27:24.090 --> 00:27:28.395
<v Speaker 0>rely heavily on unsafe blocks. Wait. Did I

00:27:28.695 --> 00:27:31.575
<v Speaker 0>read that right? With Rust based kernel trials

00:27:31.575 --> 00:27:37.895
<v Speaker 0>converting potentially, exploitable conditions into deterministic crashes. While

00:27:37.895 --> 00:27:40.955
<v Speaker 0>challenges remain, including the potential for AI generated

00:27:41.015 --> 00:27:43.630
<v Speaker 0>code to rely heavily on unsafe blocks that

00:27:43.630 --> 00:27:48.690
<v Speaker 0>bypass Rust guarantees, the overall direction represents Microsoft's

00:27:48.750 --> 00:27:51.470
<v Speaker 0>most serious effort yet to modernize its massive

00:27:51.470 --> 00:27:54.190
<v Speaker 0>code base and eliminate a long standing source

00:27:54.190 --> 00:27:57.654
<v Speaker 0>of security vulnerabilities. Now for those of you

00:27:57.654 --> 00:27:59.894
<v Speaker 0>that are not super tech savvy, this might

00:27:59.894 --> 00:28:03.414
<v Speaker 0>just seem like a mouthful of hogwash or

00:28:03.414 --> 00:28:07.975
<v Speaker 0>however you're supposed to say it. But, to

00:28:07.975 --> 00:28:12.140
<v Speaker 0>be clear, the the biggest the hardest part

00:28:12.140 --> 00:28:13.820
<v Speaker 0>about switching off a c and c plus

00:28:13.820 --> 00:28:18.140
<v Speaker 0>plus is the performance. The memory safety is

00:28:18.220 --> 00:28:20.299
<v Speaker 0>has been a constant issue from the start.

00:28:20.299 --> 00:28:23.600
<v Speaker 0>And, you know, as we've introduced newer languages

00:28:23.900 --> 00:28:27.284
<v Speaker 0>with the with the the the thing called

00:28:27.284 --> 00:28:31.125
<v Speaker 0>a garbage collector in it. These languages are

00:28:31.125 --> 00:28:33.465
<v Speaker 0>easier to manage or don't have as much

00:28:33.524 --> 00:28:35.684
<v Speaker 0>memory issues, but they're also a little bit

00:28:35.684 --> 00:28:37.684
<v Speaker 0>slower due to the garbage collector in the

00:28:37.684 --> 00:28:41.930
<v Speaker 0>system. So it's kinda cool to see how,

00:28:42.170 --> 00:28:45.950
<v Speaker 0>how they've optimized or they've worked on optimizing,

00:28:46.650 --> 00:28:50.030
<v Speaker 0>managing memory and how successful the ownership system

00:28:50.090 --> 00:28:54.455
<v Speaker 0>has been in, the Rust ecosystem. So it's

00:28:54.455 --> 00:28:57.175
<v Speaker 0>a yeah. I think it's cool. I don't

00:28:57.175 --> 00:28:59.335
<v Speaker 0>think it's a bad goal to eliminate every

00:28:59.335 --> 00:29:01.335
<v Speaker 0>line of c and c plus plus for

00:29:01.335 --> 00:29:04.375
<v Speaker 0>Microsoft by twenty thirty if they have as

00:29:04.375 --> 00:29:09.330
<v Speaker 0>many memory issues as they're saying. But at

00:29:09.330 --> 00:29:14.370
<v Speaker 0>the same time, yeah, doing all of it

00:29:14.370 --> 00:29:17.570
<v Speaker 0>algorithmically via, you know, AI driven migrations might

00:29:17.570 --> 00:29:18.930
<v Speaker 0>not be the best choice. That's all I

00:29:18.930 --> 00:29:22.505
<v Speaker 0>can really say. Yeah. I don't I don't

00:29:22.505 --> 00:29:25.465
<v Speaker 0>I don't particularly agree with that, that one.

00:29:25.465 --> 00:29:29.705
<v Speaker 0>Let's move on. We got this year's most

00:29:29.705 --> 00:29:32.925
<v Speaker 0>influential open source projects by the GitHub blog.

00:29:34.760 --> 00:29:38.280
<v Speaker 0>This one's written by Lee Riley. GitHub universe

00:29:38.280 --> 00:29:41.020
<v Speaker 0>twenty twenty five featured an open source zone

00:29:41.160 --> 00:29:44.680
<v Speaker 0>showcasing twelve standout open source projects that represent

00:29:44.680 --> 00:29:47.100
<v Speaker 0>the current state of innovation in the ecosystem.

00:29:47.764 --> 00:29:51.125
<v Speaker 0>This annual event brings together maintainers, contributors, and

00:29:51.125 --> 00:29:53.764
<v Speaker 0>developers to highlight projects that are shaping how

00:29:53.764 --> 00:29:56.725
<v Speaker 0>software is built and maintained. The twenty twenty

00:29:56.725 --> 00:29:59.365
<v Speaker 0>five cohort spans diverse categories from back end

00:29:59.365 --> 00:30:02.730
<v Speaker 0>platforms and release automation to security frameworks and

00:30:02.730 --> 00:30:05.950
<v Speaker 0>developer tools, reflecting reflecting the breadth of challenges

00:30:06.330 --> 00:30:10.330
<v Speaker 0>the open source community is tackling. And, you

00:30:10.330 --> 00:30:13.050
<v Speaker 0>know, with this note, I was thinking about

00:30:13.050 --> 00:30:15.290
<v Speaker 0>doing, like, a, like, a false segment at

00:30:15.290 --> 00:30:17.815
<v Speaker 0>the end of every episode. So who knows?

00:30:17.815 --> 00:30:19.895
<v Speaker 0>I might try that out next, next episode

00:30:19.895 --> 00:30:21.735
<v Speaker 0>that I do. Just do a little a

00:30:21.735 --> 00:30:24.535
<v Speaker 0>FOSS introduction on on a free and open

00:30:24.535 --> 00:30:28.375
<v Speaker 0>source software, tell you guys what their mission

00:30:28.375 --> 00:30:30.990
<v Speaker 0>is, what they're doing, and how you guys

00:30:30.990 --> 00:30:32.750
<v Speaker 0>can get involved if you're if you're a

00:30:32.750 --> 00:30:39.310
<v Speaker 0>developer. But I think, FOSS tools really align

00:30:39.310 --> 00:30:42.450
<v Speaker 0>a lot with the, you know, the ecosystem

00:30:42.510 --> 00:30:45.345
<v Speaker 0>of podcasting as well and and what it

00:30:45.345 --> 00:30:50.385
<v Speaker 0>means to be a podcaster, today. So I

00:30:50.385 --> 00:30:51.825
<v Speaker 0>think that's something that we should all talk

00:30:51.825 --> 00:30:53.345
<v Speaker 0>about and check out. So I'm probably gonna

00:30:53.345 --> 00:30:55.345
<v Speaker 0>bring that into the show starting, my next

00:30:55.345 --> 00:30:58.465
<v Speaker 0>episode. So new new New Year format, we'll

00:30:58.465 --> 00:31:04.460
<v Speaker 0>call it that. But, let's move on. So

00:31:05.159 --> 00:31:06.919
<v Speaker 0>the timing of the showcase is significant as

00:31:06.919 --> 00:31:09.960
<v Speaker 0>the open source landscape undergoes major shifts. And

00:31:09.960 --> 00:31:11.400
<v Speaker 0>I did talk about this a few weeks

00:31:11.400 --> 00:31:14.805
<v Speaker 0>ago. TypeScript recently surpassed Python as the most

00:31:14.805 --> 00:31:16.725
<v Speaker 0>used language on GitHub for the first time

00:31:16.725 --> 00:31:19.605
<v Speaker 0>in over a decade driven by AI assisted

00:31:19.605 --> 00:31:23.285
<v Speaker 0>development and frameworks that develop that default to

00:31:23.285 --> 00:31:27.765
<v Speaker 0>TypeScript. Meanwhile, Python continues dominating AI and data

00:31:27.765 --> 00:31:31.230
<v Speaker 0>science with two point six million contributors. This

00:31:31.230 --> 00:31:33.870
<v Speaker 0>reflects a broader trend towards hybrid stacks where

00:31:33.870 --> 00:31:36.910
<v Speaker 0>Python handles data pipelines and machine learning, while

00:31:36.910 --> 00:31:41.870
<v Speaker 0>TypeScript powers user facing applications and APIs. And,

00:31:41.870 --> 00:31:45.230
<v Speaker 0>again, TypeScript is a superset of JavaScript, if

00:31:45.230 --> 00:31:48.985
<v Speaker 0>I remember correctly. I personally don't think I've

00:31:48.985 --> 00:31:52.505
<v Speaker 0>played around with TypeScript, at all, so I

00:31:52.505 --> 00:31:55.225
<v Speaker 0>definitely have to check it out. I'm definitely

00:31:55.225 --> 00:31:57.645
<v Speaker 0>a huge fan of that vanilla JS despite

00:31:58.950 --> 00:32:01.850
<v Speaker 0>the that that controversial idea, I could say.

00:32:02.149 --> 00:32:04.630
<v Speaker 0>But I guess maybe if I like vanilla

00:32:04.630 --> 00:32:09.429
<v Speaker 0>JS, I might like, TypeScript too. So the

00:32:09.429 --> 00:32:11.909
<v Speaker 0>feature projects at Universe twenty twenty five demonstrate

00:32:11.909 --> 00:32:14.149
<v Speaker 0>how open source is evolving to meet modern

00:32:14.149 --> 00:32:18.245
<v Speaker 0>development challenges. AppWright provides developers with an open

00:32:18.245 --> 00:32:21.845
<v Speaker 0>source back end platform that eliminates boilerplate code

00:32:21.845 --> 00:32:25.605
<v Speaker 0>with ready made APIs for databases, authentication, and

00:32:25.605 --> 00:32:29.544
<v Speaker 0>storage. Wow. That's cool. It's basically a template.

00:32:30.770 --> 00:32:32.929
<v Speaker 0>And then Go Releaser has become the go

00:32:32.929 --> 00:32:37.169
<v Speaker 0>to release engineering tool for Go maintainers, automating

00:32:37.169 --> 00:32:39.890
<v Speaker 0>the entire process of packaging and publishing and

00:32:39.890 --> 00:32:43.485
<v Speaker 0>distributing projects with over fifteen thousand stars and

00:32:43.485 --> 00:32:46.445
<v Speaker 0>paying customers worldwide. Oh, no. This now I

00:32:46.445 --> 00:32:49.245
<v Speaker 0>need to check that one out. I've I

00:32:49.245 --> 00:32:53.425
<v Speaker 0>have a Go tool that I've, I have

00:32:53.565 --> 00:32:55.680
<v Speaker 0>hosted on a cloud service that I use

00:32:56.080 --> 00:33:01.280
<v Speaker 0>at my other job. And, I always have

00:33:01.280 --> 00:33:03.200
<v Speaker 0>to run my own personal scripts to get

00:33:03.200 --> 00:33:05.760
<v Speaker 0>everything running back up running up again on

00:33:05.760 --> 00:33:08.320
<v Speaker 0>on the production side. So this might be

00:33:08.320 --> 00:33:10.400
<v Speaker 0>something that really helps me out. See, okay.

00:33:10.400 --> 00:33:15.335
<v Speaker 0>Cool. Go releaser. But, yeah, the Open Source

00:33:15.335 --> 00:33:21.655
<v Speaker 0>Project Security Baseline, OSPSB, and OpenSSF initiative addresses

00:33:21.655 --> 00:33:24.795
<v Speaker 0>the critical but often overlooked aspect of security

00:33:24.935 --> 00:33:28.470
<v Speaker 0>by providing maintainers with a practical, actionable checklist

00:33:28.529 --> 00:33:31.730
<v Speaker 0>of minimum security requirements that any project any

00:33:31.730 --> 00:33:35.169
<v Speaker 0>project can implement regardless of team size. And

00:33:35.169 --> 00:33:39.090
<v Speaker 0>let me tell you, yes. Security is a

00:33:39.090 --> 00:33:42.155
<v Speaker 0>hard thing to, you know, bake into your

00:33:42.155 --> 00:33:44.395
<v Speaker 0>code when you're building it. It is good

00:33:44.395 --> 00:33:49.675
<v Speaker 0>to do habitually, but oftentimes, you know, you

00:33:49.835 --> 00:33:52.075
<v Speaker 0>you're more focused on the general flow rather

00:33:52.075 --> 00:33:54.870
<v Speaker 0>than worrying about someone trying to bust into

00:33:54.870 --> 00:33:58.150
<v Speaker 0>your machine. But, I mean, we we talked

00:33:58.150 --> 00:34:00.390
<v Speaker 0>about those Chrome extensions earlier. It's a valid

00:34:00.390 --> 00:34:04.870
<v Speaker 0>concern. But the broader ecosystem has experienced rapid

00:34:04.870 --> 00:34:07.350
<v Speaker 0>growth in AI enabled development tools and low

00:34:07.350 --> 00:34:11.335
<v Speaker 0>code platforms. Projects like ShadCN slash UI have

00:34:11.335 --> 00:34:14.535
<v Speaker 0>become foundational for web applications due to their

00:34:14.535 --> 00:34:18.555
<v Speaker 0>flexibility and accessibility or accessible copy paste component

00:34:18.855 --> 00:34:22.855
<v Speaker 0>architecture. I've I think I have that on

00:34:22.855 --> 00:34:25.810
<v Speaker 0>my computer. I've seen that updated before. So,

00:34:25.810 --> 00:34:27.650
<v Speaker 0>you know, things that I don't even realize

00:34:27.650 --> 00:34:31.670
<v Speaker 0>I'm using is in my system. And then,

00:34:32.610 --> 00:34:35.970
<v Speaker 0>Mitosis is solving framework lock in by allowing

00:34:35.970 --> 00:34:38.825
<v Speaker 0>developers to write components once and compile them

00:34:38.825 --> 00:34:44.025
<v Speaker 0>to React, Vue, Svelte, Angular, Solid, and mobile

00:34:44.025 --> 00:34:47.224
<v Speaker 0>frameworks. The low code movement is thriving with

00:34:47.224 --> 00:34:51.450
<v Speaker 0>n8n showing explosive growth in workflow automation, while

00:34:51.450 --> 00:34:56.170
<v Speaker 0>Supabase, AppFlowy, and Anocodb remains or maintain strong

00:34:56.170 --> 00:35:00.270
<v Speaker 0>momentum alongside newer contenders like NoCoBase and Windmill.

00:35:01.609 --> 00:35:02.810
<v Speaker 0>And I do I do have a little

00:35:02.810 --> 00:35:04.810
<v Speaker 0>bit of experience with Supabase. That's a pretty

00:35:04.810 --> 00:35:11.335
<v Speaker 0>fun, what did they use? PostgreSQL database cloud

00:35:11.335 --> 00:35:16.375
<v Speaker 0>service. That one's a pretty cool one. But

00:35:16.375 --> 00:35:19.800
<v Speaker 0>the shift towards supa or TypeScript the shift

00:35:19.800 --> 00:35:21.480
<v Speaker 0>towards Supabase is not but the shift the

00:35:21.480 --> 00:35:23.560
<v Speaker 0>shift towards TypeScript as a dominant language on

00:35:23.560 --> 00:35:26.360
<v Speaker 0>GitHub, I think, really signaled a fundamental change

00:35:26.360 --> 00:35:29.580
<v Speaker 0>in, like, how developers are approaching building software.

00:35:29.880 --> 00:35:31.480
<v Speaker 0>And I think it will kinda change how

00:35:31.480 --> 00:35:33.960
<v Speaker 0>you guys start to experience software in the

00:35:33.960 --> 00:35:39.025
<v Speaker 0>coming future. I do think that it is

00:35:39.025 --> 00:35:41.984
<v Speaker 0>a little bit obvious when, a site or

00:35:41.984 --> 00:35:45.025
<v Speaker 0>component has built been built with AI. You

00:35:45.025 --> 00:35:47.285
<v Speaker 0>can kind of tell it uses a similar

00:35:47.345 --> 00:35:51.750
<v Speaker 0>styling, but who knows? That might change in

00:35:51.750 --> 00:35:53.750
<v Speaker 0>the future. I do like that there are

00:35:53.750 --> 00:35:56.810
<v Speaker 0>now a lot of frameworking tools or templating

00:35:56.870 --> 00:35:58.630
<v Speaker 0>tools that allow you to that give you

00:35:58.630 --> 00:36:02.890
<v Speaker 0>the basis that you can extend upon, really

00:36:03.110 --> 00:36:06.805
<v Speaker 0>making software be released at a much quicker

00:36:06.805 --> 00:36:09.205
<v Speaker 0>and more efficient rate. We might start seeing

00:36:09.205 --> 00:36:12.565
<v Speaker 0>downscaling of businesses and the increasing the increase

00:36:12.565 --> 00:36:15.125
<v Speaker 0>of the amount of businesses, with all these

00:36:15.125 --> 00:36:18.440
<v Speaker 0>efficiencies being introduced. But who knows? I don't

00:36:18.440 --> 00:36:22.200
<v Speaker 0>even know. It I think this is awesome.

00:36:22.200 --> 00:36:24.680
<v Speaker 0>I love that GitHub is doing this. I

00:36:24.680 --> 00:36:27.240
<v Speaker 0>would love to go to GitHub, you know,

00:36:27.240 --> 00:36:31.415
<v Speaker 0>or universe GitHub universe. One of these years,

00:36:31.415 --> 00:36:33.575
<v Speaker 0>that'll be definitely a goal for me to

00:36:33.575 --> 00:36:36.055
<v Speaker 0>to check it out, but check this website

00:36:36.055 --> 00:36:39.255
<v Speaker 0>out. A lot of cool open source tools

00:36:39.255 --> 00:36:43.815
<v Speaker 0>here. I'm definitely gonna be trying out the

00:36:43.815 --> 00:36:47.990
<v Speaker 0>Go Releaser. I think that, that one will

00:36:47.990 --> 00:36:52.790
<v Speaker 0>definitely help with my own personal, my own

00:36:52.790 --> 00:37:00.954
<v Speaker 0>personal business. So, yeah, let's move on. This

00:37:00.954 --> 00:37:03.135
<v Speaker 0>one kinda sounds straight out of science fiction,

00:37:03.195 --> 00:37:09.695
<v Speaker 0>but, Engine AI unveils t eight hundred, combat

00:37:09.755 --> 00:37:15.800
<v Speaker 0>ready humanoid combat ready humanoid targets mass production

00:37:15.940 --> 00:37:19.160
<v Speaker 0>for industry. Now this one's from New Atlas

00:37:19.380 --> 00:37:25.720
<v Speaker 0>by Stefan Ionescu. And we did talk about,

00:37:26.925 --> 00:37:29.325
<v Speaker 0>the what was it? I can't remember what

00:37:29.325 --> 00:37:30.925
<v Speaker 0>the name of the robot was, but they

00:37:30.925 --> 00:37:35.085
<v Speaker 0>just released another automated robot in China, unless

00:37:35.085 --> 00:37:37.725
<v Speaker 0>this is the same one. But the humanoid

00:37:37.725 --> 00:37:40.930
<v Speaker 0>robotics industry is experiencing explosive growth in twenty

00:37:40.930 --> 00:37:43.490
<v Speaker 0>twenty five with the global market projected to

00:37:43.490 --> 00:37:45.830
<v Speaker 0>surge from two point nine two billion to

00:37:45.890 --> 00:37:48.450
<v Speaker 0>fifteen point twenty six billion by two thousand

00:37:48.450 --> 00:37:52.290
<v Speaker 0>and thirty, representing a staggering thirty nine point

00:37:52.290 --> 00:37:55.955
<v Speaker 0>two percent annual growth rate. This acceleration has

00:37:55.955 --> 00:37:58.515
<v Speaker 0>driven by fierce competition between the United States

00:37:58.515 --> 00:38:01.315
<v Speaker 0>and China, with China emerging as a dominant

00:38:01.315 --> 00:38:05.635
<v Speaker 0>force through aggressive government support, massive investment, and

00:38:05.635 --> 00:38:08.915
<v Speaker 0>a commanding lead in patent fill fillings or

00:38:08.915 --> 00:38:12.710
<v Speaker 0>filings. Wow. In just the first nine months

00:38:12.710 --> 00:38:15.690
<v Speaker 0>of twenty twenty five, China's robotics sector extracted

00:38:15.910 --> 00:38:21.290
<v Speaker 0>six hundred ten investment deals totaling fifty billion

00:38:21.510 --> 00:38:25.305
<v Speaker 0>yuan, about seven billion dollars, and which is

00:38:25.305 --> 00:38:27.865
<v Speaker 0>a two hundred fifty percent year over year

00:38:27.865 --> 00:38:33.145
<v Speaker 0>increase. Major players like Tesla, Agility Robotics, Boston

00:38:33.145 --> 00:38:36.265
<v Speaker 0>Dynamics, and Figure AI are racing to scale

00:38:36.265 --> 00:38:40.204
<v Speaker 0>production with Tesla targeting five thousand Optimus units

00:38:40.265 --> 00:38:42.980
<v Speaker 0>in twenty twenty five and plan to reach

00:38:43.040 --> 00:38:45.680
<v Speaker 0>hundred thousand by twenty twenty six. You know,

00:38:45.680 --> 00:38:49.280
<v Speaker 0>I I don't wanna be a hater, but

00:38:49.280 --> 00:38:51.780
<v Speaker 0>why they gotta use the the name Optimus?

00:38:52.080 --> 00:38:54.455
<v Speaker 0>Like, come on. We all know you're referencing

00:38:54.515 --> 00:38:57.235
<v Speaker 0>transformers. Like, get your own original name. This

00:38:57.955 --> 00:39:00.055
<v Speaker 0>I hate that. I'm sorry. I hate that.

00:39:01.235 --> 00:39:03.635
<v Speaker 0>Like, you couldn't even be creative enough to

00:39:03.635 --> 00:39:05.715
<v Speaker 0>come up with a freaking different robot name

00:39:05.715 --> 00:39:08.115
<v Speaker 0>for your first company's robot. You're gonna name

00:39:08.115 --> 00:39:15.950
<v Speaker 0>it Optimus. That's crazy to me, man. What

00:39:15.950 --> 00:39:18.589
<v Speaker 0>an insane lack of creativity. I have no

00:39:18.589 --> 00:39:20.750
<v Speaker 0>other comment for that. An insane lack of

00:39:20.750 --> 00:39:24.805
<v Speaker 0>creativity. Cost barriers are collapsing at unprecedented rates

00:39:25.025 --> 00:39:30.065
<v Speaker 0>disrupting industry expectations. Chinese mac manufacturer Unitree shocked

00:39:30.065 --> 00:39:32.244
<v Speaker 0>the market by launching its r one humanoid

00:39:32.625 --> 00:39:35.345
<v Speaker 0>at just fifty nine hundred in July twenty

00:39:35.345 --> 00:39:38.599
<v Speaker 0>twenty five, a price point previously thought impossible

00:39:38.819 --> 00:39:42.500
<v Speaker 0>for years, and yet fifty nine hundred dollars

00:39:42.500 --> 00:39:46.099
<v Speaker 0>is dirt cheap for a freaking humanoid robot.

00:39:46.099 --> 00:39:49.859
<v Speaker 0>What? The industry is converged on a unified

00:39:49.859 --> 00:39:53.525
<v Speaker 0>strategy. Build a single general purpose humanoid body

00:39:53.525 --> 00:39:55.845
<v Speaker 0>that can learn many jobs through software and

00:39:55.845 --> 00:39:59.045
<v Speaker 0>data then deploy at scale. The humanoid form

00:39:59.045 --> 00:40:01.525
<v Speaker 0>factor is favored because it fits existing human

00:40:01.525 --> 00:40:05.940
<v Speaker 0>environments, including stairs, doors, elevators, and tools designed

00:40:05.940 --> 00:40:09.620
<v Speaker 0>for human proportions. In the in short or

00:40:09.620 --> 00:40:12.740
<v Speaker 0>in the short to midterm before twenty thirty,

00:40:12.740 --> 00:40:15.160
<v Speaker 0>the automotive industry is expected to lead humanoid

00:40:15.300 --> 00:40:19.905
<v Speaker 0>adaptation with companies like Mercedes Benz, BMW, Tesla,

00:40:20.285 --> 00:40:24.285
<v Speaker 0>Xiaomi, and XPeng, all deliver developing or deploying

00:40:24.285 --> 00:40:30.365
<v Speaker 0>humanoid robots in their production facilities. Wow. So

00:40:30.365 --> 00:40:33.005
<v Speaker 0>for this specific humanoid robot, the t eight

00:40:33.005 --> 00:40:36.670
<v Speaker 0>hundred, Chinese robotics company, Engine AI, founded in

00:40:36.670 --> 00:40:39.170
<v Speaker 0>late twenty twenty three and based in Shenzhen

00:40:40.109 --> 00:40:43.950
<v Speaker 0>officially unveiled its twenty eight hundred humanoid robot

00:40:43.950 --> 00:40:46.509
<v Speaker 0>in December twenty twenty five backed by one

00:40:46.509 --> 00:40:50.805
<v Speaker 0>billion yuan in financing. Standing a hundred seventy

00:40:50.805 --> 00:40:53.685
<v Speaker 0>three centimeters tall and weighing seventy five kilograms

00:40:53.685 --> 00:40:56.405
<v Speaker 0>with battery, it's at, like, about a hundred

00:40:56.405 --> 00:40:59.845
<v Speaker 0>fifty pounds. The t eight hundred features twenty

00:40:59.845 --> 00:41:02.425
<v Speaker 0>nine degrees of freedom in the body, excluding

00:41:02.485 --> 00:41:05.930
<v Speaker 0>hands, each hand with seven degrees of freedom

00:41:05.930 --> 00:41:10.430
<v Speaker 0>and five kilogram payload capacity with integrated tactile

00:41:10.490 --> 00:41:14.250
<v Speaker 0>sensing. The robot achieves a maximum joint torque

00:41:14.250 --> 00:41:17.825
<v Speaker 0>of four hundred fifty nanometers and can move

00:41:17.825 --> 00:41:20.065
<v Speaker 0>at speeds of up to three meters per

00:41:20.065 --> 00:41:24.305
<v Speaker 0>second. Built from aviation grade aluminum panels for

00:41:24.305 --> 00:41:27.345
<v Speaker 0>strength and lightweight, the t eight hundred includes

00:41:27.345 --> 00:41:30.005
<v Speaker 0>an active cooling system in leg joints, enabling

00:41:30.065 --> 00:41:33.190
<v Speaker 0>continuous high intensity operation for up to four

00:41:33.190 --> 00:41:35.750
<v Speaker 0>hours powered by a seventy two quick seventy

00:41:35.750 --> 00:41:42.150
<v Speaker 0>two volt quick release modular battery. The Pro

00:41:42.150 --> 00:41:45.770
<v Speaker 0>and Max versions are powered by NVIDIA Jetson

00:41:45.830 --> 00:41:49.904
<v Speaker 0>THOR chips capable of two thousand TOPS f

00:41:49.904 --> 00:41:52.325
<v Speaker 0>p four processing. Not sure what that means.

00:41:53.265 --> 00:41:55.924
<v Speaker 0>Combined with an Intel n ninety seven controller

00:41:56.224 --> 00:42:00.144
<v Speaker 0>and NVIDIA AGX Orin module offering two seventy

00:42:00.144 --> 00:42:04.380
<v Speaker 0>five TOPS of AI computing performance. For perception,

00:42:04.840 --> 00:42:07.800
<v Speaker 0>the t eight hundred uses Intel RealSense d

00:42:07.800 --> 00:42:10.119
<v Speaker 0>four one five and d four three five

00:42:10.119 --> 00:42:13.960
<v Speaker 0>I depth cameras, three hundred sixty degree LIDAR.

00:42:13.960 --> 00:42:16.665
<v Speaker 0>Wow. It even has LIDAR in it. Stereo

00:42:16.665 --> 00:42:20.185
<v Speaker 0>cameras and an AC one sensor suite for

00:42:20.185 --> 00:42:29.085
<v Speaker 0>navigation and obstacle detection. We are entering into

00:42:29.145 --> 00:42:33.230
<v Speaker 0>some iRobot age level stuff right here. This

00:42:33.230 --> 00:42:36.510
<v Speaker 0>is I mean, even just the image that's

00:42:36.510 --> 00:42:38.770
<v Speaker 0>on here, and it obviously looks AI generated,

00:42:38.830 --> 00:42:46.085
<v Speaker 0>but but, man, man, oh, man, expect to

00:42:46.085 --> 00:42:50.805
<v Speaker 0>see humanoid robots in, you know, warehouses and

00:42:50.805 --> 00:42:53.045
<v Speaker 0>workplaces within the next ten to fifteen years,

00:42:53.045 --> 00:42:57.224
<v Speaker 0>guys. I it they're already shipping. They're already

00:42:57.285 --> 00:43:08.900
<v Speaker 0>shipping. Another fantastical article, I guess. This one's

00:43:08.900 --> 00:43:13.404
<v Speaker 0>from Yahoo Tech. Aviation startup shares incredible video

00:43:13.404 --> 00:43:18.605
<v Speaker 0>of prototype EVs' maiden takeoff flight. Yes. It's

00:43:18.605 --> 00:43:24.865
<v Speaker 0>true. A flying car. This one does not

00:43:24.924 --> 00:43:27.510
<v Speaker 0>really look what I would have expected a

00:43:27.510 --> 00:43:30.230
<v Speaker 0>flying vehicle to look like. I I don't

00:43:30.230 --> 00:43:33.050
<v Speaker 0>even know how it flies. This this what?

00:43:33.270 --> 00:43:35.050
<v Speaker 0>Okay. Wait. Let me put the video on.

00:43:37.030 --> 00:43:38.565
<v Speaker 0>Let's see. Let's see. There's so there's a

00:43:38.565 --> 00:43:40.085
<v Speaker 0>video here that you guys can tune in

00:43:40.085 --> 00:43:42.325
<v Speaker 0>to The Blackbird has taken flight. We are

00:43:42.325 --> 00:43:44.565
<v Speaker 0>proud to announce the successful maiden flight of

00:43:44.565 --> 00:43:49.125
<v Speaker 0>our Blackbird And the car looks cool. It

00:43:49.125 --> 00:43:54.589
<v Speaker 0>looks like it has, like, wheels, but the

00:43:54.589 --> 00:43:57.069
<v Speaker 0>wheels, I believe, are what allow it to

00:43:57.069 --> 00:44:02.349
<v Speaker 0>fly. But, yeah, the electrical vertical takeoff and

00:44:02.349 --> 00:44:07.895
<v Speaker 0>landing air, eVTOL aircraft makes it experiencing explosive

00:44:07.895 --> 00:44:12.935
<v Speaker 0>makes it what? The electrical vertical takeoff and

00:44:12.935 --> 00:44:17.335
<v Speaker 0>landing aircraft market is experiencing explosive growth in

00:44:17.335 --> 00:44:20.769
<v Speaker 0>twenty twenty five valued at approximately one point

00:44:20.769 --> 00:44:23.170
<v Speaker 0>one nine billion and projected to reach four

00:44:23.170 --> 00:44:24.849
<v Speaker 0>point three six billion by two thousand and

00:44:24.849 --> 00:44:27.009
<v Speaker 0>thirty. So obviously not the same growth as

00:44:27.009 --> 00:44:32.470
<v Speaker 0>the, the robots, I will say, but still

00:44:32.529 --> 00:44:35.490
<v Speaker 0>pretty significant. It's expected to grow about four

00:44:35.490 --> 00:44:39.305
<v Speaker 0>times. The surge is driven by increasing urban

00:44:39.305 --> 00:44:43.305
<v Speaker 0>congestion, environmental concerns, and the aviation industry's pressure

00:44:43.305 --> 00:44:46.365
<v Speaker 0>to reduce carbon emissions by forty five percent

00:44:46.744 --> 00:44:52.150
<v Speaker 0>before twenty thirty. Austrian aviation company, Cyclotec, has

00:44:52.150 --> 00:44:54.390
<v Speaker 0>emerged as an innovator in this space with

00:44:54.390 --> 00:45:00.490
<v Speaker 0>its unique cyclo road cyclo cyclorotor propulsion technology,

00:45:01.285 --> 00:45:06.805
<v Speaker 0>which differs fundamentally from conventional eVTOL designs by

00:45:06.805 --> 00:45:10.005
<v Speaker 0>using barrel shaped rotors inspired by maritime prepare

00:45:10.085 --> 00:45:14.085
<v Speaker 0>propellers. The company's approach enables three hundred sixty

00:45:14.085 --> 00:45:17.480
<v Speaker 0>degree thrust vectoring, allow aircraft to move precisely

00:45:17.620 --> 00:45:20.980
<v Speaker 0>in any direction without needing to reorient their

00:45:20.980 --> 00:45:25.540
<v Speaker 0>body. Wow. The the the the like I

00:45:25.540 --> 00:45:27.540
<v Speaker 0>said, it looks like it's got four wheels

00:45:27.540 --> 00:45:29.460
<v Speaker 0>and a jetpack on the back. It it

00:45:29.460 --> 00:45:33.935
<v Speaker 0>looks cool. As of early twenty twenty five,

00:45:33.935 --> 00:45:37.235
<v Speaker 0>the urban air mo mobility infrastructure is expanding

00:45:37.375 --> 00:45:40.835
<v Speaker 0>rapidly with a hundred fifty six Verti points

00:45:41.135 --> 00:45:45.060
<v Speaker 0>operational globally and another hold on. Let me

00:45:45.060 --> 00:45:47.080
<v Speaker 0>reread that because that that was a mouthful.

00:45:47.380 --> 00:45:49.380
<v Speaker 0>As of early twenty twenty five, the urban

00:45:49.380 --> 00:45:53.300
<v Speaker 0>air mobility infrastructure is expanding rapidly with a

00:45:53.300 --> 00:45:58.365
<v Speaker 0>hundred fifty six Vertiports operational globally and another

00:45:58.365 --> 00:46:01.245
<v Speaker 0>three hundred fifty under construction. What is a

00:46:01.245 --> 00:46:03.165
<v Speaker 0>Vertiport? Is that, like, where one of these

00:46:03.165 --> 00:46:07.005
<v Speaker 0>would fly and land from? Major players like

00:46:07.005 --> 00:46:10.465
<v Speaker 0>Joby Aviation and Archer Aviation dominate the market,

00:46:10.860 --> 00:46:13.660
<v Speaker 0>but companies like Cyclotech are pushing the boundaries

00:46:13.660 --> 00:46:18.160
<v Speaker 0>with alternative propulsion systems that promise unprecedented maneuverability.

00:46:18.940 --> 00:46:22.400
<v Speaker 0>The race to commercialize eVTOL technology is intensifying,

00:46:22.985 --> 00:46:26.765
<v Speaker 0>with most industry observers predicting commercial passenger services

00:46:27.065 --> 00:46:30.025
<v Speaker 0>to emerge as the dominant sector, accounting for

00:46:30.025 --> 00:46:33.065
<v Speaker 0>approximately forty five percent of the total market

00:46:33.065 --> 00:46:37.860
<v Speaker 0>value. Commercial passenger. So maybe like buses, airbuses.

00:46:38.000 --> 00:46:41.840
<v Speaker 0>I would not be against airbuses. Yeah. That

00:46:41.840 --> 00:46:44.240
<v Speaker 0>would be cool, especially with this type of

00:46:44.240 --> 00:46:47.440
<v Speaker 0>design on it. That'd be sick. We'd rather

00:46:47.440 --> 00:46:50.255
<v Speaker 0>ride the bus than sit in traffic. But

00:46:50.255 --> 00:46:53.295
<v Speaker 0>Cyclotek successfully completed the maiden flight of its

00:46:53.295 --> 00:46:57.055
<v Speaker 0>Blackbird eVTOL technology demonstrator on March twenty twenty

00:46:57.055 --> 00:47:00.595
<v Speaker 0>seven twenty twenty five, marking a significant milestone

00:47:00.655 --> 00:47:04.675
<v Speaker 0>achieved just eleven months after initial concept design.

00:47:05.559 --> 00:47:08.040
<v Speaker 0>The three hundred forty kilogram Blackbird is the

00:47:08.040 --> 00:47:11.559
<v Speaker 0>world's first aircraft powered by six advanced seventh

00:47:11.559 --> 00:47:16.680
<v Speaker 0>generational cyclo rotors, featuring four mounted horizontally and

00:47:16.680 --> 00:47:20.140
<v Speaker 0>two vertically to facilitate vertical takeoff and landing.

00:47:20.795 --> 00:47:24.635
<v Speaker 0>During its inaugural unmanned flight, the aircraft demonstrated

00:47:24.635 --> 00:47:28.155
<v Speaker 0>hovering capabilities and validated the operational readiness of

00:47:28.155 --> 00:47:33.375
<v Speaker 0>Cyclotec's electrical prop propulsion, battery system, flight controls,

00:47:33.675 --> 00:47:40.140
<v Speaker 0>software, and avionics. I'm I'm just so blown

00:47:40.140 --> 00:47:41.740
<v Speaker 0>away right now. It literally looks like an

00:47:41.740 --> 00:47:46.540
<v Speaker 0>airboat, like an airship. And if and if

00:47:46.540 --> 00:47:50.025
<v Speaker 0>that's if that's how it works, by by

00:47:50.025 --> 00:47:53.464
<v Speaker 0>propelling itself through the air like we propel

00:47:53.464 --> 00:47:55.705
<v Speaker 0>our boats through the water, then I'm gonna

00:47:55.705 --> 00:47:59.785
<v Speaker 0>be blown away. The cyclorotor technology represents a

00:47:59.785 --> 00:48:03.810
<v Speaker 0>paradigm shift in eVTOL propulsion using barrel shaped

00:48:03.810 --> 00:48:06.610
<v Speaker 0>roll rotors with blades that change angle as

00:48:06.610 --> 00:48:09.830
<v Speaker 0>they spin. This design is the only propulsion

00:48:09.890 --> 00:48:13.410
<v Speaker 0>system capable of controlling thrust vector strength and

00:48:13.410 --> 00:48:16.530
<v Speaker 0>direction in a full three hundred sixty degree

00:48:16.530 --> 00:48:22.855
<v Speaker 0>circular path, enabling advanced maneuvering capabilities, including mid

00:48:22.855 --> 00:48:25.655
<v Speaker 0>air braking, hover with pitch control up to

00:48:25.655 --> 00:48:29.735
<v Speaker 0>thirty degrees, precise landings, and even lateral movements

00:48:29.735 --> 00:48:35.560
<v Speaker 0>like parallel parking. The Blackbird serves as technology

00:48:35.700 --> 00:48:39.320
<v Speaker 0>demonstrator for Cyclotec's larger project, the Cruise Up,

00:48:39.380 --> 00:48:41.940
<v Speaker 0>a two seat personal air vehicle designed for

00:48:41.940 --> 00:48:44.980
<v Speaker 0>urban and suburban travel with a top feet

00:48:44.980 --> 00:48:46.820
<v Speaker 0>of ninety five miles per hour and a

00:48:46.820 --> 00:48:50.625
<v Speaker 0>range of sixty miles, slated for market debut

00:48:50.625 --> 00:48:54.065
<v Speaker 0>in twenty thirty five or later. Cyclotec now

00:48:54.145 --> 00:48:57.185
<v Speaker 0>has now launched an extensive flight test campaign

00:48:57.185 --> 00:48:59.985
<v Speaker 0>to fully characterize the performance envelope and flight

00:48:59.985 --> 00:49:05.620
<v Speaker 0>dynamics of its cyclo rotor based architecture. So

00:49:05.620 --> 00:49:11.380
<v Speaker 0>cool. Just so cool. Hey. But hey. For

00:49:11.380 --> 00:49:14.020
<v Speaker 0>you guys for you technology enthusiasts and those

00:49:14.020 --> 00:49:18.105
<v Speaker 0>launching the future of transportation, Cyclotec's successful demonstration

00:49:18.325 --> 00:49:21.605
<v Speaker 0>represents more than just another eVTOL prototype. Again,

00:49:21.605 --> 00:49:23.845
<v Speaker 0>this is a paradigm shift. This is the

00:49:23.845 --> 00:49:26.745
<v Speaker 0>first of its kind. It showcases an entirely

00:49:26.805 --> 00:49:29.950
<v Speaker 0>different approach to solving the challenges of urban

00:49:29.950 --> 00:49:33.470
<v Speaker 0>air mobility. While most eVTOL companies are pursuing

00:49:33.470 --> 00:49:38.530
<v Speaker 0>conventional rotor or propeller designs, CycloTech's Cyclorotor technology

00:49:38.670 --> 00:49:42.290
<v Speaker 0>offers capabilities that could fundamentally change what's possible

00:49:42.590 --> 00:49:45.964
<v Speaker 0>in personal aviation. The ability to move instantly

00:49:46.025 --> 00:49:49.065
<v Speaker 0>in any direction, break mid air, and maintain

00:49:49.065 --> 00:49:52.664
<v Speaker 0>stable hover even in gusty conditions addresses key

00:49:52.664 --> 00:49:56.025
<v Speaker 0>safety and practicality concerns that have plagued traditional

00:49:56.025 --> 00:49:58.950
<v Speaker 0>vertical flight systems. This could make urban air

00:49:58.950 --> 00:50:01.430
<v Speaker 0>taxis more viable in real world conditions where

00:50:01.430 --> 00:50:08.330
<v Speaker 0>weather and tight spaces are constant challenges. Man,

00:50:08.550 --> 00:50:11.625
<v Speaker 0>who knows? Fifteen years. Maybe fifteen years, we'll

00:50:11.625 --> 00:50:14.825
<v Speaker 0>we'll start well, we'll start seeing Airbuses or

00:50:14.825 --> 00:50:19.865
<v Speaker 0>something. They're saying that the cruise up vehicle

00:50:19.865 --> 00:50:22.425
<v Speaker 0>isn't isn't even expected to twenty thirty five,

00:50:22.425 --> 00:50:26.120
<v Speaker 0>actually. So, never mind. The two man, sixty

00:50:26.120 --> 00:50:29.400
<v Speaker 0>mile vehicle that goes up to ninety five

00:50:29.400 --> 00:50:32.460
<v Speaker 0>miles per hour, it's only gonna be available

00:50:32.600 --> 00:50:34.680
<v Speaker 0>in twenty thirty five or later. So I

00:50:34.680 --> 00:50:37.080
<v Speaker 0>I we're still at the beginning phases of

00:50:37.080 --> 00:50:39.800
<v Speaker 0>this, but this is some epic, epic, epic

00:50:39.800 --> 00:50:41.865
<v Speaker 0>stuff in my opinion. I think this is

00:50:41.865 --> 00:50:49.165
<v Speaker 0>really game changing. Alright. Next article up tonight,

00:50:50.505 --> 00:50:51.945
<v Speaker 0>we're gonna head back down to Earth with

00:50:51.945 --> 00:50:53.865
<v Speaker 0>some more consumer tech. We've been talking a

00:50:53.865 --> 00:50:57.470
<v Speaker 0>lot about phones this year, and Android Central

00:50:57.770 --> 00:50:59.850
<v Speaker 0>has released their best of twenty twenty five

00:50:59.850 --> 00:51:07.470
<v Speaker 0>phone list. This one's written by, Shruti Shekhar

00:51:08.010 --> 00:51:16.665
<v Speaker 0>with contributions from Harish Janalogdha Janalogdha, Derek Lee,

00:51:16.725 --> 00:51:22.965
<v Speaker 0>Nicholas Sutrick, and Andrew Myrick. Thanks, guys. Android

00:51:22.965 --> 00:51:25.360
<v Speaker 0>Central has released its annual best twenty five

00:51:25.440 --> 00:51:28.400
<v Speaker 0>twenty twenty five awards for smartphones, marking a

00:51:28.400 --> 00:51:31.760
<v Speaker 0>significant year in the Android ecosystem characterized by

00:51:31.760 --> 00:51:35.200
<v Speaker 0>substantial advancements in AI powered photography and battery

00:51:35.200 --> 00:51:37.355
<v Speaker 0>technology. The The awards come at a time

00:51:37.355 --> 00:51:40.315
<v Speaker 0>when OnePlus has successfully transformed from a niche

00:51:40.315 --> 00:51:44.714
<v Speaker 0>enthusiast brand to a mainstream flagship competitor, earning

00:51:44.714 --> 00:51:48.095
<v Speaker 0>its second consecutive top spot in Android's central

00:51:48.395 --> 00:51:53.440
<v Speaker 0>rankings. This year's competition was particularly notable for

00:51:53.440 --> 00:51:56.880
<v Speaker 0>showcasing devices with groundbreaking features like seventy three

00:51:56.880 --> 00:52:01.359
<v Speaker 0>hundred mega what is it? Mega amperes? Mega

00:52:01.599 --> 00:52:03.280
<v Speaker 0>I don't know how they measure the what

00:52:03.280 --> 00:52:06.224
<v Speaker 0>what are the what is the the metric

00:52:06.224 --> 00:52:09.904
<v Speaker 0>is used to measure, battery life, m a

00:52:09.904 --> 00:52:13.184
<v Speaker 0>h batteries, and then a hundred sixty five

00:52:13.184 --> 00:52:17.025
<v Speaker 0>hertz displays, which which is crazy because my

00:52:17.025 --> 00:52:19.440
<v Speaker 0>personal monitor, I think it only goes to

00:52:19.440 --> 00:52:21.119
<v Speaker 0>a hundred hertz. I mean, it's ten years

00:52:21.119 --> 00:52:24.960
<v Speaker 0>old, but still. And then Gemini powered camera

00:52:24.960 --> 00:52:27.840
<v Speaker 0>coaching systems that teach users photography principles in

00:52:27.840 --> 00:52:31.484
<v Speaker 0>real time. Oh, that's kinda clever. The smartphone

00:52:31.484 --> 00:52:33.404
<v Speaker 0>landscape in twenty twenty five has been defined

00:52:33.404 --> 00:52:36.125
<v Speaker 0>by a clear shift towards AI integration and

00:52:36.125 --> 00:52:40.525
<v Speaker 0>practical longevity improvements. Google's Pixel ten Pro introduced

00:52:40.525 --> 00:52:42.924
<v Speaker 0>camera coach, a Gemini powered feature that provides

00:52:42.924 --> 00:52:45.424
<v Speaker 0>step by step guidance on lighting and composition

00:52:45.950 --> 00:52:50.510
<v Speaker 0>while teaching foundational camera skills. Meanwhile, manufacturers like

00:52:50.510 --> 00:52:53.970
<v Speaker 0>OnePlus have focused on delivering exceptional value propositions,

00:52:54.110 --> 00:52:58.430
<v Speaker 0>combining flagship tier specifications with competitive pricing and

00:52:58.430 --> 00:53:00.990
<v Speaker 0>extended software support commitments of up to six

00:53:00.990 --> 00:53:04.525
<v Speaker 0>years. The competition between traditional camera leaders like

00:53:04.525 --> 00:53:08.605
<v Speaker 0>Google and emerging challengers like Oppo's Find x

00:53:08.605 --> 00:53:12.525
<v Speaker 0>nine Pro highlights how global availability and market

00:53:12.525 --> 00:53:15.185
<v Speaker 0>access continue to play crucial roles in determining

00:53:15.325 --> 00:53:22.460
<v Speaker 0>category winners. But yeah. So Android Central crowned

00:53:22.460 --> 00:53:25.100
<v Speaker 0>the OnePlus fifteen as the best Android phone

00:53:25.100 --> 00:53:27.820
<v Speaker 0>in twenty twenty five. I guess, it's the

00:53:27.820 --> 00:53:31.040
<v Speaker 0>fastest available processor with its Snapdragon eight Elite,

00:53:31.974 --> 00:53:35.575
<v Speaker 0>three day battery life, which is insane. Three

00:53:35.575 --> 00:53:38.214
<v Speaker 0>day battery life. And then ultra fast charging

00:53:38.214 --> 00:53:42.935
<v Speaker 0>capabilities, the hundred sixty five hertz display, and

00:53:42.935 --> 00:53:44.935
<v Speaker 0>and the advanced eye care features that are

00:53:44.935 --> 00:53:48.160
<v Speaker 0>built into that. So I think it's kinda

00:53:48.160 --> 00:53:50.640
<v Speaker 0>cool. We've really seen the device represent, like,

00:53:50.640 --> 00:53:54.580
<v Speaker 0>OnePlus OnePlus's evolution of it's, like, it's never

00:53:54.720 --> 00:53:59.360
<v Speaker 0>settle philosophy, offering flagship tier features, including excellent

00:53:59.360 --> 00:54:02.525
<v Speaker 0>build quality with IP sixty nine k water

00:54:02.525 --> 00:54:06.525
<v Speaker 0>resistance, haptic feedback, six years of software updates.

00:54:06.525 --> 00:54:09.164
<v Speaker 0>It's it's just great. I think I think

00:54:09.164 --> 00:54:13.484
<v Speaker 0>especially knowing that you're gonna be getting getting

00:54:13.484 --> 00:54:17.760
<v Speaker 0>those guaranteed six years of maintenance. Knowing that

00:54:17.760 --> 00:54:19.920
<v Speaker 0>your phone is not gonna stop receiving updates

00:54:19.920 --> 00:54:21.839
<v Speaker 0>for the next at least six years is

00:54:21.839 --> 00:54:27.575
<v Speaker 0>just fantastic in my opinion. But, yeah, I'm

00:54:27.575 --> 00:54:29.815
<v Speaker 0>not shocked to see the OnePlus dominating the

00:54:29.815 --> 00:54:34.214
<v Speaker 0>markets right now. They've the release was high

00:54:34.214 --> 00:54:39.095
<v Speaker 0>profile, and it was really successful. So I'm

00:54:39.095 --> 00:54:41.994
<v Speaker 0>just I'm just not surprised. Congratulations to them,

00:54:42.295 --> 00:54:48.080
<v Speaker 0>on such a successful release. But this next

00:54:48.080 --> 00:54:51.200
<v Speaker 0>one is a fun one, fun fun in

00:54:51.200 --> 00:54:55.795
<v Speaker 0>a sense. For the pirate archivist groups scraped,

00:54:56.335 --> 00:55:00.335
<v Speaker 0>Spotify's three hundred terabyte library, and they post

00:55:00.335 --> 00:55:04.895
<v Speaker 0>free torrents for downloading. And, you know, this

00:55:04.895 --> 00:55:07.375
<v Speaker 0>one's by Hassan Nasir. I think we've had

00:55:07.375 --> 00:55:09.295
<v Speaker 0>an article by by him before here on

00:55:09.295 --> 00:55:12.940
<v Speaker 0>Tom's Hardware. Thank you again, Hassam. But I

00:55:12.940 --> 00:55:15.819
<v Speaker 0>think I'm I'm I'm I'm on two sides

00:55:15.819 --> 00:55:19.500
<v Speaker 0>with this. So Anna's archive, an open source

00:55:19.500 --> 00:55:22.299
<v Speaker 0>shadow library search engine primarily known for its

00:55:22.299 --> 00:55:25.355
<v Speaker 0>archiving books and academic pagers, has acclaimed responsibility

00:55:26.135 --> 00:55:29.095
<v Speaker 0>for scraping and archiving nearly the entire Spotify

00:55:29.095 --> 00:55:32.375
<v Speaker 0>music library. The organization emerged in twenty twenty

00:55:32.375 --> 00:55:35.655
<v Speaker 0>two immediately following law enforcement shutdown of z

00:55:35.655 --> 00:55:39.335
<v Speaker 0>library and has since aggregate aggregated records from

00:55:39.335 --> 00:55:43.790
<v Speaker 0>z library, the Internet archive, library genesis, and

00:55:43.790 --> 00:55:47.150
<v Speaker 0>Scihub. As of December twenty five, Anna's archive

00:55:47.150 --> 00:55:50.910
<v Speaker 0>hosts more than sixty one million books and

00:55:50.910 --> 00:55:53.605
<v Speaker 0>ninety five million papers and has been banned

00:55:53.605 --> 00:55:58.325
<v Speaker 0>in several countries for repeated copyright violations. Google

00:55:58.325 --> 00:56:00.485
<v Speaker 0>removed nearly eight hundred million links to Anna's

00:56:00.485 --> 00:56:02.405
<v Speaker 0>archive from its search engine in twenty twenty

00:56:02.405 --> 00:56:06.405
<v Speaker 0>five after publishers issue after publishers issued takedown

00:56:06.405 --> 00:56:10.030
<v Speaker 0>requests. The group positions itself as a preservationist

00:56:10.250 --> 00:56:13.050
<v Speaker 0>of human knowledge and culture, arguing that digital

00:56:13.050 --> 00:56:15.210
<v Speaker 0>content needs to be archived and made freely

00:56:15.210 --> 00:56:19.610
<v Speaker 0>available to ensure long term preservation. And on

00:56:19.610 --> 00:56:23.744
<v Speaker 0>this note, I agree. I am strongly in

00:56:23.744 --> 00:56:27.204
<v Speaker 0>line with, sites like the Internet Archive and

00:56:29.665 --> 00:56:33.825
<v Speaker 0>places that make knowledge free for people to

00:56:33.825 --> 00:56:39.920
<v Speaker 0>access. For those of you that, do, you

00:56:39.920 --> 00:56:43.680
<v Speaker 0>know, a little bit more research into some

00:56:43.680 --> 00:56:46.319
<v Speaker 0>of these, you know, businesses, you know, things

00:56:46.319 --> 00:56:49.839
<v Speaker 0>like the educational, you know, research business is

00:56:49.839 --> 00:56:53.045
<v Speaker 0>one of the most profitable profitable businesses in

00:56:53.045 --> 00:56:56.164
<v Speaker 0>the US. You know? Who's paying or, I

00:56:56.164 --> 00:56:58.825
<v Speaker 0>guess, in the world, who's paying those researchers

00:56:59.125 --> 00:57:01.125
<v Speaker 0>to do the research? You know? We submit

00:57:01.125 --> 00:57:04.105
<v Speaker 0>these articles to the to these massive journal

00:57:04.645 --> 00:57:07.030
<v Speaker 0>companies that publish them. And, yeah, you get

00:57:07.030 --> 00:57:09.190
<v Speaker 0>your article published, but you didn't get paid

00:57:09.190 --> 00:57:13.430
<v Speaker 0>for that. Oftentimes, the journal company can now

00:57:13.589 --> 00:57:16.170
<v Speaker 0>or the publishing company can now, you know,

00:57:16.309 --> 00:57:19.155
<v Speaker 0>freely distribute that under their name. And libraries

00:57:19.155 --> 00:57:21.795
<v Speaker 0>and universities pay massive fees every year to

00:57:21.795 --> 00:57:25.235
<v Speaker 0>gain access to these, to these libraries, basically,

00:57:25.235 --> 00:57:28.755
<v Speaker 0>these online archives that allow their students to

00:57:28.755 --> 00:57:31.740
<v Speaker 0>do more research. So it's it's it's a

00:57:31.740 --> 00:57:34.700
<v Speaker 0>self self profit or a self growing industry

00:57:34.700 --> 00:57:36.940
<v Speaker 0>where they get to collect the research for

00:57:36.940 --> 00:57:39.920
<v Speaker 0>free and publish it. They maintain what's actually

00:57:40.140 --> 00:57:43.900
<v Speaker 0>good research, and and being published is is

00:57:43.900 --> 00:57:48.125
<v Speaker 0>a is an amazing thing, but at the

00:57:48.125 --> 00:57:49.645
<v Speaker 0>same time, it's like you're not getting paid

00:57:49.645 --> 00:57:51.085
<v Speaker 0>for that. And this is something I learned

00:57:51.085 --> 00:57:54.125
<v Speaker 0>from, one of my former professors who went

00:57:54.125 --> 00:57:56.525
<v Speaker 0>through this whole publishing process just to prove

00:57:56.525 --> 00:58:00.960
<v Speaker 0>that just to prove that point. But, prior

00:58:01.120 --> 00:58:03.280
<v Speaker 0>but but I think for something like this

00:58:03.280 --> 00:58:07.600
<v Speaker 0>where we're stealing people's music, maybe not the

00:58:07.600 --> 00:58:12.240
<v Speaker 0>best, thing to be, you know, doing as

00:58:12.240 --> 00:58:16.645
<v Speaker 0>a preservationist group, as this is people's personal

00:58:16.645 --> 00:58:18.964
<v Speaker 0>creative works. And on top of that, I

00:58:18.964 --> 00:58:24.805
<v Speaker 0>think making these making that freely downloadable and

00:58:24.805 --> 00:58:31.690
<v Speaker 0>available for potential AI training is also extremely

00:58:31.750 --> 00:58:35.210
<v Speaker 0>problematic because, you know, those people never consented

00:58:35.270 --> 00:58:41.815
<v Speaker 0>to that level of analysis. But, hey, it's

00:58:41.815 --> 00:58:46.215
<v Speaker 0>online. What's stopping someone from recording, you know,

00:58:46.215 --> 00:58:48.375
<v Speaker 0>having a recording of your recording and and

00:58:48.375 --> 00:58:51.815
<v Speaker 0>doing the same thing? Right? So it's it's

00:58:51.815 --> 00:58:55.255
<v Speaker 0>hard to argue for or against. I don't

00:58:55.255 --> 00:58:58.730
<v Speaker 0>think it's right to the people that would

00:58:58.810 --> 00:59:00.970
<v Speaker 0>are are gonna lose money from this in

00:59:00.970 --> 00:59:04.730
<v Speaker 0>terms of, like, the actual creators. Spotify, I

00:59:04.730 --> 00:59:09.710
<v Speaker 0>don't care. They they don't pay their, creatives

00:59:09.770 --> 00:59:13.865
<v Speaker 0>enough, and I think that's been outlined thoroughly

00:59:14.165 --> 00:59:17.285
<v Speaker 0>this year. And, for those of you who

00:59:17.285 --> 00:59:18.725
<v Speaker 0>have listened to the show a long time,

00:59:18.725 --> 00:59:23.045
<v Speaker 0>I'm sure you understand, my father's former stance

00:59:23.045 --> 00:59:25.170
<v Speaker 0>on that as well. But, I mean, I

00:59:25.170 --> 00:59:27.130
<v Speaker 0>I think shortly after he passed, I saw

00:59:27.130 --> 00:59:31.250
<v Speaker 0>a like, one of those hearings with the

00:59:31.250 --> 00:59:34.290
<v Speaker 0>Spotify CEO. And the the whole thing was

00:59:34.290 --> 00:59:37.250
<v Speaker 0>that, you know, they had created a platform

00:59:37.250 --> 00:59:40.875
<v Speaker 0>to make it so that anyone could freely

00:59:41.174 --> 00:59:43.255
<v Speaker 0>try to create you know, make creative works

00:59:43.255 --> 00:59:46.135
<v Speaker 0>and and potentially live off of it. But

00:59:46.135 --> 00:59:48.635
<v Speaker 0>some abysmally low amount of people are actually

00:59:48.934 --> 00:59:52.075
<v Speaker 0>profiting off of their works from Spotify, and

00:59:52.830 --> 00:59:54.510
<v Speaker 0>not many people are actually able to have

00:59:54.510 --> 00:59:57.730
<v Speaker 0>a living wage while the CEO is making

00:59:58.190 --> 01:00:00.850
<v Speaker 0>hundreds of millions of dollars a year. So

01:00:01.310 --> 01:00:03.230
<v Speaker 0>it it it really is kinda interesting. I

01:00:03.230 --> 01:00:04.910
<v Speaker 0>think the the number was, like, hundred seventy

01:00:04.910 --> 01:00:07.965
<v Speaker 0>four million was his salary, which if you

01:00:08.205 --> 01:00:10.685
<v Speaker 0>if the people that you you are claiming

01:00:10.685 --> 01:00:14.605
<v Speaker 0>to support aren't even making you know? Like,

01:00:14.605 --> 01:00:16.365
<v Speaker 0>it's an average of, like, eleven bucks or

01:00:16.365 --> 01:00:18.445
<v Speaker 0>something for the creators. If, like, they're if

01:00:18.445 --> 01:00:20.765
<v Speaker 0>that's average, your your comp your company and

01:00:20.765 --> 01:00:22.770
<v Speaker 0>your platform is supporting, I think you can

01:00:22.770 --> 01:00:25.250
<v Speaker 0>move some of those funds towards the creatives

01:00:25.250 --> 01:00:27.890
<v Speaker 0>and out of your your pockets. That seems

01:00:27.890 --> 01:00:29.510
<v Speaker 0>to make a little more sense to me,

01:00:29.570 --> 01:00:33.490
<v Speaker 0>but I digress. But NS archive claims to

01:00:33.490 --> 01:00:36.470
<v Speaker 0>have scraped Spotify's entire music library, acquiring metadata

01:00:36.530 --> 01:00:40.204
<v Speaker 0>for approximately two hundred fifty six million tracks

01:00:40.825 --> 01:00:43.565
<v Speaker 0>and audio files for eighty six million songs,

01:00:43.944 --> 01:00:47.865
<v Speaker 0>totaling nearly three hundred terabytes of data. According

01:00:47.865 --> 01:00:50.424
<v Speaker 0>to the group's blog post, this archive covers

01:00:50.424 --> 01:00:52.744
<v Speaker 0>around ninety nine point six percent of all

01:00:52.744 --> 01:00:55.760
<v Speaker 0>listings on Spotify, representing what they call the

01:00:55.760 --> 01:00:59.680
<v Speaker 0>world's first preservation archive for music, which is

01:00:59.680 --> 01:01:03.040
<v Speaker 0>fully open. And the largest publicly available music

01:01:03.040 --> 01:01:05.360
<v Speaker 0>metadata base with two hundred fifty six million

01:01:05.360 --> 01:01:08.260
<v Speaker 0>tracks and hundred eighty six million unique ISRCs,

01:01:09.165 --> 01:01:11.485
<v Speaker 0>The music files are being distributed via torrent

01:01:11.485 --> 01:01:14.225
<v Speaker 0>with most tracks preserved in Spotify's original OGT

01:01:14.365 --> 01:01:17.825
<v Speaker 0>Vorbis one sixty kilobytes BPS format. The songs

01:01:17.885 --> 01:01:20.685
<v Speaker 0>with a popularity rating of exactly zero have

01:01:20.685 --> 01:01:24.205
<v Speaker 0>been re encoded to seventy five kilobytes ps

01:01:24.205 --> 01:01:27.779
<v Speaker 0>to save space. Currently, only the metadata has

01:01:27.779 --> 01:01:30.099
<v Speaker 0>been fully released with the actual audio files

01:01:30.099 --> 01:01:33.460
<v Speaker 0>being distributed gradually, starting with the most popular

01:01:33.460 --> 01:01:37.220
<v Speaker 0>tracks. Spotify has confirmed the breach and stated

01:01:37.220 --> 01:01:39.865
<v Speaker 0>that it has identified and disabled the nefarious

01:01:39.865 --> 01:01:42.985
<v Speaker 0>user accounts that engaged in unlawful scraping and

01:01:42.985 --> 01:01:45.465
<v Speaker 0>implemented new safeguards for these types of anti

01:01:45.465 --> 01:01:48.905
<v Speaker 0>copyright attacks. The company characterized the perpetrators as

01:01:48.905 --> 01:01:52.745
<v Speaker 0>anti copyright extremists who've previously private pirated content

01:01:52.745 --> 01:01:56.260
<v Speaker 0>from YouTube and other platforms. Emphasizing that since

01:01:56.260 --> 01:01:58.500
<v Speaker 0>day one, we have stood with artist community

01:01:58.500 --> 01:02:00.900
<v Speaker 0>against piracy, and we are actively working with

01:02:00.900 --> 01:02:03.220
<v Speaker 0>our industry partners to protect creators and defend

01:02:03.220 --> 01:02:05.140
<v Speaker 0>their rights. We'll pay them too instead of

01:02:05.140 --> 01:02:08.905
<v Speaker 0>just defending their rights. Spotify indicated that there's

01:02:08.905 --> 01:02:11.785
<v Speaker 0>no evidence that non public user information was

01:02:11.785 --> 01:02:15.085
<v Speaker 0>compromised with the only user related data involved

01:02:15.145 --> 01:02:18.425
<v Speaker 0>relating to public playlist created by users. Beyond

01:02:18.425 --> 01:02:21.740
<v Speaker 0>immediate piracy concerns, the music industry is worried

01:02:21.740 --> 01:02:24.619
<v Speaker 0>about potential implications for AI training as similar

01:02:24.619 --> 01:02:27.980
<v Speaker 0>datasets from YouTube have been used unlicensed have

01:02:27.980 --> 01:02:30.800
<v Speaker 0>been used by unlicensed AI music generation services

01:02:30.859 --> 01:02:33.920
<v Speaker 0>to train their models, which could undermine licensing

01:02:34.060 --> 01:02:37.195
<v Speaker 0>efforts with a with AI firms. Exactly. But

01:02:37.195 --> 01:02:40.734
<v Speaker 0>I again, so if if it is available

01:02:40.795 --> 01:02:44.075
<v Speaker 0>online and it it just because it's it's

01:02:44.075 --> 01:02:48.075
<v Speaker 0>hard to to to to justify because you

01:02:48.075 --> 01:02:49.915
<v Speaker 0>you will never be able to stop someone

01:02:49.915 --> 01:02:53.560
<v Speaker 0>from being able to save or or steal

01:02:53.780 --> 01:02:55.940
<v Speaker 0>this type of data. Right? The music or

01:02:55.940 --> 01:02:57.700
<v Speaker 0>or an art piece. You know? A picture

01:02:57.700 --> 01:03:01.140
<v Speaker 0>is enough. Right? And it although it's not

01:03:01.140 --> 01:03:06.085
<v Speaker 0>the the original, the the the techniques and

01:03:06.085 --> 01:03:08.325
<v Speaker 0>intent that are built into the piece are

01:03:08.325 --> 01:03:14.484
<v Speaker 0>are there. So kind of a interesting, and

01:03:14.484 --> 01:03:15.765
<v Speaker 0>I'm I'm sure we're gonna see a lot

01:03:15.765 --> 01:03:18.644
<v Speaker 0>of this, in the next few years in

01:03:18.644 --> 01:03:22.460
<v Speaker 0>terms of, you know, more data being stolen

01:03:22.760 --> 01:03:27.020
<v Speaker 0>and, at the same time, the concern being

01:03:27.080 --> 01:03:30.760
<v Speaker 0>the AI training that is going, on behind

01:03:30.760 --> 01:03:36.655
<v Speaker 0>the scenes with these, stolen datasets. Let's move

01:03:36.655 --> 01:03:40.275
<v Speaker 0>on. This one's a little bit mind bending.

01:03:41.214 --> 01:03:44.755
<v Speaker 0>This breakthrough brain simulation captures a true brain

01:03:44.974 --> 01:03:48.355
<v Speaker 0>at work. So this one's from Popular Mechanics

01:03:48.494 --> 01:03:56.730
<v Speaker 0>written by Stav. Oh, Dimitropoulos Dimitropoulos. Alright. I'm

01:03:56.730 --> 01:03:58.810
<v Speaker 0>horrible at saying these last names. I'll try

01:03:58.810 --> 01:04:03.915
<v Speaker 0>harder. But for decades, neuroscientists have dreamed of

01:04:04.235 --> 01:04:06.875
<v Speaker 0>creating detailed digital models of the brain to

01:04:06.875 --> 01:04:09.755
<v Speaker 0>unlock its mysteries and develop better treatments for

01:04:09.755 --> 01:04:13.515
<v Speaker 0>neurological diseases. However, the brain's complexity with billions

01:04:13.515 --> 01:04:16.155
<v Speaker 0>of neurons and trillions of connections has made

01:04:16.155 --> 01:04:20.540
<v Speaker 0>this vision extraordinarily challenging to achieve. Early brain

01:04:20.540 --> 01:04:23.200
<v Speaker 0>simulations were either too simplified to capture realistic

01:04:23.260 --> 01:04:26.460
<v Speaker 0>behavior or so computationally expensive that that they

01:04:26.460 --> 01:04:29.120
<v Speaker 0>could only model tiny fragments of brain tissue.

01:04:29.820 --> 01:04:32.140
<v Speaker 0>The gap between what scientists wanted to simulate

01:04:32.140 --> 01:04:34.800
<v Speaker 0>and what was technically feasible has been enormous,

01:04:35.214 --> 01:04:37.934
<v Speaker 0>limiting our ability to study brain functions, test

01:04:37.934 --> 01:04:41.214
<v Speaker 0>treatments, or understand how diseases like Alzheimer's and

01:04:41.214 --> 01:04:45.694
<v Speaker 0>epilepsy spread through neural networks. Recent advances in

01:04:45.694 --> 01:04:49.500
<v Speaker 0>supercomputing power and neuroscience data collection have converged

01:04:49.640 --> 01:04:53.640
<v Speaker 0>to make unprecedented brain simulations possible. In November

01:04:53.640 --> 01:04:56.680
<v Speaker 0>twenty twenty five, researchers from the Allen Institute,

01:04:56.680 --> 01:04:59.900
<v Speaker 0>in collaboration with Japan's University of Electro Communications

01:05:00.280 --> 01:05:04.255
<v Speaker 0>at RIKEN Center for Computational Science, announced one

01:05:04.255 --> 01:05:06.975
<v Speaker 0>of the most detailed virtual brain simulations ever

01:05:06.975 --> 01:05:11.135
<v Speaker 0>created. Using Japan's Fugaku supercomputer, one of the

01:05:11.135 --> 01:05:14.115
<v Speaker 0>world's fastest with over seven point six million

01:05:14.335 --> 01:05:17.160
<v Speaker 0>cores and capable of more than four hundred

01:05:17.160 --> 01:05:21.560
<v Speaker 0>quadrillion operations per second. They successfully simulated an

01:05:21.560 --> 01:05:25.480
<v Speaker 0>entire mouse cortex comprising nearly ten million neurons

01:05:25.480 --> 01:05:28.700
<v Speaker 0>and twenty six billion synapses across eighty six

01:05:28.760 --> 01:05:32.974
<v Speaker 0>interconnected brain regions. This represents the largest biophysically

01:05:33.275 --> 01:05:36.734
<v Speaker 0>realistic model of the mouse cortex to date,

01:05:36.954 --> 01:05:40.875
<v Speaker 0>marking a critical milestone towards eventual whole brain

01:05:40.875 --> 01:05:46.529
<v Speaker 0>simulations of larger animals and potentially humans. Wow.

01:05:46.589 --> 01:05:50.609
<v Speaker 0>That's cool. That's really cool. The breakthrough simulation

01:05:50.670 --> 01:05:53.329
<v Speaker 0>runs on all one hundred forty five thousand

01:05:53.470 --> 01:05:55.789
<v Speaker 0>seven hundred twenty eight compute nodes of the

01:05:55.789 --> 01:06:00.285
<v Speaker 0>Fugaku supercomputer, creating a fully digital mouse cortex

01:06:00.285 --> 01:06:03.345
<v Speaker 0>where millions of neurons fire and electrical signals

01:06:03.405 --> 01:06:05.725
<v Speaker 0>cascade through billions of connections just as they

01:06:05.725 --> 01:06:08.285
<v Speaker 0>would in a living brain. What makes this

01:06:08.285 --> 01:06:10.845
<v Speaker 0>simulation remarkable is not just its scale, but

01:06:10.845 --> 01:06:14.470
<v Speaker 0>its biophysical accuracy. It follows the brain's actual

01:06:14.470 --> 01:06:19.349
<v Speaker 0>biological rules rather than simplified approximations. Researchers can

01:06:19.349 --> 01:06:23.109
<v Speaker 0>pause the simulation, rewind it, zoom into single

01:06:23.109 --> 01:06:26.069
<v Speaker 0>synapses, and replay moments of neural activity with

01:06:26.069 --> 01:06:30.215
<v Speaker 0>unprecedented detail. The Allen Institute provides the virtual

01:06:30.215 --> 01:06:33.575
<v Speaker 0>brain's blueprint and biophysical properties, the real data

01:06:33.575 --> 01:06:36.615
<v Speaker 0>from the Allen cell types database and Allen

01:06:36.615 --> 01:06:40.455
<v Speaker 0>Connectivity Atlas, while Japan's Fugaku com provided the

01:06:40.455 --> 01:06:42.780
<v Speaker 0>computational power to bring this data to life

01:06:42.860 --> 01:06:46.480
<v Speaker 0>using specialized neuron simulator software called New Light.

01:06:47.580 --> 01:06:50.620
<v Speaker 0>This achievement opens new possibilities for neuroscience research

01:06:50.620 --> 01:06:54.160
<v Speaker 0>and medical applications. Scientists can now simulate diseases

01:06:54.380 --> 01:06:57.500
<v Speaker 0>like Alzheimer's or epilepsy in the virtual world

01:06:57.500 --> 01:07:00.265
<v Speaker 0>and watch in detail how damage spreads through

01:07:00.265 --> 01:07:04.825
<v Speaker 0>neural networks, test potential treatments without risking living

01:07:04.825 --> 01:07:08.045
<v Speaker 0>subjects, and conduct experiments that would be impossible

01:07:08.185 --> 01:07:12.119
<v Speaker 0>or unethical in real animals. According to doctor

01:07:12.180 --> 01:07:17.400
<v Speaker 0>Anton Arkhipov, an investigator at the Allen Institute,

01:07:17.859 --> 01:07:21.300
<v Speaker 0>this work demonstrates that very detailed microscopic level

01:07:21.300 --> 01:07:24.280
<v Speaker 0>simulations of larger brains may be possible sooner

01:07:24.500 --> 01:07:27.845
<v Speaker 0>than previously expected, suggesting that a simulation of

01:07:27.845 --> 01:07:31.045
<v Speaker 0>a whole macaque monkey brain with six billion

01:07:31.045 --> 01:07:33.525
<v Speaker 0>neurons could fit on the full scale Fugaku

01:07:33.525 --> 01:07:36.244
<v Speaker 0>system. Long term goal is to build whole

01:07:36.244 --> 01:07:40.140
<v Speaker 0>brain models eventually, even human models, using all

01:07:40.140 --> 01:07:43.359
<v Speaker 0>the biological details the institute continues to uncover.

01:07:44.059 --> 01:07:46.859
<v Speaker 0>This research connects to broader developments in in

01:07:46.859 --> 01:07:50.380
<v Speaker 0>digital twin brain technology, where AI powered models

01:07:50.380 --> 01:07:53.615
<v Speaker 0>can predict brain responses to stimuli and enable

01:07:53.675 --> 01:07:59.275
<v Speaker 0>personalized medicine approaches from neurological conditions. That is

01:07:59.275 --> 01:08:01.035
<v Speaker 0>crazy. Hey. If you wanna live in a

01:08:01.035 --> 01:08:03.115
<v Speaker 0>computer, I'm sure they're gonna have brain mapping

01:08:03.115 --> 01:08:05.695
<v Speaker 0>and transference in the next twenty five years.

01:08:06.260 --> 01:08:08.020
<v Speaker 0>And then you could be a virtual man

01:08:08.020 --> 01:08:12.180
<v Speaker 0>forever or a virtual woman. But this I

01:08:12.180 --> 01:08:16.360
<v Speaker 0>think this is fantastic. It's amazing. This is

01:08:17.460 --> 01:08:25.155
<v Speaker 0>amazing use of science and our time, but

01:08:25.155 --> 01:08:28.035
<v Speaker 0>really, really, really impressive. I think this breakthrough

01:08:28.035 --> 01:08:30.115
<v Speaker 0>represents a fundamental shift in how we can

01:08:30.115 --> 01:08:33.075
<v Speaker 0>study the brain, you know, develop treatments for

01:08:33.075 --> 01:08:38.130
<v Speaker 0>neurological diseases, actually understand how, yeah, Alzheimer's and

01:08:38.130 --> 01:08:43.730
<v Speaker 0>other brain diseases develop. This is cool. Really

01:08:43.730 --> 01:08:48.130
<v Speaker 0>impressive breakthrough by The Allen Institute and Japan's

01:08:48.130 --> 01:08:53.405
<v Speaker 0>Fugaku computer. Pretty cool stuff. And, you know,

01:08:53.405 --> 01:08:58.285
<v Speaker 0>a little bit more Japanese news. This is

01:08:58.285 --> 01:08:59.405
<v Speaker 0>the last one I got for you guys

01:08:59.405 --> 01:09:01.485
<v Speaker 0>tonight. Sorry. I just just wanted a little

01:09:01.485 --> 01:09:03.510
<v Speaker 0>long. I didn't really expect to go this

01:09:03.510 --> 01:09:07.110
<v Speaker 0>deep on all my articles, but Japan prepares

01:09:07.110 --> 01:09:10.949
<v Speaker 0>to restart the world's biggest nuclear plant fifteen

01:09:10.949 --> 01:09:16.070
<v Speaker 0>years after the Fukushima incident. So, yes, it

01:09:16.070 --> 01:09:20.224
<v Speaker 0>looks like we're turning Fukushima back on. The

01:09:20.224 --> 01:09:25.844
<v Speaker 0>Kashiwazaki the Kashiwazaki karionu nuclear power station located

01:09:25.905 --> 01:09:29.425
<v Speaker 0>in Niigata Prefecture about three hundred kilometers north

01:09:29.425 --> 01:09:33.150
<v Speaker 0>of Tokyo is the world's largest nuclear power

01:09:33.150 --> 01:09:37.710
<v Speaker 0>plant by capacity with seven reactor units. Following

01:09:37.710 --> 01:09:41.550
<v Speaker 0>the devastating two thousand eleven Fukushima Daiichi nuclear

01:09:41.550 --> 01:09:44.450
<v Speaker 0>disaster triggered by the nine point o magnitude

01:09:44.670 --> 01:09:48.455
<v Speaker 0>earthquake and tsunami, Japan shut down all fifty

01:09:48.455 --> 01:09:51.755
<v Speaker 0>four of its nuclear power stations, including Kashiwazaki,

01:09:52.295 --> 01:09:57.034
<v Speaker 0>Kariba. The plant has experienced troubles before Fukushima.

01:09:57.735 --> 01:09:59.574
<v Speaker 0>In two thousand seven, it was shut down

01:09:59.574 --> 01:10:02.360
<v Speaker 0>for twenty one months after a magnitude six

01:10:02.360 --> 01:10:05.400
<v Speaker 0>point six earthquake caused small radiation leaks and

01:10:05.400 --> 01:10:08.280
<v Speaker 0>fires. And then more recently in twenty twenty

01:10:08.280 --> 01:10:11.179
<v Speaker 0>one, regulators effectively banned the plant from restarting

01:10:11.320 --> 01:10:15.364
<v Speaker 0>due to security breaches and falsified safety inspections

01:10:15.425 --> 01:10:19.344
<v Speaker 0>by its operators, Tokyo Electric Power Company. It's

01:10:19.344 --> 01:10:21.764
<v Speaker 0>the same company that ran the Fukushima plant.

01:10:22.304 --> 01:10:27.440
<v Speaker 0>So Japan's energy landscape has kinda gone undergone

01:10:27.440 --> 01:10:31.520
<v Speaker 0>significant changes since this Fukushima disaster. Before two

01:10:31.520 --> 01:10:34.400
<v Speaker 0>thousand eleven, the nuclear reactors provided around thirty

01:10:34.400 --> 01:10:38.560
<v Speaker 0>percent of the country's electricity. And since then,

01:10:38.560 --> 01:10:41.040
<v Speaker 0>Japan basically has had to rely on imported

01:10:41.040 --> 01:10:45.215
<v Speaker 0>fossil fuels. So that that makes about sixty

01:10:45.215 --> 01:10:47.295
<v Speaker 0>seven percent of their power generation coming from

01:10:47.295 --> 01:10:49.855
<v Speaker 0>coal and gas imports and which will cost

01:10:49.855 --> 01:10:52.735
<v Speaker 0>them about ten point seven trillion dollars, last

01:10:52.735 --> 01:10:55.535
<v Speaker 0>year alone or ten point seven trillion yen.

01:10:55.535 --> 01:11:00.150
<v Speaker 0>Excuse me. That's a magnitude of difference. Sixty

01:11:00.150 --> 01:11:04.070
<v Speaker 0>eight billion dollars. In February twenty twenty five,

01:11:04.070 --> 01:11:07.270
<v Speaker 0>Japan's government approved a new strategic energy plan

01:11:07.270 --> 01:11:09.590
<v Speaker 0>that for the first time since Fukushima removed

01:11:09.590 --> 01:11:13.125
<v Speaker 0>language about minimizing nuclear dependence and instead called

01:11:13.125 --> 01:11:16.585
<v Speaker 0>for making maximum use of existing nuclear plants.

01:11:16.724 --> 01:11:19.364
<v Speaker 0>This policy shift aims to double new double

01:11:19.364 --> 01:11:22.344
<v Speaker 0>nuclear power share in Japan's electricity mix from

01:11:22.485 --> 01:11:24.930
<v Speaker 0>ten percent to twenty percent by twenty forty,

01:11:25.250 --> 01:11:28.050
<v Speaker 0>driven by rising energy demand from AI data

01:11:28.050 --> 01:11:30.610
<v Speaker 0>centers and the need to reduce reliance on

01:11:30.610 --> 01:11:34.310
<v Speaker 0>expensive fossil fuel imports while meeting climate commitments.

01:11:35.170 --> 01:11:40.055
<v Speaker 0>Man. You know? And from my understanding, most

01:11:40.275 --> 01:11:43.795
<v Speaker 0>most people are against the reactor coming back

01:11:43.795 --> 01:11:46.435
<v Speaker 0>on, especially the locals. Oh, yeah. Here it

01:11:46.435 --> 01:11:50.115
<v Speaker 0>is. A prefectural survey published in October showed

01:11:50.115 --> 01:11:53.640
<v Speaker 0>that sixty one percent of local resident residents

01:11:53.640 --> 01:11:55.960
<v Speaker 0>believe conditions for a restart have not been

01:11:55.960 --> 01:12:00.300
<v Speaker 0>met. Nearly seventy percent expressed concerns about TEPCO's

01:12:00.440 --> 01:12:03.560
<v Speaker 0>ability to operate the plant safely. And this

01:12:03.560 --> 01:12:08.085
<v Speaker 0>is literally because of their, you know, falsified

01:12:08.085 --> 01:12:13.685
<v Speaker 0>safety inspections, the the the failure of, two

01:12:13.685 --> 01:12:19.045
<v Speaker 0>thousand eleven when the, when the tsunami hit

01:12:19.045 --> 01:12:20.325
<v Speaker 0>back then. I'm not sure how many of

01:12:20.325 --> 01:12:26.860
<v Speaker 0>you guys remember that, but I think they

01:12:26.860 --> 01:12:28.780
<v Speaker 0>are getting to a point where they they

01:12:28.780 --> 01:12:30.860
<v Speaker 0>don't have a choice. They need to turn

01:12:30.860 --> 01:12:33.180
<v Speaker 0>them back on with all the AI stuff

01:12:33.180 --> 01:12:36.315
<v Speaker 0>that's starting to come into play. One of

01:12:36.315 --> 01:12:38.715
<v Speaker 0>the most popular ads I always see on

01:12:38.715 --> 01:12:41.215
<v Speaker 0>Abima is, they have this app called CookieChat,

01:12:41.915 --> 01:12:45.275
<v Speaker 0>and it's literally your personal AI boyfriend or

01:12:45.275 --> 01:12:50.560
<v Speaker 0>girlfriend on your app. And, you know, I

01:12:50.560 --> 01:12:56.260
<v Speaker 0>think we've all heard, historically about Japan's problems

01:12:56.400 --> 01:13:01.760
<v Speaker 0>with, you know, the children or or, like,

01:13:01.760 --> 01:13:07.555
<v Speaker 0>having children and the generation of otakus and

01:13:07.555 --> 01:13:12.775
<v Speaker 0>whatnot that have further dropped the birth rates

01:13:13.155 --> 01:13:15.975
<v Speaker 0>in Japan. And now we're seeing, you know,

01:13:18.180 --> 01:13:21.640
<v Speaker 0>AI chatbots that are designed as dating tools.

01:13:23.700 --> 01:13:25.560
<v Speaker 0>You know, I I find that really concerning,

01:13:26.180 --> 01:13:30.580
<v Speaker 0>but it it would be it'll be interesting

01:13:30.580 --> 01:13:35.335
<v Speaker 0>to kinda see how they they they relaunch

01:13:35.395 --> 01:13:41.955
<v Speaker 0>this going into, the next fifteen years. So

01:13:41.955 --> 01:13:43.315
<v Speaker 0>definitely keep an eye on this one and

01:13:43.315 --> 01:13:45.075
<v Speaker 0>keep you guys posted, but that's all I

01:13:45.075 --> 01:13:47.555
<v Speaker 0>got for you guys tonight. Really long show.

01:13:47.795 --> 01:13:49.369
<v Speaker 0>I didn't really expect to go go this

01:13:49.369 --> 01:13:52.250
<v Speaker 0>long tonight, but, hey, thanks for hanging out

01:13:52.250 --> 01:13:54.110
<v Speaker 0>if you guys are here up until now.

01:13:54.570 --> 01:13:56.409
<v Speaker 0>Happy happy New Year to those of you

01:13:56.409 --> 01:14:01.065
<v Speaker 0>that are listening, still in twenty twenty five.

01:14:01.465 --> 01:14:02.985
<v Speaker 0>And for those of you in twenty twenty

01:14:02.985 --> 01:14:05.645
<v Speaker 0>six, I hope, your New Year went well.

01:14:05.945 --> 01:14:09.785
<v Speaker 0>And I hope, if you guys do end

01:14:09.785 --> 01:14:13.005
<v Speaker 0>up setting yourself a New Year resolution, which

01:14:13.530 --> 01:14:15.690
<v Speaker 0>I'm not I haven't met many people this

01:14:15.690 --> 01:14:17.530
<v Speaker 0>year that have that have told me that

01:14:17.530 --> 01:14:19.050
<v Speaker 0>they're doing them. I asked a lot of

01:14:19.050 --> 01:14:20.890
<v Speaker 0>my customers, not a lot of people doing

01:14:20.890 --> 01:14:23.770
<v Speaker 0>them. So don't feel obligated, but it is

01:14:23.770 --> 01:14:25.850
<v Speaker 0>a time of change, real real good time

01:14:25.850 --> 01:14:28.010
<v Speaker 0>to to take a look at yourself, self

01:14:28.010 --> 01:14:30.665
<v Speaker 0>reflect, and, you know, get your life in

01:14:30.665 --> 01:14:34.525
<v Speaker 0>order if it's not. But have an amazing

01:14:34.825 --> 01:14:37.865
<v Speaker 0>New Year, folks, and a great night. Hopefully,

01:14:37.865 --> 01:14:39.065
<v Speaker 0>next year, we can be a little more

01:14:39.065 --> 01:14:40.905
<v Speaker 0>consistent for you folks with delivering on the

01:14:40.905 --> 01:14:45.758
<v Speaker 0>shows, but thanks for tuning in regardless. Have
