WEBVTT

00:00:06.879 --> 00:00:12.559
HELLO WORLD AND WELCOME TO THE WAN Show.

00:00:10.400 --> 00:00:18.800
HAPPY FRIDAY EVERYBODY. We've got a great show lined up for you. It is the

00:00:14.880 --> 00:00:22.640
first day of the second month of Good

00:00:18.800 --> 00:00:25.439
News Wow. That's right. The ratio of

00:00:22.640 --> 00:00:29.279
good news to bad news has to be I forget what we settled on, but it's pretty much

00:00:27.519 --> 00:00:36.160
mostly good news this week. Starting with something that is like a blast from

00:00:32.320 --> 00:00:40.640
my childhood past. The one and only Zs

00:00:36.160 --> 00:00:44.879
Knight, original developer of Z SNES,

00:00:40.640 --> 00:00:46.399
is back. Zess is back. Completely

00:00:44.879 --> 00:00:50.079
rewritten from scratch. I actually haven't tried it yet, but I intend to

00:00:48.000 --> 00:00:54.559
this weekend. I'm super excited to talk about that. Also, we've got to be

00:00:52.480 --> 00:01:00.079
talking about Oh, no. I don't want to talk about that.

00:00:56.879 --> 00:01:01.920
Oh, this one's good. Microsoft has

00:01:00.079 --> 00:01:08.159
committed in something that they are codenaming K2 seemingly as an

00:01:05.439 --> 00:01:14.000
acknowledgement of the mountain they have to climb a concerted effort to fix

00:01:12.080 --> 00:01:18.000
Windows. Very excited to talk about that. What else we got?

00:01:15.600 --> 00:01:21.040
>> Uh I took mine Toyota. >> You know I try baby.

00:01:19.439 --> 00:01:26.400
>> Toyota did what people have thought about for a really long time which is they took a chair from a car and they

00:01:24.640 --> 00:01:30.400
put it on a stand with some wheels on it and they called it a computer chair.

00:01:27.920 --> 00:01:36.400
Toyota's limited edition $3,500 Crown gaming chair has heating, cooling, and

00:01:32.400 --> 00:01:39.759
USBC seat seat belt buckle. I didn't

00:01:36.400 --> 00:01:40.479
even know that part. It's so expensive.

00:01:39.759 --> 00:01:49.439
Ah, >> but cheaper than a real Toyota. >> That's true. Maybe not much more than a

00:01:45.920 --> 00:01:51.520
used one. Um, and I don't know. We've

00:01:49.439 --> 00:01:55.200
got stuff. There's other stuff. We sponsored a drift car.

00:01:54.000 --> 00:02:02.680
>> Really? You went with that? >> I don't know. Sure.

00:01:58.399 --> 00:02:02.680
I saw a better one right under it.

00:02:03.280 --> 00:02:07.000
It is what it is.

00:02:16.640 --> 00:02:24.080
The show IS BROUGHT TO YOU BY VESSIE, ODO, SQUARESPACE, and Ninja 1, along

00:02:22.000 --> 00:02:28.480
with our rap partner, Dbrand, and our laptop partner, Razer, and our chair

00:02:26.640 --> 00:02:31.840
partner, also Razer. >> If you were a famous musician, what

00:02:30.080 --> 00:02:37.120
genre would you >> want to be in? >> What's the most annoying genre?

00:02:34.800 --> 00:02:39.280
>> No, I think it's called noise. >> Is it? >> No, I think it's called noise.

00:02:38.480 --> 00:02:42.000
>> Is that a thing, >> Dan? Tell me something. What What do you

00:02:41.680 --> 00:02:46.000
think? >> I would defin knows way infinitely more about this than either of us.

00:02:45.040 --> 00:02:50.800
>> I'm going with Sure. >> I would definitely be cringey cringey.

00:02:49.680 --> 00:02:57.440
>> You agree? >> Yeah. >> Okay. Okay. >> I'd be cringey pop style music for like

00:02:54.640 --> 00:03:02.959
moms at this point. I think I think that would be that would be my best shot.

00:02:59.440 --> 00:03:05.360
>> I don't know. Taylor Swift. Um,

00:03:02.959 --> 00:03:09.280
if I could if I had half the talent that Taylor Swift has in one thigh, then I

00:03:07.200 --> 00:03:12.879
could hope to be, you know, more like Taylor Swift. But no, no, I'm afraid I

00:03:11.680 --> 00:03:17.040
might have thighs, but they're not talented. Uh, let's jump right in.

00:03:14.879 --> 00:03:20.879
>> Hold on one second. Noise music, or simply noise, is a subgenre of

00:03:19.040 --> 00:03:27.360
experimental music that is characterized by its use of unwanted noise as a

00:03:24.000 --> 00:03:28.800
primary musical element.

00:03:27.360 --> 00:03:33.519
So, that's that's I think that's probably the most annoying one.

00:03:31.760 --> 00:03:40.159
It's just terrible. Often featuring little or no melody, rhythm, or harmony.

00:03:38.159 --> 00:03:44.640
>> That just sounds like someone was taking the piss. >> It's just terrible.

00:03:41.840 --> 00:03:48.640
>> And then it just accidentally a whole genre.

00:03:45.760 --> 00:03:50.560
>> All right. You're No, no, we're not. We're not.

00:03:49.120 --> 00:03:54.400
>> It's important that everyone knows about noise. Okay. Sorry. Yeah.

00:03:52.239 --> 00:04:00.480
>> Microsoft has created an internal initiative called K2 to fix Windows 11.

00:03:59.519 --> 00:04:06.400
Apparently, it's been going on for a while, though. >> They have finally admitted to themselves

00:04:03.360 --> 00:04:08.959
that Windows 11 is a giant boatload of

00:04:06.400 --> 00:04:14.239
suck. And according to sources inside Microsoft is using the K2 initiative to

00:04:12.400 --> 00:04:21.680
fix the operating system's biggest pain points and win, pun intended, back user

00:04:18.400 --> 00:04:24.240
trust. The company is also reportedly

00:04:21.680 --> 00:04:29.120
intentionally pivoting away from shipping new features as fast as

00:04:26.000 --> 00:04:32.160
possible and refocusing on quality. You

00:04:29.120 --> 00:04:36.800
know, it's kind of amazing

00:04:32.160 --> 00:04:41.440
how every time a company is like having

00:04:36.800 --> 00:04:45.520
big big problems, the idea is, hey,

00:04:41.440 --> 00:04:47.440
why don't we stop intentionally sucking?

00:04:45.520 --> 00:04:51.520
Actually, I wish that was often the solution. I I went on a rant about this

00:04:49.440 --> 00:04:56.960
recently, but not on camera. So, here you go. Ready for it? Here comes the Tim

00:04:54.720 --> 00:05:01.919
Horton's WAN Show rant. >> Oh, hell yeah. This made me so angry. I

00:05:00.000 --> 00:05:04.960
was talking to an American or something and they were basically like, "Well,

00:05:03.520 --> 00:05:09.759
yeah." Yeah, right. You know, you know, right? Like, bud, like Tim Hortons, right? Y'all Canadians, y'all like the

00:05:08.080 --> 00:05:14.880
Tim Hortons, right, Bud? Instantly triggered. >> And and I was basically like

00:05:11.360 --> 00:05:19.199
>> instantly triggered. Okay, let me

00:05:14.880 --> 00:05:21.680
clarify because yes, I do like Tim

00:05:19.199 --> 00:05:27.840
Hortons, but there's a bit of a temporal issue with that statement because while

00:05:24.000 --> 00:05:30.800
it was once true for me and every proud

00:05:27.840 --> 00:05:36.240
Canadian, it is no longer true. Tim Hortons is now owned by restaurant

00:05:33.199 --> 00:05:40.960
brands, which seriously, did they go to

00:05:36.240 --> 00:05:43.039
that to the LTT Store of naming?

00:05:40.960 --> 00:05:48.160
We're going to have a company that owns restaurant. What should we call it?

00:05:44.960 --> 00:05:51.039
Let's call it restaurant brands.

00:05:48.160 --> 00:05:57.039
That aside, okay, restaurant brands is owned by like Black Rockck and some

00:05:54.479 --> 00:06:02.240
Brazilian conglomerate, like a bunch of private equity. There is nothing

00:05:59.759 --> 00:06:07.199
Canadian about Tim Hortons anymore. Oh yeah. >> And after all of that happened, Tim

00:06:05.039 --> 00:06:11.680
Hortons went, at least here on the West Coast, I've been told that on the east

00:06:09.759 --> 00:06:15.759
on the eastern side, some of them do still bake the donuts fresh in store. So

00:06:13.919 --> 00:06:20.880
really here on the West Coast, they went from baking the donuts fresh in store

00:06:18.160 --> 00:06:26.160
every day. Their slogan used to be always fresh. Always Tim Hortons. That

00:06:24.000 --> 00:06:32.080
was their slogan. Now they're still always Tim Hortons, but they're a gross,

00:06:29.120 --> 00:06:35.759
messed up, not fresh version of it. Like you you could get a brand new like the

00:06:34.240 --> 00:06:41.600
freshest doughnut in Tim Hortons. It'll taste like it's 3 days old these days.

00:06:37.840 --> 00:06:44.080
It It's so It's so bad. It's It's

00:06:41.600 --> 00:06:49.600
absolutely disgusting. Uh how did I get on the subject of Tim Hortons?

00:06:45.520 --> 00:06:51.600
>> I literally to be honest. Oh, right.

00:06:49.600 --> 00:06:55.440
When companies start sucking >> Right. Okay. So, this was a while back.

00:06:53.840 --> 00:06:59.440
This must have been like a year ago at this point, but it like it made its way

00:06:57.039 --> 00:07:04.639
into my news feed that Tim Hortons was experiencing less than stellar growth

00:07:02.000 --> 00:07:09.120
and customer engagement. And on a shareholder call, okay, on a shareholder

00:07:06.800 --> 00:07:15.039
call, they're literally acknowledging soft sales and they go,

00:07:11.759 --> 00:07:18.800
>> "Yeah, so here's our plan. We're gonna

00:07:15.039 --> 00:07:21.680
really like double down on the Canadana

00:07:18.800 --> 00:07:26.400
in our marketing and like you know little kids skating on outdoor hockey

00:07:23.919 --> 00:07:31.520
rinks and maple leaves and beavers and all those very Canadian things in order

00:07:28.880 --> 00:07:36.319
to connect more to our Canadian cere's an idea. Why don't you makeing edible

00:07:34.240 --> 00:07:41.440
food as a way to connect with your Canadian customers? I used to when I

00:07:38.560 --> 00:07:46.000
would travel abroad, uh, so when I'm at airports basically, um, I I had a

00:07:44.400 --> 00:07:49.680
routine where every single time I would go to Tim Hortons. So like the last

00:07:48.000 --> 00:07:53.840
thing I did in Canada was like one of the most Canadian things you could do, which is go to Tim Hortons.

00:07:51.759 --> 00:08:00.400
>> Go to Tim Hortons, get some chili. >> Haven't done it. Yep. >> Get a sandwich, get get a donut.

00:07:58.960 --> 00:08:06.720
>> They all suck now. >> Haven't done it in years. >> They even up the chili. How do

00:08:03.759 --> 00:08:12.000
you up chili? It's literally just like meat and tomato paste and beans and then

00:08:09.919 --> 00:08:15.120
you just put it over heat. Okay. The chili is fine. But the problem is the

00:08:14.080 --> 00:08:18.879
bun sucks. >> Oh, the chili has gotten worse as well. >> Has it really? Okay. I think so.

00:08:17.840 --> 00:08:21.919
>> I haven't had it in a while. >> It feels like it. I might just be like, >> "Dude,

00:08:21.280 --> 00:08:25.759
>> annoyed. >> The bun tastes >> I also use the bun as a spoon."

00:08:24.639 --> 00:08:30.319
>> Well, yeah. That's the whole point. >> So, the bun being way worse may have

00:08:27.680 --> 00:08:34.959
impacted my opinion of the chili. >> Okay. Because like I used to go and get

00:08:32.159 --> 00:08:37.599
Tim Horton's chili for my lunch. Like seriously, this is embarrassing, but

00:08:36.880 --> 00:08:44.320
like >> two to three times a week when I was working at NCX, I'd get my chili, I'd

00:08:41.760 --> 00:08:48.240
get my bun, I'd get usually when they had them, I'd get the blueberry fritter.

00:08:46.320 --> 00:08:50.959
Oh, the blueberry fritter. The only problem with the blueberry fritter was

00:08:49.519 --> 00:08:55.519
how often they ended up undercooking them, which looking back on it is maybe why they stopped baking them in store.

00:08:53.760 --> 00:08:59.040
The point is that doesn't matter. I would get my blueberry fritter, I'd get

00:08:56.959 --> 00:09:06.480
my lemon iced tea, and that was it. The lunch of champions. That lunch took OCZ

00:09:03.120 --> 00:09:09.200
as a product line from like $3,000 a

00:09:06.480 --> 00:09:15.600
month to $300,000 a month. Okay, that's what Tim Horton's

00:09:11.760 --> 00:09:19.600
Chili did in his prime. Now

00:09:15.600 --> 00:09:23.800
I wouldn't feed my dog that bun.

00:09:19.600 --> 00:09:23.800
I don't even have a dog

00:09:24.720 --> 00:09:32.720
anyway. So yeah, I wish that every company came up with the idea of how

00:09:30.160 --> 00:09:36.320
about making the product suck less, but restaurant brands couldn't do it.

00:09:35.839 --> 00:09:41.279
Anyway, >> I I genuinely think Tim Hortons was so

00:09:39.040 --> 00:09:47.519
important to Canada's national identity that that sale should have been blocked.

00:09:43.680 --> 00:09:50.560
>> I I actually strongly agree. It like

00:09:47.519 --> 00:09:52.560
actually was like our prime minister

00:09:50.560 --> 00:09:56.800
would talk about it globally. Like this was this was it was not a

00:09:54.880 --> 00:10:02.640
>> this was not just some random like restaurant. Yeah. >> Like like going to Tim Hortons in the

00:09:59.920 --> 00:10:06.399
morning for breakfast is like was >> might as well be the canteen of Canada.

00:10:04.480 --> 00:10:09.760
Like it's it's just Yeah. >> And it's ruined now. >> Like I'm trying to think of like what

00:10:08.560 --> 00:10:15.519
would be an like >> I don't know of a single example. It would be like Ford like not be it would

00:10:13.839 --> 00:10:19.519
be like Ford selling to like >> Volkswagen company.

00:10:16.959 --> 00:10:23.519
>> Yeah. Or to Gily or something like imagine as an American if you're

00:10:21.200 --> 00:10:27.760
watching this right now if like Ford did not was not American.

00:10:25.920 --> 00:10:30.000
>> I don't think Ford is as tied into the American ID as as Tim Bordon was in

00:10:29.600 --> 00:10:38.000
Canadian. >> Depends you know like like built Ford tough like dude is there a country on

00:10:35.600 --> 00:10:41.839
earth that loves the F-150 the way that America does? Like let's let's be real

00:10:39.760 --> 00:10:45.200
here. But still, let's be real here. I still think

00:10:43.360 --> 00:10:48.480
>> I still think it's more >> like what would be what would be like a

00:10:46.800 --> 00:10:54.320
what would be like a like a like a German equivalent? Like what would what

00:10:50.480 --> 00:10:57.360
would be so so offensive

00:10:54.320 --> 00:10:58.560
to like uh guys hit me hit me with it.

00:10:57.360 --> 00:11:03.040
You know what? No, we can move on. We can move on. Okay, so coming back to

00:11:00.560 --> 00:11:08.079
Windows on the performance side, the start menu is being completely rewritten

00:11:05.600 --> 00:11:12.480
in Microsoft's own WinUI3 framework, which is supposed to make it 60% faster

00:11:10.160 --> 00:11:16.640
and more responsive. That is such a See, that's such a baffling one to me is like

00:11:14.399 --> 00:11:20.560
when I open the start, what are you even doing?

00:11:18.959 --> 00:11:26.560
Like there's there's a there's there's things that I do on computers that just

00:11:24.240 --> 00:11:29.839
completely bewilder me how they can take as long as they do. Uh, perfect example

00:11:28.240 --> 00:11:34.399
of this. We were running a benchmark on set yesterday. We were uh performance

00:11:32.320 --> 00:11:40.320
testing. Oh, we ran SLI. >> We we grabbed some 3090 Ti, okay,

00:11:37.200 --> 00:11:42.720
>> and we we like ran like modern games

00:11:40.320 --> 00:11:48.399
that would still run. It's not really SLI. It's more of like the direct X12

00:11:45.040 --> 00:11:50.160
multiGPU thing, but hey, we we ran them

00:11:48.399 --> 00:11:53.200
and in the best case scenario, it was actually pretty competitive with a 5090

00:11:51.680 --> 00:11:58.079
in like 3D Mark. It was pretty pretty crazy. Anyway, the point is when we were

00:11:55.040 --> 00:12:00.880
running 3D Mark, I was just like I was

00:11:58.079 --> 00:12:04.800
losing my mind because it's just always bothered me. You know how it does that

00:12:02.800 --> 00:12:11.360
thing where it's like um detecting system configuration

00:12:07.920 --> 00:12:12.480
and it takes like a minute

00:12:11.360 --> 00:12:16.800
to do what? >> Yeah. Like how long does Steam hardware survey take?

00:12:14.880 --> 00:12:21.279
>> How how long does it take to get a string of characters for for the

00:12:19.279 --> 00:12:26.160
identifier of a piece of hard? Like we we run at billions of operations per

00:12:24.000 --> 00:12:30.240
second on modern computing devices. You've got to be kidding me. Or like

00:12:28.000 --> 00:12:37.120
when a Wi-Fi access point takes like forever to authenticate the password.

00:12:32.160 --> 00:12:38.480
It's like it's literally eight bits.

00:12:37.120 --> 00:12:44.880
>> I know it isn't. >> Okay. >> I know it isn't.

00:12:41.760 --> 00:12:46.959
>> But but it's it seems so trivial. And in

00:12:44.880 --> 00:12:52.000
the same way the start menu is like what are you even actually doing? Like all of

00:12:49.440 --> 00:12:58.959
this has got to be pre-cached. What are you doing? You're You're not doing

00:12:54.399 --> 00:13:00.560
anything. Why Why is there like a delay?

00:12:58.959 --> 00:13:03.839
Well, hopefully there won't be anymore. >> I don't know enough of the the

00:13:02.079 --> 00:13:08.720
difference between like what is it? Win UI or whatever um and React Native. As

00:13:07.440 --> 00:13:14.240
far as my understanding goes, React Native was calling Win UI. So there the

00:13:11.839 --> 00:13:18.399
the the so the the start menu right now is a React Native app as far as my

00:13:15.920 --> 00:13:23.440
understanding goes. Um, and if they're just removing that layer and stepping

00:13:20.560 --> 00:13:26.800
down one and going to win UUI. I I don't know how this stack works. I read

00:13:24.959 --> 00:13:29.680
quickly that apparently at least sometimes it is calling Win UI. So, I'm

00:13:28.480 --> 00:13:37.519
assuming they're just stepping down a layer. Like maybe you gain a bunch of performance there. The fact that any

00:13:34.480 --> 00:13:40.560
part of Windows native UI is React

00:13:37.519 --> 00:13:42.560
Native is wild to me. Oh, this is great.

00:13:40.560 --> 00:13:46.079
Greak has another good one. I hate it when Windows takes forever to tell me my

00:13:44.079 --> 00:13:50.560
password's wrong. I accidentally pressed enter instead of, you know, enter

00:13:47.440 --> 00:13:52.240
anything like just immediately when you

00:13:50.560 --> 00:13:54.880
when you do it like six or seven times or whatever. That could be that can be a

00:13:53.839 --> 00:14:01.040
security feature where it's like delaying you being able to put it in again. But when it just like takes a

00:13:59.040 --> 00:14:05.360
while, it's dude, it's like a handful of characters. It either the hash matches

00:14:02.800 --> 00:14:10.800
or it doesn't for crying out loud. >> Anyway, Microsoft is also reportedly

00:14:07.760 --> 00:14:13.440
removing ads from its start menu. Again,

00:14:10.800 --> 00:14:17.920
like a a bold move. Bold move. This is like restaurant sales falling. They come

00:14:15.839 --> 00:14:25.519
up with the bold idea of making food fresh. Um, and then for gaming,

00:14:21.279 --> 00:14:28.800
Microsoft is treating. This is crazy.

00:14:25.519 --> 00:14:30.800
This is probably the best marketing for

00:14:28.800 --> 00:14:35.279
Steam OS >> that Valve could have never afforded

00:14:33.120 --> 00:14:40.160
with all their billions and billions of dollars of I'm Gabe Newell. Rather than

00:14:38.160 --> 00:14:44.399
buying a yacht, I will literally buy the company that makes the yachts. all of

00:14:42.560 --> 00:14:49.519
the money that they have could never have purchased. Microsoft is treating

00:14:46.720 --> 00:14:54.079
Valve's Steam OS as a performance benchmark.

00:14:51.040 --> 00:14:56.320
They want Windows gaming performance to

00:14:54.079 --> 00:15:00.959
be comparable to Steam OS on identical hardware, which they say is critical

00:14:58.480 --> 00:15:06.399
because the next Xbox is reportedly going to run Windows 11.

00:15:04.959 --> 00:15:11.920
Oh man, they were doing really good up until >> Is this is this Have they hard confirmed

00:15:09.760 --> 00:15:16.160
that there was going to be another Xbox? >> Yeah, Project Scorpio I think it's

00:15:13.680 --> 00:15:19.600
called like the new CEO Helix.

00:15:18.000 --> 00:15:24.800
Helio something. Helix. Helix. Thank you.

00:15:21.440 --> 00:15:26.320
Lightning X in chat. Um File Explorer is

00:15:24.800 --> 00:15:30.240
also getting major performance fixes with a third party app called File Pilot

00:15:28.320 --> 00:15:34.079
being used as the performance benchmark they're shooting for. This is like

00:15:31.519 --> 00:15:38.000
embarrassing. Who makes File Pilot? Like, no offense. No offense. You're

00:15:37.600 --> 00:15:44.240
probably >> No, it's it's I mean, it's the opposite. It's a huge brag if you're File

00:15:42.720 --> 00:15:48.959
Pilot. That's amazing. >> But I don't even know who you are. And

00:15:47.120 --> 00:15:55.759
the fact that Microsoft, a multi-trillion dollar company, is

00:15:51.199 --> 00:15:58.959
looking at this going, "Yeah, these guys

00:15:55.759 --> 00:16:00.880
are crushing us. We need to do we need

00:15:58.959 --> 00:16:04.720
to do better." Okay. Who are you? Manifesto fast,

00:16:02.480 --> 00:16:06.320
>> dude. Search for system commands. This is actually sick.

00:16:05.519 --> 00:16:11.920
>> Hold on. My god. >> Is file pilot dope? >> File pilot is one guy,

00:16:09.680 --> 00:16:18.639
>> dude. >> Catholic Croatian husband, father of

00:16:14.800 --> 00:16:20.639
five. One extremely busy guy.

00:16:18.639 --> 00:16:24.639
>> Just donking on Windows. Look at that. Look at this. >> That's awesome.

00:16:23.120 --> 00:16:29.440
>> Hey, what am I looking at here? Oh, this is File Pilot. >> Yeah, he's selected a bunch of things

00:16:27.040 --> 00:16:32.639
and select a system he can search. >> Yeah, >> I never even like thought about that.

00:16:31.360 --> 00:16:36.560
That's awesome. Finally, Windows Update is being

00:16:34.720 --> 00:16:42.839
reworked, too, with the goal of making Windows 11 reliable enough that you only

00:16:38.560 --> 00:16:42.839
need to restart once a month.

00:16:44.639 --> 00:16:49.199
>> Dude, File Pilot's cool. You might if we're doing that thing, you should maybe

00:16:48.639 --> 00:16:56.800
include >> Microsoft Microsoft setting the bar. Okay, we want to We want to beat the

00:16:54.320 --> 00:17:01.440
performance of an operating system that the games literally don't even run

00:16:58.399 --> 00:17:06.000
natively on. We want to beat this one

00:17:01.440 --> 00:17:08.880
dude in Explorer, like the most critical

00:17:06.000 --> 00:17:14.480
thing in Windows that literally is like Windows 3.1. Okay. And we want to only

00:17:12.799 --> 00:17:20.720
have to restart your computer once a month. They put the bar

00:17:17.280 --> 00:17:22.319
here. Come on, you guys.

00:17:20.720 --> 00:17:27.839
>> Also, the taskbar is getting back the ability to put the bar somewhere.

00:17:23.919 --> 00:17:29.840
>> Moved and resized. K2 is reportedly not

00:17:27.839 --> 00:17:33.679
going to be a single release, but an ongoing initiative that started in the

00:17:31.679 --> 00:17:38.840
second half of 2025 with Moe's changes rolling out through the end of 2026 and

00:17:35.520 --> 00:17:38.840
into 2027

00:17:40.480 --> 00:17:46.559
discussion question. And for this, I

00:17:44.000 --> 00:17:51.120
need you to put away the chat, close your eyes,

00:17:49.120 --> 00:17:54.240
and search deep inside your feelings. Search your feelings, Luke.

00:17:52.480 --> 00:17:59.919
>> Okay? I'm channeling the force. >> Sorry.

00:17:56.799 --> 00:18:02.240
>> Do you think Windows can win back its

00:17:59.919 --> 00:18:07.520
users? And you're searching your feelings because, you know, you at least

00:18:05.440 --> 00:18:12.520
used to be a Windows user. >> Or is it too little too late? Search

00:18:08.960 --> 00:18:12.520
your feelings, Luke.

00:18:15.360 --> 00:18:20.400
>> Uh, I mean, I think I think so. And the

00:18:18.799 --> 00:18:24.480
reason why I think so is I think most of them haven't left yet.

00:18:22.000 --> 00:18:28.520
I think most of them are very vocally honestly they should be

00:18:28.960 --> 00:18:35.440
action of the rage that the community

00:18:32.160 --> 00:18:38.559
has had. I think some people have left.

00:18:35.440 --> 00:18:39.760
I've left. I'm not stopping using Linux

00:18:38.559 --> 00:18:45.039
when the Linux challenge is over. There's a spoiler. Um I'm going to

00:18:41.919 --> 00:18:46.720
continue using it. Um but it isn't it

00:18:45.039 --> 00:18:51.440
isn't completely too late. the the approach that I'm taking right now is

00:18:49.440 --> 00:18:58.160
what is the most appropriate tool for me to use to have the least frustration,

00:18:55.200 --> 00:19:02.480
the the most good time, >> whatever you want to call it. Y

00:18:59.840 --> 00:19:06.640
>> um and be able to operate and get stuff done without significant um like

00:19:05.039 --> 00:19:11.120
inability to do the thing that I want to do. And

00:19:08.400 --> 00:19:18.640
>> right now that is almost always pushing me to Linux either mint on my laptop,

00:19:14.080 --> 00:19:20.559
cache on my desktop. Um, I do

00:19:18.640 --> 00:19:24.320
plan on ending with a dual boot setup on my desktop, but it's honestly completely

00:19:22.640 --> 00:19:30.240
unnecessary on my laptop, and I will be continuing to run Mint. If this bar

00:19:27.280 --> 00:19:34.880
shifts and it makes more sense for me to use Windows,

00:19:32.400 --> 00:19:39.440
I'd probably just use Windows, but that is not currently true. And like

00:19:37.520 --> 00:19:43.120
I'm I'm trying to be honestly like pretty

00:19:40.960 --> 00:19:45.919
um what would I say about that?

00:19:44.559 --> 00:19:53.039
>> Objective. Yeah. >> Yeah. >> And like I I I whipped I I went over to

00:19:50.240 --> 00:19:56.000
my Windows drive. Uh cuz I still have my Windows drive in my desktop. It's just

00:19:54.640 --> 00:20:00.480
been sitting there untouched for like 2 months. I jumped over to my Windows

00:19:57.679 --> 00:20:03.039
drive just to like Okay. Like is it going to function? I haven't even booted

00:20:01.919 --> 00:20:07.120
into it for two months. I don't know. Like did I corrupt it in that time? Maybe.

00:20:05.039 --> 00:20:11.679
>> I bet I know where this is going. >> I ran Windows update for a while. Got

00:20:09.520 --> 00:20:18.080
annoyed by a few things. booted back into Cashi and was like, "Nice."

00:20:15.120 --> 00:20:23.360
It took, dude, it took and I know I haven't updated in a while. Okay. Okay.

00:20:20.400 --> 00:20:32.240
All right. It took forever to update. It was so long. Super

00:20:28.559 --> 00:20:34.320
super long time. Um I It felt so stupid

00:20:32.240 --> 00:20:38.559
that like the control panel seems like it wants to fight me.

00:20:37.200 --> 00:20:43.919
Like there's just there's just like I'm trying to do multiple things at once and it's like no no I'm just going to like

00:20:42.320 --> 00:20:47.760
redirect. I guess you can just have one of me open. It's like what are you what

00:20:45.360 --> 00:20:52.240
are you even talking about? Um search was just annoying again. Just like

00:20:49.520 --> 00:20:56.880
everything it was just like it felt gross. So I I went back.

00:20:54.720 --> 00:21:00.559
>> All right let's jump into Windows Insiders. >> Actually sorry there's an interesting

00:20:58.640 --> 00:21:05.120
question from chat at at ZM said have you tried macOS recently? If not would

00:21:02.240 --> 00:21:09.039
you give it a try? I am more open to trying other operating systems now. I

00:21:06.799 --> 00:21:12.080
recently learned Mint and Cashy. >> Do you want to borrow my Neo?

00:21:10.400 --> 00:21:17.600
>> I'm not using it right now. It's on my desk. >> I don't necessarily think so. But what I

00:21:14.640 --> 00:21:19.280
was going to add is that I was using my mom's Neo for a bit.

00:21:18.720 --> 00:21:24.880
>> Mhm. >> And it was totally fine.

00:21:22.000 --> 00:21:28.880
I do find macOS a little weird. >> I don't know if I would fully get used

00:21:26.640 --> 00:21:32.799
to it. I still don't think it's for me really. There's some stuff that I find

00:21:30.720 --> 00:21:37.600
just completely unnecessary and irritating about macOS. The fact that

00:21:34.480 --> 00:21:39.760
you have to click on a window first to

00:21:37.600 --> 00:21:44.960
make it the focus window before you can interact with a thing.

00:21:42.640 --> 00:21:49.520
I see it both ways. Like on Windows sometimes you can like if a window like

00:21:47.200 --> 00:21:52.400
pops up and you're like about to click something, you can like accidentally

00:21:50.880 --> 00:21:56.960
interact with something that you didn't mean to. And I can see how the macOS

00:21:54.960 --> 00:22:02.880
way kind of prevents that, but also it just

00:22:00.240 --> 00:22:08.559
it just creates a second click like anytime I'm switching between things and

00:22:04.640 --> 00:22:09.919
I I do not find that to be um great.

00:22:08.559 --> 00:22:14.720
>> There's a couple Yeah, there's a couple little things like that. There's a couple things that feel a little clunky

00:22:12.080 --> 00:22:19.600
to me just cuz it I don't know. It's just not really my style. Um, I do

00:22:17.039 --> 00:22:24.000
think, however, at this point in time, if there was a killer app on macOS, I

00:22:22.240 --> 00:22:29.120
wouldn't flinch using it. >> Yeah. >> Which I think is not true as of a year

00:22:26.640 --> 00:22:33.280
ago. So, like, if I was an editor and it was like, oh boy, I'm going to have to

00:22:30.480 --> 00:22:37.440
use Final Cut, it's like, okay, I mean, if I have a Mac, yeah, sounds good. More

00:22:35.360 --> 00:22:42.480
Windows news, though. Windows Insiders can now pause updates indefinitely in

00:22:39.679 --> 00:22:46.960
35day increments. Uh, Windows Insiders can uh Oh, and there's no cap on

00:22:44.559 --> 00:22:51.360
renewals. This is a Windows in Oh, for crying out loud. Okay, we need to do a

00:22:48.799 --> 00:22:55.280
thing where the the title and the first line are not the same

00:22:53.120 --> 00:22:59.600
>> cuz just >> Yeah. No, I completely agree also

00:22:57.679 --> 00:23:05.039
indefinitely for 35 days. >> Yeah. So, so for as long as you want,

00:23:02.400 --> 00:23:09.440
you can keep saying 35 days later. >> 35 days later. Um Okay.

00:23:07.520 --> 00:23:14.400
>> You can also restart or shut down without being forced into an update and

00:23:11.760 --> 00:23:18.640
restart. previously got 5 weeks max before Windows would force these

00:23:16.799 --> 00:23:23.280
updates. This is only available in the experimental channel which replaced the

00:23:20.640 --> 00:23:27.280
old dev and canary channels. Microsoft's own description, uh, features here may

00:23:25.600 --> 00:23:30.799
change, get delayed, or not ship at all. So, the people testing this are the ones

00:23:29.039 --> 00:23:34.720
who opted into the most bleeding edge pre-release builds because they want

00:23:32.320 --> 00:23:38.480
updates as early as possible. uh regular Windows users who've been getting forced

00:23:36.240 --> 00:23:44.000
restarted mid meeting for a decade don't have this yet and there's no timeline or

00:23:40.559 --> 00:23:45.840
confirmation for a general rollout. Now,

00:23:44.000 --> 00:23:49.120
our discussion question is, how did it take Microsoft over a decade to let

00:23:47.600 --> 00:23:56.320
people decide when their own computer updates? And my crazy hottake response

00:23:52.720 --> 00:23:57.440
is, I actually don't like this

00:23:56.320 --> 00:24:03.760
crazy >> people should probably update their computers. I uh when I did my first Mac

00:24:01.919 --> 00:24:08.880
OS challenge, so the first time I switched to macOS, I think it was on

00:24:05.200 --> 00:24:11.120
the 5K iMac uh was the first time I like

00:24:08.880 --> 00:24:16.320
used nothing but I uh nothing but macOS for 30 days or 60 days or however long

00:24:13.360 --> 00:24:20.640
it was. The thing that was most life-changing about it for me in a

00:24:18.320 --> 00:24:25.679
positive way was the way that macOS handled updates at that time and it

00:24:22.559 --> 00:24:28.080
still does actually. And that is that it

00:24:25.679 --> 00:24:33.919
would say hey there's an update like a little you know little thing and then

00:24:30.400 --> 00:24:36.799
you'd be like okay and then you would

00:24:33.919 --> 00:24:39.840
come in the next day in the morning and everything would be exactly where you

00:24:38.240 --> 00:24:44.960
left it and your computer would have installed all the updates and then opened everything back up right where

00:24:42.240 --> 00:24:50.960
you left it. Pausing updates is not the solution.

00:24:48.000 --> 00:24:55.520
better handling of saving all of my work, saving my state, and then

00:24:53.200 --> 00:25:02.159
restoring my state and just doing the update when I'm not using my computer

00:24:58.000 --> 00:25:06.559
is, in my opinion, a way more elegant

00:25:02.159 --> 00:25:09.120
solution. Like I I get I get like I get

00:25:06.559 --> 00:25:13.679
agitated when, you know, someone hands me their phone or their computer to use

00:25:11.120 --> 00:25:17.840
and I see that they're running like a year old build of whatever operating

00:25:16.240 --> 00:25:22.880
system they're on. Something I've really started to enjoy is I I actually system

00:25:20.080 --> 00:25:27.840
update way more often on Linux than I did on Windows. But I really like that

00:25:25.279 --> 00:25:32.159
it just updates everything. Like that's awesome. Like I'll get

00:25:29.360 --> 00:25:35.840
Discord updates. I'll get any other software that I have. It'll just update

00:25:33.760 --> 00:25:38.880
my entire system all at once. I'm not individually updating programs.

00:25:37.200 --> 00:25:42.240
>> But are you asking for the I mean the Microsoft Store is a thing that exists

00:25:40.400 --> 00:25:46.480
and Windows can manage your updates for you. But I think most of us

00:25:43.919 --> 00:25:50.880
>> just make it not terrible though. Like I I that but honestly I think that's

00:25:48.640 --> 00:25:55.600
really the solution. Like games for Windows would have been fine if it

00:25:52.480 --> 00:25:57.840
wasn't dog crap. Microsoft Store would

00:25:55.600 --> 00:26:05.120
be totally fine. People like package managers on Linux. They just don't

00:26:00.880 --> 00:26:07.600
>> always uh suck complete butt. And a lot

00:26:05.120 --> 00:26:10.799
of time the Microsoft Yeah. The first one that I had on on Cashy sucked and

00:26:09.360 --> 00:26:15.600
then I I went with KDE and now I actually really like it. Um,

00:26:14.000 --> 00:26:19.200
and and the one that comes packaged with Mint is like fantastic to be honest, but

00:26:17.520 --> 00:26:22.880
it it's it's very up and down. But the Microsoft Store in my opinion is like

00:26:20.880 --> 00:26:27.279
the the the problem. Um, >> yeah. And the fact that Windows Update

00:26:25.039 --> 00:26:28.559
and the Microsoft Store are not integrated.

00:26:28.080 --> 00:26:33.600
>> Yeah. >> Like >> crazy. Like if the best way to install

00:26:31.840 --> 00:26:37.760
stuff on Windows was Microsoft Store because Microsoft Store wasn't an

00:26:35.279 --> 00:26:40.720
annoying piece of crap and also because that way it would just auto update along

00:26:39.279 --> 00:26:46.480
with Windows update and just made everything really smooth. >> And like why do I have to go digging for

00:26:44.080 --> 00:26:50.400
a driver update? And I know that Microsoft has actually done a lot of

00:26:48.080 --> 00:26:57.120
really good work around like automatic driver management, but the fact that

00:26:52.799 --> 00:26:59.360
some of it is over here and some of it

00:26:57.120 --> 00:27:04.400
is like it'll never update unless I like go and get it and some of it is handled

00:27:01.440 --> 00:27:09.600
by like Armory Crate and some of it is in Windows Update and like the fact that

00:27:06.400 --> 00:27:12.720
it's everywhere is

00:27:09.600 --> 00:27:14.559
it's one of those things where the first

00:27:12.720 --> 00:27:20.559
thing that someone would would tell me from Microsoft or even you know a viewer

00:27:17.840 --> 00:27:24.960
would tell me is well that's not X's fault you know or that's because of you

00:27:24.320 --> 00:27:29.600
know this >> and that might be true of choice

00:27:27.840 --> 00:27:35.360
>> and and you know what those things are super super true

00:27:32.640 --> 00:27:38.960
but you know what as as a user from a user perspective I don't give a flying

00:27:37.760 --> 00:27:44.240
whose fault it is >> yeah it doesn't matter >> it doesn't matter what matters is that

00:27:42.240 --> 00:27:50.720
it's a terrible user experience experience and somebody needs to fix it.

00:27:48.080 --> 00:27:54.880
Like the way that um >> this is while you think of that this is

00:27:53.120 --> 00:27:57.600
what I'm talking about like all the time when I talk about how it's actually it's

00:27:56.640 --> 00:28:01.760
not even here right now so I keep gesturing at it but my my laptop when I

00:27:59.840 --> 00:28:06.960
talk about how it's actually easier and like less annoyance and more

00:28:04.799 --> 00:28:10.559
productivity to use it. This is what I'm talking about. I don't have to go around

00:28:08.640 --> 00:28:13.279
and update all these individual apps. I'm not like partway through working on

00:28:12.320 --> 00:28:18.960
something and then I need to open another app to do something and oh my god, now that needs an update, whatever.

00:28:16.480 --> 00:28:25.520
No, I just update once and it does everything and it's fine and it works.

00:28:22.240 --> 00:28:27.520
It's great. Every everyone freaks you

00:28:25.520 --> 00:28:29.840
out when you go to any Archbased DRO because they're like, "Oh, it's rolling.

00:28:28.880 --> 00:28:36.480
You're going to update. It's going to break everything." When I go to update on Cashachi, it

00:28:33.840 --> 00:28:40.960
checks Arch news. >> Oh, it and it it'll be like, "Oh, no.

00:28:39.520 --> 00:28:44.880
this one might require manual intervention. He might not want to install this right now. And it's like,

00:28:43.120 --> 00:28:49.679
okay. And I just close it and then I wait until it doesn't. I just do it that

00:28:47.840 --> 00:28:53.120
way. Like it's >> Harry G made a good point. The driver

00:28:51.760 --> 00:28:57.200
nightmare is because of third parties. They don't want to ship their drivers via Windows update because they can't

00:28:55.279 --> 00:29:01.919
bundle their bloatware with it. So then Microsoft should just straight up stop

00:28:59.279 --> 00:29:04.880
Wickle certifying anything that requires bloatware to be shipped with it. Like

00:29:03.200 --> 00:29:09.120
these are things that Microsoft >> flex your muscle, man. does like they're

00:29:06.720 --> 00:29:14.320
they flex their muscle to do the wrong things. Like they're flexing their

00:29:11.279 --> 00:29:16.480
muscle to put stupid Candy Crush in my

00:29:14.320 --> 00:29:22.080
stupid operating system. No, flex your muscle to do things that enhance the

00:29:18.960 --> 00:29:26.159
user experience and make Windows more

00:29:22.080 --> 00:29:27.919
secure and faster and more powerful and

00:29:26.159 --> 00:29:35.039
more usable. Uh, all right. Let's jump into Ooh.

00:29:31.919 --> 00:29:38.080
Okay. This is one of our bad newses for

00:29:35.039 --> 00:29:41.520
this week. Intel has reportedly

00:29:38.080 --> 00:29:46.000
cancelled discrete gaming GPUs in the

00:29:41.520 --> 00:29:49.520
upcoming XC3P Arc Celestial family.

00:29:46.000 --> 00:29:51.919
According to Intel leaker JKEN, Intel

00:29:49.520 --> 00:29:58.240
cancelled their discrete GPUs. So, these are the add-in cards for Celestial long

00:29:54.880 --> 00:30:00.320
ago. That means that the ARK B580, so

00:29:58.240 --> 00:30:07.120
this is their battle mage generation, will remain Intel's latest gaming GPU

00:30:03.120 --> 00:30:08.880
with no clear successor in sight. XC3P

00:30:07.120 --> 00:30:16.080
will show up in data center and workstation products, just not gaming

00:30:12.240 --> 00:30:19.200
cards. The nextG XC4 Druid architecture

00:30:16.080 --> 00:30:23.600
is expected late 2027, but whether it

00:30:19.200 --> 00:30:26.080
gets a gaming GPU, in JK's words, is up

00:30:23.600 --> 00:30:31.679
in the air. Intel has not confirmed or denied any of this. Our discussion

00:30:29.039 --> 00:30:36.880
question here is if Intel quietly walks away from gaming GPUs, what happens to

00:30:34.640 --> 00:30:42.159
GPU pricing? The answer is it goes up.

00:30:40.880 --> 00:30:45.279
>> However, however, >> the answer is nothing. >> However,

00:30:44.320 --> 00:30:49.760
>> unfortunately, >> I um

00:30:47.360 --> 00:30:54.159
>> I really want to keep the faith. This is something that former Intel CEO Pat

00:30:52.640 --> 00:31:01.360
Gellinger um >> allowed to continue Intel's discrete GPU

00:30:58.960 --> 00:31:08.399
ambitions. And I really hope that Lipboutan uh does not kill. I know that

00:31:05.039 --> 00:31:10.640
there's a lot of like issues with the

00:31:08.399 --> 00:31:17.600
consumer cards that you know like being low margin and uh catering to a a super

00:31:14.399 --> 00:31:19.840
noisy, highmaintenance customer base.

00:31:17.600 --> 00:31:26.960
Let's face it, gamers are not the easiest customers to deal with. But I

00:31:23.760 --> 00:31:28.640
really do believe and if there the

00:31:26.960 --> 00:31:34.799
strongest argument that I can make for this is so does Jensen Hang who is the

00:31:32.000 --> 00:31:39.440
CEO of from time to time the world's most valuable company. I really do

00:31:37.200 --> 00:31:47.120
believe that the innovation on the gaming side makes the enterprise and

00:31:43.279 --> 00:31:49.760
professional sides better and stronger

00:31:47.120 --> 00:31:55.360
for all the work that they do and also gives you a volume market that you can

00:31:52.720 --> 00:31:59.600
dump silicon into to help fund all the development that you need to do. like

00:31:56.720 --> 00:32:04.799
you I don't think it makes sense to build a GPU business that doesn't have a

00:32:01.760 --> 00:32:07.840
consumer arm if you've all like you've

00:32:04.799 --> 00:32:10.559
already done so much of the work for

00:32:07.840 --> 00:32:17.200
Alchemist and Battle Mage to fix the backwards compatibility and to refine

00:32:13.200 --> 00:32:19.919
the architecture. Um, please, please

00:32:17.200 --> 00:32:25.840
just give us a bigger desktop version of, you know, what you're already

00:32:23.120 --> 00:32:31.279
shipping like amazing technology on on like laptop, like

00:32:28.320 --> 00:32:34.880
please don't let it die. >> And if you have to skip Celestial,

00:32:34.399 --> 00:32:41.279
>> fine. >> Don't skip Druid. >> Don't skip Druid.

00:32:38.480 --> 00:32:45.519
We need more options. And gamers, it's like the Windows thing. Like gamers are

00:32:43.440 --> 00:32:49.519
they're mad at Microsoft, they're mad at NVIDIA, but you've got to give them a

00:32:47.919 --> 00:32:54.159
better option or they're just going to begrudgingly stay there forever. And

00:32:51.760 --> 00:32:58.240
like, oh man, like Intel continues to put in the work on the software side.

00:32:56.399 --> 00:33:01.840
You got to give us hardware to run it on.

00:33:00.559 --> 00:33:06.000
Let's go. >> Yeah. >> You know. >> Yep.

00:33:04.399 --> 00:33:12.240
>> Um, thank you for coming to my TED talk.

00:33:10.000 --> 00:33:16.159
Uh Dan, what are we supposed to be doing? >> You can keep doing topics or we can do

00:33:14.880 --> 00:33:20.640
uh the CW announcements. >> Oh, I feel like I should probably talk about the CW announcements. Uh do you

00:33:19.360 --> 00:33:29.760
want to do you want to fire up the site? >> Sure. >> This week, it's a huge week for Creator

00:33:24.720 --> 00:33:30.720
Warehouse. Is Shiptorm still running?

00:33:29.760 --> 00:33:37.039
>> Uh yes, >> looks like it. >> I believe so. So, the Shiptorm sale is

00:33:34.799 --> 00:33:42.960
still running. So, now is an amazing time to pick up uh I mean basically

00:33:40.399 --> 00:33:46.799
anything at LT store. So, we've got buy more, save more on our blank t-shirts.

00:33:44.960 --> 00:33:53.120
Uh we've got deals running on our scribe driver bolt action um pen and pencil as

00:33:50.399 --> 00:33:57.039
well as our long sleeve t-shirts. And then uh hold on, hold on, let me see if

00:33:54.799 --> 00:34:01.039
I can find the details. And we have some super cool new items. So, Shiptorm free

00:33:59.120 --> 00:34:06.399
shipping across Canada on orders over 150 and worldwide on over orders over

00:34:03.519 --> 00:34:11.359
225. And then on the US site, oh no, I wish I had these details ready. I'm so

00:34:08.240 --> 00:34:13.919
sorry you guys.

00:34:11.359 --> 00:34:19.359
And then on the US site, Shiptorm is uh yeah, free US-wide shipping on orders

00:34:16.639 --> 00:34:22.720
over 150. And then uh Floatplane supporter plus. So if you're on float

00:34:20.800 --> 00:34:27.520
plane at the supporter plus tier, it actually goes down to just $100. So it's

00:34:25.200 --> 00:34:35.119
a great time to join Floatplane. Also, we have some new arrivals. Uh so yeah,

00:34:32.720 --> 00:34:40.079
Luke's laptop. We have some new prints for our party shirts.

00:34:37.440 --> 00:34:45.040
>> These are flipping amazing. Want to give us uh want to give us a closeup of that?

00:34:44.159 --> 00:34:50.079
>> Are you serious right now? >> Laptop zoom. This touchpad is a little weird. It's not the site. It's the

00:34:48.399 --> 00:34:54.800
touchpad. Cursors. >> Yeah. >> Some of them are are glasses.

00:34:53.760 --> 00:34:57.760
>> How cute is that? >> My hands. Some of them are pointers. >> Right.

00:34:56.960 --> 00:35:04.320
>> That's fun. >> Yeah. And then we've also got Okay, this

00:35:00.640 --> 00:35:05.440
one's this one's sick. Let's let me just

00:35:04.320 --> 00:35:12.240
There we go. That works. >> There we go. So, this is like a very

00:35:07.920 --> 00:35:15.440
kind of 90s and like ' 90s screen saver

00:35:12.240 --> 00:35:17.200
and computing and also I don't know work

00:35:15.440 --> 00:35:22.079
from home. It's got a whole bunch of different like vibes like work from the

00:35:19.040 --> 00:35:24.960
beach kind of. Yeah, like the palm trees

00:35:22.079 --> 00:35:29.680
and stuff. Just like don't mind me here chilling on my like CRT laptop or

00:35:27.760 --> 00:35:37.359
whatever. And then this one's meant to just be like a very wearable uh lollipop

00:35:33.440 --> 00:35:39.359
lollipop print. Totally not inspired by

00:35:37.359 --> 00:35:46.079
anything else that looks like that. It's lollipops. It's uh it's it's uh it's

00:35:43.359 --> 00:35:53.359
candies. It's umbrellas. It definitely is not a beach ball. 100% not a beach

00:35:49.839 --> 00:35:56.240
ball. Uh we've also got the spinning

00:35:53.359 --> 00:36:01.200
wheel of death pin set. Okay. Well, now we've really gotten rid of any plausible

00:35:59.680 --> 00:36:05.839
deniability that we could have had around where that design inspiration

00:36:03.520 --> 00:36:09.520
came from. So, here's our pin set that is Yeah, definitely not a beach ball,

00:36:07.920 --> 00:36:14.240
except for the one that definitely is a beach ball. So, we've got candy umbrella

00:36:11.440 --> 00:36:18.560
as well as a lollipop in there. Uh, what else do we got? Yo, yeah, so you can get

00:36:16.079 --> 00:36:23.760
yours at LMG.gg/partyshirt and LMG.gg/wheelof

00:36:21.520 --> 00:36:27.359
death. If you're looking for something that's a

00:36:25.680 --> 00:36:32.079
little bit more low-key, we've also got two new polo colors, plus a restock on

00:36:30.320 --> 00:36:36.000
black. So, soft cotton blend with a bit of stretch, so it's comfortable without

00:36:33.440 --> 00:36:39.200
feeling sloppy. Clean, simple look that works whether you dress it up or keep it

00:36:37.359 --> 00:36:43.119
casual. These are just easy to put on pieces that go with pretty much anything

00:36:41.520 --> 00:36:47.599
and that you can wear it pretty much anywhere. And you can shop at

00:36:44.720 --> 00:36:51.119
LMG.gg/polos. We also do this kind of fun thing where

00:36:49.359 --> 00:36:56.640
we have like a little kind of splash of accent color down there. There you go.

00:36:53.760 --> 00:37:01.119
Polo shirts, dress blues, brilliant white and black.

00:36:59.680 --> 00:37:05.520
Look how much happier Plof looks. Come on, Reese. Would it kill you to smile?

00:37:03.760 --> 00:37:10.800
Love that guy. We uh we did an upgrade for him yesterday. Uh we're bringing

00:37:07.680 --> 00:37:13.680
back setup doctor and his setup

00:37:10.800 --> 00:37:19.839
>> needed some doctoring. He he streams, he games, he does like unboxings of fancy

00:37:16.160 --> 00:37:20.720
shoes. He had so many shoes. Uh so we

00:37:19.839 --> 00:37:28.880
helped a little bit with the organization of that. We got him like a new desk setup. Um, and he tufts

00:37:26.000 --> 00:37:33.440
does like carpet tufting. And so we got like a like a much more ergonomic, space

00:37:31.839 --> 00:37:36.880
efficient setup in his little room where he does all of those things.

00:37:35.200 --> 00:37:41.680
>> So that was that was a fun shoot, guys. Don't miss that one. Lots of good vibes.

00:37:39.920 --> 00:37:47.040
>> Also, uh, okay. Yeah, that's pretty much it. So yeah, now's a great time to get

00:37:43.520 --> 00:37:50.880
an order in. Also, I think that a lot of

00:37:47.040 --> 00:37:53.359
people probably missed it, but

00:37:50.880 --> 00:37:58.880
um hold on. Where are they? Yeah, cables. So, we did have a small restock

00:37:56.240 --> 00:38:06.480
hit our US distribution hub today for Truepec cables. Uh okay. Yeah, many of

00:38:03.680 --> 00:38:12.640
the sizes are already out of stock again. The only way that you're going to

00:38:09.440 --> 00:38:14.240
have a shot of getting these guys is to

00:38:12.640 --> 00:38:22.160
make sure that you get the notify me because when

00:38:17.680 --> 00:38:24.160
they hit they're gone. So, uh there's

00:38:22.160 --> 00:38:28.400
nothing I can do about that. It's in priority sequence. You guys got to you

00:38:26.079 --> 00:38:32.880
got to get in there. Um so, yeah, we had an order hit today and then you can

00:38:30.560 --> 00:38:38.560
actually you can actually see in the dashboard where it hits

00:38:35.680 --> 00:38:41.560
here. Check this out. This is hilarious. Uh,

00:38:42.079 --> 00:38:47.920
gee, Luke, can you tell me where the cable restock

00:38:46.400 --> 00:38:51.920
was? >> Yeah. I mean, >> maybe where the maybe where the snake

00:38:50.720 --> 00:38:54.880
ate the deer. >> Yeah. >> Um, yeah. So,

00:38:54.240 --> 00:38:59.359
>> wild. >> Yeah. >> So, make sure you do that.

00:38:58.560 --> 00:39:05.680
>> All right. >> Two coms. >> All right. So, if you're placing an

00:39:02.640 --> 00:39:07.760
order now, it's a perfect time because

00:39:05.680 --> 00:39:11.760
we have what we call checkout messages. We when we stream, we don't want you

00:39:09.839 --> 00:39:16.320
guys to just throw money at us for nothing. We want to work for it. That's

00:39:14.079 --> 00:39:21.280
right, me, Luke, and Dan. We all want to work for it. So,

00:39:19.599 --> 00:39:25.119
instead of having people just send like Twitch bits or super chats or whatever,

00:39:23.520 --> 00:39:30.400
we created what are called checkout messages or coms. All you got to do to

00:39:27.599 --> 00:39:36.480
send one is head on over to ltstore.com, add something like our new flex pants to

00:39:32.800 --> 00:39:38.400
your cart, and go to the checkout. There

00:39:36.480 --> 00:39:41.520
it is. You can choose to have it displayed as a checkout message. You can

00:39:40.000 --> 00:39:45.200
make your name anonymous or you can show your name. You can send a little message

00:39:43.359 --> 00:39:48.640
and then you can choose your color and whether or not you want to opt into

00:39:46.960 --> 00:39:52.160
email communication about your message. This will help us follow things up with

00:39:50.000 --> 00:39:56.079
you if you want. All right. Then you go ahead and place your order and it will

00:39:53.760 --> 00:39:58.480
go to producer Dan. I already waved. I don't know what to do now.

00:39:57.359 --> 00:40:02.160
>> Uh you'll have to come up with something. >> Wave with the other hand. >> Nice.

00:40:01.119 --> 00:40:06.000
>> Solid. >> It looks weird. I'm not used to him doing that.

00:40:04.240 --> 00:40:10.640
>> It hurts. Anyway, it'll go to producer Dan who will reply to your checkout

00:40:08.079 --> 00:40:16.400
message or will pop it up down here or up there or who will curate it for me

00:40:13.280 --> 00:40:18.160
and Luke and often Dan to respond to.

00:40:16.400 --> 00:40:22.960
Dan, do you want to do a couple for us? >> Yeah, sure. Hey, DL. Currently visiting

00:40:20.480 --> 00:40:27.200
Vancouver with my wife and kids. I had no idea it was so beautiful. Kapalino

00:40:25.520 --> 00:40:30.400
Park is awesome. Yeah. >> Do any of you guys go hiking or anything

00:40:29.599 --> 00:40:38.640
like that? >> Not as much as I should.

00:40:33.920 --> 00:40:43.520
Literally, we were like flying over the

00:40:38.640 --> 00:40:46.160
the like outer Vancouver region and I

00:40:43.520 --> 00:40:48.560
was like, Luke, did you have any idea that there were this many hiking trails

00:40:48.079 --> 00:40:53.920
in this area? >> I knew there was a lot, but it looked like a wherever we particularly were at

00:40:51.839 --> 00:40:57.680
the time like Chilowak or whatever it was like >> very likely. It looked like a video game

00:40:56.720 --> 00:41:02.720
map. >> It >> like there was just so many trails.

00:41:01.040 --> 00:41:07.520
>> It was crazy. And they weren't they didn't seem to be like dried river beds.

00:41:04.800 --> 00:41:11.040
Like they seemed to be hiking trails. >> Yeah. Oh yeah.

00:41:08.560 --> 00:41:15.520
>> The entire area was just littered with them. And I was like, "How have I never

00:41:14.000 --> 00:41:20.400
been on any of these?" >> Some of them are pretty great. >> Absolutely ridiculous.

00:41:17.839 --> 00:41:24.160
>> Oh, team is pretty legendary. >> Um, so yeah, we should Have Have you

00:41:22.880 --> 00:41:28.240
ever done the grind? >> No, I've always gone the other way.

00:41:27.119 --> 00:41:31.920
>> Gone the other way? >> Yeah. >> What's the other way? Isn't the grind

00:41:30.960 --> 00:41:35.280
north van? >> Uh yeah. >> Yeah. I've always gone like out.

00:41:34.079 --> 00:41:38.880
>> Oh. Oh, I thought you meant you've always like gone down it. Like you're

00:41:37.440 --> 00:41:42.480
>> I take the I take Yeah, I take the gondola up.

00:41:40.720 --> 00:41:46.240
>> You're literally not even allowed. Like it's >> That would be That would also be the one

00:41:44.720 --> 00:41:50.079
way that would be really bad for my knees. Is to go down.

00:41:48.880 --> 00:41:54.720
>> Okay. Well, if you ever want to do the grind, I'll do the grind. It's called the grouse grind. It's on grouse

00:41:53.280 --> 00:41:59.359
mountain. You can like hike up the mountain. >> It's Yeah,

00:41:56.480 --> 00:42:03.839
>> it's pretty savage. Wait till your knees are of like a workout than what you

00:42:02.400 --> 00:42:06.960
might expect from a traditional hike. >> This is fair. >> It's just like an incredible amount of

00:42:05.920 --> 00:42:12.640
stairs, >> which is awesome. There's people that do it like literally every day.

00:42:10.560 --> 00:42:17.920
>> Like it's it's great. It's just uh it's a quite a bit of a different experience

00:42:14.240 --> 00:42:20.079
from what I've heard. My brother shot up

00:42:17.920 --> 00:42:26.400
there recently. I wan. DLL. First off, San update when

00:42:24.560 --> 00:42:30.800
I'm a storage and backup engineer and that is my daily bread and butter.

00:42:28.480 --> 00:42:35.200
Second, did you consider any centralized backup solution? Also, why no why so few

00:42:34.560 --> 00:42:39.440
tall shirts? >> Now, I can see why you curated this one, Dan. Um,

00:42:38.079 --> 00:42:46.960
>> it's a really good question. >> We are we are expanding slowly our

00:42:42.800 --> 00:42:49.040
selection of tall merchandise. Um, we

00:42:46.960 --> 00:42:53.200
just we have to be we have to go slow and steady. Sure,

00:42:50.800 --> 00:43:00.319
>> this may be a surprise to you, all of you, but physical goods are an extremely

00:42:56.800 --> 00:43:03.599
cash flow sensitive business. Uh they

00:43:00.319 --> 00:43:06.400
every new product requires a brand new

00:43:03.599 --> 00:43:10.319
upfront investment that may or may not pay off. And we just have to be careful.

00:43:08.480 --> 00:43:14.400
We have to go slow. We have to be careful. We don't we're not taking

00:43:12.240 --> 00:43:21.520
private equity. We don't have outside investors. So every time we launch a new

00:43:17.599 --> 00:43:23.200
product, that's the product team working

00:43:21.520 --> 00:43:28.000
with me and working with our other leadership and going, "Okay, here's all

00:43:25.520 --> 00:43:33.119
the chips. These are our chips. Here we are betting them. Let's hope it pays

00:43:30.480 --> 00:43:37.200
off. It doesn't always We've got to be careful. It's It really is that simple

00:43:35.520 --> 00:43:42.560
and also complicated." >> I think I think the new the new war is

00:43:40.000 --> 00:43:45.760
going to have to be over pants. >> Tall pants.

00:43:43.359 --> 00:43:50.640
>> I know. when when not even necessarily tall pants, just when you guys launched

00:43:48.160 --> 00:43:56.480
the flex pants, I was really surprised the inseam length was 29. And then on on

00:43:53.760 --> 00:44:02.000
uh on an internet forum, uh somebody posted like, "Wow, LTT Store really

00:43:58.480 --> 00:44:04.240
makes me feel really tall

00:44:02.000 --> 00:44:09.920
and it was in relation to those pants cuz they're like, "Wait, inseam 29 is is

00:44:06.960 --> 00:44:13.200
all they Yeah. Yeah, >> pants are tough, man. There's

00:44:12.240 --> 00:44:17.520
>> Yeah, >> you have to have all the waist sizes.

00:44:15.760 --> 00:44:22.880
Ideally, you would have all the inseam sizes. We've done as much as two inseam

00:44:19.839 --> 00:44:25.760
sizes for a pair of pants. Um I believe

00:44:22.880 --> 00:44:29.760
the cargo pants, we have two inseams for >> and it it literally double like you got

00:44:28.319 --> 00:44:33.520
to you got to think about it in terms of skew count. You literally double your

00:44:31.680 --> 00:44:37.680
skew count. And if we still had everything consolidated at a single

00:44:35.599 --> 00:44:42.960
distribution center, that would be a little bit easier. But every additional

00:44:40.640 --> 00:44:44.240
layer of complexity you add, it's a multiplier.

00:44:43.920 --> 00:44:49.599
>> Yeah. >> It's not additive, it's multiplicative.

00:44:47.280 --> 00:44:53.200
>> So, was that like I'm just genuinely curious. We've sold

00:44:51.359 --> 00:44:57.440
pants before. So, was that like did we have was most of our orders 29 or like

00:44:55.920 --> 00:45:04.560
how did we land on 29? >> Um, we landed on that as sort of a like

00:45:00.640 --> 00:45:05.200
a best middle ground for most people

00:45:04.560 --> 00:45:09.119
>> really. >> Yeah. H.

00:45:08.319 --> 00:45:15.359
>> Okay. >> Yep. And what we would have probably

00:45:12.720 --> 00:45:18.960
done if we had another skew is we would have gone longer. Yeah. But that was one

00:45:18.319 --> 00:45:25.359
of those ones where >> it's like the tech pants are 30 and 32.

00:45:23.200 --> 00:45:29.240
People also got a kick out of you guys calling tall 32.

00:45:30.960 --> 00:45:36.319
>> There's degrees of tall. >> I'm a 32.

00:45:35.839 --> 00:45:40.560
So >> yeah, >> Dan's tall. >> Dan's pretty tall. >> What What do we call

00:45:39.760 --> 00:45:44.800
>> got stumpy legs? >> Jonathan and Conrad and Lucas and those guys.

00:45:43.280 --> 00:45:48.079
>> I mean Lucas. I mean >> towers. >> Yeah. >> Yeah.

00:45:46.560 --> 00:45:54.800
>> Like uh Okay. SN update. Um I am still not

00:45:51.920 --> 00:46:00.000
convinced that SAN is the right solution for us. I've every time I've asked

00:45:57.599 --> 00:46:06.800
someone who's very pro storage area network uh why we should have one, they

00:46:03.680 --> 00:46:11.359
have not given me a satisfactory answer.

00:46:06.800 --> 00:46:14.880
Um NAS seems like the way to go for us.

00:46:11.359 --> 00:46:18.160
I we don't have the same kind of like

00:46:14.880 --> 00:46:21.599
resiliency and like like crossorg

00:46:18.160 --> 00:46:24.240
access complications that um that you

00:46:21.599 --> 00:46:28.560
might have if you're like uh I I don't know flipping like multinational or if

00:46:26.400 --> 00:46:32.400
you're or if you're like you know you're running a data center that has you know

00:46:30.400 --> 00:46:35.440
CPU compute over here and GPU compute over here so you need to have like a

00:46:33.760 --> 00:46:40.319
storage network that they all access like we don't have any of those use

00:46:37.040 --> 00:46:43.839
cases we just have individual users

00:46:40.319 --> 00:46:46.480
accessing saying file level resources

00:46:43.839 --> 00:46:51.000
that are centrally stored. Can someone explain to me why we need sand?

00:46:52.319 --> 00:46:58.400
>> I think Floatplane has sand. >> Yeah, Floatplane does. But

00:46:56.400 --> 00:47:01.119
>> do we have no seph, right? >> Yeah. Do we have no seph locally? I

00:47:00.319 --> 00:47:06.319
don't think so. >> I don't think there was a reason to.

00:47:04.640 --> 00:47:13.119
>> It was a pitch at one point. >> Yeah. And then >> we didn't go that route.

00:47:09.839 --> 00:47:14.880
Uh it's all redundancy. Yeah, but we

00:47:13.119 --> 00:47:21.200
don't need that much redundancy. We have the one share that is like the current

00:47:18.319 --> 00:47:25.760
projects actually redundant and replicated places share and then

00:47:23.920 --> 00:47:33.119
everything else we made a conscious decision and it's been it you know it

00:47:30.400 --> 00:47:39.040
it's it's funny for me seeing people sort of go oh remember that time they

00:47:35.599 --> 00:47:40.800
lost data? Yes. Yes. Yes. We we've other

00:47:39.040 --> 00:47:45.200
than okay when we lost Wanic that was bad but the time that our vault had some

00:47:43.440 --> 00:47:50.160
data loss we had made a conscious decision that this was non-essential

00:47:47.520 --> 00:47:55.040
archived data and that if we lost it we had decided that it was not worth the

00:47:52.800 --> 00:48:00.640
additional expense of replicating that storage and that's especially true today

00:47:57.599 --> 00:48:03.440
man storage has gotten so expensive and

00:48:00.640 --> 00:48:07.440
so we've made the decision that we only really need the projects we're working

00:48:05.119 --> 00:48:12.160
on and every other like random snippet of footage. If we lost it, we lost it.

00:48:09.359 --> 00:48:17.760
It doesn't really matter. And so going for something more complicated, more

00:48:15.200 --> 00:48:24.200
expensive that requires more administration,

00:48:19.280 --> 00:48:24.200
I I just I don't

00:48:24.400 --> 00:48:29.839
um I don't see the point. Oh, are you are you literally talking to

00:48:28.800 --> 00:48:35.680
AJ in chat right now? >> And Jonathan, they're both in here. We do have Seth on prem. Um it's just in

00:48:33.920 --> 00:48:39.200
the lab and it's just an MVP right now. Sure, >> there's only a few things kind of

00:48:37.440 --> 00:48:44.480
running into it. But the thing is when you take AJ and Jonathan and you throw

00:48:42.319 --> 00:48:49.680
them in the pool of IT people that do stuff for LMG, they come from Seph and

00:48:48.400 --> 00:48:54.800
Kubernetes land. >> Yeah. >> So like it

00:48:52.319 --> 00:48:59.599
why not? It becomes I think a lot more reasonable. It's it's a right tool for

00:48:57.920 --> 00:49:04.000
the right job for the right person type of situation. We have AJ and Jonathan.

00:49:02.240 --> 00:49:09.599
We might as well do this thing. It doesn't necessarily mean that it's a

00:49:06.319 --> 00:49:12.559
recommendation for everybody. Um,

00:49:09.599 --> 00:49:16.800
>> like TCL 987 says, I would think you'd want SAN for running VMs so that a

00:49:15.200 --> 00:49:23.200
storage node going down doesn't take down the VMs too.

00:49:19.760 --> 00:49:26.240
in terms of like like critical on the

00:49:23.200 --> 00:49:28.559
media group side and the creator

00:49:26.240 --> 00:49:35.040
warehouse side which make up the majority of our revenue.

00:49:31.839 --> 00:49:36.640
I can think of like a couple of VMs we

00:49:35.040 --> 00:49:41.680
run like sure on the flow plane side. Yeah.

00:49:39.440 --> 00:49:45.440
Yeah. Sure. You're 100% right. Like you want that redundancy built into that

00:49:43.839 --> 00:49:50.680
storage network that everything else is using. But >> yeah, >> for video editing,

00:49:50.800 --> 00:49:57.280
we don't we don't have nodes of storage.

00:49:54.559 --> 00:50:02.559
We just have a storage server that every periodically

00:49:59.119 --> 00:50:04.160
backs up to another one.

00:50:02.559 --> 00:50:07.839
If flowplane was on prem, you need it. Flow plane has it anyways. I just I just

00:50:06.720 --> 00:50:17.119
said that. >> Yeah. >> Yeah. Um Oh, faint locket asks, can you

00:50:12.640 --> 00:50:19.280
explain what sand is? So basically the

00:50:17.119 --> 00:50:26.240
idea is that instead of having your storage in each machine right like this

00:50:22.960 --> 00:50:27.839
and this and then like allocating uh you

00:50:26.240 --> 00:50:32.720
know like instead of putting like a drive into your computer and going okay

00:50:30.240 --> 00:50:40.079
here virtual machine this is like your drive. uh SAN is an entire

00:50:36.960 --> 00:50:43.200
an entire separate network of machines

00:50:40.079 --> 00:50:45.040
whose entire job is to provide storage

00:50:43.200 --> 00:50:49.680
for all the other machines on the network. >> A big pool.

00:50:46.240 --> 00:50:53.200
>> Yeah. So whether whether their job is to

00:50:49.680 --> 00:50:55.680
run VMs or whether their job is to uh

00:50:53.200 --> 00:51:02.000
serve media or whether their job is for the editors to access it, all of these

00:50:59.040 --> 00:51:07.520
compute resources will just instead of having local storage over the network,

00:51:04.960 --> 00:51:11.839
they will access this this storage network which is entirely separate boxes

00:51:09.599 --> 00:51:17.119
that maybe don't need a ton of compute but do need like a butt ton of storage.

00:51:14.720 --> 00:51:22.079
And then this this storage network is going to be built with redundancies and

00:51:19.359 --> 00:51:26.240
and safeties that make it so that if one of these machines goes down, all the

00:51:24.880 --> 00:51:31.359
other machines that are doing all of your web serving and all of your uh your

00:51:29.359 --> 00:51:35.040
compute or all of your research or whatever it is they're doing are still

00:51:33.200 --> 00:51:40.160
able to access their storage as if nothing happened. So, it's a way of of

00:51:37.200 --> 00:51:46.319
distributing your storage to make it so that a failure will not impact your

00:51:43.599 --> 00:51:53.760
operation at all rather than taking down one of your nodes. But we have so few

00:51:49.200 --> 00:51:56.160
nodes outside of the Floatplane side

00:51:53.760 --> 00:52:00.400
and so little critical critical infrastructure that I just uh I'm just

00:51:58.400 --> 00:52:05.040
not convinced that it is relevant for us. Um,

00:52:03.040 --> 00:52:08.720
yeah, Torpedo Bench describes it as kind of like RAID but at a much bigger scale.

00:52:07.200 --> 00:52:13.040
And and that's kind of a way of thinking about it. Instead of your one machine

00:52:11.119 --> 00:52:18.720
having multiple drives, one of which could fail, all of your machines have

00:52:16.240 --> 00:52:22.480
like a bunch of machines that have a bunch of drives in them and an entire

00:52:20.640 --> 00:52:26.559
machine could fail and then they'd be able to still access it. It's that's

00:52:24.880 --> 00:52:31.599
it's kind of a it's kind of a neat way of thinking about it. And then NAS is

00:52:29.440 --> 00:52:35.599
more like like a it's like a storage area network that only that it's not

00:52:33.200 --> 00:52:40.400
really a network. It's just it's just a a standalone resource that all of those

00:52:38.000 --> 00:52:44.720
things can access over the network that might have some redundancy in the form

00:52:42.079 --> 00:52:49.440
of uh in the form of RAID for instance but it doesn't have like multi-achine

00:52:47.599 --> 00:52:55.640
level redundancy. That's about the kind of simplest way that I can

00:52:52.079 --> 00:52:55.640
summarize it.

00:52:58.079 --> 00:53:02.200
Okay. Yeah. Time to do more topics.

00:53:03.040 --> 00:53:11.520
Uh, no. Legendary ZNAS Nintendo emulator has

00:53:08.720 --> 00:53:18.160
been rewritten from scratch with GPU acceleration. The original developers of

00:53:14.400 --> 00:53:21.599
ZNES or ZSNES or ZSNES, whatever you

00:53:18.160 --> 00:53:23.359
want to call it, ZS Knight and Demo are

00:53:21.599 --> 00:53:30.400
back together for the first time in nearly two decades with Super

00:53:27.040 --> 00:53:32.880
ZNES, a complete groundup rewrite of the

00:53:30.400 --> 00:53:38.800
legendary SNES emulator that dates back to the DOS era and the first N Super

00:53:36.319 --> 00:53:45.040
Nintendo emulator that I ever used. I have personally played through Final

00:53:42.079 --> 00:53:50.880
Fantasy 6 on this emulator, Chrono Trigger on this emulator. Like, man, I

00:53:47.920 --> 00:53:56.480
have very fond memories of using this often times uncooperative but quite

00:53:54.160 --> 00:53:59.040
quite treasured piece of software. >> It was what Yeah, it was what everybody

00:53:58.079 --> 00:54:05.520
used for a long time. >> The last major release was almost 20

00:54:02.400 --> 00:54:07.839
years ago, though. So big change here is

00:54:05.520 --> 00:54:14.240
a GPU powered pu core that enables high-res mode 7, widescreen support in

00:54:11.760 --> 00:54:18.960
supported games, overclocking for games that were notorious for slowdown,

00:54:16.160 --> 00:54:24.720
uncompressed audio, and perame visual enhancements that the devs are calling

00:54:21.119 --> 00:54:27.599
super enhancement engine. It also keeps

00:54:24.720 --> 00:54:31.760
the classic falling snow UI. It's available now on Windows, Mac, Linux,

00:54:29.200 --> 00:54:36.480
and Android with iOS coming soon. And the devs made a point of listing no vibe

00:54:34.400 --> 00:54:43.200
coding as an official feature. Everything was handwritten the classic

00:54:39.119 --> 00:54:46.160
way. Now with that said, I have heard

00:54:43.200 --> 00:54:51.119
that it's a little buggy. It is an early build. Special chips like chips like the

00:54:48.079 --> 00:54:53.760
Super FX are not supported yet, but in a

00:54:51.119 --> 00:54:57.280
world where vibe coding is everywhere. Is no vibe coding a selling point for

00:54:55.920 --> 00:55:02.319
this for you? Would you want to try it? I I want to try it. I'm spoiler. I want to try it.

00:55:00.559 --> 00:55:07.359
Uh, I don't know if like

00:55:05.280 --> 00:55:11.359
no vibe coding is particularly a selling point, but I'm going to try anyways. I

00:55:09.440 --> 00:55:19.359
wanna I wanna I want to hear you talk about that

00:55:14.559 --> 00:55:21.920
>> if stuff is properly like I I know

00:55:19.359 --> 00:55:26.160
people that use vibe coding stuff in a way that I would consider properly and I

00:55:24.079 --> 00:55:34.160
know people that use vibe coding in a way that I would hyperaggressively not

00:55:29.280 --> 00:55:38.160
consider properly. Um, if these two guys

00:55:34.160 --> 00:55:39.599
said that they used AI assisted tools, I

00:55:38.160 --> 00:55:44.800
don't think I'd be too concerned about it. >> Interesting. So, to you, it's more about

00:55:44.240 --> 00:55:51.680
having >> who's wielding the tools, >> having the skills and having the street

00:55:48.160 --> 00:55:55.359
cred to take shortcuts

00:55:51.680 --> 00:55:56.720
>> and know to like review it and make sure

00:55:55.359 --> 00:56:02.640
that bad stuff doesn't get through still. Um because it also it also

00:55:59.680 --> 00:56:06.960
depends like did they say no? Okay, so no vibe coding specifically. So okay

00:56:05.119 --> 00:56:09.920
maybe yeah maybe that is particularly a good thing but like

00:56:08.880 --> 00:56:15.200
>> AI assisted. >> So here's the quote the quote no vibe

00:56:12.079 --> 00:56:16.480
coding classic development style but

00:56:15.200 --> 00:56:21.119
that's pretty ambiguous. >> Yeah that's classic. >> Well to them 20 years ago might be just

00:56:20.480 --> 00:56:27.599
no assistance. >> No no I don't think it's that they haven't been doing work. They just haven't been working on zness.

00:56:24.480 --> 00:56:29.920
>> No. Yeah that's fair. Um, but yeah, I

00:56:27.599 --> 00:56:33.359
mean, a AI assisted coding has been a thing for a super long time. Yeah, Peter

00:56:31.839 --> 00:56:36.799
said this and I I mean, I've said this on W show like a billion times and I

00:56:35.200 --> 00:56:41.920
just still agree with it. The buck stops with the one who commits the code

00:56:39.680 --> 00:56:48.240
100%. It goes back to that IBM thing that I've also shown on W show before.

00:56:43.839 --> 00:56:50.640
Um, quote, "A computer cannot be held

00:56:48.240 --> 00:56:56.880
responsible." Um, let's find the slide

00:56:53.920 --> 00:57:00.720
here. A computer cannot be held accountable.

00:56:59.040 --> 00:57:05.839
Therefore, a computer must never make a management decision. And a management

00:57:02.160 --> 00:57:08.400
decision is to commit code. So like uh

00:57:05.839 --> 00:57:14.480
from the vibe that I get from this team, these two people, um yeah, I mean I

00:57:12.240 --> 00:57:19.760
wouldn't particularly be too concerned about it. Um, but there there will be

00:57:17.599 --> 00:57:23.839
people that will vibe code something and they'll tell me that excitedly and I

00:57:21.839 --> 00:57:29.040
know who it is and I know how much work in development they've done and I'll be

00:57:25.359 --> 00:57:32.000
like, "Oh boy, I'm excited to see how

00:57:29.040 --> 00:57:37.200
many different ways this breaks." Um, I wonder how many security keys are like

00:57:34.079 --> 00:57:38.240
hardcoded and publicly readable.

00:57:37.200 --> 00:57:42.319
Like things like that. >> Now you have to call me out like that.

00:57:40.720 --> 00:57:45.839
>> No, that that never happened. >> Oh, no. No. um security key for your

00:57:45.119 --> 00:57:50.720
Google sheet. >> Yeah. Um >> speaking of the Lionus Vibe coding

00:57:49.040 --> 00:57:54.319
challenge, the project is officially dead, unfortunately. Yeah.

00:57:52.240 --> 00:57:59.599
>> In the form of a video, >> but I'm still trying to uh I'm still

00:57:57.440 --> 00:58:04.640
trying to turn it into at least if it can be if it can be cobbled together

00:58:02.000 --> 00:58:10.720
relatively easily a Floatplane video or something. So, the problem is not that I

00:58:07.920 --> 00:58:16.960
was not able to vibe code a solution. I was and it's actually been in production

00:58:14.079 --> 00:58:20.720
since I vibe coded it which is like six months ago now or something which is the

00:58:19.599 --> 00:58:28.240
problem. >> By the time we would be releasing this video

00:58:24.079 --> 00:58:31.200
>> everything that I did is so far removed

00:58:28.240 --> 00:58:35.359
from the current state of AI and vibe coding that it just doesn't make any

00:58:33.200 --> 00:58:39.440
sense to talk about the entire thing like yeah

00:58:36.559 --> 00:58:42.880
>> which I could probably do. In fact, I could probably do way faster with better

00:58:41.119 --> 00:58:48.799
tools and now that I've done it. But the entire premise of the video for me was

00:58:46.000 --> 00:58:54.079
as someone who's never done this, what does that look like? And we would no

00:58:51.760 --> 00:58:58.640
longer be answering that question. The other thing that it wasn't killed

00:58:55.599 --> 00:59:00.799
because of is our real developer. Our

00:58:58.640 --> 00:59:07.520
real developer was able to create a solution, but because of scheduling and

00:59:04.880 --> 00:59:12.880
stuff and people being busy, I still haven't seen it.

00:59:10.960 --> 00:59:20.400
So, what I was hoping that we could still do is

00:59:15.440 --> 00:59:25.040
have um like have me sit down and like

00:59:20.400 --> 00:59:27.040
have it shown to me and then

00:59:25.040 --> 00:59:30.000
>> like Yeah, Dan could just kind of walk me through it and then we just do that

00:59:28.880 --> 00:59:33.680
on camera. Sure. >> And then we can do that as And then I

00:59:32.079 --> 00:59:38.000
could do like a short little summary. >> He already walked me through it on camera.

00:59:35.680 --> 00:59:40.160
>> Okay, perfect. And then we and then we can just throw that up on flow plane or

00:59:39.520 --> 00:59:45.599
something like that. >> Yeah. >> Um >> another another Sorry, are you done?

00:59:43.440 --> 00:59:48.720
>> No, I just And then I probably I probably need a little bit more of his

00:59:46.880 --> 00:59:51.680
time though >> cuz I need it to work for mixed doubles

00:59:50.480 --> 00:59:54.880
and singles as well. >> Ult ultimately I mean you you you pay

00:59:54.079 --> 00:59:59.280
his check. So >> Well, I know. But but then why did we

00:59:58.079 --> 01:00:03.040
have to do this whole vibe coding? So the vibe coding challenge started because I needed some development

01:00:01.839 --> 01:00:06.319
resources for something that didn't really matter. Um, but then then it

01:00:05.119 --> 01:00:11.760
mattered because it was a video, but then now it's not a video. I feel like it would have been better for us to just

01:00:09.760 --> 01:00:15.680
say, "Hey, can I have some of Dan Seagull's time?" It's it's easier now

01:00:14.079 --> 01:00:23.760
and more appropriate now, I think. So, if you want service time, it makes sense. Um, I wanted to say one more

01:00:18.799 --> 01:00:26.400
thing on the super zed schnes thing. Um,

01:00:23.760 --> 01:00:30.880
>> I think there's also a like >> is what can I classify this as a crywolf

01:00:28.960 --> 01:00:35.680
problem? I don't know. I watched a a short clip last night before completely

01:00:32.720 --> 01:00:40.960
tearing down my entire computer setup um of Shroud going back to Counterstrike

01:00:39.119 --> 01:00:44.640
because I was interested because what I've heard is that Counter-Strike is

01:00:43.119 --> 01:00:49.200
covered in cheaters >> and the title didn't say anything about cheaters. It just said Trout goes back

01:00:47.920 --> 01:00:54.880
to Counter-Strike in the first time or whatever. So, I watched it in the first two games he was in, there was two

01:00:51.839 --> 01:00:57.359
blatant cheaters. Um and it's it's it's

01:00:54.880 --> 01:01:02.400
this thing where like modern, especially FPS games, but modern every game. Uh,

01:01:00.960 --> 01:01:06.480
basically, don't kid yourself. There's people that cheat in like Rocket League

01:01:04.559 --> 01:01:10.960
and MMOs and and everything you can imagine. Um, with with cheaters freaking

01:01:09.440 --> 01:01:14.920
everywhere. Something that has ruined

01:01:14.960 --> 01:01:21.599
something that has ruined. That's a

01:01:18.079 --> 01:01:24.559
weird sentence. Whatever. Um, is

01:01:21.599 --> 01:01:28.160
defeat >> because it it often feels like

01:01:26.960 --> 01:01:33.280
>> there's a built-in excuse for everything. Yes. So, if you don't think

01:01:31.680 --> 01:01:37.040
that people are cheating or if it's they're probably not, then it's like, oh

01:01:35.359 --> 01:01:38.960
man, that guy's really good. I want to watch this replay and try to learn from

01:01:38.480 --> 01:01:44.480
them, >> right? >> But if it's like, I don't know, there's usually at least one cheater per lobby.

01:01:43.200 --> 01:01:50.160
Then it's like, nah, that guy's just cheating. Screw that guy. And it like it

01:01:46.960 --> 01:01:52.319
it loses a lot of the like

01:01:50.160 --> 01:01:56.880
the interesting nature of losing, if that makes sense. >> Yeah. Do you how do you how do you get

01:01:54.480 --> 01:01:59.920
motivation from loss if the

01:01:58.319 --> 01:02:02.400
>> how do you get if the competition was never fair? >> How do you get like a rival?

01:02:02.160 --> 01:02:06.720
>> Yeah. >> Like you know back back when there was dedicated servers and you jump on a

01:02:05.280 --> 01:02:11.680
server and there was always that freaking guy who just >> Yeah. who'd get you like every time.

01:02:09.680 --> 01:02:14.880
>> Yeah. And then and then you you train and you get better and you beat that guy

01:02:13.280 --> 01:02:18.079
and then it feels good. Like that that type of stuff is just kind of gone from

01:02:16.640 --> 01:02:24.240
cheating. And I think something that they're dodging here to bring it back to

01:02:20.319 --> 01:02:26.400
superness, super zness, um, is they're

01:02:24.240 --> 01:02:31.359
saying no vibe coding. So if it comes out and it has a bug,

01:02:29.119 --> 01:02:34.880
you don't get to go, "Nah, it's probably just modern AI junk spaghetti code,

01:02:34.640 --> 01:02:39.520
right?" >> Cuz they're saying no. >> No. If there's a bug, it's because we

01:02:39.200 --> 01:02:44.640
think >> we haven't fixed that yet. >> That part I think is kind of cool. >> I think that's super cool.

01:02:42.880 --> 01:02:51.359
>> Yeah. >> Yeah. Yeah. >> Want to pick a topic? Sure.

01:02:48.880 --> 01:02:55.520
Uh, what do we got here? Sony finally responds to PlayStation DRM. Panic says,

01:02:53.599 --> 01:02:59.040
"Only a one-time license check is needed. No 30-day requirement. This was

01:02:57.839 --> 01:03:03.440
confusing if you weren't on top of this news cuz you're a PC person. There was a

01:03:01.280 --> 01:03:07.760
mysterious 30-day license timer showing up on PlayStation digital games

01:03:05.280 --> 01:03:11.760
purchased after March 2026's firmware update." So, people were freaking out.

01:03:09.359 --> 01:03:16.400
What is this 30-day thing? modders on Twitter spotted it first, but things

01:03:13.440 --> 01:03:21.760
spiraled when PlayStation's own AI support chat bots told users that they'd

01:03:18.640 --> 01:03:24.240
lose access every 30 days unless they

01:03:21.760 --> 01:03:28.720
were online, which is just not true, to be clear. That's just what the chatbot

01:03:26.079 --> 01:03:31.440
said. With nobody sure what was real, players started just testing stuff,

01:03:30.240 --> 01:03:36.960
trying to see what was going on. YouTuber Spawnwave pulled his PS5 CMOS

01:03:34.480 --> 01:03:41.200
battery to simulate a timer expiring and watched his brand new digital purchases

01:03:38.799 --> 01:03:44.640
just refuse to load with a license error. >> Nice.

01:03:42.079 --> 01:03:48.400
>> What actually happens if you miss the window is that the game stops working

01:03:46.799 --> 01:03:51.520
until you connect back to the internet. It doesn't delete it or get revoked

01:03:50.079 --> 01:03:55.920
permanently or anything like that. Once you're back online, access is restored

01:03:53.680 --> 01:03:59.839
and I believe once it does that actual check-in, you do get a permanent token.

01:03:58.240 --> 01:04:04.079
Sony says that if you launch the game once while connected, a one-time check

01:04:02.000 --> 01:04:07.119
kicks in and the 30-day timer won't apply at all ever again. It's fine.

01:04:06.559 --> 01:04:13.520
>> Okay. >> But, >> oh, testing from Reset Era user and

01:04:10.559 --> 01:04:18.480
Shrew found it's not quite that simple. There appears to be around a 15-day

01:04:16.319 --> 01:04:23.599
delay before the console actually converts your temporary license into a

01:04:20.799 --> 01:04:27.760
permanent one, a permanent offline one. Until that conversion happens, going

01:04:25.359 --> 01:04:33.760
offline for 30 days will lock you out. That 15-day window lines up suspiciously

01:04:31.039 --> 01:04:37.599
close to PlayStation's 14-day refund period, suggesting

01:04:35.920 --> 01:04:43.839
that this might have been an anti-fraud measure because apparently some people

01:04:39.839 --> 01:04:46.000
were buying games, going offline, having

01:04:43.839 --> 01:04:50.960
their offline version, refunding the game, >> right?

01:04:48.799 --> 01:04:55.680
>> Yeah. Uh Sony hasn't confirmed that part, but apparently that has been

01:04:52.400 --> 01:04:57.039
happening. So, yeah, makes sense. Uh,

01:04:55.680 --> 01:05:00.960
Sony has now officially responded to GameSpot saying a one-time check is

01:04:59.359 --> 01:05:06.720
required to confirm the game's license, after which no further check-ins are required. The DRM is real, but it's not

01:05:04.960 --> 01:05:11.359
the always online nightmare that people feared. That said, Sony rolled this out

01:05:09.280 --> 01:05:15.599
silently and let the panic build for a freaking week before saying a single

01:05:13.680 --> 01:05:18.640
thing. as a company.

01:05:17.520 --> 01:05:23.039
>> God, it's kind of annoying. >> That sometimes

01:05:21.280 --> 01:05:28.000
is has things

01:05:25.440 --> 01:05:34.799
fester in the community. I understand it both ways.

01:05:31.839 --> 01:05:40.160
I can understand why it seems crazy that Sony didn't say anything for a week. And

01:05:37.520 --> 01:05:46.960
then I can equally understand all the like mechanisms and checks that

01:05:44.079 --> 01:05:51.359
external comms need to go through especially in the midst of a crisis and

01:05:49.200 --> 01:05:58.200
why it can take a while. >> I I'm I'm going to firmly stand on both

01:05:55.200 --> 01:05:58.200
sides.

01:05:58.720 --> 01:06:06.760
Going wide. Yes.

01:06:02.960 --> 01:06:06.760
Strong firm stance.

01:06:07.280 --> 01:06:14.400
H I don't love this. I understand their

01:06:11.920 --> 01:06:19.039
whole trying to dodge the fraud thing. >> Honestly, it seems better than Steam.

01:06:16.559 --> 01:06:21.920
And we we hold Steam up on this like this pillar,

01:06:20.960 --> 01:06:27.359
this this pedestal. >> It's better. How is it better than Steam? >> Steam checks like all the time.

01:06:25.520 --> 01:06:30.079
>> Yeah, but if you go offline >> Yeah. then it works, which is fine.

01:06:28.960 --> 01:06:33.599
>> Playing single player games. >> Yeah. Not always. They'll they'll make

01:06:32.160 --> 01:06:36.640
you check once in a while. >> Oh, >> yeah. I guess I've never been offline

01:06:35.440 --> 01:06:40.400
long enough to notice. >> As someone who uh actually it seems like

01:06:39.039 --> 01:06:44.720
it's been a little better lately, but there was definitely a period where they

01:06:42.240 --> 01:06:46.480
had cracked down on it quite a bit and uh we would really run into it like on

01:06:46.160 --> 01:06:53.359
set. >> Can you just run the executables out of the folder? >> No, no, cuz it'll still launch Steam and

01:06:50.799 --> 01:06:56.720
it'll still do a DRM check. So, so we'd run into this on set when we only had

01:06:55.039 --> 01:07:00.400
like one copy of a game and we'd try to like pull the Ethernet cord and then launch it on the next computer and then

01:06:59.200 --> 01:07:08.000
pull the Ethernet cord and then launch it on the next one and pull the Ethernet cord. So, obviously this is like not a,

01:07:04.559 --> 01:07:11.599
you know, classic use case, but I have

01:07:08.000 --> 01:07:14.319
definitely run up against this. Um,

01:07:11.599 --> 01:07:17.599
>> I I haven't steam I haven't done this often, but I have not ran into it

01:07:16.240 --> 01:07:20.559
opening Steam when you try to just run the executable for the game. I've had it

01:07:19.280 --> 01:07:25.280
just launch the game. >> Okay, people in chat are saying they definitely do. Does it depend on the

01:07:23.839 --> 01:07:31.680
game? Cuz from my understanding, >> I definitely see it depending on the game. Not like GG where part of the deal

01:07:29.359 --> 01:07:36.079
is that there's no online DRM. Like with Steam there there's online DRM. It's

01:07:34.240 --> 01:07:38.880
like a feature, not a button. >> I bet you it depends on the game. It

01:07:37.440 --> 01:07:41.760
depends on whether the game uses Steam Works, which is Steam's DRM. That also

01:07:41.039 --> 01:07:46.480
makes sense. >> Uh Couscous Captain says, "Can you keep your Steam Deck in offline mode for just

01:07:45.200 --> 01:07:51.680
a limited amount of time?" Yeah, from my understanding, it'll eventually need to phone home, but I correct me if I'm

01:07:50.400 --> 01:07:55.920
wrong. Like I said, this is something that I ran into more before and lately

01:07:54.640 --> 01:08:04.400
when we've been doing the Ethernet unplug thing, now that I'm thinking about it, it's been a little more

01:07:59.599 --> 01:08:06.720
successful. Um, TCL 987 says Steamworks

01:08:04.400 --> 01:08:09.359
and Steam DRM are independent. Um, blah blah blah. A lot of games use Steam

01:08:07.920 --> 01:08:14.240
library stuff for networking, voice chat, etc. Yeah, so it's probably going

01:08:11.119 --> 01:08:17.440
to be dependent on the game somewhat.

01:08:14.240 --> 01:08:20.319
Um, man, one thing that I find really

01:08:17.440 --> 01:08:23.759
annoying as somebody who has to set up a system for travel probably more often

01:08:22.480 --> 01:08:29.440
than most people because when I'm traveling is often when I'll have time to like, oh yeah, I'm going to try out

01:08:27.440 --> 01:08:34.960
the Steam controller, so I need like to load a bunch of games onto a system

01:08:31.120 --> 01:08:38.239
before I go. I really really wish there

01:08:34.960 --> 01:08:40.960
was a way to with one button like do the

01:08:38.239 --> 01:08:47.759
pre-launch crap for every game on my system because if I'm like if I have no

01:08:44.719 --> 01:08:50.319
internet or I'm or I'm somewhere remote

01:08:47.759 --> 01:08:53.279
with very slow internet or whatever >> like okay like installing stuff not

01:08:52.080 --> 01:08:57.679
shaders you mean >> no like get thenet whatever get the

01:08:56.159 --> 01:09:06.000
redistributable whatever >> install all dependencies >> do your DRM check like did install all

01:09:02.719 --> 01:09:07.920
dependencies cuz like it's it's

01:09:06.000 --> 01:09:12.719
become more and more of an annoyance over time how many Steam games have

01:09:10.719 --> 01:09:18.400
other launchers or have random dependencies especially on Linux uh

01:09:15.679 --> 01:09:23.040
which I've been using more lately uh where they'll have to grab like Proton

01:09:20.080 --> 01:09:29.600
crap ahead of time. Uh, so if I So if installing the game installed the game

01:09:27.120 --> 01:09:34.000
so that I just click go and it goes, I would actually I would love that. So if

01:09:31.199 --> 01:09:38.880
Valve is taking suggestions right now, uh, that's something that I'd love to

01:09:35.440 --> 01:09:40.799
see Steam level up on ever so slightly.

01:09:38.880 --> 01:09:47.359
When I install a game, do all of it. Assume that my intention when I install

01:09:43.040 --> 01:09:49.679
a game is to play the game. Um, not just

01:09:47.359 --> 01:09:54.759
not just enjoy it being in my readytoplay filter. Um,

01:09:55.520 --> 01:10:01.440
okay. Uh, Igny

01:09:58.880 --> 01:10:03.840
says, "As a game dev, requiring Steam is a toggle in the SDK API."

01:10:03.199 --> 01:10:09.120
>> Yeah. Okay. >> Game either confirms Steam is open and connected on Steamworks initialization

01:10:07.199 --> 01:10:12.000
or it doesn't. So, that explains why >> we just tried to open different games.

01:10:10.480 --> 01:10:16.080
>> We both would have had completely different experiences because both are

01:10:14.239 --> 01:10:19.840
both are true. That makes sense. >> Um,

01:10:18.000 --> 01:10:26.159
>> it's not like a thing I do all the time, so I wasn't super confident in it.

01:10:23.840 --> 01:10:31.040
>> Okay, you want to we Oh, we should probably uh do some show sponsors. The

01:10:28.239 --> 01:10:35.840
show is brought to you today by Vessie. Earlier this week, we did a fun

01:10:33.760 --> 01:10:39.920
breakdown of Valve's Steam Controller, but today we need to stop talk about

01:10:37.760 --> 01:10:45.840
something that's even more important. A rain and moisture controller.

01:10:43.199 --> 01:10:51.280
That's right. Grown at the joke all you want, Luke. Oh, but Vessie makes shoes

01:10:48.880 --> 01:10:56.320
that they claim are 100% waterproof, meaning you can take back control of

01:10:53.760 --> 01:11:00.000
your dry socks. This is thanks to Vessie's Diamondex material, which also

01:10:58.560 --> 01:11:04.400
makes the shoes lightweight and easy to pack on trips. Their weekend Neo shoes

01:11:02.800 --> 01:11:10.480
are a great choice for the spring, and their simple design means they pair great with most wardrobes. So regardless

01:11:08.640 --> 01:11:14.000
of whether it's just a commute to work or if you find yourself caught in some

01:11:12.080 --> 01:11:18.239
spring rain out in the city, Vessie has your back and your feet. Every pair

01:11:16.640 --> 01:11:21.760
comes with free shipping, hassle-free returns, as well as a full year

01:11:19.760 --> 01:11:27.199
warranty. So don't be like meat boy here.

01:11:24.080 --> 01:11:29.760
Stay dry, comfortable, and stylish. Get

01:11:27.199 --> 01:11:33.120
15% off your weekend Neo or Stormbburst at bessie.com/show.

01:11:31.440 --> 01:11:37.520
This is just me playing Super Meat Boy in the Steam Controller video. I don't

01:11:36.080 --> 01:11:42.960
know what that has to do with Bessie's, but sure. >> I mean, he like splooshes when he lands,

01:11:40.800 --> 01:11:47.840
>> I guess. The show is also brought to you by ODO. How many different applications

01:11:46.159 --> 01:11:53.120
and platforms do you and your team have to switch between in order to get a

01:11:49.760 --> 01:11:55.360
project over the line?

01:11:53.120 --> 01:11:58.560
Yeah. With our sponsor ODU, you can manage multiple aspects of your business

01:11:56.800 --> 01:12:02.239
all in one platform without needing to pay for a dozen different subscriptions.

01:12:00.560 --> 01:12:08.080
If you need to run a help desk to assist with solving tickets submitted by customers, ODU's platform can sync with

01:12:05.520 --> 01:12:11.280
things like WhatsApp, email, and live chats. Or if your business team needs

01:12:10.000 --> 01:12:16.719
help tracking leads and keeping organized on potential sales opportunities, ODO's CRM tool is there

01:12:15.280 --> 01:12:20.960
for them. They can even provide essential tools to an accounting team

01:12:18.320 --> 01:12:24.719
like budgeting and payment tracking. And something that's really cool about ODO

01:12:22.880 --> 01:12:30.560
is that if you need to use a single app within their suite, it's free. So, use

01:12:28.080 --> 01:12:34.960
our link below to get a 15-day free trial or to book a demo with a member of

01:12:32.640 --> 01:12:38.640
their team to learn how ODU can help your business.

01:12:36.960 --> 01:12:42.080
>> Lionus, we have a guest. >> We have a guest

01:12:40.480 --> 01:12:44.880
>> for the Floatplane announcements. >> For the Floatplane, you just don't

01:12:43.520 --> 01:12:48.880
trust us to do it right. >> Yeah. >> Okay. Well, come on.

01:12:48.000 --> 01:12:53.520
>> Announcement first. The announcement first. >> Do the announcements first. What What's

01:12:52.080 --> 01:12:57.440
happening right now? >> You want us to do the read, >> Dan? Point at him. Show how he's being

01:12:56.480 --> 01:13:01.040
weird. >> Wait, what? Wait, what? >> He's like holding a monitor.

01:13:00.239 --> 01:13:05.280
>> Look at that guy. >> What's up with that? >> Look at that guy. >> I don't understand what's happening

01:13:03.760 --> 01:13:10.080
right now. If you read the document, you'll know >> he's up to something. >> All right, I'm going to read the

01:13:07.440 --> 01:13:15.000
document. I'm reading the document. >> You know what the L in line stands for?

01:13:16.000 --> 01:13:23.040
>> Oh, there's a lot of flow plane exclusives about me this week. In the

01:13:20.400 --> 01:13:28.159
first video, Sammy gave me such a wonderful welcome back gift to welcome

01:13:25.840 --> 01:13:31.040
me back to the office. He will be fired for this injunction. Okay. So, first of

01:13:29.840 --> 01:13:33.760
all, Sammy, that's not really what injunction means. >> Is it not? >> No.

01:13:33.280 --> 01:13:37.600
>> Oh. >> Um, >> it's about >> And second of all, you're not fired

01:13:36.800 --> 01:13:43.840
>> allegedly. >> Um, okay. Anyway, this is the video. Uh,

01:13:41.679 --> 01:13:50.640
people really loved this video on Floatplane. I came back to work and my entire

01:13:46.800 --> 01:13:53.520
office had been gift wrapped. Um, to

01:13:50.640 --> 01:13:56.520
this day, this is still how I feel about it.

01:13:57.120 --> 01:14:03.920
Anywh who, um, and if PC building is more your

01:14:01.679 --> 01:14:09.600
style, I went head-to-head against Elijah, Jordan, and Pancratz to see who

01:14:06.400 --> 01:14:10.480
can build a PC the fastest at Lionus

01:14:09.600 --> 01:14:17.600
Media Group. Wow. >> Did any of you wear a horse head? >> Dude, you filmed that ages ago. That

01:14:15.760 --> 01:14:21.600
video is just coming out. It took forever to edit. >> We should do Yeah, we should do a video

01:14:19.520 --> 01:14:25.280
on who's the fastest to edit a video at Linus Media Group cuz I think I think

01:14:23.920 --> 01:14:29.840
you would not be in good shape. >> 4 hours and eight POVs I had to edit and

01:14:28.480 --> 01:14:34.320
then I got I have to do other stuff. >> What kind of videos you editing with the POVs? Sick,

01:14:33.440 --> 01:14:39.040
>> huh? >> You disgust me. Get your mind out of the

01:14:36.560 --> 01:14:43.440
gutter. Uh anyway, so that exclusive went up very recently. Oh yeah, you guys

01:14:41.760 --> 01:14:46.320
are you guys are loving this one, too. >> Just upload that today. Okay, I'm not

01:14:44.960 --> 01:14:51.520
going to scroll down to the comments because I feel like it's going to be

01:14:48.880 --> 01:14:55.120
somewhat debatable who won. So, it's probably going to come down to

01:14:52.800 --> 01:14:59.840
commenters to decide who uh who did it best. Uh what else is going on on Float

01:14:57.440 --> 01:15:04.000
Plane? Uh to wrap it up, we've uploaded the full interview with the creator of

01:15:01.440 --> 01:15:06.719
Pop OS, Carl Michelle. That's pretty cool. Techquicki has been doing a ton of

01:15:05.679 --> 01:15:10.800
interviews with interesting people lately. So, if you want to hear more from our special guests, we'll be

01:15:09.120 --> 01:15:17.280
uploading them to Flowplane. Very cool. Check out the sea of exclusives at LMG.gg/fp1. GG/FPWAN.

01:15:14.560 --> 01:15:22.960
And don't forget guys that now is a better time than ever to subscribe to

01:15:20.000 --> 01:15:27.280
Floatplane because at the supporter plus tier, you'll be getting a lower

01:15:24.640 --> 01:15:31.280
threshold for shiptorm free shipping. Now Sammy has a special show and tell

01:15:30.560 --> 01:15:35.920
for us. >> What do you want, Sammy? >> You can't get mad at me, Linus.

01:15:35.040 --> 01:15:42.239
>> Hold on. >> You're telling me I can't I can't get mad at you. Uh

01:15:39.679 --> 01:15:45.120
>> can I stand here? You can stand anywhere you want. >> Don't touch the foils.

01:15:44.000 --> 01:15:48.719
>> So, you know, you know, >> you don't have a mic here, though. Did we

01:15:47.199 --> 01:15:50.960
>> Is it Is this No, this this was last minute. I forgot you're not here next to me. That's why.

01:15:50.640 --> 01:15:57.920
>> Okay. >> So, you know, you know the uh the the chair you bought with uh David?

01:15:54.960 --> 01:16:00.719
>> Um Oh, you mean the gun chair? >> Uh yeah, hold on.

01:15:59.920 --> 01:16:06.000
>> Yes, >> I'll bring I'll bring this up so people >> commissioned machine gun chair.

01:16:04.080 --> 01:16:11.280
>> Yes, that one. So, I >> So, here this was uh this was

01:16:07.440 --> 01:16:13.120
yesterday's video. Uh, it has actually

01:16:11.280 --> 01:16:16.920
one of my favorite intros that we've done in quite a while.

01:16:16.960 --> 01:16:23.120
Uh, okay. That that wasn't it.

01:16:21.120 --> 01:16:29.280
>> What are you watching? What are you >> There we go. No, no, we're good. We're

01:16:24.960 --> 01:16:32.880
good. But this is a gaming chair. Um, so

01:16:29.280 --> 01:16:35.760
you can Yeah. So, we had

01:16:32.880 --> 01:16:38.080
>> I love David Crawling. So, >> but uh anyway, sorry.

01:16:36.719 --> 01:16:41.440
>> Solid effort, David. I'm not trying to take too much time today, but um so I

01:16:40.000 --> 01:16:46.880
promised I would daily drive that thing for 30 days. >> I did not approve that.

01:16:44.480 --> 01:16:51.360
>> Uh the ergonomics are like not safe in my opinion. >> Is this a good monitor, do you think?

01:16:49.600 --> 01:16:54.480
>> Yeah. >> Do you like it?

01:16:54.080 --> 01:17:00.719
>> Yes. >> Do you like that monitor? >> Um so, uh the the lumbar I agree is bad.

01:16:59.360 --> 01:17:05.000
So I was trying to adjust it. >> Yeah. >> Did you know that thing has no limiters?

01:17:06.640 --> 01:17:13.199
It blew. >> Sammy, >> you can see my hand here. When I visit

01:17:11.199 --> 01:17:16.000
tried to physically try to stop it, it did not stop. There's no limiter on that

01:17:15.360 --> 01:17:25.920
chair. >> Yes, I know. >> I didn't know that. So then it broke.

01:17:22.480 --> 01:17:29.360
>> I'm sorry. I'm sorry. I felt so bad. I'm

01:17:25.920 --> 01:17:31.440
so sorry. I'm so sorry.

01:17:29.360 --> 01:17:34.880
>> Uh yeah, but I recorded for Flow Plane. Uh, so you'll see my reaction on there

01:17:32.880 --> 01:17:38.560
where you see my my the horror in my face as I try to save this monitor.

01:17:37.679 --> 01:17:44.400
>> Oh my god, >> it's mangled. >> That's deep.

01:17:42.239 --> 01:17:48.480
>> You don't like the uh the the keyboard like plate? It went through it.

01:17:46.400 --> 01:17:51.840
>> Did it occur to you to stop it not with your hand like by pressing the button?

01:17:50.159 --> 01:17:55.600
>> So the button wasn't responsive. >> It wasn't responsive. >> No, the one remote doesn't like work.

01:17:54.880 --> 01:18:01.040
>> Yeah, I didn't know. >> You have to use the other. >> Did you think to watch the video before?

01:17:59.440 --> 01:18:05.760
>> I watched like I watched mostly through. was like, "I know enough." And then >> I didn't know the I didn't know this.

01:18:04.400 --> 01:18:10.080
>> You are the problem. >> I know I'm the problem. I I

01:18:08.719 --> 01:18:13.760
>> Okay, Lance would have just read the comments. >> I'm sorry.

01:18:11.920 --> 01:18:18.320
>> Yeah. And through reading the comments, I would have known all the critical

01:18:15.520 --> 01:18:22.640
information that he didn't have. You're I will die on this hill. You are better

01:18:20.239 --> 01:18:28.239
off reading all the comments on a video than like watching the first 30% of it.

01:18:25.040 --> 01:18:29.760
>> I watched 50%. I, you know, I still

01:18:28.239 --> 01:18:31.920
maintain you're better off reading the comments on a video than watching only

01:18:31.280 --> 01:18:37.360
half of it. >> But I I am sorry. Um, but I have my

01:18:35.360 --> 01:18:39.199
reaction on it on Full Play next week, >> so we're getting some content.

01:18:38.640 --> 01:18:43.199
>> Okay. All right. >> You know that crazy expensive computer you built for him?

01:18:41.760 --> 01:18:45.760
>> I feel like you have to take the value of this monitor out of that computer

01:18:45.040 --> 01:18:49.920
somehow. >> They took away my GPU already. >> Oh, >> really?

01:18:48.800 --> 01:18:53.920
>> I I stood up for you. >> I know you did. I appreciate it. >> You saw me stand up for you. I said they

01:18:52.719 --> 01:18:56.000
shouldn't take it away. You know why they took it? Your department. Oh, get

01:18:55.840 --> 01:19:00.480
owned. >> Yeah, now beak with you. Yeah, let's get one. >> Get owned. Yeah,

01:18:59.199 --> 01:19:05.760
>> I don't think the two of us could take it with this broken monitor. I just

01:19:04.320 --> 01:19:08.960
might. It's very durable. >> All right. Thank you, Sammy.

01:19:07.360 --> 01:19:12.719
>> I'm very sorry. I'm very sorry. I feel so bad. I'm sorry.

01:19:10.719 --> 01:19:15.199
>> Oh, man. That's a really nice monitor. >> I know. I'm sorry. I'm

01:19:13.920 --> 01:19:21.120
>> What's the What's the model? That's not the 4K one, is it? >> It's like 800 Canadian.

01:19:18.719 --> 01:19:25.280
>> I'm sorry. I did It wasn't intentional. I'm sorry. I'm sorry. I feel so bad.

01:19:23.040 --> 01:19:28.560
>> What monitor is it? Uh, it's a it's an Alienware something.

01:19:26.960 --> 01:19:30.480
>> You know that you're the one holding it who can see the model number, right?

01:19:30.000 --> 01:19:35.520
That's >> going to have to. >> Yeah, it's always on there.

01:19:34.400 --> 01:19:39.920
>> He's going to drop it. >> See, >> I mean, that's fine at this point.

01:19:37.920 --> 01:19:42.640
>> Sammy's one of those guys that we make a video with him and then half the

01:19:41.199 --> 01:19:46.640
comments are like, "Why does this guy even work there?" >> I promise. He's really good at other

01:19:46.159 --> 01:19:54.640
things. >> Wait, where's the model? He >> He is. Oh, Alienware 2725Q

01:19:52.159 --> 01:20:00.239
October 2025. >> I think that's the 1440p. I'm sorry. I'm

01:19:57.760 --> 01:20:06.080
so sorry. Wait, how much does it cost? It's It's 500 US, right?

01:20:03.760 --> 01:20:09.040
>> OH MY GOD. NO. WAIT. NO. WAIT. OH MY GOD.

01:20:07.600 --> 01:20:13.600
That's the first one I saw. >> This is a 240 Hz 4K. Yeah. This is like

01:20:11.920 --> 01:20:17.679
top of the line. >> Holy crap.

01:20:15.040 --> 01:20:20.320
>> Studled. like one of the best monitors on the market.

01:20:18.560 --> 01:20:24.560
>> Wow. >> I'm sorry. I'm so sorry.

01:20:22.400 --> 01:20:28.640
>> I honestly had no idea when you showed me. I thought it was just like some

01:20:25.840 --> 01:20:31.600
random junk monitor. I had no idea. >> I had no idea.

01:20:29.520 --> 01:20:36.800
>> No, we got like really nice monitors and we had that like sick Alienware that

01:20:34.480 --> 01:20:39.600
like sick Alienware gaming PC on it. It was like

01:20:37.679 --> 01:20:43.840
>> that was like peak gaming other than the lumbar support and the headrest.

01:20:41.840 --> 01:20:47.600
>> But aren't you glad I'm okay? I didn't get hurt. Actually, yes. That would have

01:20:46.960 --> 01:20:54.800
been worse. >> Did you get blood on the monitor? >> I got my hand on it. See, see this this

01:20:50.880 --> 01:20:56.800
this this hand sign shows war. I went

01:20:54.800 --> 01:20:59.360
>> war shows that you were like banging in the depths of a steam ship.

01:20:58.719 --> 01:21:03.199
>> Yeah. I was like, >> that's another possibility. >> That's not the kind of banging I meant,

01:21:02.560 --> 01:21:07.600
but sure. >> Yeah. >> What do you mean? >> He's never seen Titanic. This is the

01:21:06.239 --> 01:21:10.400
problem with the kids today. >> I watched Never mind. Sorry. Anyways, I

01:21:09.360 --> 01:21:16.880
don't take too much time, but >> All right. Thanks, Sammy. >> Sorry. hasn't seen Titanic.

01:21:14.560 --> 01:21:20.320
Hasn't seen POV. >> Who is this guy?

01:21:18.560 --> 01:21:24.040
>> That's That's more expensive than any monitor I've ever owned.

01:21:24.719 --> 01:21:31.600
Just a random random fun fact. >> That might be worth more than every

01:21:28.560 --> 01:21:33.440
multimonitor setup you've ever owned.

01:21:31.600 --> 01:21:36.080
1300 CAD >> probably. And I run three pretty good

01:21:35.520 --> 01:21:42.960
monitors. >> Yeah. >> Yeah. No, I think it is actually. >> I think so.

01:21:38.800 --> 01:21:44.880
>> That's uh Wow. I would I like I I

01:21:42.960 --> 01:21:48.400
honestly had no idea. He showed me in the lab and I was like, "Okay." I mean,

01:21:46.560 --> 01:21:51.600
losing a monitor like sucks because we just always need monitors, but I'm sure

01:21:49.840 --> 01:21:54.719
it's just like some random generic monitor. I had no idea it was an

01:21:53.199 --> 01:21:59.679
Alienware. I had no idea it was high-end at all.

01:21:56.880 --> 01:22:04.239
>> No, it's the highest of end. >> It's It's like full Downward Dog

01:22:02.560 --> 01:22:07.760
Highend. >> Is Downward Dog the one where your butts

01:22:05.679 --> 01:22:10.080
in the air? >> I It sounds like it.

01:22:09.120 --> 01:22:13.280
>> Yeah. >> Yes. Yeah. >> No,

01:22:12.400 --> 01:22:18.520
>> I was thinking of child. >> It doesn't It doesn't get much more high-end than that.

01:22:21.120 --> 01:22:28.639
>> All right. Well, subscribe to Floatplane so Sammy can

01:22:26.639 --> 01:22:31.360
>> continue to do the things he does. No, he does really good stuff, too. I

01:22:30.320 --> 01:22:36.080
promise. >> Dude, that's that's a lot. >> All right, let's pick Let's move on.

01:22:34.639 --> 01:22:40.159
Let's pick another topic. Hey, really cool LTT Labs article this week. Yeah,

01:22:38.719 --> 01:22:44.400
let's talk about that instead. >> We know it can be daunting to take your

01:22:42.320 --> 01:22:50.159
first steps into the world of Linux. We know this because we've been doing it

01:22:46.000 --> 01:22:53.440
recently, but LTT Labs is here for you.

01:22:50.159 --> 01:22:57.440
This article uh from Nick tested by Sean

01:22:53.440 --> 01:23:01.679
and Steven is we tried popular Linux

01:22:57.440 --> 01:23:03.760
gaming distros. It's I have not read

01:23:01.679 --> 01:23:06.960
this one yet cuz it just went up, but I'm very excited to. This went up like

01:23:05.840 --> 01:23:12.400
two days ago. can maybe summarize for us. >> We we had some well yeah it's I mean

01:23:10.000 --> 01:23:18.320
we're kind of benchmarking a bunch of gaming dros and there's there's tests if

01:23:15.360 --> 01:23:22.000
you go down um there's there's standard you know Labs charts with different

01:23:19.920 --> 01:23:27.040
games and how the different dros did and as you might expect they're pretty

01:23:24.400 --> 01:23:32.400
similar cuz it kind of goes that way every time but we still looked at stuff.

01:23:30.080 --> 01:23:38.239
Cashy did pretty good. Let's go Cashy. Uh >> hey look at that. Look at that. I

01:23:35.040 --> 01:23:40.000
managed to pick the one the one that's

01:23:38.239 --> 01:23:42.639
bad specifically for Doom the Dark Ages. The

01:23:41.600 --> 01:23:46.159
other games it was uh >> if we if we do another Linux I switch

01:23:44.719 --> 01:23:51.120
challenge in the future, you should just have to use whatever I pick.

01:23:49.199 --> 01:23:58.719
>> No, that's less interesting. No, >> I I like I I think it's really important

01:23:55.840 --> 01:24:01.120
to have the conversation around what information a normie is likely to be

01:24:00.719 --> 01:24:08.800
exposed. >> No, that's true. That's true. That to me is a whether I end up making the right

01:24:05.760 --> 01:24:12.800
choice or the wrong choice is is

01:24:08.800 --> 01:24:15.920
actually a fundamentally important part

01:24:12.800 --> 01:24:19.199
of the Linux challenge. And I

01:24:15.920 --> 01:24:21.120
intentionally will not just ask people.

01:24:19.199 --> 01:24:24.480
>> I could have we even said this in the first episode. I could literally call

01:24:22.960 --> 01:24:28.000
Linus Torvoltz. Yeah. >> Literally have his digits and ask him

01:24:26.480 --> 01:24:32.080
what district he used. But I'm not doing that. The one the only thing that really

01:24:30.719 --> 01:24:36.880
surprised me and this would have led you to a dro that I didn't even recommend,

01:24:34.239 --> 01:24:40.639
but I had a gut feeling that you were going to go with what he said he used.

01:24:39.760 --> 01:24:43.600
>> Oh, yeah. Yeah. >> In the video you guys did together. That's what I thought you were going to

01:24:43.280 --> 01:24:50.719
do. >> Nope. No. So, my my part of my method is

01:24:47.760 --> 01:24:54.800
that I am I'm I'm looking at the entire switching experience

01:24:52.639 --> 01:24:59.840
>> and part of the switching experience is going out there and fact finding. And

01:24:57.600 --> 01:25:08.080
so, you know, when the community kind of comes and goes like he did the factf

01:25:03.600 --> 01:25:09.600
finding wrong because he found the wrong

01:25:08.080 --> 01:25:13.360
conclusion. What we need to do is we need to look at

01:25:11.520 --> 01:25:16.800
okay, what are all these resources and why are they recommending this thing if

01:25:14.960 --> 01:25:23.360
quote unquote everyone knows that it's like not good? And honestly, we've

01:25:20.159 --> 01:25:24.320
already seen some positive change

01:25:23.360 --> 01:25:32.239
>> every time. Yeah. >> Already. Yeah. And so it's one of those things where maybe I just accept my role

01:25:29.120 --> 01:25:35.360
as the bearer of bad news and the

01:25:32.239 --> 01:25:37.760
reality check for people who are so

01:25:35.360 --> 01:25:41.520
knowledgeable that they don't realize what they don't what they know I guess

01:25:40.239 --> 01:25:47.440
is probably the best way that I could describe it. It's like a curse of knowledge thing to a lot of Linux

01:25:44.719 --> 01:25:53.679
community members. They don't realize how easy it is to make the wrong choice

01:25:50.639 --> 01:25:56.080
because to them it's so obvious. They

01:25:53.679 --> 01:26:00.239
have they know the right people to ask. They know the right resources to look

01:25:57.760 --> 01:26:05.440
at. But to someone who to whom it's not obvious, who's coming into it for the

01:26:02.159 --> 01:26:06.560
first time, it's very easy to end up on

01:26:05.440 --> 01:26:11.280
a different path. >> And and honestly, I do find this pretty

01:26:09.199 --> 01:26:14.719
interesting because I I didn't initially use chat. I've used chat GPD to try to

01:26:13.280 --> 01:26:19.280
figure out things that are going on with my system, but I didn't use it to pick

01:26:16.560 --> 01:26:24.159
my dro at all. But you did and it spat out pop OS and then I did to see if mine

01:26:22.000 --> 01:26:26.159
would as well. And I don't it was one of the options. I don't remember if it was

01:26:25.280 --> 01:26:32.000
number one, but it was one of the options. >> I don't think it was number one, >> but it was there. >> I thought number one was Cashy for you.

01:26:30.480 --> 01:26:35.920
>> I don't remember. >> I thought it was like open susi or

01:26:33.520 --> 01:26:38.960
something. >> I'm sorry. I don't remember.

01:26:36.880 --> 01:26:42.000
>> It was a while ago. Um but this time I just did this sitting here right now,

01:26:40.239 --> 01:26:48.480
not logged in. So it's not tailored on me. And best overall experience, Pop OS.

01:26:45.920 --> 01:26:52.560
So like we can say we can say whatever we want, but a ton of people will use

01:26:52.159 --> 01:26:58.560
this. >> Yes. Yeah. >> And people can be like upset about that,

01:26:56.320 --> 01:27:04.239
right? You can be upset about that. You can think they shouldn't use it. But and

01:27:01.760 --> 01:27:10.080
I said this I said this in episode one. If I am trying to be representative of

01:27:06.960 --> 01:27:13.760
Joe Gamer, who's doing my own research

01:27:10.080 --> 01:27:16.239
today and I didn't ask a chatbot, I'd be

01:27:13.760 --> 01:27:22.320
doing a complete disservice. That would be a completely unrealistic assumption

01:27:20.239 --> 01:27:27.199
that they would not use a chatbot because so many people are using them.

01:27:24.719 --> 01:27:31.600
And we know this. This is just a fact that we don't have to like, but we do

01:27:29.600 --> 01:27:36.080
have to deal with. We've got to deal with the fact that when Luke typed in

01:27:33.840 --> 01:27:43.199
what Linux dro should I use and then closed his tab right as I was about to

01:27:38.080 --> 01:27:43.760
switch back to his screen it out pop OS.

01:27:43.199 --> 01:27:48.560
>> Yeah. >> And you know what's funny is um >> I know bar and a couple other things but

01:27:46.880 --> 01:27:51.040
it said best overall was Pop OS. >> I never actually switched off of Pop Os

01:27:50.000 --> 01:27:55.120
on my desktop. >> I don't know if I ever actually acknowledged that on Wancho.

01:27:53.679 --> 01:28:00.800
>> I don't I don't feel like I realized that. I I kept it because I I did the

01:27:58.320 --> 01:28:06.639
vast majority of my Linuxing on my other machines which were not running pop OS.

01:28:03.199 --> 01:28:08.800
I was running Steam OS on uh on the

01:28:06.639 --> 01:28:13.040
media PC and then I was running Kubuntu on my laptop which I actually ended up

01:28:10.639 --> 01:28:16.400
mostly really happy with. There were some issues, you know, we'll talk about

01:28:14.719 --> 01:28:19.280
those. But uh yeah, I didn't actually end up

01:28:17.840 --> 01:28:22.960
using my desktop that much. And for the limited amount that I did use it, Pop

01:28:21.199 --> 01:28:29.080
West not only was usable, but it actually got better over the entire

01:28:25.600 --> 01:28:29.080
course of the challenge.

01:28:31.520 --> 01:28:36.159
Someone in chat said, "I asked the LLM search and Ubuntu and Mint was number

01:28:35.199 --> 01:28:40.000
one." I was like, "Oh, that's an interesting idea. I should just ask

01:28:38.239 --> 01:28:47.120
search," which I never do. >> Yeah, >> but I should just do that. And it's the

01:28:43.600 --> 01:28:49.520
exact same output. Um,

01:28:47.120 --> 01:28:54.000
no bar project. I am specifying I'm switching to Linux from Windows

01:28:51.600 --> 01:28:57.520
>> and that's where a lot so so a big part of why it recommended Pop OS for me was

01:28:56.000 --> 01:29:05.760
that I laid out what my requirements were. >> Yeah, >> I want and and a huge part of the of the

01:29:01.520 --> 01:29:07.360
residual sort of branding for Pop OS is

01:29:05.760 --> 01:29:12.560
that it's really good for people with NVIDIA GPUs who want a turnkey gaming

01:29:10.880 --> 01:29:17.440
experience and are coming from Windows. That's like that's the identity

01:29:15.199 --> 01:29:22.880
>> of Pop OS. And also that it's not just for gaming. Like that was

01:29:20.719 --> 01:29:26.719
that's that's the kind of like branding in a nutshell for Pop OS.

01:29:24.400 --> 01:29:29.600
>> I think I think first of all I think a lot of people

01:29:27.920 --> 01:29:34.000
have labeled me as like the Linux guy here, which I think is just not

01:29:31.280 --> 01:29:36.800
>> it's not true. But you're definitely um you definitely had more familiarity

01:29:35.760 --> 01:29:42.639
going into it than either of you. >> Oh, no. just trying to qualify my next statement as like I probably don't know

01:29:41.040 --> 01:29:47.360
as much about this as some of you seem to think that I do. Um but in my

01:29:45.679 --> 01:29:53.600
experience the whole >> better NVIDIA driver native stuff is

01:29:51.120 --> 01:29:56.480
like eh >> yeah no I know

01:29:54.800 --> 01:30:02.080
>> that hasn't been a thing for me in like a long time. I think that's uh I think

01:29:58.960 --> 01:30:04.159
that's an old and it's it's everywhere.

01:30:02.080 --> 01:30:07.040
So, like it was talked about a lot in the past, but I think we're kind of past

01:30:05.760 --> 01:30:13.520
that problem. >> Um, at least in in like everything I've

01:30:09.840 --> 01:30:15.520
used. Like Mint is much more casual and

01:30:13.520 --> 01:30:21.280
has no problem with NVIDIA drivers. Mint for me can switch between Intel and and

01:30:18.320 --> 01:30:24.800
NVIDIA graphics for like performance or battery saving setups and stuff and just

01:30:22.800 --> 01:30:30.560
has no problem with it. Like I I don't think that's a modern problem. Um, just

01:30:28.639 --> 01:30:34.239
as a note for anyone watching, I wouldn't get too scared about the NVIDIA

01:30:32.320 --> 01:30:38.159
on Linux thing, it's it's really not as big of a deal as it was before.

01:30:35.600 --> 01:30:42.159
>> Tim 000x3 says, "Okay, here's my counterpoint, Lionus." Joe Gamer is

01:30:40.080 --> 01:30:45.199
actually going to also watch LT. So, they're going to say Lionus has a lot of

01:30:43.920 --> 01:30:49.440
problems with Pop OS and probably not use Pop OS now. Are you taking that into

01:30:47.280 --> 01:30:53.280
account? Well, I can't at the time. there's a bit of a like temporal issue

01:30:51.199 --> 01:30:57.520
with your argument because at the time that I selected Pop OS, I have not yet

01:30:55.120 --> 01:31:00.800
made a video finding out that Pop OS was problematic for me now.

01:30:59.199 --> 01:31:06.480
>> So, it's Yeah. So, >> and also the chat GPT user base versus

01:31:03.840 --> 01:31:11.280
Linus TechTips viewers. >> So, the chat GPT user base is this big

01:31:09.199 --> 01:31:15.040
and the Linus Tech Tips user B viewer base is this big. Yeah,

01:31:12.880 --> 01:31:20.239
>> like we I've talked about this a fair bit, but I

01:31:17.280 --> 01:31:27.360
think our regular viewers, especially our WAN Show viewers,

01:31:23.920 --> 01:31:29.520
overestimate the importance of us

01:31:27.360 --> 01:31:32.719
>> and I'm flattered. You know, I appreciate that.

01:31:30.960 --> 01:31:37.600
>> If if people that I game with figure out what I do, the most common question I

01:31:34.560 --> 01:31:40.080
get is, "What pre-build should I buy

01:31:37.600 --> 01:31:42.480
because I'm not into this stuff?" >> Yeah.

01:31:42.159 --> 01:31:48.719
Y >> it was astonishing to me. I think much less so you, but it was astonishing to

01:31:46.639 --> 01:31:52.880
me to figure out how massive the pre-built market was. I thought some of

01:31:51.120 --> 01:31:57.679
these companies were just kind of small. They've existed forever. Some people

01:31:54.719 --> 01:32:04.159
build computers, whatever. No, they're big. They're very big. They're huge. I

01:32:00.880 --> 01:32:06.080
didn't realize how much like sway system

01:32:04.159 --> 01:32:10.080
integrators had as well because they're so massive.

01:32:07.520 --> 01:32:13.920
>> I had really no clue. And because of how important they are, not even necessarily

01:32:12.080 --> 01:32:19.199
>> their computers cuz I'm dumb. even from a sales perspective, but from a

01:32:16.880 --> 01:32:26.480
marketing perspective, like when people are shopping for a for a gaming system,

01:32:23.600 --> 01:32:31.840
having your brand in everyone's configurator is in some ways like way

01:32:29.280 --> 01:32:36.080
more powerful than any reviewer that you could ever seed product to because

01:32:33.760 --> 01:32:40.080
that's where people with a very high purchase intent are going to be seeing

01:32:38.400 --> 01:32:45.520
your brand and are going to be exposed to your product. And it's it's funny

01:32:42.320 --> 01:32:48.480
because I um I in a lot of for a lot of

01:32:45.520 --> 01:32:53.040
my career I sort of took for granted my experience as a product manager and

01:32:50.800 --> 01:32:57.280
working in sales and marketing as just like well yeah but like everyone knows

01:32:55.280 --> 01:33:02.320
that the enthusiast side of things is just this like you know tiny little cute

01:32:59.679 --> 01:33:07.120
niche. Um and and and understands that there's actually a much larger machine

01:33:04.000 --> 01:33:09.040
here that doesn't really care about us.

01:33:07.120 --> 01:33:14.560
But then the longer I've been actually that

01:33:12.159 --> 01:33:21.920
perspective was really important in trying to frame products in a way that

01:33:18.639 --> 01:33:24.480
because I'm one of you because I am an

01:33:21.920 --> 01:33:29.280
enthusiast I I can see the things that are important to us but also share the

01:33:27.679 --> 01:33:34.639
perspective that

01:33:31.440 --> 01:33:35.280
guides product decisions that we don't

01:33:34.639 --> 01:33:43.040
like. >> Yeah. And that is that 99 out of the 100

01:33:39.760 --> 01:33:46.719
people that are purchasing it are not us

01:33:43.040 --> 01:33:48.320
and don't care. Like, okay, here here's

01:33:46.719 --> 01:33:52.480
something that I know is a bug bear for you. Boring modern graphics card

01:33:51.679 --> 01:34:00.320
packaging. >> Yeah, >> but look at it from NVIDIA's

01:33:56.719 --> 01:34:01.679
perspective. Okay. GPU box. Here we go.

01:34:00.320 --> 01:34:04.560
>> Dude, they were so cool. >> Oh my god. Packages.

01:34:03.440 --> 01:34:11.600
>> So boring. >> Okay. Look at that boring box. >> So, this is what they used to look like.

01:34:08.960 --> 01:34:14.320
>> That's so sick. >> So much better, dude.

01:34:12.800 --> 01:34:19.280
>> Here's what they look like. >> Here's what they look like now.

01:34:16.239 --> 01:34:22.400
>> So, NVIDIA mandates that you have to

01:34:19.280 --> 01:34:23.840
have, you know, this and on the side,

01:34:22.400 --> 01:34:29.360
uh, let me see if I can find a shot from the side. Uh, you've got to have, so

01:34:27.040 --> 01:34:31.760
you've got to have certain elements. >> I know, I know. Relax.

01:34:30.719 --> 01:34:36.960
>> Overclocked. >> Okay, here you go. So, you've got to have this on the side so that no matter

01:34:34.560 --> 01:34:42.080
how it's faced on the shelf, everyone can see the GeForce and the model number

01:34:40.639 --> 01:34:46.239
and you know, whatever. And you know what? In fairness to NVIDIA,

01:34:43.679 --> 01:34:50.719
>> I'm not that against that. >> This was pretty hard to read. You know

01:34:49.040 --> 01:34:53.440
about this, right? This is like a It's like a table book. Did you Did you order

01:34:52.719 --> 01:34:59.520
it? >> No. >> Um >> Oh, remember this thing?

01:34:56.800 --> 01:35:04.320
>> Oh, yeah. No, I didn't. I should. >> Yeah. Did did Did that ever uh

01:35:02.320 --> 01:35:09.760
noteworthy find from the Did Did that ever like come to life? Publishers

01:35:06.480 --> 01:35:13.920
website for stock alerts. Overclocked an

01:35:09.760 --> 01:35:16.800
archive of graphics card box art. Can we

01:35:13.920 --> 01:35:19.120
Let's go. All right. Uh this is your birthday present.

01:35:17.600 --> 01:35:23.679
>> Sick. Thank you. >> All right. Um,

01:35:21.840 --> 01:35:29.199
yeah, I I think having some amount of standard labeling so that you can tell

01:35:26.320 --> 01:35:35.040
what thing you're buying is fine, but then beyond that, I would like it if it

01:35:31.600 --> 01:35:37.440
was if NVIDIA would screw off.

01:35:35.040 --> 01:35:40.960
Um, and just let people do fun stuff outside of like, you know, have your we

01:35:39.520 --> 01:35:44.080
we talk about it with thumbnails where there's like the the safety zones or

01:35:43.280 --> 01:35:49.760
whatever >> where like, okay, this is this isn't going to conflict with YouTube putting a

01:35:47.360 --> 01:35:53.920
timestamp or or or a hover over or something like that. Have those areas

01:35:51.840 --> 01:35:58.320
just be where NVIDIA has their mandatory branding. Cool. No problem. And then

01:35:56.159 --> 01:36:02.560
beyond that, have some fun with it. It's a graphics card. It's supposed to do fun

01:36:00.480 --> 01:36:06.560
things. >> Somehow we ended up here. We were

01:36:04.320 --> 01:36:11.760
talking about this article on the Labs website. Check it out at ltlabs.com.

01:36:09.440 --> 01:36:15.760
Um, it's just up here in the in the feed right here. Before you ask, yes, we do

01:36:14.239 --> 01:36:19.120
have an RSS feed >> so that you can make sure that you see

01:36:17.280 --> 01:36:22.960
all these all these really all these really cool articles that are actually

01:36:20.719 --> 01:36:24.960
coming out on a very regular basis these days. >> Yeah.

01:36:23.760 --> 01:36:32.000
>> Go check it out. >> Yeah. >> All right, let's pick another topic.

01:36:29.440 --> 01:36:38.400
Oh, this is cool. Uh, here. Do you want to bring up the visuals for uh wave

01:36:34.320 --> 01:36:41.840
overhangs is a new open-source slicer

01:36:38.400 --> 01:36:46.080
forked from Orca Slicer that can print,

01:36:41.840 --> 01:36:50.960
and this is wild, fully horizontal 90°

01:36:46.080 --> 01:36:52.639
overhangs without support material.

01:36:50.960 --> 01:36:57.040
That's what I looked like. >> That's confusing.

01:36:54.639 --> 01:36:59.119
I'm I don't I'm not a big 3D printer omega brain, but this that's confusing

01:36:58.880 --> 01:37:04.320
to me. >> Okay, you've got the visuals up now. >> I think so. Okay. So, here, let's throw

01:37:02.400 --> 01:37:09.920
a Okay, this is cool. Yeah. Can you like zoom zoom zoom? Yeah, there we go. So,

01:37:06.960 --> 01:37:15.040
instead of laying plastic into thin air and then just hoping for the best. Okay.

01:37:12.880 --> 01:37:20.560
It generates concentric rings of material that each grab onto the cooled

01:37:18.400 --> 01:37:24.719
ring that was laid down before them in the same layer, propagating outward from

01:37:22.880 --> 01:37:29.920
the supporting from the supported edge like a wave. So, we're looking at the

01:37:27.440 --> 01:37:38.719
one on the right over there. So you can see that it it kind of it kind of goes

01:37:34.960 --> 01:37:42.080
a little farther a little farther each

01:37:38.719 --> 01:37:44.159
time in order to in order for that

01:37:42.080 --> 01:37:49.679
overhang to have something to grab onto. >> Yeah. Yeah. Yeah. >> This concept isn't brand new. Arc

01:37:47.280 --> 01:37:53.760
overhangs first appeared back in 2022 as a proof of concept that using

01:37:51.679 --> 01:37:58.000
overlapping circular tool paths could achieve the same basic idea. The

01:37:56.000 --> 01:38:01.360
difference is arc overhangs were never integrated into a real slicer and

01:37:59.679 --> 01:38:04.400
required manually extracting coordinates, running a separate script,

01:38:02.800 --> 01:38:09.760
and then pasting the G-code back into your sliced model. >> Wave paths do look a lot more simple.

01:38:07.040 --> 01:38:13.119
>> Not exactly the kind of thing that most people are going to want to bother with.

01:38:11.520 --> 01:38:16.960
Wave overhangs then is the first time the technique has been built directly

01:38:14.560 --> 01:38:20.880
into a usable slicer with a gooey toggle with tunable settings and two different

01:38:18.880 --> 01:38:25.840
algorithms to choose from. It is still very experimental. There are around 20

01:38:23.520 --> 01:38:30.080
tunable parameters and no presets yet. And warping on larger spans is a known

01:38:28.000 --> 01:38:34.480
limitation. Uh, but the developers are asking users to be part of its

01:38:32.159 --> 01:38:38.800
development and upload test prints to a community gallery at waveoverhangs.com

01:38:37.040 --> 01:38:45.360
to help figure out what settings work best across different printers and

01:38:41.679 --> 01:38:47.679
materials. Um, so be be part of the

01:38:45.360 --> 01:38:53.360
change you want to see in the world. Let's have a look at um some stuff from

01:38:49.760 --> 01:38:54.320
the gallery. Like Oh. Oh, how cool is

01:38:53.360 --> 01:39:00.920
that? >> Wow. >> Right.

01:38:57.360 --> 01:39:00.920
>> That's pretty sweet.

01:39:00.960 --> 01:39:06.239
Oh, I like it. Less supports should mean less wasted

01:39:05.360 --> 01:39:13.360
plastic. >> More warping observed. >> It's always >> Hold on a second. No, wait a second. Oh,

01:39:10.239 --> 01:39:16.800
wait. What am I looking at here?

01:39:13.360 --> 01:39:18.400
This looks like a uh No, forget this

01:39:16.800 --> 01:39:24.400
one. Hold on. Hold on. Let's find what? Yeah. Here we go. Here we go. Here we go.

01:39:22.000 --> 01:39:30.960
Okay. That isn't that is an that's an overhang and a half. That's wild.

01:39:28.400 --> 01:39:39.320
Being able to print that. Like, yeah, not perfect, but like that's crazy.

01:39:35.199 --> 01:39:39.320
There's the print bed right there.

01:39:43.440 --> 01:39:53.280
Man, dang. 3D printing you crazy.

01:39:49.679 --> 01:39:56.000
>> Look at this. Best print so far on this

01:39:53.280 --> 01:39:58.960
very challenging test print. Pattern zigzag.

01:39:58.239 --> 01:40:04.880
>> Wow. >> There's definitely some warping. >> Oh, yeah.

01:40:02.639 --> 01:40:09.440
But like this is how this is how these things get to the point where it's like

01:40:07.199 --> 01:40:13.600
>> click and forget. Am I wrong that this would even just be a good idea to do

01:40:11.600 --> 01:40:16.560
even if you did have some supports to help stop the warping? Because wouldn't

01:40:15.040 --> 01:40:19.840
it be stronger once you remove the supports as well? >> Or am I just totally tripping?

01:40:19.360 --> 01:40:24.400
>> Possibly. >> Cuz what I'm seeing in the in the demo imagery,

01:40:23.119 --> 01:40:27.679
>> the the thing that was most interesting to me, I'm going to jump over to mine. >> Look at that.

01:40:26.639 --> 01:40:31.040
>> Oh, wait. We can look at that for a second. >> Look at that. Look at this, Luke.

01:40:30.159 --> 01:40:35.600
>> Look at this. >> That is cool. >> No supports, Luke. >> That's pretty wild.

01:40:33.760 --> 01:40:39.040
>> That's crazy. This is the base, guys, for context. This is what was stuck to

01:40:37.360 --> 01:40:43.600
the base of the print bed. Yeah. So, this gives us a look at what it looks

01:40:41.199 --> 01:40:49.520
like from the bottom. Like, >> so what I'm seeing here is like in these

01:40:46.320 --> 01:40:51.840
example images, the detached lines here,

01:40:49.520 --> 01:40:56.639
>> just removing those and making it so that you're you're like

01:40:54.960 --> 01:41:02.400
uh your your path is all the way from back here. So, you have all the strength from back here on these like uh these

01:41:00.960 --> 01:41:06.960
parts here, which seem like they might be more breakable. I don't know. I'm not

01:41:04.080 --> 01:41:11.679
3D printer brain guy, but it seems like potentially using wave paths in

01:41:09.119 --> 01:41:17.280
combination with supports if you can't afford to have any deformation uh could

01:41:15.119 --> 01:41:20.560
be a cool option for strength. I don't know.

01:41:18.719 --> 01:41:25.040
>> Uh James Unknown says, "I've been 3D printing for years now, my own business

01:41:22.239 --> 01:41:28.320
now, and this is huge. Not just saving material, but also what Luke is saying,

01:41:26.639 --> 01:41:32.000
I can see that being way stronger." >> Cool. Okay, sweet.

01:41:30.080 --> 01:41:35.600
>> Very I mean, that that seems awesome to me because you might even end up with a

01:41:33.600 --> 01:41:40.719
combination of both. You might not need as much support if it's not going to be

01:41:38.560 --> 01:41:44.400
as much of a as big of a problem. So, you can save some material and it can be

01:41:42.320 --> 01:41:50.480
stronger. Like, what a win. All right, I got a funny one. Qualcomm's stock surges

01:41:48.560 --> 01:41:57.679
in response to a report that it could make chips for an open AI smartphone

01:41:54.719 --> 01:42:02.719
and then it lost much of those gains on subsequent trading days. According to a

01:42:00.719 --> 01:42:06.639
report from well-known tech analyst uh Mingchi Quo, OpenAI is working on its

01:42:05.199 --> 01:42:11.199
own smartphone in an effort to compete with the iPhone with mass production

01:42:08.400 --> 01:42:14.159
targeted for 2028. Quo Yeah, we'll get to it. We'll get to it. Just a sec. Just

01:42:12.400 --> 01:42:18.000
a sec. Hold on. Hold on. Relax. Relax. Kuo says that OpenAI has partnered with

01:42:16.320 --> 01:42:21.760
chipmakers Qualcomm and MediaTek to develop the smartphone's processors with

01:42:19.920 --> 01:42:26.800
Lux Share handling system co-design and manufacturing. The phone will reportedly

01:42:23.760 --> 01:42:29.600
have no apps and be a completely agentic

01:42:26.800 --> 01:42:33.679
workflow, whatever that means. This is another in a handful of hardware. So,

01:42:31.600 --> 01:42:37.920
hold on, hold on, contain yourself. This is another in a handful of hardware

01:42:36.159 --> 01:42:42.320
products that OpenAI has announced but not yet released, including earbuds and

01:42:40.400 --> 01:42:48.199
that HomePod style smart speaker that Johnny IV is reportedly working on.

01:42:44.800 --> 01:42:48.199
Okay, go.

01:42:52.159 --> 01:42:59.520
First of all, just flatline used no

01:42:55.440 --> 01:43:01.679
brain power had a thought sounds

01:42:59.520 --> 01:43:08.320
terrible. I would never want to buy this. Oh my god. Okay, diving a little

01:43:05.760 --> 01:43:14.639
bit more into things. It uses no apps. Dang, that sucks a lot.

01:43:12.080 --> 01:43:20.880
So much of what I'm going to need to do is using apps on my phone. Uh hopefully

01:43:18.480 --> 01:43:23.760
I'm not just like, you know, that old guy that gets clipped in the future when

01:43:22.480 --> 01:43:28.960
people are like, "Oh, obviously we didn't need whatever." But at least

01:43:25.520 --> 01:43:31.360
right now, this seems genuinely bad. Um,

01:43:28.960 --> 01:43:36.800
also isn't it called apps when you add like functions to agentic

01:43:34.719 --> 01:43:38.880
systems? Like when when

01:43:38.000 --> 01:43:42.159
>> what does app even mean? >> When a >> It used to be short for application.

01:43:41.119 --> 01:43:47.040
>> This is kind of what I mean. >> Now it's developed. It's kind of its own meaning. I don't know what

01:43:44.719 --> 01:43:53.360
>> when they added wolffram alpha as a thing to open AI's agentic mode. Was

01:43:51.119 --> 01:43:59.520
that was it not an app? >> They could be called skills too. Skills

01:43:55.360 --> 01:44:02.320
and tools. Sure. Whatever. Um, sounds

01:43:59.520 --> 01:44:07.119
sounds good. Uh, other than the product. The product sounds terrible. Um,

01:44:05.280 --> 01:44:08.880
>> remember that time that Facebook wanted to make a phone?

01:44:08.320 --> 01:44:17.280
>> Yeah. >> Remember how nobody wants or needs a

01:44:13.119 --> 01:44:21.040
phone that is not at least at least a

01:44:17.280 --> 01:44:22.880
walled garden ecosystem that is that is

01:44:21.040 --> 01:44:30.000
accepting of, you know, pretty much everything else running on it as a

01:44:25.040 --> 01:44:33.520
platform. Can you think of any reason to

01:44:30.000 --> 01:44:35.920
want this over a phone from someone with

01:44:33.520 --> 01:44:39.360
decades of experience building hardware like Apple?

01:44:37.840 --> 01:44:44.800
>> The Western world is still going to want iPhones and the rest of the world is

01:44:42.320 --> 01:44:52.000
still going to want open systems that they can extend and modify and and keep

01:44:47.679 --> 01:44:53.600
going long term. And this is neither.

01:44:52.000 --> 01:44:58.320
And I don't think it's going to breach the market basically anywhere. Maybe

01:44:56.080 --> 01:45:02.880
it'll be popular for sales in San Francisco.

01:45:00.080 --> 01:45:08.800
Uh, and that's probably about it. So, it's the it's the smartphone for tech

01:45:05.760 --> 01:45:10.719
bros and tech bros only.

01:45:08.800 --> 01:45:13.440
Whoa. Okay. Do you want to hear something kind of wild?

01:45:12.159 --> 01:45:16.800
>> There's more viewers on >> there's more viewers on the WAN Show

01:45:15.199 --> 01:45:20.239
channel than there are on the Linus Tech Tips channel. I think it's going to be

01:45:18.400 --> 01:45:23.760
time to cut it off pretty soon. Guys, if you're watching on Linus Tech Tips right

01:45:21.840 --> 01:45:26.639
now, you got to go switch over to the WAN Show channel. >> We got to figure out that collaborative

01:45:26.080 --> 01:45:31.840
thing. >> Yeah, >> I think that's probably the way to go like moving forward.

01:45:29.920 --> 01:45:34.719
>> Yeah, like a collab stream. So, we stream on the WAN Show and then

01:45:33.440 --> 01:45:40.719
>> we just collab with LT >> collab for a while. I don't think we should do it forever because I don't

01:45:37.679 --> 01:45:42.639
want to be sending notifications on both

01:45:40.719 --> 01:45:46.880
forever. I think we should move to WAN Show sooner rather than >> I don't think it will if you're

01:45:44.560 --> 01:45:51.600
subscribed to both. I think YouTube is smart about that.

01:45:48.480 --> 01:45:53.600
>> I also I also don't want to let people

01:45:51.600 --> 01:45:58.960
get complacent about it. They should subscribe to the WAN Show in order to

01:45:55.679 --> 01:45:59.520
continue to follow the WAN Show. So, G

01:45:58.960 --> 01:46:04.239
get on >> You can do it for streams. >> Get on over there. >> Really, Sammy?

01:46:03.440 --> 01:46:12.159
>> Um, >> YouTube collabs. >> All right, moving on to our next topic.

01:46:09.840 --> 01:46:17.679
I'm going to pick one. Maryland >> video >> has become the first American state to

01:46:15.280 --> 01:46:21.199
ban surveillance pricing in grocery stores.

01:46:19.119 --> 01:46:26.880
Critics do say that the law has too many loopholes. But look, let's let's start

01:46:24.960 --> 01:46:32.639
with let's start with the good news side of it. The law was signed by Governor

01:46:29.280 --> 01:46:34.639
Wes Moore on Tuesday and bans grocerers

01:46:32.639 --> 01:46:39.840
and third party delivery services from using personal data to set higher

01:46:37.360 --> 01:46:46.159
prices. If you're not familiar, surveillance pricing is a practice that

01:46:42.880 --> 01:46:48.960
uses some characteristic of yourself,

01:46:46.159 --> 01:46:55.760
like your zip code, for instance, or your ethnicity or um just any personal

01:46:53.600 --> 01:47:03.119
personally identifiable personal information about you and uses it to

01:46:58.320 --> 01:47:05.360
adjust the pricing upward um because of

01:47:03.119 --> 01:47:08.400
what you can presumably afford. there's some camera thing and it's like, "Oh,

01:47:06.800 --> 01:47:13.119
white people like broccoli. Let's increase the price of broccoli." >> Pretty much. It doesn't have to be a

01:47:11.520 --> 01:47:17.119
racial thing, but um >> it could be. >> Let's face it,

01:47:16.239 --> 01:47:21.199
>> it could be. >> Whether we want it to go to a race place or not, it often ends up

01:47:20.080 --> 01:47:24.880
>> they'll put it behind some machine learning thing and call it a black box and say they have no control over it.

01:47:23.920 --> 01:47:28.199
>> Sorry, what kind of box? >> Oh my god.

01:47:31.840 --> 01:47:37.360
>> I think you're more intimately familiar than me.

01:47:35.440 --> 01:47:40.360
Uh, no.

01:47:42.560 --> 01:47:45.560
Listen,

01:47:50.239 --> 01:47:57.600
Colorado, California, Massachusetts, Illinois, and

01:47:55.440 --> 01:48:02.400
New Jersey are all considering similar bills. But while this is a win, consumer

01:48:00.560 --> 01:48:07.040
advocates are saying that Maryland's law is full of loopholes. The biggest one is

01:48:04.960 --> 01:48:10.480
that it bans raising prices based on personal data, but doesn't stop

01:48:08.960 --> 01:48:15.440
companies from raising prices for everyone, then offering personalized

01:48:12.880 --> 01:48:20.159
discounts that ultimately arrive at the exact same outcome. There are also

01:48:17.840 --> 01:48:23.679
exemptions for loyalty programs and promotional offers, which are some of

01:48:21.920 --> 01:48:28.159
the main vehicles that companies already use to do this. And there's no private

01:48:26.719 --> 01:48:31.920
right of action, meaning that regular consumers can't actually sue if they get

01:48:30.080 --> 01:48:35.520
caught up in surveillance pricing. Only the state attorney general can enforce

01:48:33.280 --> 01:48:39.840
it, which critics say guts any real deterrent. So, it's a little bit of

01:48:38.080 --> 01:48:44.639
progress in that we're finally talking about the issue. We're acknowledging the

01:48:42.159 --> 01:48:48.880
issue, but it's very clear that there is a lot more that needs to be done. And I

01:48:47.440 --> 01:48:53.760
mean, personally, I would just love to see this happen across the board. you

01:48:51.280 --> 01:48:56.800
know why are airline t why are airline operators allowed to do this

01:48:55.840 --> 01:49:02.400
>> actually crazy >> like the entire vacation industry seems

01:48:59.199 --> 01:49:05.679
to operate based on this um however

01:49:02.400 --> 01:49:09.679
however I I would caution that we don't

01:49:05.679 --> 01:49:13.119
want to go too far regional pricing on

01:49:09.679 --> 01:49:14.800
services like steam for example I

01:49:13.119 --> 01:49:19.760
>> fundamentally support >> so this shouldn't be able to be done within a country is that fair enough

01:49:17.840 --> 01:49:24.239
>> I think that's a fair line to draw let's use the those arbit arbitrary lines on

01:49:21.440 --> 01:49:29.480
the map and let's let's make those the boundaries.

01:49:24.800 --> 01:49:29.480
>> Would you go as far as like

01:49:29.600 --> 01:49:36.719
a province >> or a city?

01:49:34.239 --> 01:49:39.280
>> Would I allow different pricing

01:49:38.400 --> 01:49:43.280
>> because I'm pretty sure >> somebody had Alberta plates on?

01:49:42.080 --> 01:49:46.639
>> Oh, right. Cuz it would have to be dynamic. It has to be dynamic. Yeah.

01:49:45.600 --> 01:49:51.840
>> No, I don't. I >> Okay. So, cuz my mind is like I mean there is different pricing for like say

01:49:50.080 --> 01:49:55.280
milk in Alberta versus here. >> Yeah. But it shouldn't be because of

01:49:53.520 --> 01:50:00.800
where you're from or because of who you are. >> It shouldn't be. Yeah. >> Yeah. No, that's up. Especially

01:49:58.239 --> 01:50:03.199
because it incentivizes these organizations to then collect the data

01:50:02.480 --> 01:50:07.360
on everybody. >> Yeah. >> And then whether or not they actually use it, I mean, a lot of they're going

01:50:06.639 --> 01:50:12.000
to use it anyway. >> You can set your pricing. There might be market factors. It might be more

01:50:10.239 --> 01:50:17.280
expensive to get trucks to wherever you are. Maybe you're way north in Canada or

01:50:13.840 --> 01:50:18.800
something. That's just a fact. Um, but

01:50:17.280 --> 01:50:25.360
you can't you can't change it based on who's in the store. Yeah, obviously that

01:50:21.920 --> 01:50:28.400
seems like it should just happen.

01:50:25.360 --> 01:50:30.639
Um, Fools and Horses says, "Linus, do

01:50:28.400 --> 01:50:34.400
you collect any trends or data from LT store? Where does the line get drawn?"

01:50:33.280 --> 01:50:39.840
You know what? This was actually something that >> you don't use that to

01:50:38.080 --> 01:50:46.159
target pricing for specific users, though. >> Uh, no, we don't. But Colton had

01:50:42.159 --> 01:50:49.280
actually messaged us about um like what

01:50:46.159 --> 01:50:51.280
we do and don't collect on LT store and

01:50:49.280 --> 01:50:55.520
like where we think the right line would be. I don't know if we ever actually

01:50:53.600 --> 01:50:59.040
talked about that on WAN Show. I can't actually I can't find the email from him

01:50:57.920 --> 01:51:06.880
right now, but do you remember the one that I'm talking about? They're trying to figure out like what would be what

01:51:03.040 --> 01:51:09.280
would be uh you know an LMG friendly

01:51:06.880 --> 01:51:13.440
level of like cookies and data collection to determine whether some of

01:51:11.679 --> 01:51:19.679
the marketing efforts that his team is doing are actually working because right

01:51:15.840 --> 01:51:21.760
now we do some limited data collection

01:51:19.679 --> 01:51:26.880
but there are pieces of it that would be very helpful to them that right now they

01:51:24.480 --> 01:51:31.360
don't they don't have enough to get a to get a clear picture. For instance, like

01:51:29.600 --> 01:51:38.639
um one of the things they were looking at was like conversion of um of people

01:51:35.679 --> 01:51:44.639
on Floatplane for subscriptions and stuff like that. Uh what what is what's

01:51:42.080 --> 01:51:48.239
the right amount? >> The Floatplane one was a pretty big

01:51:46.400 --> 01:51:52.239
line because we don't have a banner for stuff like that because we don't do like

01:51:49.840 --> 01:51:56.960
any of it. So we were like h we'd have to do >> Oh, like a GDPR like and like a cookie

01:51:55.360 --> 01:52:00.159
banner and like all that kind of stuff. Yeah.

01:51:58.639 --> 01:52:04.159
Um, so I we just didn't do it.

01:52:02.320 --> 01:52:08.159
>> Ze says, "I avoid ads at a very high cost." Yeah, we're not we're not talking

01:52:05.679 --> 01:52:10.560
about ads though. We're talking about like >> forms of tracking.

01:52:09.440 --> 01:52:14.960
>> Yeah. >> Because like you it's it's there are

01:52:12.800 --> 01:52:17.440
also other ways to do it though and that that was the counter pitch from flow

01:52:16.639 --> 01:52:25.199
plane. >> So how do we do it? Um, you can have

01:52:20.960 --> 01:52:27.440
like you can have it so that it's a link

01:52:25.199 --> 01:52:30.239
and like the where did the URL come from. >> Yeah.

01:52:28.560 --> 01:52:35.199
>> So we we can't track it on like an individual user basis, but we can see

01:52:32.080 --> 01:52:37.679
like this many people clicked this link

01:52:35.199 --> 01:52:41.440
and this many people that clicked on that link did follow through and

01:52:39.280 --> 01:52:45.679
purchase a description. Now, someone could screw that up because the for us

01:52:44.400 --> 01:52:52.960
because they could click on the link and then like navigate somewhere else manually and that manual navigation

01:52:49.199 --> 01:52:55.040
might get rid of the the uh the URL.

01:52:52.960 --> 01:52:58.800
Like there's there's yeah, there are other ways to do it. They're not

01:52:56.639 --> 01:53:03.760
perfect, but neither is aggressive cookies that you're also feeding to

01:53:02.159 --> 01:53:09.239
Facebook or whoever else because you're running it through their systems. It's

01:53:05.440 --> 01:53:09.239
another thing to keep in mind.

01:53:12.000 --> 01:53:18.960
Yeah. >> All right. Well, let's leave it alone

01:53:15.520 --> 01:53:21.040
for now and then we'll go from there, I

01:53:18.960 --> 01:53:25.440
guess. >> I don't know, man. I I understand why

01:53:23.520 --> 01:53:28.639
his team wants to do this stuff, but I also understand the hesitation.

01:53:27.280 --> 01:53:32.480
>> Yeah, but like I said, there are other options. It's not like we're we're

01:53:30.480 --> 01:53:35.280
saying I mean, we we might have said no at the time because we're such a small

01:53:34.000 --> 01:53:39.840
team. We can't just do everything all the time, but um

01:53:38.159 --> 01:53:45.119
there's ways that you can track how well that campaign is working without being

01:53:41.920 --> 01:53:45.520
able to tie it down to a specific user.

01:53:45.119 --> 01:53:50.960
>> Okay? >> Like it is possible. You can you can have flags in the URL that follow the

01:53:50.000 --> 01:53:56.480
process. >> And if if one of those like URL flagged

01:53:54.800 --> 01:54:03.520
people that goes through does a purchase, >> it's just holding tallies.

01:54:01.119 --> 01:54:07.199
>> Okay. So you like the advertising platform side should know how many

01:54:05.280 --> 01:54:12.800
people you served that ad to. >> Mhm. >> Our side should know how many people

01:54:09.280 --> 01:54:14.320
came to the site with that in the URL

01:54:12.800 --> 01:54:18.800
and then our side should know how many people checked out with that in the URL

01:54:16.639 --> 01:54:22.880
and then you have your three data points and like ideally that's enough and then

01:54:20.719 --> 01:54:26.080
we're not feeding it through Meta or whoever else. Um

01:54:24.400 --> 01:54:30.960
>> Amaker asks are you just putting yourself at a commercial disadvantage by

01:54:28.000 --> 01:54:39.199
trying to be ethical about this? Yes, but like we often do and that's

01:54:36.080 --> 01:54:40.800
something we've decided to do. And I

01:54:39.199 --> 01:54:45.480
think I think that should almost potentially uh reflect

01:54:46.639 --> 01:54:51.679
I'm just going to skip.

01:54:49.920 --> 01:54:55.520
>> All right. In some other cool news, >> you guys can come up with your own

01:54:52.960 --> 01:55:00.560
morality on that one. The first Tesla semi-truck from their Gigafactory Nevada

01:54:58.560 --> 01:55:07.199
highvolume production line has officially rolled off the line. The semi

01:55:03.679 --> 01:55:09.280
is a little late. It was first unveiled

01:55:07.199 --> 01:55:15.840
in 2017 with an original promised production date of 2019.

01:55:12.159 --> 01:55:17.599
Okay, a little late, but it's here. It

01:55:15.840 --> 01:55:21.840
is worth noting this is not the first semi to be produced. A handful were

01:55:19.440 --> 01:55:27.360
delivered to PepsiCo in late 2022, but those were essentially like handbuilt on

01:55:23.920 --> 01:55:29.119
a pilot line. This time, we're talking

01:55:27.360 --> 01:55:33.119
mass-produced units with an expected annual production capacity of 50,000

01:55:31.760 --> 01:55:36.239
trucks. Although, it is worth noting that that will have to ramp up over the

01:55:35.280 --> 01:55:42.320
next few years. >> Doesn't mean anything. >> And it doesn't mean anything because

01:55:38.400 --> 01:55:44.400
Tesla lies constantly. But but but this

01:55:42.320 --> 01:55:50.159
is, as far as we can tell, truthfully, the mass production line. These trucks

01:55:46.480 --> 01:55:52.400
have a range of 325 m or 500 m depending

01:55:50.159 --> 01:55:57.119
on whether they are the standard or long range model. And that is apparently

01:55:54.560 --> 01:56:03.199
fully loaded, though it's not clear in our notes what exactly fully loaded

01:56:01.280 --> 01:56:09.840
means. There's definitely degrees of loaded for semi-truckss. They support

01:56:05.440 --> 01:56:13.280
Tesla's mega charger, which is 1.2

01:56:09.840 --> 01:56:17.040
megawatt charger. I

01:56:13.280 --> 01:56:21.199
could they not have done 1.21? 21.

01:56:17.040 --> 01:56:22.639
They were so close. 1.21 megaww.

01:56:21.199 --> 01:56:29.280
>> Yeah, it would be pretty sick. >> And that does that'll restore 60% of the

01:56:26.159 --> 01:56:31.679
truck's range in 30 minutes. Cost on the

01:56:29.280 --> 01:56:38.360
long range model. And this is what makes this good news show. Cost on the long

01:56:34.000 --> 01:56:38.360
range model is expected to be $290,000.

01:56:39.280 --> 01:56:44.320
That >> do we have a reference point for other semi trucks?

01:56:42.320 --> 01:56:46.320
>> Oh, they're really expensive. I know >> they're so expensive.

01:56:45.360 --> 01:56:51.119
>> That was my grandpa's job. >> And like the maintenance and the dealer

01:56:48.560 --> 01:56:55.280
network and just the like old boys club of everything, the financing,

01:56:53.199 --> 01:56:58.960
>> crazy loans. >> $290,000

01:56:57.679 --> 01:57:05.280
for something >> that is going to have sure all the

01:57:02.480 --> 01:57:08.159
disadvantages of an electric vehicle, right? Like these batteries will

01:57:06.639 --> 01:57:13.760
eventually wear out and you have to charge and blah blah blah blah blah. But

01:57:10.480 --> 01:57:15.599
that will also have the advantages

01:57:13.760 --> 01:57:21.760
of an electric vehicle and that you're using simple electric motors.

01:57:19.599 --> 01:57:26.960
Not okay, sorry, not simple, but relatively lowmaintenance electric

01:57:23.280 --> 01:57:28.719
motors. Dude, this thing looks freaking

01:57:26.960 --> 01:57:33.760
awesome. I am uh I am I'm like kind of stoked on

01:57:31.840 --> 01:57:39.520
it. To be clear, I don't think that the Tesla Semi is going to be taking over

01:57:35.599 --> 01:57:41.280
long haul trucking anytime

01:57:39.520 --> 01:57:44.080
>> in the foreseeable future. >> There's a ton of trucking that isn't

01:57:43.040 --> 01:57:51.360
long haul trucking. >> Yes. And >> that's okay. >> And and what's kind of cool about this

01:57:48.159 --> 01:57:53.760
is for semis, I can actually see the

01:57:51.360 --> 01:57:57.440
range being less of an issue, especially for companies that are somewhat

01:57:55.280 --> 01:58:01.280
integrated where they can build in charging infrastructure at the various

01:57:59.920 --> 01:58:03.840
docks that they're going to be visiting. cuz it said 60% in half an hour, right?

01:58:03.440 --> 01:58:10.000
>> Mhm. >> If you're doing an unload or load, >> well, that wouldn't get a lot of char.

01:58:07.679 --> 01:58:14.960
>> You wouldn't have a mega charger at like your warehouse.

01:58:12.000 --> 01:58:18.719
>> But if every time you docked, you would be able cuz I mean you like your

01:58:16.800 --> 01:58:23.119
transformer for your for your warehouse building like simply will not have that

01:58:20.800 --> 01:58:24.800
level of unless you went out of your way like you're not going to have a mega

01:58:24.239 --> 01:58:29.360
charger. >> Sorry. Sorry. Specifically mega charger. Yeah. Yeah. So I guess it won't do that

01:58:27.679 --> 01:58:34.080
rate but still you could plug into something. >> Yes. But but the way that I see it is as

01:58:32.320 --> 01:58:38.400
long as this thing is charged in the morning >> as you're going around to, you know,

01:58:36.719 --> 01:58:42.400
your bottling, let's use Pepsi as an example, just because they were one of

01:58:40.239 --> 01:58:45.360
the first customers for the Tesla Semi. So, you're going around to your various

01:58:44.080 --> 01:58:49.599
ports of call. You're going to like the bottling depot here. You're dropping off some, you're making some drop offs at a

01:58:48.400 --> 01:58:54.880
distribution hub here, you're going back to the bottling depot. If at every one of those or at or at some of those at

01:58:53.119 --> 01:58:58.800
the at the ones that you own, you're able to plug in while things are are

01:58:56.960 --> 01:59:03.280
loading and and being unloaded >> a little bit more, >> you can you can juice yourself up a

01:59:01.599 --> 01:59:07.760
little bit over the course of the day. And if you're mostly doing local

01:59:05.199 --> 01:59:15.199
distribution runs, this is just going to be so huge for everything from noise to

01:59:11.679 --> 01:59:17.119
urban smog to just convenience for

01:59:15.199 --> 01:59:21.440
operators. It's like driving a big rig like like a like man. Did you know that

01:59:19.040 --> 01:59:24.800
some of them have like two stick shifts? >> I didn't know about the two. Yeah,

01:59:22.960 --> 01:59:30.159
>> I didn't know you can like slip gears on purpose and there's all this like

01:59:26.960 --> 01:59:33.040
>> like driving a truck is nonsimple.

01:59:30.159 --> 01:59:38.400
>> If it could be if it could be one one pedal driving semis like if we could

01:59:35.760 --> 01:59:42.960
lower the barrier to entry for for operating these vehicles.

01:59:40.719 --> 01:59:45.760
Lower the mental load of operating them so you can be more focused on the road.

01:59:44.560 --> 01:59:50.960
>> All right. The barrier to entry thing spooks me because of the amount of opened tin cans we've had in in BC of

01:59:49.920 --> 01:59:56.159
people hitting bridges. >> When I say okay, when I say lower the barrier to entry, I don't mean that we

01:59:54.239 --> 01:59:58.719
need people who are less cognitively capable operating them. What I mean is

01:59:57.920 --> 02:00:04.400
that >> fewer fewer distractions. >> Sure.

02:00:01.520 --> 02:00:07.360
>> Um I I just I see this as an absolute I see this as an absolute win.

02:00:05.760 --> 02:00:11.760
>> Yeah, it seems cool. I always have like a little bit of skepticism

02:00:09.840 --> 02:00:14.560
um because of their track record on being

02:00:13.280 --> 02:00:19.360
able to hit their targets and stuff like that, but these things just rolling off

02:00:16.880 --> 02:00:25.920
the line sounds great to me. >> Uh Tim asks, "How about maintenance?" I

02:00:22.400 --> 02:00:28.639
mean, look, a diesel engine is a super

02:00:25.920 --> 02:00:32.880
reliable engine. You know, like a like a Cumins diesel that you might find in a

02:00:30.800 --> 02:00:36.719
in a large truck. It's going to be pretty flipping reliable. Like those

02:00:34.719 --> 02:00:39.920
Volvo trucks, they'll do a million miles, you know?

02:00:38.320 --> 02:00:44.400
>> And that's not even like that's not even like, whoa, you should get a free truck

02:00:42.800 --> 02:00:48.159
cuz it did a million miles, you know? Like remember that first car that that

02:00:46.560 --> 02:00:52.400
like traveling salesman or whatever who put a million miles on his car and the company gave him a new one. Like that's

02:00:51.040 --> 02:00:58.719
not that's not even like that remarkable, >> but uh actually, okay. A Hayago ego says

02:00:56.960 --> 02:01:02.080
diesels used to be super reliable, but now they are not as good. Interesting.

02:01:01.520 --> 02:01:09.679
>> Okay. >> Classic. >> Yeah. No. many such cases. >> No comment on that. I I I was not aware

02:01:06.800 --> 02:01:17.119
of that. From my understanding, big rigs do tend to be pretty reliable. Um Edison

02:01:14.400 --> 02:01:19.920
motors, hold on a second. Um but yeah, from a maintenance standpoint, I know

02:01:18.480 --> 02:01:27.360
that my experience with electric vehicles has been that it's relatively low. And I would imagine that especially

02:01:23.280 --> 02:01:28.400
on braking, these would just be

02:01:27.360 --> 02:01:32.239
so much better. >> Breaking on one of these must be insane,

02:01:30.560 --> 02:01:35.599
>> right? >> Yeah. I mean, maybe I'm missing

02:01:33.760 --> 02:01:40.080
something here. Feel free to tell me if I'm missing something, but regenerative

02:01:37.520 --> 02:01:41.840
braking would be amazing for trucks, and they spend so much time idling and

02:01:41.599 --> 02:01:47.440
stuff. >> Wonder if it's just relative. Wonder if it takes so much energy to get them

02:01:45.360 --> 02:01:51.599
going that it's it's relative. I'm not sure.

02:01:49.040 --> 02:01:54.960
>> Um, okay. Hold on. >> Either way, neat. Cool. To be clear,

02:01:54.159 --> 02:02:00.159
>> see it when it happens. >> Tesla's not the only player in the game. We actually I really I still need to go

02:01:59.280 --> 02:02:06.840
>> these guys shipping. >> Check out these guys. is uh >> can you buy a semi-truck from them?

02:02:03.840 --> 02:02:06.840
>> Uh

02:02:07.280 --> 02:02:14.239
okay, so hybrid so diesel and battery.

02:02:11.920 --> 02:02:15.520
So hybrid trucks could be a better approach to

02:02:15.199 --> 02:02:22.239
>> idea >> to long range trucking and Edison Motors is a company that uh they they they're

02:02:20.560 --> 02:02:27.119
doing like an investment drive right now. Like I don't know what kind of

02:02:24.320 --> 02:02:31.040
shape they're in right now. So this is not like an endorsement of the company

02:02:29.440 --> 02:02:38.000
or anything like that. I I don't know enough to say one way or the other, but

02:02:33.599 --> 02:02:41.880
I do I do love the idea of what they're

02:02:38.000 --> 02:02:41.880
doing. Um,

02:02:43.840 --> 02:02:49.520
uh, V&G Supernova says, "I thought semis used pneumatic braking, so regen braking

02:02:47.760 --> 02:02:56.320
wouldn't be that useful. Does the Tesla Semi not use regen braking?"

02:02:52.960 --> 02:02:57.920
Regenerative braking

02:02:56.320 --> 02:03:01.119
uses powerful regenerative braking across all three electric motors as

02:02:59.520 --> 02:03:06.080
Yeah. Um yeah. No, no, no. Yeah, regular semis

02:03:04.239 --> 02:03:11.679
do use pneumatic. A lot of them use air brakes, but no, the Tesla should be uh

02:03:10.239 --> 02:03:16.800
should be using regenerative braking. Yeah. Yeah, it uses regenerative braking. So, that's kind of like the

02:03:14.320 --> 02:03:20.320
whole point of the Tesla Semi is that it is doing things differently to bring

02:03:18.400 --> 02:03:24.400
advantages that traditional semis do not.

02:03:22.480 --> 02:03:28.159
Uh, Kitsuni Sensei says, "Most of your wishes for trucks are already reality

02:03:25.920 --> 02:03:34.480
outside of North America." This is this is true. Uh, electric trucks in um like

02:03:32.639 --> 02:03:40.000
I I I remember seeing like a crazy number apparently in the last year there

02:03:37.040 --> 02:03:45.360
were more electric trucks produced in China than the entire total addressable

02:03:42.320 --> 02:03:47.840
market like the entire annual market for

02:03:45.360 --> 02:03:51.199
um fossil fuel and electric trucks in North America.

02:03:48.719 --> 02:03:56.719
>> Wow. Um, so yes, electric trucks are definitely a thing, but guys, it's good

02:03:54.320 --> 02:04:02.360
news. W show, can we just let a win be a win? Okay, there's more electric trucks

02:03:59.040 --> 02:04:02.360
on the road.

02:04:03.360 --> 02:04:07.840
All right. Uh, what else we got? You want to pick

02:04:07.119 --> 02:04:13.119
one? >> Sure. Let's jump through here.

02:04:11.679 --> 02:04:17.280
>> I think I know what you might pick. I'm going to be ready for it. >> Is it just the next one?

02:04:16.320 --> 02:04:22.560
>> Whatever you want. >> Right to repair. Repeal repelled. What a

02:04:20.480 --> 02:04:27.119
what a title. Colorado's consumer rights continue. Kick rocks corpose. Colorado's

02:04:25.119 --> 02:04:31.440
consumer rights right to repair digital electronics equipment law took effect in

02:04:29.440 --> 02:04:35.760
January 2026 providing access to documentation and tools to repair or

02:04:33.199 --> 02:04:40.239
modify electronics. However, a new bill was proposed that would create an

02:04:37.440 --> 02:04:46.719
exception for critical infrastructure, a term that advocates uh

02:04:44.159 --> 02:04:51.760
that advocates feel is too loosely defined. The bill was supported by

02:04:49.280 --> 02:04:58.080
lobbyists for Cisco and IBM and passed unanimously through the Colorado Senate

02:04:54.400 --> 02:05:00.800
really but was shot down in a 7 to4 vote

02:04:58.080 --> 02:05:05.119
by the Colorado House's state civic military and veteran affairs committee.

02:05:03.360 --> 02:05:10.880
The core arguments from Cisco representatives claimed that there was

02:05:06.880 --> 02:05:13.520
potential cyber security risks

02:05:10.880 --> 02:05:17.360
to what uh what's to stop bad actors from using those tools to reverse

02:05:15.040 --> 02:05:22.239
engineer internet routers? I mean lots of Okay, carry on.

02:05:19.920 --> 02:05:25.520
>> Cyber security experts pointed out it doesn't really work like that. The vast

02:05:24.159 --> 02:05:30.480
majority of hacks are carried out remotely and it is more likely the

02:05:27.920 --> 02:05:33.920
victims of hacks um that that need to make changes on the fly without

02:05:31.520 --> 02:05:37.840
acquiring permission from manufacturers. >> Yes.

02:05:35.679 --> 02:05:43.280
>> Yeah. Cool. Oh man, our discussion question

02:05:40.159 --> 02:05:45.040
here is is there is there Oh, okay. No,

02:05:43.280 --> 02:05:49.840
I misread it. I thought it was wanting us to get into uh whether lobbying

02:05:47.440 --> 02:05:52.239
should be a thing or not. No, we're definitely not approaching that on the

02:05:51.280 --> 02:05:55.280
WAN Show today. >> No. >> Uh I thought you were going to do this

02:05:54.320 --> 02:05:59.599
one. >> Oh, where is that one?

02:05:58.800 --> 02:06:03.760
>> Up a little higher. >> I see it. Yeah. Yeah. Yeah. This week,

02:06:01.920 --> 02:06:08.560
Noctua announced that they now offer public 3D CAD models for all their fans.

02:06:06.719 --> 02:06:13.119
You can find the files directly from their product download section, just

02:06:10.480 --> 02:06:21.199
like any fan. Uh, sorry. Just find any fan such as the classic NFF12PWM.

02:06:17.840 --> 02:06:23.920
Oh, one sec. Go away. Uh, if you want to

02:06:21.199 --> 02:06:28.560
download a step file to check it out, Sammy might have a 3D printed one for

02:06:25.760 --> 02:06:34.159
you to check out, which is here. >> Yeah, it is worth noting that this is

02:06:31.760 --> 02:06:39.360
not going to allow you to make your own knock to a fan. This fan that Luke is

02:06:37.520 --> 02:06:47.440
holding is not really a fan so much as it is a motor model of a fan. Yeah,

02:06:42.320 --> 02:06:50.320
there's no motor in it. And um Noctua

02:06:47.440 --> 02:06:54.079
says that they intentionally adjusted the geometry a little bit so that

02:06:51.840 --> 02:06:57.920
cosmetically it looks like their fans, but if you were to 3D print your own fan

02:06:56.400 --> 02:07:03.520
and actually put a motor in it, it would not achieve the same performance

02:06:59.840 --> 02:07:06.400
characteristics. Um, you know, obviously

02:07:03.520 --> 02:07:09.760
that wouldn't prevent anyone from just buying a real knock to a fan and

02:07:07.840 --> 02:07:14.800
scanning it or whatever. A sophisticated enough counterfeitter uh would be able

02:07:12.560 --> 02:07:19.760
to make it without this anyway, but this is more for community members to have

02:07:17.840 --> 02:07:22.320
realistic looking Noctua products in their, you know, their renderings or

02:07:21.440 --> 02:07:28.800
whatever else. >> Sure. >> So, yeah, I think I don't know. I just I just I just thought it was pretty cool.

02:07:27.040 --> 02:07:35.280
>> Sweet. >> Exactly. In other sweet news, Libropods

02:07:32.880 --> 02:07:41.440
no longer requires root for some features. So, Libropods, if you're not

02:07:37.599 --> 02:07:44.400
familiar, is a way to use AirPods on

02:07:41.440 --> 02:07:50.159
Android and have some of the uh Apple exclusive features accessible. The app

02:07:47.119 --> 02:07:53.440
now works without root privileges on

02:07:50.159 --> 02:07:55.040
Google Pixels um running Android 16

02:07:53.440 --> 02:07:59.360
March update or later with the latest Play System update. Uh, Google Pixels

02:07:57.440 --> 02:08:03.760
running Android 17 beta 3 or above. Okay, hold on. I'm a little confused by

02:08:00.880 --> 02:08:08.079
those two. Uh, are my do I have a problem with my

02:08:05.920 --> 02:08:11.800
notes? Control F pixel.

02:08:11.840 --> 02:08:19.040
Okay. Well, mileage may vary on those two. OnePlus

02:08:17.199 --> 02:08:23.920
devices that are running oxygen OS 16 and above. OPPO devices on Color OS 16

02:08:21.360 --> 02:08:30.320
and above. And Realme devices on Realme UI 7.0 toe and above. You can now get

02:08:27.840 --> 02:08:36.960
the following features without root noise control modes, ear detection,

02:08:33.840 --> 02:08:39.679
battery status, head gestures, and

02:08:36.960 --> 02:08:43.199
conversational awareness. There are a few more features that Libra Pod

02:08:41.199 --> 02:08:46.800
supports, but still require root, and that's hearing aid mode, customized

02:08:45.040 --> 02:08:51.840
transparency mode, and multi-device connectivity. Honestly, they've nailed

02:08:48.480 --> 02:08:54.560
down most of the stuff that I would

02:08:51.840 --> 02:08:59.760
think I would need. The app is free on the Play Store, but does require an

02:08:56.560 --> 02:09:01.360
inapp purchase of €5 in order to unlock

02:08:59.760 --> 02:09:06.800
all functionality. I think I actually bought it a while ago. I just need to

02:09:03.040 --> 02:09:11.679
check. Um, it's my uh my Galaxy phone is

02:09:06.800 --> 02:09:14.960
still not on the list, but I am very

02:09:11.679 --> 02:09:18.400
very ready to have more

02:09:14.960 --> 02:09:21.040
more Libra Pods goodness.

02:09:18.400 --> 02:09:26.639
Man, it's amazing how many updates like modern platforms make to make them

02:09:24.000 --> 02:09:30.639
supposedly faster and yet they are so slow. Like I remember when

02:09:28.480 --> 02:09:33.760
>> it's a lot of updates are not for speed. >> YouTube updated their dashboard. They

02:09:32.239 --> 02:09:37.440
claimed it was all about speed. It is still slower than it ever was. Like the

02:09:35.360 --> 02:09:43.199
creator dashboard and like graphs and everything. Like hello. Can we can I

02:09:40.880 --> 02:09:46.480
search for something? Anyway, not right now apparently. H what else we got

02:09:45.040 --> 02:09:50.679
today? Um, let's see.

02:09:51.040 --> 02:09:59.199
Boink pentathlon. The LCT Boink team will be competing in the seventh Boink

02:09:56.079 --> 02:10:02.480
Pentathlon running from 17th. That makes

02:09:59.199 --> 02:10:04.880
more sense. Uh, running from May 5th to

02:10:02.480 --> 02:10:08.800
19th in this event. We'll go up against other tech communities contributing

02:10:06.480 --> 02:10:14.079
computing power through Boink to support scientific research and progress. Last

02:10:11.119 --> 02:10:18.000
year, LT placed in second overall. Our goal this year is to take home the gold.

02:10:16.639 --> 02:10:22.719
If you want to join the competition and support science, you can find the details and sign up on the thread on the

02:10:21.679 --> 02:10:27.599
forum. >> Oh, I finally have a use for my computer. I will compete this year with

02:10:25.599 --> 02:10:30.639
you guys. >> Here's all the details. There will be

02:10:29.119 --> 02:10:33.440
prizes. Oh, wow. There's community donated prizes.

02:10:32.639 --> 02:10:37.760
>> Yeah. Yeah. Yeah. >> Steam keys. Uh yeah. Well, we're

02:10:35.679 --> 02:10:43.280
providing some prizing, too, right? >> We better be. >> We better be. Well, we're on it. We'll

02:10:40.719 --> 02:10:45.920
find some prizes. Don't worry about it. Uh, let me uh

02:10:44.400 --> 02:10:53.679
>> I didn't see us in there, but we usually do. >> Yeah, I don't know. We'll we'll we'll get it done. Heck yeah. All right, cool.

02:10:51.920 --> 02:10:58.079
Heck yeah. LT forum. >> And

02:10:55.760 --> 02:11:04.000
Xbox mode begins rolling out to players on Windows 11 PCs.

02:11:00.880 --> 02:11:06.000
Scroll. Today, Microsoft is expanding

02:11:04.000 --> 02:11:12.159
what used to be called the full screen experience on handhelds like the RG Xbox

02:11:09.119 --> 02:11:15.440
Ally to all Windows 11 PCs, laptops,

02:11:12.159 --> 02:11:17.199
desktops, tablets, etc. Xbox mode is a

02:11:15.440 --> 02:11:20.719
full screen controller optimized interface that puts your game library

02:11:18.960 --> 02:11:25.840
front and center while minimizing background distractions. rolling out

02:11:22.960 --> 02:11:31.440
gradually in select markets via Windows update. You can toggle it in settings,

02:11:28.560 --> 02:11:37.040
then enter it with Windows and F11 from the game bar or by pressing the Xbox

02:11:35.040 --> 02:11:41.199
button on a paired controller. >> Yeah. So, three different ways to

02:11:38.480 --> 02:11:45.679
activate it. Discussion question. Is Xbox mode what Windows gaming should

02:11:42.800 --> 02:11:48.000
have been all along? >> Yeah,

02:11:47.199 --> 02:11:52.400
>> probably. >> Yeah. I mean, it's it's basically the

02:11:50.480 --> 02:12:00.520
game folder from Windows Vista, but like way better.

02:11:54.159 --> 02:12:00.520
Um, overall I like itish. Um,

02:12:00.719 --> 02:12:09.520
in some ways it feels like it can be a little unnecessary because my entire

02:12:06.800 --> 02:12:14.880
game library is in Steam pretty much. Uh, but if I was someone who had a game

02:12:12.480 --> 02:12:21.040
library that spanned multiple launchers to a greater degree, then yeah, having

02:12:18.239 --> 02:12:24.639
the the Xbox mode experience consolidate them all would have more of a value to

02:12:24.000 --> 02:12:29.599
me. >> I definitely have multiple launchers. >> Yeah.

02:12:27.280 --> 02:12:33.599
>> Uh, I mean, especially with Yeah, I might. Especially with um new Assassin's

02:12:31.920 --> 02:12:38.800
Creed, not new Assassin's Creed, the new Assassin's Creed remaster coming and

02:12:35.280 --> 02:12:42.079
stuff. It's definitely a little bit, you

02:12:38.800 --> 02:12:43.599
know, full of game pass and stuff,

02:12:42.079 --> 02:12:47.520
>> but you don't have to click those buttons. So,

02:12:45.920 --> 02:12:52.800
>> as they're there, they'll probably annoy me. >> Well, let's see. Let's see.

02:12:50.560 --> 02:12:57.760
>> Uh, hey, speaking of things that are there and might not annoy you, Toyota's

02:12:54.800 --> 02:12:59.760
limited edition $3,500 Crown gaming chair. Yeah.

02:12:58.480 --> 02:13:03.360
>> I mean, is here. >> You know what does annoy me about this

02:13:01.520 --> 02:13:07.280
is I've >> I don't know, man. I don't fit a lot of

02:13:05.119 --> 02:13:08.800
chairs. Just being honest.

02:13:08.400 --> 02:13:15.360
>> Mhm. >> I don't. So, I saw this and was like,

02:13:11.520 --> 02:13:17.679
"No way. Let's go. I want the purchase

02:13:15.360 --> 02:13:22.639
page right now." And then I saw the price and I was like, "Well, someone

02:13:20.239 --> 02:13:26.159
will have fun with that." >> It looks

02:13:24.480 --> 02:13:28.960
pretty fancy. >> I love that there's actually a

02:13:28.239 --> 02:13:37.920
>> USBC. >> I didn't notice that when I first looked at it. That is actually so funny. Um,

02:13:34.560 --> 02:13:40.480
sorry. My uh my zoom wait. My zoom is

02:13:37.920 --> 02:13:46.320
being a little funky. Uh here, hold on. I'm 100%. Yeah. Why is it $3500

02:13:46.000 --> 02:13:51.520
though? >> It's like the crown collection. Like the price of two monitors.

02:13:49.760 --> 02:13:54.000
>> Oh my two.

02:13:52.960 --> 02:13:58.239
>> That's so painful. >> Heating. >> Cooling sounds pretty cool.

02:13:56.880 --> 02:14:05.920
>> The cooling sounds incredible. >> The cooling sounds amazing. Um

02:14:02.639 --> 02:14:07.280
I don't know what I would do with this.

02:14:05.920 --> 02:14:10.800
>> You know what my chair at home is right now? >> Charging, I guess, cuz it wouldn't be

02:14:09.280 --> 02:14:14.159
data. Like, it wouldn't be connected to my computer. >> Don't answer that, Luke. We got a merge

02:14:13.280 --> 02:14:20.000
message for later. >> Wait. >> Oh, okay. >> Oh, wait. >> For some reason,

02:14:16.880 --> 02:14:22.159
>> what's in the caboose?

02:14:20.000 --> 02:14:24.239
>> Uh, is that all the like is that the like

02:14:23.280 --> 02:14:28.400
>> Oh, does it >> stuff for the heating and cooling? >> Is that the junk?

02:14:26.480 --> 02:14:31.760
>> Wait, so you like this needs to be like plugged in. >> Oh, I'm sure.

02:14:30.320 --> 02:14:36.880
>> Right. Which makes sense. Yeah. Heating and cooling. Wow. You know, I I want to

02:14:34.480 --> 02:14:39.840
try it. Is it Japan only, though? >> I think it's Japan only.

02:14:38.320 --> 02:14:48.159
>> Just Just you know, >> there's only about 70 units being made.

02:14:43.199 --> 02:14:51.760
>> H Why, man? Ah,

02:14:48.159 --> 02:14:55.040
what? Okay. My question is, if you're

02:14:51.760 --> 02:14:58.560
going to put the work into creating it,

02:14:55.040 --> 02:15:01.760
why so few? You know, there's more than

02:14:58.560 --> 02:15:02.880
70 people who'd be like Toyota gaming

02:15:01.760 --> 02:15:11.679
chair and just do it. >> 3500 >> more than 70 for sure. Come on.

02:15:09.280 --> 02:15:14.000
>> Toyota fanboys with money. >> And the Toyota Crown,

02:15:12.800 --> 02:15:18.159
>> you know, they didn't spend that much on their car. So, >> the Toyota Crown is one of those like

02:15:16.320 --> 02:15:20.480
super fancy cars, right? >> Uh I actually

02:15:19.599 --> 02:15:27.400
>> I'm pretty sure it is. >> Don't know what's a Toyota Crown.

02:15:23.360 --> 02:15:27.400
>> I thought they were really nice.

02:15:28.639 --> 02:15:35.679
Yeah, it according to AI, the Toyota Crown Hybrid sedan starts at around

02:15:33.920 --> 02:15:40.159
55,000 Canadian dollars.

02:15:37.920 --> 02:15:43.760
So, no, not even. Like I said, they bought a Toyota, so they clearly didn't

02:15:41.840 --> 02:15:48.719
overpay for their car, so they can afford a fancy chair, I guess. I don't

02:15:46.719 --> 02:15:52.960
know. >> Is this a plug-in hybrid?

02:15:52.560 --> 02:15:57.920
>> Is it? >> What? The chair? >> No, the car. >> Oh. Oh, I'm

02:15:55.760 --> 02:16:02.239
>> so a hybrid system. >> If it doesn't say plug-in hybrid, then

02:16:00.239 --> 02:16:06.719
it's just a regular hybrid. >> Powertrains, limited models, blah blah.

02:16:04.159 --> 02:16:08.800
Hybrid system, turbocharged, hybrid, max. Yeah. No, no, they're hybrid, not

02:16:08.000 --> 02:16:12.599
plugging hybrid. >> Damn. >> Sorry, Luke.

02:16:13.040 --> 02:16:18.239
>> All right. The show is brought to you by Squarespace. Whether it's a business or

02:16:16.719 --> 02:16:22.079
a hobby, if you want to share what you're doing with the world, a website

02:16:19.840 --> 02:16:27.520
goes an awful long way. And our sponsor Squarespace is still here to help you.

02:16:25.040 --> 02:16:31.280
You can do it yourself without the stress or headache of coding or figuring

02:16:29.440 --> 02:16:34.880
out the business aspect of running a site with Squarespace. They're like a

02:16:33.519 --> 02:16:37.920
partner that way. They've got a ton of templates to help you get started. Or

02:16:36.880 --> 02:16:43.120
you can even use their design intelligence tool to create something personal by just answering a few

02:16:40.960 --> 02:16:46.719
questions about your business. You can also run your business through their

02:16:44.479 --> 02:16:51.040
platform thanks to direct invoicing with payment options like direct debit, Apple

02:16:48.479 --> 02:16:55.040
Pay, and more. And even if your brand name is followed by.com, or even if your

02:16:53.439 --> 02:16:58.559
brand name followed by.com is already taken, Squarespace can help you pick

02:16:56.639 --> 02:17:02.319
from millions of domains so you can get something that's both searchable and

02:17:00.319 --> 02:17:05.280
easy to remember. And once your site's up and running, you can keep track of

02:17:03.840 --> 02:17:09.040
its performance with a variety of analytic tools that Squarespace

02:17:07.040 --> 02:17:11.840
provides. So start building your website today and get 10% off your first

02:17:10.960 --> 02:17:15.760
purchase by visiting squarespace.com/wan.

02:17:14.639 --> 02:17:20.880
Finally, the show is brought to you by Ninja 1. If you manage more than a handful of machines, you probably know

02:17:19.359 --> 02:17:24.559
that it can be a bit of a nightmare keeping everything patched, monitored,

02:17:22.479 --> 02:17:27.920
and under control without that becoming a full-time job on its own. Well, our

02:17:26.559 --> 02:17:33.359
sponsor, Ninja 1, lets you handle endpoint management, patch management,

02:17:29.760 --> 02:17:35.439
remote access, and

02:17:33.359 --> 02:17:41.120
um and what I I assume this is backup.

02:17:39.599 --> 02:17:44.559
I must be >> from a single console. I got Okay, they

02:17:43.120 --> 02:17:48.080
they do that. So, that must be It just says back in my notes. Yeah,

02:17:46.399 --> 02:17:53.920
>> from a single console, whether that's for Windows, macOS, Linux servers, or

02:17:51.120 --> 02:17:58.719
mobile devices. Ninja 1 was built for IT teams and MSPs who were tired of

02:17:56.319 --> 02:18:02.800
metaphorically duct taping a bunch of tools together. It's been rated number

02:18:00.639 --> 02:18:07.599
one by users across 14 IT management categories on G2 in the spring of this

02:18:05.200 --> 02:18:12.000
year and is used by over 35,000 customers across more than 140

02:18:09.760 --> 02:18:15.679
countries. And the best part, you don't have to take my word for any of it. You

02:18:13.439 --> 02:18:19.599
can try it for free with no credit card, no sales pressure. Just go to

02:18:17.120 --> 02:18:25.760
ninjawone.com or click the link in the description to start your free trial.

02:18:23.120 --> 02:18:28.000
We got a couple more topics still, too. Do we?

02:18:26.319 --> 02:18:32.960
>> A bank robber is trying to get out of his conviction by claiming that geoence

02:18:31.200 --> 02:18:36.240
warrants are a violation of his constitutional rights. This is down in

02:18:34.719 --> 02:18:40.559
the states. The Supreme Court is hearing this case on whether a geoence warrant

02:18:39.200 --> 02:18:43.599
violates the Fourth Amendment's protection against unreasonable searches.

02:18:42.800 --> 02:18:50.559
>> What is that? >> The case uh well, here we'll get to it. The case stems from a 2019 bank robbery

02:18:48.240 --> 02:18:56.319
in Richmond, Virginia, where a man made off with $195,000.

02:18:53.439 --> 02:19:01.840
Police had no leads until they served a geoence warrant on Google, which handed

02:18:59.200 --> 02:19:06.240
over location data for every device that was in the area around the time of the

02:19:04.399 --> 02:19:11.280
robbery, which eventually led to the man's arrest when they found a bunch of

02:19:08.800 --> 02:19:15.280
cash with them. So context of geoffence warrants if you

02:19:13.200 --> 02:19:19.599
need it. It's police draw a virtual circle around a crime scene, pick a time

02:19:17.519 --> 02:19:23.280
window and then ask a tech company like Google to hand over data on every device

02:19:21.519 --> 02:19:28.639
that was inside that circle during that time. Practical usage tends to follow

02:19:25.920 --> 02:19:32.240
these stages. Initial sweep gives police anonymized location pings and timestamps

02:19:30.639 --> 02:19:36.160
for every device within the circle identified only by numerical IDs. Police

02:19:34.639 --> 02:19:39.920
then flag any devices that look suspicious based on movement patterns

02:19:37.920 --> 02:19:43.519
and go back to the tech company with a follow-up request to unmask those

02:19:42.160 --> 02:19:47.359
specific accounts, getting the email addresses, phone numbers, and usernames

02:19:45.280 --> 02:19:50.880
that are tied to them. In the case of Google, this data comes from Google's

02:19:48.960 --> 02:19:54.560
location history feature, which technically requires you to opt in, but

02:19:52.960 --> 02:19:59.040
most people who use Google Maps or other Google services are already sharing this

02:19:56.479 --> 02:20:03.280
information. So, the plaintiff's lawyer argued that even anonymized location

02:20:01.280 --> 02:20:06.399
data acts like a type of fingerprint since your specific moving pattern

02:20:04.800 --> 02:20:10.560
movement patterns can be used to identify you. The DOJ countered that

02:20:08.640 --> 02:20:14.640
location data just represents public movements that anyone could observe. So,

02:20:12.560 --> 02:20:18.560
the Fourth Amendment defense shouldn't apply. Uh, the discussion question here

02:20:16.640 --> 02:20:22.240
is that the justices seem split and generally reluctant to wait into how the

02:20:20.479 --> 02:20:25.240
Fourth Amendment operates in today's world.

02:20:25.359 --> 02:20:33.760
This one is complicated.

02:20:30.800 --> 02:20:36.960
>> Yeah. Why do criminals keep bringing identifiable phones to crime scenes?

02:20:35.840 --> 02:20:43.520
>> Yeah. >> A very complicated question that I really will never understand. But then

02:20:40.399 --> 02:20:47.520
also also

02:20:43.520 --> 02:20:50.640
why am I able to be tracked

02:20:47.520 --> 02:20:53.840
in a personal personally identifiable

02:20:50.640 --> 02:20:56.479
way by something that supposedly cares

02:20:53.840 --> 02:21:00.560
about my privacy. >> Yeah, I don't like that. But then

02:20:58.000 --> 02:21:05.760
counter counterpoint if you're an do well taking money that

02:21:03.439 --> 02:21:08.800
ultimately you know we all pay for like I'm not an American and I don't bank at

02:21:07.280 --> 02:21:13.840
that bank so I have nothing to do with like that specific case but at the end

02:21:10.720 --> 02:21:15.439
of the day we all pay for crime like

02:21:13.840 --> 02:21:18.880
society um

02:21:16.880 --> 02:21:22.640
>> do I mind if >> everyone there got their information

02:21:21.200 --> 02:21:27.359
flagged and taken by the government >> but then counter counter counter point

02:21:25.359 --> 02:21:31.439
yes to Luke's point that's exact what the lawyer's arguing >> and who's defining how big the circle

02:21:30.399 --> 02:21:38.720
is. >> So, what if they're like, "There was a bank robbery in North Vancouver. What if

02:21:36.560 --> 02:21:44.160
what if we circled the entire greater Vancouver area and just grabbed

02:21:41.520 --> 02:21:49.840
everything and use this data for multiple other things going on and also

02:21:46.319 --> 02:21:51.920
so I can track my wife's phone to see if

02:21:49.840 --> 02:21:54.000
she's going somewhere that I don't like or I'm not going to tell anyone that I

02:21:53.439 --> 02:21:57.760
just did that." >> What if there was no bank robbery? What if there was a protest?

02:21:57.439 --> 02:22:04.359
>> Yeah. >> Now all of a sudden it can become a tool for government crackdown.

02:22:07.840 --> 02:22:16.160
>> I actually do not envy the Supreme Court

02:22:12.640 --> 02:22:20.720
justices as they navigate this one.

02:22:16.160 --> 02:22:22.560
To be clear, I have no pity for buddy

02:22:20.720 --> 02:22:27.439
who got busted stealing a bunch of money from a bank.

02:22:24.800 --> 02:22:34.479
just desserts. However, the methods do matter if you

02:22:31.680 --> 02:22:40.560
want to even maintain the branding of having a free society.

02:22:37.439 --> 02:22:42.080
And this one is complicated.

02:22:40.560 --> 02:22:46.399
>> They're just exercising their freedom to all of your information and data, knowing where you are all the time.

02:22:44.880 --> 02:22:51.439
>> Oh. Oh, that's what you think freedom is. >> It's just it's just freedom.

02:22:49.359 --> 02:22:55.920
I don't know what you're talking about. >> Yeah, man. freedom is uh it's she's a

02:22:54.000 --> 02:23:02.080
complicated she's a complicated concept. I read a really interesting essay

02:22:57.359 --> 02:23:04.240
recently on the um the ways that the

02:23:02.080 --> 02:23:09.359
word and the concept of freedom have been kind of perverted

02:23:06.479 --> 02:23:14.319
um from the way that a lot of people kind of intended them in the in the in

02:23:12.000 --> 02:23:19.439
the in the creation of sort of the the western model of free society.

02:23:16.160 --> 02:23:22.319
>> Sure. and how they've become kind of

02:23:19.439 --> 02:23:30.479
divorced from the responsibilities that accompany that freedom and how we're not

02:23:26.080 --> 02:23:33.840
sure if that freedom will survive. Um,

02:23:30.479 --> 02:23:36.479
an unwillingness to also

02:23:33.840 --> 02:23:41.120
exercise the freedom responsibly and be a part of be a part of that functioning

02:23:39.439 --> 02:23:45.920
free society. It's a really interesting essay. I wish I could find the link for

02:23:43.040 --> 02:23:49.280
you guys, but um yeah, fascinating. It doesn't come to a conclusion because

02:23:47.840 --> 02:23:53.280
it's because it's complicated. >> Archangel of death said, "As the saying

02:23:51.200 --> 02:23:56.960
goes, your freedom ends when the freedom of the big corporation and government

02:23:55.120 --> 02:24:02.960
starts or something like that." >> Yeah, sure.

02:24:00.240 --> 02:24:07.920
Just so that everyone's clear, Archangel of Death meant that with a big fat

02:24:05.120 --> 02:24:11.520
slashs. Okay, relax. >> Sometimes.

02:24:10.160 --> 02:24:15.680
Well, yeah, but >> your freedom to have your IP not ripped

02:24:13.200 --> 02:24:17.840
off just got obliterated by every single AI company on the planet.

02:24:17.200 --> 02:24:23.600
>> Well, yes. >> Oh, >> Luke, it's good news. Wow.

02:24:22.720 --> 02:24:30.880
>> Right. Okay, >> calm down. >> Next topic. >> Android developers are revoling against

02:24:28.319 --> 02:24:34.880
Google's 2026 sideloading registration mandate. Starting September 2026, Google

02:24:33.600 --> 02:24:39.040
is fundamentally changing how sideloading works on Android. Right now,

02:24:37.520 --> 02:24:43.280
installing an app from outside the Play Store is as simple as downloading an APK

02:24:40.960 --> 02:24:47.280
and tapping install. Sort of. You have to enable unknown developers, whatever.

02:24:45.280 --> 02:24:50.800
Whatever. Whatever. But sort of. Under the new rules, every developer, even

02:24:49.200 --> 02:24:54.000
hobbyists and open source contributors who never touch the Play Store, must

02:24:52.399 --> 02:24:59.439
register with Google, verify their identity with governmentissued ID, register their app signing keys, agree

02:24:56.800 --> 02:25:04.000
to Google's terms, and pay a $25 fee. If they don't, their app gets silently

02:25:01.760 --> 02:25:10.240
blocked from installing on any certified Android device. Google says that power

02:25:07.120 --> 02:25:12.560
users can still install unverified apps,

02:25:10.240 --> 02:25:15.680
but the new advanced flow requires enabling developer mode by tapping the

02:25:14.080 --> 02:25:19.840
build number seven times, navigating through multiple setting screens, and

02:25:17.439 --> 02:25:26.399
waiting out a mandatory 24-hour cooling off period. Over 37 organizations,

02:25:23.359 --> 02:25:28.240
including the EFF, Foid, Proton,

02:25:26.399 --> 02:25:32.479
Nextcloud, and the Tour Project, have signed an open letter demanding that

02:25:29.760 --> 02:25:36.800
Google reverse course. Foid calls the mandate existential since its entire

02:25:34.720 --> 02:25:41.200
model relies on volunteer and pseudonmous developers who have no

02:25:39.439 --> 02:25:45.120
reason or desire to register with Google. The rollout starts in Brazil,

02:25:43.439 --> 02:25:50.240
Indonesia, Singapore, and Thailand with a global expansion planned for 2027.

02:25:47.840 --> 02:25:56.080
Custom ROMs like Graphine OS and Lineage OS are unaffected.

02:25:54.080 --> 02:25:59.520
Discussion question. If installing an app on your own phone now requires a

02:25:57.920 --> 02:26:03.600
24-hour waiting period in developer mode, can Google still call Android an

02:26:01.680 --> 02:26:07.840
open platform? >> I mean, I think they can still call it

02:26:05.200 --> 02:26:11.520
whatever they want, but is it one? Um, I don't know. I think this is something

02:26:09.359 --> 02:26:14.000
that would kind of push me to do the same thing I'm doing with Linux right

02:26:12.720 --> 02:26:20.800
now on my phone, which is just try alternative options. >> Let me pitch you some food for thought.

02:26:18.640 --> 02:26:25.520
With this change, would you be more comfortable recommending an Android

02:26:22.160 --> 02:26:26.399
phone for your grandpa or grandma?

02:26:25.520 --> 02:26:34.000
>> No. >> Really? I would. Straight up. 24-hour

02:26:30.960 --> 02:26:38.880
waiting period for random APKs. The way

02:26:34.000 --> 02:26:40.960
that scams work? Zero question.

02:26:38.880 --> 02:26:51.200
Now, does that mean that I support the move? Not necessarily. I see lots of

02:26:44.640 --> 02:26:54.240
problems with it, but I also can see a

02:26:51.200 --> 02:26:56.479
good faith argument for why Google wants

02:26:54.240 --> 02:27:02.319
to unmask developers on the platform. And they are still offering a way that

02:26:59.280 --> 02:27:04.319
you can install anything.

02:27:02.319 --> 02:27:10.000
>> A 24-hour waiting period would functionally kill the like, oh yeah,

02:27:07.840 --> 02:27:13.280
Grandpa, just go here and install this and click through this and click through

02:27:11.359 --> 02:27:15.040
this. I'll wait on the phone with you while you dump all of your life savings

02:27:14.720 --> 02:27:20.399
into >> a lot of those scams are multi-day long. >> Okay. Not all.

02:27:19.120 --> 02:27:25.680
>> That's totally fair. That's what you're >> It would make it so much more work.

02:27:22.160 --> 02:27:29.760
>> Yes, it definitely would. I um I would

02:27:25.680 --> 02:27:32.640
like to see this as a

02:27:29.760 --> 02:27:36.080
feature >> that is like family management

02:27:35.040 --> 02:27:40.319
controllable. >> Interesting. So like a fleet management

02:27:38.240 --> 02:27:45.680
feature. Okay, so here's my question though because

02:27:43.120 --> 02:27:50.960
who is the administrator of that though? Like as as a as a head of family like

02:27:48.399 --> 02:27:53.439
techy dude, I hear that and I go, "Oh yeah, that totally makes sense. That's

02:27:52.160 --> 02:28:01.399
how I would manage it through family link and I would do this and I would do that." But most people's structure is

02:27:57.359 --> 02:28:01.399
not necessarily like that.

02:28:02.800 --> 02:28:08.319
Like I can this is one of those ones where on the surface

02:28:07.520 --> 02:28:14.960
>> I can see >> this feels like sacrificing freedom for security in a way that I do not like. Um

02:28:12.560 --> 02:28:18.880
it does but I I think if you put that in the power of users, yeah, you'll still

02:28:17.439 --> 02:28:26.240
lose some people because they're not going to have that type person in their family or whatever. But in my experience

02:28:22.479 --> 02:28:28.800
of my my grandpa living far away in a

02:28:26.240 --> 02:28:33.920
retirement village effectively, there was like an IT person thing. I don't

02:28:32.560 --> 02:28:38.080
even know what I would call it. It was like the person that everyone in that

02:28:36.319 --> 02:28:40.640
town because it was it was a pretty sprawling area, but it was a and

02:28:39.520 --> 02:28:44.640
everyone had their own homes and stuff, but it was a retirement focused area. I

02:28:43.120 --> 02:28:47.439
don't even know. I'm sure it has a name. I don't know what it is. Um

02:28:46.160 --> 02:28:51.680
>> retirement community. >> Sure. Um and I don't know if this

02:28:49.359 --> 02:28:58.080
person's shop was like on site in that community or not, but like just

02:28:53.200 --> 02:28:59.920
everybody knew who he was. Um, and he

02:28:58.080 --> 02:29:04.000
had a particular way of dealing with everyone, which was actually like kind

02:29:01.920 --> 02:29:07.680
of neat because it was like the only person everybody really used. Word of

02:29:06.000 --> 02:29:12.560
mouth was everywhere that like if you were have like if your laptop was screwed up, he'd just exchange you

02:29:10.800 --> 02:29:15.359
>> and then fix yours and like sell it to somebody else or whatever. Like he was

02:29:14.240 --> 02:29:20.640
pretty good about just like keeping people going. and he had basically like

02:29:17.359 --> 02:29:22.319
team viewer on everyone's systems,

02:29:20.640 --> 02:29:25.920
>> which I know, >> but he could tap in if he like needed to

02:29:24.640 --> 02:29:29.680
help you with something cuz there would often be like, oh, there's something going on with whatever.

02:29:28.160 --> 02:29:32.720
>> That's what our angel of death says. 24 hours is enough time for my elderly

02:29:31.280 --> 02:29:36.160
family members to call me just to check if they're doing the right thing. I'm

02:29:34.560 --> 02:29:43.280
still fundamentally against it for other reasons. And I think that actually summarizes sort of where I'm at right

02:29:41.600 --> 02:29:45.840
now. I haven't had a lot of time to think about it. My reason for this very

02:29:45.120 --> 02:29:48.960
long story >> Oh, sorry. >> Is whoever that dude was

02:29:48.560 --> 02:29:53.840
>> Yeah. >> could maybe enable this thing for these people. >> But he was a good actor. What if he

02:29:52.560 --> 02:29:56.560
wasn't? >> Yeah. >> Then disaster.

02:29:56.160 --> 02:30:02.720
>> And >> I mean, if you're not a good actor and you're in that dude's position, this

02:30:00.160 --> 02:30:06.720
24-hour window will not stop you. >> This is true. Fools and Horses has a

02:30:04.880 --> 02:30:12.560
really good point and asks asks the question, has Android gotten so large

02:30:10.160 --> 02:30:17.359
that the risk of being called negligent for allowing these things and for not

02:30:14.880 --> 02:30:22.000
putting obstacles in the way is greater than the risk of their disgruntled

02:30:20.000 --> 02:30:27.439
customers over this loss of freedom, loss of openness. Um, how much of the

02:30:25.120 --> 02:30:31.359
market would they really lose? And I think that's got to be the question that

02:30:29.520 --> 02:30:35.520
Google's asking themselves as they navigate this decision. And I I suspect

02:30:33.840 --> 02:30:39.120
the answer for how many people they're going to lose is

02:30:37.680 --> 02:30:44.240
extremely small. >> Yeah. >> Um

02:30:42.000 --> 02:30:49.920
and and that's not like that's not me saying that I support the decision. I'm

02:30:46.640 --> 02:30:52.160
just saying that that's the reality is

02:30:49.920 --> 02:30:56.640
that most people are not even watching the WAN Show, not even aware of this,

02:30:54.720 --> 02:31:03.120
would have never sideloadaded an APK anyway unless some rando told them to do

02:30:59.680 --> 02:31:06.319
it, in which case this was probably a

02:31:03.120 --> 02:31:10.960
thing. Um,

02:31:06.319 --> 02:31:11.840
so Greak asks, "Why is this also?" Okay,

02:31:10.960 --> 02:31:16.399
sorry, they're responding to someone else. Yeah, never mind. Um, yeah, Ann

02:31:14.720 --> 02:31:21.200
White says it won't be zero, but yeah, it will be small. Uh, leaving one's most

02:31:19.200 --> 02:31:24.560
experienced OS and just like switching is like kind of a pain. Like honestly,

02:31:22.640 --> 02:31:29.200
that's why Ivonne's still on iOS. Not because she prefers it, but just after

02:31:26.800 --> 02:31:33.680
she did the iPhone challenge, she's just like, uh, switching phones is such a

02:31:31.439 --> 02:31:38.479
pain in the butt. It really is. And just I I do think it's going to be pretty

02:31:35.600 --> 02:31:46.960
negligible. Arcomian says leave to what? iOS. I mean, graphine OS is an option.

02:31:42.399 --> 02:31:48.240
iOS. Um, I saw I saw a cool uh this was

02:31:46.960 --> 02:31:54.160
cool. This was not really good news enough to be good newsws W show, but um

02:31:51.600 --> 02:31:58.880
Windows phone Android launcher someone's uh someone is working on or

02:31:57.120 --> 02:32:02.960
um made Oh, no. Apparently this is old.

02:32:01.120 --> 02:32:06.800
Just uh an Android launcher that like looks a lot like Windows Phone, which I

02:32:04.960 --> 02:32:10.160
thought was pretty cool. Anyway, that's it. That was a little highlight for

02:32:08.080 --> 02:32:14.080
that. I I don't think we're gonna reach a conclusion on this one because I don't

02:32:12.240 --> 02:32:22.960
think that it's it's cut and dried. >> Sounds simple. >> I do I do appreciate Google's um

02:32:20.479 --> 02:32:29.439
position that they are still allowing sideloading with these caveats. And for

02:32:26.560 --> 02:32:33.120
me, for my use of Android, the handful of times that I've needed to sideloadad,

02:32:31.439 --> 02:32:37.439
this would have been good enough. This would have been a minor inconvenience.

02:32:34.640 --> 02:32:40.960
>> Where does the slope end? Are we on the slipper? So, so,

02:32:39.359 --> 02:32:43.359
>> and I can't tell. I don't know that we are. I'm not trying to claim necessarily

02:32:42.560 --> 02:32:49.600
that we are. >> I don't either. >> There are there are times where I have been like, "This is a slope." I don't

02:32:47.680 --> 02:32:57.120
know that this one is, but it it smells like one. >> It Well, okay. In a vacuum, I would push

02:32:54.319 --> 02:33:01.040
back. If this was the only change that Google had made to Android over the last

02:32:58.800 --> 02:33:03.439
5 years, then I'd be like, "Luke, come on.

02:33:01.840 --> 02:33:07.840
>> They've been good stewards. They've done this. They've done that."

02:33:05.920 --> 02:33:12.000
In the context of everything that Google has done though with Chrome and with

02:33:09.439 --> 02:33:17.840
Android um with their products in general over I mean the last while it's

02:33:16.399 --> 02:33:20.399
a lot harder for me to do that. I they've lost my trust.

02:33:19.520 --> 02:33:26.319
>> Yeah. >> And I think that's a big part of it is like they've there was a time when

02:33:24.560 --> 02:33:31.120
Google might have done this and said trust me bro I got you. And I said okay

02:33:28.800 --> 02:33:36.319
>> I would have I still have a little bit of that with them but not as much as

02:33:32.640 --> 02:33:39.760
before. I I feel like they uh Let's

02:33:36.319 --> 02:33:41.520
check in on Killed by Google.

02:33:39.760 --> 02:33:45.240
I feel like they've been slowing down, but I'm not sure.

02:33:50.000 --> 02:33:55.920
Okay, so 2026 and beyond is these. Oh,

02:33:54.560 --> 02:34:04.000
okay. Yeah, that's actually not that much >> compared to I mean 2024

02:34:01.439 --> 02:34:08.319
being like what all of this

02:34:05.120 --> 02:34:11.040
>> the postcoid time was a big was a time

02:34:08.319 --> 02:34:13.840
of a lot of consolidation for the big tech companies.

02:34:11.840 --> 02:34:17.680
>> God >> team sizes shrank projects were

02:34:15.920 --> 02:34:22.080
abandoned. It wasn't just Google at that time.

02:34:19.600 --> 02:34:28.479
>> Wow. Fascinating. Yeah. that Google is like

02:34:24.800 --> 02:34:30.080
the the corporate uh embodiment of throw

02:34:28.479 --> 02:34:36.560
things at the wall and see what sticks, man.

02:34:32.640 --> 02:34:39.040
Yeah. And this next uh after dark

02:34:36.560 --> 02:34:44.880
segment is the embodiment of throw questions at us and producer

02:34:42.080 --> 02:34:50.000
>> Dan. He's a Rubbermaid bin shelf now. Oh, there he is. Uh throw questions at

02:34:46.960 --> 02:34:53.040
us and see what sticks.

02:34:50.000 --> 02:34:55.760
I have become square.

02:34:53.040 --> 02:35:01.120
Let me get us changed over uh after dark. And I have to push this button,

02:34:58.800 --> 02:35:05.359
too. Sorry, that came out of nowhere. I was unprepared.

02:35:03.520 --> 02:35:09.120
You good? Hey, LLD.

02:35:07.760 --> 02:35:13.600
I've been thinking about this lately. badminton is super popular around the

02:35:10.960 --> 02:35:19.280
world, but most pro players, aside from the very top, don't seem to make nearly

02:35:16.240 --> 02:35:24.000
as much as athletes in other big sports.

02:35:19.280 --> 02:35:27.040
I think about this a lot. So, take this

02:35:24.000 --> 02:35:32.479
for the semi-informed

02:35:27.040 --> 02:35:34.880
um rant that it kind of is. Um I think

02:35:32.479 --> 02:35:40.000
it's a number of problems and I think that BWF uh so badminton world

02:35:37.920 --> 02:35:44.160
federation is doing some things right to address it. Uh for for instance they

02:35:42.319 --> 02:35:49.840
actually just recently changed the scoring format. So in the in the olden

02:35:47.760 --> 02:35:55.520
days so I guess this ended ended in the '9s or early 2000s I think badminton was

02:35:52.880 --> 02:35:59.680
done with service point. So that is that you can only score a point when you

02:35:57.760 --> 02:36:06.319
begin the rally with the serve. Okay. So, it was service point um sets of 15

02:36:03.600 --> 02:36:10.640
and then best of three sets. The problem with service point is that the games

02:36:08.000 --> 02:36:14.960
would sometimes drag on forever. It was an enormous burden on the athletes. And

02:36:12.640 --> 02:36:19.760
when you consider that often times during tournaments they're playing

02:36:16.720 --> 02:36:21.920
backto back to back uh across subsequent

02:36:19.760 --> 02:36:26.960
days, um it could put you at a major disadvantage if one of your if one of

02:36:24.479 --> 02:36:31.680
your sets dragged on for a really long time because you have to win by two. So

02:36:29.040 --> 02:36:38.800
a service point win by two means that you could just defensively carry things

02:36:34.800 --> 02:36:41.200
forever and it really rewarded endurance

02:36:38.800 --> 02:36:45.280
and less aggressive play. So it was changed to rally point so you can win a

02:36:43.520 --> 02:36:49.920
point on any service whether it's yours or the other players. Um so I believe in

02:36:48.319 --> 02:36:56.399
the I believe in the 2000s. Don't quote me on that but I believe it was the 2000s to encourage a more aggressive

02:36:54.319 --> 02:37:01.359
style of play but to make sure the matches weren't crazy short. It was

02:36:58.000 --> 02:37:05.280
changed to 21 points per set.

02:37:01.359 --> 02:37:07.920
I think the 21 point service point or

02:37:05.280 --> 02:37:13.760
excuse me 21 point rally point format still best of three was horrible for the

02:37:11.520 --> 02:37:17.680
game, not for the players. The players like it and they actually from my

02:37:15.439 --> 02:37:22.640
understanding still mostly like it and there's a lot of resistance to the new

02:37:19.840 --> 02:37:28.479
scoring format which is 15 points rally point. Um,

02:37:25.920 --> 02:37:36.319
but why I think it's so detrimental to the sport is it's really boring to watch

02:37:32.160 --> 02:37:38.800
a 21point match. I mean, tell me how

02:37:36.319 --> 02:37:42.240
important in hockey, how important is the first goal to you as a player,

02:37:40.800 --> 02:37:47.280
>> right? Yeah. Extremely >> extremely important. From the opening

02:37:44.399 --> 02:37:50.160
faceoff, from that moment, the entire game could be riding on the

02:37:48.960 --> 02:37:54.479
line. There's also a significant amount of like fear at any point in time that something might happen which could

02:37:53.280 --> 02:37:59.520
result in a goal. >> Okay. >> Like if you see if you're if you're you

02:37:56.800 --> 02:38:03.439
know if the the enemy team is in your team zone and you're a fan, you're

02:38:01.760 --> 02:38:08.080
shaking in your boots >> at most stages of the game.

02:38:04.960 --> 02:38:11.600
>> Yes. Okay. So counterpoint. What if a

02:38:08.080 --> 02:38:13.120
hockey game was played to 21 goals?

02:38:11.600 --> 02:38:17.600
>> Yeah. You don't >> the first goal. Are you

02:38:15.600 --> 02:38:20.319
>> almost doesn't matter. So what's happened and especially

02:38:18.800 --> 02:38:27.359
>> you got to set the tone >> especially in a format that um is is

02:38:24.720 --> 02:38:31.680
like a seated bracketed tournament where your top seeds are playing against your

02:38:29.600 --> 02:38:37.359
bottom seeds up until you reach realistically like the the round of 16

02:38:34.399 --> 02:38:44.960
or quarterfinals. Um you end up with a lot of boring play that no one cares

02:38:41.120 --> 02:38:46.479
about. Um because the first like little

02:38:44.960 --> 02:38:51.359
bit of the game is everyone just kind of like settling in and then after that

02:38:49.359 --> 02:38:55.359
you've got like a very obvious who's going to win and who's not going to win

02:38:53.040 --> 02:39:01.760
and there's very little upset in the rally point system because a better

02:38:58.720 --> 02:39:04.319
player will just win more points and

02:39:01.760 --> 02:39:10.160
there's less like oh but hold on he could defend he could defend their

02:39:06.960 --> 02:39:13.200
service regain the serve and like like

02:39:10.160 --> 02:39:15.280
like scrape his way back into the game.

02:39:13.200 --> 02:39:18.640
You don't really get as many momentum swings and you get don't get as many

02:39:16.720 --> 02:39:22.640
upsets and you get a lot of the game that's just kind of like people are the

02:39:20.720 --> 02:39:27.600
players themselves are kind of tuned out. They're not going as hard and I

02:39:25.359 --> 02:39:31.680
think it's really boring to watch. The other thing that contributes to

02:39:28.800 --> 02:39:38.399
badminton being boring to watch is the camera is is the broadcast. The camera

02:39:33.920 --> 02:39:40.160
angles suck. They do such a poor job.

02:39:38.399 --> 02:39:43.680
But I remember showing someone like a really high level badminton match at one

02:39:41.920 --> 02:39:49.680
point and I'm going, "Well, why are they just like lobbing it to each other?" And

02:39:45.760 --> 02:39:52.800
I'm like, "Bro, if I hit those shots to

02:39:49.680 --> 02:39:55.359
you on a court and you like properly

02:39:52.800 --> 02:40:00.240
understood from the actual movement how far they're going, they travel way

02:39:57.680 --> 02:40:04.479
farther in way less time than top level tennis players, but you don't know that

02:40:02.080 --> 02:40:07.600
from watching it. You can't tell like the sheer athleticism of the game is not

02:40:06.479 --> 02:40:11.920
apparent from >> farther. I don't think that's true. >> Way farther. It's not even close. You

02:40:10.720 --> 02:40:16.080
cannot think it's true, but it's >> in the amount of time. I think you're totally right. But the distance,

02:40:14.640 --> 02:40:20.000
>> it's not even close. >> I promise you. Men's sing. So, it's a

02:40:18.240 --> 02:40:22.560
men's singles to men's singles, like top level Olympic match comparison. Someone

02:40:22.000 --> 02:40:26.560
did the math. >> Total distance moved. >> Total distance moved. >> Okay. I think Yeah, I think we're

02:40:25.600 --> 02:40:32.720
talking about different things, but >> total distance moved is higher and it's

02:40:29.520 --> 02:40:34.640
in less time. Both of those things. It's

02:40:32.720 --> 02:40:37.359
crazy like what they're doing out there and the explosiveness of the movement.

02:40:36.160 --> 02:40:44.640
It's a great game. It's a wonderful game. Um, you can't tell the the the the

02:40:41.760 --> 02:40:47.200
angles do it no service whatsoever. And especially the English- speakaking

02:40:45.920 --> 02:40:51.840
commentators, they might as well be commentating golf.

02:40:50.080 --> 02:40:55.760
So, I'm coming around to my point finally. >> You should commentate a game.

02:40:55.040 --> 02:41:00.160
>> It'd be fun. >> I I'm not experienced. I'm not like I It

02:40:58.560 --> 02:41:04.720
would still be very amateur and like crappy and boring. Bring one, this is

02:41:02.560 --> 02:41:10.319
how game casting does it. Bring one person on who? Bring one of the people

02:41:07.520 --> 02:41:14.880
from Babon Insights and you

02:41:12.160 --> 02:41:18.479
and then you have like you're the energy and they're the next person.

02:41:17.280 --> 02:41:22.720
>> You know what? That's kind of an interesting idea. It's kind of an interesting idea. I kind of I kind of

02:41:21.359 --> 02:41:27.680
like the idea. >> Um anyway, I'm coming around to my point

02:41:25.359 --> 02:41:33.040
here. So, you ask why the players aren't paid as much. And it's because, in my

02:41:30.640 --> 02:41:38.720
humble opinion, I see a lot of resistance from the players to rule

02:41:36.000 --> 02:41:41.920
changes that would make the game more entertaining to watch. Where does money

02:41:41.200 --> 02:41:46.880
come from? >> Interesting. >> It doesn't necessarily come from people

02:41:45.520 --> 02:41:50.080
playing the game in their backyards. They'll go and they'll buy a racket from

02:41:48.560 --> 02:41:54.160
Yonx or Victor or whatever. So there's revenue coming into the companies that

02:41:52.080 --> 02:41:57.280
are that are sponsoring these events, but it's not necessarily attributable to

02:41:56.399 --> 02:42:03.520
the players. >> Yeah. >> It's not attributable necessarily to the broadcast except like you said to those

02:42:01.280 --> 02:42:07.359
very top players where the matches are interesting, where anyone could win. So

02:42:05.760 --> 02:42:11.520
I would actually like to see them go even farther in the reduction of points

02:42:09.680 --> 02:42:16.160
per set. I'd like to see something that's closer to like a tennis scoring

02:42:13.600 --> 02:42:20.640
system. Uh so for badminton because the rallies are generally shorter uh what

02:42:18.240 --> 02:42:27.280
I'd like to see is maybe like best of five sets but playing service point to

02:42:23.760 --> 02:42:30.319
like five points or seven points. So

02:42:27.280 --> 02:42:32.640
very very very short sets

02:42:30.319 --> 02:42:37.680
but that have service point in order to give an opportunity for upset victories

02:42:34.640 --> 02:42:39.520
because realistically even if I'm a much

02:42:37.680 --> 02:42:42.800
better badminton player than you I could make three mistakes

02:42:40.800 --> 02:42:45.439
>> if you know Yeah. I'm kidding. >> Yeah. But but I could make three

02:42:44.240 --> 02:42:49.760
mistakes. >> Now the pressure's on. >> Yeah. Yeah.

02:42:47.439 --> 02:42:53.840
>> Right. You create tension. I want tension and I want excitement the whole

02:42:52.399 --> 02:42:57.200
time I'm watching. Think about sports that are fun to watch that keep you on

02:42:55.840 --> 02:43:00.640
the edge of your seat the whole time you're watching. Anything could happen.

02:42:58.960 --> 02:43:04.319
>> Yeah. It's Yeah, it's always tension. >> Bad doesn't achieve that.

02:43:02.640 --> 02:43:09.040
>> All the ideas your idea is very interesting. All the ideas I've been trying to think of while sitting here I

02:43:07.280 --> 02:43:14.560
don't think work for the players at all. I had one where like if your rally gets

02:43:11.680 --> 02:43:19.760
>> far enough in it starts it becomes like worth more or something

02:43:17.120 --> 02:43:24.319
>> but like now you have players like counting on cords so it doesn't work.

02:43:22.640 --> 02:43:26.399
>> It would be kind of fun as like a video game but it doesn't work as like a

02:43:25.920 --> 02:43:32.720
sport. >> Yeah. Like and then and then if you get enough multiplier bonus you could have

02:43:30.479 --> 02:43:38.080
you could nuke your opponent from orbit with the geo positioning laser. If you

02:43:35.520 --> 02:43:44.160
if you go six six rally back and forth, you can like double jump.

02:43:41.760 --> 02:43:46.479
>> You could do a special a special combo move.

02:43:45.120 --> 02:43:49.600
>> Yeah. >> Um >> helicopter hit.

02:43:48.160 --> 02:43:53.040
>> Yeah. So there, sorry, that's my extremely long answer to what I think is

02:43:51.439 --> 02:43:59.040
wrong with badminton is it's not it's not fun enough to watch. >> A lot of sports have that problem.

02:43:55.920 --> 02:44:01.920
>> Yeah. It also has the problem of like

02:43:59.040 --> 02:44:07.359
being very very multinational and therefore

02:44:04.080 --> 02:44:09.439
um it being hard to get like good common

02:44:07.359 --> 02:44:12.479
language interviews >> for your various geographies of

02:44:11.680 --> 02:44:15.800
audience. >> Yeah. Um,

02:44:16.000 --> 02:44:25.279
it's tough. It like it's it's a funny thing because in general I I I find

02:44:21.680 --> 02:44:28.960
myself not liking the corporatization of

02:44:25.279 --> 02:44:31.279
sports. Like it it kind of sucks that

02:44:28.960 --> 02:44:34.479
Mlin Celibbrini doesn't play for the Vancouver Conucks given he's

02:44:33.200 --> 02:44:37.120
from here. >> He's like the most exciting player in

02:44:36.319 --> 02:44:44.520
hockey right now. >> Be pretty freaking cool if he did. >> I don't think I would mind that.

02:44:40.240 --> 02:44:44.520
>> That would be awesome. Um

02:44:45.920 --> 02:44:54.720
um and like the fact that Conor McDavid doesn't play for the Toronto Maple Leafs

02:44:51.120 --> 02:44:56.560
is like, you know, kind of ridiculous.

02:44:54.720 --> 02:44:59.439
Uh where where's where's Sid from? He's from he's from Nova Scotia, I think.

02:44:58.240 --> 02:45:03.840
Right. So the fact that the Hartford Whalers don't get to still exist and Sid

02:45:01.279 --> 02:45:08.000
plays for them, like come on, man. >> That was like Okay, so yeah, this is

02:45:06.560 --> 02:45:11.040
very true with hockey where like Americans will be like, "Oh, well we

02:45:09.920 --> 02:45:16.800
beat you." And it's like, yeah, your team has a lot of Canadians on it. But then baseball, you look at the Toronto

02:45:15.040 --> 02:45:19.520
Raptors and it was like, >> it's like, oh, the Canadians finally

02:45:18.160 --> 02:45:23.040
made it. It was like kind of >> Were there like two Canadians on the team or something?

02:45:21.600 --> 02:45:28.240
>> Yeah, it's kind of a lot of Americans. >> So So as much as I So as much as I don't

02:45:25.359 --> 02:45:33.680
love the corporatization of of sport where like the Vancouver Conucks is just

02:45:30.720 --> 02:45:36.640
a brand. It has no meaning. Like there was at one point there was more Swedes

02:45:35.279 --> 02:45:40.240
than Canadians on the team, which I don't mind. I have nothing against Swedes. I just

02:45:38.960 --> 02:45:44.399
>> historically been a big thing for Vancouver to have a like disproportionate amount of

02:45:42.640 --> 02:45:52.560
>> basically the Canucks were team Sweden at one point. >> Um and and so I don't like that.

02:45:49.200 --> 02:45:56.319
>> But what that does a really good job of

02:45:52.560 --> 02:45:59.520
is like getting people excited about,

02:45:56.319 --> 02:46:01.840
you know, like their team. Whereas when

02:45:59.520 --> 02:46:04.800
it's like the national team, if you don't happen to have a star player,

02:46:03.439 --> 02:46:08.880
especially in a more individual sport like badminton, there's like kind of

02:46:06.800 --> 02:46:14.960
nothing to cheer for. Whereas if you just, you know, had the, you know, the

02:46:11.200 --> 02:46:17.600
Malaysia aces and, you know, the the the

02:46:14.960 --> 02:46:22.319
the Canadian geese or, you know, like you had you you did more branding around

02:46:19.520 --> 02:46:25.520
it, then yeah, I think there's then I think there's a chance to to

02:46:24.560 --> 02:46:31.359
>> there's also >> to build long-term fandom. >> Yeah. Like people will identify like

02:46:29.279 --> 02:46:36.000
they'll wear the hat, you know, like I'm a I'm a Chargers fan, you know, I'm a

02:46:34.080 --> 02:46:41.040
Raptors guy. >> Nobody nobody very few people do that

02:46:38.880 --> 02:46:44.000
except like on the court like they'll they'll wear like, you know, a jersey or

02:46:42.640 --> 02:46:48.800
whatever for their favorite player, but there's not that that team branding. And

02:46:46.640 --> 02:46:52.960
it works. It works. I don't make the rules. It works.

02:46:51.040 --> 02:46:59.120
>> This is an ignorance thing. Is most of the world as interested in sports at all

02:46:55.439 --> 02:47:00.800
as North America is? Oh dude. Yeah. Like

02:46:59.120 --> 02:47:04.479
>> as a viewer, as a fan, >> dude. Like cricket in India, right?

02:47:03.439 --> 02:47:07.680
>> It's crazy. >> Is that them having a massive massive

02:47:06.479 --> 02:47:13.840
population? >> It's just crazy. >> Okay. >> And like dude, soccer.

02:47:11.840 --> 02:47:18.160
>> Soccer South America. Yes. Spectator 100%. Hund the Brits.

02:47:16.479 --> 02:47:24.640
>> Hyundai is pretty huge. >> Yeah. Huge.

02:47:22.319 --> 02:47:29.200
>> Oh yeah. Yeah. Agent Renzo, Japan loves baseball, dude. the way that Japan just

02:47:26.720 --> 02:47:32.880
kind of was like, "Oh, this American thing, nope, it's a Japanese thing now.

02:47:31.200 --> 02:47:37.520
By the way, the greatest player on the face of the earth is Japanese. He's an

02:47:35.200 --> 02:47:42.080
absolute god at absolutely everything." Like, Japan just exploded into the

02:47:40.479 --> 02:47:45.840
baseball scene. That's been that's been wild to watch over my lifetime.

02:47:43.680 --> 02:47:48.960
>> I just like whenever I'm traveling, literally anywhere that I've gone, I've

02:47:47.520 --> 02:47:52.880
never been to India, but anywhere that I've gone, you don't see it.

02:47:51.760 --> 02:47:58.880
>> H interesting. >> That's what I mean.

02:47:56.160 --> 02:48:02.720
Like if if like in Canada, you go basically anywhere and you're going to

02:48:00.720 --> 02:48:06.080
see somebody wearing something to do with some sports team. In America, same

02:48:05.600 --> 02:48:10.880
deal. >> Would you necessarily recognize their sports attire?

02:48:09.120 --> 02:48:14.240
>> Not necessarily. But usually sports attire has kind of a vibe.

02:48:12.479 --> 02:48:17.760
>> It does. >> Solid color, big logo,

02:48:15.920 --> 02:48:22.479
>> but I wouldn't I wouldn't necessarily >> There are definitely I I

02:48:20.880 --> 02:48:25.840
guarantee you there are cricket teams. I would have no idea. Yeah.

02:48:24.240 --> 02:48:30.240
>> Um, >> yeah. >> All right. Hit us, Dan. >> And sometimes some soccer jerseys just

02:48:28.720 --> 02:48:36.160
look like an advertisement. >> This is true, but I can't tell.

02:48:33.600 --> 02:48:41.120
>> Hey, DLL. Loving the cables. Do we have any news on DisplayPort or HDMI? Um,

02:48:39.359 --> 02:48:45.840
the news is that we're working on development, but realistically, even if

02:48:43.600 --> 02:48:50.399
we got our golden samples and signed off and said go, there's no production

02:48:48.080 --> 02:48:55.920
capacity for them until we can somewhat catch up on USBC and USBA.

02:48:54.240 --> 02:48:59.600
So, we're working on it. We're going to do it. They're not going to be the same.

02:48:58.399 --> 02:49:04.560
So, they're going to be a little bit more rigid just because the conductors

02:49:01.439 --> 02:49:05.840
are so thick. Um,

02:49:04.560 --> 02:49:10.000
so they're they're going to have like a bit more like memory to them, but they're still going to have the same

02:49:08.080 --> 02:49:14.240
outer sheath. So, they'll be super UV resistant and they'll have that kind of

02:49:11.840 --> 02:49:18.399
that nice feel to them. Uh, and obviously the signal quality will be a

02:49:16.399 --> 02:49:22.640
top priority. Uh, but they won't have quite the same flexibility. So, that's

02:49:19.840 --> 02:49:27.920
something to watch out for. Hello, DLL. Steam frame hype. Oh, I

02:49:25.439 --> 02:49:32.319
know. If it ever comes out, any opinion on the way Valve has handled the release

02:49:29.680 --> 02:49:34.399
so far? Has Luke tried the controller? >> I have not.

02:49:33.040 --> 02:49:37.600
>> Oh, yeah. You should You should borrow one just to try it out. It's It's

02:49:36.080 --> 02:49:41.439
different. It's >> definitely better for people with big

02:49:39.200 --> 02:49:44.640
hands than for people with my size mits. >> When I saw the imagery of it, I thought

02:49:43.840 --> 02:49:48.000
that'd probably be true. >> She's a thick boy. >> The big pads, man. >> Yeah.

02:49:47.200 --> 02:49:52.720
>> Yeah. >> Um, as for how Valve's handled the release

02:49:51.520 --> 02:49:56.640
so far, I don't think Valve had a choice. Obviously, Valve would have

02:49:54.720 --> 02:50:00.240
loved to have the Steam Controller and the Steam Machine and the Steam frame

02:49:58.240 --> 02:50:04.240
come out at the same time. like no question. But

02:50:02.160 --> 02:50:05.600
>> Rams already in the warehouse for the controller. He's got to start moving

02:50:05.279 --> 02:50:11.279
them. >> Yeah. >> Um I I saw in your review the the thumb

02:50:08.800 --> 02:50:13.439
collision thing. I suspect I'll have an issue with that.

02:50:11.840 --> 02:50:16.000
>> Right. You don't love the symmetrical thumb sticks. Neither do I.

02:50:14.960 --> 02:50:21.760
>> Really hate it. >> Neither do I. >> Really hate it.

02:50:20.080 --> 02:50:26.560
Real bad, man. >> AF deal. It's great to watch live from

02:50:24.399 --> 02:50:30.000
the UK. From your limited experience with it, would you say that the Steam

02:50:28.160 --> 02:50:35.920
Machine will be worth the wait or bite the bullet and upgrade my i77700 K at

02:50:33.040 --> 02:50:39.200
today's prices? There are some deals to be had on DRAM right now. I don't know

02:50:37.920 --> 02:50:43.600
how long they're going to last. >> It's funny looking at them be like, "Oh,

02:50:41.760 --> 02:50:48.560
it's whatever percentage off." It's like, yeah. >> Yeah. Don't ignore that. Just look at

02:50:47.040 --> 02:50:53.359
the price. >> If you can snag a deal, I would snag the

02:50:51.439 --> 02:51:00.000
deal you can snag and I wouldn't wait much longer. i77700 K is old enough that

02:50:57.279 --> 02:51:06.080
um there are modern games that are going to benefit from a from a big upgrade for

02:51:02.800 --> 02:51:08.800
you. I would go for it.

02:51:06.080 --> 02:51:13.840
I Linus and team, are you still running an LG TV OLED as your work monitor? Any

02:51:12.000 --> 02:51:17.120
annoyances you've come across and how did you fix them?

02:51:15.200 --> 02:51:21.439
>> Um I am not anymore. The biggest annoyance

02:51:19.680 --> 02:51:24.960
has got to be the auto brightness control as you go from from windowed

02:51:23.760 --> 02:51:30.000
applications to full screen applications. There's not a ton that can

02:51:27.439 --> 02:51:35.439
really be done about that. The monitor that I'm using for work right now is the

02:51:32.000 --> 02:51:39.760
one that uh we did a sponsored LT for.

02:51:35.439 --> 02:51:40.160
This thing is absolutely knucking futs.

02:51:39.760 --> 02:51:46.800
>> Wa. >> It's 52 in 6K. And the way Dell markets

02:51:42.880 --> 02:51:50.399
it is as like a 4K

02:51:46.800 --> 02:51:52.319
um what's the size of the 4K they they

02:51:50.399 --> 02:51:59.200
compare it to? I I don't remember. But basically it's like

02:51:54.319 --> 02:52:01.359
>> 6144x 2560 at 120 Hz. This thing is

02:51:59.200 --> 02:52:07.279
wild. So it's like having a 4K display and then like two 1080s flanking it. Um

02:52:04.720 --> 02:52:13.200
and it's 52 in across. It's curved. It's got a built-in Thunderbolt hub. So, I

02:52:09.680 --> 02:52:14.800
just roll up with my laptop, plug in,

02:52:13.200 --> 02:52:19.760
and all my peripherals are ready to rock. My webcam, my mic, everything's

02:52:16.720 --> 02:52:22.240
good to go. It's IPS, so there's no tom

02:52:19.760 --> 02:52:27.359
foolery around like auto brightness and dimming and anything like that. It's

02:52:24.399 --> 02:52:29.840
like $4,000 Canadian, so it's like three grand us.

02:52:28.160 --> 02:52:35.040
>> I was going to say, I think I'll keep my uh my three monitors. >> It's the nicest monitor that I use, but

02:52:33.200 --> 02:52:39.760
could never recommend. You know what I'm saying? >> Sure. Yeah. Yeah. I mean, that's fair

02:52:37.200 --> 02:52:46.080
enough. And hopefully, you know, that we're you're seeing prices like

02:52:42.720 --> 02:52:48.319
of standard class monitors, I don't 10

02:52:46.080 --> 02:52:50.880
1080, 1440p monitors right now constantly coming down. Stuff like that

02:52:49.920 --> 02:52:56.800
will come down eventually. >> And for the for the price, I would

02:52:53.439 --> 02:53:00.080
solidly recommend the 42-in TV instead.

02:52:56.800 --> 02:53:02.319
>> That's uh even with the distractions and

02:53:00.080 --> 02:53:05.359
annoyances. I remember we did a video a while back on how you can get like a

02:53:03.760 --> 02:53:08.000
service remote for the LG and you there's more stuff you can adjust. I

02:53:06.800 --> 02:53:14.399
don't know that that's true of the newer ones, though. I think I was on like a C2 at the time. Yeah, I've got a C2 as my

02:53:12.000 --> 02:53:19.040
main monitor. 52 in is nice and they're pretty damn cheap.

02:53:16.560 --> 02:53:24.560
Uh, let's see what else is next. Hey, Luke, how are you liking Tarov 1.0?

02:53:22.240 --> 02:53:27.439
>> Uh, I was having a pretty okay time with it. And then

02:53:26.000 --> 02:53:31.200
>> you sound so enthusiastic. >> We And then we Linux challenged. I do

02:53:29.680 --> 02:53:34.000
want to escape from Tarive. I want to like complete the game, which is

02:53:32.800 --> 02:53:38.319
possible now. Uh, >> okay. Hit me up. Hit me up. I'll join. Yeah,

02:53:36.000 --> 02:53:42.640
>> I'll I'll be your boat anchor. >> Come have fun. Um, we'll see how that

02:53:40.640 --> 02:53:47.760
goes. Especially because like I was playing decently close to launch and

02:53:45.520 --> 02:53:50.479
doing okay, but if I jumped in now, everyone's going to have like crazy

02:53:48.800 --> 02:53:54.960
gear. So, it might make sense for me to wait for a wipe again and then try to

02:53:52.399 --> 02:53:58.800
beat it then. But we'll see.

02:53:56.880 --> 02:54:05.040
Hello, DLL from the Netherlands. Question one. My company is looking to

02:54:00.960 --> 02:54:08.960
give non techy users uh to vibe code

02:54:05.040 --> 02:54:11.520
in-house apps users think will help them

02:54:08.960 --> 02:54:14.319
with their work. What's your thoughts? Um also when's the LTD Vibe Code video

02:54:14.080 --> 02:54:21.040
coming? >> I talked about that earlier. >> Oh, you did? Okay. So, >> yeah, it's it's dead. It'll maybe be a

02:54:18.479 --> 02:54:24.880
Floatplane exclusive with like sort of roughly cut together, but it's just it's

02:54:23.359 --> 02:54:27.680
been so long since I did the challenge that it just doesn't seem that relevant

02:54:26.399 --> 02:54:32.080
today. >> Um Uh, so I'm going to hear your

02:54:30.720 --> 02:54:36.640
question and take it in a slightly different angle, but an interesting

02:54:34.399 --> 02:54:40.640
application for vibe coding that I've thought of recently that I've kind of

02:54:38.080 --> 02:54:43.760
pitched to somebody internally who was trying to vibe code their own thing, but

02:54:42.399 --> 02:54:50.560
something that would be pretty sketchy to vibe code. Um, was how about you try

02:54:47.359 --> 02:54:52.479
to vibe code it on your own and use that

02:54:50.560 --> 02:54:55.200
as the request. >> Yeah.

02:54:54.160 --> 02:55:01.680
>> So like >> make this but not crap. >> Yeah. basically because one of the most

02:54:59.279 --> 02:55:07.200
difficult parts is actually getting out of someone's brain what they actually

02:55:04.560 --> 02:55:11.520
want. And you'd think that wouldn't be that hard, but it's really, really

02:55:10.319 --> 02:55:15.760
difficult sometimes. >> That was what I expected to be the conclusion of the vibe coding challenge.

02:55:15.359 --> 02:55:21.920
>> Yeah. >> Was that the best use of it for someone like me was to make a proof of concept

02:55:20.479 --> 02:55:26.240
that I could then hand to a developer and go, "This is what I need it to do. Now it does everything I need it to do.

02:55:24.800 --> 02:55:30.880
Make it not suck." And I'm not gonna lie, if you handed your version to Dan

02:55:28.960 --> 02:55:34.080
and he got to start with that instead of your notes, I bet you would have done a

02:55:32.960 --> 02:55:37.760
better job. And your notes weren't even like that bad. Like compared to most

02:55:36.080 --> 02:55:43.200
people pitching things, your notes were pretty good. Some people will give you

02:55:40.640 --> 02:55:47.600
just nothing. And it's like >> I tried to put a lot of thought into

02:55:45.120 --> 02:55:50.800
like I what I tried to do was I tried to provide Dan with the same prompting

02:55:50.560 --> 02:55:57.439
>> Yeah. >> that I would give to an LLM. >> Yeah. cuz if you know if the LLM can't

02:55:55.200 --> 02:56:00.399
do it then he can't do it for sure or like if he can't do it then the LLM

02:55:59.200 --> 02:56:04.000
can't do it. That's that's what I was going for. So he would have to have all

02:56:02.560 --> 02:56:07.840
the information. So I tried to I actually tried like tried to be extra

02:56:05.760 --> 02:56:12.160
super serial like thorough. >> Yeah.

02:56:08.960 --> 02:56:14.319
>> Um so like I I think that can be kind of

02:56:12.160 --> 02:56:18.640
neat like let this person brainstorm with themselves effectively and come up

02:56:16.800 --> 02:56:22.560
with like a Yeah. I mean, this thing doesn't necessarily work or maybe it's

02:56:20.399 --> 02:56:26.240
like a just absolute nightmare for security reasons or whatever else, but

02:56:24.880 --> 02:56:31.439
this is kind of what I want it to do. You can poke around and see the intention and then take that and

02:56:30.080 --> 02:56:36.000
actually make a thing out of it. Sounds pretty cool. Um, a company really

02:56:34.080 --> 02:56:39.760
encouraging their employees to do that. I mean, yeah, sounds like security

02:56:37.840 --> 02:56:43.640
problems depending on what your company works on. Um,

02:56:43.680 --> 02:56:51.520
I've also seen people do some really cool stuff with VIP coding. I I'm pretty

02:56:47.600 --> 02:56:54.240
sure what's his name? Hank Green. Uh

02:56:51.520 --> 02:56:59.279
Hank Green YouTube. Let's go to his channel.

02:56:56.000 --> 02:57:02.319
He has a video, the Artemis photos you

02:56:59.279 --> 02:57:04.560
didn't see yet. And then in here, he

02:57:02.319 --> 02:57:11.439
vibecoded a website called Artemis timeline. And you can go through and see

02:57:08.240 --> 02:57:14.319
the the photos that were taken and the

02:57:11.439 --> 02:57:18.000
like time of day and which camera took it and what they were supposed to be

02:57:16.240 --> 02:57:24.000
doing at the time >> and all that kind of stuff. And he put

02:57:21.600 --> 02:57:28.960
this together with some vibe coding and it didn't perfectly work and he had to

02:57:25.920 --> 02:57:31.040
step in and make some changes to it and

02:57:28.960 --> 02:57:35.760
improve things and fix data and whatnot. but like he got part of the way there

02:57:33.520 --> 02:57:39.600
with vibe coding. And if it if you're not Hank Green and you can't take it the

02:57:37.359 --> 02:57:41.439
rest of the way there, um maybe within your company, you can hand it off to

02:57:40.640 --> 02:57:45.680
somebody who can. >> Yeah, >> it's funny you bring up like creators

02:57:44.080 --> 02:57:50.960
using vibe coding. I was at creator summit recently and I spoke to at least

02:57:47.600 --> 02:57:53.520
one, I'll just put it that way creator

02:57:50.960 --> 02:57:55.760
who uses vibe coding very regularly in their projects and just doesn't disclose

02:57:55.359 --> 02:58:00.880
it. >> Yeah. because they just don't feel like dealing with the hate. Because at the

02:57:59.120 --> 02:58:05.040
end of the day, all the viewers care about is like the end result of the

02:58:03.520 --> 02:58:10.560
product. They're never going to audit the code. It doesn't matter because they're never going to ship it to anyone

02:58:08.240 --> 02:58:14.399
and they just love it. >> I I know multiple creators personally

02:58:12.319 --> 02:58:19.359
that that use it and don't disclose it. Um

02:58:17.040 --> 02:58:22.319
but they're also not like shipping. >> Yeah.

02:58:20.160 --> 02:58:28.479
>> These are tools for themselves. Yeah. Yeah. like and and Hank Green did, but

02:58:25.359 --> 02:58:30.720
he disclosed it I think like multiple

02:58:28.479 --> 02:58:34.800
times in one video. Like he wasn't uh >> That's a Hank Green thing to do.

02:58:32.160 --> 02:58:36.880
>> Yeah, sure is. >> That's a cool site.

02:58:35.439 --> 02:58:40.080
>> Oh, sorry. Sorry. Cool. >> What's up, boys? Luke, what specific

02:58:38.560 --> 02:58:45.560
chair do you use at home when sitting at your computer and gaming?

02:58:42.560 --> 02:58:45.560
>> Uh,

02:58:48.160 --> 02:58:52.399
I had the name on my head earlier and I don't remember. Uh, let me see. One

02:58:52.160 --> 02:58:57.800
second. >> I took that from you. >> I can I can find it pretty easily.

02:58:58.720 --> 02:59:03.960
Computer. Oh my god. Chair.

02:59:06.160 --> 02:59:14.880
The Marcus. The IKEA Marcus.

02:59:11.040 --> 02:59:18.319
That's it. Nice. Solid. It's cheap. It's

02:59:14.880 --> 02:59:22.399
not that good.

02:59:18.319 --> 02:59:24.000
Nice. Hello, Legendary Lords of Devices.

02:59:22.399 --> 02:59:28.000
This question mostly goes to Luke. Well, three in a row, but Lionus is free to

02:59:25.920 --> 02:59:31.840
answer as well. I've heard you mention playing Ballers Gate 3 before. What's

02:59:30.399 --> 02:59:35.279
your favorite class to play? >> Oh, dude, I don't think Lionus is going

02:59:34.479 --> 02:59:40.319
to have one of these. I don't think you've played it. >> I always play Mage Chicks.

02:59:38.319 --> 02:59:45.040
>> Okay. Mage, I think. >> World of Warcraft or Dragon uh Dragon

02:59:43.120 --> 02:59:47.840
Age or like whatever. I'm just I'm just I go straight for the mage chick. I

02:59:46.640 --> 02:59:51.279
personally think those are cooler in Divinity because the the interaction of

02:59:50.000 --> 02:59:58.000
all the spells with each other and being able to do that kind of stuff. >> Um, fighter

02:59:55.200 --> 03:00:04.640
>> classic are just so sick in Boulders Gate. They're crazy, dude. They're nuts.

03:00:02.080 --> 03:00:08.000
Attacking like six times in one turn is just crazy.

03:00:06.640 --> 03:00:13.120
>> Jumping all over the place. >> Yeah, they're just they're nuts. I I

03:00:10.960 --> 03:00:16.080
like one of the designers for Ballers's Gate must have looked at D and D and

03:00:14.479 --> 03:00:20.319
been like, "Fighters are boring. What if we just gave them crack?

03:00:18.960 --> 03:00:23.840
Just like what happened? >> Worked for the Germans

03:00:22.000 --> 03:00:28.880
>> basically. >> Yeah. Um, so I don't know. Those are

03:00:26.000 --> 03:00:33.439
fun. Um, I I like tons of stuff, though. I've played I've played a bunch of

03:00:30.319 --> 03:00:35.520
different classes, but yeah, just just

03:00:33.439 --> 03:00:41.520
send it just full sending Lazelle down fighter is is sick.

03:00:38.160 --> 03:00:43.760
>> All right, DLL. If LDD could pivot to a

03:00:41.520 --> 03:00:47.520
completely channel unrelated topic for one week, what would you cover? Also,

03:00:45.920 --> 03:00:51.359
thanks for the new shipping perk. I upgraded to Floatplane plus because I

03:00:49.760 --> 03:00:55.359
did the math and I would actually save money.

03:00:52.800 --> 03:01:01.359
>> Uh yeah, if you order a fair bit from LT store, it's a it's kind of a no-brainer.

03:00:57.200 --> 03:01:03.600
Um the Floatplane perk includes um

03:01:01.359 --> 03:01:07.040
always free shipping. I have clarified with the team that is apparently

03:01:04.880 --> 03:01:11.439
forever. So, free shipping over a threshold, but during shiptorm the

03:01:08.399 --> 03:01:11.920
threshold's even lower.

03:01:11.439 --> 03:01:18.160
>> Okay. >> Yeah. >> Okay. >> Um,

03:01:15.760 --> 03:01:23.359
it would probably be Okay, this is going to sound crazy, but I think it would be

03:01:20.399 --> 03:01:27.840
like going to garage sales. If it was just for a week, just like a throwaway

03:01:25.359 --> 03:01:31.439
thing, I would I would probably I would I would probably like thrift or like go

03:01:30.080 --> 03:01:35.279
to garage sales. I love hunting for deals. >> Garageyard Wars. And it'd be kind of fun

03:01:33.359 --> 03:01:39.840
to like not have to bother with computer deals for a change.

03:01:38.000 --> 03:01:43.760
I' like I think that would be a blast. Lionus and Luke just go to garage sales.

03:01:42.160 --> 03:01:49.680
I would I would watch the crap out of that. >> I was thinking I don't feel like this is

03:01:47.600 --> 03:01:52.479
I my personal vote, which I think everyone's going to get pissed about,

03:01:50.880 --> 03:01:55.200
but my personal vote is that we maybe don't even do a Scrapard Awards this year.

03:01:54.080 --> 03:02:00.880
>> Oh, we're not doing one this year. >> Yeah. Okay. Everything's just kind of a mess. But I was thinking next time we

03:01:58.640 --> 03:02:04.080
bring it back, I think you and I should be teamed up.

03:02:03.200 --> 03:02:12.000
I don't know. >> You just want a trophy. >> Maybe. I don't I don't know what the uh

03:02:10.240 --> 03:02:14.160
>> I don't know what the challenge is. I don't know why it makes sense, but I

03:02:13.359 --> 03:02:19.279
think it would be fun. >> Just going to be two adults beating up toddlers at that point.

03:02:17.920 --> 03:02:22.399
>> No, we've done it before. >> Yeah, we we lost once when we were

03:02:21.439 --> 03:02:25.040
teamed up, I think. Really? >> Nope. >> Did we not? >> We did and then figured out that they

03:02:24.640 --> 03:02:30.560
cheated. >> Oh, that's right. I remember that. >> Yeah,

03:02:28.000 --> 03:02:34.000
>> but they did they did super well. And I think they only really cheated cuz their

03:02:32.000 --> 03:02:39.680
part like died which was >> unfortunate but we still win.

03:02:37.840 --> 03:02:44.720
>> Hello Lionus Luke and Dan. What has been the biggest tech interruption caused by

03:02:41.680 --> 03:02:46.160
pets? Once I had our dog rip a DSL cable

03:02:44.720 --> 03:02:51.359
which took down internet and television for a few hours. >> When I was a kid we had a pet rabbit and

03:02:49.680 --> 03:02:53.840
they chewed through all of the cables behind the TV.

03:02:53.439 --> 03:03:00.640
>> Nice. >> And then my brother and I didn't think quite as highly of the rabbit.

03:02:59.200 --> 03:03:07.600
Yeah, I can imagine you two not being into that. Uh, not a pet, but I had rats

03:03:04.399 --> 03:03:09.279
uh destroy both our minivan and Ivon's

03:03:07.600 --> 03:03:13.760
SUV recently, >> making nests in them and chewing through

03:03:11.520 --> 03:03:16.319
wires. They both they both had to go in for work over the last like few months.

03:03:15.680 --> 03:03:22.080
>> Yikes. >> Pretty not impressed by that. So, I have to like I have to like rodent proof my

03:03:20.319 --> 03:03:27.520
garage now, which is just, you know, the kind of thing I love doing on a weekend.

03:03:25.359 --> 03:03:31.760
I had that problem ages ago that in an effort to be green, they made the wires

03:03:29.120 --> 03:03:33.040
out of cellulose. >> Let's just make

03:03:32.479 --> 03:03:38.160
>> Wait, really? >> Yeah, it was some derivative or something. Let's just make all the wires

03:03:36.000 --> 03:03:44.479
in the car out of rat food. Great choice. Okay. as much as uh as much as

03:03:41.840 --> 03:03:50.399
it's like a champagne problem, um I was talking to my uncle about um sort of

03:03:47.600 --> 03:03:53.760
green initiatives in manufacturing and how they sometimes have unintended

03:03:52.240 --> 03:03:59.279
consequences. And uh he was saying that in some ways

03:03:56.319 --> 03:04:05.439
an older airframe is actually more desirable than a newer one. And the

03:04:02.080 --> 03:04:09.359
reason is that the EPA mandates the use

03:04:05.439 --> 03:04:12.800
of more ecologically friendly primers on

03:04:09.359 --> 03:04:14.720
the frames now that uh just crack and

03:04:12.800 --> 03:04:18.720
fail after >> not that many years compared to the old

03:04:16.960 --> 03:04:26.479
>> painting's like crazy expensive cuz I don't know it flies >> cuz and so the one from 1990 he was

03:04:22.960 --> 03:04:30.319
telling me it's actually more economical

03:04:26.479 --> 03:04:33.279
to carefully remove only the paint and

03:04:30.319 --> 03:04:36.640
then just touch up the primer uh with the cuz you can't use the old stuff

03:04:34.800 --> 03:04:41.520
anymore. So, you just like touch up the spots where you like accidentally went

03:04:38.560 --> 03:04:44.960
through it um than it is to like strip it and reprime it because of how often

03:04:43.439 --> 03:04:50.479
you'll have to completely strip it and reprime it now. And everyone knows this

03:04:47.920 --> 03:04:56.560
and just keeps doing it. And it sort of raises the question, how much

03:04:53.200 --> 03:04:58.080
eco-friendly paint do you need to use

03:04:56.560 --> 03:05:01.359
before it would have been better to just paint it once with the note eco-friendly

03:05:00.080 --> 03:05:05.439
paint? And I I don't know the answer to that question. >> I also wonder what about it is not

03:05:03.680 --> 03:05:08.800
eco-friendly and and how not eco-friendly it is cuz it could be that

03:05:06.880 --> 03:05:11.840
that original primer is just like really brutal. >> It could be as bad as painting it six

03:05:11.200 --> 03:05:17.359
times, >> right? >> But unless we unless we know for sure

03:05:14.880 --> 03:05:20.240
that math, which maybe someone has done, but I just >> hopefully

03:05:18.560 --> 03:05:23.840
>> I just doubt it. Like how many times do they have to manufacture the cable

03:05:21.600 --> 03:05:26.479
harness in mine and Dan's car before it would have been better to just use the

03:05:25.040 --> 03:05:31.279
less eco-friendly cable harness? >> Yeah. What if it's rat food? >> You know what I mean? I mean, the

03:05:29.760 --> 03:05:35.760
potential of the manufacturing of the product could also be super super

03:05:33.200 --> 03:05:41.760
brutal. Like maybe not so much for for wire, you know, installation. But

03:05:39.279 --> 03:05:43.760
eh, sometimes these have unintended consequences. Bro.

03:05:43.040 --> 03:05:50.960
>> Mhm. >> A bro. >> What? >> I just got some good news.

03:05:46.800 --> 03:05:52.960
>> What? I just got a tracking number.

03:05:50.960 --> 03:05:56.319
Um. Uh oh. No. Or here. Here. I'll bring

03:05:55.120 --> 03:06:02.240
I'll bring it up here. I'll bring it up here.

03:05:58.640 --> 03:06:04.560
I told these guys at CES, I guess it

03:06:02.240 --> 03:06:11.120
was. Did Did we even make a video?

03:06:07.920 --> 03:06:13.680
Kataw, stop tracking people.

03:06:11.120 --> 03:06:16.680
Uh uh

03:06:17.920 --> 03:06:21.439
I don't think I made a video. Did I do a

03:06:21.040 --> 03:06:26.240
short video? >> Bro, what are you talking about? You got to tell me what you're talking about.

03:06:24.080 --> 03:06:28.880
>> Okay. Okay. Okay. Do you remember Roar Systems? The guys who did that like

03:06:27.840 --> 03:06:33.560
AirJet thing? >> Yeah. >> Okay. At CES,

03:06:33.600 --> 03:06:41.200
>> they showed off something called liquid

03:06:36.880 --> 03:06:43.760
jet. So traditional cold plates, right,

03:06:41.200 --> 03:06:48.479
like water blocks are made by taking a plate of copper and then you either you

03:06:46.080 --> 03:06:53.760
like mill a design in it. So you know like little pins or whatever. Uh or or

03:06:51.920 --> 03:06:58.000
like a lot of modern ones use what's called skydived copper where you take a

03:06:56.000 --> 03:07:03.279
blade and so you take that flat piece of copper and you like shave a sliver of

03:07:01.120 --> 03:07:08.000
copper and then like fold it up and then make another fin videos of making heat

03:07:05.279 --> 03:07:11.840
sink. Sky copper is so cool. Anyway, that's the traditional way. Your

03:07:09.760 --> 03:07:17.120
geometries are pretty limited because it's subtractive or like like using the

03:07:15.359 --> 03:07:24.800
malleability of the copper to reshape it.

03:07:19.840 --> 03:07:28.399
>> Roar is using more like um more like uh

03:07:24.800 --> 03:07:31.359
like like silicon manufacturing. So

03:07:28.399 --> 03:07:34.399
they're using like metal deposition like you would like you would make

03:07:32.880 --> 03:07:42.160
microchips. So by using copper deposition they can

03:07:38.560 --> 03:07:45.680
make geometries that are like

03:07:42.160 --> 03:07:49.920
like out of this world more thermally

03:07:45.680 --> 03:07:51.120
efficient than even skydived copper. Um

03:07:49.920 --> 03:07:56.160
>> this is not a good >> that's not what I'm getting. That's not what I'm getting. I'm getting just Oh no

03:07:54.399 --> 03:08:00.960
no you can keep that up though. I'm getting just the like cooling engines at

03:07:58.640 --> 03:08:04.399
the top right. I'm getting two. So, we're going to try putting one on a

03:08:03.439 --> 03:08:09.600
gaming GPU. >> Cool. >> And just like >> seeing how fast she go. This this

03:08:07.840 --> 03:08:16.240
stuff's so cool. So, I was I've been working on this since January. Um,

03:08:14.319 --> 03:08:18.800
>> and I was like, yeah, I don't see the point of me making Yeah, I remember now.

03:08:17.600 --> 03:08:23.200
I was like, I don't see the point of me making a video about like, here's a demo

03:08:20.880 --> 03:08:26.479
on a GPU no one will ever own, but I'm really excited about this and I really

03:08:24.640 --> 03:08:31.920
want to work with you guys, but I want one. And it's taken until now to kind of

03:08:29.520 --> 03:08:36.399
give them all the reassurances that like, you know, we're not going to judge

03:08:34.800 --> 03:08:40.560
them based on that the, you know, the the VRM are going to be hotter cuz it's

03:08:39.040 --> 03:08:43.520
not a full coverage solution and just like, no, no, no, guys. It's Yeah. Yeah.

03:08:42.319 --> 03:08:48.000
Yeah. We're good. We're good. We're good. Um, I'm, Dude, I'm stoked. I'm so

03:08:47.040 --> 03:08:50.880
stoked to check it out. >> Yeah. Nice. That's sweet.

03:08:50.160 --> 03:08:55.680
>> Yeah. >> Howdy from Texas. Mechanical/manufacturing

03:08:53.920 --> 03:09:00.000
engineer here. What manufacturing methods do y'all use in the production

03:08:57.520 --> 03:09:06.399
of your products or any product in general that still fascinates you today?

03:09:04.640 --> 03:09:08.399
>> Injection molding. >> I was going to say it's all kind of

03:09:07.760 --> 03:09:15.359
fascinating. >> Casting. Um >> 3D metal printing.

03:09:12.640 --> 03:09:21.040
>> Uh I mean lots of different things. Laser engraving.

03:09:18.640 --> 03:09:25.680
Um I mean we have a lot of like small scale stuff in house but realistically

03:09:23.120 --> 03:09:31.439
you know we're we're we're using industrial scale manufacturers for for a

03:09:29.600 --> 03:09:38.000
lot of the stuff that makes it to LT store otherwise we wouldn't be able to produce in any meaningful volume. So, I

03:09:35.040 --> 03:09:44.479
I I'm very fascinated by manufacturing technology, but unless you asked me a

03:09:41.600 --> 03:09:48.000
specific product, then I I wouldn't really be able to I wouldn't really be

03:09:46.319 --> 03:09:51.000
able to narrow it down too much, I'm afraid.

03:09:52.479 --> 03:09:58.319
Sorry, Linus and Luke about to quit my

03:09:55.600 --> 03:10:03.279
job to be an executive at a startup. Oh, huge step. small business focused on

03:10:00.319 --> 03:10:07.600
home services. After seeing many businesses rise and fall, what are the

03:10:05.279 --> 03:10:12.720
biggest indicators of success? Tips: culture. You have to have a culture

03:10:10.000 --> 03:10:18.640
that's hungry and wants to win. Um, at times we've had a very hungry winning

03:10:15.760 --> 03:10:23.840
oriented culture and at times we've had a very complacent

03:10:20.720 --> 03:10:25.120
um, collect a paycheck culture and

03:10:23.840 --> 03:10:31.359
>> and times we've had mixed >> and at times we've had a mix that has

03:10:27.760 --> 03:10:33.359
been at various levels of health. Um,

03:10:31.359 --> 03:10:38.160
and I would say that if there's anything that I could tell you to focus on, it's

03:10:35.680 --> 03:10:45.240
have a culture that is laser focused on just winning and being hungry and and su

03:10:41.279 --> 03:10:45.240
failure is not an option.

03:10:46.240 --> 03:10:52.240
Hey, Litlap Dap, you mentioned a while

03:10:49.600 --> 03:10:56.399
ago that you were going to hold a Smash tournament as a middle finger to

03:10:53.760 --> 03:11:01.279
Nintendo's crazy guidelines. Any update to that for the future of Whailand?

03:10:58.319 --> 03:11:06.120
>> We got yelled at. of the Elcoin by our own people.

03:11:02.240 --> 03:11:06.120
>> Yeah, we basically

03:11:06.479 --> 03:11:13.600
I'm not going to tell you my wife said no,

03:11:10.240 --> 03:11:17.200
but my wife said no,

03:11:13.600 --> 03:11:19.520
and she was right. She usually is.

03:11:17.200 --> 03:11:23.680
Sometimes she's not hypothetically. I

03:11:21.840 --> 03:11:28.720
I imagine sometimes she's not, but usually she usually she's right. Uh

03:11:26.399 --> 03:11:33.279
sometimes she can be very very conservative

03:11:30.319 --> 03:11:38.720
um in terms of like like CIA, you know, covering our butts. Um but that has, you

03:11:36.160 --> 03:11:43.120
know, and and there are times when it's very annoying to navigate that, but then

03:11:40.800 --> 03:11:51.160
we'll get audited and we like pass our audits and I'm like, right, good, good

03:11:47.279 --> 03:11:51.160
job. you know,

03:11:51.680 --> 03:12:01.200
do you have any recommendations on what I should use on my PX13 for the memory

03:11:56.479 --> 03:12:03.279
modules? I plan on repasting my CPU to

03:12:01.200 --> 03:12:08.399
get the get rid of the liquid metal before I kill my unit. I plan to use

03:12:06.560 --> 03:12:14.720
BTM7950 for processing. Ooh. Uh,

03:12:12.880 --> 03:12:18.720
it's less a matter of what you should use and it's more a matter of what

03:12:16.319 --> 03:12:23.520
thickness you should use. Uh, you may want to try checking with ASUS. They may

03:12:21.439 --> 03:12:28.800
be willing to tell you. If they're not willing to tell you, then man, your best

03:12:27.200 --> 03:12:31.520
bet might be to just take it off and measure the thickness of those thermal

03:12:30.240 --> 03:12:36.160
pads and then make sure that you're not putting in something that is thinner or thicker than what's already in there. Or

03:12:34.800 --> 03:12:40.800
you could just keep using the thermal pads that are in there. I mean, realistically, are those going to be a

03:12:39.200 --> 03:12:45.200
real problem for you? is your memory overheating.

03:12:43.680 --> 03:12:49.520
There's no liquid metal on the memory. So, I if I if it was me, the convenient

03:12:48.000 --> 03:12:55.760
way would be to just reuse my thermal pads there. That's going to be that's going to be my my low friction um

03:12:53.760 --> 03:12:59.359
recommendation. What's your opinion on the online belief

03:12:57.439 --> 03:13:03.680
that the Steam Machine will include a controller on launch? I'm interested,

03:13:01.359 --> 03:13:07.359
but the price worries me. Also, what's the status on the physical Linus coin

03:13:05.359 --> 03:13:12.000
shipping? uh status on the physical coins is they are in manufacturing and

03:13:10.000 --> 03:13:17.040
if you check your order confirmation, it should tell you like when they're

03:13:13.600 --> 03:13:18.560
expected to be uh being minted. Um as

03:13:17.040 --> 03:13:22.240
for the Steam Machine including a controller, from my understanding, it should include a controller. That was

03:13:21.279 --> 03:13:29.520
what Valve >> pretty sure told me when I went down there for the announcement or the

03:13:25.920 --> 03:13:31.840
unveiling. Um, if if something changed

03:13:29.520 --> 03:13:37.279
due to the way the market is right now, I I wouldn't actually like hold Valve to

03:13:35.040 --> 03:13:44.040
the coals over it, like it's a tough situation that they're in. Um, but from

03:13:39.840 --> 03:13:44.040
my understanding, that is the intent.

03:13:45.040 --> 03:13:49.920
Hello from Toronto. I just finished Sea

03:13:48.399 --> 03:13:54.160
of Stars and I'm looking for my next fix. Got any recommendations for more

03:13:51.680 --> 03:13:58.760
retro vibe fun times? already finished Cross Code from your WAN Show

03:13:55.760 --> 03:13:58.760
recommendation.

03:13:59.359 --> 03:14:06.720
Um, is it retro or is it JRPG? Cuz you could

03:14:04.560 --> 03:14:10.560
you recommend Expedition 33? >> Oh, Expedition 33 is so good.

03:14:08.479 --> 03:14:13.279
>> Not not retrolooking, but JRPG.

03:14:12.800 --> 03:14:18.080
>> Uh, >> not technically retro vibe fun time.

03:14:16.720 --> 03:14:23.439
>> French RPG FRPG. >> Oh, they want a retro vibe fun time. Uh,

03:14:21.359 --> 03:14:26.560
Chain Deckos. Chained Echoes is another one I played and really enjoyed. The

03:14:24.720 --> 03:14:32.760
story gets a little sort of weird, but that's kind of typical of the genre um

03:14:29.200 --> 03:14:32.760
toward the end.

03:14:34.880 --> 03:14:42.960
Chain Deckos was my answer, Dan. Oh, there he goes. Sorry. And last one I got

03:14:39.920 --> 03:14:45.439
for you today is, "Hey DL, is there any

03:14:42.960 --> 03:14:52.640
plan to make a windbreaker coat? Love from Leel Province." Um,

03:14:49.359 --> 03:14:54.080
I think so.

03:14:52.640 --> 03:15:00.479
I actually don't know. I'm so sorry. You might have to message support and I

03:14:56.560 --> 03:15:03.200
think I'm going to message support that

03:15:00.479 --> 03:15:08.239
it's time for the end of the show. We'll see you again next week. Same bad time.

03:15:05.840 --> 03:15:11.200
Different channel. You want to head over to the WAN Show channel. We're going to

03:15:10.080 --> 03:15:15.520
we're going to have to transition over there pretty quick cuz this whole streaming on both is not working. We

03:15:14.319 --> 03:15:22.080
might have to figure out the collab feature. I don't know. >> Apparently, that isn't a thing. Maybe.

03:15:18.800 --> 03:15:22.960
You could collab the VOD.

03:15:22.080 --> 03:15:29.359
>> Okay. >> I don't know. >> See you later.

03:15:27.359 --> 03:15:33.399
>> Bye. >> I have to fly.

03:15:30.399 --> 03:15:33.399
>> Yeah.

03:15:58.319 --> 03:16:00.479
Whatever.