1 00:00:00,000 --> 00:00:05,440 The Linux Challenge 2026 edition was supposed to be a three-part series. 2 00:00:05,440 --> 00:00:11,840 The setup, a task-off challenge episode, testing day-to-day usability, and a conclusion. 3 00:00:11,840 --> 00:00:17,840 But then the first week was full of so many unexpected highs and lows. 4 00:00:17,840 --> 00:00:23,040 We knew there had to be another video, especially after the Linux community exploded 5 00:00:23,040 --> 00:00:28,720 after I picked PopoS again. And while Luke and I seem to have been praised for our choices, 6 00:00:28,720 --> 00:00:33,200 I can tell you guys firsthand that it has not been a smooth ride for me. 7 00:00:33,200 --> 00:00:40,560 Meanwhile, things were going so great for me. I decided to dip my toes even further, attempting some more complex tasks 8 00:00:40,560 --> 00:00:44,480 that I didn't expect to go super well, just to see what would happen. 9 00:00:44,480 --> 00:00:49,440 And I ended up trying some other distros, which addressed some of my issues with PopoS, 10 00:00:49,440 --> 00:00:52,640 but also ended up being frustrating in their own ways. 11 00:00:52,640 --> 00:00:56,400 But what is even more frustrating is that they aren't letting me be the one. 12 00:00:56,400 --> 00:00:58,160 So segue to our sponsor. 13 00:01:07,680 --> 00:01:12,880 I feel like I've got to start this by explaining my brain-dead choice of PopoS. 14 00:01:12,880 --> 00:01:20,480 It was amazing how many people got angry at me for picking the same distro that screwed me over last time. 15 00:01:20,480 --> 00:01:24,480 But if you guys remember, I actually used Manjaro last time 16 00:01:24,480 --> 00:01:29,280 after I was assured that the bug that I encountered when I was setting up PopoS 17 00:01:29,280 --> 00:01:34,560 was a one-time fluke, and then I got piled on for being so quick to abandon it. 18 00:01:34,560 --> 00:01:38,080 So this is me putting aside my past experience 19 00:01:38,080 --> 00:01:42,400 after seeing so many people, listicles, and chatbots that still recommend it. 20 00:01:42,400 --> 00:01:46,320 That willingness to try again is a good thing for Linux. 21 00:01:46,320 --> 00:01:51,840 I mean, if everybody bailed after one bad experience, there would be no distros left to try. 22 00:01:51,840 --> 00:01:55,440 Nothing is perfect. And unfortunately, that goes especially for PopoS. 23 00:01:55,440 --> 00:02:00,800 System76 has spent the last couple of years hard at work on a new desktop environment, 24 00:02:00,800 --> 00:02:03,520 Cosmic, and it's been a challenge. 25 00:02:04,160 --> 00:02:08,320 Linus, Cosmic is basically in beta. Don't you know that it's not ready yet? 26 00:02:08,320 --> 00:02:12,240 No, I didn't. For one thing, where does it say that? 27 00:02:12,240 --> 00:02:16,720 The thing that I downloaded was called LTS, or Long Term Support. 28 00:02:16,720 --> 00:02:24,080 That's like the opposite of beta. I would have had to journey to a random blog post from back in September of 2025 29 00:02:24,080 --> 00:02:27,280 to discover that Cosmic is now in public beta. 30 00:02:27,280 --> 00:02:32,960 Number two, maybe this is a hot take, but maybe if System76, a commercial entity, 31 00:02:32,960 --> 00:02:37,200 not a random open source contributor, knows that it's not ready for prime time, 32 00:02:37,200 --> 00:02:40,880 instead of blaming me, we should probably blame the company that shipped it. 33 00:02:40,880 --> 00:02:46,720 And you know what? Yeah, I could have come across some of the Linux YouTube channels that have highlighted these issues, 34 00:02:46,720 --> 00:02:51,600 but a key element of the Linux challenge is highlighting that unless you know to ask the 35 00:02:51,600 --> 00:02:55,440 question, is this distro's desktop environment in beta? 36 00:02:55,440 --> 00:02:59,600 It can be hard for new Penguin curious users to find the right answers. 37 00:02:59,600 --> 00:03:03,360 So as we keep going, it's important to think of the Linux challenge, 38 00:03:03,360 --> 00:03:09,680 not as an attack on Linux, but as more of a pen test for how friendly it is to newbies. 39 00:03:09,680 --> 00:03:13,760 My Bazide adventures started a bit better than Linus at first, 40 00:03:13,760 --> 00:03:18,000 but if you remember in part one, I mounted my SMB share. 41 00:03:18,000 --> 00:03:22,080 I was shocked at how easy it was to find, because normally on Windows, 42 00:03:22,080 --> 00:03:26,240 I would have to type in the address bar and find it, versus on Bazide, 43 00:03:26,240 --> 00:03:33,040 I just clicked on network and it found it right away. But I didn't realize that that wasn't mounting it. 44 00:03:33,040 --> 00:03:38,400 That was just creating a shortcut. This means my read and write permissions were all over the place, 45 00:03:38,400 --> 00:03:43,920 and I couldn't save some files to my network drive if I clicked on that shortcut. 46 00:03:43,920 --> 00:03:48,800 To solve this, I had to do some Googling, and I found out that I needed to modify my FSTab file 47 00:03:48,800 --> 00:03:52,880 to point the network location to the MNT folder on my drive. 48 00:03:52,880 --> 00:03:56,160 So I did that, but then I noticed that I had two, 49 00:03:56,160 --> 00:03:59,200 both of which were still behaving like a shortcut. 50 00:03:59,200 --> 00:04:03,280 I tried at least a dozen different options in order to mount the share correctly, 51 00:04:03,280 --> 00:04:07,360 none of which ultimately succeeded, or should have even been necessary if you ask me. 52 00:04:07,360 --> 00:04:12,000 Opening context menus on icons, shortcuts, or applications is a great tool, 53 00:04:12,000 --> 00:04:15,440 and it seems like a big oversight on the Bazide team 54 00:04:15,440 --> 00:04:18,720 to not include a quick mount option that just works. 55 00:04:18,720 --> 00:04:24,080 Instead, I want to FSTab myself in the head. Meanwhile, I was having a grand old time on Cache, 56 00:04:24,080 --> 00:04:29,120 and since I felt more comfortable than the other two guys, I decided to get a little bit daring. 57 00:04:29,120 --> 00:04:33,600 I uninstalled my entire cinema desktop environment on purpose 58 00:04:33,600 --> 00:04:40,800 to see if I would run into any challenges. I took about 20 minutes max before I was up and running with KDE Plasma, 59 00:04:40,800 --> 00:04:45,840 and my only issue was that I had to clean up some small things left over from Cinnamon, 60 00:04:45,840 --> 00:04:49,440 like an additional sound icon that was in the bottom tray, 61 00:04:49,440 --> 00:04:56,080 because I had two sound icons and they could conflict and stuff, and that was honestly also really easy to do, so no big deal. 62 00:04:56,080 --> 00:04:59,840 As for my gaming adventures, my first real challenge 63 00:04:59,840 --> 00:05:03,280 in this Linux challenge was probably my own fault. 64 00:05:03,280 --> 00:05:10,960 I had read some stuff online saying that I could do it, but I think I was trying to be a little bit more optimistic than realistic. 65 00:05:10,960 --> 00:05:15,920 I had a Windows game drive previously that I just kind of left alone and tried to use on Linux, 66 00:05:15,920 --> 00:05:19,120 which means that it was formatted in NTFS. 67 00:05:20,240 --> 00:05:24,400 I just added it to my Steam library in Linux and tried to go. 68 00:05:24,400 --> 00:05:27,760 All my games showed up perfect and everything seemed fine at first. 69 00:05:27,760 --> 00:05:31,120 Some games even ran okay, but I started to notice some glitches, 70 00:05:31,200 --> 00:05:35,120 and even some games that I had freshly installed on that drive just wouldn't work. 71 00:05:35,120 --> 00:05:38,560 It would just be click play and it just wouldn't launch sometimes. 72 00:05:38,560 --> 00:05:42,080 It turns out that while Linux can still use NTFS, 73 00:05:42,080 --> 00:05:51,600 and there's been some ongoing development to make it even smoother, even since we started this challenge, I can say in my experience it was kind of rough, 74 00:05:51,600 --> 00:05:58,560 especially when used with Proton. Proton doesn't seem to like it, so in my opinion, if you want to play games off of an NTFS drive, 75 00:05:58,560 --> 00:06:00,960 just don't, at least not right now. 76 00:06:01,760 --> 00:06:06,560 My gaming experiences were mostly smooth, with two major exceptions though, 77 00:06:06,560 --> 00:06:10,640 one of which I'm actually going to save for the conclusion, because it's kind of a spicy one, 78 00:06:10,640 --> 00:06:16,400 so make sure you get subscribed for that. But the other was actually the first game that I tried to fully play on Linux, 79 00:06:16,400 --> 00:06:19,920 Poppy Playtime Chapter 5. I wanted to stream it, 80 00:06:19,920 --> 00:06:24,640 but I was getting no audio and no picture, which is not ideal for a stream. 81 00:06:25,200 --> 00:06:30,800 Oh no, are we not going to be able to play? But then it suddenly just popped in and started working fine. 82 00:06:31,360 --> 00:06:34,960 I played it for a little while, and then the same thing happened again. 83 00:06:34,960 --> 00:06:37,840 Look, all the friends are here, isn't this amazing? Oh. 84 00:06:38,880 --> 00:06:42,720 Well, it turns out that the pre-rendered cutscenes weren't working. 85 00:06:42,720 --> 00:06:46,400 Proton, which is the compatibility layer that allows non-native Linux titles 86 00:06:46,400 --> 00:06:53,840 to work on Linux, is missing proprietary licenses for H.264 and H.265 video codecs. 87 00:06:53,840 --> 00:06:57,600 What was the solution? A community fork called ProtonGE, 88 00:06:57,600 --> 00:07:01,840 which thankfully was in the Bazite Store. That's a pretty simple fix, 89 00:07:01,840 --> 00:07:07,680 but it's also one that highlights how unrealistic some Linux evangelists can be about the experience. 90 00:07:07,680 --> 00:07:10,880 No, in many cases, it doesn't just work out of the box, 91 00:07:10,880 --> 00:07:14,560 and users who don't treat fixing their operating system as a hobby 92 00:07:14,560 --> 00:07:18,080 will be looking for someone to blame for this hassle. So is it Linux? 93 00:07:18,720 --> 00:07:21,680 Valve? Mob Entertainment? The user? 94 00:07:22,400 --> 00:07:26,080 Maybe all? Or hear me out, none? 95 00:07:26,080 --> 00:07:31,520 It's easy to jump on the blame bandwagon and hate on some developers for not prioritizing Linux. 96 00:07:31,520 --> 00:07:35,840 But ask yourself this, if 50% of your customers were on Windows 97 00:07:35,840 --> 00:07:38,960 and the other 48% are on Xbox and PlayStation, 98 00:07:38,960 --> 00:07:42,000 would you be stoked on hiring a fourth group of employees 99 00:07:42,000 --> 00:07:48,800 whose job it is to deal with the other 2%? Especially knowing that those 2% are not running one OS, 100 00:07:48,800 --> 00:07:53,200 but are probably running different flavors of OS? I mean, maybe you would. 101 00:07:53,200 --> 00:07:56,560 But it's more important to remember that just like the users, 102 00:07:56,560 --> 00:08:00,960 many companies don't treat fixing operating systems like a hobby. 103 00:08:00,960 --> 00:08:04,640 Okay, so then we blame Valve. No, obviously not. 104 00:08:04,640 --> 00:08:08,080 It's super cool that they have put so much support into Proton, 105 00:08:08,080 --> 00:08:11,120 but the fact that they've paid so much already 106 00:08:11,120 --> 00:08:15,760 is not a good argument that they should just obviously pay 107 00:08:15,760 --> 00:08:19,520 even more for these commercial video codecs. The point I'm trying to make here 108 00:08:19,760 --> 00:08:24,000 is that enjoying the Linux experience requires a no blame mindset. 109 00:08:24,000 --> 00:08:27,920 Some stuff's gonna work and some stuff won't. It's not anybody's fault. 110 00:08:28,480 --> 00:08:32,400 Everyone is doing their best. So with that in mind, throw out what I said earlier, 111 00:08:32,400 --> 00:08:38,880 because I'm not mad at System 76. In fact, I left PopOS on my main desktop just for the lulls 112 00:08:38,880 --> 00:08:42,000 and it mostly worked for most things. With that said, 113 00:08:42,000 --> 00:08:45,040 when it came time to install Linux on my other systems, 114 00:08:45,040 --> 00:08:49,760 I did opt for something different. Starting with Bazite on my home theater PC. 115 00:08:49,760 --> 00:08:52,240 It's just too bad the Linux curse followed me there as well. 116 00:08:52,800 --> 00:08:56,960 Bazite has different versions of their installer, depending on the brand of your GPU 117 00:08:56,960 --> 00:09:00,480 and whether or not you want the SteamOS full screen experience. 118 00:09:00,480 --> 00:09:04,560 Well, I've got an NVIDIA GPU and yeah, I want that experience. 119 00:09:04,560 --> 00:09:11,200 That's kind of the point of it on a home theater PC. So I picked this one and let's put it this way. 120 00:09:11,200 --> 00:09:17,680 The Bazite team feels that I should have known the one that I selected would result in a completely unusable experience. 121 00:09:17,680 --> 00:09:20,720 But to me, that's actually not that obvious. 122 00:09:20,720 --> 00:09:24,000 Coming from the Windows Google normie world, 123 00:09:24,000 --> 00:09:29,280 where a stable service like Gmail was labeled beta for five years, 124 00:09:29,280 --> 00:09:33,760 it's not that unreasonable to think that you can daily drive a beta 125 00:09:33,760 --> 00:09:41,920 and have a mostly functioning experience. In Linux, that's an expectation that needs to be completely thrown out the window. 126 00:09:42,000 --> 00:09:45,040 Here, beta seems to mean this is broken. 127 00:09:45,040 --> 00:09:49,040 And if you're not a developer, you should probably just download the LTS, 128 00:09:49,040 --> 00:09:54,000 which might also be beta. Ha ha! Clearly we've got to reach a middle ground here 129 00:09:54,000 --> 00:09:57,920 and Bazite seems to agree because they have updated the messaging on their site. 130 00:09:57,920 --> 00:10:01,120 Anyway, that happened later. So to get my system up and running, 131 00:10:01,120 --> 00:10:07,280 I ended up doing what many Linux people do and switching to a Radeon card, which was completely painless. 132 00:10:07,280 --> 00:10:10,880 Why run Bazite when I could just run SteamOS 133 00:10:10,880 --> 00:10:14,640 on the Steam machine that we built on this channel like a couple months ago? 134 00:10:14,640 --> 00:10:20,560 I can't believe I forgot about this thing. I've been meaning to install it. I actually ended up throwing SteamOS on my home theater PC. 135 00:10:20,560 --> 00:10:24,880 Nice. Okay. Is it a bit of a hack to just switch out your hardware? 136 00:10:25,840 --> 00:10:31,280 Yes, but also no, because a lot of Linux gamers would go out of their way 137 00:10:31,280 --> 00:10:34,960 to choose compatible hardware in the first place. So I'm pretending I did that. 138 00:10:34,960 --> 00:10:37,680 First, I want to see how well this integrates with my system here. 139 00:10:38,400 --> 00:10:40,640 Let's hit PowerToggle for the PC. 140 00:10:41,760 --> 00:10:49,520 No way. Did Valve seriously bake in support for this old Microsoft IR receiver? 141 00:10:49,520 --> 00:10:53,680 Which was child's play to get working and it's been kind of awesome from the couch. 142 00:10:53,680 --> 00:10:58,640 Nothing further to report there. As for my laptop, I decided it was finally time to practice what I preach 143 00:10:58,640 --> 00:11:01,920 and go for good old-fashioned, trustworthy Ubuntu. 144 00:11:02,000 --> 00:11:06,720 Sort of. Ubuntu is actually Ubuntu, but with the KDE desktop environment, 145 00:11:06,720 --> 00:11:09,760 which I find quite comfortable to navigate. Sort of. 146 00:11:09,760 --> 00:11:14,000 I mean, first I have to get to the desktop and day one was kind of terrible. 147 00:11:14,000 --> 00:11:19,280 After completing setup, it just black screened and it sat there for hours. 148 00:11:19,280 --> 00:11:23,760 And I was like, come on, man, this is ridiculous. Then I came down in the morning 149 00:11:23,760 --> 00:11:28,400 and it was like Santa had visited because it was magically sitting at the login screen 150 00:11:28,400 --> 00:11:31,840 and it's been downright pretty solid ever since 151 00:11:31,840 --> 00:11:36,240 with a bit of a learning curve. For example, I did run into issues getting some applications to work 152 00:11:36,240 --> 00:11:41,760 due to downloading the wrong package. Debian packages, snap packages, and flat packs 153 00:11:41,760 --> 00:11:46,480 will all work on Kubuntu. But I figured, okay, well, Debian makes the most sense 154 00:11:46,480 --> 00:11:50,320 since Kubuntu is based on Debian. But then after I installed OBS, 155 00:11:50,320 --> 00:11:54,720 I realized I had no option to select the display that I wanted to screen capture. 156 00:11:54,720 --> 00:11:57,760 The solution? Use the flat pack installer, apparently. 157 00:11:58,400 --> 00:12:03,200 Okay, but where? The top result, as far as I can tell, doesn't convey that it's a flat pack. 158 00:12:03,200 --> 00:12:07,360 Oh right, I need to enable a flat pack search. Except that wasn't the solution either 159 00:12:07,360 --> 00:12:11,360 because Wayland, which Kubuntu uses as part of its desktop environment, 160 00:12:11,360 --> 00:12:15,200 has a privacy thing built in that no likey screen capture. 161 00:12:15,200 --> 00:12:19,280 Now it can be worked around, but threads like this one are a great example 162 00:12:19,280 --> 00:12:23,040 of how troubleshooting can often be a guess and check experience 163 00:12:23,040 --> 00:12:26,080 because there are like five different solutions in here 164 00:12:26,080 --> 00:12:29,200 and I actually can no longer remember which one worked. 165 00:12:29,200 --> 00:12:33,360 Of course, though, it's important to point out that every problem that we're having with Linux 166 00:12:33,360 --> 00:12:39,040 can also be a problem with Windows. But the fact that Microsoft is also bad 167 00:12:39,040 --> 00:12:42,080 doesn't mean that we shouldn't be honest about issues 168 00:12:42,080 --> 00:12:46,560 or like level of tinkering required with Linux. 169 00:12:46,560 --> 00:12:50,240 My laptop, for example, running Mint and a very simple use case 170 00:12:50,240 --> 00:12:54,880 of basically just loading a browser hasn't required any tinkering this whole time 171 00:12:54,880 --> 00:12:58,400 and hasn't really had any problems. My desktop running CacheOS, 172 00:12:58,400 --> 00:13:01,440 I've intentionally tried to like put myself in harm's way 173 00:13:01,440 --> 00:13:07,120 and ran into some really complex scenarios that have been fun to diagnose and work through. 174 00:13:07,120 --> 00:13:11,360 But there are things that are quite simple on Windows 175 00:13:11,360 --> 00:13:16,400 and very easy to do that are more complicated on Linux. 176 00:13:16,400 --> 00:13:20,160 And that's okay, but trying to hide that fact 177 00:13:20,160 --> 00:13:24,640 in order to recruit more Windows users to join the community, 178 00:13:24,720 --> 00:13:29,920 I think does more harm than good, especially when they are unfortunately 179 00:13:29,920 --> 00:13:32,960 fairly often met with hostility from the community 180 00:13:32,960 --> 00:13:36,880 when they then run into these problems and are unequipped to deal with. 181 00:13:36,880 --> 00:13:40,240 I think there are some obviously extremely bright lights 182 00:13:40,240 --> 00:13:43,440 in the Linux community that bring a lot of hope and joy 183 00:13:43,440 --> 00:13:52,240 and fun to the whole experience of learning Linux. But there is a lot of negative communication 184 00:13:52,320 --> 00:13:59,200 on forums, on Reddit, elsewhere. It's very off-putting for new Linux community members, 185 00:13:59,200 --> 00:14:02,000 which we're going to be seeing a lot more of soon 186 00:14:02,640 --> 00:14:07,760 to receive that type of energy. The biggest thing that didn't work for me 187 00:14:07,760 --> 00:14:11,600 was just software compatibility. But with some time and effort, 188 00:14:11,600 --> 00:14:14,320 I did manage to find either an alternative way 189 00:14:15,120 --> 00:14:20,080 to get the Windows native version working for my admittedly somewhat basic software suite. 190 00:14:20,080 --> 00:14:23,600 I didn't. I use Adobe Premiere for editing, 191 00:14:23,600 --> 00:14:27,200 and one of the many fun ways that Adobe is kind of ass 192 00:14:27,200 --> 00:14:31,120 is that it just doesn't work on Linux. Now, I tried messing around with Bottles a bit, 193 00:14:31,120 --> 00:14:34,320 which allows you to run Windows software on Linux, 194 00:14:34,320 --> 00:14:38,640 but that was obviously still a no-go, which then sent me looking for alternatives. 195 00:14:38,640 --> 00:14:44,000 DaVinci Resolve has a Linux build, though it's only officially supported on Rocky Linux of all things. 196 00:14:44,000 --> 00:14:47,520 Still, Rocky Linux is a lot closer to Bazite than Windows is, 197 00:14:47,600 --> 00:14:51,760 so maybe? And yeah, after two hours of trying, 198 00:14:51,760 --> 00:14:54,800 I got her up and running, but not the way I thought. 199 00:14:54,800 --> 00:14:57,840 See, I just tried installing it like a Windows application. 200 00:14:58,400 --> 00:15:01,920 Download and run. But Bazite, as I learned, 201 00:15:01,920 --> 00:15:05,360 is in a mutable operating system similar to SteamOS. 202 00:15:05,360 --> 00:15:09,120 This means core operating system files and permissions are locked down 203 00:15:09,120 --> 00:15:12,800 in such a way that the user either can't screw them up or they can, 204 00:15:12,800 --> 00:15:19,760 but then they'll reset themselves after a reboot. Unfortunately, this same lockdown applies to some software installers, 205 00:15:19,760 --> 00:15:22,800 which then means that they can't alter the files that they need to. 206 00:15:22,800 --> 00:15:25,440 The solution was for me to beat my head against a wall, 207 00:15:26,080 --> 00:15:29,840 until I found this six-minute video about a simple command to run. 208 00:15:29,840 --> 00:15:34,640 Hey, software installed! But then I ran into the same problem as Poppy Playtime. 209 00:15:35,200 --> 00:15:38,480 Depending on the file that I was trying to play or export, 210 00:15:39,040 --> 00:15:43,280 it wouldn't work. Frickin' curse you, video codecs! 211 00:15:43,440 --> 00:15:46,640 Sigh. So I then tried Kaden Live, 212 00:15:46,640 --> 00:15:50,080 which is fine for basic editing, but if I want to be a power user, 213 00:15:50,080 --> 00:15:53,840 it's just not quite there yet. And for stills, neither is GIMP. 214 00:15:53,840 --> 00:15:56,640 You know what? I'm going to be the one to say it. GIMP sucks. 215 00:15:57,280 --> 00:16:02,320 With that said, I still want to emphasize the gratitude that I feel. 216 00:16:02,320 --> 00:16:06,240 And you, Elijah, I know you feel it too, toward the open source community, 217 00:16:06,240 --> 00:16:10,320 whether it's applications or drivers or Linux in general, 218 00:16:10,320 --> 00:16:14,080 the fact that people are stepping up against the corporate overlords 219 00:16:14,080 --> 00:16:19,120 who are limiting our choices, feasting on our wallets, and then spying on us for good measure 220 00:16:19,120 --> 00:16:24,560 is amazing and it's admirable. However, context matters. 221 00:16:24,560 --> 00:16:27,920 And when we're evaluating the experience of switching to Linux, 222 00:16:27,920 --> 00:16:34,480 we're doing so from a user perspective. And so we do have to point out things that might not be ideal. 223 00:16:34,480 --> 00:16:38,640 Just try to understand that it comes from a place of love and appreciation, 224 00:16:38,640 --> 00:16:42,080 not from a place of hate. Everybody involved in the Linux challenge today 225 00:16:42,080 --> 00:16:45,600 is rooting for Linux to succeed. And it's actually been really exciting 226 00:16:45,600 --> 00:16:50,960 to see so many social media posts of people who have joined the challenge alongside us, 227 00:16:50,960 --> 00:16:55,280 even though we didn't ask anybody to. But as exciting as all of that is, 228 00:16:55,280 --> 00:16:59,040 part of succeeding in this is taking off the blinders 229 00:16:59,040 --> 00:17:02,480 and being honest about the areas where things need to improve. 230 00:17:02,480 --> 00:17:06,480 And it's actually been pretty cool to see that some of our observations 231 00:17:06,480 --> 00:17:11,920 are already resulting in clearer documentation that's going to help pave the path for future users. 232 00:17:12,560 --> 00:17:17,760 Now, I know we're releasing part two, like way past the one month point already. 233 00:17:17,760 --> 00:17:21,040 Elijah was busy fixing our environmental chamber, among other things. 234 00:17:21,040 --> 00:17:24,960 But we do still have more videos lined up for the series. And as you guys can see, 235 00:17:24,960 --> 00:17:29,600 even though we're past the month, there will be some surprises in the future parts. 236 00:17:29,600 --> 00:17:34,080 Part three is going to have us do some fun challenges. And then part four is going to be the conclusion 237 00:17:34,080 --> 00:17:37,440 where we sit down on the couch together and talk about our final thoughts. 238 00:17:38,000 --> 00:17:41,680 Oh, and we'll probably also talk about our segue to our sponsor. 239 00:17:41,680 --> 00:17:46,480 If you guys enjoyed this video, go check out part one. We talked through the choices that we made 240 00:17:46,480 --> 00:17:50,080 and the installation process. It's over a month old at this point, 241 00:17:50,080 --> 00:17:54,640 which I know we said we were only going to do a one month challenge, but maybe that gives you a little hint 242 00:17:54,640 --> 00:17:56,560 as to what our conclusion might be.