WEBVTT

00:00:11.424 --> 00:00:16.103
<v Chris>Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.

00:00:16.103 --> 00:00:17.003
<v Wes>My name is Wes.

00:00:17.003 --> 00:00:18.036
<v Brent>And my name is Brent.

00:00:18.559 --> 00:00:22.183
<v Chris>Hello, gentlemen. Well, coming up on the show today, from Austin to London,

00:00:22.183 --> 00:00:26.103
<v Chris>this week's episode, racked up the air miles so you don't have to.

00:00:26.103 --> 00:00:30.923
<v Chris>We'll take you inside Texas Linux Fest and the shift we're seeing in these community events.

00:00:31.300 --> 00:00:35.313
<v Chris>And then it's across the pond for an on-the-ground coverage of Ubuntu Summit.

00:00:35.313 --> 00:00:38.323
<v Chris>Then we're going to round it out with some great boosts, picks,

00:00:38.323 --> 00:00:41.513
<v Chris>and a lot more. So before we go there, let's say time-appropriate greetings

00:00:41.513 --> 00:00:43.207
<v Chris>to our virtual lug. Hello, Mumble Room.

00:00:43.549 --> 00:00:46.539
<v Mumble>Hello. Oh, hey there. Hey, Wes, and hello, Brent.

00:00:46.742 --> 00:00:50.083
<v Chris>Hello. And hello, everybody up there in quiet listening, everybody on the live

00:00:50.083 --> 00:00:52.367
<v Chris>stream at jblive.tv or in the chat room.

00:00:52.849 --> 00:00:56.424
<v Chris>And, of course, good morning to our friends over at Defined Networking.

00:00:56.790 --> 00:01:01.560
<v Chris>Head on over to defined.net slash unplugged and meet Manage Nebula from Defined Networking.

00:01:02.390 --> 00:01:06.463
<v Chris>What makes Nebula different, I think, is the risk profile. This is something

00:01:06.463 --> 00:01:09.130
<v Chris>we don't think enough about, but we need to start thinking about this more.

00:01:09.693 --> 00:01:12.703
<v Chris>It's open source, and it's built on proven security concepts,

00:01:12.703 --> 00:01:16.533
<v Chris>encryption, certificates, security groups in Linux, and tunneling.

00:01:16.533 --> 00:01:18.836
<v Chris>These are things that when there's a vulnerability in those,

00:01:19.207 --> 00:01:22.249
<v Chris>it's shared across the Linux landscape. So you're going to know about it,

00:01:22.772 --> 00:01:25.384
<v Chris>and every Linux vendor is going to be releasing a CVE and a patch.

00:01:25.686 --> 00:01:29.424
<v Chris>So you'll benefit from that collective work to fix these things when you use Nebula.

00:01:30.301 --> 00:01:34.887
<v Chris>And of course, since it uses the noise protocol, you're going to hear a lot about that too.

00:01:35.618 --> 00:01:39.573
<v Chris>Nebula brings it all together with a decentralized VPN. Direct connections and

00:01:39.573 --> 00:01:42.538
<v Chris>lighthouse you can host yourself or you can have Define Networking help you.

00:01:42.880 --> 00:01:47.832
<v Chris>You can try it. 100 hosts for free. No credit card required at Define.net slash unplugged.

00:01:48.691 --> 00:01:52.273
<v Chris>That's Define.net slash unplugged. Go redefine your VPN experience.

00:01:52.273 --> 00:01:55.033
<v Chris>That's why they call it Define at Define.net slash unplugged.

00:01:55.033 --> 00:01:57.171
<v Chris>It came in so handy on our trip.

00:01:57.722 --> 00:02:00.433
<v Chris>And we got a fair amount of questions about Nebula too.

00:02:00.433 --> 00:02:01.153
<v Wes>Yes, we did.

00:02:01.153 --> 00:02:04.373
<v Chris>People are definitely getting Nebula curious. So if that's you,

00:02:04.373 --> 00:02:08.752
<v Chris>defined.net slash unplugged, big thank you to Defined. Thank you, guys.

00:02:10.905 --> 00:02:12.717
<v Chris>Now, we have some housekeeping.

00:02:18.057 --> 00:02:21.932
<v Chris>This is a big one. There's a lot to get into. So let's start with maybe the

00:02:21.932 --> 00:02:23.247
<v Chris>biggest announcement in here.

00:02:24.060 --> 00:02:30.033
<v Chris>And that is we are officially announcing and relaunching the Holiday Home Lab. It's live now.

00:02:30.822 --> 00:02:37.208
<v Chris>We told you it was coming. Holiday.jupiterbroadcasting.com. You can go submit your home lab now.

00:02:37.812 --> 00:02:42.092
<v Chris>Thursday, December 10th is the cutoff. So you have a limited time.

00:02:42.092 --> 00:02:43.797
<v Chris>December 10th is when we cut it off.

00:02:44.226 --> 00:02:48.142
<v Chris>We will be revealing the entries before that on November 29th.

00:02:48.142 --> 00:02:51.784
<v Chris>The entries will go public where you will be able to vote on them.

00:02:52.429 --> 00:02:54.812
<v Chris>We promised you'd be able to vote on the entries last year. And,

00:02:54.812 --> 00:02:55.950
<v Chris>boys, we have delivered.

00:02:57.001 --> 00:03:01.542
<v Chris>Well done. Well done. Team effort here. Everybody pulling to their strength

00:03:01.542 --> 00:03:03.842
<v Chris>to get that done. Even on the trip, we were working on this.

00:03:03.842 --> 00:03:05.969
<v Chris>But I'm really, really happy with where it came.

00:03:06.585 --> 00:03:10.662
<v Chris>So here's the rundown. We want to see your glorious mess, your home lab,

00:03:10.662 --> 00:03:13.899
<v Chris>whatever it might be. go to holiday.jupiterbroadcasting.com.

00:03:14.247 --> 00:03:18.772
<v Chris>Get that submitted, ideally before the end of November, so that way it can be

00:03:18.772 --> 00:03:21.486
<v Chris>in the public voting. Because here's the catch, guys.

00:03:22.566 --> 00:03:26.402
<v Chris>The Holiday Home Lab special, it goes live December 13th. That's our last episode

00:03:26.402 --> 00:03:28.319
<v Chris>of the year of Everything Goes As Planned.

00:03:29.392 --> 00:03:32.783
<v Chris>And we're going to go out with a bang. So show off your lab,

00:03:33.276 --> 00:03:37.096
<v Chris>holiday.jupiterbroadcasting.com. And to make it even easier this year.

00:03:38.320 --> 00:03:41.325
<v Chris>The form has been streamlined. It has been optimized. So if you want to fill

00:03:41.325 --> 00:03:42.905
<v Chris>it out manually, you absolutely can.

00:03:44.065 --> 00:03:49.115
<v Chris>However, if you've set yourself up a clanker, we now have a one-line clanker

00:03:49.115 --> 00:03:53.825
<v Chris>copy that you can prompt to your bot, and it will help you fill out a perfect

00:03:53.825 --> 00:03:57.055
<v Chris>submission for the Holiday Home Lab to make it even easier for you.

00:03:57.055 --> 00:04:00.105
<v Wes>You know, we've already got five early birds submitted in there,

00:04:00.105 --> 00:04:01.595
<v Wes>but I hope to see that grow.

00:04:01.595 --> 00:04:05.295
<v Chris>Oh, I love it. I love it. This is going to be a fun episode.

00:04:05.295 --> 00:04:09.085
<v Chris>and now with your participation out there and you voting and help surfacing

00:04:09.085 --> 00:04:10.803
<v Chris>some of these, I think it's going to be even better.

00:04:11.238 --> 00:04:14.495
<v Chris>I think this is going to be a great year. And if you want to give a little more

00:04:14.495 --> 00:04:19.452
<v Chris>exposure to your home lab, tell us a bit more about it, send us a boost because once these go public,

00:04:19.952 --> 00:04:23.255
<v Chris>each submission is going to have a public URL and you could include that in

00:04:23.255 --> 00:04:26.565
<v Chris>your boost and then the whole audience will hear about it and maybe they'll

00:04:26.565 --> 00:04:28.119
<v Chris>know why to go vote for your home lab.

00:04:28.468 --> 00:04:32.165
<v Chris>And of course, you could leave us an uplink at uplink.jupiterbroadcasting.com

00:04:32.444 --> 00:04:34.760
<v Chris>and you could explain it in your own words if you'd like.

00:04:35.138 --> 00:04:38.025
<v Chris>And you can include a link back to your HomeLab submission in the notes for

00:04:38.025 --> 00:04:40.954
<v Chris>your uplink. A couple of options there. It's back.

00:04:41.773 --> 00:04:45.459
<v Chris>Holiday.jupiterbroadcasting.com. It's going to be a blast.

00:04:49.993 --> 00:04:52.991
<v Chris>Also, we want to let you know that just around the corner, PJ's coming in with

00:04:52.991 --> 00:04:54.595
<v Chris>a Valve Steamframe review.

00:04:55.454 --> 00:04:58.721
<v Chris>I think that's going to be fun. So let us know what you'd like to hear from

00:04:58.721 --> 00:05:00.721
<v Chris>that, because he has a little bit of time to still put that together.

00:05:00.721 --> 00:05:02.321
<v Chris>Boost.JupiterBroadcasting.com.

00:05:02.321 --> 00:05:03.201
<v Wes>Oh, I want it now.

00:05:03.561 --> 00:05:07.901
<v Chris>Get your questions in. And then while we're talking about the upcoming hardware

00:05:07.901 --> 00:05:12.681
<v Chris>reviews, in that same episode, I believe, we'll be featuring an XPS 14 review,

00:05:12.681 --> 00:05:18.140
<v Chris>the new XPS 14, with a shared memory architecture, MPUs, the latest ARC graphics.

00:05:18.540 --> 00:05:22.111
<v Chris>all of that with its screen. So if you have any questions about the latest Dell

00:05:22.111 --> 00:05:26.421
<v Chris>XPS 14, I have that in my hot little hands and am underway on the review right

00:05:26.421 --> 00:05:28.711
<v Chris>now. So I'd be happy to answer questions.

00:05:28.711 --> 00:05:32.281
<v Wes>You even took it out of your complicated test bench to bring it in to show it to us.

00:05:32.281 --> 00:05:35.551
<v Chris>To surprise you. Because I knew you knew about it, but I think you'd kind of

00:05:35.551 --> 00:05:36.821
<v Chris>forgotten because, you know, you've been a little busy.

00:05:37.281 --> 00:05:40.591
<v Wes>Yeah, I did. And I did forget. And it's shinier than I even expected.

00:05:40.591 --> 00:05:44.801
<v Chris>It is quite shiny. It is quite shiny. So let us know, boost.jupiterbroadcasting.com.

00:05:44.801 --> 00:05:49.331
<v Chris>And also don't forget, steam frame questions if you've got those you can send

00:05:49.331 --> 00:05:54.431
<v Chris>those in and if you want to know about the xps 14 send those in very excited about the home labs too,

00:06:00.381 --> 00:06:05.655
<v Chris>Well, boys, we went to Austin and it was, as always, a great time.

00:06:05.655 --> 00:06:07.144
<v Chris>And it's always really good to see everybody.

00:06:07.684 --> 00:06:10.273
<v Wes>There's a passionate group and super smart people down there.

00:06:10.563 --> 00:06:16.935
<v Chris>Yeah, yeah, I agree. And I feel like we're starting to become kind of like old

00:06:16.935 --> 00:06:18.963
<v Chris>pros at how to cover these.

00:06:19.474 --> 00:06:23.143
<v Chris>But it does mean every now and then some bad habits kind of creep in.

00:06:23.746 --> 00:06:26.985
<v Clips>In an unusual twist, we're waiting on Wes. What is happening?

00:06:28.054 --> 00:06:32.195
<v Clips>It's because he is last minute finishing the Holiday Home Lab website.

00:06:32.195 --> 00:06:34.428
<v Clips>That's what he said. Yeah, that's what he said.

00:06:35.785 --> 00:06:38.120
<v Clips>Down to the wire. All right, boys, let's go fest.

00:06:38.375 --> 00:06:41.695
<v Chris>So one of the things that we do at Texas Linux Fest, we don't really do this

00:06:41.695 --> 00:06:43.785
<v Chris>pretty much anywhere else, but one of the things that we've kind of done at

00:06:43.785 --> 00:06:49.165
<v Chris>Texas Linux Fest is we sneak in through the back door. We kind of avoid registration.

00:06:51.345 --> 00:06:52.255
<v Wes>And or forget about it.

00:06:52.255 --> 00:06:55.675
<v Chris>It's not like we're a big deal, but it's a small fest. So when we show up at

00:06:55.675 --> 00:06:57.765
<v Chris>registration, There's kind of like a group that forms around us.

00:06:57.765 --> 00:06:59.863
<v Chris>It immediately sets a different kind of experience.

00:07:00.554 --> 00:07:05.345
<v Chris>But if you sneak in the back door, you get a feel for how things are going before

00:07:05.345 --> 00:07:06.457
<v Chris>the crowd starts to form.

00:07:07.561 --> 00:07:11.764
<v Clips>We went straight for the vibes, and we snuck in, and it smells like food,

00:07:12.530 --> 00:07:16.066
<v Clips>and there's people doing Linux stuff all over the place. What caught your eye first?

00:07:16.350 --> 00:07:21.180
<v Clips>Everyone, everyone is out chatting. I think the hallway track might be already in effect.

00:07:21.714 --> 00:07:24.457
<v Clips>Brentley, what caught your eye at first? Well, I see a lot of hacking going

00:07:24.457 --> 00:07:27.089
<v Clips>on at the tables there. I love seeing that.

00:07:27.739 --> 00:07:31.681
<v Clips>For me, obviously, it was the food. But yeah, those things are good, too.

00:07:32.407 --> 00:07:36.317
<v Chris>I think your early observation about the hallway track turned out to be really

00:07:36.317 --> 00:07:40.157
<v Chris>kind of nailing it early on like we walked in and that was one of the first

00:07:40.157 --> 00:07:41.358
<v Chris>things you you tuned in on.

00:07:41.887 --> 00:07:45.237
<v Wes>I you know we joke a lot about the hallway track can be the real conference

00:07:45.237 --> 00:07:49.402
<v Wes>at some of these events but i think texas linux fest might be where that is the most pronounced.

00:07:49.832 --> 00:07:54.067
<v Chris>And maybe not for the best i want to get to that towards the end but before

00:07:54.067 --> 00:07:57.407
<v Chris>we get to our old crusty view i think it's yeah everybody has their own reasons,

00:07:57.901 --> 00:07:59.793
<v Chris>to go to a trip ours are different,

00:08:00.414 --> 00:08:03.707
<v Chris>sometimes you know it's just it's about trying something new it's about learning

00:08:03.707 --> 00:08:06.247
<v Chris>something it's about this thing that you've always wanted to try,

00:08:06.247 --> 00:08:09.540
<v Chris>but have never really just had the motivation to do it. And this is your moment to push yourself.

00:08:09.975 --> 00:08:12.849
<v Clips>Can you tell us what you learned here at the Festus this weekend?

00:08:13.423 --> 00:08:19.237
<v Clips>I spent two hours and 50 minutes learning the inside, every single command and

00:08:19.237 --> 00:08:21.827
<v Clips>operant and everything else I could about V,

00:08:22.327 --> 00:08:28.627
<v Clips>or Vim or NeoVim, the extremely old school, but extremely relevant text-based editor.

00:08:28.998 --> 00:08:31.447
<v Clips>Has this been a goal of yours for years? Absolutely.

00:08:32.567 --> 00:08:35.577
<v Clips>The Gmail shortcuts are your inroad to Vim because the Gmail keyboard shortcuts

00:08:35.577 --> 00:08:37.444
<v Clips>are extremely Vim-coded.

00:08:38.465 --> 00:08:41.842
<v Clips>Pun intended, not intended. And then I used to use a, I still use an extension

00:08:41.842 --> 00:08:44.852
<v Clips>called Vimium, which lets you do web browser stuff with a Vim shortcut.

00:08:44.852 --> 00:08:48.742
<v Clips>So I've been Vim adjacent for so long and now I've been like dipped in the waters.

00:08:48.742 --> 00:08:50.492
<v Clips>Yeah. Why is now the right time?

00:08:51.148 --> 00:08:53.932
<v Clips>Besides being at a Linux festival and them offering that course.

00:08:53.932 --> 00:08:57.852
<v Clips>And honestly, you spend a lot more time inside the terminal with text files

00:08:57.852 --> 00:09:02.332
<v Clips>with like AI and containers and Docker and, you know, environment files.

00:09:02.332 --> 00:09:06.392
<v Clips>So knowing how to operate in Vim makes me feel like, not like real or like,

00:09:07.432 --> 00:09:10.432
<v Clips>I feel like I've graduated from nano to vim and like i i went from the junior

00:09:10.432 --> 00:09:14.374
<v Clips>varsity squad to the varsity squad nice at least like a little bit.

00:09:14.670 --> 00:09:18.222
<v Chris>That was kevin purdy i i like that kind of experience it makes.

00:09:18.222 --> 00:09:19.105
<v Wes>Me have hope for you.

00:09:19.470 --> 00:09:25.212
<v Chris>Yeah one day maybe maybe the fest would be the right time maybe if i could ever

00:09:25.212 --> 00:09:28.972
<v Chris>just figure out how to get out of vim you know if i could just figure it.

00:09:28.972 --> 00:09:31.336
<v Wes>Well once you're in and you actually know how to use it you never need to quit.

00:09:31.655 --> 00:09:37.532
<v Chris>Right jk other users though you know I think they go there to really kind of

00:09:37.532 --> 00:09:41.065
<v Chris>dig into stuff that is something for work.

00:09:41.227 --> 00:09:43.932
<v Chris>I think that's another big draw for people or something they've had to wrap

00:09:43.932 --> 00:09:46.933
<v Chris>their head around and now they've been tasked and like, I got to figure this out.

00:09:47.130 --> 00:09:49.982
<v Wes>It's a high bandwidth way maybe to go find people who know a lot more than you

00:09:49.982 --> 00:09:52.632
<v Wes>so you don't have to ask on a forum or try to read it from docs.

00:09:52.632 --> 00:09:53.852
<v Wes>You can just get the answer.

00:09:53.852 --> 00:09:56.238
<v Chris>Pick up some of that nuance or whatnot. Yeah, like Brandon.

00:09:56.865 --> 00:10:00.932
<v Clips>Brandon, what did you learn this weekend? I learned about Kubernetes virtual

00:10:00.932 --> 00:10:04.388
<v Clips>machines and how cursed you can get with it. So that was a cool one.

00:10:04.806 --> 00:10:07.692
<v Clips>Okay. Why is that striking you as a thing that comes out?

00:10:08.432 --> 00:10:11.732
<v Clips>Mostly just because I was always thinking Kubernetes was just pods.

00:10:11.732 --> 00:10:14.452
<v Clips>But the fact that you can just manage virtual machines, like it flipped the

00:10:14.452 --> 00:10:17.512
<v Clips>way that I think about Kubernetes. Instead of it just managing like containers,

00:10:17.512 --> 00:10:20.852
<v Clips>it's like any resource, as long as you can define it and build an operator for

00:10:20.852 --> 00:10:22.392
<v Clips>it, you can define in Kubernetes.

00:10:23.301 --> 00:10:27.552
<v Chris>Texas Linux Fest does something that is a little unique in that Friday,

00:10:27.552 --> 00:10:30.325
<v Chris>it's a two-day event, and Friday is really workshop focused.

00:10:31.196 --> 00:10:35.387
<v Chris>And so that means it either really works for you or it doesn't work for you,

00:10:35.549 --> 00:10:36.402
<v Chris>depending on the topics.

00:10:36.402 --> 00:10:41.822
<v Wes>Yeah, a lot of longer, you know, 50 minutes, hour, couple of hour type events.

00:10:41.822 --> 00:10:45.362
<v Wes>So you bring your laptop, you get ready to work, right? And you're going to

00:10:45.362 --> 00:10:49.412
<v Wes>be learning in depth. You're going to have hands-on, but a very different vibe

00:10:49.412 --> 00:10:52.603
<v Wes>than bopping into a few different, say, 25, 30-minute talks.

00:10:53.178 --> 00:10:56.882
<v Chris>I felt like day one wasn't really Brent's speed, wasn't really my speed.

00:10:56.882 --> 00:10:58.922
<v Chris>Maybe there's one or two things. I don't know that it was.

00:10:58.922 --> 00:11:01.752
<v Wes>Yeah, if you guys weren't dragging me down, I had to be with you.

00:11:01.752 --> 00:11:03.802
<v Wes>I probably could have gotten into a few workshops.

00:11:03.802 --> 00:11:05.490
<v Chris>Do you agree? Is that sort of your feeling too?

00:11:05.926 --> 00:11:10.702
<v Brent>A little bit. Yeah, I would go into these events just like seeking to sponge

00:11:10.702 --> 00:11:14.000
<v Brent>up the knowledge and not necessarily do it on site.

00:11:14.372 --> 00:11:17.742
<v Brent>That said, at these workshops, the rooms are full from what I noticed.

00:11:17.742 --> 00:11:20.241
<v Brent>So it's obviously working for some folks.

00:11:20.595 --> 00:11:24.060
<v Chris>Yep, yep. And I think Saturday, though, is when it's kind of more generally appealing.

00:11:24.356 --> 00:11:26.282
<v Wes>It makes sense to do it that way if you're going to do Friday,

00:11:26.282 --> 00:11:30.032
<v Wes>Saturday, right? Because the workshop's probably better suited for folks in

00:11:30.032 --> 00:11:32.502
<v Wes>the industry who maybe their employers are helping them come or they're coming

00:11:32.502 --> 00:11:36.112
<v Wes>for work. And Saturday is like a more general event for whoever.

00:11:36.112 --> 00:11:38.752
<v Chris>If you could only make it one day, I think Saturday would be the day to make it.

00:11:38.752 --> 00:11:39.064
<v Wes>Though.

00:11:39.813 --> 00:11:43.462
<v Chris>And Saturday, Major Hayden gave his talk, Thou Shall Not Make a Machine in the

00:11:43.462 --> 00:11:48.102
<v Chris>Likeness of a Senior Engineer, which got our attention and turned out largely

00:11:48.102 --> 00:11:51.551
<v Chris>to be a talk about stoicism and navigating change.

00:11:52.622 --> 00:11:56.762
<v Chris>It's worth watching online because it's kind of a bait and switch a little bit, but in a good way.

00:11:57.102 --> 00:12:00.872
<v Wes>Yeah. Pulls in a whole bunch of Dune references. So if you're a Dune nerd, you'll like that too.

00:12:00.872 --> 00:12:05.575
<v Chris>That's true too. And so after Major wrapped up with his keynote,

00:12:05.924 --> 00:12:07.880
<v Chris>Brentley caught up with him right afterwards.

00:12:08.246 --> 00:12:13.352
<v Chris>And Major shared a few stories. And one of them was about just getting started

00:12:13.352 --> 00:12:16.582
<v Chris>with this tooling to learn it because that's where we're at in this day and age.

00:12:16.988 --> 00:12:20.402
<v Chris>And sometimes troubleshooting problems on your system, not building some crazy

00:12:20.402 --> 00:12:24.202
<v Chris>app or vibe coding, but just like solving something like Wi-Fi,

00:12:24.202 --> 00:12:27.251
<v Chris>if you're having Wi-Fi issues, can be a great way to learn these tools.

00:12:28.360 --> 00:12:31.697
<v Clips>And just try something, try something small or go to a code base you've always

00:12:31.697 --> 00:12:34.747
<v Clips>had and say, hey, you know, this doesn't work as well as I like,

00:12:34.747 --> 00:12:39.191
<v Clips>or this is slow, or I always have a bug with this, or the program crashes in this spot.

00:12:39.667 --> 00:12:43.137
<v Clips>Just find something small. I've even had fun connecting my phone,

00:12:43.137 --> 00:12:46.707
<v Clips>like I have an Android phone, I'll turn on USB debugging and I'll just say,

00:12:46.707 --> 00:12:49.866
<v Clips>hey, like help me figure out why my Wi-Fi always drops.

00:12:50.249 --> 00:12:53.487
<v Clips>And sure enough, it looks at the logs and says, hey, your router's misconfigured.

00:12:53.487 --> 00:12:57.215
<v Clips>And I'm like, okay, here's a read-only login to my router.

00:12:57.581 --> 00:13:00.257
<v Clips>I will let you have a look and it looks and it's like yep there it is right

00:13:00.257 --> 00:13:03.147
<v Clips>there and I'm like what does that setting mean you know what does it mean if

00:13:03.147 --> 00:13:06.770
<v Clips>I change it what are the trade-offs and that kind of stuff is so fun because

00:13:06.886 --> 00:13:11.188
<v Clips>all the things that you thought were beyond you before are now in your grasp.

00:13:12.192 --> 00:13:15.890
<v Chris>Yeah, it is true. It's been really useful for me for troubleshooting my Android tablets.

00:13:16.209 --> 00:13:16.687
<v Wes>Oh, yeah.

00:13:16.687 --> 00:13:17.835
<v Chris>And the Android TV stuff.

00:13:18.837 --> 00:13:22.587
<v Wes>I moved to a new phone. I had to refurb a phone, get a new version of the same

00:13:22.587 --> 00:13:27.137
<v Wes>phone, and having easy control of a bunch of the ADB stuff to move files on and off.

00:13:27.477 --> 00:13:31.217
<v Wes>It was a whole other way to do it that made it much more doable before a tight travel schedule.

00:13:31.217 --> 00:13:34.907
<v Chris>That's how I'm doing my all-future phone migration. 100%.

00:13:35.434 --> 00:13:38.007
<v Chris>Brian, you had a nice long chat with Major, and I think we're going to have

00:13:38.007 --> 00:13:41.827
<v Chris>an opportunity to play the entire thing in the future. But I just want to,

00:13:41.827 --> 00:13:43.927
<v Chris>you know, you, you had some, you spent the most time with them,

00:13:43.927 --> 00:13:44.763
<v Chris>kind of get your impressions.

00:13:45.686 --> 00:13:50.138
<v Brent>Yeah, I did spend a while. Usually we like to get in and do like quick little,

00:13:50.324 --> 00:13:51.407
<v Brent>you know, audio interviews.

00:13:51.407 --> 00:13:55.322
<v Brent>And I just got, I don't know, something about his philosophies around,

00:13:55.978 --> 00:14:01.697
<v Brent>especially the technology of today and AI and how to approach it in a way that won't make you sad.

00:14:02.503 --> 00:14:08.047
<v Brent>And also like he has been using it to help his son learn math and stuff.

00:14:08.047 --> 00:14:11.927
<v Brent>So there's just like some really nice ways to approach modern technology,

00:14:11.927 --> 00:14:12.958
<v Brent>if you want to put it that way.

00:14:13.405 --> 00:14:17.097
<v Brent>I did notice some people in the background while I was interviewing that were

00:14:17.097 --> 00:14:20.577
<v Brent>like trying to distract me throughout. I don't know what that was about,

00:14:20.577 --> 00:14:25.386
<v Brent>but yeah, we'll have to give them a hard time. Thanks, guys.

00:14:25.880 --> 00:14:28.757
<v Brent>But I would say, yeah, we did do a long chat.

00:14:29.257 --> 00:14:33.707
<v Brent>I think we have hopes of releasing that somewhere. But if you have the time,

00:14:33.707 --> 00:14:38.765
<v Brent>you can totally watch his talk on the website. and it's 100% worth it.

00:14:39.555 --> 00:14:43.972
<v Chris>Yeah. We do have that bit where you talked about helping his kids learn. Let's play that.

00:14:44.286 --> 00:14:47.943
<v Clips>Well, especially when it comes to like mathematics and things,

00:14:47.943 --> 00:14:50.352
<v Clips>you know, obviously it's been trained on a lot of that material.

00:14:50.776 --> 00:14:53.933
<v Clips>But I think the awesome thing about it is that we all learn things differently.

00:14:53.933 --> 00:14:56.763
<v Clips>Like I talked about in the talk, I'm a very visual learner. If you draw me a

00:14:56.763 --> 00:15:00.377
<v Clips>picture, I will understand it. If you write me two paragraphs, I will struggle.

00:15:00.784 --> 00:15:04.583
<v Clips>And so a lot of times I'll ask a model, draw me a picture and I'll do the same,

00:15:04.583 --> 00:15:07.913
<v Clips>for example, with my son working on his math homework or my daughter,

00:15:07.913 --> 00:15:10.466
<v Clips>you know, sometimes I'll try and help summarize something in Texas history,

00:15:10.867 --> 00:15:12.723
<v Clips>you know, that's a little bit difficult to understand.

00:15:12.723 --> 00:15:16.620
<v Clips>And so I'll say like, okay, you know, how can we explain something like this on that level?

00:15:17.014 --> 00:15:20.593
<v Clips>Or sometimes my, you know, what'll happen in math is the teacher teaches something

00:15:20.593 --> 00:15:22.378
<v Clips>in a certain way or teaches a method.

00:15:22.837 --> 00:15:25.533
<v Clips>And I'm like, there's got to be a better method out there for doing it and go

00:15:25.533 --> 00:15:27.388
<v Clips>to Claude and say, don't give me the answer.

00:15:27.939 --> 00:15:32.221
<v Clips>Here's the problem. My son is in 11th grade taking pre-calculus and AP pre-cal.

00:15:32.611 --> 00:15:35.953
<v Clips>Help us figure out two or three different ways to solve this problem that would

00:15:35.953 --> 00:15:37.708
<v Clips>be memorable for him on the test.

00:15:38.312 --> 00:15:40.813
<v Clips>And then I sit down with him and I'm like, Hey, do any of these resonate with

00:15:40.813 --> 00:15:44.412
<v Clips>you? And he's like that middle one, it uses the Pascal's triangle. I'm good at that.

00:15:44.685 --> 00:15:46.786
<v Clips>And I'm like, okay, well let's have Claude dig into that one.

00:15:47.070 --> 00:15:51.018
<v Clips>And so then we'll dig in and I'll find the way his mind works,

00:15:51.390 --> 00:15:54.878
<v Clips>the way his, you know, internal LLM trains itself, you know,

00:15:55.494 --> 00:15:58.803
<v Clips>and then I'll use Claude to basically say, okay, well, let's,

00:15:58.803 --> 00:16:03.365
<v Clips>let's save this so that, you know, you are a visual learner and you love Pascal's triangle.

00:16:03.638 --> 00:16:06.533
<v Clips>So maybe Claude can And every time we talk to it about that,

00:16:06.533 --> 00:16:09.263
<v Clips>it can go back to that for you. And so that we can work on that on your homework.

00:16:09.640 --> 00:16:13.698
<v Chris>Helping unlock how your kid learns is such a huge win for a parent.

00:16:13.815 --> 00:16:15.602
<v Brent>I thought that was so brilliant.

00:16:16.304 --> 00:16:19.399
<v Brent>And if you only take that away from the talk, totally worth it.

00:16:19.399 --> 00:16:20.449
<v Brent>But there was much more to it.

00:16:21.366 --> 00:16:24.609
<v Wes>I think that's been maybe an underappreciated part of these tools is,

00:16:25.069 --> 00:16:28.449
<v Wes>yes, you can use them to push the edge or solve new math or build programs that

00:16:28.449 --> 00:16:29.469
<v Wes>have never been made before.

00:16:30.009 --> 00:16:33.619
<v Wes>But they are also just so great at recontextualizing to meet you where you are

00:16:33.619 --> 00:16:36.539
<v Wes>at on your, right? Often in learning, you're like, if I hear it from two different

00:16:36.539 --> 00:16:39.669
<v Wes>ways, maybe that helps me or this textbook worked really well,

00:16:39.669 --> 00:16:40.893
<v Wes>but I hated that version.

00:16:41.224 --> 00:16:43.929
<v Wes>And the bot can just switch to meet you where you need it to be.

00:16:43.929 --> 00:16:44.602
<v Chris>Yeah, yeah.

00:16:45.421 --> 00:16:46.454
<v Chris>Major's always great.

00:16:48.561 --> 00:16:50.739
<v Chris>I think you could call him a regular Texas Linux Fest.

00:16:50.739 --> 00:16:51.399
<v Brent>Yeah.

00:16:51.399 --> 00:16:52.739
<v Wes>And a past guest on this year's show.

00:16:52.739 --> 00:16:55.406
<v Chris>Yep, yep. And when you see his name on the talk list, you go.

00:16:55.777 --> 00:16:57.112
<v Chris>If Major's doing a talk, you go.

00:16:58.049 --> 00:17:01.965
<v Chris>And then the nice thing was is Saturday was also our lunch day.

00:17:02.505 --> 00:17:05.729
<v Chris>I really appreciate that they do this. They give you a nice two-hour window

00:17:05.729 --> 00:17:09.639
<v Chris>on Saturday for the lunch, which is rare and very much appreciated.

00:17:10.115 --> 00:17:16.124
<v Chris>So we jumped in the car and we had to drive us, or at least attempt drive us, to the meetup location.

00:17:16.739 --> 00:17:21.000
<v Clips>It goes quick. It goes really quick. So it was nice to chat with Major Hayden.

00:17:21.493 --> 00:17:26.253
<v Clips>And now it's time to go get lunch. Already? And this time we're going just a little bit early.

00:17:26.770 --> 00:17:29.439
<v Clips>So that way maybe we have a chance to get food before people show up.

00:17:29.439 --> 00:17:33.709
<v Clips>We can suss it out, check out what's good, what's not good, get recommendations,

00:17:33.709 --> 00:17:36.179
<v Clips>make it seem like we know what we're doing, instead of just showing up blunt.

00:17:36.179 --> 00:17:40.709
<v Clips>There's also probably a 50% chance there's already going to be some people there. Yes.

00:17:41.049 --> 00:17:42.901
<v Clips>No, I bring that up to 78.

00:17:45.549 --> 00:17:49.649
<v Clips>Oh, cool. That was a pretty good Dodge. I wish mine would Dodge like that.

00:17:50.149 --> 00:17:52.717
<v Clips>All right, we'll see how it goes. All I know is I'm going to get a taco.

00:17:52.850 --> 00:17:56.109
<v Chris>Yeah, there was people there. You were right, Brent. There was people there when we got there.

00:17:56.109 --> 00:17:58.394
<v Brent>Yeah, that bumps it up to at least 82% for next time.

00:17:58.992 --> 00:18:01.399
<v Chris>We're doing the self-driving thing, and we're taking a route,

00:18:01.399 --> 00:18:06.169
<v Chris>and it takes us in behind these buildings. And I'm like, this seems kind of sketch.

00:18:06.529 --> 00:18:10.469
<v Chris>And it keeps on going. And it ends up kind of almost looking like a military facility.

00:18:10.469 --> 00:18:12.219
<v Wes>Yeah, there was a really cool radio dish.

00:18:12.219 --> 00:18:12.519
<v Chris>Yeah.

00:18:12.519 --> 00:18:13.377
<v Brent>Yeah, it was awesome.

00:18:13.714 --> 00:18:16.219
<v Chris>Not used for a long time. And then we get to the end of this,

00:18:16.219 --> 00:18:19.298
<v Chris>what has turned into like this lane. And there's a fence.

00:18:20.070 --> 00:18:23.519
<v Chris>A locked fence. Yeah, a locked fence that you can't get past.

00:18:23.519 --> 00:18:27.739
<v Chris>And it dawns on me that everybody that's visiting the area, that's attending

00:18:27.739 --> 00:18:29.329
<v Chris>the meetup, is going to get sent

00:18:29.329 --> 00:18:31.423
<v Chris>this same route. Because we're just using what's on Google Maps. Yeah.

00:18:32.666 --> 00:18:37.133
<v Chris>And sure enough, everybody that didn't know the area got sent down that route.

00:18:37.133 --> 00:18:39.963
<v Chris>One guy jumped the fence because he walked it because he said it was walking

00:18:39.963 --> 00:18:42.613
<v Chris>distance. Well, the map said it was walking distance.

00:18:42.613 --> 00:18:43.953
<v Brent>Jumped the fence.

00:18:44.513 --> 00:18:48.670
<v Chris>He jumped the fence. Then to make things even more complicated,

00:18:49.082 --> 00:18:51.493
<v Chris>Meetup, of course, gets the time zone wrong.

00:18:51.493 --> 00:18:55.328
<v Chris>So it had the wrong time listed for everybody. So the people that weren't able

00:18:55.462 --> 00:18:59.133
<v Chris>to do the time conversion or didn't think about doing the time conversion didn't

00:18:59.133 --> 00:19:01.483
<v Chris>know about the time. And despite all of that.

00:19:01.483 --> 00:19:04.193
<v Wes>Yeah, we made it as hard as possible for y'all, and we're sorry.

00:19:04.693 --> 00:19:09.033
<v Chris>Despite all that, we filled up the outside venue of the Austin Beer Works,

00:19:09.033 --> 00:19:11.003
<v Chris>and we couldn't have had more people.

00:19:11.003 --> 00:19:14.503
<v Wes>Super grateful that you managed to figure out how to get there and come, despite of it.

00:19:14.503 --> 00:19:20.223
<v Chris>Yeah, it really was. It was great. And, you know, I'm not a very social person,

00:19:20.223 --> 00:19:21.793
<v Chris>and I still love these things.

00:19:22.263 --> 00:19:25.893
<v Chris>And one of the more difficult things, and I'm always glad we do it,

00:19:25.893 --> 00:19:29.663
<v Chris>is, you know, you've been going all day. you sit down and you're eating and

00:19:29.663 --> 00:19:32.513
<v Chris>maybe you're drinking and you just want to sit there and just chat.

00:19:33.408 --> 00:19:37.683
<v Chris>But everybody's there to say hi to us and if they've traveled so we get up and

00:19:37.683 --> 00:19:39.370
<v Chris>we mingle and then we always love doing it.

00:19:39.822 --> 00:19:42.829
<v Chris>But it's hard at first to get up and do that initial mingling often for me.

00:19:43.236 --> 00:19:44.228
<v Chris>And I'm always really grateful.

00:19:44.408 --> 00:19:47.033
<v Wes>And it's bittersweet because we never get to talk to everyone there.

00:19:47.033 --> 00:19:48.833
<v Wes>We try to talk to as many people as we can.

00:19:51.165 --> 00:19:56.373
<v Chris>And we try to get some on audio like James and this was James' very first Linux.

00:19:57.046 --> 00:20:03.692
<v Clips>Any advice on someone who hasn't been to a fest before, how to approach it?

00:20:04.540 --> 00:20:09.613
<v Clips>Try talking to people, I guess. I feel like it could be very easily something

00:20:09.613 --> 00:20:16.273
<v Clips>that you just show up and then kind of go through the motions and never really get connected.

00:20:17.334 --> 00:20:21.473
<v Clips>There's so much more value when you're able to chat with people on what you

00:20:21.473 --> 00:20:23.193
<v Clips>saw or just about things.

00:20:24.134 --> 00:20:28.751
<v Clips>interesting topics, you know? So yeah, don't, don't forget to chat with people.

00:20:28.751 --> 00:20:30.595
<v Clips>So yeah. Nice. Thanks, James.

00:20:31.124 --> 00:20:32.952
<v Clips>All right. Good to, good to talk.

00:20:33.243 --> 00:20:36.351
<v Chris>It's funny how the gate broke for just a moment. You wouldn't get the sense

00:20:36.351 --> 00:20:39.061
<v Chris>there was anybody there and then the gate broke for you. You can hear there's

00:20:39.061 --> 00:20:39.977
<v Chris>actually quite a crowd there.

00:20:40.761 --> 00:20:45.791
<v Chris>But how good is that audio considering that really? So I, I have thoughts,

00:20:45.791 --> 00:20:50.971
<v Chris>you know, I have been going to Texas Linux Fest for many, many years and been

00:20:50.971 --> 00:20:55.407
<v Chris>going since before COVID and we've been going after COVID,

00:20:56.283 --> 00:20:58.768
<v Chris>and it kind of doesn't feel the same.

00:20:59.041 --> 00:21:05.136
<v Chris>And I'm not sure if it's me, if it's the fest, if it's times are changing.

00:21:06.521 --> 00:21:11.001
<v Chris>It feels like there's a broadening happening of folks that are out there in

00:21:11.001 --> 00:21:15.511
<v Chris>the industry, and they're working with Kubernetes and their VMs and their Red

00:21:15.511 --> 00:21:19.457
<v Chris>Hat Enterprises and their Enterprise SUSAs and their Ubuntu LTSs.

00:21:20.113 --> 00:21:23.850
<v Chris>and they, you know, they'll be doing that for another 10 years.

00:21:24.942 --> 00:21:28.777
<v Chris>And then there's another half that's attending these events and they're building

00:21:28.777 --> 00:21:32.997
<v Chris>like these new workflows that aren't fully figured out yet. And they're looking

00:21:32.997 --> 00:21:35.560
<v Chris>to see how other people are solving these problems.

00:21:36.047 --> 00:21:41.487
<v Chris>And they don't want to be told how to solve XYZ backup problem or they don't

00:21:41.487 --> 00:21:46.682
<v Chris>need the 15th introduction to Postgres or the 20th introduction on how to make a Debian package.

00:21:47.187 --> 00:21:52.317
<v Chris>What they need is how somebody who's out there in the thick of things is fixing

00:21:52.317 --> 00:21:54.223
<v Chris>and solving problems and delivering.

00:21:55.059 --> 00:21:58.337
<v Chris>And they want to see them doing that. And that was something I just kept hearing

00:21:58.337 --> 00:22:01.987
<v Chris>from people over and over again was either, oh, man, the workshop was so great

00:22:01.987 --> 00:22:03.075
<v Chris>and I got exactly what I needed.

00:22:03.447 --> 00:22:08.227
<v Chris>Or I heard, I don't really like any of these talks and I just want to ask people

00:22:08.227 --> 00:22:10.977
<v Chris>what they're doing and how they're doing it. And none of this is really working

00:22:10.977 --> 00:22:13.141
<v Chris>for me, but the hallway track's been great.

00:22:13.844 --> 00:22:17.247
<v Chris>And I'm curious if you boys heard similar things, if that was an impression

00:22:17.247 --> 00:22:19.299
<v Chris>you walked away with. Brent, was that true for you?

00:22:20.042 --> 00:22:24.727
<v Brent>Yeah, I kept hearing over and over that people were really just hanging out outside the talks.

00:22:24.727 --> 00:22:29.557
<v Brent>been getting a lot of benefit from that um i didn't get as many people saying

00:22:29.557 --> 00:22:31.957
<v Brent>oh yeah i went to this talk it was really interesting i went to this talk it

00:22:31.957 --> 00:22:34.305
<v Brent>was really interesting that we get sometimes at other fests so,

00:22:34.862 --> 00:22:40.261
<v Brent>i think that really is the same sentiment i got that you did was like people,

00:22:41.056 --> 00:22:44.447
<v Brent>it felt a little different and we were trying to figure it out the whole time

00:22:44.447 --> 00:22:49.549
<v Brent>i think maybe we have some theories um but that's the takeaway that i had.

00:22:50.395 --> 00:22:52.922
<v Chris>I thought, Wes, one of the things was a sort of split. Like some of the people

00:22:52.922 --> 00:22:56.162
<v Chris>I talked to that were new timers, like I said, that were out in the industry,

00:22:56.162 --> 00:22:59.979
<v Chris>they're like, oh, yeah, this is really helpful to learn how I make an RPM package.

00:23:00.897 --> 00:23:04.962
<v Chris>And then other folks that had been going for a while, the conversation often

00:23:04.962 --> 00:23:09.612
<v Chris>drifted to how could you make a better fest? How would you do this if you were setting this up?

00:23:09.612 --> 00:23:14.271
<v Wes>Yeah, we spent a lot of time having meta conversation about what we want to see out of the event.

00:23:15.282 --> 00:23:19.472
<v Wes>and events like these. A lot of trying to compare and contrast to some of the

00:23:19.472 --> 00:23:24.092
<v Wes>other events we go to and which ones we find more like, because always we get distracted.

00:23:24.092 --> 00:23:26.982
<v Wes>The hallway talk is like, track is like half of why we're there anyway because

00:23:26.982 --> 00:23:29.352
<v Wes>we want to meet new people. We want to make relationships. We want to see all

00:23:29.352 --> 00:23:33.122
<v Wes>of the wonderful audience members. But there's a big, I think that one of the

00:23:33.122 --> 00:23:36.072
<v Wes>factors we see is like how pulled and forced are we to like,

00:23:36.072 --> 00:23:37.711
<v Wes>we need to see what these talks are about.

00:23:37.937 --> 00:23:40.332
<v Wes>Or like, this is something I want to capture that information.

00:23:40.332 --> 00:23:44.102
<v Wes>And there's a huge variance between some of these events. and that's one of

00:23:44.102 --> 00:23:45.262
<v Wes>the things we were noticing at Texas.

00:23:45.622 --> 00:23:51.068
<v Chris>Yeah, and this holds true for the LinuxFest Northwest up here in Bellingham,

00:23:51.637 --> 00:23:55.950
<v Chris>and it seems to be even true for Texas LinuxFest in Austin.

00:23:57.430 --> 00:24:02.126
<v Chris>You wouldn't know some of the biggest names in technology are right next door,

00:24:02.254 --> 00:24:06.439
<v Chris>especially for Texas Linux. It's like Microsoft actually makes an appearance at our event.

00:24:07.293 --> 00:24:11.699
<v Chris>But down there, there are ginormous tech companies. And the way we know that

00:24:11.699 --> 00:24:13.659
<v Chris>is because, well, A, we know what companies are down there. But B,

00:24:13.659 --> 00:24:16.599
<v Chris>some of the staff show up on their own volition. And then they're like,

00:24:16.599 --> 00:24:17.565
<v Chris>oh, yeah, I work at Apple.

00:24:17.774 --> 00:24:20.239
<v Chris>Oh, yeah, I work at Dell. Oh, yeah, I work at XYZ.

00:24:20.579 --> 00:24:23.449
<v Wes>Or as you're driving around the city, you see the names on the signs.

00:24:23.449 --> 00:24:27.239
<v Chris>Right, all the big tech names that have Austin offices. But they're not supporting

00:24:27.239 --> 00:24:31.329
<v Chris>the fest. They're not showing up at the fest as vendors or holding talks.

00:24:32.003 --> 00:24:33.639
<v Chris>And I don't know why that is.

00:24:34.799 --> 00:24:38.400
<v Chris>But anyways, it just strikes me because when we step outside the fest,

00:24:38.725 --> 00:24:40.763
<v Chris>that's when we have all those interactions, which was wild.

00:24:42.159 --> 00:24:45.979
<v Chris>I don't know. And speaking of that, we had the opportunity to spend Sunday at

00:24:45.979 --> 00:24:48.689
<v Chris>the FUTO offices, which was a really neat opportunity.

00:24:48.799 --> 00:24:52.466
<v Wes>Yeah, big thank you to them for taking the time and showing up on the weekend to show us around.

00:24:53.023 --> 00:24:59.420
<v Chris>Now, you listening at home, you remember Futo, right? They make that fantastic keyboard for Android.

00:24:59.797 --> 00:25:02.919
<v Chris>And, of course, they've been providing support for the Image Project,

00:25:02.919 --> 00:25:05.769
<v Chris>which is now a full team, which is really cool.

00:25:05.769 --> 00:25:06.359
<v Wes>So excited.

00:25:06.359 --> 00:25:09.759
<v Brent>Like a full team of, like, 11 people, which is, wow.

00:25:10.459 --> 00:25:15.126
<v Chris>I am such a fan of Image, too. And then they have, really, a handful of projects,

00:25:15.539 --> 00:25:20.345
<v Chris>including Futo Notes, Futo Voice, Grey J, Polycentric.

00:25:21.461 --> 00:25:25.810
<v Chris>fcast live captions and fubs and ret i mean there's they have a whole fleet

00:25:25.810 --> 00:25:30.650
<v Chris>of open source stuff and they're also actively supporting um 501c free software

00:25:30.650 --> 00:25:31.570
<v Chris>projects yeah they've got.

00:25:31.570 --> 00:25:32.926
<v Wes>Grants you can apply for and.

00:25:33.071 --> 00:25:35.960
<v Chris>That kind of stuff and it was we saw their office and that's been really great

00:25:35.960 --> 00:25:38.070
<v Chris>and got to see some of the things that they're working on that i'm sure we'll

00:25:38.070 --> 00:25:41.670
<v Chris>be talking about in the future and stuff like that and that's just an example of um,

00:25:42.237 --> 00:25:47.180
<v Chris>you know they have a big old office right there in austin 30 minutes and i'm

00:25:47.180 --> 00:25:50.420
<v Chris>not shaming them because their staff went and And that's how we found out about it.

00:25:50.420 --> 00:25:54.270
<v Chris>And other companies send their staff. But there's some sort of disconnect because

00:25:54.270 --> 00:25:55.873
<v Chris>it's a community event or whatever it is.

00:25:56.285 --> 00:26:01.340
<v Chris>But also because it feels like some of the companies that are in that area aren't

00:26:01.340 --> 00:26:02.840
<v Chris>working on those things anymore.

00:26:02.840 --> 00:26:07.500
<v Chris>They're working on new stuff. And the Fest is talking about the stuff that we

00:26:07.500 --> 00:26:10.250
<v Chris>were talking about before COVID for a lot of it. Not all of it,

00:26:10.250 --> 00:26:13.050
<v Chris>but a lot of it. And that's just, I don't know.

00:26:14.459 --> 00:26:17.830
<v Wes>It's something we're going to be paying a lot of attention to and kind of trying

00:26:17.830 --> 00:26:20.760
<v Wes>to see where this goes. and what are the sustainable models because we want

00:26:20.760 --> 00:26:24.920
<v Wes>to see these events continue. They are an important function for folks who want

00:26:24.920 --> 00:26:29.378
<v Wes>to learn more to pass on the culture and the knowledge and the communities that we have.

00:26:29.686 --> 00:26:32.880
<v Chris>You know, it would be a good perspective. And also the patron that made a possible

00:26:32.880 --> 00:26:34.330
<v Chris>tech dev for us to go down there,

00:26:36.210 --> 00:26:40.877
<v Chris>TechDev, I think this is, is this like your second, was this your second or third Texas Linux Fest?

00:26:41.237 --> 00:26:46.027
<v Mumble>Second Linux Fest, or sorry, second Texas Linux Fest, fourth Fest overall.

00:26:46.619 --> 00:26:50.253
<v Mumble>Yeah, I think your observations are apt, that,

00:26:52.273 --> 00:26:56.147
<v Mumble>in the past, in the Fest that I've been at, the talks have been the star,

00:26:56.147 --> 00:26:57.857
<v Mumble>the hallway track is a bonus.

00:26:58.275 --> 00:27:02.629
<v Mumble>And this year, the talks were engaging.

00:27:02.757 --> 00:27:06.217
<v Mumble>I could tell that the presenters were very into what they were into,

00:27:06.217 --> 00:27:10.284
<v Mumble>but they weren't into the same things that I was trying to move forward with.

00:27:10.673 --> 00:27:13.965
<v Mumble>Looking at the schedule, I don't think there was much similar to my own talk.

00:27:14.214 --> 00:27:19.717
<v Mumble>That being said, though, I do echo that many conversations in and around the

00:27:19.717 --> 00:27:24.727
<v Mumble>participants did seem to push more towards we're here to connect with each other,

00:27:24.727 --> 00:27:28.384
<v Mumble>but the topics don't match up with what we're connecting on in the hallway.

00:27:29.127 --> 00:27:34.973
<v Chris>Okay. So I wonder if this is where scale has kind of found the recipe. Not completely.

00:27:36.680 --> 00:27:40.707
<v Chris>but you have sub-conferences that are focused. And let's stick with this.

00:27:40.707 --> 00:27:43.257
<v Chris>We'll move on quick, and we'll come back to this, but we'll stick with this

00:27:43.257 --> 00:27:44.284
<v Chris>later, I guess what I'm trying to say.

00:27:44.754 --> 00:27:47.959
<v Chris>But maybe these are too broad and too general now.

00:27:48.684 --> 00:27:53.007
<v Chris>And I want to test that theory by switching gears now and talking about going

00:27:53.007 --> 00:27:54.697
<v Chris>to Ubuntu Summit, which is the

00:27:54.697 --> 00:27:58.356
<v Chris>exact opposite of a broad thing and is very much a very focused summit.

00:27:58.802 --> 00:28:03.243
<v Chris>So you guys really went from one type of event to a totally different type of event.

00:28:06.152 --> 00:28:08.972
<v Chris>When I first started putting my websites online back in the day,

00:28:09.320 --> 00:28:12.331
<v Chris>it was a project in itself. The hosting, the domain, the designing,

00:28:12.331 --> 00:28:15.166
<v Chris>the figuring out the toolkit, the weekends of research.

00:28:15.630 --> 00:28:19.331
<v Chris>That's why when I tried Hostinger's AI Builder, not only was I surprised that

00:28:19.331 --> 00:28:22.781
<v Chris>you could get started without having to create an account, but the mix of being

00:28:22.781 --> 00:28:25.911
<v Chris>able to bring your own assets and prompt your way through it was pretty nice.

00:28:26.154 --> 00:28:29.191
<v Chris>And now, several weeks later, after I've hatched more chickens and I need to

00:28:29.191 --> 00:28:32.586
<v Chris>update my website, their tooling makes it straightforward to do that as well.

00:28:32.929 --> 00:28:36.711
<v Chris>And if you ever get stuck trying to figure out how to optimize SEO or maybe

00:28:36.711 --> 00:28:41.160
<v Chris>get some good copy for your website, Hostinger has tools to help you there as well.

00:28:41.590 --> 00:28:45.241
<v Chris>But I think what's most important right now is their Black Friday and Cyber

00:28:45.241 --> 00:28:47.006
<v Chris>Monday pricing. It's live.

00:28:47.279 --> 00:28:50.518
<v Chris>A premium plan is just $1.99 a month.

00:28:50.895 --> 00:28:54.750
<v Chris>Snag Hostinger services at their lowest prices before the sale ends.

00:28:55.040 --> 00:28:58.459
<v Chris>Create your website today for just $1.99.

00:28:58.778 --> 00:29:04.501
<v Chris>Go to Hostinger.com slash unplugged and use the code unplugged for an additional

00:29:04.501 --> 00:29:08.070
<v Chris>10% off the Black Friday and Cyber Monday pricing.

00:29:08.383 --> 00:29:13.701
<v Chris>That's Hostinger.com slash unplugged and use the promo code unplugged.

00:29:17.306 --> 00:29:22.861
<v Brent>Immediately after Texas Linux Fest, Wes and I headed out to London.

00:29:23.481 --> 00:29:27.691
<v Brent>That's not the little one in Ontario I'm used to. It's the one in the UK at

00:29:27.691 --> 00:29:30.657
<v Brent>Canonical's Invite to attend Ubuntu Summit.

00:29:31.139 --> 00:29:35.911
<v Brent>Wes, I think you made it home for a half day, and I didn't even make it home.

00:29:35.911 --> 00:29:40.781
<v Brent>I just stayed traveling. That's how close these two events were for us, and it was really fun.

00:29:41.901 --> 00:29:47.526
<v Brent>So the first day in London, as is, of course, tradition, we were running a little late.

00:29:48.559 --> 00:29:53.167
<v Clips>Well, it's our first proper morning in London, and we're already a little bit

00:29:53.167 --> 00:29:55.723
<v Clips>late. Oh, well, you know, the breakfast was amazing.

00:29:56.071 --> 00:29:58.828
<v Clips>Yeah, full English or full Indian.

00:29:59.316 --> 00:30:04.918
<v Clips>So we're just on our way trying to find Canonical's offices. Good luck to us both.

00:30:05.398 --> 00:30:07.087
<v Chris>Oh, so were you nearby, like in a hotel?

00:30:07.087 --> 00:30:10.257
<v Wes>Yeah, just not that far, turns out. I don't know, seven-minute walk.

00:30:10.257 --> 00:30:14.527
<v Wes>But we had only seen the hotel and not actually seen how to get into this large

00:30:14.527 --> 00:30:18.047
<v Wes>office park building. And we're, like, on the wrong side of the building.

00:30:18.387 --> 00:30:20.867
<v Wes>We're actively walking pretty quickly while recording that, obviously.

00:30:20.867 --> 00:30:24.577
<v Chris>Yeah, yeah. And trying to navigate a new space. And yeah, that's good.

00:30:24.577 --> 00:30:26.447
<v Chris>Hey, good on you. See, look at them.

00:30:26.767 --> 00:30:29.327
<v Brent>You got to stay to the left over there. It's really weird.

00:30:29.667 --> 00:30:32.733
<v Chris>Look at them. They're committing to it even when they're in a new space.

00:30:33.180 --> 00:30:36.287
<v Chris>So I imagine day one's a little bit of getting your bearings,

00:30:36.287 --> 00:30:40.597
<v Chris>figuring out that kind of stuff, meeting people, kind of seeing what the format

00:30:40.597 --> 00:30:42.407
<v Chris>is. A lot of it is just taking it in on day one.

00:30:42.407 --> 00:30:47.077
<v Wes>Yeah, meeting the very helpful staff, Leilani, our handler, showing us around,

00:30:47.077 --> 00:30:50.217
<v Wes>setting us up with where we even put our bags and our coats.

00:30:50.217 --> 00:30:53.847
<v Wes>And they've got wonderful little recording, sort of like quiet whisper room

00:30:53.847 --> 00:30:56.075
<v Wes>boots in the back, showing us how to get those.

00:30:56.383 --> 00:30:59.512
<v Brent>I think they built that for just for us because it worked wonderfully.

00:31:00.287 --> 00:31:02.542
<v Chris>I would really appreciate that. I would really appreciate that.

00:31:02.976 --> 00:31:06.737
<v Chris>So day one had a lot going on. I saw that there was a Notify Talk,

00:31:06.737 --> 00:31:11.074
<v Chris>NTFY, and that the next day you guys did have a chat with him about how it all went.

00:31:11.598 --> 00:31:16.447
<v Clips>Yesterday you gave a talk going through the journey of i guess i would call

00:31:16.447 --> 00:31:18.591
<v Clips>it the growth of the infrastructure behind notify.

00:31:19.608 --> 00:31:20.525
<v Chris>This is philip by the way.

00:31:20.704 --> 00:31:27.307
<v Clips>Turns out that's actually quite difficult you gave some stats 8.4 million notifications

00:31:27.687 --> 00:31:29.197
<v Clips>are going out every single day,

00:31:29.742 --> 00:31:35.457
<v Clips>you also said 1.4 billion push notifications have been sent out since 2022 what

00:31:35.457 --> 00:31:38.345
<v Clips>did you learn about the infrastructure to make all that happen.

00:31:39.152 --> 00:31:44.928
<v Clips>Yeah, it's been quite the journey. If you saw the talk, you see that it started

00:31:44.928 --> 00:31:51.447
<v Clips>out really small with a tiny VM that was largely idle for a very long time.

00:31:51.662 --> 00:31:56.928
<v Clips>Didn't publicize the project actively other than a few subreddits.

00:31:56.928 --> 00:32:00.834
<v Clips>The self-hosted community has been really open to that sort of thing.

00:32:01.449 --> 00:32:07.388
<v Clips>And over the years, it's been really interesting to see how people use it.

00:32:07.388 --> 00:32:13.038
<v Clips>And as it's a publicly available free service with no sign-up,

00:32:13.038 --> 00:32:18.278
<v Clips>which is very rare on the internet, so people plugged it into all sorts of things.

00:32:18.278 --> 00:32:25.008
<v Clips>And as it has become more popular over the years, the infrastructure requirements

00:32:25.008 --> 00:32:26.746
<v Clips>have grown significantly.

00:32:27.065 --> 00:32:33.078
<v Clips>so in the last year especially with the raise of with the rise of ai and the agents now suggesting

00:32:33.438 --> 00:32:38.698
<v Clips>notify it has been interesting the growth has been like truly exploding from

00:32:39.018 --> 00:32:43.848
<v Clips>i think it was 7 million http requests per day to 60 million,

00:32:44.417 --> 00:32:50.228
<v Clips>which is absolutely bonkers not gonna lie so yeah you asked what did i learn

00:32:50.228 --> 00:32:55.038
<v Clips>uh it's a like i learned a lot of things but i learned how to scale a system.

00:32:55.538 --> 00:32:59.668
<v Clips>I mean, I've done that for my day job a lot, so it's not like I started from

00:32:59.668 --> 00:33:04.048
<v Clips>zero, but it was a little bit under pressure. I had to, you know,

00:33:04.048 --> 00:33:06.214
<v Clips>like, make sure it doesn't fall over.

00:33:07.478 --> 00:33:12.358
<v Clips>So I, you know, scaled the database, had read replicas, learned a lot about

00:33:12.358 --> 00:33:17.778
<v Clips>clustering and how to, like, cluster leaders and how to, yeah,

00:33:18.418 --> 00:33:23.158
<v Clips>lots of things like that, how to do shared rate limits across nodes it's absolutely,

00:33:24.538 --> 00:33:29.598
<v Clips>absolutely bonkers things all the state that you have to keep in memory you

00:33:29.598 --> 00:33:34.211
<v Clips>now have to share across a cluster and things like that yeah oof.

00:33:34.932 --> 00:33:38.401
<v Chris>I really do appreciate the Notify project. I've been using it a lot more myself.

00:33:38.401 --> 00:33:40.980
<v Wes>I mean, it really has become infrastructure in the last few years.

00:33:41.761 --> 00:33:45.001
<v Wes>The scale of that exponential curve is just mind-blowing. And yet,

00:33:45.001 --> 00:33:46.297
<v Wes>Phil's still just keeping it working.

00:33:46.703 --> 00:33:49.291
<v Brent>Yeah, I think sometimes we see these projects and just think,

00:33:49.291 --> 00:33:51.162
<v Brent>oh, yeah, it's like a really handy thing.

00:33:52.213 --> 00:33:55.191
<v Brent>But what really struck me was like, he's working super hard.

00:33:55.191 --> 00:34:01.021
<v Brent>And as it gets more and more popular, he's continuing to offer free service and somehow,

00:34:01.721 --> 00:34:05.331
<v Brent>waking up in the middle of the night when things go wrong And like you should

00:34:05.331 --> 00:34:07.850
<v Brent>he's talked in his the talk that he gave,

00:34:08.297 --> 00:34:14.721
<v Brent>about the extensive like ban list that he has and the number of very interesting

00:34:14.721 --> 00:34:18.554
<v Brent>but really not helpful ways that people use notify to like,

00:34:19.460 --> 00:34:22.331
<v Brent>save scripts for certain things.

00:34:22.331 --> 00:34:28.071
<v Brent>Like some people built a game that would use like two gigs of data through Notify

00:34:28.071 --> 00:34:33.511
<v Brent>to make the game. It's like all these wonderfully odd ways that people accidentally

00:34:33.511 --> 00:34:36.480
<v Brent>break Notify. So it sounds like quite the journey.

00:34:37.008 --> 00:34:38.663
<v Chris>Jeez, people, you can self-host it.

00:34:38.965 --> 00:34:39.421
<v Brent>Right?

00:34:39.421 --> 00:34:39.911
<v Chris>Gosh.

00:34:40.375 --> 00:34:46.501
<v Brent>The other thing that really stood out for me was he just like very gently mentioned

00:34:46.501 --> 00:34:51.201
<v Brent>how he's using a little bit of AI and seeing some AI contributions,

00:34:51.201 --> 00:34:55.236
<v Brent>but also using it on the back end. So he gave us a bit more perspective on that.

00:34:56.177 --> 00:35:00.074
<v Clips>There's a lot, I also said this in the talk, right? There's a lot of AI hate out there.

00:35:00.074 --> 00:35:07.154
<v Clips>I actually held back a lot before I published the Postgres integration because

00:35:07.154 --> 00:35:11.884
<v Clips>of, I got so much backlash because people noticed that it's AI,

00:35:11.884 --> 00:35:13.474
<v Clips>like nobody can write that much code.

00:35:13.474 --> 00:35:22.542
<v Clips>and I had attempted to sort of, not hide, but I had attempted to make it harder to see that it's AI.

00:35:23.324 --> 00:35:28.024
<v Clips>And people hated that. And they asked for an AI policy. And I'm like,

00:35:28.504 --> 00:35:31.344
<v Clips>why does it matter? I'm looking at every single line of code.

00:35:31.804 --> 00:35:35.184
<v Clips>I'm the author, even though AI wrote it.

00:35:35.876 --> 00:35:42.364
<v Clips>I came up with the concepts and such. And it took a long time to just say, screw those people.

00:35:42.844 --> 00:35:48.764
<v Clips>this is my project i know what i'm doing i'm using it the right way i'm i'm

00:35:48.764 --> 00:35:53.084
<v Clips>using this superpower and i'm choosing to do it out in the open now so now i

00:35:53.084 --> 00:35:57.499
<v Clips>have an ai policy and i say i use it here's how i use it here's how i,

00:35:58.224 --> 00:36:02.634
<v Clips>review and test and whatnot and as i said in the talk i probably review and

00:36:02.664 --> 00:36:08.538
<v Clips>test much more because it's someone else's code as a software engineer you do code review for a living

00:36:08.950 --> 00:36:12.654
<v Clips>so like this is just another code review but you scrutinize it more because

00:36:12.654 --> 00:36:17.478
<v Clips>you know the person or aka the ai sitting across from you,

00:36:18.082 --> 00:36:23.304
<v Clips>doesn't have a brain they just complete you know the autocomplete on steroids

00:36:23.304 --> 00:36:27.265
<v Clips>and so you have to think critically and and sort of.

00:36:28.524 --> 00:36:33.744
<v Clips>You know treat it as as a as if an untrusted party wrote it so,

00:36:34.744 --> 00:36:39.734
<v Clips>i mean to wrap it up i'm like Like, I'm super happy with how I can use AI and

00:36:39.734 --> 00:36:46.375
<v Clips>how it is development on steroids and the things that I can do now that I couldn't before.

00:36:47.171 --> 00:36:48.100
<v Chris>So, day one.

00:36:49.196 --> 00:36:53.812
<v Chris>Are your impressions, this is more hands-on type sessions? These are people

00:36:53.812 --> 00:36:56.112
<v Chris>doing work and they're showing you how they're working? Is it more,

00:36:56.112 --> 00:36:58.889
<v Chris>or is it more like talks on like, here's how to make a snap?

00:36:59.081 --> 00:37:02.482
<v Wes>There were a few talks about some of the internal, you know,

00:37:02.482 --> 00:37:07.446
<v Wes>like from Canonical employees about Canonical things. Like we heard a lot about Workshop.

00:37:08.102 --> 00:37:09.422
<v Chris>Well, that's actually, I mean, that's interesting.

00:37:10.682 --> 00:37:15.432
<v Wes>No, it was almost exclusively about, you know, folks either from companies and

00:37:15.432 --> 00:37:18.626
<v Wes>what they're doing or independent open source projects.

00:37:18.986 --> 00:37:23.212
<v Wes>and what people have been building. So it was way more on the look at this thing

00:37:23.212 --> 00:37:27.992
<v Wes>that we're doing or pushing towards or this thing that I've built.

00:37:27.992 --> 00:37:32.308
<v Wes>And a lot of emphasis on the open source and the community side of that and the intersection of...

00:37:33.140 --> 00:37:38.579
<v Wes>you know building open source and how we navigate this in the in the new era and the new tools.

00:37:39.316 --> 00:37:42.697
<v Chris>Your thoughts brent on the different styles implementations here which which

00:37:42.697 --> 00:37:45.556
<v Chris>has worked better for you so far i mean i know this is just day one so far but

00:37:45.777 --> 00:37:47.588
<v Chris>on day one what had worked better for you so far.

00:37:48.058 --> 00:37:51.177
<v Brent>Yeah i think day one was a bit of a surprise for me because the energy we had

00:37:51.177 --> 00:37:54.987
<v Brent>at texas linux fest was like go and hang out with people it's kind of a little

00:37:54.987 --> 00:37:59.852
<v Brent>bit more i don't know slow paced hangout which was nice in its own way for sure,

00:38:00.328 --> 00:38:05.167
<v Brent>um but i i had a little bit of chalk a because of the crazy time zone changes

00:38:05.167 --> 00:38:09.865
<v Brent>that we had been subjected to but also the density of information,

00:38:10.487 --> 00:38:14.737
<v Brent>uh and just really neat stuff that like it was like bang bang bang each talk

00:38:14.737 --> 00:38:16.065
<v Brent>was something really interesting,

00:38:16.623 --> 00:38:21.397
<v Brent>and like for instance uh john did an opening keynote that mentioned everything

00:38:21.397 --> 00:38:24.744
<v Brent>in the last episode here on linux unplugged that he mentioned which was really great,

00:38:25.237 --> 00:38:29.987
<v Brent>and then we talked to pierre from canonical who we'll get into in a second but

00:38:29.987 --> 00:38:32.128
<v Brent>there were other talks that um,

00:38:32.905 --> 00:38:37.277
<v Brent>were just great open source projects one of them was about exoplanet hunting

00:38:37.277 --> 00:38:41.797
<v Brent>and how linux like automates a bunch of telescopes around the world which is

00:38:41.797 --> 00:38:43.677
<v Brent>oh that's cool you must love.

00:38:43.677 --> 00:38:44.266
<v Chris>That wes yeah.

00:38:44.643 --> 00:38:49.117
<v Wes>Yeah i mean the code that scientists produce and some of the processes and just

00:38:49.117 --> 00:38:54.418
<v Wes>the legacy there is wild and um you know having people who are able to

00:38:54.806 --> 00:38:57.757
<v Wes>take that to the next level and just make this the science part which is really

00:38:57.757 --> 00:39:00.780
<v Wes>the focus not all the things you got to do to get to the science work better

00:39:01.076 --> 00:39:02.330
<v Wes>it's going to have profound results.

00:39:03.311 --> 00:39:08.087
<v Brent>There was also a talk that mentioned text to cad which was really interesting

00:39:08.087 --> 00:39:12.497
<v Brent>like how to i don't know convert your thoughts to 3d objects you can then print

00:39:12.497 --> 00:39:15.588
<v Brent>and try that was pretty awesome uh so there were just,

00:39:16.447 --> 00:39:22.583
<v Brent>yeah lots there was the zed project was there qualcomm gave a talk so amd and video this was like,

00:39:23.547 --> 00:39:24.464
<v Brent>All the first day?

00:39:24.958 --> 00:39:25.364
<v Chris>Mm-hmm.

00:39:25.544 --> 00:39:25.811
<v Brent>So.

00:39:25.811 --> 00:39:29.881
<v Chris>Yeah, I did, I saw it, because in the next clip you mentioned that,

00:39:29.881 --> 00:39:33.758
<v Chris>but I didn't know Zed was there. That's neat. Yeah, we had long chats.

00:39:33.868 --> 00:39:36.601
<v Wes>We need to look at Delta, which is something they've been working on,

00:39:36.601 --> 00:39:38.451
<v Wes>and it is right up our alley.

00:39:38.451 --> 00:39:38.751
<v Chris>Okay.

00:39:38.751 --> 00:39:39.226
<v Brent>Oh, yeah.

00:39:39.685 --> 00:39:42.971
<v Chris>All right, well, on day two, it starts with a clip kind of wrapping up some of your thoughts.

00:39:43.620 --> 00:39:47.702
<v Clips>Well, it's day two at the Ubuntu Summit. We've made it back to the event.

00:39:48.194 --> 00:39:52.322
<v Clips>I chose the extra sleep option. Brent, you chose the full breakfast option.

00:39:52.537 --> 00:39:57.201
<v Clips>Yesterday, I had a wonderful Indian breakfast in the Great Hall in this hotel

00:39:57.201 --> 00:40:02.230
<v Clips>room, and I had to repeat that experience. And it was, I did not regret it. It was wonderful.

00:40:02.787 --> 00:40:07.692
<v Clips>Yeah, okay, so yesterday, full day, unconference, bunch of speakers,

00:40:08.290 --> 00:40:09.712
<v Clips>we kind of just had to take it all in.

00:40:10.124 --> 00:40:12.847
<v Clips>Today, we actually got to do some interviews.

00:40:13.456 --> 00:40:17.441
<v Clips>Yeah, I think we found our bearing now. It took us a day. What was your thought

00:40:17.441 --> 00:40:19.807
<v Clips>about the themes that came up yesterday?

00:40:20.126 --> 00:40:27.251
<v Clips>Yeah, I was impressed that it seemed like, one, they weren't shying away from AI eating everything.

00:40:27.711 --> 00:40:31.081
<v Clips>It didn't feel like a dirty word. I do think people were, you know,

00:40:31.081 --> 00:40:35.364
<v Clips>it wasn't baked into every talk or every sentence, so it wasn't a hype fest.

00:40:35.678 --> 00:40:41.211
<v Clips>But at the same time, it was like acknowledging engineering realities, maybe, right?

00:40:41.211 --> 00:40:44.871
<v Clips>Like, I was impressed with a diverse array of speakers, and it felt like many

00:40:44.871 --> 00:40:51.071
<v Clips>of them were working on adapting to, in this new era, what does what I do look like?

00:40:51.411 --> 00:40:55.941
<v Clips>It's like a new reality. Yes. And that included the folks at Canonical and how

00:40:55.941 --> 00:40:59.571
<v Clips>they're changing things and steering the ship, but also folks from,

00:40:59.571 --> 00:41:04.266
<v Clips>you know, folks from AMD, folks from Qualcomm, a diverse array of people.

00:41:05.142 --> 00:41:07.736
<v Clips>The Zed talk was excellent. The gentleman from Notify as well.

00:41:07.736 --> 00:41:09.826
<v Clips>He's like, oh, wait, actually, this tool is really helping me.

00:41:10.146 --> 00:41:13.722
<v Clips>So it was people unlocking new abilities, dreaming bigger.

00:41:13.919 --> 00:41:18.156
<v Clips>But also what really stuck out to me is like, these are serious professionals

00:41:18.156 --> 00:41:22.696
<v Clips>with long histories doing impressive, impressive feats of engineering.

00:41:23.079 --> 00:41:27.206
<v Clips>And they want to keep the bar high, right? This isn't like, I just need any

00:41:27.206 --> 00:41:32.309
<v Clips>implementation. It's like, how do I, how do I keep some of this craft and rigor?

00:41:32.663 --> 00:41:35.159
<v Clips>And how do we take rigor to the next level? Nice.

00:41:35.769 --> 00:41:41.826
<v Clips>my I think one thing I noticed was the striving everyone we heard from was like

00:41:41.826 --> 00:41:44.976
<v Clips>striving for the next thing oh I'm working on this currently it's really cool,

00:41:45.452 --> 00:41:47.872
<v Clips>I'm having successes and some challenges but like,

00:41:48.412 --> 00:41:51.066
<v Clips>I actually want to be over here like way over here and that's what I'm dreaming

00:41:51.066 --> 00:41:53.637
<v Clips>for and that's where I'm headed so it was nice to see,

00:41:54.187 --> 00:41:56.146
<v Clips>I don't know the inspiration I guess from,

00:41:57.966 --> 00:42:01.266
<v Clips>everywhere from Qualcomm all the way to like the Notify project and stuff like

00:42:01.266 --> 00:42:05.495
<v Clips>that so the theme was basically like just really interesting cool stuff happening,

00:42:06.139 --> 00:42:08.630
<v Clips>let's see if day two can match oh yeah i think i just started.

00:42:08.966 --> 00:42:12.989
<v Brent>Now day two was pretty much the exact same thing uh i was,

00:42:13.813 --> 00:42:17.286
<v Brent>just all of a sudden thrown into a bunch of really dense talks which is exactly

00:42:17.626 --> 00:42:21.926
<v Brent>why we were there and the one that stood out to me first thing in the morning

00:42:21.926 --> 00:42:26.590
<v Brent>was crosspoint now chris have you heard of crosspoint before.

00:42:27.526 --> 00:42:31.346
<v Chris>You know i've heard different Crosspoint name. So I wasn't, I didn't really

00:42:31.346 --> 00:42:34.226
<v Chris>ring a bell when I saw it. When I saw this come, when I saw this interview come

00:42:34.226 --> 00:42:36.816
<v Chris>through, I was like, Crosspoint, is this a new thing? Yeah.

00:42:36.816 --> 00:42:38.455
<v Wes>Almost sounds enterprise-y at first.

00:42:39.001 --> 00:42:44.056
<v Brent>That's almost identically how I felt until Justin just started introducing us

00:42:44.056 --> 00:42:48.296
<v Brent>to Crosspoint. And it turns out it's actually an extremely popular open source

00:42:48.296 --> 00:42:50.534
<v Brent>software for micro e-readers.

00:42:50.714 --> 00:42:54.776
<v Brent>You can get a ton of like teeny tiny little phone shaped e-readers with e-ink

00:42:54.776 --> 00:43:00.666
<v Brent>screens that are very inexpensive, and well, Crosspoint is like the de facto

00:43:00.666 --> 00:43:03.033
<v Brent>open source software that you can throw on these.

00:43:04.136 --> 00:43:06.469
<v Clips>Wonderful. And how the heck did you get involved in all that?

00:43:06.835 --> 00:43:11.394
<v Clips>Yeah, you know, I bought one of these after I saw it go viral on Reddit and

00:43:11.394 --> 00:43:14.144
<v Clips>thought, you know, for 50 bucks, what kind of, it's not that bad of a gamble,

00:43:14.144 --> 00:43:15.124
<v Clips>right? I might as well try.

00:43:15.544 --> 00:43:19.154
<v Clips>Within like minutes, was incredibly frustrated with the stock firmware.

00:43:19.154 --> 00:43:23.147
<v Clips>Found this open source project online called Crosspoint and said,

00:43:23.530 --> 00:43:26.384
<v Clips>you know what, this has a lot of, you know, promise behind it.

00:43:26.384 --> 00:43:29.399
<v Clips>Checked the open issues and said, I can knock those out.

00:43:29.776 --> 00:43:34.705
<v Clips>Knocked out a bunch of the issues. X-T8 came out with their second device, which was the X3.

00:43:34.984 --> 00:43:38.594
<v Clips>And I didn't even bother with the stock firmware and immediately started to

00:43:38.594 --> 00:43:39.918
<v Clips>port Crosspoint over to it.

00:43:40.231 --> 00:43:44.954
<v Clips>And it just got to a point where I was kind of the main person doing a lot of the stuff.

00:43:44.954 --> 00:43:48.704
<v Clips>And then it was like me and this other guy, and we were doing most of it together.

00:43:48.704 --> 00:43:52.314
<v Clips>And I thought, you know what? I should probably just ask the repo owner who

00:43:52.314 --> 00:43:55.235
<v Clips>hasn't been around in like six months if I can just buy it from him.

00:43:55.903 --> 00:43:58.564
<v Clips>Because what ended up actually happening is I was doing some stuff,

00:43:58.564 --> 00:44:01.804
<v Clips>especially around the jailbreaking of these devices. once they started getting

00:44:01.804 --> 00:44:05.584
<v Clips>locked down. I had to build a jailbreak tool and people were doing a bunch of

00:44:05.584 --> 00:44:10.607
<v Clips>like press and YouTube videos saying that the original project creator was the guy who did this.

00:44:11.135 --> 00:44:15.484
<v Clips>And not that I really cared about the credit, but I messaged him on Reddit and

00:44:15.484 --> 00:44:18.854
<v Clips>I was like, hey, just so you know, like I'm sort of kind of doing something

00:44:18.854 --> 00:44:22.504
<v Clips>that's maybe, I don't know, sketchy because it's jailbreaking something.

00:44:22.504 --> 00:44:26.044
<v Clips>And I don't want everyone saying that you were the person that did it because

00:44:26.044 --> 00:44:28.596
<v Clips>like you're not and you're not remotely involved.

00:44:28.870 --> 00:44:32.677
<v Clips>So like maybe we should just pass the torch so that I don't have to worry about impersonating you.

00:44:34.161 --> 00:44:39.221
<v Clips>I imagine he said yes. He did. You know, at that time, I had I'd offered him

00:44:39.221 --> 00:44:40.521
<v Clips>a price a couple of months ago.

00:44:40.981 --> 00:44:44.131
<v Clips>And, you know, because of the now the lockdown, I said, well,

00:44:44.131 --> 00:44:47.111
<v Clips>I don't know if it's quite worth what I had originally offered you.

00:44:47.111 --> 00:44:51.051
<v Clips>But I tell you what, I will honor that price in Australian dollars because that's

00:44:51.051 --> 00:44:53.541
<v Clips>where he's from. And that conversion rate worked out really great for me.

00:44:55.461 --> 00:44:56.091
<v Chris>That's good.

00:44:56.091 --> 00:44:59.861
<v Wes>I was really impressed how fast he went from like, oh, well,

00:45:00.053 --> 00:45:03.331
<v Wes>this might need a little help to I mean, he's totally transparent.

00:45:03.541 --> 00:45:07.601
<v Wes>transformed it from an open source product like an open product with a ton of

00:45:07.601 --> 00:45:11.571
<v Wes>focus on that whole vertical around like how do we make it easy how do we make

00:45:11.571 --> 00:45:14.409
<v Wes>it clear how do the defaults just work how do we make it so you can

00:45:14.722 --> 00:45:17.871
<v Wes>somebody has no idea has never heard of flashing a device can actually put this

00:45:17.871 --> 00:45:19.481
<v Wes>on the little reader they get just get started.

00:45:19.921 --> 00:45:21.705
<v Chris>And as they say read without limits.

00:45:22.621 --> 00:45:26.461
<v Wes>I even mentioned sort of trying to tick tockify reading he's like it might seem

00:45:26.461 --> 00:45:29.761
<v Wes>weird to have such a small device but there's something about the only so much

00:45:29.761 --> 00:45:34.011
<v Wes>on a single page that you just kind of want to keep tapping and it it turns

00:45:34.011 --> 00:45:35.521
<v Wes>out to be kind of addicting in a good way.

00:45:35.901 --> 00:45:39.331
<v Chris>Huh i saw too that uh he's at least in the talk it sounds like he gets into

00:45:39.331 --> 00:45:44.245
<v Chris>how some of his uh can his readers then became contributors to the project.

00:45:44.431 --> 00:45:46.071
<v Clips>Nice and so you gave a talk earlier

00:45:46.071 --> 00:45:51.646
<v Clips>today just describing the interesting challenge that happened when both,

00:45:52.098 --> 00:45:56.255
<v Clips>readers got very interested in all of a sudden customizing their devices and

00:45:56.441 --> 00:46:00.969
<v Clips>somehow they all had access to ai can you describe that journey because I found it really interesting.

00:46:01.439 --> 00:46:05.741
<v Clips>Yeah, you know, I think the vast majority of us in the open source community.

00:46:06.461 --> 00:46:09.851
<v Clips>Unless we are packaging something up as a simple app that you're going to get

00:46:09.851 --> 00:46:13.911
<v Clips>in the App Store or the Google Play Store or website, we think of our open source

00:46:13.911 --> 00:46:16.526
<v Clips>projects as sort of like by developers for developers.

00:46:16.886 --> 00:46:22.991
<v Clips>And it turns out that, yeah, developers 100% are part of this audience and they

00:46:22.991 --> 00:46:24.451
<v Clips>loved it and they're enjoying it.

00:46:24.451 --> 00:46:28.691
<v Clips>And I don't know, Maybe 30% of our contributors are all active readers on the

00:46:28.691 --> 00:46:32.182
<v Clips>device who love to develop code and read.

00:46:32.804 --> 00:46:36.339
<v Clips>And then there's a very large portion of our user base that are not developers

00:46:36.339 --> 00:46:40.385
<v Clips>at all. And they just love the idea of having a dedicated e-reader device.

00:46:40.710 --> 00:46:44.109
<v Clips>And maybe some of them are tinkerers. I wouldn't call them coders,

00:46:44.109 --> 00:46:46.769
<v Clips>but they kind of like this idea of having something they can mess with and they

00:46:46.769 --> 00:46:48.540
<v Clips>can, you know, customize and make their own.

00:46:48.888 --> 00:46:52.079
<v Clips>And so you put all those people, you know, in a room together.

00:46:52.079 --> 00:46:56.859
<v Clips>And what you have is a bunch of folks that all want a common goal of having

00:46:56.859 --> 00:47:04.209
<v Clips>a self-owned custom and made-to-order e-reader that does everything they want

00:47:04.209 --> 00:47:05.468
<v Clips>just the way they want it.

00:47:05.764 --> 00:47:08.086
<v Clips>And some of them know how to code and some of them don't know how to code.

00:47:08.219 --> 00:47:11.203
<v Clips>But thanks to AI, everyone can code.

00:47:11.673 --> 00:47:15.489
<v Clips>Sometimes it's a good thing. Sometimes it's a bad thing. You know, in our world,

00:47:15.869 --> 00:47:20.978
<v Clips>we're very welcoming of folks that want to come in and customize this thing,

00:47:21.216 --> 00:47:24.889
<v Clips>whether that's, you know, giving them an avenue to do that without having to

00:47:24.889 --> 00:47:27.556
<v Clips>do it on the firmware itself, or by just

00:47:27.927 --> 00:47:31.039
<v Clips>taking over the PR and saying, hey, this was an awesome idea.

00:47:31.039 --> 00:47:34.149
<v Clips>Like, I'm totally behind this. I'm going to rework some of this for you,

00:47:34.149 --> 00:47:35.822
<v Clips>but thank you so much for your contribution.

00:47:36.158 --> 00:47:40.129
<v Clips>So it's really just turned into kind of more of a community management thing

00:47:40.129 --> 00:47:45.109
<v Clips>than it really has a software development PR review thing, right?

00:47:45.589 --> 00:47:49.532
<v Clips>It becomes more about how you welcome people into the ecosystem,

00:47:49.747 --> 00:47:52.713
<v Clips>realizing that, yeah, maybe they're not all developers.

00:47:55.009 --> 00:47:58.238
<v Wes>This talk might be essential for folks in our community who are worried about

00:47:58.453 --> 00:48:00.415
<v Wes>the intersection of AI and open source.

00:48:01.053 --> 00:48:04.729
<v Wes>This is really getting ahead, I think, and working out patterns that we need.

00:48:05.109 --> 00:48:08.689
<v Wes>Because we've talked a lot about the struggles, right, of on one hand,

00:48:08.689 --> 00:48:11.309
<v Wes>you don't want to gatekeep because suddenly there's new access for people that

00:48:11.309 --> 00:48:13.439
<v Wes>have never been able to contribute to open source before.

00:48:13.439 --> 00:48:17.019
<v Wes>But we also know there's limited maintainer time. Like, you can't implement

00:48:17.019 --> 00:48:19.499
<v Wes>every feature. You don't want to tell people no all the time.

00:48:19.499 --> 00:48:22.218
<v Wes>You don't want to be really strict and unwelcoming.

00:48:22.462 --> 00:48:24.419
<v Wes>And you've got to figure out how you can advance the project,

00:48:24.419 --> 00:48:28.273
<v Wes>keep the project healthy, not burn out, and embrace this new wave.

00:48:28.714 --> 00:48:30.884
<v Wes>And the Crosspoint Project is doing it.

00:48:31.151 --> 00:48:34.809
<v Chris>So we have both day one and day two linked in the show notes.

00:48:34.809 --> 00:48:38.049
<v Chris>They're complete days. Maybe they'll add time codes or something else.

00:48:38.049 --> 00:48:40.849
<v Wes>They're working on splitting them out. Some of the early videos are already

00:48:40.849 --> 00:48:42.837
<v Wes>up, but the Ubuntu channel will have more of those.

00:48:44.429 --> 00:48:48.769
<v Chris>All right. I will have to watch the rest of that. Now, I've been kind of curious.

00:48:49.869 --> 00:48:54.989
<v Chris>This is all happening in the backdrop of we just had that kernel CVE that they

00:48:54.989 --> 00:48:58.639
<v Chris>sort of famously took a little while to get out. There's just been a lot of

00:48:58.639 --> 00:49:01.650
<v Chris>kernel patches that have been landing, a lot of security issues.

00:49:03.264 --> 00:49:08.159
<v Chris>Was security a topic? Did Canonical address their thoughts about the pace and

00:49:08.159 --> 00:49:09.069
<v Chris>all of this? Did that come up?

00:49:09.069 --> 00:49:13.569
<v Wes>Yeah. Yeah, in the keynote, we got to hear from John and Pierre,

00:49:13.569 --> 00:49:15.060
<v Wes>two of the VPs at Canonical,

00:49:16.009 --> 00:49:19.699
<v Wes>a lot on some of their programs like Surge and other projects where they are

00:49:19.699 --> 00:49:24.659
<v Wes>really trying to scale up the speed and, I mean, just pure scale of their ability

00:49:24.659 --> 00:49:27.059
<v Wes>to fix and apply patches and deliver them.

00:49:27.059 --> 00:49:29.539
<v Wes>And of course, we talked with John recently about Ubuntu Core,

00:49:29.539 --> 00:49:32.119
<v Wes>which is also part of that effort because you can, you know,

00:49:32.119 --> 00:49:34.291
<v Wes>with the core setup, you can really deliver things a lot faster.

00:49:34.807 --> 00:49:35.819
<v Chris>Right. You had a chance to chat

00:49:35.819 --> 00:49:39.701
<v Chris>with Pierre, I imagine after his talk a little bit about some of this.

00:49:40.943 --> 00:49:44.392
<v Chris>Why don't we play that clip and then get your impressions from the chat?

00:49:44.792 --> 00:49:48.891
<v Clips>Pierre, you mentioned Surge yesterday. Can you get into details about that?

00:49:49.564 --> 00:49:57.263
<v Clips>Yes. Surge is really, I think, our take on an orchestration system that will

00:49:57.263 --> 00:50:02.300
<v Clips>allow us to tackle the exponential growth of CVs that we see coming.

00:50:02.683 --> 00:50:08.483
<v Clips>So at the moment, it's accessible in an experimental fashion with your process

00:50:08.483 --> 00:50:13.301
<v Clips>description, where you can subscribe to the section of the archive we call EDGE,

00:50:13.695 --> 00:50:16.883
<v Clips>where CVs that are produced by CVs,

00:50:17.403 --> 00:50:22.769
<v Clips>the fixes, the backports about the CVs are produced by the surge system.

00:50:23.146 --> 00:50:28.023
<v Clips>So search really represents, I think, the best know-how that we accumulated

00:50:28.023 --> 00:50:33.503
<v Clips>over 20 years of maintaining security at Ubuntu and really put together in a

00:50:33.503 --> 00:50:36.120
<v Clips>way that I think is really.

00:50:38.263 --> 00:50:43.643
<v Clips>An agentic engineering effort, right? Like it's not just you throw an agent

00:50:44.023 --> 00:50:47.973
<v Clips>and a model at a problem, but you really are trying to think about it from a

00:50:47.973 --> 00:50:50.823
<v Clips>comprehensive engineering point of view.

00:50:50.823 --> 00:50:56.222
<v Clips>So it means we are going to use multiple sets of agents, purpose-built,

00:50:56.436 --> 00:51:01.167
<v Clips>with many models that are sometimes in some part of the steps are competing with each other.

00:51:01.492 --> 00:51:05.883
<v Clips>So it creates a very interesting, I think, viewpoint about security,

00:51:06.243 --> 00:51:10.804
<v Clips>both in terms of understanding the real problems that you are facing with.

00:51:10.978 --> 00:51:15.263
<v Clips>For example, if your vulnerability is really affecting some packages or it's

00:51:15.263 --> 00:51:16.829
<v Clips>affecting Ubuntu as a whole.

00:51:17.236 --> 00:51:22.153
<v Clips>and secondly how can we see different viewpoints on how we fix it and so you

00:51:22.153 --> 00:51:26.923
<v Clips>can compare the models you can really see differences with frontier models or

00:51:26.923 --> 00:51:31.003
<v Clips>open weight models so we have a comprehensive view on a single side system.

00:51:32.397 --> 00:51:33.516
<v Chris>It sounds pretty aggressive.

00:51:34.335 --> 00:51:37.103
<v Wes>Yeah, fixed velocity up 119% in one year.

00:51:37.483 --> 00:51:42.043
<v Wes>October of this year has had almost as many CVEs as all of 2025.

00:51:42.043 --> 00:51:44.063
<v Wes>That's the environment that we're kind of living in.

00:51:44.063 --> 00:51:47.713
<v Chris>That is. Brent, when you were talking to him, did you get the impression that

00:51:47.713 --> 00:51:50.269
<v Chris>that's a sort of like pedal to the metal kind of initiative for them?

00:51:50.793 --> 00:51:56.183
<v Brent>Oh, yeah. And they've been thinking about this for much longer than is obvious to us.

00:51:56.183 --> 00:52:01.653
<v Brent>like okay we're seeing cvs in the news and things but they're getting 10 times more,

00:52:02.738 --> 00:52:08.143
<v Brent>you know the need to fix 10 times more cvs than they ever did like they used

00:52:08.143 --> 00:52:12.399
<v Brent>to get 250 per year and now they're up like more than 10 times over that so,

00:52:12.943 --> 00:52:16.603
<v Brent>they've been thinking about how to solve this problem for quite a while and,

00:52:17.203 --> 00:52:22.363
<v Brent>uh one way that pierre put it in the keynote i thought was really great he said

00:52:22.363 --> 00:52:28.697
<v Brent>it's a multi-agent orchestration framework for remediation of vulnerabilities in ubuntu which,

00:52:29.683 --> 00:52:33.483
<v Brent>is kind of wild but he also just said like it's really we're really just doing

00:52:33.483 --> 00:52:37.153
<v Brent>gamification with agents so we're having multiple competing agents trying to

00:52:37.153 --> 00:52:39.297
<v Brent>solve these problems and then a,

00:52:39.866 --> 00:52:46.813
<v Brent>like a consensus of agents saying which solution matches best with how canonical wants to do it.

00:52:46.813 --> 00:52:52.898
<v Brent>So it was a really interesting insight into the engineering that's happening on the back end.

00:52:53.563 --> 00:52:56.333
<v Brent>And that's just for the security part. So it was really fascinating.

00:52:56.333 --> 00:53:01.309
<v Brent>Pierre really, I guess, opened my eyes to the security behind the scenes at Ubuntu.

00:53:02.251 --> 00:53:06.487
<v Wes>Yeah, he also had a line in there about trying to restore balance for defenders versus attackers.

00:53:06.487 --> 00:53:09.997
<v Wes>We've talked a lot about the rise in just the attacks and introspection of open

00:53:09.997 --> 00:53:13.477
<v Wes>source software. And we've talked maybe about the need to leverage this tech

00:53:13.477 --> 00:53:17.127
<v Wes>on the other side. And this is an example of them doing it. And they're also

00:53:17.127 --> 00:53:19.597
<v Wes>hiring. They're looking to try and find the best security folks,

00:53:19.597 --> 00:53:21.343
<v Wes>people who can help build out this effort.

00:53:21.679 --> 00:53:24.105
<v Wes>So if you're interested in that, it may be worth exploring.

00:53:24.581 --> 00:53:28.127
<v Wes>I was impressed more generally because they really are on the theme of like,

00:53:28.127 --> 00:53:31.147
<v Wes>what do we do with these new tools as professional engineers?

00:53:31.408 --> 00:53:34.427
<v Wes>they're trying to step up the rigor, right? Like they used formal methods to

00:53:34.427 --> 00:53:39.767
<v Wes>try to make the distributed SQLite database that they use for LexD like more provably correct.

00:53:39.767 --> 00:53:44.747
<v Wes>They're engaging with the firm Antithesis who helps do deterministic and property-based

00:53:44.747 --> 00:53:47.597
<v Wes>testing to apply that to like SnapD itself.

00:53:47.597 --> 00:53:50.717
<v Wes>So they're not, they're like not sitting still with the bar.

00:53:50.717 --> 00:53:54.577
<v Wes>They're raising the bar actively to try to make the software they use and deploy

00:53:54.577 --> 00:53:55.947
<v Wes>and put on our machines better.

00:53:55.947 --> 00:54:00.957
<v Chris>Yeah, that's what you want to hear. That's good. All right, our last clip from the summit.

00:54:01.657 --> 00:54:05.287
<v Chris>You boys wrap us up with your thoughts there on location. And apparently as

00:54:05.287 --> 00:54:08.136
<v Chris>time went on, the time math got a little bit harder.

00:54:08.931 --> 00:54:12.120
<v Clips>Well, somehow we are done. The

00:54:12.120 --> 00:54:16.025
<v Clips>conference, the summit is just done like that. And we go home tomorrow?

00:54:16.292 --> 00:54:19.940
<v Clips>Weren't we just in Texas? What's happening? I can't. Which time zone is this?

00:54:20.912 --> 00:54:24.400
<v Clips>It's a little strange that so much has happened and then it'll last a little

00:54:24.400 --> 00:54:28.900
<v Clips>bit. But this has been an amazing experience. We met amazing people.

00:54:29.510 --> 00:54:33.647
<v Clips>And I don't know. What do you think of the density of the talks?

00:54:34.216 --> 00:54:38.669
<v Clips>Very good. I mean, it was a very wide array of different subjects.

00:54:38.970 --> 00:54:43.320
<v Clips>And, okay, there were a few Canonical employees who gave talks about Canonical

00:54:43.320 --> 00:54:46.970
<v Clips>things, but they are also people giving, who were at Canonical giving talks

00:54:46.970 --> 00:54:48.665
<v Clips>or lightning talks not about Canonical things.

00:54:49.025 --> 00:54:53.060
<v Clips>And it felt like the opposite of a vendor conference. I think they really nailed

00:54:53.060 --> 00:54:57.850
<v Clips>the celebrate and showcase open source because that's what it was.

00:54:57.850 --> 00:55:02.132
<v Clips>And maybe it says a lot about the people who work there that they have the taste

00:55:02.510 --> 00:55:07.260
<v Clips>to select these speakers because they were pretty much all excellent.

00:55:07.260 --> 00:55:09.481
<v Clips>it. And that doesn't happen by accident.

00:55:10.085 --> 00:55:13.916
<v Clips>Yeah. It's like the cream is how I would describe it.

00:55:14.183 --> 00:55:17.990
<v Clips>And I just want more. I came away just like, hey, it's over.

00:55:17.990 --> 00:55:19.901
<v Clips>What? I would do another day or two of this.

00:55:20.331 --> 00:55:24.430
<v Clips>I think almost everyone that we had a chance to interview or just go mingle

00:55:24.430 --> 00:55:28.340
<v Clips>with or chat with or, you know, ask more details about their talk was super

00:55:28.340 --> 00:55:30.517
<v Clips>engaging, super nice, had a lot more to say.

00:55:31.052 --> 00:55:34.906
<v Clips>That's the thing. Yeah. These talks are just little snippets of all of their

00:55:35.283 --> 00:55:37.420
<v Clips>combined experience and knowledge and I just want more.

00:55:39.120 --> 00:55:44.920
<v Clips>So would we come back, I guess is the question. Yeah, I think I would.

00:55:46.167 --> 00:55:48.036
<v Clips>Do you think you'd give another lightning talk? Because you gave,

00:55:48.286 --> 00:55:50.712
<v Clips>you didn't even tell me you were doing a lightning talk. And all of a sudden.

00:55:50.712 --> 00:55:55.263
<v Clips>I didn't realize I didn't mention that. I thought I did. But the entire week is a blur.

00:55:55.852 --> 00:55:57.841
<v Clips>So what was your lightning talk? Give us a little.

00:55:58.671 --> 00:56:02.552
<v Clips>Yeah, well, I like to make programs that shouldn't exist. And this time around,

00:56:02.552 --> 00:56:07.432
<v Clips>I decided I'd put forth an ancient, mostly forgotten, very strange looking language

00:56:07.432 --> 00:56:11.452
<v Clips>inside the kernel because the kernel is static and frustrating and it's nothing

00:56:11.452 --> 00:56:13.073
<v Clips>like closure, even though it's a wonderful kernel.

00:56:13.386 --> 00:56:16.974
<v Clips>and it doesn't really make sense as much as I want to to put a lisp in the kernel

00:56:17.299 --> 00:56:19.273
<v Clips>and fourth is kind of the next best thing.

00:56:19.592 --> 00:56:23.458
<v Clips>Okay. Well, I'm looking forward to that talk being recorded and shared.

00:56:24.137 --> 00:56:26.962
<v Clips>Maybe next time you have to give the lightning talk, buddy. Okay.

00:56:26.962 --> 00:56:29.627
<v Clips>All right. Well, Wes, thanks for joining me on this adventure.

00:56:29.918 --> 00:56:30.963
<v Clips>Thank you for joining me.

00:56:31.200 --> 00:56:34.752
<v Chris>How did this lightning talk come about? Was this a prearranged thing or was

00:56:34.752 --> 00:56:36.848
<v Chris>it like in the moment you're like, I could do a talk on this?

00:56:37.208 --> 00:56:41.172
<v Wes>No. Once we got invited to the event and signed up, I guess for the folks who

00:56:41.172 --> 00:56:45.301
<v Wes>come in person and some online and they'd had some that they showed on the stream as well.

00:56:46.112 --> 00:56:50.232
<v Wes>They send out a little, hey, you're invited to apply to, throw in your hat in

00:56:50.232 --> 00:56:54.792
<v Wes>the ring for the lightning talks, which was a fun little, they do it right at the end of the day.

00:56:55.412 --> 00:56:58.872
<v Wes>There was some really great ones, including philosophical talk at the end of

00:56:59.192 --> 00:57:03.782
<v Wes>the last day about how could you do something nice for computers where someone

00:57:03.782 --> 00:57:07.682
<v Wes>had rigged up cute little ESP devices that could hear sound and then they could

00:57:07.682 --> 00:57:09.942
<v Wes>share the reactions with each other. It was excellent.

00:57:09.942 --> 00:57:10.352
<v Chris>That's good.

00:57:10.692 --> 00:57:14.782
<v Wes>So it's a nice way to keep things balanced. Overall, too, you know,

00:57:14.782 --> 00:57:19.452
<v Wes>we were talking about sort of the talk length at Texas, and the longest talks were like 45 minutes.

00:57:19.772 --> 00:57:19.932
<v Brent>Yeah.

00:57:20.849 --> 00:57:23.732
<v Wes>Everything else was 25 minutes or shorter. And so it was really interesting

00:57:23.732 --> 00:57:28.007
<v Wes>because you really, you got deep ideas, but quickly. And so you never felt stagnant.

00:57:28.279 --> 00:57:31.492
<v Chris>It's probably hard to admit, but I have a sense that if you could have only

00:57:31.492 --> 00:57:34.113
<v Chris>picked one, would you have picked the Ubuntu Summit?

00:57:35.136 --> 00:57:35.801
<v Wes>Yeah, I think so.

00:57:36.101 --> 00:57:36.494
<v Brent>Yeah.

00:57:36.866 --> 00:57:37.551
<v Chris>Yeah.

00:57:37.551 --> 00:57:39.941
<v Wes>I had a wonderful time in Texas and we got to see some people that I really

00:57:39.941 --> 00:57:43.521
<v Wes>wanted to see and Major's Talk was wonderful, but it was a very different experience.

00:57:43.521 --> 00:57:47.141
<v Chris>So this is my question to you boys and to the audience, if you want to boost in and let us know.

00:57:48.575 --> 00:57:52.251
<v Chris>Is it because maybe, you know, it's not just that it's a more focused event.

00:57:52.251 --> 00:57:56.391
<v Chris>That's kind of the wrong term. It's the people in charge have a very particular

00:57:56.391 --> 00:57:59.631
<v Chris>opinion and view. And so they bring those groups of people together of kind

00:57:59.631 --> 00:58:01.441
<v Chris>of common goals and mindsets.

00:58:01.901 --> 00:58:06.601
<v Chris>And that focus seems to result in people that go to that conference and also

00:58:06.601 --> 00:58:09.896
<v Chris>share those same things to have a lot more out of it or something.

00:58:10.442 --> 00:58:13.076
<v Chris>I don't know. I'm working on this focus versus general event.

00:58:13.686 --> 00:58:17.198
<v Chris>And I'm curious. Yeah, it sounds like you kind of like the focused event more,

00:58:17.447 --> 00:58:20.891
<v Chris>even though there was a broad range of topics, which we should link to.

00:58:20.891 --> 00:58:22.219
<v Chris>We will link to in the show notes.

00:58:22.562 --> 00:58:25.961
<v Chris>I also want to say again thank you to TechDev for helping us get down there and cover this.

00:58:25.961 --> 00:58:26.863
<v Wes>No kidding.

00:58:26.991 --> 00:58:28.146
<v Brent>Yes, absolutely.

00:58:28.692 --> 00:58:33.254
<v Chris>This is like one of those things that we feel like we're in a rare position to be able to do.

00:58:35.601 --> 00:58:39.651
<v Chris>And the journey and growth of these events is absolutely part of what we want

00:58:39.651 --> 00:58:42.426
<v Chris>to document and cover on the shows. That's why we talk about it the way we do,

00:58:42.995 --> 00:58:45.404
<v Chris>because we think this is reflective of where the Linux community is at.

00:58:45.816 --> 00:58:49.761
<v Chris>And so for us, it's not only a great time to check in and recharge and kind

00:58:49.761 --> 00:58:53.611
<v Chris>of get a new reboost at the meetups, But it's also a chance to do these kind

00:58:53.611 --> 00:58:58.111
<v Chris>of community event check-ins that we've been following now for almost the entire

00:58:58.111 --> 00:58:58.976
<v Chris>lifetime of the show, really.

00:58:59.574 --> 00:59:03.243
<v Chris>So thank you very much, TechDev. We appreciate that. Thank you, sir.

00:59:04.712 --> 00:59:08.491
<v Chris>Also, thanks to the folks at Canonical for inviting us back,

00:59:08.491 --> 00:59:09.821
<v Chris>even though we've declined them.

00:59:11.521 --> 00:59:13.341
<v Wes>More times than we can remember.

00:59:13.941 --> 00:59:18.031
<v Chris>We said no for so long. And I thought they'd finally give up on us,

00:59:18.031 --> 00:59:20.921
<v Chris>but they didn't. And it worked out everything. and so thank you to the team

00:59:20.921 --> 00:59:23.490
<v Chris>over there. John, Lillian, was it?

00:59:24.321 --> 00:59:27.021
<v Wes>Leilani, John, yeah, Pierre. I mean, just everyone who helped us.

00:59:27.201 --> 00:59:27.671
<v Wes>Everybody over there, yes.

00:59:27.671 --> 00:59:30.061
<v Chris>Of course. Shout out to all you guys.

00:59:32.021 --> 00:59:35.499
<v Chris>I would have, I would have loved to meet John and we'll have links to all of

00:59:35.499 --> 00:59:38.760
<v Chris>that in the show notes. Go watch the talks because you can see him too.

00:59:47.951 --> 00:59:50.749
<v Brent>Well, it turns out while we're gone to all these wonderful events,

00:59:51.369 --> 00:59:53.210
<v Brent>the boosts keep happening.

00:59:53.367 --> 00:59:58.429
<v Brent>And the first baller booster hasn't been here for a while, but the dude is abiding.

01:00:03.809 --> 01:00:06.753
<v Wes>250,000 satoshis. Whoa!

01:00:10.518 --> 01:00:11.447
<v Chris>All right.

01:00:11.761 --> 01:00:14.866
<v Brent>Thank you. Hello, gentlemen. I haven't boosted in a while. Well,

01:00:15.133 --> 01:00:17.357
<v Brent>four months are more than a while, but you know what I mean?

01:00:17.757 --> 01:00:21.002
<v Brent>Life got the better of me. I never missed an episode, though,

01:00:21.112 --> 01:00:24.369
<v Brent>so thanks for the company and the psychotherapy each week.

01:00:25.729 --> 01:00:30.348
<v Brent>Here's something for that Texas Linux Fest. Hope you'll get this while you're there. P.S.

01:00:30.656 --> 01:00:34.220
<v Brent>First time sending from Podverse via my AlbiHub. Hope it arrives.

01:00:34.905 --> 01:00:35.410
<v Wes>It did.

01:00:35.660 --> 01:00:36.469
<v Chris>Thank you. Well done.

01:00:36.469 --> 01:00:37.198
<v Wes>Impressive work.

01:00:37.372 --> 01:00:44.199
<v Chris>Self-hosted setup. Greg the lawyer is up next with 44,444 Satoshis.

01:00:47.635 --> 01:00:51.059
<v Chris>Greg writes, been letting my membership run on autopilot. More people should

01:00:51.059 --> 01:00:54.996
<v Chris>be members. But I wanted to boost in to tell you about what's been taking up some of my time.

01:00:55.379 --> 01:01:01.289
<v Chris>I built a local AI server by rescuing a system that was bound for e-waste.

01:01:01.289 --> 01:01:02.029
<v Chris>And he sends us a link here.

01:01:02.089 --> 01:01:02.972
<v Brent>Nicely done.

01:01:03.425 --> 01:01:07.739
<v Wes>My Trash Day AI server? This is the story of Kirby, my local AI server that

01:01:07.739 --> 01:01:10.429
<v Wes>started as a tower case sitting on the curb on Trash Day.

01:01:10.829 --> 01:01:12.119
<v Chris>I think that's brilliant.

01:01:12.119 --> 01:01:12.659
<v Wes>So cute.

01:01:12.659 --> 01:01:13.089
<v Chris>I love it.

01:01:14.169 --> 01:01:16.932
<v Wes>And Greg's turned it into a pretty neat machine.

01:01:17.222 --> 01:01:20.529
<v Chris>Yeah. It's a nice looking post about it, too. So we'll put a link to that in

01:01:20.529 --> 01:01:22.598
<v Chris>the show notes. That's great.

01:01:23.439 --> 01:01:27.909
<v Wes>Well, Anonymous boosts in with 12,345 SATs.

01:01:33.193 --> 01:01:36.382
<v Wes>trying out this web boost thing. And I would say it was a success.

01:01:36.382 --> 01:01:36.982
<v Chris>Hey, you did it.

01:01:37.282 --> 01:01:38.102
<v Wes>Thank you for the value.

01:01:38.102 --> 01:01:39.085
<v Chris>Yes, appreciate that.

01:01:39.218 --> 01:01:43.572
<v Brent>Well, PCNOLREF sent in 3,402 Satoshis.

01:01:46.010 --> 01:01:48.907
<v Brent>He says, make it so to enterprise boost.

01:01:49.249 --> 01:01:50.142
<v Chris>Ah, yes.

01:01:50.502 --> 01:01:51.629
<v Brent>Also, live long.

01:01:52.645 --> 01:01:57.342
<v Chris>The olds, the pats do. They always will.

01:01:57.667 --> 01:02:00.215
<v Wes>And, you know, with the help of the sats, we'll prosper too.

01:02:02.618 --> 01:02:08.912
<v Chris>Nicely done, Wesley Wes, you're still on point after all that travel Aidmate

01:02:08.912 --> 01:02:11.986
<v Chris>comes in with 6,666 Satushers,

01:02:17.159 --> 01:02:20.122
<v Chris>Did you know graphene can now auto-record phone calls?

01:02:20.122 --> 01:02:24.302
<v Chris>What a lifesaver for directions and part numbers, etc but their stock dialer

01:02:24.302 --> 01:02:28.172
<v Chris>is terrible for finding contacts or dialing numbers I'm a millennial,

01:02:28.172 --> 01:02:33.134
<v Chris>I wanted a dialer that opens to a keyboard first that I can actually use to make a phone call.

01:02:33.720 --> 01:02:36.932
<v Chris>And while I'm using the keyboard, why not implement T9 Search?

01:02:36.932 --> 01:02:41.249
<v Chris>Some T9 dialers exist, but most of them want to take control of the phone app,

01:02:41.644 --> 01:02:43.589
<v Chris>which negates graphene's recording.

01:02:44.076 --> 01:02:48.862
<v Chris>I clanked out a dialer called 9Pad. It works seamlessly and even has an easy

01:02:48.862 --> 01:02:52.512
<v Chris>way to play the recordings from the call log so you don't have to go searching

01:02:52.512 --> 01:02:53.442
<v Chris>through the file system.

01:02:54.067 --> 01:02:56.720
<v Chris>I've been daily driving for a couple of weeks and it's working well.

01:02:57.079 --> 01:02:59.065
<v Chris>I'm not a developer, so take it with a grain of salt.

01:02:59.343 --> 01:03:03.860
<v Chris>But if you want to try it, and he links us to 9pad on AbeMate's GitHub.

01:03:05.188 --> 01:03:09.392
<v Chris>I have been, I don't know what it is, but since Texas, I have been thinking

01:03:09.392 --> 01:03:10.882
<v Chris>about T9 dialing. Did it come up?

01:03:11.222 --> 01:03:12.922
<v Wes>Yeah, we had a conversation about it, I'm pretty sure.

01:03:12.922 --> 01:03:16.084
<v Chris>Yeah, I've been thinking about the T9. Yeah, at the meetup. Yeah.

01:03:17.482 --> 01:03:21.732
<v Brent>Should we, hang on, should we explain T9 for the younger viewers here?

01:03:21.732 --> 01:03:22.742
<v Chris>Do you got an explanation?

01:03:22.742 --> 01:03:27.119
<v Brent>Because I'm going to I'm going to lob this one at Wes I think.

01:03:28.754 --> 01:03:29.174
<v Chris>You're welcome.

01:03:29.774 --> 01:03:30.674
<v Wes>How am I dragged in this?

01:03:30.674 --> 01:03:34.387
<v Chris>I love it. Wes, could you tell us how T9 works really quick? Yeah.

01:03:37.214 --> 01:03:41.914
<v Wes>Well, if you have yourself only, you know, a little dial pad at your touchtone

01:03:41.914 --> 01:03:45.604
<v Wes>phone there, you need a way to be able to iterate through all the letters.

01:03:45.604 --> 01:03:47.514
<v Chris>Let's try this. Okay, let's try this. All right?

01:03:47.914 --> 01:03:48.424
<v Wes>You got an idea.

01:03:48.424 --> 01:03:53.201
<v Chris>Let's see if this works. Janice, can you explain how T9 works on a phone keyboard?

01:03:53.560 --> 01:03:57.809
<v Clips>T9 is the old predictive text on phone keypads, Captain.

01:03:58.436 --> 01:04:03.016
<v Clips>Each number holds three or four letters, so you tap once per letter,

01:04:03.243 --> 01:04:07.916
<v Clips>and the software guesses the word from a dictionary instead of you cycling through letters.

01:04:08.653 --> 01:04:13.484
<v Clips>It learns as you go, which is why it gets faster, and one number sequence can

01:04:13.484 --> 01:04:16.674
<v Clips>map to a few words until context picks the right one.

01:04:17.284 --> 01:04:19.634
<v Chris>You know that bit there about it learns so you go faster?

01:04:19.634 --> 01:04:23.658
<v Brent>That was the unlock with T9 back in the day.

01:04:24.123 --> 01:04:29.174
<v Brent>it was really impressive like i remember well really that was the only way texting

01:04:29.174 --> 01:04:33.594
<v Brent>could happen because it was like the transition between well talking to people

01:04:33.594 --> 01:04:35.466
<v Brent>on the phone and then just being able to text yeah uh,

01:04:36.841 --> 01:04:43.296
<v Brent>and man watching people who texted lots use their t9 like that's what we heard,

01:04:43.743 --> 01:04:47.814
<v Brent>at texas linux fest was like someone said they were faster at t9 than with a

01:04:48.254 --> 01:04:49.409
<v Brent>on-screen keyboard which,

01:04:50.263 --> 01:04:54.367
<v Brent>at first I didn't believe, but then now thinking back, like you can get super fast.

01:04:54.866 --> 01:05:00.305
<v Chris>I like nine pad. I think this is a great idea. My only suggestion Abe made is a screenshot or two.

01:05:01.000 --> 01:05:04.024
<v Chris>You know, we like to see it, you know, we, you got to tease us with the screenshot.

01:05:04.024 --> 01:05:06.384
<v Chris>That's all. That's great though. Thank you for sending that our way.

01:05:06.384 --> 01:05:10.154
<v Wes>It does continue to be, make me excited about this era of like super easy,

01:05:10.574 --> 01:05:13.914
<v Wes>quick ways to just run our own custom apps on our phones because it's,

01:05:13.914 --> 01:05:17.674
<v Wes>we've had that on the Linux desktop for a long time. We haven't had it there.

01:05:17.674 --> 01:05:21.814
<v Chris>Just in time for Google to screw it all up. Thanks, Googs. I'm sure they'll

01:05:21.814 --> 01:05:22.809
<v Chris>come up with something that sucks.

01:05:23.448 --> 01:05:26.518
<v Chris>Adversary 17 sent in 14,700 sats.

01:05:29.253 --> 01:05:33.780
<v Chris>No message, just value. No problem there. Thank you, adversaries. Appreciate you.

01:05:34.663 --> 01:05:41.133
<v Wes>JPEG boosts in with 5,000 sats. I really enjoyed the interview with Canonical on Ubuntu Core.

01:05:41.133 --> 01:05:44.688
<v Chris>Oh, good. Thank you. Yeah, we always enjoy John. He's a straight shooter.

01:05:44.880 --> 01:05:48.426
<v Chris>So when he wants to come on and we can arrange it, it all works out pretty well.

01:05:48.833 --> 01:05:51.003
<v Brent>Well, the gene of beans boosted in Aerovdux.

01:05:53.732 --> 01:05:58.363
<v Brent>I'm curious if the new version of Ubuntu Core desktop will have a snappified

01:05:58.363 --> 01:06:00.476
<v Brent>way to install Nix and Home Manager.

01:06:01.503 --> 01:06:04.917
<v Brent>If that would be maybe a workshop thing or something else.

01:06:05.352 --> 01:06:06.653
<v Chris>I bet I could see it in the workshop, right?

01:06:06.653 --> 01:06:09.893
<v Wes>Yeah, I think so. Something where you have it, they're going to do a lot of

01:06:09.893 --> 01:06:13.223
<v Wes>work on making the interfaces kind of rich so you can plug stuff in and get

01:06:13.223 --> 01:06:17.133
<v Wes>stuff bidirectional, but probably the Nix stuff, at least in the foreseeable

01:06:17.133 --> 01:06:18.420
<v Wes>future, would be in some kind of,

01:06:19.283 --> 01:06:23.963
<v Wes>maybe not fully isolated, but snappified, isolated, little hole-you-poke world.

01:06:23.963 --> 01:06:25.883
<v Chris>Yeah, something we're going to be watching.

01:06:25.883 --> 01:06:26.543
<v Wes>We'll have to play with.

01:06:27.223 --> 01:06:30.233
<v Chris>Thanks, Gene. Magnolia Mayhem's here with 3,000 sats.

01:06:32.415 --> 01:06:35.103
<v Chris>Small boost. Big thanks. Thank you, Mayhem. Appreciate you.

01:06:35.898 --> 01:06:40.420
<v Wes>Brian from Boise Boosin with 12,121 sats across two boosts.

01:06:44.924 --> 01:06:48.309
<v Wes>A few weeks back, I mentioned that I was working on a website for my sister's

01:06:48.309 --> 01:06:51.878
<v Wes>rural library. It's still in development, but I wanted to share a pic.

01:06:52.221 --> 01:06:58.119
<v Wes>I've been using Sveltea CMS. It's an MIT-licensed Git-based editor that library

01:06:58.119 --> 01:07:02.319
<v Wes>staff can use to draft and publish content without touching code.

01:07:02.319 --> 01:07:05.379
<v Chris>Oh, this is great. So they can update their own website.

01:07:05.379 --> 01:07:05.989
<v Brent>Whoa.

01:07:06.469 --> 01:07:10.691
<v Wes>It has a clean interface, real-time previews, and no database to maintain.

01:07:11.051 --> 01:07:15.089
<v Wes>It's really slick and will give this tiny library tools that large organizations

01:07:15.089 --> 01:07:16.305
<v Wes>have and take for granted.

01:07:16.548 --> 01:07:19.269
<v Wes>And best of all, it's free and open source.

01:07:19.269 --> 01:07:22.255
<v Chris>Quick sign-in with a QR code, works on phones, works on tablets.

01:07:22.591 --> 01:07:26.318
<v Chris>Drafts are backed up automatically and you're warned before overriding someone else's work.

01:07:26.707 --> 01:07:30.370
<v Chris>Accessible by design with a full keyboard, screen reader support as well.

01:07:32.559 --> 01:07:36.448
<v Chris>It's VeltiaCMS.app. We'll put a link to that in the show notes too, right?

01:07:37.729 --> 01:07:40.999
<v Chris>That is a good one. You know what? Thank you so much, Brian.

01:07:40.999 --> 01:07:44.369
<v Chris>So not only is Brian in the mumble room this week, hanging out in the quiet

01:07:44.369 --> 01:07:46.989
<v Chris>listening, and then supporting us with the boost here, right?

01:07:46.989 --> 01:07:50.849
<v Chris>But like, I love it when you're out there working on stuff and you come across

01:07:50.849 --> 01:07:53.869
<v Chris>something useful. Yeah, we love hearing about that stuff. Please keep sending

01:07:53.869 --> 01:07:57.554
<v Chris>that in. Bradley, you want to take Space Warlock?

01:07:57.831 --> 01:08:03.475
<v Brent>Yeah, the Space Warlock is here with our first Fiat Boost, 42 US dollars.

01:08:06.605 --> 01:08:09.790
<v Brent>It was great meeting you guys at Texas Linux Fest. I didn't get a chance to

01:08:09.790 --> 01:08:11.930
<v Brent>buy y'all a drink, though, but cheers.

01:08:12.370 --> 01:08:16.410
<v Chris>Oh, well, thank you very much. You know what? No drink required.

01:08:16.410 --> 01:08:17.940
<v Chris>We appreciate you. Thank you.

01:08:17.940 --> 01:08:18.760
<v Wes>Thanks for coming out.

01:08:20.786 --> 01:08:24.792
<v Chris>Thank you, everybody who made it out. Atypical came in with a free member boost.

01:08:25.065 --> 01:08:28.970
<v Chris>For your next challenge, the loser should have to recreate their entire setup

01:08:28.970 --> 01:08:33.330
<v Chris>and workflow without any nicks or run Windows on their main computer for one month.

01:08:34.120 --> 01:08:36.750
<v Chris>After all, Nix on Nix. It's just too flaky.

01:08:37.610 --> 01:08:39.160
<v Wes>Colonel coming in hot.

01:08:39.160 --> 01:08:43.989
<v Chris>We have kicked around a couple ideas a couple of times about the Windows penalty.

01:08:45.004 --> 01:08:49.898
<v Chris>And I do like the idea of before the next challenge, whatever it is,

01:08:50.878 --> 01:08:55.450
<v Chris>we just set up the Windows laptop and whoever loses has to use it.

01:08:56.370 --> 01:08:59.540
<v Chris>This could be fun for 700 if we could make it work where Brent could be in person

01:08:59.540 --> 01:09:03.520
<v Chris>because then he could just take the loser laptop because I'm going to try to make it so Brent loses.

01:09:03.520 --> 01:09:04.570
<v Brent>You just want to see me suffer.

01:09:04.570 --> 01:09:07.110
<v Wes>We haven't figured out what the challenge is yet to make the outcome.

01:09:07.890 --> 01:09:09.160
<v Wes>Sort of like Cardassian Justice.

01:09:09.160 --> 01:09:15.000
<v Chris>Yeah, exactly. Yeah, exactly. So he says, please stop saying Docker container.

01:09:15.000 --> 01:09:16.738
<v Chris>Did we read this before? I feel like I've read this before.

01:09:17.127 --> 01:09:20.070
<v Chris>Oh, we've just gotten this feedback before. You also need to check on the projects

01:09:20.070 --> 01:09:21.499
<v Chris>that are publishing OCI containers.

01:09:21.736 --> 01:09:25.370
<v Chris>Many projects publish Docker containers that require Docker and are not OCI compliant.

01:09:25.850 --> 01:09:29.858
<v Chris>Saying OCI container is not being pandemic. It's being accurate.

01:09:30.329 --> 01:09:32.650
<v Chris>Can I get a mommy needs a joint for a sound clip?

01:09:33.677 --> 01:09:37.130
<v Chris>You know, do I have that? Do I have Mommy Needs a... That's a different show,

01:09:37.130 --> 01:09:41.498
<v Chris>buddy. I got to really go. That's a way callback. I do have it, though, somewhere.

01:09:42.810 --> 01:09:43.686
<v Chris>Let me find it first.

01:09:46.053 --> 01:09:49.020
<v Chris>All right, I'm getting close. I'm getting close. Let's see if I've found it

01:09:49.020 --> 01:09:52.810
<v Chris>yet. Nope, that's not it. That's not it.

01:09:52.810 --> 01:09:54.046
<v Brent>What is happening?

01:09:54.208 --> 01:09:56.300
<v Wes>See, this is the depth of the soundbar we don't usually get to.

01:09:56.310 --> 01:09:59.510
<v Chris>Let's see. Yeah, I see. I don't know if I have it anymore. I might not.

01:09:59.510 --> 01:10:00.692
<v Brent>Dust off those buttons.

01:10:05.695 --> 01:10:08.083
<v Chris>There you go. You got a few things, though, but I don't know if I have that

01:10:08.083 --> 01:10:11.663
<v Chris>one anymore. Because, you know, I never play that stuff. Who wants to hear that?

01:10:12.583 --> 01:10:17.433
<v Chris>Nobody wants to hear that. So I have been kicking this around.

01:10:17.433 --> 01:10:20.132
<v Chris>We actually have talked about this. It even came up on our trip.

01:10:20.515 --> 01:10:23.573
<v Chris>Should we be saying Docker container? Should we just be saying container?

01:10:23.573 --> 01:10:24.983
<v Chris>Should we say OCI container?

01:10:24.983 --> 01:10:25.943
<v Wes>Linux container.

01:10:25.943 --> 01:10:32.463
<v Chris>Yeah. And we really haven't landed on what is exactly the right language to

01:10:32.463 --> 01:10:35.153
<v Chris>use. Because sometimes they are specifically Docker containers.

01:10:35.153 --> 01:10:38.505
<v Chris>Sometimes they are, and the irony is we use Podman.

01:10:38.981 --> 01:10:42.143
<v Chris>That's what we use. So the irony is we're not even really, we have,

01:10:42.143 --> 01:10:45.723
<v Chris>I have some Docker containers from years around that are still in production.

01:10:45.723 --> 01:10:49.870
<v Chris>But anything I've deployed this year, or maybe even since last year, has been Podman.

01:10:50.423 --> 01:10:54.233
<v Wes>I advocated internally for Tarball with a specific type of metadata,

01:10:54.233 --> 01:10:55.883
<v Wes>but apparently that's too wordy.

01:10:57.063 --> 01:11:01.747
<v Chris>It's just a mouthful, Wes. It's just a mouthful. i5 Connoisseur, free member boosts.

01:11:02.188 --> 01:11:07.223
<v Chris>You can get your dashboard as your new tab page. That's how I do it as a jumping

01:11:07.223 --> 01:11:10.170
<v Chris>off point for my services. I think that's the only way, High Five, I would ever use it.

01:11:10.414 --> 01:11:10.983
<v Wes>Or see it.

01:11:11.337 --> 01:11:11.859
<v Chris>But I just...

01:11:12.382 --> 01:11:14.065
<v Brent>You wouldn't want to pin your dashboard?

01:11:14.878 --> 01:11:17.813
<v Chris>Well, and I launched... First of all, I don't close my...

01:11:17.813 --> 01:11:19.475
<v Brent>You guys are always going on about pin tabs.

01:11:19.841 --> 01:11:23.473
<v Chris>I don't close my browser much. So usually I'm resuming work,

01:11:23.473 --> 01:11:26.343
<v Chris>and the browser's already got a couple of pages open. Not a lot,

01:11:26.343 --> 01:11:28.183
<v Chris>because I'm a gentleman, but a couple of pages open.

01:11:29.094 --> 01:11:32.623
<v Chris>You know, and a few pin tabs. But, yeah, I don't know if that would work for me.

01:11:33.003 --> 01:11:37.023
<v Chris>But I could see having a dedicated, you know how sometimes you can bust websites

01:11:37.023 --> 01:11:39.340
<v Chris>off into their own standalone app and there's always some way to cook that up?

01:11:40.124 --> 01:11:42.748
<v Chris>If I had a screen, yeah, I don't know. High five. I just don't know.

01:11:43.927 --> 01:11:48.674
<v Wes>Unicorn 1999 comes in with a member boost now that i've clanked my tv thanks

01:11:48.674 --> 01:11:53.394
<v Wes>to you nice maybe the living room tv would be a great spot for an alert dashboard a

01:11:53.774 --> 01:11:57.194
<v Wes>home assistant or home lab something out of spec or sensor batteries needing

01:11:57.194 --> 01:12:00.794
<v Wes>replaced something like that you know turn the tv display all the problems.

01:12:01.114 --> 01:12:04.772
<v Chris>So that's a nice idea unicorn let me throw another thought technology at you,

01:12:05.340 --> 01:12:12.624
<v Chris>you can get e-ink esp displays for pretty cheap like 60 50 bucks on amazon or

01:12:12.624 --> 01:12:14.118
<v Chris>wherever you know, the Allibab,

01:12:14.704 --> 01:12:17.769
<v Chris>and hook them up to the home assistant and then just have it.

01:12:18.326 --> 01:12:20.264
<v Chris>And it's really nice because it's that kind of matte display.

01:12:20.264 --> 01:12:23.584
<v Chris>Although I do think the TV is a great way to, especially if you could just have

01:12:23.584 --> 01:12:26.324
<v Chris>it something that when you turn the TV on, it could have a few alerts on there

01:12:26.324 --> 01:12:27.487
<v Chris>if you need to take care of something.

01:12:27.951 --> 01:12:30.754
<v Wes>I could see that too. Maybe you have like something like an auxiliary kitchen

01:12:30.754 --> 01:12:33.054
<v Wes>screen or other screens around your house that isn't the living room.

01:12:33.134 --> 01:12:34.394
<v Chris>Definitely, definitely. For sure.

01:12:34.414 --> 01:12:36.072
<v Brent>I think I'm going to push back on this one actually.

01:12:36.240 --> 01:12:36.925
<v Wes>Whoa.

01:12:37.494 --> 01:12:38.824
<v Brent>Because when you agree.

01:12:38.824 --> 01:12:39.154
<v Wes>I know.

01:12:39.554 --> 01:12:42.829
<v Brent>You know, you made a nice dinner. You're sitting down and you just want to,

01:12:43.305 --> 01:12:46.674
<v Brent>you know, watch TV with a significant other. Is that when you want to be reminded

01:12:46.674 --> 01:12:47.691
<v Brent>of all the things that are broken?

01:12:49.214 --> 01:12:53.154
<v Chris>Maybe not. I go back to my ESP dashboard thing. You just don't look at that.

01:12:53.154 --> 01:12:55.750
<v Chris>During dinner, you have a display pictures. I'm going to really try this.

01:12:56.654 --> 01:13:02.019
<v Chris>I have one. It's an e-ink. It's about a seven inch e-ink photo display,

01:13:02.640 --> 01:13:05.705
<v Chris>but it's really an ESP machine and the photo display is just a monitor.

01:13:06.233 --> 01:13:10.842
<v Chris>So what I'm thinking is sometimes it's a dashboard. Sometimes it's a photo display.

01:13:11.236 --> 01:13:15.104
<v Chris>And during dinner and during nighttime, it's a photo display. We'll see.

01:13:15.104 --> 01:13:17.244
<v Brent>It's a mandatory photo display at that time.

01:13:17.244 --> 01:13:18.255
<v Chris>If I can make it work, I might.

01:13:19.706 --> 01:13:23.773
<v Brent>Well, Encoded sent in a free members boost. Looking forward to the meetup at

01:13:23.773 --> 01:13:25.283
<v Brent>Texas Linux Fest. See you there.

01:13:25.283 --> 01:13:31.053
<v Chris>Hey, nice. Mike from KY comes in.

01:13:31.613 --> 01:13:34.153
<v Chris>Long time member. First time booster. Hey, all right.

01:13:34.673 --> 01:13:34.953
<v Brent>Hey.

01:13:35.393 --> 01:13:36.473
<v Chris>Please save my home.

01:13:36.913 --> 01:13:37.233
<v Wes>Oh, no.

01:13:37.233 --> 01:13:37.483
<v Brent>What?

01:13:37.483 --> 01:13:40.613
<v Chris>How did you clean up your NVIDIA shield? Oh.

01:13:43.095 --> 01:13:46.739
<v Chris>Oh. Oh, my God. I hadn't.

01:13:47.395 --> 01:13:51.545
<v Chris>Eyebone. Oh, my gosh. I forgot I have a handhold NVIDIA shield I could clank.

01:13:51.893 --> 01:13:52.223
<v Brent>Oh.

01:13:52.223 --> 01:13:55.443
<v Chris>I could clank the old handhold NVIDIA shield. I just thought of that as soon

01:13:55.443 --> 01:13:58.663
<v Chris>as Mike, he's talking about the TV one, but for some reason it made me think

01:13:58.663 --> 01:14:01.093
<v Chris>about the handheld one. It's just been abandoned.

01:14:01.093 --> 01:14:01.983
<v Wes>You're sitting somewhere.

01:14:01.983 --> 01:14:04.153
<v Chris>But it's a beautiful piece of hardware.

01:14:04.153 --> 01:14:04.392
<v Wes>Yeah.

01:14:04.740 --> 01:14:08.603
<v Chris>Oh, but it did go well. I kind of tried to go a little too far,

01:14:08.603 --> 01:14:11.553
<v Chris>got a little ambitious, but the basic clanking worked so great.

01:14:11.553 --> 01:14:15.630
<v Chris>I've used it several nights since, and oh man, it's such a better experience.

01:14:16.379 --> 01:14:20.332
<v Chris>Projectivity works great most of the time. Yeah, that's the problem is most of the time.

01:14:20.756 --> 01:14:23.983
<v Chris>Absolutely would recommend the Clean My TV or whatever that project was that

01:14:23.983 --> 01:14:26.329
<v Chris>we linked. That's the one I used on my NVIDIA Shield.

01:14:26.915 --> 01:14:31.646
<v Chris>We'll do it 100% every time that I get a device like this. It's great.

01:14:32.952 --> 01:14:35.994
<v Chris>Moo-ha-ha-ha-ha! Comes in with a free member boost.

01:14:36.401 --> 01:14:41.067
<v Chris>Hey, JB, can you go into a bit of details about why you ended up using Rustafest

01:14:41.067 --> 01:14:42.901
<v Chris>instead of Seaweed for your S3 storage?

01:14:43.330 --> 01:14:46.097
<v Chris>I have something like 15 laptops at work that use different things which I'm

01:14:46.097 --> 01:14:50.871
<v Chris>looking for connecting into something simple and redundant. Maybe an S3 storage solution.

01:14:53.077 --> 01:14:57.067
<v Chris>Boy, Wes, I'm trying to remember. I think it was due to an extended type of

01:14:57.067 --> 01:14:58.452
<v Chris>attribute that we needed for Git.

01:14:59.033 --> 01:15:01.517
<v Wes>Yeah, there were some specific things for what we were hosting.

01:15:02.516 --> 01:15:04.697
<v Wes>We'd also just recently seen it, and we were quite curious about it,

01:15:04.697 --> 01:15:07.647
<v Wes>and we wanted to try. Like, we poked at it to talk about it on the show,

01:15:07.647 --> 01:15:10.177
<v Wes>but we hadn't really put it into, before that, hadn't, like,

01:15:10.177 --> 01:15:12.698
<v Wes>super put it into any real angry use cases yet.

01:15:13.772 --> 01:15:17.047
<v Chris>I think it might have been Clanker Therapy 2 where we got into the details.

01:15:17.047 --> 01:15:18.027
<v Wes>Yeah, I think so.

01:15:18.027 --> 01:15:21.787
<v Chris>So when it was fresh, I think we talked about it in Clanker Therapy 2 about

01:15:21.787 --> 01:15:26.457
<v Chris>the specific feature that it had that we needed, if you want to go dig into it.

01:15:26.457 --> 01:15:29.187
<v Wes>It also seemed maybe a little more focused on the side that we wanted.

01:15:29.187 --> 01:15:33.347
<v Wes>I think Seaweed FS can also handle more like distributed over the internet sort

01:15:33.347 --> 01:15:36.767
<v Wes>of use cases was not necessarily what we were going for. That didn't mean it

01:15:36.767 --> 01:15:39.137
<v Wes>wouldn't be a good fit or anything or isn't an excellent project.

01:15:41.861 --> 01:15:44.437
<v Chris>Digital Farmer comes in with a free member boost. You guys seem to make use

01:15:44.437 --> 01:15:46.992
<v Chris>of the open router project for your model use.

01:15:47.416 --> 01:15:52.466
<v Chris>What is the benefit of using that as opposed to using monthly all you can use from ChatGPT?

01:15:52.820 --> 01:15:55.067
<v Chris>Is it just for the ability to use the different models for different tasks?

01:15:55.067 --> 01:15:58.521
<v Chris>I use ChatGPT Pro for everything, and I'm wondering if I'm missing anything.

01:15:59.241 --> 01:16:05.377
<v Chris>Oh, I like this question. I'm going to take the route and say that if you use it a lot,

01:16:05.928 --> 01:16:09.307
<v Chris>like if you're using codecs and using those things a lot or you're running agents

01:16:09.307 --> 01:16:15.207
<v Chris>frequently and you want to use the chat GPT models, your best route is the monthly.

01:16:15.207 --> 01:16:15.605
<v Wes>Mm-hmm.

01:16:16.527 --> 01:16:19.615
<v Chris>I think the benefit with OpenRouter is you can shop around, right?

01:16:19.615 --> 01:16:23.737
<v Chris>You can try out different stuff. It's integrated into just about everything.

01:16:24.126 --> 01:16:26.912
<v Chris>So like OpenCode, it's just really simple to set up.

01:16:27.735 --> 01:16:32.455
<v Chris>But I think the Codex Pro plan, even the $100 a month plan, is a really good

01:16:32.455 --> 01:16:36.235
<v Chris>value because you get a crap ton of agent usage for that.

01:16:36.543 --> 01:16:40.165
<v Chris>You get a crap ton of Codex usage for that. And you get a significant amount

01:16:40.165 --> 01:16:45.098
<v Chris>of API credits, $100 a month, for the audio transcribing API.

01:16:45.382 --> 01:16:49.748
<v Chris>So if you use those things and you want a model that has vision and can generate images,

01:16:52.255 --> 01:16:54.542
<v Chris>I think it's a tempting offer, unfortunately.

01:16:54.723 --> 01:16:57.775
<v Wes>There's also, like, you don't have to use, you know, I use multiple things.

01:16:57.775 --> 01:17:00.574
<v Wes>Open Router is kind of nice as a fallback as well because, you know,

01:17:00.725 --> 01:17:03.295
<v Wes>maybe you've hit your limit for whatever the time period you're in,

01:17:03.715 --> 01:17:05.115
<v Wes>but you still have a project you want to work on.

01:17:05.115 --> 01:17:10.128
<v Wes>Well, compared to sort of the opaque pricing and value, it is a good deal,

01:17:10.321 --> 01:17:12.505
<v Wes>but you don't really know exactly what you're getting, especially until you

01:17:12.505 --> 01:17:14.095
<v Wes>actually try it. And it can change at any time.

01:17:14.455 --> 01:17:17.235
<v Wes>Whereas Open Router can be expensive if you're doing heavy usage depending on

01:17:17.235 --> 01:17:21.344
<v Wes>the model you use, but you know right up front exactly what it's going to cost you per token. True.

01:17:21.576 --> 01:17:26.265
<v Chris>And just as sort of an addition to all of this, I'm surprised that Noa's Portal

01:17:26.265 --> 01:17:28.005
<v Chris>doesn't get more recognition for this.

01:17:28.005 --> 01:17:28.450
<v Wes>Yeah.

01:17:28.595 --> 01:17:33.385
<v Chris>Because Noa's Portal has a bunch of really great models that you can use that

01:17:33.385 --> 01:17:34.939
<v Chris>you can just sort of fund as you want.

01:17:35.427 --> 01:17:39.175
<v Chris>But something they offer is a ChatGPT subscription pass-through.

01:17:39.646 --> 01:17:43.825
<v Chris>So if you have a ChatGPT Pro subscription, you can authorize it in the NOIS

01:17:43.825 --> 01:17:48.242
<v Chris>portal account, and it will pass through all of your ChatGPT stuff through that.

01:17:48.428 --> 01:17:52.765
<v Chris>And so then you don't get charged API tokens for that, which means you can log

01:17:52.765 --> 01:17:56.921
<v Chris>in to all your Hermes agents or your open code or whatever it is into NOIS portal,

01:17:57.183 --> 01:18:01.449
<v Chris>and then you get all of their models plus your ChatGPT subscription passed through.

01:18:01.884 --> 01:18:05.553
<v Chris>And NOIS is free to sign up for, and they're the folks behind Hermes.

01:18:06.191 --> 01:18:07.290
<v Chris>I think it should get more attention.

01:18:08.504 --> 01:18:10.042
<v Chris>Good question, obviously. Thank you, Digital Farmer.

01:18:10.338 --> 01:18:12.294
<v Wes>And if you haven't checked out the Clinko Therapy stuff already,

01:18:12.294 --> 01:18:14.477
<v Wes>maybe do, because I think we've talked a little bit about this there, too.

01:18:15.151 --> 01:18:18.474
<v Chris>Pabby comes in with a free member boost. Clack it up! After finally catching

01:18:18.474 --> 01:18:23.144
<v Chris>up with lots of time and travel and boosts, I got around to trying Hermes, and I'm hooked.

01:18:23.445 --> 01:18:27.207
<v Chris>So many projects are getting done now that were previously on hold because of time constraints.

01:18:27.480 --> 01:18:33.679
<v Chris>Today, my 256-gigabyte M5 Ultra Mac Studio arrived. Looking forward to taking things local.

01:18:34.164 --> 01:18:37.604
<v Chris>Wow, what an adventure you're about to start, Pabby. Keep us posted.

01:18:37.604 --> 01:18:39.605
<v Chris>Local AI is definitely an area of interest of ours.

01:18:39.785 --> 01:18:42.908
<v Wes>Yeah, please do tell us what you're building with that and how that new box works out.

01:18:44.057 --> 01:18:47.436
<v Chris>Oh, I see Sam H. sent us a link. You want to take that? Pull this up here?

01:18:47.633 --> 01:18:52.991
<v Wes>Yeah, Sam H. boosts in. Have you heard of numtide slash LLM agents on GitHub?

01:18:53.293 --> 01:18:57.118
<v Wes>This is how I've been installing codecs, Pi, open code, et cetera, on NixOS.

01:18:57.397 --> 01:19:02.379
<v Wes>I'm also trying its packaging of Hermes desktop for accessing a remote Hermes agent.

01:19:02.529 --> 01:19:03.344
<v Chris>I had not heard of this.

01:19:03.344 --> 01:19:06.952
<v Wes>I think I'd heard of it when it was early, but I haven't actually ever really used it.

01:19:07.260 --> 01:19:10.484
<v Wes>Looks like it's being quite actively maintained. Numtide folks obviously do

01:19:10.484 --> 01:19:15.284
<v Wes>a lot of good stuff. So, and boy, there's a lot of stuff in here.

01:19:15.964 --> 01:19:19.174
<v Wes>Antigravity, ChatGPT, ClaudeCode's in here. Everything's in here.

01:19:19.174 --> 01:19:22.155
<v Wes>Everything's in here. Everything's in here. Pi's in there if you want that.

01:19:22.528 --> 01:19:26.594
<v Chris>Grok, Goose, Jewels, KimiCode stuff in here. Minimax stuff's in here.

01:19:26.594 --> 01:19:28.664
<v Chris>I'm sure the DeepSeek stuff's in here. I just haven't gotten that far down on

01:19:28.664 --> 01:19:29.634
<v Chris>the list because there's so much stuff.

01:19:29.634 --> 01:19:33.184
<v Wes>They've got OpenCode and OpenCode2 and OpenCode2 Desktop. That's nice.

01:19:33.524 --> 01:19:36.777
<v Chris>Hermes Agent, if you want to get Hermes going on next. Holy moly.

01:19:38.884 --> 01:19:40.284
<v Chris>All right, go and do it the hard way.

01:19:40.284 --> 01:19:42.100
<v Wes>Maybe we'll have to swap that in. Thank you, Sam.

01:19:42.396 --> 01:19:46.644
<v Brent>Papa John came in with a free members boost. I think this one's going to roast us a little bit.

01:19:47.024 --> 01:19:47.446
<v Chris>Okay.

01:19:47.853 --> 01:19:53.060
<v Brent>Here is a pick for your ham radio studying. It's called Ham Trainer.

01:19:53.617 --> 01:19:59.004
<v Brent>It's a progressive web app for studying for either the U.S. or Canada ham radio certification.

01:20:00.519 --> 01:20:03.816
<v Brent>Well, gents, I think we're starting to run out of reasons not to do this.

01:20:04.072 --> 01:20:08.224
<v Chris>It's impressive how persistent they are. It really is.

01:20:08.924 --> 01:20:13.070
<v Chris>They may be more persistent than the Arch people and the Nix people ever were.

01:20:13.418 --> 01:20:16.244
<v Chris>Honestly, the hams, I think, have been more persistent.

01:20:17.301 --> 01:20:18.625
<v Chris>Something needs to be done about this.

01:20:21.254 --> 01:20:22.984
<v Wes>I mean, we have to get our license.

01:20:24.208 --> 01:20:26.089
<v Chris>Can I get an agent that interfaces with ham radio?

01:20:26.861 --> 01:20:27.587
<v Brent>We would do that.

01:20:27.819 --> 01:20:28.376
<v Chris>Yeah.

01:20:28.527 --> 01:20:29.707
<v Brent>Was that last year or the year before?

01:20:30.087 --> 01:20:33.477
<v Chris>Is it ham-y? I know they got a lot of rules. Is it ham-y legal for our agents

01:20:33.477 --> 01:20:36.327
<v Chris>to talk to each other over ham radio? Could we have agents communicate?

01:20:36.327 --> 01:20:39.944
<v Brent>Oh, my goodness. You just figured it out. There you go.

01:20:40.258 --> 01:20:43.787
<v Chris>There you go. Moan comes in with a member boost. Just wanted to pass this gem

01:20:43.787 --> 01:20:46.277
<v Chris>along. A fellow co-worker shared on our internal Slack chat,

01:20:46.277 --> 01:20:50.359
<v Chris>Terminal2Shell.com. Check out Terminal2Shell.com.

01:20:51.235 --> 01:20:54.867
<v Chris>A critical flaw present in every operating system since 1971 allows anyone to

01:20:54.867 --> 01:20:58.307
<v Chris>open a terminal to obtain fully interactive shell instantly with no authentication

01:20:58.307 --> 01:20:59.908
<v Chris>beyond one that they already did.

01:21:01.287 --> 01:21:02.827
<v Chris>Terminal2Shell. Done.

01:21:02.967 --> 01:21:06.787
<v Wes>You know, we've got to be careful with this kind of satire because some of the

01:21:06.787 --> 01:21:08.497
<v Wes>closed platforms might just block the terminal.

01:21:08.497 --> 01:21:11.587
<v Chris>Hey, hey, oh, you could be right.

01:21:12.867 --> 01:21:13.617
<v Wes>Don't give them ideas.

01:21:13.617 --> 01:21:15.147
<v Chris>The idea is cute, though, right?

01:21:15.487 --> 01:21:16.287
<v Wes>We have everything to shell.

01:21:18.087 --> 01:21:21.647
<v Chris>You wouldn't ship a terminal today. It's too dangerous. Although it's more famous than ever.

01:21:22.717 --> 01:21:25.642
<v Chris>Hey, Brent's buddy, Chuck Runamuck, is back with a member, Boost,

01:21:25.642 --> 01:21:27.970
<v Chris>talking about whole house audio.

01:21:28.394 --> 01:21:32.562
<v Chris>My solution for the last 15 years is a Linux box K-Chuck running MPD connected

01:21:32.562 --> 01:21:36.442
<v Chris>to a CZE05B whole house FM transmitter.

01:21:36.442 --> 01:21:37.322
<v Wes>Oh, clever.

01:21:37.942 --> 01:21:38.835
<v Chris>Oh, yeah.

01:21:39.184 --> 01:21:41.222
<v Brent>It's like what we used to do in our cars.

01:21:41.222 --> 01:21:45.778
<v Chris>Yeah. Huh. Only 0.5 watts, so not overly illegal.

01:21:47.362 --> 01:21:51.352
<v Wes>Yeah, no 5.1, only stereo, but it plays on any FM radio, so that's pretty great.

01:21:51.352 --> 01:21:53.822
<v Chris>Sounds great up to one. A quarter of a mile or more.

01:21:54.082 --> 01:21:56.174
<v Brent>A quarter of a mile?

01:21:56.802 --> 01:22:00.012
<v Wes>This is making me think maybe it'd be a good idea like at my folks' house or something.

01:22:00.012 --> 01:22:00.802
<v Chris>Or the farm.

01:22:00.802 --> 01:22:01.522
<v Wes>Yeah, the farm.

01:22:01.522 --> 01:22:04.982
<v Chris>This would be great for the farm. Right? I think this is...

01:22:05.062 --> 01:22:05.342
<v Brent>Oh my goodness.

01:22:05.342 --> 01:22:08.422
<v Wes>You could have like a little pocket transistor radio that you walk around and

01:22:08.422 --> 01:22:10.282
<v Wes>you can tune into your stream at any time.

01:22:11.102 --> 01:22:12.502
<v Chris>Love this. Love this.

01:22:15.042 --> 01:22:17.821
<v Chris>Man. Thanks, Chuck. And thanks for running amok.

01:22:18.095 --> 01:22:22.812
<v Wes>Anonymous comes in with a member boost. I wanted to pass along this self-hosting

01:22:22.812 --> 01:22:26.181
<v Wes>platform. It's store.elfhosted.com.

01:22:26.395 --> 01:22:27.853
<v Wes>Not sure if it's been previously mentioned.

01:22:28.143 --> 01:22:31.242
<v Wes>I'm looking to check it out for my Open Gym setup. Looks promising for those

01:22:31.242 --> 01:22:34.399
<v Wes>that want to self-host, but don't have the tech know-how or the hardware.

01:22:34.631 --> 01:22:35.908
<v Chris>Huh, I've never seen this before.

01:22:36.077 --> 01:22:37.592
<v Wes>Your apps run for you.

01:22:37.766 --> 01:22:38.764
<v Chris>Well, I do like that.

01:22:39.565 --> 01:22:42.982
<v Wes>Pick your own apps, password managers, bookmark notes, dashboards.

01:22:42.982 --> 01:22:48.072
<v Wes>Run four of them for $9 per month or $18 on FlexPro. Swap whenever you like.

01:22:48.072 --> 01:22:52.392
<v Chris>No. $18 a month for Image, huh? Boy, if that's the thing, Image,

01:22:52.392 --> 01:22:53.933
<v Chris>they ought to just do that directly.

01:22:54.653 --> 01:22:56.502
<v Brent>So this is not self-hosting. Upselling Kuma is $1.29.

01:22:56.502 --> 01:23:01.872
<v Chris>A month. Oh, man. Vault Warden is $1.29 a month. Oh, boy, you'd just be better

01:23:01.872 --> 01:23:02.930
<v Chris>off giving that money to Bitwarden.

01:23:05.542 --> 01:23:07.189
<v Chris>I'm not sure how I feel about this. I'll be honest with you.

01:23:07.489 --> 01:23:11.259
<v Chris>A couple of red flags is they're reselling individual things that,

01:23:11.259 --> 01:23:12.647
<v Chris>yes, I know are difficult to set up.

01:23:12.960 --> 01:23:15.769
<v Wes>See, I'm going to push back. I don't know about this business because I haven't

01:23:15.769 --> 01:23:18.586
<v Wes>investigated. I have wanted exactly this for a long time.

01:23:19.529 --> 01:23:23.619
<v Wes>I want to run self-hosted open source stuff, but I want to pay an admin to do

01:23:23.619 --> 01:23:25.662
<v Wes>all the stuff I don't want to do to be on call for it.

01:23:26.514 --> 01:23:30.439
<v Wes>I don't want six accounts. Because if I self-host it, I can have one box that

01:23:30.439 --> 01:23:34.149
<v Wes>has all those things on it in a simple setup instead of having to have an account

01:23:34.149 --> 01:23:35.970
<v Wes>at Whitboard. or an account image.

01:23:36.255 --> 01:23:37.230
<v Chris>So you're saying...

01:23:38.745 --> 01:23:42.875
<v Chris>Okay, so you're saying like you would be all in on image if you didn't have

01:23:42.875 --> 01:23:44.005
<v Chris>to manage an image server.

01:23:44.005 --> 01:23:47.035
<v Wes>Yeah, and maybe not even me, right? Because I'm kind of a weirdo who could do that.

01:23:47.035 --> 01:23:49.403
<v Wes>But there are, I think, other people who maybe value open source,

01:23:49.629 --> 01:23:53.845
<v Wes>friends, family of ours, where it's like it's mostly that admin burden.

01:23:53.845 --> 01:23:57.635
<v Wes>And even with clankers of like who's responsible, who's on call.

01:23:57.635 --> 01:23:59.685
<v Wes>If this goes down and you start getting your family hooked on it.

01:23:59.895 --> 01:24:01.005
<v Chris>And there's OSs that have to be updated.

01:24:01.005 --> 01:24:01.505
<v Wes>Exactly.

01:24:01.505 --> 01:24:04.395
<v Chris>That's true, that's true. Okay, all right. You're kind of winning me around with that.

01:24:05.204 --> 01:24:10.005
<v Chris>I think what's initially turning me off is the pricing. So $18 a month for image

01:24:10.231 --> 01:24:13.735
<v Chris>is almost understandable because out of almost anything you could host,

01:24:13.735 --> 01:24:17.415
<v Chris>image could be one of the more challenging if you take a lot of photos and you want AI recognition.

01:24:18.062 --> 01:24:21.455
<v Chris>But where it kind of falls apart is like image frame, $9 a month is ridiculous.

01:24:21.455 --> 01:24:24.295
<v Chris>That's a tiny sidecar container. It doesn't take any additional resources.

01:24:24.295 --> 01:24:27.123
<v Chris>PeerTube, $18 a month for PeerTube?

01:24:28.035 --> 01:24:30.095
<v Brent>Is that because of the data? Like is it giving you data?

01:24:30.095 --> 01:24:34.695
<v Chris>It must. I mean it must be storage if it comes with it. AI tools?

01:24:34.695 --> 01:24:39.515
<v Chris>Ah, I don't know. All right. So tell us what you think. Like store.elfhosted.com, look through it.

01:24:40.375 --> 01:24:42.305
<v Chris>Where do you stand, listeners, on this kind of thing?

01:24:42.305 --> 01:24:45.182
<v Wes>Have you tried it? Have you seen other services doing this kind of thing?

01:24:45.310 --> 01:24:48.855
<v Chris>If it was, maybe you could bundle it all together.

01:24:49.295 --> 01:24:52.145
<v Wes>Yeah, and what's the right price point slash payment model if you were going to do it?

01:24:52.145 --> 01:24:55.055
<v Chris>The UI is approachable for new users looking at that. All right,

01:24:55.055 --> 01:24:56.449
<v Chris>well, M4 wraps this up, boys.

01:24:56.809 --> 01:24:59.004
<v Chris>Hi, guys. I've been listening to your open code setup and tips.

01:24:59.317 --> 01:25:03.263
<v Chris>Check out Passio Multiplexer at passio.sh. How do you think you really say that?

01:25:04.335 --> 01:25:08.535
<v Chris>It runs open code alongside Cloud Code, Codex, Pi, and Hermes with web and mobile

01:25:08.535 --> 01:25:11.920
<v Chris>apps. A cross-agent orchestration is in their schedules and remote host CLI.

01:25:13.563 --> 01:25:15.322
<v Wes>I'm going to say Paseo. Okay.

01:25:15.618 --> 01:25:20.431
<v Chris>And I just run it behind my reverse proxy of choice. Paseo.sh.

01:25:20.976 --> 01:25:25.542
<v Chris>Is this like a really, really fancy herder on steroids? Is that what I'm seeing here?

01:25:25.542 --> 01:25:26.712
<v Wes>Yeah, but like a graphical version.

01:25:26.712 --> 01:25:30.892
<v Chris>I guess, huh? Yeah. And with status updates of what they're working on on the

01:25:30.892 --> 01:25:32.253
<v Chris>sidebar. Pretty cool looking.

01:25:32.538 --> 01:25:33.412
<v Wes>Got plugins.

01:25:34.392 --> 01:25:38.640
<v Chris>P-A-S-E-O.sh. I do like that you can pick up on the mobile app.

01:25:39.098 --> 01:25:42.692
<v Wes>It's also got, if you want to use Timescript, it's got an SDK you can use,

01:25:42.692 --> 01:25:46.092
<v Wes>right? so you can build issue stuff, dashboards, orchestration services,

01:25:46.092 --> 01:25:48.758
<v Wes>reuse their code if you want. That could be handy.

01:25:50.092 --> 01:25:53.862
<v Chris>I will just quickly note that I have been recently testing the Hermes mobile

01:25:53.862 --> 01:25:56.228
<v Chris>app, and it is unreasonably good.

01:25:56.717 --> 01:26:00.772
<v Chris>I had no expectations of it being this good. The way it automatically updates

01:26:00.772 --> 01:26:06.851
<v Chris>the UI and indicates working in the background and tool calls and subagents, it's so good.

01:26:07.386 --> 01:26:09.157
<v Chris>It's so good. They've really done a great job.

01:26:10.596 --> 01:26:13.722
<v Chris>If you can, get on that beta. All right, let's wrap it up. Let's wrap it up.

01:26:13.722 --> 01:26:16.712
<v Chris>We had some good support. Thank you, everyone. Of course, we always want to

01:26:16.712 --> 01:26:19.252
<v Chris>say thank you to our members, too, who put their support on Autopilot.

01:26:19.252 --> 01:26:20.598
<v Chris>It really makes a huge difference.

01:26:21.068 --> 01:26:28.189
<v Chris>We had 13 of you stream sats, and collectively, you sat streamers stacked us 55,994 sats.

01:26:30.250 --> 01:26:34.012
<v Chris>When you bring it all together and you convert the fiat boost to sats,

01:26:34.012 --> 01:26:44.594
<v Chris>which are on sale this week, That means we stacked a total of 476,690 Satoshis. Not too bad at all.

01:26:44.948 --> 01:26:48.472
<v Chris>Helps after a long couple of weeks of travel. It really does.

01:26:48.472 --> 01:26:52.686
<v Chris>And we have big plans that we're starting to brew for 700 that we'll be talking about soon.

01:26:53.035 --> 01:26:55.496
<v Chris>So your support is very much appreciated at this time.

01:26:55.960 --> 01:27:00.252
<v Chris>If you'd like to send us a message, boost.jupiterbroadcasting.com.

01:27:00.252 --> 01:27:03.315
<v Chris>That's where you go. Members, you get a free boost.

01:27:11.564 --> 01:27:14.912
<v Chris>Now, just because we were hustling and bustling all week doesn't mean that we

01:27:14.912 --> 01:27:16.881
<v Chris>didn't come away with some great picks.

01:27:18.634 --> 01:27:21.812
<v Chris>So let's start with one that probably came in pretty handy for travel.

01:27:21.812 --> 01:27:25.361
<v Chris>I don't know if anybody actually had a chance to try this, but I think that was the idea.

01:27:26.777 --> 01:27:32.462
<v Chris>YouTube D or YouTube L N I S Y T L N S something like that. It's a,

01:27:32.462 --> 01:27:36.032
<v Chris>it's an audio and downloader app for Android. I don't really, the name Brent found it.

01:27:36.032 --> 01:27:36.962
<v Wes>I think he has to pronounce it.

01:27:36.962 --> 01:27:39.012
<v Chris>Yeah. Okay. That's like, that's the rule.

01:27:39.012 --> 01:27:39.452
<v Wes>There we go.

01:27:40.272 --> 01:27:43.232
<v Chris>If you find it, you're the jerk that has to be the one that pronounces it.

01:27:43.232 --> 01:27:44.674
<v Chris>So Brent, how do we pronounce this one?

01:27:45.592 --> 01:27:48.477
<v Brent>Y-T-D-L-N-I-S. Pretty simple.

01:27:48.860 --> 01:27:49.352
<v Wes>Cheating.

01:27:49.452 --> 01:27:51.432
<v Chris>That was rough too. It wasn't even that good.

01:27:51.432 --> 01:27:52.552
<v Brent>YouTube D-L-N-I-S.

01:27:53.032 --> 01:27:55.826
<v Chris>Tell us about this because this seems very handy for travel.

01:27:56.702 --> 01:28:01.012
<v Brent>Yeah, Wes was a gentleman and before we were headed to London,

01:28:01.012 --> 01:28:05.392
<v Brent>he was like, hey Brent, don't forget to download stuff for that long eight to

01:28:05.392 --> 01:28:07.383
<v Brent>nine hour trip without any internet.

01:28:08.097 --> 01:28:10.611
<v Chris>Wow, is that your way of saying you better entertain yourself, kid?

01:28:12.729 --> 01:28:16.189
<v Wes>I don't want him to be bored. He does dangerous stuff when he's bored.

01:28:17.727 --> 01:28:20.049
<v Chris>He just makes pleasant conversation with me the entire flight.

01:28:20.734 --> 01:28:23.699
<v Chris>He never tells me to download anything. In fact, he and I drove to Texas and

01:28:23.699 --> 01:28:26.005
<v Chris>back, and we just had pleasant conversation the entire time.

01:28:26.643 --> 01:28:27.549
<v Chris>I don't know. I've never had.

01:28:28.329 --> 01:28:30.184
<v Chris>Anyways, but useful. Okay, continue on.

01:28:32.249 --> 01:28:36.469
<v Brent>It's basically YouTube DL on your phone. It's exactly what you think it is.

01:28:36.969 --> 01:28:40.599
<v Brent>It allows you to, well, the reason I liked it is it has a really nice interface

01:28:40.599 --> 01:28:45.669
<v Brent>for on mobile to look through a bunch of videos or just like YouTube channels

01:28:45.669 --> 01:28:49.269
<v Brent>that you can select specific videos to download.

01:28:49.269 --> 01:28:51.181
<v Chris>The interface seems to be what really sets it apart.

01:28:51.361 --> 01:28:54.014
<v Brent>Yeah. And that's exactly what I was looking for. I was like,

01:28:54.315 --> 01:28:56.929
<v Brent>I can download from YouTube using my laptop. That's fine.

01:28:57.049 --> 01:29:00.823
<v Brent>And then transfer it to my phone. But that's two steps. I don't want to do that.

01:29:01.421 --> 01:29:06.679
<v Brent>so this came in handy to just get stuff locally which i have to admit i haven't

01:29:06.679 --> 01:29:09.909
<v Brent>done very much for flights previously,

01:29:10.589 --> 01:29:15.109
<v Brent>i'm mostly a music guy but uh or audiobooks but i did it this time sure paid

01:29:15.109 --> 01:29:19.078
<v Brent>off that was a fantastic uh suggestion west thank you very much,

01:29:19.781 --> 01:29:24.390
<v Brent>and uh so i would highly recommend this it also has crazy features in the back like,

01:29:24.907 --> 01:29:28.339
<v Brent>you could just pull up a full terminal on your phone if you want to i guess

01:29:28.339 --> 01:29:32.279
<v Brent>that's how it's doing youtube dl on the back end and it just like auto downloads

01:29:32.279 --> 01:29:35.425
<v Brent>youtube dl whenever it's it's got a new version and stuff so it's pretty cool.

01:29:35.849 --> 01:29:41.169
<v Chris>It can do it can do a lot it can do episode recuts um in here there's a lot

01:29:41.169 --> 01:29:45.119
<v Chris>of good stuff that it can pull it's it's beyond kind of any other youtube downloader

01:29:45.119 --> 01:29:46.693
<v Chris>app that i've ever seen for android before,

01:29:47.349 --> 01:29:51.349
<v Chris>um and it is a gpl3 licensed ytdlnis,

01:29:52.549 --> 01:29:52.881
<v Chris>for that,

01:29:54.140 --> 01:29:58.138
<v Chris>Now, this I'm actually seriously considering. I haven't made the switch yet,

01:29:58.138 --> 01:30:00.439
<v Chris>but I have been very frustrated with web mail.

01:30:00.810 --> 01:30:05.588
<v Chris>Always just makes my browser run slow, especially on my old Latitude.

01:30:05.913 --> 01:30:09.373
<v Chris>It's like I can type faster than it can input into the interface.

01:30:09.831 --> 01:30:16.546
<v Chris>So T-Mail has come along. It's a terminal email client with a special workspace for conversations.

01:30:16.773 --> 01:30:20.888
<v Chris>It's a fast keyboard and mouse-friendly mail client for the terminal and keeps

01:30:20.888 --> 01:30:24.028
<v Chris>your mail in a local mail dirt, It syncs with any IMAP server in the background

01:30:24.028 --> 01:30:26.345
<v Chris>and sends over SMTV, SMTP.

01:30:27.368 --> 01:30:31.262
<v Chris>And, of course, it looks good. And it's 99% Rust.

01:30:33.827 --> 01:30:35.173
<v Brent>Didn't quite cut to 100.

01:30:35.888 --> 01:30:36.611
<v Chris>Gmail.

01:30:36.611 --> 01:30:39.921
<v Wes>And next to the conversation list, it draws each thread as a little map so you

01:30:39.921 --> 01:30:42.611
<v Wes>can see who answered whom at a glance, which I really like.

01:30:42.611 --> 01:30:44.071
<v Chris>That's a fun feature.

01:30:44.531 --> 01:30:46.161
<v Wes>It's Rust. It's got Ratatouille in there.

01:30:46.161 --> 01:30:46.531
<v Chris>Of course.

01:30:46.531 --> 01:30:50.171
<v Wes>And so it has all the right rich primitives to, if you're going to try to do

01:30:50.171 --> 01:30:51.433
<v Wes>this in the terminal, to do it right.

01:30:51.764 --> 01:30:56.681
<v Chris>And it resizes nicely. So I haven't done it yet, but I am very seriously considering

01:30:56.681 --> 01:30:59.161
<v Chris>this as a Tui male contender.

01:30:59.161 --> 01:31:01.981
<v Chris>I know there's a lot of classics that I'd be shoving my nose up or whatever

01:31:01.981 --> 01:31:04.731
<v Chris>the saying is, but I do like some of the concepts they have here.

01:31:04.731 --> 01:31:07.571
<v Chris>And that diagram thing does seem kind of neat when you're trying to track down.

01:31:07.571 --> 01:31:09.811
<v Wes>Just a quick way to understand, kind of like Major was saying.

01:31:10.971 --> 01:31:16.254
<v Chris>So that's T-Mail, and it's MIT licensed. And then I'm betting Wes found this one.

01:31:16.758 --> 01:31:17.711
<v Wes>I thought you found it.

01:31:17.879 --> 01:31:22.381
<v Chris>Oh, then it's a Brentley pick. All right, Brentley, then you get to determine.

01:31:22.381 --> 01:31:25.025
<v Chris>It's pretty obvious, but you get to determine how this one is pronounced.

01:31:25.692 --> 01:31:27.031
<v Brent>Well, T-T.

01:31:28.416 --> 01:31:28.771
<v Chris>Stop it.

01:31:30.210 --> 01:31:32.629
<v Brent>No, it's called Tailmux. And it

01:31:32.816 --> 01:31:39.630
<v Brent>basically, I got this from a listener who shared it with me at our meetup.

01:31:40.728 --> 01:31:45.505
<v Brent>Tailmux allows you to connect to multiple tailnets at once.

01:31:45.632 --> 01:31:49.221
<v Brent>Remember we've been having this problem for, well ever since we started using

01:31:49.221 --> 01:31:52.541
<v Brent>Tailmux is you can't use them at the exact same time.

01:31:52.837 --> 01:31:56.518
<v Brent>So this allows you to use multiple tailnets connected at the same time,

01:31:58.088 --> 01:32:00.291
<v Brent>Well, that's basically it. I think it's amazing.

01:32:00.888 --> 01:32:04.708
<v Chris>I have been thinking about how to solve this. One of the things that's been

01:32:04.708 --> 01:32:11.158
<v Chris>on my mind, actually, is to keep a legacy tail net, because there's a lot of

01:32:11.158 --> 01:32:14.174
<v Chris>applications that have integrations for it, or like IPKVMs,

01:32:14.749 --> 01:32:19.364
<v Chris>and bridge that with a host to a Nebula network that's sort of the main mesh network.

01:32:20.388 --> 01:32:23.368
<v Chris>But I hadn't really figured out how to solve for the fact that there's currently

01:32:23.688 --> 01:32:27.278
<v Chris>multiple tail nets. So you can see using something like tailmux to kind of solve

01:32:27.278 --> 01:32:28.222
<v Chris>for that part of the problem.

01:32:28.403 --> 01:32:33.018
<v Wes>Yeah, I've been doing a setup with network namespaces so I can have multiple tailnets going.

01:32:33.018 --> 01:32:33.768
<v Chris>I like that too.

01:32:33.768 --> 01:32:37.358
<v Wes>And hey, maybe I could just replace that with tailmux and it'd be simpler. That could be nice.

01:32:37.358 --> 01:32:40.328
<v Chris>Maybe. Your solution's pretty good too, though. I like that as well.

01:32:40.328 --> 01:32:43.498
<v Chris>But yeah, tailmux, and it's up there on the GitHub.

01:32:43.498 --> 01:32:44.447
<v Wes>Should be pretty useful.

01:32:44.611 --> 01:32:47.518
<v Chris>And I believe it was BSD3 clause licensed.

01:32:47.518 --> 01:32:48.162
<v Wes>Yeah, that is right.

01:32:48.476 --> 01:32:52.528
<v Chris>So there you have it. But of course, the most important pick,

01:32:53.085 --> 01:33:00.040
<v Chris>not just of this week but of the season of the next at least few weeks is the Holiday Home Lab,

01:33:03.599 --> 01:33:11.448
<v Chris>holiday.jupiterbroadcasting.com. Your glorious mess or your perfect setup.

01:33:11.448 --> 01:33:13.616
<v Chris>We want it and embrace all of it.

01:33:13.989 --> 01:33:16.898
<v Chris>We really had a lot of fun last year and we're going to try to make it even

01:33:16.898 --> 01:33:20.598
<v Chris>better this year, but it only works if you take the time to actually submit

01:33:20.598 --> 01:33:23.526
<v Chris>your home lab. I know it's some work, but we've tried to make it very easy for you.

01:33:24.072 --> 01:33:27.448
<v Brent>Also, if you submitted last year, I'm sure you made upgrades.

01:33:27.448 --> 01:33:32.437
<v Brent>So we want to see what you changed, why you changed it. Maybe you kept it just the same and tell us why.

01:33:32.865 --> 01:33:33.218
<v Chris>Yep.

01:33:33.218 --> 01:33:36.953
<v Wes>And if you do try, and please do, give us feedback along the way.

01:33:38.230 --> 01:33:41.518
<v Wes>New setup, new infrastructure, and if it works, it's something we hope we can

01:33:41.518 --> 01:33:45.098
<v Wes>continue to build on for a few years after. And there's only one way to make

01:33:45.098 --> 01:33:48.118
<v Wes>it really nice, and that's to mess it up a few times first.

01:33:48.118 --> 01:33:52.378
<v Chris>I think that's a good point. We hope this is something that not only do we build

01:33:52.378 --> 01:33:54.728
<v Chris>on, but then we can start iterating with the community and public,

01:33:54.728 --> 01:33:56.908
<v Chris>too, throughout the year. And it's something we've all worked on,

01:33:56.908 --> 01:33:58.535
<v Chris>and it's going to be a lot of fun.

01:33:59.047 --> 01:34:02.756
<v Chris>And we're just getting started. So there's a lot there, all right?

01:34:02.993 --> 01:34:05.235
<v Chris>holiday.jupiterbroadcasting.com,

01:34:08.594 --> 01:34:12.128
<v Chris>Don't forget you can upgrade your experience by making it a live vibe.

01:34:12.128 --> 01:34:15.722
<v Chris>Head over to jblive.tv on a Tuesday, which is actually a Sunday,

01:34:16.053 --> 01:34:19.032
<v Chris>converted to your local time at jupiterbroadcasting.com slash calendar.

01:34:19.374 --> 01:34:22.382
<v Chris>And Wes, we got transcripts, we got chapters. Where do they find that?

01:34:22.614 --> 01:34:25.288
<v Wes>You can find that at, well, wherever you get our podcast actually,

01:34:25.288 --> 01:34:29.408
<v Wes>because it's in the feed, but feeds.jupiterbroadcasting.com slash lup for this one.

01:34:29.408 --> 01:34:30.928
<v Chris>I didn't think you'd give the actual URL.

01:34:30.928 --> 01:34:33.508
<v Wes>Yeah, well, you know, you can curl it down, You can give it to a bot.

01:34:33.508 --> 01:34:33.998
<v Chris>Get that MP4 file.

01:34:34.508 --> 01:34:35.548
<v Wes>You can book it in Firefox if you want.

01:34:35.548 --> 01:34:36.558
<v Chris>Read that transcript.

01:34:36.558 --> 01:34:39.368
<v Wes>There's a whole bunch of extra little hidden stuff in there, turns out.

01:34:39.368 --> 01:34:43.158
<v Chris>That's right. There you go. See? You can also find that linked on our website.

01:34:43.158 --> 01:34:45.588
<v Chris>In fact, links to everything we talked about today, how to contact us,

01:34:45.588 --> 01:34:49.928
<v Chris>our Mumble Room, our Matrix Room, how to become a member, LinuxUnplugged.com,

01:34:49.928 --> 01:34:52.156
<v Chris>and of course, JupyterBroadcasting.com.

01:34:52.510 --> 01:34:56.456
<v Chris>Thank you so much for joining us on this week's episode of your Unplugged program,

01:34:56.752 --> 01:35:01.322
<v Chris>and we'll see you right back here next Tuesday, as in Sunday.

