WEBVTT

00:00:00.320 --> 00:00:05.759
One way you can know we always keep it real on this show is the fact that I

00:00:03.840 --> 00:00:08.960
forgot to write an intro for this one. I'm just going off the cuff here just

00:00:07.279 --> 00:00:14.160
telling you straight up. Isn't that endearing? >> He just read that off the prompt.

00:00:11.599 --> 00:00:18.960
>> The YouTube view apocalypse, as some have called it, may not be YouTube's

00:00:16.320 --> 00:00:24.000
fault, despite some commentators basing entire jokes on that very assumption. In

00:00:22.080 --> 00:00:28.080
their blog post on Monday, YouTube mentioned the possibility that updates

00:00:25.760 --> 00:00:32.239
to ad blockers may have caused some views to stop being counted. And

00:00:29.599 --> 00:00:38.480
YouTube's own liaison Renee Richie reiterated that YouTube didn't change

00:00:34.800 --> 00:00:40.559
anything. And turns out he was right. As

00:00:38.480 --> 00:00:46.239
explained on Twitter by YouTuber and former expert troll Theo Joe, he's

00:00:43.200 --> 00:00:48.559
changed his ways. On August 11th, a URL

00:00:46.239 --> 00:00:52.800
filter was added to Easy List, specifically its affiliated Easy Privacy

00:00:50.879 --> 00:00:57.039
List, which is used by multiple ad blockers to let them know what to block.

00:00:54.719 --> 00:01:02.559
But this change appears to have inadvertently blocked YouTube's method

00:00:59.840 --> 00:01:07.200
of counting views. Fellow YouTuber and Extra Dad, in case you need one, Jeff

00:01:05.040 --> 00:01:11.200
Gearling also drew attention to this with a blog post with much additional

00:01:09.439 --> 00:01:15.840
discussion taking place in this GitHub thread between him, Theo Joe, Yuki, the

00:01:14.159 --> 00:01:18.720
volunteer who made the change on August 11th, and who we love and appreciate for

00:01:17.439 --> 00:01:23.040
their work, even if they accidentally kicked all this off, and Scratchy, who

00:01:21.280 --> 00:01:27.439
did a lot of investigating and made a guide for how users can override this

00:01:25.280 --> 00:01:32.159
change, so creators can benefit from registering their views properly while

00:01:29.600 --> 00:01:37.439
still protecting their privacy. You dropped this king. Can you can you put a

00:01:35.360 --> 00:01:42.159
crown there? Yeah. Thank you. Hold on. Wait a second. Privacy. Yeah. You see,

00:01:39.680 --> 00:01:46.399
while any ad block user could go and manually remove the easy privacy filter

00:01:44.479 --> 00:01:50.079
from their ad blocker settings, they might not want to do that, even if it

00:01:48.479 --> 00:01:54.159
would mean allowing YouTube to count their views. Because the main reason

00:01:51.920 --> 00:02:00.719
many people use ad blockers is to protect their privacy. Because fun fact,

00:01:57.439 --> 00:02:03.119
most ads are also trackers. Isn't that

00:02:00.719 --> 00:02:07.040
fun? Why not both? So, where does all this leave us? Well, another update to

00:02:05.119 --> 00:02:11.680
Easy List has apparently made it so that only third-party hit counters will be

00:02:09.200 --> 00:02:15.520
filtered out, which should mean YouTube's view tracking should work

00:02:13.920 --> 00:02:19.760
properly again. So, at the end of the day, it looks like YouTube wasn't the

00:02:17.360 --> 00:02:22.800
immediate cause of this change. But that doesn't mean they can't mess up the

00:02:20.959 --> 00:02:27.440
platform in other ways, like announcing that today they're integrating their V3

00:02:24.879 --> 00:02:32.000
AI video and audio generator directly into shorts because the internet doesn't

00:02:29.280 --> 00:02:37.519
have nearly enough slop yet. More slop immediately, please. Tell you what, we

00:02:35.120 --> 00:02:40.560
need slop block is what we need. Okay, somebody get on that. Not me, though.

00:02:39.040 --> 00:02:45.040
Google is launching something that's either terrifying or very useful

00:02:43.120 --> 00:02:48.879
depending on how much access to your computer you like to give to third

00:02:46.959 --> 00:02:54.160
parties. It's Google's new app for Windows that helps you find what you

00:02:51.120 --> 00:02:56.640
need faster. Just install it, hit alt

00:02:54.160 --> 00:03:01.519
space, kind of like the shortcut on Mac for Spotlight, and let it sift and

00:02:59.120 --> 00:03:06.239
search through all of your local files as well as Google Drive, your installed

00:03:03.680 --> 00:03:10.959
apps, and the web. If you're intrigued by the idea of anything that could be

00:03:09.280 --> 00:03:16.720
even slightly better than Windows Search, it's available now, but only in

00:03:13.440 --> 00:03:19.280
the US. Still, somehow I managed to

00:03:16.720 --> 00:03:23.840
download it from Google Labs. And yeah, it searches your files, but if you're

00:03:21.920 --> 00:03:29.040
expecting something better than Windows search that doesn't have web search

00:03:26.560 --> 00:03:32.720
involved, I I mean, it very much is still involved. Sometimes it could find

00:03:31.200 --> 00:03:36.799
specific files when I search for the file name, but other times I just got

00:03:34.239 --> 00:03:42.159
web results, so I don't know. Maybe it'll get better over time. Windows

00:03:39.120 --> 00:03:44.560
Search didn't. Windows Search couldn't

00:03:42.159 --> 00:03:48.720
even find today's sponsor, War Thunder. The game that immerses you in intense

00:03:46.480 --> 00:03:52.400
combat with more than 2500 incredibly detailed tanks, planes, helicopters, and

00:03:50.400 --> 00:03:56.480
ships, and one of the most sophisticated vehicle damage models in gaming. We're

00:03:54.400 --> 00:04:01.360
talking individual components, models like engines, fuel tanks, weapons, and

00:03:58.879 --> 00:04:05.920
even crew members. This is still a video game, so they are a component. All

00:04:03.599 --> 00:04:09.519
susceptible to damage or disabling by enemy shells or missiles. different

00:04:07.760 --> 00:04:13.760
types of which behave differently according to the type of armor you have

00:04:11.439 --> 00:04:17.600
equipped. This is basically the Matrix. You can learn about how all those things

00:04:15.280 --> 00:04:21.600
interacted to cause you to blow up using the X-ray view, which would be great to

00:04:19.759 --> 00:04:26.160
have in real life. Maybe they'll make that someday. Join a worldwide community

00:04:23.919 --> 00:04:30.000
of over 70 million players in one of the most comprehensive vehicle combat games

00:04:28.080 --> 00:04:34.240
ever made. Check out War Thunder for free today on PC, console, and mobile

00:04:32.160 --> 00:04:37.120
using our links in the description. And I don't know, it's just like it's just

00:04:35.520 --> 00:04:40.160
sad because most people watching the show, they don't have any quick bits

00:04:38.720 --> 00:04:44.080
when the show starts. So then I'm like, I gota we should give them we should

00:04:42.240 --> 00:04:48.720
give them quick bits, right? Because it's just Oh. Oh, it's recording. Oh,

00:04:46.639 --> 00:04:54.000
you just I found a natural moment. Oh, Mark. Oh, what? Okay. All right. A

00:04:52.000 --> 00:04:58.080
couple huge VR events are happening this evening. One is the Meta Connect event,

00:04:56.320 --> 00:05:01.520
which I think is happening as we're filming this right now because of course

00:04:59.759 --> 00:05:04.720
they scheduled it for 5:00 p.m. Come back on Friday for coverage of that.

00:05:03.120 --> 00:05:08.479
They probably released some new smart glasses. Please ask Mark to run the

00:05:06.800 --> 00:05:12.880
event earlier next time. Mark Zuckerberg. Not this, not Mark.

00:05:10.720 --> 00:05:17.120
>> I'm sorry Gabber. Okay. Then there's a bunch of prominent VR content creators

00:05:15.199 --> 00:05:20.560
who have been heading to Seattle possibly to get a sneak peek of the new

00:05:18.880 --> 00:05:25.840
Steam frame, but I wouldn't know for sure because Gabe didn't invite me.

00:05:22.960 --> 00:05:30.320
That's okay. Uh maybe next time. Uh sounds like we'll find out more soon, so

00:05:27.440 --> 00:05:33.520
stay tuned. That was You're like, what was the news there? It was there was no

00:05:31.759 --> 00:05:39.039
news. That's the problem. Tesla has settled another wrongful death lawsuit

00:05:36.240 --> 00:05:44.240
due to its autopilot technology. This one comes from 2019 when a 15-year-old

00:05:41.919 --> 00:05:50.639
riding in a truck with his pops was hit by a Model 3 going over 60 mph. That's

00:05:47.919 --> 00:05:55.680
almost 100 kmh for the Europeans out there. Tesla has of course argued that

00:05:53.280 --> 00:05:59.680
it's the driver who's at fault here, not their trusty autopilot. But they lost a

00:05:58.080 --> 00:06:05.360
similar case in Florida last month that's going to cost them $243 million.

00:06:03.120 --> 00:06:09.360
They don't want to lose another $243 million. So now they're settling out of

00:06:07.360 --> 00:06:12.759
court for an undisclosed amount. Can't win them all.

00:06:15.120 --> 00:06:21.840
But you could try to settle them. What's the No, you can't. But AMD just won

00:06:19.440 --> 00:06:27.120
another battle in the eternal CPU war against its blue rival, Intel. See, Team

00:06:24.960 --> 00:06:33.280
Blue likes to release two generations of CPUs per motherboard socket over two or

00:06:30.080 --> 00:06:36.960
three years, while AMD likes to release

00:06:33.280 --> 00:06:39.600
at least three generations over 9 years.

00:06:36.960 --> 00:06:45.199
How do they do it? By releasing a clock down version of the Ryzen 5 5600 and

00:06:42.240 --> 00:06:50.639
calling it the new 5600F. Is it the best upgrade if you're still

00:06:47.759 --> 00:06:54.960
on AM4? Not really, but people just like options, you know. But sometimes you

00:06:52.639 --> 00:07:00.720
pick the wrong one. SKH Heinix and their DDR5 DIMs are in some hot water for

00:06:57.600 --> 00:07:03.919
remaining vulnerable to a variant of the

00:07:00.720 --> 00:07:06.479
Rowhammer exploit called Phoenix or if

00:07:03.919 --> 00:07:10.280
you're cultured like me, CVE 20256202.

00:07:11.199 --> 00:07:18.639
Okay. Researchers from ETHZurich and Google found a blind spot in the refresh

00:07:16.400 --> 00:07:23.599
sampling logic and used one of two patterns to flip bits on 15 different

00:07:20.880 --> 00:07:28.800
oni ECC memory modules made between 21 and 2024. Hey, that's the same year

00:07:25.840 --> 00:07:33.280
Casio's Mofflin launched. And I'm telling you that now because it's

00:07:30.560 --> 00:07:39.599
finally coming to America. What it's a fuzzy, cuddly, cute AI robot thing that

00:07:36.639 --> 00:07:45.360
is surprisingly, maybe unsurprisingly, selling out in Japan. So, the Tyrell

00:07:42.160 --> 00:07:47.360
Corporation, I mean Casio, decided it

00:07:45.360 --> 00:07:52.880
was time to spread the love. Pre-orders are already up for the gold or silver

00:07:49.280 --> 00:07:54.720
fuzzball. And it costs a lot for a smart

00:07:52.880 --> 00:07:59.039
companion designed to support, reassure, and grow with you through life's

00:07:56.240 --> 00:08:04.400
everyday moments. Who needs that? And with two axes of movement, operating

00:08:01.440 --> 00:08:10.560
temperatures of up to 35° C, and an included Mofflin bed, it sounds like I'd

00:08:07.680 --> 00:08:16.319
be dumb not to buy one on October 1st. And I'd be dumb not to make more tech

00:08:12.720 --> 00:08:19.759
news for you to watch on Friday. So, I

00:08:16.319 --> 00:08:21.199
guess I will. Hey, see you then. And um

00:08:19.759 --> 00:08:24.759
thanks for watching. Please like and subscribe. Okay, bye.

00:08:24.960 --> 00:08:27.360
It'll