0:00

So when we first started digging into today's topic,

0:03

I kind of had a long-timers reaction.

0:05

Oh, I've been here since the 90s. What

0:08

are you talking about? Someone new is coming to Linux

0:10

and they claim they're going to solve all our problems.

0:12

You know, that was sort of my first reaction. But

0:14

then as we really dug in more, I

0:17

started to get excited to see Amacube

0:19

getting created and the passion around it.

0:22

It really is kind of the best

0:24

of Linux. It's fun watching somebody discover

0:26

this and see their ability to make

0:28

an impact and make a change and

0:31

discover something special in Linux. And

0:33

that's what we've had a front row seat to this week. Hello,

0:47

friends, and welcome back to your weekly Linux

0:49

talk show. My name is Chris. My name

0:51

is Wes. And my name is

0:53

Brent. Hello, gentlemen. Yep. Coming up on

0:56

this week's episode, we try out Amacube,

0:58

an opinionated Ubuntu desktop setup for

1:01

power users and Mac OS expats

1:03

that are sick and tired of the way things

1:05

are going. We try that and then share our

1:07

thoughts as long timers. Then we'll round out the

1:09

show with some great boosts and picks and

1:12

a lot more. So I want

1:14

to say good morning to Tailscale.

1:16

tailscale.com/unplugged. Check it out. It

1:19

is programmable networking software that is private,

1:22

secure by default and powered

1:24

by Waggled. That's right. You can

1:27

try it for free for up to 100 devices. It's

1:29

not a limited time thing. It's the plan I'm on. Try

1:32

it for free and support the show. No

1:34

more inbound firewall ports.

1:37

I say tailscale.com/unplugged and

1:39

a big time appropriate greetings to our virtual

1:41

lug. Hello, Mumble Room. Hello,

1:45

everybody. Thank you for joining us. It's

1:47

nice seeing you in there getting

1:49

a nice low latency Opus stream of the show

1:52

as we do this live on a Sunday noon

1:54

Pacific 3 p.m. Eastern. And

1:56

there's a lot to get into this

1:58

week. So let's Let's start with a bit

2:00

of housekeeping. There's a few items we want you guys to

2:02

know about. Now

2:06

number one, we're going

2:08

to introduce the Knicks drinking game on the

2:11

show. Now this

2:13

is in response to perhaps

2:15

some feedback that we try to bring

2:17

Knicks up every moment possible. This

2:19

is designed to help throttle that a

2:21

bit, maybe introduce some sort

2:23

of buffer or punishment should the host accidentally

2:27

utter the words too much. So

2:29

here is the official decree, our commitment

2:31

to you upon utterance of this. Any

2:34

mention of the name Knicks within this program

2:36

shall warrant a hearty swig of spirits by

2:38

your hosts. One shot of

2:40

spirits shall be had by all hosts present

2:43

except when chapters

2:45

bear its name or fortune favors us

2:47

a boost which mentions Knicks. In

2:49

such designated chapters or moments such as

2:51

the boost, one shot

2:54

shall suffice for the initial mention

2:56

of Knicks. Oh my. I

2:59

feel like I better just take a preemptive drink right

3:01

away. Then there's going to be another.

3:04

Do we have enough drinks? That's the real question.

3:06

Do we all agree? Do we need to make

3:08

any clarifications? Yeah I'm kind of

3:11

curious here. Okay so

3:13

there's exceptions for if we're doing like

3:15

a specific Knicks chapter, right? Or

3:17

if someone boosts in about it. Right.

3:20

Then it's like at the first mention of

3:22

Knicks. Are those separate? Is this like we,

3:24

you know, we still have to do at least one

3:26

drink? It's just that we won't have to drink

3:28

for every single mention after that in that particular

3:31

segment? Okay. Yeah.

3:33

I feel like the first time it's mentioned in those segments because

3:35

like we're in that's where that is like like for example in

3:38

Knicks chapter we'll chapter it off and then you know like that's

3:40

what they're talking about. You could just skip right over it if

3:42

you want. So only one punishing drink.

3:44

Same with the boost so that way we can't

3:46

everybody say Knicks in every single boost and then

3:48

we just get sloshed. The first time it gets

3:50

mentioned in the first boost we take a shot.

3:52

We're covered there therefore after the boost. So anywhere

3:54

else in the main show, every mention, one drink,

3:57

one shot. All right. Cheers

4:00

to this boys. All right. Lock it in boys. All

4:05

right. So that's the important business out

4:07

of the way. We also have some

4:09

meetups coming up. Our buddy Alex is

4:11

going to be in Norwich Sunday, June

4:14

16th meetup.com/Jupiter Broadcasting. Go have a pint

4:16

with Alex. And then

4:18

we are just in the very

4:20

early stages of planning a Spokane

4:22

meetup in Eastern Washington on Saturday,

4:24

July 13th. Go to

4:27

meetup.com/Jupiter Broadcasting. If

4:29

you are interested at all,

4:32

because if we don't see a few people sign up, we're

4:34

not going to bother. So last time we didn't see very

4:36

many people sign up, we kind of made the call to

4:38

cut it. And then we heard from a bunch

4:40

of people that were sad to see we didn't go meetup.com/Jupiter

4:43

Broadcasting. And then

4:45

there is one more event coming

4:48

up that we want to let people know

4:50

about, right, Brentley? There sure is. Now, a

4:52

couple of weeks ago, I set the intention

4:54

to have a September meetup in Berlin connected

4:56

with the Next Cloud Conference, which

4:59

is also in the same

5:01

place. meetup.com/Jupiter Broadcasting. Now that's

5:03

set up right now for

5:05

September 13th. So

5:07

please RSVP there if you can

5:09

just to signal your interests. But

5:11

the whole reason for this particular

5:14

meetup is to have it

5:16

connected with the Next Cloud Conference. And

5:18

that happened last year, which was a ton

5:20

of fun. The people from the JB community

5:23

that joined me there really enjoyed themselves. And

5:26

every year we have these lightning

5:28

talks that the community can be a part

5:31

of and the call for speakers is open

5:33

right now. So we will have a

5:35

link to that. If you want to do a little trip to

5:37

Berlin and you want to hang out with me

5:39

and the rest of the JB community there, please, yeah,

5:42

come join us. It's going to be a good

5:44

time. Sounds interesting. All right. Very good. That's a lot

5:46

going on. So go check

5:48

it out. meetup.com/Jupiter Broadcasting. We'll have links

5:50

to everything in the show

5:52

notes, of course. So for the last

5:54

few years on the show, I think

5:57

we've kind of had like this slow

5:59

burn theory. about desktop Linux. And

6:02

sometimes we've come at it in different directions. We've

6:05

talked about it a little bit in the last couple of

6:07

episodes in the past. We've talked

6:09

about it in maybe the sense of, did

6:11

we focus on the wrong thing for too

6:13

long? We being Linux advocates and

6:16

developers of Linux desktop, have

6:18

we wasted time trying to appeal to this

6:20

totally mythical new computer user who doesn't know

6:22

how to use a computer, but somehow ends

6:24

up, ends up using Linux? I

6:26

mean, and I, I don't want to hammer on this too hard,

6:29

but if you look at the design ethos

6:31

behind the standard Ubuntu desktop or

6:34

GNOME or many of them, it's

6:37

designed to appeal to somebody who doesn't

6:40

know what a computer is as

6:43

if they were somehow going to just float

6:46

down onto a computer and

6:48

it would just be bestowed with Linux. And we had

6:50

to make sure Linux would work great for them. And

6:53

we've argued now for years on this

6:55

show that the next real wave of

6:58

adopters of desktop Linux is

7:00

most likely going to be technically inclined

7:02

folks, people that are looking

7:04

to get away from commercial operating systems,

7:07

people that are getting frustrated with the

7:09

strategy taxes. Yeah. And it kind of

7:11

feels like Linux is maybe closer to

7:13

being something deployable as a, you know,

7:16

a power tool for users who are using

7:18

their computers to, to create

7:20

software, to work in on it things who

7:22

are familiar with all the

7:24

underlying bits, at least in principle, then

7:27

we are to really being a great general purpose

7:29

operating system. Yeah. Well said. We've

7:31

been seeing this theme for the last couple of weeks on this

7:33

show because this conversation has been

7:36

going on in, on the broader

7:38

internet. Yeah. You know, that said, I feel like,

7:41

you know, my parents have been on Linux for

7:43

like many, many years now. And so there, there's

7:45

still a space for those new users, but

7:48

I, yeah, I agree with you Chris. This last

7:51

week, at least we've seen maybe a new type

7:54

of user that's coming

7:56

to Linux, especially with all this AI craze

7:58

in some of the bigger. operating systems

8:00

and that's a real opportunity for us.

8:02

And I remember last episode you were saying, hey, this

8:05

is our chance to not screw it up. And

8:07

I'm hoping this episode we can see evidence of

8:09

that. Yeah, you know, so today I saw a

8:11

tweet from just a few hours ago from Notch,

8:13

the creator of Minecraft, and he writes, all right,

8:15

that's enough spyware in my OS. Do

8:18

I go to desktop Mac or do I have the energy

8:20

to go full Linux? Not sure. I'm

8:22

tired of my operating system treating me like

8:24

the product. That hit.

8:26

Amen. And then, for

8:28

about the last month, we have

8:30

seen David Henenmeyer Hanson, or DHH,

8:33

go on about his transition first

8:35

to Windows from Mac OS after being

8:37

a 22, 25 year, whatever it is, multi,

8:41

you know, 20 plus year user of Mac OS. He

8:44

gets frustrated with Apple's direction, with Apple's policies

8:46

as a company. He gets

8:48

kind of into the spot where he decides

8:50

it's time to try something else. And first

8:52

it was Windows, and then he tried Linux.

8:55

Yeah, so I have been on a personal

8:57

journey of discovery when it comes to computing

8:59

in the last few months. The

9:02

final straw kind of hit the

9:04

camels back at some point when

9:06

Apple announced they were yanking support

9:09

for web apps in Europe in

9:11

their petty fight with EU bureaucrats

9:13

over their monopoly case. And

9:16

I just, at that point, finally felt like, you know

9:18

what, why am I still

9:21

supporting this company? And I don't even

9:23

mean that in a economic sense.

9:25

I mean that in a sense of attention.

9:28

Why is Apple still the gravity of

9:30

all my computing? Why do I have

9:32

all these Apple devices? Why am I

9:34

on all these Apple services? If I

9:37

fundamentally have grown to dislike how the

9:39

companies run. And this is the

9:41

slow bleed that we've been talking about for a

9:43

while. Now, DHH is the creator of Ruby on

9:45

Rails. He's the co-owner of 37signals, which

9:48

is the company behind Basecamp and Hey, which

9:51

he's also well-documented in the Apple space for

9:53

battling with app store policies with Apple, which

9:55

we've covered on Coda radio quite a bit.

9:59

And he said, you know, I have a fundamental misalignment

10:01

with Apple. Yeah, you know, he's not

10:03

just a Apple user as a consumer as someone

10:05

using it as a workstation, but is also, you

10:07

know, someone making products and having to interface them

10:09

with Apple from that perspective. So I think that

10:11

definitely also brings some color to how he views

10:14

the company. And this really

10:17

came to a head, I don't know, a week ago

10:19

when I think it's been actually since our last episode,

10:21

he announced on the cube, O

10:24

M A K U B, which turns

10:26

a fresh Ubuntu installation into a fully

10:28

configured, quote unquote, beautiful modern

10:31

web development system by running a

10:33

single command. It's like the chef's

10:35

choice of a developer setup for Ubuntu 24.04 as curated

10:37

by DHH. And

10:42

they note that, yes, you could do this

10:44

in other ways, obviously, but they wanted to

10:46

create something that was tailored as

10:48

they put it upfront by someone

10:51

with strong opinions that's been

10:53

created for developers. And

10:55

it's got a curated set of applications that you'll

10:57

kind of see as we go through here and

11:00

an Ubuntu base. Some of

11:03

the design decisions that I think we'll get

11:05

into are really fascinating to me here. And

11:07

you mentioned, Chris, seeing Linux with

11:10

new eyes and it feels

11:12

like this project specifically has

11:15

taught us a lot

11:17

about how those eyes see Linux and

11:19

want Linux to be

11:21

and look and feel and behave,

11:24

not to give too much away. But I didn't

11:27

think I'd be this curious about this project. And

11:30

I'm, do you feel the same

11:32

way over there? At first, I was a little put

11:34

off to tell you the truth, because

11:36

I would imagine a lot of people listening. Their

11:38

first thought is, well, this is the

11:40

path to frustration. We have all

11:43

seen somebody really smart come

11:45

along and create a customization script for

11:47

Ubuntu that works for a release or

11:49

two and then becomes just

11:51

impossible to maintain. And

11:54

so that was my first reaction, because I was like,

11:56

oh, I've been here before. But then

11:58

you're right, as we dug into it and we

12:00

looked. at it, I thought, actually, this is a

12:02

real opportunity to understand and appreciate what this user

12:04

base finds valuable. And

12:09

so when I installed it, which I did on Ubuntu 24.04,

12:14

I kind of at that point had wrapped my head around what

12:16

their goal was. And they say it here, they say they wanted

12:19

to streamline just bootstrapping a Linux environment, something

12:21

for themselves. At this point, the script is

12:23

and they admit it, it's really kind of

12:25

designed for the staff at 37 signals

12:28

and DHH. Their plan

12:30

is is they have a couple of people

12:32

and DHH in house at 37 signals using

12:34

Linux. And their intention is new hires

12:36

will also start using the setup out of the box. And

12:38

then over time, they're going to try to migrate more

12:41

of their staff. But Wes, one of the things

12:43

that means is you do end up with an

12:46

install that has some stuff you might not actually

12:48

want installed. Oh, yeah, definitely. I mean, who doesn't

12:50

need a MySQL and Redis container just pre

12:53

setup for you. There's a bunch of other stuff,

12:56

you know, like one password,

12:58

Spotify, WhatsApp

13:00

installed. But I think

13:02

if you get too caught up in those kinds of things, you

13:05

might you might be missing the spirit because those are easy to

13:07

remove and nothing about this, like, Oma

13:10

cubes not going to forcefully reinstall it.

13:12

So it's just kind of like get you

13:14

to a nice base. And that's kind of like that's the

13:16

that's the topmost layer. I think where a lot of the

13:18

niceties come in is, you know,

13:21

all of the theming, the customization and

13:23

like the pre setup and pre-configured tweaks

13:25

to applications like neovim

13:27

and the terminal. Yeah. Yeah.

13:30

So they're using a lacrity in place of

13:32

the standard gnome shell. It is all based

13:34

on top of gnome in there. It runs

13:36

LG or Yelly, whatever, which gives

13:38

you multiple pains in session, which we love. Thank

13:41

you. It's bash underneath, of course, but

13:43

with more tooling by default. You got

13:45

neovim that's been pre-configured with lazy vim

13:48

and vs codes installed. Gnome

13:51

has been tweaked for more of a

13:53

keyboard for centric kind of setup with

13:55

some window tiling stuff installed. You launchers

13:57

pre-installed set up to super space. So

14:00

that way you have a launcher in there. One

14:03

thing I actually really liked is there is

14:05

this mapping to the caps key,

14:07

so caps M, and then you enter a letter

14:09

of an emoji and it just inserts an emoji.

14:12

That was actually kind of nice. And

14:14

then what will really hit you is the look. It's

14:17

been re-themed to Tokyo Night, and

14:19

you can actually select from a few

14:21

themes by re-running the Amacube command

14:24

later. But you get, and when you

14:26

do that, you get the terminal

14:28

gets re-themed, the editors get re-themed,

14:30

the background gets changed, the U-Life

14:32

for GNOME, the GNOME theme gets

14:35

changed. It also installs some great

14:37

looking fonts. They're some of

14:39

my favorite fonts on Linux. Yeah, like Microsoft Cascadia.

14:41

Right, well it's a good looking font. Yeah,

14:45

no bias at all. It is though,

14:47

it really is nice. And then a

14:49

handful of GNOME extensions, you get Docker

14:51

and like Wes was saying, MySQL and

14:54

Chrome and Slack, and some of these

14:56

things that I think some

14:58

people listening probably wouldn't necessarily want, but that's

15:00

how this kind of script works, especially right

15:02

now. I do get

15:04

the sense that they're open to input, and

15:07

they're creating documentation around some of this. But

15:09

when you're done, it's like you have an

15:11

Ubuntu setup that's kind of been maxed

15:13

out a little bit, the sort of purpose built

15:15

for a really nice looking developer workstation with

15:18

a workflow that, while not a one

15:20

to one to macOS, is

15:22

trying to outdo macOS in some areas. I think

15:24

you do have to give them credit. I

15:26

mean, there's the theme, which is very nice and

15:29

consistency I think is appreciated. But

15:31

it's also just with the tiling, with

15:33

some of the configuration for GNOME, it

15:36

stops feeling so much like Ubuntu in a way.

15:38

I mean, obviously it's still there and you get the

15:40

benefits of that, right? Like you're still on Ubuntu

15:42

base, you have apt under the hood, you can download

15:44

dev files and install them like

15:46

the script ends up doing a bunch. But

15:49

you get something that does have, I think,

15:51

a distinct look and feel to it. I

15:53

also have to give DHH some credit. I think I've

15:55

seen in some of the commentary on this online, some

15:57

of the more veteran Linux folks who do a

15:59

lot. a lot of customization being like, why'd

16:02

you use alacrity? You could have used Wes term, or you know,

16:04

like a bunch of different

16:06

opinions and customizations. And you

16:08

might argue with some of the apps that come pre-installed

16:10

or you know, which apps are for

16:12

which purpose. But I think a lot of the

16:14

picks are not bad, you know. Zornel

16:17

plus plus is there for filling out and

16:19

signing PDF forms. And I knew about that one,

16:21

but I hadn't tried it for years. And it is

16:24

really nice. Flame Shot comes by default, which is

16:26

a great screenshotting tool. Plus

16:29

stuff like Lazy Docker and Lazy Git.

16:32

So there might be some stuff you didn't need, but there's also some

16:34

stuff that I think a lot of people

16:36

would like and might not have known about.

16:38

You get the sense that DHH got

16:40

really excited and went down the rabbit hole

16:43

and watched a ton of YouTube videos, read

16:45

a ton of blog posts, hopefully listen to

16:47

some podcasts, and really got a sense of

16:49

the different kinds of tools that he likes.

16:52

He's built the setup script while he's super

16:54

passionate about it. You know how you're in

16:56

that honeymoon phase and you really have all

16:58

of the energy in the world for this

17:00

and you'll really commit. And he's taking advantage

17:02

of that energy and building out documentation around

17:04

it, GitHub around it, getting

17:07

people in his company on board. It's

17:09

a fascinating transition to watch. And

17:11

it's neat to see somebody create something kind of

17:13

at the peak of that excitement when they're truly

17:15

enthusiastic about this, right? Because if this just becomes

17:17

normal for them for 37 signals

17:20

in DHH in three, four, five years,

17:23

they're not gonna quite have this passion for it because it's

17:25

just gonna be the day-to-day operation. So

17:27

we're tapping in when some special creative energy is happening

17:29

right now. collide.com/unplugged.

17:35

You've probably heard me talk about collide because I think it's just

17:37

a game changer. But have you heard

17:40

that collide has joined forces with one password?

17:42

It's big news because these two companies have

17:46

really exemplified customer first, user

17:48

first security solutions. And

17:50

collide for over a year has had collide

17:53

device trust, which has helped companies with Okta

17:55

that only known and secure devices can access

17:57

their data. Now, there's a new technology called

18:00

doing it as part of one password. So if

18:02

you've got Okta and you've been meaning to check

18:04

out Collide, now is the time. This system is

18:06

so slick. It gives users the ability to solve

18:08

problems. I wish I had this when I was

18:11

in the business. And it comes with a library

18:13

of pre-built device posture checks so you can get

18:15

started right away. But of course, of

18:18

course, you can write your own if you need to. When

18:21

things come up, and you can use

18:23

Collide on devices that don't have MDM.

18:26

So contractor devices, tablets, Chromebooks,

18:28

you know, the BYOD trend,

18:31

which barely was getting started

18:33

back in my day is huge now. So

18:35

you need something that addresses that, then also

18:38

has it all under one pane of glass

18:40

to manage. Windows,

18:42

Linux, Mac, everything, one dashboard, one

18:44

set of reports. It's so slick.

18:47

Go check out Collide now that

18:49

it's part of one password, they're

18:51

just getting better. So support the

18:53

show and go to kolide.com/unplugged. That's

18:55

collide.com/unplugged. To learn more and to

18:57

support the show and check out

18:59

their information. That's collide.com/unplugged.

19:07

Well, I gave Omicub a spin this week,

19:09

and I have a few impressions that

19:11

I thought we could share. The

19:13

very first one for me was that

19:16

intro video that he includes on, I

19:19

think it's omicub.org, right

19:21

front and center about why,

19:23

like what's the intention, who's it

19:25

for, even some things

19:28

like his use case and

19:30

exposing key bindings and the workflow

19:32

that this was designed around. And

19:35

I thought that was just like a

19:38

very simple thing to add as a,

19:41

you know, marketing for this project. But

19:43

also it just for me was a

19:45

really good launching point into this project

19:47

without having all these, you know, which

19:49

we've seen on Reddit talking about this,

19:51

these preconceived notions of what this should

19:54

be or who the audience should be.

19:56

And so I thought, geez, every project

19:58

should have a nice, you know, it's like, a

20:00

20 minute watch, but there's so much info

20:02

in there. And that for

20:04

me was a really nice introduction

20:06

to this project. You

20:08

know, there's a lot of folks who have dot files or

20:11

other sort of configurations published on the web. And

20:13

I saw some of that in the commentary on

20:15

this too, of like, how is this new, right?

20:17

Like there's tons of people are already publishing their

20:19

setups on Ubuntu. But I think what you're hitting

20:21

on there, Brent, that like the introduction, the

20:23

actual, you know, sort of seeing him

20:25

go through the workflow and showing how

20:27

he uses the configured system adds a

20:29

lot to kind of grokking

20:32

what DHH is trying to do

20:34

with this. Well, and also exposing some

20:36

of the like thoughtfulness that went into

20:38

some of the decisions, because for a

20:40

lot of these tools, you have, you

20:42

know, sometimes five different reasonably

20:44

good alternatives and you have to

20:46

choose one in the end

20:48

for a project like this. But

20:51

really, Chris, just echoing what you were

20:53

saying, it was

20:55

also clear to me that that passion

20:57

and the like desire for new discoveries

20:59

and that came

21:01

through in a really infectious

21:04

and beautiful way for someone

21:06

like us who've been kind of watching the Linux

21:08

landscape for a while, it made me kind of

21:10

feel like, oh, actually, things

21:12

aren't stale around here at all. Like someone

21:14

who's new to Linux is

21:16

having a great time. And for me, that's

21:18

like, okay, we're, we're having some

21:21

successes here and we need to keep this energy

21:23

going because it feels really great.

21:25

And be other people are going to benefit from it, either

21:28

by discovering this project or having their

21:30

own path very similar to DHH here.

21:32

Yeah, that's all really good. You're right.

21:35

And I think when I when I

21:37

turn off part of my brain, I

21:39

had the same exact experience you did.

21:41

And I thought, this

21:44

is really nice right now. But

21:46

I couldn't help while I was using it worry about

21:48

a year down the road.

21:51

You know what I mean, Brent, like a

21:53

year down the road when maybe a repo

21:55

that has been added doesn't respond anymore, or

21:58

canonical has had to make some sort of kernel change. or

22:00

some sort of GNOME change and the GNOME

22:02

extensions that are pre-installed by the script get

22:04

broken. Did that cross your

22:06

mind? It was one of the first things

22:08

because, well, A, it's

22:11

kind of a two-step process. You got to install

22:13

the OS and then apply this on top. And

22:16

for me with my space internet being

22:18

out in the middle of nowhere, that took actually

22:20

quite a long time, like an hour for me

22:22

to go from start to finish in this process,

22:25

which was great because it

22:27

offered me the opportunity to see

22:29

what was happening. You get some

22:31

visibility into what Omacube is installing

22:33

and changing and setting up. And

22:36

yeah, you're totally right, Chris. There's something

22:38

like 10 PPAs that are getting added

22:41

for different projects, everything

22:43

from Spotify to

22:46

Neovim, but also a

22:48

lot of just straight up curl

22:50

and WGet commands to install some software,

22:53

which gets me

22:55

wondering, like, A, how is this system

22:57

getting updated in a way that's actually

23:00

quite friendly and going to work long-term?

23:02

But also, yeah, like you're saying, a

23:04

year down the road, what is this

23:06

going to look like? So I know

23:08

it's early days for

23:10

this project, but I'm hoping it can kind

23:12

of address some of those concerns. Yeah, we'll

23:14

see. I mean, a really active community could

23:17

stay on top of some of this stuff. But Wes, when I

23:19

was using this, I thought to myself, boys, I'm

23:21

going to break the seal on it, but I really felt this way. I

23:25

kept thinking, man, I wish instead

23:27

of a bash script, I wish this was like a

23:29

Nix module or a flake. And there it is. There

23:31

it is. Take a shot. I want

23:34

to do it. Get your drinks, boys. Cheers, gents.

23:36

But maybe I don't want

23:38

Zoom. Maybe I don't want

23:40

Zoom. It's like, I wish this was just something

23:42

I could edit. Here it is. Cheers, everybody. Thank

23:44

you. Thank you. Here we go. I

23:49

will say, I think maybe we'll have

23:52

more to say about that option that you're kind of

23:54

describing there. But it being just

23:56

a set of bash scripts has some negatives like

23:58

you're talking about, right? It's

24:00

very imperative. It's going through slowly

24:02

one by one, downloading

24:04

dev files, adding PBAs, installing a bunch

24:07

of packages, and not

24:09

even all the packages get installed in one apt thing because

24:11

there's a bunch of different commands so you keep having to

24:13

run through all the stuff that apt does every time. And

24:17

each piece doesn't really have knowledge of the other

24:19

components. You can't reference stuff. But

24:22

the flip side, I think, is

24:25

if you actually go look at the repo, one,

24:28

it's pretty well crafted. It's not just a

24:30

thrown together bash script that got pushed

24:32

up and never looked at again. Like,

24:35

as you're saying, right now there's excitement and there's

24:37

been a lot of maintenance and tuning and just

24:40

aesthetic tweaks even at the code level. But

24:43

it's also, it's not really like there's a whole system

24:45

to learn. There's a little bit of one, right? But

24:47

it's mostly just folders with bash scripts

24:49

in them. And then there's one main install script that

24:52

then goes and looks in the directory that has

24:54

all the other scripts. And it runs

24:56

all of those. And to

24:59

Brent's point, I think, yes,

25:02

it's a lot of wgets and curls and

25:05

PPAs and devs, but I think

25:07

a lot of those end up being kind of what you

25:09

would be doing manually anyway, right? If

25:11

you're just following the GitHub readme instructions for how

25:13

to add these things. And

25:16

it makes me think that on some

25:18

level, it's maybe less of a limitation of Omicube and

25:20

more of a limitation of the platform it's on. So

25:22

you kind of have to tease those apart a little

25:24

bit. But I think instead

25:26

of having to learn a whole system, one plus

25:28

could be you just clone this repo. And if you

25:31

don't want to install a bunch of stuff, you just

25:33

delete the folders out of its install folder. And if

25:35

you're comfortable with bash, you

25:37

can reasonably make changes to it, even if it's

25:40

not pretty. I see what you're saying is in

25:42

a way, because it's bash, it's actually more approachable.

25:44

Yeah, it's not pretty. It's not,

25:46

it could be brittle as you're talking

25:48

about. But there is

25:50

a layer of simplicity, a

25:53

certain kind of simplicity about it, which I can't appreciate.

25:56

Once this install script got

25:58

through, and I started looking at

26:00

it, around and seeing what's installed and how and

26:02

digging into the repo there

26:04

just to see how they were doing things. I

26:06

agree with you Wes, it's nicely done and easy

26:08

for someone who even isn't

26:10

that deep and vast just to understand.

26:13

But I kind

26:15

of realized that there are some technologies

26:17

that we at least on the show

26:19

here, but mostly our audience has

26:21

loved in the last couple of years that are

26:23

completely missing. Something like Flat Packs

26:25

is not mentioned at all. I'm not sure

26:27

if that was a conscious decision or just

26:30

someone who's new to Linux who doesn't know

26:33

about Flat Packs. It would solve a lot

26:35

of some of the problems

26:37

here with PPAs and updates for

26:40

some of the software like Zoom for

26:42

instance that's just installed literally

26:45

like a one-off package that's downloaded

26:47

from their website. So I

26:49

feel like there's an opportunity to grow

26:52

this project by learning some of

26:54

these modern ways of installing Linux

26:56

software. I think that is the

26:58

downside to the Amacube system overall

27:00

is and I don't mean this

27:02

is any kind of gatekeeping way

27:04

it's just they're new and

27:06

I don't think they know about Flat Packs

27:09

and I don't think they necessarily have experienced

27:11

what it's like when Ubuntu releases a new

27:13

version and GNOME releases a new version and

27:16

everything they've done has to be kind

27:18

of updated. Not redone but definitely tweaked

27:20

definitely changed maybe some things have to

27:23

be substituted and that's gonna be

27:25

an ongoing thing that's gonna be an ongoing problem

27:27

and like you said Flat Packs would

27:30

at least resolve some of the

27:32

underlying host OS dependencies so that would

27:34

give them multiple releases of support in

27:36

theory and also avoid

27:39

that whole PPA repo eventually goes

27:41

away. Anybody that's been using

27:43

Ubuntu since like you know the six series knows

27:45

that when you add something via

27:47

an apt repo or a PPA you know

27:49

it works generally for one release at most

27:52

for one release of Ubuntu at most and

27:54

then that's not gonna work after that and

27:56

it may even go 404 during that release

27:58

and I think that's just something gain after you've used

28:00

it for a while. But the folks

28:03

over there are pretty intelligent, and they could

28:05

probably pivot and tweak these things and change

28:07

pretty quickly, right? They're not married to any

28:09

one particular thing. Right. And if they are

28:11

actually, you know, deploying this in anger at

28:13

work, they're going to have to keep making

28:15

those updates. Yeah, a good point. You know

28:17

what, in a way, the more they use it at work, the

28:20

more likely we are as end users to see

28:22

this thing get iterated and developed and fixed. So

28:24

okay, so looking under the covers aside, I'm curious

28:26

what you guys think in terms of how

28:29

effectively is it accomplishing its goal? Because

28:31

thinking about like day job things, I

28:34

get the busy dev mentality, you know, you've

28:36

been you're maybe familiar with a proprietary platform.

28:38

I'm thinking of some of my past co

28:41

workers who were Linux users at work, you

28:43

know, they were given development Linux workstations, liked

28:46

Linux, but we're not necessarily enthusiasts, they

28:48

might not listen to Linux podcast, they

28:50

might not go on YouTube watching people,

28:52

you know, or r slash Unix porn

28:54

to check out crazy customized configurations. They

28:57

don't keep up with like wayland and how to get

28:59

things all working. And so each time have to solve

29:01

those problems. So I could really see, you know,

29:05

the the after effects of running all these scripts

29:08

being kind of great, because you don't if you

29:10

don't need to look under the covers and make

29:12

any changes, I think it does get you to

29:14

a pretty good web development workstation. That certainly feels

29:16

like one of its strengths is the strong

29:19

opinions. Because if you like those

29:21

opinions, then I think

29:24

this is a wonderful place to start, you know,

29:26

okay, maybe you have to tweak a couple things

29:28

for your own particular workflow. But

29:30

those strong opinions, I really

29:33

appreciate especially as someone like

29:35

DHH, who has a lot of

29:38

experience doing some of this type of work,

29:40

you know, building web

29:42

development friends and like that style

29:45

of work, I could see if you're

29:48

just like a junior coming into the

29:50

field or you're new to Linux and

29:53

you have similar workflows on another platform.

29:55

It's a wonderful thing

29:57

to come into someone's like predetermined

30:01

flow of how you should apply

30:05

similar solutions. So I could see

30:07

that being like, what

30:09

a dream. Because I remember a

30:11

time when I was forced to use Windows at

30:13

a small little tiny local food

30:16

co-op that I was working at and they were like, no,

30:18

no, none of this. I don't even know what Linux is.

30:20

And I literally spent a week trying to get Windows to

30:22

do the things I wanted to. And I could imagine

30:25

many people come to Linux and have the exact

30:27

same experience. So having someone who just says, here,

30:30

start here. I've set up everything like 90% of

30:32

what you need. Then

30:34

you could just tweak a little bit from

30:37

there as you see fit. That actually is

30:39

such a wonderful, wonderful gift. Yeah, that's the

30:41

target, right? That is, I think, exactly who

30:43

they're going for. It's somebody

30:45

who's a little fed up. Like we

30:47

mentioned, Notch is a little fed up. DHA's got

30:50

fed up. It's somebody who's a little

30:52

fed up but doesn't have the time. And

30:54

they just want somebody with some taste to just make a

30:56

few good choices. And they're just going to roll with it.

30:58

And they can tweak from there. And

31:00

as they put it, tailored upfront is what they call

31:02

it. It's not for

31:05

somebody who wants to choose the exact terminal

31:07

they're going to use. Or they're not going

31:09

to tweak every little thing, right? It's for

31:11

somebody who wants a pre-setup. Setup

31:14

kind of like cosmic might be. Or kind of like

31:16

some of the more tailored distros might be. But instead

31:18

of being from this origin

31:20

of for the new user who's

31:22

not really familiar with computers, it's

31:24

the starting line is, I'm building

31:26

this for software developers. I think

31:28

Neovim might be a nice microcosm

31:30

of this. I mean, I've been

31:32

using Neovim more lately. It's great.

31:35

And you really can turn it into a lovely

31:37

development environment. But if you're used to

31:39

something like VS Code, which is also included

31:41

with Omacube or JetBrains

31:43

products, it's a big lift to

31:45

get Neovim like halfway decent compared

31:48

to those things. So having a

31:50

working developer get that going with

31:52

admittedly a lot of help from

31:54

LazyVim, I think that can

31:56

cross the line from like, oh, Neovim's neat,

31:58

but I view it as a toy or a condition.

32:00

never work for me to like actually being able to

32:02

consider using it for real. In that

32:04

way, West, do you feel like this is

32:06

the Amaka say spirit at work here?

32:09

Oh yeah, definitely. I mean, you might not like

32:11

what the chef chooses for you, right? But, um,

32:14

it is a thoughtfully put together thing and we

32:16

don't, you know, uh, we get that

32:18

to some extent with Linux, but as you're saying,

32:20

Chris, right? On these big general purpose basis, like

32:22

Ubuntu that are trying to target a wide audience

32:25

and maybe, you know, uh,

32:27

not super technical audience at times. You

32:29

don't get the technical level of, um,

32:32

consideration of holistic approach, um, to the Gestalt of

32:34

like the entire experience. And you get that a

32:36

little bit with all my QP, which is, which

32:38

is unique. Yeah. And it is built on top

32:41

of an LTS. So it's going to be around

32:43

for a while. And I think that makes a

32:45

lot of sense for a developer workstation. I

32:48

think, you know, when we talk about the shifting sands

32:50

that are Ubuntu and GNOME extensions, I think you have

32:52

to keep in mind that we are talking about an

32:54

LTS here, so it's a little bit better, but say

32:57

37 signals were to hire the Linux unplugged

32:59

consulting group. I think all

33:02

three of us are

33:04

number one, but a fit feedback would have been this path

33:07

does ultimately, ultimately lead to some kind

33:09

of anger. You know, you will frustration

33:11

problems. You will find that. And

33:13

now it is what the question that you are

33:15

going to have to ask yourself is. How

33:18

much are you willing to battle that? How much are

33:21

you willing to just constantly solve

33:23

for new problems that are created by the

33:25

upstream stuff that you're building on top of?

33:28

And we have seen this play

33:30

out over and over and over

33:32

again. Linux Mint is essentially this

33:34

problem. The cosmic

33:36

desktop is essentially

33:38

this problem. Matei is

33:41

essentially this problem, right? I mean, I could

33:43

go on and on. We

33:45

have seen this over and over again. So

33:49

that is my, that would be the only big red flag is you

33:52

are setting off on a journey in which you

33:54

will have to constantly account

33:56

for the upstream changes. So

33:58

there's that, but I think if you're. willing to take that

34:00

on. When I look

34:02

at the overall implementation of what's been done here,

34:05

the aesthetic tweaks are really my favorite changes. I

34:07

think there's a lot of taste that's gone into

34:10

the look. The modifications to GNOME

34:12

are nice. Alacrity works really well. The font

34:14

choice is really good. All

34:16

of that, I think, is really nice. The

34:18

software selection, overall I'm

34:20

a little mediocre on, but I think the aesthetics

34:22

are really good. But for me, it's

34:24

the idea. That's what I'm the most excited about. DHH

34:27

has built a Linux desktop for the actual

34:29

user base, the next wave of users. It

34:31

does make me think, I'm kind of glad

34:33

I saw some commentary around, you know, should

34:35

this be like a whole custom distribution? And

34:37

I think I'm thankful that it's not, you

34:40

know? It can accomplish these same goals,

34:42

but without having to be

34:44

an entirely new thing, it

34:47

can do so as a layer on top. But I think one

34:49

thing to think about in this way is, what

34:52

if this could be applied to more than

34:54

just Ubuntu? Like, what if you want a

34:56

different base? How do you accomplish that? And

34:59

is that a missed opportunity? Well, that is really the

35:01

elephant in the room, isn't it? Okay,

35:04

so this is the dedicated Nix. If we could

35:06

just go into the Nix universe for a moment.

35:08

Cone of science. All

35:15

right, boys, grab your drink because this is the one

35:17

mandatory shot for this segment. No, you don't have to

35:19

do more than this, but you do have what we

35:21

have to take one mandatory shot for the next segment.

35:25

Cheers, guys. All right.

35:31

What if this had been done via Nix

35:33

West? Question we've all been waiting to ask.

35:36

I wonder, you know, I mean, we've spent a

35:38

lot of the last year, two years, I don't know

35:40

how long now, learning the power

35:42

and advantage of Nix. And I think

35:45

just upfront, you know, it is a

35:47

powerful package manager with a

35:49

wide selection of available packages already

35:51

right out of the gate in

35:54

a way that feels a lot more sustainable, maybe

35:56

than a bunch of

35:58

devs downloaded from the internet. Plus,

36:00

you also get that Nix kind of reifies

36:02

your config to a new layer, right? So

36:04

instead of having to like fork his script

36:07

at the repo level, you

36:09

could import the flake that had his Nix

36:11

config or home manager config and then just

36:13

make the tweaks you wanted on top of

36:15

it in a sort of immutable,

36:17

accretive manner instead of having to actually go

36:19

blow away files in the repo and maintain

36:22

your own version. Yeah, and they

36:24

could also make those changes. You know, internally at

36:26

37signals, it would be a lot simpler for them

36:28

to swap certain things out or make those changes

36:30

if upstream demands it. And I

36:33

think it's important to clarify here, we're talking about

36:35

Nix on Ubuntu. So you could keep

36:37

that Ubuntu base, but still use

36:39

Nix to orchestrate so much of this. Yeah,

36:42

I think we should be clear about that

36:44

because it's easy to get confused between Nix

36:46

and Nix OS. And while Nix OS might

36:48

be great, and could probably be workable

36:50

in this situation, we're not saying it necessarily needs to

36:52

be. I mean, it could be really nice. We all

36:54

know about how Nix OS is great. But

36:58

you know, Nix has advantages beyond just Nix OS.

37:00

If you don't want to go full declarative system,

37:02

or you just have too many use cases that

37:04

aren't currently a good fit for Nix OS, you

37:07

can still get a lot of the advantages of Nix. And

37:09

I think one of those huge ones is

37:11

portability. It might be

37:13

a lot to learn to package something to Nix.

37:15

But one, it's also not

37:18

a ton of fun packaging stuff for regular Linux

37:20

distros. I've written more Nix packages

37:22

than I ever have, you know, Deb or RPM files

37:24

at this point. And

37:26

once you've gotten it packaged in Nix,

37:28

because Nix brings its whole own user

37:30

land, you can take that with you

37:33

anywhere you go, at whatever other distro, as long

37:35

as it supports Nix. You

37:37

don't have to redo it, you don't have

37:39

to change out which packages get installed. It's

37:42

the same consistent system. That is really powerful.

37:44

And it means too, that it would be simple,

37:46

it'd be a simple matter for say, an

37:49

internal team, another company, not

37:52

37 signals to just take it, fork it,

37:55

replace Zoom with Teams or whatever their

37:57

tweaks would be, their modifications. I

37:59

don't want to. call it tweaks because Amacube is

38:01

specifically being made for people that don't want

38:03

to tweak their system. What

38:05

I'm talking about is sustainability over

38:07

time because the one thing about

38:09

the free software universe is things

38:11

change consistently. Like on the

38:14

Mac platform, Apple will

38:16

keep apps around and just neglect them for

38:18

a long time but the Apple stay around

38:20

and maybe the API stays the same. That

38:23

is not necessarily the case in Linux desktop.

38:25

So you need kind of this multi-year strategy

38:27

where you can swap components out, change

38:29

things as you need because there's always going

38:31

to be another alternative but you're

38:34

going to have to modify what you've built to

38:36

accommodate that. And it's going to be

38:38

true for your internal teams, it's going to be true

38:40

for everybody using it and it's going to be a

38:42

constant source of nagging external people using

38:44

it to the project. Where

38:46

if you brought it in with like a

38:49

Nix module or a flake, it

38:51

would be something that is a matter of just going

38:53

in and tweaking a few

38:55

lines and then it's

38:57

theirs and it doesn't require much more than

38:59

that. But on top of that, it's

39:01

like Wes said earlier, it's going to get built every single

39:03

time so it's going to get validated, it's going to get

39:05

checked and it's going to be portable. So you could

39:08

also do it on a different system, say should

39:10

Ubuntu not be the base that you want

39:12

to use five, six years from now. It

39:14

feels to me also like Nix

39:16

doesn't have to be obvious

39:19

to the user here either. Like

39:21

for those of us who want to maybe

39:23

customize this before we get going, maybe we

39:26

have our own group of people we want

39:28

to apply this to, yeah, okay, maybe you

39:30

dive into it. But same as the Bash

39:32

script, it can just be like a one-off

39:34

run that handles all of this. At

39:37

least that's how I imagine it, is that how you've

39:39

seen it, Wes? I mean, I think there's

39:41

a lot of ways, there's a lot of flexibility. So it does need,

39:45

it would need the same level of curation I

39:47

think or maybe more and we should be upfront

39:49

that some problems would

39:51

need to be solved, right? Like having the

39:53

OmaCube sort of like interactive thing where you

39:55

can go and tweak the themes right there,

39:57

that might be a really nice experience for

39:59

folks versus... yeah, having to go like figure

40:01

out how flakes work and learn the next

40:03

expression language. But the technology under

40:05

the hood, having those portable

40:07

apps, having a programmatic

40:09

interface to it, I think it would, you know,

40:12

it has the bones that would let you build

40:14

that if you want. And we've seen stuff, right?

40:16

This is kind of a similar problem. In some

40:18

extent that the folks at Fox or

40:20

dev end or toolbox, there's a

40:23

ton of different projects that

40:25

are kind of trying to address this. I guess

40:28

we'll see which one wins. Here's why I would

40:31

prefer this setup. Ultimately,

40:33

the number one thing that kind

40:35

of gets me about Amacube and

40:37

using Ubuntu in general as a

40:39

development workstation is

40:41

that at my core, I really,

40:43

whenever possible, believe that applications, user

40:45

data, and the operating system should

40:48

all be separated. And

40:50

I'm not a big fan of what I

40:52

this is, this is my opinion, I'm not

40:54

a big fan of what I call spraying

40:57

the file system and modifying everything around the

40:59

whole OS because now you've just basically created

41:02

your own boutique bespoke Linux

41:05

installation. And

41:07

I just I find a lot

41:09

more sanity when everything is properly

41:11

isolated and separated out. And

41:14

I feel like it's kind of funny because

41:17

Mac OS is just kind of semi recently

41:19

solved this very problem. And

41:22

DHH is leaving Mac OS. But Mac

41:24

OS has worked for several releases in

41:26

a row to separate out user data

41:28

applications, the system files to switch to

41:30

image based updates. And now

41:32

we're kind of going back to more of a

41:34

90s style where it's a spray and pray approach

41:36

to updating your system and installing packages. And I'm

41:38

not a big fan of that. And that's also

41:40

something I feel like using the Nix package manager,

41:42

be it on Ubuntu, be it on Fedora, be

41:45

it on whatever, would be a sort

41:47

of level of separation from the host OS, which

41:49

could be a more minimal set of packages. I've

41:51

been pleasantly surprised by how well that can work

41:53

too. I was just playing

41:55

with my Omicube setup and I was bringing in a bunch

41:58

of 24.4 already has pipeline of course, but I was trying

42:00

to get a little audio environment going and I was able

42:02

to bring my own pipe wire

42:04

and wire plumber, pipe wire

42:06

pulse and Reaper and a

42:08

bunch of other tools all on top of this Ubuntu

42:10

24.04 base but I

42:13

got newer versions. The

42:15

ones there on the system are there if I need to fall back or I'm

42:17

not trying to do pro level audio kind

42:19

of things but I

42:22

just have a whole separate base that I can bring

42:24

with me to whatever platform I need. And I think

42:26

you could, you do need, there are some things where

42:28

you need to solve having

42:30

the Nix world talk to the non-Nix world or

42:32

vice versa but those

42:34

are solvable, especially maybe if you've

42:36

got the kind of energy going into Omakube right now. But

42:39

and especially so when you're not on Nix OS, some of

42:41

those things just work. Like if you install VS code from

42:44

Nix but

42:46

you're running it on Ubuntu, you don't have all of

42:49

the same complications you have running VS code on

42:52

Nix OS. There's a little more ability of it to actually

42:54

reach in and go to all the usual

42:56

places on the file system that's gonna look for stuff. So

42:59

some of those problems get ameliorated just by

43:01

not being on Nix OS as a base.

43:03

Yeah, yeah. So this topic

43:05

using ARCH, using Nix, it

43:07

was actually brought up by DHH in

43:09

one of the podcasts of the videos

43:11

that he did. So I thought I'd

43:13

play his comments on why they didn't

43:15

choose Nix. I've really designed Omakube first

43:17

of all for myself. I wanted a

43:19

way to recreate my exact setup on

43:21

GNOME, on Ubuntu. I wasn't looking to

43:23

use Nix OS. I wasn't using to

43:25

use ARCH. I wasn't using to use any of the other, let's

43:28

say more exotic, more niche compilations of

43:30

way to run Linux. They're all great.

43:32

And I wish nothing but all the

43:34

best for people who wanna dive into

43:36

those very deep pools. But Omakube is

43:38

for a different kind of user. Someone

43:40

who's probably been using a Mac or

43:42

Windows machine and isn't

43:45

necessarily a total wizard with

43:47

Linux. Now I get this

43:49

and I understand this. And what I hear in

43:52

there though is what Wes was touching on earlier

43:54

is this conflation between Nix OS

43:57

and Nix the package manager, which works.

43:59

on Mac OS, which works on all

44:01

the different Linux flavors. And

44:03

you know, as part of this, you wouldn't have to do

44:06

everything in Nix. Like this could maybe be like a, you

44:08

know, like a home manager config that did like kind of

44:10

everything from a top layer. But

44:12

you could also just sort of augment stuff. Maybe you still

44:14

want to install a couple of things with dev files or

44:16

from flat packs. Ideally, that'd be a little more portable. And

44:19

then some stuff, you know, the stuff that works well, you

44:21

bring in from Nix and other stuff maybe you still have

44:23

to fall back to the stuff from the host platform or

44:25

a container. It

44:27

doesn't have to be a one way

44:29

or the other. It can complement nicely. Linux

44:35

unplugged.com/ membership. And now

44:37

the promo code summer will get $1 a

44:40

month off your membership forever.

44:43

Forever that's valid for both the Jupiter

44:45

signal network membership and the core contributor

44:48

membership. When you sign up,

44:50

you get two options. There is two

44:52

choices before you. One

44:54

is the total bootleg version, raw recording.

44:56

We have a bunch of extra stuff

44:58

in the pre and post show stuff

45:00

that just doesn't fit in the show.

45:03

Like if we put all this stuff in main, main, love

45:05

would be two hours long. It would be too long. It'd

45:07

just be too big, too big, but we

45:09

can't help ourselves. We give that to the

45:11

members in the bootleg version, but

45:13

a lot of you, your time constraint, hence the

45:15

reason why we can't make love so big, the

45:17

main show we, for you, for you, we have

45:19

the ad free version. It's got all of Drew's

45:21

fine touches post production, but it's even just a

45:23

little bit shorter because the ads have been cut

45:25

out for you. So check

45:27

it out. Two options for our members.

45:29

You get started at Linux unplugged.com/membership and

45:32

use that promo code summer to

45:34

take $1 a month off forever.

45:36

That's Linux unplugged.com/membership. And

45:40

now it is time for the

45:42

boost. Well lucky us. We got

45:44

a couple of live boosts this episode so far.

45:47

Here's one from Max VDM for 5,000 sats about

45:49

20 minutes ago. Heya

45:52

from Johannesburg, South Africa. Finally

45:55

able to catch a live show. Hey,

45:58

hello, South Africa. That's

46:00

pretty great. Thank you for listening

46:02

live. Max VDM also came in

46:04

just to say, Hey, Nick's OS,

46:06

drink up fellas. Okay. It's catching

46:08

on. Right off the

46:10

top. We got a drink right off the

46:12

top, boys. Okay, here we go. This is

46:14

the one Nick's OS mentioned shot for the

46:16

boost segment. Here we go. Cheers

46:20

to you, Max. Thanks for listening. Oh,

46:24

all right. Bobby Pin comes in with

46:26

50,000 sats. And guess what? He

46:28

is our lobster. It's

46:30

your lifestyle. Bobby

46:34

says, I finally got my Albie Sats transferred

46:36

to Fountain. I can't

46:38

believe how easy it was this whole time. Just

46:40

barely hopping on the crypto train after listening to

46:42

you sing his praises since 2014. Keep

46:45

up the good work. Thank you, Bobby. Yeah,

46:47

two things there. Number one, you

46:50

could think of the Lightning Network as as SMTP.

46:53

You know, we needed that to build out over time. And

46:56

once it's set up, it's just a matter of sending

46:58

messages between systems. It's pretty straightforward, but it just had

47:00

to get built out. And

47:03

then remember, Bitcoin, not necessarily

47:05

crypto. Bitcoin is the

47:07

only digital currency that doesn't

47:09

have an active founder, that doesn't have a pre-mine,

47:12

that doesn't have a team organizing it, that has

47:14

a Linux foundation type structure, that has a dev

47:17

team that is large and also not the only

47:19

ones in control because there's node operators and miners

47:21

as well. And it separates it out

47:23

from the rest of the pack. But just

47:25

because there's no second best doesn't mean I don't appreciate your

47:27

boost. Thank you, Bobby, for that 50,000 sats. All

47:30

right. Well, we've got a special chain of

47:32

boosts from one max power. It's 49,380 sats,

47:35

but it's across four boosts. And

47:39

I think we better do these individually. The

47:41

first one for 12,345 sats. So

47:46

the combination is one,

47:48

two, three, four, five. This

47:50

first boost just says spaceballs and

47:52

then another 12,345 sats. Yes,

47:56

that's amazing. I've got the same combination on my

47:58

luggage. To say. Boosts! And

48:01

another 1, 2, 3, 4, 5. The

48:04

hell was that? Spaceball 1! They've

48:07

gone to plaid! To

48:09

say must! And finally... 1, 2, 3, 4, 5. Smoke

48:14

if you got him! Stay. Spaceballs

48:16

boosts must stay. I

48:19

don't know you guys, I feel like there's a message in there. You

48:21

guys think there's a message in there? I can't

48:23

quite pick it up but I know there's something. Pretty

48:25

convincing if you ask me. Seems like

48:27

a strong vote. I agree. Caden came

48:29

in with 40,243 satoshis from Fountain. I

48:35

hoard that with your kind covered. I love

48:37

the show on the software dev at a

48:40

.net shop but I use an

48:42

Ubuntu VM and Neovim predominantly. Looking

48:45

to add Docker and Nix to that tool belt.

48:48

Do you have any suggestions? Okay,

48:51

let's pause right there. You

48:54

know what I didn't even think about with Amacube? How

48:56

perfect is it for people that are just using Ubuntu

48:58

and a dev VM to make a nice little dev

49:00

VM? Like that, I didn't even think about that. That

49:03

is a great use case. But then also, I love

49:06

that he's thinking about integrating Nix into the toolset.

49:09

That's a brilliant idea. Do

49:11

we have any suggestions? Wes Payne, do you

49:13

got any suggestions? Yeah, I mean I suppose

49:15

I would say go

49:17

check out all the packages available. Nix

49:20

is a great way to very lightweight

49:22

install stuff to your system. You

49:24

can remove it really easily. It doesn't leave a lot

49:26

of cruft because it's all under slash Nix slash store

49:28

and then Sim links to that. So

49:31

as you're setting up your dev environment, take a

49:33

look at what's in the Nix package database. Search.NixOS.org

49:35

is a great way to do that. And

49:38

try installing some of the regular tools you use

49:40

from there. Stuff like, I don't

49:43

know, JQ, RIPGRAP, SemGRAP.

49:45

Any of these kind of like standalone

49:47

things that maybe don't need complicated

49:49

library access or to like super

49:51

integrate at a language level into

49:53

your setup and go from there. Also

49:56

maybe check out DevEnd. I've

49:58

been playing with that a little bit more. I think

50:01

it's from the folks behind Kashix, which

50:03

is a Nix

50:05

cache, but it's fast, declarative, reproducible, and composable

50:07

development environments using Nix. I've had a pretty

50:09

decent experience for that. And then there's also

50:11

just kind of several different versions of dev

50:14

shells you can use, which is a nice

50:16

way to pull a bunch

50:18

of packages from Nix with

50:20

a little configuration, maybe set up environment variables or

50:22

have stuff that runs when you enter the shell,

50:24

that kind of thing. You can

50:26

kind of start light, add in tools as you want,

50:29

and get used to maybe writing a

50:31

flake and kind of reading the Nix

50:33

expression language. Now, Kaden does continue. Hey,

50:35

I recently flashed a laptop with Pop

50:37

OS, but every time the

50:40

battery dies in the laptop, secure boot

50:42

turns back on and I'm locked out

50:44

of my OS. Any

50:46

ideas why or how to fix this? Man,

50:48

I've never heard of that. I'm sorry. That

50:51

doesn't sound fun in any case. No, no.

50:54

Yeah, I can't. And we can put this

50:56

one out there to the audience. Help

50:58

us out, audience. Does this happen to you? Do

51:01

you have any tips for Kaden? And the last little tidbit

51:03

here is PS. This

51:05

is a zip code boost. Oh, no. Wes

51:07

has already got the map out. All right. Wow.

51:11

Wow, Wes. Do you bring that

51:13

with you everywhere you go? Yeah, I had a premonition this was

51:15

happening. I got the big map this time. Okay.

51:18

This is a postal code, I think, in

51:21

Jefferson County, Kentucky with cities

51:23

like Louisville, Middleton and Douglas

51:25

Hills. Hello, Jefferson

51:27

County. Thank you for being here. Hello,

51:30

Kentucky. Appreciate that. Not

51:33

the one comes in with 20,000 sats. Perhaps

51:36

not possible. Nothing can do that.

51:38

He says I like the sound effects. If we

51:40

didn't have them, we wouldn't know how much sats

51:43

to send. Also, I play things at one speed.

51:45

If it was good enough for the Romans, it's

51:47

good enough for me. When

51:52

you do a Babylon 5 sound effect, here's

51:54

some quotes. Ah, arrogance and

51:56

stupidity all in the same package.

51:59

How efficient of you. And

52:01

quote, the avalanche has started. It's too late

52:03

for the plebs to vote. Wow,

52:05

I need some time codes. I'm not a

52:07

big Babylon guy yet. I am just midway

52:10

into season two, so I will start

52:12

listening. Maybe I'll find one. 4.12,

52:15

Linux boosts in with 2,000 cents. Pee-pew!

52:18

My Linux mistake is not being patient

52:20

enough when using a new desktop environment,

52:23

leaving DE the first time it gets frustrating.

52:26

I stuck with Mate and I'm very

52:28

happy. I've got that muscle

52:30

and visual memory now. So be

52:32

patient with yourself and be

52:34

patient with the desktop environment. P.S.

52:37

boosting in while on a walk, while listening

52:39

live, so awesome. Coming in hot

52:41

with the boost. That is good for you being

52:43

out on the walk while listening in. I also

52:45

like that about the audio stream. You can plug

52:47

jblive.fm into your browser and

52:49

listen live while you're on a walk, or if you've

52:52

got a podcasting 2.0 app, we are live in the

52:54

podcasting 2.0 apps. Now, that's a

52:56

good kind of moral of

52:59

the story right there, I guess, right? Be patient with yourself.

53:02

Take time to learn the new desktop environment. Take

53:05

it off in bits and pieces. Learn one little piece

53:07

at a time. It applies on a lot of levels,

53:09

too. It applies to the

53:12

desktop environment. It applies to Linux

53:14

as a whole system. It applies to a

53:16

new editor or new tool you're adopting. Yeah,

53:18

it really does take time to get to

53:20

that level of comfort. Now, WAM

53:23

Geek came in with almost 12,000, 11,949

53:25

satoshis. Pew,

53:29

pew, pew. Hey, guys, I've been

53:31

a long time listener all the way back to

53:33

Linux Action Show days. This is my first time

53:35

boosting, so I'm hoping I'm doing this right. One

53:38

mistake I learned quickly to avoid is

53:40

to make sure to unplug my external

53:43

hard drive with the backup on it

53:45

before doing an installation, or

53:47

else you may find that you've installed the OS

53:50

on the external hard drive and have no more

53:52

backups. Oh. This

53:55

I learned, someone told me to

53:57

do this way early in my

53:59

computing career. and I have

54:02

stuck to it religiously. I will

54:05

report. It works every time if you just happen

54:07

to do it. So

54:09

I can advocate for

54:11

this one completely. Oh, and by the

54:13

way, that's a zip code boost. Ow!

54:16

I gave myself a paper cut on this one. But

54:19

I did get the results because this is a

54:22

postal code in Suffolk County,

54:24

New York with cities like

54:26

Manorville, Eastport, or Northampton. Oh,

54:29

that's cool. I was hoping for a Schenectady.

54:31

It's been a minute since we've had a

54:33

zip code boost

54:35

from the East Coast. Hello. You know what? I

54:37

was just gonna say I would love some more

54:39

zip code boosts and now we've had two. I

54:42

really, really like these. Thank you very much, Wham

54:44

Geek, and hello, New York. Magnolia

54:46

Mayhem comes in with 15,678 sats. Boost! And it's

54:48

actually also a space

54:53

balls boost, the first one. So the combination

54:55

is one, two, three, four,

54:57

five. Because I can't wait to hear about

55:00

your backwoods setup. I spend my weekdays on

55:02

a chicken farm and my weekends as a

55:04

rural carrier. So I'm almost always in a

55:06

bad connection setup. Yeah.

55:11

So. How's it going? Well,

55:13

it's pretty good except for the trees have

55:16

grown in quite a bit and the bush

55:18

has kind of precluded my

55:20

Northwest view. So I

55:22

am dropping packets. Let's see. I've

55:24

dropped 1,600 packets

55:27

to the studio. I've dropped 12,000 packets to

55:29

Brent and I've dropped 600 packets to Wes.

55:35

So. You didn't need

55:38

those packets, right? So

55:41

it's not great. So if you want to use Starlink,

55:43

you do need to make sure you have a good

55:45

clear shot of the Northwesternly sky,

55:47

but really the whole sky. Now, the nice thing is

55:49

that they do have an app you can download and

55:51

you can do a little survey and

55:53

it'll give you a pretty good idea how you're going to do now.

55:58

That aside. amazing

56:00

what you can accomplish with say

56:02

six, seven, 800 amp hours of

56:04

lithium battery power and solar and

56:08

maybe a generator when you need it. It

56:10

is incredible. I've been out here since Wednesday

56:13

and the weather has been great. We've had really

56:15

good solar. So we start producing two, 300 Watts

56:18

of electricity by about 738 AM and by

56:20

about noon I'm making 800 Watts of

56:25

electricity. Just free power, unlimited free

56:27

power. Now where we're parked,

56:29

we're kind of intentionally in the shade.

56:31

So about one, two o'clock when it's

56:33

really, really good solar, we

56:36

end up in the shade and it all drops off.

56:38

So I am supplementing with generator a little bit, but

56:40

it's been so nice out here and

56:43

it's so quiet. It's so rare where

56:45

I'm somewhere on location where I can

56:47

have all the windows open. I have

56:49

the front door open and

56:52

it's quiet. There's nobody here.

56:54

I haven't seen anybody since Wednesday except

56:56

for the family. So starlink, a

56:58

little bit of lithium power and inverter to

57:00

make it work. It's

57:02

been really nice. And then for the mobility aspect, because

57:05

I am in an RV, I have everything kind of

57:08

on a visa mount and that, you know, just

57:10

different arms and visa mounts is really the way

57:12

to go. It really is because I can just

57:14

take down things in chunks and

57:16

put them away and then I can set back up. So

57:18

that's been really great and it's

57:21

really kind of nice. We'll see how it turns

57:23

out. I have two coder radios and a self

57:25

hosted to record out here and this week in

57:27

Bitcoin. So I still have quite a few more

57:29

shows to record. We'll see how they turn out.

57:32

And then he finishes with, does squid still

57:34

have a place in the modern world? That's

57:37

the last part of his boost. Does squid,

57:39

the proxy, still have a place in the

57:41

modern world? I guess I'd

57:43

flip that around, boys. Why wouldn't it? Oh, when don't

57:45

you need a little caching? Well, you know,

57:48

that's, I mean, that's a good question. But when was the

57:50

last time you actually deployed it? I've

57:52

thought about deploying it here at the house or in the

57:54

RV over star link or over cellular. Cause you know, we

57:56

kind of swapped back and forth. So

57:58

I have actually given it real. If

58:00

my piehole had an SSD attached

58:02

to it, I think I'd consider trying

58:05

to put Squid proxy on it somehow. Because

58:08

what it does is it's essentially a browser cache for

58:10

all your machines at the network level. So

58:13

the first time you go to google.com

58:15

or the first time you go to

58:17

jupyterbroadcasting.com on one of your machines, the

58:20

Squid cache will cache all of that

58:22

locally. So the next time any other

58:24

machine goes to Jupiter Broadcasting or Google

58:26

or MSNBC or whatever it is, you'll

58:28

get the images loaded, ideally those that

58:31

can be, that haven't changed, from your

58:33

local cache instead of from

58:35

the remote server. So it just takes one

58:37

system on the entire land to access it

58:39

once, cache that stuff on the Squid proxy

58:41

server, and then every machine from that point

58:43

forward will load that off of your local

58:45

cache instead of off of the internet. And

58:47

if you think about an LTE connection or

58:49

a space internet connection, it just seems kind

58:51

of like a good idea to me. But

58:54

I've never really gotten around to it. But I still

58:56

think it does have, in my opinion, I think it

58:58

has a place. Maybe some boosters can boost in and

59:00

let us know. Anyone out there making good use of

59:02

Squid? I'd be curious to hear about it. Great

59:04

question. Are Palgene being boosted with 11,249

59:07

sets across six boosts? Make

59:11

it show. A couple rows of ducks

59:13

here. First one to say, please do keep us

59:15

updated on the Nix community stuff as I just

59:18

don't have the time to read about it all

59:20

myself. All right, we will do. And

59:22

a second row of ducks here to say my five year

59:24

old son is listening with me and asked,

59:27

why is the show named Linux

59:29

Unplugged? And well, I

59:31

told them I'd ask you. So why? Why

59:33

indeed? Why are

59:36

so many things? You

59:38

know, it originally started. This is I'll give the

59:41

short version of the story because I've told it

59:43

many times. It originally started as a podcast that

59:45

was just going to cover the feedback that

59:48

came into our intensely popular show, Linux Action

59:50

Show. And the reality was

59:52

is we were getting so much. And I was new

59:54

to podcasting, I guess, in retrospect. And I just thought,

59:57

well, this is just going to be a one time

59:59

problem. And we had so much feedback coming in that

1:00:02

I needed to cover it somewhere. And I couldn't cover it all in Linux

1:00:04

action show. So we covered. We, I

1:00:06

thought, well, how about we'll cover it in the Linux action

1:00:09

show feedback program or something like that. And we came up

1:00:11

with this idea and I just started doing it. And

1:00:14

then as we started doing Linux unplugged, we realized it

1:00:16

really had its own identity and the mumble room was

1:00:18

crucial to that, you know, bringing in the virtual lug.

1:00:20

And then things really turned when

1:00:22

West joined in episode 100 and it really became

1:00:25

its own podcast and it ran in parallel

1:00:27

for a short period of time with Linux

1:00:29

action show. And then when Linux

1:00:31

action show wrapped up, it became our main show. The idea

1:00:33

though, is it's mostly unscripted. You know,

1:00:36

we got the mumble room open. Anybody could pop

1:00:38

in and chat with us. And,

1:00:40

uh, we kind of, uh, try to keep

1:00:42

some of that original ethos, but also then

1:00:44

make it its own unique thing. And so

1:00:47

it's called Linux unplugged, you know what? And

1:00:49

then you look around and you, and

1:00:51

I didn't do this intentionally, but you'll see a lot

1:00:53

of things out there now are XYZ unplugged. There's a

1:00:55

lot of this. It's a, it's, it's

1:00:58

its whole kind of naming category

1:01:00

now is XYZ unplugged. You know,

1:01:02

um, even MTV copied you, right?

1:01:04

Yeah, yeah, right. Maybe that's maybe they

1:01:06

were the OG. That's a good point.

1:01:08

Well, Gene Bean continues with another row

1:01:10

of ducks. Um, regarding a distro for

1:01:12

new users, Pop OS is

1:01:15

hands down the answer. My

1:01:17

70 plus year old father has been happy

1:01:19

with it since January of 2022. I

1:01:23

agree. I really think Pop OS is one

1:01:25

to consider in part because it's backed by

1:01:27

a company. And if you think about what

1:01:29

traditional users want, you know,

1:01:31

they want something that is backed by a company. And ultimately if

1:01:33

they like Pop OS, they want to pop up, they want to

1:01:36

be able to go buy a system 76 machine

1:01:38

and they want to be able to call a support number.

1:01:41

Um, and if, you know, you're not trying

1:01:43

to do anything special with your system and

1:01:45

Ubuntu base is a really solid,

1:01:48

widely supported compatible base to start with.

1:01:51

Maybe we should do a Pop OS challenge. Oh,

1:01:53

maybe we should. Uh, perhaps,

1:01:55

uh, perhaps when the next cosmic evolution happens, huh? Yeah,

1:01:57

there you go. Okay. Yeah, I'd be down for that.

1:02:00

Now, Gene continues with some leet sets with

1:02:02

a little dig at you, Chris. Why

1:02:05

don't you use a flake for your system config,

1:02:07

huh? It's probably my fault

1:02:10

for not, you know, making you. Yeah,

1:02:12

I don't. Yeah. Yeah. If

1:02:15

Wes would have suggested it, I probably would have done it.

1:02:17

I don't think I considered it because it started as

1:02:20

I was taking a config from another system. And

1:02:23

then I just expanded that NixOS

1:02:25

configuration for my new B-Link

1:02:27

system that is the... system

1:02:30

I was planning to use for audio production. I'll get into that

1:02:32

more later. And

1:02:34

I didn't really ever stop from that point

1:02:36

forward. I just took that config file and

1:02:39

immediately started iterating on that. And that was

1:02:41

my line of thinking. But I go back

1:02:43

to if you're introducing yourself to Nix and

1:02:45

you just start with a flake first approach,

1:02:48

I actually think you'd be better off. And

1:02:50

I think ultimately this is where the community is going to

1:02:52

wind up. It's just going to take a while for us to

1:02:54

get the consensus there. And one little bit here from Mr. Bean,

1:02:57

1,024 sets to link us to a guide

1:02:59

for getting started with

1:03:02

Nix that he really liked called

1:03:05

Walkthrough of Nix Install and Set Up on

1:03:07

macOS by ZMRE over on YouTube. So check

1:03:09

that out if you're curious. We'll have it

1:03:11

in the show notes. One

1:03:14

more row of ducks just to say, bring

1:03:16

on those brunches, Brent. Well,

1:03:20

thank you for the vote of confidence. We

1:03:22

shall see. Now Tom's dad

1:03:24

did boost in for us this week. 9,001

1:03:26

satoshis. It's

1:03:28

over 9,000! Party

1:03:33

member here. A couple of things. Number

1:03:35

one, I'm interested in a camping meetup,

1:03:37

but would be making the trek

1:03:40

from Denver. So maybe somewhere in the middle. Also

1:03:43

the local SRE group doesn't open spaces

1:03:45

in wild spaces a couple of times

1:03:47

a year. So a link to that.

1:03:49

Wild spaces don't work. Also

1:03:52

in one of the pre-shows, you were talking about

1:03:55

cheap Android tablets. Good for home assistant

1:03:57

dashboards. Any recommendation? These are some great

1:03:59

questions. So on the camping meetup, there

1:04:01

is no meetup in my life. I

1:04:05

would rather do more than the camping meetup. I

1:04:08

mean, here's what I'm picturing is maybe just a

1:04:10

couple of nights. I'm picturing some

1:04:12

people in their RVs, some people tent

1:04:14

camping, some people nearby that just

1:04:16

come up during the day. And during the day,

1:04:18

we do food, we cook, then we do like

1:04:20

little sessions. So

1:04:23

if somebody's got a skill or a talent, we

1:04:26

do little sessions during the day. Then

1:04:28

maybe we go on a trip somewhere, like a

1:04:30

little caravan somewhere nearby, wherever we're camping at. Then

1:04:32

we end the night with a fire, you

1:04:35

know, telling some jokes and some stories. Then we go to bed

1:04:37

and we rinse and repeat one more day, and then we all

1:04:39

go our separate ways. But I can't

1:04:41

think of anywhere I could, to be honest

1:04:43

with you, afford to go outside of the Pacific Northwest.

1:04:46

Because this thing gets

1:04:48

10 miles to the gallon and it, you know, it

1:04:50

has an 80 gallon tank and the

1:04:52

fuel is extremely expensive. So

1:04:55

the only way I could figure doing it would be

1:04:57

somewhere in the Pacific Northwest. And that has cooled my

1:05:02

motivation just because I know that's so far for so many

1:05:04

of you. And what I

1:05:06

do think would be probably more doable for

1:05:09

the rest of the audience would be something

1:05:11

probably in the Denver area, something a little

1:05:13

more central, not way, way over here

1:05:15

on the west coast. And so I've

1:05:17

slowed my role, even though it's number one by

1:05:19

afar, the meetup I'd rather do. And

1:05:22

then if the boys could make it, like we'd do a show

1:05:24

there. Maybe we just need to

1:05:26

do it in Canada. That way it's far away

1:05:28

from everybody. Everybody. Wouldn't

1:05:33

it be great to do a podcast there and everybody who

1:05:35

comes in camps would be our live audience and we could

1:05:37

still live stream it. We'd bring the star link and I

1:05:40

just I am so into it.

1:05:42

I just don't think it's I think in order to actually

1:05:44

make it happen, I need to centralize it. And then about

1:05:46

10 months ahead of time, I need to either

1:05:48

find a sponsor or we go to the store. Or we

1:05:51

got to raise the boost to make it happen. And

1:05:53

I just I think we're too late in the process.

1:05:57

I don't know. Maybe we're not. But I feel like it.

1:05:59

I guess if we maybe. aimed for September or

1:06:02

maybe late August, maybe we could do it

1:06:04

still. I just, I don't know where

1:06:06

the gas money comes from. And then that's true for so many

1:06:08

people as well. That's the only

1:06:11

hiccup there. And, um, I

1:06:14

don't know if people, anybody has any advice or,

1:06:16

you know, is a, is a, is an organizer of

1:06:18

these kinds of events and has some suggestions, please let

1:06:20

me know, I'd love to, uh, to

1:06:23

figure it out. So, uh, I

1:06:25

did on March 30th, I purchased

1:06:27

at a, a octa-core eight gigs.

1:06:29

Ram 128 gigabytes of

1:06:31

storage, Android tablet, and

1:06:34

it's a 10.1 inch Android tablet. And

1:06:36

it was 75 bucks and now

1:06:38

it's 69 bucks on Amazon.

1:06:43

Um, it has gotten even cheaper. And

1:06:46

what I use this for is

1:06:48

a dedicated home assistant tablet. It's

1:06:50

just constantly displaying the home assistant

1:06:52

dashboard using the, um, gosh, what's

1:06:54

that? Uh, it's a, it's

1:06:57

a kiosk software that

1:06:59

I can't remember the name of. It's dedicated kiosk

1:07:01

software for Android. You can just download the APK inside,

1:07:03

load it. So you don't even need an app store.

1:07:06

And, uh, then I inside there load the dashboard

1:07:08

and it doesn't have a product name, it's just

1:07:11

on Amazon called tablet 10.1 inch Android 13 octa-core.

1:07:15

So I'll put a link in the show notes for it. And,

1:07:18

uh, 100% absolutely

1:07:20

solid, no buts at

1:07:23

all recommendation. If you're looking for a

1:07:25

dedicated dashboard in your home,

1:07:28

I don't think it's a very good tablet in

1:07:30

terms of performance. I mean, if you're just watching

1:07:32

video, it's probably fine. In fact, if it's, if

1:07:34

you're just looking for consumption, it's actually probably a

1:07:37

pretty good little tablet. I mean, we're talking $70

1:07:39

for a 10.1 inch tablet and

1:07:41

it is incredible as a dashboard. I

1:07:43

was just thinking last

1:07:45

night, how happy I am with that. Now

1:07:47

I've only had it since March 30th. Uh,

1:07:50

but I am very happy with that as

1:07:52

a purchase. The screen is beautiful. It's been

1:07:54

reliable. I can control the screen.

1:07:56

I can control the sleep stuff, the auto wake

1:07:58

stuff, all from home assistant. using

1:08:01

the fully kiosk browser. That's

1:08:03

the other app I use. I install

1:08:05

fully kiosk browser in fully

1:08:07

kiosk, which I pay for, you don't have to, but

1:08:10

I pay for. Then I get home assistant control. It's

1:08:13

incredible. Great question, thank you

1:08:15

for following up. I do like to follow up when I

1:08:17

can. Big recommendation, we'll put a link for

1:08:19

that in the show notes. 8565 sent us 13,000 SATs across

1:08:21

three boosts. Thank

1:08:26

you very much. Fun will now

1:08:28

commence. Number one, so

1:08:30

in a matter of two days, I

1:08:34

wiped out both systems and

1:08:36

had to rebuild both of my

1:08:38

systems. This is

1:08:40

now why I have a two-beer limit when

1:08:43

I'm doing computer stuff. Oh no,

1:08:46

but probably wise. Boost number two, I

1:08:48

made a huge mistake recently as well.

1:08:50

On a two-year-old Arch install, I was

1:08:53

SSH'd into my Bunty Jellyfin server and

1:08:55

I needed a drive to have 777

1:08:57

permissions for media. So

1:09:01

I grabbed a terminal and did a little chone. Except

1:09:04

the terminal I was in wasn't my SSH

1:09:06

terminal, it was the one I had just

1:09:08

used for an update on my local Arch

1:09:10

system. No. So I set

1:09:12

the entire file system to 777 and

1:09:16

exactly nothing was happy with that. Gosh, I'm

1:09:18

pretty sure I've done something similar. You just

1:09:20

get all the permissions and for the

1:09:22

most part it doesn't matter, but then

1:09:24

there's some specific permissions on your system that

1:09:27

really do matter. Now 8.5 continues. The

1:09:29

worst part was that once I figured

1:09:32

it out, I made the very same

1:09:34

mistake the next night, except on the

1:09:36

server this time. That sounds even worse,

1:09:38

oh my gosh. Oh. I'd

1:09:41

be curious, how did you recover 8.5, 6.5? Did

1:09:44

you have backups to go through? Did you have to

1:09:46

reset up the system? Did you have to try

1:09:49

to manually fix the permissions? What'd you do? Still

1:09:52

recovering perhaps. Any

1:09:56

suggestions on how to avoid this in the future? Try

1:10:00

and just be careful. You can make sure you

1:10:03

have clear banners on your servers for stuff. There's

1:10:05

a lot of neat apps to do that. And like in

1:10:08

your message of the day or in your bash prompt or

1:10:10

is it a such prompt or whatever to like make it

1:10:12

really clear which system you're on. Maybe

1:10:15

don't give yourself pseudo. I don't know. Don't

1:10:18

trust yourself. Now in

1:10:20

the last boost here, 8.5 says, Jellyfinn

1:10:24

also has a very good desktop client that

1:10:27

you can make point to VLC. It's

1:10:29

a super handy little client. I

1:10:31

use it in lieu of a web app. All

1:10:34

right. Yeah, that's in reference I think to

1:10:37

our app pick. Neat, you know, I don't know if I've

1:10:39

ever tried this but I'm seeing one over on their GitHub.

1:10:42

It's based on Jellyfinn, or based on

1:10:44

the Plex Media Player. I

1:10:46

guess, yeah, you can do VLC. It

1:10:48

also supports like has an embedded MPV

1:10:50

player, supports Windows, macOS and Linux. That's

1:10:52

great. Good. And I mean, I think

1:10:54

I knew that, but like it's good to actually like remember that.

1:10:57

Well, Leaky Canoe comes in with 10,000

1:10:59

cents. I've

1:11:01

been listening to JB for

1:11:03

four years now and

1:11:07

I'm making it my goal this month to tune

1:11:10

into LUP Live for the very first time. Any

1:11:13

tips, advice or software recommendations to get

1:11:15

the best experience when listening live? That's

1:11:17

a great question. Well, Boostmaster, I think

1:11:19

this is your question. Well,

1:11:21

you could start really easy. You could just use your

1:11:23

web browser and go to JBlive.fm. And

1:11:26

if we're live, you'll hear us live. And if

1:11:28

we're not live, you'll hear some reruns. And

1:11:31

that's probably just like the most like low tech way to

1:11:33

do it. Then the step

1:11:35

up is if you're on Android,

1:11:38

I really like RadioDroid as a

1:11:40

simple MP3 streaming application and you

1:11:42

can just throw JBlive.fm in

1:11:45

RadioDroid. If you're on iOS, I

1:11:47

really like broadcasts. It's a solid

1:11:49

little app and it'll sync also

1:11:51

your preferences across your iOS apps,

1:11:53

which is nice. And you can

1:11:55

plug JBlive.fm in there. But

1:11:57

if you're a podcasting 2.0 user. it

1:12:00

gets a lot better because we're actually

1:12:02

using all totally standard stuff to do

1:12:05

the live stream including the

1:12:07

podcasting and 2.0 live item spec. So

1:12:09

say you got fountain or podverse or

1:12:11

cast-o-matic something like that that supports the

1:12:13

live streams you'll actually see like

1:12:15

the day before you'll see our pending stream in

1:12:17

there with what we're gonna talk about the

1:12:20

title and when we're gonna go live and then

1:12:22

when we actually do go live we flip that

1:12:24

and all we're doing on our end is we're

1:12:26

just updating an XML file right we're just updating

1:12:29

the RSS feed the clients ingest that RSS feed

1:12:31

and they mark it as live and then you

1:12:33

just hit a button right there and say fountain

1:12:35

or whatever just starts playing the

1:12:37

stream and You can see the

1:12:40

description if you do boost you can boost in and it

1:12:42

will come in live and they'll show up in our Chat

1:12:44

room and we'll get it in the show. Oh, it's

1:12:47

it's so so so slick It's it's

1:12:49

such a nicer experience and like YouTube

1:12:51

live streams And

1:12:53

I'm so proud of what the podcasting to the community

1:12:56

and all the devs and everybody has created there So

1:12:58

if you do have like fountain or podverse or something

1:13:00

like that That's really the way to do it is

1:13:02

just subscribe to our regular old RSS feed and then

1:13:04

you just get it right there in The feed but

1:13:07

at the end of the day, it's just an ice

1:13:09

cast thing So like JBLive.fm and anything that supports an

1:13:12

ice cast mp3 stream like VLC MPV

1:13:15

It'll work just Chrome. Yeah, whatever. Yeah. Yeah

1:13:17

to add to that if you want to

1:13:19

take it just up even one more notch

1:13:21

There's always the mumble room that you can

1:13:24

join if you want to go, you know

1:13:26

All the way to live the ultimate experience

1:13:28

experience now I'll take this one thumbs comes

1:13:30

in and guys, I don't know if you're

1:13:32

familiar with this one. It's called a space

1:13:34

ball combination is one two

1:13:36

three four five Are

1:13:39

they right? I listen at one point

1:13:41

two five X. I've been debating increasing

1:13:43

so reasonable Okay,

1:13:46

so that way I don't keep falling

1:13:48

behind the member feeds are monsters and

1:13:51

that's fair that is true. That's true

1:13:53

Yeah, you guys sound well caffeinated at

1:13:55

that speed music is 5050 at

1:13:57

that speed and some tracks like the outro are pretty

1:13:59

bad But most of the

1:14:01

80s songs are great with a little extra speed.

1:14:04

Yeah, we do play some 80s songs in the members

1:14:06

feed. That is very true. Yeah, I think about that

1:14:08

when I listen to somebody else's show at higher speed

1:14:10

and the music sounds like garbage. And I think about

1:14:12

how much music we play in the members feed in

1:14:14

one. I just think. Thank

1:14:18

you, thumbs, for being willing to listen to it. Appreciate it.

1:14:20

Oppie 1984 comes in with 4000 cents. Hmm.

1:14:25

I had been a lifelong Windows

1:14:28

user and Windows 8 pushed me

1:14:30

to try Linux. I first

1:14:32

tried Ubuntu and hated it so much. I went

1:14:34

back to a Vista machine. Later,

1:14:36

I tried Zorin OS and was actually able

1:14:38

to ease into Linux with that. And

1:14:41

after a while, moved over to Mint and have been

1:14:43

happy with that ever since. Oh,

1:14:46

that's what I always recommend for those looking

1:14:48

to jump from Windows to Linux. It's just

1:14:50

close enough to the Windows experience that it's

1:14:52

easy for noobs to get comfortable and start

1:14:55

to learn. Very

1:14:57

fair, very fair. Mint, I think nails that

1:15:00

that is the MVP performance for Mint

1:15:02

is that kind of nailing that Windows

1:15:04

X bat really cinnamon. Yeah,

1:15:07

cinnamon is pretty great. With

1:15:09

10000 SaaS, Otterbrain sent us a little

1:15:11

boost. Now, thinking

1:15:13

about Chris's new audio machine, which

1:15:16

is the most cost effective or

1:15:18

environmentally friendly system, a single all

1:15:20

in one multitasker or

1:15:23

a set of dedicated task specific

1:15:25

machines? For

1:15:27

me, I'm thinking about writing and reading tasks, data analysis, graphics

1:15:31

like presentations or making figures for papers. And

1:15:33

then there's gaming, mostly indie co-op games. It's

1:15:36

a good question. And I will say

1:15:38

it's one I've been asking myself this week, because

1:15:40

very frustratingly, after

1:15:45

three weeks of thinking about it, worrying about it,

1:15:49

configuring different things, trying different setups, buying

1:15:51

gear, buying mounts, buying equipment. Yesterday, as

1:15:53

I was doing one final test before

1:15:55

we got going, my B-Link died. new

1:16:00

brand new beelink that I talked about recently. Wouldn't

1:16:03

power on. I powered it off to save battery because I'm

1:16:05

running off solar. And when I

1:16:07

went to turn it back on, it just would not power back

1:16:09

on. And I tried clearing the CMOS. There's a little pin you

1:16:11

can push in the front and hold it down for a bit.

1:16:13

I'll pull the power. Let it sit for 10, 15 minutes, plug

1:16:15

it back in. Didn't work. And

1:16:17

I'm going to do the whole RMA thing and

1:16:20

I'll, I'll give the complete story when I

1:16:22

know what the complete story is, but

1:16:24

it had crossed my mind that if I

1:16:26

had just a regular old tower PC, I

1:16:30

could just start swapping out individual components. I

1:16:32

could have another power supply. I could have

1:16:34

another disc. You know, the only

1:16:36

thing I could do is buy two beelinks and

1:16:38

then reset up one of those beelinks if something

1:16:40

like this happens, because it's all an integrated package.

1:16:43

And so when you think about it

1:16:45

from like an environmental sustainability standpoint, I

1:16:47

think the individual modules, while more gear

1:16:49

upfront, actually makes something last

1:16:52

longer in the overall usability, because my other option, what

1:16:54

am I going to do, right? I'm going to RMA

1:16:56

this and they're going to send me a new beelink.

1:16:58

Totally brand new, all new parts when it could be

1:17:00

one individual tiny component in this that has failed. So

1:17:03

it's been on my mind. That's a good question, Autobrain. Thank you

1:17:05

for the boost. It might, it might

1:17:07

matter too, if you're, you know, do you

1:17:09

need to do these things at the same

1:17:11

time and will the machine be struggling? I

1:17:14

think just from the hardware perspective, having one

1:17:16

machine probably works out better, but that's predicated

1:17:18

on you actually be able to do all

1:17:20

of those myriad tasks on

1:17:22

that machine. Obviously you get more

1:17:24

redundancy if you have multiple machines and you can offload things,

1:17:26

but if you can get by with just one, it might

1:17:29

work. Yeah. And we got

1:17:31

a row of ducks from Ford humor. A

1:17:34

great episode guys. I'm learning so much from

1:17:36

your tips and your mistakes. Please keep sharing.

1:17:38

Yes. Last episode, some of our

1:17:41

bigger mistakes with Linux. Thank you for humor.

1:17:43

Appreciate the boost. Fear guys balls comes in

1:17:45

with 3000 sets across two

1:17:47

boosts. First 2k sets

1:17:49

here catching up with episode 553. Um,

1:17:52

is the next node config you made available

1:17:55

for listeners to use the fountain show notes

1:17:57

didn't include any links from the show. And

1:18:00

then another thousand sats to say, the next

1:18:02

sound effect should be the Borg, resistance

1:18:05

is futile. That

1:18:07

is it. Very appropriate. That

1:18:09

is great. Yeah, I

1:18:12

think we fixed the fountain show notes, right, Wes, by

1:18:14

now publishing the HTML of the

1:18:16

entire show notes? Yeah, we did

1:18:18

have to move some things around in which

1:18:20

particular feed items had which particular version from

1:18:23

how our feed was doing it previously. I'm

1:18:25

not sure if that's been backboarded to all episodes yet.

1:18:27

We probably will. So

1:18:29

if you don't see it there, go to

1:18:32

jupyrobroadcasting.com. You can find all the links there

1:18:34

or Linux unplugged.com as well. Do you remember,

1:18:36

was there anything that we did substantially

1:18:39

different? I don't remember now, with our

1:18:41

node config versus just what the Nix

1:18:43

Bitcoin project does? And did

1:18:45

we publish it? No, not necessarily. I mean,

1:18:47

we started working on the

1:18:50

helipad flake, which is, I

1:18:52

can have a link to that. We haven't really used

1:18:54

it very much, but I have a link to that. I

1:18:57

think maybe once we get everything actually

1:18:59

deployed, because right now we started down

1:19:01

the Nix node path. And

1:19:03

then we had to go to a bunch

1:19:05

of conferences, and there's just been a bunch of other projects in

1:19:08

the way. So we haven't had a chance to return to it

1:19:10

for a while. So we haven't actually really used it in any

1:19:12

production sense. But I think we

1:19:15

could try to post the tweaks we do

1:19:17

make when we get there. Yeah, we will

1:19:19

pick that back up. Now, ambient

1:19:21

noise sent four boosts for a total of

1:19:23

15,720 SATs. Coming

1:19:26

in hot with the boost. And these are in

1:19:28

response to Linux Unplugged 565, the

1:19:31

mistakes that made us love Linux, if you remember

1:19:34

that episode. I'm a

1:19:36

gamer and got into Linux by

1:19:38

watching the LTT channel, specifically Emily's

1:19:40

Excellent getting into Linux,

1:19:42

PopOS, and Proton segments. Don't

1:19:45

get me wrong, Linus just doesn't

1:19:47

know much about Linux. Maybe

1:19:50

I'm an outlier. He continues,

1:19:52

please, no talk of

1:19:54

manually partitioning the hard drive for new

1:19:57

users. Automatic is fine

1:19:59

in PopOS. and mint. New users

1:20:01

remember don't scare them

1:20:03

away while they're still new. Also

1:20:06

gotta say plus one to the no dual boot. Most of

1:20:08

the time there will be

1:20:10

another Windows PC somewhere you'll have

1:20:12

to access for that edge

1:20:14

case. Dual boot will break at some point and

1:20:16

the users will just never commit

1:20:19

to Linux. Another one here please

1:20:21

don't recommend NixOS to new users.

1:20:23

I know it's the cool new

1:20:25

thing but it's not a good

1:20:27

idea for new users even a

1:20:29

new dev that's looking

1:20:31

at Linux for the very first time. Some

1:20:33

very driven people might make it but how

1:20:35

many would be scared away? It's just too

1:20:37

risky in my opinion. You know it occurs

1:20:39

to me that with a lot of these

1:20:41

we probably be more careful about how we

1:20:43

define new user. You

1:20:45

know there's new users who are

1:20:47

like Gene Bean's dad

1:20:50

who aren't looking under the covers very

1:20:52

much and just need a system that you know you

1:20:54

can install stuff from the app store and go

1:20:57

about your business. There's power

1:20:59

users migrating from Windows. There's

1:21:01

Linux curious folks who have an innate you know

1:21:03

who are curious and want to learn Linux versus

1:21:05

folks who are just trying to cut off Windows.

1:21:07

So I think a lot of

1:21:09

this can be good advice but we should probably have been more

1:21:11

careful around like what which segment are we actually talking about and

1:21:14

what are their motivations because I think that changes what makes good

1:21:17

advice for them. There's one last one

1:21:19

here just addressing how I was complaining

1:21:21

about small boot partitions and running into

1:21:24

kernel issues. I did a

1:21:26

little research. Pop West automatically sets a boot partition size

1:21:28

of 1.1 gigs on

1:21:30

their system but it only seems to keep

1:21:32

two old kernels. I can

1:21:34

confirm this using Google but the install has

1:21:36

been up for over a year now with

1:21:39

auto updates and everything

1:21:41

seems to be working fine. Now

1:21:44

I have to say I did get a

1:21:46

note from our dear friend Carl. He

1:21:49

sent me a little tip here. He sent me

1:21:51

a project called K Thresher which would

1:21:54

potentially help me with this exact issue

1:21:56

I was having with kernels.

1:22:00

on Kubuntu specifically filling up the boot

1:22:02

partitions. So if you are having similar

1:22:04

issues to me, K-Thresher

1:22:06

might be worth checking out. K-Thresher for the

1:22:09

win. Mononite comes in with 6,666 ads. Make

1:22:14

it so. The safety you feel in

1:22:16

NixOS being able to just try something

1:22:18

without risking borking your system truly

1:22:21

cannot be overstated.

1:22:24

You can swap out the whole subsystems and

1:22:26

see if they work better or see if

1:22:28

something on your hardware works without fear that

1:22:30

you're going to irreversibly break your system. It's

1:22:34

a tinkerer's dream. Though I still have some

1:22:36

reservations about it as a daily driver desktop

1:22:38

system. Curious if anyone else has

1:22:40

slapped Nix onto a gaming machine and if they've

1:22:42

had a good no fuss experience. God,

1:22:45

you know, I'm so tired of

1:22:48

this mentality. I mean, that's a great boost,

1:22:50

Mononite. But I don't know.

1:22:52

Computers used to be so much harder than they

1:22:54

are now. And is Nix as

1:22:56

easy as Ubuntu? No. But

1:22:59

it is so much easier than computers

1:23:01

used to be. And I do use

1:23:03

it for gaming. And, Mononite, I'm

1:23:05

not disagreeing with you. I think you're right. It's

1:23:07

not necessarily as easy, but like that's a

1:23:10

variable self-defined bar that each one of

1:23:12

us has that we then project onto

1:23:14

everybody else. And I guess I'm kind

1:23:16

of tired of it. I'm not the

1:23:18

smartest guy in the world. I'm not

1:23:20

a developer by day. And all of

1:23:22

my desktops use NixOS. I

1:23:24

don't know. Somehow this Luddite's getting it

1:23:27

done. And I

1:23:29

game on these systems. In fact, the system

1:23:31

I have the most problems gaming on is

1:23:33

my Steam Deck that runs Arch. So,

1:23:36

riddle me that, Batman. Like, I know it's

1:23:38

not easy for everybody. And I know it's

1:23:40

not super simple to just download a binary

1:23:42

and execute it. And that's really hard and

1:23:44

everybody hates that. But like, it's not like

1:23:46

it's so fricking difficult. And you

1:23:48

bounce off everything a couple of times. And just

1:23:50

because you bounce off it once or twice doesn't

1:23:52

mean it's a bad thing. Now, it

1:23:54

also means people need to know what's up going

1:23:56

in. And I think Moon Knight nails that. I'm

1:23:59

actually more really kind of just frustrated. fact that

1:24:01

ambient noise seems to think that you can't use

1:24:03

NixOS as a desktop. But I, whatever, whatever.

1:24:06

It is what it is and just use whatever makes you

1:24:08

happy. I'm tired of fighting about

1:24:10

it. Amen to that. Well,

1:24:13

maybe this'll, maybe this'll help you

1:24:15

out here, Chris. Southern Fried Santa Sephrasse comes in

1:24:17

with 10,000 sets. Perhaps

1:24:19

not possible, nothing can do that.

1:24:22

After putting it off for so long,

1:24:24

I'm finally giving NixOS a try. I

1:24:26

had Pop OS installed on my work

1:24:29

laptop, but it had been just sluggish

1:24:31

enough to be noticeable lately and

1:24:33

it had been doing updates even though I

1:24:36

turned automatic updates off. Well,

1:24:38

an update broke something in the boot

1:24:40

process that the laptop was stuck on

1:24:42

the manufacturer logo. Rather than

1:24:44

try to fix that, I just pulled

1:24:46

any non-backtop files off and installed Nix.

1:24:50

I think I'm on the Nix train now. Even

1:24:52

after taking way too long to get WireGuard working

1:24:54

and there's still some kinks to sort out, but

1:24:56

I'm really liking it. I'm

1:24:58

also giving Plasma Six a go after being on

1:25:00

a GNOME desktop for years. Different

1:25:03

but clean. It will definitely take

1:25:05

some getting used to. Good on you for

1:25:08

being willing to take the journey. You know, we say it all

1:25:10

the time and it may become a cliche on the show, but

1:25:12

it is true. It is harder

1:25:14

on Nix, but you solve it once. Like, listener

1:25:16

Jeff was, when he first connected in the mobile

1:25:18

room, he was on his Nix

1:25:20

desktop and he realized, oh, I

1:25:22

don't have like the higher quality audio

1:25:25

codec for my Bluetooth headset. Yeah,

1:25:27

you know what? That means you got to go set up a couple

1:25:29

more things in the Nix config. Yeah, you got to go do that.

1:25:31

And it kind of sucks because you're already on the call. Oh,

1:25:34

silly me. I don't have the higher quality audio. I thought I would

1:25:36

just have it because I always have that and now I don't have

1:25:38

it. God, Nix sucks so much. Right?

1:25:41

But then you disconnect. You go add the

1:25:43

three lines to your configuration file. You

1:25:45

rebuild and now you've solved that problem

1:25:48

forever. Right? That's the difference.

1:25:50

We were also really impressed

1:25:53

this week about just how much we are

1:25:55

using Nix shell. Wes,

1:25:58

could you explain Nix shell? I'm using the

1:26:00

heck out of this thing because I just forget to install

1:26:02

software all the time and it's just like, oh yeah, I

1:26:04

need that thing and I go and grab it. Yeah,

1:26:07

I think the way you're using it is probably running

1:26:10

nix-shell-p and

1:26:13

then the package you want. And it's just a

1:26:15

super handy quick way to go

1:26:17

ask Nix to temporarily give

1:26:19

you a shell environment where you have that

1:26:21

package available. It doesn't get installed permanently once

1:26:23

you exit the shell, it's gone,

1:26:26

and it's gonna get cleaned up

1:26:28

whenever you do your next Nix store garbage collection. So

1:26:30

it's a super handy, no cost way to basically like,

1:26:32

oh, I wanna try this tool or I need this

1:26:34

tool. I don't really use it all the time, maybe

1:26:37

a couple times a month and I don't really wanna

1:26:39

keep it around in my system. I just know I

1:26:41

can go fetch it from Nix whenever

1:26:43

I want. Yeah, crazy handy and again,

1:26:45

available on any distro. But like

1:26:47

for my set set up here, I was testing network connectivity

1:26:50

and I wanted to install MTR and

1:26:52

a couple other things that I was only gonna use for like

1:26:54

the couple of days that I'm here and then I probably won't

1:26:56

use it again for a long time. And Nix shell-p

1:26:59

install is really kinda handy for that because you

1:27:01

temporarily have that, you're in that environment where that

1:27:03

exists and then when you're done and

1:27:05

you do a garbage collection, it's gone. It's

1:27:07

really, really great. I wanted to shout out to user 77.3 who

1:27:09

boosted and he

1:27:11

was below the 2000 sat cutoff, but

1:27:14

he had a great note. Long time listener,

1:27:16

first time booster. So first of all,

1:27:18

thank you very much, appreciate it. Boop,

1:27:20

boop, boop. Thanks for taking that journey. Says,

1:27:23

thanks for the great shows. I found a

1:27:25

backup program that looks very promising and I

1:27:27

thought it might be worth your while. It's

1:27:29

called Copia, K-O-P-I-A at k-o-p-i-a.io.

1:27:33

I've been using Restick, but I wanted something a

1:27:35

bit more. That is

1:27:37

great. Thank you for being a long time listener and

1:27:39

taking the effort to sign up. We

1:27:41

had a bunch of boosters. We

1:27:44

have a 2000 sat cutoff for time and

1:27:46

we had 25 boosters across 42 total boosts.

1:27:49

Now we do have the 2000 sat cutoff. Thank

1:27:52

you everybody who boosted and we stacked 300,403 sats. ["Taps"]

1:28:05

Thank you everybody. Now if you're the first time listener for some

1:28:07

reason, you're like, what did I just listen to? The

1:28:10

boosts are a peer-to-peer way for our listeners

1:28:12

to send value into the show. At one

1:28:14

point in time, we were owned by a

1:28:17

corporation and it just didn't really work for

1:28:19

the niche that we're trying to serve. It didn't really work

1:28:21

for the show and we fought to

1:28:23

get this back. And now it's an independent production

1:28:25

that is supported by our audience. And

1:28:28

so you can boost in and if you

1:28:30

value each individual production, if you like that

1:28:32

episode, it made you think about something, you

1:28:34

got some signal from it, you want to

1:28:36

participate in the conversation, go get a new

1:28:38

podcast app at podcastapps.com. Something like fountain or

1:28:40

podverse, which is GPL. Great

1:28:42

way to participate in the conversation and

1:28:44

send your message in. Thank you everybody who

1:28:47

boosted in. We really do appreciate it. You

1:28:49

guys, you really make the show

1:28:51

possible. The boosters, the members, we

1:28:53

wouldn't be able to do without you. Thank you very much. newpodcastapps.com,

1:28:56

or if you want to become a

1:28:58

member, it's linuxunplug.com/membership.

1:29:03

Now, before we get out of here, Wes,

1:29:06

you were on fire this week with

1:29:08

the picks. Like I had a really

1:29:10

hard choice trying to get it down

1:29:13

to one, but the

1:29:15

one of the out of all of them just

1:29:17

seems so unique and like

1:29:19

something I don't think we heard, we'd hear anybody else

1:29:22

talk about that. I felt like this should be the

1:29:24

pick this week and it's called multiplex.

1:29:26

Can you tell us a bit about it? Yeah,

1:29:28

multiplex is a go app to

1:29:31

watch torrents with your

1:29:34

friends. So, you know,

1:29:36

you might have experienced something like Apple

1:29:38

Share Play or Amazon's prime video watch

1:29:40

party, or, you know, jelly

1:29:42

fin sink or the Plex feature that exists

1:29:44

for this. Well, this

1:29:46

is the same idea. But for

1:29:48

torrents, you don't have to have some proprietary platform, you just

1:29:50

gotta, you know, have a have a torrent to a file,

1:29:53

maybe you're sharing that for your friends, maybe you're finding it

1:29:55

somewhere else. And it lets you

1:29:57

stream any file directly using a wide range

1:29:59

of video. program

1:32:00

and we'll see you right back here next

1:32:02

Tuesday as in

1:32:04

Sunday! you