WEBVTT

NOTE
Transcription provided by Deepgram

00:00:01.439 --> 00:00:03.439
<v Speaker 0>Hi there. Hello. Welcome to the Geek News

00:00:03.439 --> 00:00:06.799
<v Speaker 0>Central podcast, eighteen forty five. We got a

00:00:06.799 --> 00:00:08.580
<v Speaker 0>great show lined up for you guys tonight.

00:00:09.360 --> 00:00:13.840
<v Speaker 0>Lead story. OpenAI turns ChatTBT into an app

00:00:13.840 --> 00:00:18.625
<v Speaker 0>platform. Yeah. At Dev Day twenty twenty five,

00:00:18.625 --> 00:00:21.585
<v Speaker 0>OpenAI announced that ChatTBT is evolving from a

00:00:21.585 --> 00:00:24.705
<v Speaker 0>chatbot into a full blown app platform. Through

00:00:24.705 --> 00:00:28.230
<v Speaker 0>a new ChatTBT apps SDK, developers can build

00:00:28.230 --> 00:00:30.490
<v Speaker 0>plug and play apps that run inside ChatGPT,

00:00:30.789 --> 00:00:33.930
<v Speaker 0>giving users access to tools like Canva, Zillow,

00:00:34.070 --> 00:00:38.870
<v Speaker 0>Spotify, and Coursera without leaving the chat. Let's

00:00:38.870 --> 00:00:40.629
<v Speaker 0>get into the article. This is a really

00:00:40.629 --> 00:00:43.110
<v Speaker 0>exciting one. They just announced this on October

00:00:43.110 --> 00:00:46.545
<v Speaker 0>sixth, but really, really exciting news to kinda

00:00:46.545 --> 00:00:49.425
<v Speaker 0>see them bringing those API endpoints directly into

00:00:49.425 --> 00:00:53.585
<v Speaker 0>the chat. It's kinda cool. So here's a,

00:00:54.385 --> 00:00:57.265
<v Speaker 0>yes, one of my dad's love hate sites,

00:00:57.265 --> 00:01:01.210
<v Speaker 0>The Verge. OpenAI will let developers build apps

00:01:01.210 --> 00:01:06.410
<v Speaker 0>that work inside ChatGPT. OpenAI is introducing a

00:01:06.410 --> 00:01:08.510
<v Speaker 0>way to work with apps right inside ChatGPT.

00:01:09.210 --> 00:01:11.370
<v Speaker 0>For software and services that connect to a

00:01:11.370 --> 00:01:14.585
<v Speaker 0>new ChatGPT SDK, now you can tag in

00:01:14.585 --> 00:01:16.345
<v Speaker 0>their apps to help you complete a task

00:01:16.345 --> 00:01:20.104
<v Speaker 0>while ChatGPT offers context and advice. The company

00:01:20.104 --> 00:01:22.024
<v Speaker 0>showed off a few different ways that this

00:01:22.024 --> 00:01:24.845
<v Speaker 0>can work. In a live demo, an OpenAI

00:01:24.985 --> 00:01:27.780
<v Speaker 0>employee launched ChatGPT and then asked Canva to

00:01:27.780 --> 00:01:29.299
<v Speaker 0>create a poster of a name for a

00:01:29.299 --> 00:01:34.500
<v Speaker 0>dog walking business. Say what? After a bit

00:01:34.500 --> 00:01:36.340
<v Speaker 0>of waiting, Canva came back with a few

00:01:36.340 --> 00:01:38.580
<v Speaker 0>different examples, and the presenter followed up by

00:01:38.580 --> 00:01:41.140
<v Speaker 0>asking for a generated pitch deck based on

00:01:41.140 --> 00:01:44.325
<v Speaker 0>the poster. The employee also asked Zillow via

00:01:44.325 --> 00:01:47.385
<v Speaker 0>Chativity to show homes for sale in Pittsburgh,

00:01:47.525 --> 00:01:49.685
<v Speaker 0>and it created an interactive Zillow map that

00:01:49.685 --> 00:01:52.725
<v Speaker 0>the employee then asked follow-up questions about. Isn't

00:01:52.725 --> 00:01:56.579
<v Speaker 0>that amazing? I think we were kinda waiting

00:01:56.579 --> 00:01:58.020
<v Speaker 0>for this. We didn't know what was next,

00:01:58.020 --> 00:01:59.939
<v Speaker 0>but we were waiting for something kinda big.

00:01:59.939 --> 00:02:02.180
<v Speaker 0>They already kinda had this with, some other

00:02:02.180 --> 00:02:05.079
<v Speaker 0>Google integrations like Drive or you could, like,

00:02:05.539 --> 00:02:07.795
<v Speaker 0>link a page through, you know, sharing to

00:02:07.795 --> 00:02:09.315
<v Speaker 0>the app, but this is, like, on another

00:02:09.315 --> 00:02:13.075
<v Speaker 0>level. Everything from within the app. What a

00:02:13.075 --> 00:02:19.175
<v Speaker 0>fantastic, fantastic little, like, release they got here.

00:02:21.550 --> 00:02:25.630
<v Speaker 0>Anyway, yeah, really, really awesome stuff coming out

00:02:25.630 --> 00:02:30.770
<v Speaker 0>from, Chat GPT, OpenAI. Let's, kinda get into

00:02:31.069 --> 00:02:33.810
<v Speaker 0>the rest of the show. This is Ray,

00:02:34.525 --> 00:02:38.284
<v Speaker 0>checking in for my weekly show and kinda

00:02:38.284 --> 00:02:42.224
<v Speaker 0>talk about some new stuff with me. Kinda

00:02:43.004 --> 00:02:45.245
<v Speaker 0>rounding out the middle of the week for

00:02:45.245 --> 00:02:47.245
<v Speaker 0>my second week of back to school, my

00:02:47.245 --> 00:02:50.519
<v Speaker 0>senior year here at Portland State doing a

00:02:50.519 --> 00:02:54.760
<v Speaker 0>computer science degree. And I feel like the

00:02:54.760 --> 00:02:57.340
<v Speaker 0>courses this term have really taken a sharp

00:02:58.200 --> 00:03:02.280
<v Speaker 0>upturn in, difficulty. Today's course was like a

00:03:02.280 --> 00:03:07.665
<v Speaker 0>visual programming class and really getting into the

00:03:07.665 --> 00:03:13.445
<v Speaker 0>math behind, doing masking and filtering and and

00:03:13.505 --> 00:03:17.745
<v Speaker 0>understanding, like, image topography, edge detection. It was

00:03:17.745 --> 00:03:20.645
<v Speaker 0>really interesting, but really complicated as well. So

00:03:20.920 --> 00:03:22.360
<v Speaker 0>a lot of focus being put in that

00:03:22.360 --> 00:03:26.840
<v Speaker 0>direction, I guess. Few other courses that kinda

00:03:26.840 --> 00:03:29.099
<v Speaker 0>on par with that, but I'm definitely enjoying

00:03:29.159 --> 00:03:31.319
<v Speaker 0>the the rigor. It's gonna be a nice

00:03:31.319 --> 00:03:34.280
<v Speaker 0>change. And then we got some cool updates

00:03:34.280 --> 00:03:38.065
<v Speaker 0>rolling out at Blueberry. Hopefully, we can been

00:03:38.065 --> 00:03:39.665
<v Speaker 0>working on a little power press change, so,

00:03:39.665 --> 00:03:41.905
<v Speaker 0>hopefully, we can get that out soon. That'd

00:03:41.905 --> 00:03:45.185
<v Speaker 0>be a nice, little benefit for everyone if

00:03:45.185 --> 00:03:46.785
<v Speaker 0>you want to take advantage of podcast two

00:03:46.785 --> 00:03:48.625
<v Speaker 0>point o if you're straight from their WordPress

00:03:48.625 --> 00:03:55.210
<v Speaker 0>website. But, yeah, let's, let's talk about, our

00:03:55.210 --> 00:03:58.650
<v Speaker 0>incredible sponsor, GoDaddy. Talking about WordPress already. Just

00:03:58.650 --> 00:04:01.130
<v Speaker 0>lead right into it. Score exclusive deals and

00:04:01.130 --> 00:04:03.130
<v Speaker 0>discounts right now at geek news central dot

00:04:03.130 --> 00:04:06.094
<v Speaker 0>com forward slash GoDaddy. And to you guys,

00:04:06.094 --> 00:04:08.094
<v Speaker 0>all of our listeners, you are truly the

00:04:08.094 --> 00:04:10.415
<v Speaker 0>heartbeat of this show. If you wanna support

00:04:10.415 --> 00:04:12.734
<v Speaker 0>Geek News Central directly, head over to geek

00:04:12.734 --> 00:04:15.215
<v Speaker 0>news central dot com forward slash insider and

00:04:15.215 --> 00:04:19.640
<v Speaker 0>become a GNC insider. Grab yourself a modern

00:04:19.640 --> 00:04:21.960
<v Speaker 0>podcast app at podcast apps dot com for

00:04:21.960 --> 00:04:25.480
<v Speaker 0>the full next gen podcast experience. Of course,

00:04:25.480 --> 00:04:27.240
<v Speaker 0>you can check out the entire Geek News

00:04:27.240 --> 00:04:29.655
<v Speaker 0>Central universe at geek news central dot com

00:04:29.735 --> 00:04:31.995
<v Speaker 0>where you'll find all our partner shows and

00:04:32.055 --> 00:04:34.795
<v Speaker 0>tons of great content published every single week.

00:04:35.735 --> 00:04:37.895
<v Speaker 0>Stay in the loop, follow or subscribe in

00:04:37.895 --> 00:04:39.735
<v Speaker 0>your favorite podcast app, and don't forget to

00:04:39.735 --> 00:04:41.895
<v Speaker 0>sign up for our newsletter for more behind

00:04:41.895 --> 00:04:44.820
<v Speaker 0>the scenes updates and insider scoops. You can

00:04:44.820 --> 00:04:46.900
<v Speaker 0>always reach us directly at geek news central

00:04:46.900 --> 00:04:49.460
<v Speaker 0>at g mail dot com. I've, we did

00:04:49.460 --> 00:04:51.699
<v Speaker 0>get some feedback from, some of the longtime

00:04:51.699 --> 00:04:53.960
<v Speaker 0>listeners. Really happy to hear from you folks.

00:04:55.540 --> 00:04:57.699
<v Speaker 0>I think I emailed back a, a Brian

00:04:57.699 --> 00:04:59.780
<v Speaker 0>today so much. Thank you so much for

00:04:59.780 --> 00:05:03.465
<v Speaker 0>your ongoing support. We do plan to do

00:05:03.605 --> 00:05:06.165
<v Speaker 0>a little announcement for all the insiders. I

00:05:06.165 --> 00:05:07.765
<v Speaker 0>didn't get that list ready for today. I

00:05:07.765 --> 00:05:10.105
<v Speaker 0>kinda get a a get all the logistics

00:05:10.165 --> 00:05:12.085
<v Speaker 0>for that figured out still, but I get

00:05:12.085 --> 00:05:13.900
<v Speaker 0>a a little list going so we can

00:05:13.900 --> 00:05:15.340
<v Speaker 0>do some shout outs for you guys. Thank

00:05:15.340 --> 00:05:21.580
<v Speaker 0>you so much, our ongoing insiders. But now

00:05:21.580 --> 00:05:23.440
<v Speaker 0>we wanna take a moment to thank GoDaddy,

00:05:23.500 --> 00:05:25.660
<v Speaker 0>our longtime sponsor, for their incredible support of

00:05:25.660 --> 00:05:28.435
<v Speaker 0>this podcast. They make it possible for us

00:05:28.435 --> 00:05:30.035
<v Speaker 0>to keep doing what we love and what

00:05:30.035 --> 00:05:32.275
<v Speaker 0>you enjoy hearing every week, you know, up

00:05:32.275 --> 00:05:33.875
<v Speaker 0>up to up to date news on all

00:05:33.875 --> 00:05:36.355
<v Speaker 0>the new stuff in tech. If you're ready

00:05:36.355 --> 00:05:38.355
<v Speaker 0>to start your own website or even launch

00:05:38.355 --> 00:05:41.710
<v Speaker 0>a podcast, GoDaddy has you covered. At geek

00:05:41.710 --> 00:05:44.190
<v Speaker 0>news central dot com forward slash GoDaddy, you'll

00:05:44.190 --> 00:05:46.350
<v Speaker 0>find special promo codes that make it easy

00:05:46.350 --> 00:05:51.630
<v Speaker 0>and affordable to get started. Economy hosting, just

00:05:51.630 --> 00:05:53.805
<v Speaker 0>six ninety nine a month. It's a full

00:05:53.805 --> 00:05:56.605
<v Speaker 0>year of hosting with a free domain name

00:05:56.605 --> 00:06:00.305
<v Speaker 0>and a professional email and an SSL certificate.

00:06:00.845 --> 00:06:03.645
<v Speaker 0>Now WordPress hosting, which is typically what we

00:06:03.645 --> 00:06:05.245
<v Speaker 0>tend to use, is a little bit more,

00:06:05.245 --> 00:06:08.780
<v Speaker 0>twelve ninety nine a month, extremely affordable, which

00:06:08.780 --> 00:06:11.979
<v Speaker 0>also include includes that free domain, email, and

00:06:11.979 --> 00:06:14.940
<v Speaker 0>SSL certificate for a whole year. And that

00:06:14.940 --> 00:06:19.900
<v Speaker 0>one, that yeah. That one's a nice little

00:06:19.900 --> 00:06:22.139
<v Speaker 0>bundle, to really, like, nail down for a

00:06:22.139 --> 00:06:24.025
<v Speaker 0>little while. And Even if you just want

00:06:24.025 --> 00:06:25.945
<v Speaker 0>a a domain name, eleven ninety nine to

00:06:25.945 --> 00:06:28.025
<v Speaker 0>get started, you can save a domain name.

00:06:28.025 --> 00:06:30.825
<v Speaker 0>You know? Maybe you have a up and

00:06:30.825 --> 00:06:35.220
<v Speaker 0>coming teenager or or a college kid that

00:06:35.300 --> 00:06:36.740
<v Speaker 0>if, you know, they they might have a

00:06:36.740 --> 00:06:38.660
<v Speaker 0>website in their future. They might wanna do

00:06:38.660 --> 00:06:41.220
<v Speaker 0>some post some of their photography or some

00:06:41.220 --> 00:06:43.860
<v Speaker 0>of their, portfolio work. You know? That's a

00:06:43.860 --> 00:06:45.380
<v Speaker 0>good place to get started. Get them a

00:06:45.380 --> 00:06:47.380
<v Speaker 0>domain. You can tell them in a few

00:06:47.380 --> 00:06:49.300
<v Speaker 0>years, hey. We've got this domain reserved for

00:06:49.300 --> 00:06:50.740
<v Speaker 0>you. No one else has got it. You

00:06:50.740 --> 00:06:52.795
<v Speaker 0>know? We've got anna cochran dot com. We

00:06:52.795 --> 00:06:55.995
<v Speaker 0>gotta build her website. And if you're not

00:06:55.995 --> 00:06:58.875
<v Speaker 0>super tech savvy, which most of us aren't,

00:06:59.115 --> 00:07:01.835
<v Speaker 0>GoDaddy's website builder gives you a free thirty

00:07:01.835 --> 00:07:04.795
<v Speaker 0>day trial on personal business and business plus

00:07:04.795 --> 00:07:07.620
<v Speaker 0>plans. So you can literally get online in

00:07:07.620 --> 00:07:09.300
<v Speaker 0>no time. You don't even have to build

00:07:09.300 --> 00:07:11.780
<v Speaker 0>the website yourself. You got a little website

00:07:11.780 --> 00:07:13.639
<v Speaker 0>builder that gets it all done for you.

00:07:14.500 --> 00:07:16.500
<v Speaker 0>Now we use GoDaddy products here at Geek

00:07:16.500 --> 00:07:19.165
<v Speaker 0>News Central. I use it personally myself. I

00:07:19.165 --> 00:07:21.085
<v Speaker 0>can tell you their reliability is the real

00:07:21.085 --> 00:07:24.525
<v Speaker 0>deal. Your support of GoDaddy directly supports this

00:07:24.525 --> 00:07:27.565
<v Speaker 0>show, so please use our codes, click and

00:07:27.565 --> 00:07:30.845
<v Speaker 0>save, and help keep this independent podcast going

00:07:30.845 --> 00:07:33.500
<v Speaker 0>strong. Share those links with friends and family.

00:07:33.720 --> 00:07:35.400
<v Speaker 0>Every time one's used, it's like writing a

00:07:35.400 --> 00:07:38.039
<v Speaker 0>check to the show. We truly thank you

00:07:38.039 --> 00:07:39.960
<v Speaker 0>for supporting us, and a huge thanks again

00:07:39.960 --> 00:07:42.199
<v Speaker 0>to GoDaddy for believing in independent creators like

00:07:42.199 --> 00:07:46.165
<v Speaker 0>us here at Geek News Central. Let's get

00:07:46.165 --> 00:07:48.505
<v Speaker 0>into the next article. I got a little

00:07:48.645 --> 00:07:50.565
<v Speaker 0>article about the Mesa project. For those of

00:07:50.565 --> 00:07:52.485
<v Speaker 0>you that don't know what the Mesa project

00:07:52.485 --> 00:07:54.885
<v Speaker 0>is, Mesa is an open source project that

00:07:54.885 --> 00:07:58.159
<v Speaker 0>powers Linux graphics drivers. So this can be

00:07:58.159 --> 00:08:00.879
<v Speaker 0>used by AMD, Intel, and and many other

00:08:00.879 --> 00:08:04.240
<v Speaker 0>brands. Recently, a contributor submitted code generated by

00:08:04.240 --> 00:08:06.740
<v Speaker 0>an AI assistant, and it looked correct syntactically

00:08:07.360 --> 00:08:09.840
<v Speaker 0>but made no logical sense. The team caught

00:08:09.840 --> 00:08:11.939
<v Speaker 0>it before it went live, but it triggered

00:08:12.000 --> 00:08:14.745
<v Speaker 0>a new rule. The con contributors gonna have

00:08:14.745 --> 00:08:17.305
<v Speaker 0>to show or prove that they come comprehend

00:08:17.305 --> 00:08:18.825
<v Speaker 0>the code that they're submitting. They have to

00:08:18.825 --> 00:08:20.585
<v Speaker 0>know what they're doing. I think this is

00:08:20.585 --> 00:08:23.705
<v Speaker 0>kind of important, context going into this article

00:08:23.705 --> 00:08:26.425
<v Speaker 0>because, like, we've been hearing now about all

00:08:26.425 --> 00:08:28.790
<v Speaker 0>these code gen tools. Get away from boilerplate.

00:08:29.090 --> 00:08:31.970
<v Speaker 0>Just get straight to architecting. Well, if you're

00:08:31.970 --> 00:08:35.330
<v Speaker 0>submitting massive changes that needs massive amount of

00:08:35.330 --> 00:08:39.910
<v Speaker 0>review, the AI slop is not helping contribute

00:08:39.970 --> 00:08:43.595
<v Speaker 0>to, you know, allowing everyone to keep up

00:08:43.595 --> 00:08:45.755
<v Speaker 0>with what's what's changing in the code base.

00:08:45.755 --> 00:08:47.595
<v Speaker 0>It's very important for people to know what's

00:08:47.595 --> 00:08:49.355
<v Speaker 0>going on, how to fix things, where a

00:08:49.355 --> 00:08:52.074
<v Speaker 0>mess might be. So let's get into the

00:08:52.074 --> 00:08:56.490
<v Speaker 0>article. Recently, Faith Xtrand announced on Mastodon that

00:08:56.490 --> 00:08:59.770
<v Speaker 0>Mesa was updating its contributor guide. This follows

00:08:59.770 --> 00:09:02.250
<v Speaker 0>a recent AI slop incident where someone submitted

00:09:02.250 --> 00:09:04.250
<v Speaker 0>a massive patch to the Mesa project with

00:09:04.250 --> 00:09:06.810
<v Speaker 0>the claim that this would improve performance by

00:09:06.810 --> 00:09:10.305
<v Speaker 0>a few percent. The catch, the entire patch

00:09:10.305 --> 00:09:13.425
<v Speaker 0>was generated by ChatTBT with the submitter becoming

00:09:13.425 --> 00:09:16.085
<v Speaker 0>somewhat irate when the very patient Mesa developers

00:09:16.305 --> 00:09:18.465
<v Speaker 0>tried to explain that they'd happily look at

00:09:18.465 --> 00:09:21.440
<v Speaker 0>the issue after the submitter had condensed the

00:09:21.440 --> 00:09:26.320
<v Speaker 0>purported improvement into a bite sized patch. Now

00:09:26.320 --> 00:09:28.320
<v Speaker 0>they get a little bit more into this

00:09:28.320 --> 00:09:30.800
<v Speaker 0>whole saga in a in a video by

00:09:30.800 --> 00:09:36.325
<v Speaker 0>Brody Robertson, and, you know, it's kinda crazy

00:09:36.325 --> 00:09:38.325
<v Speaker 0>to to see something like this, you know,

00:09:38.325 --> 00:09:41.785
<v Speaker 0>even to be upset that someone doesn't want

00:09:42.964 --> 00:09:48.660
<v Speaker 0>AI Slob in their open source project. So

00:09:48.660 --> 00:09:52.100
<v Speaker 0>the entire saga the saga is summarized in

00:09:52.100 --> 00:09:54.580
<v Speaker 0>a recent video by Brody Robertson, which highlights

00:09:54.580 --> 00:09:56.980
<v Speaker 0>both how incredibly friendly the Mesa developers are

00:09:56.980 --> 00:09:59.540
<v Speaker 0>and how the use of ChatTBT and Kin

00:09:59.540 --> 00:10:02.120
<v Speaker 0>has made some people with zero programming skills

00:10:02.285 --> 00:10:04.285
<v Speaker 0>apparently believe that they can now contribute code

00:10:04.285 --> 00:10:08.945
<v Speaker 0>to open source projects. Unsurprisingly, the Mesa developers

00:10:09.005 --> 00:10:11.885
<v Speaker 0>were unable to disabuse this particular individual from

00:10:11.885 --> 00:10:14.125
<v Speaker 0>that notion. But the diff to the Mesa

00:10:14.125 --> 00:10:17.180
<v Speaker 0>contributor guide by Timmer Kristoff should make it

00:10:17.180 --> 00:10:19.820
<v Speaker 0>abundantly clear that someone playing telephone between a

00:10:19.820 --> 00:10:22.620
<v Speaker 0>chatbot and an open source project developers is

00:10:22.620 --> 00:10:28.460
<v Speaker 0>neither desirable nor helpful. That said, Brody also

00:10:28.460 --> 00:10:31.155
<v Speaker 0>highlights a recent post by Daniel Stenberg of

00:10:31.235 --> 00:10:32.995
<v Speaker 0>curl fame. And if you guys don't remember,

00:10:32.995 --> 00:10:35.335
<v Speaker 0>we talked about Daniel last week, an awesome,

00:10:36.275 --> 00:10:39.175
<v Speaker 0>awesome maintainer of the curl project, longtime maintainer.

00:10:39.315 --> 00:10:41.475
<v Speaker 0>He always is talking about AI slop on

00:10:41.475 --> 00:10:44.775
<v Speaker 0>Mastodon. He's always doing presentations on AI slop.

00:10:47.610 --> 00:10:51.370
<v Speaker 0>But, anyway, he thanked, Joshua Rogers for contributing

00:10:51.370 --> 00:10:53.370
<v Speaker 0>a massive list of potential issues that were

00:10:53.370 --> 00:10:56.330
<v Speaker 0>found using AI assisted tools as detailed in

00:10:56.330 --> 00:10:59.210
<v Speaker 0>this blog post by Joshua. An important point

00:10:59.210 --> 00:11:01.050
<v Speaker 0>here is that these AI tools are not

00:11:01.050 --> 00:11:04.154
<v Speaker 0>l m LLM based chatbots, but rather tweaked

00:11:04.154 --> 00:11:07.355
<v Speaker 0>existing tools like static code analyzers with more

00:11:07.355 --> 00:11:11.055
<v Speaker 0>smart spoiled bolted on. They're purpose made tools

00:11:11.274 --> 00:11:13.194
<v Speaker 0>that still require you to know what you're

00:11:13.194 --> 00:11:15.595
<v Speaker 0>doing, but they can be a real asset

00:11:15.595 --> 00:11:17.035
<v Speaker 0>to a developer and a heck of a

00:11:17.035 --> 00:11:18.840
<v Speaker 0>lot more useful to a project like CURL

00:11:18.840 --> 00:11:21.640
<v Speaker 0>than getting say than getting sent fake bug

00:11:21.640 --> 00:11:24.760
<v Speaker 0>reports by a confabulating chatbot as has happened

00:11:24.760 --> 00:11:28.760
<v Speaker 0>previously. So, yeah, that's kinda cool. It's kinda

00:11:28.760 --> 00:11:30.435
<v Speaker 0>cool to see that. It it's it's and

00:11:30.435 --> 00:11:32.675
<v Speaker 0>it's so you can see Daniel Stenberg is

00:11:32.675 --> 00:11:37.095
<v Speaker 0>not necessarily against the use of AI, but

00:11:37.635 --> 00:11:39.975
<v Speaker 0>he has experienced a lot of, like, oh,

00:11:41.315 --> 00:11:44.035
<v Speaker 0>you know, big PR reports from people that

00:11:44.035 --> 00:11:45.900
<v Speaker 0>are obviously generated fully generated by chat chat

00:11:49.100 --> 00:11:51.100
<v Speaker 0>ridiculous to kinda read through them and see

00:11:51.100 --> 00:11:56.140
<v Speaker 0>the the the changes they're proposing. Moving on.

00:11:56.140 --> 00:11:59.180
<v Speaker 0>We got another article, in the AI space.

00:11:59.180 --> 00:12:02.895
<v Speaker 0>If you haven't heard already, Google Jules has

00:12:02.895 --> 00:12:07.235
<v Speaker 0>joined the Claude Code, the the Gemini CLI

00:12:07.535 --> 00:12:11.315
<v Speaker 0>gang, and it has brought Google Jules, into

00:12:11.375 --> 00:12:14.015
<v Speaker 0>developer workflows by, getting it on the command

00:12:14.015 --> 00:12:17.290
<v Speaker 0>line system, which is kinda kinda cool. If

00:12:17.290 --> 00:12:18.810
<v Speaker 0>you've never used any of these tools, they're

00:12:18.810 --> 00:12:22.410
<v Speaker 0>pretty neat. It's kinda hard to, like, keep

00:12:22.410 --> 00:12:26.170
<v Speaker 0>up with them. But, again, that is the

00:12:26.170 --> 00:12:29.290
<v Speaker 0>whole problem right now with generated code. Right?

00:12:29.290 --> 00:12:35.745
<v Speaker 0>It's it's quite literally generated slot because you

00:12:35.745 --> 00:12:38.305
<v Speaker 0>don't know what's going on. You have to

00:12:38.305 --> 00:12:40.945
<v Speaker 0>keep everything together yourself. And, you know, when

00:12:40.945 --> 00:12:45.810
<v Speaker 0>big changes happen and you don't you can't

00:12:45.810 --> 00:12:47.970
<v Speaker 0>pinpoint the problem because it's all generated, then

00:12:47.970 --> 00:12:49.410
<v Speaker 0>what are you gonna do? No no one

00:12:49.410 --> 00:12:53.250
<v Speaker 0>knows where to look. Anyway, I keep reiterating

00:12:53.250 --> 00:12:54.770
<v Speaker 0>this over and over. I'm like a broken

00:12:54.770 --> 00:12:56.654
<v Speaker 0>record, but, you know, I just feel like

00:12:56.654 --> 00:12:59.055
<v Speaker 0>it's the the raging conversation these days. You

00:12:59.055 --> 00:13:00.975
<v Speaker 0>know? People are saying, use the tools, and

00:13:00.975 --> 00:13:06.095
<v Speaker 0>other people are like yeah. It's it's the

00:13:06.095 --> 00:13:08.675
<v Speaker 0>whole thing. But let's get into the article.

00:13:08.940 --> 00:13:11.580
<v Speaker 0>Google is bringing its AI coding agent, Jules,

00:13:11.580 --> 00:13:14.140
<v Speaker 0>deeper into developer workflows with a new command

00:13:14.140 --> 00:13:17.020
<v Speaker 0>line interface and public API, allowing it to

00:13:17.020 --> 00:13:20.780
<v Speaker 0>plug into terminals, CICD systems, and tools like

00:13:20.780 --> 00:13:24.225
<v Speaker 0>Slack as competition intensifies among tech companies to

00:13:24.225 --> 00:13:26.625
<v Speaker 0>own the future of software development and make

00:13:26.625 --> 00:13:29.985
<v Speaker 0>coding more of an AI assisted task. Until

00:13:29.985 --> 00:13:33.425
<v Speaker 0>now, JUULS, Google's asynchronous coding agent, was only

00:13:33.425 --> 00:13:36.730
<v Speaker 0>accessible via its website and GitHub. On Thursday,

00:13:36.730 --> 00:13:39.529
<v Speaker 0>the company introduced Jules tools, a command line

00:13:39.529 --> 00:13:42.490
<v Speaker 0>interface that brings Jules directly into the developer's

00:13:42.490 --> 00:13:46.009
<v Speaker 0>terminal. The CLI lets developers interact with the

00:13:46.009 --> 00:13:49.610
<v Speaker 0>agent using commands, streamlining workflows by eliminating the

00:13:49.610 --> 00:13:52.395
<v Speaker 0>need to switch between the web interface and

00:13:52.395 --> 00:13:54.875
<v Speaker 0>GitHub. It allows them to stay within their

00:13:54.875 --> 00:13:58.255
<v Speaker 0>environment while delegating coding tasks and validating results.

00:13:59.115 --> 00:14:01.775
<v Speaker 0>We want to reduce context switching for developers

00:14:01.835 --> 00:14:04.715
<v Speaker 0>as much as possible, and Cathy Korovec, director

00:14:04.715 --> 00:14:07.170
<v Speaker 0>of products at Google Labs, oh, said Cathy

00:14:07.170 --> 00:14:09.810
<v Speaker 0>Korovec, excuse me, director of products at Google

00:14:09.810 --> 00:14:13.590
<v Speaker 0>Labs in an interview. Google already offers Gemini

00:14:13.650 --> 00:14:16.050
<v Speaker 0>CLI, an AI based command line tool that

00:14:16.050 --> 00:14:19.750
<v Speaker 0>works across developer environments like terminals and CICD

00:14:19.890 --> 00:14:24.375
<v Speaker 0>pipelines. Both Gemini CLI and JUULS use Google's

00:14:24.515 --> 00:14:27.315
<v Speaker 0>Gemini two point four two point five Pro

00:14:27.315 --> 00:14:30.835
<v Speaker 0>AI model under the hood. However, Korovic told

00:14:30.835 --> 00:14:34.695
<v Speaker 0>TechCrunch that JUULS tools is designed for Veriscope

00:14:34.835 --> 00:14:37.650
<v Speaker 0>tasks while Gemini CLI requires used to be

00:14:38.050 --> 00:14:39.890
<v Speaker 0>users to be a lot more iterative and

00:14:39.890 --> 00:14:41.910
<v Speaker 0>to collaborate a lot more with the tool.

00:14:42.370 --> 00:14:44.290
<v Speaker 0>It's kinda cool. So and now Google's got

00:14:44.290 --> 00:14:50.365
<v Speaker 0>two CLI based, coding agent assistants to get

00:14:50.365 --> 00:14:54.205
<v Speaker 0>your tech flows going faster, I guess. Google

00:14:54.205 --> 00:14:57.165
<v Speaker 0>senior developer advocate, Denise Quan, also elaborated in

00:14:57.165 --> 00:14:59.085
<v Speaker 0>a Medium post on how Jules differs from

00:14:59.085 --> 00:15:02.705
<v Speaker 0>Gemini CLI. Jules is less interactive by design,

00:15:03.000 --> 00:15:06.280
<v Speaker 0>she noted, and executes tasks independently once the

00:15:06.280 --> 00:15:09.160
<v Speaker 0>user approves its plan. In addition to the

00:15:09.160 --> 00:15:12.360
<v Speaker 0>CLI, Google has made Jules API public, which

00:15:12.360 --> 00:15:15.455
<v Speaker 0>it had previously used for internal development. The

00:15:15.455 --> 00:15:17.555
<v Speaker 0>purpose of this is also to help developers

00:15:17.615 --> 00:15:19.935
<v Speaker 0>use Jules more often as they can extend

00:15:19.935 --> 00:15:22.575
<v Speaker 0>the tool into their existing workflows where they

00:15:22.575 --> 00:15:25.075
<v Speaker 0>have a lot of muscle memory and familiarity,

00:15:25.775 --> 00:15:29.940
<v Speaker 0>Corvex said. Developers can also use the API

00:15:29.940 --> 00:15:32.760
<v Speaker 0>to integrate Jules with their integrated development environment,

00:15:32.980 --> 00:15:36.100
<v Speaker 0>IDE, a software application that keep that helps

00:15:36.100 --> 00:15:38.420
<v Speaker 0>make coding easier by providing a list of

00:15:38.420 --> 00:15:42.024
<v Speaker 0>tools such as Versus Code. However, Horvek told

00:15:42.024 --> 00:15:44.425
<v Speaker 0>TechCrunch that her team is keen to build

00:15:44.425 --> 00:15:47.385
<v Speaker 0>specific plugins for IDEs to further expand Jewel's

00:15:47.385 --> 00:15:56.060
<v Speaker 0>presence. So, yeah, really exciting, launch. So higher

00:15:56.060 --> 00:15:57.980
<v Speaker 0>limits are the a free plan offers up

00:15:57.980 --> 00:16:00.560
<v Speaker 0>to fifteen individual daily tasks and three concurrent

00:16:00.620 --> 00:16:03.500
<v Speaker 0>tasks. Higher limits are available through the Google

00:16:03.500 --> 00:16:05.980
<v Speaker 0>AI Pro and Ultra plans priced at nineteen

00:16:05.980 --> 00:16:07.740
<v Speaker 0>ninety nine and one twenty four ninety nine

00:16:07.740 --> 00:16:10.675
<v Speaker 0>per month, offering approximately five times and twenty

00:16:10.675 --> 00:16:17.095
<v Speaker 0>times the limits respectively. So you gotta wonder,

00:16:18.675 --> 00:16:25.670
<v Speaker 0>how big is a task? Fifteen individual daily

00:16:25.670 --> 00:16:29.110
<v Speaker 0>tasks and three concurrent tasks. Oh, that's kinda

00:16:29.110 --> 00:16:30.950
<v Speaker 0>cool. So it can be building stuff while

00:16:30.950 --> 00:16:33.910
<v Speaker 0>you're or, like, working on something while you're

00:16:33.910 --> 00:16:38.265
<v Speaker 0>talking to another, instance or prompting another one,

00:16:38.265 --> 00:16:40.685
<v Speaker 0>prompting doing a little prompt. Thanks to TechCrunch

00:16:40.745 --> 00:16:43.225
<v Speaker 0>for this article. Really cool one. We'll send

00:16:43.225 --> 00:16:45.945
<v Speaker 0>this one out in the show notes. I

00:16:45.945 --> 00:16:47.705
<v Speaker 0>got another one for you guys tonight. A

00:16:47.705 --> 00:16:50.025
<v Speaker 0>lot of AI. You know? AI is the

00:16:50.025 --> 00:16:53.010
<v Speaker 0>rage right now. A lot of stories coming

00:16:53.010 --> 00:16:55.890
<v Speaker 0>out saying we're in an AI bubble. And,

00:16:55.890 --> 00:16:58.370
<v Speaker 0>you know, I'm sure you guys have heard

00:16:58.370 --> 00:17:02.210
<v Speaker 0>about, Perplexity's offer for Google Chrome, something like

00:17:02.210 --> 00:17:05.395
<v Speaker 0>thirty four billion, thirty four point five billion

00:17:05.395 --> 00:17:10.675
<v Speaker 0>for, the browser, which I'm not I don't

00:17:10.675 --> 00:17:12.515
<v Speaker 0>know. I don't know what that's about, but,

00:17:12.515 --> 00:17:16.035
<v Speaker 0>yeah, maybe it's a flex. But if you

00:17:16.035 --> 00:17:18.755
<v Speaker 0>guys don't haven't heard about Complexity's Comet browser

00:17:18.755 --> 00:17:22.200
<v Speaker 0>yet, it's a browser with built in AI.

00:17:23.060 --> 00:17:25.700
<v Speaker 0>It merges search, chat, and reasoning into one

00:17:25.700 --> 00:17:28.660
<v Speaker 0>window instead of searching. You ask questions, and

00:17:28.660 --> 00:17:32.740
<v Speaker 0>it responds conversationally, pulling verified sources into an

00:17:32.740 --> 00:17:35.825
<v Speaker 0>AI summary. It's now free to all users.

00:17:35.965 --> 00:17:37.085
<v Speaker 0>I don't know if you guys knew this,

00:17:37.085 --> 00:17:39.085
<v Speaker 0>but, yes, it's, it's out as of last

00:17:39.085 --> 00:17:41.805
<v Speaker 0>Thursday, I believe. Kind of exciting news because

00:17:41.805 --> 00:17:43.725
<v Speaker 0>they were offering this before at two hundred

00:17:43.725 --> 00:17:46.045
<v Speaker 0>dollars a month. So you had to be

00:17:46.045 --> 00:17:48.470
<v Speaker 0>on something equivalent to, like, the ChatGPT Max

00:17:48.470 --> 00:17:52.950
<v Speaker 0>plan to even use their browser. So, check

00:17:52.950 --> 00:17:54.790
<v Speaker 0>that out. I know the requirements to run

00:17:54.790 --> 00:17:56.550
<v Speaker 0>it are a little bit steep. I think

00:17:56.550 --> 00:17:59.590
<v Speaker 0>at a minimum, sixteen gigabytes of RAM, and

00:17:59.590 --> 00:18:01.750
<v Speaker 0>then recommended thirty two gigabytes. So I don't

00:18:01.750 --> 00:18:04.345
<v Speaker 0>know what people's specs are like on average

00:18:04.345 --> 00:18:08.585
<v Speaker 0>these days, but, yeah, I'm not putting that

00:18:08.585 --> 00:18:11.305
<v Speaker 0>on, my old old gal. She she won't

00:18:11.305 --> 00:18:13.405
<v Speaker 0>be able to do that. No way, Jose.

00:18:14.265 --> 00:18:16.950
<v Speaker 0>But, yeah, let's get into the article. Perplexity

00:18:17.090 --> 00:18:20.070
<v Speaker 0>AI rolls out Comet browser for free worldwide,

00:18:21.810 --> 00:18:23.810
<v Speaker 0>and, hope this is okay. This one's from

00:18:23.810 --> 00:18:28.450
<v Speaker 0>CNBC. Perplexity on a Perplexity AI on Thursday

00:18:28.450 --> 00:18:31.590
<v Speaker 0>announced that its artificial intelligence powered web browser,

00:18:31.715 --> 00:18:34.275
<v Speaker 0>Comet, is available worldwide and will be free

00:18:34.275 --> 00:18:37.315
<v Speaker 0>to users. The Comet browser is designed to

00:18:37.315 --> 00:18:39.875
<v Speaker 0>serve as a per personal assistant that can

00:18:39.875 --> 00:18:43.475
<v Speaker 0>search the web, organize tabs, draft emails, shop,

00:18:43.475 --> 00:18:46.900
<v Speaker 0>and more according to Perplexity. The startup initially

00:18:46.960 --> 00:18:49.700
<v Speaker 0>launched Comet in July to Perplexity Max subscribers

00:18:49.760 --> 00:18:51.679
<v Speaker 0>for two hundred dollars a month, and the

00:18:51.679 --> 00:18:54.340
<v Speaker 0>wait list has ballooned to, quote, unquote, millions

00:18:54.480 --> 00:18:58.895
<v Speaker 0>of people, the company said. Complexity's decision to

00:18:58.895 --> 00:19:00.975
<v Speaker 0>provide Comet for free could help it attract

00:19:00.975 --> 00:19:02.895
<v Speaker 0>more users as it works to fend off

00:19:02.895 --> 00:19:06.174
<v Speaker 0>rivals like Google, OpenAI, and Anthropic that have

00:19:06.174 --> 00:19:10.015
<v Speaker 0>their own AI browser offerings. In September, Google

00:19:10.015 --> 00:19:12.355
<v Speaker 0>rolled out Gemini in its Chrome browser. Anthropic

00:19:13.130 --> 00:19:15.770
<v Speaker 0>announced an a a browser based AI agent

00:19:15.770 --> 00:19:19.210
<v Speaker 0>in August, and OpenAI unveiled operator, an agent

00:19:19.210 --> 00:19:21.530
<v Speaker 0>that uses a browser to complete tasks in

00:19:21.530 --> 00:19:23.450
<v Speaker 0>January. And this is on top of what

00:19:23.450 --> 00:19:27.485
<v Speaker 0>we just talked about with o OpenAI now

00:19:27.485 --> 00:19:30.784
<v Speaker 0>releasing their, like, app SDK. So that that

00:19:31.325 --> 00:19:32.845
<v Speaker 0>that's, like, on top of that. They just

00:19:32.845 --> 00:19:37.085
<v Speaker 0>one up to this, Comet release, just a

00:19:37.085 --> 00:19:39.820
<v Speaker 0>week later. You know? But Perplexity is best

00:19:39.820 --> 00:19:41.820
<v Speaker 0>known for its AI powered search engine that

00:19:41.820 --> 00:19:45.020
<v Speaker 0>gives users simple answers to questions and links

00:19:45.020 --> 00:19:47.360
<v Speaker 0>out to original source material on the web.

00:19:47.580 --> 00:19:50.059
<v Speaker 0>After the company was accused of plagiarizing content

00:19:50.059 --> 00:19:52.595
<v Speaker 0>for media outlets, it launched a revenue sharing

00:19:52.595 --> 00:19:55.154
<v Speaker 0>model with publishers last year. And I think

00:19:55.154 --> 00:19:58.595
<v Speaker 0>that's the, the Reddit case there, that I'm

00:19:58.595 --> 00:20:00.355
<v Speaker 0>sure we I I think we've talked about

00:20:00.355 --> 00:20:01.875
<v Speaker 0>a lot on the show in the past,

00:20:01.875 --> 00:20:05.950
<v Speaker 0>how Reddit is not happy with chatbots, scanning

00:20:05.950 --> 00:20:11.470
<v Speaker 0>and scraping their websites. So, yeah, definitely light

00:20:11.470 --> 00:20:14.430
<v Speaker 0>reference to that. The company also introduced Comet

00:20:14.430 --> 00:20:16.670
<v Speaker 0>Plus in August, which is a subscription that

00:20:16.670 --> 00:20:19.794
<v Speaker 0>gives users accent access to content from trusted

00:20:19.794 --> 00:20:22.914
<v Speaker 0>publishers and journalists. According to a blog blog

00:20:22.914 --> 00:20:26.755
<v Speaker 0>blog post, quote, can't speak. Perplexity said Tuesday

00:20:26.755 --> 00:20:30.355
<v Speaker 0>that CNN, Conde Nast, The Washington Post, Los

00:20:30.355 --> 00:20:33.809
<v Speaker 0>Angeles Times, Fortune, Le Monde, and Le Figaro

00:20:34.350 --> 00:20:38.429
<v Speaker 0>are its inaugural publishing partners. Pulp Perplexity said

00:20:38.429 --> 00:20:40.669
<v Speaker 0>additional features are also on the way. The

00:20:40.669 --> 00:20:42.750
<v Speaker 0>company teased a mobile version of Comet and

00:20:42.750 --> 00:20:46.205
<v Speaker 0>features called background assistant, which can work on

00:20:46.205 --> 00:20:51.404
<v Speaker 0>multiple tasks simultaneously and asynchronously. So, welcome to

00:20:51.404 --> 00:20:53.904
<v Speaker 0>the era of automating your life, I guess.

00:20:55.085 --> 00:20:56.845
<v Speaker 0>And I'm, like, I don't this kinda reminds

00:20:56.845 --> 00:20:59.560
<v Speaker 0>me again of another tool called n eight

00:20:59.560 --> 00:21:02.120
<v Speaker 0>n that you can use. It's, it's like

00:21:02.120 --> 00:21:06.300
<v Speaker 0>one of those, like, drag and drop task,

00:21:06.680 --> 00:21:09.320
<v Speaker 0>like, task what do you call them? Like,

00:21:09.320 --> 00:21:11.080
<v Speaker 0>task flow things. So, like, oh, you get

00:21:11.080 --> 00:21:12.920
<v Speaker 0>an email from someone, and then this thing

00:21:12.920 --> 00:21:15.555
<v Speaker 0>triggers. And, oh, if you get an email

00:21:15.555 --> 00:21:17.155
<v Speaker 0>from this person, it's gonna, oh, post it

00:21:17.155 --> 00:21:18.995
<v Speaker 0>to your note and also send it as

00:21:18.995 --> 00:21:21.315
<v Speaker 0>an email to someone else, you know, or

00:21:21.315 --> 00:21:23.075
<v Speaker 0>add it to your Google Drive or something.

00:21:23.075 --> 00:21:26.435
<v Speaker 0>You know? So it's, kinda cool. Or, you

00:21:26.435 --> 00:21:28.720
<v Speaker 0>know, your shop restocks, and they hit your

00:21:28.720 --> 00:21:30.720
<v Speaker 0>mailing list that something restocked, and it emails

00:21:30.720 --> 00:21:32.639
<v Speaker 0>all the people automatically. So you don't have

00:21:32.639 --> 00:21:36.720
<v Speaker 0>to worry about, restocking on items or sending

00:21:36.720 --> 00:21:39.360
<v Speaker 0>out emails for people's wish lists and stuff.

00:21:39.360 --> 00:21:41.120
<v Speaker 0>You know? It's just like it's automatic. Oh,

00:21:41.120 --> 00:21:43.174
<v Speaker 0>this is on this person's wish list. Let's

00:21:43.174 --> 00:21:45.015
<v Speaker 0>automatically send an email out that we just

00:21:45.015 --> 00:21:49.495
<v Speaker 0>restocked it. You know? So, cool cool release

00:21:49.495 --> 00:21:52.775
<v Speaker 0>here by Perplexity, Comet Browser for free now.

00:21:52.775 --> 00:21:54.455
<v Speaker 0>Give it a try if your computer can

00:21:54.455 --> 00:21:57.815
<v Speaker 0>run it. But, yeah, pretty cool stuff from

00:21:57.815 --> 00:22:00.610
<v Speaker 0>them. And I got a sweet article from

00:22:00.610 --> 00:22:06.710
<v Speaker 0>Tom's Hardware. Let's go. Harvard researchers hail quantum

00:22:06.770 --> 00:22:10.130
<v Speaker 0>computing breakthrough with machine that can run for

00:22:10.130 --> 00:22:15.105
<v Speaker 0>two hours. Atomic loss quashed by experimental design,

00:22:15.105 --> 00:22:17.265
<v Speaker 0>systems that can run forever just three years

00:22:17.265 --> 00:22:20.165
<v Speaker 0>away. Now that might be an exaggeration, but,

00:22:20.305 --> 00:22:23.585
<v Speaker 0>apparently, it's over a fifty five thousand percent

00:22:23.585 --> 00:22:27.510
<v Speaker 0>increase in operational time. A group of physicists

00:22:27.570 --> 00:22:30.230
<v Speaker 0>from Harvard and MIT just built a quantum

00:22:30.290 --> 00:22:33.190
<v Speaker 0>computer that ran continuously for more than two

00:22:33.250 --> 00:22:36.290
<v Speaker 0>hours. Although it doesn't sound like much versus

00:22:36.290 --> 00:22:38.850
<v Speaker 0>regular computers, like servers that run twenty four

00:22:38.850 --> 00:22:41.284
<v Speaker 0>seven for months, if not years, this is

00:22:41.284 --> 00:22:44.725
<v Speaker 0>a huge breakthrough in quantum computing. As reported

00:22:44.725 --> 00:22:48.664
<v Speaker 0>by the Harvard Crimson, most current quantum computers

00:22:48.804 --> 00:22:52.485
<v Speaker 0>run for only a few milliseconds with record

00:22:52.485 --> 00:22:54.965
<v Speaker 0>breaking machines only able to operate for a

00:22:54.965 --> 00:22:57.870
<v Speaker 0>little over ten seconds. Wow. The record record

00:22:57.870 --> 00:22:59.710
<v Speaker 0>breaking one's ten seconds. This one just ran

00:22:59.710 --> 00:23:02.270
<v Speaker 0>for two hours. Although two hours still a

00:23:02.270 --> 00:23:05.070
<v Speaker 0>bit limited, researchers say that the concept behind

00:23:05.070 --> 00:23:07.150
<v Speaker 0>this could allow future quantum computers to run

00:23:07.150 --> 00:23:10.785
<v Speaker 0>for much longer, maybe even indefinitely. There is

00:23:10.785 --> 00:23:12.945
<v Speaker 0>still a way to go and scale from

00:23:12.945 --> 00:23:15.925
<v Speaker 0>where we are now, says research associate, Touti

00:23:15.985 --> 00:23:18.625
<v Speaker 0>Wang. But the road map is now clear

00:23:18.625 --> 00:23:20.705
<v Speaker 0>based on that breakthrough experiments that we've done

00:23:20.705 --> 00:23:25.050
<v Speaker 0>here at Harvard. The main difference between regular

00:23:25.050 --> 00:23:26.970
<v Speaker 0>and quantum computing is that the latter uses

00:23:26.970 --> 00:23:29.770
<v Speaker 0>qubits, which are subatomic particles to hold and

00:23:29.770 --> 00:23:32.650
<v Speaker 0>process data. But unlike the former, which retain

00:23:32.650 --> 00:23:36.294
<v Speaker 0>information even without power, quantum computers can lose

00:23:36.294 --> 00:23:38.955
<v Speaker 0>these qubits in a process called atom loss.

00:23:39.335 --> 00:23:41.735
<v Speaker 0>This research this results in information loss and

00:23:41.735 --> 00:23:47.815
<v Speaker 0>eventually system failure. So they address this by

00:23:47.815 --> 00:23:51.290
<v Speaker 0>developing the optical lattice conveyor belt and optical

00:23:51.350 --> 00:23:53.830
<v Speaker 0>tweezers to replace qubits as they're lost. Oh,

00:23:53.830 --> 00:23:56.230
<v Speaker 0>that's kinda cool. The system has three thousand

00:23:56.230 --> 00:23:58.310
<v Speaker 0>qubits and allows them to inject thirty three

00:23:58.310 --> 00:24:00.630
<v Speaker 0>hundred thousand atoms per second into the quantum

00:24:00.630 --> 00:24:04.085
<v Speaker 0>computer overcoming the qubit loss. There's now fundamentally

00:24:04.225 --> 00:24:06.385
<v Speaker 0>nothing limiting how long our usual atom and

00:24:06.385 --> 00:24:09.265
<v Speaker 0>quantum computers can run for. Even if atoms

00:24:09.265 --> 00:24:11.184
<v Speaker 0>get lost with a small probability, we can

00:24:11.184 --> 00:24:13.025
<v Speaker 0>bring fresh atoms in to replace them and

00:24:13.025 --> 00:24:15.345
<v Speaker 0>not affect the quantum information being stored in

00:24:15.345 --> 00:24:18.180
<v Speaker 0>the system. Other team members believe that this

00:24:18.180 --> 00:24:20.260
<v Speaker 0>breakthrough allows to have quantum computers that can

00:24:20.260 --> 00:24:22.980
<v Speaker 0>run forever in about three years. Before this,

00:24:22.980 --> 00:24:24.580
<v Speaker 0>experts said that it was at least half

00:24:24.580 --> 00:24:27.940
<v Speaker 0>a decade away, if not longer. Quantum computing

00:24:27.940 --> 00:24:29.620
<v Speaker 0>has the potential to change the way we

00:24:29.620 --> 00:24:33.835
<v Speaker 0>do computing, breaking barriers in cryptography, finance, medicine,

00:24:33.835 --> 00:24:37.434
<v Speaker 0>and more. However, despite these advancements, it's unlikely

00:24:37.434 --> 00:24:39.755
<v Speaker 0>that we'll have a personal quantum computers in

00:24:39.755 --> 00:24:41.914
<v Speaker 0>our living room and offices within the next

00:24:41.914 --> 00:24:44.554
<v Speaker 0>decade unless you're a physicist or researcher working

00:24:44.554 --> 00:24:47.360
<v Speaker 0>on these cutting edge devices. Can you imagine,

00:24:47.660 --> 00:24:50.620
<v Speaker 0>like, just having a quantum laptop? I don't

00:24:50.620 --> 00:24:55.900
<v Speaker 0>even know what that would mean. What what

00:24:55.900 --> 00:24:58.460
<v Speaker 0>would that mean to have a device like

00:24:58.460 --> 00:25:02.005
<v Speaker 0>that? What what what is the benefit? So

00:25:02.005 --> 00:25:04.985
<v Speaker 0>I don't know. Really cool stuff. I think

00:25:05.685 --> 00:25:07.285
<v Speaker 0>we've seen a lot of this quantum stuff

00:25:07.285 --> 00:25:08.565
<v Speaker 0>come out in the last few years that

00:25:08.565 --> 00:25:11.765
<v Speaker 0>are just, like, so hype. The devices look

00:25:11.765 --> 00:25:13.845
<v Speaker 0>crazy. But then, you know, you say that,

00:25:13.845 --> 00:25:14.965
<v Speaker 0>but then you look at some of the

00:25:14.965 --> 00:25:18.649
<v Speaker 0>computers. The first computers that were were made,

00:25:18.649 --> 00:25:19.570
<v Speaker 0>those were big old boxes too. So, hey,

00:25:20.590 --> 00:25:23.789
<v Speaker 0>really awesome stuff. Now I got some space

00:25:23.789 --> 00:25:25.630
<v Speaker 0>news. I don't know if y'all wanna hear

00:25:25.630 --> 00:25:27.710
<v Speaker 0>some space news, but we got it. ARC

00:25:27.710 --> 00:25:31.625
<v Speaker 0>Aerospace is developing a hypersonic reusable spacecraft that

00:25:31.625 --> 00:25:35.304
<v Speaker 0>can deliver payloads globally within sixty minutes. The

00:25:35.304 --> 00:25:37.945
<v Speaker 0>design borrows from suborbital rocket tech and could

00:25:37.945 --> 00:25:44.380
<v Speaker 0>revolutionize logistics and emergency response. So this this

00:25:44.380 --> 00:25:47.180
<v Speaker 0>could potentially make same day global delivery a

00:25:47.180 --> 00:25:50.060
<v Speaker 0>reality, but it also raises questions about cost,

00:25:50.060 --> 00:25:52.700
<v Speaker 0>safety, and, apparently, a lot of it's being

00:25:52.700 --> 00:25:57.235
<v Speaker 0>developed for military use. Would you trust your,

00:25:57.235 --> 00:25:59.395
<v Speaker 0>like, your next Amazon rocket on or order

00:25:59.395 --> 00:26:02.115
<v Speaker 0>on a rocket that reenters the atmosphere at

00:26:02.115 --> 00:26:06.595
<v Speaker 0>Mach ten? So a little bit niche right

00:26:06.595 --> 00:26:08.115
<v Speaker 0>now, but let's get into the article. This

00:26:08.115 --> 00:26:10.530
<v Speaker 0>one's from Ars Technica. Thank you, guys. Ars

00:26:10.590 --> 00:26:14.270
<v Speaker 0>Technica. Meet the arc space spacecraft. It aims

00:26:14.270 --> 00:26:16.510
<v Speaker 0>to deliver cargo anywhere in the world in

00:26:16.510 --> 00:26:20.350
<v Speaker 0>an hour. The key discriminator is, does this

00:26:20.350 --> 00:26:22.450
<v Speaker 0>make a difference in the moment it's needed?

00:26:23.115 --> 00:26:25.915
<v Speaker 0>Oh, that's that's a good question. It's still

00:26:25.915 --> 00:26:27.355
<v Speaker 0>it's still an hour, I guess. Even if

00:26:27.355 --> 00:26:30.795
<v Speaker 0>it's an emergency, it's still an hour. A

00:26:30.795 --> 00:26:34.155
<v Speaker 0>relatively new spacecraft company, Inversion, revealed its new

00:26:34.155 --> 00:26:37.035
<v Speaker 0>on demand delivery vehicle Wednesday evening during a

00:26:37.035 --> 00:26:39.990
<v Speaker 0>splash ceremony at its factory in Los Angeles.

00:26:39.990 --> 00:26:42.310
<v Speaker 0>So this is last Wednesday. The show was

00:26:42.310 --> 00:26:45.110
<v Speaker 0>meant to come out on Monday, but some

00:26:45.110 --> 00:26:47.750
<v Speaker 0>stuff happened with the recording. So we're redoing

00:26:47.750 --> 00:26:50.950
<v Speaker 0>it tonight. It's Wednesday, but this happened last

00:26:50.950 --> 00:26:58.775
<v Speaker 0>Wednesday. Let's see here. Phenomenal mission for us

00:26:58.775 --> 00:27:01.575
<v Speaker 0>is pre positioning ARCS on orbit and having

00:27:01.575 --> 00:27:04.055
<v Speaker 0>them stay up there for up to five

00:27:04.055 --> 00:27:06.215
<v Speaker 0>years, able to be called upon and then

00:27:06.215 --> 00:27:10.320
<v Speaker 0>autonomous autonomously go and land wherever they wherever

00:27:10.320 --> 00:27:12.559
<v Speaker 0>and whenever they're needed, being able to bring

00:27:12.559 --> 00:27:15.200
<v Speaker 0>their cargo effects to desired location in under

00:27:15.200 --> 00:27:20.240
<v Speaker 0>an hour. Inversion was found in founded in

00:27:20.240 --> 00:27:23.360
<v Speaker 0>early twenty twenty one by Justin Fiacheti and

00:27:23.360 --> 00:27:26.415
<v Speaker 0>Austin Briggs. Both were students at Boston University.

00:27:26.875 --> 00:27:30.635
<v Speaker 0>Fiacchetti had internships at SpaceX and Relativity Space

00:27:30.635 --> 00:27:32.955
<v Speaker 0>where he worked on propulsion. He dropped out

00:27:32.955 --> 00:27:35.355
<v Speaker 0>of Boston University to cofound Inversion because of

00:27:35.355 --> 00:27:38.795
<v Speaker 0>a simple idea. Space is a highway. It's

00:27:38.795 --> 00:27:41.150
<v Speaker 0>kinda cool. Kinda reminds me of, like, the

00:27:41.150 --> 00:27:45.390
<v Speaker 0>whole idea that there's, like, satellites just, like,

00:27:45.390 --> 00:27:50.910
<v Speaker 0>flying around. There's satellites everywhere. I remember they

00:27:50.910 --> 00:27:52.270
<v Speaker 0>used to say, like, they would become a

00:27:52.270 --> 00:27:53.390
<v Speaker 0>point where it would just be like a

00:27:53.390 --> 00:27:55.867
<v Speaker 0>trash field because, you know, we put new

00:27:55.867 --> 00:27:58.494
<v Speaker 0>satellites up, but not do anything about the

00:27:58.494 --> 00:28:01.122
<v Speaker 0>old ones. I don't think that's true anymore.

00:28:01.122 --> 00:28:04.078
<v Speaker 0>I know that they've decommissioned satellites. But, yeah,

00:28:04.078 --> 00:28:07.034
<v Speaker 0>I mean, does how does that compare to

00:28:07.034 --> 00:28:09.661
<v Speaker 0>how many we're putting up? You know? Gotta

00:28:09.661 --> 00:28:12.710
<v Speaker 0>wonder. Not everyone can pay to take their

00:28:12.710 --> 00:28:14.230
<v Speaker 0>satellite down. I guess that's kind of a

00:28:14.230 --> 00:28:17.110
<v Speaker 0>thing too, which is kind of a crazy

00:28:17.110 --> 00:28:20.790
<v Speaker 0>thing. But the test spacecraft with a mass

00:28:20.790 --> 00:28:26.304
<v Speaker 0>about two hundred pounds, two hundred pounds performed

00:28:26.304 --> 00:28:30.144
<v Speaker 0>well, Fiocchetti said. It demonstrated the capability to

00:28:30.144 --> 00:28:32.544
<v Speaker 0>raise and lower its orbit and remains power

00:28:32.544 --> 00:28:35.205
<v Speaker 0>positive to date, periodically checking in with inversion

00:28:35.264 --> 00:28:38.304
<v Speaker 0>flight controllers. However, the spacecraft will not make

00:28:38.304 --> 00:28:41.450
<v Speaker 0>a controlled landing. Ray won't be coming back.

00:28:41.450 --> 00:28:42.990
<v Speaker 0>I guess that's the name of the spaceship,

00:28:43.210 --> 00:28:45.950
<v Speaker 0>but, I guess I won't be coming back.

00:28:46.010 --> 00:28:47.850
<v Speaker 0>I I'll be back. Don't worry, guys. We're

00:28:47.850 --> 00:28:50.590
<v Speaker 0>doing long term testing of software on orbit.

00:28:51.290 --> 00:28:53.205
<v Speaker 0>I was like, so Ray's staying in space.

00:28:53.284 --> 00:28:55.765
<v Speaker 0>Although Ray did not land, Inversion now feels

00:28:55.765 --> 00:28:57.605
<v Speaker 0>confident enough in its technology to move into

00:28:57.605 --> 00:28:59.924
<v Speaker 0>the production of larger ARC vehicles. Okay. So

00:28:59.924 --> 00:29:02.164
<v Speaker 0>that was just tester size. I was like,

00:29:02.164 --> 00:29:04.745
<v Speaker 0>dude, two hundred pounds is freaking nothing, dude.

00:29:07.550 --> 00:29:09.790
<v Speaker 0>Excuse me. Sorry. I got I didn't I

00:29:09.790 --> 00:29:11.650
<v Speaker 0>didn't know. I didn't see that part before.

00:29:14.030 --> 00:29:15.710
<v Speaker 0>Okay. Let's see here. Where were we? About

00:29:15.710 --> 00:29:17.870
<v Speaker 0>the size of a large tabletop is what

00:29:17.870 --> 00:29:20.030
<v Speaker 0>they're estimating it's gonna be. So ARC is

00:29:20.030 --> 00:29:22.255
<v Speaker 0>four feet wide and eight feet tall. The

00:29:22.255 --> 00:29:24.015
<v Speaker 0>company is aiming to launch the first ARC

00:29:24.015 --> 00:29:26.115
<v Speaker 0>vehicle by the end of twenty twenty six.

00:29:27.135 --> 00:29:29.615
<v Speaker 0>Fiacheti said Inversion is on a really good

00:29:29.615 --> 00:29:32.174
<v Speaker 0>path to make that timeline. So what does

00:29:32.174 --> 00:29:34.835
<v Speaker 0>the military want to ship? ARC is lifting

00:29:34.975 --> 00:29:38.809
<v Speaker 0>body spacecraft. It's a lifting body spacecraft, and

00:29:38.809 --> 00:29:40.570
<v Speaker 0>it will do the majority of its maneuvering

00:29:40.570 --> 00:29:42.649
<v Speaker 0>in the atmosphere where it has a thousand

00:29:42.649 --> 00:29:46.090
<v Speaker 0>kilometers of cross range capability during reentry. It

00:29:46.090 --> 00:29:48.570
<v Speaker 0>will land under parachutes and therefore not require

00:29:48.570 --> 00:29:51.795
<v Speaker 0>a runway. Because the vehicle's propulsion system uses

00:29:51.795 --> 00:29:55.095
<v Speaker 0>nontoxic materials, a soldier can approach it immediately

00:29:55.155 --> 00:29:57.795
<v Speaker 0>after landing without any protective gear. That's kinda

00:29:57.795 --> 00:30:00.595
<v Speaker 0>cool. So what would the US military wanna

00:30:00.595 --> 00:30:03.235
<v Speaker 0>pre preposition in space for delivery at any

00:30:03.235 --> 00:30:05.495
<v Speaker 0>moment's notice to any location around the world?

00:30:08.809 --> 00:30:10.890
<v Speaker 0>We would we like to describe this as

00:30:10.890 --> 00:30:14.570
<v Speaker 0>mission enabling cargo or effects. This could be

00:30:14.570 --> 00:30:18.010
<v Speaker 0>a wide variety of specific payloads, anything from

00:30:18.010 --> 00:30:20.750
<v Speaker 0>medical supplies to drones to what have you.

00:30:20.975 --> 00:30:22.975
<v Speaker 0>But the key discriminator is, does this make

00:30:22.975 --> 00:30:24.815
<v Speaker 0>a difference in the moment it's needed when

00:30:24.815 --> 00:30:26.655
<v Speaker 0>it get back to the ground? You know,

00:30:26.655 --> 00:30:28.575
<v Speaker 0>for the military and national security, if they

00:30:28.575 --> 00:30:30.675
<v Speaker 0>need their cargo before the fight is over.

00:30:32.415 --> 00:30:35.350
<v Speaker 0>Yeah. So it's still an hour. Right? So

00:30:35.350 --> 00:30:36.950
<v Speaker 0>the company said it's already built a full

00:30:36.950 --> 00:30:40.090
<v Speaker 0>scale manufacturing development unit of the primary structure

00:30:40.149 --> 00:30:42.630
<v Speaker 0>for the first ARC vehicle, and it would

00:30:42.630 --> 00:30:45.029
<v Speaker 0>be impressive capability if the small team at

00:30:45.029 --> 00:30:48.070
<v Speaker 0>Inversion, now sixty people strong and growing, can

00:30:48.070 --> 00:30:51.405
<v Speaker 0>bring the ARC space spacecraft to market. If,

00:30:51.405 --> 00:30:53.885
<v Speaker 0>of course, is the operative word. Space is

00:30:53.885 --> 00:30:55.885
<v Speaker 0>hard may be a cliche, but it also

00:30:55.885 --> 00:30:59.265
<v Speaker 0>happens to be true. So that's pretty cool,

00:30:59.805 --> 00:31:03.505
<v Speaker 0>to kinda see that little spacecraft delivery system.

00:31:03.565 --> 00:31:05.565
<v Speaker 0>I guess this picture of the Arc is

00:31:05.565 --> 00:31:08.550
<v Speaker 0>not real. This one's that's a rendering of

00:31:08.550 --> 00:31:09.830
<v Speaker 0>the arc spacecraft. So if you wanna see

00:31:09.830 --> 00:31:11.030
<v Speaker 0>what it looks like, you can check the

00:31:11.030 --> 00:31:14.950
<v Speaker 0>website out, from Ars Technica, but I'll have

00:31:14.950 --> 00:31:16.809
<v Speaker 0>that linked in the show notes, of course.

00:31:17.590 --> 00:31:19.275
<v Speaker 0>And I got one last article for you

00:31:19.275 --> 00:31:20.715
<v Speaker 0>tonight. I thought this was sick when I

00:31:20.715 --> 00:31:22.155
<v Speaker 0>was kinda reading through it, so I think

00:31:22.235 --> 00:31:25.775
<v Speaker 0>I hope you guys enjoy it too. Galaxies

00:31:25.835 --> 00:31:28.395
<v Speaker 0>with high radio emissions could be home to

00:31:28.395 --> 00:31:33.690
<v Speaker 0>many advanced civilizations. For decades, scientists engaged in

00:31:33.690 --> 00:31:37.850
<v Speaker 0>the search for extraterrestrial intelligence have proved the

00:31:37.850 --> 00:31:41.770
<v Speaker 0>galaxy for signs of artificial radio transmissions. Beginning

00:31:41.770 --> 00:31:44.985
<v Speaker 0>with Project Ozma in nineteen sixty, astronomers have

00:31:44.985 --> 00:31:47.485
<v Speaker 0>used radio antennas to listen for possible transmissions

00:31:47.545 --> 00:31:50.685
<v Speaker 0>from other star systems or galaxies. These efforts

00:31:50.985 --> 00:31:53.545
<v Speaker 0>culminated in January twenty sixteen with the launch

00:31:53.545 --> 00:31:59.660
<v Speaker 0>of Breakthrough Listen, the most comprehend comprehensive SETI,

00:31:59.660 --> 00:32:02.700
<v Speaker 0>which is search for extraterrestrial intelligence, effort to

00:32:02.700 --> 00:32:06.860
<v Speaker 0>date. This project combines radio wave observations from

00:32:06.860 --> 00:32:09.340
<v Speaker 0>Green Bank and Parkes Observatory as well as

00:32:09.340 --> 00:32:13.934
<v Speaker 0>visible light observations from automated plant PlanetFinder. The

00:32:13.934 --> 00:32:16.495
<v Speaker 0>results of Breakthrough Listen surveys have been shared

00:32:16.495 --> 00:32:19.375
<v Speaker 0>via a series of public releases. The latest

00:32:19.375 --> 00:32:23.775
<v Speaker 0>series, artificial broadcast as galactic populations, authored by

00:32:23.775 --> 00:32:27.154
<v Speaker 0>Brian c Laki, explores the possibility that galaxies

00:32:27.215 --> 00:32:31.350
<v Speaker 0>that are bright in radio spectrum, AKA radio

00:32:31.350 --> 00:32:34.230
<v Speaker 0>bright galaxies, could be an indication that such

00:32:34.230 --> 00:32:37.029
<v Speaker 0>galaxies could be packed with advanced civilizations. So

00:32:37.029 --> 00:32:38.789
<v Speaker 0>I guess this is just a theory that

00:32:38.789 --> 00:32:41.350
<v Speaker 0>this guy has been kinda, like, going through

00:32:41.350 --> 00:32:43.669
<v Speaker 0>or following up on through a series of

00:32:43.669 --> 00:32:49.645
<v Speaker 0>papers that, that kinda follow the conventional beliefs

00:32:49.645 --> 00:32:54.765
<v Speaker 0>around, like, you know, planetary, expansion for a

00:32:54.765 --> 00:32:58.430
<v Speaker 0>civilization. So we'll kinda get into that. So

00:32:58.430 --> 00:33:00.910
<v Speaker 0>Brian c Lackey is a theoretical astronomer with

00:33:00.910 --> 00:33:03.870
<v Speaker 0>breakthrough listen with the breakthrough listen initiative and

00:33:03.870 --> 00:33:06.370
<v Speaker 0>a Jansky Fellow with the National Radio Astronomy

00:33:06.510 --> 00:33:09.309
<v Speaker 0>Observatory. The paper is the third in a

00:33:09.309 --> 00:33:11.710
<v Speaker 0>series that explores the latest data provided by

00:33:11.710 --> 00:33:15.784
<v Speaker 0>the initiative's affiliated observatories. The paper describes Lackey's

00:33:15.845 --> 00:33:18.325
<v Speaker 0>findings recently appeared online and has been submitted

00:33:18.325 --> 00:33:20.565
<v Speaker 0>for publication to the publications of the Astro

00:33:20.804 --> 00:33:24.405
<v Speaker 0>Astronomical Society of the Pacific. The paper is

00:33:24.405 --> 00:33:26.164
<v Speaker 0>the third in a series that address techno

00:33:26.164 --> 00:33:29.350
<v Speaker 0>signatures of an entire population of ETIs rather

00:33:29.350 --> 00:33:33.049
<v Speaker 0>than individual star bound civilizations. As Lackey explained,

00:33:33.190 --> 00:33:35.350
<v Speaker 0>the series was partly motivated by the idea

00:33:35.350 --> 00:33:38.630
<v Speaker 0>that ETIs might rely on self replicating von

00:33:38.630 --> 00:33:41.590
<v Speaker 0>Neumann probes to explore and settle beyond their

00:33:41.590 --> 00:33:44.715
<v Speaker 0>system. This theory is foundational to the Fermi

00:33:44.775 --> 00:33:47.175
<v Speaker 0>paradox, which assumes that this method is most

00:33:47.175 --> 00:33:50.075
<v Speaker 0>likely is the most likely way advanced civilizations

00:33:50.135 --> 00:33:53.895
<v Speaker 0>will become interstellar and possibly galactic. The first

00:33:53.895 --> 00:33:56.775
<v Speaker 0>paper presents the theory and a mathematical framework

00:33:56.775 --> 00:33:58.830
<v Speaker 0>for the calculations conducted in the second and

00:33:58.830 --> 00:34:02.910
<v Speaker 0>third papers. In the second, Lackey explores what

00:34:02.910 --> 00:34:05.710
<v Speaker 0>happened when you have multiple broadcasting civilizations in

00:34:05.710 --> 00:34:08.510
<v Speaker 0>a single galaxy and applies this understanding to

00:34:08.510 --> 00:34:12.050
<v Speaker 0>the Milky Way, Andromeda, and Messier fifty nine.

00:34:12.425 --> 00:34:14.905
<v Speaker 0>The latest paper examines the potential signatures that

00:34:14.905 --> 00:34:17.705
<v Speaker 0>a population of advanced civilizations would produce in

00:34:17.705 --> 00:34:20.425
<v Speaker 0>galaxies throughout the universe. If you have some

00:34:20.425 --> 00:34:22.925
<v Speaker 0>subset that has a lot of radio transmissions,

00:34:23.224 --> 00:34:26.200
<v Speaker 0>they will appear radio bright. Like he told

00:34:26.200 --> 00:34:29.020
<v Speaker 0>Universe Today via email, since we know basically

00:34:29.160 --> 00:34:31.640
<v Speaker 0>how many galaxies there are at each level

00:34:31.640 --> 00:34:34.040
<v Speaker 0>of flux, we can set up we can

00:34:34.040 --> 00:34:35.880
<v Speaker 0>set upper limits on how many of these

00:34:35.880 --> 00:34:39.515
<v Speaker 0>artificial radio galaxies there are. Galaxies are known

00:34:39.515 --> 00:34:41.195
<v Speaker 0>to produce radio waves as part of their

00:34:41.195 --> 00:34:45.295
<v Speaker 0>natural emissions. This includes Sagittarius a a star,

00:34:45.675 --> 00:34:48.175
<v Speaker 0>like, I guess. There's a there's asterisk there,

00:34:48.475 --> 00:34:51.515
<v Speaker 0>the supermassive black hole SMBH at the center

00:34:51.515 --> 00:34:55.650
<v Speaker 0>of our galaxy. During the nineteen seventies, scientists

00:34:55.650 --> 00:34:57.490
<v Speaker 0>discovered that the radio bright emissions at the

00:34:57.490 --> 00:34:59.090
<v Speaker 0>center of our galaxy were caused by an

00:34:59.090 --> 00:35:02.450
<v Speaker 0>extremely compact object embedded within a larger radio

00:35:02.450 --> 00:35:06.070
<v Speaker 0>source. Since then, astronomers have determined that SMBHs

00:35:06.865 --> 00:35:09.205
<v Speaker 0>reside at the center of every massive galaxy

00:35:09.425 --> 00:35:12.785
<v Speaker 0>and are responsible for active galactic nuclei, a

00:35:12.785 --> 00:35:15.525
<v Speaker 0>phenomenon in which core region of a galaxy

00:35:15.585 --> 00:35:18.565
<v Speaker 0>temporarily outshines all the stars in the galactic

00:35:18.705 --> 00:35:24.559
<v Speaker 0>disk. So kind of a cool article. It's

00:35:24.559 --> 00:35:26.720
<v Speaker 0>mostly theoretical. If you wanna check it out,

00:35:26.720 --> 00:35:28.160
<v Speaker 0>I got a I'll have it linked in

00:35:28.160 --> 00:35:30.720
<v Speaker 0>the show notes. But if you stuck around,

00:35:30.720 --> 00:35:32.240
<v Speaker 0>thank you so much for listening all the

00:35:32.240 --> 00:35:35.045
<v Speaker 0>way through. Again, sorry for the late show.

00:35:35.045 --> 00:35:36.645
<v Speaker 0>I did mean to record this on Monday,

00:35:36.645 --> 00:35:38.164
<v Speaker 0>and I do plan to release these on

00:35:38.164 --> 00:35:41.444
<v Speaker 0>Monday going forward. Just had some issues with

00:35:41.444 --> 00:35:43.125
<v Speaker 0>the recording, so I had to redo it

00:35:43.125 --> 00:35:45.865
<v Speaker 0>and just been having a busy week. So,

00:35:47.160 --> 00:35:48.520
<v Speaker 0>if you guys have any questions or you

00:35:48.520 --> 00:35:50.200
<v Speaker 0>wanna reach out about any of the articles

00:35:50.200 --> 00:35:53.720
<v Speaker 0>or if you want to, even provide some

00:35:53.720 --> 00:35:55.240
<v Speaker 0>feedback, hit us up at geek news at

00:35:55.240 --> 00:35:56.599
<v Speaker 0>g mail dot com. I've been going through

00:35:56.599 --> 00:35:59.565
<v Speaker 0>the emails trying to keep up, but I'll

00:35:59.565 --> 00:36:01.325
<v Speaker 0>do what I can, respond where I can.

00:36:01.325 --> 00:36:02.845
<v Speaker 0>Thank you guys so much for listening. You

00:36:02.845 --> 00:36:05.565
<v Speaker 0>guys have a phenomenal night. We'll see you

00:36:05.565 --> 00:36:07.005
<v Speaker 0>guys next time. Hopefully, Chris will have a

00:36:07.005 --> 00:36:08.445
<v Speaker 0>show tomorrow too so you guys are gonna

00:36:08.445 --> 00:36:11.565
<v Speaker 0>have a little back to back. But have