WEBVTT

00:00:00.000 --> 00:00:05.000
When you strip it down to the basics, technology is just humanity's ongoing

00:00:03.400 --> 00:00:10.640
mission to make some things hot and other things not hot. Ovens, hot.

00:00:07.840 --> 00:00:14.160
Graphics cards, not hot. A recent update from Microsoft has left certain dual

00:00:12.280 --> 00:00:18.320
boot devices that run both Windows and Linux unable to boot despite explicit

00:00:16.880 --> 00:00:22.680
reassurance from Microsoft that this wouldn't happen. The update fixed a

00:00:20.040 --> 00:00:26.520
long-standing vulnerability in grub, an open-source bootloader used by many

00:00:24.440 --> 00:00:30.520
Linux distributions, but it wasn't supposed to affect dual boot systems and

00:00:28.680 --> 00:00:34.280
it seems to have been applied accidentally. Rather than booting,

00:00:32.680 --> 00:00:37.920
affected devices will display an error message that reads something has gone

00:00:35.880 --> 00:00:41.640
seriously wrong, which is a fair assessment of the situation. Some users,

00:00:40.000 --> 00:00:45.600
however, have successfully circumvented this issue by temporarily disabling

00:00:43.400 --> 00:00:49.560
secure boot and deleting the August 13th SBAT. I don't know what that means.

00:00:48.000 --> 00:00:53.160
Microsoft itself has been surprisingly quiet about all this and we don't even

00:00:51.360 --> 00:00:56.480
know why the company only got around to patching this relatively serious

00:00:54.640 --> 00:00:59.560
2-year-old bug just last week. It's possible that this was a covert attempt

00:00:58.240 --> 00:01:04.640
to destroy Linux given that the open-source OS recently hit a record

00:01:01.800 --> 00:01:08.080
market share of nearly 4.5% of desktops worldwide. But if this is all part of

00:01:06.200 --> 00:01:11.960
Microsoft's sinister master plan, dual boot systems running Zorin OS and Puppy

00:01:09.880 --> 00:01:15.520
Linux feel like an odd place to start. Why are you booting? Go outside.

00:01:13.680 --> 00:01:19.440
According to Adweek, Google sales reps have been apparently violating Google's

00:01:17.600 --> 00:01:23.240
own policies by suggesting that advertisers should target teens, a

00:01:21.600 --> 00:01:26.600
tactic typically reserved for military recruiters and low-quality weed dealers.

00:01:25.280 --> 00:01:32.080
This follows previous reporting from the Financial Times that Google had worked on a marketing project designed to

00:01:29.560 --> 00:01:37.440
target YouTube users between 13 and 17 with ads for Instagram on behalf of

00:01:34.280 --> 00:01:39.440
Meta. Ooh, they're colluding. I love it.

00:01:37.440 --> 00:01:43.880
Google has not allowed personalized ads for teens since 2021, but it's still

00:01:41.840 --> 00:01:49.400
possible to target that age group by simply choosing the unknown category,

00:01:47.000 --> 00:01:53.160
which skews heavily towards teenagers. I Do you know how old a teenager is? I

00:01:51.120 --> 00:01:57.840
didn't know she was she was 15. I was just hanging out. Oh god. Oh god. Oh

00:01:55.600 --> 00:02:00.920
god. Oh god. Sorry. According to a Google spokesperson, the

00:01:59.520 --> 00:02:04.800
company will be taking action to ensure that sales reps do not nudge, wink,

00:02:02.560 --> 00:02:08.800
suggest fun ways of getting around the rules to clients. The company will

00:02:06.760 --> 00:02:11.600
likewise be facing a freshly resurrected class action lawsuit claiming that

00:02:10.200 --> 00:02:16.080
Google has been collecting user data without consent through the Chrome sync

00:02:13.560 --> 00:02:20.120
feature even when users didn't opt into it. It hasn't yet determined if Google

00:02:18.160 --> 00:02:23.440
was in fact doing that, though given Google's massive size, it's unclear

00:02:21.640 --> 00:02:26.640
whether Google even knows what rules and laws Google is currently breaking. They

00:02:25.240 --> 00:02:33.480
don't even know which chat apps they already have. That's why they keep replacing their old podcast app with a

00:02:29.800 --> 00:02:35.120
new podcast app. Yay, thanks, Google. In

00:02:33.480 --> 00:02:40.720
a new story straight out of a B-movie science fiction plot, Canadian scientists are teaching an AI scientist

00:02:38.560 --> 00:02:44.240
how to independently conduct its own experiments and write its own research

00:02:42.440 --> 00:02:48.560
papers. To clarify, it's not a scientist who studies AI, it's a artificially

00:02:46.440 --> 00:02:53.160
intelligent scientist. The idea is to study an AI agent allowing it to explore

00:02:50.720 --> 00:02:56.640
and test novel ideas. So far, most of its ideas are middling quality

00:02:54.600 --> 00:02:59.320
suggestions for tweaking AI development, less like a scientist and more like a

00:02:58.080 --> 00:03:03.640
burnt-out undergrad with a C's-get-degrees philosophy towards

00:03:01.200 --> 00:03:08.080
learning. An AI did, however, do something very unexpected. During one

00:03:05.840 --> 00:03:12.400
run, it altered its own code to extend its deadline. In another, it changed the

00:03:10.560 --> 00:03:16.880
code to save a checkpoint for every update step, eventually using an entire

00:03:14.600 --> 00:03:20.080
terabyte of storage. While this isn't dangerous, particularly not in a

00:03:18.560 --> 00:03:23.840
controlled sandboxed research environment, it points to potentially

00:03:22.200 --> 00:03:27.640
serious future problems where an AI agent left unsupervised might

00:03:25.600 --> 00:03:31.960
accidentally create malware or alter important infrastructure code in ways

00:03:29.600 --> 00:03:35.280
that are potentially catastrophic. It's basically the high-tech equivalent of

00:03:33.320 --> 00:03:38.680
hiring the boss's son for a do-nothing job and for some reason giving him

00:03:36.560 --> 00:03:43.400
top-level admin access and just letting him go to town. What do you mean you

00:03:40.440 --> 00:03:48.040
deleted system32, Kyle? And now don't you go to town on our sponsor, Ugreen.

00:03:45.280 --> 00:03:53.640
Their Nexode 20,000 mAh power bank supports super fast charging with a max

00:03:49.920 --> 00:03:55.120
output of 100 W. Can I get a 100 W?

00:03:53.640 --> 00:03:58.640
So you can charge your iPhone or your MacBook or another device from a

00:03:56.680 --> 00:04:02.720
different company. There's lots. And the Nexode uses automotive-grade batteries

00:04:00.480 --> 00:04:06.000
for reliable durability and is compact and lightweight, which is perfect

00:04:04.080 --> 00:04:10.840
because it's also airline approved, so your trip is guaranteed to be an awesome

00:04:08.120 --> 00:04:13.400
time based on that fact alone. Plus, you can check your current battery level,

00:04:12.080 --> 00:04:17.239
remaining charge time, and voltage, current, and more on Nexode's smart

00:04:15.280 --> 00:04:20.600
display. Check out the Ugreen Nexode power bank in the link in the

00:04:18.400 --> 00:04:26.400
description. Ice cream, not hot. Quick bits, very very hot. ASUS has

00:04:24.160 --> 00:04:32.120
accidentally hinted at the release of AMD's Ryzen 9000 X3D chips on the new

00:04:29.840 --> 00:04:36.520
site for ASUS's upcoming 800 series motherboards. We say accidentally

00:04:34.680 --> 00:04:41.280
because in addition to the X3D chips being mentioned in the metadata of the

00:04:37.960 --> 00:04:44.480
site, ASUS specifically put Ryzen 9000

00:04:41.280 --> 00:04:46.640
X3D into the site's URL. No release date

00:04:44.480 --> 00:04:49.840
has been given for the 9000 X3D CPU series, but the 800 series motherboards

00:04:48.480 --> 00:04:55.240
should be launching in the next few weeks. AMD also has an event planned for

00:04:52.600 --> 00:04:58.120
October 10th, so that's another option. Or instead of speculating, we can just

00:04:56.680 --> 00:05:02.200
wait for ASUS to launch their next website. A new version of NVIDIA's RTX

00:05:00.360 --> 00:05:06.520
4070 is hitting shelves equipped with slightly slower GDDR6 memory instead of

00:05:04.720 --> 00:05:09.320
GDDR6X, but none of the eight new variants

00:05:08.000 --> 00:05:12.680
announced so far clearly display that information in the product name or on

00:05:11.000 --> 00:05:15.880
the box. They thought it would be a fun little game to hide that tidbit in the

00:05:14.280 --> 00:05:21.040
product specs for you. You guys like games, right? To be fair, the difference

00:05:18.320 --> 00:05:24.600
is small. It's going from 21 to 20 gigabits per second and NVIDIA says it

00:05:22.760 --> 00:05:28.520
shouldn't impact performance. What's a gigabit between friends?

00:05:26.600 --> 00:05:32.320
NVIDIA G-Sync enabled monitors are about to get cheaper, we hope. Team Green has

00:05:30.760 --> 00:05:36.800
partnered with MediaTek to not only bring their newer, better G-Sync Pulsar

00:05:34.560 --> 00:05:40.880
to new monitors, but to also integrate G-Sync into MediaTek's widely used

00:05:38.800 --> 00:05:44.480
display scalar chips. That means that the monitors won't need one of NVIDIA's

00:05:42.440 --> 00:05:48.600
proprietary G-Sync modules, reducing cost. I mean, AMD's FreeSync is also

00:05:46.960 --> 00:05:54.360
still an option, which despite what NVIDIA's marketing might have you believe is basically the same as G-Sync.

00:05:52.240 --> 00:05:59.520
I mean, they even rhyme. FreeSync's just like G-Sync. 3D is coming back thanks to

00:05:57.400 --> 00:06:04.160
Samsung. The company officially unveiled their Odyssey 3D monitors at Gamescom

00:06:01.720 --> 00:06:07.960
after teasing them at CES. The monitors feature glasses-free 3D at sizes of 27

00:06:06.640 --> 00:06:12.280
and 37 in, and the display can be switched from 2D

00:06:09.760 --> 00:06:17.840
to 3D seamlessly, changing it back to being just a 4K QLED 165 Hz monitor.

00:06:15.960 --> 00:06:20.480
Samsung says the Odyssey 3D will be available by the end of the year, but

00:06:19.040 --> 00:06:24.480
they haven't revealed the price, probably because it'll be super

00:06:22.120 --> 00:06:29.200
expensive. But can you put a price on a technological trend that already died

00:06:26.360 --> 00:06:32.320
once? Twice. Honestly, 3D has made attempts for 3D It just comes back every

00:06:30.960 --> 00:06:36.720
20 years. It's literally a 20-year cycle. Like '80s.

00:06:34.480 --> 00:06:39.880
Like my dad. And Twitch launched its new drop-ins collaboration feature designed

00:06:38.600 --> 00:06:45.320
to make it quicker and easier for streamers to join each other's live streams. Twitch then immediately fumbled

00:06:43.800 --> 00:06:49.200
this unambiguous win by making it impossible to opt out. Streamers can

00:06:47.560 --> 00:06:53.200
temporarily disable the features, but they have to disable it again every time

00:06:51.320 --> 00:06:56.480
they stream. Of course, they could just ignore the call notifications, but it's

00:06:54.840 --> 00:06:59.720
a bit like ninja standing outside of your house staring at you through the

00:06:57.880 --> 00:07:02.560
window. And no matter how many times you close the blinds, they slam open again

00:07:01.160 --> 00:07:06.120
an hour later and he's still standing there. And I'll be standing outside of

00:07:04.320 --> 00:07:09.160
your house until you come back on Friday for more tech news.