add all 2021 transcripts and summaries

35： The Perfect Media Server _summary.txt

@@ -0,0 +1,92 @@
+• Discussion of SyncThing server setup and performance
+• Feedback from listeners about previous episodes on SyncThing
+• Introduction to the host's "perfect media server" project
+• Overview of the perfect media server concept and its evolution over time
+• The project's five-year development journey and upcoming release
+• Plans for a 2020 version of the article on perfect mediaservers.com
+• Creating a wiki-style website for media server setup and management
+• The importance of having up-to-date information on media server setup
+• Using open-source tools and community contributions for media server setup
+• The value of opinionated guidance in helping people choose a specific setup
+• Introducing the site perfectmediaserver.com as a resource for setting up a home media server
+• Discussing the potential for users to get overwhelmed by various options and documentation
+• Highlighting the need for clear, step-by-step guides for installing Ubuntu, MergerFS, and other tools
+• Covering topics such as Docker, ZFS, Proxmox, and hardware setup
+• Media server build costs
+• Minimum hardware requirements (CPU, motherboard, RAM, hard drives)
+• Comparison of True NAS and Free NAS products (Synology, QNAP, Unraid, ZFS)
+• MergerFS for dynamic storage growth and flexibility
+• Benefits of using Linux for media servers (open source, reliability, battle-tested)
+• Discussion of MergerFS vs ButterFS
+• ZFS limitations and comparison to other file systems
+• Use cases for MergerFS and its benefits
+• Experience with MergerFS on Raspberry Pi media servers
+• Comparison of MergerFS, ZFS, and SnapRaid solutions
+• Contributing to the self-hosted wiki using MKDocs
+• Vim and search function
+• MKDocs features, customization, and usability
+• Documentation presentation and readability
+• Open-source documentation platform
+• Ease of use and flexibility for internal documentation
+• Future-proofing with plain text Markdown files in a Git repo
+• The user has spent several hundred hours working on their website
+• They are open to receiving pull requests and issue reports through the GitHub repository
+• A listener is asked about ButterFS documentation, prompting an exchange of comments
+• The conversation then shifts to discussing Linode, a cloud hosting provider, including its pricing and features
+• Two listeners share their experiences with using Linode for NextCloud setups and perfectmediaserver.com
+• Discussing generating public URLs for soundboard clips
+• Linode services, including object storage and load balancers
+• Powerline networking, including its use in scenarios where Wi-Fi is unreliable
+• Personal experience with powerline adapters and TP-Link AV1000s
+• JT's email sharing his positive experience with using powerline adapters
+• Issues with packet drops and bandwidth limitations
+• Customer's experience with Cloudfree.shop smart plugs and Home Assistant
+• Automation of home devices, including bearded dragon cage lights and fish tank lights
+• Integration of a D1 mini ESP8266 Wi-Fi board and BME280 sensor for temperature, pressure, and humidity control
+• Discussion on the importance of redundancy in automation systems
+• Discussion about Powerline adapters and their performance
+• Comparison of Powerline speeds to wired Ethernet and mesh Wi-Fi
+• Sharing of listener's experience with TP-Link Powerline products
+• Mention of various speed tests conducted by the listener
+• Discussion of the listener's preference for mesh Wi-Fi over Powerline
+• Misleading marketing practices by manufacturers regarding gigabit speeds
+• Separation of solar power system from main electrical system
+• Use of coax for running ethernet cables in modern homes
+• Potential benefits of using QuickSync-enabled motherboards, specifically the ASRock J5040 ITX board, for low energy usage and NAS capabilities
+• QuickSync hardware acceleration is mentioned as looking "really good"
+• The latest AMD desktop APUs are getting idle power consumption below 10 watts
+• A Ryzen 5000 processor is being considered due to its performance benefits
+• A cloud guru has a Python 3 scripting course for system administrators available at their website
+• NFC tags and their limitations on iOS
+• Using NFC tags for home automation, such as controlling heating and lighting
+• Comparison of NFC tag functionality between iOS and Android devices
+• Setting up a studio mixer with an NFC tag to automate tasks
+• Storage setup strategies for media collection (8 terabytes) and personal photos
+• Recommendations for storage solutions and software, including perfectmediaserver.com
+• Building a media server for storing 8 terabytes of data
+• Recommending used enterprise gear from serverbuilds.net
+• Discussing the importance of redundancy and duplication in storage solutions
+• Suggesting a mini ITX box with two bays to hold a large hard drive
+• Advising on hardware capacity, recommending at least 12 terabytes for current users
+• Mentioning Amazon.de as a potential source for affordable Western Digital drives
+• Local storage vs cloud storage
+• Personal risk profile and importance of data
+• Cost of ownership and potential surprises with cloud storage
+• Self-hosted solutions for digitalizing and organizing recipes
+• Options for scanning and digitizing handwritten family recipe books, including apps like Scanbot and Vapeen 1111/Recipes
+• Syncing files to multiple cloud services
+• Recipe management and importing from websites
+• Open-source software for managing household items
+• Self-hosted solutions vs. mainlining Linux distributions
+• Hardware support for open-source operating systems
+• Ecosystem limitations for rapid hardware support
+• Comparisons with the Raspberry Pi and its image availability
+• The speaker's experience with the Helios 64 and its Pi KVM setup
+• ZFS working on the Helios 64 after a kernel update and DKMS fix
+• Challenges of getting ARM-based devices to run with Linux and Windows
+• Apple's transition to ARM CPUs and its impact on the industry
+• Support for projects like the Helios 64 and COBOL from the community
+• The speaker selling their Helios 64 unit and offering a special thank you to Self-Hosted members
+• Contact information: dot show/contact and social media handles
+• Self-hosted podcast and Jupiter Signal network
+• Show URL: selfhosted.show/35

35： The Perfect Media Server _transcript.txt

@@ -0,0 +1,1741 @@
+[0.08 --> 2.50]  Today's episode is a really exciting one for me.
+[3.06 --> 5.70]  It's the culmination of five years' work.
+[6.00 --> 9.66]  The perfect media server is now, well, I'll save it for the show.
+[10.06 --> 11.68]  We also respond to a ton of your feedback.
+[11.96 --> 13.50]  This is Self-Hosted 35.
+[15.00 --> 17.50]  Well, Alex, I'll admit it right here on the show,
+[17.66 --> 20.66]  I set up yet another SyncThing server this weekend.
+[21.00 --> 23.54]  You thought you'd leave 2020 behind in style, hey?
+[24.10 --> 25.86]  I wanted more speed, Alex.
+[25.92 --> 29.58]  Actually, it really came down to me doing the math and realizing,
+[29.58 --> 33.92]  hey, you know, when I switch networks, it kind of slows the syncing down.
+[34.28 --> 37.02]  But if I can pull from multiple Sync servers,
+[37.62 --> 40.64]  it kind of makes up for it and goes even faster in ideal situations.
+[40.80 --> 44.58]  So I thought, why not set up a SyncThing server on Linode
+[44.58 --> 47.80]  and just sync a small select stuff that I really want to move fast?
+[48.56 --> 51.10]  And it legit works. It's really nice.
+[51.76 --> 54.52]  It's like doubles the amount of files that can be transferred at once, too,
+[55.02 --> 56.88]  from what I can tell in my brief testing.
+[56.88 --> 59.64]  I'll be honest, I haven't continued with SyncThing
+[59.64 --> 61.62]  after we talked about it a couple of episodes ago.
+[61.96 --> 62.80]  It just doesn't work for me.
+[62.88 --> 64.58]  It just doesn't do it, I'm afraid.
+[64.84 --> 66.16]  But I'm glad it's working for you.
+[66.54 --> 67.86]  You're a hater. I understand.
+[68.30 --> 69.46]  I understand. I understand.
+[69.64 --> 71.16]  I love it.
+[71.52 --> 80.10]  I think 2020 is the year that I stepped into a long-term relationship with SyncThing.
+[80.10 --> 84.18]  And it's not like I'm working on files super quick
+[84.18 --> 85.54]  and I want to move it between machines
+[85.54 --> 88.42]  and I want to edit a file upstairs and then walk down into the studio
+[88.42 --> 90.06]  and have that file on my desktop.
+[90.68 --> 94.26]  It may be able to serve that function, but I've learned not to expect that.
+[94.58 --> 97.28]  The one caveat I do have with SyncThing
+[97.28 --> 99.94]  is you've got to let it go at its own pace.
+[100.22 --> 101.46]  You've got to let it go at its own pace.
+[101.96 --> 103.56]  And that's why I love online learning, too.
+[103.62 --> 106.04]  And this episode is brought to you by the all-new A Cloud Guru,
+[106.04 --> 109.82]  the leader in learning for cloud Linux and other modern tech skills.
+[110.16 --> 112.62]  Hundreds of courses, thousands of hands-on labs.
+[112.72 --> 116.48]  Get certified, get hired, get learning at acloudguru.com.
+[117.02 --> 119.14]  Well, Alex, I think we should start the show today by,
+[119.38 --> 121.34]  well, maybe we started by talking about SyncThing,
+[121.44 --> 125.76]  but now we should start talking about a project in various forms, at least,
+[125.82 --> 127.96]  you've been working on for about five years.
+[128.16 --> 132.92]  And I think, if I'm not wrong, it's like about to reach its ultimate form.
+[133.32 --> 134.06]  Perhaps, yeah.
+[134.06 --> 136.58]  Well, I mean, as we record, it's still 2020,
+[136.90 --> 139.58]  but I think this is going to come out on New Year's morning.
+[139.76 --> 141.34]  So Happy New Year, everybody.
+[141.78 --> 142.74]  Welcome to 2021.
+[143.20 --> 146.12]  Hopefully, it's more prosperous than the last one was.
+[146.62 --> 149.02]  We're talking about my perfect media server project.
+[149.26 --> 152.64]  So this was something that, when I was involved with linuxserver.io,
+[152.80 --> 159.12]  that actually helped me kind of form the direction for that site
+[159.12 --> 160.60]  and the blog and stuff like that.
+[160.60 --> 169.48]  So on the 2nd of February 2016, I wrote a post about what I called the perfect media server,
+[169.66 --> 171.56]  for want of a better name, and it's kind of stuck now.
+[171.96 --> 174.70]  It's bold, but now you've kind of become the perfect media server guy.
+[174.94 --> 176.08]  Yeah, I guess so.
+[176.92 --> 179.06]  You know, I've toyed with changing the name a few times,
+[179.18 --> 181.18]  but enough people have seen it.
+[181.44 --> 182.64]  And, you know, I've looked at the analytics,
+[182.64 --> 185.88]  and a lot of people have read that post over the years.
+[187.16 --> 189.16]  In fact, funnily enough, when I moved to Raleigh,
+[189.22 --> 191.54]  one of my closest friends now, who's also called Alex,
+[192.16 --> 194.92]  he joined Linux server originally.
+[195.14 --> 196.52]  He's now one of the Linux server devs.
+[196.74 --> 200.36]  He joined that website because he read my perfect media server post.
+[200.90 --> 203.62]  And so when I came to town, like, he met up with me,
+[203.66 --> 205.90]  and we had a few beers and stuff like that.
+[205.90 --> 209.22]  And he was so excited to tell me that he'd built one as well around,
+[209.30 --> 213.68]  you know, Docker and Snap Raid and Merger FS and all this kind of stuff.
+[213.82 --> 217.72]  So it's been a really cool thing to share with the world.
+[218.26 --> 221.88]  Well, you also got a great domain name for it, perfectmediaserver.com.
+[221.98 --> 222.78]  Is that new?
+[223.12 --> 223.96]  Brand new, yes.
+[224.30 --> 228.98]  I, well, when I say brand new, I mean, I bought it in June.
+[228.98 --> 238.52]  I've been promising a 2020 version of this article for rather longer than I would like.
+[238.82 --> 243.58]  So I released one in 2016, another one in 17, and another one in 19.
+[244.06 --> 246.66]  And, you know, when you start thinking about what can I write about
+[246.66 --> 249.70]  with these perfect media servers,
+[249.96 --> 253.72]  when everything is just so reliable and just works,
+[254.78 --> 256.46]  there comes a limit when you think,
+[256.46 --> 260.10]  well, I can't really rehash the same thing again and again.
+[261.38 --> 264.78]  And so this time I was looking at the three posts.
+[265.08 --> 267.74]  And since I'm no longer involved with Linux server,
+[267.92 --> 271.06]  I don't have access to edit those blog posts easily anymore.
+[271.22 --> 273.48]  I mean, I can ask the team to fix things and stuff,
+[273.64 --> 276.32]  but invariably information goes out of date.
+[276.66 --> 280.18]  And I am a huge advocate of open source
+[280.18 --> 284.56]  and community contributions and wikis and all that kind of stuff.
+[284.56 --> 288.18]  And so I just thought that this would make much more sense
+[288.18 --> 293.38]  as a kind of a wiki type website with first class search categories,
+[293.72 --> 296.22]  walking people through how to do things,
+[296.28 --> 298.10]  you know, in a step-by-step kind of fashion,
+[298.38 --> 302.30]  and then leave the blog posts as kind of like an annual opinion piece
+[302.30 --> 305.50]  alongside this more kind of dry,
+[305.68 --> 309.80]  technical wiki style website at perfectmediaserver.com.
+[309.80 --> 311.18]  Okay, that makes a lot of sense.
+[311.74 --> 315.86]  And I think probably the real value for people to understand is
+[315.86 --> 318.64]  you're telling people there's a lot of options out there,
+[318.74 --> 320.82]  but maybe this is a great stack to use.
+[320.88 --> 321.78]  You can use this stack.
+[321.88 --> 322.60]  I've tested this.
+[322.68 --> 329.54]  I've refined it over the years to do really a beyond just okay media setup,
+[329.58 --> 330.74]  but a great home media setup.
+[330.96 --> 333.76]  And instead of saying, oh, there's so many use cases
+[333.76 --> 336.54]  or the answer, which is frequently it depends,
+[336.98 --> 338.60]  you make some opinionated decisions
+[338.60 --> 341.12]  and kind of point people in a direction
+[341.12 --> 342.34]  and then lay out how to do it.
+[342.66 --> 345.88]  And I think that's maybe, for me, the real value of the site.
+[345.88 --> 348.98]  I think as well, a lot of people come to Linux,
+[349.04 --> 350.34]  and I've said this before on the show,
+[350.94 --> 353.70]  a lot of people come to Linux not through the desktop,
+[354.14 --> 356.34]  but through Plex,
+[356.62 --> 358.90]  through running headless apps on a Synology
+[358.90 --> 360.88]  or a Raspberry Pi or something like that.
+[360.88 --> 364.54]  And once you start having a box in your house
+[364.54 --> 367.46]  that does everything 24 hours a day,
+[367.62 --> 369.16]  that is on 24 hours a day,
+[369.58 --> 370.82]  you think, what else could I do with it?
+[371.04 --> 374.04]  And that single spark is a huge rabbit hole.
+[374.20 --> 377.12]  And I think one of my primary goals with the site
+[377.12 --> 379.38]  is to equip those newer people
+[379.38 --> 383.74]  with the skills that they need to install Ubuntu,
+[384.82 --> 385.94]  set up MergerFS,
+[386.48 --> 388.16]  figure out what an FS tab is,
+[388.16 --> 391.02]  and not be intimidated by, you know,
+[391.22 --> 396.10]  wading through lots of different disparate documentation
+[396.10 --> 397.94]  across different places on the internet.
+[398.04 --> 399.22]  It's just all in one place.
+[399.88 --> 402.78]  And if you want to have multiple hard drives
+[402.78 --> 405.32]  in a single box that are of mismatched sizes
+[405.32 --> 406.80]  with different file systems,
+[407.24 --> 408.58]  well, here's a solution for you.
+[409.10 --> 410.70]  You've already got data on these drives.
+[410.78 --> 411.88]  You don't want to do RAID.
+[412.22 --> 413.04]  Great, cool.
+[413.14 --> 414.66]  Come along and join the party.
+[414.66 --> 416.62]  Yeah, and honestly,
+[416.92 --> 418.98]  it's a lot of the stack that we talk about frequently.
+[419.34 --> 420.58]  You talk about Docker,
+[420.76 --> 422.34]  kind of some of the background in there,
+[422.40 --> 423.02]  how to get it going.
+[423.34 --> 425.12]  And you work your way up through
+[425.12 --> 426.76]  how to manage multiple disks
+[426.76 --> 427.88]  of different sizes, like you say.
+[427.96 --> 428.54]  But then also,
+[429.08 --> 430.32]  if you want to go ZFS,
+[430.70 --> 433.78]  and here's also a Proxmox layer you should consider,
+[434.68 --> 436.44]  any one of those could be broken out
+[436.44 --> 438.42]  and really have nothing to do
+[438.42 --> 440.30]  with building a media server.
+[440.64 --> 442.28]  So it's kind of valuable in that way too, I suppose.
+[442.28 --> 444.00]  So I mentioned that just for the audience
+[444.00 --> 446.02]  who's not interested in building a media server,
+[446.16 --> 449.04]  but does want to learn more about Docker
+[449.04 --> 452.36]  or MergerFS or SnapRate or ZFS or Proxmox
+[452.36 --> 454.88]  or hardware, any of that kind of stack,
+[454.96 --> 456.24]  stuff we talk about on this show
+[456.24 --> 458.16]  and you want to read something from Alex on it,
+[458.68 --> 459.52]  you can find it there too.
+[459.66 --> 462.42]  And I could totally have seen a guy like me,
+[463.24 --> 465.10]  maybe if I was building my media server setup
+[465.10 --> 465.90]  for the first time,
+[466.22 --> 467.18]  I'd be thinking, okay,
+[467.24 --> 468.52]  I know I want to use containers,
+[468.70 --> 470.00]  but I don't quite know how
+[470.00 --> 472.60]  and in what way to use them to do this right.
+[473.24 --> 474.52]  I know about MergerFS,
+[474.80 --> 476.42]  but I don't know how to deploy it.
+[476.52 --> 478.62]  And so having you write something,
+[479.52 --> 481.04]  having used this stuff in production
+[481.04 --> 482.16]  for five years now,
+[482.70 --> 484.16]  there's value to that.
+[484.46 --> 486.08]  So you should be the perfect media server guy.
+[486.56 --> 487.88]  I think that's, I said good on you.
+[488.20 --> 490.02]  You be the perfect media server guy
+[490.02 --> 492.84]  because I endorse this media server build here.
+[492.94 --> 494.80]  You are, Chris, and you support this message.
+[495.04 --> 496.08]  I wonder what the cost is.
+[496.12 --> 496.92]  Have you thought about that?
+[496.92 --> 499.44]  Have you thought about like what the cost would be
+[499.44 --> 502.38]  for a minimal build of something from this guide?
+[502.64 --> 503.58]  Well, in terms of hardware?
+[504.60 --> 505.58]  Yeah, in terms of hardware.
+[506.00 --> 507.66]  I think QuickSync now for me
+[507.66 --> 509.50]  is a minimum price of entry
+[509.50 --> 511.54]  after everything we talked about in the last episode.
+[512.24 --> 515.04]  So a hundred bucks for a CPU.
+[515.76 --> 517.32]  You can probably find a used motherboard
+[517.32 --> 518.82]  that will do the trick for a hundred dollars.
+[519.02 --> 520.74]  Again, RAM is about a hundred.
+[521.44 --> 522.66]  And then hard drives.
+[522.74 --> 524.00]  For an eight terabyte hard drive now,
+[524.00 --> 525.30]  you can go to Best Buy and pick one up
+[525.30 --> 528.14]  for around 130, 140.
+[528.58 --> 529.86]  So I don't know.
+[529.92 --> 531.86]  Let's say 140.
+[532.88 --> 533.42]  What's that?
+[533.50 --> 537.14]  It's like $1,100 or so for hard drives.
+[538.06 --> 538.86]  I don't know, $1,500.
+[539.60 --> 541.44]  I think all in would get you
+[541.44 --> 543.58]  five, eight terabyte drives
+[543.58 --> 545.00]  of 40 terabytes of storage
+[545.00 --> 548.28]  for $1,500 all in.
+[548.28 --> 550.92]  And you own it forever.
+[551.68 --> 552.54]  It's, you know, you're not,
+[553.40 --> 555.10]  I mean, Synology make a great product.
+[555.20 --> 557.68]  So do QNAP and Unraid's also great,
+[557.78 --> 558.82]  but it's not open source.
+[559.68 --> 562.50]  Free NAS requires learning ZFS,
+[563.16 --> 565.72]  which I know I talk about in Perfect Media Server,
+[565.82 --> 569.94]  but it's kind of orthogonal to the main content.
+[570.06 --> 571.82]  It's not required learning.
+[571.98 --> 574.44]  Whereas with a True NAS or a Free NAS product,
+[574.66 --> 575.24]  it is.
+[575.24 --> 578.50]  It's just the most flexible thing for most people.
+[578.64 --> 581.32]  And I think when you start looking at
+[581.32 --> 582.86]  putting together one of these servers,
+[583.00 --> 585.80]  $1,500 isn't a small upfront investment.
+[586.00 --> 586.50]  And you think, right,
+[586.56 --> 587.84]  well, where can I cut some costs?
+[587.94 --> 590.64]  And the obvious answer is the hard drives.
+[591.06 --> 592.60]  You know, rather than buying five,
+[592.70 --> 594.58]  let's only buy a couple, right?
+[594.60 --> 596.90]  And then I'll add the other three
+[596.90 --> 598.12]  over the next year or two.
+[598.90 --> 600.20]  MergerFS lets me do that.
+[600.28 --> 603.40]  It lets me add drives as my collection grows
+[603.40 --> 607.60]  without having to re-silver a ZFS array
+[607.60 --> 611.40]  or rebuild a RAID setup or anything like that.
+[611.44 --> 613.36]  It just grows as I do,
+[613.42 --> 614.66]  and it changes and matures.
+[615.00 --> 616.66]  And because it's just Linux,
+[617.00 --> 620.16]  it's open and I can go and tinker
+[620.16 --> 621.52]  as deep as I want under the hood.
+[621.90 --> 623.40]  Or again, because it's Linux,
+[623.56 --> 624.96]  it will just work.
+[625.04 --> 625.76]  It's just reliable.
+[626.02 --> 628.16]  It's battle-tested and hardened everywhere.
+[628.16 --> 632.58]  So I really do think that if you're willing
+[632.58 --> 636.34]  to put the time in and learn a little bit of this stuff
+[636.34 --> 638.92]  with the information that's provided here for you,
+[639.12 --> 640.10]  for free, I might add,
+[640.14 --> 641.76]  I don't make a penny off of this stuff.
+[642.20 --> 643.62]  Anyway, I never have.
+[643.68 --> 644.90]  I just wanted to give this information
+[644.90 --> 645.90]  back to the community.
+[646.76 --> 648.72]  I don't think there's a better solution, really,
+[648.80 --> 650.12]  if you're willing to put the effort in.
+[650.92 --> 652.44]  And I'll just give one more mention,
+[652.76 --> 654.14]  because as you were talking there,
+[654.14 --> 656.30]  I was just also reviewing your QuickSync
+[656.30 --> 657.68]  and Proxmox page.
+[658.18 --> 659.98]  And damn, you put some work into this.
+[660.46 --> 662.38]  But I also, I think it's pretty clever
+[662.38 --> 665.18]  that you embedded the relevant JB content
+[665.18 --> 667.42]  where we've talked about a lot of this stuff in depth
+[667.42 --> 668.96]  when it still holds up.
+[669.04 --> 671.76]  So not only do you get a lot of the written stuff
+[671.76 --> 672.72]  and the visual examples,
+[672.88 --> 675.26]  but you've got a video from Wendell in here too.
+[675.44 --> 678.14]  And so you add the supplemental media content.
+[678.94 --> 682.48]  I could see us linking this to a lot of people
+[682.48 --> 684.16]  that write into the show and ask questions
+[684.16 --> 684.96]  about this stuff.
+[685.78 --> 687.58]  If I were going to contribute one area,
+[687.68 --> 688.68]  I just thought to troll you,
+[688.74 --> 690.40]  I'd probably contribute using ButterFS.
+[690.96 --> 693.96]  Because literally everything you just said
+[693.96 --> 696.44]  about MergerFS is why I use ButterFS.
+[698.14 --> 699.50]  Seriously, like word for word.
+[699.76 --> 702.62]  So on the ZFS page,
+[702.76 --> 705.28]  there's a whole section about what about ButterFS.
+[706.72 --> 708.20]  Okay, good.
+[708.24 --> 709.24]  You've addressed it, I can see.
+[709.76 --> 711.12]  Well, a little bit.
+[711.12 --> 714.14]  And my conclusion was that using ButterFS
+[714.14 --> 717.06]  would probably be easier than ZFS
+[717.06 --> 720.08]  simply because it's shipped as part of the Linux kernel.
+[720.34 --> 724.02]  But I've invested in ZFS mentally,
+[724.20 --> 727.32]  but also I've synced six,
+[727.46 --> 730.82]  seven terabytes worth of data across the ocean to the UK.
+[731.36 --> 733.14]  And I don't want to have to spend another
+[733.14 --> 736.58]  six or seven weeks doing that again if I switch.
+[736.92 --> 738.80]  Well, ironically, it's more about
+[738.80 --> 740.48]  it's more about how you use MergerFS.
+[741.00 --> 742.92]  However, I think, you know, both are gray.
+[743.02 --> 744.72]  And if MergerFS is working for you,
+[745.52 --> 747.16]  I'm not, I will really not, I'm just more teasing.
+[747.64 --> 749.22]  But it did strike me
+[749.22 --> 752.08]  that being able to join mismatched disks
+[752.08 --> 753.66]  and add them as it grows
+[753.66 --> 755.06]  and be able to remove them easily
+[755.06 --> 757.74]  is why I switched to using ButterFS
+[757.74 --> 759.26]  on my Raspberry Pi media servers.
+[759.26 --> 760.36]  Because I needed something
+[760.36 --> 762.54]  that essentially was no cost.
+[762.54 --> 764.74]  Since ButterFS is built into the kernel
+[764.74 --> 767.18]  and it also doesn't have a high,
+[767.28 --> 768.86]  it's a very efficient file system.
+[768.94 --> 770.10]  There's not a big performance penalty.
+[770.24 --> 771.24]  I don't need a lot of RAM.
+[771.94 --> 773.04]  It meant that I didn't have to install
+[773.04 --> 775.28]  any additional software at all.
+[775.62 --> 778.50]  And actually no additional config files or anything.
+[778.74 --> 779.40]  There's no config.
+[779.50 --> 781.86]  It's just, it's all just with volume management
+[781.86 --> 782.74]  on the command line.
+[782.82 --> 783.72]  And it's very simple.
+[783.84 --> 785.92]  It's like ButterFS add volume
+[785.92 --> 786.86]  and you give it the path
+[786.86 --> 788.16]  and you tell it what volume to add to
+[788.16 --> 789.02]  and boom, you're done.
+[789.22 --> 789.76]  And then remove.
+[789.76 --> 790.90]  And as long as you have enough space,
+[790.98 --> 791.80]  it sinks everything off
+[791.80 --> 792.56]  and you can remove it.
+[792.76 --> 794.68]  And I actually have not tested that.
+[794.80 --> 796.14]  I could imagine it being tricky.
+[796.66 --> 797.66]  But I think, you know,
+[797.76 --> 799.60]  it's, there's different ways
+[799.60 --> 800.56]  to solve all of these.
+[800.72 --> 802.36]  And what you've done here with this
+[802.36 --> 803.66]  is said, well, these are ways
+[803.66 --> 807.36]  that not only are very sensible solutions,
+[807.36 --> 808.32]  but ones that I've tested.
+[808.74 --> 810.04]  And that's the value again.
+[810.12 --> 811.24]  Like, yeah, I could add something
+[811.24 --> 811.84]  about ButterFS,
+[812.18 --> 815.12]  but there's limited value in it.
+[815.22 --> 816.44]  You know, it's my experience.
+[816.98 --> 817.80]  And this is something
+[817.80 --> 819.16]  that you've worked at for a long time.
+[819.16 --> 820.70]  So I think it's, yeah,
+[820.88 --> 822.20]  I think MurderFS is a great solution
+[822.20 --> 823.00]  for that kind of stuff.
+[823.12 --> 824.68]  And, you know, things like ZFS
+[824.68 --> 825.44]  and SnapRaid,
+[825.54 --> 827.12]  depending on what your needs are,
+[827.16 --> 828.84]  also can be appropriate solutions.
+[829.44 --> 830.30]  So I've built this site
+[830.30 --> 831.16]  around MKDocs,
+[831.74 --> 834.02]  which happens to be the same project
+[834.02 --> 835.02]  that we're using
+[835.02 --> 836.14]  for the self-hosted wiki,
+[836.26 --> 837.56]  which I've also put some work
+[837.56 --> 838.36]  into this week
+[838.36 --> 840.06]  over the Christmas break.
+[840.48 --> 841.66]  So please go ahead
+[841.66 --> 843.34]  and contribute to the self-hosted wiki
+[843.34 --> 845.14]  at wiki.selfhosted.show
+[845.14 --> 846.92]  because we're crying out
+[846.92 --> 847.94]  for content over there.
+[847.94 --> 850.14]  But MKDocs,
+[850.20 --> 851.04]  I'll tell you what, Chris,
+[851.16 --> 854.70]  has become a hell of a wiki software,
+[855.02 --> 855.32]  you know?
+[855.64 --> 856.16]  So I don't know
+[856.16 --> 857.02]  when you're browsing this,
+[857.08 --> 858.16]  but I don't know if you noticed
+[858.16 --> 859.30]  it has a keyboard shortcut.
+[859.58 --> 860.38]  And they don't tell you this,
+[860.44 --> 860.62]  obviously,
+[860.72 --> 862.00]  but it's the same as Vim.
+[862.40 --> 864.80]  So you can press the forward slash key,
+[865.00 --> 866.38]  which brings up search,
+[866.52 --> 867.50]  and then you can search
+[867.50 --> 869.00]  for any string in any page.
+[869.18 --> 870.06]  And it will just,
+[870.30 --> 870.98]  in real time,
+[871.06 --> 872.12]  and then use the arrow keys.
+[872.28 --> 873.08]  Oh, yes.
+[873.08 --> 874.58]  And it will just take you straight
+[874.58 --> 876.10]  to the section of that page.
+[876.22 --> 877.36]  Just that feature alone
+[877.36 --> 878.64]  had me sold.
+[878.88 --> 879.02]  Huh.
+[879.64 --> 880.16]  That's great.
+[880.22 --> 881.02]  But they've added dozens
+[881.02 --> 881.88]  of other features,
+[882.30 --> 882.52]  you know,
+[882.60 --> 884.04]  like they've got little tool tips,
+[884.50 --> 885.62]  little info boxes,
+[885.62 --> 887.42]  and stuff that breaks up the content.
+[888.06 --> 889.76]  The code formatting,
+[890.02 --> 890.44]  highlighting,
+[890.84 --> 892.04]  is just brilliant.
+[892.82 --> 894.22]  It's fully customizable.
+[894.22 --> 896.00]  So, you know,
+[896.26 --> 898.30]  it was using the COBOL wiki
+[898.30 --> 899.82]  for the Helios 64 review,
+[899.98 --> 900.86]  which finally got me
+[900.86 --> 903.58]  to really take MKDocs seriously
+[903.58 --> 905.82]  and really went through
+[905.82 --> 906.34]  the documentation
+[906.34 --> 907.66]  with a fine tooth comb.
+[907.84 --> 908.80]  And I've enabled
+[908.80 --> 909.96]  all the features that I want.
+[910.16 --> 910.84]  And the only thing
+[910.84 --> 912.16]  I haven't done yet is comments,
+[912.38 --> 913.94]  which I might do.
+[914.02 --> 914.48]  I might not.
+[914.56 --> 915.46]  I haven't decided yet.
+[915.98 --> 918.24]  But the material theme
+[918.24 --> 920.72]  for MKDocs really is stunning.
+[921.08 --> 923.36]  And I don't think at the moment
+[923.36 --> 924.74]  there's a better open source
+[924.74 --> 926.88]  documentation platform.
+[927.48 --> 928.04]  Yeah, I will say
+[928.04 --> 929.26]  that just the presentation,
+[929.54 --> 930.52]  so not even commenting
+[930.52 --> 931.04]  on what it's like
+[931.04 --> 932.62]  to actually write on it,
+[932.66 --> 933.28]  but the presentation
+[933.28 --> 935.48]  is extremely readable.
+[936.26 --> 936.82]  You know, documentation,
+[937.14 --> 938.32]  especially something
+[938.32 --> 939.86]  as extensive as a topic like this,
+[939.92 --> 941.08]  can be just a chore
+[941.08 --> 941.76]  to get through.
+[942.18 --> 943.40]  But the way it lays out,
+[943.46 --> 943.90]  like you said,
+[943.94 --> 944.44]  the way it does
+[944.44 --> 945.42]  some of the different quoting
+[945.42 --> 946.92]  and code blocks
+[946.92 --> 948.14]  and all of it,
+[948.26 --> 950.02]  just all of it is really,
+[950.10 --> 950.40]  it's just,
+[950.50 --> 951.42]  it makes me want to use it
+[951.42 --> 951.94]  for my stuff.
+[951.94 --> 953.02]  So I was going to ask you,
+[953.02 --> 953.66]  I was going to talk to you
+[953.66 --> 954.24]  about MKDocs
+[954.24 --> 954.86]  and see what you thought
+[954.86 --> 956.70]  because, yeah,
+[956.78 --> 957.72]  it really seems impressive
+[957.72 --> 960.86]  and probably the perfect solution
+[960.86 --> 963.88]  for just JB internal documentation.
+[964.38 --> 964.66]  Yeah, I mean,
+[964.80 --> 965.28]  it's all,
+[965.50 --> 966.68]  everything's written in Markdown.
+[967.52 --> 968.96]  So if in the future
+[968.96 --> 969.80]  you decided to use
+[969.80 --> 970.64]  a different solution
+[970.64 --> 971.34]  for some reason,
+[972.14 --> 973.24]  it's just plain text.
+[973.34 --> 974.94]  It's not in a CMS somewhere.
+[975.46 --> 976.40]  It lives in a Git repo.
+[976.90 --> 978.14]  You can just copy and paste
+[978.14 --> 978.70]  and job done.
+[979.08 --> 979.84]  That's pretty nice.
+[980.22 --> 981.94]  Well, so as we record right now,
+[981.94 --> 983.64]  this isn't live.
+[983.90 --> 985.26]  So what's your plan?
+[985.30 --> 985.86]  I assume you're going to try
+[985.86 --> 986.36]  to get it out
+[986.36 --> 987.62]  when the show goes live.
+[988.12 --> 989.06]  If you look at my GitHub
+[989.06 --> 990.42]  commit history this week,
+[990.42 --> 991.90]  it's going to be bright green.
+[992.30 --> 992.70]  Yeah.
+[993.42 --> 994.92]  I'm working away feverishly
+[994.92 --> 995.66]  on this to get it done
+[995.66 --> 996.42]  by the end of 2020.
+[996.84 --> 998.12]  So I'm aiming
+[998.12 --> 999.46]  for a New Year's Eve launch.
+[999.56 --> 1000.34]  So by the time you listen
+[1000.34 --> 1000.98]  to this episode,
+[1001.06 --> 1001.86]  it should be live.
+[1002.58 --> 1003.38]  PerfectMediaServer.com.
+[1003.50 --> 1004.32]  Let me know what you think
+[1004.32 --> 1005.74]  at IronicBadger on Twitter.
+[1005.74 --> 1007.96]  I would love to hear
+[1007.96 --> 1008.38]  what you think
+[1008.38 --> 1009.58]  because I've put a lot of time,
+[1010.04 --> 1011.20]  probably several hundred hours
+[1011.20 --> 1012.60]  into this site
+[1012.60 --> 1013.24]  by the end of it,
+[1013.42 --> 1014.14]  all told.
+[1014.76 --> 1016.08]  I'd also accept PRs
+[1016.08 --> 1016.84]  on the GitHub repo.
+[1016.98 --> 1017.86]  So if you want to open an issue,
+[1017.94 --> 1018.72]  if you find a mistake
+[1018.72 --> 1019.82]  or something,
+[1019.96 --> 1021.08]  which is highly likely
+[1021.08 --> 1021.54]  at the pace
+[1021.54 --> 1022.44]  I'm working right now,
+[1023.18 --> 1023.62]  let me know
+[1023.62 --> 1024.46]  through a GitHub issue
+[1024.46 --> 1025.44]  or open a pull request
+[1025.44 --> 1025.80]  or something.
+[1025.88 --> 1026.78]  I would love to hear from you.
+[1026.78 --> 1027.18]  Okay.
+[1027.58 --> 1032.42]  Needs more ButterFS documentation.
+[1033.20 --> 1033.64]  Serious.
+[1033.64 --> 1034.52]  Seriously.
+[1035.26 --> 1035.74]  Jeez.
+[1037.88 --> 1038.74]  You, sir,
+[1038.86 --> 1040.54]  are a grade A troll.
+[1040.74 --> 1041.18]  Thank you.
+[1043.56 --> 1044.66]  Linode.com
+[1044.66 --> 1045.86]  slash SSH.
+[1045.96 --> 1046.24]  Go there
+[1046.24 --> 1047.50]  to get a $100
+[1047.50 --> 1048.90]  60-day credit
+[1048.90 --> 1049.68]  towards a new account
+[1049.68 --> 1050.76]  and go there
+[1050.76 --> 1051.54]  to support the show.
+[1051.94 --> 1052.68]  Linode is our
+[1052.68 --> 1053.78]  cloud hosting provider
+[1053.78 --> 1054.84]  and because the price
+[1054.84 --> 1055.32]  is so great,
+[1055.44 --> 1056.40]  they can make it possible
+[1056.40 --> 1058.24]  for you to use Linode
+[1058.24 --> 1059.60]  even for a small deployment
+[1059.60 --> 1061.06]  or for a large deployment.
+[1061.68 --> 1062.44]  Jeff used Linode
+[1062.44 --> 1063.26]  to test migrate
+[1063.26 --> 1063.82]  his important
+[1063.82 --> 1064.72]  NextCloud setup.
+[1065.10 --> 1066.04]  He just took things
+[1066.04 --> 1067.24]  one step at a time
+[1067.24 --> 1068.26]  using different guides
+[1068.26 --> 1068.74]  on Linode
+[1068.74 --> 1069.24]  to make sure
+[1069.24 --> 1070.10]  everything was right
+[1070.10 --> 1071.48]  and he says
+[1071.48 --> 1072.36]  eventually after about
+[1072.36 --> 1073.32]  three pages of notes
+[1073.32 --> 1074.80]  he did a completed
+[1074.80 --> 1076.26]  successful migration
+[1076.26 --> 1077.46]  and then he was able
+[1077.46 --> 1078.84]  to take that knowledge,
+[1079.52 --> 1080.76]  take that hands-on experience
+[1080.76 --> 1083.62]  and go actually implement it
+[1083.62 --> 1084.28]  on his production
+[1084.28 --> 1085.12]  NextCloud instance.
+[1085.50 --> 1085.70]  He said,
+[1085.78 --> 1086.36]  but in the testing
+[1086.36 --> 1087.32]  he noticed that
+[1087.32 --> 1090.26]  even their smaller Linodes
+[1090.26 --> 1091.98]  were still faster
+[1091.98 --> 1092.68]  than his local
+[1092.68 --> 1093.30]  quad-core
+[1093.30 --> 1094.12]  16-gigabyte
+[1094.12 --> 1094.86]  local machine.
+[1096.14 --> 1098.14]  So he's looking at
+[1098.14 --> 1098.92]  maybe just hosting it
+[1098.92 --> 1099.92]  on Linode.com
+[1099.92 --> 1100.94]  And Alex,
+[1101.04 --> 1102.06]  I know that you're using
+[1102.06 --> 1102.52]  Linode for
+[1102.52 --> 1103.86]  the perfectmediaserver.com
+[1103.86 --> 1105.10]  I sure am, yeah.
+[1105.32 --> 1106.64]  Same node as
+[1106.64 --> 1107.54]  is doing the wiki
+[1107.54 --> 1109.94]  and gallery.selfhosted.show
+[1109.94 --> 1111.18]  is doing
+[1111.18 --> 1112.74]  perfectmediaserver.com
+[1112.74 --> 1114.40]  So you can really squeeze
+[1114.40 --> 1114.92]  quite a lot
+[1114.92 --> 1115.84]  out of these little things.
+[1115.84 --> 1116.94]  I love hearing
+[1116.94 --> 1118.02]  how people are using
+[1118.02 --> 1118.58]  Linode.
+[1118.72 --> 1119.56]  So do let me know
+[1119.56 --> 1120.82]  either at the contact
+[1120.82 --> 1121.98]  forum or at Chris Lass
+[1121.98 --> 1122.62]  on Twitter
+[1122.62 --> 1124.08]  because with $5
+[1124.08 --> 1125.14]  a month rigs
+[1125.14 --> 1125.96]  you can do a lot
+[1125.96 --> 1127.56]  but they also have
+[1127.56 --> 1129.60]  dedicated CPU systems
+[1129.60 --> 1130.30]  or machines
+[1130.30 --> 1131.30]  with tons of RAM
+[1131.30 --> 1132.44]  or lots of GPU
+[1132.44 --> 1133.72]  so go experiment
+[1133.72 --> 1134.50]  with that $100
+[1134.50 --> 1135.56]  60-day credit.
+[1135.98 --> 1136.66]  They also offer
+[1136.66 --> 1138.14]  S3 object storage.
+[1138.50 --> 1139.42]  This is a great way
+[1139.42 --> 1140.18]  to store things
+[1140.18 --> 1140.84]  in the cloud
+[1140.84 --> 1142.00]  that don't need
+[1142.00 --> 1142.48]  a Linode
+[1142.48 --> 1142.94]  or a server
+[1142.94 --> 1143.70]  sitting in front of them.
+[1143.76 --> 1144.34]  You can just generate
+[1144.34 --> 1145.00]  a public URL
+[1145.00 --> 1145.72]  for that asset.
+[1146.24 --> 1146.74]  I do this
+[1146.74 --> 1147.66]  for soundboard clips
+[1147.66 --> 1148.66]  you can do this
+[1148.66 --> 1149.22]  for websites
+[1149.22 --> 1150.04]  it's a great way
+[1150.04 --> 1151.00]  to get a super fast
+[1151.00 --> 1151.60]  portfolio
+[1151.60 --> 1152.60]  where everything's
+[1152.60 --> 1153.30]  stored statically
+[1153.30 --> 1154.16]  in object storage
+[1154.16 --> 1155.06]  and their prices
+[1155.06 --> 1155.52]  are great.
+[1155.80 --> 1156.22]  They also have
+[1156.22 --> 1156.96]  load balancers
+[1156.96 --> 1157.26]  and they have
+[1157.26 --> 1157.82]  data centers
+[1157.82 --> 1159.00]  in 11 locations
+[1159.00 --> 1159.76]  around the world.
+[1160.48 --> 1160.88]  So you're going to
+[1160.88 --> 1161.38]  find something
+[1161.38 --> 1161.90]  close to you
+[1161.90 --> 1163.30]  or close to your client.
+[1163.86 --> 1164.18]  So go to
+[1164.18 --> 1165.08]  linode.com
+[1165.08 --> 1166.32]  slash SSH
+[1166.32 --> 1167.06]  go there
+[1167.06 --> 1168.00]  get that $100
+[1168.00 --> 1169.00]  60-day credit
+[1169.00 --> 1169.94]  apply that towards
+[1169.94 --> 1170.44]  a new account
+[1170.44 --> 1171.56]  and go there
+[1171.56 --> 1172.30]  to support the show.
+[1172.82 --> 1173.92]  You help make
+[1173.92 --> 1175.08]  independent content
+[1175.08 --> 1175.58]  like this
+[1175.58 --> 1175.86]  free
+[1175.86 --> 1176.68]  when you go to
+[1176.68 --> 1177.44]  linode.com
+[1177.44 --> 1178.86]  slash SSH.
+[1178.86 --> 1181.96]  I can't quite believe
+[1181.96 --> 1182.64]  just how many
+[1182.64 --> 1183.48]  powerline emails
+[1183.48 --> 1184.30]  we had this week
+[1184.30 --> 1184.86]  though can you?
+[1185.68 --> 1186.74]  Alex it was
+[1186.74 --> 1187.62]  wild.
+[1187.88 --> 1188.66]  So I responded
+[1188.66 --> 1189.74]  to several of them
+[1189.74 --> 1190.16]  directly.
+[1190.32 --> 1190.96]  I figured we respond
+[1190.96 --> 1191.56]  to a couple here
+[1191.56 --> 1192.14]  in the show
+[1192.14 --> 1193.34]  when we had a few
+[1193.34 --> 1193.88]  people write in
+[1193.88 --> 1194.60]  about this stuff.
+[1194.60 --> 1196.24]  I kind of suspected
+[1196.24 --> 1197.04]  that powerline
+[1197.04 --> 1197.64]  networking was
+[1197.64 --> 1198.44]  probably something
+[1198.44 --> 1200.88]  that got more
+[1200.88 --> 1202.62]  use and deployments
+[1202.62 --> 1205.28]  than kind of
+[1205.28 --> 1206.32]  gets representation
+[1206.32 --> 1207.16]  because there's so
+[1207.16 --> 1208.06]  many scenarios
+[1208.06 --> 1209.60]  where Wi-Fi
+[1209.60 --> 1210.64]  just doesn't work
+[1210.64 --> 1212.36]  especially older
+[1212.36 --> 1213.08]  style Wi-Fi
+[1213.08 --> 1213.98]  non-mesh Wi-Fi
+[1213.98 --> 1214.90]  where like
+[1214.90 --> 1215.90]  either a house
+[1215.90 --> 1217.48]  construction materials
+[1217.48 --> 1218.08]  involved
+[1218.08 --> 1219.30]  or distance
+[1219.30 --> 1220.98]  or all kinds
+[1220.98 --> 1221.64]  of weird things.
+[1221.64 --> 1223.58]  I have a family
+[1223.58 --> 1224.28]  member who's
+[1224.28 --> 1225.04]  next to an airport
+[1225.04 --> 1226.32]  and their
+[1226.32 --> 1227.22]  radio signal
+[1227.22 --> 1228.12]  situation is just
+[1228.12 --> 1228.50]  crazy.
+[1229.02 --> 1229.48]  It's just
+[1229.48 --> 1230.82]  unusable.
+[1231.58 --> 1231.98]  So I
+[1231.98 --> 1233.14]  suspected
+[1233.14 --> 1234.00]  we would hear
+[1234.00 --> 1234.90]  a lot about this
+[1234.90 --> 1236.86]  but JT wrote in
+[1236.86 --> 1237.50]  to say that he's
+[1237.50 --> 1238.02]  been using
+[1238.02 --> 1238.82]  powerline adapters
+[1238.82 --> 1239.76]  for a couple of years.
+[1240.38 --> 1241.26]  He currently has
+[1241.26 --> 1241.94]  three of the
+[1241.94 --> 1243.34]  TP-Link AV1000s
+[1243.34 --> 1243.88]  which is the kit
+[1243.88 --> 1244.28]  I bought
+[1244.28 --> 1246.06]  with two different kits
+[1246.06 --> 1246.84]  and he's using them
+[1246.84 --> 1247.50]  without any issues.
+[1247.62 --> 1247.90]  So he bought
+[1247.90 --> 1248.74]  two of the kits
+[1248.74 --> 1249.70]  two of what I have
+[1249.70 --> 1250.40]  and they all
+[1250.40 --> 1251.00]  link together.
+[1251.00 --> 1251.90]  He says I do
+[1251.90 --> 1252.32]  have a problem
+[1252.32 --> 1252.78]  with one of the
+[1252.78 --> 1253.36]  rooms though
+[1253.36 --> 1254.34]  where one adapter
+[1254.34 --> 1255.00]  normally gets about
+[1255.00 --> 1256.16]  120 megabits
+[1256.16 --> 1257.64]  and then it gets
+[1257.64 --> 1258.18]  out of sync
+[1258.18 --> 1258.84]  and it starts
+[1258.84 --> 1259.80]  dropping packets
+[1259.80 --> 1260.42]  like mad
+[1260.42 --> 1261.16]  dropping the
+[1261.16 --> 1261.98]  bandwidth next to
+[1261.98 --> 1262.40]  nothing
+[1262.40 --> 1263.06]  sometimes even
+[1263.06 --> 1263.54]  less than a
+[1263.54 --> 1263.98]  megabit
+[1263.98 --> 1264.78]  but if I
+[1264.78 --> 1265.22]  unplug and
+[1265.22 --> 1265.72]  replug them
+[1265.72 --> 1266.14]  back in
+[1266.14 --> 1266.62]  it seems to
+[1266.62 --> 1267.00]  fix it.
+[1267.36 --> 1268.12]  It happens
+[1268.12 --> 1268.46]  from time
+[1268.46 --> 1268.94]  to time
+[1268.94 --> 1270.12]  but also
+[1270.12 --> 1270.60]  I wanted to
+[1270.60 --> 1270.96]  give just a
+[1270.96 --> 1271.52]  quick shout out
+[1271.52 --> 1272.68]  to cloudfree.shop
+[1272.68 --> 1273.38]  one of our
+[1273.38 --> 1274.14]  official unofficial
+[1274.14 --> 1274.86]  sponsors here
+[1274.86 --> 1276.06]  of the self-hosted
+[1276.06 --> 1276.54]  podcast.
+[1277.00 --> 1277.38]  Coupon code
+[1277.38 --> 1278.04]  self-hosted.
+[1278.32 --> 1278.54]  He said
+[1278.54 --> 1279.42]  cloudfree.shop
+[1279.42 --> 1281.02]  finally gave him
+[1281.02 --> 1281.88]  the kick in the
+[1281.88 --> 1282.56]  butt he needed
+[1282.56 --> 1283.48]  to begin automating
+[1283.48 --> 1283.92]  his home.
+[1284.44 --> 1284.64]  He says
+[1284.64 --> 1285.10]  I never want
+[1285.10 --> 1285.52]  anything really
+[1285.52 --> 1286.04]  connected to the
+[1286.04 --> 1286.56]  cloud and with
+[1286.56 --> 1287.20]  smart plugs from
+[1287.20 --> 1288.16]  cloudfree and
+[1288.16 --> 1288.68]  home assistant
+[1288.68 --> 1289.66]  I felt like I
+[1289.66 --> 1290.22]  could finally get
+[1290.22 --> 1290.56]  started.
+[1291.06 --> 1291.68]  The first thing
+[1291.68 --> 1292.42]  that I automated
+[1292.42 --> 1293.64]  was my bearded
+[1293.64 --> 1294.50]  dragon's cage
+[1294.50 --> 1294.84]  lights.
+[1295.38 --> 1295.62]  Yep.
+[1295.74 --> 1296.24]  One of the first
+[1296.24 --> 1296.80]  things I automated
+[1296.80 --> 1297.32]  here in the studio
+[1297.32 --> 1298.22]  was my fish tank
+[1298.22 --> 1299.16]  lights so totally
+[1299.16 --> 1299.86]  totally with you
+[1299.86 --> 1300.16]  JT.
+[1300.58 --> 1301.08]  He says
+[1301.08 --> 1302.22]  which got rid of
+[1302.22 --> 1302.80]  a terrible
+[1302.80 --> 1303.84]  constantly clicking
+[1303.84 --> 1304.70]  analog timer that
+[1304.70 --> 1305.40]  I used to use.
+[1305.40 --> 1306.68]  I also bought a
+[1306.68 --> 1308.76]  D1 mini ESP8266
+[1308.76 --> 1310.02]  Wi-Fi board and
+[1310.02 --> 1311.54]  a BME280 temperature
+[1311.54 --> 1312.44]  pressure and
+[1312.44 --> 1313.86]  humidity sensor and
+[1313.86 --> 1314.70]  combined them into
+[1314.70 --> 1315.98]  an MQTT based
+[1315.98 --> 1316.80]  sensor that home
+[1316.80 --> 1317.78]  assistant uses to
+[1317.78 --> 1318.48]  control the heat
+[1318.48 --> 1319.40]  lamp in the cage.
+[1319.50 --> 1320.62]  Heck yeah he did.
+[1321.88 --> 1322.68]  That's great.
+[1322.72 --> 1323.42]  That's next level.
+[1323.82 --> 1324.74]  Talk about like you
+[1324.74 --> 1327.30]  want a backup no
+[1327.30 --> 1328.14]  fail state for that
+[1328.14 --> 1328.36]  thing.
+[1328.76 --> 1329.42]  He says the
+[1329.42 --> 1330.36]  spousal approval
+[1330.36 --> 1331.98]  factor was very high
+[1331.98 --> 1333.00]  on these purchases
+[1333.00 --> 1334.46]  and the time I
+[1334.46 --> 1335.48]  spent learning to
+[1335.48 --> 1336.22]  solder.
+[1337.06 --> 1337.66]  That's great.
+[1337.74 --> 1338.26]  Says thanks for the
+[1338.26 --> 1338.92]  shows looking forward
+[1338.92 --> 1339.52]  to the next one.
+[1339.90 --> 1340.60]  Good to hear that
+[1340.60 --> 1340.96]  JT.
+[1341.06 --> 1341.62]  I love it when it
+[1341.62 --> 1342.76]  works out and yeah
+[1342.76 --> 1343.80]  for those of you who
+[1343.80 --> 1344.54]  are new to the show
+[1344.54 --> 1346.28]  cloudfree.shop is a
+[1346.28 --> 1347.20]  community built store
+[1347.20 --> 1349.50]  and we're official
+[1349.50 --> 1350.40]  unofficial official
+[1350.40 --> 1351.52]  sponsors or they are
+[1351.52 --> 1353.06]  we just love them and
+[1353.06 --> 1354.26]  we worked out a deal
+[1354.26 --> 1355.24]  when you use the
+[1355.24 --> 1356.42]  promo code and you
+[1356.42 --> 1357.34]  get devices that
+[1357.34 --> 1358.84]  don't have like the
+[1358.84 --> 1359.74]  cloud connected stuff
+[1359.74 --> 1360.16]  on there.
+[1360.64 --> 1361.34]  You know sometimes I
+[1361.34 --> 1362.02]  like a little cloud
+[1362.02 --> 1362.70]  like I put a sync
+[1362.70 --> 1363.34]  things over up in
+[1363.34 --> 1364.30]  the cloud made
+[1364.30 --> 1365.68]  stuff faster but
+[1365.68 --> 1366.84]  the smart plug that
+[1366.84 --> 1367.76]  controls the old fish
+[1367.76 --> 1368.70]  tank I don't want any
+[1368.70 --> 1369.40]  cloud involved with
+[1369.40 --> 1370.34]  that you know it's
+[1370.34 --> 1371.66]  just how it goes.
+[1372.68 --> 1373.16]  And you also don't
+[1373.16 --> 1373.68]  have to wait
+[1373.68 --> 1374.42]  necessarily on the
+[1374.42 --> 1375.02]  slow boat from
+[1375.02 --> 1376.16]  China sometimes for
+[1376.16 --> 1376.68]  these things to
+[1376.68 --> 1377.38]  arrive so.
+[1377.66 --> 1378.42]  True true.
+[1378.66 --> 1379.52]  It is nice that they
+[1379.52 --> 1380.56]  are stateside as well.
+[1380.90 --> 1381.86]  Yeah that's good
+[1381.86 --> 1382.50]  that's a good point.
+[1383.78 --> 1385.22]  Ro wrote in about
+[1385.22 --> 1386.48]  Powerline Finicky and
+[1386.48 --> 1387.22]  I think the reason I
+[1387.22 --> 1388.40]  included his email is
+[1388.40 --> 1389.30]  because he referred to
+[1389.30 --> 1390.80]  us as Chris and the
+[1390.80 --> 1392.68]  Badger which I
+[1392.70 --> 1395.00]  which gave me like
+[1395.00 --> 1398.50]  this morning AM or
+[1398.50 --> 1400.36]  FM radio vibe and I
+[1400.36 --> 1401.14]  just pictured you and
+[1401.14 --> 1402.42]  I doing a morning
+[1402.42 --> 1405.44]  KWRAX Chris and the
+[1405.44 --> 1406.48]  Badger yeah I can I
+[1406.48 --> 1407.14]  can hear it now.
+[1407.34 --> 1407.80]  It's Chris and the
+[1407.80 --> 1408.16]  Badger.
+[1409.76 --> 1410.64]  Welcome to Chris and
+[1410.64 --> 1411.04]  the Badger.
+[1411.18 --> 1411.68]  Chris and the Badger.
+[1411.76 --> 1412.10]  Chris and the Badger.
+[1412.18 --> 1412.96]  It's the Badger.
+[1413.68 --> 1415.42]  Yeah I could see that.
+[1416.62 --> 1418.06]  I want a listener now to
+[1418.06 --> 1418.98]  try and make us a jingle
+[1418.98 --> 1419.76]  Chris and the Badger
+[1419.76 --> 1420.12]  please.
+[1420.36 --> 1420.92]  That would be fun.
+[1422.20 --> 1423.30]  Chris and the Badger in
+[1423.30 --> 1423.74]  the morning.
+[1424.46 --> 1425.48]  He says Chris I was
+[1425.48 --> 1426.20]  surprised to hear about
+[1426.20 --> 1426.82]  your experiences with
+[1426.82 --> 1427.24]  Powerline.
+[1427.34 --> 1427.92]  I've been using the
+[1427.92 --> 1428.74]  TP-Link Powerline
+[1428.74 --> 1429.36]  products for several
+[1429.36 --> 1430.82]  years now and I've had
+[1430.82 --> 1431.78]  mixed results and my
+[1431.78 --> 1433.06]  experience it works but
+[1433.06 --> 1434.20]  sometimes it has some
+[1434.20 --> 1434.92]  problems that make it
+[1434.92 --> 1436.92]  hard to really recommend
+[1436.92 --> 1438.74]  and he tells me about
+[1438.74 --> 1439.76]  different products that
+[1439.76 --> 1440.32]  he's tried and
+[1440.32 --> 1441.42]  troubleshooting and he
+[1441.42 --> 1442.74]  has a pretty solid
+[1442.74 --> 1443.76]  looking house layout.
+[1444.00 --> 1444.32]  You know there's
+[1444.32 --> 1445.36]  nothing too crazy about
+[1445.36 --> 1445.92]  his electrical.
+[1445.92 --> 1447.48]  It's a modern house
+[1447.48 --> 1450.76]  and it's shorter than
+[1450.76 --> 1451.78]  300 meters and all of
+[1451.78 --> 1452.48]  that kind of stuff that
+[1452.48 --> 1453.04]  you'd look at.
+[1453.62 --> 1454.62]  But he says Powerline
+[1454.62 --> 1455.56]  works but it's
+[1455.56 --> 1456.64]  definitely nowhere as
+[1456.64 --> 1457.86]  fast as wired Ethernet.
+[1458.46 --> 1459.38]  In fact it isn't even
+[1459.38 --> 1460.56]  as fast as some of the
+[1460.56 --> 1462.58]  mesh Wi-Fi that he's
+[1462.58 --> 1462.88]  tested.
+[1462.98 --> 1463.60]  So he did several
+[1463.60 --> 1464.28]  different kind of speed
+[1464.28 --> 1465.16]  tests for us and said
+[1465.16 --> 1467.80]  in all he is able to
+[1467.80 --> 1469.06]  get better performance on
+[1469.06 --> 1471.32]  mesh Wi-Fi but in some
+[1471.32 --> 1473.00]  situations where Wi-Fi
+[1473.00 --> 1473.74]  didn't reach or there
+[1473.74 --> 1475.38]  was other issues he was
+[1475.38 --> 1476.30]  still able to get
+[1476.30 --> 1477.70]  around 100, 150
+[1477.70 --> 1478.92]  megabits with his
+[1478.92 --> 1479.84]  Powerline adapters.
+[1480.58 --> 1481.54]  In one case depending
+[1481.54 --> 1482.44]  on a product he tried he
+[1482.44 --> 1483.38]  was able to get 300
+[1483.38 --> 1485.22]  megabits which that's
+[1485.22 --> 1485.88]  pretty respectable.
+[1486.12 --> 1486.76]  That's really all I'd
+[1486.76 --> 1487.52]  want over Powerline.
+[1487.70 --> 1488.50]  I'm not expecting
+[1488.50 --> 1489.00]  gigabit.
+[1489.46 --> 1490.14]  I mean if all you're
+[1490.14 --> 1492.28]  doing is streaming you
+[1492.28 --> 1493.50]  know on Cody or
+[1493.50 --> 1494.44]  something like that you
+[1494.44 --> 1495.00]  know that's all you
+[1495.00 --> 1495.38]  need.
+[1495.58 --> 1496.58]  He points out and it's
+[1496.58 --> 1497.14]  a great thing to
+[1497.14 --> 1498.82]  consider is a little
+[1498.82 --> 1501.26]  play of words that
+[1501.26 --> 1502.60]  these manufacturers use.
+[1502.84 --> 1503.20]  Yes.
+[1503.38 --> 1504.06]  And I haven't verified
+[1504.06 --> 1504.92]  this but according to
+[1504.92 --> 1506.30]  him he says when they
+[1506.30 --> 1507.28]  say it's a gigabit
+[1507.28 --> 1508.74]  they mean it's a
+[1508.74 --> 1509.44]  gigabit when you
+[1509.44 --> 1510.52]  combine the send and
+[1510.52 --> 1510.94]  the receive.
+[1511.52 --> 1512.86]  It's actually half a
+[1512.86 --> 1514.68]  gigabit in both
+[1514.68 --> 1515.24]  directions.
+[1515.62 --> 1516.68]  In a perfect world
+[1516.68 --> 1517.86]  when there is no wind
+[1517.86 --> 1518.46]  outside.
+[1519.14 --> 1519.32]  Right.
+[1519.56 --> 1520.56]  They're about one
+[1520.56 --> 1521.54]  centimeter apart
+[1521.54 --> 1522.44]  probably yes.
+[1522.92 --> 1523.96]  So if you get a two
+[1523.96 --> 1525.34]  gigabit model which
+[1525.34 --> 1526.30]  there are two gigabit
+[1526.30 --> 1527.30]  units then it's one
+[1527.30 --> 1528.22]  gigabit send one
+[1528.22 --> 1529.24]  gigabit receive and it's
+[1529.24 --> 1531.16]  actually a one gigabit
+[1531.16 --> 1532.22]  unit the way we think of
+[1532.22 --> 1532.92]  it in terms of like
+[1532.92 --> 1533.76]  ethernet adapters.
+[1534.40 --> 1535.12]  So that's a little
+[1535.12 --> 1536.08]  trick of rooskies that
+[1536.08 --> 1537.40]  they like to pull that
+[1537.40 --> 1537.92]  when they're quoting
+[1537.92 --> 1539.00]  speeds they're quoting
+[1539.00 --> 1540.74]  just a send or receive.
+[1541.76 --> 1542.70]  But we got lots of
+[1542.70 --> 1543.10]  other feedback.
+[1543.22 --> 1544.02]  Some people thought that
+[1544.02 --> 1545.04]  it was that maybe I'd
+[1545.04 --> 1545.84]  have better performance
+[1545.84 --> 1546.58]  if I didn't have solar
+[1546.58 --> 1549.80]  panels on the RV that
+[1549.80 --> 1550.50]  they thought maybe that
+[1550.50 --> 1551.78]  was causing some high
+[1551.78 --> 1552.80]  degree of interference
+[1552.80 --> 1553.82]  just because of you know
+[1553.82 --> 1554.70]  the intensity of that.
+[1554.86 --> 1556.34]  But those systems are
+[1556.34 --> 1557.02]  totally separate.
+[1557.36 --> 1559.14]  The house power doesn't
+[1559.14 --> 1560.26]  connect to like the
+[1560.26 --> 1562.14]  charge controller or the
+[1562.14 --> 1562.90]  batteries directly.
+[1563.30 --> 1564.16]  Yeah because a lot of
+[1564.16 --> 1565.54]  folks wrote in and said
+[1565.54 --> 1567.34]  that if you have coax in
+[1567.34 --> 1567.94]  your walls you can
+[1567.94 --> 1569.66]  actually get power line
+[1569.66 --> 1572.72]  over coax adapters and
+[1572.72 --> 1573.50]  because they're not
+[1573.50 --> 1575.12]  carrying any signal in
+[1575.12 --> 1576.58]  modern houses generally
+[1576.58 --> 1578.68]  speaking anymore you can
+[1578.68 --> 1579.70]  actually get away with
+[1579.70 --> 1581.80]  you know running ethernet
+[1581.80 --> 1583.90]  over those and they're a
+[1583.90 --> 1585.06]  very clean signal so you
+[1585.06 --> 1585.80]  get better performance
+[1585.80 --> 1586.20]  that way.
+[1586.58 --> 1587.32]  That could be worth
+[1587.32 --> 1587.90]  looking into.
+[1588.20 --> 1590.26]  You know I got a couple
+[1590.26 --> 1591.54]  of spots that have coax
+[1591.54 --> 1592.10]  pre-run.
+[1593.00 --> 1593.82]  That's interesting.
+[1594.14 --> 1594.32]  Hmm.
+[1594.66 --> 1594.94]  Hmm.
+[1595.06 --> 1595.78]  I don't know Alex.
+[1595.86 --> 1597.80]  Maybe one day in the
+[1597.80 --> 1598.42]  future.
+[1599.24 --> 1600.90]  Brad wrote in about a
+[1600.90 --> 1603.54]  killer MOBO with QuickSync.
+[1603.54 --> 1604.68]  Yeah he's found the
+[1604.68 --> 1608.16]  ASRock J5040 ITX board.
+[1608.50 --> 1609.74]  It's a mini ITX form
+[1609.74 --> 1611.00]  factor with a quad core
+[1611.00 --> 1613.92]  Pentium chip and it has
+[1613.92 --> 1615.54]  QuickSync version 605.
+[1615.54 --> 1617.96]  Now he wrote in about
+[1617.96 --> 1619.70]  this one because of
+[1619.70 --> 1620.50]  energy usage.
+[1620.64 --> 1621.96]  This one idles he says
+[1621.96 --> 1624.48]  between 10 and 15 watts
+[1624.48 --> 1624.86]  only.
+[1625.42 --> 1627.40]  But it also has four
+[1627.40 --> 1628.50]  SATA ports which I
+[1628.50 --> 1630.56]  thought hmm this would
+[1630.56 --> 1632.38]  make a really nice sort
+[1632.38 --> 1633.54]  of NAS motherboard
+[1633.54 --> 1634.54]  potentially because you
+[1634.54 --> 1635.60]  know four hard drives
+[1635.60 --> 1637.74]  a small enclosure low
+[1637.74 --> 1639.58]  power draw QuickSync.
+[1640.40 --> 1641.08]  You know you're pushing
+[1641.08 --> 1642.24]  my buttons here Brad.
+[1642.60 --> 1643.16]  Yeah really.
+[1643.16 --> 1643.96]  Me too.
+[1644.32 --> 1645.06]  It looks like a really
+[1645.06 --> 1645.74]  nice motherboard.
+[1645.88 --> 1649.66]  Yeah this ASRock J5040
+[1649.66 --> 1650.16]  ITX.
+[1650.96 --> 1651.74]  We'll put a link in the
+[1651.74 --> 1653.72]  in the show notes.
+[1654.02 --> 1655.30]  But that hardware
+[1655.30 --> 1656.16]  acceleration that
+[1656.78 --> 1658.00]  QuickSync boy that that
+[1658.00 --> 1658.84]  is looking really good.
+[1658.96 --> 1660.02]  And this you could
+[1660.02 --> 1661.28]  totally build I bet you
+[1661.28 --> 1662.76]  for if you had the
+[1662.76 --> 1665.16]  storage I bet two
+[1665.70 --> 1666.40]  three hundred dollars
+[1666.40 --> 1667.64]  to build a nice system
+[1667.64 --> 1668.30]  with a decent little
+[1668.30 --> 1668.70]  case.
+[1668.88 --> 1669.82]  There's some memory
+[1669.82 --> 1670.64]  around this thing.
+[1671.06 --> 1672.82]  It's a passive CPU as
+[1672.82 --> 1674.80]  well so it takes it
+[1674.80 --> 1675.70]  doesn't need a fan on
+[1675.70 --> 1676.18]  the CPU.
+[1676.92 --> 1678.06]  Also it takes a
+[1678.06 --> 1679.50]  laptop style SO
+[1679.50 --> 1680.58]  DIM memory.
+[1681.32 --> 1682.22]  So this thing is tiny.
+[1682.34 --> 1682.86]  It's got a couple of
+[1682.86 --> 1684.46]  M2 slots on there for
+[1684.46 --> 1685.36]  Wi-Fi if you want.
+[1686.10 --> 1687.50]  So yeah yeah go go
+[1687.50 --> 1688.10]  ahead and check that
+[1688.10 --> 1688.36]  one out.
+[1688.42 --> 1688.90]  That looks like a
+[1688.90 --> 1689.96]  really really useful
+[1689.96 --> 1690.50]  little build.
+[1690.96 --> 1691.80]  Stefan wrote in to tell
+[1691.80 --> 1692.72]  us about some benchmarks
+[1692.72 --> 1693.80]  in German that show
+[1693.80 --> 1694.72]  that the latest AMD
+[1694.72 --> 1696.70]  desktop APUs are
+[1696.70 --> 1698.10]  getting idle power well
+[1698.10 --> 1700.22]  below 10 watts and
+[1700.22 --> 1700.72]  depending on the
+[1700.72 --> 1701.70]  motherboard as low
+[1701.70 --> 1702.52]  as six or seven
+[1702.52 --> 1702.92]  watts.
+[1703.44 --> 1704.16]  So it seems like
+[1704.16 --> 1704.72]  there's something to
+[1704.72 --> 1705.42]  watch there too.
+[1705.86 --> 1706.72]  Oh I'm trying to
+[1706.72 --> 1707.88]  avoid buying a Ryzen
+[1707.88 --> 1708.46]  5000.
+[1709.12 --> 1710.04]  I'm really trying to
+[1710.04 --> 1711.74]  avoid it but stuff
+[1711.74 --> 1713.06]  like that makes me
+[1713.06 --> 1713.96]  want to buy one.
+[1715.86 --> 1716.68]  Hey while we're doing
+[1716.68 --> 1717.30]  feedback I want to
+[1717.30 --> 1717.92]  take a moment and
+[1717.92 --> 1719.38]  mention that a cloud
+[1719.38 --> 1720.86]  guru has a Python 3
+[1720.86 --> 1722.18]  scripting course for
+[1722.18 --> 1723.08]  system administrators
+[1723.08 --> 1724.50]  where you can develop
+[1724.50 --> 1725.24]  the skills you need to
+[1725.24 --> 1725.98]  write effective and
+[1725.98 --> 1727.32]  powerful scripts and
+[1727.32 --> 1728.46]  create command line
+[1728.46 --> 1730.56]  tools using Python 3.
+[1730.56 --> 1731.18]  So in the course
+[1731.18 --> 1731.46]  you're going to
+[1731.46 --> 1732.02]  develop skills you
+[1732.02 --> 1732.36]  need to write
+[1732.36 --> 1732.88]  effective and
+[1732.88 --> 1733.54]  powerful Python
+[1733.54 --> 1734.90]  scripts and it's
+[1734.90 --> 1736.00]  it's a big one.
+[1736.10 --> 1736.50]  So beyond the
+[1736.50 --> 1737.24]  language itself you'll
+[1737.24 --> 1737.88]  go through the full
+[1737.88 --> 1738.62]  development process
+[1738.62 --> 1739.36]  including project
+[1739.36 --> 1740.12]  setup, planning,
+[1740.74 --> 1741.78]  automated testing to
+[1741.78 --> 1742.30]  build two different
+[1742.30 --> 1743.10]  command line tools and
+[1743.10 --> 1743.34]  more.
+[1743.82 --> 1744.46]  So check out the link
+[1744.46 --> 1745.20]  we'll have in the
+[1745.20 --> 1746.16]  show notes for the
+[1746.16 --> 1747.22]  Python 3 scripting for
+[1747.22 --> 1748.02]  system administrators
+[1748.02 --> 1749.52]  at cloudguru.com.
+[1750.90 --> 1751.94]  Hey so I'm sat here
+[1751.94 --> 1752.34]  whilst we were
+[1752.34 --> 1753.30]  recording and thought
+[1753.30 --> 1754.22]  my feet are cold.
+[1754.64 --> 1755.20]  So whilst you were
+[1755.20 --> 1756.28]  reading that ad spot
+[1756.28 --> 1757.56]  I logged into my
+[1757.56 --> 1758.20]  home assistant and
+[1758.20 --> 1758.86]  just bumped up the
+[1758.86 --> 1759.76]  thermostat a little bit.
+[1760.56 --> 1762.94]  It's nice isn't it?
+[1763.56 --> 1764.42]  Yep, yep.
+[1764.64 --> 1765.54]  I think my favorite
+[1765.54 --> 1767.66]  still is because of
+[1767.66 --> 1768.10]  the HomeKit
+[1768.10 --> 1769.76]  integration when I'm
+[1769.76 --> 1771.14]  driving home I just
+[1771.14 --> 1771.84]  push a button on the
+[1771.84 --> 1772.96]  steering wheel and I
+[1772.96 --> 1775.10]  tell the computer just
+[1775.10 --> 1776.26]  to turn on you know
+[1776.26 --> 1777.04]  the heaters to extra
+[1777.04 --> 1777.24]  heat.
+[1777.44 --> 1778.00]  We have an extra heat
+[1778.00 --> 1778.52]  mode that kind of
+[1778.52 --> 1779.06]  brings up the
+[1779.06 --> 1780.22]  temperature more a
+[1780.22 --> 1781.48]  little quicker and
+[1781.48 --> 1782.28]  so when I buy the
+[1782.28 --> 1782.84]  and turn on the
+[1782.84 --> 1783.10]  lights.
+[1783.44 --> 1783.96]  So when I get home
+[1783.96 --> 1784.78]  all the lights are on
+[1784.78 --> 1786.06]  place is nice and
+[1786.06 --> 1786.34]  toasty.
+[1786.34 --> 1788.68]  Oh I've been
+[1788.68 --> 1789.32]  thinking about like
+[1789.32 --> 1790.42]  an NFC tag on the
+[1790.42 --> 1791.16]  dashboard or something
+[1791.16 --> 1791.82]  that I could just
+[1791.82 --> 1792.62]  tap with my phone
+[1792.62 --> 1792.96]  maybe.
+[1793.66 --> 1794.68]  I haven't done it but
+[1794.68 --> 1795.22]  I've been thinking
+[1795.22 --> 1795.70]  about it.
+[1796.18 --> 1796.58]  I've been thinking
+[1796.58 --> 1797.14]  about that too.
+[1797.20 --> 1797.84]  I actually have an
+[1797.84 --> 1798.70]  NFC tag at the
+[1798.70 --> 1800.06]  door out the
+[1800.06 --> 1800.78]  studio so on my
+[1800.78 --> 1801.28]  way out the
+[1801.28 --> 1802.36]  studio I can tap it
+[1802.36 --> 1803.10]  and right now it
+[1803.10 --> 1803.70]  just kind of sends
+[1803.70 --> 1804.40]  like an alert to the
+[1804.40 --> 1805.86]  wife with an ETA
+[1805.86 --> 1807.04]  and all of that kind
+[1807.04 --> 1807.98]  of stuff you know
+[1807.98 --> 1808.82]  based on my location
+[1808.82 --> 1810.28]  and her location but
+[1810.28 --> 1810.96]  I have been thinking
+[1810.96 --> 1811.58]  man it'd be pretty
+[1811.58 --> 1812.98]  great to tie that in
+[1812.98 --> 1814.22]  with the heating and
+[1814.22 --> 1815.12]  the lighting check to
+[1815.12 --> 1815.72]  see if it's on or
+[1815.72 --> 1815.98]  not.
+[1816.54 --> 1817.80]  NFC tags and all of
+[1817.80 --> 1819.06]  that is probably still
+[1819.06 --> 1820.28]  the most underutilized
+[1820.28 --> 1821.62]  area because on iOS
+[1821.62 --> 1823.78]  it kind of sucks and I
+[1823.78 --> 1824.48]  think it's similar on
+[1824.48 --> 1825.22]  Android but not quite
+[1825.22 --> 1825.88]  the same where on
+[1825.88 --> 1827.26]  iOS it just brings up
+[1827.26 --> 1827.74]  as far as I
+[1827.74 --> 1828.62]  understand it a
+[1828.62 --> 1829.68]  notification prompt
+[1829.68 --> 1830.34]  that you then have to
+[1830.34 --> 1832.64]  tap to execute the
+[1832.64 --> 1834.46]  NFC automation and
+[1834.46 --> 1835.12]  that just sounds like
+[1835.12 --> 1835.52]  garbage.
+[1836.04 --> 1837.00]  Not true on Android I
+[1837.00 --> 1838.06]  just tap the tag and
+[1838.06 --> 1839.02]  my garage door opens
+[1839.02 --> 1839.58]  it's amazing.
+[1840.26 --> 1840.94]  That's what I want.
+[1841.34 --> 1842.32]  I can kind of see
+[1842.32 --> 1843.52]  maybe why Apple did it
+[1843.52 --> 1844.30]  this way for
+[1844.30 --> 1846.02]  novices who you
+[1846.02 --> 1846.76]  know they don't they
+[1846.76 --> 1847.46]  don't want to execute
+[1847.46 --> 1848.30]  stuff randomly on
+[1848.30 --> 1850.44]  their phone but man
+[1850.44 --> 1852.22]  I totally appreciate
+[1852.22 --> 1853.24]  that but I just would
+[1853.24 --> 1854.16]  love a setting to say
+[1854.16 --> 1855.28]  don't require user
+[1855.28 --> 1855.78]  interaction.
+[1856.12 --> 1856.22]  Yeah.
+[1856.34 --> 1857.38]  It just sort of kills
+[1857.38 --> 1857.78]  the usefulness.
+[1857.90 --> 1859.02]  I have also here on
+[1859.02 --> 1860.42]  the studio mixer I
+[1860.42 --> 1861.94]  have an NFC tag because
+[1861.94 --> 1862.74]  for some reason
+[1862.74 --> 1863.60]  Behringer thought it'd
+[1863.60 --> 1864.42]  be a great idea to put
+[1864.42 --> 1865.70]  a like a phone holder
+[1865.70 --> 1866.74]  on the mixer because
+[1866.74 --> 1867.46]  the ideas are going to
+[1867.46 --> 1867.84]  use like their
+[1867.84 --> 1868.78]  touchscreen app on your
+[1868.78 --> 1870.94]  phone and so I have a
+[1870.94 --> 1871.58]  spot where my phone
+[1871.58 --> 1873.88]  sits and I just put an
+[1873.88 --> 1874.80]  NFC tag in that spot
+[1874.80 --> 1875.86]  just set my phone to
+[1875.86 --> 1877.32]  D&D and turn on the
+[1877.32 --> 1878.24]  studio lights which are
+[1878.24 --> 1879.14]  on home assistant and
+[1879.14 --> 1879.66]  all that.
+[1880.66 --> 1881.44]  Oli wrote into the
+[1881.44 --> 1882.44]  holiday mailbag and
+[1882.44 --> 1883.16]  said I'm a long time
+[1883.16 --> 1883.98]  listener occasional
+[1883.98 --> 1885.22]  disc order from Norway
+[1885.22 --> 1886.88]  and we talk about
+[1886.88 --> 1887.58]  storage setups on the
+[1887.58 --> 1888.46]  show a little bit but
+[1888.46 --> 1889.14]  I'd love you to go into
+[1889.14 --> 1890.46]  some details with
+[1890.46 --> 1891.88]  setups ranging from
+[1891.88 --> 1892.70]  smaller setups to
+[1892.70 --> 1893.26]  bigger setups.
+[1893.74 --> 1894.10]  Do you have any
+[1894.10 --> 1895.18]  strategies deciding on
+[1895.18 --> 1896.66]  what you invest in?
+[1897.30 --> 1898.28]  My backups are going to
+[1898.28 --> 1899.44]  backblaze but I'm
+[1899.44 --> 1900.48]  rethinking things a little
+[1900.48 --> 1901.18]  bit and I think I want
+[1901.18 --> 1901.88]  more sane local
+[1901.88 --> 1903.16]  storage but I'm a
+[1903.16 --> 1903.84]  little put off at the
+[1903.84 --> 1904.18]  price.
+[1905.20 --> 1905.80]  What would be a sweet
+[1905.80 --> 1906.56]  spot in terms of
+[1906.56 --> 1908.00]  discs and storage for
+[1908.00 --> 1909.18]  about an 8 terabyte
+[1909.18 --> 1910.42]  media collection as
+[1910.42 --> 1910.94]  well as some more
+[1910.94 --> 1912.00]  personal media like
+[1912.00 --> 1913.26]  photos that I just
+[1913.26 --> 1914.02]  don't want to lose?
+[1914.42 --> 1915.02]  Any links would be
+[1915.02 --> 1915.44]  great too.
+[1915.84 --> 1916.78]  Man this question was
+[1916.78 --> 1917.76]  made for me wasn't it?
+[1917.88 --> 1919.00]  It really was.
+[1919.34 --> 1921.74]  So perfectmediaserver.com
+[1921.74 --> 1923.84]  first of all I think is
+[1923.84 --> 1925.14]  where I will send you in
+[1925.14 --> 1926.96]  the first instance to
+[1926.96 --> 1927.52]  look at the software
+[1927.52 --> 1928.20]  side of things.
+[1928.80 --> 1930.06]  I will be building up the
+[1930.06 --> 1931.04]  hardware recommendations
+[1931.04 --> 1932.12]  section of that site
+[1932.12 --> 1932.80]  over the next few
+[1932.80 --> 1935.06]  months but really I
+[1935.06 --> 1935.86]  would just take a look
+[1935.86 --> 1937.06]  at serverbuilds.net.
+[1937.38 --> 1938.82]  They have some amazing
+[1938.82 --> 1940.84]  used enterprise gear and
+[1940.84 --> 1942.06]  I know it's quite a US
+[1942.06 --> 1944.28]  centric website but you
+[1944.28 --> 1945.16]  can still get a lot of
+[1945.16 --> 1946.26]  good ideas about what to
+[1946.26 --> 1947.34]  use like QuickSync for
+[1947.34 --> 1949.08]  example that that came
+[1949.08 --> 1950.42]  from JDM the guy behind
+[1950.42 --> 1951.40]  that site who we've had on
+[1951.40 --> 1953.32]  the show before and just
+[1953.32 --> 1953.98]  take a look at what
+[1953.98 --> 1954.86]  they're doing and the
+[1954.86 --> 1956.12]  trends and the way the
+[1956.12 --> 1957.34]  industry is going with
+[1957.34 --> 1958.48]  what those guys are doing
+[1958.48 --> 1959.26]  over there at server
+[1959.26 --> 1961.32]  builds and I think you
+[1961.32 --> 1961.96]  can probably get away
+[1961.96 --> 1963.56]  with a fairly minimal
+[1963.56 --> 1964.38]  kind of setup.
+[1964.54 --> 1965.06]  So you've got 8
+[1965.06 --> 1966.16]  terabytes worth of stuff
+[1966.16 --> 1967.78]  you want to store so I
+[1967.78 --> 1969.16]  would buy a hard drive
+[1969.16 --> 1971.46]  that is at least 8
+[1971.46 --> 1972.78]  probably 10 or 12
+[1972.78 --> 1973.74]  terabytes so you've got a
+[1973.74 --> 1975.58]  bit of headroom and buy
+[1975.58 --> 1976.74]  a pair of them so that
+[1976.74 --> 1978.64]  you you know can have
+[1978.64 --> 1980.24]  full redundancy.
+[1981.12 --> 1981.92]  You're already using
+[1981.92 --> 1983.48]  Backblaze so you know
+[1983.48 --> 1985.48]  raid is not backup is a
+[1985.48 --> 1986.70]  very common phrase that
+[1986.70 --> 1987.60]  you'll hear people say.
+[1987.60 --> 1989.60]  Make sure that you have
+[1989.60 --> 1991.96]  everything duplicated in
+[1991.96 --> 1993.82]  at least two different
+[1993.82 --> 1994.82]  physical locations.
+[1995.50 --> 1996.56]  So even if that just
+[1996.56 --> 1998.84]  takes the form of you
+[1998.84 --> 1999.88]  know a USB hard drive
+[1999.88 --> 2000.48]  that you leave at your
+[2000.48 --> 2001.28]  parents house when you
+[2001.28 --> 2002.84]  go and see them one day
+[2002.84 --> 2005.38]  in the future who knows
+[2005.38 --> 2007.92]  you know the world is so
+[2007.92 --> 2009.00]  different right now but
+[2009.00 --> 2011.46]  if it's just a USB hard
+[2011.46 --> 2012.76]  drive in a drawer at a
+[2012.76 --> 2014.02]  parents house then that
+[2014.02 --> 2015.08]  will do the trick as well
+[2015.08 --> 2015.78]  you know in a lot of
+[2015.78 --> 2016.96]  situations unless you
+[2016.96 --> 2019.10]  have lots of media being
+[2019.10 --> 2019.98]  added all the time but
+[2019.98 --> 2020.66]  I don't think that's the
+[2020.66 --> 2021.58]  use case for a lot of
+[2021.58 --> 2021.80]  people.
+[2021.98 --> 2023.68]  I think most people those
+[2023.68 --> 2024.98]  kind of periodical backups
+[2024.98 --> 2026.90]  every three to six
+[2026.90 --> 2028.04]  months is probably
+[2028.04 --> 2028.70]  sufficient.
+[2029.78 --> 2032.52]  So build yourself you
+[2032.52 --> 2035.42]  know a small mini ITX
+[2035.42 --> 2037.80]  couple of bay box and
+[2037.80 --> 2039.62]  you know stick the
+[2039.62 --> 2040.82]  perfect media server stack
+[2040.82 --> 2041.60]  on there and you'll be
+[2041.60 --> 2042.02]  good to go.
+[2042.02 --> 2043.94]  Yeah thankfully eight
+[2043.94 --> 2045.02]  terabytes is a really
+[2045.02 --> 2046.86]  pretty pretty doable
+[2046.86 --> 2047.64]  problem to solve.
+[2048.14 --> 2048.86]  So you know of course
+[2048.86 --> 2049.60]  you want more than that
+[2049.60 --> 2050.34]  you're gonna you know at
+[2050.34 --> 2051.70]  least at least I'd say go
+[2051.70 --> 2053.28]  12 terabytes if not more
+[2053.28 --> 2054.74]  if you already are using
+[2054.74 --> 2056.34]  eight terabytes and you
+[2056.34 --> 2056.90]  could probably even
+[2056.90 --> 2058.84]  justify a bit more than
+[2058.84 --> 2059.06]  that.
+[2059.48 --> 2060.54]  That's some great strategy
+[2060.54 --> 2061.70]  advice right there and
+[2061.70 --> 2062.74]  perfect timing for the
+[2062.74 --> 2064.54]  show too so so best of
+[2064.54 --> 2064.78]  luck.
+[2065.12 --> 2066.20]  I would take a look at
+[2066.20 --> 2069.04]  amazon.de quite often
+[2069.04 --> 2070.94]  have the Western Digital
+[2070.94 --> 2072.28]  what are they called
+[2072.28 --> 2072.68]  over there?
+[2072.98 --> 2073.80]  They're not easy stores
+[2073.80 --> 2074.62]  because they're Best Buy
+[2074.62 --> 2075.74]  like US centric ones
+[2075.74 --> 2077.66]  they're called MyBooks I
+[2077.66 --> 2078.74]  think in Europe.
+[2079.30 --> 2080.66]  You can quite often get
+[2080.66 --> 2082.50]  those for a you know 10
+[2082.50 --> 2084.06]  12 14 terabyte hard drive
+[2084.06 --> 2086.34]  in the 200 250 euro
+[2086.34 --> 2088.16]  range so that would be a
+[2088.16 --> 2089.14]  good place to start it's
+[2089.14 --> 2089.72]  not going to be super
+[2089.72 --> 2090.08]  cheap.
+[2090.74 --> 2092.76]  My philosophy with regards
+[2092.76 --> 2094.84]  to how much local storage
+[2094.84 --> 2096.58]  do I need versus cloud is
+[2096.58 --> 2099.36]  it's up to you right it's
+[2099.36 --> 2101.42]  it's your personal risk
+[2101.42 --> 2103.28]  profile or and how
+[2103.28 --> 2104.84]  important is this data to
+[2104.84 --> 2105.14]  you?
+[2106.04 --> 2106.82]  Are you going to be upset
+[2106.82 --> 2108.44]  if if backblaze and I
+[2108.44 --> 2108.86]  don't know if they're
+[2108.86 --> 2110.28]  going to but if they turn
+[2110.28 --> 2111.60]  around next week and you
+[2111.60 --> 2112.76]  know triple their prices
+[2112.76 --> 2113.36]  what are you going to do
+[2113.36 --> 2114.02]  if that happens?
+[2115.02 --> 2116.16]  If you have a hard drive
+[2116.16 --> 2118.54]  in your closet you know
+[2118.54 --> 2120.40]  up front what that cost is
+[2120.40 --> 2121.20]  going to be what the total
+[2121.20 --> 2122.22]  cost of ownership for that
+[2122.22 --> 2124.10]  that storage is going to be
+[2124.10 --> 2125.04]  and there's there'll be no
+[2125.04 --> 2126.10]  surprises or anything like
+[2126.10 --> 2127.72]  that so I mean you're
+[2127.72 --> 2128.38]  talking to a guy that's got
+[2128.38 --> 2129.36]  100 terabytes in his
+[2129.36 --> 2130.42]  basement so maybe I'm not
+[2130.42 --> 2132.26]  the right guy to speak to
+[2132.26 --> 2132.88]  you know.
+[2133.14 --> 2134.12]  And the other guy who's
+[2134.12 --> 2134.84]  like I need to get more
+[2134.84 --> 2135.88]  disk as fast as possible
+[2135.88 --> 2136.96]  I've only got 12 terabytes
+[2136.96 --> 2138.94]  free right now like yeah
+[2138.94 --> 2141.46]  yeah but really there's so
+[2141.46 --> 2143.56]  many ways to solve it but
+[2143.56 --> 2144.58]  I'd love to hear what you
+[2144.58 --> 2145.78]  do so go to self-hosted
+[2145.78 --> 2146.90]  dot show slash contact to
+[2146.90 --> 2148.50]  update us and then Scott
+[2148.50 --> 2149.32]  wrote in with another
+[2149.32 --> 2150.90]  another question I have a
+[2150.90 --> 2152.14]  sense the audience may have
+[2152.14 --> 2153.30]  a few answers for us so
+[2153.30 --> 2154.42]  keep that contact link in
+[2154.42 --> 2155.88]  mind he says I was hoping
+[2155.88 --> 2156.52]  you could make a
+[2156.52 --> 2158.00]  recommendation for self-hosted
+[2158.00 --> 2160.60]  online cookbook my mother
+[2160.60 --> 2162.34]  has a huge cookbook full of
+[2162.34 --> 2164.48]  old family recipes which I
+[2164.48 --> 2165.52]  would like to digitalize
+[2165.52 --> 2168.16]  ideally with OCR and the
+[2168.16 --> 2169.44]  ability to take and search
+[2169.44 --> 2170.48]  the recipes as well as
+[2170.48 --> 2172.00]  preserving original image of
+[2172.00 --> 2173.36]  the old handwritten family
+[2173.36 --> 2175.60]  recipe Scott I love this
+[2175.60 --> 2177.32]  idea what do you think
+[2177.32 --> 2178.70]  Alex has anything come to
+[2178.70 --> 2180.12]  mind for you well we
+[2180.12 --> 2181.68]  covered chow down a little
+[2181.68 --> 2183.40]  while ago as a self-hosted
+[2183.40 --> 2185.26]  recipes app there is another
+[2185.26 --> 2186.98]  one which whilst we're doing
+[2186.98 --> 2188.44]  this segment I will try and
+[2188.44 --> 2190.02]  find which I can't remember
+[2190.02 --> 2191.86]  right now but there is also
+[2191.86 --> 2194.22]  an old JB project isn't it
+[2194.22 --> 2196.26]  yeah that's true that is true
+[2196.26 --> 2198.56]  there is the the open your
+[2198.56 --> 2200.30]  mouth recipes which we
+[2200.30 --> 2201.56]  actually used GitHub and
+[2201.56 --> 2203.30]  Markdown for those I was
+[2203.30 --> 2204.18]  thinking you know Scott could
+[2204.18 --> 2206.54]  get started with even out any
+[2206.54 --> 2207.96]  without any software selected
+[2207.96 --> 2209.36]  yet by just getting good
+[2209.36 --> 2212.26]  quality captures of those cards
+[2212.26 --> 2213.84]  and he's gonna want probably
+[2213.84 --> 2214.98]  something he can take over to
+[2214.98 --> 2216.90]  grandma's house or mom's house
+[2216.90 --> 2219.98]  or whoever whoever the the
+[2219.98 --> 2220.70]  family members you want to
+[2220.70 --> 2221.60]  capture these from because why
+[2221.60 --> 2223.14]  not get them all right you
+[2223.14 --> 2224.50]  could probably get away with
+[2224.50 --> 2226.56]  something like scan bot or the
+[2226.56 --> 2229.16]  other available scanning apps on
+[2229.16 --> 2230.02]  your phone but you might look
+[2230.02 --> 2231.10]  into scanner options too and
+[2231.10 --> 2232.80]  just start there start getting the
+[2232.80 --> 2234.86]  high quality images from there and
+[2234.86 --> 2237.06]  then the software will come I
+[2237.06 --> 2238.60]  found it okay it's called
+[2238.60 --> 2243.70]  vapeen 1111 slash recipes what a
+[2243.70 --> 2245.68]  catchy name huh it's a Django
+[2245.68 --> 2247.26]  application designed for managing
+[2247.26 --> 2249.96]  recipes and it's a web app so I
+[2249.96 --> 2251.56]  would imagine it runs out of a
+[2251.56 --> 2253.52]  container but it's got a search
+[2253.52 --> 2256.26]  built on top of Django's trigram
+[2256.26 --> 2259.24]  similarity search engine and it
+[2259.24 --> 2260.72]  allows you to create and search for
+[2260.72 --> 2263.28]  tags and assign them in batches to
+[2263.28 --> 2264.64]  certain files matching certain
+[2264.64 --> 2266.90]  criteria it will sync with both
+[2266.90 --> 2269.80]  dropbox and next cloud with more
+[2269.80 --> 2271.62]  support being added every every
+[2271.62 --> 2273.96]  week and you can import lots of
+[2273.96 --> 2275.72]  recipes from different websites
+[2275.72 --> 2278.14]  with JSON objects and stuff like
+[2278.14 --> 2279.94]  that and there are also apps for
+[2279.94 --> 2281.52]  mobile devices like phones and
+[2281.52 --> 2283.96]  tablets so yeah lots and lots of
+[2283.96 --> 2285.80]  stuff in there runs in a docker
+[2285.80 --> 2289.38]  this is what the reddit collective
+[2289.38 --> 2292.98]  thought recommends at the moment so I
+[2292.98 --> 2294.56]  haven't tried this one I just
+[2294.56 --> 2295.72]  haven't got to it but it's on my
+[2295.72 --> 2297.00]  short list so go and take a look at
+[2297.00 --> 2299.10]  that link in the show notes I also
+[2299.10 --> 2302.16]  recall that groceries had a bit of a
+[2302.16 --> 2304.12]  recipe manager I don't recall how
+[2304.12 --> 2306.76]  extensive it was but that's a past
+[2306.76 --> 2308.92]  pick too so we'll put links to all of
+[2308.92 --> 2310.06]  these the one that Alex just talked
+[2310.06 --> 2312.02]  about you could see the example of
+[2312.02 --> 2313.34]  how we used open your mouth on
+[2313.34 --> 2315.08]  github and just made it a community
+[2315.08 --> 2316.30]  project so you could have multiple
+[2316.30 --> 2317.78]  family members that contribute that
+[2317.78 --> 2320.02]  way or perhaps somebody out there will
+[2320.02 --> 2322.34]  know a great software project that we
+[2322.34 --> 2323.86]  haven't mentioned and inform us all
+[2323.86 --> 2325.40]  itself posted that show slash contact
+[2325.40 --> 2327.58]  the last one in our holiday
+[2327.58 --> 2329.82]  extravaganza mailbag here is a jasua
+[2329.82 --> 2332.90]  writes in regarding thoughts that were
+[2332.90 --> 2334.84]  inspired by self hosted episode 33
+[2334.84 --> 2337.58]  triggered by the helio 64 discussion he
+[2337.58 --> 2338.92]  says hey guys I was listening to your
+[2338.92 --> 2340.82]  review of the helio 64 with some
+[2340.82 --> 2342.38]  interest since I am the owner of their
+[2342.38 --> 2344.86]  previous product the helios for I
+[2345.56 --> 2346.92]  believe the points you make about
+[2346.92 --> 2348.84]  software are quite valid yet I'd like to
+[2348.84 --> 2350.46]  point out that there's a really hard
+[2350.46 --> 2353.02]  problem to solve I work personally with
+[2353.02 --> 2355.40]  a company in Israel that makes SBCs and
+[2355.40 --> 2358.62]  SOMs mostly with ARM based system on
+[2358.62 --> 2361.06]  chips it's my job to make Debian
+[2361.06 --> 2362.76]  available for each product to their
+[2362.76 --> 2365.62]  customers long ago when I started I
+[2365.62 --> 2367.12]  really wanted to do this the right way
+[2367.12 --> 2369.14]  I submitted bug reports and patches to
+[2369.14 --> 2370.50]  the Debian project for enabling all
+[2370.50 --> 2373.04]  kinds of small things a kernel.config for
+[2373.04 --> 2374.68]  a driver here a customized boot script
+[2374.68 --> 2377.12]  there enabling open GL ES backends and
+[2377.12 --> 2379.88]  shared libraries and continuously watching
+[2379.88 --> 2382.42]  and testing the distributions for things
+[2382.42 --> 2385.04]  that break turns out I never got to the
+[2385.04 --> 2386.78]  point where I could give customers a
+[2386.78 --> 2388.64]  pure Debian system there's always
+[2388.64 --> 2390.54]  another tweak that I had to carry out
+[2390.54 --> 2392.78]  of tree so to this day I'm creating
+[2392.78 --> 2394.54]  block device images with custom kernel
+[2394.54 --> 2397.54]  packages integrated binary blobs and
+[2397.54 --> 2398.96]  maybe a systemd service for loading
+[2398.96 --> 2401.12]  Bluetooth firmware and even patch parts
+[2401.12 --> 2404.06]  of X or Wayland so why do I tell you
+[2404.06 --> 2406.10]  all of this well the reason being for a
+[2406.10 --> 2407.74]  new product it takes time and
+[2407.74 --> 2410.10]  continued effort for mainlining all the
+[2410.10 --> 2411.94]  things and the experience can differ
+[2411.94 --> 2414.38]  largely by a particular SoC in your
+[2414.38 --> 2416.64]  hands and you'll find that despite even
+[2416.64 --> 2417.84]  when the vendor does everything right
+[2417.84 --> 2420.14]  it's still not perfect to really solve
+[2420.14 --> 2421.48]  this problem there has to be a way for
+[2421.48 --> 2423.14]  hardware makers who are both capable and
+[2423.14 --> 2424.76]  willing to do the work to achieve
+[2424.76 --> 2426.26]  something greater than what I was able
+[2426.26 --> 2429.18]  to do in my job in his opinion it's just
+[2429.18 --> 2430.74]  not there yet he says Alex that the
+[2430.74 --> 2433.64]  ecosystem just can't support the kind of
+[2433.64 --> 2435.64]  rapid support that the hardware needs at
+[2435.64 --> 2437.38]  this stage and you know after reading
+[2437.38 --> 2439.46]  this I was thinking look at the
+[2439.46 --> 2441.98]  Raspberry Pi it's been around forever
+[2441.98 --> 2443.34]  and of course they've had iterations
+[2443.34 --> 2445.26]  that have changed things but you really
+[2445.26 --> 2447.82]  still even there you kind of have to get
+[2447.82 --> 2451.38]  an image that's at least been tested
+[2451.38 --> 2453.58]  for the Raspberry Pi you can now get the
+[2453.58 --> 2455.68]  Ubuntu ARM image and it will boot on the
+[2455.68 --> 2457.98]  Raspberry Pi but that's only just recently
+[2457.98 --> 2459.96]  it's and it's really not there with all
+[2459.96 --> 2462.10]  distros yeah you make a good point I
+[2462.10 --> 2464.76]  mean the Ubuntu image for the Pi 4 has
+[2464.76 --> 2466.96]  made a big difference for me to the
+[2466.96 --> 2468.94]  overall kind of feel of it being a real
+[2468.94 --> 2472.34]  air quotes a real device and it's now in
+[2472.34 --> 2474.22]  production for me I'm using it as Pi KVM
+[2474.22 --> 2476.76]  which ironically runs on Arch but anyway
+[2476.76 --> 2479.56]  yeah I agree with you I mean I ended up
+[2479.56 --> 2481.50]  getting ZFS working on the Helios 64
+[2481.50 --> 2484.66]  after the review in the end it was a few
+[2484.66 --> 2486.56]  days it was a kernel update and DKMS
+[2486.56 --> 2489.50]  started working again but yeah I just
+[2489.50 --> 2492.50]  don't know how without you know an
+[2492.50 --> 2494.58]  Apple level of control over both the
+[2494.58 --> 2496.54]  hardware and software you could ever hope
+[2496.54 --> 2499.98]  to solve this problem fully slow but
+[2499.98 --> 2501.82]  steady there are standards like server
+[2501.82 --> 2505.38]  ready that try to solve this more for the
+[2505.38 --> 2507.40]  data center but those lessons could be
+[2507.40 --> 2508.94]  learned in the consumer devices but
+[2508.94 --> 2511.30]  there's just not necessarily the vendor
+[2511.30 --> 2513.42]  buy-in and there's not necessarily the
+[2513.42 --> 2515.26]  vendor buy-in to support the development
+[2515.26 --> 2516.66]  right that's an area where they could
+[2516.66 --> 2518.58]  apply a little bit of leverage they could
+[2518.58 --> 2520.50]  hire people to just write the code and
+[2520.50 --> 2522.12]  contribute it more and participate in
+[2522.12 --> 2525.34]  these projects but it's only it's only so
+[2525.34 --> 2528.40]  scalable and it's really not a problem we
+[2528.40 --> 2531.76]  have on the x86 side of things we're so
+[2531.76 --> 2534.70]  kind of swept up by the power usage of arm
+[2534.70 --> 2538.06]  or the small size form factor or the price
+[2538.06 --> 2540.84]  point I think we forget some of the
+[2540.84 --> 2542.68]  luxuries that we've gained over the years
+[2542.68 --> 2545.04]  with the x86 platform it just works you
+[2545.04 --> 2546.24]  don't have to think about it you don't
+[2546.24 --> 2550.18]  have to grab a special version of a linux
+[2550.18 --> 2553.12]  distro or windows or whatever it is to
+[2553.12 --> 2556.46]  to run on it and with apple changing to
+[2556.46 --> 2560.16]  arm you know based cpus it is that's the
+[2560.16 --> 2561.84]  first real departure that mainstream
+[2561.84 --> 2565.72]  computing has seen from x86 instruction
+[2565.72 --> 2568.78]  sets for 15 years yep and I think that's
+[2568.78 --> 2572.36]  going to influence hopefully in five years
+[2572.36 --> 2574.82]  time or so the rest of the industry will
+[2574.82 --> 2576.60]  will be in a similar position to where
+[2576.60 --> 2578.30]  apple are now with that kind of level of
+[2578.30 --> 2580.82]  integration of course apple will be five
+[2580.82 --> 2582.44]  years further down the road by then so
+[2582.44 --> 2584.42]  who knows maybe they'll never catch up
+[2584.42 --> 2587.32]  but it's a really interesting time for
+[2587.32 --> 2590.08]  sure and I really want to support these
+[2590.08 --> 2593.20]  guys doing these projects like like
+[2593.20 --> 2596.06]  COBOL you know they're a small team you
+[2596.06 --> 2597.24]  know they're not they're not doing this
+[2597.24 --> 2599.04]  to become millionaires overnight you know
+[2599.04 --> 2600.70]  it's they're doing it for the love I'm
+[2600.70 --> 2603.22]  sure and they made a really great
+[2603.22 --> 2605.10]  product it just missed in a few key areas
+[2605.10 --> 2607.22]  so I wanted to let some of the listeners
+[2607.22 --> 2611.36]  know that I will be selling my Helios 64
+[2611.36 --> 2613.50]  so if you're interested in the market just
+[2613.50 --> 2615.82]  let me know via Twitter you know you'd
+[2615.82 --> 2616.88]  have to wait for it to ship or anything
+[2616.88 --> 2618.78]  for the next batch we'll sort something
+[2618.78 --> 2620.32]  out just leave a little stink on it when
+[2620.32 --> 2621.58]  you ship it out let's make it real
+[2621.58 --> 2623.84]  special okay get a little bit of your
+[2623.84 --> 2626.00]  stink on there I'll sign the inside in
+[2626.00 --> 2629.90]  Tippex or something how about that I want
+[2629.90 --> 2631.56]  to say also a special thank you to our
+[2631.56 --> 2633.90]  members at self hosted dot show slash sre
+[2633.90 --> 2635.74]  you can become a site reliability engineer
+[2635.74 --> 2638.22]  for this show you get a limited ad feed
+[2638.22 --> 2640.68]  and you get extra content you get a post
+[2640.68 --> 2642.56]  show I think it's going to be a doozy
+[2642.56 --> 2646.10]  today so thank you to our sre team you
+[2646.10 --> 2648.76]  keep this show up and running you are our
+[2648.76 --> 2650.94]  reliability engineers I want to mention
+[2650.94 --> 2653.22]  that you can find our sponsor a cloud guru
+[2653.22 --> 2655.56]  on social media it's just slash the cloud guru
+[2655.56 --> 2657.12]  on any of the major platforms so like
+[2657.12 --> 2659.88]  youtube.com slash a cloud guru and go
+[2659.88 --> 2661.54]  find them there now I know that you all
+[2661.54 --> 2664.06]  know how to find this with the gargantuan
+[2664.06 --> 2665.74]  amounts of feedback we've had I mean we
+[2665.74 --> 2667.46]  really only got to a small portion of it
+[2667.46 --> 2669.92]  this episode but please do keep sending
+[2669.92 --> 2672.00]  it in because it keeps us vitalized and
+[2672.00 --> 2674.02]  connected with you guys and particularly
+[2674.02 --> 2676.70]  in these present times hearing from you
+[2676.70 --> 2679.36]  helps us keep the show focused on what
+[2679.36 --> 2681.70]  you guys want to hear about so self hosted
+[2681.70 --> 2683.70]  dot show slash contact is the place to go to
+[2683.70 --> 2686.06]  get in touch with us you can find me on
+[2686.06 --> 2687.86]  twitter at ironic badger and I'm there
+[2687.86 --> 2689.86]  too at chris last and the show is at
+[2689.86 --> 2691.46]  self hosted show and don't forget the
+[2691.46 --> 2693.70]  network at jupiter signal thanks for
+[2693.70 --> 2695.44]  listening everybody that was self hosted
+[2695.44 --> 2697.08]  dot show slash 35
+[2697.08 --> 2699.68]  you

36： Google Docs Replacement _summary.txt

@@ -0,0 +1,49 @@
+• Review of Home Assistant's new dedicated hardware
+• Alex's computer lab and server setup, including using QuickSync capable systems
+• Discussion of ITX boards and PCI port limitations
+• Comparison of the benefits and drawbacks of having multiple servers and desktops for various tasks
+• Introduction to HedgeDoc, a modern Google Docs alternative that can be self-hosted
+• HedgeDoc is a collaboration tool for markdown documents
+• It allows real-time editing and rendering of documents
+• Supports features like tags, document library, and shortcuts
+• Can be self-hosted using Docker containers
+• Migrating from Code EMD to HedgeDoc was relatively smooth and straightforward
+• Linode as cloud server provider
+• Backend infrastructure and new projects hosted on Linode
+• Features and capabilities of Linode
+• Home Assistant blue box device
+• Specifications and features of the Odroid N2+ processor in the Home Assistant blue box
+• Comparison to other smart home devices and hubs
+• Price: $180 total cost, including shipping
+• First boot experience: plug in, go to browser, type homeassistant.local
+• Performance comparison: faster than Raspberry Pi 4 with Home Assistant install
+• Hardware: uses a disk (USB) rather than SD card
+• Value proposition: dedicated box for Home Assistant worth under $200
+• Benefits of using Home Assistant on its own dedicated host: improved performance, easier management, and better long-term strategy
+• Power draw and efficiency of the device
+• Compatibility with solar power and off-grid living
+• Device specifications and performance under load and idle conditions
+• Reliability and potential issues with WiFi connectivity in metal housing
+• EMMC write endurance and its implications for long-term use
+• Potential future updates and improvements to the device
+• EMMC storage limitations and potential for data loss
+• Importance of moving logs off of SSDs to prevent wear out
+• Pros and cons of using USB storage vs internal EMMC
+• Docker and container management systems (Rancher OS, Ubuntu)
+• Minimalist Docker setup options and recommendations
+• Ubuntu base with Docker installation
+• Comparison of CentOS Stream as a container platform vs Ubuntu
+• Importance of community support, LTS releases, and cloud support in choosing an OS
+• ZFS and WireGuard support in Ubuntu
+• Concerns about snap packaging system in Ubuntu
+• Discussion of vendor-agnosticism in Linux packaging
+• The importance of vendor neutrality in the Linux ecosystem
+• Comparison of Flatpaks and Snaps, including host-your-own repository capabilities
+• Arch Linux and its AUR package manager as a desirable alternative
+• Use cases for snaps in business settings due to their ability to facilitate vendor relationships and distribution
+• Comparison of Ethernet over coax and Powerline networking, with Ethernet over coax being recommended for better performance
+• The host mentions an "interesting thing" and considers it for a future project
+• A term called "Mocha" is mentioned, but its meaning is unclear
+• Reports from an email are discussed regarding internet speeds (gigabit)
+• The show's reliance on site reliability engineers is mentioned
+• Self-hosted.show membership is promoted as a way to support the show

36： Google Docs Replacement _transcript.txt

@@ -0,0 +1,663 @@
+[0.00 --> 6.32]  Coming up on the show, I review Home Assistant's new dedicated hardware, Alex is literally buried
+[6.32 --> 10.72]  in computers, and our favorite Google Docs killer has a big update. I'm Chris.
+[11.10 --> 13.20]  And I'm Alex, and this is Self Hosted.
+[14.44 --> 21.12]  Oh, Chris, I am surrounded by computer parts. I mean, literally, I could open a shop right now.
+[21.20 --> 25.14]  I've got every single computer I own in pieces right now.
+[25.14 --> 29.44]  I feel your pain. I am surrounded in laptop parts at the moment.
+[30.00 --> 32.16]  Is that because of the XPS reviews you're doing?
+[32.48 --> 36.90]  I have a couple of machines in for review at the moment, plus a personal server project that I'm working on.
+[37.00 --> 42.40]  And then I was moving offices, and I had all of the different screws neatly organized for each laptop case.
+[42.66 --> 48.16]  And my daughter came in and said, what are these, Daddy? And mixed them.
+[48.26 --> 49.24]  Oh, no.
+[50.38 --> 51.18]  Mixed them all.
+[52.92 --> 54.54]  Screws are the worst as well.
+[55.06 --> 55.30]  Yeah.
+[55.66 --> 57.12]  Particularly laptop-sized ones.
+[57.12 --> 60.10]  What are you, what are you, deepen projects over there, several at a time?
+[60.50 --> 61.68]  Yeah, that's just it.
+[61.80 --> 66.04]  So I built a system around the UNAZ and QuickSync a little while ago.
+[66.52 --> 72.20]  But I decided that I wanted something that was a little more future-proof in terms of expansion and stuff like that.
+[72.28 --> 81.74]  And the ITX board that the UNAZ case can fit only has one PCI port, which is taken up with the HBA disk expansion card that I have.
+[81.74 --> 82.46]  Right.
+[82.82 --> 90.88]  And so if I wanted to put, say, OpenSense as a VM on top of Proxmox, I don't have any PCI ports to add an extra NIC to the motherboard.
+[91.52 --> 99.50]  So anyway, I decided to take my desktop motherboard and put it into my Rosewill server case that was housing my Dual Xeon system.
+[99.50 --> 108.08]  Basically, all this comes as a result of me finally deciding to break up with my Dual Xeon system and go all in on QuickSync.
+[108.26 --> 112.12]  It's worked really well for the last month or so as I've been testing it in the UNAZ build.
+[112.30 --> 113.52]  So I'm going all in.
+[113.66 --> 119.28]  My home lab's going to be an i5-8500 and my NAS is going to be also an i5-8500.
+[119.28 --> 123.92]  So, yeah, I'll have two of those QuickSync capable systems in the house.
+[124.24 --> 136.12]  And the idea is that I've got one system that is just sort of always on bulletproof and is running Blue Iris and Home Assistant and DNS separate from the storage,
+[136.30 --> 142.36]  which will be running on the other system, which is housing Plex and media apps and that kind of stuff.
+[142.86 --> 146.54]  Because the one you take offline most of all is the one with the hard drives in it.
+[146.54 --> 154.86]  And it's not like I take it offline a lot, but when I do, it takes everything out because I've got, you know, all of my services running on one box.
+[155.12 --> 163.04]  So it's been a pain because I've had to move all of my desktop out of its case and my server out of its case.
+[163.26 --> 171.32]  And I've got literally four or five computers worth of parts around me and I'm selling stuff off to people and it's nuts.
+[171.94 --> 174.94]  And doing the day job all off a laptop in the meantime, I suppose.
+[174.94 --> 181.98]  Yes. Yeah. And the worst part is my IRC bouncer for Red Hat is currently in pieces on the table behind me.
+[182.02 --> 184.08]  So I haven't been on IRC all day, which has been a bit bad.
+[184.08 --> 193.24]  I was moving offices recently and like literally like my priority was get the desktop, reset up, get everything connected, get it powered on.
+[193.66 --> 194.76]  It's got to be online.
+[195.16 --> 199.82]  The best part was as well that my laptop decided it was going to screw up and I had to reinstall that today as well.
+[199.90 --> 204.88]  So I've completely nuked and paved seemingly everything in this house and I'm starting from scratch.
+[205.22 --> 205.62]  Wow.
+[206.16 --> 206.94]  That's going to be fun.
+[206.94 --> 210.74]  I haven't yet found out what I've forgotten to back up yet, but I'm sure there'll be something.
+[211.36 --> 214.58]  And days of setting small little things up as it always goes.
+[214.78 --> 215.02]  Yeah.
+[215.08 --> 220.82]  Just before we were recorded, for example, I'd turn off Turbo Boost on my Mac so that the fans weren't spinning up.
+[222.02 --> 222.94]  Oh, Max.
+[223.02 --> 230.56]  Well, let's take a moment and say that this episode is brought to you by the all new Cloud Guru, the leader in learning for the cloud for Linux and other modern tech skills.
+[230.56 --> 233.14]  They have hundreds of courses and thousands of hands on labs.
+[233.24 --> 238.44]  So get certified, get hired and get learning at a cloud guru dot com.
+[238.78 --> 249.14]  One of the things I have in my new office is a bench for projects and I have the new Home Assistant blue hardware on there, which I'm going to be talking about in a little bit in the show.
+[249.14 --> 264.14]  But in the meantime, before we get there, Alex and I kind of wanted to do a PSA on the show and talk a moment about HedgeDoc, which might be a solution for anyone out there who wants a really modern Google Docs alternative that you can self host.
+[264.50 --> 266.84]  And it happens to be an excellent markdown editor.
+[267.80 --> 271.34]  Real time collaborative editing for markdown documents.
+[271.60 --> 272.48]  It's great.
+[272.72 --> 275.04]  You know, we've used it at JB now for how long?
+[275.14 --> 275.68]  Two years?
+[275.82 --> 276.02]  Three?
+[276.62 --> 276.88]  Yeah.
+[276.88 --> 276.96]  Yeah.
+[277.24 --> 278.90]  So it's it stood the test of time.
+[279.02 --> 280.50]  Battle tested in production.
+[280.84 --> 281.28]  Air quotes.
+[282.04 --> 284.80]  Use it for all the LUP show notes as well and stuff like that.
+[284.88 --> 285.96]  And you and Wes use it.
+[286.22 --> 287.42]  And we use it for all the shows.
+[287.58 --> 290.92]  And now I use it for a lot of my notes just for JB stuff in general.
+[291.28 --> 294.24]  It's the project for formerly known as Cody MD.
+[294.60 --> 300.94]  They went through a name change to annoy just to avoid like naming conflicts out there.
+[300.94 --> 303.02]  I guess there was another project that's had a similar name.
+[303.02 --> 309.14]  And so now it's called HedgeDoc and it lets you just easily collaborate on markdown documents.
+[309.30 --> 312.20]  And all you really have to do is get started and you just share a link with somebody.
+[312.44 --> 314.40]  And now they're in and they can start editing.
+[314.60 --> 318.50]  And then if you create an account, you get kind of like a document library.
+[318.50 --> 326.84]  And it supports things like tags, which we don't use a lot, but it supports things that allow you to recall documents pretty quickly or categorize documents.
+[327.34 --> 332.56]  It also does real time rendering of that markdown so you can see what you're writing in real time.
+[332.56 --> 334.82]  And then it gives you a bunch of shortcuts.
+[335.06 --> 338.76]  So maybe you don't remember how to do a table and markdown or embed an image.
+[338.80 --> 340.04]  It's got a button for that as well.
+[340.28 --> 340.62]  It does?
+[341.14 --> 341.34]  Yeah.
+[341.42 --> 342.06]  I didn't know that.
+[342.06 --> 343.96]  Right along the top there.
+[344.56 --> 344.68]  Yeah.
+[344.98 --> 351.10]  And Alex, you recently reset it up for us because we were on an older Code EMD instance.
+[351.50 --> 352.06]  Yeah, that's right.
+[352.10 --> 354.40]  There's nothing more permanent than a temporary solution, right?
+[354.66 --> 354.92]  Yeah.
+[355.28 --> 358.46]  Wes threw it up on a, was it a droplet or something a couple of years ago?
+[358.46 --> 362.46]  We wanted to test it for an episode of Linux Unplugged or something like that.
+[362.46 --> 365.10]  And then we liked it so much, we just kept using it.
+[365.30 --> 365.78]  That's right.
+[366.14 --> 366.16]  So typical.
+[366.56 --> 370.68]  And it was just hanging out on an open port with no TLS or anything.
+[370.68 --> 372.74]  So I've been wanting to fix that for a while.
+[372.84 --> 378.30]  So when I saw the renaming come through on the Linux server image, I was just like, yes,
+[378.50 --> 381.54]  here's my excuse to push it to Chris and say, I can do it.
+[382.00 --> 382.10]  Yep.
+[382.38 --> 385.38]  So yeah, Wes sent me the database.
+[385.84 --> 393.12]  He zipped up the Docker app data volume that stores the database and stuff like that,
+[393.86 --> 400.38]  span it up in a container on Linode with just SCP the tar.gz file across.
+[401.14 --> 404.54]  Unzipped it, pointed the container at the correct directory.
+[405.20 --> 408.60]  And I think it uses Postgres on the backend, our setup.
+[409.38 --> 414.34]  All the infrastructure, by the way, is open sourced on the self-hosted infra wiki.
+[414.94 --> 415.36]  Not wiki.
+[415.84 --> 416.16]  GitHub.
+[416.54 --> 417.14]  GitHub repo.
+[417.14 --> 420.88]  So, but yeah, it just came straight up.
+[421.06 --> 422.30]  You know, there was no drama.
+[422.50 --> 426.94]  The only slightly tricky bit was that you own the domain name and we had to point the name
+[426.94 --> 432.90]  service for the domain name at my Cloudflare account so that we could get TLS through traffic
+[432.90 --> 435.14]  working with the DNS challenge.
+[435.14 --> 437.28]  Yeah, but I love what we ended up with.
+[438.14 --> 443.06]  It's a cute little URL that's easy for the team to remember and it makes it possible to
+[443.06 --> 446.92]  share easily with anybody and they'll remember it as well.
+[447.08 --> 452.68]  So I think it turned out to be a pretty nice setup and maybe the perfect time to migrate.
+[453.12 --> 458.68]  I mean, it seems like it was nearly flawless to import a somewhat stale Code EMD database
+[458.68 --> 460.10]  right into HedgeDoc.
+[460.10 --> 466.14]  So if you're using Code EMD today, it's probably a good time to upgrade because that migration
+[466.14 --> 467.24]  is pretty simple right now.
+[467.72 --> 468.08]  Easy peasy.
+[468.20 --> 470.96]  Yeah, there's a couple of options for containers that you could use.
+[471.48 --> 474.52]  Linux server, of course, make a container for this one.
+[475.10 --> 481.20]  They've migrated over from Code EMD to HedgeDoc, but I actually ended up for our installation
+[481.20 --> 484.04]  here using the one that the development team now provide.
+[484.54 --> 488.50]  This is the thing about Linux server is a lot of their images make projects popular enough
+[488.50 --> 491.12]  that the devs go, oh, we've got lots of people using it in Docker.
+[491.80 --> 494.34]  And then the projects themselves start providing an image.
+[494.52 --> 499.06]  And generally speaking, I will keep using the Linux server image until I have good reason
+[499.06 --> 499.98]  to switch.
+[500.62 --> 505.00]  And the migration seemed like a perfect excuse, as you say.
+[505.18 --> 508.72]  So we're running out of the official HedgeDoc image.
+[509.18 --> 510.38]  And yeah, it just works.
+[510.46 --> 512.32]  And there's nothing more really to say about that.
+[512.32 --> 518.56]  It's the best kind of tool because admittedly, it takes a little more skill set and a little
+[518.56 --> 523.02]  more effort than just going and signing up for a Google Docs, for, you know, signing
+[523.02 --> 525.46]  into a Google Docs account and using Google Docs.
+[525.50 --> 526.98]  Like it takes a little more effort than that.
+[527.50 --> 528.40]  But we own this.
+[528.46 --> 529.34]  It's self-hosted.
+[529.34 --> 533.04]  And we get to have fun with the domain because of that.
+[533.24 --> 537.04]  We get to just sort of own the entire stack.
+[537.46 --> 544.02]  And that's great because it's a tool we use every single day, six days a week to produce
+[544.02 --> 544.56]  the shows.
+[545.16 --> 550.26]  And replicate the data from the backend to a local endpoint.
+[550.50 --> 552.68]  So it's completely backed up offline.
+[552.98 --> 557.60]  So that if for any reason that Linode ever had a problem, we're good to go.
+[559.34 --> 561.48]  Linode.com slash SSH.
+[561.60 --> 565.50]  Go there to get a $100 60-day credit towards a new account and support the show.
+[565.86 --> 569.10]  Like Alex was saying, they are our cloud server provider.
+[569.32 --> 570.60]  We have the wiki on there.
+[570.72 --> 572.48]  Perfect Media Server dot com is on there.
+[572.56 --> 573.86]  HedgeDoc's on there and a lot more.
+[574.22 --> 575.58]  We have the Matrix server on there.
+[576.22 --> 577.74]  We have our Cast and Coding server.
+[577.90 --> 578.52]  Next Cloud.
+[578.96 --> 583.32]  A lot of our backend infrastructure and new things that we're working on that we haven't even
+[583.32 --> 583.68]  announced.
+[583.82 --> 585.46]  We're hosting them all on Linode.
+[585.98 --> 589.18]  And personally, one of the things that I think is great about Linode is all the
+[589.18 --> 590.18]  distributions they support.
+[590.28 --> 595.20]  So whatever environment you're comfortable working in, even the Alpines, Arch, recent
+[595.20 --> 600.70]  CentOS releases, Debian, Fedora, OpenSUSE, several versions of Ubuntu, on and on and on.
+[601.52 --> 606.38]  But what I really like about Linode is you can tell when a company is passionate about the
+[606.38 --> 607.56]  actual technology.
+[608.24 --> 610.78]  And I think people listening to the show probably get that.
+[610.78 --> 614.90]  When you're passionate about the technology, you have the insight into what it's capable of.
+[614.90 --> 622.08]  And that's why Linode started in 2003 as one of the very first companies and in something we
+[622.08 --> 623.94]  weren't even really calling cloud computing yet.
+[624.02 --> 627.58]  That was three years before AWS even started.
+[627.78 --> 630.34]  And now they're the largest independent cloud provider.
+[630.34 --> 638.44]  And you can get a $100 credit and play with infrastructure that's professional grade with native SSDs,
+[638.48 --> 643.46]  40 gigabit connections to the hypervisors, 11 data centers around the world, object storage,
+[643.94 --> 648.26]  node balancers, a really nice, clean dashboard.
+[648.90 --> 651.34]  You can get started at linode.com slash SSH.
+[652.02 --> 655.98]  You go there, get that $100 60-day credit towards a new account and support the show.
+[655.98 --> 659.62]  So that's linode.com slash SSH.
+[661.48 --> 662.18]  All right, then.
+[662.22 --> 664.38]  Why don't you tell me about this Home Assistant blue box?
+[664.48 --> 667.04]  I've been pretty jealous, honestly, since I heard you got yours.
+[667.38 --> 668.88]  You know, it's real.
+[669.14 --> 673.96]  I was watching the Home Assistant conference when they announced it, and I ordered one as
+[673.96 --> 674.76]  fast as I could.
+[674.84 --> 678.16]  A lot of other people did, too, because the order page was having issues.
+[678.16 --> 684.88]  But it is a small, tiny, I mean, it's not as small as a Raspberry Pi, but it's smaller
+[684.88 --> 687.76]  than a NUC or any kind of desktop PC.
+[688.42 --> 692.42]  And it is a dedicated Home Assistant box, and it's called the Home Assistant blue.
+[692.68 --> 695.22]  It's a six-core ARM processor system.
+[695.30 --> 697.64]  It has four gigs of DDR4 RAM.
+[697.64 --> 705.56]  And a big upgrade over the Raspberry Pi 4 is it comes with 128 gigabytes of eMMC storage.
+[705.78 --> 710.04]  Plus, of course, there's other ways to expand that, like through USB, because it has four
+[710.04 --> 716.28]  USB 3.0 ports on the sucker, as well as an Ethernet and full HDMI out.
+[716.84 --> 720.44]  And it's really well built, Alex.
+[720.60 --> 722.20]  It's very, very solid.
+[722.52 --> 727.60]  I would feel comfortable with this strapped to the RV going down the road for years.
+[727.96 --> 729.40]  On the inside or the outside?
+[731.00 --> 732.10]  Definitely the inside.
+[732.64 --> 734.70]  But the top is a nice blue aluminum.
+[734.96 --> 739.14]  They've made it look really nice with a classy white version of the Home Assistant logo.
+[739.40 --> 742.98]  And the bottom is an integrated heatsink system.
+[743.12 --> 743.52]  Oh, neat.
+[743.76 --> 744.34]  How big is it?
+[744.34 --> 753.28]  It's about four inches wide and about, I'd say about an inch and a half high at its peak,
+[753.38 --> 755.70]  maybe, because it's kind of got an arched shape to the case.
+[756.10 --> 758.68]  And it's about half a pound in weight.
+[758.80 --> 760.66]  So it's just over half a pound.
+[760.76 --> 763.36]  So it's got a really solid, hefty feel to it.
+[763.80 --> 766.40]  So it's like, what, a couple of CD cases stacked on top of each other?
+[766.74 --> 769.68]  Yeah, with a little bit of an arch at the top of it.
+[770.30 --> 774.10]  And what's really at the heart of this thing is an Odroid N2+.
+[774.10 --> 775.86]  That's really what this is.
+[776.36 --> 780.78]  I've noted that the Home Assistant team has mentioned the Odroid N2+, a few times, and
+[780.78 --> 785.90]  it seemed to be one of the favorite devices of one of the primary Home Assistant developers.
+[786.56 --> 790.26]  So I think this box is kind of like their favorite experience.
+[790.26 --> 792.64]  It's the one that they personally test on.
+[792.64 --> 796.66]  And so to say it's well-supported is an understatement.
+[797.00 --> 801.02]  And so I think it was a natural fit for them to just bundle it when they partnered up with
+[801.02 --> 801.80]  a hardware provider.
+[802.28 --> 805.66]  In terms of a smart home hub, it's lacking a couple of things.
+[805.76 --> 810.18]  You need to add Z-Wave or ZigBee via USB, right?
+[810.48 --> 810.70]  Yep.
+[810.78 --> 814.66]  Although that's the same kind of trade-off you have with any of these other kind of ARM boards,
+[814.66 --> 821.26]  because it's kind of competing between something like a smart things home hub and a Raspberry
+[821.26 --> 822.36]  Pi DIY kit.
+[822.46 --> 824.68]  It's like trying to live in that middle ground there.
+[825.16 --> 826.42]  So remind me of the price then.
+[826.50 --> 827.00]  How much was it?
+[827.36 --> 835.04]  It's listed for $140, but after all in for me with $21 and change of shipping, it was $180
+[835.04 --> 836.70]  total to get this device.
+[837.14 --> 837.38]  Ooh.
+[837.88 --> 838.20]  Okay.
+[838.32 --> 841.46]  I had 100 in my mind for some reason, but 180.
+[841.78 --> 842.00]  Wow.
+[842.18 --> 842.38]  Okay.
+[842.56 --> 843.68]  That's getting up there.
+[843.68 --> 844.46]  Well, okay.
+[844.62 --> 846.24]  So I'll get to the value.
+[846.48 --> 850.44]  So the first boot experience, they're trying to make it very out-of-the-box friendly.
+[850.58 --> 851.70]  Two steps to set up.
+[852.00 --> 857.00]  You plug it in to your network and then go to your browser and you type in homeassistant.local
+[857.00 --> 858.56]  and it's supposed to just come up.
+[858.94 --> 860.50]  But of course, that's not how it works on my network.
+[860.58 --> 864.64]  I already have a DNS and DHCP server set up and my system isn't just going to start resolving
+[864.64 --> 865.74]  some new machine.
+[866.30 --> 868.78]  But I was able to get the IP out of the DHCP log.
+[868.84 --> 869.36]  Pretty simple.
+[869.78 --> 870.42]  Put that in.
+[870.52 --> 871.96]  Went to port 8123.
+[871.96 --> 875.66]  And it's really at this point, it's a basic home assistant install.
+[875.82 --> 879.56]  It's really kind of just what you'd expect if you'd set up the home assistant suite with
+[879.56 --> 880.80]  supervisor and everything.
+[881.22 --> 882.88]  You create the first time account.
+[883.78 --> 886.46]  But Alex, it feels fast.
+[886.56 --> 891.76]  It definitely feels noticeably faster in the UI than my Raspberry Pi 4.
+[891.90 --> 894.90]  Granted, it's a new, happy, fresh install.
+[894.90 --> 898.64]  But I've set up home assistant enough times on the Pi to know what it feels like.
+[898.74 --> 901.64]  And I can tell you with confidence, this thing absolutely feels faster.
+[902.22 --> 904.20]  Are you SD card based in the Pi then?
+[904.66 --> 904.96]  USB.
+[905.28 --> 906.06]  So it is on a disk.
+[906.20 --> 906.58]  Oh, really?
+[906.88 --> 907.12]  Yeah.
+[907.22 --> 908.08]  That's interesting then.
+[908.32 --> 909.52]  I think it's just got a little more horsepower.
+[910.06 --> 912.90]  And I think the developers are optimizing for this thing.
+[912.90 --> 917.66]  That's why, you know, when we talk about the value, so I'd say round it off to $200 or just
+[917.66 --> 921.14]  under $200, you know, just as a concept price point.
+[922.04 --> 929.46]  Well, what is a totally local, merges all the different vendors together with no subscription
+[929.46 --> 935.48]  and is completely under your control, standalone box worth?
+[935.48 --> 942.12]  So to me, home assistant, home assistant is one of the few open source projects that has
+[942.12 --> 947.62]  changed my life at the level that, like say Linux has, where it has, it has changed.
+[947.82 --> 951.56]  It has changed the quality of life for my entire family.
+[952.20 --> 957.72]  And I also use it here at the studio to help with remote presence and other, other like,
+[957.76 --> 959.42]  you know, just light management in the studio.
+[959.76 --> 962.36]  And so it also helps in a professional capacity.
+[962.36 --> 964.94]  So $200 for a dedicated box.
+[965.02 --> 966.02]  It's really fast.
+[966.10 --> 967.38]  It feels very well built.
+[967.48 --> 973.60]  I mean, it feels like a polished product that is also supporting home assistant development
+[973.60 --> 975.00]  at the same time when I buy it.
+[975.60 --> 975.84]  Mm-hmm.
+[976.02 --> 976.36]  Mm-hmm.
+[976.66 --> 978.64]  I feel like that's, you know, under $200.
+[978.90 --> 980.18]  It is a good value for this.
+[980.20 --> 981.92]  And I think I'm actually going to buy another one.
+[982.04 --> 984.70]  I'm going to buy one for the studio because this is what I set this one up for.
+[984.74 --> 988.90]  I wasn't sure if I was ready to deploy my serious, serious home assistant setup yet.
+[988.90 --> 993.56]  So I put it in production here at the studio where it's, it's kind of important, but honestly,
+[993.72 --> 995.28]  like I could recreate it in a day.
+[995.54 --> 995.98]  You know what I mean?
+[996.16 --> 1003.54]  It's that level of, but at home, like, I just, I mean, I would take a snapshot and I would
+[1003.54 --> 1008.22]  restore the snapshot, but it just has to be perfect at home because it literally impacts
+[1008.22 --> 1009.00]  our quality of life.
+[1009.10 --> 1013.30]  So I wanted to take it slow and I wasn't sure if I was ready to replace my raspberry pie,
+[1013.30 --> 1019.02]  but I am a believer in having home assistant on its own dedicated host, either being a
+[1019.02 --> 1020.32]  VM or on hardware.
+[1020.66 --> 1025.78]  And I don't necessarily think having it live alongside a lot of my other services in Docker
+[1025.78 --> 1030.34]  while trying to also use the supervisor is a good long-term strategy.
+[1030.34 --> 1034.24]  Like in there, it gives me errors about being on an unsupported OS all the time.
+[1034.36 --> 1039.92]  And I look at the development trajectory and I think if they're selling these machines and
+[1039.92 --> 1043.16]  they are themselves are developing, like you have to imagine the developers all have these,
+[1043.16 --> 1044.26]  or we'll all have these.
+[1045.26 --> 1047.72]  That's likely where they're going to invest a lot of their time and energy and they're
+[1047.72 --> 1051.16]  going to be developing with a mindset that they're doing it on a dedicated host.
+[1051.66 --> 1055.98]  When I look at the power draw for this thing and I look at the, you know, I got to always
+[1055.98 --> 1056.64]  do that math.
+[1056.72 --> 1062.10]  Like if I bring a box in, I really have to be aware of what it's going to take because
+[1062.10 --> 1064.32]  I want to be able to go off grid.
+[1064.44 --> 1068.06]  I want to be able to survive on solar power alone, which means I got to extend the life of
+[1068.06 --> 1069.68]  my batteries as long as possible.
+[1069.68 --> 1075.38]  And this thing under load, and I'm not, you know, I didn't, I didn't do extensive testing
+[1075.38 --> 1078.58]  here, but it went, it was right in line with what their specs were.
+[1079.20 --> 1080.00]  Six Watts.
+[1080.66 --> 1081.84]  That's pretty remarkable.
+[1082.72 --> 1083.18]  Six Watts.
+[1083.36 --> 1083.52]  Wow.
+[1084.02 --> 1084.30]  Yeah.
+[1084.68 --> 1088.52]  And, and around idle, it was around two Watts, sometimes two and a half Watts.
+[1089.10 --> 1091.26]  I only really started testing it today.
+[1091.26 --> 1095.40]  So I want to do more extensive testing, like, because it's a pretty simple home assistant install,
+[1095.40 --> 1099.18]  but I was monitoring during the first load and getting all that stuff like first set up.
+[1099.20 --> 1103.06]  And I monitored a little bit under, under just sitting there idle, you know, just like kind
+[1103.06 --> 1104.46]  of just daily, just sitting there running.
+[1105.08 --> 1105.80]  That's what I noted.
+[1105.84 --> 1106.40]  And I went and checked.
+[1106.48 --> 1108.48]  I looked up their specs for this, for this board.
+[1108.54 --> 1110.14]  That's exactly what it's in line with the specs.
+[1110.40 --> 1115.76]  Pretty sure my garage door opener uses more than six Watts just sat there doing nothing all
+[1115.76 --> 1115.92]  day.
+[1116.84 --> 1120.90]  I know there's power bricks that just sit there and plugged into the wall that use more than
+[1120.90 --> 1121.38]  two Watts.
+[1121.38 --> 1122.06]  Uh, yeah.
+[1122.32 --> 1126.60]  So we'll see because that's the, that's the big deal breaker is if that ends up being
+[1126.60 --> 1131.68]  a higher, higher load wattage, uh, that would be, that'd be a deal breaker.
+[1131.68 --> 1137.04]  But at this point, I think plugging in a device that would be using around six Watts would be
+[1137.04 --> 1139.42]  kind of just lost in the wash.
+[1139.50 --> 1141.24]  I don't think I'm really going to notice that on my runtime.
+[1141.50 --> 1145.02]  So I think it means from a power budget standpoint, I can put this thing in production.
+[1145.88 --> 1147.66]  I think, I think I'm going to get another one.
+[1148.14 --> 1151.02]  You do like highly available single board computers though, don't you?
+[1151.02 --> 1153.96]  So there is something to this.
+[1154.04 --> 1158.62]  You could, you know, if a guy really wanted, he could buy two of these.
+[1158.62 --> 1162.18]  I'm not saying he should, but he could, and just keep one in the drawer, right?
+[1162.50 --> 1162.66]  Yeah.
+[1162.98 --> 1163.14]  Yeah.
+[1163.30 --> 1165.12]  And keep a snapshot somewhere.
+[1165.78 --> 1170.50]  And if one pops you in, in 35 seconds, you pull it out.
+[1170.58 --> 1171.62]  All the plugs are all the same.
+[1171.68 --> 1175.60]  You swap it in and you restore the snapshot and you're back in business.
+[1175.60 --> 1182.24]  But if ever there is a use case for a literal plug and play appliance, it's your smart home
+[1182.24 --> 1182.48]  hub.
+[1182.80 --> 1183.02]  Yeah.
+[1183.12 --> 1185.06]  And this is version one, right?
+[1185.14 --> 1189.56]  And maybe even, and I'm not, I'm not knocking it when I say this, but maybe it's even version
+[1189.56 --> 1194.56]  0.5 because I have a sense this kind of came along during the year and it's, it's, it's a
+[1194.56 --> 1196.96]  really good, it's a really good first, first start.
+[1196.96 --> 1203.16]  But I could see future ones that maybe have things like Zigbee or Z-Wave or, or whatever
+[1203.16 --> 1206.72]  this new conglomerate standard is that I can't remember.
+[1207.30 --> 1209.02]  Makes me think of the XKCD comic.
+[1210.02 --> 1210.42]  Yeah.
+[1210.60 --> 1211.88]  Just one more standard, Alex.
+[1211.92 --> 1212.48]  That's all we need.
+[1212.82 --> 1213.64]  There are 12 standards.
+[1213.72 --> 1215.40]  We should have one that unifies them all.
+[1215.66 --> 1215.80]  Okay.
+[1215.84 --> 1217.00]  Now we have 13 standards.
+[1217.24 --> 1217.42]  Great.
+[1218.34 --> 1222.38]  Also they, you know, one that has wifi built in, I don't know how they would handle it with
+[1222.38 --> 1226.44]  the metal housing because I think the casing is providing some heat transfer.
+[1226.44 --> 1228.14]  It's mostly cool to the touch.
+[1228.24 --> 1230.92]  The bottom's warm, but that's, that's kind of expected.
+[1231.02 --> 1231.46]  It's a heat sink.
+[1231.78 --> 1236.94]  Is, is wifi the right kind of expectation to set for reliability for this type of device
+[1236.94 --> 1237.18]  though?
+[1237.50 --> 1239.50]  Probably in that light, it's probably a good thing.
+[1239.56 --> 1241.02]  They at least didn't put it in 1.0.
+[1241.42 --> 1241.60]  Right.
+[1242.16 --> 1247.04]  I'll tell you one thing that I am just a little concerned about, and I'd be really curious
+[1247.04 --> 1253.96]  to see how this actually plays out in the longterm for you is EMMC write endurance is not
+[1253.96 --> 1255.74]  famously very good.
+[1256.08 --> 1261.20]  So I'd be curious to see how home assistant, which writes a lot of data to that database
+[1261.20 --> 1266.44]  all the time will be, you know, in, in a year or two's time, whether it'll have burnt
+[1266.44 --> 1267.48]  through that flash or not.
+[1267.48 --> 1267.92]  Yeah.
+[1268.08 --> 1273.76]  And I wouldn't be surprised if they have a way to switch it to USB storage.
+[1273.76 --> 1278.52]  Cause I do remember there being some discussion about that during the product launch, but going
+[1278.52 --> 1282.26]  through like the first time setup process, there's nothing that prompts you to store it
+[1282.26 --> 1282.90]  anywhere else.
+[1283.06 --> 1284.24]  You know, it's all on that EMMC.
+[1284.60 --> 1286.56]  I got bitten with a PF sense box.
+[1286.56 --> 1292.78]  Uh, this was, um, one of the APU one D boxes, I think several years ago, I didn't move the
+[1292.78 --> 1295.42]  logs off of the, uh, M SATA SSD.
+[1295.66 --> 1301.86]  So obviously M SATA is different to EMMC, but just to tend, you know, a related comment
+[1301.86 --> 1306.76]  really that if you don't move logs off of SSDs, they can wear out pretty quickly.
+[1307.60 --> 1307.62]  Yeah.
+[1307.64 --> 1311.42]  I had a free NAS box that had the EMMC finally die on it.
+[1311.56 --> 1312.58]  It was a really old one.
+[1312.58 --> 1314.72]  It was like an appliance version that somebody prebuilt.
+[1315.82 --> 1319.58]  And, um, that's when I learned that those things have a limit.
+[1319.92 --> 1323.96]  Actually, that's when I learned that it was actually even using EMMC.
+[1326.08 --> 1327.62]  And then I learned they had a limit.
+[1328.62 --> 1329.28]  So you're right.
+[1329.36 --> 1330.66]  That's a good thing to keep an eye on.
+[1330.74 --> 1335.08]  I'm also going to, if I was going to put it in production, I would prefer to have all
+[1335.08 --> 1339.48]  of the home assistant data and anything that needs a lot of read, write on external storage.
+[1339.54 --> 1341.26]  I mean, the thing has plenty of USB ports.
+[1342.58 --> 1348.50]  I want to take a moment and mention that a cloud guru has learn Docker by doing, which
+[1348.50 --> 1353.42]  is a course that gives you a series of hands-on labs that are picked to showcase Docker and
+[1353.42 --> 1354.34]  gain experience with it.
+[1354.38 --> 1355.82]  You hear us talk about Docker all the time.
+[1356.06 --> 1359.46]  If you want to learn Docker, you can learn it faster and better when you learn by doing.
+[1359.76 --> 1361.42]  So check out the link in the show notes.
+[1361.82 --> 1366.34]  They have a fundamentals course that features a 100% hands-on experience.
+[1366.96 --> 1370.72]  Everything in the course is inside a real Linux environment provisioned with whatever you
+[1370.72 --> 1374.38]  need through ACG's hands-on lab and cloud playground platform.
+[1374.92 --> 1375.78]  There's no reason to wait.
+[1376.10 --> 1377.38]  Learn by doing today.
+[1377.56 --> 1379.24]  Get started at thecloudguru.com.
+[1379.24 --> 1380.90]  Hello, people.
+[1381.28 --> 1381.76]  Wake up.
+[1381.96 --> 1383.24]  Chris and the Badger.
+[1383.36 --> 1383.68]  Morning.
+[1384.06 --> 1384.74]  All right, let's go.
+[1384.82 --> 1385.22]  Let's go.
+[1385.30 --> 1385.82]  Let's get up.
+[1385.96 --> 1387.64]  Or whenever you happen to listen to it, I guess.
+[1387.88 --> 1389.42]  On selfhosted.show.
+[1390.26 --> 1391.06]  Isn't that amazing?
+[1391.40 --> 1392.68]  That's so good.
+[1393.00 --> 1396.50]  That's exactly what I was thinking of when I was talking about it.
+[1396.58 --> 1397.92]  Do you know who sent that in?
+[1397.96 --> 1399.42]  Because it's pure amazement.
+[1399.66 --> 1400.14]  I do.
+[1400.24 --> 1400.46]  Yeah.
+[1400.64 --> 1403.20]  Someone on the Discord with the username, oh, yeah.
+[1403.88 --> 1405.10]  That's perfect, actually.
+[1405.66 --> 1406.06]  Wow.
+[1406.80 --> 1407.82]  Yeah, I really like that.
+[1407.94 --> 1409.04]  Yeah, I could see it, Alex.
+[1409.18 --> 1413.84]  You know, you and I in another reality, we're just two morning AM DJs talking about people's
+[1413.84 --> 1416.66]  tech problems and telling people about the morning commute.
+[1417.06 --> 1417.96]  And the traffic.
+[1418.38 --> 1418.50]  Yeah.
+[1418.54 --> 1418.88]  Yes.
+[1419.40 --> 1420.70]  Let's cut to the chopper.
+[1421.06 --> 1421.24]  Yeah.
+[1421.84 --> 1424.00]  We'd be good at it, I think, though, you know.
+[1424.18 --> 1425.00]  Are we silly enough?
+[1425.00 --> 1428.06]  Your whole bit would be like a silly face holding a coffee cup, right?
+[1428.14 --> 1429.88]  And my thing would be hats.
+[1429.88 --> 1434.58]  But it's a radio show, so it only works in the promotional material.
+[1435.32 --> 1439.40]  We had a question from Gone in a Flash on Twitter, and he asked,
+[1439.68 --> 1445.02]  I'm thinking about retiring my Docker on Rancher OS setup as it doesn't support Docker Compose.
+[1445.58 --> 1449.90]  What's the most supported and easy way to manage an alternative Docker system?
+[1450.08 --> 1450.98]  Is it something on Ubuntu?
+[1451.56 --> 1454.12]  Is that light and small as possible?
+[1454.34 --> 1454.66]  Thanks.
+[1455.06 --> 1455.64]  Gone in a Flash.
+[1455.64 --> 1460.72]  So he wants to move off of Rancher OS and embrace the Docker Compose lifestyle and is
+[1460.72 --> 1462.88]  wondering what the simplest minimalist stack is.
+[1463.64 --> 1463.86]  Whew.
+[1464.56 --> 1468.06]  That's a hard question to answer because we don't know exactly what his use case is.
+[1468.40 --> 1469.42]  What would you go, though?
+[1469.48 --> 1470.44]  What would be your go-to?
+[1471.20 --> 1472.18]  Perfectmediaserver.com.
+[1473.04 --> 1473.38]  Yeah.
+[1473.62 --> 1474.82]  That's an Ubuntu base, right?
+[1475.30 --> 1475.58]  Yeah.
+[1475.58 --> 1478.38]  So I base that off of Ubuntu 2004.
+[1479.08 --> 1483.86]  I use an answerable role by GeelingGuy to install Docker.
+[1484.42 --> 1487.38]  Although you could, of course, just install Docker however you like.
+[1488.22 --> 1490.26]  Install Docker Compose, and that's it.
+[1490.30 --> 1490.56]  You're done.
+[1490.88 --> 1492.04]  Really isn't a lot to it.
+[1492.38 --> 1495.36]  I think it's funny that this is coming from a Red Hat employee.
+[1495.54 --> 1501.84]  If anybody ever needed proof that Alex is independent and speaks his mind, there you have it.
+[1501.84 --> 1506.28]  But I think that's a fantastic setup, too, because the community support is huge.
+[1506.72 --> 1511.92]  The free five-year patches from Canonical on an LTS are pretty tough to beat at this point.
+[1513.88 --> 1516.80]  There's other games in town, but yeah.
+[1517.34 --> 1521.04]  Well, I've avoided commenting on the whole CentOS thing quite deliberately,
+[1521.04 --> 1523.76]  because obviously Red Hat pay my mortgage.
+[1524.02 --> 1530.14]  But, you know, I feel somewhat vindicated in my choice of using Ubuntu for my personal systems
+[1530.14 --> 1534.80]  and keeping that separation between work and pleasure with all this news.
+[1535.02 --> 1537.16]  So it's been an interesting time.
+[1537.62 --> 1542.10]  I know this is what nobody wants to hear right now because it's just too damn reasonable and low-key,
+[1542.38 --> 1549.10]  but I will go on record right now in early 2021 and say that I bet you CentOS Stream
+[1549.10 --> 1551.90]  makes for an excellent containers platform.
+[1552.22 --> 1557.48]  If you wanted to run Docker or Podman, CentOS could make a great host OS,
+[1557.48 --> 1560.90]  because, I mean, what was the thing that people loved about Core OS?
+[1561.38 --> 1566.96]  It was essentially rolling updates at an enterprise scale for an enterprise distribution to run your containers.
+[1567.86 --> 1570.22]  And what's CentOS Stream now?
+[1570.70 --> 1576.48]  It's going to be a consistently updated rolling enterprise-grade distribution that can run your containers.
+[1576.98 --> 1583.68]  I think it's worth considering going down that route, especially if you work with Red Hat systems.
+[1583.68 --> 1587.38]  But otherwise, I just really have to agree with Alex.
+[1587.84 --> 1593.30]  I think the Ubuntu ecosystem makes for a fantastic home server because there's such a good community support system out there.
+[1593.74 --> 1597.38]  Canonical really has their eye on the ball when it comes to their LTS releases.
+[1598.00 --> 1600.54]  And cloud support is just fantastic as well.
+[1601.16 --> 1603.60]  I mean, you could go with Debian without much penalty.
+[1603.82 --> 1606.78]  The reason that I go with Ubuntu really is for a couple of reasons.
+[1607.16 --> 1610.68]  The first is ZFS support baked right into the kernel.
+[1610.68 --> 1613.20]  That may or may not be important to you.
+[1613.40 --> 1616.28]  The other one is WireGuard support baked right in as well.
+[1616.36 --> 1619.88]  So for both of those things, you only have to install the user space tool.
+[1619.98 --> 1623.26]  You don't have to do any DKMS modules or anything crazy like that.
+[1623.78 --> 1625.58]  You could do the same thing on Debian.
+[1625.84 --> 1631.94]  And arguably, you know, if you're a freedom-respecting person, like I purport to be,
+[1632.20 --> 1633.74]  I should be running Debian everywhere.
+[1633.74 --> 1637.30]  But I don't like DKMS, so I run Ubuntu everywhere.
+[1637.30 --> 1637.58]  Yeah.
+[1637.80 --> 1643.00]  And having seen a bit behind the curtain for the Ubuntu development process,
+[1643.36 --> 1648.14]  I am keenly aware of the kind of attention that Canonical puts into an LTS.
+[1648.32 --> 1650.64]  It's not that they don't put a lot of work into their other releases,
+[1650.98 --> 1655.18]  but they really want to make sure that thing is enterprise-grade and supportable
+[1655.18 --> 1657.30]  for the time that they're committed to support it.
+[1657.30 --> 1663.30]  And that means it just gets a level of polish and pass that maybe Debian 9 doesn't.
+[1663.30 --> 1665.92]  I just wish they'd stop pushing snaps.
+[1666.54 --> 1670.08]  You know, it's such easy fodder for people when they come to me and say,
+[1670.14 --> 1673.18]  oh, you shouldn't use Ubuntu because snaps are horrible.
+[1673.76 --> 1677.32]  And, you know, when I want to install Docker, I don't want to install Docker as a snap.
+[1677.40 --> 1678.86]  I just want it as a package and stuff.
+[1678.94 --> 1679.68]  And I'm like, yeah.
+[1679.84 --> 1680.56]  Well, yeah.
+[1680.60 --> 1684.66]  I mean, you can go and grab the Docker dev file from wherever you like and install it.
+[1684.70 --> 1685.84]  But the default is a snap.
+[1685.94 --> 1688.20]  And as I always say, default is king.
+[1688.52 --> 1690.74]  So yeah, I'm torn on that.
+[1690.74 --> 1692.64]  I myself don't prefer it.
+[1692.78 --> 1698.16]  But I've also heard from audience members who dip their toes into NextCloud for the first time
+[1698.16 --> 1701.48]  because it was just a snap away and it was approachable for them.
+[1701.76 --> 1705.24]  And, you know, like we got that email from the one guy who set it up on a snap first
+[1705.24 --> 1707.22]  and then migrated it to a whole instance afterwards.
+[1708.00 --> 1714.66]  I just don't like, I suppose, how snap is an Ubuntu canonical thing.
+[1714.66 --> 1719.06]  I don't know, I can't really explain it or articulate it very well,
+[1719.20 --> 1722.50]  but I feel like the packaging system should almost be vendor agnostic,
+[1722.70 --> 1727.10]  which is kind of where Docker really wins or containers in general really win.
+[1727.42 --> 1728.10]  Containers do, yeah.
+[1728.16 --> 1730.12]  They'll just run on any Linux kernel.
+[1730.36 --> 1731.44]  It doesn't really matter which.
+[1731.80 --> 1736.02]  Yeah, I think there is some things that are always going to be vendor specific.
+[1736.40 --> 1738.80]  Debian's always going to have apt and that's unique to them.
+[1738.80 --> 1740.98]  You know, Debian and Debian derivatives.
+[1741.50 --> 1747.82]  But there's some things that people really want to be vendor neutral in the Linux ecosystem.
+[1748.00 --> 1751.14]  And it seems software distribution at that level is one of them.
+[1751.60 --> 1755.34]  And I also can appreciate that a lot of projects want to host their own repositories.
+[1755.38 --> 1760.62]  And I think that's what's really been nice for Flatpaks is you could host your own Flatpak repository.
+[1761.14 --> 1763.64]  And, you know, I think our audience understands why people might prefer that.
+[1763.88 --> 1764.94]  You can't do that with snaps.
+[1765.40 --> 1766.62]  I mean, they have their place, don't they?
+[1766.62 --> 1770.26]  But then again, when I'm on my desktop, I'll run Arch.
+[1770.76 --> 1773.54]  Everything is just in one place.
+[1773.62 --> 1775.28]  There's no installing repos.
+[1775.38 --> 1776.74]  It's just all in the AUR.
+[1776.98 --> 1784.46]  And if we could somehow get the AUR for every Linux distro, then problem solved, right?
+[1784.68 --> 1786.94]  It sounds silly, but I agree so much.
+[1787.36 --> 1788.54]  It's so nice.
+[1788.68 --> 1791.02]  Just it's I manage everything with yay.
+[1791.36 --> 1792.88]  It's yay for anything.
+[1793.18 --> 1796.00]  And there's never any math of is this going to be isolated?
+[1796.00 --> 1796.86]  Is this a Flatpak?
+[1796.94 --> 1797.52]  Is this a Snap?
+[1797.60 --> 1798.54]  Is this an app image?
+[1798.82 --> 1800.24]  Is this an out of date version?
+[1800.36 --> 1801.86]  I never have any of those questions.
+[1802.26 --> 1803.56]  And you don't even have to Google it.
+[1803.68 --> 1807.00]  You just search in yay first and nine times out of 10, you'll find it.
+[1807.36 --> 1809.06]  It's so nice on the workstation side.
+[1809.14 --> 1810.78]  Now, here's the thing, and I'll just wrap it up with this.
+[1811.22 --> 1817.18]  Here's where I think snaps do play a role because I've seen this side of it too, is in the business world, it generally works.
+[1817.18 --> 1824.34]  If you have something that's of a high value, like a piece of software like Adobe might have or Blackmagic or whoever, you want to talk to another company.
+[1824.46 --> 1830.54]  You want to work with another company and you want to have a legal relationship and then you want to have like cross team relationships.
+[1830.54 --> 1841.92]  So the packaging people at Plex, for example, interface with the Snap people at Canonical and they actually have a business to business relationship, Plex and Canonical.
+[1842.46 --> 1848.16]  And there is a vendor relationship there where I think just for Plex, they package for everything.
+[1848.16 --> 1862.14]  But I think a lot of companies like that kind of traditional relationship and that's a role where snaps can really kind of be more appealing to the commercial software industry because they can have an agreement with Canonical.
+[1862.34 --> 1864.14]  They can distribute via Canonical store.
+[1864.76 --> 1869.66]  It works on most distributions and they are the ones that can publish.
+[1870.66 --> 1877.38]  I think that's really appealing to that type of business, but it just doesn't seem to really be appealing to community use cases as much.
+[1878.16 --> 1882.30]  Despite all that I just said about snaps, I still use Ubuntu everywhere.
+[1883.02 --> 1884.68]  Yeah, and you really learn the tricks.
+[1885.08 --> 1886.24]  You know, you learn the tricks.
+[1886.44 --> 1890.22]  I follow the directions on the Docker site for getting Docker set up really.
+[1890.30 --> 1891.52]  I don't even use it from the repos.
+[1891.68 --> 1894.66]  Yeah, get.docker.com and then pipe it to sudo bash, right?
+[1894.84 --> 1895.78]  You could do that.
+[1896.02 --> 1897.02]  You definitely could.
+[1897.14 --> 1897.84]  What could go wrong?
+[1897.94 --> 1905.62]  I thought maybe I should summarize like several emails we've gotten over the last couple of weeks since we talked about Powerline networking, which just super brief follow up.
+[1905.74 --> 1906.38]  Still working awesome.
+[1906.38 --> 1909.98]  I haven't even had to reset any of like the adapters or anything.
+[1910.20 --> 1911.64]  They're still working great.
+[1912.18 --> 1913.62]  It's like having Ethernet.
+[1913.70 --> 1914.46]  It's so wonderful.
+[1914.54 --> 1915.24]  It's just slightly slower.
+[1915.62 --> 1917.82]  We have had a few people write in that have told me.
+[1918.34 --> 1922.98]  Actually, we had a whole range of concerns like from my solar is going to generate too much interference.
+[1923.12 --> 1927.70]  But of course, they're separate systems to turning my RV into a radio broadcast system.
+[1928.04 --> 1931.90]  I don't think we've had a topic that has been quite so feedback generating.
+[1931.90 --> 1935.82]  Yeah, it's really and a wide range of successes and failures.
+[1935.96 --> 1938.06]  But there has been one consistent theme.
+[1938.28 --> 1941.98]  And that is you got to go to the next level if you really want this to work great.
+[1942.22 --> 1944.58]  And that is check out Ethernet over coax.
+[1944.76 --> 1947.34]  People have been writing that in for a couple of weeks straight now.
+[1947.34 --> 1955.84]  And the ActionTech MOCA network adapter for Ethernet over coax 2 pack has been linked a couple of times.
+[1955.84 --> 1961.14]  And the word from these emails is it's night and day difference way better.
+[1961.38 --> 1966.44]  If you if you've got coax pre run in your place, it's a way better route to go than power over Ethernet.
+[1967.26 --> 1968.94]  Apparently haven't tested it myself.
+[1969.08 --> 1973.98]  I do have a bit of coax, not in the areas where I would want to have servers.
+[1974.90 --> 1976.76]  But I do have a bit of coax in the RV.
+[1976.88 --> 1978.98]  So maybe at some point it could be useful.
+[1979.44 --> 1984.04]  I could see maybe using it for like, say, a Nvidia Shield hookup or something where the TV is already at.
+[1984.04 --> 1985.30]  And that's where a coax connection is.
+[1985.30 --> 1987.08]  I think that's a perfect use case.
+[1987.20 --> 1990.26]  Something I mean, a Shield's not going to be using crazy amounts of bandwidth.
+[1990.96 --> 1995.68]  But the other thing to consider as well is that coax is a lot cheaper than Ethernet cable.
+[1996.14 --> 2008.84]  And it can be purchased a lot cheaper than weatherproof Ethernet as well, which is also, you know, if you want to run it from the attic, say, down to your basement, probably the easiest route is going to be out the side of the building.
+[2009.20 --> 2011.14]  And doing that with Ethernet could get expensive.
+[2011.14 --> 2013.90]  So it's definitely an interesting thing.
+[2013.96 --> 2015.34]  And it's not something I considered before.
+[2015.52 --> 2017.84]  So I don't know, maybe next house.
+[2018.24 --> 2019.48]  I'll give it a whirl.
+[2019.84 --> 2022.24]  I'm going to keep it in my back pocket for a future project.
+[2022.34 --> 2024.12]  And it has a cool acronym too.
+[2024.54 --> 2024.84]  Mocha.
+[2025.28 --> 2026.02]  M-O-C-A.
+[2026.34 --> 2026.62]  Mocha.
+[2026.92 --> 2027.88]  Mo-C-A-C-E-N-O.
+[2027.88 --> 2028.18]  Mocha.
+[2028.18 --> 2029.24]  So I kind of like it already.
+[2029.46 --> 2030.08]  Sounds delicious.
+[2030.30 --> 2030.52]  Mocha.
+[2030.70 --> 2035.06]  If the reports from the email are true, it's like if they say it's a gigabit, it's a true gigabit.
+[2035.14 --> 2036.12]  It's actually that fast.
+[2036.62 --> 2037.06]  Mocha.
+[2037.06 --> 2037.18]  Mocha.
+[2037.18 --> 2037.46]  Mocha.
+[2037.46 --> 2037.54]  Mocha.
+[2037.54 --> 2037.82]  Mocha.
+[2037.94 --> 2038.00]  Mocha.
+[2038.00 --> 2038.12]  Mocha.
+[2038.12 --> 2038.26]  Mocha.
+[2038.26 --> 2039.14]  Mocha.
+[2039.14 --> 2040.22]  Mocha.
+[2040.22 --> 2041.30]  Mocha.
+[2041.30 --> 2042.08]  Mocha.
+[2042.08 --> 2042.38]  Mocha.
+[2042.38 --> 2042.46]  Mocha.
+[2042.46 --> 2042.64]  Mocha.
+[2042.64 --> 2043.32]  Mocha.
+[2043.32 --> 2044.48]  Mocha.
+[2044.48 --> 2047.00]  our site reliability engineers who support the show.
+[2047.32 --> 2048.50]  They keep us independent.
+[2048.74 --> 2051.28]  They get a limited ad feed available to them as a member,
+[2051.48 --> 2053.76]  and they get a little bit of extra content, a post-show.
+[2054.18 --> 2056.38]  So if you'd like to support the show and become a member,
+[2056.52 --> 2058.72]  go to selfhosted.show slash SRE.
+[2059.08 --> 2062.00]  Yes, big thank you to our site reliability engineers.
+[2062.30 --> 2066.18]  You can go to selfhosted.show slash contact to get in touch with us,
+[2066.26 --> 2068.56]  and you can find me on Twitter at Ironic Badger.
+[2068.78 --> 2069.32]  I'm there too.
+[2069.44 --> 2074.04]  I'm at Chris LAS, and the show is at selfhostedshow.
+[2074.04 --> 2076.52]  Don't forget at Jupitersignal for the network.
+[2076.90 --> 2077.54]  Thanks for listening.
+[2077.78 --> 2080.00]  That was selfhosted.show slash 36.

37： Security Growing Pains _summary.txt

@@ -0,0 +1,60 @@
+• Home Assistant Security Bulletin: discussion of its handling and lack of clear information from the project
+• Update on the show's first anniversary and future plans
+• Discussion of milestones for podcast success (episode 300) and celebration
+• Brief review of the show's growth and reception over its first year
+• Upcoming schedule and potential changes to release frequency
+• High standards for platform security and communication
+• Importance of clear communication in resolving security issues
+• Reliability of vendor-supported OS vs project-controlled stack
+• Challenges of building a comprehensive home automation platform
+• Need for delegation of complex tasks to specialized vendors
+• Home Assistant update process and potential issues with custom integrations
+• The speaker experiences issues with the update process in Home Assistant
+• Problems are resolved after a reboot and running the update again
+• Issues with config checker and custom integration explained
+• Discussion of using Home Assistant on an RV's Internet connection
+• Speaker shares experience with using Home Assistant's snapshot feature to back up data
+• Discussion of using Google Drive backup plugin for automated snapshots
+• The speaker discusses their use of Linode as a server provider, mentioning its ease of use and customer support.
+• They explain that Linode offers one-click deployments for applications like Minecraft and CSGO servers, making it simple to set up private gaming spaces.
+• The speaker also talks about Linode's human-powered customer support and its history as an independently owned company founded in 2003.
+• They share their experience using Linode's services for their own infrastructure and personal projects, including experimenting with different WordPress stacks.
+• The conversation shifts to the topic of building versus buying solutions, with the speaker sharing a personal anecdote about regretting building a solution that could have been purchased more affordably.
+• Finally, they showcase a small Bluetooth temperature sensor from Xiaomi, discussing its features and potential uses in home automation projects.
+• Temperature sensors and display
+• ESP32 devices for temperature monitoring
+• Web configurator tool for flashing firmware
+• Automating thermostats using Home Assistant
+• Generic thermostat component in Home Assistant
+• Smart thermostat integration issues
+• Difficulty with thermostat settings and heat distribution in specific room
+• Desire to use a sensor to monitor temperature and adjust heating accordingly
+• Interest in automation that turns off heating when a certain threshold is reached
+• Consideration of energy efficiency and potential for future development
+• Discussion of solar power options, including Tesla Powerwall and Tractor Supply
+• Research process for installing solar panels, including reading reviews and seeking advice from online communities
+• Listener Phil asks about protecting backups from ransomware and accidental mass deletion
+• Host discusses using ZFS for backups, including snapshot support and data set encryption
+• Host explains his backup strategy, which includes hourly, daily, weekly, monthly, and annual snapshots
+• Host mentions potential issue of ransomware requiring execution to affect the system
+• Discussion turns to backup solution for a NAS (Network-Attached Storage) device, and the challenge of backing up large amounts of data (15 terabytes)
+• Host shares personal experience with losing access to media due to DVDs/Blu-rays becoming obsolete and online availability issues
+• Plans to sync a large amount of data locally and then offsite via personal setup
+• Discussion of backup solutions, including using Google Drive and duplicati for encryption and multi-cloud storage
+• Concerns about relying on Google services due to changes in terms and API access revocation
+• Alternative solutions like cloudfree.shop devices that are pre-configured for local network use without cloud connections
+• NFC automation tricks and using NFC tags for tasks like D&D and turning on lights
+• Android users' workaround for using NFC tags on iOS
+• Using HomeKit to integrate with Home Assistant for automation
+• Two workarounds for avoiding notification confirmation when using NFC tags: Billy's method and Quinton Ronan's web hook solution
+• Discussion of preparing a setup to be accessible by others in case of absence or incapacitation
+• The speaker is considering transitioning from LastPass to another password manager like Bitwarden
+• They need a solution that allows for different logins with separate credentials, especially for sharing with their wife and others
+• The speaker questions whether their family would be able to maintain the current setup if they were no longer around
+• They discuss the importance of documentation and making systems accessible to others
+• The conversation touches on the concept of "craftsmanship" in setting up technical solutions and leaving a legacy for others
+• Discussion of a hypothetical show idea similar to "Wife Swap" but with systems and infrastructure
+• Overview of the host's current server setup, including its age and previous operating systems
+• Mention of Cloud Guru as the sponsor and invitation to engage on social media
+• Host's personal Twitter account and contact information for the show
+• Discussion of self-hosting and infrastructure choices, including Proxmox and Arch Linux

37： Security Growing Pains _transcript.txt

@@ -0,0 +1,782 @@
+[0.00 --> 3.32]  Coming up on today's show, we discuss the Home Assistant Security Bulletin.
+[3.76 --> 9.58]  I've got some pretty cool Bluetooth low-energy OLED temperature sensors for you from Xiaomi,
+[10.00 --> 12.62]  and we get philosophical in the feedback section. I'm Alex.
+[12.98 --> 15.74]  I'm Chris, and this is Self-Hosted 37.
+[16.92 --> 20.74]  You know, it was only the last few weeks I realized that we just sort of blew right past
+[20.74 --> 22.38]  our one-year anniversary in September.
+[22.92 --> 23.74]  We're one.
+[23.98 --> 28.74]  Yeah, and I think it was just because we were doing the whole going independent thing again.
+[28.74 --> 30.66]  And so we just had a lot on our plate.
+[30.96 --> 32.66]  What's your opinion on first birthdays?
+[32.96 --> 36.26]  I think the show's been really well-received, and it seems like it's still growing,
+[36.42 --> 38.04]  but it's found its audience.
+[38.52 --> 41.80]  And I think it's a good first year, especially because we're not weekly.
+[42.10 --> 45.36]  And so for some podcasts, that can be rough, but it doesn't really seem to have held us back.
+[45.72 --> 49.26]  I wasn't talking about that. I was talking about kids, first birthday.
+[49.50 --> 52.76]  Do you make a whole big deal about it? Because obviously, they're not going to remember it.
+[53.00 --> 54.20]  That's true. That's true.
+[54.20 --> 58.84]  Yeah, I don't know. I feel like for podcasts, it's a good sign that it's a stable podcast,
+[59.20 --> 66.20]  but there's like kind of this, the real, I think, real landmark for a podcast is five years.
+[66.32 --> 67.94]  That feels like the one you celebrate to me.
+[68.40 --> 71.76]  Yeah, you've done a few that have reached episode 300. I think for me, that's a big number.
+[72.14 --> 77.04]  Yeah, that's also a pretty big one. Yeah, so congratulations, though, on the anniversary.
+[77.16 --> 80.92]  We thought this seems like the perfect episode to follow up on a lot of things because of that.
+[80.92 --> 87.34]  You know, it's going to take us 11 and a half years, twice a month, to reach episode 300.
+[89.02 --> 93.02]  Maybe we'll have to step it up at some point. Maybe we'll go daily for a last little bit.
+[93.74 --> 98.94]  We have flirted with the idea of weekly, but you know, with going indie, you've had so much on your plate again.
+[99.70 --> 102.50]  It's not really been feasible for both of our schedules yet.
+[102.86 --> 107.64]  Yeah, life is busy, but you never know. Things change in the future, but right now we don't have many plans to change it.
+[107.64 --> 113.00]  We have discussed it from time to time. The future is, well, it hasn't happened yet.
+[113.62 --> 120.32]  But this episode has happened. It's happening right now, and it's brought to you by a Cloud Guru, the leader in learning for Cloud Linux and other modern tech skills.
+[120.70 --> 126.82]  Hundreds of courses, thousands of hands-on labs. Get certified, get hired, get learning at cloudguru.com.
+[126.82 --> 134.98]  I got a rather alarming set of emails and Reddit posts from the Home Assistant project this week about a security bulletin.
+[135.72 --> 143.62]  And I wanted to get your take on how they're handling it, because to me it seems like controlled, well, not even controlled. It just seems like chaos over there.
+[143.98 --> 149.06]  Yeah, they're really trying to get the word out. That's one of the reasons, I think by now, when this episode comes out, people will know about it.
+[149.06 --> 154.56]  But just because this seems to be really important, I even got a notification again this morning via their Discord community.
+[155.08 --> 158.18]  So there was a security bulletin put out by the Home Assistant project.
+[158.18 --> 171.20]  We will have the blog post linked in our show notes, but there's not much to it, other than it just strongly encourages you to update as fast as possible and spread the word as far as possible.
+[171.50 --> 180.00]  There is a specific callout in the blog post to an issue with custom components, which are not reviewed by the core Home Assistant team.
+[180.00 --> 184.04]  But otherwise, there's really zero information in the bulletin as we record.
+[184.16 --> 186.16]  This is several days after the bulletin as well.
+[186.70 --> 192.84]  We were told there would be an update with more information, but it so far hasn't shown up anywhere.
+[193.78 --> 204.98]  However, we do have several questions that we'd like to have answered, like which integrations were leaking stuff, under which circumstances were those integrations leaking stuff, and does the update that's been released fully address those issues?
+[204.98 --> 210.32]  Or, as some are speculating right now, is it just merely mitigating them?
+[210.80 --> 215.30]  Will there still be some risk after updating if we use whatever integration this supposedly was?
+[215.34 --> 220.42]  So there's definitely questions that haven't been properly answered by the Home Assistant project right now.
+[220.96 --> 223.18]  I wonder if that's because they just don't have the answers yet.
+[223.56 --> 224.64]  You speculate, really.
+[225.30 --> 229.70]  And at this point, I want to just let the audience know we are recording this a couple of weeks ahead of time.
+[229.92 --> 232.56]  I've got some personal stuff coming up, so it's unavoidable.
+[232.56 --> 240.04]  But, you know, from my perspective, I want to see like CVE-style clarity here.
+[240.20 --> 241.38]  I want to know what the problem is.
+[241.46 --> 244.50]  I want to know what they've done to fix it or that they haven't fixed it.
+[244.66 --> 253.62]  I actually don't necessarily mind if they haven't because at least I know what the problem is, so I could maybe go and try and contribute to creating a fix, perhaps.
+[254.06 --> 255.02]  Yeah, I'm sure they're very busy.
+[255.44 --> 260.64]  But there are basic questions like if I didn't use any custom components, do I have any cause for concern?
+[260.64 --> 269.34]  Now, if you go by the code, because it's an open source project, it looks like maybe they caught that some nasty things were happening via the HTTP API.
+[269.34 --> 274.52]  Seems like maybe they've added some basic filters to the code for some common web-based attacks.
+[275.12 --> 276.66]  But really, the context matters here.
+[276.74 --> 278.32]  So that's only something the project can provide.
+[278.84 --> 290.94]  Yeah, I see some stuff in the code for one of the commits that's referenced in the forum post about the security bulletin about file injection attacks at certain web URLs as well as SQL injection protections and stuff like that.
+[290.94 --> 292.92]  So who knows what's going on?
+[293.48 --> 302.42]  This is where it's a really tricky balance, especially for an overburdened project and especially a new one that hasn't really had to deal with a security issue quite like this yet.
+[302.92 --> 309.06]  There is a real high standard for a platform, a really high standard of clear communication.
+[309.06 --> 314.88]  And even if that communication is a status update that they don't have the full report yet, it needs to be communicated.
+[315.38 --> 316.84]  It's a hard lesson to learn.
+[317.00 --> 318.76]  You also have to create process.
+[319.12 --> 321.92]  It's a human problem as well as a process problem.
+[322.44 --> 326.56]  But clear communication is critical for any kind of popular platform.
+[327.42 --> 330.94]  And I know that they're very busy, but that's always going to be the case.
+[330.94 --> 336.96]  And as more and more people integrate their homes and businesses around this, it's pretty important that we know what's going on.
+[337.60 --> 342.80]  That's where the communication is probably going to be a bit of a learning opportunity in the future.
+[342.98 --> 350.72]  But it also reminds me that they're still, you know, as far as a project goes of this scope, relatively young.
+[351.34 --> 354.12]  And they still have things that they're going to have to figure out.
+[354.12 --> 364.80]  And it's not why it's a knock when I say this, but it sort of speaks to why I'm not a huge fan of their entire integrated approach with the OS and Home Assistant and the supervisor.
+[365.44 --> 370.50]  I'm not a huge fan of this project building an OS.
+[372.04 --> 381.38]  With these types of security things, with the underlying platform, that's just an area I'd like to outsource that work to the folks at Canonical, Red Hat, or Debian.
+[381.38 --> 385.12]  I just don't really prefer having the project control the entire stack.
+[385.46 --> 389.12]  I understand why they do it, and it's an entirely separate conversation.
+[389.30 --> 397.68]  But it's one of my arguments why I hope they keep making it possible for folks like me to deploy the entire Home Assistant experience on the OS of my choice.
+[398.02 --> 406.86]  Because just for my personal comfort and just the way I view the world, I like to know that a vendor like Red Hat or Canonical is behind the server OS that I'm using.
+[406.86 --> 416.36]  I mean, I see on a daily basis at work, a lot of the stuff that goes on behind the curtain of maintaining a kernel, of maintaining a Kubernetes distribution and that kind of stuff.
+[416.48 --> 418.68]  And it's an astronomical amount of work.
+[419.00 --> 420.14]  And I've got to agree with you.
+[420.14 --> 440.46]  I think if the project were to take the limited resources that they have and kind of share them out in their area, well, not share them out, but like delegate the responsibilities of the more complex tasks like building an OS to vendors whose day job it is and who have 25 plus years.
+[440.58 --> 443.70]  I'm looking at Debian experience in doing this kind of stuff.
+[443.70 --> 449.16]  And then they can focus on what they're good at, which is building a brilliant home automation platform.
+[449.58 --> 450.84]  But to their credit, they caught this.
+[450.98 --> 456.66]  And the other thing I think they've done right in this process is they have communicated the need to upgrade.
+[456.88 --> 464.52]  They haven't been particularly great about communicating why other than security, but they have been very good at getting the word out.
+[465.20 --> 469.34]  And there is a pretty safe process to do that upgrade.
+[469.34 --> 473.86]  So I decided to do it over the weekend so that way I could report back here on the show.
+[474.48 --> 480.44]  And my setup is it's Ubuntu 2004 running on a Raspberry Pi 4.
+[480.78 --> 487.56]  I can't even remember how I set it up now, but I have the full supervised home assistant setup so I can install the add-ons and take snapshots.
+[487.98 --> 491.88]  And I really love that setup, even though it's not technically a supported setup anymore.
+[492.18 --> 495.72]  But I went into my home assistant supervisor and I clicked update.
+[495.72 --> 498.44]  Well, first I took a snapshot, actually, did the snapshot.
+[498.64 --> 512.42]  And whenever I'm doing something that may introduce a breaking change, because it wasn't clear here, if there was an issue with custom integrations, I thought it's possible they just disabled custom integrations until they have this thing fixed.
+[512.60 --> 514.80]  And so I thought, this could be a breaking update.
+[514.88 --> 515.32]  I don't know.
+[515.54 --> 517.28]  There's not really been any information about that.
+[517.28 --> 522.50]  So I took a snapshot and then I downloaded that snapshot to my local hard drive, just in case.
+[522.96 --> 526.84]  Then I head over to the update button, click the update, nothing happens.
+[527.38 --> 529.66]  Click it again, nothing happens.
+[529.96 --> 533.16]  And it's not exceptionally good at communicating status.
+[533.46 --> 534.92]  So I SSH into the server.
+[535.08 --> 537.16]  Again, I love that it's a server I can just get access to.
+[537.20 --> 538.78]  And I have things like Bashtop installed.
+[539.12 --> 540.70]  And I run Bashtop and Htop.
+[540.76 --> 541.42]  And I get an idea.
+[541.54 --> 543.80]  It's like, is there anything happening in the background?
+[543.80 --> 546.32]  And I pretty quickly determine nothing's happening.
+[547.12 --> 550.12]  So I turn to an integration that I have.
+[550.14 --> 555.26]  And this is one of the reasons I wanted the full Home Assistant experience and not just Home Assistant core.
+[555.80 --> 571.32]  Because there's integrations like the upgrade configuration checker that will download the latest version of Home Assistant, do a fake contained install, and then check it against your config YAML and tell you if there's anything that's going to break in the upgrade.
+[571.32 --> 572.86]  So I thought, I'll run that.
+[573.30 --> 574.26]  Only it broke.
+[574.46 --> 583.28]  And I had to go digging for the logs on the file system to discover that there was some issue with, quote, custom integration, quote, but they didn't say which integration it was.
+[583.64 --> 586.26]  So I didn't really know what was going to happen.
+[586.38 --> 593.70]  But I decided for the good of the show, I'd pull the trigger, and I did the update, and it still did nothing.
+[594.38 --> 595.20]  Okay, what's going on?
+[595.36 --> 597.30]  So the configuration check failed.
+[597.60 --> 599.14]  The update has failed.
+[599.14 --> 601.26]  There must be something wrong.
+[601.54 --> 605.78]  So I reboot the whole machine, figure, let's just get that out of the way.
+[606.28 --> 607.48]  Home Assistant loads back up.
+[607.54 --> 608.62]  I verify functionality.
+[608.92 --> 609.98]  I go into Supervisor.
+[610.12 --> 613.36]  I hit the update button, and I start to get the circle of progress.
+[613.84 --> 616.44]  It starts working all of a sudden, even though I hadn't changed anything.
+[616.50 --> 617.20]  I just did a reboot.
+[617.30 --> 621.10]  And the machine had only been rebooted about 24 hours ago, too, which I thought was kind of funny about it.
+[621.62 --> 622.62]  It pulls it down.
+[622.96 --> 623.92]  It does the update.
+[624.02 --> 626.28]  And so far, I don't see any issue.
+[626.38 --> 627.60]  I have now the latest version.
+[627.60 --> 629.16]  Everything seems to be going just smooth.
+[629.76 --> 632.18]  And I'm not quite sure why I had the problems with it updating.
+[632.28 --> 634.46]  I'm not quite sure why my config check had problems.
+[635.26 --> 637.30]  But everything's tested and working.
+[637.84 --> 643.00]  The only time I've had issues with the config checker is when there's been an error in my config, actually.
+[643.44 --> 643.72]  Yeah.
+[643.72 --> 647.70]  I created an include that was pointing at a missing file or something.
+[647.70 --> 652.72]  And rather than telling me that, the config checker just sat there and span and span and span.
+[653.04 --> 658.92]  And it takes a while, too, on the Raspberry Pi because you're downloading it, which I don't have the fastest connection in the RV.
+[659.46 --> 660.46]  So I wait for that.
+[660.46 --> 660.96]  Oh, yeah.
+[661.04 --> 662.20]  It can take a beat.
+[662.28 --> 662.86]  That is true.
+[663.04 --> 666.24]  At least I would say set aside two or three minutes.
+[666.52 --> 666.64]  Yeah.
+[666.70 --> 667.14]  Oh, yeah.
+[667.46 --> 668.02]  Or more.
+[668.30 --> 669.00]  Maybe 15.
+[669.40 --> 670.24]  But you see the error.
+[670.32 --> 671.70]  I put it there in the show notes for you.
+[671.84 --> 675.26]  It just says invalid config for script integration.
+[675.26 --> 677.84]  And then it's just blank.
+[678.38 --> 679.58]  And it says not found.
+[679.96 --> 681.26]  Two quotes that are just empty.
+[681.44 --> 681.94]  Very helpful.
+[682.12 --> 682.28]  Yeah.
+[682.76 --> 684.02]  So I'm going to pull it up.
+[684.28 --> 686.78]  It says it's on line 21, so I know where to go look.
+[687.04 --> 690.96]  But I decided to run the update since I had a snapshot and everything went through.
+[691.16 --> 694.14]  I have the latest version and it's working perfectly fine.
+[694.48 --> 702.50]  But I do kind of wonder what that custom integration airs about and if it's related to some of the fixes they just did since their fixes are related to custom integration.
+[702.50 --> 705.58]  So I'll be diving deeper into that into the future.
+[705.94 --> 708.44]  But have you decided to pull the trigger on the upgrade for you?
+[708.84 --> 715.40]  Well, I mean, I was I was quite busy the other night and I just saw the notification come through and was like, oh, so I just hit upgrade.
+[715.46 --> 716.38]  I don't have time to check.
+[716.82 --> 719.64]  I subscribed through the Nabucasa app.
+[719.76 --> 726.00]  So technically, my install is Internet facing, even if you have to guess a very long obfuscated URL.
+[726.32 --> 727.48]  When did you start doing that?
+[727.50 --> 728.24]  I didn't know that.
+[728.36 --> 730.10]  Well, I started supporting the project.
+[730.10 --> 737.10]  That was the reason I actually started paying for it was was really to support development, not necessarily because I wanted the remote features.
+[737.18 --> 742.02]  But it actually turned out to be pretty handy because, you know, with with COVID, I haven't really left the house that much.
+[742.02 --> 745.94]  So I haven't had the need to SSH into my house remotely very much.
+[746.64 --> 752.14]  And I got to where I was going and found out I couldn't connect to my house to pass the time or whatever.
+[752.14 --> 768.40]  And so I opened up Home Assistant in the phone app, looked at the URL, typed that into on my on my laptop and then used the VS Code plugin with the built in shell to create the SSH keys I needed.
+[768.52 --> 769.12]  And I was good to go.
+[769.56 --> 772.30]  That's a great little example of how all that stuff can really come together.
+[773.06 --> 773.24]  Yeah.
+[773.30 --> 774.32]  So I got the update loaded.
+[774.32 --> 782.86]  I haven't actually updated the version on my Home Assistant Blue hardware at the studio, but I'm, you know, more a couple of weeks into using that and I'm still loving that as well.
+[783.14 --> 784.36]  I'm grateful they're doing the update.
+[784.82 --> 785.80]  What do you use for snapshots?
+[786.04 --> 788.30]  I use the built in supervisor tool that does the snapshots.
+[788.58 --> 791.06]  Have you come across the Google Drive backup plugin?
+[791.46 --> 792.50]  I don't think I have.
+[792.72 --> 792.96]  No.
+[793.10 --> 794.56]  It's not in the main store.
+[794.56 --> 798.26]  I'm pretty sure it's an external thing, but it is awesome.
+[798.58 --> 810.94]  So I think in the self-hosted live hack that we did a few months ago, I showed it off there where I basically took a completely fresh install of Home Assistant, applied the snapshot, which was taken by this Google Drive plugin.
+[811.32 --> 814.50]  So it automatically does stuff like snapshot rotation.
+[814.50 --> 818.74]  So you can have a daily, a weekly, a monthly, yearly snapshot, that kind of thing.
+[818.88 --> 819.28]  Really?
+[819.50 --> 821.88]  I can have up to seven days and four months or whatever.
+[822.06 --> 822.86]  You got to link this.
+[822.98 --> 823.76]  You got to link this up.
+[823.76 --> 824.58]  I got to check this out.
+[824.76 --> 825.00]  All right.
+[825.04 --> 827.48]  Yeah, it's pretty slick and it obviously integrates with Google Drive.
+[827.66 --> 832.06]  So, you know, each snapshot's 200 megs or so in my setup.
+[832.50 --> 834.32]  So it doesn't really take much storage.
+[835.88 --> 837.74]  Linode.com slash SSH.
+[837.82 --> 841.56]  Go there to get a $100 60-day credit and support the self-hosted podcast.
+[842.26 --> 843.84]  Linode is our server provider.
+[843.84 --> 848.78]  Whenever we're building something for the show or my personal infrastructure and now JB 3.0's infrastructure.
+[849.46 --> 851.42]  Yeah, it's all up on Linode.
+[851.42 --> 854.30]  And gamers, Linode is your DIY of choice.
+[854.30 --> 863.04]  They make it really easy and there are plenty of simple one-click deployments for things like Minecraft and CSGO servers.
+[863.16 --> 868.32]  That's a really simple way and a really nice and fast way to get a nice private gaming space.
+[868.32 --> 876.00]  And they will have you fill out like just some of the basics you need to get some of the fundamental server options set and they'll deploy it pre-configured for you.
+[876.24 --> 877.34]  So make sure you check that out.
+[877.42 --> 882.00]  Every plan comes with Linode's amazing human-powered customer support.
+[882.00 --> 888.20]  We've had story after story from our audience of great experience with Linode's customer support.
+[888.32 --> 893.48]  You can email, you can hit them up on social media, you can pick up a phone and talk to an actual human.
+[894.10 --> 895.00]  How about that?
+[895.30 --> 896.08]  I mean, Linode gets it.
+[896.10 --> 897.56]  They've been around for a long time.
+[897.90 --> 901.28]  They started in 2003 as one of the first companies in cloud computing.
+[901.62 --> 904.98]  Three years before AWS and other enterprise providers.
+[905.26 --> 909.06]  And they're independently owned and they're founded on a love for Linux and open source technologies.
+[909.06 --> 911.80]  And they really support the community that surrounds them.
+[911.90 --> 919.46]  Like this show, like the Kubuntu project, like LinuxFest Northwest, which you know is very special to us.
+[919.92 --> 920.94]  Linode's a supporter of them.
+[921.30 --> 926.58]  But you get a $100 credit when you go to linode.com slash SSH.
+[926.70 --> 929.84]  So you can play around with their really powerful systems if you want.
+[930.20 --> 932.46]  Try out building some tools around object storage.
+[932.68 --> 935.48]  It's a great opportunity to experiment with different stacks.
+[935.48 --> 940.68]  That's one of the things I've done on Linode is I tried several different WordPress stacks to see which one I like.
+[940.78 --> 945.14]  You know, with Nginx or I even tried a web browser where everything runs out of RAM.
+[945.24 --> 951.12]  And they have all of this stuff that is just ready to go as configuration scripts that you can just kick off and get going.
+[951.68 --> 952.76]  It's really simple.
+[953.42 --> 955.32]  And they also offer a lot of powerful tools.
+[955.42 --> 956.78]  They don't hide that stuff from you either.
+[957.12 --> 957.68]  So try it out.
+[957.92 --> 959.92]  Linode.com slash SSH.
+[959.92 --> 968.18]  How often do you ask yourself the question, when does it make sense to build versus buy a solution?
+[968.54 --> 972.06]  I mean, a lot of times that's one of the first or second questions I ask myself.
+[972.16 --> 973.70]  I very frequently do that math.
+[973.90 --> 974.88]  You must as well.
+[975.26 --> 978.82]  Yeah, what's particularly annoying is that I actually built a solution last year.
+[979.12 --> 986.56]  And there's a solution I can now buy that is so much better for half the price that I'm kind of sat here going,
+[986.80 --> 988.64]  I wish I hadn't built one now.
+[988.64 --> 990.46]  Yeah, it's tricky, right?
+[990.50 --> 995.26]  Because things like temperature sensors and humidity sensors, you might end up wanting a lot of them.
+[995.52 --> 995.96]  You do, yeah.
+[996.06 --> 999.30]  So, I mean, probably every single room is a bit of overkill.
+[999.48 --> 1006.86]  But certainly at the other end of the spectrum, just a single thermostat as a single point of measurement in a house is,
+[1007.30 --> 1009.38]  I've always, it's always struck me as weird.
+[1009.62 --> 1011.16]  It's absolutely nutty.
+[1011.24 --> 1014.20]  It's even nutty in a tiny space like a tiny home or an RV.
+[1014.20 --> 1018.74]  Yeah, because one room, if you shut a door, can get to, you know, several degrees higher than the hallway.
+[1019.22 --> 1019.34]  Yeah.
+[1019.76 --> 1022.56]  So, I'm holding in my hand up to the camera so you can see it.
+[1022.90 --> 1024.84]  This is the little temperature sensor I've bought.
+[1025.02 --> 1026.14]  It's from Xiaomi.
+[1026.46 --> 1029.88]  So, it's a Bluetooth low energy temperature sensor with an OLED screen.
+[1030.56 --> 1032.08]  There'll be a picture of it in the show notes.
+[1032.08 --> 1037.12]  It's about the size of three or four keys on my keyboard square.
+[1037.26 --> 1038.32]  So, it's pretty small.
+[1038.46 --> 1039.96]  Fits in the palm of my hand very comfortably.
+[1040.90 --> 1047.30]  And they supply these things with a small little piece of adhesive tape that you can use to just stick it on the wall anywhere.
+[1047.86 --> 1049.06]  They're fully battery powered.
+[1049.06 --> 1054.24]  They connect to an ESP32, which you flash with ESP Home.
+[1054.76 --> 1061.70]  You give it the Bluetooth MAC address of this device and then ESP Home will connect to these sensors.
+[1062.26 --> 1063.26]  There is a catch.
+[1063.80 --> 1066.38]  You need to flash a custom firmware on the sensors as well.
+[1067.08 --> 1072.82]  So, expect to set aside an evening to do this if you're flashing, you know, half a dozen sensors or so.
+[1073.20 --> 1076.92]  But the best part is that it's $9 for a four pack of these sensors.
+[1077.42 --> 1077.88]  No.
+[1078.88 --> 1080.50]  With the screen on there?
+[1080.54 --> 1081.82]  I mean, that's what I love about them.
+[1082.06 --> 1082.40]  I know.
+[1082.86 --> 1083.70]  It's crazy, isn't it?
+[1083.76 --> 1087.68]  I have very expensive temperature sensors that'll do all kinds of fancy things.
+[1088.12 --> 1091.58]  But, you know what they don't do is they don't actually just display the temperature on them.
+[1091.58 --> 1096.58]  And, in a way, that's a killer feature because you get the context right there for the room you're in.
+[1096.68 --> 1098.12]  And it's also being fed to Home Assistant.
+[1098.44 --> 1104.86]  The temperature and the humidity on the screen, which in the southeast of the U.S., humidity is the bane of my life.
+[1104.86 --> 1107.02]  So, yeah.
+[1107.12 --> 1109.16]  So, you want to keep an eye on that damn thing.
+[1109.38 --> 1109.50]  Yeah.
+[1109.50 --> 1113.70]  How long would you say for four of them to get that flashing process done?
+[1113.70 --> 1120.44]  Well, there's actually a really slick sort of web configurator thing built into the GitHub repo that's linked in the show notes.
+[1120.76 --> 1122.24]  So, what you do is you fire up your phone.
+[1122.36 --> 1124.32]  You connect your phone's Bluetooth to this thing.
+[1125.06 --> 1126.72]  Flash the firmware through a web browser.
+[1126.72 --> 1129.90]  And then listen for the MAC address in the logs that way.
+[1129.98 --> 1132.36]  And then paste that into the ESP Home configuration.
+[1132.92 --> 1134.86]  And flash that to your ESP32.
+[1135.18 --> 1136.54]  It sounds like a lot of steps.
+[1136.94 --> 1140.28]  But it really isn't that bad if you're familiar with ESP Home.
+[1140.68 --> 1142.16]  Doesn't sound bad at all, actually.
+[1142.42 --> 1143.34]  Sounds quite doable.
+[1143.62 --> 1144.14]  Yeah, very slick.
+[1144.22 --> 1145.18]  I've been very impressed with it.
+[1145.42 --> 1149.30]  I think I came across this first on the Intimate.tech YouTube channel.
+[1149.38 --> 1150.78]  We had him on a few episodes ago.
+[1151.40 --> 1152.58]  The Quinn LED guy.
+[1153.08 --> 1154.36]  They just seem to work really well.
+[1154.36 --> 1160.22]  I had a couple of Bluetooth dropouts with the ESP32s being on a different end of the house.
+[1160.34 --> 1165.78]  So, I've ended up buying four ESP32s, which is the most expensive part of the setup.
+[1166.52 --> 1168.98]  One on each floor, at each end of each floor.
+[1169.54 --> 1172.52]  And they're basically stacked on top of each other, each end of the house.
+[1173.28 --> 1179.66]  So, I mean, even at $11 each on Amazon for an ESP32, we're not talking crazy amounts of money.
+[1179.86 --> 1184.12]  And you can definitely order them a lot cheaper than that on AliExpress if you're willing to wait for the slow boat.
+[1184.36 --> 1187.62]  So, now that you're getting the temperature data, what are you going to do with it?
+[1187.62 --> 1188.74]  Are you going to do any automations?
+[1188.92 --> 1191.40]  Because that's, I mean, that's really where it gets next level.
+[1191.90 --> 1192.60]  Yeah, I want to.
+[1192.72 --> 1194.26]  I haven't quite figured it out yet.
+[1194.38 --> 1196.94]  So, we're going to talk more about this in the post-show, I think.
+[1197.02 --> 1201.52]  We've got something in there about thermostats and the Venn style unit that I use.
+[1201.52 --> 1206.84]  But what I want to do is take the average, and this is something Dr. Z does a lot of.
+[1207.12 --> 1213.44]  He takes the average of several sensors and then uses that as his thermostat input number.
+[1213.78 --> 1219.36]  What I would like to see is I take the average across the entire top floor of my house, for example,
+[1219.36 --> 1222.36]  and then use that as the input to the thermostat.
+[1222.36 --> 1228.54]  I haven't figured out how to use a custom input with a thermostat that has an integration.
+[1229.02 --> 1233.12]  You can do that with the generic thermostat module of Home Assistant,
+[1233.36 --> 1238.80]  but I haven't quite joined all the dots up to make it work with a pre-configured one.
+[1239.20 --> 1240.50]  Justin wrote into the show.
+[1240.50 --> 1246.94]  So, he said he was actually writing in because on Coder Radio, which, by the way, not this podcast.
+[1247.44 --> 1248.02]  Where's my robe?
+[1248.24 --> 1249.46]  Yeah, I'm working on it.
+[1249.82 --> 1251.64]  I am wearing the minimum viable robe at the moment.
+[1251.88 --> 1256.62]  I was talking to Mike about his problems with he moved into a new place and it comes with a smart thermostat,
+[1257.16 --> 1259.32]  and it's been freezing him out at night.
+[1259.62 --> 1261.84]  And mine has my system every now and then.
+[1262.76 --> 1266.42]  Something happens and the automation triggers don't fire and I cook out.
+[1266.42 --> 1267.34]  I get too hot.
+[1267.50 --> 1268.74]  A heater doesn't get turned off.
+[1268.74 --> 1274.76]  And I generally, this fix has always just been, I reboot my Home Assistant host,
+[1274.94 --> 1277.16]  and then it doesn't happen for another couple of weeks.
+[1277.32 --> 1281.06]  But Justin wrote into the show and he said, you'd mentioned that failed automation.
+[1281.38 --> 1284.24]  Home Assistant, like you were just talking about, Alex, he says,
+[1284.68 --> 1287.60]  has a generic thermostat component and it is fantastic.
+[1287.80 --> 1289.86]  I use it in several rooms of our house.
+[1290.16 --> 1295.32]  You provided a temperature sensor and a switch and the component handles all of the rest.
+[1295.32 --> 1302.34]  It looks like there's some affordance for it understanding if you want something in a target temperature,
+[1302.34 --> 1307.28]  that it might need to kick in a little bit at a different time in order to actually get that temperature just right.
+[1307.36 --> 1313.78]  Like it seems clever and like a way better idea than me completely building this automation from scratch like I have been.
+[1313.78 --> 1317.16]  So when you do go down that route, I agree with listener Justin.
+[1317.40 --> 1318.66]  Check out the generic thermostat.
+[1319.20 --> 1320.98]  Yeah, I need to connect those dots for sure.
+[1321.10 --> 1327.12]  I mean, in my specific situation, the room above my garage happens to be where we spend most of our time.
+[1327.58 --> 1331.60]  And if I close the door to the hallway on this room and the heat is running,
+[1332.20 --> 1336.32]  it can easily get four or five Celsius higher in this room than the hallway.
+[1336.32 --> 1339.82]  When the forced air is blowing, it gets very dry, the air,
+[1339.94 --> 1342.98]  and the static electricity becomes a bit of a problem and stuff like that.
+[1343.10 --> 1348.98]  So what I really want is just a way to use that sensor that I'm looking at right now in this room
+[1348.98 --> 1351.66]  as the dedicated input to the thermostat.
+[1351.74 --> 1353.82]  If I can use an average, then, well, even better.
+[1353.94 --> 1356.78]  But what I absolutely want is an automation that fires
+[1356.78 --> 1362.40]  when that particular sensor gets above a certain threshold that it just doesn't turn off the heating
+[1362.40 --> 1363.56]  because that's not what I want.
+[1363.56 --> 1368.56]  I just want it to stop heating me for a bit right now and then evaluate things in 10 minutes
+[1368.56 --> 1372.58]  and figure out whether it needs to still keep blasting us with the heat or not.
+[1373.04 --> 1380.82]  And to add an extra layer of complication, if it could also be somehow energy efficient aware,
+[1381.16 --> 1386.16]  so if you were running off grid or maybe in your case you have like a Tesla Powerwall
+[1386.16 --> 1388.28]  and the grid was down and you were running off battery,
+[1388.54 --> 1393.00]  if the system could adjust to use less power but still maintain a minimum comfort,
+[1393.00 --> 1394.46]  that'd be the next level.
+[1394.70 --> 1396.88]  You know, like that's what I really want now for Joops.
+[1397.32 --> 1398.56]  That's our next business idea.
+[1398.96 --> 1400.44]  You know, we had cloudfree.shop.
+[1400.90 --> 1406.80]  You know, the next one is this sort of mega thermostat that beats the pants off the nest.
+[1407.12 --> 1407.44]  Right.
+[1407.92 --> 1412.76]  So Jim wrote into the show and he wants just our thoughts on going solar.
+[1412.88 --> 1416.88]  He says, I'm looking for solar for my home and I'm not really sure where to start looking.
+[1416.88 --> 1420.46]  Everywhere I go, I get bombarded with ads and people who seem like salesmen.
+[1420.96 --> 1423.52]  I've looked at businesses like Tractor Supply and other sources,
+[1423.72 --> 1426.90]  but I worry about what they're selling and if they're actually the best tech.
+[1427.60 --> 1430.04]  And he wonders what we did to look into this,
+[1430.06 --> 1431.86]  because I know you've considered solar for the home,
+[1431.94 --> 1433.62]  you've considered Powerwalls for the home.
+[1434.48 --> 1438.90]  I'm curious what your route and trajectory is when you go off on a research binge for this.
+[1439.30 --> 1443.28]  It's amazing how quickly you end up at the Tesla stuff when you start Googling this stuff.
+[1443.28 --> 1446.68]  They must spend a lot on marketing or SEO or something.
+[1446.68 --> 1452.22]  I ended up looking at getting, I think it was like 12 panels put on my roof.
+[1452.32 --> 1456.28]  Ultimately, it ended up being too expensive to consider right now.
+[1456.30 --> 1458.50]  And they weren't in North Carolina yet and stuff like that.
+[1458.58 --> 1460.30]  So I haven't done it yet.
+[1460.52 --> 1467.42]  It's definitely on my list because I do feel guilty about burning several hundred watts a day of permanent,
+[1467.74 --> 1469.84]  you know, server electricity and stuff like that,
+[1469.88 --> 1473.10]  that could very easily be supplied through solar.
+[1473.10 --> 1477.32]  So, you know, part of it is I want to try and do my bit for the environment.
+[1477.50 --> 1479.76]  But the other part is it'd be nice to save some money too.
+[1480.20 --> 1482.90]  Yeah, the research of it for me has always kind of been,
+[1483.26 --> 1487.16]  I try to find communities that are discussing the type of builds that I'm doing.
+[1487.24 --> 1489.60]  So in my case, they're more mobile builds, but, you know,
+[1489.78 --> 1491.82]  we just shift communities depending on the build.
+[1492.20 --> 1496.14]  And then also YouTube tends to play a pretty significant role.
+[1496.46 --> 1501.74]  And it's really a process of finding and refining the selection of YouTubers you find
+[1501.74 --> 1502.64]  and getting their advice.
+[1503.12 --> 1506.82]  I went to a company called AM Solar to have my mobile install done.
+[1506.96 --> 1512.88]  And I did that through a process of reading lots of reviews about people's solar installs
+[1512.88 --> 1517.62]  and finding forums where people were discussing getting solar installed
+[1517.62 --> 1521.02]  and kind of narrowed it down to a few companies.
+[1521.26 --> 1526.30]  And then, you know, had my geographic location and they were kind of within my striking distance.
+[1526.30 --> 1531.02]  And then I went and looked up pictures of their work, which I think is another really good tip.
+[1531.10 --> 1535.46]  If you can find any on their website or on Google Images, I went and found pictures of their work
+[1535.46 --> 1538.12]  and thought that, you know, everything looked really good and tidy.
+[1538.26 --> 1540.92]  And that was something that was important to me in this installs.
+[1540.96 --> 1543.02]  I didn't want it to be just a ball of wires.
+[1543.02 --> 1547.40]  I wanted it to look like it was maybe built from the factory that way.
+[1547.78 --> 1549.02]  And they did absolutely that.
+[1549.08 --> 1550.62]  So that was sort of my process.
+[1551.18 --> 1554.88]  I don't know about you, but the more salesy a company is, the less interested I am.
+[1554.88 --> 1557.82]  Yeah, and when it comes to that kind of stuff, too, it's easy to get scammed.
+[1557.96 --> 1561.80]  So just take your time, you know, get multiple opinions on stuff.
+[1562.20 --> 1564.48]  And the other thing is, and this is a very U.S.-centric comment,
+[1564.70 --> 1569.78]  but there are some federal tax incentives that tend to expire at the end of each calendar year.
+[1570.08 --> 1576.12]  So I noticed the number of texts I was receiving about sign up for solar now in December
+[1576.12 --> 1577.70]  was a lot higher than it has been in January.
+[1577.88 --> 1579.56]  So just factor that in as well.
+[1579.78 --> 1580.58]  So Phil wrote in.
+[1580.64 --> 1582.96]  He's a fan of your Perfect Media Guide.
+[1582.96 --> 1584.74]  I think it's really helped him a lot.
+[1584.88 --> 1589.70]  And he had questions about your VDEV configurations that you're using for the Perfect Media Server.
+[1590.10 --> 1595.56]  From what I understand, if you use one disk per VDEV, there is no protection benefit for ZFS.
+[1596.26 --> 1601.96]  I'm researching options for setting up a DIY NAS and need to have a cost to bring to the wife
+[1601.96 --> 1603.60]  to get the spousal approval.
+[1605.12 --> 1605.68]  Yeah, we've been there.
+[1605.92 --> 1610.12]  You know, my biggest fear in life is that my wife sells my service for what I told her they cost.
+[1610.12 --> 1614.04]  Yes, and I know she's listening to this.
+[1614.12 --> 1614.86]  So hello, wife.
+[1614.86 --> 1618.18]  I run in a mirror VDEV.
+[1618.50 --> 1619.30]  Very, very simple.
+[1619.52 --> 1626.34]  I just mirror two drives and that gives me 50%, you know, space efficiency and stuff like that.
+[1626.34 --> 1632.38]  So I can sustain one drive failing locally before I need to start resorting to backups.
+[1633.12 --> 1638.12]  Standard moment where I say RAID is not a backup and you should never rely on it as such.
+[1638.12 --> 1643.74]  I very much look at it as that's my primary source of truth.
+[1644.16 --> 1647.88]  But if anything was to go wrong with that server or both of those drives were to fail at once,
+[1648.42 --> 1653.04]  I actually have just, you know, I've been using the Helios 64 since the review for this,
+[1653.10 --> 1662.72]  but I'm just putting together a new system to act as a local ZFS mirror of the mirror VDEV in my house.
+[1662.72 --> 1667.58]  So that will live at the other end of the building in case one end, I don't know, catches fire or something, God forbid.
+[1668.22 --> 1670.44]  So the short answer is mirrored VDEV.
+[1670.74 --> 1677.32]  And if you can swing it as well, a second copy of the data somewhere else and preferably another copy offsite.
+[1677.56 --> 1679.92]  Well, this is right on topic because listener Phil wrote in.
+[1679.98 --> 1684.82]  He said, you guys often talk about syncing files offsite for a backup, but I'd like to hear a little bit more detail.
+[1685.20 --> 1689.60]  How are you guys protecting your backups from things like ransomware or accidental mass deletion?
+[1689.60 --> 1693.22]  In those cases, maybe you're not even aware that something is wrong for months.
+[1693.78 --> 1698.64]  I know we do it in the enterprise level, but I'd love your thoughts on using tools for yourself for folks at home.
+[1698.82 --> 1700.12]  Thanks and keep up the good work, Phil.
+[1700.74 --> 1701.82]  How do you protect your backups?
+[1701.90 --> 1706.36]  And I think you might mean encryption and other things like, you know, the whole gamut.
+[1706.98 --> 1709.32]  Well, ZFS recently added data set encryption.
+[1709.90 --> 1713.92]  So the remote system in my setup isn't encrypted.
+[1714.28 --> 1715.14]  It's at my dad's house.
+[1715.20 --> 1716.86]  So I do trust that as an endpoint.
+[1716.86 --> 1721.60]  But I think that is a valid thing that I want to try and implement moving forward.
+[1721.78 --> 1727.50]  But this is one of the primary reasons I run ZFS is snapshot support.
+[1727.50 --> 1738.16]  So I can roll back to a specific snapshot, you know, much like the Home Assistant Google Drive plugin that lets me do hourly, daily, weekly, monthly backups.
+[1738.16 --> 1740.64]  ZFS lets me do that as well.
+[1740.72 --> 1743.96]  And I use Jim Salter's Sanoid tool to configure.
+[1744.78 --> 1747.92]  I think I've got like 24 hours worth of hourly backups.
+[1748.12 --> 1750.16]  And then I've got a week's worth of daily backups.
+[1750.68 --> 1754.74]  And then I've got four weeks worth of backups going back a month.
+[1754.78 --> 1758.76]  And then I've got one month backup going back six months, I think.
+[1758.80 --> 1760.52]  And then I've got an annual thing as well.
+[1760.52 --> 1762.90]  So pretty well covered, I think.
+[1763.38 --> 1770.14]  But I don't know how I would spot ransomware other than just going to access a file and be like, oh, crap.
+[1770.58 --> 1773.98]  Ransomware I'm not particularly concerned about because it would have to get executed.
+[1774.38 --> 1776.44]  And, you know, the server environment's my data setting on.
+[1776.54 --> 1778.08]  That's not particularly likely.
+[1778.66 --> 1784.72]  Kind of like yourself, I have the NAS here at the studio is kind of like a central repository of truth.
+[1784.72 --> 1789.58]  And then JB as a business has several cloud instances of different data sets.
+[1790.08 --> 1792.28]  I have my data set personally in Lady Joops.
+[1792.46 --> 1797.02]  I sync all of that back to the NAS here at the studio.
+[1797.56 --> 1801.28]  I don't have a great backup solution for that NAS.
+[1801.42 --> 1807.60]  Now, most of the data on it is actually reproducible by all the other locations if I just brought them all back again.
+[1807.84 --> 1812.84]  But now I have a little bit more historical information on there that isn't necessarily duplicated anywhere else.
+[1812.84 --> 1819.06]  And I'm starting to change my opinion on backing up my media stuff.
+[1819.06 --> 1822.28]  In the past, I always thought, well, I have the source material.
+[1822.74 --> 1826.16]  And what I can't find on disk, I could probably find on the Internet.
+[1826.70 --> 1830.20]  And I'm OK with that because I've likely paid for it at some point.
+[1830.44 --> 1832.22]  So I think I'm OK.
+[1832.34 --> 1835.58]  But now I actually have found that that's not necessarily the case.
+[1835.66 --> 1837.70]  I've had trouble getting DVDs and Blu-rays.
+[1837.84 --> 1840.96]  And I've had trouble finding things online of some series.
+[1840.96 --> 1844.80]  So now I'm actually thinking maybe I need to back up absolutely everything.
+[1845.04 --> 1851.16]  But that becomes like, you know, a 15 terabyte problem I have to solve.
+[1851.34 --> 1852.32]  It becomes a race to the bottom.
+[1852.52 --> 1853.34]  Yeah, very quickly.
+[1854.16 --> 1854.34]  Yeah.
+[1854.42 --> 1861.24]  And there's just I mean, I think the only way would be I need to create like a box that maybe I mean,
+[1861.24 --> 1872.24]  maybe it's possible with USB storage if I had the money, if I wanted to invest that kind of money into it and sync it here locally and then take it off site via myself, set it up somewhere off site and sync it up.
+[1872.44 --> 1879.80]  That is the solution, you know, is to build a server and stick 100 terabytes in it and just forget about it.
+[1879.80 --> 1880.16]  Yeah.
+[1880.88 --> 1882.42]  Well, in my case, my parents house.
+[1882.88 --> 1883.80]  I could do my dad's.
+[1883.86 --> 1885.40]  I could probably even do it at Angela's house.
+[1885.62 --> 1887.48]  You know, she has fiber at her at her place.
+[1887.58 --> 1888.50]  She's a pretty good connection.
+[1889.00 --> 1889.32]  I know.
+[1889.82 --> 1890.24]  I know.
+[1890.54 --> 1891.26]  I would love that.
+[1891.72 --> 1901.44]  As far as protecting my backups that I send to Google Drive, which are things like my Docker config directories, my Docker compose files, that kind of stuff.
+[1901.44 --> 1909.30]  I still am very happily using duplicati, which I think I've been using for the entire run of the show, and that will do encryption for me.
+[1909.60 --> 1913.68]  And it handles the both sides, encrypting and decrypting side of it.
+[1914.04 --> 1915.40]  And I just love it.
+[1915.48 --> 1924.80]  And I've experimented with using duplicati to save to multiple different cloud providers, which is kind of what I would do in the case of, say, mass deletion on Google Drive or some sort of issue.
+[1925.24 --> 1929.60]  But I haven't pulled the trigger yet just because of the bandwidth requirements every single night to do that.
+[1929.60 --> 1932.30]  It's not like Google ever killed a product either, is it?
+[1932.68 --> 1935.90]  It seems like Drive's pretty core, but you never know, right?
+[1935.96 --> 1942.38]  They could also start doing stupid things like revoking API access for third-party applications.
+[1942.78 --> 1945.96]  Google Drive itself as a core product is probably safe.
+[1946.06 --> 1946.28]  Yeah.
+[1946.56 --> 1948.22]  Although nothing truly is with Google.
+[1948.22 --> 1961.30]  But the workarounds that I've been using for the last several years of buying one seat of G Suite or whatever it's called this week, and then just uploading three or four terabytes, I think those days are numbered.
+[1961.70 --> 1962.28]  So, yeah.
+[1962.38 --> 1968.32]  I don't know if you saw, but they're also revoking sync access to the Chromium upstream, you know, open source browser.
+[1968.50 --> 1971.50]  They change the terms all the time, and I could see them revoking.
+[1971.68 --> 1977.14]  They've also revoked, like, the sign-on for Geary, the email client on Linux.
+[1977.14 --> 1977.22]  Nice.
+[1977.66 --> 1979.12]  That's just hostile, isn't it?
+[1979.18 --> 1980.74]  I thought their slogan was, don't be evil.
+[1981.02 --> 1984.56]  Well, I think their slogan now is, become ginormous?
+[1984.96 --> 1985.42]  I'm not sure.
+[1985.76 --> 1990.44]  They've done a lot of stuff with turning the screws on storage, particularly in the last six months.
+[1990.66 --> 1990.88]  Yeah.
+[1990.96 --> 2000.52]  So I really don't think that relying on Google anymore as your off-site backup is going to be a viable strategy beyond, I think it's June this year.
+[2000.52 --> 2007.08]  The Google Photos Unlimited Storage for Pixel Owners deal that ended is now officially done, too, as this episode is out.
+[2007.20 --> 2007.80]  So that's all over.
+[2008.26 --> 2008.62]  Yeah, you're right.
+[2008.66 --> 2009.80]  There has been a lot of changes there.
+[2010.22 --> 2011.98]  That's why you mentioned it earlier.
+[2011.98 --> 2021.50]  I think things like cloudfree.shop are the way to go because they're devices that have just been, they're pre-divorced from the cloud when you get them.
+[2021.98 --> 2029.66]  They've been pre-flashed with OSs that are open source, that just use your local network, that don't need any cloud connection.
+[2030.12 --> 2034.10]  And like Alex said, it's somebody in the community that built this, and I just think it's so cool.
+[2034.76 --> 2036.84]  They're like our official, unofficial sponsor.
+[2037.06 --> 2038.28]  We do have a promo, right?
+[2038.38 --> 2039.10]  Do we have a promo code?
+[2039.10 --> 2039.88]  We do, yeah.
+[2040.02 --> 2041.64]  Self-hosted is the coupon code.
+[2042.20 --> 2046.18]  I think you get 10% off a light bulb, and we get a little kickback from anything else that you buy.
+[2046.70 --> 2048.10]  Oh, you know what?
+[2048.14 --> 2049.56]  I need light bulbs at the studio.
+[2049.88 --> 2056.44]  I was going to mention they have that outdoor smart plug, too, which is slick, but I actually am in the market for light bulbs.
+[2056.96 --> 2059.32]  Correction, I think it's smart plugs, not smart bulbs.
+[2059.60 --> 2060.18]  My bad.
+[2060.46 --> 2060.72]  Sorry.
+[2061.40 --> 2062.34]  You know what, man?
+[2062.38 --> 2063.40]  You got me so excited.
+[2063.50 --> 2065.56]  I thought he's got like some sort of light bulb.
+[2065.66 --> 2066.64]  It's all built in over there.
+[2066.70 --> 2067.20]  No, that's cool.
+[2067.58 --> 2067.98]  That's cool.
+[2067.98 --> 2070.14]  The smart plugs, smart plugs will do.
+[2070.54 --> 2071.92]  I thought of a slogan for them, though.
+[2072.04 --> 2074.66]  Cloudfree.shop, your cloud prenup.
+[2075.82 --> 2076.78]  That's pretty good.
+[2077.26 --> 2078.12]  I like that.
+[2078.22 --> 2078.82]  I like that.
+[2079.02 --> 2079.42]  Yeah, you're welcome.
+[2079.56 --> 2080.08]  That's free.
+[2080.44 --> 2084.52]  What do you say we do a couple of NFC automation tricks that the audience wrote in about?
+[2084.64 --> 2086.96]  Because, you know, we've talked about these NFC tags a couple of times.
+[2087.02 --> 2091.88]  I have one right here on the mixer that I've set up to do like D&D and stuff like that and turn on lights.
+[2091.88 --> 2095.66]  This is particularly relevant for me right now because I've just switched to iOS.
+[2096.10 --> 2098.94]  I wanted to take my camera game to the next level.
+[2099.18 --> 2101.62]  And boy, is the camera on this thing good.
+[2101.84 --> 2110.32]  But moving some of the NFC stuff across and just some of the, you know, more esoteric Android stuff that I like has been tricky.
+[2110.32 --> 2120.18]  So with iOS, what happens is when I tap my NFC tag, I then have to tap on a notification that comes in on the phone, which is just, it's just one extra step, right?
+[2120.28 --> 2122.14]  But someone wrote in with a workaround?
+[2122.60 --> 2122.82]  Oh, yeah.
+[2122.90 --> 2124.58]  And this, we got two workarounds.
+[2124.78 --> 2126.26]  And I was wondering about these.
+[2126.32 --> 2129.94]  So that's why I love these emails because I had seen these as possibilities.
+[2130.20 --> 2133.04]  In the back of my mind, I was chewing on it as maybe something to try.
+[2133.58 --> 2136.16]  But this confirms my suspicions.
+[2136.28 --> 2137.42]  Billy wrote in with the first one.
+[2137.42 --> 2140.78]  On episode 35, you guys talked about NFC tags in the car.
+[2140.92 --> 2143.92]  I also use an NFC tag to open my garage door just like the Badger.
+[2144.24 --> 2150.40]  I switched recently from Android to an iPhone and figured out a way to run the NFC automation without having to click the notification.
+[2150.90 --> 2156.66]  It does require that you have your garage door brought into HomeKit, which I am using via Home Assistant.
+[2157.42 --> 2160.14]  He says, then you just create an automation in the Home app.
+[2160.28 --> 2163.82]  When a specific tag is tapped, like toggle the garage door.
+[2163.82 --> 2168.42]  It kind of sucks that you have to do it that way, but it is triggering a Home Assistant action.
+[2168.54 --> 2172.26]  If you're already using the app, this is very easy and it's simple to make it work.
+[2172.42 --> 2178.28]  You could just create a Boolean that acts as a virtual switch in the Home app and then triggers a Home Assistant automation or action.
+[2178.92 --> 2179.60]  That's great.
+[2179.84 --> 2180.92]  That is a great idea.
+[2181.00 --> 2188.52]  And I actually, I have encouraged you off air, but I am encouraging you on air at some point in the future to play around with the HomeKit integration with Home Assistant.
+[2188.52 --> 2199.68]  I don't know if this gets talked about enough because I think maybe we have a lot of Android users out there that are Home Assistant users, but it brings all of the functionality in Home Assistant into HomeKit.
+[2200.20 --> 2204.70]  And that makes it work with your watch, with the HomePods, with Siri.
+[2204.88 --> 2205.82]  It's pretty great.
+[2206.36 --> 2208.12]  I am glad that Billy wrote in with that one.
+[2208.24 --> 2210.72]  I'm also even more gladder.
+[2211.04 --> 2213.98]  That's not a word, but you know what I mean, that he called me the Badger.
+[2214.10 --> 2214.56]  That's fun.
+[2214.96 --> 2215.62]  That is fun.
+[2215.62 --> 2215.78]  Yeah.
+[2216.42 --> 2218.90]  Quinton Ronan with maybe even a better one, though.
+[2219.32 --> 2222.00]  He's also, he says he's a site reliability engineer.
+[2222.78 --> 2225.20]  I think one of you commented about using NFC tags.
+[2225.44 --> 2226.80]  I found a way around this.
+[2227.24 --> 2235.66]  You create a web hook in Home Assistant and then use an automation on the phone, which is created with the shortcuts app, to call that web hook.
+[2236.06 --> 2240.84]  You're allowed to trigger these from an NFC scan without having to confirm the action manually.
+[2240.84 --> 2247.20]  And he has linked us to a post where he explains it more on his blog, so I will include that in the show notes.
+[2247.66 --> 2251.68]  But this is, if you look in the Home Assistant app, you'll see this web hooks action.
+[2252.02 --> 2255.72]  You combine that with the shortcuts app, and you've essentially solved the problem.
+[2255.92 --> 2259.36]  So you've got two options, and one of them doesn't require you mess around with HomeKit at all.
+[2259.80 --> 2260.12]  That's neat.
+[2260.28 --> 2262.94]  I mean, I've only ever really used web hooks when it comes to Jenkins.
+[2262.94 --> 2267.24]  So the fact that we can use them for something actually fun and useful.
+[2267.88 --> 2268.24]  Cool.
+[2268.96 --> 2270.10]  Hey, just a thank you to our members.
+[2270.26 --> 2280.68]  I've noticed some of these emails are from SREs, and we really appreciate everyone who becomes a site reliability engineer, helps the show stay independent, and as a thank you, you get a little extra content.
+[2280.84 --> 2283.64]  A limited ad feed with a little extra content at the end.
+[2283.80 --> 2287.54]  If you'd like to help the show and become a member, it's selfhosted.show slash SRE.
+[2287.82 --> 2289.42]  And so Linus writes in.
+[2289.66 --> 2291.56]  I don't know if it's that Linus, although I doubt it.
+[2291.78 --> 2292.52]  Let's just pretend.
+[2292.52 --> 2295.00]  Okay, Mr. Torvalds.
+[2295.50 --> 2297.34]  I'm going to give you advice on something.
+[2297.48 --> 2297.74]  Yeah, right.
+[2297.86 --> 2298.00]  Okay.
+[2298.48 --> 2299.30]  Linus writes in.
+[2299.48 --> 2302.32]  Could you give your opinions on how your setup will survive you?
+[2302.68 --> 2305.50]  What will happen to your awesome setup if you aren't around anymore?
+[2305.68 --> 2307.96]  Will your spouse just pick up everything and it just work?
+[2308.50 --> 2311.66]  How can I strive towards such a situation if worse comes to the worst?
+[2312.02 --> 2313.72]  Thanks for a great podcast, Linus.
+[2314.04 --> 2314.80]  Deep question.
+[2315.14 --> 2317.54]  One that's a little uncomfortable to think about sometimes.
+[2317.54 --> 2325.52]  I do think this played a little role in my recent renewed push to document as much as my setup as possible in Markdown.
+[2325.52 --> 2332.06]  But I know that, no, my family wouldn't really use these systems.
+[2332.48 --> 2337.42]  I have documented the passwords in a password vault that they have the password to.
+[2337.52 --> 2339.96]  So they, if they needed to, could get access to that.
+[2340.06 --> 2346.36]  And then they could share that with somebody like Alex who could help spin stuff up or down for them and, you know, transition them.
+[2346.36 --> 2347.64]  I think that's a great point.
+[2348.10 --> 2354.20]  Plain text all the things as much as possible and have a Bitwarden or a LastPass or something like that.
+[2354.52 --> 2354.66]  Yeah.
+[2354.78 --> 2356.18]  So right now it's in LastPass.
+[2356.32 --> 2365.68]  However, I have been thinking about transitioning to something else like Bitwarden or something that is, I mean, it's something I want to have a conversation with them because I need to have their buy-off as well.
+[2365.68 --> 2370.68]  But I want to share, you know, primarily with my wife, but there's some things that I would leave for Angela too.
+[2370.80 --> 2375.26]  And so I kind of wanted something that could accommodate different logins with different credentials.
+[2375.42 --> 2377.76]  So if anybody has any suggestions, I'd love to know.
+[2377.86 --> 2381.80]  But what do you think about, do you think your wife would keep it going for a bit?
+[2381.88 --> 2383.50]  Do you think she'd ask just for somebody to help?
+[2383.64 --> 2389.08]  Or do you think she'd just shut it down and get a cable subscription and start reading books?
+[2389.18 --> 2390.54]  I mean, what do you think she would do?
+[2391.08 --> 2393.90]  Well, at the end of the day, this stuff is my hobby.
+[2394.06 --> 2394.32]  Right.
+[2394.32 --> 2399.36]  And it just so happens I've been lucky enough to turn it into a podcast and Linux as a job.
+[2400.06 --> 2403.06]  But I also enjoy doing this stuff in my spare time as well.
+[2403.36 --> 2403.52]  Yeah.
+[2403.72 --> 2419.54]  I just don't see how she or anyone else in my family would have that level of interest to keep things on the road beyond, you know, the initial 6, 12 months, you know, that these things would probably continue running for untouched.
+[2420.18 --> 2424.20]  There are some things I think that would be missed in terms of quality in life.
+[2424.32 --> 2428.06]  Like Plex, like BookSonic, like Home Assistant.
+[2428.06 --> 2440.72]  But are they sufficiently useful that it's not worth just buying a Netflix membership or buying some proprietary smart home automation stuff?
+[2440.72 --> 2446.78]  Like a lot of what we've done is ultimately boils down to being nice to have versus absolutely critical.
+[2446.96 --> 2450.88]  I view it as critical because of my value set and who I am.
+[2450.88 --> 2459.92]  But there's a huge swathe of people in my immediate circle in my family that wouldn't care if that stuff went away tomorrow, really.
+[2459.92 --> 2463.54]  So I think it would continue to work for some time.
+[2463.62 --> 2467.86]  But ultimately, it would sort of decay and die with me, which is a bit sad to think about.
+[2468.36 --> 2468.38]  Yeah.
+[2468.50 --> 2473.22]  I think the things that they would care more about would be things like documents and photos.
+[2473.22 --> 2477.26]  I think that is something that would be a little more significant.
+[2477.62 --> 2485.66]  And so that's something I try to give thought to a little bit long term is just in that maybe I haven't done a good enough job with that currently.
+[2485.66 --> 2491.56]  But it wouldn't take a lot of work to make that pretty accessible to my wife without my help.
+[2492.00 --> 2498.08]  Maybe the way to think about this is try to think of things that they would want access to and then make it as easy as possible for them.
+[2498.64 --> 2502.94]  But it's always worth thinking and trying to build your systems that way, if nothing else.
+[2503.02 --> 2508.76]  Because even though it's a little bit of a morbid thought, I think it actually leads to building better systems.
+[2509.20 --> 2509.56]  Totally does.
+[2509.56 --> 2516.94]  I mean, just stop and ask yourself the question now, if something did happen to you tomorrow or, well, even if it doesn't, right?
+[2516.96 --> 2531.74]  If you just had to give your partner or your brother or sister or parent or something your laptop and say, go and do something, you know, download a photo or find this tax return or whatever it is.
+[2532.50 --> 2537.10]  Do you think they'd be able to do it without you going, oh, you just do this or you just do that?
+[2537.10 --> 2552.46]  You know, and if the answer is no, then like Chris says, maybe you need to write some better documentation and print it out or something and put it in a safe or something and say, go to this web URL and you will find the answers to the kingdom, you know.
+[2552.92 --> 2560.36]  It kind of goes back to a topic that comes up on our show, well, several times over the, you know, the year plus run now because it's over a year now.
+[2561.02 --> 2561.50]  Craftsmanship.
+[2561.88 --> 2562.28]  Absolutely.
+[2562.86 --> 2565.48]  You know, and that can be another aspect of craftsmanship about your setup.
+[2565.48 --> 2566.04]  And why not?
+[2566.08 --> 2567.40]  Because nobody else is going to do it.
+[2567.50 --> 2568.46]  And it's your setup.
+[2568.88 --> 2570.90]  It's your opportunity to show a little craftsmanship.
+[2571.00 --> 2574.48]  And also it's another, it's another nice way for people to remember you by.
+[2574.54 --> 2577.42]  Look at the time and effort he took to make this accessible for us.
+[2577.64 --> 2578.56]  So it's a win-win.
+[2578.70 --> 2579.92]  It's just a matter of time.
+[2580.28 --> 2583.34]  And I kind of pulled back on it a little bit, but you know what?
+[2584.00 --> 2585.24]  Mr. Torvald's writing in here.
+[2585.30 --> 2587.40]  It's got me feeling like I'm going to keep up with it again.
+[2587.40 --> 2591.86]  It's like inheriting someone else's workshop tools, you know.
+[2592.12 --> 2592.42]  Yeah.
+[2592.66 --> 2595.70]  When my wife's dad passed away, we inherited a bunch of his workshop stuff.
+[2595.96 --> 2601.96]  And it was, I don't know, just odd to be in someone else's cave, you know.
+[2602.16 --> 2604.72]  And I guess it's a similar situation with these types of systems.
+[2604.92 --> 2609.08]  So I'm all sad now thinking about this.
+[2609.54 --> 2612.14]  I feel like if I logged into your box, though, I'd feel pretty comfortable.
+[2612.14 --> 2613.18]  I'd have a pretty quick.
+[2613.18 --> 2615.56]  Yeah, but you're a massive nerd, mate, you know.
+[2616.10 --> 2616.76]  I know, I know.
+[2616.84 --> 2620.10]  But that's what's, I mean, there's something about that that's like kind of weird, like
+[2620.10 --> 2621.24]  server swapping.
+[2621.40 --> 2623.52]  We should try that sometime and then record our reaction.
+[2624.40 --> 2626.08]  Yeah, like wife swap, but shitter.
+[2627.96 --> 2631.68]  Yeah, just like almost like that, but just a little bit different.
+[2633.04 --> 2634.12]  Just see what it's like.
+[2634.22 --> 2634.88]  Where would it air?
+[2634.94 --> 2635.88]  Would it air on TLC?
+[2636.12 --> 2636.88]  Would that be the place?
+[2637.38 --> 2639.02]  No, I don't think they'd want it.
+[2639.10 --> 2641.60]  But, you know, it's funny is if you look at some of my servers,
+[2641.60 --> 2647.16]  you can really see transitions and how I organize stuff or just legacy stuff.
+[2647.26 --> 2652.64]  Like the way we have the NAS set up here is really, really far and removed on how I build
+[2652.64 --> 2655.56]  a system now and the way I lay out the disks and all of it.
+[2655.72 --> 2661.16]  And actually, the ZFS array that we're using was originally set up and partitioned and managed
+[2661.16 --> 2661.92]  by Alan Jude.
+[2662.12 --> 2664.54]  So it's like extensively complex.
+[2665.32 --> 2666.30]  The man, the myth, the legend.
+[2666.64 --> 2668.38]  Yeah, he set it up while he was out here.
+[2668.38 --> 2669.92]  And it's worked with us.
+[2670.02 --> 2673.72]  I mean, it's clearly scaled for years because we've changed out operating systems.
+[2673.86 --> 2674.62]  We've moved hardware.
+[2674.98 --> 2679.02]  But that ZFS pool just continues to grow and survive.
+[2679.70 --> 2684.26]  But if you look at it now, it's a total, total misrepresentation of how I would build
+[2684.26 --> 2684.72]  a system.
+[2685.70 --> 2687.78]  Not to mention just because it's an Arch server.
+[2688.26 --> 2691.60]  Didn't it start life on BSD and now, yeah, like you say, it's running Arch?
+[2692.14 --> 2693.52]  Yeah, BSD for a while.
+[2693.60 --> 2695.38]  I think it lived on Fedora for a bit.
+[2695.62 --> 2696.88]  And now it's on Arch.
+[2697.08 --> 2700.54]  And so far, it stayed there because it's a minimum viable Arch.
+[2700.68 --> 2703.84]  So it's just the absolute bare minimum of a system we need.
+[2704.10 --> 2704.98]  Yeah, I was listening to that.
+[2705.02 --> 2707.56]  Was it Coda where you were talking about minimum viable server?
+[2708.06 --> 2713.62]  And I was resonating so hard with that because I've just switched over to Proxmox and all
+[2713.62 --> 2715.28]  of its weird abstractions and stuff.
+[2715.36 --> 2718.16]  And I was thinking, oh, if I was just on Arch, this would have been so easy.
+[2718.20 --> 2719.92]  It would have been done 10 minutes ago, you know.
+[2719.92 --> 2720.76]  Yep, yep, yep.
+[2721.00 --> 2722.28]  Yeah, there is something to that.
+[2722.52 --> 2725.78]  I also want to mention our sponsor, Cloud Guru, is on social media.
+[2725.88 --> 2728.66]  So if you are learning this stuff right now and you want to engage with them on social
+[2728.66 --> 2732.60]  media, they're just slash a Cloud Guru on YouTube, Twitter, and Facebook.
+[2733.14 --> 2736.00]  Alex, you're probably on Twitter too, I bet.
+[2736.34 --> 2737.32]  I sure am.
+[2737.42 --> 2739.20]  I'm there at, let's stop that.
+[2739.26 --> 2740.14]  Let's stop that right now.
+[2740.60 --> 2742.28]  I am there at Ironic Badger.
+[2742.54 --> 2742.74]  Yep.
+[2742.80 --> 2745.58]  And you can contact the show, self-hosted.show slash contact.
+[2745.90 --> 2748.72]  That's the place to get in touch and get your email on the show.
+[2748.72 --> 2753.92]  I'm at ChrisLAS and the show itself is at self-hosted show on the Twitter.
+[2754.38 --> 2755.44]  Okay, I almost started doing it again.
+[2755.48 --> 2755.78]  I'm sorry.
+[2756.08 --> 2757.20]  I don't know what came over me.
+[2757.56 --> 2758.46]  It was weird.
+[2758.70 --> 2759.40]  It got weird.
+[2759.72 --> 2760.86]  Oh, I shouldn't do accents.
+[2760.92 --> 2761.62]  That's what we've learned.
+[2762.04 --> 2763.98]  You can find the network at Jupiter Signal.
+[2764.40 --> 2767.02]  And that was self-hosted.show slash 37.
+[2767.02 --> 2770.60]  Neverland Fluge Event
+[2772.68 --> 2772.70]  at Jupiter Signal.
+[2772.78 --> 2772.88]  To 1st.
+[2772.96 --> 2773.32]  To 1st.
+[2773.52 --> 2775.58]  To 2nd.
+[2775.66 --> 2776.48]  To 2nd.
+[2776.56 --> 2777.56]  To 2nd.
+[2779.72 --> 2780.48]  To 2nd.
+[2784.54 --> 2784.76]  To 2nd.
+[2785.78 --> 2786.08]  To 2nd.
+[2786.62 --> 2786.92]  To 2nd.
+[2787.70 --> 2787.98]  To 2nd.
+[2787.98 --> 2788.66]  To 2nd.
+[2788.76 --> 2789.14]  To 1st.
+[2789.28 --> 2789.80]  To 2nd.
+[2789.92 --> 2789.94]  To 4th.
+[2789.94 --> 2790.86]  To 5th.
+[2790.92 --> 2791.78]  To 2nd.
+[2792.00 --> 2792.66]  To 3nd.
+[2792.72 --> 2793.08]  To 4th.
+[2793.10 --> 2793.90]  To 3rd.
+[2794.02 --> 2794.10]  To 4th.
+[2794.12 --> 2794.58]  To 530.

38： Crouching Pi, Hidden Server _summary.txt

@@ -0,0 +1,54 @@
+• Shout out to the self-hosted subreddit for community love
+• Discussion of involving community members in future shows, including a potential "community spotlight" segment
+• Sharing and learning from each other's projects and ideas
+• Phone tethering hack to bypass carrier data limits using TTL parameter
+• Use of WireGuard to get around carrier bandwidth shaping
+• VPN solution for bridging AT&T and Verizon
+• Unlimited data plans and bandwidth limitations
+• TTL parameter for full speed data allowance
+• Self-hosted file sync and sharing solutions (Nextcloud vs FileRun)
+• FileRun features and functionality (file indexing, search, guest users)
+• File Run is discussed as a tool for file syncing and management with an enterprise version available
+• The mention of Docker Compose relates to setting up File Run on a system
+• TermPad.io is introduced as a simple text editor-like application that provides syntax highlighting
+• The discussion of termpad.com mentions it as a hosted version of the software, with options for self-hosting and database-free operation
+• TinyPin is discussed as an alternative to Pinterest, providing a minimalistic image collection board that can be self-hosted in a container
+• OpenSense stores data in a data directory and has a simple setup process
+• OpenSense 21.1 (Marvelous Meerkat) was released, featuring new firewall rules and improved traffic graphs
+• Comparison to pfSense's addition of WireGuard support
+• Discussion of the speaker's frustration with getting WireGuard working on OpenSense
+• Consideration of switching from OpenSense to ViOS or other alternatives due to the difficulty with WireGuard
+• Discussion of WireGuard and its use with Linux servers
+• Introduction to the Linux server WireGuard container, which simplifies setup and configuration
+• Demonstration of using Docker Compose with the WireGuard container
+• Mention of John Muchovesch's blog post on routing specific containers through the WireGuard container
+• Promotion of Linode as a cloud hosting provider, offering fast network connections and competitive pricing compared to AWS and Google
+• The host discusses the benefits of using Linode as an independent cloud provider
+• Accusations are made that the show is similar to the Raspberry Pi and RV Home Assistant podcast
+• The host shares their experience with running Home Assistant on a Raspberry Pi 4
+• They discuss the limitations of using a USB-to-SATA converter for storage
+• A previous setup involving Intel GVT-G pass-through and virtual GPUs did not work out as expected, resulting in kernel panics and hung processes
+• Discussion of running Plex on a server with QuickSync
+• Using Proxmox to run Docker containers and LXCs, but not managing them directly due to limitations
+• Preference for minimizing host reboots by keeping the host clean and using VMs
+• Alternative setup options, including installing Docker directly on the host or considering different hardware configurations
+• Use of Intel GVTG technology in a previous server configuration that proved unreliable
+• Plans to repurpose an HP290 as a Windows box with Pi KVM for server use
+• Discussion of a Homelab setup using Dual Xeons and 128GB RAM, but considering underutilization for specific tasks
+• Potential use of smaller hardware, such as Raspberry Pis, for certain tasks and the trade-offs between performance and cost
+• Discussion around scaling down Pis and scaling up Pi usage
+• Comparison between Raspberry Pi and Odroid devices, with the speaker preferring x86 boxes for home hosting due to compatibility and flexibility
+• Challenges of using ARM devices in production, including limitations and edge cases
+• Importance of implementation and ecosystem in determining a device's effectiveness
+• Advertisement for A Cloud Guru's Linux networking and troubleshooting course
+• Discussion around backing up Home Assistant through a Google Drive plugin
+• Google Drive backup add-on for Home Assistant
+• Automatic snapshot management and configuration options
+• Integration with Duplicati for system-level backups
+• Comparison of using Git to manage config files vs. existing setup
+• Discussion of the cost and complexity of rewriting code versus incremental changes
+• The concept of "if it ain't broke, don't fix it" and its application in software development
+• Technical debt as an investment vs. a necessary evil
+• The importance of learning from past mistakes and building on existing code
+• The potential need to restart or reboot projects due to complexity and scope creep
+• Self-hosting projects and the trade-offs between feature set, complexity, and deployment ease

38： Crouching Pi, Hidden Server _transcript.txt

@@ -0,0 +1,661 @@
+[0.00 --> 3.98]  Coming up on the show today, Alex shocks me with his latest project. Seriously.
+[4.24 --> 8.52]  Then he lays down some quick fire picks. So get your notepad ready.
+[8.78 --> 13.54]  And then we'll discuss what's going on with OpenSense's WireGuard setup. I'm Chris.
+[13.84 --> 19.86]  I'm Alex. And this is self-hosted. No, wait, the RV and Home Assistant podcast, episode 38.
+[21.14 --> 24.84]  Thought I'd open today's show with a quick shout out to the self-hosted subreddit.
+[24.94 --> 28.58]  We had some love from you guys this week. Hello. Hello. Hi, if you're listening.
+[28.58 --> 30.20]  Hey there. How's it going?
+[30.48 --> 34.40]  It was pretty cool. Like someone tagged me in one of the threads who is on our Discord.
+[34.68 --> 38.12]  And I don't know, it's just cool to see community come together like that.
+[38.22 --> 45.10]  And we aren't like an official partner with the subreddit or anything, but I reached out to one of the mods or, well, they reached out to me.
+[45.12 --> 49.98]  And we had a chat about a few things. We might have them on one of the shows in future.
+[50.02 --> 54.36]  And it's sort of got my mind thinking about how we can involve the community a bit more.
+[54.36 --> 65.78]  And, you know, getting random people on to talk about their setups and sort of figure out what containers people are running, how much storage they actually have, what the hardware underneath is.
+[65.88 --> 71.86]  You know, maybe we could have a little 10, 15 minute segment every now and again with community members, like a community spotlight section.
+[72.28 --> 78.72]  And you know what will end up happening is we'll get all these ideas from each other and we'll then all go off and build projects and get excited to do different stuff.
+[78.88 --> 79.38]  That'd be awesome.
+[79.38 --> 82.48]  People often accuse me of making them spend money. Well, it's not my fault.
+[84.32 --> 85.98]  I can attest to that, actually.
+[88.06 --> 89.94]  Yeah, I feel like that has definitely been the case.
+[90.04 --> 94.18]  I mean, the thing is, is I love just getting ideas from the community in general.
+[94.28 --> 98.38]  We get people that email into the show, but like you were saying, also over on Reddit, there's some great ideas.
+[98.50 --> 102.16]  And our Discord, that's another spot where I see people kicking around stuff.
+[102.16 --> 109.34]  And often either, either tried something and it, and then tell us about it or are thinking about trying something and want our advice.
+[109.42 --> 111.00]  That kind of stuff goes down in there all the time as well.
+[111.44 --> 114.70]  My favorite stuff to read about is, well, there's two things.
+[114.84 --> 116.52]  One is the stuff that works really well.
+[116.52 --> 128.56]  But the other thing is things, you know, all the stuff that people try and then abandon, for whatever reason, that's more often more interesting because that's what takes the time.
+[128.76 --> 132.26]  That's what eats my time is trying stuff and failing and trying stuff and failing.
+[132.42 --> 136.30]  And if I can community crowdsource that stuff, I'm in.
+[136.30 --> 136.74]  Absolutely.
+[138.02 --> 139.76]  There's always many ways to learn.
+[139.88 --> 144.90]  Like our friends over at A Cloud Guru, they are the leader in learning for the cloud, Linux, and other modern tech skills.
+[145.36 --> 148.12]  They have hundreds of courses, thousands of hands-on labs.
+[148.24 --> 151.94]  You can get certified, you can get hired, you can get learning at acloudguru.com.
+[152.56 --> 156.94]  Now, I've been doing a lot of travel the last few weeks back and forth to the hospital.
+[157.68 --> 160.36]  And I've been needing to use a lot of hotspot data.
+[160.36 --> 162.94]  And I came across, this was on Hack 5, I think, actually.
+[162.94 --> 177.22]  Yeah, I came across just a really interesting little hack, little tip for anybody looking to do, you know, phone tethering and try and bypass the limits that people have that Verizon or AT&T and people like that set.
+[177.38 --> 178.20]  Now you got my attention.
+[178.48 --> 181.26]  Yeah, I'm sure I do, given that your house is on wheels.
+[181.74 --> 185.68]  So the thing you can do is set something called a TTL, time to live parameter.
+[186.00 --> 192.22]  And this is apparently how the phone providers recognize whether you're on a laptop or a phone.
+[192.22 --> 195.28]  That seems too easy, too good to be true.
+[195.34 --> 206.00]  But I can confirm, having been streaming Netflix over 4G, 5G for the last month, that I went from it being unwatchable to being usable.
+[206.26 --> 207.08]  So it does work.
+[207.14 --> 209.16]  And there's a link in the show notes to a Reddit thread about this.
+[209.50 --> 210.18]  This is fantastic.
+[210.84 --> 213.68]  I absolutely have struggled with this.
+[214.26 --> 215.90]  I've experimented with this myself.
+[215.90 --> 222.32]  So by checking the TTL of the IP packets, they seem to be able to suss out the type of device that it is.
+[222.78 --> 227.20]  But you can tweak that yourself, which is what this guide walks you through.
+[227.86 --> 228.96]  And there's other ways, too.
+[229.50 --> 239.16]  I have found WireGuard to be an extremely successful way to get around carrier bandwidth shaping, which is really what's happening here is they're looking at your IP traffic, right?
+[239.16 --> 243.50]  And they can say, okay, well, you're going to YouTube on port 443 or whatever it is.
+[243.52 --> 246.10]  They can actually look at the traffic because it's all running over their gear.
+[246.76 --> 248.74]  They have complete access to your traffic.
+[248.74 --> 257.60]  And they have systems in place that will automatically force, and in some cases, in a really brute sort of lowbrow way.
+[258.02 --> 270.66]  One of the ways AT&T will do this is they will just make YouTube smack up against a wall and try all of the different bit rates until YouTube, the servers, finally select a low enough bit rate.
+[270.84 --> 274.20]  And then AT&T will allow the YouTube traffic to pass.
+[274.58 --> 275.54]  And that's how they do it.
+[275.54 --> 282.12]  Then you have others like T-Mobile who will actually re-encode your video traffic while it's in transit.
+[283.10 --> 284.28]  Yeah, there's different approaches.
+[284.62 --> 285.04]  That's nuts.
+[285.16 --> 289.54]  That sounds, I mean, that's going to cost them a lot in CPU, surely, if nothing else.
+[289.86 --> 291.36]  That may not be how they do it anymore either.
+[291.44 --> 292.36]  They change as well.
+[292.48 --> 297.08]  So that's why I say today in early 2021 may not be how they do it at the end of 2021.
+[297.08 --> 303.58]  But I have found, so what I do is I have a kind of a special sauce VPN.
+[303.84 --> 308.54]  It's a bit of a proprietary solution from a vendor, but it bridges AT&T and Verizon.
+[308.84 --> 311.16]  And the endpoint is a couple of Linode servers.
+[311.90 --> 315.52]  And the carriers just have no idea what I'm doing when I do that.
+[315.56 --> 319.82]  And that allows you to get around this, but it doesn't allow you to get around bandwidth limitations.
+[319.82 --> 325.26]  So if you still have, you know, X amount, you know, 18 gigs a month and you can't go over that, it doesn't solve that problem.
+[325.44 --> 326.40]  Are you on an unlimited plan?
+[326.92 --> 327.44]  I am, yes.
+[327.66 --> 332.70]  My employer pays for it, so I don't really have to look at the bill, which is quite a nice position to be in.
+[332.80 --> 334.54]  Oh, that is sweet.
+[334.76 --> 341.68]  You mean, really, as a consumer, as an average consumer, it's pretty tricky to even get unlimited data to begin with, let alone get it for free.
+[342.04 --> 346.60]  Well, I'm sure it's, you know, it's Verizon Unlimited, so it's probably got all sorts of T's and C's.
+[346.60 --> 353.98]  I think I get 30 gig of hotspot data and then the rest is throttled down to like 600 kilobits or something like that.
+[354.70 --> 363.06]  What this TTL parameter does is it basically gives you all of your data allowance that the T's and C's permit at full speed.
+[363.60 --> 365.34]  That's effectively what this does.
+[365.82 --> 366.44]  That is great.
+[366.52 --> 368.26]  We will put a link to that in the show notes.
+[368.52 --> 371.92]  It's going to be different per carrier, but that seems to work on Verizon.
+[371.92 --> 372.74]  Mm-hmm.
+[373.46 --> 377.76]  Now, have you been looking for a self-hosted file sync and sharing, like, web UI?
+[378.38 --> 381.84]  This just came up, actually, within 24 hours.
+[382.08 --> 384.98]  And I don't really know what's good anymore, so I'm hoping you have a solution for me.
+[385.18 --> 394.68]  Well, I was spinning up some stuff on Proxmox the other day, and I had a VM, and I didn't have Samba installed on my server because I'd literally just built it.
+[394.72 --> 397.20]  I hadn't run the Ansible, and I just needed one file.
+[397.20 --> 401.22]  So I thought, why don't I find a web UI to browse my files?
+[401.64 --> 402.62]  And I thought, well, I've got Nextcloud.
+[402.72 --> 404.34]  I could just upload the zip file to Nextcloud.
+[404.50 --> 407.24]  Oh, wait, I haven't deployed Docker yet.
+[407.28 --> 408.32]  I haven't done all this stuff yet.
+[408.44 --> 419.88]  So what I did was I ended up spending two hours to solve a five-minute problem by spinning up FileRun, which is a self-hosted file sync and sharing solution.
+[419.88 --> 430.44]  It purports to install on any private Linux, Mac, or Windows server, but it will also support, you know, cPanel-style, PHP-based type stuff as well.
+[430.76 --> 433.62]  I've got it running out of a container, well, four, actually.
+[433.76 --> 438.16]  So it uses the FileRun container itself.
+[438.26 --> 447.50]  It uses Elasticsearch and something called Apache Ticker to do file indexing as well as MariaDB or MySQL for a backend database.
+[447.50 --> 454.52]  So it's not a super lightweight thing, but it is very pretty, it's very performant, and it does exactly what it says on the tin.
+[454.86 --> 458.08]  I don't really need the search, so I don't need all that overhead.
+[458.22 --> 466.50]  What I really wanted was just browse my files, but this does have something I hadn't considered, but now looking at the feature list would be extremely useful.
+[467.28 --> 470.20]  And that is it lets you send file requests to somebody.
+[470.20 --> 475.96]  So I could send you a request, say, hey, Alex, send me that, you know, send me that batch of pictures or whatever.
+[476.62 --> 478.18]  And then it would give you a way to send those to me.
+[478.62 --> 481.80]  It's not like you send and receive files around the internet for your day job or anything, is it?
+[482.06 --> 482.64]  Yeah, right?
+[482.92 --> 489.88]  And so to actually be able to request something from someone, it just seems like it's a, it's a sort of an extra level of care for guests on the network.
+[489.88 --> 493.94]  And then it also supports guest users too, which I also would need.
+[493.94 --> 501.18]  And so help me understand this, is it creating its own document space and what you upload and put into it is what you see through the web UI?
+[501.34 --> 505.50]  Or does it let you browse existing folders and files on your server?
+[506.08 --> 508.90]  So you're trying to compare it to a Nextcloud with that comment, I suppose.
+[509.42 --> 513.96]  With Nextcloud, you end up sort of creating your own space within your file system.
+[513.96 --> 522.02]  But this guy, FileRun, you just point it at a file share or an existing directory or a volume bind mount, in my case, with a container.
+[522.78 --> 524.14]  And everything just showed up.
+[524.18 --> 525.32]  I didn't have to change permissions.
+[525.52 --> 526.98]  I didn't have to mess about with anything else.
+[527.34 --> 534.16]  I've actually got it set to read only just because, well, I mean, the DNS that I have is exposed through traffic.
+[534.36 --> 537.34]  So, I mean, it's not going outside my LAN anyway.
+[537.82 --> 541.72]  But, you know, I feel like a web UI, it's a bit too easy to get a bit trigger happy sometimes.
+[542.10 --> 543.62]  So it's read only for me.
+[543.62 --> 545.90]  I just want to use it to download the odd file here and there.
+[545.98 --> 549.20]  But it's very useful and no import is required.
+[549.54 --> 551.84]  So, yeah, very easy to get started.
+[552.36 --> 553.86]  That is exactly what I was hoping for.
+[553.94 --> 558.98]  It seems it also even has file versioning, if that's something that matters to you, and has a trash.
+[559.10 --> 562.28]  So if you delete something, it'll first store them in there before it gets permanently erased.
+[562.34 --> 564.90]  So you kind of have an escape hatch if you need it.
+[565.54 --> 565.88]  All right.
+[566.48 --> 566.72]  Yep.
+[567.10 --> 570.10]  I'm going to deploy this, especially since it seems like...
+[570.10 --> 571.06]  You know what you need to do, Alex?
+[571.06 --> 572.52]  You've got to send me your Docker Compose for me.
+[572.52 --> 573.48]  Make it real easy for me.
+[574.38 --> 574.80]  All right.
+[575.52 --> 575.84]  Yeah.
+[575.90 --> 576.76]  But no, I'm going to give it a try.
+[576.90 --> 577.62]  That's a great find.
+[577.70 --> 579.04]  It's called, again, File Run.
+[579.42 --> 583.54]  So they do offer an enterprise version in case you see any prices or anything like that.
+[583.60 --> 586.20]  It's free for up to 10 users for personal and family use.
+[586.28 --> 591.10]  But they have paid versions for, you know, small businesses and enterprise as well.
+[591.34 --> 592.60]  So they have a means to make money.
+[592.66 --> 593.58]  They have a business side.
+[593.58 --> 596.46]  And that means it's probably going to stick around.
+[596.72 --> 597.76]  Does use web dev, though.
+[598.00 --> 599.38]  I'm never mad keen on web dev.
+[599.60 --> 603.34]  But that does mean you can do file syncing using, I think, the next cloud client.
+[603.76 --> 604.68]  We'll talk to this.
+[605.18 --> 609.64]  And if you're behind a corporate firewall, too, it's just kind of nice to do everything over the web ports.
+[610.06 --> 612.74]  I'll put a link to my Compose snippet in the show notes.
+[613.22 --> 615.78]  I did come across a new project called TermPad.
+[616.02 --> 617.86]  I think it's termpad.io this week.
+[617.98 --> 618.30]  All right.
+[618.32 --> 619.02]  Let's take a look at this.
+[619.20 --> 619.82]  TermPad, huh?
+[620.10 --> 620.90]  TermPad.com.
+[621.06 --> 621.74]  My apologies.
+[622.36 --> 627.00]  And it's a very, very super simple, like, if you just create some text and then click save.
+[627.28 --> 629.40]  Oh, that's what I'm seeing.
+[629.70 --> 630.48]  Oh, my gosh.
+[630.48 --> 634.20]  It's a full screen, not a terminal per se, but it looks kind of like one.
+[634.64 --> 635.70]  This is just a write space.
+[636.38 --> 636.98]  It's neat.
+[637.38 --> 642.40]  You know, like, Docker containers come up with fake names if you don't name them, like Angry Torvalds or something.
+[643.66 --> 644.02]  Yeah.
+[644.02 --> 646.48]  It's funny my mind went to Angry Torvalds, isn't it?
+[646.52 --> 646.86]  It's funny.
+[647.02 --> 647.42]  Funny that.
+[647.42 --> 656.74]  So the one I've just created for you was termpad.com slash awful wide eyed napkin, which is a really strange, random generated name.
+[656.84 --> 662.84]  But it does code syntax highlighting as well, just for super simple, you know, paste bin stuff.
+[663.00 --> 663.64]  There's no database.
+[663.90 --> 665.48]  It's all just open.
+[665.82 --> 668.90]  So termpad.com is a hosted version, free.
+[669.02 --> 670.50]  I don't know what happens to the data on that one.
+[670.72 --> 672.34]  But you can self host it as well.
+[672.34 --> 675.10]  There is a container, which we'll put a link to in the show notes.
+[675.10 --> 677.36]  Kind of surprisingly useful.
+[677.60 --> 678.02]  I love it.
+[678.60 --> 680.90]  Okay, let's see if you are two for two here, Alex.
+[680.98 --> 682.12]  Tell me about TinyPin.
+[682.52 --> 684.12]  We're going to be redoing our bathroom soon.
+[684.24 --> 687.40]  So I was looking across Pinterest the other day and it's just garbage.
+[687.54 --> 691.48]  They make you sign in and do all this kind of nonsense about tracking what you're looking at.
+[691.66 --> 695.96]  And I mean, it's kind of okay from a discovery point of view, but it's also just garbage.
+[696.72 --> 697.36]  I hate Pinterest.
+[697.36 --> 703.06]  So I went on the look for something, you know, minimal to just share like a mood board almost.
+[703.14 --> 704.42]  And I came across TinyPin.
+[704.72 --> 706.08]  I'll put a link in the show notes, of course.
+[706.36 --> 709.88]  And this is a self hosted minimalistic image collection board.
+[710.66 --> 711.40]  Super simple.
+[711.58 --> 715.06]  You can run it in a container and there isn't a lot else to say.
+[715.20 --> 718.72]  It just does the job it's supposed to do, which I suppose is the praise that you want.
+[719.20 --> 720.98]  And it's nice to see that they have Chrome extensions.
+[721.50 --> 725.78]  And through iOS shortcuts, there's a way you could add it to your share sheet as well.
+[725.78 --> 726.84]  It seems that's handy.
+[727.16 --> 732.16]  I don't see necessarily something in here for Android, but there probably is a means if you can think it up.
+[732.76 --> 743.54]  I had a quick look at TinyPin just before the show and it is very minimal, but it does a good job of laying images out in different sizes in a very dynamically scalable way.
+[743.60 --> 747.88]  So you can have a tablet size, you can have a full web page version, or it can be on your phone.
+[748.06 --> 753.44]  And it actually manages to sort of present the images in a unique way while also letting you get in there at full screen.
+[753.44 --> 756.20]  So I kind of, I think this is a nice little find.
+[756.26 --> 760.28]  I don't quite grok how it's, okay, can you explain to me how it's sucking the images in and storing them?
+[760.32 --> 761.88]  Because that's the part I don't quite grok.
+[762.18 --> 763.14]  No, I'm not sure.
+[764.02 --> 766.94]  It stores in the backend, it stores stuff in a data directory.
+[767.08 --> 769.10]  So it's just a volume bind mount on the file system.
+[769.36 --> 771.86]  Nothing too crazy, no database needed or anything like that.
+[772.14 --> 775.10]  And you could go sniffing through there and back them up pretty easily if you needed to.
+[775.26 --> 775.58]  Mm-hmm.
+[775.98 --> 777.10]  Okay, well, we're two for two.
+[777.18 --> 778.22]  I think that's a pretty good find.
+[778.34 --> 780.18]  I think also the wifey would really love that one.
+[780.26 --> 783.04]  That'd be a good one to add to the home server to impress her, I think.
+[783.70 --> 786.32]  Now I want to see if you can be three for three on this one, Alex.
+[786.42 --> 788.80]  Tell me about OpenSense 21.1.
+[789.16 --> 791.36]  I vicariously OpenSense threw you.
+[792.56 --> 797.00]  Well, PFSense made a bit of a stink the other week by adding WireGuard support finally.
+[797.56 --> 805.80]  And not to be outdone, the OpenSense project released 21.1, which is nicknamed Marvelous Meerkat.
+[806.20 --> 806.54]  Hmm.
+[806.54 --> 813.32]  They say that it has new and improved firewall rules, NAT categories, better traffic graphs, all that kind of stuff.
+[813.76 --> 819.44]  And they have a really small dig in their release notes at PFSense, which I really enjoyed, which says,
+[819.88 --> 828.00]  for those wondering, the WireGuard plugin has been available on OpenSense since 2019 and receives continuous improvements by its maintainer.
+[828.00 --> 830.34]  And that feature is unlikely to change.
+[830.34 --> 834.76]  My eyes were immediately drawn to that in their release notes.
+[835.58 --> 838.24]  I didn't realize PFSense had added WireGuard, but this is really good now.
+[838.32 --> 840.40]  We have it in both OpenSense and PFSense.
+[840.84 --> 842.92]  Our WireGuard future has arrived.
+[842.92 --> 848.92]  I'm just sad that it didn't make it into in 2020 because my prediction was that PFSense would ship WireGuard.
+[849.62 --> 853.20]  But I guess those BSD guys just shit when they're ready.
+[853.72 --> 855.52]  No plans for you to go back, I assume?
+[855.72 --> 858.32]  You're going to stick with the old OpenSense, I would imagine?
+[859.86 --> 861.58]  OpenSense is kind of driving me crazy.
+[861.82 --> 862.06]  Oh.
+[862.32 --> 863.18]  There's a few reasons.
+[863.64 --> 865.74]  Mostly to do with WireGuard, if I'm honest.
+[866.06 --> 867.92]  I just think the implementation is...
+[868.72 --> 870.48]  Maybe it's user error.
+[870.48 --> 886.22]  Okay, I will fully admit that I am not a network guy, but I spent, from the hospital, at least two or three weeks for maybe half an hour to an hour at a time, most days, trying to get WireGuard fully working.
+[886.54 --> 889.48]  So I can connect in remotely just fine.
+[890.00 --> 893.84]  I can ping the firewall just fine.
+[893.92 --> 896.34]  I can connect to the web UI of the firewall itself just fine.
+[896.58 --> 899.60]  I can route traffic through my home internet connection just fine.
+[899.60 --> 904.84]  But I can't access any hosts on my LAN, which kind of defeats the purpose for me.
+[904.92 --> 910.36]  I mean, I don't necessarily really want to route my traffic through my house, but it's a nice benefit of WireGuard.
+[910.60 --> 917.70]  What I wanted was to be able to access Proxmox or ESXi remotely and continue rebuilding my servers, which I've been doing for the last couple of months.
+[917.70 --> 925.40]  And I've wasted, I don't even know how many hours, trying to make this effing thing work.
+[925.52 --> 930.96]  And I wrote the man page on WireGuard for OpenSense, and I feel like a fraud because I just can't make it work.
+[932.36 --> 933.50]  I wrote the book.
+[933.72 --> 936.70]  I'm convinced at this point that there is a bug that I can't find.
+[936.70 --> 947.12]  So I'm probably going to NukemPave my OpenSense install, which is, I don't want to do it, but I've wasted so much time and I'm convinced I've got all the firewall rules set up correctly.
+[947.68 --> 949.54]  I don't see that I'm left with any other option.
+[950.30 --> 961.32]  And so that then makes me think, well, if I'm going to NukemPave OpenSense, why don't I try ViOS or some other, I don't know, there's a million different options to try out there.
+[961.32 --> 966.26]  Or I could just go whole hog and run, you know, CentOS streams and IP tables.
+[967.50 --> 969.42]  Go full West Payne on it is what you could do there.
+[969.56 --> 970.26]  He does it home.
+[971.00 --> 973.04]  Yeah, that WireGuard routing issue is tricky.
+[973.16 --> 976.38]  He and I had to do some troubleshooting to get that working here at the studio.
+[977.36 --> 980.34]  ViOS, I've heard the Discord talking about that recently.
+[980.46 --> 981.42]  Is that a firewall platform?
+[981.84 --> 982.28]  It is, yeah.
+[982.30 --> 983.90]  It's Linux-based, so not BSD.
+[984.60 --> 987.46]  There's no web UI whatsoever, so far as I'm aware.
+[987.46 --> 995.60]  I did try it once about a year ago for a few hours and the learning curve is real, so I gave up.
+[997.02 --> 1002.46]  The trouble is with learning a firewall is you go on the internet to Google stuff, don't you?
+[1003.06 --> 1006.76]  But if your firewall's down, you have a hard time doing that.
+[1006.88 --> 1012.36]  So there are some things that are so mission critical that I just almost can't be bothered to change them
+[1012.36 --> 1016.72]  because I know how much work it's going to be to learn a new thing and OpenSense is good enough.
+[1017.46 --> 1018.62]  I do love the project.
+[1018.76 --> 1020.84]  I mean, I think it's very stable.
+[1021.02 --> 1022.40]  I never have to reboot the box.
+[1022.50 --> 1025.56]  I never have to worry about updates or anything like that.
+[1026.08 --> 1028.56]  But this WireGuard issue is kicking my ass, to be honest with you.
+[1028.96 --> 1029.30]  I agree.
+[1029.38 --> 1030.24]  It is a great product.
+[1030.72 --> 1036.44]  It is a solid project that, and PFSense before it, too, just I also really like it.
+[1037.00 --> 1037.58]  But I get you.
+[1037.70 --> 1038.36]  I know what you mean.
+[1038.54 --> 1041.54]  And sometimes it's really easy with WireGuard because something has it built in,
+[1041.62 --> 1044.82]  like some of the GI routers that we've talked about before.
+[1045.46 --> 1047.24]  And sometimes it's something you've got to build up.
+[1047.46 --> 1053.58]  I'm the guy that was trying to do WireGuard from behind a double carrier grade NAT to a Linode,
+[1053.74 --> 1054.86]  then down to the studio.
+[1055.24 --> 1057.26]  And I wanted to get to everything by its name.
+[1057.46 --> 1058.96]  And I mean, that's quite the setup.
+[1059.22 --> 1060.70]  Maybe we'll chat more about it sometime.
+[1060.70 --> 1066.06]  What I did end up doing was I ended up looking at the Linux server WireGuard Docker image.
+[1066.66 --> 1068.78]  Now, this thing is slick AF.
+[1069.70 --> 1071.56]  So you spin up the container.
+[1071.80 --> 1072.90]  You do it in Docker Compose.
+[1072.98 --> 1075.60]  You name your peers just as an environment variable.
+[1075.60 --> 1078.26]  So you can either say, I want peers four.
+[1078.66 --> 1081.76]  You know, so I want four peers and just deal with peers via a number.
+[1081.76 --> 1087.60]  Or you can say peers and then just put a space limited list.
+[1088.10 --> 1094.06]  So, you know, you put phone space, desktop space, server, whatever, as the environment variable.
+[1094.06 --> 1096.84]  And it will go and generate all the config files for you.
+[1096.94 --> 1098.56]  But here's the really cool bit.
+[1098.56 --> 1107.04]  They've built in an alias into the container that will print out a QR code for each of those setups from a single line command.
+[1107.68 --> 1108.92]  It's just slick.
+[1109.16 --> 1117.44]  You know, after messing about with OpenSense for so long and it's kind of older, less mature, I would say, implementation,
+[1117.74 --> 1120.72]  to come across the Linux server container was just a breath of fresh air.
+[1121.42 --> 1123.38]  And so I ended up using our sponsor, Linode.
+[1123.58 --> 1126.74]  So you can use the coupon code linode.com slash SSH.
+[1126.74 --> 1133.54]  I ended up using our sponsor, Linode, to spin up a host dedicated to running this Linux server WireGuard container.
+[1133.82 --> 1135.28]  And it just works really well.
+[1135.34 --> 1136.32]  The performance is great.
+[1136.74 --> 1138.94]  And I'm able to back this thing up.
+[1139.00 --> 1141.72]  So I know that if anything happens, I've got the Linode backups.
+[1142.22 --> 1143.52]  It just works really, really well.
+[1144.28 --> 1151.56]  And whilst I was fiddling about with this container, I ran across a blog post from John Muchovesch.
+[1152.24 --> 1153.96]  I'm sorry, I probably butchered that name.
+[1153.96 --> 1157.20]  The website link will be in the show notes, of course.
+[1157.46 --> 1159.40]  And this is super cool.
+[1159.70 --> 1165.48]  It lets you route specific containers through the WireGuard container as well.
+[1165.56 --> 1172.50]  So you're able to use the Docker networking to potentially have multiple instances of WireGuard going to different places for different services,
+[1172.50 --> 1174.00]  all on the same box.
+[1174.76 --> 1187.56]  And it uses a parameter that is released as part of Docker Compose 3.8 schema of network mode service colon WireGuard to route the traffic through that container.
+[1187.74 --> 1195.26]  So you could, for example, basically bind NextCloud or any other service to listen only on that WireGuard server,
+[1195.62 --> 1198.24]  just using one line of config in your Compose file.
+[1198.50 --> 1199.28]  Super cool.
+[1199.28 --> 1201.06]  And I love this kind of stuff.
+[1201.06 --> 1204.80]  linode.com slash SSH.
+[1204.88 --> 1209.66]  Go there to get a $100 60-day credit towards a new account and go there to support the show.
+[1209.74 --> 1211.80]  This is a great way to see what Linode can do.
+[1212.26 --> 1213.86]  They're our cloud hosting provider.
+[1214.04 --> 1218.40]  If it's backend infrastructure for the network, if it's a game server for my kids,
+[1218.52 --> 1222.88]  or if it's a project we're working on for self-hosted, we run it all on Linode.
+[1223.14 --> 1224.90]  You have $100 here to work with.
+[1225.24 --> 1226.22]  I mean, I want to be frank with you.
+[1226.22 --> 1229.04]  You can do so much at Linode with that much credit.
+[1229.60 --> 1231.90]  Check out some of their GPU systems.
+[1232.02 --> 1232.94]  These are crazy.
+[1233.06 --> 1239.38]  And in fact, Cloud Spectator Benchmarking, it's a group that goes around and tries the performance aspects of different cloud providers.
+[1239.38 --> 1248.80]  They recently said that Linode has the fastest GPUs in the industry, outperforming AWS, Azure, Google.
+[1249.10 --> 1254.98]  I mean, if you have any kind of image manipulation workload that you need to do and you just want to crank it out super fast,
+[1255.32 --> 1261.14]  go to linode.com slash SSH and get our $100 credit and use some of it for that.
+[1261.60 --> 1267.76]  Image stuff is so cool right now because there's so many fun open source projects that you can play with and easily deploy on Linode.
+[1267.76 --> 1275.78]  The entire stack, regardless of what kind of system you get, they all have super fast native SSDs, 40 gigabit connections into the hypervisors,
+[1275.92 --> 1278.30]  and they have 11 data centers around the world.
+[1278.38 --> 1282.60]  So there's probably something that's going to work for you, a client, a customer, et cetera.
+[1283.08 --> 1289.94]  And additionally, they have all of this while being 30 to 50% less than AWS or Google, right?
+[1289.98 --> 1290.96]  I mean, that's what's amazing.
+[1291.12 --> 1293.74]  Fastest GPUs, crazy fast network connections.
+[1294.10 --> 1296.40]  The reason why is they've been around since 2003.
+[1296.40 --> 1299.30]  So they had a lot of time to figure out how to do this right.
+[1299.62 --> 1303.44]  They have had a lot of time to get great deals, great network providers and connections.
+[1303.94 --> 1308.38]  I mean, this is the benefit of being an independent cloud provider for as long as they have.
+[1308.44 --> 1310.58]  They got a jumpstart on everybody else.
+[1310.78 --> 1316.00]  And you can benefit now by going to linode.com slash SSH and you can support this here show.
+[1316.96 --> 1320.82]  Linode is really dedicating to offering the best Linux experience in the cloud.
+[1320.82 --> 1325.80]  If it runs on Linux, you'll be able to run it on Linode and be able to manage it easily with their cloud manager.
+[1326.28 --> 1327.90]  Linode.com slash SSH.
+[1328.06 --> 1330.32]  Thanks to Linode for sponsoring the self-hosted program.
+[1330.84 --> 1335.72]  And thanks to everybody who supports our show by visiting linode.com slash SSH.
+[1335.72 --> 1338.28]  What show is that?
+[1338.28 --> 1343.80]  I mean, we had accusations this week of being the Raspberry Pi and RV Home Assistant podcast.
+[1344.24 --> 1348.62]  Well, it kind of goes that way sometimes, but I think it's a reflection of the trends of the time, man.
+[1349.44 --> 1352.36]  Pi's come to a really good price point and performance.
+[1352.90 --> 1355.28]  Low power is more popular than ever.
+[1355.72 --> 1357.24]  Also, low noise, I'll point out.
+[1357.92 --> 1361.20]  And Home Assistant is just blown up in the last three years.
+[1361.20 --> 1366.72]  You know what's really going to annoy that comment here in particular is that I have been running Home Assistant on the Pi.
+[1366.92 --> 1370.58]  So we're going to talk about the Pi for a little bit right now for the last month.
+[1370.70 --> 1371.64]  And it's been great.
+[1371.72 --> 1372.30]  The Pi 4.
+[1372.80 --> 1376.26]  I found an old SSD in a drawer, 120 gig SSD.
+[1376.48 --> 1378.06]  That's probably five years old.
+[1378.74 --> 1385.64]  And I have, from my shucking of easy stores, I have a USB to SATA converter.
+[1385.84 --> 1387.48]  So I just reused that.
+[1387.48 --> 1391.56]  So I'm upcycling, reducing e-waste, all that kind of good stuff.
+[1391.76 --> 1392.12]  Go me.
+[1392.78 --> 1401.34]  And I put the Raspberry Pi Home Assistant image on there, expecting it to be, you know, I'm coming from an x86 platform.
+[1401.50 --> 1407.22]  So whilst I move across from my Xeons to the Intel system and sort of redo things and move things around,
+[1407.28 --> 1411.70]  I got fed up of my DNS stopping working all the time because I was running AdGuard in a container.
+[1411.70 --> 1419.34]  And I got fed up of Home Assistant not being up because it automates a lot more in my house than I really realized when it's not there.
+[1420.30 --> 1424.36]  And I was expecting the Pi to be just a stopgap.
+[1424.50 --> 1431.32]  I was expecting it to be good enough, but I was expecting to be ready to leave it after a few weeks.
+[1431.32 --> 1437.54]  And I'm pleasantly surprised to report that I think it's fine for most people.
+[1437.98 --> 1438.08]  Wow.
+[1438.12 --> 1439.10]  I got to take all this in.
+[1439.22 --> 1441.88]  This is a moment in the show.
+[1441.96 --> 1442.74]  Episode 38.
+[1442.86 --> 1444.16]  Mark it down in the books, everybody.
+[1444.36 --> 1444.76]  Wow.
+[1445.42 --> 1445.78]  Wow.
+[1445.88 --> 1448.90]  Because I feel like you always thought I was a little silly for doing it on the Pi.
+[1449.04 --> 1449.36]  I did.
+[1449.62 --> 1450.12]  I'll be honest.
+[1450.20 --> 1450.40]  Yeah.
+[1450.40 --> 1453.82]  I mean, the storage thing is still a problem.
+[1454.00 --> 1462.96]  I don't like having an SSD with its ass hanging out on my desk with some random SATA to USB board connected up.
+[1463.16 --> 1468.98]  And I'm not comfortable, if I'm being honest, with so much of what I depend on running over USB.
+[1469.50 --> 1469.80]  Yeah.
+[1470.12 --> 1470.74]  I don't like it.
+[1470.98 --> 1471.32]  I agree.
+[1471.40 --> 1471.64]  Totally.
+[1472.18 --> 1473.70]  But the performance has been good.
+[1473.84 --> 1477.86]  I mean, I don't do anything too crazy with image processing or anything like that through Home Assistant.
+[1477.86 --> 1483.92]  I do that generally through Blue Iris, which is a dedicated box in my closet over there.
+[1484.44 --> 1486.82]  And this leads us nicely into some follow-up.
+[1486.92 --> 1497.00]  So a little while ago, I talked about doing or wrote about doing Intel GVT-G pass-through, which is virtual GPUs.
+[1497.12 --> 1504.30]  So you can slice up the graphics card built into your CPU into a couple of slices, give Plex and QuickSync one slice,
+[1504.38 --> 1506.96]  and then give Blue Iris and QuickSync another slice over there.
+[1506.96 --> 1512.16]  And then there's still some left for the host at the same time with no PCIe GPUs required.
+[1512.88 --> 1514.42]  That's like the holy grail for me.
+[1514.48 --> 1515.88]  That was like the perfect setup.
+[1516.78 --> 1519.38]  Unfortunately, it didn't work very well.
+[1519.48 --> 1520.36]  Didn't work out very well.
+[1520.82 --> 1521.02]  What happened?
+[1521.26 --> 1524.24]  I was getting kernel panics with Proxmox.
+[1524.52 --> 1529.16]  I was getting hung processes without kernel panics.
+[1529.16 --> 1532.92]  So it was fine as long as I wasn't running Blue Iris.
+[1533.24 --> 1540.04]  And I think the Windows Blue Iris load was just too much for the GVT-G stuff to handle.
+[1540.70 --> 1543.96]  And I wrote a blog post about how to do it with Proxmox.
+[1544.08 --> 1547.20]  And a lot of people have been pinging me about the performance and stuff like that.
+[1547.20 --> 1555.96]  So this is unfortunately my update is to say that I have bought and sold an HP 290 in the last month because I was so happy it worked.
+[1556.04 --> 1559.00]  And then the proof in the pudding turned out to be it wasn't good enough.
+[1559.06 --> 1564.40]  So I've gone back to a dedicated Windows box for Blue Iris with QuickSync.
+[1564.40 --> 1576.06]  And now my server is still the i5-8500 that I purchased running Plex using QuickSync on that box with pass-through for the storage and that kind of stuff to a VM.
+[1576.66 --> 1583.62]  So I'm running Plex on the host, but I'm still running most of my containers in a VM on that host with Proxmox.
+[1583.76 --> 1585.62]  And a lot of people will think I'm mad for doing that.
+[1585.62 --> 1591.94]  But I prefer doing it that way because it minimizes the number of reboots I need to do on the host.
+[1591.94 --> 1596.42]  When you say you're running on the host, do you mean in a container or do you mean actually installed like a package?
+[1596.84 --> 1599.12]  Plex is running in a container on top of Proxmox.
+[1599.78 --> 1601.80]  A Docker container, not an LXC.
+[1602.12 --> 1608.96]  I'm using LXC for stuff like AdGuard and a couple of other things like Bastion, SSH host and that kind of stuff.
+[1609.12 --> 1615.10]  But for the most part, I like to try and keep the host as clean as possible to minimize host reboots.
+[1615.20 --> 1619.56]  Because, you know, when I reboot that server, it takes a lot of services out and it's a pain in the bum.
+[1619.74 --> 1621.04]  So I'd rather not do that.
+[1621.04 --> 1624.92]  And Proxmox, does it still give you a GUI to manage a Docker container pretty well?
+[1625.00 --> 1626.80]  Like all that's just built into Proxmox?
+[1627.04 --> 1627.82]  Not Docker, no.
+[1627.88 --> 1629.76]  It does LXCs, but not Dockers.
+[1630.10 --> 1634.04]  So did you get on the host, like command line and install Docker?
+[1634.70 --> 1635.60]  SSH, yeah, yeah.
+[1635.78 --> 1637.94]  I mean, so Proxmox is built on top of Debian.
+[1638.32 --> 1643.96]  And actually the route that I went to install Proxmox was a naked Debian install.
+[1644.12 --> 1648.08]  And then you can install the Proxmox packages and repos on top of that.
+[1648.08 --> 1652.82]  So it's just, you know, vanilla Debian with the Proxmox kernel effectively.
+[1653.30 --> 1657.88]  It's not like FreeNAS where you start mucking about on the host OS and you could really screw stuff up.
+[1658.30 --> 1660.02]  That's what's always put me off on these appliances.
+[1660.30 --> 1660.58]  You could.
+[1660.70 --> 1661.64]  I mean, it's Linux.
+[1661.92 --> 1664.18]  But Proxmox isn't an appliance.
+[1664.36 --> 1665.50]  It's an abstraction layer.
+[1665.50 --> 1674.04]  So they do weird stuff with like networking and they put all the VM configs in, you know, bespoke places that are unique to Proxmox.
+[1674.22 --> 1678.26]  And that's probably my biggest issue with Proxmox as a project, to be honest, is it's slightly esoteric.
+[1678.62 --> 1683.60]  But once you learn those little foibles, does the job.
+[1684.22 --> 1685.24]  Yeah, it doesn't seem like it's too bad.
+[1685.28 --> 1686.28]  And you were able to get it working.
+[1686.88 --> 1690.84]  So you kind of have a real, I mean, a bit of a hodgepodge right now.
+[1690.84 --> 1694.74]  Sounds like you got like three different servers running in your house right now.
+[1694.74 --> 1695.30]  I did.
+[1695.48 --> 1695.66]  Yeah.
+[1695.82 --> 1701.98]  So I predicated all of my buying and purchase decisions around this Intel GVTG stuff actually working.
+[1702.72 --> 1710.22]  And it was only once it had been in production for a couple of weeks, I sort of really realized that now this isn't this isn't going to be reliable enough.
+[1710.52 --> 1713.70]  And I'm going to have to constantly keep poking and tending this thing.
+[1714.48 --> 1724.54]  And so, yeah, going back to the HP290 as a Windows box, the i5-8500 based system with Pi KVM.
+[1724.74 --> 1726.06]  I'm going to have to be able to use it as my server.
+[1726.42 --> 1734.26]  And then I've got a Homelab box as well, which currently is the Dual Xeons, which I was running for the last two, three years with 128 gigs of RAM.
+[1734.26 --> 1738.24]  And I'm going to use that as like a Homelab slash backup box.
+[1738.44 --> 1741.08]  So I'll power it on minimum, I don't know, once a week, whatever.
+[1741.78 --> 1746.94]  Have a couple of 10 terabyte hard drives in there and mirror my ZFS array with ZFS send or whatever.
+[1746.94 --> 1750.98]  And then that'll be my on-site backup, effectively.
+[1751.32 --> 1764.34]  But what I'm thinking is that those Dual Xeons are massive overkill for running OpenShift in my context of developing infrastructure at work, which is its primary use case.
+[1765.22 --> 1769.02]  And so I'm thinking maybe I could get away with a knock or two for that role.
+[1769.02 --> 1772.98]  Or maybe I should just stop spending money and just use what I've got.
+[1773.48 --> 1778.46]  Well, I think clearly you just haven't gotten the Pi religion enough because that just sounds like great uses for a bunch of Pis.
+[1779.22 --> 1779.92]  Oh, yeah.
+[1780.32 --> 1781.88]  Because you also have a Pi running now.
+[1781.98 --> 1783.16]  You now have a Pi running with Home Assistant.
+[1783.26 --> 1784.42]  So it is several systems.
+[1784.42 --> 1785.86]  Yeah, I think so.
+[1785.98 --> 1789.42]  I probably will take Home Assistant off the Pi.
+[1790.28 --> 1794.14]  I'll probably put it back on Proxmox because I've got NVMA storage in there.
+[1794.34 --> 1801.02]  It's going to be more performant than the Pi, particularly when you're loading lots of plugins like VS Code and the heavier stuff like Node.red.
+[1801.40 --> 1803.30]  You do notice a difference there.
+[1803.78 --> 1805.34]  Yeah, or snapshots or updates.
+[1805.62 --> 1807.54]  Yeah, updates for sure.
+[1808.02 --> 1810.92]  It takes 10 or 15 minutes instead of five.
+[1810.92 --> 1815.04]  So, yeah, you do notice it's a less powerful system.
+[1815.32 --> 1822.44]  But in terms of just day-to-day functionality of controlling your devices and automations, it does do the job just fine.
+[1822.64 --> 1827.58]  Well, that's the thing about an automation, right, is it just happens without me knowing how long it takes.
+[1827.82 --> 1831.74]  And if it takes eight milliseconds instead of four, I don't really care.
+[1832.72 --> 1839.74]  No, and for me, in my particular use case, because in 2021, I think I will be off-grid more than I ever have been.
+[1839.74 --> 1841.22]  And power matters more than ever.
+[1841.34 --> 1843.08]  I've actually been condensing down.
+[1843.82 --> 1845.34]  I'm now down to just two Pis.
+[1845.56 --> 1849.98]  And I'm going to try to condense down to maybe just one Pi or the Odroid item.
+[1850.06 --> 1850.64]  I'm not sure yet.
+[1850.98 --> 1853.68]  The Pi intervention that we staged appears to be working then.
+[1854.08 --> 1854.56]  Yeah, it's funny.
+[1854.62 --> 1856.98]  As I'm sort of scaling down, you're scaling up your Pi usage.
+[1857.12 --> 1858.58]  I think you'll be on the show soon.
+[1858.66 --> 1860.76]  Tell me about more Pi deployments you've done.
+[1860.76 --> 1862.34]  You say that.
+[1862.74 --> 1867.68]  But I was looking at the Odroid stuff, particularly after Home Assistant Blue came out.
+[1867.78 --> 1869.50]  I was like, okay, well, this is the future of Home Assistant.
+[1869.64 --> 1872.14]  I should just buy one of those and call it good.
+[1872.30 --> 1874.08]  But they're $180.
+[1876.08 --> 1877.16]  That's too much.
+[1877.32 --> 1881.86]  Like compared to what you can buy as a used Dell or a used HP system,
+[1882.58 --> 1886.90]  the HP 290 that's now running my Blue Iris was $140 shipped.
+[1886.90 --> 1889.60]  And for that, I got a 500 gig hard drive.
+[1889.96 --> 1896.70]  I got eight gigabytes of RAM and a QuickSync capable eighth gen Intel CPU with two PCIe slots.
+[1897.02 --> 1898.88]  So I can add an NVMe drive.
+[1899.16 --> 1900.02]  X86 compatibility.
+[1900.46 --> 1902.02]  Yeah, and X86 as well.
+[1902.46 --> 1906.44]  So I could add any eighth gen Intel CPU into there if, for whatever reason,
+[1906.50 --> 1908.10]  the Celeron that's in there isn't good enough,
+[1908.46 --> 1912.18]  which it is actually for the six cameras that I have with QuickSync.
+[1912.74 --> 1914.82]  I could add an NVMe drive in there.
+[1914.88 --> 1915.96]  I could add more RAM.
+[1915.96 --> 1917.76]  I can do PCIe slots.
+[1918.12 --> 1919.04]  And it was $140.
+[1919.62 --> 1920.80]  It is too expensive then.
+[1920.90 --> 1922.14]  The Eldroid is just too expensive.
+[1922.28 --> 1925.74]  And it doesn't have the compatibility that the Raspberry Pi 4 does.
+[1926.00 --> 1928.52]  I'm still feeling the pain from that Helios purchase.
+[1928.92 --> 1929.12]  Yeah.
+[1929.24 --> 1936.64]  I still feel really almost burned by that because I thought ARM would be better by now.
+[1936.82 --> 1937.76]  It's just a struggle.
+[1938.16 --> 1939.76]  Like whenever you're trying to do something,
+[1939.76 --> 1947.52]  you'll always come across some edge case of the container you want to run doesn't have an image for the correct architecture.
+[1948.08 --> 1953.34]  Or, you know, some package isn't built for ARM or it's not got QuickSync.
+[1953.34 --> 1955.38]  I know I keep going on about QuickSync, but it is amazing.
+[1956.34 --> 1970.64]  And for me, the price I pay of a few extra watts and a few extra liters of space in my house being used up is totally worth it for not having to futz around with ARM stuff for another year or two until it's ready.
+[1970.64 --> 1974.06]  Yeah, I think that's a perfectly reasonable outlook.
+[1974.52 --> 1975.96]  Even you make a good price argument.
+[1976.34 --> 1984.56]  I think the reality is that if I could only choose between an x86 box or an Odroid type system for my home hosting,
+[1984.76 --> 1987.38]  I would absolutely choose the x86 box every single time.
+[1988.18 --> 1992.44]  There are kind of examples in the market, though, that show us where ARM is going.
+[1992.74 --> 1994.92]  So I think this is going to be a solved problem.
+[1995.20 --> 1999.10]  It really kind of demonstrates how it's all about implementation.
+[1999.10 --> 2003.44]  You look at Apple with the M1, look what they're capable of doing with ARM,
+[2003.78 --> 2010.16]  and then you look at, say, the Raspberry Pi Foundation and the different kind of scale of machines they can do with ARM
+[2010.16 --> 2014.74]  and the ecosystem they've built around it now and the foundation that they have built around it.
+[2015.34 --> 2019.66]  There are implementations that do it really well, and then their implementations are a little bit rough.
+[2019.76 --> 2024.72]  And I think it's so nuanced, it's hard for consumers to understand the value differences there.
+[2024.72 --> 2029.96]  And I think that's why you and I have been kind of chilling on this recently is because these are sort of the unspoken things
+[2029.96 --> 2033.66]  that aren't necessarily specs that are bullet points on a web page.
+[2033.74 --> 2037.54]  These are the more nuanced things that you learn over time when you use them in production.
+[2038.28 --> 2039.22]  By using it, yeah.
+[2039.72 --> 2045.84]  By trying to solve a particular problem and butting your head up against endless forum posts,
+[2046.06 --> 2051.72]  or in some cases, because what you're trying to do, you might be the first trying to do it on ARM.
+[2051.72 --> 2055.18]  There are no forum posts, and good luck to you, you know.
+[2056.54 --> 2061.70]  Well, our friends at A Cloud Guru want you to know about their Linux networking and troubleshooting course this month.
+[2062.14 --> 2067.04]  This is something you may want to look into if you need the fundamentals or want to know more about tools and techniques
+[2067.04 --> 2072.02]  or use cases to configure, manage, and troubleshoot Linux in a networking context.
+[2072.42 --> 2076.70]  By the end of their course, you'll feel comfortable in working with a large variety of networking tools
+[2076.70 --> 2081.08]  and configurations to manage complex Linux networking implementations.
+[2081.08 --> 2085.42]  It's at A Cloud Guru, and we will have a link in the show notes to go specifically to this course
+[2085.42 --> 2087.36]  or go to acloudguru.com.
+[2088.98 --> 2093.48]  Continuing talking about the pie, just to annoy that one specific Reddit commenter.
+[2094.34 --> 2096.18]  I'm full troll mode today.
+[2096.72 --> 2101.26]  We talked about backing up Home Assistant last time through a Google Drive plugin,
+[2101.84 --> 2105.30]  and a little birdie tells me you tried it out at last.
+[2105.78 --> 2107.20]  You talked me into it. You did.
+[2107.30 --> 2107.68]  Hooray!
+[2107.68 --> 2110.38]  You in the audience, we got a couple of emails in about it too.
+[2110.58 --> 2113.74]  And so I finally gave this Google Drive backup a try.
+[2113.90 --> 2115.92]  It's an add-on specifically for Home Assistant.
+[2116.14 --> 2121.06]  And this is a good example of why it's kind of nice to have the full supervised Home Assistant setup
+[2121.06 --> 2124.96]  is it's easy to add repositories for this kind of stuff, and you're off to the races.
+[2125.70 --> 2128.70]  And what it lets me do, and if you're not familiar, we talked about it a little bit,
+[2128.76 --> 2131.22]  is it lets you take your snapshots and send them up to Google Drive.
+[2131.30 --> 2132.78]  Pretty simple. That's all it does.
+[2132.78 --> 2139.44]  What I've learned now after using it for a little bit is it has a couple of nice built-in management features.
+[2139.56 --> 2144.88]  It'll keep four snapshots locally, and by default it'll keep four snapshots in Google Drive,
+[2144.96 --> 2146.94]  but that is totally configurable.
+[2147.42 --> 2150.42]  You can also have it automatically create the snapshots for you,
+[2150.56 --> 2154.68]  which is probably a feature I needed more than I realized.
+[2154.68 --> 2160.54]  I was only doing snapshots right before major events, but if you think about it, it could break at any time.
+[2161.08 --> 2161.86]  Something could die.
+[2162.22 --> 2163.70]  You need stuff that's more current.
+[2163.80 --> 2170.10]  So I set this every three days at 2 a.m. to take a snapshot and then upload it to Google Drive.
+[2170.28 --> 2175.64]  And what I really was impressed by is how it displays what snapshots are local only,
+[2175.74 --> 2179.60]  what snapshots are on Drive, and just really easy options to manage it.
+[2179.92 --> 2183.84]  And as you would expect, it's stupid easy to connect it to your Google account.
+[2183.84 --> 2188.20]  It just uses all of Google's authorization stuff where you go through all the standard Google login screens,
+[2188.32 --> 2190.56]  and it's set up and you're off to the races.
+[2190.64 --> 2192.04]  I can't believe how easy it was.
+[2192.18 --> 2193.62]  And now it's just hands off.
+[2194.02 --> 2195.94]  There's a little triangle as well that shows up to say,
+[2196.18 --> 2200.20]  this snapshot will be deleted when I run the next backup set,
+[2200.28 --> 2205.12]  just so that you know, oh, right, that's my weekly snapshot falling off the end of the conveyor belt.
+[2205.30 --> 2208.06]  I like this pairing with Duplicati too.
+[2208.18 --> 2211.18]  So this is how I'm still backing up any of my system level stuff.
+[2211.18 --> 2213.70]  This has nothing to do with Raspberry Pi or Home Assistant.
+[2213.82 --> 2216.90]  You could use this on any Linux box, and I really, really love it.
+[2217.60 --> 2222.00]  Duplicati is what I use for off-siting my Docker Compose files,
+[2222.12 --> 2225.02]  my configuration files in general, Etsy Config,
+[2225.56 --> 2229.66]  any of those kinds of things that I think I would want to be able to restore
+[2229.66 --> 2231.96]  if I were to reload a base system.
+[2231.96 --> 2234.74]  I use Duplicati to off-site that system level stuff.
+[2235.12 --> 2238.82]  So now I have this Home Assistant Google Drive paired for the snapshots,
+[2239.04 --> 2243.14]  which is the application level stuff, and Duplicati for the system level stuff.
+[2243.42 --> 2247.30]  And I feel like I probably have my backup more dialed in than I ever have right now.
+[2247.74 --> 2252.04]  Are you not ever tempted to use, you know, Git to manage your config files?
+[2252.10 --> 2253.24]  Because they are just text files.
+[2253.70 --> 2257.34]  You've put that seed in my mind a little while ago, and I have been considering it.
+[2257.34 --> 2262.10]  It's mostly just taking the time to set it up and bother.
+[2262.68 --> 2266.36]  Because what I have now kind of works, so I don't have like an impetus to replace it.
+[2266.62 --> 2270.02]  But I know I probably should replace it before I have that impetus.
+[2271.10 --> 2278.22]  I'm reminded of a conversation I had at my first developer job with one of the senior architects.
+[2278.50 --> 2283.04]  I came in fresh out of my computer science degree.
+[2283.42 --> 2284.06]  Just a lad.
+[2284.40 --> 2284.68]  Yeah.
+[2285.22 --> 2286.90]  Saying, well, why don't we just rewrite this?
+[2286.90 --> 2287.90]  Why don't we just rewrite that?
+[2288.00 --> 2288.72]  I mean, this is stupid.
+[2288.82 --> 2289.46]  This is really old.
+[2289.54 --> 2290.98]  Why are we still running Java 5?
+[2291.12 --> 2291.98]  And blah, blah, blah, blah, blah, blah.
+[2292.68 --> 2295.30]  And he sort of sat me down, and it was over like lunch break.
+[2295.34 --> 2297.04]  It wasn't like a super formal thing.
+[2297.10 --> 2301.90]  But he was like, well, what you've got to realize, Alex, is that when you rewrite code,
+[2302.34 --> 2304.42]  obviously there's a cost to rewriting the code.
+[2305.26 --> 2307.04]  Someone has to pay that bill.
+[2307.72 --> 2311.04]  The business, in air quotes, the business has to pay that bill.
+[2311.04 --> 2318.18]  Some product manager somewhere has to sign off product owner and say, yes, I'm going to pay for this out of my budget and do that.
+[2318.98 --> 2319.32]  All right.
+[2319.40 --> 2320.12]  Okay, cool.
+[2321.16 --> 2322.86]  What's the spec going to be?
+[2323.38 --> 2325.64]  Well, at a minimum, it's got to be what it already does.
+[2325.64 --> 2330.48]  But what the product owner is looking for is something extra.
+[2330.72 --> 2338.06]  They want to add a new type of credit card that they can accept, or they want to add a new feature, whatever it might be.
+[2338.06 --> 2354.10]  And so the bill for them to add a new feature to the existing pile of crap that's already there is, you know, 5% versus 105% of rewriting the entire code base, which could take multiple years.
+[2354.78 --> 2362.56]  During which time, you still have to innovate to keep ahead of your competition and patch and write code for the old code base.
+[2362.56 --> 2379.22]  And you're just like, oh, yeah, now I see why massive enterprises have code bases that are 30, 40 years old that people are scared to touch because what they have just works and is a stinking cash cow.
+[2379.40 --> 2381.26]  So the spec is the code.
+[2381.32 --> 2382.16]  The code is the spec.
+[2382.36 --> 2384.40]  Why would anybody fit?
+[2384.54 --> 2390.18]  If it ain't broke, don't fix it or just keep fixing the minimum viable fixes, you know?
+[2390.18 --> 2393.76]  What you call technical debt, they call an investment.
+[2394.96 --> 2396.02]  It's very true.
+[2396.38 --> 2397.22]  It's very true.
+[2397.76 --> 2401.78]  Yeah, I've very much had that same arc over my career.
+[2401.94 --> 2404.72]  I was the bull in the china shop.
+[2404.76 --> 2407.98]  Let's come in and tear it all down and replace it with the new stuff guy.
+[2409.00 --> 2413.34]  And towards the end, I was the guy being like, well, let's not replace it.
+[2413.40 --> 2414.72]  Let's build on what we've got.
+[2414.72 --> 2417.88]  But I feel like in some ways, you know, you learn how to do things better.
+[2418.10 --> 2420.32]  And by the end, you should be able to build on what you've done.
+[2420.98 --> 2423.00]  But software is tricky like that.
+[2423.32 --> 2424.64]  Sometimes it is better just to restart.
+[2424.80 --> 2426.78]  And we see it a lot with the projects we use to self-host.
+[2426.88 --> 2433.90]  You'll see them either fork or you'll see them just sort of reboot completely with a little bit less features because that's the only way they could get it out the door.
+[2434.74 --> 2436.40]  Well, we're just about done, I think.
+[2436.70 --> 2438.24]  But we have more in the post show.
+[2438.36 --> 2440.30]  If you are a member, you get a little extra show.
+[2440.30 --> 2444.24]  You can go to self-hosted.show slash SRE if you'd like to become one.
+[2444.64 --> 2449.24]  Not only do you support the show, but you do get a limited ad feed and that extra content out there.
+[2449.86 --> 2452.36]  As always, you can go to self-hosted.show slash contact.
+[2452.66 --> 2454.34]  That's the place to go to get in touch with us.
+[2454.44 --> 2456.54]  And you can find me on Twitter at Ironic Badger.
+[2456.94 --> 2458.60]  I'm there too at Chris LAS.
+[2458.68 --> 2460.70]  And the show is at self-hosted show.
+[2461.06 --> 2462.88]  Don't forget the network at Jupiter Signal.
+[2463.14 --> 2465.74]  And that was self-hosted.show slash 38.

39： We run Arch BTW _summary.txt

@@ -0,0 +1,76 @@
+• Discussion of Arch Linux as a favorite distribution
+• Benefits of using Arch, including ease of software deployment and minimal system requirements
+• Comparison to other distributions, such as Ubuntu and Debian
+• Mention of the AUR (Arch User Repository) as a key feature of Arch
+• Personal experience with Arch and its documentation, credited with helping the user transition to Linux in 2013-2014
+• Discussion of Systemd, Docker, and their role in making Linux accessible to new users
+• The speaker's operating system is continuously updated in a minor way to avoid major upgrades
+• They prefer Arch Linux for its flexibility and ability to get updates quickly, but dislike package management systems like AUR
+• Arch makes a great minimum viable server due to its minimalism and small attack surface
+• Ubuntu is settling as the industry standard in the cloud, making it a safer choice for servers
+• The speaker sticks with Ubuntu LTS for cloud deployment due to its stability and Canonical's testing efforts
+• Using Ubuntu LTS on Raspberry Pis for minimal updates
+• Running Arch Linux on local physical hardware at the studio
+• Challenges with running Arch in the cloud due to vendor limitations
+• Importance of not mocking people's choice of distribution, and including others in the conversation
+• Linode.com as a platform that supports various distributions, including Arch, Alpine, Debian, CentOS, SUSE, Ubuntu, and Fedora
+• Native SSD storage and 40 gigabit connections in machines
+• Company's experience and locations, allowing leverage of expertise and relationships
+• Data centers around the world
+• James' experience with SMTP relay issues at previous VPS provider
+• Linode support and policy on blocking SMTP-related ports by default
+• Comparison to original provider's lack of helpful response to James' issue
+• Importance of good support for infrastructure setup
+• LastPass free tier limitations
+• Comparison of LastPass and Bitwarden pricing
+• Self-hosted Bitwarden server options
+• Alternative to self-hosting: Bitwarden RS project
+• Security considerations for hosting a password manager on a shared cloud VPS
+• Blast radius of bots or web servers
+• Running password manager on LAN for local data storage
+• Configuring secure access to self-hosted backend
+• Balancing security concerns vs convenience of hosted service
+• Trusting organization like Bitwarden to handle sensitive data
+• Concerns about security responsibilities and potential risks
+• The speaker considers the cost of Bitwarden's subscription plan, finding it reasonable.
+• They weigh the benefits of using a password manager with a sustainable business model.
+• Mobile access and hosting concerns are mentioned as important considerations for the speaker.
+• The speaker compares Bitwarden to LastPass and notes that team plans are available at $3 per user.
+• Bitwarden self-hosting and Docker image
+• Sharing passwords with others through Bitwarden organizations
+• Comparison of Bitwarden to other password management solutions like KeePass
+• Discussion of Plex media server security issues and a recent botnet attack
+• DDoS attacks and amplification by misconfigured Plex servers
+• Discussion of a vulnerability in Plex that allows remote access through a common port
+• Steps to mitigate the risk, including closing the vulnerable port and setting up a custom server URL and DNS entry with Cloudflare
+• Importance of using a reverse proxy or similar setup to protect against abuse
+• Mention of a study by Netscout finding 27,000 servers vulnerable to this issue
+• Discussion of unrelated issue with WireGuard VPN, involving a misconfigured DHCP subnet and resulting routing issues
+• User describes the benefits of separating subnets for different VPN endpoints
+• User explains their own experience with subnetting and networking issues
+• A listener helps user troubleshoot an issue, teaching them new concepts about networking and triage
+• Promotion for 20% off annual plans at CloudGuru.com mentioned
+• Discussion of growing demand for cloud professionals and benefits of cloud certification
+• Listener "Ryan" asks about running a Linux server with IGPU pass-through to a Windows VM for Blue Iris, while still using the IGPU for containerized applications like Plex.
+• The user discusses using Graphics Virtualization Technology (GVT-G) for virtualized GPU acceleration
+• GVT-G is compared to Intel QuickSync, with the former being significantly slower and less stable
+• The user performs a test on an iPad using Plex for offline playback, comparing CPU rendering vs. GVT-G acceleration
+• Results show that GVT-G is 80-82% slower than running QuickSync natively on the host machine
+• Stability issues are also reported, with system crashes, kernel panics, and processes hanging during use
+• The user concludes that GVT-G is not a viable option due to its poor performance and stability problems
+• Discussion of encoding options and performance per watt
+• Comparison of Intel QuickSync to NVIDIA GPU performance
+• Decision to split tasks into physical boxes for better power management
+• Overview of hardware used for server and Blue Iris setup (HP290 Slim, i5 CPUs)
+• Details on blog setup using Ghost and mkdocs
+• User account management discussion, including centralized authentication options
+• Discussion of Active Directory support on Linux distributions
+• Use of standardized accounts and SSH keys for authentication
+• Potential use of Systemd HomeD for centralized user management
+• Consideration of central authentication systems and single sign-on
+• Personal experience with managing large LDAP installations
+• Current approach to security practices, including infrequent password rotation
+• Upcoming post-show 3D printing discussion
+• Reminder to visit selfhosted.show for show content and contact information
+• Hosts' social media presence (Twitter, Discord)
+• Show hashtag (#selfhostedshow) or ID mentioned (selfhosted.show.com/39)

39： We run Arch BTW _transcript.txt

@@ -0,0 +1,1336 @@
+[0.00 --> 3.52]  Coming up on today's show, we cover our favourite LastPass alternative,
+[4.14 --> 7.50]  we talk about why more boxes might be better than one,
+[7.72 --> 10.98]  and we confess our undying love for Arch.
+[11.86 --> 12.46]  I'm Alex.
+[12.76 --> 15.28]  And I'm Chris, and this is Self-Hosted 39.
+[30.00 --> 45.44]  I, too, I, too, Alex, have been worshipping at the altar of Arch recently.
+[45.58 --> 47.84]  After experimenting with various different distributions,
+[48.52 --> 50.80]  I like that I can set up a minimal system,
+[50.80 --> 56.46]  and I actually have been enjoying using Arch as my base application server.
+[56.84 --> 58.42]  I don't run apps directly on Arch,
+[58.42 --> 61.96]  but in containers or VMs, I find it to be a fantastic platform.
+[62.06 --> 63.04]  I've been doing it for a while now.
+[63.64 --> 66.16]  This comes hot off the heels of this week's Linux Unplugged,
+[66.24 --> 70.40]  where I think it's fair to say you got in your soapbox and preached the Arch gospel.
+[70.74 --> 71.70]  I don't know.
+[71.94 --> 75.22]  I think what I got in my soapbox about was
+[75.22 --> 77.96]  it's become kind of a joke or a meme,
+[77.96 --> 82.26]  oh, Arch users, people are just trying to flex and talk about how elite they are,
+[82.76 --> 85.14]  when the reality is that's not it at all.
+[85.14 --> 89.42]  I simply just want something that makes it really quick to get software deployed or up and running,
+[89.54 --> 92.96]  and maybe have the most minimal Linux install before I run an application.
+[93.14 --> 96.96]  And I find it great for that, without sort of all of the upfront work
+[96.96 --> 99.62]  that something like Gen 2 or Linux from scratch takes.
+[100.08 --> 100.88]  Hey, bro, bro, bro.
+[101.50 --> 102.52]  I run Arch, by the way.
+[103.02 --> 103.40]  Yeah.
+[103.74 --> 105.16]  Well, that's kind of how it started.
+[105.60 --> 109.18]  And then it became, it kind of grew from there, didn't it?
+[109.32 --> 109.72]  It did.
+[109.72 --> 111.50]  Yeah, I definitely feel the shame.
+[111.50 --> 114.22]  Like, when you say to people, I run Arch,
+[114.32 --> 118.34]  it's not because you want to flex, or at least I don't want to flex.
+[118.76 --> 121.74]  It's because I just love it so gosh darn much,
+[121.74 --> 124.78]  and I think other people would too if they just gave it a chance.
+[125.14 --> 126.04]  Well, why is that?
+[126.08 --> 128.36]  I think we should talk about, maybe just really briefly,
+[128.52 --> 129.88]  why it is you love it so much.
+[129.90 --> 132.02]  Because it's not the forms, right?
+[132.04 --> 134.94]  It's not the Arch user base, necessarily.
+[135.14 --> 136.96]  It's the practicality of it, right?
+[137.38 --> 137.78]  It is.
+[137.78 --> 142.88]  I am one command away from pretty much any piece of software that I want.
+[143.72 --> 146.28]  Yay-S, everything, literally.
+[147.16 --> 150.44]  You know, the AUR is Arch's secret sauce.
+[151.08 --> 151.98]  Think of anything.
+[152.14 --> 153.06]  Think of a custom kernel.
+[153.36 --> 156.86]  You know, VFIO stuff is pretty complex to get into.
+[157.46 --> 159.46]  There is a custom kernel already compiled,
+[159.68 --> 163.16]  or there's a package build to compile a custom kernel already there for you,
+[163.18 --> 163.66]  ready to go.
+[164.36 --> 167.00]  You want some esoteric piece of software that,
+[167.00 --> 168.96]  on Ubuntu would be a PPA,
+[169.30 --> 171.26]  or on Fedora would be a copper repo.
+[171.78 --> 173.32]  I don't have to worry about any of that.
+[173.38 --> 175.28]  It's just yay-s install,
+[175.56 --> 176.56]  and off you go.
+[177.54 --> 180.34]  And besides that, you know, as a new user,
+[180.46 --> 183.06]  when I was getting into Linux in 2013,
+[183.38 --> 184.64]  14 sort of time period,
+[185.46 --> 186.38]  the Arch documentation
+[186.38 --> 189.48]  is just the best around,
+[189.48 --> 191.82]  and it's crowdsourced.
+[192.02 --> 193.98]  It's not always completely accurate
+[193.98 --> 195.80]  and always completely totally up to date,
+[195.86 --> 196.82]  but it's good enough
+[196.82 --> 200.24]  that even an idiot like me can pick it up
+[200.24 --> 200.96]  and get going
+[200.96 --> 202.94]  when I knew basically nothing.
+[203.60 --> 204.36]  And at that point,
+[204.40 --> 206.50]  that was when Arch had just transitioned to Systemd.
+[206.50 --> 210.52]  So I kind of credit Arch and Systemd and Docker
+[210.52 --> 212.44]  as being the three kind of pillars
+[212.44 --> 213.84]  of what got me into Linux
+[213.84 --> 216.82]  and being able to get me over that initial new user
+[216.82 --> 218.58]  not knowing what I'm doing hump.
+[218.84 --> 220.26]  Those three things together,
+[220.46 --> 223.24]  for me, were just game-changing.
+[223.84 --> 225.22]  There really is a Linux for every type.
+[225.34 --> 227.02]  Obviously, there's benefits
+[227.02 --> 228.54]  to running something like Debian
+[228.54 --> 232.46]  or CentOS or Ubuntu LTS on a server
+[232.46 --> 234.40]  that make just a ton of sense for most people.
+[234.92 --> 235.94]  I'm the type of user,
+[236.04 --> 238.16]  I don't mind logging in at least once a week,
+[238.78 --> 240.02]  doing a package update
+[240.02 --> 242.90]  and seeing what needs to be installed.
+[243.38 --> 245.62]  I don't always have time for that.
+[245.62 --> 247.68]  I don't always get to do it weekly,
+[247.86 --> 249.38]  but I generally am able to do it
+[249.38 --> 250.46]  at least once a month,
+[250.50 --> 251.40]  if not twice a month.
+[251.40 --> 254.00]  And that seems to be all it's taken for me
+[254.00 --> 255.60]  to keep these systems up and running.
+[255.66 --> 256.78]  And the benefit that I get
+[256.78 --> 258.52]  from a self-hosting standpoint
+[258.52 --> 261.72]  is my operating system is continuously updated.
+[261.84 --> 264.08]  I don't have this event
+[264.08 --> 265.80]  that comes up every few years
+[265.80 --> 267.80]  where I kind of brace myself
+[267.80 --> 270.42]  and do this massive upgrade.
+[271.10 --> 272.54]  Instead, I take my medicine
+[272.54 --> 274.10]  kind of on a weekly basis
+[274.10 --> 276.78]  and it kind of stretches out the changes
+[276.78 --> 278.00]  so that they're just more minor.
+[278.12 --> 278.70]  They're more frequent,
+[278.86 --> 280.06]  but they're more minor.
+[280.06 --> 281.44]  I prefer that.
+[281.44 --> 282.64]  And then when you add something
+[282.64 --> 283.36]  like Alex was saying,
+[283.46 --> 283.94]  the AUR,
+[284.32 --> 286.42]  with the package management system,
+[286.60 --> 289.40]  I can get something up and running
+[289.40 --> 291.68]  in moments on Arch
+[291.68 --> 294.38]  that would take a bit of fiddling around,
+[294.48 --> 295.44]  maybe adding a package repository,
+[296.36 --> 298.14]  following a guide to add the keys
+[298.14 --> 299.24]  and all that kind of stuff
+[299.24 --> 300.50]  to a machine.
+[300.62 --> 302.08]  And then I have the joy
+[302.08 --> 303.76]  of watching that repo go by
+[303.76 --> 305.30]  every time I do an apt update
+[305.30 --> 306.38]  or a DNF update.
+[306.50 --> 308.44]  And I'm not a huge fan of that system.
+[308.44 --> 308.90]  It works.
+[309.54 --> 310.78]  And for some people,
+[310.82 --> 311.46]  it works really well.
+[311.60 --> 312.82]  For me, I just like to have it
+[312.82 --> 314.66]  all integrated with a single package manager,
+[315.22 --> 316.80]  single set of updates that I do.
+[317.08 --> 319.60]  And it's always guaranteed to be
+[319.60 --> 320.94]  at least close to guaranteed,
+[321.06 --> 321.62]  I should say,
+[321.88 --> 322.74]  the latest version
+[322.74 --> 323.62]  when I install something.
+[323.82 --> 325.18]  So I know the security stuff's
+[325.18 --> 325.68]  taken care of,
+[325.72 --> 326.36]  the feature stuff
+[326.36 --> 327.36]  that I've been reading about online,
+[327.40 --> 328.58]  I know it's already landed.
+[329.12 --> 330.86]  And then anything that's more complex
+[330.86 --> 332.78]  than a basic system level tool,
+[333.02 --> 335.44]  I'm already loading in a container anyways.
+[335.44 --> 337.68]  Anyways, and those are often based on Alpine
+[337.68 --> 338.98]  or Ubuntu, et cetera.
+[339.12 --> 340.56]  And it kind of doesn't really matter
+[340.56 --> 341.72]  what the host OS is running
+[341.72 --> 343.30]  as long as it's secure and up to date.
+[343.64 --> 345.88]  I kind of view Arch a little bit like
+[345.88 --> 347.42]  stock Android.
+[347.96 --> 349.86]  You know, like on a Pixel phone
+[349.86 --> 351.48]  or, well, not OnePlus anymore,
+[351.76 --> 353.10]  but definitely on the Pixel phones.
+[353.28 --> 355.10]  Like, it has no opinion.
+[355.42 --> 356.68]  There's no opinionation really
+[356.68 --> 357.54]  in how it does stuff.
+[357.60 --> 358.62]  It just gives you stuff
+[358.62 --> 360.08]  and lets you figure it out by yourself.
+[360.72 --> 361.86]  And for that reason,
+[361.98 --> 363.58]  it makes a really great
+[363.58 --> 364.66]  minimum viable server.
+[365.38 --> 366.32]  It also makes
+[366.32 --> 367.94]  a really great workstation.
+[368.36 --> 370.70]  It could make a great cloud box
+[370.70 --> 371.82]  because you can only install
+[371.82 --> 373.48]  very, very minimal numbers of packages.
+[373.74 --> 375.08]  So from a security perspective,
+[375.72 --> 377.40]  there's a smaller attack surface.
+[378.16 --> 380.44]  The downside is that the industry,
+[380.64 --> 382.40]  and I use air quotes around industry,
+[383.32 --> 384.20]  in the cloud at least,
+[384.36 --> 386.52]  does seem to be settling on Ubuntu.
+[386.52 --> 387.84]  Like if you look at market share
+[387.84 --> 388.68]  and stuff like that.
+[389.20 --> 391.00]  So you are kind of
+[391.00 --> 393.20]  trailblazing your own path
+[393.20 --> 394.28]  by going with Arch.
+[394.48 --> 397.06]  But I would argue that
+[397.06 --> 398.22]  what distro you run
+[398.22 --> 399.56]  doesn't really matter
+[399.56 --> 400.38]  that much anymore.
+[400.74 --> 402.36]  I mean, I do feel pretty strongly
+[402.36 --> 403.02]  that, you know,
+[403.06 --> 404.50]  all my systems will just run Arch.
+[405.28 --> 406.38]  You know, if it's a laptop
+[406.38 --> 407.30]  or a desktop or whatever.
+[407.46 --> 408.22]  But if it's a server,
+[408.94 --> 410.32]  I'll probably put Ubuntu on it.
+[410.88 --> 412.22]  Even though everything
+[412.22 --> 412.98]  we've just said,
+[413.10 --> 416.08]  because it has canonical behind it
+[416.08 --> 417.12]  doing a bunch of testing,
+[417.58 --> 418.80]  especially when it comes to ZFS
+[418.80 --> 420.08]  and the licensing there.
+[420.34 --> 421.20]  That's a tricky one,
+[421.20 --> 421.96]  even on Arch.
+[422.48 --> 423.44]  Just a bunch of stuff,
+[423.52 --> 424.04]  a bunch of testing
+[424.04 --> 425.04]  and things like that
+[425.04 --> 427.04]  mean that I don't run Arch
+[427.04 --> 428.16]  absolutely everywhere,
+[428.68 --> 429.60]  just most places.
+[430.08 --> 431.28]  I have found that for the cloud,
+[431.40 --> 433.06]  I'm sticking with Ubuntu LTS
+[433.06 --> 434.12]  for the most part.
+[434.32 --> 435.54]  I find that works really well.
+[435.88 --> 437.06]  And for my Raspberry Pis
+[437.06 --> 438.66]  that are at the RV
+[438.66 --> 440.44]  on an LTE connection,
+[440.84 --> 442.98]  I'm also running Ubuntu LTS there
+[442.98 --> 444.48]  in part because they've done
+[444.48 --> 445.56]  a really good job
+[445.56 --> 447.48]  with their Pi support.
+[447.48 --> 450.16]  But also, less updates
+[450.16 --> 451.74]  is a feature when you're on cellular.
+[452.26 --> 452.66]  Yeah.
+[453.02 --> 454.34]  And I'm already updating
+[454.34 --> 455.70]  my laptop enough as it is.
+[456.18 --> 457.72]  So there's those elements of it.
+[457.86 --> 459.24]  But when I have an opportunity
+[459.24 --> 460.58]  to run local physical hardware,
+[460.66 --> 461.72]  like I do here at the studio,
+[461.80 --> 462.38]  it's all Arch.
+[462.80 --> 463.80]  It works fantastic.
+[464.24 --> 465.72]  I do have one Arch box
+[465.72 --> 466.56]  up in the cloud
+[466.56 --> 468.22]  that is like an example
+[468.22 --> 469.72]  of Arch in the cloud gone wrong,
+[469.86 --> 473.02]  where the vendor tried to pin
+[473.02 --> 474.72]  to a certain version of the kernel.
+[474.82 --> 475.14]  And of course,
+[475.16 --> 475.76]  that just doesn't work
+[475.76 --> 476.44]  very well with Arch.
+[476.86 --> 478.14]  So I think it is a little trickier
+[478.14 --> 478.54]  in the cloud.
+[478.60 --> 479.84]  And it's not a 100% solution.
+[480.42 --> 481.86]  And what I was just advocating
+[481.86 --> 482.92]  now, I guess, here
+[482.92 --> 483.66]  and in that episode
+[483.66 --> 484.68]  of Linux Unplugged
+[484.68 --> 487.90]  is let's not mock people
+[487.90 --> 489.06]  for their choice of distribution.
+[489.24 --> 489.96]  There's functionality
+[489.96 --> 491.34]  behind everything
+[491.34 --> 493.38]  and like perfectly good reasons
+[493.38 --> 494.44]  to run SUSE as well.
+[494.96 --> 496.54]  My buddy on Coda Radio, Mike,
+[496.92 --> 498.30]  that's what he prefers to run.
+[498.40 --> 499.86]  He likes SUSE in the enterprise.
+[500.08 --> 501.70]  He runs Pop! OS on his desktop
+[501.70 --> 503.42]  and SUSE in the rack.
+[503.60 --> 504.96]  And that works really well for him.
+[505.40 --> 506.46]  It's not like we're trying
+[506.46 --> 507.38]  to create a
+[507.38 --> 509.08]  this distribution is better debate.
+[509.36 --> 510.46]  What we're trying to say is
+[510.46 --> 511.84]  let's include everybody
+[511.84 --> 512.72]  in the conversation
+[512.72 --> 513.76]  and not mock people
+[513.76 --> 515.58]  for their choice of distribution.
+[516.00 --> 517.26]  And as a couple
+[517.26 --> 518.28]  of counter-narrative guys,
+[518.36 --> 519.74]  I guess we happen to find Arch
+[519.74 --> 520.70]  actually works pretty well
+[520.70 --> 521.88]  if you're willing to maintain it.
+[523.62 --> 525.94]  Linode.com slash SSH.
+[526.04 --> 527.14]  Go there to get a $100
+[527.14 --> 528.14]  60-day credit
+[528.14 --> 528.88]  towards a new account.
+[529.00 --> 530.86]  Yeah, $100 in credit
+[530.86 --> 531.38]  to play with.
+[531.72 --> 532.12]  And of course,
+[532.12 --> 533.08]  you're supporting the show
+[533.08 --> 535.50]  by going to linode.com slash SSH.
+[535.70 --> 536.70]  That's where we set up
+[536.70 --> 537.58]  all of our infrastructure
+[537.58 --> 538.68]  for JB 3.0.
+[538.80 --> 539.62]  If we're playing around
+[539.62 --> 541.22]  for something like SSH,
+[541.30 --> 542.52]  like segment work or something,
+[542.94 --> 544.54]  yeah, we do that up on Linode.
+[544.64 --> 545.84]  And speaking of Arch,
+[545.88 --> 546.74]  one of the great things
+[546.74 --> 547.46]  about Linode
+[547.46 --> 548.48]  is they let you pick
+[548.48 --> 549.40]  just about any distribution
+[549.40 --> 549.92]  you want.
+[549.98 --> 550.56]  They have Arch.
+[550.94 --> 551.52]  They got, I mean,
+[551.52 --> 552.04]  they got everything.
+[552.16 --> 553.18]  Alpine, Debian,
+[554.08 --> 554.86]  CentOS, SUSE,
+[555.30 --> 556.18]  Ubuntu's, of course.
+[556.46 --> 557.08]  I mean, they got like
+[557.08 --> 558.06]  everything up there.
+[558.44 --> 559.52]  Even some Fedora
+[559.52 --> 561.02]  for you crazy kids out there.
+[561.14 --> 562.58]  You can run it up on Linode.
+[562.66 --> 563.66]  They've been in this game
+[563.66 --> 564.70]  since 2003.
+[564.88 --> 566.32]  They've learned what works
+[566.32 --> 567.40]  and they've learned
+[567.40 --> 568.34]  what doesn't work.
+[568.38 --> 569.40]  And they were doing that
+[569.40 --> 571.10]  years before everybody else.
+[571.26 --> 572.58]  And they've really managed
+[572.58 --> 573.44]  to modernize it
+[573.44 --> 575.30]  with a beautiful cloud dashboard
+[575.30 --> 576.22]  that makes it approachable
+[576.22 --> 576.60]  to somebody
+[576.60 --> 577.88]  who's brand new to servers
+[577.88 --> 579.56]  or maybe you're like
+[579.56 --> 580.28]  a longtime pro.
+[580.68 --> 581.22]  You're going to love
+[581.22 --> 582.40]  the way this dashboard works.
+[582.52 --> 582.76]  Of course,
+[582.80 --> 584.44]  they have native SSD storage,
+[584.54 --> 585.48]  40 gigabit connections
+[585.48 --> 586.56]  coming into the machines.
+[586.96 --> 588.30]  It's all super fast.
+[588.56 --> 589.38]  And because they've been around
+[589.38 --> 590.34]  since 2003,
+[590.52 --> 592.46]  they've got some great locations.
+[592.62 --> 593.72]  Like, think about that, right?
+[593.74 --> 594.50]  They can leverage
+[594.50 --> 595.28]  their experience,
+[595.40 --> 596.08]  their relationships
+[596.08 --> 597.94]  in a way that nobody else can
+[597.94 --> 598.82]  because they've been
+[598.82 --> 599.62]  in cloud computing
+[599.62 --> 600.94]  before it was cloud computing.
+[601.20 --> 602.10]  11 data centers
+[602.10 --> 602.88]  around the world.
+[603.12 --> 603.76]  We got an email
+[603.76 --> 604.88]  into the show from James.
+[605.76 --> 606.10]  He said,
+[606.16 --> 606.92]  I wanted to set up
+[606.92 --> 608.56]  an SMTP relay
+[608.56 --> 610.08]  at my previous
+[610.08 --> 611.70]  VPS provider,
+[612.30 --> 614.20]  but because they were
+[614.20 --> 615.28]  kind of, you know,
+[615.48 --> 617.00]  trying to be competitive
+[617.00 --> 617.58]  in the market,
+[617.72 --> 618.78]  they ended up
+[618.78 --> 619.66]  with not the best
+[619.66 --> 620.66]  IP reputation
+[620.66 --> 621.76]  and they ended up
+[621.76 --> 622.28]  getting blocked
+[622.28 --> 622.92]  by Microsoft.
+[623.20 --> 624.10]  And so then he spun up
+[624.10 --> 625.60]  another box on their system
+[625.60 --> 626.68]  and that also got blocked
+[626.68 --> 627.42]  by Microsoft.
+[629.12 --> 629.62]  He's like,
+[629.64 --> 630.54]  I couldn't even find them
+[630.54 --> 631.58]  on any public blacklist.
+[631.64 --> 632.88]  Yet Microsoft just started
+[632.88 --> 634.78]  blacklisting all of these IPs.
+[634.78 --> 635.70]  So I decided I'd go over
+[635.70 --> 636.24]  to Linode
+[636.24 --> 638.44]  and try a Linode over there
+[638.44 --> 639.14]  and support the show.
+[639.22 --> 639.88]  So he goes to
+[639.88 --> 641.56]  linode.com slash SSH.
+[641.70 --> 642.94]  He spins up a system
+[642.94 --> 643.34]  on Linode
+[643.34 --> 643.86]  and he discovers,
+[644.06 --> 644.34]  oh,
+[644.34 --> 646.44]  Linode has a policy
+[646.44 --> 647.16]  where they block
+[647.16 --> 648.66]  all SMTP related ports
+[648.66 --> 649.32]  by default.
+[649.46 --> 650.06]  Oh, well,
+[650.36 --> 651.20]  I guess I'll email support
+[651.20 --> 652.14]  and see what they say.
+[652.28 --> 652.92]  So he sends off
+[652.92 --> 653.88]  a quick email to support.
+[654.06 --> 655.48]  He gets a prompt response
+[655.48 --> 656.06]  later
+[656.06 --> 657.66]  and they open up the ports
+[657.66 --> 658.52]  and everything
+[658.52 --> 659.80]  is working perfectly.
+[660.42 --> 660.86]  He goes,
+[661.44 --> 663.04]  then a few days later,
+[663.04 --> 664.18]  I finally got a response
+[664.18 --> 665.38]  from my original provider
+[665.38 --> 666.54]  with some canned email
+[666.54 --> 667.52]  that didn't help it at all.
+[667.58 --> 668.38]  I reply to that.
+[668.58 --> 670.46]  I got another canned email response
+[670.46 --> 671.44]  and that was it.
+[671.44 --> 672.24]  I just gave up
+[672.24 --> 673.32]  and I'm moving everything
+[673.32 --> 674.18]  over to Linode.
+[674.44 --> 676.14]  They're genuinely just great
+[676.14 --> 678.34]  and I've gotten so many notes
+[678.34 --> 678.68]  into the show
+[678.68 --> 679.80]  that talk about Linode support.
+[679.96 --> 680.50]  It's not an aspect
+[680.50 --> 681.32]  I touch on a lot
+[681.32 --> 682.32]  but it really matters
+[682.32 --> 683.24]  once you get up and running,
+[683.38 --> 684.72]  especially if you've got
+[684.72 --> 685.66]  some important infrastructure
+[685.66 --> 686.08]  on there.
+[686.34 --> 686.98]  So go check them out.
+[687.08 --> 689.16]  Linode.com slash SSH.
+[689.16 --> 692.22]  Now I know you covered
+[692.22 --> 693.58]  some stuff about LastPass
+[693.58 --> 695.24]  in Linux Unplugged.
+[695.28 --> 697.60]  This is like Linux Unplugged Plus
+[697.60 --> 698.58]  this episode, isn't it?
+[699.68 --> 701.60]  But LastPass have been doing
+[701.60 --> 702.52]  some shenanigans
+[702.52 --> 704.28]  with their free tiers and stuff.
+[704.40 --> 705.76]  I think we've all been expecting this
+[705.76 --> 706.80]  for quite a long time
+[706.80 --> 709.16]  since they were acquired.
+[709.82 --> 711.46]  Now they are limiting
+[711.46 --> 713.84]  the access
+[713.84 --> 715.90]  to unlimited devices
+[715.90 --> 716.86]  of one type.
+[717.36 --> 718.72]  So to clarify what that means
+[718.72 --> 720.26]  is you can access
+[720.26 --> 721.36]  LastPass free
+[721.36 --> 723.30]  on an unlimited number
+[723.30 --> 723.98]  of computers
+[723.98 --> 725.74]  or an unlimited number
+[725.74 --> 727.00]  of mobile devices
+[727.00 --> 728.20]  but not both
+[728.20 --> 729.14]  on their free tier.
+[729.86 --> 730.72]  I say enough.
+[731.04 --> 732.14]  I say that stinks.
+[732.44 --> 733.50]  And we have a recommendation
+[733.50 --> 734.14]  for you.
+[734.64 --> 735.00]  I agree.
+[735.20 --> 736.12]  I mean the price right now
+[736.12 --> 737.06]  is kind of reasonable.
+[737.30 --> 738.04]  It's like what?
+[738.20 --> 739.04]  Four bucks a year
+[739.04 --> 739.60]  or something?
+[740.16 --> 741.16]  It's not outrageous
+[741.16 --> 742.70]  for a year.
+[742.92 --> 743.18]  I mean
+[743.18 --> 744.72]  but it stinks
+[744.72 --> 745.80]  the way it's going about.
+[746.54 --> 747.14]  And I agree.
+[747.38 --> 748.40]  It's time to look
+[748.40 --> 749.04]  at an alternative
+[749.04 --> 749.94]  and this is
+[749.94 --> 751.04]  the self-hosted podcast
+[751.04 --> 752.98]  and I think both of us
+[752.98 --> 754.52]  landed on Bitwarden
+[754.52 --> 755.38]  pretty quickly.
+[755.96 --> 757.36]  I have some trepidation
+[757.36 --> 757.82]  here though.
+[757.82 --> 758.52]  Hold on a minute.
+[758.64 --> 759.50]  I think LastPass
+[759.50 --> 761.08]  is $27 a year.
+[761.74 --> 763.76]  It's $2.25 a month
+[763.76 --> 764.54]  billed annually.
+[765.46 --> 766.38]  Oh you're kidding me.
+[766.72 --> 766.86]  Yeah.
+[767.08 --> 767.88]  Oh jeez.
+[767.98 --> 768.18]  Okay.
+[769.20 --> 771.02]  Ah yeah you're right.
+[771.12 --> 771.46]  So that's
+[771.46 --> 772.36]  that's not nearly
+[772.36 --> 773.34]  the deal I thought it was.
+[773.40 --> 774.06]  That's a bad deal.
+[774.06 --> 775.84]  Especially when
+[775.84 --> 776.94]  Bitwarden is only
+[776.94 --> 778.28]  $10 a year.
+[778.52 --> 779.06]  That's if you
+[779.06 --> 780.38]  buy an annual plan.
+[781.08 --> 781.90]  But if you don't
+[781.90 --> 783.00]  even want to do that
+[783.00 --> 784.86]  you can self-host
+[784.86 --> 785.98]  the Bitwarden
+[785.98 --> 786.76]  server
+[786.76 --> 787.78]  which is just
+[787.78 --> 788.96]  so cool.
+[789.38 --> 789.56]  Yeah.
+[789.70 --> 791.20]  I really love seeing this
+[791.20 --> 791.72]  and
+[791.72 --> 793.08]  I know it's a little
+[793.08 --> 793.94]  complicated.
+[794.22 --> 795.12]  I think it requires
+[795.12 --> 795.60]  SQL
+[795.60 --> 796.98]  among other things.
+[797.14 --> 798.10]  So the community
+[798.10 --> 798.68]  has come up
+[798.68 --> 799.46]  with an alternative.
+[799.46 --> 800.58]  Yeah there's a project
+[800.58 --> 801.94]  called Bitwarden RS
+[801.94 --> 803.42]  which is written in Rust.
+[804.42 --> 805.10]  Where's Wes
+[805.10 --> 805.68]  when you need him?
+[806.98 --> 808.44]  And this is a
+[808.44 --> 810.50]  Bitwarden server
+[810.50 --> 811.04]  that can run
+[811.04 --> 811.66]  in a container
+[811.66 --> 813.16]  that will essentially
+[813.16 --> 815.06]  perform the same role
+[815.06 --> 816.34]  as the $10 a year
+[816.34 --> 817.80]  hosted service.
+[818.04 --> 818.94]  The difference being
+[818.94 --> 819.62]  is you own
+[819.62 --> 820.26]  all the data
+[820.26 --> 821.48]  it remains
+[821.48 --> 822.40]  on your servers
+[822.40 --> 823.18]  or your VPS
+[823.18 --> 823.60]  or whatever.
+[824.18 --> 824.74]  So there's a couple
+[824.74 --> 825.32]  of ways you could
+[825.32 --> 826.14]  go about doing this.
+[826.38 --> 827.38]  The first and most
+[827.38 --> 828.28]  obvious way is to
+[828.28 --> 829.04]  spin up a Linode
+[829.04 --> 829.96]  or something like that
+[829.96 --> 831.14]  and throw Bitwarden
+[831.14 --> 831.58]  on there
+[831.58 --> 833.58]  and just call it good.
+[833.84 --> 834.54]  And because it's
+[834.54 --> 835.58]  your password manager
+[835.58 --> 836.42]  I would probably
+[836.42 --> 837.82]  caution against
+[837.82 --> 839.14]  running this
+[839.14 --> 840.16]  on a shared
+[840.16 --> 841.36]  cloud VPS.
+[841.56 --> 842.18]  You know if you're
+[842.18 --> 843.34]  hosting a ton of websites
+[843.34 --> 844.98]  and it's a very
+[844.98 --> 845.50]  public
+[845.50 --> 846.96]  you know VPS
+[846.96 --> 848.02]  I probably wouldn't
+[848.02 --> 848.96]  put your password manager
+[848.96 --> 850.08]  on that same system.
+[850.36 --> 851.04]  I would put it
+[851.04 --> 852.14]  on a separate system
+[852.14 --> 853.28]  just so you're
+[853.28 --> 854.20]  reducing the blast
+[854.20 --> 855.32]  radius of any bots
+[855.32 --> 855.74]  or anything
+[855.74 --> 856.68]  doing something crazy
+[856.68 --> 857.92]  with the web servers.
+[857.92 --> 859.36]  The other thing
+[859.36 --> 860.00]  you can do
+[860.00 --> 860.98]  is run it
+[860.98 --> 861.90]  on your LAN
+[861.90 --> 862.48]  and I think
+[862.48 --> 863.58]  the running
+[863.58 --> 864.18]  it on a separate
+[864.18 --> 864.88]  system becomes
+[864.88 --> 865.70]  less important
+[865.70 --> 866.24]  when it's on
+[866.24 --> 867.46]  your network.
+[868.08 --> 868.82]  And the idea
+[868.82 --> 869.80]  of running it
+[869.80 --> 870.58]  on your LAN
+[870.58 --> 871.08]  of course
+[871.08 --> 872.58]  is that your data
+[872.58 --> 873.48]  never leaves
+[873.48 --> 874.36]  your house
+[874.36 --> 875.00]  right?
+[875.18 --> 875.84]  And that will
+[875.84 --> 876.20]  hopefully
+[876.20 --> 877.64]  reduce
+[877.64 --> 878.50]  the risk
+[878.50 --> 879.16]  even further.
+[879.66 --> 880.56]  Now the downside
+[880.56 --> 881.70]  of running your own
+[881.70 --> 882.46]  password manager
+[882.46 --> 882.86]  backend
+[882.86 --> 883.68]  is you've got to
+[883.68 --> 884.54]  configure secure
+[884.54 --> 885.34]  access to it.
+[885.34 --> 886.50]  So that could be
+[886.50 --> 887.46]  using WireGuard
+[887.46 --> 889.10]  or some other
+[889.10 --> 890.08]  kind of authentication
+[890.08 --> 890.84]  through SSH
+[890.84 --> 891.70]  or something like that.
+[892.04 --> 892.72]  But ultimately
+[892.72 --> 893.18]  you're going to want
+[893.18 --> 893.92]  to be really careful
+[893.92 --> 894.74]  and really sure
+[894.74 --> 895.28]  you know what you're
+[895.28 --> 896.18]  doing from a security
+[896.18 --> 896.74]  perspective
+[896.74 --> 898.00]  before you start
+[898.00 --> 898.70]  going and storing
+[898.70 --> 899.32]  all your passwords
+[899.32 --> 900.80]  on a public system.
+[901.50 --> 901.82]  That's where you
+[901.82 --> 902.56]  could make the argument
+[902.56 --> 903.36]  that it could just
+[903.36 --> 904.12]  be worth paying
+[904.12 --> 904.82]  for their
+[904.82 --> 906.18]  hosted service.
+[906.92 --> 907.82]  And this is where
+[907.82 --> 908.82]  I'm currently
+[908.82 --> 909.76]  experiencing my
+[909.76 --> 910.32]  trepidation.
+[910.52 --> 912.44]  I 100% know
+[912.44 --> 913.66]  I could self-host it.
+[913.66 --> 914.90]  And the nice thing
+[914.90 --> 915.54]  about this Rust
+[915.54 --> 916.38]  version of their
+[916.38 --> 917.00]  server is
+[917.00 --> 918.32]  really minimal
+[918.32 --> 918.84]  resources.
+[918.84 --> 919.40]  So you could
+[919.40 --> 919.90]  really run it
+[919.90 --> 920.66]  on anything.
+[920.82 --> 921.62]  So I could run
+[921.62 --> 922.56]  it on my Raspberry Pi
+[922.56 --> 923.30]  or I could run it
+[923.30 --> 924.00]  easily here on the
+[924.00 --> 924.70]  server at the studio.
+[925.22 --> 926.84]  But I'm not sure
+[926.84 --> 927.78]  I want to.
+[928.30 --> 928.44]  You know,
+[928.48 --> 928.96]  there's something
+[928.96 --> 930.02]  about the
+[930.02 --> 931.26]  master password
+[931.26 --> 931.70]  vault.
+[932.06 --> 932.80]  It's such a
+[932.80 --> 934.00]  sacred responsibility
+[934.00 --> 936.76]  that I almost
+[936.76 --> 937.40]  trust an
+[937.40 --> 938.18]  organization like
+[938.18 --> 939.58]  Bitwarden to be
+[939.58 --> 940.58]  more focused on
+[940.58 --> 941.12]  securing that
+[941.12 --> 942.10]  platform than I am.
+[942.18 --> 943.28]  Not that I really
+[943.28 --> 944.06]  have no concerns
+[944.06 --> 944.76]  about our security.
+[945.00 --> 945.42]  Really?
+[946.30 --> 946.78]  But there's
+[946.78 --> 947.52]  something that
+[947.52 --> 948.18]  still gives me
+[948.18 --> 948.70]  pause.
+[949.12 --> 949.48]  They've got one
+[949.48 --> 950.28]  job to do.
+[950.42 --> 951.60]  And I've actually
+[951.60 --> 952.50]  paid Bitwarden
+[952.50 --> 953.44]  the $10 a year
+[953.44 --> 954.68]  for two or three,
+[954.82 --> 955.48]  maybe four years
+[955.48 --> 955.94]  at this point.
+[956.38 --> 956.94]  I've been very,
+[957.06 --> 957.44]  very happy.
+[957.64 --> 958.50]  It just does the
+[958.50 --> 958.78]  job.
+[958.94 --> 959.62]  I never have to
+[959.62 --> 960.36]  think about it.
+[960.68 --> 961.06]  All of the
+[961.06 --> 962.10]  autofill stuff on
+[962.10 --> 962.88]  Android and iOS
+[962.88 --> 963.50]  just works
+[963.50 --> 964.58]  fantastically well.
+[965.34 --> 965.58]  You know,
+[965.64 --> 966.88]  $10 is that kind
+[966.88 --> 968.34]  of screw it
+[968.34 --> 969.36]  amount of money
+[969.36 --> 969.92]  when it's spread
+[969.92 --> 970.86]  over an entire year.
+[971.00 --> 971.14]  You know,
+[971.18 --> 971.68]  it's less than a
+[971.68 --> 972.28]  dollar a month.
+[972.28 --> 973.72]  And to just
+[973.72 --> 974.56]  not have to worry
+[974.56 --> 975.20]  about it and to
+[975.20 --> 975.74]  just not have to
+[975.74 --> 976.48]  think about it for
+[976.48 --> 978.00]  what, 80, 90 cents
+[978.00 --> 978.44]  a month,
+[978.88 --> 979.82]  that's worth it for me.
+[980.06 --> 981.22]  It reminds me of
+[981.22 --> 982.20]  why I kind of like
+[982.20 --> 983.74]  supporting Nebukasa
+[983.74 --> 985.14]  and how supporting
+[985.14 --> 986.66]  Nebukasa goes into
+[986.66 --> 987.10]  home assistant
+[987.10 --> 987.62]  development and
+[987.62 --> 988.22]  makes home assistant
+[988.22 --> 988.56]  better.
+[988.88 --> 990.16]  By subscribing to
+[990.16 --> 990.90]  Bitwarden, you're
+[990.90 --> 991.88]  helping them come up
+[991.88 --> 992.40]  with a sustainable
+[992.40 --> 993.38]  business model that
+[993.38 --> 994.36]  encourages them to
+[994.36 --> 995.00]  make the password
+[995.00 --> 996.16]  manager better and
+[996.16 --> 996.92]  keep their service
+[996.92 --> 997.32]  secure.
+[997.32 --> 999.14]  So it incentivizes
+[999.14 --> 1000.14]  the right things
+[1000.14 --> 1001.56]  and on top of that
+[1001.56 --> 1002.02]  it means I don't
+[1002.02 --> 1002.56]  have to host it
+[1002.56 --> 1002.86]  myself.
+[1003.04 --> 1003.56]  I haven't actually
+[1003.56 --> 1004.40]  made my decision
+[1004.40 --> 1006.24]  because I have
+[1006.24 --> 1007.40]  kept a lot of
+[1007.40 --> 1008.38]  business stuff in
+[1008.38 --> 1009.30]  LastPass for a
+[1009.30 --> 1009.52]  while.
+[1009.66 --> 1010.16]  I know I like
+[1010.16 --> 1010.88]  Bitwarden so I've
+[1010.88 --> 1011.46]  always thought that's
+[1011.46 --> 1012.08]  what I would jump
+[1012.08 --> 1012.36]  to.
+[1013.20 --> 1013.74]  And so I went over
+[1013.74 --> 1015.18]  to their subscription
+[1015.18 --> 1016.50]  pricing page and
+[1016.50 --> 1017.26]  they also offer
+[1017.26 --> 1018.80]  team plans for as
+[1018.80 --> 1019.46]  little as like $3
+[1019.46 --> 1020.58]  per user and that's
+[1020.58 --> 1021.74]  still pretty reasonable.
+[1022.54 --> 1023.22]  So I think that might
+[1023.22 --> 1023.96]  be the direction I
+[1023.96 --> 1024.50]  end up going.
+[1024.70 --> 1025.28]  I'm going to research
+[1025.28 --> 1025.96]  more about how
+[1025.96 --> 1026.92]  they host it first
+[1026.92 --> 1029.08]  because I know a
+[1029.08 --> 1030.24]  big use case for me
+[1030.24 --> 1031.52]  a really big use
+[1031.52 --> 1032.06]  case for me is
+[1032.06 --> 1032.82]  mobile access.
+[1033.40 --> 1034.08]  It's such a
+[1034.08 --> 1034.84]  crapshoot with me.
+[1034.96 --> 1035.88]  I don't just connect
+[1035.88 --> 1036.96]  from one machine.
+[1037.20 --> 1038.28]  It's just ridiculous
+[1038.28 --> 1039.00]  especially when you
+[1039.00 --> 1040.04]  bring in like
+[1040.04 --> 1041.38]  traveling or setting
+[1041.38 --> 1042.08]  up family member
+[1042.08 --> 1042.80]  systems or.
+[1043.18 --> 1043.64]  And hosts.
+[1043.98 --> 1044.62]  Yeah it's just
+[1044.62 --> 1045.34]  it's ridiculous.
+[1045.62 --> 1047.56]  So I kind of like
+[1047.56 --> 1048.40]  the idea of something
+[1048.40 --> 1048.94]  where I'm not
+[1048.94 --> 1050.06]  handing out WireGuard
+[1050.06 --> 1051.18]  connections to 15
+[1051.18 --> 1052.02]  different people so
+[1052.02 --> 1052.58]  that way they can
+[1052.58 --> 1053.38]  access the central
+[1053.38 --> 1054.34]  password database.
+[1054.34 --> 1055.80]  And don't forget
+[1055.80 --> 1056.48]  as well generally
+[1056.48 --> 1057.28]  the time when you
+[1057.28 --> 1058.22]  need Bitwarden the
+[1058.22 --> 1059.00]  most is when your
+[1059.00 --> 1060.08]  device is completely
+[1060.08 --> 1061.50]  brand new or empty.
+[1062.16 --> 1062.26]  Right.
+[1062.66 --> 1063.48]  And so you've always
+[1063.48 --> 1064.26]  got that awkward
+[1064.26 --> 1065.30]  first 10 minutes
+[1065.30 --> 1065.88]  where you're getting
+[1065.88 --> 1066.94]  you know your two
+[1066.94 --> 1067.96]  factor auth set up
+[1067.96 --> 1068.86]  again and your
+[1068.86 --> 1069.86]  Bitwarden whatever
+[1069.86 --> 1070.60]  set up again.
+[1071.18 --> 1071.74]  And once you've got
+[1071.74 --> 1072.40]  those two things
+[1072.40 --> 1072.98]  you're good to go
+[1072.98 --> 1074.54]  generally but yeah I
+[1074.54 --> 1075.08]  can see you don't
+[1075.08 --> 1075.50]  want to be handing
+[1075.50 --> 1076.50]  that out to randos.
+[1077.04 --> 1077.50]  If you do want to
+[1077.50 --> 1078.06]  self host it though
+[1078.06 --> 1079.22]  Alex like somebody
+[1079.22 --> 1079.86]  in our audience who
+[1079.86 --> 1080.36]  may have a different
+[1080.36 --> 1081.74]  use case it's easier
+[1081.74 --> 1082.70]  than ever now because
+[1082.70 --> 1083.74]  the Bitwarden
+[1083.74 --> 1084.80]  Rust server has a
+[1084.80 --> 1086.12]  Docker image fully
+[1086.12 --> 1087.64]  up to date as of
+[1087.64 --> 1088.82]  like 19 hours ago as
+[1088.82 --> 1089.50]  we record this.
+[1089.98 --> 1091.16]  It's like the old
+[1091.16 --> 1092.52]  proverb if something
+[1092.52 --> 1093.56]  isn't Dockerized at
+[1093.56 --> 1094.20]  this point does it
+[1094.20 --> 1094.82]  even exist?
+[1095.78 --> 1096.74]  Now another nice
+[1096.74 --> 1097.60]  thing that I do with
+[1097.60 --> 1098.30]  Bitwarden is I
+[1098.30 --> 1098.72]  actually share
+[1098.72 --> 1099.54]  passwords with my
+[1099.54 --> 1099.84]  wife.
+[1100.06 --> 1100.92]  She has a Bitwarden.
+[1101.30 --> 1101.80]  I don't think she
+[1101.80 --> 1102.64]  pays the premium I
+[1102.64 --> 1103.30]  think she just has the
+[1103.30 --> 1104.94]  basic free account but
+[1104.94 --> 1105.64]  we created an
+[1105.64 --> 1107.14]  organization and when
+[1107.14 --> 1107.86]  you create a
+[1107.86 --> 1109.26]  particular login you
+[1109.26 --> 1110.52]  can assign that login
+[1110.52 --> 1111.72]  to an organization and
+[1111.72 --> 1112.52]  share it with that
+[1112.52 --> 1113.14]  organization.
+[1113.92 --> 1114.90]  So certain passwords
+[1114.90 --> 1115.94]  for us like Amazon,
+[1116.44 --> 1117.88]  eBay, you know stuff
+[1117.88 --> 1118.36]  that you want to
+[1118.36 --> 1120.10]  share goes into that
+[1120.10 --> 1122.04]  shared area if you
+[1122.04 --> 1122.64]  like that shared
+[1122.64 --> 1123.52]  organization and we've
+[1123.52 --> 1124.58]  both got access to it.
+[1124.70 --> 1125.38]  I find that really
+[1125.38 --> 1125.74]  useful.
+[1126.24 --> 1126.86]  There's of course other
+[1126.86 --> 1127.72]  solutions out there.
+[1127.84 --> 1128.70]  Another beloved one in
+[1128.70 --> 1129.38]  the audience is
+[1129.38 --> 1130.70]  KeePass and KeePassX
+[1130.70 --> 1132.36]  and there's several
+[1132.36 --> 1134.06]  solutions to this but
+[1134.06 --> 1135.08]  Bitwarden is the one we
+[1135.08 --> 1136.10]  both landed on I think
+[1136.10 --> 1137.60]  in part because of the
+[1137.60 --> 1138.56]  UI, the browser
+[1138.56 --> 1140.24]  integration, the ability
+[1140.24 --> 1142.12]  to self-host and the
+[1142.12 --> 1143.00]  quality of the mobile
+[1143.00 --> 1144.20]  apps all kind of come
+[1144.20 --> 1145.02]  together to make it our
+[1145.02 --> 1145.62]  favorite choice.
+[1146.16 --> 1146.80]  So whilst we're sort of
+[1146.80 --> 1147.86]  kind of on the topic of
+[1147.86 --> 1149.44]  security, why don't we
+[1149.44 --> 1151.70]  discuss the Plex hoopla
+[1151.70 --> 1152.68]  that's been going on as
+[1152.68 --> 1155.42]  well about this botnet
+[1155.42 --> 1156.26]  thing that's been
+[1156.26 --> 1157.70]  amplifying stuff across
+[1157.70 --> 1158.16]  the internet?
+[1158.16 --> 1159.50]  It just stinks because
+[1159.50 --> 1160.86]  you know you got a Plex
+[1160.86 --> 1162.28]  server going, you've
+[1162.28 --> 1163.02]  opened it up to the
+[1163.02 --> 1163.74]  internet so that way you
+[1163.74 --> 1164.40]  can share it.
+[1164.78 --> 1165.94]  Some scanner finds your
+[1165.94 --> 1167.74]  server, indexes it and
+[1167.74 --> 1168.84]  then some botnet author
+[1168.84 --> 1170.88]  figures out a way to
+[1170.88 --> 1171.78]  take advantage of a
+[1171.78 --> 1172.98]  vulnerability in Plex to
+[1172.98 --> 1174.86]  amplify by a factor of
+[1174.86 --> 1177.28]  five their DDoS traffic.
+[1177.50 --> 1179.48]  They kind of corral all of
+[1179.48 --> 1180.36]  these different Plex
+[1180.36 --> 1182.54]  installs together to kind
+[1182.54 --> 1183.90]  of do this amplified
+[1183.90 --> 1185.30]  attack against a single
+[1185.30 --> 1186.64]  source and just happened
+[1186.64 --> 1187.50]  the last week as we're
+[1187.50 --> 1188.20]  recording this.
+[1188.60 --> 1189.90]  NetScout said that there
+[1189.90 --> 1191.02]  was a DDoS for hire
+[1191.02 --> 1192.62]  service that recently
+[1192.62 --> 1194.16]  turned misconfigured Plex
+[1194.16 --> 1195.34]  media servers into
+[1195.34 --> 1196.74]  amplifying attack servers.
+[1196.74 --> 1198.72]  Rut roll.
+[1199.20 --> 1200.26]  Yeah, not only does it
+[1200.26 --> 1201.20]  suck up all of your
+[1201.20 --> 1202.40]  bandwidth and attack
+[1202.40 --> 1203.50]  somebody but it also
+[1203.50 --> 1204.64]  runs your server like
+[1204.64 --> 1205.06]  crazy.
+[1205.38 --> 1206.50]  It's just bad.
+[1206.98 --> 1207.90]  Yeah, what really kind
+[1207.90 --> 1209.30]  of, I don't want to use
+[1209.30 --> 1210.90]  the word scared me, but
+[1210.90 --> 1212.06]  I suppose so, you know,
+[1212.26 --> 1213.38]  gave me cause for a
+[1213.38 --> 1215.80]  concern at least was just
+[1215.80 --> 1218.78]  opening port 32400,
+[1218.96 --> 1222.52]  32400 on TCP, just
+[1222.52 --> 1224.26]  opening that port alone is
+[1224.26 --> 1225.58]  enough to be vulnerable
+[1225.58 --> 1226.30]  because it's such a
+[1226.30 --> 1226.94]  common port.
+[1227.64 --> 1228.68]  People will scan it and
+[1228.68 --> 1229.58]  find it and then be like,
+[1229.64 --> 1230.34]  oh, this guy's running
+[1230.34 --> 1230.74]  Plex.
+[1231.10 --> 1231.24]  Yeah.
+[1231.48 --> 1233.14]  So what I've done since
+[1233.14 --> 1234.38]  this vulnerability to
+[1234.38 --> 1235.62]  kind of remove myself
+[1235.62 --> 1239.06]  from the risk factor is
+[1239.06 --> 1239.96]  I've closed that port in
+[1239.96 --> 1241.10]  my firewall and I have
+[1241.10 --> 1242.74]  started to define a
+[1242.74 --> 1244.66]  custom server URL in my
+[1244.66 --> 1245.68]  Plex server settings.
+[1245.68 --> 1248.04]  And I set a DNS entry in
+[1248.04 --> 1248.56]  Cloudflare.
+[1249.24 --> 1251.00]  That then points to my
+[1251.00 --> 1251.64]  WAN IP.
+[1252.60 --> 1254.20]  From there, that then
+[1254.20 --> 1256.00]  points to a traffic
+[1256.00 --> 1257.12]  instance that's running on
+[1257.12 --> 1257.94]  the same server as
+[1257.94 --> 1258.28]  Plex.
+[1259.00 --> 1260.22]  And from there, it does a
+[1260.22 --> 1261.72]  standard reverse proxy
+[1261.72 --> 1263.54]  thing and just does the
+[1263.54 --> 1265.32]  remote access as if I was
+[1265.32 --> 1267.16]  going through port 32400
+[1267.16 --> 1269.08]  like I was last month.
+[1269.56 --> 1271.78]  Very easy fix and I highly
+[1271.78 --> 1272.76]  recommend you take a look
+[1272.76 --> 1273.16]  into that.
+[1273.16 --> 1274.06]  That's a great idea
+[1274.06 --> 1275.36]  because Netscout said that
+[1275.36 --> 1276.30]  after a scan they
+[1276.30 --> 1277.20]  conducted, they found
+[1277.20 --> 1279.26]  about 27,000 servers on
+[1279.26 --> 1280.06]  the internet that can be
+[1280.06 --> 1281.08]  abused this way.
+[1281.80 --> 1283.16]  So it doesn't mean you
+[1283.16 --> 1284.00]  have to shut off remote
+[1284.00 --> 1286.46]  Plex, but it does mean
+[1286.46 --> 1287.18]  you should probably take
+[1287.18 --> 1287.96]  some steps to protect
+[1287.96 --> 1288.30]  yourself.
+[1288.72 --> 1289.50]  Yeah, just put it behind
+[1289.50 --> 1290.24]  a reverse proxy.
+[1290.40 --> 1291.00]  I mean, it doesn't have
+[1291.00 --> 1291.46]  to be traffic.
+[1291.62 --> 1292.28]  It could be Nginx.
+[1292.38 --> 1292.84]  It could be whatever.
+[1293.22 --> 1296.02]  But just don't open any
+[1296.02 --> 1296.84]  ports in your firewall.
+[1296.96 --> 1297.96]  You absolutely don't
+[1297.96 --> 1298.44]  need to.
+[1298.92 --> 1300.18]  Which actually brings me
+[1300.18 --> 1301.62]  very nicely onto a very,
+[1301.76 --> 1302.48]  very quick bit of
+[1302.48 --> 1303.14]  follow up about the
+[1303.14 --> 1304.36]  WireGuard rant I had
+[1304.36 --> 1306.08]  last week on OpenSense.
+[1307.24 --> 1308.94]  Turns out, like an
+[1308.94 --> 1312.02]  idiot, I set a slash 16
+[1312.02 --> 1313.96]  subnet in my DHCP server.
+[1314.82 --> 1315.48]  Now for those that don't
+[1315.48 --> 1316.60]  know, what that means is
+[1316.60 --> 1319.96]  every address from 192.168.0
+[1319.96 --> 1323.70]  all the way up to 192.168.255
+[1323.70 --> 1326.56]  was within my DHCP range.
+[1326.70 --> 1328.74]  So I had 65,000 or whatever
+[1328.74 --> 1330.24]  DHCP addresses available.
+[1331.24 --> 1332.92]  The upshot of that was when
+[1332.92 --> 1334.24]  I was trying to route through
+[1334.24 --> 1337.50]  WireGuard, I was doing a 192.168.13
+[1337.50 --> 1338.54]  subnet.
+[1339.16 --> 1341.54]  And so the remote servers were
+[1341.54 --> 1343.64]  hearing that were receiving the
+[1343.64 --> 1344.88]  commands from my laptop or my
+[1344.88 --> 1345.42]  phone or whatever.
+[1345.92 --> 1347.66]  But they didn't know how to route
+[1347.66 --> 1349.68]  back to the client device because
+[1349.68 --> 1351.14]  as far as they were concerned, the
+[1351.14 --> 1352.70]  slash 16 overrode everything and
+[1352.70 --> 1353.72]  it just thought everything was on
+[1353.72 --> 1354.08]  the LAN.
+[1354.08 --> 1357.02]  So what I did was I changed the
+[1357.02 --> 1360.12]  subnet of the WireGuard VPN to a
+[1360.12 --> 1361.12]  10.something.
+[1361.74 --> 1362.94]  So it was a completely different
+[1362.94 --> 1365.14]  subnet and I reduced my slash 16
+[1365.14 --> 1367.14]  down to a more manageable slash 20.
+[1367.62 --> 1368.92]  So I've only got a few thousand, like
+[1368.92 --> 1370.98]  4,000 addresses now instead of
+[1370.98 --> 1371.96]  65,000.
+[1372.08 --> 1373.38]  I think that should tie me over for a
+[1373.38 --> 1373.72]  bit, right?
+[1374.08 --> 1374.60]  Nicely done.
+[1375.02 --> 1376.58]  I definitely always suggest if
+[1376.58 --> 1379.30]  people can, different subnets for
+[1379.30 --> 1381.68]  the different VPN endpoints makes it
+[1381.68 --> 1383.90]  so much simpler, you know, and I've
+[1383.90 --> 1385.40]  tried, I've tried to do that myself
+[1385.40 --> 1387.84]  so many times because it can solve
+[1387.84 --> 1390.76]  you just a few simple problems and
+[1390.76 --> 1392.74]  keeps it a little clear in your
+[1392.74 --> 1393.02]  head.
+[1393.18 --> 1396.12]  Like I know that the studio is .4
+[1396.12 --> 1399.84]  and home is .7 and the WireGuard
+[1399.84 --> 1401.42]  network is actually a .10 network.
+[1401.54 --> 1402.50]  It's all separated out.
+[1402.86 --> 1402.96]  Yeah.
+[1403.02 --> 1404.20]  So I just wanted to be absolutely
+[1404.20 --> 1406.16]  clear that the problem was the user
+[1406.16 --> 1408.50]  not OpenSense or WireGuard.
+[1408.60 --> 1409.80]  It was totally my fault.
+[1409.80 --> 1412.92]  And I owe a huge debt of gratitude to
+[1412.92 --> 1414.18]  one of our listeners who reached out
+[1414.18 --> 1418.04]  to me on Discord and did a screen
+[1418.04 --> 1419.16]  share with me and walked me through
+[1419.16 --> 1420.40]  it for half an hour because he works
+[1420.40 --> 1423.32]  in security down in Charlotte in
+[1423.32 --> 1423.88]  North Carolina.
+[1424.56 --> 1426.12]  And he sort of taught me some new
+[1426.12 --> 1427.88]  stuff about, you know, networking and
+[1427.88 --> 1428.88]  triage and that kind of stuff.
+[1428.94 --> 1429.56]  So that was pretty cool.
+[1429.62 --> 1431.70]  So huge thank you to that listener.
+[1432.24 --> 1434.06]  Sounds like somebody we should buy a
+[1434.06 --> 1436.78]  beer for when community events happen
+[1436.78 --> 1437.10]  again.
+[1437.44 --> 1437.88]  One day.
+[1438.68 --> 1439.08]  Yeah.
+[1439.80 --> 1442.06]  Well, if you'd like to learn
+[1442.06 --> 1444.18]  networking or anything else, ACG has
+[1444.18 --> 1447.16]  20% off annual plans right now.
+[1447.28 --> 1448.56]  We'll have a link in the show notes
+[1448.56 --> 1450.10]  or just go to cloudguru.com.
+[1450.16 --> 1451.80]  And when you sign up, use the promo
+[1451.80 --> 1454.00]  code springintocloud21.
+[1454.24 --> 1455.86]  You know that cloud is growing.
+[1455.96 --> 1457.48]  There's lots of new services and
+[1457.48 --> 1459.62]  systems more every day, it seems.
+[1459.98 --> 1461.50]  And that also means the demand for
+[1461.50 --> 1463.16]  skilled cloud professionals is growing
+[1463.16 --> 1463.48]  too.
+[1463.84 --> 1465.98]  82% of hiring managers say a cloud
+[1465.98 --> 1468.30]  certification makes a candidate more
+[1468.30 --> 1468.80]  attractive.
+[1468.80 --> 1471.36]  So go grow your skills with hands-on
+[1471.36 --> 1472.08]  labs and learning.
+[1472.42 --> 1473.72]  Keep up with change and develop the
+[1473.72 --> 1475.38]  skills you need with a cloud guru.
+[1475.62 --> 1478.32]  To get that 20% off, sign up for an
+[1478.32 --> 1480.22]  annual plan and use that promo code
+[1480.22 --> 1482.54]  springintocloud21.
+[1482.54 --> 1485.32]  95% of learners say that a cloud guru's
+[1485.32 --> 1487.08]  tools and content directly help them
+[1487.08 --> 1488.22]  advance their careers.
+[1488.54 --> 1489.72]  Spring into cloud21.
+[1489.90 --> 1490.82]  Link in the show notes or go to
+[1490.82 --> 1492.20]  cloudguru.com.
+[1494.48 --> 1496.98]  Ryan writes in with an IGPU question.
+[1497.46 --> 1498.00]  Hey there, friends.
+[1498.08 --> 1499.12]  I'm a big fan of the show.
+[1499.72 --> 1501.50]  I currently am in the process of building
+[1501.50 --> 1503.10]  an off-grid house in New Zealand.
+[1503.42 --> 1504.88]  Oh, that's the dream.
+[1504.88 --> 1505.44]  I know.
+[1506.00 --> 1506.40]  Right?
+[1506.66 --> 1507.04]  Amazing.
+[1507.32 --> 1508.10]  Can we come visit?
+[1509.06 --> 1510.26]  Self-hosted on tour.
+[1511.08 --> 1513.32]  Power consumption is key, so I want a
+[1513.32 --> 1514.82]  small box to run basically everything
+[1514.82 --> 1516.62]  I need, which thankfully isn't going to
+[1516.62 --> 1517.36]  be that much.
+[1517.80 --> 1520.24]  My question is, is it possible to run a
+[1520.24 --> 1522.44]  Linux server and pass through an IGPU to
+[1522.44 --> 1525.42]  a Windows VM for Blue Iris, while still
+[1525.42 --> 1527.32]  using the IGPU for containerized
+[1527.32 --> 1528.60]  applications like Plex?
+[1529.24 --> 1531.26]  I can't seem to see any problem with
+[1531.26 --> 1533.08]  this in theory, but wonder if you have
+[1533.08 --> 1533.72]  any ideas.
+[1534.16 --> 1534.92]  Love your work.
+[1535.22 --> 1535.58]  Ryan.
+[1536.62 --> 1537.88]  What do you think about this one?
+[1537.98 --> 1539.90]  I have also contemplated, is there a
+[1539.90 --> 1541.52]  way I can have my cake and eat it too
+[1541.52 --> 1544.10]  when it comes to an IGPU and a low
+[1544.10 --> 1544.66]  power system?
+[1545.08 --> 1546.58]  I thought I'd solve this problem.
+[1546.64 --> 1547.94]  I thought I had the answer.
+[1548.46 --> 1551.50]  And it was a technology called GVT-G,
+[1551.50 --> 1555.20]  which is a virtual graphics card kind
+[1555.20 --> 1557.84]  of slicing thing that basically lets you
+[1557.84 --> 1561.58]  take an Intel GPU built into your CPU
+[1561.58 --> 1564.62]  and slice it up into two slices and give
+[1564.62 --> 1566.14]  one to one VM and one to another.
+[1566.34 --> 1569.04]  So the obvious use case for that is to
+[1569.04 --> 1571.66]  give one slice to a Windows VM for Blue
+[1571.66 --> 1574.14]  Iris and then give the other slice to
+[1574.14 --> 1576.84]  another Linux VM for Plex and then keep
+[1576.84 --> 1578.06]  the host as clean as possible.
+[1578.72 --> 1578.78]  Yeah.
+[1579.30 --> 1581.58]  However, and I've written a blog post about
+[1581.58 --> 1582.36]  this this week.
+[1583.22 --> 1586.54]  Unfortunately, the performance of GVT-G is
+[1586.54 --> 1587.78]  horrible.
+[1589.58 --> 1593.38]  I found it to be anywhere from 58 to 82%
+[1593.38 --> 1595.56]  slower than Quicksync being run natively
+[1595.56 --> 1596.54]  on the bare metal host.
+[1597.16 --> 1598.16]  Holy smokes.
+[1598.46 --> 1599.92]  I did not expect that at all.
+[1600.34 --> 1600.46]  Yeah.
+[1600.52 --> 1602.12]  So my test that I did was it was pretty
+[1602.12 --> 1604.54]  unscientific, but it was a very real
+[1604.54 --> 1605.56]  world use case for me.
+[1605.56 --> 1608.76]  So I used the Plex sync for offline
+[1608.76 --> 1612.22]  playback feature and I chose a high bit
+[1612.22 --> 1612.50]  rate.
+[1612.62 --> 1615.78]  So about a 38 megabyte a second.
+[1616.44 --> 1617.54]  Was it megabit?
+[1617.62 --> 1618.52]  I always get confused.
+[1618.96 --> 1622.62]  Video file encoded with MPEG-4 and H.264
+[1622.62 --> 1626.52]  with a DTS master audio soundtrack.
+[1626.92 --> 1631.04]  And I used the four megabytes a second 720p
+[1631.04 --> 1634.00]  sync for offline playback option within Plex.
+[1634.00 --> 1636.36]  And I did that on an iPad.
+[1636.90 --> 1637.90]  You know, that was the client.
+[1638.02 --> 1639.48]  I don't think that bit really mattered too
+[1639.48 --> 1641.56]  much, but I did a few different tests.
+[1641.68 --> 1642.86]  So I did a software render.
+[1643.04 --> 1647.76]  So this is using the Intel i5-8500 CPU.
+[1648.24 --> 1650.20]  I picked that up for about a hundred dollars
+[1650.20 --> 1650.88]  used on eBay.
+[1651.04 --> 1652.32]  So it's a pretty good value.
+[1652.68 --> 1653.44]  Four gigahertz.
+[1653.54 --> 1656.44]  I think 4.1 gigahertz, six core CPU.
+[1657.20 --> 1661.60]  With CPU rendering only, I saw a 1.1 times
+[1661.60 --> 1662.32]  speed.
+[1662.32 --> 1665.96]  The best I saw running it natively in QuickSync
+[1665.96 --> 1668.00]  on the host was 10.2.
+[1668.52 --> 1671.22]  And then on a sliding scale between those two
+[1671.22 --> 1676.86]  numbers of 1 times and 10 times, with the GVTG stuff set
+[1676.86 --> 1682.78]  into two slice mode, I saw only about a 1.8, 1.9 times.
+[1683.32 --> 1687.68]  So it was faster than CPU software encoding, you know, twice as fast
+[1687.68 --> 1695.28]  actually, but it was 80, what, something, 82% slower than running it on the
+[1695.28 --> 1695.96]  bare metal host.
+[1695.96 --> 1702.70]  So the other problem that I ran into, besides, you know, leaving 80 plus percent performance
+[1702.70 --> 1705.44]  on the table, was stability.
+[1705.86 --> 1708.76]  Unfortunately, that wasn't a great story either.
+[1709.18 --> 1715.52]  The problems I ran into were, so I was running Proxmox as the base OS because the Proxmox
+[1715.52 --> 1720.86]  wiki actually has a really great entry about enabling GVTG and QuickSync and pass through
+[1720.86 --> 1721.64]  and all that kind of stuff.
+[1721.64 --> 1723.58]  And it was really painless to get going.
+[1723.68 --> 1726.52]  It only took me an hour or so to figure it all out and get it going.
+[1727.38 --> 1729.50]  But the stability was just not there.
+[1730.02 --> 1731.92]  My evidence is only anecdotal, though.
+[1732.34 --> 1736.12]  Because of the instability, I couldn't really get the log files that I needed
+[1736.12 --> 1741.68]  because the system either had to be hard reset or it was just hanging and processes were just
+[1741.68 --> 1743.48]  hanging or I was getting kernel panics.
+[1743.48 --> 1745.24]  It was just a mess.
+[1745.80 --> 1748.32]  And, you know, at the end of the day...
+[1748.32 --> 1751.92]  Just not something you could just let run and just not have to think about it.
+[1752.06 --> 1753.70]  No, unfortunately, it wasn't.
+[1753.80 --> 1759.76]  And, you know, things worked fine until I powered on the Windows VM that was running Blue Iris.
+[1760.00 --> 1763.54]  And that system has six 4K cameras going into it.
+[1763.58 --> 1765.38]  So it's got a decent amount of load.
+[1765.38 --> 1772.26]  Now, I know for a fact that the i5 CPU can handle that load because it's been running in my HP 290 Slim
+[1772.26 --> 1776.72]  for six months just fine, handling everything perfectly.
+[1777.24 --> 1784.86]  But for some reason, when it's in the GVTG mode, it just, I guess, because the performance is so poor
+[1784.86 --> 1791.04]  with the emulation, whatever they're doing to slice the GPU up, however they're doing it in the Intel drivers,
+[1791.04 --> 1799.72]  it just meant that as soon as I powered up Blue Iris, within 30 minutes, the whole Proxmox system was just unhappy.
+[1800.06 --> 1804.30]  You know, like the web UI wouldn't load sometimes or you actually go and reboot the system
+[1804.30 --> 1810.78]  and you'll see SystemD printing out waiting on Kimu guest to shut down for like 30 minutes.
+[1811.32 --> 1815.62]  So it wasn't just guest stability issues, but the entire host.
+[1815.82 --> 1816.14]  Uh-huh.
+[1817.06 --> 1817.90]  Ooh, yeah.
+[1818.18 --> 1819.56]  Well, that's just a deal breaker.
+[1819.56 --> 1822.18]  Oh, man, Alex.
+[1822.36 --> 1824.98]  At the end of the day, you want it to be on and functional.
+[1825.24 --> 1831.26]  And yes, this is a hobby, and I do enjoy messing about with servers, but there comes a point.
+[1831.34 --> 1832.34]  It's not a full-time job.
+[1832.50 --> 1833.24]  No, exactly.
+[1833.58 --> 1837.70]  There comes a point where you're like, this S just needs to work now.
+[1838.04 --> 1838.26]  Yeah.
+[1838.64 --> 1839.98]  And it just didn't, unfortunately.
+[1840.26 --> 1844.58]  I think you crossed the threshold of devoting more time to this than most folks quite a while ago.
+[1844.58 --> 1848.36]  I mean, even taking a pass at the different encoding options, that's good insight.
+[1848.36 --> 1854.76]  And it really shows you that you're, I mean, yeah, it's almost twice as fast if you use GVT.
+[1854.76 --> 1860.42]  When you consider the stability issues, I would rather just use CPU encoding.
+[1860.42 --> 1869.42]  CPU encoding with QuickSync, because that's only pulling down about 10 watts when it's doing a full 1080p stream, and it's running at 10x real time.
+[1869.92 --> 1874.70]  So it actually, you know, in terms of performance per watt is the best thing out there.
+[1874.94 --> 1879.18]  I actually also, just for giggles, use my 1080 Ti to run one of these transcodes.
+[1879.76 --> 1881.62]  So QuickSync is running at 10x.
+[1882.02 --> 1888.02]  A 1080 Ti, which is pulling down 18 times the amount of power, is running at 17 times.
+[1888.20 --> 1889.98]  So 10x versus 17x.
+[1890.08 --> 1890.50]  Wow.
+[1890.70 --> 1897.44]  It's a good way to see the performance discrepancy between Intel's GPU and the NVIDIA GPU right there, isn't it?
+[1897.46 --> 1897.96]  You can really.
+[1898.28 --> 1900.82]  And then, of course, CPU with its measly 1.1x.
+[1901.24 --> 1901.40]  Yeah.
+[1902.02 --> 1905.70]  Performance per watt of the NVIDIA card was just hilariously bad.
+[1906.06 --> 1906.58]  Well, sure.
+[1906.98 --> 1907.30]  Sure.
+[1907.30 --> 1914.94]  So what I've ended up doing, actually, and this is to go back to Ryan's question now, is I've ended up splitting things back out into physical boxes.
+[1915.56 --> 1920.04]  The Blue Iris box is an HP290 Slim that I already had.
+[1920.44 --> 1927.58]  I've put the i5 back into there, and I bought another i5 to put into my server, so I have two now, which is a shame, but hey-ho.
+[1928.06 --> 1932.36]  I was doing some testing on the HP290 for average power usage.
+[1932.36 --> 1938.12]  When I say idle, what I mean by that is Blue Iris is running with its normal sort of load.
+[1938.30 --> 1945.72]  So an average sort of power usage I see on that box is anywhere from sort of 10 to 25 watts, depending on what it's doing.
+[1945.72 --> 1951.08]  Which, for the performance I'm getting, you know, that kind of power usage is fantastic, really.
+[1951.82 --> 1960.20]  And then my main server is pulling it anywhere with, you know, it's got, I think, 12 hard drives in it, anywhere from 40 to 80 watts at idle.
+[1960.20 --> 1967.36]  So, you know, it's all pretty good, pretty low, you know, to have all that performance for under 100 watts at idle is, I'm pretty happy with that.
+[1967.90 --> 1969.64]  Yeah, thanks for sharing the details with us.
+[1969.68 --> 1970.86]  You mentioned the blog in there.
+[1970.96 --> 1973.38]  Well, Sam actually writes in with our next question.
+[1973.46 --> 1981.38]  He's a new listener, and he says, I'd love to hear more about what Alex uses for building his blog, and if you've experimented with any other options and what you thought.
+[1981.56 --> 1982.24]  Thanks for the great show.
+[1982.24 --> 1995.84]  Well, several years ago, when I was launching LinuxServer.io, I actually had a personal blog, blog.katz.me, that got turned into LinuxServer's blog and eventually the LinuxServer website, and that kind of took over and became its own thing.
+[1996.26 --> 2004.84]  So we used to use WordPress, and then we moved to Ghost on LinuxServer, and this would be, I dread to think how long ago, like five years ago?
+[2004.84 --> 2013.84]  We moved to Ghost, and it's been so solid, I then ended up spinning up Ghost for my own personal blog to do, like, travel writing and all that kind of stuff as well.
+[2014.58 --> 2022.22]  So I use Ghost almost exclusively for blogging, and then the Perfect Media Server website is written in mkdocs.
+[2022.70 --> 2024.66]  I live vicariously through you on Ghost.
+[2024.90 --> 2032.26]  That was the route I thought I might go if I were going to set up a blog again, and I'm going to put a link to that in the show notes because I think that's worth checking out.
+[2032.26 --> 2035.50]  Although they've changed their model a lot since I first originally found them.
+[2035.54 --> 2041.38]  Now they seem like they're really focused on them hosting the blog, but you can still self-host and all that?
+[2041.78 --> 2050.02]  Self-host out of a container, yeah, and I've actually got a custom theme, so I spent quite a bit of time before the Perfect Media Server 2020 edition came out,
+[2050.02 --> 2058.02]  making sure that my blog had search and a few other different, you know, like fav icons and social media icons, all that kind of crap.
+[2058.02 --> 2064.52]  So you can customize the theme relatively easily, and all of that stuff is open source in GitHub.
+[2064.80 --> 2067.60]  So, you know, I have no complaints about Ghost at all.
+[2067.66 --> 2069.02]  It just does exactly what I need.
+[2069.20 --> 2073.60]  It looks pretty good, and you see it all over the place on the internet, really.
+[2073.80 --> 2077.14]  So I think that's kind of, you know, proof is in the pudding.
+[2077.40 --> 2080.38]  How many blogs do you see that are in Ghost?
+[2080.72 --> 2081.46]  Quite a few.
+[2081.56 --> 2082.72]  So yeah, it must be okay.
+[2082.72 --> 2088.10]  All right, so I think our final question for today, Tamo writes in about user account management.
+[2088.90 --> 2091.92]  Hi guys, I'm a new listener, and this show is perfect for me.
+[2091.98 --> 2093.18]  I started at episode one.
+[2093.36 --> 2093.88]  Well, thank you.
+[2094.58 --> 2099.44]  I was wondering if you have done a podcast about how you manage different servers and user accounts.
+[2099.62 --> 2102.74]  Do you have LDAP or some kind of centralized authentication?
+[2103.70 --> 2110.68]  I'm finding creating unique user accounts for every server and saving their credentials every time to be a bit of a pain in the bum.
+[2110.68 --> 2113.14]  I was wondering if you have any thoughts.
+[2113.66 --> 2116.42]  Looking through the episode descriptions, I didn't find anything about this.
+[2116.64 --> 2117.92]  Thanks, Tamo.
+[2118.24 --> 2120.92]  Good question, because it's been on my mind a lot.
+[2121.58 --> 2128.86]  Recently, Linux distributions like Fedora and Ubuntu added checkbox Active Directory support to their installers.
+[2129.66 --> 2137.60]  And that got me thinking, yeah, almost wouldn't mind having like an Active Directory setup here on the LAN,
+[2137.60 --> 2142.56]  either actual Active Directory or some Samba Frankenstein version of it.
+[2142.78 --> 2148.06]  But truthfully, what I have landed on is standardized accounts.
+[2148.16 --> 2152.38]  So we have a standardized Studio account, and I have an account on all the systems.
+[2153.06 --> 2156.76]  And the people who work here at the Studio, we know those logins.
+[2156.76 --> 2159.68]  And then for our server logins, we use SSH keys.
+[2160.36 --> 2169.94]  But I do long term have my eye on Systemd HomeD as a potential way to solve this, at least here on the LAN at the studio.
+[2170.68 --> 2172.42]  And I'll have a link to that in the show notes.
+[2172.50 --> 2179.16]  But essentially, it takes your home directory and all of your user information and puts it into JSON.
+[2179.16 --> 2185.72]  And then you can drop this home directory bundle into a Systemd HomeD enabled system.
+[2186.06 --> 2191.94]  And not only does your home directory show up there, but you also then become a user on the system.
+[2192.56 --> 2195.82]  That's obviously me giving you the short version.
+[2196.06 --> 2197.28]  But it has some potential.
+[2197.52 --> 2202.68]  So you could see here in the studio where perhaps we'd keep our master HomeD directories on the server
+[2202.68 --> 2208.72]  and then R-sync them down to the studio machines in my workstation, I don't know, every hour, every 24 hours.
+[2208.80 --> 2209.16]  I don't know.
+[2209.48 --> 2210.48]  I haven't really looked into it yet.
+[2210.94 --> 2213.84]  But if we did that, it would also sync down our user credentials.
+[2214.50 --> 2219.26]  Early days, just something that's on my horizon, kind of keeping on my radar as a possibility
+[2219.26 --> 2221.42]  because I don't need something too advanced.
+[2221.72 --> 2226.10]  I've managed large LDAP single sign-on installations in the past as part of my job.
+[2226.10 --> 2228.90]  And it worked surprisingly well for a long time.
+[2228.94 --> 2230.88]  And I just don't really have an interest in doing that anymore.
+[2230.88 --> 2233.18]  I mean, you could spin up LDAP.
+[2233.26 --> 2234.40]  You could do free IPA.
+[2234.48 --> 2235.54]  You could do a lot of things.
+[2235.90 --> 2236.90]  You could do Active Directory.
+[2237.08 --> 2238.28]  It sounds kind of fun.
+[2238.32 --> 2238.66]  I don't know.
+[2239.36 --> 2239.76]  Yeah.
+[2239.94 --> 2245.72]  But I don't know about you, but I've got to the point over the last decade where I'm managing so many different systems.
+[2246.02 --> 2249.54]  Some of them are in different houses or different cloud providers or stuff like that,
+[2249.62 --> 2256.72]  that having them sync back to a central authentication would just be so complicated.
+[2256.72 --> 2263.14]  I've kind of got, I feel like, half-decent context switching between the different servers and knowing,
+[2263.28 --> 2266.32]  oh, right, I don't have that particular setup on this one.
+[2266.42 --> 2271.92]  And any files I do need to sync between various things, I have my NAS, and I just mount that via Samba.
+[2272.82 --> 2275.44]  And I don't really worry too much about the home directory.
+[2275.54 --> 2278.72]  Anything that's in there, in my opinion at least, is ephemeral.
+[2279.36 --> 2282.30]  It goes in Git or it goes in Samba or it gets lost.
+[2282.42 --> 2283.52]  That's kind of how I treat it.
+[2283.52 --> 2284.00]  Yeah.
+[2284.40 --> 2294.16]  I think in part it's because I have, in full disclosure, I've accepted a security practice on the LAN of the studio that probably you shouldn't do,
+[2294.24 --> 2299.00]  and that is we don't rotate passwords very often, maybe once every couple of years.
+[2299.18 --> 2300.00]  But then again…
+[2300.00 --> 2300.46]  It's convenient.
+[2300.74 --> 2301.34]  I'll give you that.
+[2301.62 --> 2301.82]  Yeah.
+[2301.86 --> 2305.24]  And as far as physical access goes, it's a real small handful of people.
+[2305.70 --> 2308.92]  It's not like an organization with an office of 20 here.
+[2308.92 --> 2318.34]  And then for the servers, it's pretty much all down to SSH keys, and all remote login is usually done with that.
+[2318.46 --> 2322.80]  Any access to the LAN is done with WireGuard, and that has its own set of keys.
+[2323.20 --> 2324.74]  So there's some layers there.
+[2325.24 --> 2327.66]  Every now and then, I still think it's a fair question.
+[2327.74 --> 2331.16]  I still think to myself, I could do this a little better.
+[2331.16 --> 2339.02]  And I do fantasize about a future where I deploy everything pragmatically, and then everything has central sign-on and central storage.
+[2339.72 --> 2343.04]  But I think I'd have to clone myself to get there.
+[2344.08 --> 2345.94]  But this goes back to the point at the beginning, right?
+[2346.02 --> 2348.56]  You use Arch because you just want to get stuff done.
+[2348.78 --> 2354.20]  And I think we don't use a central authentication system because we just want to get stuff done.
+[2354.20 --> 2364.50]  We don't want to spend the week or two figuring it out and setting it up, and then every time we reinstall a box, attaching it to a domain controller or whatever it is.
+[2364.82 --> 2364.94]  Right.
+[2365.34 --> 2368.84]  I think it's just pragmatism, isn't it, that means we're lazy and don't do it.
+[2370.32 --> 2371.40]  Maybe that's a bit of it.
+[2371.66 --> 2372.54]  We've gotten old.
+[2372.74 --> 2378.12]  What we need is a young SSH intern to come into the studio and whip us together and get a single sign-on going.
+[2378.52 --> 2379.72]  Yeah, maybe, maybe.
+[2379.72 --> 2385.10]  Thank you to our members over at selfhosted.show.sre.
+[2385.22 --> 2386.40]  Thank you for supporting the show.
+[2386.58 --> 2394.36]  As a thank you, we supply you a limited ad version of the show, and you also in that feed get extra content the post show.
+[2394.52 --> 2397.80]  Thank you very much to our members at selfhosted.show.sre.
+[2398.28 --> 2402.86]  We're going to have a little bit of a 3D printing hoedown in the post show today, I think.
+[2403.24 --> 2407.00]  Yeah, I look forward to that, and I also have a bit of a confession to make.
+[2407.00 --> 2409.20]  Just a little bit of business before we go.
+[2409.20 --> 2412.04]  Everything we talk about is over at selfhosted.show.
+[2412.18 --> 2416.28]  As always, you can go to selfhosted.show.com for all the ways to get in touch with us.
+[2416.72 --> 2418.84]  And you can find me on Twitter at Ironic Badger.
+[2419.04 --> 2423.50]  I'm there too, at Chris Elias, and the show at selfhosted.show.
+[2423.84 --> 2426.18]  On Discord, I'm at AlexKTZ.
+[2426.72 --> 2427.46]  Thanks for listening.
+[2427.74 --> 2429.10]  That was selfhosted.show.com.
+[2429.10 --> 2430.02]  Slash 39.
+[2430.02 --> 2430.10]  Slash 39.

40： Password Shaming _summary.txt

@@ -0,0 +1,62 @@
+• Home Assistant password shaming
+• Backups as an age-old cloud problem
+• Off-grid solar setup and battery capacity
+• Solar system planning for homeowners
+• Sustainability and reducing fossil fuel use
+• Grid management in the US with increasing demand from electric cars and crypto mining
+• OVH data center fire affects services
+• Possible cause of fire is unknown
+• Impact on neighboring data centers and regions
+• Concerns about data center fires in general, including at AWS or DigitalOcean
+• Discussion of fire suppression systems in data centers
+• Personal story of losing data due to a server failure
+• Importance of backups and having a plan for data recovery
+• Discussion of backup strategies and data storage
+• Local vs cloud backup methods
+• Challenges of backing up large amounts of data
+• Use of hard drives for offsite backups
+• Evaluating risk and cost in backup planning
+• Importance of having multiple backup solutions
+• Family photo backup plans using iCloud and Nextcloud
+• Trust issues with Google Photos and Apple's data policies
+• Plans to implement a Google Photos alternative
+• Review of current backup strategies and potential areas for improvement
+• Backup device and lack of backups
+• Linode hosting and cloud services
+• People's Choice Stevie Award for Favorite Customer Service in the Computer Services category
+• Pricing and value of Linode
+• Complexity and simplicity of Linode's cloud manager
+• Promotion of $100 credit at linode.com/SSH
+• Home Assistant has integrated a new feature with the Have I Been Pwned website to check if passwords are compromised
+• The feature checks the first five characters of hashed passwords against the database, not the entire password
+• Some users are complaining about data transmission on metered connections, but the amount is minimal (36 kilobytes)
+• The speaker acknowledges reusing passwords on their LAN and having a "lazy" approach to security
+• However, they emphasize that home networks with IoT devices have a higher threat level and require more secure practices
+• Discussing the importance of good passwords for home networks and LANs
+• Mentioning the risks of hackers gaining access to devices via SSH sign-ins
+• Talking about Home Assistant's implementation of password requirements
+• Suggesting that a temporary disable option for password enforcement would be useful
+• Exploring the benefits of password management for new users
+• Praising Home Assistant's decision to prioritize security features
+• Discussing the potential for Home Assistant to become a consumer product in the future
+• Mentioning recent issues with add-ons leaking information and Cloudflare's involvement in anonymizing requests
+• Datadog's continuous profiler automatically collects data from production servers.
+• Analyzing this data provides a unified picture of the entire environment and correlates code performance with server metrics in real-time.
+• Datadog offers features such as tracing, log management, and machine learning alerting to help identify issues.
+• A listener asks about securely exposing services on the internet, and one possible solution is to use a VPN like WireGuard.
+• The effectiveness of security through obscurity (hiding services from public view) is questioned due to publicly available certificate information.
+• Alternative methods for testing service exposure include running it on a VPS or monitoring logs.
+• Zero inbound outside traffic for peace of mind
+• Importance of logging in monitoring security
+• Using tools like Datadog to alert on suspicious activity
+• Listener Chris asks about self-hosted smart switches
+• Shelly devices mentioned as a solution for self-hosted smart switches
+• File browser alternative suggested: github.com/file-browser/file-browser
+• Chowdown recipe app and alternatives discussed, including Tandoor Recipes
+• Tandoor recipes is a new release that uses mkdocs for documentation
+• It's available in a Docker container and also compatible with Unraid, Synology, and Kubernetes
+• The application has an import functionality but requires a Postgres database
+• The speaker compares it to their current app, Chowdown, which stores data in clear text and is more future-proof
+• Mention of Chris Elias and specific timestamp range
+• Information about the current show on selfhosted.show
+• User's Discord handle (AlexKTZ)

40： Password Shaming _transcript.txt

@@ -0,0 +1,654 @@
+[0.00 --> 6.50]  Coming up on the show, we react to Home Assistant password shaming both of us and then attempt to solve an age-old cloud problem.
+[7.28 --> 8.50]  Backups. I'm Chris.
+[8.94 --> 10.50]  And I'm Alex, and this is Self-Hosted.
+[11.72 --> 14.16]  The podcast is a middle-aged man now. We're 40.
+[15.08 --> 21.22]  Yeah, the podcast is feeling like he's still got some pet left in him, but also has a few miles on him. Or her.
+[21.46 --> 22.74]  Midlife crisis coming up.
+[23.26 --> 27.36]  Is the podcast, does it have a gender? It's a thing, right?
+[27.36 --> 29.46]  The podcast prefers to be referred to as they.
+[30.00 --> 35.02]  Podcast pronouns.
+[35.88 --> 37.52]  There's a title right there, I'll tell you what.
+[38.08 --> 41.72]  Anyway, you were going to tell me about your off-grid solar stuff. We've not heard about that for a while.
+[42.26 --> 47.88]  We were chatting about this just before we hit record because I'm off-grid and podcasting on solar right now.
+[48.22 --> 50.64]  I was just talking to you, actually, because you're thinking about getting solar.
+[50.64 --> 56.22]  And I think the thing that people have to wrap their head around is, what are you planning for?
+[56.28 --> 58.68]  Are you planning for a grid blackout or brownout?
+[58.68 --> 61.24]  Are you planning for going out into the woods?
+[61.70 --> 62.94]  What's your scenario?
+[62.94 --> 68.26]  And then how much battery do you really need versus could you supplement with a generator?
+[68.26 --> 77.40]  Like, for me right now, I think I've hit a sweet spot of enough battery capacity that I can run on it for a day or so.
+[77.54 --> 82.10]  And if it's a sunny day out, I can get a 30%, 40% charge right now in the winter.
+[82.46 --> 85.34]  But I can't get 100% charge off of solar right now.
+[85.34 --> 91.44]  And so I need to run the generator for about an hour once a day right now when I'm off-grid.
+[92.34 --> 93.48]  And that's fine.
+[93.58 --> 98.22]  I feel like that's actually a really good spot because the more battery you have, the more generator or solar you're going to need.
+[99.02 --> 100.90]  You can't, you know, you can't charge all.
+[100.96 --> 102.94]  You have to have the ability to charge all that stuff up.
+[103.08 --> 107.72]  So I feel like I've kind of hit the sweet spot that because it's winter, you know, we're not getting prime sunshine.
+[107.72 --> 110.56]  And I'm only running the generator about once a day.
+[110.78 --> 112.76]  And otherwise, we're getting along.
+[112.90 --> 114.42]  I think I'm kind of in that sweet spot.
+[114.50 --> 120.16]  And I think that's something you should think about when you're specking out your solar system for your house is what are you covering for?
+[120.24 --> 122.30]  Are you covering for a couple of days of no power?
+[122.46 --> 124.64]  Or do you really just need to cover for a couple of hours?
+[125.18 --> 128.02]  And if it goes longer, maybe you could run a generator for an hour or two.
+[128.48 --> 133.50]  I think I want to cover just the average daily low-level load of the house.
+[133.50 --> 134.94]  I want to make the house more sustainable.
+[134.94 --> 141.08]  So, you know, like just all the lighting, all the computers that are on in here, whatever that works out to be.
+[141.76 --> 146.28]  My electric bill is normally in a sort of $100 to $120-ish range.
+[146.36 --> 147.32]  So it's not too crazy.
+[148.36 --> 150.78]  And for me, it's about sustainability.
+[151.16 --> 155.46]  And I was watching a David Attenborough program, Our Perfect Planet, the other night.
+[155.80 --> 158.90]  Beautiful 4K HDR on the LG OLED.
+[159.28 --> 161.52]  Oh, it was magical to watch that thing.
+[161.82 --> 162.90]  Streaming from the Plex server.
+[163.28 --> 163.60]  Correct.
+[163.60 --> 165.30]  Yeah, through the Nvidia shield.
+[166.06 --> 176.44]  You can't help but watch these perfect planet things and be left with a sense of guilt about what humanity is doing to the planet and how we're consuming too many resources and stuff like that.
+[176.58 --> 189.10]  So, you know, I think about how I might be in a position to do something about that as just an individual when in reality we need to, as a species, collectively actually affect change.
+[189.10 --> 191.66]  But as an individual, there isn't much I can do.
+[191.66 --> 197.14]  But reducing my use of fossil fuels, even by a little bit, feels like a good place to start.
+[197.40 --> 202.64]  Yeah, I love the idea of even just offsetting the computers that run all the time.
+[202.64 --> 206.26]  So, during the day, I've reached the point where all day long I'm running off the solar power.
+[206.38 --> 215.74]  I'm bringing in more solar power than I am using, which is a great spot to be because that means my home server, all my stuff is being sustained by the sun.
+[215.74 --> 220.92]  And I'd love to do a similar setup at the studio, a couple of panels on the roof.
+[220.98 --> 227.82]  If I could just bring in, you know, 400 watts or so, I could probably cover most of my computer gear that's running 24-7.
+[227.82 --> 236.70]  And, you know, I think about long-term, Alex, say even just 10 years, 15 years down the road, maybe the majority of cars or all cars sold will be electric.
+[237.28 --> 244.88]  How does the grid in the United States, at least, handle that if we don't have some people offsetting their load with solar?
+[245.02 --> 252.94]  It seems like long-term, the direction things are going between crypto mining and electric cars, there's going to be more demand on the grid than ever.
+[252.94 --> 260.12]  So, being able to supplement a little bit might not only just be a nice thing to do for the environment, but also ensure that you have enough power to go around.
+[260.78 --> 261.50]  Free Bitcoin, baby.
+[262.06 --> 262.24]  Yep.
+[262.34 --> 263.36]  Get that crypto going.
+[263.94 --> 266.10]  And maybe, maybe spend your time learning.
+[266.22 --> 268.52]  This episode is brought to you by the all-new A Cloud Guru.
+[268.72 --> 272.96]  They are the leader in learning for the cloud, Linux, and other modern tech skills.
+[273.14 --> 273.62]  Go check them out.
+[273.66 --> 276.24]  They have hundreds of courses and thousands of hands-on labs.
+[276.34 --> 276.70]  Get certified.
+[276.86 --> 277.26]  Get hired.
+[277.68 --> 280.28]  Get learning at acloudguru.com.
+[280.28 --> 287.24]  You could spend that time mining crypto, or you could spend that time learning job skills and getting hired.
+[287.62 --> 297.32]  But, you know, I think maybe you and I are thinking about off-grid and backup power today because a lot of our listener services are down and offline as we record this right now.
+[297.74 --> 298.08]  That's right.
+[298.18 --> 298.30]  Yeah.
+[298.46 --> 304.60]  OVH, one of the largest VPS providers in Europe, have suffered a major fire this week.
+[304.60 --> 316.64]  And it's taken, literally taken out one of their data centers and had dramatic effects on some of their other regions, data centers, whatever they called for OVH as well.
+[317.36 --> 319.42]  It's just got me thinking, great.
+[319.62 --> 322.16]  There's another disaster that I hadn't really thought about.
+[322.24 --> 325.50]  What if AWS or DigitalOcean or Linode, what if they catch fire?
+[325.50 --> 327.68]  Oh, that's another one to plan for.
+[329.12 --> 335.40]  Yeah, the thing that's tricky about OVH is data centers one through four were all kind of like in the same area.
+[335.84 --> 341.86]  So after midnight on the Wednesday of the week we're recording this, OVH cloud had an alarm go off.
+[342.24 --> 344.82]  The cause as of this recording right now is still unknown.
+[344.82 --> 350.16]  However, the founder and CEO speculated it may have been a UPS fire.
+[350.34 --> 358.90]  And he noted in a video update that he released a couple of days ago that UPS number seven had been serviced earlier that day.
+[358.98 --> 361.70]  But obviously more investigation is required.
+[362.02 --> 366.38]  In total, OVH had four data centers in this area and one data center.
+[366.78 --> 370.76]  SBG two was just totally destroyed by fire.
+[370.76 --> 375.40]  And then part of SBG one was also damaged.
+[375.54 --> 378.22]  And then SBG three and four, they're fine.
+[378.40 --> 383.44]  But as we record, there's still some outages because there's some areas the staff can't get to.
+[383.52 --> 384.68]  There's network issue.
+[384.94 --> 386.64]  There's still some power issues.
+[386.64 --> 392.56]  And there's even the fact that they still have to validate that the cooling system is still fully functional.
+[392.90 --> 394.56]  It's like bad, Alex.
+[394.56 --> 406.88]  This is a weird one to me because every data center that I've worked near or in in some occasions, they've all had argon fire suppressant systems.
+[406.88 --> 414.92]  And just fire was something that you kind of assumed would never get out of control in a data center because it's a controlled environment.
+[415.42 --> 419.56]  There isn't a huge amount of flammable stuff like on a data center floor.
+[419.86 --> 423.44]  It's just metal boxes with some cables and stuff like that, essentially.
+[423.44 --> 424.04]  Yeah.
+[424.28 --> 426.98]  So it's kind of surprising to me that it was able to get to this level.
+[427.10 --> 432.44]  I mean, if you look at some of the pictures and we've got a Reuters article linked in the show notes, that building was toast.
+[433.20 --> 433.54]  Yeah.
+[433.58 --> 442.84]  The CEO says something about it using older style construction techniques and that the newer buildings that weren't damaged were using the newer style.
+[443.04 --> 447.78]  I wonder if that style is fire suppression, you know.
+[447.96 --> 448.60]  Yeah, maybe.
+[448.92 --> 450.30]  Or materials or something.
+[450.30 --> 454.94]  But it kind of got us thinking like, you know, we got kind of a sad note in from listener.
+[455.04 --> 458.62]  Kerry said, my server was in data center one and I have lost it.
+[458.68 --> 467.80]  I'm afraid I didn't have any complete backups because I didn't really have anywhere to back up to that server already blew my personal self-hosting budget.
+[468.46 --> 470.88]  I feel like I've lost a loved one.
+[471.52 --> 474.44]  I guess I'll get a box at home and I'll have to back up to that from now on.
+[474.44 --> 476.64]  But that's going to get very expensive.
+[477.42 --> 478.12]  That is tricky.
+[478.12 --> 479.08]  Well, it is.
+[479.40 --> 480.82]  It is going to get expensive.
+[481.40 --> 486.62]  But I would argue that the emotions you're feeling right now are also expensive.
+[487.18 --> 491.48]  Just in a, you know, not dollars and cents necessarily, but they're expensive in a different way emotionally.
+[492.50 --> 496.44]  And only you can quantify how much your data is worth.
+[496.44 --> 504.78]  I mean, I don't know what was on this particular server for you, Kerry, but I certainly know in the past when I've lost data, it hurts.
+[505.20 --> 516.68]  Genuinely, you spend the next few weeks, months, sometimes longer wishing you'd done things differently, thinking, oh, if only I'd spent a couple of hundred on a Pi and an external hard drive.
+[516.68 --> 519.30]  And I wouldn't even be in this situation.
+[520.56 --> 530.24]  I mean, if you think about what most typical VPSs are, they are probably less than a hundred gig disk, probably only a few gigabytes of RAM or something like that.
+[530.32 --> 533.84]  So we aren't talking about a huge amount of data to back up here.
+[534.32 --> 541.80]  And what I would say is if you've got no backup, I mean, literally zero, don't try and aim for perfect.
+[541.80 --> 553.66]  Just get a 128 gig USB stick off Amazon and then just get in the habit of downloading your data once a month, once a year even.
+[553.94 --> 559.84]  Because I'm sure right now you wish you'd had something, even if it was 11 months old, you'd have something.
+[559.84 --> 571.82]  Something I've seen really common is a lot of people these days, when they have cheap cloud hosting, they're going for like a NUC with a disk hanging off it or something that they're syncing to locally.
+[572.04 --> 576.72]  And getting that peace of mind by having the data on their local network.
+[576.72 --> 583.72]  And I got to admit, it's kind of what I did for the Jupyter Broadcasting stuff is we have NextCloud up at Linode.
+[583.88 --> 589.82]  And then we have NextCloud installed on the server at the Jupyter Broadcasting Studio on the LAN.
+[590.22 --> 593.48]  And we sync the stuff that I really care about.
+[593.58 --> 596.02]  We don't sync everything because it's hundreds of gigs.
+[596.32 --> 600.42]  But locally, we actually will also archive.
+[600.62 --> 603.88]  So I should probably back up the studio server now that I think about it.
+[603.88 --> 609.10]  But we back up the cloud locally to anything that's not ephemeral.
+[609.36 --> 611.22]  And anything that's not ephemeral, we try to keep locally.
+[611.46 --> 615.14]  And then my intention is to back that server up somewhere.
+[616.00 --> 618.70]  Alex's house, Backblaze, I don't know what.
+[618.88 --> 620.86]  But I've got the cloud part covered.
+[621.16 --> 623.98]  I just don't necessarily have the local part fully covered right now.
+[624.18 --> 629.94]  Because I ended up, and this is sort of where I connected with what Carrie was saying, is I just ended up with terabytes of data.
+[630.60 --> 630.92]  Terabytes.
+[630.92 --> 634.66]  And I don't know, I don't really know how to even get that offsite over the wire.
+[634.76 --> 635.32]  It's so much data.
+[636.14 --> 644.08]  Never underestimate, I think the saying goes, the bandwidth of a truck driving down a highway full of hard drives.
+[644.74 --> 646.72]  Get it on a hard drive and mail it to me.
+[646.82 --> 647.72]  That's the best way.
+[647.94 --> 652.04]  What you're saying is I should pack up the RV and drive a hard drive down to your place.
+[652.62 --> 653.90]  That makes the most sense, right?
+[653.94 --> 654.76]  You can if you want.
+[654.92 --> 656.50]  $3,000 backup trip.
+[656.50 --> 660.78]  But, you know, so that's something we all struggle with.
+[660.78 --> 670.00]  But you remember when we went and saw Wendell, how he was implementing at his data center on his LAN, he was backing up his place was nuts.
+[670.12 --> 670.24]  Yeah.
+[670.30 --> 675.38]  And he was backing up his client's cloud data for them to his servers, just in case their cloud providers had issues.
+[676.10 --> 681.28]  It's something you do kind of have to think about is when I'm building something, what is the risk to losing this?
+[681.28 --> 688.70]  Like there's some things I have on the cloud that if they were lost, it'd be inconvenient, but we could regenerate from source material.
+[689.68 --> 690.50]  Not everything.
+[690.92 --> 691.00]  Yeah.
+[691.16 --> 698.28]  It is about evaluating the, I don't want to say like opportunity cost or whatever, but everything has a cost.
+[698.82 --> 702.76]  And, you know, photos, for example, are irreplaceable.
+[702.98 --> 705.28]  You can't recreate those moments, videos, whatever.
+[705.28 --> 717.66]  But, you know, a PDF with an invoice of some work you did 10 years ago, maybe that, okay, it might be nice to have it, but that's all just nice.
+[717.66 --> 738.84]  But, you know, the cost of a one-time backup offsite to a pen drive or something like that is so small compared to the amount, just the amount of time you're going to spend noodling after you've lost some data whilst you reconstruct what was actually on that file system and remember, oh yeah, that was on that box as well.
+[738.90 --> 739.82]  I lost that too.
+[740.06 --> 743.40]  And some of that stuff won't occur to you until years later.
+[743.82 --> 744.40]  That's very true.
+[744.40 --> 749.28]  And it feels so, you just feel like you've, like somebody's cut a hole out of you sometimes.
+[749.64 --> 759.40]  And I think that, especially when it comes to the pictures, I have opted to leave on for the iPhone members of my family our iCloud photo backup for everybody.
+[759.88 --> 762.70]  I even ended up paying for like some sort of family storage plan.
+[762.84 --> 772.32]  So that way I knew, because my mom's on there and, you know, my wife, and I just wanted to know that everybody's photos were backed up, even though I also back them up.
+[772.32 --> 782.32]  My phone, every picture I take goes off to Nextcloud in 100% quality, but Google Photos also duplicates everything.
+[782.68 --> 789.78]  I'm off the Google Photos sauce because I'm using the iCloud photo, but it's like, you know, trading one service for the other.
+[789.78 --> 798.10]  I mean, there are arguments to be made for Google's privacy policies versus Apple's, but I'm not sure I fully trust either, to be honest with you.
+[798.42 --> 799.12]  Yeah, yeah.
+[799.22 --> 803.36]  I mean, I'm kind of gambling that Apple's are a little better and that they're not mining it for data, but...
+[803.36 --> 804.42]  No, make no mistake, bro.
+[804.54 --> 806.18]  Apple are mining you for your cash.
+[806.44 --> 806.80]  Right.
+[807.00 --> 807.44]  No kidding.
+[807.66 --> 808.10]  No kidding.
+[808.10 --> 814.30]  And we have talked about Google Photos alternatives, and it's not that I'm not going to implement one of those.
+[814.34 --> 815.36]  That's actually been my intention.
+[815.90 --> 821.36]  But I still feel like I get some value out of just paying Apple to back that thing up because they are so valuable.
+[821.98 --> 823.52]  And that's really, photos are it.
+[823.72 --> 827.08]  Like, pretty much everything else, I'm comfortable how I back it up.
+[827.82 --> 830.44]  Although I know there's a couple of areas that I could probably do better.
+[830.64 --> 835.66]  I mean, do you feel like there's an area where if you were to audit your backups right now, you'd look at it and go, oh, no, Alex, you got to fix it.
+[835.66 --> 836.60]  Yeah, I do.
+[837.20 --> 840.32]  So the last couple of months have been a bit crazy for me.
+[840.38 --> 847.46]  My wife and I had our first daughter, and she came a little bit early, and she spent a couple of months in the hospital.
+[848.20 --> 851.56]  So things have kind of been decaying whilst I've been there.
+[852.06 --> 854.34]  Congratulations, an official on-show congratulations.
+[854.66 --> 854.86]  Yay.
+[855.92 --> 856.28]  Yay.
+[857.00 --> 859.98]  I've known, but this is the first time you've said anything on the show, so it's exciting.
+[859.98 --> 863.88]  Yeah, I didn't want to go public until she was home, just in case, because, anyway.
+[864.66 --> 868.64]  She's home, she's healthy, everything's good with the world.
+[869.02 --> 875.80]  So, yeah, I purchased the Helios as to be my on-site replication backup device.
+[875.96 --> 876.10]  Right.
+[876.10 --> 888.52]  And then when everything went down in January, and Ella was born, I was in the middle of rebuilding my server at that point, because that's when the whole GVTG thing started playing up and not working quite as I'd hoped.
+[888.68 --> 895.66]  So, you know, I was at the hospital most of the day, but I'd come back here for two or three hours just to unwind and just mess around with hardware and stuff.
+[895.66 --> 899.06]  And I never quite got to putting my backups back in place.
+[899.16 --> 902.24]  And it's one of those things you think, oh, I'll get to it, I'll get to it.
+[902.26 --> 906.00]  And then before you know it, a year later, you have a problem, you think, crap.
+[906.44 --> 907.20]  I never got to it.
+[908.56 --> 908.90]  Yeah.
+[908.90 --> 914.94]  I do have plans, which we'll share with you soon, as to what's going to replace the Helios in that situation.
+[915.20 --> 923.68]  But I'm tight-lipped for now, but we do have an upcoming segment on backups that will hopefully give you some ideas and inspiration.
+[923.68 --> 927.64]  Linode.com slash SSH.
+[927.72 --> 930.26]  Go there to get $100 in Linode credit.
+[930.36 --> 933.72]  This could be the opportunity to try out Linode.
+[933.82 --> 935.42]  Linode.com slash SSH.
+[935.56 --> 937.12]  You also support the show.
+[937.64 --> 939.48]  Linode is how we host in the cloud.
+[939.70 --> 944.78]  We've built all kinds of backend services for the show and for Jupyter Broadcasting on Linode.
+[944.78 --> 948.42]  And I have a peace of mind knowing that Linode has great support.
+[948.52 --> 952.46]  So if I ever get stuck, well, I know they're going to take care of me.
+[952.46 --> 961.78]  In fact, they just received, Linode just received the People's Choice Stevie Award for Favorite Customer Service in the Computer Services category.
+[962.24 --> 963.72]  That's huge, you guys.
+[963.96 --> 969.22]  Having great support has been one of the key things that people write into our show when they switch and tell us about Linode.
+[969.48 --> 971.36]  They have 11 data centers worldwide.
+[971.36 --> 980.54]  In 2016, they became their own ISP and have full control over their own network and have built out super fast connections to their worldwide data centers.
+[980.54 --> 986.90]  They have a brilliant cloud manager that makes it simple to use Linode if you're a brand new user or if you're a pro.
+[987.06 --> 988.30]  You're going to love what they have.
+[988.48 --> 989.40]  Then there's the pricing.
+[990.42 --> 992.66]  Linode has dialed this in.
+[992.80 --> 994.22]  The value is nuts.
+[994.58 --> 996.92]  They have systems, of course, are like $5 a month, right?
+[996.96 --> 999.80]  But you can do different combinations depending on what you need.
+[999.88 --> 1001.68]  Maybe you need a lot of memory or a lot of CPU.
+[1002.10 --> 1003.16]  Maybe you need GPU.
+[1003.28 --> 1004.56]  Maybe you need several GPUs.
+[1004.66 --> 1005.74]  Maybe you need it all.
+[1005.74 --> 1011.56]  I got to be honest, we recently just decided to go all in on our matrix server because it's getting busier and busier.
+[1012.12 --> 1013.82]  And it's awesome what Linode lets you do.
+[1013.92 --> 1020.16]  And even when you need to upgrade an existing machine or clone a machine or snapshot, it's all just brilliant in their cloud manager.
+[1020.28 --> 1025.16]  I'm really impressed with the complexity that they can make seem so simple.
+[1025.26 --> 1030.52]  You know, like I'm managing servers in data centers around the world and they just make it all seem so intuitive.
+[1030.52 --> 1031.68]  So I like that.
+[1031.74 --> 1034.90]  And you can really get a sense of that when you try out our $100 credit.
+[1035.00 --> 1039.38]  $100 when you go to linode.com slash SSH.
+[1039.54 --> 1040.82]  See what I've been talking about.
+[1040.96 --> 1042.80]  And, of course, you support the show.
+[1042.94 --> 1050.32]  When you go there and you visit that URL and you use that and you sign up, it tells Linode that our audience is supporting the show and that Linode should keep supporting us.
+[1050.38 --> 1052.02]  It helps us put these shows out for free.
+[1052.18 --> 1054.42]  It makes content like this possible.
+[1055.00 --> 1056.68]  It's the circle of podcasting.
+[1056.88 --> 1059.18]  Go to linode.com slash SSH.
+[1059.18 --> 1062.40]  Don't be using that stinking Linux unplugged Linode code.
+[1062.50 --> 1064.30]  You've got to be using that self-hosted Linode code.
+[1064.38 --> 1064.74]  That's right.
+[1065.00 --> 1065.46]  Live long.
+[1065.70 --> 1067.40]  So hashtag SSH.
+[1067.52 --> 1071.08]  Live long and go to linode.com slash SSH.
+[1073.00 --> 1076.64]  My home assistant box password shamed me this week.
+[1076.74 --> 1077.44]  Did you get this?
+[1077.68 --> 1078.10]  Yes.
+[1078.50 --> 1080.14]  Did you get it for the SSH add-in?
+[1080.38 --> 1081.44]  That's what I think I got it for.
+[1082.10 --> 1084.02]  Mine was node red, I think.
+[1084.68 --> 1085.96]  Oh, node red.
+[1086.10 --> 1089.16]  Alex, you're using a bad password with node red?
+[1089.84 --> 1090.16]  Oh my goodness.
+[1090.16 --> 1091.92]  Or maybe even home assistant itself?
+[1092.18 --> 1092.36]  Yeah.
+[1092.44 --> 1092.72]  I don't know.
+[1092.74 --> 1093.30]  I've been a bit busy.
+[1093.38 --> 1094.24]  I didn't actually read it.
+[1094.76 --> 1097.22]  I just saw the notification and dismissed it.
+[1097.26 --> 1097.96]  I was like, oh, whatever.
+[1098.04 --> 1098.72]  I'll get to you later.
+[1098.86 --> 1100.38]  I dismissed it and then mine came back.
+[1100.50 --> 1106.74]  Mine is for the add-on core underscore SSH, which uses secrets, which have been detected as not secure.
+[1107.40 --> 1110.02]  Probably a lot of people in the audience are getting this if they run home assistant.
+[1110.02 --> 1113.02]  It's a new feature, quote unquote, that has been integrated.
+[1113.78 --> 1116.00]  And frankly, probably a good one.
+[1116.00 --> 1119.26]  Yeah, but the internet being the internet, people are pissed.
+[1119.78 --> 1122.12]  I don't really get this.
+[1122.36 --> 1126.38]  Maybe I'm just becoming a grumpy old man now I'm a dad.
+[1127.08 --> 1131.38]  And outrage culture is just, I don't know, I'm just tired of it.
+[1131.38 --> 1138.70]  So there's a link in the show notes to a post by Troy Hunt, who is an incredibly well-respected security researcher.
+[1139.18 --> 1142.68]  And he's the guy that is behind the website, Have I Been Pwned?
+[1142.68 --> 1145.28]  And this website is incredible.
+[1145.40 --> 1153.04]  You can tap in any password into their database and it'll tell you that, yes, this password is out in the wild.
+[1153.36 --> 1161.96]  And as Troy puts it, if your password is in this list, I've seen it clear text, which means that the bad guys have seen it clear text.
+[1161.96 --> 1162.44]  Right.
+[1162.70 --> 1171.72]  So no matter your opinion on how secure you think it is, I guarantee it's out there in the wild somewhere and somebody knows what it is.
+[1171.76 --> 1173.40]  So don't use that password.
+[1173.62 --> 1176.72]  It's actually pretty clever for the home assistant developers to build this in.
+[1176.76 --> 1179.90]  So the way it works is your passwords are hashed.
+[1180.30 --> 1188.60]  The first five characters of that hash, so just the first five characters of a hash of your password, are then used to query the Have I Been Pwned website.
+[1188.60 --> 1192.70]  It then returns a result of possible password hashes that match.
+[1193.26 --> 1197.88]  And then home assistant checks that list against your hash locally.
+[1198.10 --> 1201.34]  All of that validation is happening on your box.
+[1201.88 --> 1214.84]  And what I found really interesting, and Troy goes into full details in the article, he basically goes through the home assistant forums thread where people are bitching and moaning and whining about this feature being turned on without their permission.
+[1214.84 --> 1224.66]  To give you an idea of how, I don't want to say stupid, but honestly, when I was reading this Troy Hunt article, I was like, yeah, this thread is stupid.
+[1225.48 --> 1229.14]  Someone was complaining it was sending out data over their metered connection.
+[1229.40 --> 1229.50]  Right.
+[1229.60 --> 1232.96]  He then proceeded to say it's a few bytes.
+[1233.32 --> 1234.72]  Like 36 kilobytes, you know?
+[1235.00 --> 1235.28]  Yeah.
+[1235.48 --> 1239.24]  We're talking five times smaller than the average web page load.
+[1239.42 --> 1242.12]  If you notice that on a metered connection, then you've got problems.
+[1242.54 --> 1242.74]  Right.
+[1242.74 --> 1244.60]  We're not really talking very much data.
+[1244.80 --> 1250.86]  And it's probably, although we don't know for sure, only happening when you start up home assistant or reload the config.
+[1251.54 --> 1254.34]  How do you feel about doing this on your local LAN?
+[1254.42 --> 1257.94]  I mean, I'm definitely guilty of reusing passwords on the internet.
+[1258.58 --> 1260.90]  I'm certainly guilty of doing it on my LAN.
+[1261.28 --> 1265.60]  That seems to be the crux of everyone's argument is my LAN, my rules.
+[1265.60 --> 1272.10]  I have a safe, trusted environment, and I don't want to have to use good password hygiene.
+[1272.30 --> 1274.54]  I don't want long passwords that are unique.
+[1274.54 --> 1277.70]  And I can definitely relate.
+[1278.40 --> 1284.52]  There's sort of, when you do this for a living, every now and then it's nice to be a little lazy.
+[1285.04 --> 1289.90]  Like, you know, what's the saying about the guy who makes shoes, his kids always have the worst shoes?
+[1290.54 --> 1291.30]  You know?
+[1291.66 --> 1294.80]  Like, because you just get home, it's the last thing you want to do, right?
+[1294.84 --> 1295.84]  It's just the last thing.
+[1296.08 --> 1296.28]  Yeah.
+[1296.28 --> 1298.08]  So I do understand that.
+[1298.26 --> 1301.20]  However, this is where I fall down on it.
+[1301.70 --> 1311.16]  The home assistant community is kind of a special case because they're playing around with IoT smart devices that are network connected.
+[1312.20 --> 1319.08]  There's a higher threat level, a broader threat attack surface, if you will.
+[1319.14 --> 1325.28]  And so I feel like you have to be a little more secure when you are willing to ride the IoT train, you know?
+[1325.28 --> 1330.26]  Because the problem is any one of those individual devices one day could become compromised.
+[1330.54 --> 1333.98]  And then that becomes a launching off point where they can go after other devices on your LAN.
+[1334.04 --> 1335.34]  And we see it happen.
+[1335.84 --> 1342.18]  And to that point, Troy actually makes this point in his article that LinkedIn, I mean, we're talking a proper website here,
+[1343.06 --> 1348.64]  had a data breach because one of their developers' home networks had a weak SSH password,
+[1348.64 --> 1356.04]  which allowed people to pivot through that developer's home network into LinkedIn servers and compromise LinkedIn that way.
+[1356.48 --> 1357.82]  Yeah, they brute forced his iMac.
+[1357.96 --> 1363.58]  And so, you know, I put myself in that developer's shoes and I think, well, holy crap, someone could pivot into Red Hat from here.
+[1363.62 --> 1364.94]  And I wouldn't want that.
+[1365.12 --> 1368.96]  So I think to myself, OK, actually, Troy, you've probably got a point here.
+[1369.00 --> 1370.74]  I do need to step up my game.
+[1370.74 --> 1372.72]  And he uses 1Password.
+[1372.82 --> 1374.80]  I think he's on the advisory board for 1Password.
+[1375.02 --> 1377.66]  But we talked last episode about Bitwarden.
+[1378.20 --> 1385.34]  And I really cannot emphasize enough, you know, there are command line clients and stuff like that that you can use.
+[1385.38 --> 1388.98]  So you can put it in scripts and do all sorts of fun stuff if you want to.
+[1389.10 --> 1399.78]  And I think that's going to have to become a 2021 rather late New Year's resolution for me is to try and use that CLI stuff more on my LAN at least.
+[1399.78 --> 1404.22]  Yeah, good passwords, I think, matter when we're kind of riding the cutting edge of technology.
+[1404.22 --> 1411.94]  Even if you're not intentionally exposing your LAN to the Internet, you never know when some crazy thing could happen.
+[1412.30 --> 1413.78]  It's unlikely, but it could happen.
+[1413.98 --> 1424.82]  But really, you also never know if one day somebody's going to be able to rock up onto your Wi-Fi or something or somebody joins your LAN that you put on intentionally, but they have some misconfiguration or infection.
+[1424.82 --> 1430.32]  So it's kind of like multiple layers of protecting yourself is the best kind of protection.
+[1430.58 --> 1438.78]  And I think when you look at logins, you could look at maybe not only unique passwords, but when possible, also using keys to do SSH sign-ins.
+[1438.98 --> 1440.80]  So that way you have to have maybe a key and a password.
+[1441.18 --> 1442.98]  And that just takes it a little bit step further.
+[1442.98 --> 1451.64]  Like that LinkedIn developer, if he had had a decent password or password and a key, then the attackers would have never gotten onto his iMac and then never gotten into LinkedIn.
+[1452.12 --> 1465.80]  And when the whole COVID lockdown thing started and we had a lot more people all of a sudden working from home, that was one of my first concerns is, well, now all of these corporations are as insecure as people's home networks are.
+[1465.80 --> 1468.46]  And you never know when that could be an issue as well.
+[1468.60 --> 1475.92]  I just think as much of a pain in the arse as it is, there's enough tools and we know enough information now that it's worth doing.
+[1476.22 --> 1483.10]  The only thing I would have changed with how Home Assistant has implemented this is give me an option to turn it off for a bit.
+[1483.82 --> 1486.16]  You know, I'm not fixing it while I'm out here in the woods.
+[1486.94 --> 1490.32]  Silence that checkbox for seven days or something, you know.
+[1490.56 --> 1493.38]  Or until next update even, you know, that could work too.
+[1493.38 --> 1497.86]  I do believe they're actually working on making it opt-in or opt-out now.
+[1498.38 --> 1503.54]  So for what it's worth, the outrage has had some effect on the feature.
+[1504.24 --> 1505.44]  But I mean, I think it's great.
+[1505.56 --> 1510.76]  I think anything that we can do, and here's another point about the Home Assistant community being a special case as well,
+[1511.48 --> 1517.98]  is a lot of people are coming to servers for the first time because of Home Assistant.
+[1517.98 --> 1522.78]  They're running a box in their house for the first time that's got SSH listening on something.
+[1523.38 --> 1524.90]  Maybe for the first time ever.
+[1525.84 --> 1533.60]  And anything that Home Assistant can do for those kind of newer users that aren't, you know,
+[1534.00 --> 1541.10]  enterprise-grade buffoons like me that just reminds them that, hold on, you know,
+[1541.14 --> 1546.02]  if you're exposing your house to the internet through Nebukassar, through WireGuard,
+[1546.16 --> 1548.86]  through whatever it might be, there is some risk.
+[1548.86 --> 1555.28]  And then when you couple that up with some leaky washing machine that's running an old firmware from eight years ago,
+[1556.14 --> 1557.62]  there are risks to these things.
+[1557.68 --> 1562.00]  And I, for one, applaud the Home Assistant project for having the stones to put this in.
+[1562.00 --> 1562.36]  Yeah.
+[1562.66 --> 1568.00]  And it definitely, I think, will improve the community security overall, which is a good thing for them.
+[1568.56 --> 1572.96]  And as they make this a commercial product one day, because you know this has got to be the direction this thing's going,
+[1573.04 --> 1579.54]  when they try to make it a consumer product and not just a, you know, a more advanced prosumer or enthusiast product.
+[1579.84 --> 1580.52]  Nerd product.
+[1580.84 --> 1581.54]  Go on, you should say it.
+[1581.66 --> 1582.20]  Nerd product.
+[1582.48 --> 1583.58]  It's a nerd product right now.
+[1583.58 --> 1589.24]  But one day, maybe one day they're going to try to sell it to average Joes who have bought all these smart devices.
+[1589.24 --> 1591.26]  And now they just need something to make it all work together.
+[1591.72 --> 1594.30]  And, you know, buy the $100 Home Assistant appliance.
+[1594.60 --> 1596.22]  And you need these kind of things built in.
+[1596.70 --> 1600.76]  And they just recently had a run-in with add-ons that were leaking information.
+[1600.76 --> 1603.04]  So I could see why this is an area they're investing into.
+[1603.50 --> 1604.52]  And I say good on them.
+[1604.68 --> 1606.42]  And I think it'll be a smooth transition.
+[1606.42 --> 1614.08]  There is also something worth looking into is they're working with K-Anonemy, which is a Cloudflare-hosted service.
+[1614.30 --> 1617.62]  So Cloudflare is kind of proxying some of these requests to anonymize them.
+[1617.92 --> 1620.74]  That's also made some people uncomfortable in all of this.
+[1621.18 --> 1622.54]  But I did a read-through of the setup.
+[1622.66 --> 1626.08]  And it actually, it seems like they've done a really, really solid job here.
+[1626.20 --> 1632.08]  So we'll have a link in the show notes at selfhosted.show.40 for the Cloudflare information on that.
+[1632.08 --> 1637.48]  And if that has also perhaps gotten the hairs on the back of your neck up a little bit, it's worth reading about.
+[1637.56 --> 1638.26]  We'll have information.
+[1638.80 --> 1643.48]  I'm super curious to hear what you all do for your local LAN password situations.
+[1643.64 --> 1644.80]  Do you use a password manager?
+[1645.38 --> 1648.78]  Are you like me and reuse the same password on every box?
+[1649.66 --> 1650.16]  Let us know.
+[1650.38 --> 1651.82]  Selfhosted.show slash contact.
+[1653.68 --> 1656.34]  Datadog.com slash selfhosted.
+[1656.44 --> 1656.80]  One word.
+[1656.94 --> 1659.08]  Datadog.com slash selfhosted.
+[1659.20 --> 1659.92]  Go there.
+[1660.16 --> 1660.68]  Try it out.
+[1660.86 --> 1661.90]  And get a free T-shirt.
+[1662.52 --> 1665.36]  Datadog is going to solve problems and help you communicate them.
+[1665.56 --> 1668.56]  Analyze code level performance across your entire environment.
+[1668.96 --> 1672.22]  And troubleshoot issues faster with Datadog.
+[1672.56 --> 1678.44]  You see, Datadog's continuous profiler automatically collects information from your production servers all the time.
+[1678.44 --> 1683.84]  So then, when you're ready, when you need to, you can quickly look and analyze all of the data with minimal overhead.
+[1684.24 --> 1689.58]  And get, finally, a unified picture of your entire environment.
+[1689.58 --> 1697.00]  Correlate code performance with server metrics and other monitoring data in real-time, beautiful dashboards.
+[1697.42 --> 1699.24]  Datadog.com slash selfhosted.
+[1699.24 --> 1701.08]  Just to look at these dashboards.
+[1701.08 --> 1712.04]  And then they have a lot of tightly integrated additions, add-ons, tracing, log management, and that continuous profiler that brings it all into one platform.
+[1712.04 --> 1713.04]  That's Datadog.
+[1713.38 --> 1718.74]  And imagine getting yourself a visual dashboard that you can use to communicate issues with your team.
+[1719.12 --> 1720.36]  Developers to sysadmins.
+[1720.60 --> 1722.18]  Sysadmins to executives.
+[1722.66 --> 1723.54]  Make plans.
+[1723.86 --> 1725.20]  Predict future performance.
+[1725.82 --> 1726.62]  Try it all out.
+[1726.62 --> 1729.30]  And take advantage of their machine learning alerting.
+[1729.86 --> 1733.96]  Datadog enables you to pinpoint the root cause of an issue faster than ever.
+[1733.96 --> 1740.56]  So try their products out for free for 14 days by visiting datadog.com slash selfhosted.
+[1740.66 --> 1745.56]  For a limited time, if you start a trial and create one dashboard, you'll get some free swag.
+[1745.68 --> 1746.56]  A Datadog t-shirt.
+[1747.06 --> 1748.40]  And I miss swag.
+[1748.68 --> 1750.06]  I miss event swag.
+[1750.42 --> 1751.26]  I miss t-shirts.
+[1751.78 --> 1752.44]  So go get one.
+[1752.52 --> 1754.16]  Datadog.com slash selfhosted.
+[1754.20 --> 1754.62]  Great account.
+[1754.62 --> 1755.90]  Get that trial going.
+[1755.98 --> 1756.54]  Get a t-shirt.
+[1757.12 --> 1760.70]  And then begin visualizing your entire infrastructure.
+[1761.04 --> 1763.14]  Datadog.com slash selfhosted.
+[1765.10 --> 1766.52]  Listener Chris writes in,
+[1766.64 --> 1770.14]  I run a number of services from my home server that are internet facing.
+[1770.50 --> 1774.66]  I understand that the smart best practice is to minimize that as much as possible.
+[1774.66 --> 1777.66]  But some of these things I want to access whilst I'm away from the house.
+[1778.16 --> 1780.24]  Some of them are also used by family members.
+[1780.32 --> 1782.68]  And so it's unavoidable on some levels.
+[1782.94 --> 1784.08]  My question is this.
+[1784.08 --> 1789.82]  How do I know if a service is hardened enough to raw dog it out on the open internet?
+[1790.28 --> 1790.60]  Wow.
+[1791.80 --> 1793.96]  We're just going to let's let that sit for a second.
+[1795.16 --> 1795.96]  How do you know?
+[1796.10 --> 1797.44]  How do you know if you can raw dog it?
+[1798.06 --> 1798.40]  Yeah.
+[1798.50 --> 1802.14]  I mean, I feel this one, you know, Plex is one, you know, Plex you kind of feel safe about.
+[1802.22 --> 1806.04]  But how do you know about some of the lesser used ones like subsonic or something?
+[1806.12 --> 1806.32]  Right.
+[1806.32 --> 1810.20]  I think it's safe to assume that everything is porous.
+[1811.20 --> 1811.56]  Everything.
+[1812.06 --> 1812.34]  Yeah.
+[1812.34 --> 1815.30]  I hate, though, that the answer always is put it behind a VPN.
+[1815.76 --> 1815.98]  Why?
+[1816.16 --> 1820.22]  I mean, with WireGuard these days, it's really the barrier to entry.
+[1820.34 --> 1822.32]  As long as you don't screw up your subnets like I did.
+[1823.22 --> 1824.62]  The barrier is pretty low.
+[1824.78 --> 1828.92]  But you have friends and family that are using your Plex server without connecting to WireGuard.
+[1829.26 --> 1830.72]  You know, like Plex is such a great example.
+[1830.72 --> 1834.36]  Or Jellyfin because you do often want to share with others.
+[1834.62 --> 1834.98]  That's true.
+[1835.18 --> 1838.50]  And I could see that being true with others as well.
+[1838.90 --> 1840.48]  Nextcloud he mentions in here.
+[1840.66 --> 1843.66]  But BabyBuddy, I'm not so sure about that.
+[1843.78 --> 1845.44]  You know, that starts to get a little more niche.
+[1846.36 --> 1850.20]  And I hate to be the guy that just says, well, if it's big, you can use it publicly.
+[1850.30 --> 1851.76]  And if it's small, you should hide it.
+[1851.84 --> 1855.28]  But that's kind of a general rule of thumb that I follow.
+[1855.88 --> 1857.62]  You know, you try to figure how many eyes have been on it.
+[1857.62 --> 1861.02]  You know, another angle to consider is security by obscurity.
+[1861.72 --> 1867.38]  Now, if you think that, you know, you just have a random URL that you're using to access this service.
+[1867.58 --> 1869.14]  And you've put it behind a reverse proxy.
+[1869.58 --> 1873.60]  And probably these days you're using Let's Encrypt to generate a certificate for it.
+[1873.64 --> 1875.30]  So that you know that things are secure.
+[1876.12 --> 1877.48]  Well, I've got bad news for you, I'm afraid.
+[1877.54 --> 1881.96]  If you go to crt.sh and type in your domain name.
+[1881.96 --> 1889.48]  You'll see every single certificate that's ever been issued by Let's Encrypt for your domain name.
+[1890.10 --> 1899.26]  And so you think to yourself, okay, well now my super secret string that I came up with to hide this service is now out in the public domain.
+[1899.38 --> 1901.82]  So really, it's not secret at all.
+[1901.82 --> 1906.14]  One thing you could do to kind of work around that is use a wildcard certificate.
+[1907.02 --> 1908.98]  That would kind of sort of help.
+[1909.52 --> 1912.48]  Because it wouldn't, you know, publish the actual string.
+[1913.40 --> 1919.92]  But it just goes to show to me that, you know, security through obscurity is really not, it's an illusion.
+[1919.92 --> 1929.96]  Yeah, and I was going to suggest throwing it out on like a VPS like Linode and run your software there for a bit on the public internet and monitor the logs.
+[1930.10 --> 1933.20]  But you could run something for six months and nobody nibbles at it.
+[1933.28 --> 1938.14]  And then on, you know, day one of seven months, somebody nibbles on it.
+[1938.56 --> 1939.78]  It's tricky that way.
+[1939.78 --> 1949.38]  And so it really, the only way to have full peace of mind, and that's what I've opted to do here in Lady Joops, is just to have absolutely zero outside inbound.
+[1949.92 --> 1954.02]  It's the only way I've found to be completely comfortable with it.
+[1954.12 --> 1963.50]  I don't necessarily always follow that rule myself because some services like mail servers, web servers, media streaming servers, they have to be public by their very nature.
+[1963.78 --> 1969.42]  So you have to hope that those just have more eyes and that they get a little more attention and that they've been a little more audited.
+[1969.76 --> 1972.18]  But remember, logging is your friend.
+[1972.40 --> 1975.94]  So if you ever suspect something weird is happening, go check your logs.
+[1976.00 --> 1977.12]  See if you have weird logins.
+[1977.12 --> 1979.30]  See if you have somebody hitting your website all the time.
+[1979.30 --> 1980.36]  Use Datadog.
+[1980.68 --> 1980.94]  Yeah.
+[1981.26 --> 1981.58]  Yeah.
+[1981.62 --> 1983.60]  Use something that will go through there and alert you.
+[1983.72 --> 1985.22]  That absolutely could be a good way to go.
+[1985.72 --> 1989.78]  It's a good question, though, listener Chris, because I'm sure it's one that people struggle with.
+[1989.82 --> 1991.48]  So let us know what you out there would do.
+[1991.96 --> 1993.68]  Self-hosted.show slash contact.
+[1993.68 --> 1996.36]  Now, we have Joseph who writes in.
+[1996.42 --> 2001.28]  He says, I have a bunch of those Tekken smart switches flashed with Tasmoto and they work great.
+[2001.66 --> 2005.04]  I have a need for smart switches to replace my wall switches, though.
+[2005.40 --> 2010.22]  You know, for example, like my kids' closet lights, which are always left on.
+[2010.22 --> 2021.38]  I would also love to replace the controllers on our ceiling fans with smart devices, something that would toggle the light on and off and also set the fan to high, medium or low or even off completely.
+[2021.60 --> 2026.76]  My preference would be for something I can self-host, non-cloud connected, open source software.
+[2026.76 --> 2032.02]  Are there any devices which would actually fill this need or similar to the way the Tekken smart plugs do?
+[2032.32 --> 2032.88]  What are your thoughts?
+[2033.36 --> 2034.46]  Well, this is an easy question.
+[2035.00 --> 2038.62]  The Shelly devices are exactly what you're looking for.
+[2038.70 --> 2040.50]  And I think we've talked about them on a previous episode.
+[2040.76 --> 2047.32]  But just to recap, they're about the size of an Oreo cookie and they go inside the light box behind the switch.
+[2047.46 --> 2049.06]  So you don't change the switch itself.
+[2049.52 --> 2054.42]  But this little cookie size box has a relay inside it.
+[2054.84 --> 2056.30]  You need to do a little bit of wiring.
+[2056.30 --> 2057.76]  So, you know, mains voltage.
+[2058.16 --> 2060.88]  Be careful or get an electrician if you're not comfortable.
+[2061.62 --> 2062.64]  They make a few products.
+[2062.74 --> 2067.62]  So they make a 2.5, which will let you do up to two switches in the same box.
+[2068.16 --> 2070.32]  They make a single unit as well.
+[2070.46 --> 2074.98]  And they make a bunch of other stuff that does like rolling shutters for garage doors and all sorts of stuff.
+[2075.50 --> 2078.54]  So go to Shelly.cloud and check out their stuff if you're interested.
+[2078.74 --> 2080.44]  But it's exactly what you're looking for.
+[2080.70 --> 2082.72]  And you can put TAS motor on them.
+[2083.34 --> 2085.06]  So Mahendra writes in.
+[2085.06 --> 2088.98]  In the latest episode, you suggest file run for a simple file browser.
+[2089.40 --> 2093.00]  I wanted to suggest another minimalist alternative.
+[2093.40 --> 2100.36]  It's very light with no database required at github.com slash file browser slash file browser.
+[2100.60 --> 2101.86]  God, that rolls off the tongue, doesn't it?
+[2102.28 --> 2102.96]  It's very simple.
+[2103.06 --> 2103.58]  Easy to remember.
+[2104.08 --> 2104.30]  Yeah.
+[2104.36 --> 2108.76]  It is just a web-based file browser that sits on top of a directory.
+[2108.92 --> 2110.30]  Each user gets their own directory.
+[2110.30 --> 2112.42]  And it's just a standalone app.
+[2113.08 --> 2113.84]  Pretty simple.
+[2114.36 --> 2114.96]  I like it.
+[2115.22 --> 2117.16]  Even easier than the one we had talked about before.
+[2117.46 --> 2119.16]  So I'm going to think I'm going to grab this and try it out.
+[2119.64 --> 2120.16]  It is nice.
+[2120.34 --> 2121.58]  Yeah, I tried it out before the show.
+[2121.84 --> 2125.24]  And I kind of wish I hadn't bothered with file run now.
+[2125.40 --> 2132.46]  This is, I think, my new standard kind of throw it up and forget about it remote access software.
+[2132.46 --> 2133.72]  So, yeah, great job.
+[2133.78 --> 2134.66]  Thanks for writing in, Mahendra.
+[2135.50 --> 2139.54]  Now, I've mentioned Chowdown a couple of times on the show before as a self-hosted recipe app.
+[2139.78 --> 2140.50]  I still use it.
+[2140.56 --> 2141.26]  I still love it.
+[2141.34 --> 2145.52]  It stores all of my recipes in clear text files on disk.
+[2145.72 --> 2146.96]  But there are some alternatives.
+[2147.48 --> 2149.72]  And we've had a couple of listeners write in.
+[2150.08 --> 2152.22]  And one of them is called Tandoor Recipes.
+[2152.28 --> 2153.14]  What do you think of this one, Chris?
+[2153.36 --> 2154.66]  It looks really good.
+[2154.66 --> 2164.50]  And this, if anything, would probably get me to start doing something like this because it has a planning aspect, which is useful for a guy like me.
+[2164.56 --> 2168.40]  I can do a little meal planning, but also has a sharing feature.
+[2168.64 --> 2174.46]  And it's all on a progressive web app, which means my wife and I could share it like on our phones, which I think would be really nice.
+[2174.46 --> 2179.50]  And then the other thing I would need is, and it does support importing from Chowdown, is import.
+[2179.60 --> 2187.56]  And it has Chowdown import as well as Nextcloud cookbook import, Mealy, paprika, saffron, and a couple of others it can import from.
+[2188.22 --> 2190.46]  I think it's easy to try out.
+[2190.96 --> 2197.60]  Now, we have mentioned this one previously because it goes by the name vabeen1111 slash recipes on GitHub.
+[2197.84 --> 2199.12]  That's the repo it's in.
+[2199.76 --> 2201.88]  I think the Tandoor name must be new.
+[2201.88 --> 2204.30]  I don't know how old exactly it is.
+[2204.46 --> 2206.64]  Yeah, it is a new release too.
+[2206.80 --> 2208.32]  So that might be maybe they did a name change.
+[2208.62 --> 2210.66]  But they are using mkdocs for their documentation.
+[2211.18 --> 2212.74]  So I've got to give them a plus point for that.
+[2213.18 --> 2219.46]  Yeah, it says here that they're happy to announce they've released a new version, which gives the application its well-deserved name and logo, Tandoor recipes.
+[2219.62 --> 2220.18]  So there you go.
+[2220.60 --> 2222.62]  It runs out of a Docker container.
+[2222.90 --> 2225.38]  It will also run on Unraid, Synology, Kubernetes.
+[2225.74 --> 2227.74]  You can do it manually as well if you want to.
+[2228.40 --> 2232.36]  There's a bunch of interesting stuff about syncing and storage in their documentation.
+[2232.36 --> 2237.88]  So it's going to take a lot for me to throw away Chowdown because I do genuinely really like it.
+[2237.96 --> 2241.68]  And I've modified the CSS so I've got some fuzzy search.
+[2241.74 --> 2243.10]  You know how I love my fuzzy search.
+[2243.24 --> 2244.00]  Oh, that's cool.
+[2244.28 --> 2246.08]  You know, I've customized Chowdown for my own needs.
+[2246.54 --> 2248.92]  But then maybe the grass is greener.
+[2248.94 --> 2250.04]  Maybe I should try this one out.
+[2250.46 --> 2252.24]  I mean, it does have the import functionality.
+[2252.24 --> 2254.94]  Downside, though, is it needs a Postgres database.
+[2255.42 --> 2260.88]  And I've already got, like, it feels like a dozen different database containers running.
+[2260.96 --> 2262.14]  Do I need another one?
+[2262.62 --> 2265.44]  That is a constant internal battle.
+[2265.62 --> 2267.70]  And sometimes I'm just down to, ah, who cares?
+[2267.80 --> 2268.64]  Just run a whole bunch.
+[2268.72 --> 2269.56]  You've got the resources.
+[2269.70 --> 2273.60]  And other times, like the sysadmin in me is just not having it.
+[2274.12 --> 2277.18]  It's just you can't run three copies of Postgres.
+[2277.30 --> 2278.20]  That doesn't make any sense.
+[2278.28 --> 2279.00]  They're different versions.
+[2279.08 --> 2281.44]  They have different security issues, different features.
+[2281.44 --> 2282.22]  What are you doing?
+[2282.82 --> 2284.44]  And it's a recipes app at the end of the day.
+[2284.76 --> 2285.90]  Like, you know what I mean?
+[2286.08 --> 2291.90]  Just having the files in clear text on disk feels more future-proof to me.
+[2292.04 --> 2297.54]  So if this person loses interest in maintaining this particular app for whatever reason,
+[2297.78 --> 2300.64]  I'm not up the creek without a paddle, so to speak.
+[2300.64 --> 2302.22]  That, I think, is a great feature of Chowdown.
+[2302.66 --> 2306.14]  That kind of clear text back end gives me peace of mind.
+[2306.34 --> 2307.10]  That's just it.
+[2307.22 --> 2308.50]  Peace of mind for that kind of stuff.
+[2308.86 --> 2311.04]  And if Chowdown stops working for some reason,
+[2311.04 --> 2314.10]  I can just pull it up in any text editor and it's still readable.
+[2314.52 --> 2317.24]  Yeah, it's almost as good as writing them down on an index card.
+[2318.52 --> 2320.08]  You know, you laugh at that.
+[2320.18 --> 2324.56]  But I'm pretty sure if I asked my mom to go and find me a recipe for something,
+[2325.36 --> 2328.12]  she would find it in less time than it takes me to fix.
+[2328.58 --> 2329.90]  Oh, Chowdown's not working?
+[2330.06 --> 2334.20]  Okay, well, let me just SSH in and do this, do that, do the other.
+[2334.70 --> 2336.04]  And before you know it, 10 minutes later,
+[2336.04 --> 2338.10]  you've forgotten that you're actually looking for a recipe,
+[2338.10 --> 2340.12]  and then you go and order pizza instead, so.
+[2341.42 --> 2344.08]  Yeah, and meanwhile, she's got the index card ready to go.
+[2344.18 --> 2344.84]  It's very true.
+[2345.04 --> 2345.96]  There's something to that.
+[2346.64 --> 2350.08]  A reminder, you can find our sponsor, our Cloud Guru, on social media.
+[2350.22 --> 2351.66]  They're just slash a Cloud Guru.
+[2351.82 --> 2353.68]  It's really easy, like on Twitter, Facebook, YouTube,
+[2353.98 --> 2355.50]  pretty much all the social media platforms.
+[2355.80 --> 2357.16]  Just slash a Cloud Guru.
+[2357.66 --> 2358.62]  Also, our members.
+[2358.86 --> 2361.64]  Thank you to our members, selfhosted.show slash SRE.
+[2361.78 --> 2362.64]  You support the show.
+[2363.20 --> 2365.00]  You become our site reliability engineers.
+[2365.00 --> 2367.76]  You get a limited ad feed and extra content.
+[2368.20 --> 2369.34]  The post show.
+[2369.92 --> 2371.52]  Selfhosted.show slash SRE.
+[2371.72 --> 2373.64]  If you'd like to support the show and become a member.
+[2374.16 --> 2375.64]  My Wisecam 3 came in this week,
+[2375.70 --> 2377.26]  so we're going to have a little chat about that today.
+[2377.36 --> 2378.64]  Yes, that's going to be the post show.
+[2378.68 --> 2380.46]  I ordered a few of them, so I got thoughts.
+[2380.60 --> 2381.14]  Of course you did.
+[2383.06 --> 2385.32]  So you can go to selfhosted.show slash contact,
+[2385.60 --> 2387.28]  and that's the place to go to get in touch with us.
+[2387.52 --> 2390.56]  You can find me on Twitter at Ironic Badger.
+[2390.56 --> 2393.26]  Oh, I'm there as well, at Chris Elias,
+[2393.38 --> 2395.68]  and the show is at selfhosted.show.
+[2395.98 --> 2398.20]  On Discord, I'm at AlexKTZ.
+[2398.62 --> 2400.00]  So thanks very much for listening, everybody.
+[2400.26 --> 2402.68]  That was selfhosted.show slash 40.

40： Password Shaming _transcript_corrected.txt

@@ -0,0 +1,654 @@
+[0.00 → 6.50] Coming up on the show, we react to Home Assistant password shaming both of us and then attempt to solve an age-old cloud problem.
+[7.28 → 8.50] Backups. I'm Chris.
+[8.94 → 10.50] And I'm Alex, and this is Self-Hosted.
+[11.72 → 14.16] The podcast is a middle-aged man now. We're 40.
+[15.08 → 21.22] Yeah, the podcast is feeling like he's still got some pet left in him, but also has a few miles on him. Or her.
+[21.46 → 22.74] Midlife crisis coming up.
+[23.26 → 27.36] Is the podcast, does it have a gender? It's a thing, right?
+[27.36 → 29.46] The podcast prefers to be referred to as them.
+[30.00 → 35.02] Podcast pronouns.
+[35.88 → 37.52] There's a title right there, I'll tell you what.
+[38.08 → 41.72] Anyway, you were going to tell me about your off-grid solar stuff. We've not heard about that for a while.
+[42.26 → 47.88] We were chatting about this just before we hit record because I'm off-grid and podcasting on solar right now.
+[48.22 → 50.64] I was just talking to you, actually, because you're thinking about getting solar.
+[50.64 → 56.22] And I think the thing that people have to wrap their head around is, what are you planning for?
+[56.28 → 58.68] Are you planning for a grid blackout or brownout?
+[58.68 → 61.24] Are you planning for going out into the woods?
+[61.70 → 62.94] What's your scenario?
+[62.94 → 68.26] And then how much battery do you really need versus could you supplement with a generator?
+[68.26 → 77.40] Like, for me right now, I think I've hit a sweet spot of enough battery capacity that I can run on it for a day or so.
+[77.54 → 82.10] And if it's a sunny day out, I can get a 30%, 40% charge right now in the winter.
+[82.46 → 85.34] But I can't get 100% charge off of solar right now.
+[85.34 → 91.44] And so I need to run the generator for about an hour once a day right now when I'm off-grid.
+[92.34 → 93.48] And that's fine.
+[93.58 → 98.22] I feel like that's actually a perfect spot because the more battery you have, the more generator or solar you're going to need.
+[99.02 → 100.90] You can't, you know, you can't charge all.
+[100.96 → 102.94] You have to have the ability to charge all that stuff up.
+[103.08 → 107.72] So I feel like I've kind of hit the sweet spot that because it's winter, you know, we're not getting prime sunshine.
+[107.72 → 110.56] And I'm only running the generator about once a day.
+[110.78 → 112.76] And otherwise, we're getting along.
+[112.90 → 114.42] I think I'm kind of in that sweet spot.
+[114.50 → 120.16] And I think that's something you should think about when you're specking out your solar system for your house is what are you covering for?
+[120.24 → 122.30] Are you covering for a couple of days of no power?
+[122.46 → 124.64] Or do you really just need to cover for a couple of hours?
+[125.18 → 128.02] And if it goes longer, maybe you could run a generator for an hour or two.
+[128.48 → 133.50] I think I want to cover just the average daily low-level load of the house.
+[133.50 → 134.94] I want to make the house more sustainable.
+[134.94 → 141.08] So, you know, like just all the lighting, all the computers that are on in here, whatever that works out to be.
+[141.76 → 146.28] My electric bill is normally in a sort of $100 to $120-ish range.
+[146.36 → 147.32] So it's not too crazy.
+[148.36 → 150.78] And for me, it's about sustainability.
+[151.16 → 155.46] And I was watching a David Attenborough program, Our Perfect Planet, the other night.
+[155.80 → 158.90] Beautiful 4K HDR on the LG OLED.
+[159.28 → 161.52] Oh, it was magical to watch that thing.
+[161.82 → 162.90] Streaming from the Plex server.
+[163.28 → 163.60] Correct.
+[163.60 → 165.30] Yeah, through the Nvidia shield.
+[166.06 → 176.44] You can't help but watch these perfect planet things and be left with a sense of guilt about what humanity is doing to the planet and how we're consuming too many resources and stuff like that.
+[176.58 → 189.10] So, you know, I think about how I might be in a position to do something about that as just an individual when in reality we need to, as a species, collectively actually affect change.
+[189.10 → 191.66] But as an individual, there isn't much I can do.
+[191.66 → 197.14] But reducing my use of fossil fuels, even by a little bit, feels like a good place to start.
+[197.40 → 202.64] Yeah, I love the idea of even just offsetting the computers that run all the time.
+[202.64 → 206.26] So, during the day, I've reached the point where all day long I'm running off the solar power.
+[206.38 → 215.74] I'm bringing in more solar power than I am using, which is a great spot to be because that means my home server, all my stuff is being sustained by the sun.
+[215.74 → 220.92] And I'd love to do a similar setup at the studio, a couple of panels on the roof.
+[220.98 → 227.82] If I could just bring in, you know, 400 watts or so, I could probably cover most of my computer gear that's running 24-7.
+[227.82 → 236.70] And, you know, I think about long-term, Alex, say even just 10 years, 15 years down the road, maybe the majority of cars or all cars sold will be electric.
+[237.28 → 244.88] How does the grid in the United States, at least, handle that if we don't have some people offsetting their load with solar?
+[245.02 → 252.94] It seems like long-term, the direction things are going between crypto mining and electric cars, there's going to be more demand on the grid than ever.
+[252.94 → 260.12] So, being able to supplement a little bit might not only just be a nice thing to do for the environment, but also ensure that you have enough power to go around.
+[260.78 → 261.50] Free Bitcoin, baby.
+[262.06 → 262.24] Yep.
+[262.34 → 263.36] Get that crypto going.
+[263.94 → 266.10] And maybe, maybe spend your time learning.
+[266.22 → 268.52] This episode is brought to you by the all-new A Cloud Guru.
+[268.72 → 272.96] They are the leader in learning for the cloud, Linux, and other modern tech skills.
+[273.14 → 273.62] Go check them out.
+[273.66 → 276.24] They have hundreds of courses and thousands of hands-on labs.
+[276.34 → 276.70] Get certified.
+[276.86 → 277.26] Get hired.
+[277.68 → 280.28] Get learning at acloudguru.com.
+[280.28 → 287.24] You could spend that time mining crypto, or you could spend that time learning job skills and getting hired.
+[287.62 → 297.32] But, you know, I think maybe you and I are thinking about off-grid and backup power today because a lot of our listener services are down and offline as we record this right now.
+[297.74 → 298.08] That's right.
+[298.18 → 298.30] Yeah.
+[298.46 → 304.60] OVH, one of the largest VPS providers in Europe, have suffered a major fire this week.
+[304.60 → 316.64] And it's taken, literally taken out one of their data centres and had dramatic effects on some of their other regions, data centres, whatever they called for OVH as well.
+[317.36 → 319.42] It's just got me thinking, great.
+[319.62 → 322.16] There's another disaster that I hadn't really thought about.
+[322.24 → 325.50] What if AWS or DigitalOcean or Linde, what if they catch fire?
+[325.50 → 327.68] Oh, that's another one to plan for.
+[329.12 → 335.40] Yeah, the thing that's tricky about OVH is data centres one through four were all kind of like in the same area.
+[335.84 → 341.86] So after midnight on the Wednesday of the week we're recording this, OVH cloud had an alarm go off.
+[342.24 → 344.82] The cause as of this recording right now is still unknown.
+[344.82 → 350.16] However, the founder and CEO speculated it may have been a UPS fire.
+[350.34 → 358.90] And he noted in a video update that he released a couple of days ago that UPS number seven had been serviced earlier that day.
+[358.98 → 361.70] But obviously more investigation is required.
+[362.02 → 366.38] In total, OVH had four data centres in this area and one data centre.
+[366.78 → 370.76] SBG two was just totally destroyed by fire.
+[370.76 → 375.40] And then part of SBG one was also damaged.
+[375.54 → 378.22] And then SBG three and four, they're fine.
+[378.40 → 383.44] But as we record, there are still some outages because there are some areas the staff can't get to.
+[383.52 → 384.68] There's network issue.
+[384.94 → 386.64] There are still some power issues.
+[386.64 → 392.56] And there's even the fact that they still have to validate that the cooling system is still fully functional.
+[392.90 → 394.56] It's like bad, Alex.
+[394.56 → 406.88] This is a weird one to me because every data centre that I've worked near or in some occasions, they've all had argon fire suppressant systems.
+[406.88 → 414.92] And just fire was something that you kind of assumed would never get out of control in a data centre because it's a controlled environment.
+[415.42 → 419.56] There isn't a huge amount of flammable stuff like on a data centre floor.
+[419.86 → 423.44] It's just metal boxes with some cables and stuff like that, essentially.
+[423.44 → 424.04] Yeah.
+[424.28 → 426.98] So it's kind of surprising to me that it was able to get to this level.
+[427.10 → 432.44] I mean, if you look at some of the pictures, and we've got a Reuters article linked in the show notes, that building was toast.
+[433.20 → 433.54] Yeah.
+[433.58 → 442.84] The CEO says something about it using older style construction techniques and that the newer buildings that weren't damaged were using the newer style.
+[443.04 → 447.78] I wonder if that style is fire suppression, you know.
+[447.96 → 448.60] Yeah, maybe.
+[448.92 → 450.30] Or materials or something.
+[450.30 → 454.94] But it kind of got us thinking like, you know, we got kind of a sad note in from listener.
+[455.04 → 458.62] Kerry said, my server was in data centre one and I have lost it.
+[458.68 → 467.80] I'm afraid I didn't have any complete backups because I didn't really have anywhere to back up to that server already blew my personal self-hosting budget.
+[468.46 → 470.88] I feel like I've lost a loved one.
+[471.52 → 474.44] I guess I'll get a box at home, and I'll have to back up to that from now on.
+[474.44 → 476.64] But that's going to get very expensive.
+[477.42 → 478.12] That is tricky.
+[478.12 → 479.08] Well, it is.
+[479.40 → 480.82] It is going to get expensive.
+[481.40 → 486.62] But I would argue that the emotions you're feeling right now are also expensive.
+[487.18 → 491.48] Just in a, you know, not dollars and cents necessarily, but they're expensive in a different way emotionally.
+[492.50 → 496.44] And only you can quantify how much your data is worth.
+[496.44 → 504.78] I mean, I don't know what was on this particular server for you, Kerry, but I certainly know in the past when I've lost data, it hurts.
+[505.20 → 516.68] Genuinely, you spend the next few weeks, months, sometimes longer wishing you'd done things differently, thinking, oh, if only I'd spent a couple of hundreds on a Pi and an external hard drive.
+[516.68 → 519.30] And I wouldn't even be in this situation.
+[520.56 → 530.24] I mean, if you think about what most typical VPSs are, they are probably less than a hundred gig disk, probably only a few gigabytes of RAM or something like that.
+[530.32 → 533.84] So we aren't talking about a huge amount of data to back up here.
+[534.32 → 541.80] And what I would say is if you've got no backup, I mean, literally zero, don't try and aim for perfect.
+[541.80 → 553.66] Just get a 128 gig USB stick off Amazon and then just get in the habit of downloading your data once a month, once a year even.
+[553.94 → 559.84] Because I'm sure right now you wish you'd had something, even if it was 11 months old, you'd have something.
+[559.84 → 571.82] Something I've seen really common is a lot of people these days, when they have cheap cloud hosting, they're going for like a NFC with a disk hanging off it or something that they're syncing too locally.
+[572.04 → 576.72] And getting that peace of mind by having the data on their local network.
+[576.72 → 583.72] And I got to admit, it's kind of what I did for the Jupyter Broadcasting stuff is we have Nextcloud up at Linde.
+[583.88 → 589.82] And then we have Nextcloud installed on the server at the Jupyter Broadcasting Studio on the LAN.
+[590.22 → 593.48] And we sync the stuff that I really care about.
+[593.58 → 596.02] We don't sync everything because it's hundreds of gigs.
+[596.32 → 600.42] But locally, we actually will also archive.
+[600.62 → 603.88] So I should probably back up the studio server now that I think about it.
+[603.88 → 609.10] But we back up the cloud locally to anything that's not ephemeral.
+[609.36 → 611.22] And anything that's not ephemeral, we try to keep locally.
+[611.46 → 615.14] And then my intention is to back that server up somewhere.
+[616.00 → 618.70] Alex's house, Back blaze, I don't know what.
+[618.88 → 620.86] But I've got the cloud part covered.
+[621.16 → 623.98] I just don't necessarily have the local part fully covered right now.
+[624.18 → 629.94] Because I ended up, and this is sort of where I connected with what Carrie was saying, is I just ended up with terabytes of data.
+[630.60 → 630.92] Terabytes.
+[630.92 → 634.66] And I don't know, I don't really know how to even get that offsite over the wire.
+[634.76 → 635.32] It's so much data.
+[636.14 → 644.08] Never underestimate, I think the saying goes, the bandwidth of a truck driving down a highway full of hard drives.
+[644.74 → 646.72] Get it on a hard drive and mail it to me.
+[646.82 → 647.72] That's the best way.
+[647.94 → 652.04] What you're saying is I should pack up the RV and drive a hard drive down to your place.
+[652.62 → 653.90] That makes the most sense, right?
+[653.94 → 654.76] You can if you want.
+[654.92 → 656.50] $3,000 backup trip.
+[656.50 → 660.78] But, you know, so that's something we all struggle with.
+[660.78 → 670.00] But you remember when we went and saw Wendell, how he was implementing at his data centre on his LAN, he was backing up his place was nuts.
+[670.12 → 670.24] Yeah.
+[670.30 → 675.38] And he was backing up his client's cloud data for them to his servers, just in case their cloud providers had issues.
+[676.10 → 681.28] It's something you do kind of have to think about is when I'm building something, what is the risk to losing this?
+[681.28 → 688.70] Like there are some things I have on the cloud that if they were lost, it'd be inconvenient, but we could regenerate from source material.
+[689.68 → 690.50] Not everything.
+[690.92 → 691.00] Yeah.
+[691.16 → 698.28] It is about evaluating the I don't want to say like opportunity cost or whatever, but everything has a cost.
+[698.82 → 702.76] And, you know, photos, for example, are irreplaceable.
+[702.98 → 705.28] You can't recreate those moments, videos, whatever.
+[705.28 → 717.66] But, you know, a PDF with an invoice for some work you did 10 years ago, maybe that, okay, it might be nice to have it, but that's all just nice.
+[717.66 → 738.84] But, you know, the cost of a one-time backup offsite to a pen drive or something like that is so small compared to the amount, just the amount of time you're going to spend noodling after you've lost some data whilst you reconstruct what was actually on that file system and remember, oh yeah, that was on that box as well.
+[738.90 → 739.82] I lost that too.
+[740.06 → 743.40] And some of that stuff won't occur to you until years later.
+[743.82 → 744.40] That's very true.
+[744.40 → 749.28] And it feels so, you just feel like you've, like somebody's cut a hole out of you sometimes.
+[749.64 → 759.40] And I think that, especially when it comes to the pictures, I have opted to leave on for the iPhone members of my family our iCloud photo backup for everybody.
+[759.88 → 762.70] I even ended up paying for like some sort of family storage plan.
+[762.84 → 772.32] So that way I knew, because my mom's on there and, you know, my wife, and I just wanted to know that everybody's photos were backed up, even though I also back them up.
+[772.32 → 782.32] My phone, every picture I take goes off to Nextcloud in 100% quality, but Google Photos also duplicates everything.
+[782.68 → 789.78] I'm off the Google Photos sauce because I'm using the iCloud photo, but it's like, you know, trading one service for the other.
+[789.78 → 798.10] I mean, there are arguments to be made for Google's privacy policies versus Apple's, but I'm not sure if I fully trust either, to be honest with you.
+[798.42 → 799.12] Yeah, yeah.
+[799.22 → 803.36] I mean, I'm kind of gambling that Apple's are a little better and that they're not mining it for data, but...
+[803.36 → 804.42] No, make no mistake, bro.
+[804.54 → 806.18] Apple are mining you for your cash.
+[806.44 → 806.80] Right.
+[807.00 → 807.44] No kidding.
+[807.66 → 808.10] No kidding.
+[808.10 → 814.30] And we have talked about Google Photos alternatives, and it's not that I'm not going to implement one of those.
+[814.34 → 815.36] That's actually been my intention.
+[815.90 → 821.36] But I still feel like I get some value out of just paying Apple to back that thing up because they are so valuable.
+[821.98 → 823.52] And that's really, photos are it.
+[823.72 → 827.08] Like, pretty much everything else, I'm comfortable how I back it up.
+[827.82 → 830.44] Although I know there are a couple of areas that I could probably do better.
+[830.64 → 835.66] I mean, do you feel like there's an area where if you were to audit your backups right now, you'd look at it and go, oh, no, Alex, you got to fix it.
+[835.66 → 836.60] Yeah, I do.
+[837.20 → 840.32] So the last couple of months have been a bit crazy for me.
+[840.38 → 847.46] My wife and I had our first daughter, and she came a little bit early, and she spent a couple of months in the hospital.
+[848.20 → 851.56] So things have kind of been decaying whilst I've been there.
+[852.06 → 854.34] Congratulations, an official on-show congratulations.
+[854.66 → 854.86] Yay.
+[855.92 → 856.28] Yay.
+[857.00 → 859.98] I've known, but this is the first time you've said anything on the show, so it's exciting.
+[859.98 → 863.88] Yeah, I didn't want to go public until she was home, just in case, because, anyway.
+[864.66 → 868.64] She's home, she's healthy, everything's good with the world.
+[869.02 → 875.80] So, yeah, I purchased the Helios as to be my on-site replication backup device.
+[875.96 → 876.10] Right.
+[876.10 → 888.52] And then when everything went down in January, and Ella was born, I was in the middle of rebuilding my server at that point, because that's when the whole GVTG thing started playing up and not working quite as I'd hoped.
+[888.68 → 895.66] So, you know, I was at the hospital most of the day, but I'd come back here for two or three hours just to unwind and just mess around with hardware and stuff.
+[895.66 → 899.06] And I never quite got to putting my backups back in place.
+[899.16 → 902.24] And it's one of those things you think, oh, I'll get to it, I'll get to it.
+[902.26 → 906.00] And then before you know it, a year later, you have a problem, you think, crap.
+[906.44 → 907.20] I never got to it.
+[908.56 → 908.90] Yeah.
+[908.90 → 914.94] I do have plans, which we'll share with you soon, as to what's going to replace the Helios in that situation.
+[915.20 → 923.68] But I'm tight-lipped for now, but we do have an upcoming segment on backups that will hopefully give you some ideas and inspiration.
+[923.68 → 927.64] Linode.com slash SSH.
+[927.72 → 930.26] Go there to get $100 in Linde credit.
+[930.36 → 933.72] This could be the opportunity to try out Linde.
+[933.82 → 935.42] Linode.com slash SSH.
+[935.56 → 937.12] You also support the show.
+[937.64 → 939.48] Linde is how we host in the cloud.
+[939.70 → 944.78] We've built all kinds of backend services for the show and for Jupyter Broadcasting on Linde.
+[944.78 → 948.42] And I have a peace of mind knowing that Linde has great support.
+[948.52 → 952.46] So if I ever get stuck, well, I know they're going to take care of me.
+[952.46 → 961.78] In fact, they just received, Linde just received the People's Choice Stevie Award for Favourite Customer Service in the Computer Services category.
+[962.24 → 963.72] That's huge, you guys.
+[963.96 → 969.22] Having great support has been one of the key things that people write into our show when they switch and tell us about Linde.
+[969.48 → 971.36] They have 11 data centres worldwide.
+[971.36 → 980.54] In 2016, they became their own ISP and have full control over their own network and have built out superfast connections to their worldwide data centres.
+[980.54 → 986.90] They have a brilliant cloud manager that makes it simple to use Linde if you're a brand-new user or if you're a pro.
+[987.06 → 988.30] You're going to love what they have.
+[988.48 → 989.40] Then there's the pricing.
+[990.42 → 992.66] Linde has dialled this in.
+[992.80 → 994.22] The value is nuts.
+[994.58 → 996.92] They have systems, of course, are like $5 a month, right?
+[996.96 → 999.80] But you can do different combinations depending on what you need.
+[999.88 → 1001.68] Maybe you need a lot of memory or a lot of CPU.
+[1002.10 → 1003.16] Maybe you need GPU.
+[1003.28 → 1004.56] Maybe you need several GPUs.
+[1004.66 → 1005.74] Maybe you need it all.
+[1005.74 → 1011.56] I got to be honest, we recently just decided to go all in on our matrix server because it's getting busier and busier.
+[1012.12 → 1013.82] And it's awesome what Linde lets you do.
+[1013.92 → 1020.16] And even when you need to upgrade an existing machine or clone a machine or snapshot, it's all just brilliant in their cloud manager.
+[1020.28 → 1025.16] I'm really impressed with the complexity that they can make seem so simple.
+[1025.26 → 1030.52] You know, like I'm managing servers in data centres around the world, and they just make it all seem so intuitive.
+[1030.52 → 1031.68] So I like that.
+[1031.74 → 1034.90] And you can really get a sense of that when you try out our $100 credit.
+[1035.00 → 1039.38] $100 when you go to linode.com slash SSH.
+[1039.54 → 1040.82] See what I've been talking about.
+[1040.96 → 1042.80] And, of course, you support the show.
+[1042.94 → 1050.32] When you go there, and you visit that URL and you use that, and you sign up, it tells Linde that our audience is supporting the show and that Linde should keep supporting us.
+[1050.38 → 1052.02] It helps us put these shows out for free.
+[1052.18 → 1054.42] It makes content like this possible.
+[1055.00 → 1056.68] It's the circle of podcasting.
+[1056.88 → 1059.18] Go to linode.com slash SSH.
+[1059.18 → 1062.40] Don't be using that stinking Linux unplugged Linde code.
+[1062.50 → 1064.30] You've got to be using that self-hosted Linde code.
+[1064.38 → 1064.74] That's right.
+[1065.00 → 1065.46] Live long.
+[1065.70 → 1067.40] So hashtag SSH.
+[1067.52 → 1071.08] Live long and go to linode.com slash SSH.
+[1073.00 → 1076.64] My home assistant box password shamed me this week.
+[1076.74 → 1077.44] Did you get this?
+[1077.68 → 1078.10] Yes.
+[1078.50 → 1080.14] Did you get it for the SSH add-in?
+[1080.38 → 1081.44] That's what I think I got it for.
+[1082.10 → 1084.02] Mine was node red, I think.
+[1084.68 → 1085.96] Oh, node red.
+[1086.10 → 1089.16] Alex, you're using a bad password with node red?
+[1089.84 → 1090.16] Oh my goodness.
+[1090.16 → 1091.92] Or maybe even home assistant itself?
+[1092.18 → 1092.36] Yeah.
+[1092.44 → 1092.72] I don't know.
+[1092.74 → 1093.30] I've been a bit busy.
+[1093.38 → 1094.24] I didn't actually read it.
+[1094.76 → 1097.22] I just saw the notification and dismissed it.
+[1097.26 → 1097.96] I was like, oh, whatever.
+[1098.04 → 1098.72] I'll get to you later.
+[1098.86 → 1100.38] I dismissed it and then mine came back.
+[1100.50 → 1106.74] Mine is for the add-on core underscore SSH, which uses secrets, which have been detected as not secure.
+[1107.40 → 1110.02] Probably a lot of people in the audience are getting this if they run home assistant.
+[1110.02 → 1113.02] It's a new feature, quote unquote, that has been integrated.
+[1113.78 → 1116.00] And frankly, probably a good one.
+[1116.00 → 1119.26] Yeah, but the internet being the internet, people are pissed.
+[1119.78 → 1122.12] I don't really get this.
+[1122.36 → 1126.38] Maybe I'm just becoming a grumpy old man now I'm a dad.
+[1127.08 → 1131.38] And outrage culture is just, I don't know, I'm just tired of it.
+[1131.38 → 1138.70] So there's a link in the show notes to a post by Troy Hunt, who is an incredibly well-respected security researcher.
+[1139.18 → 1142.68] And he's the guy that is behind the website, Have I Been Pwned?
+[1142.68 → 1145.28] And this website is incredible.
+[1145.40 → 1153.04] You can tap in any password into their database, and it'll tell you that, yes, this password is out in the wild.
+[1153.36 → 1161.96] And as Troy puts it, if your password is in this list, I've seen it clear text, which means that the bad guys have seen it clear text.
+[1161.96 → 1162.44] Right.
+[1162.70 → 1171.72] So no matter your opinion on how secure you think it is, I guarantee it's out there in the wild somewhere and somebody knows what it is.
+[1171.76 → 1173.40] So don't use that password.
+[1173.62 → 1176.72] It's actually pretty clever for the home assistant developers to build this in.
+[1176.76 → 1179.90] So the way it works is your passwords are hashed.
+[1180.30 → 1188.60] The first five characters of that hash, so just the first five characters of a hash of your password, are then used to query the Have I Been Pwned website.
+[1188.60 → 1192.70] It then returns a result of possible password hashes that match.
+[1193.26 → 1197.88] And then home assistant checks that list against your hash locally.
+[1198.10 → 1201.34] All of that validation is happening on your box.
+[1201.88 → 1214.84] And what I found fascinating, and Troy goes into full details in the article, he basically goes through the home assistant forums thread where people are bitching and moaning and whining about this feature being turned on without their permission.
+[1214.84 → 1224.66] To give you an idea of how, I don't want to say stupid, but honestly, when I was reading this Troy Hunt article, I was like, yeah, this thread is stupid.
+[1225.48 → 1229.14] Someone was complaining it was sending out data over their metered connection.
+[1229.40 → 1229.50] Right.
+[1229.60 → 1232.96] He then proceeded to say it's a few bytes.
+[1233.32 → 1234.72] Like 36 kilobytes, you know?
+[1235.00 → 1235.28] Yeah.
+[1235.48 → 1239.24] We're talking five times smaller than the average web page load.
+[1239.42 → 1242.12] If you notice that on a metered connection, then you've got problems.
+[1242.54 → 1242.74] Right.
+[1242.74 → 1244.60] We're not really talking very much data.
+[1244.80 → 1250.86] And it's probably, although we don't know for sure, only happening when you start up home assistant or reload the config.
+[1251.54 → 1254.34] How do you feel about doing this on your local LAN?
+[1254.42 → 1257.94] I mean, I'm definitely guilty of reusing passwords on the internet.
+[1258.58 → 1260.90] I'm certainly guilty of doing it on my LAN.
+[1261.28 → 1265.60] That seems to be the crux of everyone's argument is my LAN, my rules.
+[1265.60 → 1272.10] I have a safe, trusted environment, and I don't want to have to use good password hygiene.
+[1272.30 → 1274.54] I don't want long passwords that are unique.
+[1274.54 → 1277.70] And I can definitely relate.
+[1278.40 → 1284.52] There's sort of, when you do this for a living, every now, and then it's nice to be a little lazy.
+[1285.04 → 1289.90] Like, you know, what's the saying about the guy who makes shoes, his kids always have the worst shoes?
+[1290.54 → 1291.30] You know?
+[1291.66 → 1294.80] Like, because you just get home, it's the last thing you want to do, right?
+[1294.84 → 1295.84] It's just the last thing.
+[1296.08 → 1296.28] Yeah.
+[1296.28 → 1298.08] So I do understand that.
+[1298.26 → 1301.20] However, this is where I fall down on it.
+[1301.70 → 1311.16] The home assistant community is kind of a special case because they're playing around with IoT smart devices that are network connected.
+[1312.20 → 1319.08] There's a higher threat level, a broader threat attack surface, if you will.
+[1319.14 → 1325.28] And so I feel like you have to be a little more secure when you are willing to ride the IoT train, you know?
+[1325.28 → 1330.26] Because the problem is any one of those individual devices one day could become compromised.
+[1330.54 → 1333.98] And then that becomes a launching off point where they can go after other devices on your LAN.
+[1334.04 → 1335.34] And we see it happen.
+[1335.84 → 1342.18] And to that point, Troy actually makes this point in his article that LinkedIn, I mean, we're talking a proper website here,
+[1343.06 → 1348.64] had a data breach because one of their developers' home networks had a weak SSH password,
+[1348.64 → 1356.04] which allowed people to pivot through that developer's home network into LinkedIn servers and compromise LinkedIn that way.
+[1356.48 → 1357.82] Yeah, they brute forced his iMac.
+[1357.96 → 1363.58] And so, you know, I put myself in that developer's shoes and I think, well, holy crap, someone could pivot into Red Hat from here.
+[1363.62 → 1364.94] And I wouldn't want that.
+[1365.12 → 1368.96] So I think to myself, OK, actually, Troy, you've probably got a point here.
+[1369.00 → 1370.74] I do need to step up my game.
+[1370.74 → 1372.72] And he uses 1Password.
+[1372.82 → 1374.80] I think he's on the advisory board for 1Password.
+[1375.02 → 1377.66] But we talked last episode about Bitwarden.
+[1378.20 → 1385.34] And I really cannot emphasize enough, you know, there are command line clients and stuff like that you can use.
+[1385.38 → 1388.98] So you can put it in scripts and do all sorts of fun stuff if you want to.
+[1389.10 → 1399.78] And I think that's going to have to become a 2021 rather late New Year's resolution for me is to try and use that CLI stuff more on my LAN at least.
+[1399.78 → 1404.22] Yeah, good passwords, I think, matter when we're kind of riding the cutting edge of technology.
+[1404.22 → 1411.94] Even if you're not intentionally exposing your LAN to the Internet, you never know when some crazy thing could happen.
+[1412.30 → 1413.78] It's unlikely, but it could happen.
+[1413.98 → 1424.82] But really, you also never know if one day somebody's going to be able to rock up onto your Wi-Fi or something or somebody joins your LAN that you put on intentionally, but they have some misconfiguration or infection.
+[1424.82 → 1430.32] So it's kind of like multiple layers of protecting yourself is the best kind of protection.
+[1430.58 → 1438.78] And I think when you look at logins, you could look at maybe not only unique passwords, but when possible, also using keys to do SSH sign-ins.
+[1438.98 → 1440.80] So that way you have to have maybe a key and a password.
+[1441.18 → 1442.98] And that just takes it a little bit step further.
+[1442.98 → 1451.64] Like that LinkedIn developer, if he had had a decent password or password and a key, then the attackers would have never gotten onto his iMac and then never gotten into LinkedIn.
+[1452.12 → 1465.80] And when the whole COVID lockdown thing started, and we had a lot more people all of a sudden working from home, that was one of my first concerns is, well, now all of these corporations are as insecure as people's home networks are.
+[1465.80 → 1468.46] And you never know when that could be an issue as well.
+[1468.60 → 1475.92] I just think as much of a pain in the arse as it is, there are enough tools, and we know enough information now that it's worth doing.
+[1476.22 → 1483.10] The only thing I would have changed with how Home Assistant has implemented this is give me an option to turn it off for a bit.
+[1483.82 → 1486.16] You know, I'm not fixing it while I'm out here in the woods.
+[1486.94 → 1490.32] Silence that checkbox for seven days or something, you know.
+[1490.56 → 1493.38] Or until next update even, you know, that could work too.
+[1493.38 → 1497.86] I do believe they're actually working on making it opt-in or opt-out now.
+[1498.38 → 1503.54] So for what it's worth, the outrage has had some effect on the feature.
+[1504.24 → 1505.44] But I mean, I think it's great.
+[1505.56 → 1510.76] I think anything that we can do, and here's another point about the Home Assistant community being a special case as well,
+[1511.48 → 1517.98] is a lot of people are coming to servers for the first time because of Home Assistant.
+[1517.98 → 1522.78] They're running a box in their house for the first time that's got SSH listening on something.
+[1523.38 → 1524.90] Maybe for the first time ever.
+[1525.84 → 1533.60] And anything that Home Assistant can do for this kind of newer users that aren't, you know,
+[1534.00 → 1541.10] enterprise-grade buffoons like me that just reminds them that, hold on, you know,
+[1541.14 → 1546.02] if you're exposing your house to the internet through Nebukassar, through WireGuard,
+[1546.16 → 1548.86] through whatever it might be, there is some risk.
+[1548.86 → 1555.28] And then when you couple that up with some leaky washing machine that's running an old firmware from eight years ago,
+[1556.14 → 1557.62] there are risks to these things.
+[1557.68 → 1562.00] And I, for one, applaud the Home Assistant project for having the stones to put this in.
+[1562.00 → 1562.36] Yeah.
+[1562.66 → 1568.00] And it definitely, I think, will improve the community security overall, which is a good thing for them.
+[1568.56 → 1572.96] And as they make this a commercial product one day, because you know this has got to be the direction this thing's going,
+[1573.04 → 1579.54] when they try to make it a consumer product and not just a, you know, a more advanced prosumer or enthusiast product.
+[1579.84 → 1580.52] Nerd product.
+[1580.84 → 1581.54] Go on, you should say it.
+[1581.66 → 1582.20] Nerd product.
+[1582.48 → 1583.58] It's a nerd product right now.
+[1583.58 → 1589.24] But one day, maybe one day they're going to try to sell it to average Joes who have bought all these smart devices.
+[1589.24 → 1591.26] And now they just need something to make it all work together.
+[1591.72 → 1594.30] And, you know, buy the $100 Home Assistant appliance.
+[1594.60 → 1596.22] And you need this kind of things built in.
+[1596.70 → 1600.76] And they just recently had a run-in with add-ons that were leaking information.
+[1600.76 → 1603.04] So I could see why this is an area they're investing into.
+[1603.50 → 1604.52] And I say good on them.
+[1604.68 → 1606.42] And I think it'll be a smooth transition.
+[1606.42 → 1614.08] There is also something worth looking into is they're working with K-Annecy, which is a Cloudflare-hosted service.
+[1614.30 → 1617.62] So Cloudflare is kind of proxying some of these requests to anonymize them.
+[1617.92 → 1620.74] That's also made some people uncomfortable in all of this.
+[1621.18 → 1622.54] But I did a read-through of the setup.
+[1622.66 → 1626.08] And it actually, it seems like they've done a really, really solid job here.
+[1626.20 → 1632.08] So we'll have a link in the show notes at self-hosted.show.40 for the Cloudflare information on that.
+[1632.08 → 1637.48] And if that has also perhaps gotten the hairs on the back of your neck up a little bit, it's worth reading about.
+[1637.56 → 1638.26] We'll have information.
+[1638.80 → 1643.48] I'm super curious to hear what you all do for your local LAN password situations.
+[1643.64 → 1644.80] Do you use a password manager?
+[1645.38 → 1648.78] Are you like me and reuse the same password on every box?
+[1649.66 → 1650.16] Let us know.
+[1650.38 → 1651.82] Self-hosted. Show slash contact.
+[1653.68 → 1656.34] Datadog.com slash self-hosted.
+[1656.44 → 1656.80] One word.
+[1656.94 → 1659.08] Datadog.com slash self-hosted.
+[1659.20 → 1659.92] Go there.
+[1660.16 → 1660.68] Try it out.
+[1660.86 → 1661.90] And get a free T-shirt.
+[1662.52 → 1665.36] Datadog is going to solve problems and help you communicate them.
+[1665.56 → 1668.56] Analyze code level performance across your entire environment.
+[1668.96 → 1672.22] And troubleshoot issues faster with Datadog.
+[1672.56 → 1678.44] You see, Datadog's continuous profiler automatically collects information from your production servers all the time.
+[1678.44 → 1683.84] So then, when you're ready, when you need to, you can quickly look and analyze all the data with minimal overhead.
+[1684.24 → 1689.58] And get, finally, a unified picture of your entire environment.
+[1689.58 → 1697.00] Correlate code performance with server metrics and other monitoring data in real-time, beautiful dashboards.
+[1697.42 → 1699.24] Datadog.com slash self-hosted.
+[1699.24 → 1701.08] Just to look at these dashboards.
+[1701.08 → 1712.04] And then they have a lot of tightly integrated additions, add-ons, tracing, log management, and that continuous profiler that brings it all into one platform.
+[1712.04 → 1713.04] That's Datadog.
+[1713.38 → 1718.74] And imagine getting yourself a visual dashboard that you can use to communicate issues with your team.
+[1719.12 → 1720.36] Developers to sysadmins.
+[1720.60 → 1722.18] Sysadmins to executives.
+[1722.66 → 1723.54] Make plans.
+[1723.86 → 1725.20] Predict future performance.
+[1725.82 → 1726.62] Try it all out.
+[1726.62 → 1729.30] And take advantage of their machine learning alerting.
+[1729.86 → 1733.96] Datadog enables you to pinpoint the root cause of an issue faster than ever.
+[1733.96 → 1740.56] So try their products out for free for 14 days by visiting datadog.com slash self-hosted.
+[1740.66 → 1745.56] For a limited time, if you start a trial and create one dashboard, you'll get some free swag.
+[1745.68 → 1746.56] A Datadog t-shirt.
+[1747.06 → 1748.40] And I miss swag.
+[1748.68 → 1750.06] I miss event swag.
+[1750.42 → 1751.26] I miss t-shirts.
+[1751.78 → 1752.44] So go get one.
+[1752.52 → 1754.16] Datadog.com slash self-hosted.
+[1754.20 → 1754.62] Great account.
+[1754.62 → 1755.90] Get that trial going.
+[1755.98 → 1756.54] Get a t-shirt.
+[1757.12 → 1760.70] And then begin visualizing your entire infrastructure.
+[1761.04 → 1763.14] Datadog.com slash self-hosted.
+[1765.10 → 1766.52] Listener Chris writes in,
+[1766.64 → 1770.14] I run a number of services from my home server that are internet facing.
+[1770.50 → 1774.66] I understand that the smart best practice is to minimize that as much as possible.
+[1774.66 → 1777.66] But some of these things I want to access whilst I'm away from the house.
+[1778.16 → 1780.24] Some of them are also used by family members.
+[1780.32 → 1782.68] And so it's unavoidable on some levels.
+[1782.94 → 1784.08] My question is this.
+[1784.08 → 1789.82] How do I know if a service is hardened enough to raw dog it out on the open internet?
+[1790.28 → 1790.60] Wow.
+[1791.80 → 1793.96] We're just going to let's let that sit for a second.
+[1795.16 → 1795.96] How do you know?
+[1796.10 → 1797.44] How do you know if you can raw dog it?
+[1798.06 → 1798.40] Yeah.
+[1798.50 → 1802.14] I mean, I feel this one, you know, Plex is one, you know, Plex you kind of feel safe about.
+[1802.22 → 1806.04] But how do you know about some of the lesser used ones like subsonic or something?
+[1806.12 → 1806.32] Right.
+[1806.32 → 1810.20] I think it's safe to assume that everything is porous.
+[1811.20 → 1811.56] Everything.
+[1812.06 → 1812.34] Yeah.
+[1812.34 → 1815.30] I hate, though, that the answer always is put it behind a VPN.
+[1815.76 → 1815.98] Why?
+[1816.16 → 1820.22] I mean, with WireGuard these days, it's really the barrier to entry.
+[1820.34 → 1822.32] As long as you don't screw up your subnets like I did.
+[1823.22 → 1824.62] The barrier is pretty low.
+[1824.78 → 1828.92] But you have friends and family that are using your Plex server without connecting to WireGuard.
+[1829.26 → 1830.72] You know, like Plex is such a great example.
+[1830.72 → 1834.36] Or Jellyfin because you do often want to share with others.
+[1834.62 → 1834.98] That's true.
+[1835.18 → 1838.50] And I could see that being true with others as well.
+[1838.90 → 1840.48] Nextcloud he mentions in here.
+[1840.66 → 1843.66] But Baby Buddy, I'm not so sure about that.
+[1843.78 → 1845.44] You know, that starts to get a little more niche.
+[1846.36 → 1850.20] And I hate to be the guy that just says, well, if it's big, you can use it publicly.
+[1850.30 → 1851.76] And if it's small, you should hide it.
+[1851.84 → 1855.28] But that's kind of a general rule of thumb that I follow.
+[1855.88 → 1857.62] You know, you try to figure how many eyes have been on it.
+[1857.62 → 1861.02] You know, another angle to consider is security by obscurity.
+[1861.72 → 1867.38] Now, if you think that, you know, you just have a random URL that you're using to access this service.
+[1867.58 → 1869.14] And you've put it behind a reverse proxy.
+[1869.58 → 1873.60] And probably these days you're using Let's Encrypt to generate a certificate for it.
+[1873.64 → 1875.30] So that you know that things are secure.
+[1876.12 → 1877.48] Well, I've got bad news for you, I'm afraid.
+[1877.54 → 1881.96] If you go to crt.sh and type in your domain name.
+[1881.96 → 1889.48] You'll see every single certificate that's ever been issued by Let's Encrypt for your domain name.
+[1890.10 → 1899.26] And so you think to yourself, okay, well now my super secret string that I came up with to hide this service is now out in the public domain.
+[1899.38 → 1901.82] So really, it's not secret at all.
+[1901.82 → 1906.14] One thing you could do to kind of work around that is use a wildcard certificate.
+[1907.02 → 1908.98] That would kind of sort of help.
+[1909.52 → 1912.48] Because it wouldn't, you know, publish the actual string.
+[1913.40 → 1919.92] But it just goes to show to me that, you know, security through obscurity is really not, it's an illusion.
+[1919.92 → 1929.96] Yeah, and I was going to suggest throwing it out on like a VPS like Linde and run your software there for a bit on the public internet and monitor the logs.
+[1930.10 → 1933.20] But you could run something for six months and nobody nibbles at it.
+[1933.28 → 1938.14] And then on, you know, day one of seven months, somebody nibbles on it.
+[1938.56 → 1939.78] It's tricky that way.
+[1939.78 → 1949.38] And so it really, the only way to have full peace of mind, and that's what I've opted to do here in Lady Joop's, is just to have absolutely zero outside inbound.
+[1949.92 → 1954.02] It's the only way I've found to be completely comfortable with it.
+[1954.12 → 1963.50] I don't necessarily always follow that rule myself because some services like mail servers, web servers, media streaming servers, they have to be public by their very nature.
+[1963.78 → 1969.42] So you have to hope that those just have more eyes and that they get a little more attention and that they've been a little more audited.
+[1969.76 → 1972.18] But remember, logging is your friend.
+[1972.40 → 1975.94] So if you ever suspect something weird is happening, go check your logs.
+[1976.00 → 1977.12] See if you have weird logins.
+[1977.12 → 1979.30] See if you have somebody hitting your website all the time.
+[1979.30 → 1980.36] Use Datadog.
+[1980.68 → 1980.94] Yeah.
+[1981.26 → 1981.58] Yeah.
+[1981.62 → 1983.60] Use something that will go through there and alert you.
+[1983.72 → 1985.22] That absolutely could be a good way to go.
+[1985.72 → 1989.78] It's a good question, though, listener Chris, because I'm sure it's one that people struggle with.
+[1989.82 → 1991.48] So let us know what you out there would do.
+[1991.96 → 1993.68] Self-hosted. Show slash contact.
+[1993.68 → 1996.36] Now, we have Joseph who writes in.
+[1996.42 → 2001.28] He says, I have a bunch of those Taken smart switches flashed with Yasumoto, and they work great.
+[2001.66 → 2005.04] I have a need for smart switches to replace my wall switches, though.
+[2005.40 → 2010.22] You know, for example, like my kids' closet lights, which are always left on.
+[2010.22 → 2021.38] I would also love to replace the controllers on our ceiling fans with smart devices, something that would toggle the light on and off and also set the fan to high, medium or low or even off completely.
+[2021.60 → 2026.76] My preference would be for something I can self-host, non-cloud connected, open source software.
+[2026.76 → 2032.02] Are there any devices which would actually fill this need or similar to the way the Taken smart plugs do?
+[2032.32 → 2032.88] What are your thoughts?
+[2033.36 → 2034.46] Well, this is an easy question.
+[2035.00 → 2038.62] The Shelly devices are exactly what you're looking for.
+[2038.70 → 2040.50] And I think we've talked about them on a previous episode.
+[2040.76 → 2047.32] But just to recap, they're about the size of an Oreo cookie, and they go inside the light box behind the switch.
+[2047.46 → 2049.06] So you don't change the switch itself.
+[2049.52 → 2054.42] But this little cookie size box has a relay inside it.
+[2054.84 → 2056.30] You need to do a little bit of wiring.
+[2056.30 → 2057.76] So, you know, mains voltage.
+[2058.16 → 2060.88] Be careful or get an electrician if you're not comfortable.
+[2061.62 → 2062.64] They make a few products.
+[2062.74 → 2067.62] So they make a 2.5, which will let you do up to two switches in the same box.
+[2068.16 → 2070.32] They make a single unit as well.
+[2070.46 → 2074.98] And they make a bunch of other stuff that does like rolling shutters for garage doors and all sorts of stuff.
+[2075.50 → 2078.54] So go to Shelly.cloud and check out their stuff if you're interested.
+[2078.74 → 2080.44] But it's exactly what you're looking for.
+[2080.70 → 2082.72] And you can put TAS motor on them.
+[2083.34 → 2085.06] So Mahendra writes in.
+[2085.06 → 2088.98] In the latest episode, you suggest file run for a simple file browser.
+[2089.40 → 2093.00] I wanted to suggest another minimalist alternative.
+[2093.40 → 2100.36] It's very light with no database required at GitHub.com slash file browser slash file browser.
+[2100.60 → 2101.86] God, that rolls off the tongue, doesn't it?
+[2102.28 → 2102.96] It's very simple.
+[2103.06 → 2103.58] Easy to remember.
+[2104.08 → 2104.30] Yeah.
+[2104.36 → 2108.76] It is just a web-based file browser that sits on top of a directory.
+[2108.92 → 2110.30] Each user gets their own directory.
+[2110.30 → 2112.42] And it's just a standalone app.
+[2113.08 → 2113.84] Pretty simple.
+[2114.36 → 2114.96] I like it.
+[2115.22 → 2117.16] Even easier than the one we had talked about before.
+[2117.46 → 2119.16] So I'm going to think I'm going to grab this and try it out.
+[2119.64 → 2120.16] It is nice.
+[2120.34 → 2121.58] Yeah, I tried it out before the show.
+[2121.84 → 2125.24] And I kind of wish I hadn't bothered with file run now.
+[2125.40 → 2132.46] This is, I think, my new standard kind of throw it up and forget about it remote access software.
+[2132.46 → 2133.72] So, yeah, great job.
+[2133.78 → 2134.66] Thanks for writing in, Mahendra.
+[2135.50 → 2139.54] Now, I've mentioned Showdown a couple of times on the show before as a self-hosted recipe app.
+[2139.78 → 2140.50] I still use it.
+[2140.56 → 2141.26] I still love it.
+[2141.34 → 2145.52] It stores all of my recipes in clear text files on disk.
+[2145.72 → 2146.96] But there are some alternatives.
+[2147.48 → 2149.72] And we've had a couple of listeners write in.
+[2150.08 → 2152.22] And one of them is called Tandoor Recipes.
+[2152.28 → 2153.14] What do you think of this one, Chris?
+[2153.36 → 2154.66] It looks perfect.
+[2154.66 → 2164.50] And this, if anything, would probably get me to start doing something like this because it has a planning aspect, which is useful for a guy like me.
+[2164.56 → 2168.40] I can do a little meal planning, but also has a sharing feature.
+[2168.64 → 2174.46] And it's all on a progressive web app, which means my wife and I could share it like on our phones, which I think would be really nice.
+[2174.46 → 2179.50] And then the other thing I would need is, and it does support importing from Showdown, is import.
+[2179.60 → 2187.56] And it has Showdown import as well as Nextcloud cookbook import, Mealy, paprika, saffron, and a couple of others it can import from.
+[2188.22 → 2190.46] I think it's easy to try out.
+[2190.96 → 2197.60] Now, we have mentioned this one previously because it goes by the name vabeen1111 slash recipes on GitHub.
+[2197.84 → 2199.12] That's the repo it's in.
+[2199.76 → 2201.88] I think the Tandoor name must be new.
+[2201.88 → 2204.30] I don't know how old exactly it is.
+[2204.46 → 2206.64] Yeah, it is a new release too.
+[2206.80 → 2208.32] So that might be maybe they did a name change.
+[2208.62 → 2210.66] But they are using medics for their documentation.
+[2211.18 → 2212.74] So I've got to give them a plus point for that.
+[2213.18 → 2219.46] Yeah, it says here that they're happy to announce they've released a new version, which gives the application its well-deserved name and logo, Tandoor recipes.
+[2219.62 → 2220.18] So there you go.
+[2220.60 → 2222.62] It runs out of a Docker container.
+[2222.90 → 2225.38] It will also run on Unpaid, Synology, Kubernetes.
+[2225.74 → 2227.74] You can do it manually as well if you want to.
+[2228.40 → 2232.36] There's a bunch of interesting stuff about syncing and storage in their documentation.
+[2232.36 → 2237.88] So it's going to take a lot for me to throw away Showdown because I do genuinely really like it.
+[2237.96 → 2241.68] And I've modified the CSS, so I've got some fuzzy search.
+[2241.74 → 2243.10] You know how I love my fuzzy search.
+[2243.24 → 2244.00] Oh, that's cool.
+[2244.28 → 2246.08] You know, I've customized Showdown for my own needs.
+[2246.54 → 2248.92] But then maybe the grass is greener.
+[2248.94 → 2250.04] Maybe I should try this one out.
+[2250.46 → 2252.24] I mean, it does have the import functionality.
+[2252.24 → 2254.94] Downside, though, is it needs a Postgres database.
+[2255.42 → 2260.88] And I've already got, like, it feels like a dozen different database containers running.
+[2260.96 → 2262.14] Do I need another one?
+[2262.62 → 2265.44] That is a constant internal battle.
+[2265.62 → 2267.70] And sometimes I'm just down to, ah, who cares?
+[2267.80 → 2268.64] Just run a bunch.
+[2268.72 → 2269.56] You've got the resources.
+[2269.70 → 2273.60] And other times, like the sysadmin in me is just not having it.
+[2274.12 → 2277.18] It's just you can't run three copies of Postgres.
+[2277.30 → 2278.20] That doesn't make any sense.
+[2278.28 → 2279.00] They're different versions.
+[2279.08 → 2281.44] They have different security issues, different features.
+[2281.44 → 2282.22] What are you doing?
+[2282.82 → 2284.44] And it's a recipes' app at the end of the day.
+[2284.76 → 2285.90] Like, you know what I mean?
+[2286.08 → 2291.90] Just having the files in clear text on disk feels more future-proof to me.
+[2292.04 → 2297.54] So if this person loses interest in maintaining this particular app for whatever reason,
+[2297.78 → 2300.64] I'm not up the creek without a paddle, so to speak.
+[2300.64 → 2302.22] That, I think, is a great feature of Showdown.
+[2302.66 → 2306.14] That kind of clear text back end gives me peace of mind.
+[2306.34 → 2307.10] That's just it.
+[2307.22 → 2308.50] Peace of mind for that kind of stuff.
+[2308.86 → 2311.04] And if Showdown stops working for some reason,
+[2311.04 → 2314.10] I can just pull it up in any text editor, and it's still readable.
+[2314.52 → 2317.24] Yeah, it's almost as good as writing them down on an index card.
+[2318.52 → 2320.08] You know, you laugh at that.
+[2320.18 → 2324.56] But I'm pretty sure if I asked my mom to go and find me a recipe for something,
+[2325.36 → 2328.12] she would find it in less time than it takes me to fix.
+[2328.58 → 2329.90] Oh, Showdown's not working?
+[2330.06 → 2334.20] Okay, well, let me just SSH in and do this, do that, do the other.
+[2334.70 → 2336.04] And before you know it, 10 minutes later,
+[2336.04 → 2338.10] you've forgotten that you're actually looking for a recipe,
+[2338.10 → 2340.12] and then you go and order pizza instead, so.
+[2341.42 → 2344.08] Yeah, and meanwhile, she's got the index card ready to go.
+[2344.18 → 2344.84] It's very true.
+[2345.04 → 2345.96] There's something to that.
+[2346.64 → 2350.08] A reminder, you can find our sponsor, our Cloud Guru, on social media.
+[2350.22 → 2351.66] They're just slashed a Cloud Guru.
+[2351.82 → 2353.68] It's really easy, like on Twitter, Facebook, YouTube,
+[2353.98 → 2355.50] pretty much all the social media platforms.
+[2355.80 → 2357.16] Just slash a Cloud Guru.
+[2357.66 → 2358.62] Also, our members.
+[2358.86 → 2361.64] Thank you to our members, self-hosted. Show slash SRE.
+[2361.78 → 2362.64] You support the show.
+[2363.20 → 2365.00] You become our site reliability engineers.
+[2365.00 → 2367.76] You get a limited ad feed and extra content.
+[2368.20 → 2369.34] The post show.
+[2369.92 → 2371.52] Self-hosted. Show slash SRE.
+[2371.72 → 2373.64] If you'd like to support the show and become a member.
+[2374.16 → 2375.64] My Wise cam 3 came in this week,
+[2375.70 → 2377.26] so we're going to have a little chat about that today.
+[2377.36 → 2378.64] Yes, that's going to be the post show.
+[2378.68 → 2380.46] I ordered a few of them, so I got thoughts.
+[2380.60 → 2381.14] Of course you did.
+[2383.06 → 2385.32] So you can go to self-hosted. Show slash contact,
+[2385.60 → 2387.28] and that's the place to go to get in touch with us.
+[2387.52 → 2390.56] You can find me on Twitter at Ironic Badger.
+[2390.56 → 2393.26] Oh, I'm there as well, at Chris Elias,
+[2393.38 → 2395.68] and the show is at self-hosted.show.
+[2395.98 → 2398.20] On Discord, I'm at Alex.
+[2398.62 → 2400.00] So thanks very much for listening, everybody.
+[2400.26 → 2402.68] That was self-hosted. Show slash 40.

41： The One with Jeff Geerling _summary.txt

@@ -0,0 +1,45 @@
+• Nabu Casa acquiring ESP Home and the benefits of the acquisition
+• Explanation of what ESP Home is and how it simplifies firmware management for ESP boards
+• Discussion of potential future improvements to ESP Home through integration with Home Assistant
+• Linode's role as a cloud hosting provider and its support for the show
+• Hosts major infrastructure on Linode and praises its performance
+• Compares Linode's costs to AWS, Google Cloud, and Azure (30-50% cheaper)
+• Discusses flexibility in deploying a mix of on-premises and cloud computing
+• Mentions Linode's 11 global data centers and monitoring tools
+• Cites Cloud Spectator study that shows Linode has best CPU and disk performance among providers
+• Introduces guest Jeff Geerling, an Ansible expert and YouTube creator
+• Discusses Jeff's background with Ansible, from getting started to writing a popular 101 guide
+• What Ansible is and how it automates repetitive tasks
+• YAML configuration in Ansible, its advantages over JSON/XML, and common criticisms
+• Misuse of Ansible features, such as turning it into a programming language or abusing conditions in tasks
+• Importance of using Python for complex logic and separating code from configuration
+• Overview of recent changes in Ansible 3.0 and the ongoing transition from Ansible 2.9
+• Upgrading Ansible to version 3 requires careful consideration due to changes in how modules and plugins are managed.
+• The introduction of collections, which break down large codebases into smaller, maintainable components.
+• Challenges in making collections work together seamlessly, resulting in potential "growing pains" for users.
+• Benefits of the new system include flexibility and the ability to install only necessary modules.
+• Recommended resources for learning about Ansible 3 changes include the official documentation, release notes, and a guide for upgrading.
+• The speaker's book on Ansible has been updated to reflect the changes in version 3.
+• The Compute Module 4 has a standard PCI Express slot on its I/O board.
+• This allows for building custom boards with different form factors and features, such as M.2 slots for storage and LTE modems.
+• Broadcom contacted the speaker after seeing their work and offered to send them a hardware RAID controller card to test.
+• The speaker successfully implemented a live stream with 16 hard drives plugged into the Pi using the card.
+• Performance was limited by the X1 PCI Express lane, which only supports up to 5 gigabits per second (3.2 gigabits in real-world tests).
+• The Compute Module may be an indication of where future Raspberry Pi boards are headed, potentially including the Pi 5.
+• The advantages of using the Compute Module include leveraging the existing Raspberry Pi ecosystem and community.
+• Limitations of Raspberry Pi's network throughput
+• Desired improvements in future Pi models (PCI bandwidth and CPU speed)
+• Comparison to Apple M series performance
+• Self-hosting projects, including pydramble.com and potential use of Starlink for hosting services
+• ISP uptime and reliability concerns
+• Testing Starlink for redundancy and link aggregation
+• Host is using various devices for different tasks, including Raspberry Pi, x86 server, and Mac Mini.
+• The host's Mac Mini is outdated but still serves as primary network storage device.
+• The host has a significant amount of data on their LAN, with 24 terabytes online and approximately 60 in-house.
+• A "Petabyte Pi" project is discussed, where the goal is to build a Raspberry Pi controlling a petabyte of storage.
+• The conversation also touches on hardware requirements for such a project and potential uses for a large storage device.
+• Jeff's guest appearance on the show
+• Upcoming content mentioned but not revealed to the host
+• Promotion of Cloud Guru and links to their social media channels
+• SelfHosted members benefits and limited ad feed
+• Contact information for the show, including Twitter handles and website URL.

41： The One with Jeff Geerling _transcript.txt

@@ -0,0 +1,519 @@
+[0.00 --> 4.96]  Coming up on today's show, we have Jeff Geerling. You may know him as Geerling Guy in Ansible Galaxy.
+[5.42 --> 8.62]  He's also on a bunch of work recently with the Raspberry Pi.
+[9.48 --> 16.28]  Chris loses his mind a little bit when Jeff tells him how he hooked up 16, yes, 16 drives to a Raspberry Pi.
+[16.70 --> 17.22]  I'm Alex.
+[17.64 --> 19.82]  I'm Chris, and this is Self-Hosted 41.
+[21.06 --> 25.40]  Alex, we have a lot to talk about today, and we also have a special guest.
+[25.40 --> 33.12]  We do indeed, yes. We have Geerling Guy, Jeff Geerling, the Raspberry Pi Ansible maestro, all the sorts of superlatives.
+[33.74 --> 37.52]  My new YouTube habit. I love what he's putting out.
+[37.58 --> 38.78]  Yeah, I thought you might like him.
+[40.04 --> 43.92]  Yeah, I do. I want to say thanks to a Cloud Guru for sponsoring this episode.
+[44.06 --> 47.28]  They are the leader in learning for the cloud, Linux, and other modern tech skills.
+[47.38 --> 49.52]  Get hundreds of courses, thousands of hands-on labs.
+[49.94 --> 53.66]  Get certified, get hired, get learning at cloudguru.com.
+[53.66 --> 58.54]  So the interview really will be the bulk of the show today, because there's so many great things we get into.
+[58.96 --> 64.72]  But before we start, I kind of wanted to chat with you about Nabucasa buying ESP Home.
+[65.24 --> 65.94]  How do you feel about it?
+[65.98 --> 70.18]  I mean, when I first heard the news, I was like, oh, I wasn't quite sure how to feel.
+[70.18 --> 79.32]  And then some more details trickled out about how the original creator, Otto, was, you know, basically burning out.
+[79.32 --> 84.56]  And I think overall, it's a great way to save an open source project.
+[84.56 --> 91.56]  That is one of my personal favorite ways to configure, you know, ESP boards.
+[92.24 --> 94.88]  It's a clear value for the Home Assistant community.
+[95.60 --> 97.34]  And this was, you're right.
+[97.42 --> 100.62]  I had my first read of this was sort of like, I'm not so sure.
+[100.62 --> 103.10]  Because they're a small team with a lot to do.
+[103.42 --> 110.28]  But when you read between the lines, it seems pretty clear that Otto was about to hit the nope out button.
+[110.88 --> 115.46]  And the project would have been left without its leader and lead developer.
+[116.10 --> 119.26]  This is kind of nice because this gives the project room to grow.
+[119.44 --> 121.12]  It'll bring in some new contributors.
+[121.80 --> 123.16]  Otto is taken care of.
+[123.46 --> 126.90]  He's able to participate if he likes, but, you know, he's going to focus on life for a bit.
+[126.94 --> 128.26]  He's shutting down the Patreon account.
+[128.26 --> 131.24]  He doesn't have to worry about the management side of things.
+[131.88 --> 134.72]  And it continues to be a free software project.
+[135.48 --> 141.68]  And if anything, I would expect it will be even tighter integrated into Home Assistant now.
+[141.94 --> 142.98]  We're seeing some of that already.
+[143.48 --> 152.16]  Frank, one of the main developers for Home Assistant, has already made some significant improvements to the VS Code plugins for how that interfaces with ESP Home.
+[152.56 --> 155.44]  So there's some autocomplete stuff coming and things like that.
+[155.44 --> 159.46]  But let's just back up a little bit and explain what ESP Home is.
+[160.10 --> 168.16]  So the way I got started with it was I was programming these ESP8266 single board computers, if you like.
+[168.24 --> 171.80]  They're kind of in the same space as an Arduino, more than a Raspberry Pi.
+[172.06 --> 173.34]  So they don't run a full OS.
+[173.42 --> 175.56]  They actually run a precompiled firmware.
+[175.56 --> 186.20]  And that used to require writing an Arduino sketch and uploading it to the board and, you know, all the stuff that comes with the Arduino IDE and universe and that kind of thing.
+[186.74 --> 194.48]  And what ESP Home does, and it is pure magic in my opinion, is you define the firmware as a YAML file.
+[194.48 --> 205.24]  You add a couple of modules here with a couple of lines to, you know, enable Wi-Fi and then another couple of lines to enable logging and then another couple of lines to enable the Home Assistant API, for example.
+[205.96 --> 217.28]  And then you flash that binary that is generated from the YAML file onto the ESP8266 without having to write a single line of C code or whatever the Arduino equivalent would be.
+[217.28 --> 219.90]  And it just makes it so approachable.
+[220.36 --> 223.84]  Yeah, and there's so many devices that run off this type of firmware out there.
+[224.40 --> 230.04]  And you can really see long term the value that Home Assistant, if Home Assistant can make this even simpler.
+[230.84 --> 238.88]  Imagine a future, if you would, Alex, where Home Assistant could even auto detect devices and guide the user through generating the firmwares.
+[239.18 --> 244.08]  And maybe even has a way to deploy it with some DNS magic or something, depending on the device.
+[244.08 --> 249.62]  But they could really make this a whole inclusive package at some point.
+[250.14 --> 250.66]  Absolutely, they could.
+[250.76 --> 260.44]  Because with this acquisition, Nabu Kasa now owns the copyright to Otto's Code and therefore the ESPHome organization on GitHub and Docker as well.
+[260.74 --> 263.68]  Yeah, and ESPHome.io is a great resource.
+[263.84 --> 266.64]  So if you want to learn a little bit more, go check out ESPHome.io.
+[266.74 --> 268.82]  And of course, we'll have a link in the notes.
+[269.36 --> 271.80]  Which, as always, you can find at selfhosted.show.
+[271.80 --> 275.74]  Linode.com slash SSH.
+[275.86 --> 281.16]  Linode.com slash SSH gives you a $100 60-day credit towards a new account at Linode.
+[281.36 --> 283.18]  And of course, it supports the show.
+[284.04 --> 285.78]  Linode is our cloud hosting provider.
+[285.98 --> 289.42]  Anything we want to try out or anything we put in production, we put it up on Linode.
+[289.58 --> 290.84]  We get emails into the show.
+[290.92 --> 292.40]  We try stuff out on Linode.
+[292.54 --> 294.18]  It's really quick to get going.
+[294.30 --> 296.20]  But also, it's because it's fast.
+[296.38 --> 298.74]  We know it's just going to get done really quick.
+[298.74 --> 302.20]  And sometimes you just want to prototype something as fast as possible.
+[302.42 --> 307.16]  Now, we host all of our major infrastructure for Jupyter Broadcasting 3.0 on Linode, of course.
+[307.82 --> 312.52]  But even the stuff that never makes it public, that never is listener-facing, we run on Linode as well.
+[312.58 --> 313.32]  They're super fast.
+[313.40 --> 324.42]  They have native SSD storage, 40 gigabit network, totally easy to use cloud manager, really simple to take snapshots and get an idea of the last time your computer, or I should say Linode, was backed up.
+[324.42 --> 331.20]  You can really simplify your infrastructure while also reaping the benefits of great performance at a great price.
+[331.66 --> 336.14]  Linode costs 30% to 50% less than AWS or Google Cloud or Azure.
+[336.66 --> 341.22]  And it really works well if you want to just blend a little bit of on-premises and cloud as well.
+[341.34 --> 342.56]  That's how I use it for NextCloud.
+[342.92 --> 345.72]  I have a cloud component to my NextCloud setup on Linode.
+[346.08 --> 351.14]  And then the big bulk of the storage, like the archival stuff, it's all here locally on my LAN.
+[351.26 --> 352.58]  It works fantastic that way.
+[352.58 --> 356.46]  And with 11 data centers worldwide, you're going to find just the right spot to deploy.
+[356.68 --> 364.78]  And you'll rest easy knowing that Linode's rocking fast and has great monitoring tools that can alert you to problems before you even notice them.
+[365.04 --> 369.02]  Of course, these things are really important, but performance matters as well.
+[369.10 --> 370.58]  And Linode has you covered there too.
+[371.02 --> 376.40]  Cloud Spectator recently did a study of the different cloud providers, like all of them.
+[377.02 --> 379.46]  Dio, Amazon, Google.
+[379.46 --> 383.78]  Google looked at Azure, all of them, put them in there, and saw who was the fastest.
+[384.28 --> 392.50]  And one of the things that really makes Linode stand out is their dedicated CPU rigs have AMD EPYC processors that are just cranking faster than the other providers.
+[392.50 --> 398.56]  And Linode's disk storage is super fast, so you can feed those processors faster than the other providers.
+[398.56 --> 411.02]  And what Cloud Spectator survey shows is that not only does Linode have the best CPU and disk performance, but it has the best continuous performance as well, which really matters when you have large jobs that need processing or you're getting a lot of traffic.
+[411.18 --> 412.56]  You need that sustained performance.
+[413.46 --> 417.16]  I mean, Linode started in 2003 as one of the first companies in cloud computing.
+[417.16 --> 419.08]  So they really know what they're doing.
+[419.28 --> 424.76]  They're independently owned and founded on a love for Linux open source technologies and the community that surrounds them.
+[425.06 --> 426.94]  So just go try what I'm talking about.
+[427.12 --> 428.86]  I've told you about the object storage before.
+[428.98 --> 430.66]  I've told you about the cloud firewall before.
+[430.74 --> 432.34]  There's a lot to check out with Linode.
+[432.48 --> 435.20]  And what they've chosen to do, they do really well.
+[435.50 --> 436.72]  So go spend that $100.
+[437.44 --> 439.32]  Linode.com slash SSH.
+[439.46 --> 442.04]  Go see what I've been talking about and support the show.
+[442.38 --> 444.38]  Linode.com slash SSH.
+[444.38 --> 452.00]  Well, I'm delighted to welcome to the show somebody whose work I've been following for many years as an Ansible user.
+[452.26 --> 454.12]  We have Jeff Geerling on the show today.
+[454.22 --> 454.72]  Welcome, Jeff.
+[455.18 --> 456.24]  Thanks for having me.
+[456.60 --> 457.50]  Thank you for being here.
+[457.86 --> 462.18]  And more recently, of course, a YouTube extraordinaire content creator.
+[462.62 --> 464.04]  Yeah, that's how I came to know you.
+[464.38 --> 464.66]  Yeah.
+[465.14 --> 468.32]  So you've been doing a lot of videos lately on the Raspberry Pi 4 compute module.
+[468.42 --> 469.90]  I thought we'd talk to you a little bit about that.
+[469.90 --> 478.42]  But before we get to that side of the discussion, I wanted to sort of talk to you a little bit about what I knew you for first, which was Ansible.
+[478.64 --> 483.54]  So you have a really rather excellent 101 getting started course.
+[483.54 --> 494.10]  Before Jeff Geerling existed and created this, you know, de facto guide for people getting started with Ansible, how did you get involved with the project?
+[494.10 --> 500.10]  I started off by having a few servers, then many servers, and then dozens of servers.
+[500.36 --> 506.32]  And once I went from many to dozens, I realized I had to switch to some sort of configuration management system.
+[507.12 --> 509.66]  And at the time, Ansible was pretty much brand new.
+[510.14 --> 516.76]  That was 2012, 2013, when I was making that transition from shell scripts and runbooks to something more formal.
+[516.76 --> 519.62]  So I tried out Chef, but I'm not a Ruby developer.
+[520.32 --> 522.18]  And I didn't really like it.
+[522.38 --> 529.74]  It felt too much like programming to me and learning Ruby when, you know, I did PHP and Node.js and things like that.
+[530.14 --> 533.20]  So I got into Ansible at that time.
+[533.52 --> 538.34]  And at the time, it was so simple that you could pick everything up in a day.
+[538.36 --> 542.48]  And it was focused really on just Linux administration, not all the other things that it does today.
+[542.48 --> 547.82]  Um, but the documentation was great, but there wasn't a ton of examples out there.
+[547.98 --> 551.36]  So I just started blogging about my experiences.
+[551.36 --> 554.00]  And then I realized that there wasn't a book for it.
+[554.10 --> 561.80]  So I put my blog post together into like a 50 page sampler thing and stuck it onto LeanPub,
+[561.90 --> 566.20]  which was also pretty new at the time, and started self-publishing this little ebook.
+[566.20 --> 572.78]  And my goal was to maybe sell 100 copies or 200 copies and, you know, help some people learn Ansible.
+[573.10 --> 577.96]  And lo and behold, a couple of years later, since it was one of the first books on Ansible,
+[578.08 --> 580.28]  it became one of the most purchased books.
+[580.50 --> 584.20]  And to this point, I don't remember how many tens of thousands of books I've sold,
+[584.34 --> 587.46]  but lots of thousands of books have been sold.
+[588.10 --> 594.90]  It was the number one bestseller for infrastructure automation for a number of periods on Amazon.
+[594.90 --> 600.82]  And has been in the top five, top 10 books on LeanPub for years now, too.
+[601.18 --> 601.54]  Congratulations.
+[602.30 --> 602.86]  Yeah, thanks.
+[603.06 --> 603.88]  I don't doubt it.
+[604.10 --> 609.62]  You know, every time you search for anything related to a specific role or something like
+[609.62 --> 613.86]  that for Ansible, you're looking, there's a Jeff Geerling role in there in Ansible Galaxy.
+[614.28 --> 618.54]  So some of our listeners will be familiar with Ansible, but some won't.
+[618.64 --> 622.12]  So what's your quick kind of elevator pitch of what Ansible is and does?
+[622.12 --> 627.36]  There's an XKCD about whether or not you should automate something.
+[628.06 --> 631.14]  And I think that that's a good illustration of what Ansible is.
+[631.26 --> 635.68]  Once you reach the point where you're doing something, maybe to a group of computers or
+[635.68 --> 640.34]  to network switches or to servers, or even I use it to manage my own computer.
+[640.46 --> 645.40]  If you're doing a repetitive task that can be automated, Ansible can automate that.
+[645.60 --> 647.94]  Almost anything in the world that has to do with technology.
+[647.94 --> 650.82]  So that's what it does.
+[650.94 --> 652.02]  And it's very simple.
+[652.22 --> 657.54]  That's the big selling point for it compared to other tools is it uses YAML configuration,
+[657.92 --> 660.66]  which is very approachable, very easy to learn.
+[661.10 --> 666.74]  And that's why I liked it over the other solutions at the time, Chef and Puppet that I was looking at.
+[666.74 --> 674.54]  People back in 2012, 13 time were just moaning about how YAML was so complicated with its white space.
+[674.60 --> 681.24]  And I never quite understood the hate, to be honest with you, because JSON, people say,
+[681.42 --> 682.66]  oh, I'd much rather write JSON.
+[682.82 --> 683.80]  I'm like, are you mad?
+[685.12 --> 686.52]  YAML is way easier to work with.
+[686.52 --> 695.92]  Yeah, I think a lot of people maybe don't, they aren't used to having like a code editor do formatting for them and things like that.
+[696.00 --> 701.66]  It's much more common nowadays, especially in the infrastructure space than it was 10 years ago.
+[701.90 --> 703.44]  And I think that's the biggest difference.
+[703.58 --> 709.52]  Nowadays, YAML, people complain about it mostly because they see people do things that you shouldn't do in YAML.
+[709.52 --> 712.98]  But back then it was more the syntax and the formatting.
+[713.16 --> 717.56]  They're like, I could put in anything in JSON or God forbid, XML.
+[718.56 --> 720.52]  But, you know, YAML is going to complain about it.
+[720.64 --> 725.38]  And I think nowadays we're past the formatting stage and we're into the, you know,
+[725.46 --> 730.64]  what could be a next generation format for configuration that's even better than YAML because it does have shortcomings.
+[730.82 --> 739.30]  But it's, in my opinion, it's a thousand times better than JSON, XML and SOAP and all the other protocols we used to have to know to be able to configure things.
+[739.52 --> 740.44]  Couldn't agree more.
+[740.76 --> 740.94]  Yeah.
+[741.24 --> 747.90]  So I think, you know, speaking of things that people shouldn't do, turning Ansible into a programming language is probably up there, right?
+[748.02 --> 750.36]  I mean, you can do some pretty crazy stuff in Ansible.
+[750.72 --> 753.92]  And my day job is related to OpenShift at Red Hat.
+[754.10 --> 759.02]  And a lot of the OpenShift installer stuff for version three, the last major version,
+[759.72 --> 764.76]  there was some pretty crazy hacky stuff going on in those Ansible playbooks and stuff like that.
+[764.92 --> 767.98]  But what's the most crazy thing that you've seen with Ansible?
+[767.98 --> 772.76]  I think it's the abuse of the when condition in tasks.
+[773.44 --> 778.16]  When your when condition is longer than the rest of your Ansible task for a given piece of automation,
+[778.52 --> 779.84]  I think that's where you've failed.
+[780.46 --> 784.38]  At that point, in Ansible, you can write modules in Python.
+[784.58 --> 789.76]  You can actually, there are ways to write modules in other languages too, but typically you'd write it in Python.
+[790.30 --> 794.74]  And if you're going to use complex logic to determine whether to do something or how to do something,
+[794.74 --> 796.58]  that should be in Python.
+[796.88 --> 802.90]  At that point, you're getting into advanced Ansible usage that requires you to have some of that programming knowledge.
+[803.48 --> 806.30]  Programming in YAML is a terrible, terrible idea.
+[806.54 --> 807.22]  Never do it.
+[807.62 --> 812.18]  Every time I have gone further than an if-then or an if-else type condition,
+[812.36 --> 813.46]  I've regretted it.
+[813.52 --> 814.62]  And the maintenance is a nightmare.
+[814.62 --> 820.28]  And then there's always the ginger 2 stuff that people do, the crazy templating, for loops, all that kind of stuff.
+[820.60 --> 821.12]  So yeah.
+[821.52 --> 823.30]  Anyway, should we talk about Ansible 3 for a minute?
+[823.54 --> 826.96]  There's been a big release in the last few weeks of Ansible 3.0,
+[827.04 --> 830.58]  which brings a lot of changes to the way in which modules are delivered to users.
+[830.86 --> 832.52]  What do you make of all that change?
+[832.52 --> 834.80]  It's been an interesting transition.
+[835.18 --> 840.78]  And I think it's ongoing and will be ongoing for another period of time, six months to a year, probably.
+[841.36 --> 847.72]  Mostly because Ansible 2.9, which is the previous major version of what you would get when you installed Ansible
+[847.72 --> 850.52]  using PIP or a package manager or something like that.
+[851.06 --> 853.62]  Ansible 2.9 will still be supported for a while.
+[853.62 --> 859.58]  Ansible, mostly because I think there's just a lot of people who the transition to the new version of Ansible
+[859.58 --> 863.50]  does introduce some changes that could impact people's workflows a little bit.
+[864.04 --> 867.94]  The good thing about the transition is that all my existing playbooks,
+[868.00 --> 870.54]  and I have a ton of playbooks that do a ton of different things,
+[871.04 --> 876.54]  they all work fine if I just upgrade Ansible using PIP, which is the Python package manager.
+[876.94 --> 881.82]  There are other ways to install Ansible that might not work with Ansible 3 the same way anymore.
+[881.82 --> 883.28]  So you have to watch out for that.
+[883.46 --> 886.96]  And that's why I always recommend using PIP to install it.
+[887.16 --> 889.92]  It's a Python program and PIP is the preferred way.
+[890.66 --> 898.72]  But the big, big change is that collections of modules used to all be maintained in one giant code base.
+[899.26 --> 902.06]  And there were various reasons that was not very sustainable.
+[902.76 --> 906.58]  There were something like 4,000 or 5,000 different plugins and modules.
+[906.84 --> 910.28]  And the core team of developers who managed the releases and things,
+[910.28 --> 911.66]  it was just a lot to coordinate.
+[912.28 --> 917.30]  So the main goal was to move all of that content out into smaller collections
+[917.30 --> 921.34]  that could be maintained by people with more knowledge of just the modules in that collection.
+[921.50 --> 927.90]  Like, there's no reason why a, let's say, an F5 network load balancing module
+[927.90 --> 935.86]  should be under the same maintenance umbrella as a, I don't know, like a email script thing.
+[935.86 --> 941.66]  All these different modules were lumped together from network vendors and storage vendors and cloud vendors and Linux and Windows.
+[941.96 --> 943.56]  So now it's all broken out.
+[944.18 --> 950.88]  But the challenge has been making it all come together back into what we install if we do a PIP install Ansible.
+[950.88 --> 957.16]  And the nice thing is it all works, but the downside is there are a few little bumps,
+[957.26 --> 959.36]  especially if you have specialized use cases.
+[959.62 --> 966.94]  But another cool side effect is you could install Ansible without all that stuff and just add in the few things you need.
+[967.04 --> 971.26]  So if you just do Linux administration, you can install Ansible plus the Linux modules
+[971.26 --> 975.16]  and not install Windows, not install networking, not install cloud.
+[975.16 --> 981.00]  So it does offer some flexibility, but I think there's going to be some growing pains over the next year.
+[981.40 --> 983.50]  We've seen that trend quite a lot in technology at the moment.
+[983.84 --> 987.98]  You know, Docker being an example with Podman coming along to kind of break that out into,
+[988.22 --> 992.18]  you know, being less of a monolith type deployment model.
+[992.64 --> 994.12]  So I think it's a good thing personally.
+[994.50 --> 998.14]  And, you know, the work that's gone in has clearly been very well thought out.
+[998.14 --> 1005.48]  Are there any particularly good resources that you'd recommend people visit to get their head around what the major changes are?
+[1005.92 --> 1010.08]  The documentation is the best place to know what's going on.
+[1010.16 --> 1014.32]  There's not only is there a guide for upgrading Ansible in the release notes.
+[1015.18 --> 1022.06]  And if you are involved in using Ansible, I would highly recommend subscribing to the Ansible project mailing list on Google Groups.
+[1022.28 --> 1025.94]  But the guides and the documentation are by far the best.
+[1025.94 --> 1032.10]  They encapsulate everything that I could ever think of that people could be that could affect someone's workflow.
+[1032.96 --> 1035.84]  And also, I did update my book recently.
+[1035.84 --> 1042.64]  So if you are interested in learning Ansible and you don't know it yet, Ansible for DevOps has a major second revision.
+[1042.84 --> 1045.22]  I've actually revised it 25 times now.
+[1045.72 --> 1051.00]  But a major revision happened to incorporate some of the information about collections, especially.
+[1051.00 --> 1056.96]  And I'm still working on fully revising the book to be up to date with Ansible 3.
+[1057.60 --> 1058.30]  It all works.
+[1058.38 --> 1060.90]  It's just there are some things that could be optimized a little more.
+[1060.90 --> 1065.12]  Datadog.com slash self-hosted.
+[1065.28 --> 1072.00]  Analyze code level performance across your entire environment and troubleshoot issues faster with Datadog.
+[1072.38 --> 1078.60]  Datadog has a continuous profiler that automatically collects profiles from your production servers all the time.
+[1078.68 --> 1083.50]  So you can then analyze your data quickly with minimal overhead when you need.
+[1083.50 --> 1088.68]  Get a snapshot in time and troubleshoot and then visualize it with their beautiful dashboards.
+[1088.68 --> 1096.58]  Get a unified picture of your environment by correlating code performance metrics with your other monitoring data with real-time dashboards.
+[1096.66 --> 1097.86]  You've got to see these dashboards.
+[1097.98 --> 1103.34]  Go to datadog.com slash self-hosted to get a free trial and to see these beautiful dashboards.
+[1103.56 --> 1106.18]  And you'll get a free t-shirt when you sign up a trial and create a dashboard.
+[1106.18 --> 1117.46]  With tightly integrated APM, tracing, log management, and continuous profiler products in one single platform, Datadog enables you to pinpoint the root cause of issues faster than ever.
+[1117.46 --> 1124.14]  Are you seeing the value here when you can visualize everything at once down to the application level, server stuff, even website performance?
+[1124.26 --> 1125.90]  It's all in Datadog.
+[1126.02 --> 1127.90]  And you can get smart alerts as well.
+[1128.38 --> 1135.48]  Try Datadog's products for free for 14 days by visiting datadog.com slash self-hosted for a limited time.
+[1135.56 --> 1139.66]  If you start a free trial and create one dashboard, you'll get a free Datadog t-shirt.
+[1139.88 --> 1141.18]  And who doesn't love free swag?
+[1141.44 --> 1144.78]  So that's datadog.com slash self-hosted.
+[1144.78 --> 1148.84]  So Jeff, I've been watching on your YouTube channel.
+[1148.96 --> 1152.36]  You've been doing the impossible with Raspberry Pis.
+[1152.46 --> 1156.88]  I'm talking like, I think one of your setups was like 10 SATA disks.
+[1157.36 --> 1158.74]  16 hard drives.
+[1159.08 --> 1160.02]  How is this possible?
+[1160.14 --> 1161.72]  How is this madness accomplished?
+[1161.88 --> 1165.76]  Is it all with using the new Pi compute module?
+[1165.76 --> 1166.24]  Yes.
+[1166.68 --> 1174.34]  And the funny thing is the Raspberry Pi 4, the one that's been out since I think 2019, that was the Pi Day release back then.
+[1174.82 --> 1178.46]  The Raspberry Pi 4 actually has the same processor and capabilities.
+[1178.78 --> 1185.18]  But the big difference the compute module has is it exposes the internal PCI Express lane.
+[1185.40 --> 1185.64]  Yeah.
+[1185.64 --> 1187.14]  And that's the big game changer.
+[1187.26 --> 1189.58]  With the Pi 4, you could hack it.
+[1189.64 --> 1194.72]  You could desolder a chip on it, the VL805 chip that controls USB 3.
+[1194.78 --> 1199.42]  You could desolder that, wire up some jumpers, and get PCI through it.
+[1199.50 --> 1200.86]  And a couple people actually did that.
+[1200.92 --> 1204.28]  That was the first time that I started working with the compute module.
+[1204.28 --> 1211.96]  I was looking at their work because PCI Express support is rudimentary right now on Raspberry Pi OS.
+[1212.38 --> 1216.42]  And they were kind of like the groundbreaking people that got that going.
+[1217.06 --> 1224.30]  But the compute module 4 includes a standard PCI Express slot on the I.O. board that you can buy with it.
+[1224.84 --> 1230.64]  And the cool thing is that a lot of people are building boards around it that have different PCI form factors.
+[1230.64 --> 1244.74]  So M.2 slots for things like LTE modems or for storage with NVMe drives or SATA drives that are either in M.2 form factor or using a SATA controller.
+[1244.88 --> 1247.34]  And you can plug in hard drives and things like that.
+[1248.00 --> 1250.06]  So a really cool thing happened.
+[1250.20 --> 1254.38]  Somebody from Broadcom actually contacted me after they saw some of the work I was doing and said,
+[1254.48 --> 1258.88]  Hey, we want to see if we can get a hardware RAID controller, an enterprise storage controller.
+[1258.88 --> 1260.88]  These things cost like a thousand bucks.
+[1261.54 --> 1263.42]  We want to see if we can get that working on a Pi.
+[1263.66 --> 1264.98]  And we can't get a Pi.
+[1265.24 --> 1273.82]  Like they work at Broadcom, but they had trouble sourcing a Raspberry Pi because the compute module 4 has been in such high demand since the launch.
+[1274.54 --> 1275.78]  So they shipped me the card.
+[1275.90 --> 1280.34]  They shipped me a storage controller and had me work with a couple of storage engineers.
+[1280.48 --> 1282.22]  And we got it working.
+[1282.22 --> 1285.18]  So at that point, I had eight drives on the Pi.
+[1285.28 --> 1289.02]  But then I found that I could also plug in eight more drives with the card I had.
+[1289.18 --> 1294.96]  So I did a live stream and got all 16 hard drives plugged into the Pi and in one giant RAID array.
+[1295.50 --> 1295.72]  Wow.
+[1295.92 --> 1296.60]  How was performance?
+[1297.10 --> 1297.28]  Yeah.
+[1297.34 --> 1297.80]  How is it?
+[1297.82 --> 1298.08]  Because, right?
+[1298.16 --> 1303.56]  I mean, that's always the thing about the Pi is everybody says the Pi 4 is great, except for the IO really limits it now.
+[1303.64 --> 1305.36]  But this seems like that changes that a little bit.
+[1305.56 --> 1306.72]  It changes it a little bit.
+[1306.78 --> 1308.64]  It doesn't fix all the problems.
+[1308.64 --> 1309.54]  That's for sure.
+[1309.92 --> 1314.26]  The big problem is that it's X1, a Pi 1 lane.
+[1314.46 --> 1314.64]  Yeah.
+[1314.88 --> 1318.22]  So it's PCI Express Gen 2 by 1.
+[1318.68 --> 1323.44]  And the maximum throughput you can get with that is 5 gigabits per second.
+[1324.16 --> 1325.82]  But that's theoretical.
+[1326.04 --> 1330.40]  So the maximum real-world throughput that I've gotten, I've tested 10 gig Ethernet.
+[1330.48 --> 1331.76]  I've tested the storage controller.
+[1331.88 --> 1334.34]  I've tested all kinds of different crazy things so far.
+[1334.34 --> 1341.52]  And the maximum real-world throughput is about 3.2 gigabits, a little over 400 megabytes per second.
+[1342.06 --> 1345.22]  So I threw this hardware RAID storage controller on it.
+[1345.30 --> 1348.02]  It could do like 10 gigabytes per second.
+[1348.30 --> 1350.94]  But I can only put through 400 megabytes per second.
+[1350.94 --> 1358.84]  So it's not going to give you magically access to all of the wonderful things you could throw into like a modern Threadripper PC.
+[1358.84 --> 1367.60]  But it does give us a lot more options than with the Pi 4 where you just have USB 3.0, which has its own limitations.
+[1368.22 --> 1373.30]  I mean, the fact that you could have redundant storage is an upgrade beyond the fact that it's slightly faster too.
+[1373.76 --> 1380.46]  But do you think this kind of is maybe an indication of where the Pi is going to go?
+[1380.58 --> 1384.22]  Is this compute module a hint of what we might see maybe in the Pi 5?
+[1384.22 --> 1385.20]  I hope so.
+[1385.58 --> 1389.58]  Another thing to keep in mind is there are a lot of Pi competitors.
+[1389.94 --> 1393.32]  And it's, you know, which one is going to be the Pi killer?
+[1393.48 --> 1404.68]  Nothing's going to kill the Raspberry Pi just because the Raspberry Pi has a community and a force behind it that is unparalleled in all the other kind of makerspace single board computing realm.
+[1405.12 --> 1411.98]  And don't you think that's kind of the advantage of using the compute module in another board versus getting an SBC that just has all this stuff?
+[1411.98 --> 1416.90]  It's like you're getting the Raspberry Pi ecosystem with some of these cool new toys.
+[1417.24 --> 1417.68]  Yeah, yeah.
+[1417.84 --> 1423.22]  On the flip side, though, there are some boards like the, what is it, the Rockchip RX?
+[1423.58 --> 1425.22]  I forget what the specific chip is.
+[1425.38 --> 1425.98]  Rockchip Pro.
+[1426.18 --> 1428.54]  Yeah, it has a Pi 4 lane.
+[1428.68 --> 1434.38]  So you get more bandwidth and more lanes so that you can do more with it and have more I.O. speed.
+[1434.38 --> 1439.34]  There's still limitations just based on the fact that the CPU is not super fast.
+[1439.50 --> 1451.04]  And even if you give it, you know, let's say we get 10 gigabits or 20 gigabits of throughput, the CPU is going to be limited in other ways on these cheaper ARM SBCs like the Raspberry Pi.
+[1451.42 --> 1461.48]  For instance, today I'm doing some testing for a 2.5 gigabit NAS that I'm building with a Pi to see if it can compete with an out of the box NAS from QNAP or Synology or something like that.
+[1461.48 --> 1473.46]  And without overclocking the CPU, I can only pump through 1.7 gigabits of network traffic because the way the CPU is architected, all packets go on one core on the CPU.
+[1473.62 --> 1475.80]  It's a four core CPU, so it could support more.
+[1476.18 --> 1481.40]  But the way the network throughput works on the Pi, it's stuck on one core and it maxes out.
+[1481.52 --> 1483.50]  So you have to overclock it to get more speed.
+[1483.70 --> 1487.50]  I think, you know, there are two things I really want to see in the next Pi.
+[1487.64 --> 1489.76]  One is maybe more PCI bandwidth.
+[1489.76 --> 1492.54]  The other is just a faster CPU.
+[1492.82 --> 1494.04]  And we've seen what's possible.
+[1494.22 --> 1505.08]  Apple with their M series, even the A series, just blows away the competition in terms of performance per watt and, you know, single threaded performance for any kind of mobile device.
+[1505.70 --> 1510.34]  So I think that the ARM SBCs have a bright future.
+[1510.34 --> 1517.46]  And that's, I'm hoping that IO speed and CPU speed, which is becoming the bottleneck for a lot of my projects.
+[1517.90 --> 1520.34]  Those are the two things I really hope to see improved.
+[1520.76 --> 1522.82]  I wonder where you come up with some of these ideas, man.
+[1522.94 --> 1524.32]  Now your head must be an interesting place.
+[1524.32 --> 1529.62]  If you want to come over to my house sometime, I will show you the pile.
+[1529.78 --> 1532.82]  I have so many projects that I really, really want to work on.
+[1533.40 --> 1536.30]  And I don't think I'll get to them in the next few months, unfortunately.
+[1536.60 --> 1537.16]  Are you near me?
+[1537.24 --> 1537.90]  Are you in Raleigh?
+[1537.98 --> 1539.88]  No, I'm in St. Louis, Missouri.
+[1540.10 --> 1543.16]  But, you know, fly over here after the coronavirus is over.
+[1543.56 --> 1545.16]  Oh, maybe one day we'll do another road trip.
+[1545.24 --> 1545.56]  Hey, Chris?
+[1545.90 --> 1546.52]  Yeah, for sure.
+[1546.60 --> 1547.74]  I don't think that's a maybe.
+[1547.88 --> 1549.02]  Nothing about that's a maybe.
+[1549.02 --> 1553.84]  So if we were to come visit, what kind of stuff would we see you self-hosting in your place?
+[1554.24 --> 1558.68]  Right now, the major thing that I'm hosting is pydramble.com.
+[1558.80 --> 1560.74]  This has been a project since 2014.
+[1560.94 --> 1561.88]  I started doing it.
+[1562.10 --> 1568.54]  It was to see if I could host a Drupal site specifically, because I'm involved in the Drupal open source community.
+[1569.10 --> 1578.10]  If I could host Drupal in my house long term, and that site has had 99.997 or 8 uptime since 2014.
+[1578.10 --> 1579.64]  Running on Raspberry Pis.
+[1579.74 --> 1581.20]  Now, I cheated in 2016.
+[1581.20 --> 1585.46]  I switched to use Cloudflare as a front end, but the cache is only 30 minutes.
+[1586.02 --> 1589.14]  So if I do have a major outage, it will go down after 30 minutes.
+[1589.42 --> 1590.66]  So I don't think that's cheating.
+[1590.74 --> 1591.64]  That's just good engineering.
+[1592.42 --> 1597.98]  Yeah, well, I was getting tired of, you know, if my ISP goes down for two minutes, I would get a notification.
+[1598.32 --> 1602.08]  I was going to say, like, how have you managed to have ISP uptime that high at home?
+[1602.22 --> 1603.46]  That was the most impressive part.
+[1603.58 --> 1605.96]  Well, I've switched to in St. Louis.
+[1605.96 --> 1607.80]  Of course, we have spectrum, but...
+[1607.80 --> 1608.48]  Yeah, me too.
+[1608.66 --> 1609.20]  It sucks.
+[1609.40 --> 1614.06]  Yeah, it's difficult because the ISPs, they have a monopoly, basically.
+[1614.30 --> 1619.58]  And another fun thing that I'm going to be trying, I actually just got last week a Starlink.
+[1619.84 --> 1620.28]  Awesome.
+[1620.28 --> 1622.58]  And I'm going to be testing it out.
+[1623.74 --> 1631.98]  My ultimate goal is to have, either through the router, I have an ASUS router, either through that or maybe through a Raspberry Pi.
+[1632.64 --> 1636.00]  I'm also testing a router build using a Raspberry Pi compute module.
+[1636.26 --> 1636.54]  Of course.
+[1636.54 --> 1642.84]  Having a redundant link that will automatically fail over and possibly do link aggregation.
+[1643.00 --> 1644.92]  But for now, I just care about the redundancy.
+[1645.38 --> 1647.22]  Just because I do work from home.
+[1647.50 --> 1648.06]  I do streaming.
+[1648.28 --> 1649.60]  I do video uploads.
+[1649.60 --> 1652.14]  And I just, I need a lot of bandwidth and I need reliability.
+[1652.14 --> 1656.14]  And I do want to host more besides just the Pi Dramble site.
+[1656.36 --> 1658.72]  I want to host my personal site here at some point.
+[1658.80 --> 1666.52]  I want to host some other things that are more high impact and, you know, could survive an outage of one of the two network links, which Starlink could give me.
+[1666.78 --> 1671.38]  I don't think we've seen many people discussing hosting services on Starlink, either.
+[1671.68 --> 1674.24]  I'd be curious to see what they allow, what can get through.
+[1674.90 --> 1675.60]  Have you heard much?
+[1676.10 --> 1677.38]  It's a mixed story there.
+[1677.48 --> 1680.10]  So they don't give you a consistent IP address.
+[1680.22 --> 1684.36]  And they also don't, they don't pass through traffic in a way that you can host directly from home.
+[1684.44 --> 1685.98]  So I'd have to use some sort of proxy.
+[1686.52 --> 1694.76]  And I, you know, I can have a, one of the VPSs I have at DigitalOcean or something like that pass through the traffic for me.
+[1695.12 --> 1695.22]  Sure.
+[1695.42 --> 1700.46]  So give us an idea of what other, so I heard you have a, sounded like you're running Drupal on a Raspberry Pi server.
+[1700.74 --> 1702.92]  Any x86 boxes in that mix we'd see?
+[1702.92 --> 1711.94]  I do have one x86 server that mostly what it's doing is allowing me to RDP into it and do Windows things when I need to.
+[1712.12 --> 1714.10]  It's running Windows 10 Pro.
+[1714.34 --> 1719.48]  And I use it for a lot of network testing because it has a Mellanox card inside of it.
+[1719.50 --> 1721.66]  So I can get 10 gig network tests done on it.
+[1722.20 --> 1724.80]  Especially if it's a long test that's going to take a few hours.
+[1724.94 --> 1727.44]  I don't want to do it on my main workstation, which is a laptop.
+[1727.88 --> 1730.04]  Because then it's stuck wherever I have it running.
+[1730.42 --> 1731.20]  Yeah, I know that.
+[1731.20 --> 1733.38]  Like, why did I start that job on the laptop?
+[1733.60 --> 1734.04]  Dang it.
+[1734.56 --> 1734.92]  Exactly.
+[1736.08 --> 1739.08]  And then you have to come back downstairs later and find it.
+[1739.64 --> 1746.02]  And then the other things that I do, I have a couple PIs that run around the clock doing just little tasks around the house.
+[1746.02 --> 1754.94]  Checking on things, keeping track of temperature and like my sump pump, checking the level of the pit and just logging that data.
+[1754.94 --> 1762.80]  The other thing that I have running right now, and this is part of the motivation for all this Pi experimentation, is I have a 2011 Mac Mini.
+[1763.32 --> 1764.06]  Super old.
+[1764.78 --> 1766.54]  The OS is not even supported on it.
+[1766.56 --> 1767.52]  I can't upgrade it anymore.
+[1767.98 --> 1771.84]  It's still my primary network storage device, which is terrible.
+[1771.84 --> 1777.68]  Like, I've set up all these different NASAs and things, and I still am using this Mac Mini, which has USB 2.
+[1778.00 --> 1784.74]  So my external 12 terabyte single hard drive, not a RAID, my single hard drive is running at USB 2 speed.
+[1784.86 --> 1789.78]  So I'm doing file copies with, you know, 20 gigs, 40 gigs at 30 megabytes per second.
+[1789.78 --> 1792.16]  So this would be a bad time to ask you how many terabytes.
+[1792.32 --> 1796.92]  One of the questions we tend to ask all of our guests is how many terabytes do you have on your LAN?
+[1796.96 --> 1800.18]  And we had Wendell on a few months ago, and I think he had a petabyte.
+[1800.62 --> 1803.48]  So maybe you won't quite match that.
+[1803.54 --> 1804.52]  But how many do you have, Jeff?
+[1804.72 --> 1805.44]  No, no.
+[1806.18 --> 1808.94]  Online right now, I have about 24 terabytes.
+[1809.36 --> 1813.26]  But in the house, I have about 60 or so.
+[1814.08 --> 1821.02]  There's a lot of terabytes of hard drives that are sitting on my desk over there that are being tested and not in use.
+[1821.12 --> 1825.76]  Because when you're testing, you don't want to have production data on a hard drive you're running benchmarks against.
+[1826.12 --> 1828.02]  Ready to go in that NAS you were talking about.
+[1828.58 --> 1829.40]  Yes, yeah.
+[1829.40 --> 1841.78]  And the other thing that I mentioned on, I don't remember if it was a video or a live stream, but my goal is at some point in the next year, if I can get a storage vendor to work with me, I would love to build a petabyte Pi.
+[1841.78 --> 1845.32]  Have one Raspberry Pi controlling a petabyte of storage.
+[1845.48 --> 1847.08]  I think that would be something fun.
+[1847.16 --> 1848.96]  It'd be 400 megabytes per second.
+[1849.50 --> 1852.22]  It'd be such a waste, but it'd be so cool to see that.
+[1852.60 --> 1854.72]  Petabyte Pi project rolls off the tongue, too.
+[1854.78 --> 1855.14]  I like it.
+[1855.22 --> 1855.92]  It's bop, bop, bop.
+[1856.20 --> 1856.60]  Exactly.
+[1856.96 --> 1859.60]  Is a petabyte 1,000 or 100 terabytes?
+[1859.70 --> 1860.36]  I can never remember.
+[1860.52 --> 1860.92]  1,000.
+[1861.32 --> 1862.02]  Oh, my goodness.
+[1862.18 --> 1863.06]  How would you even do that?
+[1863.76 --> 1864.16]  Wow.
+[1864.54 --> 1864.68]  Yeah.
+[1864.86 --> 1866.62]  You've got to get at least 100 hard drives.
+[1866.62 --> 1870.48]  So it would not be super fun to do the project.
+[1870.68 --> 1871.76]  I mean, it'd be super fun.
+[1871.96 --> 1881.76]  But the hardware, I would probably have to build a rack or something and figure out a place, maybe in my wood workshop or something, to try to fit that.
+[1881.98 --> 1885.36]  If you've got a 3D printer, you could probably rustle something up with one of those.
+[1885.54 --> 1886.18]  There you go.
+[1886.46 --> 1887.36]  How did I know?
+[1887.44 --> 1888.20]  How did I know?
+[1888.28 --> 1889.68]  That would be your suggestion, Alex.
+[1889.68 --> 1894.36]  Well, see, this is why I'm going to say subscribe to your channel, Jeff, because there's just some great videos over there.
+[1894.52 --> 1896.86]  And maybe one day I'll see that project on there.
+[1897.18 --> 1897.74]  I hope so.
+[1897.90 --> 1898.52]  That would be fun.
+[1898.76 --> 1904.20]  Well, Jeff, before we get out of here, I was wondering if there's any way you'd like to send people your channel or Twitter or something like that.
+[1904.62 --> 1908.10]  Everything is linked from my personal website, jeffgearling.com.
+[1908.62 --> 1913.40]  I started my personal site back in 2001 or 2002 or something like that.
+[1913.88 --> 1916.98]  And I like to have my data in my site.
+[1916.98 --> 1919.54]  So I typically post things preferentially there.
+[1920.46 --> 1924.22]  And, you know, I can't do video hosting and things like that.
+[1924.36 --> 1931.56]  I could, and I actually did at one point, but I realized that YouTube does it way better than I ever could with streaming and all that kind of stuff.
+[1931.66 --> 1933.92]  So I like to take ownership of that.
+[1934.08 --> 1936.96]  So jeffgearling.com is where I throw everything primarily.
+[1937.16 --> 1939.58]  And then you can go to the other sites from there.
+[1940.02 --> 1941.28]  We'll have a link in our show notes, too.
+[1941.38 --> 1942.26]  Thanks for joining us, Jeff.
+[1942.56 --> 1944.00]  Yeah, thanks so much for having me.
+[1944.00 --> 1947.28]  And a big thank you from me because you saved my bacon.
+[1947.84 --> 1951.20]  I can't count the number of times with the roles on Ansible Galaxy.
+[1951.46 --> 1952.68]  So huge, huge past Alex.
+[1952.84 --> 1953.78]  Thanks, current Jeff.
+[1956.82 --> 1959.42]  Well, now I'm even more excited about the Raspberry Pi.
+[1959.56 --> 1960.58]  Thanks to Jeff for coming on.
+[1960.62 --> 1964.74]  And of course, like we said, we have links to his channel and everything in the show notes.
+[1964.94 --> 1968.40]  And I want to mention you can find our sponsor, Cloud Guru, on social media.
+[1968.40 --> 1973.76]  It's just slash a Cloud Guru at YouTube, Twitter, Facebook, like all the social media platforms.
+[1973.84 --> 1974.68]  Just slash a Cloud Guru.
+[1974.80 --> 1975.88]  It's super, super easy.
+[1976.34 --> 1980.24]  And a big thank you to our members over at selfhosted.show slash SRE.
+[1980.46 --> 1982.54]  Our site reliability engineers support the show.
+[1982.86 --> 1987.54]  You guys get a limited ad feed and a little bit of extra post show every week.
+[1987.88 --> 1988.10]  Oh, yeah.
+[1988.10 --> 1989.74]  I haven't told you what I want to talk about yet.
+[1989.80 --> 1991.28]  That's coming up for the members.
+[1991.46 --> 1991.94]  No, no.
+[1992.00 --> 1993.32]  It's going to be a surprise to me, too.
+[1994.04 --> 1996.20]  And you can go to selfhosted.show slash contact.
+[1996.42 --> 1998.06]  That's the place to go to get in touch with us.
+[1998.06 --> 1999.78]  I'm on Twitter at ironicbadger.
+[2000.18 --> 2001.84]  Yeah, I'm there, too, at Chris LAS.
+[2002.06 --> 2004.66]  And the show is at selfhostedshow.
+[2004.80 --> 2006.78]  And don't forget the network at Jupyter Signal.
+[2007.26 --> 2008.20]  Thanks for listening, everyone.
+[2008.40 --> 2010.66]  That was selfhosted.show slash 41.

42： Don't Panic _summary.txt

@@ -0,0 +1,53 @@
+• Hitchhiker's Guide to the Galaxy reference
+• Discussing ideas for an AM morning show format
+• Review of movie and TV segments, including upcoming surprise review
+• WireGuard nearly merging into BSD kernel, link provided in show notes
+• NVIDIA unlocking GPU drivers for pass-through on consumer graphics cards
+• PCI pass-through complexities
+• Using dual-booting as an alternative
+• NVIDIA news and its implications on PC setup
+• Ubiquity Gear security breach and potential risks
+• Centralized controllers for IoT devices
+• Disappointment with Ubiquity's products and support
+• Decline of quality assurance (QA) in Ubiquity's firmware and software updates
+• Discussion of the Ubiquity breach and its handling by the company
+• Alternatives to Ubiquity devices, such as TP-Link
+• Concerns about the impact on Ubiquity's reputation and user base
+• Proposal for a community-built open-source solution for wireless networking
+• Idea of open-source firmware for existing hardware to decouple from cloud services
+• Discussion of the need for a more powerful, flexible, and secure solution for home and business use cases
+• A device called Corsair Commander Pro was purchased for fan control but only worked on Windows
+• The Linux kernel now supports native control of fans via a USB header, thanks to a driver added six months ago
+• To set up fan control on Linux, you need the 5.9 or later kernel and LM sensors installed
+• A blog post details the process for configuring PWM profiles and enabling the fan control service
+• The host uses Arch Linux with a small VM on an ESXi host and praises Linode's support of Linux
+• Linode is promoted as the cloud server provider used by the podcast, offering fast infrastructure and a wide range of distributions to choose from
+• Discussion with a volunteer from Discord about their self-hosting setup
+• Volunteer's hardware setup: Ryzen 3000 series, Proxmox, virtual machines (VMs)
+• Philosophy on using VMs vs. containers: preference for containerization
+• Volunteer's setup currently has 6 VMs and 1 LXC container with multiple Docker applications
+• Discussion about storage setup: moving storage out of the main VM to handle it directly on the host
+• Issue with running TrueNAS in a VM due to poor performance, including latency spikes and slow Nextcloud access
+• Discussion of past experiences with Scale, TrueNAS, and Proxmox
+• Preference for high-performance storage solutions that are easy to manage
+• Use of bind mounts in LXC containers
+• Backup strategy using Duplicati and a mix of Backblaze and S3
+• Consideration of switching to Restic for backups
+• Discussion of restoring from offsite backups and the importance of having data in multiple locations
+• Quote from Alan Jude: "If it doesn't exist in three places, it doesn't exist at all."
+• Discussing backup solutions, including using Backblaze and attempting to roll out a custom solution with Minio
+• Mention of Kim Sufi, a cheap dedicated server host from France that is part of OVH
+• Recommendation of the movie "The Social Dilemma" for its critique of social media algorithms
+• Discussion of self-hosted apps, specifically TTRSS as an RSS reader and NextCloud for file access
+• Critique of NextCloud's sync functionality, including issues with partial syncs and forgotten login information
+• Discussion about a project called Plausible, a self-hosted Google Analytics alternative
+• Features and benefits of Plausible, including beautiful UI and GDPR compliance
+• Comparison to Google Analytics and the desire to take back control from companies like Google
+• Conversation about Jake's storage setup, with four terabytes in his current pool
+• Discussion of Jake's media storage needs and intention not to grow his storage capacity
+• Course content includes administration, Docker, SQL server, Azure instances, and Visual Studio code integration
+• Link to course in show notes at selfhosted.show/42
+• Sponsor: Cloud Guru
+• Members can support the show and get ad-free feed at selfhosted.show/sre
+• Post-show discussion of personal topics and interests
+• Contact page and social media handles mentioned

42： Don't Panic _summary_corrected.txt

@@ -0,0 +1,53 @@
+• Hitchhiker's Guide to the Galaxy reference
+• Discussing ideas for an AM morning show format
+• Review of movie and TV segments, including upcoming surprise review
+• WireGuard nearly merging into BSD kernel, link provided in show notes
+• NVIDIA unlocking GPU drivers for pass-through on consumer graphics cards
+• PCI pass-through complexities
+• Using dual-booting as an alternative
+• NVIDIA news and its implications on PC setup
+• Ubiquity Gear security breach and potential risks
+• Centralized controllers for IoT devices
+• Disappointment with Ubiquity's products and support
+• Decline of quality assurance (QA) in Ubiquity's firmware and software updates
+• Discussion of the Ubiquity breach and its handling by the company
+• Alternatives to Ubiquity devices, such as TP-Link
+• Concerns about the impact on Ubiquity's reputation and user base
+• Proposal for a community-built open-source solution for wireless networking
+• Idea of open-source firmware for existing hardware to decouple from cloud services
+• Discussion of the need for a more powerful, flexible, and secure solution for home and business use cases
+• A device called Corsair Commander Pro was purchased for fan control but only worked on Windows
+• The Linux kernel now supports native control of fans via a USB header, thanks to a driver added six months ago
+• To set up fan control on Linux, you need the 5.9 or later kernel and LM sensors installed
+• A blog post details the process for configuring PWM profiles and enabling the fan control service
+• The host uses Arch Linux with a small VM on an ESXi host and praises Linde's support of Linux
+• Linde is promoted as the cloud server provider used by the podcast, offering fast infrastructure and a wide range of distributions to choose from
+• Discussion with a volunteer from Discord about their self-hosting setup
+• Volunteer's hardware setup: Ry zen 3000 series, Proxmox, virtual machines (VMs)
+• Philosophy on using VMs vs. containers: preference for containerization
+• Volunteer's setup currently has 6 VMs and 1 LXC container with multiple Docker applications
+• Discussion about storage setup: moving storage out of the main VM to handle it directly on the host
+• Issue with running True NAS in a VM due to poor performance, including latency spikes and slow Nextcloud access
+• Discussion of experiences with Scale, True NAS, and Proxmox
+• Preference for high-performance storage solutions that are easy to manage
+• Use of bind mounts in LXC containers
+• Backup strategy using Duplicate and a mix of Back blaze and S3
+• Consideration of switching to Rustic for backups
+• Discussion of restoring from offsite backups and the importance of having data in multiple locations
+• Quote from Alan Jude: "If it doesn't exist in three places, it doesn't exist at all."
+• Discussing backup solutions, including using Back blaze and attempting to roll out a custom solution with Mini
+• Mention of Kim Sufi, a cheap dedicated server host from France that is part of OVH
+• Recommendation of the movie "The Social Dilemma" for its critique of social media algorithms
+• Discussion of self-hosted apps, specifically TTRSS as an RSS reader and Nextcloud for file access
+• Critique of Nextcloud's sync functionality, including issues with partial syncs and forgotten login information
+• Discussion about a project called Plausible, a self-hosted Google Analytics alternative
+• Features and benefits of Plausible, including beautiful UI and GDPR compliance
+• Comparison to Google Analytics and the desire to take back control from companies like Google
+• Conversation about Jake's storage setup, with four terabytes in his current pool
+• Discussion of Jake's media storage needs and intention not to grow his storage capacity
+• Course content includes administration, Docker, SQL server, Azure instances, and Visual Studio Code integration
+• Link to course in show notes at selfhosted.show/42
+• Sponsor: Cloud Guru
+• Members can support the show and get ad-free feed at selfhosted.show/sre
+• Post-show discussion of personal topics and interests
+• Contact page and social media handles mentioned

42： Don't Panic _transcript.txt

@@ -0,0 +1,604 @@
+[0.00 --> 3.28]  Episode 42, the title can mean only one thing.
+[3.58 --> 6.24]  Yes, it is a Hitchhiker's Guide to the Galaxy reference.
+[6.64 --> 8.34]  Oh, and I didn't bring my towel.
+[8.66 --> 9.62]  Oh, well, don't panic.
+[10.04 --> 11.04]  Hello, people.
+[11.42 --> 11.90]  Wake up.
+[12.10 --> 13.34]  Chris and the Badger.
+[13.72 --> 14.20]  Mornings.
+[14.20 --> 15.94]  All right, let's go, let's go, let's get up.
+[16.06 --> 17.76]  Or whenever you happen to listen to it, I guess.
+[18.00 --> 19.56]  On self-hosted.show.
+[20.28 --> 21.52]  Oh, we're bringing that back, are we?
+[21.62 --> 22.28]  Okay, cool.
+[23.48 --> 24.52]  I'm going in with this.
+[24.58 --> 25.34]  I love this.
+[25.34 --> 25.80]  We are.
+[26.00 --> 28.90]  I think you and I would have a great AM morning show.
+[28.90 --> 30.70]  We need to lean into that a bit more, yeah.
+[30.82 --> 31.16]  We do.
+[31.46 --> 37.02]  We'd be doing the traffic on the 15s, and we'd also be taking people's tech questions and
+[37.02 --> 42.24]  discussing the news of the day, and we'd have a movie review segment and a TV review segment.
+[42.36 --> 49.92]  I know you're going to give us a surprise TV review later in the show.
+[50.30 --> 50.54]  Yeah.
+[51.22 --> 54.76]  I might have interrupted an interview with an impromptu movie review, yes.
+[56.80 --> 58.24]  It just makes me laugh.
+[58.24 --> 58.98]  I love it, Alex.
+[59.40 --> 61.28]  But, you know, I think we'd have a great morning show.
+[61.42 --> 63.36]  And we'd have our friends on, right?
+[63.44 --> 67.28]  Like, we'd call Alan on and we'd give him a hard time about FreeBSD.
+[67.60 --> 68.38]  That'd be pretty great.
+[68.82 --> 69.14]  Yes.
+[69.64 --> 71.76]  That would be rather awkward at the moment, wouldn't it?
+[72.00 --> 72.34]  Yeah.
+[72.52 --> 72.76]  Yeah.
+[72.76 --> 75.74]  We'd ask him if he's got WireGuard set up, so that way we could do it.
+[76.00 --> 77.50]  We could do it over at WireGuard.
+[79.58 --> 82.80]  We should put a link in the show notes so people don't know what we're talking about.
+[82.80 --> 83.42]  Oh, yeah.
+[83.52 --> 85.12]  Quick too long didn't read.
+[85.84 --> 90.52]  WireGuard nearly got merged into the BSD kernel and the code was of questionable quality.
+[90.78 --> 96.16]  So if you have any questions about that, there is a link in the show notes to Jim Salter's Ask Technica breakdown of this.
+[96.74 --> 100.26]  You will probably come away rather salty with BSD.
+[100.58 --> 101.90]  Just full warning.
+[101.90 --> 103.92]  So, yeah, enjoy that.
+[104.22 --> 107.68]  But in the meantime, I want to say thanks to A Cloud Guru for sponsoring this here episode.
+[107.82 --> 111.62]  They are the learning in cloud, Linux, and other modern tech skills.
+[111.92 --> 114.12]  Hundreds of courses and thousands of hands-on labs.
+[114.22 --> 114.72]  Get certified.
+[114.88 --> 115.28]  Get hired.
+[115.66 --> 117.96]  Get learning at acloudguru.com.
+[118.38 --> 123.78]  But speaking of that post over at Ars Technica, you also had a new post over at Ars Technica.
+[124.34 --> 126.38]  And this is a brilliant one.
+[126.38 --> 131.54]  How to achieve smart home nirvana or home automation without a subscription.
+[131.90 --> 132.70]  Also very clever.
+[132.84 --> 135.02]  Were you stuck between two titles, Alex?
+[135.22 --> 138.66]  And congratulations also on your first post at Ars Technica.
+[139.00 --> 139.36]  Thank you.
+[139.42 --> 142.50]  Yes, that was rather a life box ticked last week.
+[142.78 --> 144.10]  It was a war of two titles, wasn't it?
+[144.40 --> 144.92]  It was.
+[145.06 --> 148.88]  Actually, I was working with their editors and they had about six titles to choose from.
+[149.00 --> 155.12]  So we ended up picking two halves of two different titles that didn't belong together and then kind of like munging them together.
+[155.36 --> 155.76]  Wow.
+[155.84 --> 158.56]  Could you imagine having people like help us come up with titles?
+[158.56 --> 163.20]  Like you and I like have to like call each other up after the show and be like, oh, what are we going to call this one?
+[163.26 --> 163.98]  We completely forget.
+[164.06 --> 165.86]  We walk away and don't even title the show.
+[166.10 --> 166.48]  We do.
+[167.00 --> 167.98]  All the time.
+[169.88 --> 176.66]  Hey, so did you see in the news this week that NVIDIA have finally seen Sense and unlocked their GPU drivers for pass-through?
+[176.98 --> 178.36]  I did see this in the news.
+[178.42 --> 181.40]  I didn't go too far into it because I figured I'd pick your brain.
+[181.52 --> 184.66]  This must be a shot in the arm for virtualization.
+[184.66 --> 185.86]  I'd say so, yeah.
+[186.16 --> 189.32]  To recap, you know, the high level of why this is a big deal.
+[190.04 --> 198.70]  NVIDIA previously locked down their consumer graphics cards from being air quotes supported on GPU pass-through.
+[198.86 --> 207.92]  So they would show an error code 43, an infamous error code 43 in the Windows device manager rather than loading and just working as normal.
+[207.92 --> 217.60]  So what you would have to do is hide the fact that the VM was running as a VM from the VM, which has some minor performance implications, only minor.
+[218.16 --> 222.16]  But what this does from NVIDIA is it basically says, yeah, okay, guys, cool.
+[222.26 --> 228.94]  Go ahead and take our consumer level graphics cards, pass them through to, you know, guests and do gaming and what have you.
+[229.04 --> 230.62]  And, you know, go nuts.
+[231.06 --> 233.36]  I don't even know if I have a rig to try this on these days, Alex.
+[233.38 --> 234.48]  Have you had a chance to try this?
+[234.78 --> 237.10]  I don't actually run pass-through very much these days.
+[237.10 --> 245.04]  I ended up basically giving up because, you know, you and I talked about this a long time ago on Linux Unplugged 308.
+[245.56 --> 249.34]  And we talked about all the different rigmarole that surrounds PCI pass-through.
+[249.44 --> 252.48]  And all of that still applies, even with this NVIDIA news.
+[252.68 --> 253.70]  All of that still applies.
+[254.64 --> 260.18]  So you're going to need a way of switching your monitor inputs, of switching your keyboard and mouse inputs and all that kind of stuff.
+[260.22 --> 264.10]  And I have 144 hertz gaming monitor in front of me here.
+[264.10 --> 272.46]  And trying to find a KVM switch that can support that and Thunderbolt from my MacBook Pro, it's just a pain in the bum.
+[272.60 --> 276.20]  So I ended up just dual booting these days.
+[276.44 --> 278.90]  You know, when I want to do some Windows stuff, I reboot.
+[279.30 --> 281.70]  And when I want to do some Linux stuff, I reboot.
+[282.08 --> 283.84]  And it's fine.
+[283.90 --> 285.06]  It's a bit of a pain, but it's fine.
+[285.06 --> 290.62]  Yeah, there is a line where you have to go, how much is it worth virtualizing versus just dual booting?
+[290.70 --> 291.74]  I totally get that.
+[292.28 --> 294.22]  That's a line I don't really often cross.
+[294.40 --> 299.32]  Like, I'm legitimately at a loss of even – I don't know why I'd install Windows right now.
+[299.36 --> 301.58]  I don't think I've installed Windows.
+[302.00 --> 303.52]  I definitely haven't installed it in 2021.
+[304.46 --> 306.24]  And I don't know if I installed it.
+[306.86 --> 310.56]  I must have at least installed it once in 2020.
+[310.78 --> 311.68]  But maybe that was it.
+[312.00 --> 315.38]  I really have over the years just sort of – this is not a brag.
+[315.76 --> 321.24]  I just – because I have in other places used Macs for special tools that other people probably would have used a Windows box.
+[321.32 --> 322.72]  So it's not like I have some superpower.
+[323.32 --> 327.90]  But it's just I have over the times just kind of migrated completely away from Windows.
+[327.90 --> 336.06]  Yeah, the only things I really use it for is Fusion 360, so 3D modeling for my printing stuff, which I can also do on the Mac as well.
+[336.10 --> 337.66]  So I don't really need Windows there.
+[338.20 --> 342.26]  I use it for Blue Iris, as we often talk about, on a separate system.
+[342.50 --> 343.28]  I could see that.
+[343.50 --> 345.40]  In terms of the desktop, yeah.
+[345.50 --> 348.48]  I mean, VS Code takes care of a lot of my coding stuff.
+[348.66 --> 352.94]  WSL 2 takes care of a lot of the SSH type stuff.
+[353.02 --> 355.40]  And the new Windows terminal is actually quite nice.
+[355.40 --> 366.36]  So, I mean, I spend a lot more time in Windows than I think I admit to myself these days, even though it doesn't really feel like Windows anymore because they've basically shoehorned Linux onto the side of it.
+[367.66 --> 370.16]  Okay, I feel like there's also an elephant in the room this week.
+[370.76 --> 377.70]  You and I have talked about Ubiquity Gear a bit on this show, and they have been in the news in a bad way.
+[378.32 --> 382.88]  Some serious security potential leaks, I guess.
+[382.88 --> 407.20]  According to someone that Brian Krebs spoke to on his blog, he writes that a cybercriminal gained administrative access to Ubiquity's AWS databases via stolen credentials, perhaps like an employee's LastPass account, it looks like, and then got root admin access, that's what they say, to the AWS accounts, S3 buckets, application logs, secrets for single sign-on cookies, all databases,
+[407.20 --> 411.20]  including databases that include user credentials.
+[411.20 --> 424.92]  There's even, according to some people who've come forward, supposedly been backdoor software that they found, that Ubiquity IT staff found, that the situation is so serious that certain people have been fired.
+[425.06 --> 426.76]  There's a lot going on.
+[427.22 --> 431.64]  And I'm wondering how you feel as somebody who's, I think, running a fair amount of their gear.
+[431.64 --> 432.74]  I certainly am, yeah.
+[432.78 --> 434.80]  I have three access points in this house.
+[434.96 --> 441.04]  I have half a dozen that I manage in England for my family across two or three different, you know, houses.
+[441.96 --> 451.54]  And, you know, from that perspective, having a centralized controller where all of these devices talk back to that runs on Linode is, for me, very convenient.
+[452.30 --> 458.14]  And so far as I understand it anyway, there is no risk to people who self-host the Unify controller.
+[458.14 --> 458.82]  Right.
+[459.34 --> 465.44]  If, however, you're running one of their cloud keys or a dream machine or something that requires you to authenticate with their cloud,
+[466.04 --> 475.26]  you may well want to change some passwords and possibly even consider, you know, not using Ubiquity stuff in that manner anymore.
+[475.26 --> 481.72]  Because, you know, the manner of the breach was that an employee's AWS S3 bucket key was compromised.
+[481.72 --> 488.32]  So we have to assume that the attackers got access to everything stored.
+[488.42 --> 494.60]  Passwords, I mean, they may well be hashed and salted, but we can break passwords with enough compute, you know.
+[495.16 --> 498.82]  Application logs, databases, database credentials.
+[499.30 --> 504.26]  All of that stuff that's in there, even just IP records, it's all bad.
+[504.50 --> 505.60]  It's all really bad, Alex.
+[505.60 --> 515.66]  And that's kind of where I was going with this is I quietly for the last couple of years have been progressively more and more disappointed with Ubiquity.
+[515.90 --> 523.30]  While my friends, like you and others around me, have seemed pretty solid with them, I have been wondering if things haven't been getting a little sour.
+[524.26 --> 526.92]  I don't feel like their latest batch of products have been that solid.
+[526.92 --> 532.54]  I have not liked some of their answers around the controller limitations and some of their solutions.
+[532.76 --> 535.28]  And it just seemed like a power grab in some circumstances.
+[535.66 --> 541.12]  And it seems like this is an indication that not all is well in HQ.
+[541.66 --> 543.62]  The QA has for sure been declining.
+[543.78 --> 553.50]  You know, there's been several firmware upgrades for the actual APs themselves, as well as the controller software that have nuked people's databases and history and stuff like that.
+[553.50 --> 560.24]  I wonder if maybe just some original people left the company a while ago and it's been in decline or if their prioritization has changed.
+[560.34 --> 561.38]  But where do you go to?
+[561.46 --> 562.54]  Like, what do you change to?
+[562.80 --> 565.60]  Well, I actually asked Jim on Twitter what he thought.
+[565.74 --> 568.28]  And he's been recommending there's a bunch of TP-Link devices.
+[569.12 --> 572.44]  And Tom from Lawrence Systems just got a bunch in to review on YouTube.
+[572.66 --> 577.16]  So if you're interested in some Ubiquity alternatives, they are out there.
+[577.78 --> 579.98]  But I'll tell you what worries me the most about this breach.
+[579.98 --> 586.30]  It's not necessarily that it happened because, unfortunately, these things are going to happen at some point to every company.
+[586.84 --> 589.88]  What matters more is how a company responds.
+[590.96 --> 594.90]  And Ubiquity tried to basically cover this up.
+[595.36 --> 597.28]  They didn't deny, I suppose is more accurate.
+[597.46 --> 598.86]  They didn't deny these claims.
+[598.86 --> 610.42]  And it took them several days, more than a week, to admit responsibility and basically inform their user base that some of their stuff might be boned.
+[610.84 --> 610.94]  Yeah.
+[611.10 --> 620.50]  And on top of that, it seems like it's taken some insiders to come out and leak information to well-known people like Krebs to get the complete picture, which is disappointing.
+[620.50 --> 622.78]  Yeah, I think you just hit the nail on the head there.
+[622.84 --> 623.40]  It's disappointing.
+[624.14 --> 632.90]  I mean, Ubiquity made their name through basically making people realize how crappy consumer-grade gear is.
+[633.56 --> 640.06]  And, you know, they're providing Cisco-grade ideas and hardware for consumer-grade prices.
+[640.06 --> 645.98]  But with these kinds of breaches and behavior as a company, I'm struggling.
+[646.22 --> 655.94]  I mean, the access point that I'm looking at behind my monitor here, I first installed into a house that I lived three houses ago, six, seven years ago.
+[656.06 --> 657.24]  And it's not Mr. Beat.
+[657.32 --> 658.06]  It still works perfectly.
+[658.96 --> 661.04]  It's had all the firmware updates and that kind of stuff.
+[661.42 --> 668.94]  But there was that one issue with the controller a few months ago where I ended up having to completely rebuild my Unify controller because of poor software QA.
+[668.94 --> 671.56]  It's critical infrastructure in my house.
+[671.78 --> 672.76]  Okay, it's not a hotel.
+[673.04 --> 676.96]  It's not a commercial setting where a lot of people do deploy Unify gear into.
+[677.58 --> 680.20]  But if it happens to me, it's going to happen to those people as well.
+[680.44 --> 686.34]  And it only takes one or two or three incidents before your brand name is completely trashed.
+[686.34 --> 708.34]  And people are already talking about just going back to consumer-grade stuff like mesh networks like Aero and, you know, all these other, you know, not as technically accomplished solutions that have, you know, POE backhaul and stuff like that in favor of something that is possibly even more leaky because it requires more cloud connectivity.
+[708.52 --> 708.86]  I don't know.
+[708.86 --> 710.48]  But what's the solution?
+[711.18 --> 714.52]  I'm probably just going to wait and see how this turns out for the next six months.
+[714.80 --> 718.58]  But my next AP will probably not be a Unify one.
+[719.00 --> 723.78]  Wouldn't it be something if the community stepped forward and built something that we could flash again?
+[724.10 --> 724.64]  Mesh networks?
+[725.30 --> 725.82]  Be amazing.
+[726.14 --> 726.72]  Oh, it'd be cool.
+[726.80 --> 727.22]  I tell you what.
+[727.22 --> 739.30]  If somehow we could open these devices up, these Unify devices we already have, and then put like a Tasmota style, completely divorcing ourselves of Unify, of Ubiquity, sorry.
+[740.26 --> 741.60]  You know, own the hardware.
+[741.74 --> 743.24]  I keep banging on about this, don't I?
+[743.30 --> 744.54]  But own the hardware.
+[744.72 --> 746.50]  It's not dependent on a cloud service then.
+[746.96 --> 748.94]  It does seem like that is exactly what we need.
+[748.94 --> 759.58]  It's something we could reflash and load a common OS on that has a common set of standards and interfaces and a web UI, like you used to do with the old Linksys routers.
+[759.64 --> 762.52]  You know, those things are still being sold today, those old Linksys routers.
+[762.66 --> 763.88]  Open WRT, yeah.
+[763.88 --> 770.62]  We just need a newer version of that, something more powerful with different hardware options, essentially like the Ubiquity options.
+[770.96 --> 783.06]  Because you're right, you need something for folks that want to run PoE and then, you know, plug an AP at the end of a barn somewhere or at the end of a building somewhere and they can only run one cable.
+[783.20 --> 784.76]  Like, you've got to have something for that solution.
+[785.10 --> 793.66]  I think your use case, too, where you've got several buildings and you want to manage all of the APs with one interface is also totally legitimate and extremely common.
+[793.88 --> 799.74]  It's so useful when my dad rings me up and he's like, oh, my Wi-Fi is not working in the bedroom.
+[799.88 --> 804.32]  I can go in and see the AP has dropped from gigabit down to megabit, for example.
+[804.52 --> 807.94]  And I'm like, oh, we just need to reboot the AP and we're good to go.
+[808.26 --> 811.20]  But there's a way to do that, Alex, you know, and get that central dashboard.
+[811.20 --> 816.22]  I know you don't use it much, but something we should talk about at some point on the show, maybe, is Cockpit.
+[816.68 --> 823.16]  One of the things I appreciate about Cockpit is they have come up with a way to allow you to manage multiple servers.
+[823.16 --> 830.16]  You can go to one UI, though, log into one web server, and you can select all your servers and manage them.
+[830.58 --> 832.08]  And it has to be set up in a special way.
+[832.16 --> 835.58]  And there's some security precautions you have to take, but it's a very secure setup.
+[835.78 --> 837.96]  And so maybe something like that could be done.
+[838.76 --> 839.08]  I don't know.
+[839.10 --> 840.68]  Maybe somebody out there in the community knows.
+[841.14 --> 841.22]  Maybe.
+[841.22 --> 841.34]  Maybe.
+[841.74 --> 854.64]  So I found out this week that a device I purchased nearly two years ago on some Black Friday sale, you know, I bought it thinking, oh, yeah, this is going to solve all my problems with my fans.
+[854.64 --> 867.88]  Because quite often when you buy a server-grade motherboard, the fan control headers are designed for server-grade fans, which spin at crazy high RPMs and draw crazy amounts of current and stuff like that.
+[868.48 --> 878.10]  And so when you put a consumer-grade fan on one of these motherboards, it kind of ramps up and then ramps down and ramps up and ramps down because it's not getting enough of a signal to think it's got enough RPMs.
+[878.10 --> 880.02]  Anyway, it's this whole thing.
+[880.36 --> 883.36]  So I bought this device called the Corsair Commander Pro.
+[883.72 --> 892.56]  It plugs into a USB header on the motherboard, controls LED lighting, it controls fans, and has some temperature probes attached to it.
+[893.30 --> 895.96]  But the downside was this device was Windows only.
+[896.56 --> 903.46]  To my surprise and absolute delight, six months ago, this device has been added to the Linux kernel.
+[903.46 --> 911.22]  There's been a driver added to the Linux kernel, so you can now natively control fans via a USB header on Linux.
+[911.72 --> 912.88]  I love it when that happens.
+[913.64 --> 915.32]  And you're always surprised, like, my little thing?
+[915.58 --> 917.18]  The little thing that I care about?
+[917.26 --> 917.80]  That's coming?
+[918.18 --> 919.30]  That's always the best feeling.
+[919.58 --> 921.40]  So I wrote a small blog post about it.
+[921.50 --> 926.20]  It doesn't require an awful lot of elbow grease to get set up.
+[926.46 --> 930.46]  But you do need to have the 5.9 or later kernel.
+[930.46 --> 933.56]  And then you need to make sure you've got LM sensors installed.
+[933.76 --> 938.18]  And then there's a couple of other instructions in the blog post about how you configure the PWM profiles.
+[938.80 --> 941.74]  And then once you've done that, you just enable the fan control service.
+[941.90 --> 946.66]  I mean, I'm using a very tiny, tiny little Arch VM on my ESXi host.
+[947.42 --> 951.86]  I think it's using 256 megs of RAM, for example, and 4 gigabytes of disk.
+[952.24 --> 955.44]  Perfect use case for Arch because I don't want anything else.
+[955.44 --> 956.66]  And I want a modern kernel.
+[957.58 --> 959.60]  And that's exactly what Arch gives me there.
+[960.46 --> 963.08]  Linode.com slash SSH.
+[963.18 --> 966.50]  Go there to get $100.68 credit towards a new account.
+[966.70 --> 967.90]  And, of course, you support the show.
+[967.98 --> 968.36]  $100!
+[969.12 --> 970.04]  And that's a lot.
+[970.16 --> 971.70]  You can really try out Linode.
+[971.82 --> 974.44]  And you support the self-hosted podcast.
+[974.62 --> 976.10]  That's like a win-win for everybody.
+[976.60 --> 978.00]  Linode is our cloud server provider.
+[978.14 --> 982.42]  When we're building or any kind of testing that we're doing, we do it on Linode.
+[982.42 --> 987.04]  And because the price is so great, it makes it possible for a small team to have killer infrastructure.
+[987.30 --> 996.62]  That's one of the things that I feel like is our secret sauce here at JB is we can have access to infrastructure that is crazy fast.
+[996.70 --> 998.16]  11 data centers around the world.
+[998.72 --> 1000.04]  Really fast network connections.
+[1000.20 --> 1001.08]  Really fast machines.
+[1001.08 --> 1004.94]  Their dedicated CPU rigs have those AMD EPYC CPUs in them.
+[1005.52 --> 1010.46]  And they have been independently verified as some of the fastest CPUs in cloud computing.
+[1010.80 --> 1017.28]  But one of the things I think that's great about them is when I'm building or testing something, they have a ton of distributions to choose from.
+[1017.46 --> 1019.36]  Basically, all the distributions you'd want to deploy.
+[1019.48 --> 1022.52]  And even some I'm not sure you'd want to deploy in production.
+[1022.80 --> 1023.10]  Arch.
+[1023.52 --> 1024.06]  But are there.
+[1024.16 --> 1025.86]  And I extremely appreciate that.
+[1025.86 --> 1029.12]  But what I really get about Linode is their love for Linux.
+[1029.22 --> 1030.66]  That's what got them into this.
+[1031.08 --> 1036.26]  That's why they started in 2003 is because they were in love with the technology itself.
+[1036.40 --> 1040.32]  They saw where it was going, what virtualization was going to bring to the market.
+[1040.50 --> 1043.20]  And so they got in before AWS or anyone else.
+[1043.20 --> 1045.18]  They started so long ago.
+[1045.46 --> 1048.20]  And yet they don't do like a million things.
+[1048.94 --> 1051.92]  They're not like a bookstore and a movie platform.
+[1051.92 --> 1057.28]  They really just focus on doing the absolute best cloud computing possible.
+[1057.66 --> 1059.60]  And they're independently owned even today.
+[1059.76 --> 1062.70]  And they're dedicated to offering the best virtualized cloud computing.
+[1062.92 --> 1065.78]  If it runs on Linux, it runs on Linode.
+[1066.12 --> 1067.52]  Also, check a link on our show notes.
+[1067.62 --> 1069.78]  We'll have a link to their Top Docs talk.
+[1070.10 --> 1070.46]  That's right.
+[1070.52 --> 1071.48]  Top Docs talk.
+[1071.90 --> 1075.48]  And they have one about the benefits of using infrastructure as code.
+[1075.80 --> 1077.52]  And, you know, that's something we're big fans of.
+[1077.66 --> 1079.08]  So check in the notes for that.
+[1079.40 --> 1081.16]  Linode.com slash SSH.
+[1081.16 --> 1084.26]  Go there, support the show, get $100 in 60-day credit.
+[1084.76 --> 1088.32]  And, of course, check out all the features of Linode.
+[1088.72 --> 1090.58]  Linode.com slash SSH.
+[1092.16 --> 1098.26]  Well, a few weeks ago, I promised something along the lines of a self-hosted community deep dive.
+[1098.68 --> 1103.44]  You know, every so often we're going to have somebody from the self-hosted community come on and chat with us
+[1103.44 --> 1112.02]  and sort of talk about the apps they run, why they run them, you know, what they wish that their setup did that it doesn't currently do.
+[1112.14 --> 1116.44]  And a lot of, hopefully, discussions about why they made some of the decisions that they made.
+[1117.00 --> 1121.22]  Hopefully it'll be an interesting portal into some of our community members for you.
+[1121.22 --> 1128.18]  And the first volunteer or the first glutton for punishment is the orange one from our Discord server.
+[1128.30 --> 1129.04]  Hey, Jake, how are you doing?
+[1129.64 --> 1133.28]  Hi. Yeah, I think I feel like maybe the correct term for this is victim.
+[1134.24 --> 1135.14]  Ah, yes, yes.
+[1135.18 --> 1137.62]  Yes. But yeah, no, it's great.
+[1137.78 --> 1138.50]  It's great to be here.
+[1138.66 --> 1139.70]  It's going to be good.
+[1139.70 --> 1143.66]  Well, it's been interesting trying to schedule three different people in three different time zones.
+[1143.78 --> 1147.60]  So thank you for joining us at, I think, what is 10.30 p.m. UK time?
+[1148.24 --> 1149.68]  Yeah, it's 10.30.
+[1149.72 --> 1153.72]  I've got to be up in nine hours for another seven and a half hours of work.
+[1153.90 --> 1155.06]  That used to be your life, Alex.
+[1155.36 --> 1156.72]  Yeah, pre-dad life, huh?
+[1156.84 --> 1157.96]  Sleep is a distant memory.
+[1159.58 --> 1162.00]  All right, so why don't we dive in with the first question then?
+[1162.28 --> 1165.10]  And let's talk a little bit about your hardware setup.
+[1165.10 --> 1169.04]  So specifically talking about the stuff you have at home and things like that.
+[1169.04 --> 1170.94]  Talk us through some of the stuff you've got there.
+[1171.28 --> 1174.16]  Most of my setup is at home.
+[1174.28 --> 1176.50]  The sort of self-hosting life is very much.
+[1176.58 --> 1179.96]  I run everything on my LAN sort of as normal.
+[1181.06 --> 1188.04]  Most of my setup is a single machine because running things over the network is a bit funky.
+[1188.80 --> 1193.40]  My main rig is a Ryzen 3000 series.
+[1193.90 --> 1196.66]  3700X is the sort of beating heart of it.
+[1197.58 --> 1198.68]  Yeah, various other parts.
+[1198.68 --> 1202.96]  It runs Proxmox because virtual machines are great.
+[1202.96 --> 1204.62]  Do you use VMs for a lot of stuff?
+[1204.70 --> 1207.44]  Because I know you're into sort of the one big VM.
+[1207.74 --> 1215.64]  We often have this discussion on Discord about the one big VM versus lots of smaller like LXC containers and Docker containers and things like that.
+[1215.74 --> 1218.12]  What's your philosophy on that?
+[1218.12 --> 1222.14]  If I'm running a hypervisor with VMs, I'd rather not do that.
+[1222.14 --> 1233.54]  I'd rather have sort of everything nicely containerized to fully take advantage of VMs in their sort of natural habitat of what they're good for.
+[1233.54 --> 1239.56]  So I think my setup is currently six VMs or so spread most of the different uses.
+[1239.56 --> 1247.88]  There is still one single LXC container which runs Docker, which has most of my Docker applications in.
+[1248.00 --> 1251.94]  There's probably 10 or so containers running under that.
+[1251.94 --> 1258.04]  Besides that, I've got a separate one for my monitoring applications.
+[1258.22 --> 1259.52]  That would be Prometheus.
+[1259.70 --> 1260.94]  Again, your advice.
+[1261.84 --> 1262.34]  Grafana.
+[1262.76 --> 1268.00]  I've got a separate VM for Home Assistant, which runs Home Assistant OS.
+[1268.00 --> 1276.22]  A couple other ones, one which deals with Ingress coming into my house, which is an interesting setup, which I'm sure we'll touch on later.
+[1277.40 --> 1280.30]  And yeah, various other little things.
+[1280.58 --> 1289.92]  The other place I've diverted away from what you've previously done is I've also moved the storage out of the one big VM.
+[1290.08 --> 1292.62]  And so storage is handled directly on the host.
+[1292.94 --> 1293.40]  Why is that then?
+[1293.40 --> 1300.50]  The main reason for that is I tried running TrueNAS in a VM and it installed great.
+[1300.86 --> 1302.28]  I could access all my files.
+[1302.44 --> 1307.42]  The issue was that performance was horrible, absolutely horrible.
+[1308.50 --> 1310.66]  I just got latency spikes everywhere.
+[1310.88 --> 1312.76]  Nextcloud, ground to halt.
+[1313.74 --> 1318.18]  SQ Lite over NFS is a really, really bad time.
+[1318.24 --> 1319.16]  I don't recommend it to anyone.
+[1319.60 --> 1321.08]  So talk us through that a little bit more then.
+[1321.08 --> 1323.52]  You know, performance was bad.
+[1323.62 --> 1327.58]  Were you passing through a disk controller to that VM or what were you doing?
+[1328.12 --> 1338.48]  So from some advice I got from, I'm sorry, I can't remember who it was on the self-hosted Discord, suggested using an LSI HPA.
+[1338.48 --> 1344.40]  That HPA I then passed in through regular PCI pass through into TrueNAS.
+[1345.18 --> 1359.46]  From there, regular mounted a very small two drive ZFS pool exposed via TrueNAS' built-in NFS sharing, which was super easy to do, which is great.
+[1359.46 --> 1363.06]  Mounted that as normal through Etsy FSTab.
+[1363.06 --> 1371.64]  And then from there, just pointing my Docker containers at it as if it was a directory in that container thing.
+[1371.72 --> 1379.14]  And because it was running entirely over the internal network inside the machine, latency-wise, it was absolutely tiny.
+[1379.14 --> 1382.00]  You're talking like fractions of milliseconds.
+[1382.48 --> 1385.44]  But for some unknown reason, it didn't like it.
+[1385.48 --> 1392.94]  Now, that might be because I went a little bit insane and decided to run TrueNAS scale rather than TrueNAS directly.
+[1393.36 --> 1399.58]  So this may be a performance regression with TrueNAS scale because at the time I ran it, it was in alpha.
+[1399.58 --> 1402.88]  And we know full well, don't run alpha software.
+[1403.28 --> 1405.62]  But I did anyway, just to try it.
+[1406.32 --> 1410.22]  Is scale the BSD one and core is the Linux one or is it the other way around?
+[1410.30 --> 1410.94]  I can never remember.
+[1411.08 --> 1411.58]  Other way around.
+[1411.78 --> 1416.36]  So scale is the Linux-y one, which at the time was in alpha.
+[1416.72 --> 1417.70]  So I tried it.
+[1417.90 --> 1420.40]  It didn't work great.
+[1420.90 --> 1426.34]  Yes, I have some thoughts on BSD this week after the whole WireGuard kernel merge thing.
+[1426.34 --> 1428.34]  But let's not derail your...
+[1428.34 --> 1429.12]  Yeah.
+[1429.58 --> 1431.54]  That's not a fun discussion.
+[1431.76 --> 1432.38]  It's all embarrassing.
+[1432.70 --> 1437.92]  After I tried scale out, it didn't work too well for me.
+[1437.98 --> 1447.58]  And I didn't want to try porting over to the actual core version of TrueNAS because keeping going with that process,
+[1447.58 --> 1455.96]  it meant I had to deal with issues where that one storage VM, as it were, would have to stay up and alive sort of all the time.
+[1455.96 --> 1466.06]  And if I needed to reboot that machine, that VM even, I would have to reboot sort of everything in the entire machine, which felt a bit like a faff.
+[1466.06 --> 1471.52]  And eventually I concluded, well, if I want high performance, I want things to be easy.
+[1471.52 --> 1482.54]  Then if I move the storage onto the actual host hypervisor under Proxmox, Proxmox has built-in support for ZFS because the OS is on ZFS.
+[1482.54 --> 1484.34]  So it just works.
+[1484.34 --> 1485.96]  It means latency is nice and low.
+[1485.96 --> 1496.88]  And because the majority of my applications live in LXC, there's the nice benefit of rather than using NFS to mount all of my data, I can use bind mounts.
+[1497.22 --> 1498.98]  And bind mounts are...
+[1498.98 --> 1507.78]  You have no network latency because it's just passing directories into containers in much the same way that you give bind mounts to Docker containers.
+[1507.78 --> 1514.04]  There's no extra latency, extra overhead, extra complexity around that.
+[1514.24 --> 1515.72]  It just works.
+[1516.16 --> 1518.40]  So it sounds like a lot of different application uses.
+[1518.40 --> 1523.76]  And it sounds like you have a pretty distinct line between what is a container and what should be a VM.
+[1523.76 --> 1529.44]  When I see complexity like this, I start to wonder, like, what's your backup strategy looking like?
+[1529.92 --> 1534.64]  My backup strategy at the moment is on that one Docker LXC.
+[1534.84 --> 1544.40]  There is a single instance of Duplicati, which backs up because that LXC specifically has access to my entire ZFS pool.
+[1545.12 --> 1550.76]  I can just take the entire pool, compress it up with Duplicati and push it up to...
+[1550.76 --> 1559.68]  Currently, there's a mixture of Backblaze and S3 for various bits, depending on how much I care about it.
+[1560.18 --> 1567.16]  I intend at some point in the maybe not too distant future to switch parts of that out to Restic.
+[1567.60 --> 1569.42]  Ah, good man. I was just about to ask you about that.
+[1570.40 --> 1572.80]  Duplicati is such a pain in the ass sometimes.
+[1572.96 --> 1577.62]  And, you know, it runs fine for weeks and weeks and then you log in and have a look at it.
+[1577.62 --> 1583.78]  And in the intervening time, stuff's just broken for seemingly no reason.
+[1583.90 --> 1585.18]  And it breaks silently.
+[1585.50 --> 1588.68]  I can only configure it through the UI, which you know how much I love that.
+[1589.34 --> 1596.54]  So Restic, I think, is something I'm really going to be looking into a lot in the future with Minio, with the S3 backend as well.
+[1596.76 --> 1598.78]  So you can use Restic with that.
+[1598.96 --> 1601.78]  So you use Backblaze and a little bit of S3.
+[1601.88 --> 1603.08]  So is that Amazon S3?
+[1603.42 --> 1603.80]  Yeah.
+[1603.80 --> 1605.04]  Wow, made of money, boy.
+[1606.16 --> 1611.18]  There's like a couple hundred meg in there just because I was testing stuff.
+[1611.66 --> 1615.12]  Like this was before when I was only backing up like the tiny bits.
+[1615.26 --> 1619.80]  And I concluded, well, if I'm just backing up the tiny bits, I might as well back up everything.
+[1620.26 --> 1621.90]  Well, object storage is perfect for that.
+[1622.12 --> 1623.28]  Exactly. 100%.
+[1623.28 --> 1626.04]  Let me ask you this then, because I'm picturing the audience.
+[1626.16 --> 1628.24]  Somebody's out there building their backup strategy right now.
+[1628.32 --> 1631.42]  If you were going to start again today, start fresh, how would you build it better?
+[1631.52 --> 1632.66]  What would you do differently?
+[1632.66 --> 1635.80]  What message would you send to a past version of yourself?
+[1636.08 --> 1639.32]  Past version would definitely be install backups sooner.
+[1639.88 --> 1646.62]  I'm very glad that I've never had a case where I've had to actually restore from an offsite backup.
+[1646.62 --> 1658.74]  I had one case where I had to restore from an offsite backup, which I still think is sort of a bug in Docker, where I was messing around with some weird Docker stuff.
+[1659.20 --> 1664.74]  And I went to log into Nextcloud a few hours later and the entire Nextcloud bind mount was empty.
+[1665.44 --> 1666.42]  Completely empty.
+[1666.52 --> 1668.36]  No app data, no files, no nothing.
+[1668.50 --> 1669.32]  Just gone.
+[1669.32 --> 1671.72]  I have no idea why it happened.
+[1671.94 --> 1677.86]  Fortunately, that morning I had done an onsite backup to a disconnected hard drive.
+[1678.20 --> 1686.72]  So a few hours of syncing files back, I lost, as far as I'm aware, no real data because I'd not made any changes.
+[1686.84 --> 1688.50]  But that was not fun.
+[1688.50 --> 1692.56]  So definitely anyone listening, I think Alan Jude says it best.
+[1692.62 --> 1695.38]  If it doesn't exist in three places, it doesn't exist at all.
+[1695.76 --> 1697.42]  Oh, you had to go and reference Alan, huh?
+[1698.42 --> 1699.18]  Yeah, I kind of did.
+[1699.24 --> 1704.04]  But it's also it's such a good point is that now my data exists on my server.
+[1704.04 --> 1710.42]  It also exists using ZFS send to a random shuck hard drive sitting on my desk.
+[1710.72 --> 1710.98]  Good man.
+[1711.14 --> 1715.70]  And then as well, like I say, backup to Backblaze, which has been absolutely great.
+[1715.78 --> 1720.98]  I did for a small amount of time decide, hey, what if I roll my own Backblaze?
+[1721.84 --> 1722.86]  Would not recommend it.
+[1723.08 --> 1731.06]  I had a $10 machine from Kim Sufi, which are a very cheap, dedicated server host out of France.
+[1731.06 --> 1735.20]  They're a subsidiary of OVH and we all know how OVH are doing right now.
+[1735.44 --> 1737.66]  Yeah, I hear their business is on fire at the minute.
+[1737.90 --> 1738.54]  Oh, Alex.
+[1738.80 --> 1739.34]  Too soon.
+[1739.50 --> 1740.04]  Too soon.
+[1740.30 --> 1740.88]  Too soon.
+[1741.40 --> 1742.74]  I thought it was funny.
+[1742.92 --> 1743.08]  Yeah.
+[1743.12 --> 1747.04]  So I tried running that and Minio and it worked fine.
+[1747.32 --> 1753.98]  But once I realized that I was backing up a server I owned to a server I owned, it was great.
+[1754.28 --> 1757.04]  But it was the Kim Sufi box was a bit finicky.
+[1757.04 --> 1758.10]  It was low powered.
+[1758.10 --> 1765.02]  Minio, as tiny as it is, it's much more resource heavy than I would expect it to be.
+[1765.80 --> 1768.70]  So should we talk a little bit about some of your favorite self-hosted apps?
+[1769.00 --> 1769.72]  Top three, maybe?
+[1770.22 --> 1777.36]  Oh, so I'd have to say the one I definitely use the most is TTRSS, which is an RSS reader,
+[1777.56 --> 1778.90]  my RSS reader of choice.
+[1778.90 --> 1783.82]  I do most of my content consumption via RSS.
+[1784.16 --> 1790.56]  All of my YouTube consumption is entirely via RSS because YouTube's algorithms and suggestions
+[1790.56 --> 1793.60]  and things like that are just, quite frankly, terrible.
+[1794.12 --> 1794.56]  That's amazing.
+[1794.68 --> 1799.52]  I think more people should do this because I watched a film the other night called The Social
+[1799.52 --> 1805.70]  Dilemma, which talks about how insidious those algorithms are in controlling what you see
+[1805.70 --> 1809.80]  and what you, eventually what you think and what you believe, you know, the ultimate conclusion.
+[1810.44 --> 1815.04]  If anybody's on the fence as to whether, you know, Facebook and Google and Twitter and
+[1815.04 --> 1820.38]  what have you are forces for good in the world or not, I recommend watching The Social Dilemma.
+[1820.58 --> 1821.44]  It might change your mind.
+[1821.86 --> 1822.82]  Anyway, as you were.
+[1823.32 --> 1825.14]  That's definitely one for my watch list as well.
+[1825.14 --> 1829.08]  Yeah, so TTRSS is definitely way up there.
+[1829.32 --> 1830.58]  What clients do you use for that?
+[1830.70 --> 1833.72]  I actually just entirely use the web UI mostly.
+[1834.10 --> 1834.50]  Cool.
+[1834.72 --> 1836.10]  It's easy and it works.
+[1836.52 --> 1840.42]  Other than TTRSS, I would have to say NextCloud is currently quite far up there.
+[1840.94 --> 1844.38]  That's been a really nice tool for just accessing files.
+[1845.00 --> 1848.78]  It's a little bit heavy for my needs, but it is, the plugins are great.
+[1848.98 --> 1850.82]  It's fast enough.
+[1850.82 --> 1855.20]  And the sync clients, when they work, they work really, really well.
+[1855.44 --> 1858.50]  See, everybody always says this, like, oh, the sync's a bit hit and miss.
+[1858.54 --> 1861.56]  And I know, Chris, you've had some actual experience with it losing data for you.
+[1861.64 --> 1865.74]  But I've used it now for, I guess, three years solid.
+[1866.02 --> 1868.80]  And it's just, NextCloud's just been really, really reliable for me.
+[1868.80 --> 1871.08]  So I've only had two issues with it.
+[1871.16 --> 1875.12]  One is that it doesn't do partial syncs.
+[1875.26 --> 1880.90]  So if you modify a small part in a very large file, it will sync the entirety of the large file.
+[1881.38 --> 1891.82]  I don't deal with large files, but I suspect if you guys are pushing around very large MP3s or uncompressed media, yeah, then it can be really, really slow.
+[1891.94 --> 1897.84]  The other issue I've had, or I did have, which I haven't had in a while, is it would keep forgetting who I am.
+[1897.84 --> 1899.26]  Oh, no big deal, right?
+[1899.62 --> 1901.84]  I know who I am, but it just forgets.
+[1902.56 --> 1908.76]  And it gets very difficult to sync anything if it just forgets who you are.
+[1909.10 --> 1910.60]  It just keeps logging me out.
+[1910.80 --> 1919.16]  I'd love to see them add LAN sync, too, because that's a fantastic feature when you power up a laptop and it hasn't been on the internet for maybe a week or more.
+[1919.50 --> 1926.42]  If you can sync from other nodes on the network directly, it's way faster and it reduces the demand on your internet connection.
+[1926.42 --> 1928.40]  I love that feature about Dropbox.
+[1928.72 --> 1939.86]  Also, I think Dropbox has some intelligence about the order in which they sync files and what operations sync first versus what operations can be queued, where NextCloud's CSync subsystem doesn't seem to support that.
+[1939.86 --> 1947.70]  So we've had situations where the NextCloud server is kind of like processing and syncing down some directory cleanup that we've done.
+[1948.52 --> 1952.36]  And maybe it's a significant amount of like just reorganizing or something.
+[1952.36 --> 1963.88]  And the client has to process all of those changes and operate all of those file system operations before it will process the sync command to send the new files up to the server.
+[1964.30 --> 1968.84]  And so we've literally just had editors on the other side waiting for files.
+[1968.84 --> 1971.56]  And so that stunk.
+[1971.66 --> 1973.50]  But what we did is we just changed the way we operate.
+[1973.62 --> 1977.28]  We don't make those kinds of changes on any kind of show day anymore.
+[1977.64 --> 1980.74]  We wait and we make sure we do it like with a couple of day buffer.
+[1980.88 --> 1982.48]  And we've adjusted the way we operate.
+[1982.70 --> 1983.76]  And we've made it work now.
+[1983.82 --> 1986.46]  We've been using it for, I mean, I don't know.
+[1986.64 --> 1987.42]  Alex, do you remember?
+[1987.62 --> 1990.30]  Since the sprint in 2019, right?
+[1990.54 --> 1991.78]  Yeah, since I appeared.
+[1992.02 --> 1992.48]  Yeah, roughly.
+[1992.84 --> 1993.42]  Yeah, right.
+[1993.42 --> 1995.30]  Since we brainstormed and started this show.
+[1996.78 --> 1998.54]  So and it's been running.
+[1998.82 --> 1999.68]  But yeah, it isn't ideal.
+[1999.96 --> 2001.36]  So what's your last pick then?
+[2001.70 --> 2011.20]  It's a project I've been involved with a little bit in sort of contributing and writing content for, which is probably also going to be a bit of a sore subject for some people.
+[2011.20 --> 2013.16]  It's an application called Plausible.
+[2013.92 --> 2018.10]  Plausible is a self-hosted Google Analytics alternative.
+[2018.68 --> 2020.24]  It's backed by a company.
+[2020.72 --> 2022.18]  There's a hosted offering.
+[2022.18 --> 2024.04]  It's really, really nice.
+[2024.14 --> 2025.76]  The UI is beautiful.
+[2026.48 --> 2028.58]  It's fully GDPR compliant.
+[2028.72 --> 2033.22]  So it only tracks the data that it needs to do to do its job.
+[2033.28 --> 2036.24]  It doesn't track things around various other places.
+[2036.24 --> 2037.74]  It's entirely self-hosted.
+[2037.86 --> 2042.22]  So I run my own instance, which tracks my own websites.
+[2042.38 --> 2043.94]  It doesn't track anything else.
+[2044.58 --> 2051.58]  And what that means is I can see which pages are getting the most traction, which ones aren't, where people are coming from.
+[2051.58 --> 2053.30]  And that's about it.
+[2053.30 --> 2054.60]  That looks great.
+[2054.84 --> 2055.82]  Yeah, really nice.
+[2056.20 --> 2057.00]  It's really nice.
+[2057.10 --> 2069.28]  I highly recommend it to anyone that's got a website, especially if they're running Google Analytics and want to sort of take back some of their control from Google and various other companies like that.
+[2069.28 --> 2070.34]  Uh-oh, ding dong.
+[2070.42 --> 2071.00]  You said it.
+[2071.54 --> 2072.62]  Take back control.
+[2072.86 --> 2074.28]  That's a trigger phrase for me.
+[2076.02 --> 2077.16]  Something, something Brexit.
+[2077.64 --> 2077.96]  Anyway.
+[2077.96 --> 2082.72]  Says the guy who's immigrated to the States to the guy who's still over there.
+[2082.88 --> 2083.28]  Incredible.
+[2083.96 --> 2084.32]  Uh-oh.
+[2084.54 --> 2084.88]  Uh-oh.
+[2085.02 --> 2085.42]  Awkward.
+[2085.94 --> 2087.90]  One final question for you there, Jake.
+[2088.00 --> 2090.22]  And it's the one that everybody's been waiting for.
+[2090.58 --> 2092.88]  It's the how many terabytes on your land question.
+[2093.26 --> 2093.62]  Oh, yeah.
+[2094.18 --> 2097.24]  Oh, so this is going to be an interesting one.
+[2097.24 --> 2102.02]  I'm going for the opposite record to what people are probably expecting.
+[2102.70 --> 2106.58]  To have from guests on here, I'm going for the lowest result possible.
+[2107.08 --> 2110.70]  So my current pool has four terabytes in.
+[2110.98 --> 2111.32]  Wow.
+[2111.32 --> 2115.44]  I love this idea because why the headache if you don't need it, right?
+[2115.92 --> 2118.54]  It's two four terabyte Seagate drives.
+[2118.68 --> 2121.46]  They've been working pretty well for my use case.
+[2121.56 --> 2124.12]  There's only 200 gig on the pool.
+[2124.60 --> 2126.64]  So I've got ample storage space.
+[2126.78 --> 2128.84]  I've got ample space to grow.
+[2129.66 --> 2131.36]  It's been working absolutely flawlessly.
+[2131.56 --> 2137.54]  There is an additional single six terabyte drive, which currently houses all of my media.
+[2137.54 --> 2144.66]  I need to get that into a pool of some kind as quick as possible because I can see Alex's face physically pained as I say that.
+[2145.10 --> 2146.00]  Perfectmediaserver.com.
+[2146.14 --> 2147.32]  Yeah, I know where to go.
+[2147.76 --> 2155.86]  It's MergerFS, SnapRaid are two things reasonably high up on my list of things to do when I get a free second.
+[2156.42 --> 2160.82]  But yeah, four terabytes is exactly just about enough for my needs.
+[2161.02 --> 2164.60]  And I don't really have any intention of growing that anytime soon.
+[2164.60 --> 2167.22]  So I'm sticking right here at the bottom of the list so far.
+[2167.54 --> 2168.94]  Okay, well, there's no shame in that.
+[2169.02 --> 2172.26]  I mean, you could be like the Michael Gambon of terabytes, huh?
+[2172.98 --> 2176.88]  That's an old Top Gear reference for some people that don't know what I'm talking about.
+[2177.26 --> 2179.28]  So thanks very much for coming on, Jake.
+[2179.30 --> 2180.40]  It was really nice to talk to you.
+[2180.58 --> 2187.22]  And please let us know from the audience if, number one, you would like to be one of these community spotlights that we're going to do.
+[2187.60 --> 2190.18]  What you thought of the segment, let us know as well.
+[2190.18 --> 2192.34]  If it's something you'd like to see us do more of, let us know.
+[2192.70 --> 2196.06]  If it's something you didn't like, well, maybe keep that opinion to yourself.
+[2196.38 --> 2196.48]  Wow.
+[2196.48 --> 2199.36]  Is there anywhere else you'd like to send people, Jake?
+[2199.46 --> 2202.66]  You know, Twitter or your personal blog that I know you write a lot of?
+[2202.92 --> 2206.48]  Yeah, I believe you described me as a, quote, prolific blogger.
+[2206.76 --> 2210.20]  And many people who hang out on the Discord know I write quite a lot.
+[2210.52 --> 2215.36]  My website is theorangeone.net, which I'm sure will be in the show notes.
+[2215.36 --> 2221.54]  My Twitter account as well is at realorangeone, which I suspect as well will be in the show notes.
+[2221.54 --> 2222.40]  Well, Jake, thank you.
+[2222.40 --> 2226.28]  A quick thank you to CloudGuru for sponsoring this episode.
+[2226.50 --> 2230.02]  And I'd like you to know about their PowerShell Core for Linux admins course.
+[2230.26 --> 2234.80]  It's an intermediate level course, and it teaches you the concepts of using PowerShell Core with Linux.
+[2235.00 --> 2238.10]  This could be game-changing if you're in a multi-platform environment.
+[2238.10 --> 2248.26]  And the course includes, of course, administration, installing Docker, working with the SQL server, even managing Azure instances, as well as integrating it all with Visual Studio code.
+[2248.58 --> 2251.54]  There's a lot there, so you'll have to click the link in our show notes.
+[2251.54 --> 2257.62]  That'll be at selfhosted.show slash 42, and you'll see the PowerShell Core for Linux admins course.
+[2257.86 --> 2260.02]  And thanks to a Cloud Guru for sponsoring this episode.
+[2261.70 --> 2266.32]  And, of course, a big thanks to our members over at selfhosted.show slash sre.
+[2266.58 --> 2269.60]  You can go there to support the show and get a limited ad feed.
+[2269.78 --> 2274.02]  We often talk as well in the post-show about some little knickknacks in our lives and things that are going on.
+[2274.64 --> 2277.28]  So you get a little bonus show, a little bonus extra content.
+[2277.66 --> 2279.46]  Yeah, selfhosted.show slash sre.
+[2279.46 --> 2283.38]  And you can also find the contact page at selfhosted.show slash contact.
+[2283.62 --> 2285.26]  That's the place to get in touch with us.
+[2285.36 --> 2286.44]  I'm on Twitter as well.
+[2286.50 --> 2287.12]  You can get me there.
+[2287.20 --> 2288.38]  I'm at ChrisLAS.
+[2288.92 --> 2290.38]  And I'm there at Ironic Badger.
+[2290.54 --> 2292.64]  And don't forget the show at selfhostedshow.
+[2293.06 --> 2294.42]  So thanks for listening, everyone.
+[2294.58 --> 2296.76]  That was selfhosted.show slash 42.

43： A New Solution for Backups _summary.txt

@@ -0,0 +1,77 @@
+• Concept for home charging station to save battery life
+• Importance of not keeping devices charged at 100% all the time
+• Ideal charge level range (40-60%) for lithium-ion batteries
+• Use of Home Assistant app to track battery life and automate smart plug control
+• Idea to expand concept to multiple devices and platforms
+• Mention of Al Dente software to limit maximum charging on Macs
+• Discussion of healthchecks.io service for monitoring server status
+• Explanation of self-hosting vs hosted version of services like healthchecks
+• Personal experience with hardware shuffles and reconfiguring home lab setup
+• Setting up a local backup system using ZFS replication
+• Using self-hosted version of HealthChecks for monitoring and notifications
+• Choosing between official and custom containers for running HealthChecks
+• Integrating with Pushover and other services for alerting and notification
+• Moving from hosted to self-hosted version due to limitations and desire to test features
+• Desiring a setup that monitors various systems, including NextCloud
+• Matrix server management and RAM usage
+• Monitoring and alerting systems (HealthChecks vs Prometheus)
+• Docker stats command for container monitoring
+• CPU usage spikes with ping stat
+• Unify controller processes under one container
+• Linode cloud computing service promotion
+• Linode services and features, including guides and tutorials
+• PHPMyAdmin security improvements and best practices
+• Linode's cloud dashboard, object storage, and backup strategies
+• Simple one-click application deployments and hosting options
+• Learning platform and $100 credit offer for new users
+• Blue Iris updates and deep stack integration
+• Using Home Assistant for live camera feeds and dashboard management
+• ZFS.rent service for storing ZFS snapshots in a co-located data center
+• Pricing and features of the ZFS.rent service
+• Discussion of cloud storage options, specifically ZFS.rent
+• Features and pricing of ZFS.rent
+• Comparison of ZFS.rent to other services
+• Options for pre-installed operating systems (OS) on ZFS.rent
+• Custom installation of OS using KVM virtual machine
+• Announcement of a Synology sponsorship
+• Overview of Synology's DS1621 Plus NAS unit and its features
+• The recipient of a Ryzen-powered NAS device from Synology for review
+• Discussion on how to review a NAS and potential challenges
+• Features of the Ryzen V1500B chip, including CPU power and ECC memory support
+• Motherboard features, such as NVMe slots and tool-less drive cages
+• Physical size and noise level of the device
+• Use of ButterFS for compression and snapshots
+• Software features, including DSM OS and app store
+• Target audience for the device: beginners in self-hosting who want hand-holding but are willing to learn
+• Setting up Docker containers on Linux
+• Sharing folders and file services using Samba or similar software
+• Creating users and configuring server management
+• Discussion of GUI options for Linux server management, including the author's preference for command-line interfaces
+• Review of Synology NAS devices as a user-friendly option for media servers and file storage
+• Comparison of Synology to other systems, such as Raspberry Pi and VMware infrastructure
+• Technical discussion of Docker versions and networking bridging on Synology devices
+• Discussion of Synology's official certification and its benefits
+• Using Synology with Intel NUC for adding storage capacity
+• Exploring backup options, specifically incremental backups and snapshots
+• Introducing Minio as an S3 frontend and its ability to provide object storage API on LAN or cloud
+• Configuring Minio with Restic for version snapshot backups
+• Introducing AutoRestic, a project that simplifies configuring Restic
+• Discussing the features of AutoRestic, including hooks, file exclusion, and forget policies
+• Designing a smart home with the wife's approval
+• Building in ethernet cables for future-proofing
+• Advantages of wired connections over wireless
+• Importance of solid networking and quality cabling (Cat6A)
+• Centralized server cupboard and patch panel for managing devices
+• Interoperability issues between different devices and protocols (e.g. Zigbee, Z-Wave)
+• Considering fan noise and heat in server space design
+• Labeling components to prevent confusion and mistakes
+• Importance of planning for future growth and needs (power, Ethernet, etc.)
+• Installing dedicated electrical circuits for equipment
+• Prioritizing long-term reliability over short-term cost savings
+• Benefits of designing with self-hosted infrastructure from the start
+• Upcoming delivery of the Helio 64
+• Selling a free NAS for $200
+• Details about selling the Helio 64, including a price and live date (Monday, April 26th)
+• Mention of sponsor Cloud Guru
+• Instructions for subscribing to the show
+• Contact information for the host and the show on social media platforms

43： A New Solution for Backups _transcript.txt

@@ -0,0 +1,711 @@
+[0.00 --> 7.90]  I have an idea for a charging station in the home that I think would be a brilliant way to save battery life.
+[8.38 --> 9.74]  I think I'm on to something here.
+[10.18 --> 13.30]  So if you need to save battery life, why do you need a charging station?
+[13.72 --> 18.20]  Here's the thing. So you got your devices, right? Like your laptops and your iPads.
+[18.20 --> 25.50]  And the actual truth is you shouldn't keep these things at 100% charge state all the time, right?
+[25.76 --> 27.04]  Wow. No, no, no.
+[27.04 --> 34.42]  In fact, somewhere between 40% and 60% is probably ideal for the type of lithium-ion batteries that are in our devices. Do you agree?
+[34.76 --> 43.72]  Yeah. When I worked in the Genius Bar, I can't tell you the number of MacBooks I saw with batteries that were exploding through the keyboard or stopping the trackpad from working.
+[43.72 --> 53.24]  I wish there was a way to just set in any OS. I want my battery level to be at this unless I press I'm going traveling button.
+[53.24 --> 62.84]  Here's what I'm thinking. So there's a couple of ways I think I could solve this, but I've got a really old MacBook from like 2013 and the battery is still kind of working and I want to keep it alive.
+[63.04 --> 67.82]  And it dawned on me that they have that Home Assistant app for macOS that tracks your battery life.
+[68.00 --> 69.00]  Oh my God, you're a genius.
+[69.66 --> 77.16]  Right? So you just put the adapter, you plug that into a smart plug and you have Home Assistant automatically turn off the smart plug when the Mac gets to 60%.
+[77.16 --> 84.34]  And I think you could probably do it with Linux. I just, I'm wondering maybe somebody in the audience knows how you could report back a battery status to Home Assistant, but.
+[84.64 --> 86.12]  That's a great idea, Brent.
+[86.52 --> 91.44]  So I want to expand the idea for other devices as well. So I want input from people on how to do this.
+[91.44 --> 99.16]  But essentially my goal would be to use a couple of smart plugs that are managed by Home Assistant to charge things for a while and then turn the charge off.
+[99.16 --> 106.48]  And if there was a way to do it intelligently, maybe I don't even need the sensor data. Maybe I could just do it by like some math. I don't know.
+[107.16 --> 112.50]  That's my current goal at home right now. So if anybody has some suggestions, I'd like them.
+[112.50 --> 122.06]  In the meantime, if you just have a Mac that you want to limit the maximum charging for, you should look into Al Dente. It works with Intel or M1 Macs.
+[122.24 --> 128.34]  And it's just letting you set a hard limit on the charge before the system continues to charge, I suppose.
+[129.04 --> 130.52]  You can look into that. We'll have a link in the show notes.
+[131.00 --> 136.32]  This is fantastic. I gave my wife my old laptop last year sometime.
+[136.32 --> 143.20]  And I know for a fact, even though I've told her, you need to unplug it at least once a month and cycle the battery.
+[143.76 --> 147.52]  I know it's been sat there since my daughter was born and hasn't moved.
+[148.28 --> 154.94]  Right. Well, we have like one Mac here in the studio that's for effects processing and it just sits there always plugged in.
+[155.00 --> 158.04]  So I put this Al Dente on there and capped it at 60%.
+[158.04 --> 163.18]  And then I started thinking, how can I do this where it's not Mac OS specific or maybe it could be for multiple devices.
+[163.18 --> 169.30]  So I'm going to expand the idea. In the meantime, you could expand your mind at a Cloud Guru.
+[169.44 --> 172.60]  They are the leading in learning for the Cloud, Linux and other modern tech skills.
+[172.92 --> 175.56]  Hundreds of courses, thousands of hands-on labs.
+[175.96 --> 179.84]  Get certified, get hired, get learning at a CloudGuru.com.
+[180.28 --> 184.16]  I think we've talked about this before. I'm talking, of course, about healthchecks.io.
+[184.36 --> 191.60]  But I've had a little epiphany with healthchecks recently and I've started using it quite heavily for my own purposes.
+[191.60 --> 193.30]  I wonder if you have used it for anything.
+[193.84 --> 199.94]  You have talked about it before and I've considered it, but I haven't been able to grok if it's worth the setup time yet.
+[200.02 --> 202.02]  It was actually one of the things I've been meaning to talk to you about.
+[202.48 --> 206.74]  I did go last time we talked about it with the hosted service.
+[207.10 --> 213.38]  And one of the struggles of being a self-hoster is do I self-host? Do I use the hosted version?
+[213.38 --> 216.76]  And with different services, I fall on different sides of that line.
+[216.96 --> 222.20]  And, you know, Bitward and I use the hosted service and I pay, I think it's $10 or $12 a year for that.
+[223.06 --> 227.38]  And with healthchecks, their hosted version is actually free for up to 10 healthchecks.
+[227.48 --> 230.06]  Beyond that, they have a pricing page.
+[230.94 --> 236.04]  So the hobbyist is actually free for up to 20 jobs, not 10, my mistake.
+[236.04 --> 241.58]  Beyond that, you can pay $5 a month and you'll get some phone support and some email support.
+[241.78 --> 247.34]  And then they have business plans at $20 and up for 100 jobs and stuff like that.
+[247.94 --> 252.04]  And I was doing a bunch of different ZFS replication tasks.
+[253.12 --> 258.46]  And what I wanted to happen was I've just done a whole bunch of hardware shuffles in my house.
+[258.84 --> 259.44]  You? Never.
+[259.44 --> 267.80]  Well, this all stems from January when I was basing everything around GVTG and wanting to do everything with that single Intel box.
+[268.04 --> 269.70]  And it didn't work out.
+[269.76 --> 273.86]  So I've had to kind of, you know, rewind and kind of reconfigure a few things.
+[273.98 --> 277.48]  So my old Dual Xeon box is now purely HomeLab.
+[277.62 --> 283.46]  That is running ESXi and it's just going to sit in a corner turned off for 95% of its life now.
+[284.74 --> 288.78]  Just such an overkill for that box because it's so powerful.
+[288.78 --> 291.86]  But it consumes a lot of power in the process.
+[292.50 --> 296.28]  And the Intel i5 system in the basement is the full-time one.
+[296.78 --> 304.34]  But what I figured I could do was take a couple of these slightly older 10 terabyte hard drives I have that are two or three years old at this point.
+[304.82 --> 311.50]  Put those into the HomeLab box and then schedule that to turn on at least once a week.
+[311.58 --> 315.24]  I'll probably turn it on more whilst I'm working during the week and doing OpenShift stuff.
+[315.24 --> 319.56]  But what I wanted to happen was to have a local backup.
+[320.08 --> 326.50]  So I wanted my ZFS in the basement to replicate to the ZFS in my HomeLab box upstairs.
+[326.50 --> 333.12]  And to keep track of when the last backup was, I needed some kind of a tool to do that.
+[333.18 --> 337.82]  Because I've got a lot going on, as we all do, and I'm going to forget stuff.
+[338.04 --> 342.74]  And the last thing I want is to come, you know, to need that backup and go,
+[343.66 --> 346.42]  oh, yes, the last time it ran was 2019.
+[346.84 --> 347.20]  Oh, dear.
+[347.66 --> 347.78]  Right.
+[348.06 --> 351.28]  Well, and you recall that did happen to me where I had a Google account outage.
+[351.28 --> 354.68]  And so the backup hadn't run for a little bit and I didn't realize it.
+[355.04 --> 355.16]  Absolutely.
+[355.84 --> 361.18]  And so I finally got round to setting up the self-hosted version of the health checks.
+[361.38 --> 371.08]  Now, I'm running this on Linode because I actually foresaw a situation where all the servers in my house are off for, you know, a couple of weeks.
+[371.16 --> 376.42]  Let's say I'm taking a vacation or something or traveling to England to see grandparents or whatever.
+[376.92 --> 379.46]  Or maybe your power is turned off because you're getting solar installed.
+[379.46 --> 381.60]  Yes, that is happening soon, actually.
+[382.38 --> 387.36]  And so I thought, right, where can I run this that is reliable and is going to be more reliable than my house?
+[387.40 --> 389.36]  And I thought Linode was a perfect fit for that.
+[389.56 --> 393.66]  So this is running on one of their $5 a month Linodes.
+[394.00 --> 399.68]  It's the same one that's doing perfectmediaserver.com and my personal blog and all the rest of it.
+[399.72 --> 403.96]  So this box is serving like quintuple duty at this point.
+[404.08 --> 405.46]  It's doing a lot of stuff for me.
+[405.52 --> 406.26]  And it's only a five.
+[406.26 --> 407.50]  It's only a five or a month.
+[407.82 --> 409.16]  I love it.
+[409.16 --> 416.22]  The self-hosted version of HealthChecks, I'm running the Linux server docker, which was written by one of my friends, also called Alex.
+[417.28 --> 423.26]  He has done a bunch of work with making sure that it pulls in the latest code from the HealthChecks repo.
+[423.26 --> 430.46]  So there is, as always with containers, it seems, a choice to be made about which container do I run.
+[430.54 --> 435.32]  Do I run the official one or do I run the Linux server one or some other random one?
+[436.00 --> 440.32]  I try and run the Linux server ones for obvious reasons whenever I can.
+[440.68 --> 445.28]  If for no other reason, then they auto-update, which is kind of nice when you restart the app.
+[445.28 --> 451.70]  So you get all the features with this self-hosted version that you don't get on the hosted version.
+[451.84 --> 459.38]  So actually, in this case, self-hosting gives you more functionality than the hosted version, which is always nice.
+[459.74 --> 461.26]  And there are a bunch of integrations.
+[461.26 --> 468.82]  I'm just using one with Pushover, which is a push notification service, which you configure through environment variables for the container.
+[469.00 --> 476.90]  You generate a token with Pushover and pass that through an environment variable in your Docker Compose file or however you like to do that.
+[476.90 --> 482.74]  It also supports a bunch of other interesting stuff like Prometheus, Ops Genie.
+[482.90 --> 485.24]  If you're doing something for work, this can be useful.
+[485.82 --> 489.86]  You can have it ping Slack, Discord, Microsoft Teams, Mattermost.
+[489.98 --> 491.06]  It does webhooks.
+[491.56 --> 494.24]  There really are a lot of integrations for alerting.
+[494.50 --> 495.96]  I'm just using Pushover, as I said.
+[496.36 --> 500.72]  It's really nice because I don't really see it if it's in the log file.
+[500.72 --> 509.44]  But if I got a message in the same communications tool I'm using to chat with you and Wes or something like that, then I'm definitely going to see it.
+[509.50 --> 510.94]  And then I'm going to be able to take action on it.
+[511.24 --> 516.56]  And so just those small things like being able to send a message to Slack, it makes a huge difference for me, Alex.
+[516.80 --> 517.94]  It supports Telegram as well.
+[518.04 --> 519.62]  So if you have a group of people.
+[519.74 --> 520.76]  Yeah, there you go.
+[520.90 --> 525.52]  You can actually have it interact with bots as well, I think, and do a bunch of stuff with that.
+[525.52 --> 533.88]  So you could make this really quite deeply integrated into some kind of an incident response solution type thing.
+[534.36 --> 535.54]  I don't really need that.
+[535.62 --> 538.96]  I just need to be reminded that, hey, dummy, you haven't run your backups for two weeks.
+[540.40 --> 545.86]  Did I track that in that description of yours, you transitioned from the hosted solution to the self-hosted version?
+[546.28 --> 546.46]  Yeah.
+[546.76 --> 547.50]  And why was that?
+[547.62 --> 551.26]  Well, number one, I was running up against the 20 job limit, which I thought was 10.
+[551.26 --> 555.42]  So maybe I wasn't running up against it, but I knew I was going to be running into that limit soon anyway.
+[555.84 --> 555.90]  Okay.
+[556.20 --> 563.50]  And I also, you know, as part of being the host of this show, feel a responsibility to try these things out on occasion.
+[564.12 --> 565.04]  That's how I felt.
+[565.18 --> 573.98]  Not just because of that, but I thought because I could host it, say, on a VPS, and then I could check even the systems here on the LAN at the studio, it might be worth doing.
+[574.66 --> 576.30]  What kind of setup am I looking at, though?
+[576.48 --> 579.80]  Because things I'd like to monitor is like, is NextCloud running?
+[579.80 --> 580.80]  So what does that mean?
+[580.82 --> 582.78]  It means, is the web port available?
+[583.06 --> 584.64]  Is the database server online?
+[584.64 --> 586.56]  I guess is the web page loading?
+[587.00 --> 588.54]  I'd like to know that kind of stuff.
+[589.02 --> 590.34]  But there's all kinds of other things.
+[590.40 --> 592.94]  Like, I'd like to know, we have our Matrix server that we run.
+[593.46 --> 596.40]  That isn't on the LAN, but it's a server we manage.
+[596.40 --> 600.36]  And Matrix eats a crap ton of RAM right now.
+[600.36 --> 603.50]  The Synapse server is definitely a work in progress.
+[604.10 --> 609.88]  And it's something that we have to log in and manage from time to time and even restart sometimes or go through some sort of cleanup.
+[609.88 --> 615.92]  And I'm wondering, like, what about those kind of scenarios where the system's running out of memory?
+[615.92 --> 619.50]  Does it do that kind of monitoring, that kind of reporting?
+[619.62 --> 623.22]  Or is it more failed, yes, or working, that kind of stuff?
+[623.22 --> 629.42]  It's a great question because it's a bit of a confusing area, all this monitoring and alerting type stuff.
+[629.92 --> 636.60]  So HealthChecks is primarily designed to be run as part of a script or a cron job or something like that.
+[636.60 --> 641.08]  And the way it works is you curl a URL, you hit a URL.
+[641.80 --> 646.44]  The HealthChecks API on the other end receives that request and goes,
+[646.60 --> 651.30]  hey, I've just been pinged on this random string of URL, UUID type stuff.
+[651.60 --> 653.26]  That's a phoning home.
+[653.46 --> 654.86]  That is that job completing.
+[655.08 --> 665.10]  So if you put it at the end of a backup script, say, the very last line is curl HTTPSHealthChecks.com slash your UID,
+[665.10 --> 672.32]  then the software knows that you've successfully got to the end of that script and it assumes everything's gone well.
+[672.64 --> 676.12]  What you're looking for, I suspect, is something more along the lines of Prometheus,
+[676.24 --> 683.38]  which is designed to monitor disk space and memory usage and CPU temperatures and percentage and all that kind of crap.
+[684.12 --> 688.12]  And Prometheus will then output to something called Alert Manager.
+[688.76 --> 692.48]  And you can write what's called PromQL, Prometheus Query Language.
+[692.48 --> 695.04]  Queries sounds complicated.
+[695.18 --> 697.26]  It's much easier than SQL to get started with.
+[697.36 --> 702.24]  So if you've ever had to write an SQL query, you can probably write a PromQL one.
+[703.06 --> 706.36]  And that's probably more what you're after in terms of monitoring.
+[706.56 --> 710.04]  You know, is Matrix, is the API still available, for example?
+[710.32 --> 713.00]  Can I still hit a certain URL?
+[713.20 --> 714.50]  Is that website still available?
+[714.50 --> 718.26]  In the meantime, I've been keeping an eye on it with net data, which feels like a cheat.
+[718.50 --> 721.38]  I feel like I almost am ashamed to admit it, but it's been handy.
+[721.62 --> 724.16]  And I've used that to kind of keep an eye on the system.
+[724.22 --> 725.78]  But I know I need to take it to the next step.
+[725.84 --> 727.86]  Maybe a topic for a future episode.
+[728.28 --> 729.64]  Who doesn't love a pretty graph, eh?
+[729.64 --> 734.84]  Speaking of which, did you know about this command I found out quite recently about this one?
+[735.50 --> 736.38]  Docker stats.
+[736.62 --> 739.56]  Just go to a box where you've got a few containers running and take a look at this.
+[739.88 --> 740.54]  This is pretty great.
+[740.62 --> 746.36]  In fact, this is one of the ways I realized how much memory and CPU Matrix actually takes.
+[746.92 --> 748.24]  The snaps, or at least.
+[748.60 --> 751.38]  This is kind of like top for your Docker containers.
+[751.52 --> 756.12]  It gives you CPU usage, memory, IO, and all that kind of stuff.
+[756.12 --> 763.00]  And you can also just get a list for a single container if you specify that container, if that's what your permissions only allow for.
+[763.30 --> 769.74]  But if you can see all of the containers, then you can just run Docker stats on its own and get a list of everything on the box.
+[770.04 --> 773.84]  And I was surprised because I run ping stat here at the studio.
+[773.94 --> 775.64]  So I just thought, well, I'll check it right before the show.
+[776.00 --> 777.40]  And I ran that.
+[777.52 --> 778.62]  And it comes up.
+[779.00 --> 781.84]  And ping stat, which is just pinging stuff and graphing it, right?
+[781.84 --> 786.70]  I ran this command.
+[786.96 --> 788.28]  And I'm like, what is it doing?
+[788.60 --> 791.04]  But then I sat there and watched it for probably five minutes.
+[791.16 --> 793.14]  And it never once again really did anything.
+[793.32 --> 799.96]  But that brief moment when I brought it up, Alex, is 300% of my CPU on my server for ping stat.
+[800.66 --> 802.10]  Yeah, it's pretty interesting, isn't it?
+[802.10 --> 811.60]  If I go into my CloudVPS where the Unify controller is running, that damn thing has 117 processes under one container.
+[812.02 --> 812.24]  Yeah.
+[812.54 --> 813.42]  Yeah, that's...
+[813.42 --> 814.90]  I don't know how that makes me feel.
+[815.20 --> 817.18]  It doesn't make me feel good, I'll be honest.
+[817.18 --> 821.18]  Linode.com slash SSH.
+[821.92 --> 826.30]  Go there to get a $100 credit on a new account for 60 days.
+[826.44 --> 828.34]  And, of course, you support the show.
+[828.80 --> 832.28]  Linode is the largest independent cloud computing provider out there.
+[832.48 --> 837.06]  No matter what technology stack you're familiar with, you're going to find Linode easy to use.
+[837.22 --> 840.88]  And if you're an expert, under the hood, there's a little thing here or there,
+[840.88 --> 846.58]  little hints that you'll see for us long-time Linux users that will make things even quicker and more efficient.
+[846.58 --> 848.04]  And things you'll really appreciate.
+[848.80 --> 858.26]  And if you ever run into any trouble, Linode has fantastic, amazing, great customer service 24-7 by phone or by ticket, whatever you prefer.
+[858.56 --> 861.36]  And they have hundreds of guides and tutorials to help you get started.
+[861.94 --> 863.80]  And we often will link to some in the notes.
+[864.36 --> 868.94]  There's one that I recommend anybody that wants to run PHP My Admin, give that one a read.
+[869.36 --> 872.64]  That's just a few steps you can go through to make that a much more secure installation.
+[873.44 --> 876.14]  Linode is easy to use and they have a powerful cloud dashboard.
+[876.14 --> 879.48]  And they also have S3-compatible object storage.
+[879.90 --> 882.66]  This could be something that works great for your backup strategy.
+[882.86 --> 887.38]  A lot of applications and tools can integrate and backup to S3-compatible storage.
+[887.90 --> 889.72]  And Linode has fantastic pricing.
+[890.12 --> 892.80]  And you could build that right into your backup or recovery strategy.
+[893.18 --> 895.66]  But additionally, you could also just use it for a static website,
+[895.80 --> 900.18]  for hosting any kind of files you need out in the cloud where you don't want to have to run a server in front of it.
+[900.18 --> 903.64]  And they have simple one-click application deployments, if that's more of your drive,
+[903.94 --> 907.64]  which I totally respect because Linode is a fantastic learning platform as well.
+[908.00 --> 910.42]  Deploy an application, learn how it works.
+[910.80 --> 911.80]  Linode's great for that.
+[911.86 --> 914.98]  With our $100 credit, there's all kinds of things you can try.
+[915.36 --> 919.34]  And learning something, trying it out, is a great use of that too.
+[919.34 --> 921.30]  I mean, absolutely, you can put it in production.
+[922.08 --> 924.68]  But why not use that credit to learn something new as well?
+[924.98 --> 926.86]  So go to linode.com slash SSH.
+[926.94 --> 930.48]  Get that $100 60-day credit and support the show.
+[930.64 --> 933.16]  That's linode.com slash SSH.
+[934.92 --> 937.62]  Now, you know how I love me some Blue Iris stuff.
+[937.74 --> 943.06]  Some pretty exciting news in the last couple of weeks about deep stack integration with Blue Iris.
+[943.06 --> 952.68]  Traditionally, what you had to do to get object detection, you know, bird, car, plane, bear, I think was one of the options.
+[953.14 --> 954.44]  You want bear detection for sure.
+[954.78 --> 955.62]  Yeah, probably.
+[956.16 --> 960.58]  Yeah, if a bear is in the woods, does it, how does the saying go?
+[961.12 --> 962.54]  Actually, I don't care where you are.
+[962.62 --> 967.30]  If there's a bear in your backyard, even where you live, Alex, I think you'd want to know about it.
+[967.30 --> 974.78]  But what's particularly exciting about this latest Blue Iris update is that built right in now to the Blue Iris software,
+[975.10 --> 981.06]  you can launch deep stack natively on the Windows system that it's running on.
+[981.20 --> 989.56]  So you don't need a helper program or any kind of JPEG kind of detection intermediary software anymore.
+[989.56 --> 991.44]  It's just all done within Blue Iris.
+[991.44 --> 996.46]  So I've put a link to a YouTube video in the description, which talks you through how to set that up.
+[996.46 --> 1002.00]  Deep stack gets even better, tempting me to come over to the Windows side, but it's not going to happen just yet.
+[1002.54 --> 1007.26]  You know, I actually find a lot of utility in just bringing the video feeds into Home Assistant
+[1007.26 --> 1011.38]  and having a dashboard and Home Assistant I can go to and just get live camera feeds.
+[1011.82 --> 1017.26]  So that, you know, that would just be a great integration one day is something that manages all of that.
+[1017.44 --> 1017.76]  Absolutely.
+[1018.32 --> 1019.88]  Alex, I know you're a big ZFS guy.
+[1019.98 --> 1022.16]  So have you seen ZFS.rent?
+[1022.48 --> 1023.04]  I have.
+[1023.14 --> 1023.32]  Yes.
+[1023.42 --> 1023.92]  Oh, my goodness.
+[1023.92 --> 1026.00]  This thing looks really, really cool.
+[1026.00 --> 1027.64]  I can't remember where I discovered it.
+[1027.98 --> 1029.78]  I think it was on the self-hosted Discord.
+[1030.00 --> 1033.50]  Somebody just said to me, have you, why don't you use ZFS.rent?
+[1033.60 --> 1035.36]  And I'm like, because I didn't know about it.
+[1036.82 --> 1043.14]  The whole premise behind ZFS.rent is that it's a simple cloud service to store ZFS snapshots.
+[1043.90 --> 1048.54]  Effectively, it's like having a ZFS send, but in a co-located data center.
+[1048.54 --> 1051.80]  But their business model is really pretty interesting.
+[1051.80 --> 1058.70]  So these guys rent out KVM virtual machines and they have dedicated hard drives to each VM.
+[1058.84 --> 1060.32]  So I guess they're using pass-through or something.
+[1060.80 --> 1064.12]  There is no sharing and no overcommitting on these VMs.
+[1064.62 --> 1070.98]  And when you sign up to their service, you receive a root password, a dedicated IBV4 address.
+[1071.24 --> 1075.30]  So you could, you know, alias that to a subdomain of your choosing.
+[1075.30 --> 1078.98]  And then you get a pre-formatted and mounted ZFS pool.
+[1079.74 --> 1081.52]  Here's where it gets really, really interesting.
+[1082.10 --> 1088.34]  You can send them hard drives with data already on them to their data center.
+[1089.00 --> 1089.68]  I love that.
+[1090.30 --> 1090.80]  That's great.
+[1090.92 --> 1095.46]  You know, you were just talking about how you had those 10 terabyte drives that you were kind of using as just scratch drives for backup.
+[1095.66 --> 1096.66]  That's a great example.
+[1096.74 --> 1098.54]  You could load those suckers up and send them off.
+[1098.72 --> 1099.06]  Absolutely.
+[1099.22 --> 1099.38]  Yeah.
+[1099.72 --> 1101.42]  Now, pricing is pretty straightforward.
+[1101.54 --> 1103.04]  It's 10 bucks a month per drive.
+[1103.04 --> 1112.42]  So if you can go on Best Buy and find one of their easy stores on a cheap deal, you could have, you know, a 14 terabyte drive for $200.
+[1113.34 --> 1117.02]  Load that sucker up with all of your data, send it off to this data center.
+[1117.42 --> 1120.48]  And for 10 bucks a month, you've got 14 terabytes of cloud storage.
+[1120.94 --> 1122.80]  You know, that is doable for what I do here.
+[1122.94 --> 1123.24]  Right?
+[1123.52 --> 1124.24]  It's one of those things.
+[1124.32 --> 1126.44]  You sort of read the website and you're like, where's the catch?
+[1126.48 --> 1127.28]  There's got to be a catch.
+[1127.82 --> 1130.88]  I was actually speaking with Ryan, who's the guy behind ZFS.rent.
+[1130.88 --> 1133.70]  And I'm hoping to get him on the show to do an interview shortly.
+[1133.90 --> 1135.42]  But he seems like a really great guy.
+[1135.66 --> 1143.80]  And honestly, I have no qualms about recommending this service, even just as a, hey, guys, you know, audience, did you know this is a cool thing existed?
+[1144.36 --> 1144.38]  Yeah.
+[1144.50 --> 1144.68]  Nope.
+[1144.72 --> 1146.98]  No sponsor, no relationship of any kind.
+[1147.00 --> 1148.28]  It's just something we came across.
+[1148.76 --> 1153.46]  Each plan includes one terabyte of base bandwidth data movement per month.
+[1153.46 --> 1156.74]  They don't distinguish between upload or download.
+[1156.84 --> 1158.06]  A terabyte is a terabyte.
+[1158.52 --> 1163.58]  They have a rate of an additional $5 per terabyte after that, which is actually pretty reasonable.
+[1164.54 --> 1170.02]  If I'm uploading more than a terabyte in a month, my ISP is probably knocking on my door.
+[1170.52 --> 1175.84]  I would imagine the time where you would actually need to exceed a terabyte is the initial seeding.
+[1176.10 --> 1182.02]  Well, we can get around that by sending them the drive preceded or in a disaster recovery scenario.
+[1182.02 --> 1191.20]  And if I'm at the point where I need to download 14 terabytes of data from my backup, I think I can probably swing, you know, the hundred bucks or whatever it is to get that.
+[1191.52 --> 1196.08]  That's just what I was thinking is that's really the only time it would be costly is when you're actually pulling it all back down.
+[1196.22 --> 1201.84]  I wonder if they would do that, although you wouldn't really want to wait, but I guess they could maybe reload a disk.
+[1201.92 --> 1203.88]  You could send them the disk and they could reload it up.
+[1205.10 --> 1206.88]  Now, did you see this on their homepage?
+[1207.72 --> 1207.84]  What?
+[1207.84 --> 1210.88]  Users have a choice of from OSes.
+[1211.22 --> 1216.54]  CentOS, with maintenance support until 2029, crossed out to 2021.
+[1217.62 --> 1218.82]  Oh, too soon.
+[1218.98 --> 1221.16]  Also, Ubuntu and Debian.
+[1221.98 --> 1228.30]  But here's where I thought it got super interesting is, as an Arch guy, no pre-installed OS.
+[1228.30 --> 1238.24]  You can attach your own Linux ISO to the KVM virtual machine and install via a tunneled VNC client any OS that you want.
+[1239.08 --> 1240.20]  That's adorable.
+[1240.96 --> 1243.28]  That's a really great setup.
+[1243.28 --> 1252.18]  They also do support Debian 10.7 out of the box and Ubuntu 20.04 until 2025, which is honestly what I would just do.
+[1253.14 --> 1254.42]  I think it's too.
+[1254.72 --> 1258.80]  It's so great that they left the 2029 on there and crossed it out.
+[1258.90 --> 1260.10]  Like, that's such a statement.
+[1260.86 --> 1261.16]  Yeah.
+[1261.16 --> 1266.36]  I've actually just deployed my first CentOS 8 stream box in production.
+[1266.66 --> 1272.68]  We're doing a small, limited Jupyter Colony mail server for like a handful of people right now.
+[1273.08 --> 1275.62]  And it's all running on CentOS 8 stream.
+[1275.98 --> 1277.16]  Look at you, you hipster.
+[1277.44 --> 1277.70]  Yeah.
+[1277.88 --> 1281.22]  So I'm going to give it a go and see how it is to run a mail server.
+[1281.66 --> 1282.76]  I'll report back.
+[1282.76 --> 1285.46]  I suspect there's going to be crappy aspects to it.
+[1287.96 --> 1294.70]  This episode is brought to you by Synology, makers of network attached storage devices, networking and surveillance equipment.
+[1295.18 --> 1303.20]  In late 2020, they released the DS1621 Plus, a six bay NAS unit with a four core, eight thread Ryzen CPU.
+[1303.92 --> 1308.42]  As a result, this system runs cool and quiet whilst being a powerhouse under the hood.
+[1308.42 --> 1314.16]  And if you need it, there's a PCIe slot for add in cards such as 10 gigabit networking as well.
+[1314.86 --> 1319.62]  What really sets Synology units apart from their competition for me, though, is their level of fit and finish.
+[1320.08 --> 1324.26]  Their enclosures are beautiful and their software is really great as well.
+[1324.56 --> 1327.14]  I'm talking about their disk station management software.
+[1327.96 --> 1330.80]  DSM is like using a desktop session inside a browser.
+[1331.10 --> 1333.30]  It's really cool if you haven't seen it.
+[1333.30 --> 1338.42]  And we've got a link for a live demo for you at selfhosted.show slash Synology.
+[1339.04 --> 1344.72]  This simple and intuitive UI is perfect for those just getting started on their self hosting journey.
+[1344.94 --> 1347.28]  I've used Synology now for many years.
+[1347.40 --> 1350.58]  I still can't quite believe how they pulled this off in a browser.
+[1351.32 --> 1358.92]  You can also find tons of apps available in their built in store, as well as community provided repos and more recently Docker support.
+[1358.92 --> 1363.68]  With this Docker support, you can run darn near anything you like on these boxes.
+[1364.28 --> 1368.66]  And remember that with that Ryzen chip, you've got full x86 compatibility.
+[1368.66 --> 1371.36]  So there's no ARM weirdness going on here.
+[1372.10 --> 1380.08]  To find out more about Synology and their other NAS products, visit selfhosted.show slash Synology so that they know we sent you and to support the show.
+[1380.20 --> 1382.98]  A big thanks to Synology for sponsoring our show.
+[1384.84 --> 1388.66]  Synology wanted us to actually have a chance to try out some of their hardware.
+[1388.66 --> 1390.70]  And so we thought we'd share our thoughts with you.
+[1390.76 --> 1395.04]  And they sent a DS1621 Plus to Alex to kick the tires.
+[1395.46 --> 1396.54]  They did indeed, yes.
+[1396.66 --> 1400.50]  So I am the proud recipient of a Ryzen-powered NAS.
+[1400.70 --> 1401.50]  That's pretty neat.
+[1401.84 --> 1404.66]  That left me thinking, how do I go about reviewing a NAS?
+[1404.76 --> 1409.34]  Because it's, you know, it's something you just throw files on and forget about for the next few years.
+[1409.52 --> 1413.12]  And when I hear Ryzen, I think it probably has a fair amount of CPU power in that thing.
+[1413.48 --> 1414.80]  This is one of their embedded chips.
+[1414.88 --> 1416.66]  This is the Ryzen V1500B.
+[1416.66 --> 1421.88]  It's a 4-core, 2.2GHz, 8-thread CPU.
+[1422.74 --> 1427.60]  And it supports up to 32GB of ECC memory, which is pretty nice.
+[1428.04 --> 1434.84]  The motherboard built into the Synology also has a couple of NVMe slots, which I thought was particularly interesting.
+[1434.84 --> 1442.62]  And one of the things, actually, that I was most disappointed about with the COBOL, you know, the Helios 64, was that it was a 5-bay NAS.
+[1443.28 --> 1448.44]  But if you used the NVMe slot that came with it, you turned it into a 4-bay NAS.
+[1448.52 --> 1449.76]  Well, there's none of that going on here.
+[1449.84 --> 1455.78]  This remains to be a 6-bay NAS with two extra PCIe NVMe slots as well.
+[1455.78 --> 1460.00]  So you can fit effectively eight drives in this thing, which is great.
+[1460.66 --> 1461.00]  That's great.
+[1461.06 --> 1461.58]  Yeah, that is.
+[1461.86 --> 1465.02]  Now, the fit and finish really is next level on this thing.
+[1465.12 --> 1470.36]  Within five minutes of taking it out of the box, I had the drive cages removed.
+[1470.36 --> 1478.94]  With the tool-less, hot-swappable drive cages they have, I had the drives installed, put them into the enclosure.
+[1479.34 --> 1484.92]  One important thing to note is that you must populate the first drive slot with a drive.
+[1485.06 --> 1487.28]  And if you don't, the Synology will fail to boot.
+[1487.38 --> 1492.98]  And I assume this is because they're installing the DSM OS onto that first drive.
+[1492.98 --> 1501.72]  Now, I don't know what that means for the long-term reliability of a spinning drive in that first slot, but it's something I can report back on in a few months' time.
+[1502.12 --> 1502.52]  Yeah.
+[1502.98 --> 1507.14]  And it could just be that maybe it just doesn't proceed because what's the point of a NAS with no disk?
+[1508.10 --> 1513.04]  Well, you say that, but these things have full-on app stores these days, and they can run Docker as well.
+[1513.18 --> 1521.30]  So, you know, you could conceivably buy a Synology unit and not put any drives in it and still run some services if you liked.
+[1521.30 --> 1523.16]  I don't know why you would, but you could.
+[1523.90 --> 1525.80]  It is easy to deploy applications on, I suppose.
+[1525.96 --> 1527.06]  So that's a good point.
+[1527.48 --> 1531.20]  I'm curious about just physical size and noise and those kinds of things.
+[1531.26 --> 1531.88]  How is all that?
+[1532.12 --> 1532.62]  And how big?
+[1532.74 --> 1534.76]  Like, give me an idea of, like, how much space this thing takes up.
+[1535.06 --> 1535.78]  Noise is great.
+[1536.38 --> 1539.02]  The fans that are included in the unit are very, very quiet.
+[1539.52 --> 1546.20]  I've actually had it in a closet right just off my office, you know, a few feet from where we're sat right now.
+[1546.92 --> 1549.16]  And I close that door and I can't hear it.
+[1549.16 --> 1551.28]  It's just, oh, it's pretty quiet.
+[1551.36 --> 1559.06]  You'll hear if it's on the desk next to you, but that's more a result of the fact of having mechanical hard drives than it is fan noise right next to you.
+[1559.78 --> 1567.00]  In terms of the size of the thing, it's, I think, it's about five kilos, give or take.
+[1567.54 --> 1571.20]  I don't know, the footprint's about the size of a 16-inch laptop, maybe a little bit less.
+[1571.20 --> 1575.12]  And then, I don't know, nine inches tall or so.
+[1575.88 --> 1580.78]  Basically, think of six hard drives lying on their side with a couple of inches either side.
+[1581.12 --> 1581.92]  That absolutely makes sense.
+[1582.00 --> 1585.62]  And now, also, I think that means you're a ButterFS user, which I think is fantastic.
+[1586.06 --> 1588.00]  Well, it would if I'd chosen ButterFS.
+[1588.34 --> 1588.94]  Oh, you sure.
+[1588.94 --> 1589.76]  Which I did, I did.
+[1589.88 --> 1590.34]  I'm such a tease.
+[1590.36 --> 1590.74]  Oh, okay.
+[1591.48 --> 1592.92]  Hello, welcome to the club.
+[1593.30 --> 1595.34]  You and I are now running ButterFS at home.
+[1595.34 --> 1600.66]  But the reason I picked ButterFS is because it enables compression and snapshots.
+[1601.28 --> 1608.58]  And that's an option that's exposed to the users at the time of creating the array or the volume of storage in the DSM software.
+[1608.92 --> 1610.56]  So, let's talk about software for a little bit.
+[1610.62 --> 1616.88]  So, this thing does run the DSM, which is their OS, and it has a nice interface on it, which has an app store.
+[1617.64 --> 1620.50]  But you are, you know, you're a long-termer.
+[1620.62 --> 1624.72]  You don't necessarily always like the graphical environments on top of stuff in the management tool.
+[1624.72 --> 1626.20]  So, how did you handle all of that?
+[1626.26 --> 1627.06]  How did you react to it?
+[1627.10 --> 1627.70]  What were your thoughts?
+[1628.12 --> 1630.98]  So, I'll tell you who I think this system is actually perfect for.
+[1632.04 --> 1638.42]  It's those people just getting started in self-hosting who want their hand-holding a little bit,
+[1638.66 --> 1645.30]  but are also comfortable with the idea that they have to learn some stuff to, you know, run these services.
+[1645.96 --> 1650.28]  And through the UI, you are guided through the process of setting up Docker containers,
+[1650.28 --> 1656.82]  of sharing folders, of doing file service sharing, like Samba, and all the rest of it, you know,
+[1656.86 --> 1660.82]  like time machine backups and all that kind of stuff, creating users.
+[1661.24 --> 1667.16]  A lot of times, people ask me when they read the perfect media server, what's the best GUI?
+[1667.38 --> 1668.74]  And I'm like, well, it's the command line.
+[1669.00 --> 1669.22]  Silly.
+[1669.66 --> 1671.44]  But actually, I think it's something like this.
+[1671.44 --> 1677.62]  I don't think a really good GUI for server management on Linux truly exists.
+[1677.72 --> 1684.10]  I know you like cockpit, but I don't think there's anything quite on this scale for vanilla Linux.
+[1684.86 --> 1684.88]  Right.
+[1684.98 --> 1685.94]  Nothing this straightforward.
+[1686.16 --> 1688.38]  Nothing this straightforward and nothing this comprehensive.
+[1688.80 --> 1688.98]  Yeah.
+[1689.14 --> 1690.70]  This does a lot more than cockpit.
+[1690.90 --> 1691.88]  Yeah, it absolutely does.
+[1692.52 --> 1695.68]  And sometimes that can be to its detriment because you think, right,
+[1695.68 --> 1700.60]  I just want to have a compose file and paste it in and create these five containers like this, please.
+[1701.16 --> 1701.56]  Right.
+[1701.78 --> 1707.26]  Whereas with the UI that Synology has, you have to click through a few things and create volumes.
+[1707.50 --> 1712.18]  And all the knobs and switches are labeled all the same as they would be in a compose file.
+[1712.38 --> 1714.28]  But you just have to go through and click them.
+[1714.72 --> 1718.36]  Which, you know, if I'm trying to explain this to my mother over the phone, for example,
+[1719.12 --> 1724.08]  and she's actually had a Synology unit in her house now for, I want to say, five years.
+[1724.08 --> 1727.74]  And I've not really had to touch it or think about it.
+[1727.82 --> 1730.56]  I mean, it just keeps on working, this thing.
+[1730.88 --> 1736.96]  And I think the long-term outlook for this Synology unit, for me, is going to be,
+[1737.42 --> 1738.70]  it's going to end up at a parent's house.
+[1739.04 --> 1740.88]  Which is no bad thing, in my opinion.
+[1741.00 --> 1746.24]  I think it's a sign of, you know, I said this a few episodes ago.
+[1746.32 --> 1750.54]  I bought a Raspberry Pi for eight gig and an external USB hard drive.
+[1750.54 --> 1757.90]  And I've been having the most difficult time trying to get that thing to USB boot with my sister's fiancé,
+[1758.02 --> 1763.24]  trying to talk him through how to set the Raspberry Pi up with USB boot and then flash it remotely.
+[1763.64 --> 1765.54]  And, oh, what a pain.
+[1765.80 --> 1770.22]  And I'm thinking to myself, well, if I just had this Synology, I could just send it to them.
+[1770.28 --> 1771.66]  And it looks nice.
+[1771.72 --> 1772.70]  It's nice and quiet.
+[1772.88 --> 1777.00]  There's no cables to be unplugged by the cat, you know.
+[1777.00 --> 1783.12]  I think Angela's been running one at her house for probably seven to eight years.
+[1783.30 --> 1784.22]  I don't even know.
+[1784.36 --> 1787.26]  It's crazy how long that thing has been running.
+[1787.72 --> 1789.64]  So it seems like it's been pretty solid.
+[1789.98 --> 1795.58]  I think for the people who like to deploy something and then begin to figure it out and learn how it works,
+[1795.72 --> 1797.52]  it fits that so well.
+[1798.22 --> 1801.24]  I worked with Synology to get one of these for Wes for Christmas.
+[1801.24 --> 1809.34]  Because it's not that Wes doesn't know how to manage a server, obviously, but he just doesn't really have the time.
+[1809.42 --> 1810.90]  He's got other stuff to do, right?
+[1810.90 --> 1819.18]  He still wants to be able to run Jellyfin, in his case, and manage his media and save files to a centralized location on his network.
+[1819.54 --> 1824.54]  But he doesn't have the time to build a box and set up all of the services, even though he knows how.
+[1824.54 --> 1827.10]  And so I thought a Synology would be perfect for him, too.
+[1827.16 --> 1833.60]  And so we say it's for beginners, but it's also just for people who got a lot going on.
+[1833.72 --> 1841.24]  Like people just kind of like in your situation that just maybe have a little less time or interest in building it completely from scratch.
+[1841.72 --> 1842.72]  I think I agree totally.
+[1842.72 --> 1849.84]  Now, one thing I would like to discuss is the version of Docker that's running on the NAS.
+[1850.08 --> 1856.32]  And it's running 18.09, which, as the name suggests, comes from 2018.
+[1856.88 --> 1863.26]  So what this means is if you SSH into the Synology, you can get in behind the scenes and go and tinker with what's going on.
+[1863.64 --> 1871.16]  And you think to yourself, great, I'm just going to use Docker Compose and I will circumvent the UI and just do it that way.
+[1871.16 --> 1879.20]  But unfortunately, because that version of Docker is so old, it means a lot of the newer features in Docker Compose aren't supported.
+[1879.46 --> 1883.90]  So you then think to yourself, hmm, I could upgrade the version of Docker, couldn't I?
+[1884.02 --> 1885.16]  And yes, you can.
+[1885.24 --> 1889.00]  There is a GitHub repo to do that in an unsupported fashion.
+[1889.00 --> 1896.98]  And then you quickly run into all sorts of problems trying to figure out how networking bridging works and all that kind of stuff and wish you'd never bothered.
+[1896.98 --> 1903.92]  So my recommendation with Docker would be to just stick to the UI on the Synology and it will just work brilliantly.
+[1904.78 --> 1912.46]  And then if you're a crazy kid like Alex, you could just end up using your Synology as an iSCSI endpoint and point your VMware infrastructure at it.
+[1912.94 --> 1913.78]  That's true, actually.
+[1913.88 --> 1918.60]  Yeah, you see Synologies in the backgrounds of so many tech YouTuber videos.
+[1918.60 --> 1923.84]  Network Chuck, Lawrence Systems, Tom from Lawrence Systems.
+[1924.04 --> 1926.40]  They've all got Synologies blinking away in the background.
+[1926.52 --> 1931.62]  And I've often wondered, what are these guys that surely know better, right?
+[1931.84 --> 1932.52]  In air quotes.
+[1932.96 --> 1934.90]  What are they all doing with their Synologies?
+[1935.04 --> 1941.08]  And it turns out, actually, if you fill this sucker up with SSDs and put a 10 gig networking card in there,
+[1941.08 --> 1949.62]  you can get some seriously good performance over iSCSI with VMware, which Synology have worked very hard to get the official certification for.
+[1950.04 --> 1954.14]  Yeah, I remember we were talking to Wendell and he even thought that was pretty remarkable back in the day.
+[1954.70 --> 1955.94]  But it is pretty good to see it.
+[1955.98 --> 1957.64]  And a nice little HomeLab addition.
+[1958.00 --> 1965.72]  So if you have something like an Intel NUC that doesn't have much storage and you want a cheap way to add, you know, six, eight or more drives,
+[1965.72 --> 1975.04]  because Synology offer a lot of different products, buy Synology, use iSCSI, and then your NUC suddenly has, you know, 20 terabytes to go at.
+[1975.52 --> 1976.20]  I can see it too.
+[1976.30 --> 1982.12]  Like, maybe one day I'll have all these Raspberry Pis and then there'll just be one centralized storage.
+[1982.50 --> 1984.04]  To be able to support VMware is pretty great.
+[1984.16 --> 1991.24]  But when you were messing around with this, one thing I didn't hear you talk about was if you dug into what your backup options would be,
+[1991.24 --> 1996.86]  if you felt like you were limited, maybe by the DSM, by what your backup options could be.
+[1997.00 --> 1998.22]  What was that experience like?
+[1998.50 --> 1999.64]  Well, it's not running ZFS.
+[1999.96 --> 2005.88]  So I needed a way in which to do version snapshots and incremental backups.
+[2006.58 --> 2013.30]  Incremental backups are really important because rather than sending the entire file system every single time,
+[2013.84 --> 2016.28]  it only sends the bits and bytes that have changed.
+[2016.28 --> 2024.76]  Now, ZFS does this at the block level, but because I'm going from ZFS to ButterFS, there's no mechanism in place to do that.
+[2025.34 --> 2031.46]  Now, I could use R-Sync, but then it's going through and it's checking MD5 hashes every time, and it can be a bit slow and a bit clunky.
+[2032.24 --> 2034.32]  And I tripped over something called Minio.
+[2034.92 --> 2038.22]  I actually mentioned this, I think, with the orange one last week.
+[2038.22 --> 2042.66]  I tripped over Minio, which is a S3 front end.
+[2043.02 --> 2049.62]  Now, this provides the S3 object storage API on your LAN, effectively, backed by your own storage.
+[2050.14 --> 2061.50]  Now, the advantage that that gives you is that you can use a tool such as Restic to do incremental version snapshot backups to this S3 endpoint backed by the Synology.
+[2061.50 --> 2066.56]  All right, so pause, because this is a big deal, and this is probably something we should dedicate an entire episode to,
+[2066.68 --> 2072.90]  but this lets you build your own S3 object storage on your LAN or maybe up in the cloud.
+[2073.40 --> 2075.92]  There's a lot of ways you could use this if you think about it.
+[2076.58 --> 2080.30]  Yeah, we should come back to this as a separate topic, but okay, so let me unpack this.
+[2080.32 --> 2089.32]  So you have something like this set up on your LAN running, exposing some storage that you're then making available to the DSM software, or how does this work?
+[2089.32 --> 2090.98]  Minio is running as a container.
+[2091.18 --> 2096.78]  That's then backed by a volume mount to one of the volumes on the Synology itself.
+[2097.02 --> 2102.22]  Lots of volumes terms going on here, but that's where it gets a little confusing.
+[2102.96 --> 2105.96]  So essentially what happens is Minio is running as a container.
+[2106.38 --> 2117.60]  It presents itself as an API that I can then call from Restic, and Restic will then just store the data on those S3 buckets as objects.
+[2117.60 --> 2124.00]  That's worth doing too, Alex, because it seems like you could use that for other stuff in the future as well, because there's a lot of things that will just plug right into that.
+[2124.18 --> 2127.72]  It does free you up from the ZFS kind of train, if you like.
+[2127.72 --> 2138.06]  So if something like ZFS.rent isn't up your street, and you want to host just a few hundred megabytes of files, then something like Restic is going to do you really well.
+[2138.54 --> 2141.62]  One of the most difficult parts of using Restic is configuring it.
+[2142.08 --> 2148.66]  Now, I came across a project this week which solves that problem in a really beautiful way called AutoRestic.
+[2148.66 --> 2158.60]  Now, there's a link to this thing in the show notes, but essentially what happens is you define the locations and the backends in a YAML file, and you're done.
+[2159.08 --> 2160.22]  That's not so bad to manage.
+[2160.38 --> 2164.10]  I mean, that sounds like something that I could probably wrap my head around.
+[2164.34 --> 2177.26]  What's really nice as well is if you just have a local backend, which is just some dumb USB hard drive, you can actually have as one of your backends just HDD type local path, my external storage.
+[2177.26 --> 2178.92]  And it's as simple as that.
+[2179.24 --> 2182.50]  Oh, although my backend is never dumb, but that does seem really nice.
+[2183.04 --> 2184.86]  I didn't mean it as an insult, darling.
+[2186.72 --> 2190.54]  There's a bunch of other cool stuff that AutoRestic supports as well, like hooks.
+[2190.74 --> 2201.80]  So if you want to perform some commands before or after a specific backup, let's say you want to delete some files after a backup's happened, for example, you can do that using the hooks that are built into AutoRestic.
+[2202.22 --> 2204.40]  You can also exclude files as well.
+[2204.84 --> 2206.20]  And there is a forget policy.
+[2206.20 --> 2224.56]  So one of the favorite things about ZFS Send for me is when I use Jim Salter's Sanoid tool, it has a policy-driven snapshot engine, which will automatically keep the last hour or the last six hours and then the last six days and then the last six weeks and then the last six months.
+[2224.72 --> 2227.88]  It will keep one snapshot from each of those different timestamps.
+[2227.88 --> 2237.84]  AutoRestic also has a forget and prune policy engine built right into it, which you configure again in the YAML right next to the location that you're defining.
+[2238.26 --> 2240.96]  It's just, it's the way Restic should work.
+[2241.44 --> 2242.44]  Yeah, that does sound nice.
+[2242.90 --> 2243.60]  Well, very good.
+[2243.60 --> 2247.76]  We will have a link to that at selfhosted.show slash 43.
+[2248.14 --> 2252.38]  Now, before we go, Alex, Jace Novell wrote in on the Discord.
+[2252.62 --> 2255.16]  So I guess that's more like sent a message on Discord.
+[2255.42 --> 2257.56]  And then we thought that's a good question to read on the show.
+[2257.66 --> 2261.72]  But he says, I'm working through the planning stages of building a new home.
+[2262.06 --> 2263.54]  Oh, I love that.
+[2263.64 --> 2263.88]  Yeah, Lee.
+[2263.88 --> 2264.78]  Oh, I'm envious.
+[2265.12 --> 2265.28]  Yeah.
+[2265.62 --> 2275.54]  He writes, if you're all starting from scratch, how would you design a smart home that would get the wife approval factor, but at the same time, not be too much overkill?
+[2275.90 --> 2280.74]  Well, that actually feels like that's how you achieve the wife approval factor is by not going overkill.
+[2280.88 --> 2283.26]  But I get the spirit of his question.
+[2283.38 --> 2289.22]  Like, what's a reasonable kind of build it in while I have the opportunity, but not go excessive?
+[2289.82 --> 2292.14]  Automated flamethrowers on the driveway should do the trick.
+[2292.14 --> 2295.52]  Right, and don't forget laser pointers on articulating arms.
+[2296.38 --> 2301.16]  So that way you can, you know, you can just put that out there and that way the pets stay entertained.
+[2301.32 --> 2307.24]  No, but really thinking about it, it comes down in my mind, like the first place I go to is just solid networking.
+[2307.58 --> 2312.12]  Whilst you've got those walls open, run as many high quality cables as you can.
+[2312.32 --> 2312.50]  Yeah.
+[2312.62 --> 2315.24]  I would suggest starting with Cat6A as a minimum.
+[2315.86 --> 2317.74]  Yes, it could be considered a little bit overkill.
+[2317.74 --> 2324.38]  You know, 5E will do quite comfortably gigabit ethernet and even, it'll even do 10 gig over a very short distance.
+[2324.66 --> 2327.94]  But Cat6A will give you 10 gig guaranteed.
+[2328.20 --> 2331.30]  I think it's like three or 500 feet, something like that.
+[2331.30 --> 2341.90]  And if you're thinking about the lifetime of a house, which could be 50 plus years, you really want to put in there as good as you can afford to at the time you're building it.
+[2341.94 --> 2347.70]  Because having retrofitted a couple of houses with ethernet cable, let me tell you, pulling cable is no fun.
+[2347.70 --> 2354.20]  It's how you'll do everything from cameras to smoke detectors to sensors to Wi-Fi endpoints.
+[2354.90 --> 2359.70]  Everything's better with ethernet or just workstations, televisions, media set top boxes.
+[2360.16 --> 2362.10]  You'll never beat wired.
+[2362.26 --> 2366.60]  As good as wireless gets, it cannot just beat a physical copper connection.
+[2366.80 --> 2368.96]  It's just the reality of physics right now.
+[2369.06 --> 2371.52]  And I just so completely agree with Alex.
+[2371.58 --> 2375.98]  I have a buddy right now who is building a tiny home and it's a really cool place.
+[2375.98 --> 2387.66]  And in this tiny home, which is probably 250 square feet, I don't actually know, he has 18 ethernet jacks in different places.
+[2387.66 --> 2389.36]  Some of them are multiple panels and stuff.
+[2389.62 --> 2391.12]  But, you know, you think about it.
+[2391.20 --> 2392.40]  That's how he's going to do his phone.
+[2392.72 --> 2394.18]  That's how he's going to do all of his TV.
+[2394.46 --> 2396.58]  HDMI is going to be over ethernet in the wall.
+[2397.12 --> 2398.46]  That's how he's going to do all of his cameras.
+[2398.60 --> 2399.88]  That's how he's going to do his desk.
+[2400.24 --> 2402.36]  That's how he's going to bring his internet connection in.
+[2403.02 --> 2405.92]  I really just completely, totally agree with you, Alex.
+[2406.24 --> 2408.76]  And it would be nice as well not to have to daisy chain switches.
+[2409.18 --> 2413.60]  One of the ways in which I extend the ethernet around some of the larger rooms in this house,
+[2414.26 --> 2419.28]  in walls that are more difficult to pull cable through, like external walls, stuff with insulation in,
+[2419.74 --> 2423.72]  I actually just run an ethernet cable along the skirting board, the baseboard,
+[2423.72 --> 2427.58]  and then have a switch and then just carry on.
+[2427.66 --> 2431.86]  So actually, if I think about it between the switch that's carrying my voice to you,
+[2432.46 --> 2433.90]  there's probably four switches.
+[2435.02 --> 2437.04]  It's a horrible network design, but it works.
+[2437.04 --> 2441.66]  I wish I could shake up so many industries too, like the hotel industries should all be putting
+[2441.66 --> 2443.38]  ethernet in the rooms for me to use.
+[2443.94 --> 2444.40]  RVs?
+[2444.46 --> 2448.92]  Oh my gosh, Alex, I wish the RV manufacturers would build an ethernet to every RV.
+[2449.48 --> 2450.72]  All home manufacturers.
+[2450.96 --> 2452.72]  You shouldn't build a home today without ethernet.
+[2452.82 --> 2455.64]  And it's happening still, Alex, in 2021.
+[2455.64 --> 2458.92]  Without ethernet, but also without a proper server cupboard.
+[2459.50 --> 2464.56]  And I think, you know, having some kind of a central place where all that ethernet comes into
+[2464.56 --> 2469.94]  with a patch panel and space for all the different bridges that you need these days,
+[2470.02 --> 2474.42]  your Zigbee bridge, your Z-Wave bridge, your Philips Hue light bulb bridge,
+[2474.90 --> 2475.74]  all this kind of stuff.
+[2475.80 --> 2478.98]  Like the solar installer came and did a survey on my roof last week,
+[2478.98 --> 2481.68]  and he said, can I take a look at your internet router?
+[2481.68 --> 2488.50]  And I'm like, okay, this is going to be complicated unless you tell me why you need to see that.
+[2489.52 --> 2493.84]  And he said, well, we have this monitoring thing that connects via Zigbee to the solar
+[2493.84 --> 2498.34]  on the roof and does a bunch of, you know, consumption monitoring stuff.
+[2498.44 --> 2500.30]  And I said, okay, so tell me what you need.
+[2500.34 --> 2501.44]  Is it just an ethernet jack?
+[2501.50 --> 2502.28]  And he went, yes.
+[2502.46 --> 2503.70]  I'm like, I've got you covered.
+[2504.96 --> 2506.62]  Yeah, that's a great example.
+[2506.80 --> 2509.00]  But just so many other things.
+[2509.00 --> 2515.76]  Like you'll have like your ISPs box you need to put somewhere and like a phone or a cable television thing
+[2515.76 --> 2517.36]  if you go that route.
+[2517.54 --> 2522.12]  So absolutely think of that and think of noise because some of these things that you're going to have in that space,
+[2522.16 --> 2525.12]  like a switch, have very loud fans.
+[2525.72 --> 2529.58]  Also, just before we completely go away from ethernet, label, man.
+[2530.20 --> 2535.44]  The first, a couple of times, the first time and then a second time, but no, no, nonsense.
+[2535.44 --> 2539.60]  But a couple of times, twice in a row, unfortunately, I got screwed.
+[2539.76 --> 2542.48]  And the guys that did my ethernet didn't properly label stuff.
+[2542.72 --> 2544.52]  And it is such a pain in the arse.
+[2544.92 --> 2545.80]  Let me tell you.
+[2546.22 --> 2548.44]  So label everything you're doing.
+[2548.68 --> 2549.68]  Consider fan noise.
+[2549.84 --> 2550.62]  Consider heat.
+[2551.12 --> 2552.30]  Because that could also be a problem.
+[2552.36 --> 2558.52]  Because if it was me, I would like to have my switch and my server and all of that in the same space.
+[2558.52 --> 2566.20]  So if I were really designing everything from scratch, I may actually consider putting all of that in my garage where I have a little room built off.
+[2566.84 --> 2571.88]  Anything you can do now is an investment that will save you problems later because you're going to have heat issues.
+[2571.88 --> 2573.06]  You're going to have power issues.
+[2573.10 --> 2574.56]  You're going to have noise problems.
+[2574.76 --> 2576.94]  You're going to have growth and sprawl problems.
+[2576.94 --> 2581.60]  So if you can give consideration to that in some way, I absolutely would think of that.
+[2581.66 --> 2588.68]  And then also maybe if you're going to do cameras, consider doing something like PoE from the start and how you might build for that.
+[2589.16 --> 2589.22]  Absolutely.
+[2589.70 --> 2594.24]  And one of the other things I would consider in that server cupboard is you mentioned heating and cooling.
+[2594.46 --> 2598.84]  But I would suggest if you can get a dedicated electrical circuit just for that equipment.
+[2598.84 --> 2608.60]  It would make things much easier to troubleshoot if that room with thousands, probably thousands of dollars worth of equipment in it has its own electrical supply.
+[2609.04 --> 2613.34]  And you could build a UPS type system in around it as well.
+[2613.58 --> 2616.78]  But it's possible that that thing is going to be drawing quite a few amps.
+[2617.06 --> 2621.00]  So it's worth having that separate circuit.
+[2621.56 --> 2628.04]  And if you did later want to have like a backup power supply for that, or maybe you wanted even solar power or something like that.
+[2628.04 --> 2634.24]  If you have that gear already isolated on its own circuit, that just got way simpler down the road.
+[2634.74 --> 2636.00]  So that's something to think of too.
+[2636.56 --> 2639.76]  And you really, I don't think you can overdo it with Ethernet.
+[2639.84 --> 2642.90]  And I don't think you can overdo it with circuits for independent stuff.
+[2643.42 --> 2649.86]  When I had my place built years and years ago, which I don't live in anymore, but I had a circuit for my home office.
+[2650.00 --> 2651.70]  Oh, actually, and here I did it in the studio too.
+[2651.76 --> 2657.50]  Now that I think about it, the studio has three separate power circuits just in the studio.
+[2657.50 --> 2662.74]  The reason for that is really overkill because of ground loops and noise like that.
+[2663.32 --> 2669.56]  And then our offices upstairs, each room upstairs is on its own circuit because we run so much computer gear.
+[2670.04 --> 2672.80]  We didn't want to be popping each other's breakers.
+[2673.20 --> 2677.86]  I never used to really worry about that when I lived in England because obviously everything's at 220 volts over there.
+[2677.96 --> 2679.48]  So half the amps.
+[2680.00 --> 2683.58]  But over here at 110 volts, it really makes a difference.
+[2683.58 --> 2685.66]  Yeah, so those are, I don't think they're overkill.
+[2685.78 --> 2694.82]  And the way you sell them is in long-term reliability and a reducement in replacements, in hacky solutions, and in stress.
+[2695.12 --> 2700.80]  And just learning from people who have tried this the cheaper way and have had to make adjustments since.
+[2700.88 --> 2702.90]  And if it's your only route, you'll make it work, man.
+[2702.90 --> 2703.38]  No problem.
+[2703.38 --> 2709.72]  But if you do have the ability to do some of this stuff ahead of time, man, future you is going to be so thankful.
+[2710.28 --> 2711.38]  Yes, absolutely they will.
+[2711.50 --> 2718.96]  Having retrofitted a few houses myself, I can tell you there is nothing worse than going through a crawl space with cockroaches trying to pull ethernet.
+[2719.16 --> 2720.92]  So save yourself some headaches.
+[2721.58 --> 2726.64]  Now, if you'd like to get your question answered or discussed on the show, you can go to selfhosted.show slash contact.
+[2726.64 --> 2727.64]  There you go.
+[2728.12 --> 2732.20]  And also selfhosted.show slash SRE if you'd like to become a member.
+[2732.56 --> 2737.88]  You support the show, you get a limited ad feed, and you get extra content a post show.
+[2738.20 --> 2742.62]  And I think it's like $5 a month, which is like our best deal on the network right now.
+[2743.06 --> 2746.96]  Selfhosted.show slash SRE and get additional content.
+[2747.64 --> 2748.50]  Best deal for the best show.
+[2748.66 --> 2749.08]  Dang right.
+[2750.74 --> 2753.70]  Now, you just launched jupitergarage.com, didn't you?
+[2753.70 --> 2757.18]  Man, you and I, I know you have the same problem.
+[2757.32 --> 2758.22]  Way too much gear.
+[2758.64 --> 2759.70]  Stuff's all over the place.
+[2759.80 --> 2763.22]  So jupitergarage.com, we've been selling off some things that we have in the studio.
+[2763.52 --> 2766.66]  Plus, I've kind of mixed it with some original stuff in there.
+[2767.32 --> 2777.16]  And you and I were talking about it, and we were thinking now that you've got a different NAS situation, maybe we ought to put the Helio 64 in the garage sale.
+[2777.58 --> 2777.74]  Yeah.
+[2777.98 --> 2779.44]  Well, I'm not really using it for anything.
+[2779.64 --> 2783.12]  So I figured I'll save someone else having to wait for it to be delivered.
+[2783.12 --> 2788.20]  So we'll put it on there for a good price, and it'll go live on Monday, which will be April the 26th.
+[2788.46 --> 2789.84]  Yeah, jupitergarage.com.
+[2789.96 --> 2792.96]  I just sold the free NAS that I used to have here in the studio.
+[2793.52 --> 2794.44]  I sold it for $200.
+[2795.14 --> 2796.26]  Man, that is a steal.
+[2796.82 --> 2797.32]  Yeah, it is.
+[2797.42 --> 2801.38]  You know, in some part, it's just because I don't – this gear's just been sitting around anyways.
+[2801.80 --> 2803.94]  So it's not like I'm doing anything with it.
+[2804.06 --> 2806.42]  Might as well go to a home with somebody in the audience.
+[2806.54 --> 2808.10]  That just seems like kind of awesome, you know.
+[2808.10 --> 2812.38]  So, yeah, the Helio 64, it will probably go pretty fast.
+[2813.04 --> 2820.30]  So maybe we should say Monday a.m. Seattle time just to kind of give people an expectation.
+[2820.64 --> 2820.96]  Absolutely.
+[2821.44 --> 2822.80]  All right, jupitergarage.com.
+[2822.90 --> 2826.20]  Also, you can find our sponsor, Cloud Guru, on social media.
+[2826.36 --> 2826.82]  It's simple.
+[2826.92 --> 2829.22]  They're just slash a Cloud Guru everywhere.
+[2829.22 --> 2834.22]  And if you're looking for all the different ways to subscribe to the show, you can go to selfhosted.show slash subscribe.
+[2834.66 --> 2836.50]  I'm on Twitter at Ironic Badger.
+[2836.92 --> 2839.32]  Yeah, I'm there too, at Chris L-A-S.
+[2839.46 --> 2842.80]  And the whole show right here, this show, this one, at Self Hosted Show.
+[2843.00 --> 2843.46]  This show?
+[2843.80 --> 2844.26]  Which show?
+[2844.48 --> 2844.90]  This show?
+[2845.00 --> 2845.48]  The whole show?
+[2845.74 --> 2846.56]  This one, yeah.
+[2846.90 --> 2847.84]  No, the whole thing.
+[2848.04 --> 2851.82]  It's all there in just the hundred and whatever it is characters now, 200 and whatever.
+[2852.18 --> 2855.16]  Actually, it's really just a good resource to get show announcements and news.
+[2855.44 --> 2857.04]  And maybe send us questions, I suppose.
+[2857.04 --> 2859.82]  And if all that isn't too much for you, I'd like to thank you for listening.
+[2860.06 --> 2862.42]  That was selfhosted.show slash 43.

44： Plex Skeptics _summary.txt

@@ -0,0 +1,62 @@
+• Discussion about the prevalence of dashboards in self-hosted and Homelab subreddits
+• Criticism of dashboard clutter and maintenance requirements
+• Mention of various dashboard options (Homer, Heimdall, etc.)
+• Complaints about dashboard overload and difficulty keeping them up to date
+• Conversation about Plexamp updates, including the addition of a shuffle button and Siri support
+• Discussion of Plex's ecosystem and its music-focused applications
+• Announcement of Plex's $50 million growth equity round and plans for further development
+• Fragmentation of streaming services and Plex's goal to bring all content into one interface
+• API access and integration with services like Hulu, Netflix, Amazon Prime, and Disney
+• Concerns about analytics and tracking by streaming companies
+• Impact on the value proposition of subscribing to separate services
+• Technical challenges and limitations of Plex accommodating multiple streaming providers
+• Monetization strategies for Plex's new direction
+• Concerns about mixing personal and family media content on a single platform
+• Discussion of the potential for an option to separate personal and family content in a future update
+• Comparison of Plex with other media server options, including Infuse and Jellyfin
+• Review of the Infuse app as a viable alternative to Plex, particularly for Apple TV users
+• Discussion of Linode's cloud computing services and their one-click application deployment for Plex
+• The speaker uses Linode for all of their hosting needs due to its performance and reliability.
+• They appreciate Linode's own ISP status, which provides faster interconnects between data centers.
+• The speaker likes that Linode is a good product with fast machines and dedicated CPU rigs.
+• They also appreciate the simplicity and ease of use of the Linode dashboard.
+• The speaker mentions using Linode's S3-compatible object storage for backup and as a back-end storage mechanism.
+• He discusses his experience with Fire tablets in home automation, mentioning performance issues and ads on one of them.
+• The speaker suggests using an old 7-inch HD tablet from 2015 that he repurposed into a wall-mounted dashboard.
+• Setting up voice transcription on tablet
+• Replacing Amazon OS with Lineage OS and customizing for Home Assistant use
+• Unlocking bootloader and installing custom recovery software
+• Using FDroid app store to install Google-less apps, including Home Assistant
+• Managing power usage and screen settings for infrequent use
+• Performance issues with Lovelace and Home Assistant on older hardware
+• Discussion of Prometheus as a monitoring tool for APIs and services
+• Overview of how Prometheus works, including scraping data from remote servers and alerting users to potential issues
+• Example of using Prometheus to monitor CPU temperatures in a VMware system
+• Hardware requirements for running Prometheus, including flash-based storage media
+• Explanation of scrape jobs and YAML configuration files
+• Discussion of data retention policies with Prometheus
+• Kubernetes and Prometheus monitoring
+• DevOps and site reliability engineering tools (Prometheus, etc.)
+• Cloudfree.shop devices for self-hosted solutions
+• Upgrading storage on a Synology NAS with mirrors and snapshots
+• NFS vs ZFS or ButterFS for file transfer and backup options
+• Risks of relying solely on RAID or mirroring for data storage
+• Importance of external hard drive backups and data redundancy
+• Utilizing free space on a LAN to pool resources for temporary storage needs
+• Home Assistant automations for cycling battery charging
+• Difficulty in finding solutions for devices without an OS, such as iOS devices and drone batteries
+• Introduction to Halcyon, a Rust-based application designed to work with Home Assistant for presenting metrics and potentially solving device management issues
+• Discussion of migrating from Google Photos and exploring self-hosted photo storage options
+• Discussing backup solutions for photos and files
+• Requirements for incremental backups due to library growth and remote LAN storage
+• Researching software that doesn't automate one-way backups from phone to server
+• Mentioning Duplicati as an unreliable option
+• Recommending Borg, Restic, NextCloud, and Photosync as alternative backup solutions
+• Discussing the discontinuation of Plex Photos camera upload feature
+• Expressing skepticism towards Plex's decision-making process
+• Discussing Google Stadia and its potential for playing games on any machine
+• Building a self-hosted gaming setup using Steam and streaming protocols like Parsec and Moonlight
+• Appreciation for site reliability experts (SRE) members who support the show
+• Announcing a limited ad feed for SRE members with benefits including extra content and post-show discussions
+• Thanking Cloud Guru for their support
+• Contact information for the self-hosted show, including social media links and Discord channels

44： Plex Skeptics _transcript.txt

@@ -0,0 +1,713 @@
+[0.00 --> 7.46]  Have you noticed lately that the self-hosted and Homelab subreddits freaking love their dashboards?
+[8.10 --> 10.78]  Yes, it's dashboards all day. Are you kidding me?
+[11.36 --> 16.54]  Every third post is, oh, I'm just humble bragging about all the self-hosted services I've got.
+[16.54 --> 20.84]  And I always feel like my dashboard is not as pretty as it could be.
+[21.34 --> 23.22]  I mean, they're not even as nice as your dashboards.
+[23.30 --> 27.00]  And these dashboards are like, they look like you should be controlling a starship with some of them.
+[27.00 --> 31.16]  The word dashboard has become a sound to me. You've just said it too much.
+[31.56 --> 33.66]  Dashboard, dashboard. Yeah.
+[33.98 --> 39.60]  I mean, there's lots of options, right? There is Homer, there is Heindal, there is, I mean, there's dozens of them.
+[39.84 --> 46.34]  I get why people like them, but they're just another thing to become out of date.
+[46.42 --> 52.54]  And I find that even if I set one up, the entropy to keeping it up to date is too high.
+[52.54 --> 57.88]  And six months later, I haven't opened it for a while. And, oh, I don't even run that service anymore.
+[57.98 --> 58.90]  Why is that still on there?
+[59.40 --> 63.06]  And it gets worse the more devices you have or you remove or add.
+[63.22 --> 67.58]  And in some cases, I have devices that go offline or online depending on my location.
+[68.16 --> 71.02]  And then the dashboard is like messed up temporarily while I'm traveling.
+[71.02 --> 74.32]  And then I just like debate the entire time if I should remove it.
+[74.62 --> 80.06]  And God forbid, I take something out and then I have to go everywhere and make sure I've got it removed from my Lovelace dashboard and my Heads Up dashboard.
+[80.40 --> 83.04]  It's just like it's dashboard overload for me.
+[83.46 --> 86.34]  But I get the people like they like sharing them.
+[86.74 --> 92.74]  And I kind of like I like I like viewing them sort of like I enjoy viewing desktop screenshots.
+[93.66 --> 95.14]  Oh, that's an interesting way to do it.
+[95.14 --> 98.56]  And sometimes I'm like, never going to do that.
+[99.18 --> 100.66]  I'm just never going to go that far.
+[101.32 --> 102.02]  It's discovery.
+[102.46 --> 104.80]  You know, oh, look, this person's got 47 apps.
+[104.94 --> 106.24]  What what's this one do?
+[106.66 --> 107.26]  Yeah, that's true.
+[107.38 --> 107.78]  That's true.
+[108.38 --> 110.40]  Well, go see what you can do at the all new a cloud guru.
+[110.52 --> 113.70]  They are the leader in learning for the cloud, Linux and other modern tech skills.
+[114.06 --> 116.28]  Hundreds of courses and thousands of hands on labs.
+[116.52 --> 119.48]  Get certified, get hired, get learning at a cloud guru dot com.
+[119.86 --> 121.52]  Did you see the Plexamp update?
+[121.92 --> 122.76]  Wow, Alex.
+[123.02 --> 124.94]  I was wondering if you if you caught this.
+[124.94 --> 126.90]  I was going to ask you if you saw the new Plexamp.
+[127.00 --> 131.48]  Yeah, it's it's a big update for for iOS and Android.
+[132.02 --> 135.10]  And I think at least the iOS one will be really soon.
+[135.16 --> 138.36]  But the death is a desktop version of Plexamp now as well, which I didn't even know.
+[139.02 --> 144.70]  And they've added one feature that I've wanted since the very first time I tried Plexamp.
+[144.90 --> 146.10]  And it's the shuffle button.
+[146.52 --> 148.30]  So happy to have a shuffle button now.
+[148.90 --> 150.28]  I don't know what to say to that.
+[150.92 --> 154.50]  And I know you're going to be elated to see that they've also added Siri support.
+[154.50 --> 159.22]  So now you can play music on Plexamp through Siri, which I'm sure you're going to use all the time.
+[160.04 --> 165.48]  And as you know, as being a heavy iOS user, I'm not I'm still on Android.
+[165.62 --> 173.26]  I tried to switch to iOS in January, but was wearing a lot of face masks in the hospital and face ID and all that.
+[173.26 --> 175.00]  I ended up going back to Android.
+[175.20 --> 179.46]  So I was delighted to see that they've now added Siri support.
+[179.90 --> 180.28]  That's true.
+[180.44 --> 180.96]  That's true.
+[181.06 --> 182.14]  And it works.
+[182.28 --> 183.16]  You know, it's very simple.
+[183.66 --> 185.38]  It's it's nothing really to write home about.
+[185.46 --> 187.56]  That's probably stuff that should have had a long time ago.
+[187.56 --> 197.26]  And I think in general, Plexamp is probably one of my favorite Plex adjacent ecosystem applications.
+[197.26 --> 200.82]  We get people that write into the show and they'll say, why do you guys use Plex?
+[200.90 --> 201.62]  There's Jellyfin.
+[201.76 --> 202.58]  There's other alternatives.
+[202.58 --> 218.08]  There's just this this ecosystem around Plex now between the friends that I can share with, like Alex, for library sharing options, but also these apps around Plex that break off like the music experience into this individual app that's dedicated to just music.
+[218.08 --> 219.34]  It's it's just wonderful.
+[219.34 --> 222.62]  And it's nice to see it get updated to version 3.4.5.
+[222.62 --> 227.64]  It really makes the music experience in Plex quite pleasurable, to be honest with you.
+[227.64 --> 235.66]  And the design language they've used for the application brings it up to the same sort of polish as something like Spotify or something like that.
+[236.08 --> 239.70]  It is just a 100% native looking music app.
+[239.80 --> 241.24]  And I think it's freaking great.
+[241.70 --> 243.34]  There's some things that aren't so freaking great, though.
+[243.88 --> 244.98]  Good and bad, I suppose.
+[245.16 --> 251.46]  Plex revealed that it recently completed a growth equity round of 50 million dollars from an existing investor.
+[251.76 --> 252.74]  Oh, yeah.
+[252.74 --> 252.88]  Yeah.
+[253.18 --> 258.76]  And the company intends to invest its money in a mission to become a one stop shop for movies and TV.
+[258.94 --> 261.74]  And it aims to do this by addressing one of the most fuss.
+[262.18 --> 268.70]  And it aims to do this by addressing one of the most frustrating aspects today in the legal streaming market, they say.
+[268.82 --> 271.04]  And that is fragmentation.
+[271.54 --> 273.06]  You know, all the different streaming services.
+[273.06 --> 279.28]  They want to bring it all into Plex, including your pirated content or whatever else you might have on there.
+[279.28 --> 284.98]  Like for me, we use Plex for just home videos that we record that we don't want to put up like on YouTube or something.
+[285.42 --> 287.88]  And they want to bring it all into one UI.
+[288.32 --> 294.18]  And you can search all of it from the stuff in your own library to the stuff that's on Hulu to Netflix and Amazon Prime.
+[294.92 --> 304.18]  And Plex says they're going to work with these companies to get API access and integrate it all in there and try to make an experience where you go to one app and you get all the streaming services.
+[304.80 --> 307.32]  I mean, I understand why they're doing this.
+[307.32 --> 314.12]  Because the revenue streams of a few Plex Pass subscribers surely can't self-sustain the company.
+[314.84 --> 322.78]  I mean, myself, as an example, I paid $75 for a lifetime Plex Pass half a decade ago, more than probably.
+[323.48 --> 325.28]  And they haven't seen a penny from me since.
+[325.42 --> 335.50]  And so, you know, I can understand how, you know, Hulu and Disney and Prime and Netflix are juicy targets for them to try and integrate into one place.
+[335.50 --> 344.34]  But if I was Netflix or Prime or Disney, I'm not sure I would want people going outside my walled garden.
+[344.34 --> 352.30]  Because the whole reason that these companies have dedicated gardens, walled gardens for their content is so that they can do analytics on it.
+[352.30 --> 357.38]  And they can track you through, you know, minute by minute, second by second of what you're watching.
+[357.38 --> 364.06]  I mean, the Grand Tour is a great example of this, you know, old Top Gear turned into the Grand Tour, Jeremy Clarkson and all that.
+[364.38 --> 366.94]  One of my favourite TV shows of all time.
+[366.94 --> 378.22]  And a couple of years ago, Amazon decided to kill the studio part of the Grand Tour, which was my favourite part, in favour of just doing these epic specials.
+[378.28 --> 384.24]  And now we only get two or three episodes, well, less, a couple of episodes a year of the Grand Tour.
+[384.24 --> 392.40]  And they're these grand expeditions where they go to Madagascar and they put tank tracks on a Ford Fiesta and stupid stuff like that.
+[392.90 --> 398.90]  Whereas what I watched the Grand Tour for was the cocking about between three old men sort of taking the mickey out of each other.
+[399.20 --> 407.42]  But the reason they did that, Amazon, was because their analytics showed that most people didn't watch the studio segments.
+[407.42 --> 411.68]  You know, I can understand why they would make that change.
+[411.80 --> 420.62]  But if you're Amazon and you're giving away API access to Plex, presumably you would bake in some of those analytics through the Plex client.
+[420.98 --> 430.20]  But one of the benefits of having people in your app is that they're not going to exit that app to go to Netflix to go and watch a specific show over there.
+[430.26 --> 432.94]  They're just going to carry on browsing in the portal they're already in.
+[432.94 --> 445.78]  And if Plex presents all of these different things in one place, the value prop to subscribe to these different services becomes just too generic at this point.
+[445.84 --> 447.52]  And I just don't see it working, do you?
+[448.06 --> 449.32]  I have to say I completely agree, Alex.
+[449.40 --> 452.68]  And it goes just beyond like analytics and whatnot.
+[452.80 --> 454.16]  But there's also a technical angle.
+[454.24 --> 458.10]  Perhaps they want to tweak how the playback engine works with their particular type of CDN.
+[458.10 --> 463.46]  Or maybe they want to feature content for some special show they've just released or some big movie.
+[463.54 --> 470.38]  Like I just read this morning that Paramount Plus is planning to do a movie a month on their Paramount Plus streaming service.
+[471.02 --> 480.04]  And I got to imagine that every time one of those movie drops, they're going to do some sort of big presentation in a carousel that lets everybody know our new content is here.
+[480.10 --> 483.22]  And I just can't imagine Plex accommodating all of those whims.
+[483.22 --> 488.28]  All of these companies just got to become their own cable network essentially with their streaming service.
+[488.72 --> 493.28]  And we've just gone through the last 10 years of them figuring out how to actually stream video.
+[493.42 --> 495.34]  And they're just starting to get good at it now.
+[496.04 --> 497.66]  You know, Netflix had to set the example.
+[498.52 --> 501.06]  And so I just don't really see this taking up.
+[502.14 --> 507.58]  Maybe if Plex was willing to do something where they got access to the search API.
+[507.58 --> 512.90]  And then if you selected a video, say it was the Grand Tour, it would then just launch the Amazon app.
+[513.00 --> 513.96]  But how valuable is that?
+[514.02 --> 516.84]  And how do you even do that, say, like in a web version or something?
+[517.22 --> 521.08]  My Google Assistant does that already with voice search on the NVIDIA Shield.
+[521.76 --> 523.76]  It'll search through all the apps for me.
+[524.12 --> 524.24]  Right.
+[524.36 --> 525.96]  And Roku's trying to do the same thing.
+[526.02 --> 528.28]  And Apple wants to offer the same thing with the Siri remote.
+[528.54 --> 528.90]  Absolutely.
+[529.36 --> 529.58]  Yeah.
+[530.02 --> 532.64]  And $15 million isn't enough to do this.
+[532.64 --> 535.34]  So they raised $50 million from an existing investor.
+[536.06 --> 541.88]  And as part of that, it includes $15 million in new capital for Plex, which they're going to invest in this mission.
+[542.50 --> 543.88]  That's nowhere near enough, is it?
+[544.14 --> 545.06]  I can't imagine.
+[545.32 --> 550.16]  Unless they see a way of monetizing this, maybe through affiliate links or something like that with the streaming providers.
+[550.40 --> 550.72]  Maybe.
+[551.10 --> 551.32]  Yeah.
+[551.54 --> 554.70]  But you know, Alex, that doesn't even touch on what I don't like about this.
+[554.70 --> 557.36]  And that is this whole single pane of glass.
+[557.50 --> 559.28]  They actually use that term, experience.
+[559.28 --> 563.32]  It's I use Plex intentionally for a curated experience.
+[563.80 --> 566.44]  I don't want to see everything because it's a family cert.
+[566.52 --> 567.68]  It's something that we use for our family.
+[567.78 --> 574.68]  That's why I take the time to put things on there individually, myself as the dad or when, you know, the mom requests something.
+[574.86 --> 579.44]  I have a UI where they can go in and they can request things.
+[579.44 --> 583.12]  But it is intentionally separated from everything else.
+[583.26 --> 584.66]  And there is an app on the screen.
+[584.84 --> 585.38]  They launch it.
+[585.44 --> 586.00]  They go in there.
+[586.06 --> 587.16]  I know everything's safe.
+[587.16 --> 589.84]  I have parent stuff separated out from kids stuff.
+[590.06 --> 592.64]  And I have really no interest in mixing it all.
+[592.72 --> 594.94]  I can't tell for sure at this stage.
+[595.04 --> 600.44]  But reading between the lines, it does look like they're going to give you the option to not mix everything together.
+[600.44 --> 602.16]  But it will be mixed by default.
+[602.48 --> 604.00]  I mean, I guess time will tell on this one.
+[604.38 --> 607.96]  I kind of hope we're proved right because I really agree with you.
+[608.02 --> 610.04]  I don't want to see this stuff.
+[610.12 --> 613.52]  The reason I have Plex is because I want to control what I see.
+[613.70 --> 615.38]  So, yeah, I'm with you on that one.
+[615.38 --> 620.06]  Yeah, it gets my head spinning immediately on, well, what would I go to?
+[620.70 --> 622.04]  What would I transition to?
+[622.30 --> 625.06]  Because I've got a lot of time invested in my Plex library.
+[625.40 --> 632.76]  And so one of the things I've already done on our Apple TV is I've switched to using – I've talked about it before on the show.
+[632.86 --> 634.48]  I've switched to using Infuse.
+[634.56 --> 635.82]  And I'm going to put a link to it again.
+[635.94 --> 636.78]  It's a paid app.
+[637.22 --> 638.78]  It's like Cody for Apple TV.
+[639.16 --> 641.00]  And I don't use that lightly.
+[641.00 --> 642.42]  I have a lot of respect for Cody.
+[642.50 --> 644.12]  But this is like Cody for Apple TV.
+[644.34 --> 651.60]  It can bring together multiple servers over network connections, Google Drive, Dropbox.
+[651.80 --> 653.80]  And it supports Plex.
+[654.20 --> 658.04]  It will do your watch status and everything that you would need to track in Plex.
+[658.68 --> 660.50]  And it's just a fantastic UI.
+[660.50 --> 664.42]  And it has much better AirPlay support.
+[664.54 --> 675.40]  So if you use HomePods with an Apple TV or you're using some kind of crazy AirPlay setup, Infuse does it perfectly where the actual Plex client on Apple TV and iOS is not actually great at that stuff.
+[675.48 --> 676.60]  It sometimes has issues.
+[676.98 --> 683.84]  And so when I see this news about one meta search engine for all streaming, I think, yeah, that's all good, guys.
+[683.88 --> 686.94]  But you're not even enticing me to use your own app these days.
+[687.08 --> 688.48]  Like there's other things to focus on.
+[688.48 --> 693.24]  And I have a lot of respect for the Plex folks, but it is just what it is now is I'm using Infuse.
+[693.52 --> 696.56]  And you can get it at firecore.com slash Infuse.
+[696.76 --> 701.36]  And they've just recently released a Mac desktop version, too, which is kind of a neat idea, I suppose.
+[701.82 --> 706.22]  I know lots of the audience are frantically screaming at their podcast devices.
+[706.34 --> 707.24]  What about Jellyfin?
+[707.40 --> 708.12]  What about MB?
+[708.60 --> 709.40]  Well, maybe one day.
+[709.48 --> 712.42]  Maybe you and I eventually will become Jellyfin guys in the future.
+[712.48 --> 712.92]  It could happen.
+[713.54 --> 716.26]  I do experiment it from time to time.
+[716.32 --> 718.04]  Have you ever kicked the tires with Jellyfin?
+[718.04 --> 718.68]  I have.
+[718.98 --> 720.02]  And I went back to Plex.
+[720.98 --> 721.50]  Okay.
+[721.66 --> 721.98]  Sorry.
+[722.80 --> 725.36]  I mean, it's pretty good for what it is.
+[725.90 --> 727.72]  It's just Plex has a head start.
+[728.10 --> 736.80]  And the fit and finish of the UI and the experience I have there is much better on Plex than Jellyfin.
+[737.28 --> 738.56]  What would it take for you to switch?
+[738.56 --> 745.80]  I think when it's suitable for my family members, you know, that they have a lot of time invested in learning.
+[746.28 --> 748.56]  Plex has various UI changes over the years.
+[748.94 --> 751.84]  And they kind of figured out how it works now for the most part.
+[751.84 --> 756.82]  Once Jellyfin's at that kind of level of polish, it's just not yet, though.
+[756.82 --> 760.24]  Linode.com slash SSH.
+[760.34 --> 763.20]  Linode is the largest independent cloud computing provider.
+[763.34 --> 769.12]  And when you go to Linode.com slash SSH, you'll get $100 in 60-day credit towards a new account.
+[769.32 --> 770.92]  And you can go there to support the show, too.
+[771.46 --> 773.18]  We were just talking about media servers.
+[773.18 --> 778.46]  Well, Linode has a one-click application deployment for Plex if you want to get a Plex server up in the cloud,
+[778.56 --> 781.60]  which is a great way to share with friends and family at super fast streaming speeds.
+[782.00 --> 784.92]  Of course, you could just build your own stack and deploy Jellyfin or anything you'd like.
+[785.02 --> 789.24]  And no matter what skill level you're at or what technology stack you're familiar with using,
+[789.72 --> 791.50]  Linode will help you get it going online.
+[791.62 --> 793.64]  They have a really easy-to-use dashboard.
+[794.08 --> 798.02]  And if you have any trouble getting things going or run into any kind of problem,
+[798.02 --> 803.46]  Linode has amazing, fantastic, great, outrageously good customer support.
+[803.68 --> 805.66]  By phone or ticket, they're going to help you get it solved.
+[805.72 --> 810.42]  If you've got one rig or you're like me and you're crossing, like, the 15-rig mark or something,
+[810.50 --> 812.98]  I mean, it's getting crazy because we use Linode for everything.
+[813.08 --> 815.16]  And it's not just, like, haphazardly.
+[815.84 --> 817.48]  We think about every machine we deploy.
+[817.68 --> 821.42]  And we decide, okay, is this going to be the machine that is just a dedicated box?
+[821.42 --> 824.46]  Maybe it only runs one application or it runs just a couple of things.
+[824.92 --> 827.08]  Or is this going to be something like an application server?
+[827.08 --> 829.72]  We have a couple of these, too, where these are more powerful Linodes.
+[830.08 --> 833.10]  And we run multiple containers on them, running multiple applications,
+[833.40 --> 839.84]  from mail to encoding services to matrix to, well, really, you run the gamut.
+[839.86 --> 842.58]  Anything we're just talking about on the show, we pretty much host it on Linode.
+[843.12 --> 844.32]  People ask me, why, Chris?
+[844.34 --> 845.62]  Because there's a lot of places to host.
+[845.76 --> 849.94]  Well, the reason for that really comes down to a few core things that I think are pretty important.
+[850.42 --> 852.50]  Number one, it is a really good product.
+[852.62 --> 853.56]  It's very fast.
+[853.64 --> 855.10]  They have 11 data centers worldwide.
+[855.10 --> 859.74]  The interconnects between the data centers, I think, beat what everybody else has, hands down.
+[860.08 --> 861.36]  Linode is their own ISP.
+[861.48 --> 866.02]  So they just have a networking opportunity that people that haven't been around as long don't have.
+[866.64 --> 871.84]  Additionally, their dedicated CPU rigs, they're just faster than other people's dedicated CPU rigs.
+[871.96 --> 872.70]  I like that.
+[873.14 --> 876.72]  Then you factor in that they're really just good Linux-loving folks.
+[876.80 --> 878.38]  They have been since 2003.
+[878.38 --> 882.16]  And that factors into some of the decisions on how they've built the product.
+[882.52 --> 884.48]  And those things appeal to me.
+[884.74 --> 886.40]  They make it easy for me to use.
+[886.44 --> 888.00]  And I feel like it's very simple.
+[888.10 --> 890.82]  But when I need power in that dashboard, it's there.
+[890.98 --> 894.16]  And then there's services like their S3-compatible object storage.
+[894.16 --> 900.72]  Now, this is great because I can use S3 object storage for backup, for configs that I want to store off-site.
+[900.80 --> 904.56]  Or we use it as the back-end storage mechanism for our next cloud instance.
+[904.64 --> 908.10]  So we're not having to sit there and fiddle with different disk sizes like amateurs.
+[908.38 --> 910.62]  We just throw it on the S3 storage.
+[910.62 --> 915.06]  But Linode's so fast that it really is very performant.
+[915.20 --> 916.70]  And it's a great way to build a static website.
+[917.14 --> 918.82]  There's so much you can do there.
+[918.90 --> 929.10]  If you just need something simple like a portfolio website, or if you want to run the back-end infrastructure for your team collaboration or for your e-commerce website, Linode's going to be able to do it all.
+[929.18 --> 931.34]  So go to linode.com slash SSH.
+[931.34 --> 934.22]  Get that $100 60-day credit on your new account.
+[934.58 --> 936.54]  And then just see what it can do.
+[937.24 --> 938.46]  See what we've been talking about.
+[938.68 --> 940.10]  And see why we use it for everything.
+[940.62 --> 942.46]  Linode.com slash SSH.
+[943.98 --> 947.12]  Now what do you do for home assistant wall panels?
+[947.20 --> 950.78]  I recall you bought a Fire tablet a while ago, right?
+[951.12 --> 952.26]  I have a couple of them now, yep.
+[952.42 --> 957.90]  I have a 10-inch one and a 7-inch one that I have mounted in the Lady Joops RV.
+[958.32 --> 959.20]  How are they working out for you?
+[959.22 --> 959.60]  Do you like them?
+[959.60 --> 960.60]  Pretty good.
+[960.80 --> 961.74]  Pretty good.
+[961.98 --> 963.72]  Not very good performance.
+[964.04 --> 969.88]  And also one of them, even though I bought the no-ads model, has ads on the lock screen.
+[970.10 --> 971.52]  And I find that frustrating.
+[972.08 --> 973.86]  So the performance is not fantastic.
+[974.02 --> 981.76]  But just sitting there with a web page up and after I install an app, after I sideload an app like an animal to keep the screen on, they get the job done.
+[981.76 --> 982.18]  All right.
+[982.18 --> 983.38]  Well, I've got a solution for you.
+[983.38 --> 993.10]  My wife has, or had, it's mine now, a Fire 7-inch HD tablet from 2015.
+[993.10 --> 998.08]  We paid £35 for this tablet six years ago.
+[999.02 --> 1001.40]  You know, the battery is crap.
+[1001.74 --> 1003.62]  I mean, the battery was crap when it was new.
+[1003.94 --> 1004.88]  The screen is bad.
+[1005.00 --> 1006.64]  It was bad back then.
+[1006.72 --> 1008.02]  So it's really bad now.
+[1008.56 --> 1010.02]  It's just not a great device.
+[1010.36 --> 1011.00]  Let's be honest.
+[1011.06 --> 1013.60]  But it was £35 six years ago.
+[1013.60 --> 1020.52]  And I thought to myself, wouldn't it be cool if I had a wall-mounted tablet dashboard?
+[1020.88 --> 1021.34]  Good for you.
+[1021.60 --> 1027.70]  In my workshop, I've been doing some automation around the woodworking blast gates that I have.
+[1027.74 --> 1030.40]  We'll talk about that more in an upcoming episode.
+[1031.18 --> 1037.14]  And then basically, I just wanted a touchscreen panel that I could just jab my fat fingers on and just open a certain blast gate.
+[1037.14 --> 1042.08]  I didn't want to spend any money because it's already, woodworking's already expensive enough.
+[1042.28 --> 1045.72]  Did you think about going with a voice tube out there before this, or do you already have one?
+[1045.96 --> 1047.50]  Well, I have a voice tube out there.
+[1047.78 --> 1048.98]  It's the lady cylinder.
+[1049.68 --> 1055.64]  And I, I don't know, I've kind of really gone off shouting orders across the room at these things.
+[1056.66 --> 1063.26]  I, in the rental house last, or before we bought this one, everything was on the Google voice system.
+[1063.26 --> 1068.86]  But I didn't set any of that up once we moved, and I haven't since, and I, I just don't miss it.
+[1069.24 --> 1074.66]  I mixed on it myself because there's sometimes you have to restate yourself and you always feel like a fool when it, when it gets it wrong.
+[1074.88 --> 1079.40]  There's always that thing where you're making eye contact with the cylinder, waiting for it to light up.
+[1079.44 --> 1080.06]  And I'm like, oh.
+[1080.52 --> 1080.66]  Yeah.
+[1080.68 --> 1086.14]  And then in my situation, you add every time we're off grid, of course, the voice transcription doesn't work.
+[1086.22 --> 1088.94]  So that's really where I was like, okay, we got to have tablets.
+[1089.14 --> 1092.60]  And also it's nice to glance at it and just see what's on and what's off.
+[1092.60 --> 1094.52]  So how did you go about accomplishing this?
+[1094.82 --> 1099.08]  Well, I put Lineage OS, which is an open source version of Android.
+[1099.40 --> 1104.08]  I think it's what came out of the Cyanogen mod project a few years ago.
+[1104.36 --> 1104.54]  Yeah.
+[1104.66 --> 1107.54]  I put Lineage OS 12 on this tablet.
+[1108.06 --> 1116.70]  And performance is better than the Amazon OS that was on there before, but it's still a six-year-old device.
+[1116.84 --> 1117.46]  You know what I mean?
+[1118.20 --> 1120.22]  Well, any performance improvement would be good.
+[1120.26 --> 1121.74]  This has crossed my mind before.
+[1121.94 --> 1123.06]  I have thought about doing this.
+[1123.10 --> 1125.26]  I just wasn't sure if it was really worth the bother.
+[1125.66 --> 1127.52]  It was a bit of a pain, right?
+[1127.52 --> 1141.52]  I had to unlock the bootloader, which involved, I had to take the back off the tablet, bridge a couple of pins on the motherboard to ground the bootloader out so that it would boot into the bootloader mode for Android.
+[1141.62 --> 1145.52]  I don't know if you've ever done anything with ADB and fast boot.
+[1145.86 --> 1146.66]  A while ago, but yeah.
+[1146.66 --> 1152.06]  I had to use those tools to put a custom recovery partition on there.
+[1152.08 --> 1161.36]  So I used Team Win Recovery Project, TWRP, and sideloaded on there a bunch of different APKs and the Lineage OS ROM.
+[1162.02 --> 1168.42]  This process probably took me an evening of mostly futzing about and getting into that bootloader mode was the hardest part.
+[1168.66 --> 1170.78]  Are you using Windows to do any of this?
+[1170.78 --> 1175.62]  I mean, I have all three in this room, so I, you know, between the different devices.
+[1175.96 --> 1177.48]  Does it require Windows is what I'm asking?
+[1177.64 --> 1178.84]  Do you need Windows?
+[1178.98 --> 1179.44]  Because I'm out.
+[1180.02 --> 1182.08]  That's a disqualifier for me right there.
+[1182.22 --> 1184.80]  I think this one works best under Linux.
+[1184.94 --> 1187.60]  I actually just used a Raspberry Pi in the end.
+[1187.70 --> 1188.16]  Oh, okay.
+[1188.52 --> 1189.32]  I have those.
+[1189.60 --> 1190.34]  I know you do.
+[1191.28 --> 1194.88]  I ended up just using a Raspberry Pi with Ubuntu on.
+[1195.44 --> 1196.00]  All right.
+[1196.02 --> 1197.10]  Now you're talking about language.
+[1197.42 --> 1198.98]  So it took you a little bit of an evening,
+[1198.98 --> 1203.30]  but it sounds like if I followed some tips from you, maybe it wouldn't take me that long.
+[1204.02 --> 1208.22]  Well, this is for the specific revision of the 2015 7-inch Fire tablet.
+[1208.54 --> 1211.48]  So I don't know if the newer ones have a more locked down bootloader.
+[1211.70 --> 1215.10]  That's the key is once you can get a custom recovery software on there,
+[1215.60 --> 1217.56]  you can install whatever image you like.
+[1217.56 --> 1224.32]  My first question, once you get the OS on there, is do you do GApps and do you need GApps for this tablet?
+[1224.62 --> 1227.22]  No, you definitely don't anymore because of FDroid.
+[1227.22 --> 1232.60]  So my use case was to use this thing exclusively for Home Assistant.
+[1232.96 --> 1233.06]  Right.
+[1233.24 --> 1238.44]  And so LinearGOS, out of the box, ships with no Google software whatsoever,
+[1238.80 --> 1241.60]  which is awesome on such an underpowered device.
+[1242.30 --> 1243.86]  And then so I just loaded FDroid.
+[1243.96 --> 1249.80]  I went to the FDroid website, enabled unsigned or unknown sources for APK installation,
+[1250.50 --> 1254.68]  installed the FDroid APK, and now I have a Google-less app store.
+[1254.68 --> 1257.16]  And Home Assistant is available in that app store.
+[1257.32 --> 1258.84]  So happy days.
+[1259.22 --> 1260.26]  And how are you doing the screen?
+[1260.38 --> 1261.24]  Are you letting it sleep?
+[1261.32 --> 1262.52]  Are you leaving it on all the time?
+[1262.78 --> 1268.62]  Because it's going to be used very infrequently, I have just used the standard lock and unlock.
+[1268.92 --> 1271.28]  And it's going to take me a couple of taps to unlock the screen,
+[1271.40 --> 1274.80]  but I use it a couple of times a day, if that.
+[1275.30 --> 1276.58]  Yeah, that makes sense.
+[1277.04 --> 1280.74]  Now, the other question I have is, are you using the web dashboard,
+[1280.74 --> 1284.44]  or did you load the Home Assistant app and interface with it that way?
+[1284.74 --> 1288.00]  Yeah, I loaded the app through FDroid and the performance.
+[1288.32 --> 1292.02]  So I have a lot of experience with how long it takes to load that app on my phone.
+[1292.26 --> 1294.76]  And it can take a beat sometimes.
+[1294.90 --> 1302.80]  Performance of Lovelace and the interface of Home Assistant could be better, shall we say,
+[1302.90 --> 1303.94]  even on modern hardware.
+[1303.94 --> 1308.94]  So you can imagine on this six-year-old device, it takes a good 10 seconds to load.
+[1309.22 --> 1310.48]  Once it's loaded, it's fine.
+[1310.54 --> 1311.92]  And it works just fine.
+[1311.96 --> 1314.72]  But it's that initial load that can take a while.
+[1315.14 --> 1317.58]  If you have a guide or anything like that, is there something we could share in the show notes?
+[1317.86 --> 1318.84]  Yep, it's already in there.
+[1319.04 --> 1319.36]  Aha!
+[1320.08 --> 1322.12]  That'll be at selfhosted.show slash 44.
+[1322.62 --> 1325.10]  We talked about HealthChecks.io last episode.
+[1325.22 --> 1329.02]  And in there, I asked you about monitoring if APIs or services are up.
+[1329.04 --> 1330.16]  And you mentioned Prometheus.
+[1330.16 --> 1336.04]  Prometheus, well, I want you to tell me more about it because we got a few people that bit via email.
+[1336.52 --> 1337.20]  Yeah, we did, actually.
+[1337.48 --> 1342.58]  And I was quite surprised to see just how many people either already used Prometheus
+[1342.58 --> 1347.62]  and wanted to tell me all about how awesome it was or didn't use it and wanted to know more.
+[1347.70 --> 1348.76]  So here's a little primer.
+[1349.46 --> 1355.30]  Essentially, Prometheus scrapes data on remote servers, gathers it into one place.
+[1355.30 --> 1364.74]  You write queries to query that data and present it in a dashboard or forward on certain things to something called Alert Manager,
+[1365.02 --> 1366.86]  which can then alert you.
+[1367.00 --> 1371.76]  So if your disk percentage, for example, on a remote system goes above 80% used,
+[1372.26 --> 1374.62]  you could have it notify you of that and say,
+[1374.98 --> 1378.64]  hey, you should probably go and delete some stuff before this server fills up.
+[1378.64 --> 1383.98]  Now, what I ended up using it for is my VMware box downstairs.
+[1385.14 --> 1386.50]  It's now just my HomeLab.
+[1386.60 --> 1387.80]  It's not actually my main server.
+[1387.92 --> 1391.28]  It's just performing OpenShift HomeLab duties for me.
+[1391.86 --> 1396.12]  And I put it into a case where fan control was a bit of an issue.
+[1396.42 --> 1400.84]  And so I mentioned in the previous episode about a fan controller,
+[1400.84 --> 1406.56]  the Corsair Commander Pro that is usable on Linux now.
+[1406.80 --> 1415.06]  But one of the things I wanted to do was actually get a feel for how the CPU temperatures were in that system over time,
+[1415.06 --> 1416.80]  because I've got a couple of hard drives in there.
+[1417.44 --> 1421.16]  And, you know, if things are getting toasty, hard drives tend to die pretty quickly.
+[1421.40 --> 1429.50]  So what I wanted to do was monitor that VMware vCenter instance with Prometheus and have it alert me if there was a problem.
+[1429.84 --> 1430.06]  Nice.
+[1430.06 --> 1433.10]  I ended up using this thing called VMware Exporter.
+[1434.16 --> 1437.46]  And there's a link to the Docker Compose snippet in the show notes.
+[1438.38 --> 1447.00]  And this thing, basically what it does is it logs into vSphere's API every pre-prescribed interval.
+[1447.12 --> 1449.26]  I think I've got it set to like 15 seconds or something.
+[1450.04 --> 1453.94]  Scrapes a bunch of data available through the vCenter API,
+[1454.46 --> 1457.44]  which includes stuff at the host level like CPU temperature,
+[1457.44 --> 1462.58]  but also includes the IPMI data like the voltages and all that kind of stuff.
+[1462.64 --> 1466.08]  So it's pretty granular and pretty detailed if you want to know that stuff.
+[1466.08 --> 1469.70]  And then it imports it into the Prometheus real-time database.
+[1469.70 --> 1475.64]  And from there, once it's in Prometheus, I can query it using Grafana or whatever else I want to.
+[1476.34 --> 1481.90]  And I use a container called Priorder, I think is how you say it.
+[1482.02 --> 1483.52]  Priorder VMware Exporter.
+[1484.22 --> 1486.76]  Super simple little Python app and just does the job.
+[1486.76 --> 1489.74]  What kind of hardware utilization, I guess, is what I'm asking.
+[1489.94 --> 1493.28]  So if I have a system, I have an existing Xeon box here at the studio.
+[1493.90 --> 1497.40]  It's probably about 30% utilized CPU-wise and memory-wise.
+[1497.92 --> 1499.36]  Do I need something more powerful?
+[1499.48 --> 1501.62]  Do I have enough headroom for running these kinds of services?
+[1502.04 --> 1504.16]  Prometheus itself is pretty lightweight.
+[1504.90 --> 1508.94]  You know, with any real-time metrics gathering system like this,
+[1509.02 --> 1512.34]  we'll probably want to put it on some kind of a flash-based storage media.
+[1512.34 --> 1517.56]  So, you know, you'll need a few gigabytes scratch disk for that to use.
+[1517.80 --> 1521.76]  But then once you've done that, you need to create what are called scrape jobs,
+[1522.02 --> 1525.14]  which is how you tell Prometheus what to look for
+[1525.14 --> 1528.56]  and what to kind of gather in terms of metrics on remote systems.
+[1529.08 --> 1533.70]  You configure that in my favorite language of them all in a YAML file.
+[1534.46 --> 1538.42]  And once you've done that with Priorder, you kind of set it, forget it,
+[1538.46 --> 1540.36]  and never worry about it ever again.
+[1540.36 --> 1542.46]  And then how long does it collect for? Forever?
+[1543.30 --> 1544.44]  How long do you do it for?
+[1545.02 --> 1546.28]  I haven't really worried about it.
+[1546.38 --> 1546.98]  I just sort of...
+[1546.98 --> 1547.32]  Forever!
+[1547.80 --> 1549.16]  Keep them forever, yeah.
+[1549.24 --> 1551.88]  I mean, I guess if you're in an enterprise situation
+[1551.88 --> 1556.14]  where you're scraping 10,000 servers, that might be an issue, but I'm not, so...
+[1556.14 --> 1558.28]  Yeah, so maybe not a big deal.
+[1558.40 --> 1560.06]  You could be. That'd be kind of fun, wouldn't it?
+[1560.10 --> 1561.68]  Go back 10 years and look at stuff.
+[1562.42 --> 1562.78]  Oh!
+[1563.38 --> 1565.72]  Well, I mean, look, this is how these big guys do it.
+[1565.72 --> 1570.38]  I mean, Kubernetes clusters the world over are monitored by Prometheus.
+[1570.94 --> 1574.38]  OpenShift actually ships a bunch of stuff with Prometheus built in.
+[1574.56 --> 1578.28]  So this is one of those technologies that if you're thinking about getting into DevOps
+[1578.28 --> 1582.08]  and that kind of space of, you know, site reliability engineering,
+[1582.80 --> 1586.48]  these are the sorts of tools that you should be mucking about within your home lab
+[1586.48 --> 1588.94]  and trying to figure out how they work and understand them
+[1588.94 --> 1592.02]  because you'll be able to take that knowledge and use it to get a better job.
+[1592.02 --> 1593.36]  Yep, great skill to have.
+[1593.90 --> 1594.98]  I just like the idea.
+[1595.04 --> 1597.32]  I just like the idea of picturing you like 10 years from now,
+[1597.40 --> 1603.72]  looking back at some graph analogs and just kind of getting nostalgic from graphs and logs.
+[1604.16 --> 1607.98]  Yeah, my CPU is 33 degrees on May the 5th, 2021.
+[1608.34 --> 1609.06]  Hey, great.
+[1609.22 --> 1610.80]  Ah, I remember that, yeah.
+[1611.16 --> 1612.26]  Those were the days.
+[1615.22 --> 1616.30]  Cloudfree.shop.
+[1616.30 --> 1618.88]  Head over there and buy from a community member
+[1618.88 --> 1624.58]  who has built a business out of creating devices that are ready to go without any cloud restriction.
+[1625.04 --> 1626.92]  And they posted an update in February.
+[1627.80 --> 1629.90]  And you got a mention in here.
+[1630.06 --> 1630.72]  He says...
+[1630.72 --> 1631.08]  Did we?
+[1631.38 --> 1632.24]  How cool is that?
+[1632.46 --> 1632.92]  He says,
+[1633.00 --> 1635.68]  I need to also thank Alex and the self-hosted podcast.
+[1635.92 --> 1638.58]  I've listened to Jupyter Broadcasting podcast for over seven years.
+[1638.92 --> 1642.82]  And without our partnership, Cloudfree would not have grown nearly as fast as it did.
+[1643.12 --> 1646.12]  And I got to say, it hit me in the feels because the picture they have in that
+[1646.12 --> 1649.68]  looks a lot like what we're doing for the Jupyter Garage shipping right now.
+[1650.20 --> 1654.84]  And I just totally realized, like, I'm learning a lot of the same stuff that they had to learn
+[1654.84 --> 1656.68]  to do Cloudfree right now.
+[1657.14 --> 1660.38]  And so I felt very like I had a kinship all of a sudden.
+[1660.54 --> 1662.86]  And I thought that was really great that they had a really...
+[1662.86 --> 1663.58]  This is a really good...
+[1663.58 --> 1664.68]  This is a really positive update.
+[1664.76 --> 1667.16]  It looks like things are going really well for Cloudfree.
+[1667.28 --> 1668.68]  And that's why we like to mention them.
+[1668.78 --> 1670.96]  It was an idea that I think needed to happen.
+[1670.96 --> 1676.12]  And it's a great way to go get devices at a very reasonable price, like outdoor and indoor
+[1676.12 --> 1683.88]  smart plugs, Zigbee dongles, temperature sensors, motion sensors, Z-Wave buttons, door sensors,
+[1684.00 --> 1687.06]  all that kind of stuff that you might want to hook up to Home Assistant.
+[1687.30 --> 1691.02]  But, you know, you don't want to have to bother with the reflashing yourself or worrying about
+[1691.02 --> 1694.08]  the required cloud connectivity that they ship with by default.
+[1694.68 --> 1695.96]  Cloudfree just takes care of all that.
+[1696.10 --> 1698.90]  That's why we like to give them a mention at cloudfree.shop.
+[1698.90 --> 1702.48]  And when you're over there, don't forget to use the coupon code self-hosted so that
+[1702.48 --> 1703.28]  they know we sent you.
+[1704.62 --> 1706.18]  All right, feedback time, I think.
+[1706.40 --> 1707.28]  Daniel writes in,
+[1707.36 --> 1712.90]  I'm currently using a Synology 216J with an EXT 4-volume mirrored on two drives.
+[1713.20 --> 1718.22]  I'm curious about how I might go about upgrading here and prioritize backup ergonomics.
+[1718.64 --> 1723.84]  Right now, I don't have snapshots and I'm considering switching to ZFS or ButterFS.
+[1724.34 --> 1724.76]  Brackets.
+[1724.98 --> 1725.80]  Please don't fight.
+[1725.80 --> 1731.74]  How can I do this without purchasing a huge external hard drive to move everything over
+[1731.74 --> 1733.02]  whilst I build a new volume?
+[1733.72 --> 1739.10]  Also, NFS seems kind of antiquated and I'm wondering if this is the fastest way to mount
+[1739.10 --> 1740.28]  things over the network.
+[1740.56 --> 1741.40]  Is there a better option?
+[1741.94 --> 1742.14]  Hmm.
+[1742.44 --> 1743.76]  A little NFS hate there, huh?
+[1744.08 --> 1745.28]  No, I used to think that too.
+[1745.74 --> 1748.68]  You know, actually, that's sort of the beauty of NFS is that it's so simple.
+[1748.82 --> 1750.14]  It is extremely efficient.
+[1750.14 --> 1753.14]  But there are lots of ways to transfer files over the network.
+[1753.62 --> 1754.10]  It is old.
+[1754.28 --> 1759.24]  But, you know, one way you could look at old is tested, you know, reliable.
+[1759.74 --> 1759.88]  Right.
+[1760.14 --> 1760.50]  Boring.
+[1761.06 --> 1762.40]  And it's still in production.
+[1762.72 --> 1764.28]  So this is an interesting question.
+[1764.38 --> 1768.24]  It's like, I want to do something that's kind of risky, like switch to ZFS or ButterFS,
+[1768.24 --> 1773.54]  but I don't want to have to purchase an external hard drive to back everything up to.
+[1773.94 --> 1777.08]  And there's definitely part of me that's like, that's just not how it works.
+[1777.24 --> 1781.06]  I just want to say, you know, when you're messing with important data, you do kind of
+[1781.06 --> 1787.48]  want to externalize it because you can convert an extended four partition in place to ButterFS.
+[1787.80 --> 1789.22]  I've done it a couple of times, actually.
+[1789.48 --> 1793.52]  I was just having a conversation with somebody earlier this morning about just that thing.
+[1793.52 --> 1794.98]  And it'll work.
+[1795.80 --> 1798.48]  But I can't tell you it's risk free.
+[1798.76 --> 1799.72]  It is absolutely not.
+[1800.60 --> 1802.26]  And so I don't know how you get around that.
+[1802.32 --> 1806.54]  Do you have any ideas on maybe like pulling other disks on your LAN or I mean, something
+[1806.54 --> 1807.24]  out of the box?
+[1807.88 --> 1808.28]  Not really.
+[1808.64 --> 1813.30]  I mean, it's it goes back to that whole raid is not a backup type thing.
+[1813.44 --> 1819.12]  So even if you have a volume mirrored on two drives, unless that data exists somewhere
+[1819.12 --> 1823.50]  else as well, I would pretty much say that data doesn't actually exist at all.
+[1823.72 --> 1827.10]  Because if that mirror was to go pop, that data is gone.
+[1827.30 --> 1830.18]  So this is probably not what you want to hear.
+[1830.66 --> 1835.58]  But I would buy that external hard drive, mirror everything onto that external hard drive,
+[1835.84 --> 1841.78]  free up the two drives that you want to put ZFS or ButterFS onto, and then you should be
+[1841.78 --> 1842.24]  good to go.
+[1842.76 --> 1844.28]  That I completely agree with.
+[1844.50 --> 1849.72]  And now, as an aside, I want to just acknowledge that I do feel like we go about our daily lives
+[1849.72 --> 1854.48]  totally underutilizing lots of free space on the systems on our LAN.
+[1854.64 --> 1858.10]  And I know there's a couple of projects out there to crack this nut.
+[1858.16 --> 1863.02]  But if anybody listening is using something and has been using it for a little bit to take
+[1863.02 --> 1867.54]  advantage of maybe, you know, a machine over here that's connected via Ethernet that has
+[1867.54 --> 1868.76]  120 gigs free.
+[1868.76 --> 1871.08]  And this machine over here that has a terabyte free.
+[1871.18 --> 1874.20]  And I have a machine over here that has 500 gigs and a machine over here that has four
+[1874.20 --> 1874.98]  terabytes free.
+[1875.42 --> 1881.40]  And I just need temporarily, I just need somewhere to store an extra seven terabytes a day.
+[1881.44 --> 1887.30]  It's like, could I pool everything somehow together and then somehow trust that this network
+[1887.30 --> 1889.34]  file system would work?
+[1889.34 --> 1893.10]  And you could, there's ways you could hack it together, especially with, you know, on
+[1893.10 --> 1894.58]  Linux with different mount points and all of that.
+[1894.64 --> 1897.04]  But I just don't, I just don't know of a solid one.
+[1897.16 --> 1899.08]  So selfhosted.show slash contact.
+[1899.40 --> 1903.98]  If anyone out there has something just out of curiosity, just be a fun thought experiment
+[1903.98 --> 1905.82]  to pool the storage on my network.
+[1906.02 --> 1909.28]  I don't think I'd use it for anything in production or for backup though.
+[1909.64 --> 1910.70]  I just don't think I would.
+[1911.30 --> 1916.94]  The next one comes from Mike and he's responding to a question I proposed last week about using
+[1916.94 --> 1921.74]  home assistant automations to cycle the charging of batteries on and off.
+[1921.80 --> 1927.06]  So that way devices don't sit at a hundred percent charged for days or they don't stay
+[1927.06 --> 1928.20]  at zero percent charge.
+[1928.28 --> 1931.24]  You may be something in the 40 to 60 percent range.
+[1931.50 --> 1935.48]  It'd be lovely to have an option to say today, I want everything charged to a hundred percent
+[1935.48 --> 1938.50]  because we're going on a road trip today and we need everything charged up.
+[1938.70 --> 1942.90]  And we got a couple ideas suggested and I liked Mike's and I wanted to give it a read
+[1942.90 --> 1943.08]  here.
+[1943.12 --> 1946.92]  He says, since there's really no out of the box solution right now, I'm going to
+[1946.92 --> 1951.78]  I'm creating a script that scrapes my laptop's battery info and then we'll publish it to
+[1951.78 --> 1956.88]  my home assistant's MQTT broker and then home assistant will act on that data to power
+[1956.88 --> 1958.84]  cycle my laptop's power supply.
+[1959.26 --> 1960.10]  Keep up the show.
+[1960.22 --> 1960.48]  Thanks.
+[1960.62 --> 1962.48]  And Mike, good idea.
+[1962.56 --> 1963.66]  That's great for the laptops.
+[1963.98 --> 1970.28]  The impossible nut that I'm trying to crack is like iOS devices, maybe even drone batteries,
+[1970.62 --> 1975.40]  things that don't even have an OS to scrape from, but you'd almost need like a time-based
+[1975.40 --> 1975.86]  system.
+[1975.86 --> 1978.34]  I suppose I'm still chewing on it right now.
+[1978.46 --> 1984.86]  I just kind of do it manually and it's not bad, but an example of a system that I probably
+[1984.86 --> 1990.68]  don't unplug and cycle the battery as frequently as I should are those fire tablets that are
+[1990.68 --> 1991.84]  plugged in and mounted on the wall.
+[1992.02 --> 1995.68]  I do power cycle them on occasion, but not regularly.
+[1995.68 --> 2000.50]  And with the home assistant app on Android, like there is something I could do there, but
+[2000.50 --> 2002.46]  I'm not looking for onesie twosie solutions.
+[2002.58 --> 2004.86]  I'm kind of looking for something that would work for everything.
+[2005.20 --> 2010.62]  I'm going to plug something that our community started about six months ago called Halcyon,
+[2010.72 --> 2012.86]  home assistant Linux companion app.
+[2013.24 --> 2016.42]  And there's a link in the show notes, halcyon.casa.
+[2016.42 --> 2023.86]  It's a Rust based application designed to run on Linux systems to present those metrics
+[2023.86 --> 2024.56]  to home assistant.
+[2025.26 --> 2028.14]  It's early days and it needs some love and some work still.
+[2028.30 --> 2032.70]  But if you're interested in that, check out, there's a dedicated channel in the discord
+[2032.70 --> 2033.68]  for Halcyon as well.
+[2034.00 --> 2035.04]  And it's written in Rust.
+[2035.14 --> 2035.94]  So what more could you want?
+[2036.10 --> 2036.78]  I love that.
+[2037.24 --> 2041.78]  Now, Brad writes in, I'm looking into moving off Google photos like everybody else.
+[2041.78 --> 2045.22]  It seems I've landed on Plex photos as my solution.
+[2045.62 --> 2051.66]  I have some friends that are also self-hosters and I've given them WireGuard access and they
+[2051.66 --> 2056.94]  said I can have a few hundred gig of storage on their networks for my photos and vice versa.
+[2057.54 --> 2061.54]  What I'm stuck on though is an encrypted backup method for backups.
+[2061.76 --> 2062.96]  I've tried Duplicati.
+[2063.24 --> 2066.26]  I've tried some other backup solutions.
+[2066.54 --> 2071.06]  I don't really care about how it backs up file changes as the library is growing.
+[2071.06 --> 2072.54]  I'm not editing the photos.
+[2072.68 --> 2074.30]  So only incremental is needed.
+[2074.66 --> 2078.50]  They do need to be encrypted though, because they're going to be on a remote LAN.
+[2079.14 --> 2082.52]  Now, I haven't done a lot of research on this yet, but do you know of any software that
+[2082.52 --> 2088.30]  doesn't automated one way backup phone to server, for example, to get the photos off
+[2088.30 --> 2092.46]  my phone and onto the server where I can delete them off my phone and they will stay on the
+[2092.46 --> 2092.72]  server.
+[2093.14 --> 2094.48]  Looking forward to future episodes.
+[2094.80 --> 2095.82]  Thanks, Brad.
+[2096.18 --> 2097.24]  This is a good question.
+[2097.38 --> 2099.10]  Duplicati is not quite cutting it.
+[2099.10 --> 2101.64]  And so what do you step up to essentially?
+[2101.88 --> 2104.34]  And you don't want something probably that's a lot to manage either.
+[2104.66 --> 2108.36]  Oh, Duplicati has just wound me up over the years.
+[2108.50 --> 2113.36]  You know, it just silently fails and stuff just breaks and there's no way to monitor it.
+[2113.42 --> 2115.36]  And you can only configure it through the GUI.
+[2115.72 --> 2116.84]  It's a great app.
+[2116.94 --> 2121.76]  It just isn't very reliable, which is not really suitable for a backup system.
+[2122.14 --> 2122.30]  Yeah.
+[2122.30 --> 2127.90]  I don't know where the failure process, when my backups failed, when my Google Drive payment
+[2127.90 --> 2129.74]  expired or switched.
+[2129.98 --> 2131.94]  I don't know where the failure was exactly.
+[2132.12 --> 2134.14]  I don't know if there wasn't a notification, but I don't know what.
+[2134.66 --> 2135.96]  It was ultimately it was my fault.
+[2136.40 --> 2141.30]  I thought about recommending Borg, which is a really solid backup open source solution.
+[2141.74 --> 2143.28]  It's pretty space efficient.
+[2143.28 --> 2145.94]  It gives you good encrypted backups.
+[2146.06 --> 2149.62]  It supports compression and it'll use Fuse, too.
+[2149.66 --> 2153.70]  So you can do kind of creative ways to mount file systems, which could be kind of nice.
+[2154.24 --> 2155.58]  And it has a pretty large community.
+[2155.74 --> 2157.70]  You can find it at borgbackup.org.
+[2157.80 --> 2159.16]  That might be worth looking into.
+[2159.72 --> 2160.46]  Borg is an alternative.
+[2161.40 --> 2162.40]  Restic is another one.
+[2162.46 --> 2165.00]  We mentioned auto-restic and Restic last episode.
+[2165.32 --> 2166.18]  That's another one.
+[2166.18 --> 2172.44]  But for getting the things off your phone, I've just been really happy with the NextCloud app.
+[2172.70 --> 2177.46]  It backs up everything off my phone in full quality to my NextCloud instance.
+[2177.92 --> 2180.30]  And then from there, I can do with them whatever I want to.
+[2180.76 --> 2184.60]  That's the one we hear the most often from the audience, too, is the NextCloud solution.
+[2184.96 --> 2189.48]  We have gotten a recommendation a couple of times into the show about Photosync as well,
+[2189.54 --> 2190.70]  which is in the Android Play Store.
+[2190.82 --> 2191.72]  Photosync, one word.
+[2191.72 --> 2198.08]  And the nice thing about Photosync is it supports various different kind of network backup options,
+[2198.18 --> 2200.34]  even Samba, if you want to go that route.
+[2200.78 --> 2203.12]  You could just back up your photos over Samba from Android.
+[2203.44 --> 2205.22]  So I'll put a link to that in the show notes as well.
+[2205.68 --> 2208.08]  Now, you mentioned in your question about Plex Photos,
+[2208.20 --> 2213.84]  and this is a really bad time to be adopting Plex Photos as a solution, unfortunately.
+[2214.74 --> 2218.60]  Plex document on their support pages that as of June 2021,
+[2219.52 --> 2221.38]  camera upload is going to be discontinued.
+[2221.38 --> 2223.00]  Womp, womp.
+[2223.08 --> 2223.56]  Yeah, boy.
+[2223.78 --> 2228.22]  And I think a lot of us are just getting, we're just getting a little Plex skeptical.
+[2228.96 --> 2231.80]  We're still Plex hopeful, but we're getting Plex skeptical.
+[2232.20 --> 2237.94]  And I do have to admit personally that Plex skepticism I'm feeling right now would probably,
+[2238.94 --> 2242.08]  I'd hesitate from using Plex Photos myself for a back,
+[2242.12 --> 2243.86]  and I'm not using it because of that reason.
+[2243.86 --> 2247.10]  Dare I say, Plex are becoming the Google of the self-hosted world,
+[2247.20 --> 2253.08]  just killing stuff randomly and not focusing on the core products like they should be?
+[2253.20 --> 2253.64]  I don't know.
+[2253.72 --> 2255.06]  I guess I feel it's kind of mean.
+[2255.32 --> 2262.16]  They are such a smaller team that they do have to be a little more conservative about where they spend their time and money,
+[2262.24 --> 2268.24]  where Google's like this, you know, this just financial monster powerhouse supplied by an endless amount of ad money.
+[2268.24 --> 2271.38]  So it's like, come on, you know, maybe you could keep this going.
+[2271.74 --> 2273.36]  Maybe you could invest a little more in Stadia.
+[2273.50 --> 2274.84]  You know, like right now they're killing Stadia.
+[2275.26 --> 2275.98]  Drives me crazy.
+[2276.26 --> 2278.48]  I know it's not a self-hosted thing, but dang it.
+[2278.72 --> 2281.74]  Well, everybody knew that was going to happen even before it launched.
+[2282.08 --> 2282.34]  I know.
+[2282.42 --> 2284.12]  Like, did you see like some big exec just left?
+[2284.18 --> 2287.32]  Like the top Stadia exec just left Google or something?
+[2287.74 --> 2288.12]  Oh, really?
+[2288.34 --> 2290.20]  Yeah, not good, not good.
+[2290.42 --> 2294.16]  I was a big fan of it, even though I often have no internet when I'm out traveling.
+[2294.34 --> 2298.88]  I just love the idea of being able to play Stadia on any machine I want, Alex.
+[2299.08 --> 2301.82]  You know, games on a machine with just a really crappy video card.
+[2301.90 --> 2302.42]  I don't care.
+[2303.30 --> 2304.02]  Here's some neat ideas.
+[2304.50 --> 2309.06]  Well, I'm actually thinking about building my own self-hosted gaming setup here in the studio just using Steam, though.
+[2309.06 --> 2312.12]  You know, just have it on the LAN and just stream it to the boxes that way.
+[2312.58 --> 2316.48]  Use Steam, use Parsec, Moonlight, all these different streaming protocols.
+[2316.88 --> 2318.08]  Lots of different ways to skin that.
+[2318.12 --> 2318.40]  Turkey.
+[2318.70 --> 2322.00]  I want to say thanks to our members at selfhosted.show slash SRE.
+[2322.14 --> 2323.58]  Become a site reliability expert.
+[2323.74 --> 2324.78]  Keep the show on the air.
+[2324.88 --> 2331.84]  And as a thank you, as a special thank you, as a golden thank you, a limited ad feed, just nice, tight production.
+[2332.34 --> 2333.66]  It's a nice, tight, quicker show.
+[2334.14 --> 2334.72]  Isn't that great?
+[2334.98 --> 2337.46]  All the Drew loving, just less ads.
+[2337.64 --> 2340.10]  And you also get extra content.
+[2340.44 --> 2341.30]  A post show.
+[2341.52 --> 2345.66]  You get a post show where I'm going to try to propose, Alex, try something new for the summer.
+[2345.88 --> 2346.80]  We'll see how that goes.
+[2346.80 --> 2347.74]  Oh, no.
+[2347.82 --> 2349.00]  How much is this going to cost me?
+[2349.24 --> 2350.58]  Oh, yes, it will cost you.
+[2351.48 --> 2352.90]  Also, thank you to a Cloud Guru.
+[2352.98 --> 2354.24]  You can find them on social media.
+[2354.36 --> 2356.40]  They're just slash a Cloud Guru everywhere.
+[2356.86 --> 2357.70]  Pretty easy to find them.
+[2357.70 --> 2361.48]  Selfhosted.show slash contact is the place to go to get in touch with us.
+[2361.60 --> 2364.42]  And you can find me on Discord at AlexKTZ.
+[2364.78 --> 2365.56]  I'm over there, too.
+[2365.62 --> 2369.28]  You can find me at Chris Lass on the Discord or on the Twitter.
+[2369.50 --> 2372.32]  And the show is on the Twitter, too, at Self Hosted Show.
+[2372.56 --> 2373.52]  Thanks for listening, everybody.
+[2373.52 --> 2376.12]  That was selfhosted.show slash 44.

44： Plex Skeptics _transcript_corrected.txt

@@ -0,0 +1,713 @@
+[0.00 → 7.46] Have you noticed lately that the self-hosted and Home lab Subreddits freaking love their dashboards?
+[8.10 → 10.78] Yes, it's dashboards all day. Are you kidding me?
+[11.36 → 16.54] Every third post is, oh, I'm just humblebragging about all the self-hosted services I've got.
+[16.54 → 20.84] And I always feel like my dashboard is not as pretty as it could be.
+[21.34 → 23.22] I mean, they're not even as nice as your dashboards.
+[23.30 → 27.00] And these dashboards are like, they look like you should be controlling a starship with some of them.
+[27.00 → 31.16] The word dashboard has become a sound to me. You've just said it too much.
+[31.56 → 33.66] Dashboard, dashboard. Yeah.
+[33.98 → 39.60] I mean, there are lots of options, right? There is Homer, there is Kendal, there is, I mean, there are dozens of them.
+[39.84 → 46.34] I get why people like them, but they're just another thing to become out of date.
+[46.42 → 52.54] And I find that even if I set one up, the entropy to keeping it up to date is too high.
+[52.54 → 57.88] And six months later, I haven't opened it for a while. And, oh, I don't even run that service anymore.
+[57.98 → 58.90] Why is that still on there?
+[59.40 → 63.06] And it gets worse the more devices you have, or you remove or add.
+[63.22 → 67.58] And in some cases, I have devices that go offline or online depending on my location.
+[68.16 → 71.02] And then the dashboard is like messed up temporarily while I'm travelling.
+[71.02 → 74.32] And then I just like debate the entire time if I should remove it.
+[74.62 → 80.06] And God forbid, I take something out, and then I have to go everywhere and make sure I've got it removed from my Lovelace dashboard and my Heads Up dashboard.
+[80.40 → 83.04] It's just like it's dashboard overload for me.
+[83.46 → 86.34] But I get the people like they like sharing them.
+[86.74 → 92.74] And I kind of like I like viewing them sort of like I enjoy viewing desktop screenshots.
+[93.66 → 95.14] Oh, that's an interesting way to do it.
+[95.14 → 98.56] And sometimes I'm like, never going to do that.
+[99.18 → 100.66] I'm just never going to go that far.
+[101.32 → 102.02] It's discovery.
+[102.46 → 104.80] You know, oh, look, this person's got 47 apps.
+[104.94 → 106.24] What what does this one do?
+[106.66 → 107.26] Yeah, that's true.
+[107.38 → 107.78] That's true.
+[108.38 → 110.40] Well, go see what you can do at the all new a cloud guru.
+[110.52 → 113.70] They are the leader in learning for the cloud, Linux and other modern tech skills.
+[114.06 → 116.28] Hundreds of courses and thousands of hands on labs.
+[116.52 → 119.48] Get certified, get hired, get learning at a cloud guru dot com.
+[119.86 → 121.52] Did you see the Preamp update?
+[121.92 → 122.76] Wow, Alex.
+[123.02 → 124.94] I was wondering if you caught this.
+[124.94 → 126.90] I was going to ask you if you saw the new Preamp.
+[127.00 → 131.48] Yeah, it's its a big update for iOS and Android.
+[132.02 → 135.10] And I think at least the iOS one will be really soon.
+[135.16 → 138.36] But the death is a desktop version of Preamp now as well, which I didn't even know.
+[139.02 → 144.70] And they've added one feature that I've wanted since the very first time I tried Preamp.
+[144.90 → 146.10] And it's the shuffle button.
+[146.52 → 148.30] So happy to have a shuffle button now.
+[148.90 → 150.28] I don't know what to say to that.
+[150.92 → 154.50] And I know you're going to be elated to see that they've also added Siri support.
+[154.50 → 159.22] So now you can play music on Preamp through Siri, which I'm sure you're going to use all the time.
+[160.04 → 165.48] And as you know, as being a heavy iOS user, I'm not I'm still on Android.
+[165.62 → 173.26] I tried to switch to iOS in January, but was wearing a lot of face masks in the hospital and face ID and all that.
+[173.26 → 175.00] I ended up going back to Android.
+[175.20 → 179.46] So I was delighted to see that they've now added Siri support.
+[179.90 → 180.28] That's true.
+[180.44 → 180.96] That's true.
+[181.06 → 182.14] And it works.
+[182.28 → 183.16] You know, it's very simple.
+[183.66 → 185.38] It's its nothing really to write home about.
+[185.46 → 187.56] That's probably stuff that should have had a long time ago.
+[187.56 → 197.26] And I think in general, Preamp is probably one of my favourite Plex adjacent ecosystem applications.
+[197.26 → 200.82] We get people that write into the show, and they'll say, why do you guys use Plex?
+[200.90 → 201.62] There's Jellyfin.
+[201.76 → 202.58] There are other alternatives.
+[202.58 → 218.08] There's just this ecosystem around Plex now between the friends that I can share with, like Alex, for library sharing options, but also these apps around Plex that break off like the music experience into this individual app that's dedicated to just music.
+[218.08 → 219.34] It's its just wonderful.
+[219.34 → 222.62] And it's nice to see it get updated to version 3.4.5.
+[222.62 → 227.64] It really makes the music experience in Plex quite pleasurable, to be honest with you.
+[227.64 → 235.66] And the design language they've used for the application brings it up to the same sort of polish as something like Spotify or something like that.
+[236.08 → 239.70] It is just a 100% native looking music app.
+[239.80 → 241.24] And I think it's freaking great.
+[241.70 → 243.34] There are some things that aren't so freaking great, though.
+[243.88 → 244.98] Good and bad, I suppose.
+[245.16 → 251.46] Plex revealed that it recently completed a growth equity round of 50 million dollars from an existing investor.
+[251.76 → 252.74] Oh, yeah.
+[252.74 → 252.88] Yeah.
+[253.18 → 258.76] And the company intends to invest its money in a mission to become a one-stop shop for movies and TV.
+[258.94 → 261.74] And it aims to do this by addressing one of the most fuss.
+[262.18 → 268.70] And it aims to do this by addressing one of the most frustrating aspects today in the legal streaming market, they say.
+[268.82 → 271.04] And that is fragmentation.
+[271.54 → 273.06] You know, all the different streaming services.
+[273.06 → 279.28] They want to bring it all into Plex, including your pirated content or whatever else you might have on there.
+[279.28 → 284.98] Like for me, we use Plex for just home videos that we record that we don't want to put up like on YouTube or something.
+[285.42 → 287.88] And they want to bring it all into one UI.
+[288.32 → 294.18] And you can search all of it from the stuff in your own library to the stuff that's on Hulu to Netflix and Amazon Prime.
+[294.92 → 304.18] And Plex says they're going to work with these companies to get API access and integrate it all in there and try to make an experience where you go to one app, and you get all the streaming services.
+[304.80 → 307.32] I mean, I understand why they're doing this.
+[307.32 → 314.12] Because the revenue streams of a few Plex Pass subscribers surely can't self-sustain the company.
+[314.84 → 322.78] I mean, myself, as an example, I paid $75 for a lifetime Plex Pass half a decade ago, more than probably.
+[323.48 → 325.28] And they haven't seen a penny from me since.
+[325.42 → 335.50] And so, you know, I can understand how, you know, Hulu and Disney and Prime and Netflix are juicy targets for them to try and integrate into one place.
+[335.50 → 344.34] But if I was Netflix or Prime or Disney, I'm not sure if I would want people going outside my walled garden.
+[344.34 → 352.30] Because the whole reason that these companies have dedicated gardens, walled gardens for their content is so that they can do analytics on it.
+[352.30 → 357.38] And they can track you through, you know, minute by minute, second by second of what you're watching.
+[357.38 → 364.06] I mean, the Grand Tour is a great example of this, you know, old Top Gear turned into the Grand Tour, Jeremy Clarkson and all that.
+[364.38 → 366.94] One of my favourite TV shows of all time.
+[366.94 → 378.22] And a couple of years ago, Amazon decided to kill the studio part of the Grand Tour, which was my favourite part, in favour of just doing these epic specials.
+[378.28 → 384.24] And now we only get two or three episodes, well, less, a couple of episodes a year of the Grand Tour.
+[384.24 → 392.40] And they're these grand expeditions where they go to Madagascar, and they put tank tracks on a Ford Fiesta and stupid stuff like that.
+[392.90 → 398.90] Whereas what I watched the Grand Tour for was the cocking about between three old men sorts of taking the mickey out of each other.
+[399.20 → 407.42] But the reason they did that, Amazon, was because their analytics showed that most people didn't watch the studio segments.
+[407.42 → 411.68] You know, I can understand why they would make that change.
+[411.80 → 420.62] But if you're Amazon, and you're giving away API access to Plex, presumably you would bake in some of those analytics through the Plex client.
+[420.98 → 430.20] But one of the benefits of having people in your app is that they're not going to exit that app to go to Netflix to go and watch a specific show over there.
+[430.26 → 432.94] They're just going to carry on browsing in the portal they're already in.
+[432.94 → 445.78] And if Plex presents all of these different things in one place, the value props to subscribe to these different services becomes just too generic at this point.
+[445.84 → 447.52] And I just don't see it working, do you?
+[448.06 → 449.32] I have to say I completely agree, Alex.
+[449.40 → 452.68] And it goes just beyond like analytics and whatnot.
+[452.80 → 454.16] But there's also a technical angle.
+[454.24 → 458.10] Perhaps they want to tweak how the playback engine works with their particular type of CDN.
+[458.10 → 463.46] Or maybe they want to feature content for some special show they've just released or some big movie.
+[463.54 → 470.38] Like I just read this morning that Paramount Plus is planning to do a movie a month on their Paramount Plus streaming service.
+[471.02 → 480.04] And I got to imagine that every time one of those movie drops, they're going to do some sort of big presentation in a carousel that lets everybody know our new content is here.
+[480.10 → 483.22] And I just can't imagine Plex accommodating all of those whims.
+[483.22 → 488.28] All of these companies just got to become their own cable network essentially with their streaming service.
+[488.72 → 493.28] And we've just gone through the last 10 years of them figuring out how to actually stream video.
+[493.42 → 495.34] And they're just starting to get good at it now.
+[496.04 → 497.66] You know, Netflix had to set the example.
+[498.52 → 501.06] And so I just don't really see this taking up.
+[502.14 → 507.58] Maybe if Plex was willing to do something where they got access to the search API.
+[507.58 → 512.90] And then if you selected a video, say it was the Grand Tour, it would then just launch the Amazon app.
+[513.00 → 513.96] But how valuable is that?
+[514.02 → 516.84] And how do you even do that, say, like in a web version or something?
+[517.22 → 521.08] My Google Assistant does that already with voice search on the NVIDIA Shield.
+[521.76 → 523.76] It'll search through all the apps for me.
+[524.12 → 524.24] Right.
+[524.36 → 525.96] And ROK's trying to do the same thing.
+[526.02 → 528.28] And Apple wants to offer the same thing with the Siri remote.
+[528.54 → 528.90] Absolutely.
+[529.36 → 529.58] Yeah.
+[530.02 → 532.64] And $15 million isn't enough to do this.
+[532.64 → 535.34] So they raised $50 million from an existing investor.
+[536.06 → 541.88] And as part of that, it includes $15 million in new capital for Plex, which they're going to invest in this mission.
+[542.50 → 543.88] That's nowhere near enough, is it?
+[544.14 → 545.06] I can't imagine.
+[545.32 → 550.16] Unless they see a way of monetizing this, maybe through affiliate links or something like that with the streaming providers.
+[550.40 → 550.72] Maybe.
+[551.10 → 551.32] Yeah.
+[551.54 → 554.70] But you know, Alex, that doesn't even touch on what I don't like about this.
+[554.70 → 557.36] And that is this whole single pane of glass.
+[557.50 → 559.28] They actually use that term, experience.
+[559.28 → 563.32] It's I use Plex intentionally for a curated experience.
+[563.80 → 566.44] I don't want to see everything because it's a family cert.
+[566.52 → 567.68] It's something that we use for our family.
+[567.78 → 574.68] That's why I take the time to put things on there individually, myself as the dad or when, you know, the mom requests something.
+[574.86 → 579.44] I have a UI where they can go in, and they can request things.
+[579.44 → 583.12] But it is intentionally separated from everything else.
+[583.26 → 584.66] And there is an app on the screen.
+[584.84 → 585.38] They launch it.
+[585.44 → 586.00] They go in there.
+[586.06 → 587.16] I know everything's safe.
+[587.16 → 589.84] I have parent stuff separated out from kids stuff.
+[590.06 → 592.64] And I have really no interest in mixing it all.
+[592.72 → 594.94] I can't tell for sure at this stage.
+[595.04 → 600.44] But reading between the lines, it does look like they're going to give you the option to not mix everything together.
+[600.44 → 602.16] But it will be mixed by default.
+[602.48 → 604.00] I mean, I guess time will tell on this one.
+[604.38 → 607.96] I kind of hope we're proved right because I really agree with you.
+[608.02 → 610.04] I don't want to see this stuff.
+[610.12 → 613.52] The reason I have Plex is that I want to control what I see.
+[613.70 → 615.38] So, yeah, I'm with you on that one.
+[615.38 → 620.06] Yeah, it gets my head spinning immediately on, well, what would I go to?
+[620.70 → 622.04] What would I transition to?
+[622.30 → 625.06] Because I've got a lot of time invested in my Plex library.
+[625.40 → 632.76] And so on of the things I've already done on our Apple TV is I've switched to using – I've talked about it before on the show.
+[632.86 → 634.48] I've switched to using Infuse.
+[634.56 → 635.82] And I'm going to put a link to it again.
+[635.94 → 636.78] It's a paid app.
+[637.22 → 638.78] It's like Cody for Apple TV.
+[639.16 → 641.00] And I don't use that lightly.
+[641.00 → 642.42] I have a lot of respect for Cody.
+[642.50 → 644.12] But this is like Cody for Apple TV.
+[644.34 → 651.60] It can bring together multiple servers over network connections, Google Drive, Dropbox.
+[651.80 → 653.80] And it supports Plex.
+[654.20 → 658.04] It will do your watch status and everything that you would need to track in Plex.
+[658.68 → 660.50] And it's just a fantastic UI.
+[660.50 → 664.42] And it has much better AirPlay support.
+[664.54 → 675.40] So if you use HomePods with an Apple TV, or you're using some kind of crazy AirPlay setup, Infuse does it perfectly where the actual Plex client on Apple TV and iOS is not actually great at that stuff.
+[675.48 → 676.60] It sometimes has issues.
+[676.98 → 683.84] And so when I see this news about one meta search engine for all streaming, I think, yeah, that's all good, guys.
+[683.88 → 686.94] But you're not even enticing me to use your own app these days.
+[687.08 → 688.48] Like there are other things to focus on.
+[688.48 → 693.24] And I have a lot of respect for the Plex folks, but it is just what it is now is I'm using Infuse.
+[693.52 → 696.56] And you can get it at firecore.com slash Infuse.
+[696.76 → 701.36] And they've just recently released a Mac desktop version, too, which is kind of a neat idea, I suppose.
+[701.82 → 706.22] I know lots of the audience are frantically screaming at their podcast devices.
+[706.34 → 707.24] What about Jellyfin?
+[707.40 → 708.12] What about MB?
+[708.60 → 709.40] Well, maybe one day.
+[709.48 → 712.42] Maybe you and I eventually will become Jellyfin guys in the future.
+[712.48 → 712.92] It could happen.
+[713.54 → 716.26] I do experiment it from time to time.
+[716.32 → 718.04] Have you ever kicked the tires with Jellyfin?
+[718.04 → 718.68] I have.
+[718.98 → 720.02] And I went back to Plex.
+[720.98 → 721.50] Okay.
+[721.66 → 721.98] Sorry.
+[722.80 → 725.36] I mean, it's pretty good for what it is.
+[725.90 → 727.72] It's just Plex has a head start.
+[728.10 → 736.80] And the fit and finish of the UI and the experience I have there is much better on Plex than Jellyfin.
+[737.28 → 738.56] What would it take for you to switch?
+[738.56 → 745.80] I think when it's suitable for my family members, you know, that they have a lot of time invested in learning.
+[746.28 → 748.56] Plex has various UI changes over the years.
+[748.94 → 751.84] And they kind of figured out how it works now for the most part.
+[751.84 → 756.82] Once Jellyfin's at that kind of level of polish, it's just not yet, though.
+[756.82 → 760.24] Linode.com slash SSH.
+[760.34 → 763.20] Linde is the largest independent cloud computing provider.
+[763.34 → 769.12] And when you go to Linode.com slash SSH, you'll get $100 in 60-day credit towards a new account.
+[769.32 → 770.92] And you can go there to support the show, too.
+[771.46 → 773.18] We were just talking about media servers.
+[773.18 → 778.46] Well, Linde has a one-click application deployment for Plex if you want to get a Plex server up in the cloud,
+[778.56 → 781.60] which is a great way to share with friends and family at superfast streaming speeds.
+[782.00 → 784.92] Of course, you could just build your own stack and deploy Jellyfin or anything you'd like.
+[785.02 → 789.24] And no matter what skill level you're at or what technology stack you're familiar with using,
+[789.72 → 791.50] Linde will help you get it going online.
+[791.62 → 793.64] They have a really easy-to-use dashboard.
+[794.08 → 798.02] And if you have any trouble getting things going or run into any kind of problem,
+[798.02 → 803.46] Linde has amazing, fantastic, great, outrageously good customer support.
+[803.68 → 805.66] By phone or ticket, they're going to help you get it solved.
+[805.72 → 810.42] If you've got one rig, or you're like me, and you're crossing, like, the 15-rig mark or something,
+[810.50 → 812.98] I mean, it's getting crazy because we use Linde for everything.
+[813.08 → 815.16] And it's not just, like, haphazardly.
+[815.84 → 817.48] We think about every machine we deploy.
+[817.68 → 821.42] And we decide, okay, is this going to be the machine that is just a dedicated box?
+[821.42 → 824.46] Maybe it only runs one application, or it runs just a couple of things.
+[824.92 → 827.08] Or is this going to be something like an application server?
+[827.08 → 829.72] We have a couple of these, too, where these are more powerful Li nodes.
+[830.08 → 833.10] And we run multiple containers on them, running multiple applications,
+[833.40 → 839.84] from mail to encoding services to matrix to, well, really, you run the gamut.
+[839.86 → 842.58] Anything we're just talking about on the show, we pretty much host it on Linde.
+[843.12 → 844.32] People ask me, why, Chris?
+[844.34 → 845.62] Because there are a lot of places to host.
+[845.76 → 849.94] Well, the reason for that really comes down to a few core things that I think are pretty important.
+[850.42 → 852.50] Number one, it is a perfect product.
+[852.62 → 853.56] It's very fast.
+[853.64 → 855.10] They have 11 data centres worldwide.
+[855.10 → 859.74] The interconnects between the data centres, I think, beat what everybody else has, hands down.
+[860.08 → 861.36] Linde is their own ISP.
+[861.48 → 866.02] So they just have a networking opportunity that people that haven't been around as long don't have.
+[866.64 → 871.84] Additionally, their dedicated CPU rigs, they're just faster than other people's dedicated CPU rigs.
+[871.96 → 872.70] I like that.
+[873.14 → 876.72] Then you factor in that they're really just good Linux-loving folks.
+[876.80 → 878.38] They have been since 2003.
+[878.38 → 882.16] And that factors into some of the decisions on how they've built the product.
+[882.52 → 884.48] And those things appeal to me.
+[884.74 → 886.40] They make it easy for me to use.
+[886.44 → 888.00] And I feel like it's very simple.
+[888.10 → 890.82] But when I need power in that dashboard, it's there.
+[890.98 → 894.16] And then there are services like their S3-compatible object storage.
+[894.16 → 900.72] Now, this is great because I can use S3 object storage for backup, for configs that I want to store off-site.
+[900.80 → 904.56] Or we use it as the back-end storage mechanism for our next cloud instance.
+[904.64 → 908.10] So we're not having to sit there and fiddle with different disk sizes like amateurs.
+[908.38 → 910.62] We just throw it on the S3 storage.
+[910.62 → 915.06] But Linde's so fast that it really is very performant.
+[915.20 → 916.70] And it's a great way to build a static website.
+[917.14 → 918.82] There's so much you can do there.
+[918.90 → 929.10] If you just need something simple like a portfolio website, or if you want to run the back-end infrastructure for your team collaboration or for your e-commerce website, Linde's going to be able to do it all.
+[929.18 → 931.34] So go to linode.com slash SSH.
+[931.34 → 934.22] Get that $100 60-day credit on your new account.
+[934.58 → 936.54] And then just see what it can do.
+[937.24 → 938.46] See what we've been talking about.
+[938.68 → 940.10] And see why we use it for everything.
+[940.62 → 942.46] Linode.com slash SSH.
+[943.98 → 947.12] Now what do you do for home assistant wall panels?
+[947.20 → 950.78] I recall you bought a Fire tablet a while ago, right?
+[951.12 → 952.26] I have a couple of them now, yep.
+[952.42 → 957.90] I have a 10-inch one and a 7-inch one that I have mounted in the Lady Joop's RV.
+[958.32 → 959.20] How are they working out for you?
+[959.22 → 959.60] Do you like them?
+[959.60 → 960.60] Pretty good.
+[960.80 → 961.74] Pretty good.
+[961.98 → 963.72] Not very good performance.
+[964.04 → 969.88] And also one of them, even though I bought the no-ads model, has ads on the lock screen.
+[970.10 → 971.52] And I find that frustrating.
+[972.08 → 973.86] So the performance is not fantastic.
+[974.02 → 981.76] But just sitting there with a web page up, and after I install an app, after I sideload an app like an animal to keep the screen on, they get the job done.
+[981.76 → 982.18] All right.
+[982.18 → 983.38] Well, I've got a solution for you.
+[983.38 → 993.10] My wife has, or had, it's mine now, a Fire 7-inch HD tablet from 2015.
+[993.10 → 998.08] We paid £35 for this tablet six years ago.
+[999.02 → 1001.40] You know, the battery is crap.
+[1001.74 → 1003.62] I mean, the battery was crap when it was new.
+[1003.94 → 1004.88] The screen is bad.
+[1005.00 → 1006.64] It was bad back then.
+[1006.72 → 1008.02] So it's terrible now.
+[1008.56 → 1010.02] It's just not a great device.
+[1010.36 → 1011.00] Let's be honest.
+[1011.06 → 1013.60] But it was £35 six years ago.
+[1013.60 → 1020.52] And I thought to myself, wouldn't it be cool if I had a wall-mounted tablet dashboard?
+[1020.88 → 1021.34] Good for you.
+[1021.60 → 1027.70] In my workshop, I've been doing some automation around the woodworking blast gates that I have.
+[1027.74 → 1030.40] We'll talk about that more in an upcoming episode.
+[1031.18 → 1037.14] And then basically, I just wanted a touchscreen panel that I could just jab my fat fingers on and just open a certain blast gate.
+[1037.14 → 1042.08] I didn't want to spend any money because it's already, woodworking's already expensive enough.
+[1042.28 → 1045.72] Did you think about going with a voice tube out there before this, or do you already have one?
+[1045.96 → 1047.50] Well, I have a voice tube out there.
+[1047.78 → 1048.98] It's the lady cylinder.
+[1049.68 → 1055.64] And I, I don't know, I've kind of really gone off shouting orders across the room at these things.
+[1056.66 → 1063.26] I, in the rental house last, or before we bought this one, everything was on the Google voice system.
+[1063.26 → 1068.86] But I didn't set any of that up once we moved, and I haven't since, and I, I just don't miss it.
+[1069.24 → 1074.66] I mixed on it myself because there's sometimes you have to restate yourself, and you always feel like a fool when it, when it gets it wrong.
+[1074.88 → 1079.40] There's always that thing where you're making eye contact with the cylinder, waiting for it to light up.
+[1079.44 → 1080.06] And I'm like, oh.
+[1080.52 → 1080.66] Yeah.
+[1080.68 → 1086.14] And then in my situation, you add every time we're off grid, of course, the voice transcription doesn't work.
+[1086.22 → 1088.94] So that's really where I was like, okay, we got to have tablets.
+[1089.14 → 1092.60] And also it's nice to glance at it and just see what's on and what's off.
+[1092.60 → 1094.52] So how did you go about accomplishing this?
+[1094.82 → 1099.08] Well, I put Lineage OS, which is an open source version of Android.
+[1099.40 → 1104.08] I think it's what came out of the Cyanogen mod project a few years ago.
+[1104.36 → 1104.54] Yeah.
+[1104.66 → 1107.54] I put Lineage OS 12 on this tablet.
+[1108.06 → 1116.70] And performance is better than the Amazon OS that was on there before, but it's still a six-year-old device.
+[1116.84 → 1117.46] You know what I mean?
+[1118.20 → 1120.22] Well, any performance improvement would be good.
+[1120.26 → 1121.74] This has crossed my mind before.
+[1121.94 → 1123.06] I have thought about doing this.
+[1123.10 → 1125.26] I just wasn't sure if it was really worth the bother.
+[1125.66 → 1127.52] It was a bit of a pain, right?
+[1127.52 → 1141.52] I had to unlock the bootloader, which involved, I had to take the back off the tablet, bridge a couple of pins on the motherboard to ground the bootloader out so that it would boot into the bootloader mode for Android.
+[1141.62 → 1145.52] I don't know if you've ever done anything with ADB and fast boot.
+[1145.86 → 1146.66] A while ago, but yeah.
+[1146.66 → 1152.06] I had to use those tools to put a custom recovery partition on there.
+[1152.08 → 1161.36] So I used Team Win Recovery Project, TWRP, and sideloaded on there a bunch of different APKs and the Lineage OS ROM.
+[1162.02 → 1168.42] This process probably took me an evening of mostly fuzzing about and getting into that bootloader mode was the hardest part.
+[1168.66 → 1170.78] Are you using Windows to do any of this?
+[1170.78 → 1175.62] I mean, I have all three in this room, so I, you know, between the different devices.
+[1175.96 → 1177.48] Does it require Windows is what I'm asking?
+[1177.64 → 1178.84] Do you need Windows?
+[1178.98 → 1179.44] Because I'm out.
+[1180.02 → 1182.08] That's a disqualified for me right there.
+[1182.22 → 1184.80] I think this one works best under Linux.
+[1184.94 → 1187.60] I actually just used a Raspberry Pi in the end.
+[1187.70 → 1188.16] Oh, okay.
+[1188.52 → 1189.32] I have those.
+[1189.60 → 1190.34] I know you do.
+[1191.28 → 1194.88] I ended up just using a Raspberry Pi with Ubuntu on.
+[1195.44 → 1196.00] All right.
+[1196.02 → 1197.10] Now you're talking about language.
+[1197.42 → 1198.98] So it took you a little bit of an evening,
+[1198.98 → 1203.30] but it sounds like if I followed some tips from you, maybe it wouldn't take me that long.
+[1204.02 → 1208.22] Well, this is for the specific revision of the 2015 7-inch Fire tablet.
+[1208.54 → 1211.48] So I don't know if the newer ones have a more locked down bootloader.
+[1211.70 → 1215.10] That's the key is once you can get a custom recovery software on there,
+[1215.60 → 1217.56] you can install whatever image you like.
+[1217.56 → 1224.32] My first question, once you get the OS on there, is do you do Gaps and do you need Gaps for this tablet?
+[1224.62 → 1227.22] No, you definitely don't anymore because of Droid.
+[1227.22 → 1232.60] So my use case was to use this thing exclusively for Home Assistant.
+[1232.96 → 1233.06] Right.
+[1233.24 → 1238.44] And so Lineages, out of the box, ships with no Google software whatsoever,
+[1238.80 → 1241.60] which is awesome on such an underpowered device.
+[1242.30 → 1243.86] And then so I just loaded Droid.
+[1243.96 → 1249.80] I went to the Droid website, enabled unsigned or unknown sources for APK installation,
+[1250.50 → 1254.68] installed the Droid APK, and now I have a Google-less app store.
+[1254.68 → 1257.16] And Home Assistant is available in that app store.
+[1257.32 → 1258.84] So happy days.
+[1259.22 → 1260.26] And how are you doing the screen?
+[1260.38 → 1261.24] Are you letting it sleep?
+[1261.32 → 1262.52] Are you leaving it on all the time?
+[1262.78 → 1268.62] Because it's going to be used very infrequently, I have just used the standard lock and unlock.
+[1268.92 → 1271.28] And it's going to take me a couple of taps to unlock the screen,
+[1271.40 → 1274.80] but I use it a couple of times a day, if that.
+[1275.30 → 1276.58] Yeah, that makes sense.
+[1277.04 → 1280.74] Now, the other question I have is, are you using the web dashboard,
+[1280.74 → 1284.44] or did you load the Home Assistant app and interface with it that way?
+[1284.74 → 1288.00] Yeah, I loaded the app through Droid and the performance.
+[1288.32 → 1292.02] So I have a lot of experience with how long it takes to load that app on my phone.
+[1292.26 → 1294.76] And it can take a beat sometimes.
+[1294.90 → 1302.80] Performance of Lovelace and the interface of Home Assistant could be better, shall we say,
+[1302.90 → 1303.94] even on modern hardware.
+[1303.94 → 1308.94] So you can imagine on this six-year-old device, it takes a good 10 seconds to load.
+[1309.22 → 1310.48] Once it's loaded, it's fine.
+[1310.54 → 1311.92] And it works just fine.
+[1311.96 → 1314.72] But it's that initial load that can take a while.
+[1315.14 → 1317.58] If you have a guide or anything like that, is there something we could share in the show notes?
+[1317.86 → 1318.84] Yep, it's already in there.
+[1319.04 → 1319.36] Aha!
+[1320.08 → 1322.12] That'll be at self-hosted. Show slash 44.
+[1322.62 → 1325.10] We talked about HealthChecks.io last episode.
+[1325.22 → 1329.02] And in there, I asked you about monitoring if APIs or services are up.
+[1329.04 → 1330.16] And you mentioned Prometheus.
+[1330.16 → 1336.04] Prometheus, well, I want you to tell me more about it because we got a few people that bit via email.
+[1336.52 → 1337.20] Yeah, we did, actually.
+[1337.48 → 1342.58] And I was quite surprised to see just how many people either already used Prometheus
+[1342.58 → 1347.62] and wanted to tell me all about how awesome it was or didn't use it and wanted to know more.
+[1347.70 → 1348.76] So here's a little primer.
+[1349.46 → 1355.30] Essentially, Prometheus scrapes data on remote servers, gathers it into one place.
+[1355.30 → 1364.74] You write queries to query that data and present it in a dashboard or forward on certain things to something called Alert Manager,
+[1365.02 → 1366.86] which can then alert you.
+[1367.00 → 1371.76] So if your disk percentage, for example, on a remote system goes above 80% used,
+[1372.26 → 1374.62] you could have it notify you of that and say,
+[1374.98 → 1378.64] hey, you should probably go and delete some stuff before this server fills up.
+[1378.64 → 1383.98] Now, what I ended up using it for is my VMware box downstairs.
+[1385.14 → 1386.50] It's now just my Home Lab.
+[1386.60 → 1387.80] It's not actually my main server.
+[1387.92 → 1391.28] It's just performing OpenShift Home Lab duties for me.
+[1391.86 → 1396.12] And I put it into a case where fan control was a bit of an issue.
+[1396.42 → 1400.84] And so I mentioned in the previous episode about a fan controller,
+[1400.84 → 1406.56] the Corsair Commander Pro that is usable on Linux now.
+[1406.80 → 1415.06] But one of the things I wanted to do was actually get a feel for how the CPU temperatures were in that system over time,
+[1415.06 → 1416.80] because I've got a couple of hard drives in there.
+[1417.44 → 1421.16] And, you know, if things are getting toasty, hard drives tend to die pretty quickly.
+[1421.40 → 1429.50] So what I wanted to do was monitor that VMware venter instance with Prometheus and have it alert me if there was a problem.
+[1429.84 → 1430.06] Nice.
+[1430.06 → 1433.10] I ended up using this thing called VMware Exporter.
+[1434.16 → 1437.46] And there's a link to the Docker Compose snippet in the show notes.
+[1438.38 → 1447.00] And this thing, basically what it does is it logs into sphere's API every pre-prescribed interval.
+[1447.12 → 1449.26] I think I've got it set to like 15 seconds or something.
+[1450.04 → 1453.94] Scrapes a bunch of data available through the venter API,
+[1454.46 → 1457.44] which includes stuff at the host level like CPU temperature,
+[1457.44 → 1462.58] but also includes the PMI data like the voltages and all that kind of stuff.
+[1462.64 → 1466.08] So it's pretty granular and pretty detailed if you want to know that stuff.
+[1466.08 → 1469.70] And then it imports it into the Prometheus real-time database.
+[1469.70 → 1475.64] And from there, once it's in Prometheus, I can query it using Grafana or whatever else I want to.
+[1476.34 → 1481.90] And I use a container called Prior der, I think is how you say it.
+[1482.02 → 1483.52] Prior der VMware Exporter.
+[1484.22 → 1486.76] Super simple little Python app and just does the job.
+[1486.76 → 1489.74] What kind of hardware utilization, I guess, is what I'm asking.
+[1489.94 → 1493.28] So if I have a system, I have an existing Leon box here at the studio.
+[1493.90 → 1497.40] It's probably about 30% utilized CPU-wise and memory-wise.
+[1497.92 → 1499.36] Do I need something more powerful?
+[1499.48 → 1501.62] Do I have enough headroom for running these kinds of services?
+[1502.04 → 1504.16] Prometheus itself is pretty lightweight.
+[1504.90 → 1508.94] You know, with any real-time metrics gathering system like this,
+[1509.02 → 1512.34] we'll probably want to put it on some kind of flash-based storage media.
+[1512.34 → 1517.56] So, you know, you'll need a few gigabytes scratch disk for that to use.
+[1517.80 → 1521.76] But then once you've done that, you need to create what are called scrape jobs,
+[1522.02 → 1525.14] which is how you tell Prometheus what to look for
+[1525.14 → 1528.56] and what to kind of gather in terms of metrics on remote systems.
+[1529.08 → 1533.70] You configure that in my favourite language of them all in a YAML file.
+[1534.46 → 1538.42] And once you've done that with Prior der, you kind of set it, forget it,
+[1538.46 → 1540.36] and never worry about it ever again.
+[1540.36 → 1542.46] And then how long does it collect for? Forever?
+[1543.30 → 1544.44] How long do you do it for?
+[1545.02 → 1546.28] I haven't really worried about it.
+[1546.38 → 1546.98] I just sort of...
+[1546.98 → 1547.32] Forever!
+[1547.80 → 1549.16] Keep them forever, yeah.
+[1549.24 → 1551.88] I mean, I guess if you're in an enterprise situation
+[1551.88 → 1556.14] where you're scraping 10,000 servers, that might be an issue, but I'm not, so...
+[1556.14 → 1558.28] Yeah, so maybe not a big deal.
+[1558.40 → 1560.06] You could be. That'd be kind of fun, wouldn't it?
+[1560.10 → 1561.68] Go back 10 years and look at stuff.
+[1562.42 → 1562.78] Oh!
+[1563.38 → 1565.72] Well, I mean, look, this is how these big guys do it.
+[1565.72 → 1570.38] I mean, Kubernetes clusters the world over are monitored by Prometheus.
+[1570.94 → 1574.38] OpenShift actually ships a bunch of stuff with Prometheus built in.
+[1574.56 → 1578.28] So this is one of those technologies that if you're thinking about getting into DevOps
+[1578.28 → 1582.08] and that kind of space of, you know, site reliability engineering,
+[1582.80 → 1586.48] these are the sorts of tools that you should be mucking about within your home lab
+[1586.48 → 1588.94] and trying to figure out how they work and understand them
+[1588.94 → 1592.02] because you'll be able to take that knowledge and use it to get a better job.
+[1592.02 → 1593.36] Yep, great skill to have.
+[1593.90 → 1594.98] I just like the idea.
+[1595.04 → 1597.32] I just like the idea of picturing you like 10 years from now,
+[1597.40 → 1603.72] looking back at some graph analogs and just kind of getting nostalgic from graphs and logs.
+[1604.16 → 1607.98] Yeah, my CPU is 33 degrees on May the 5th, 2021.
+[1608.34 → 1609.06] Hey, great.
+[1609.22 → 1610.80] Ah, I remember that, yeah.
+[1611.16 → 1612.26] Those were the days.
+[1615.22 → 1616.30] Cloudfree.shop.
+[1616.30 → 1618.88] Head over there and buy from a community member
+[1618.88 → 1624.58] who has built a business out of creating devices that are ready to go without any cloud restriction.
+[1625.04 → 1626.92] And they posted an update in February.
+[1627.80 → 1629.90] And you got a mention in here.
+[1630.06 → 1630.72] He says...
+[1630.72 → 1631.08] Did we?
+[1631.38 → 1632.24] How cool is that?
+[1632.46 → 1632.92] He says,
+[1633.00 → 1635.68] I need to also thank Alex and the self-hosted podcast.
+[1635.92 → 1638.58] I've listened to Jupyter Broadcasting podcast for over seven years.
+[1638.92 → 1642.82] And without our partnership, Cloud free would not have grown nearly as fast as it did.
+[1643.12 → 1646.12] And I got to say, it hit me in the feels because the picture they have in that
+[1646.12 → 1649.68] looks a lot like what we're doing for the Jupyter Garage shipping right now.
+[1650.20 → 1654.84] And I just totally realized, like, I'm learning a lot of the same stuff that they had to learn
+[1654.84 → 1656.68] to do Cloud free right now.
+[1657.14 → 1660.38] And so I felt very like I had a kinship all of a sudden.
+[1660.54 → 1662.86] And I thought that was really great that they had a really...
+[1662.86 → 1663.58] This is a perfect...
+[1663.58 → 1664.68] This is a really positive update.
+[1664.76 → 1667.16] It looks like things are going really well for Cloud free.
+[1667.28 → 1668.68] And that's why we like to mention them.
+[1668.78 → 1670.96] It was an idea that I think needed to happen.
+[1670.96 → 1676.12] And it's a great way to go get devices at a very reasonable price, like outdoor and indoor
+[1676.12 → 1683.88] smart plugs, Zigbee dongles, temperature sensors, motion sensors, Z-Wave buttons, door sensors,
+[1684.00 → 1687.06] all that kind of stuff that you might want to hook up to Home Assistant.
+[1687.30 → 1691.02] But, you know, you don't want to have to bother with the ref lashing yourself or worrying about
+[1691.02 → 1694.08] the required cloud connectivity that they ship with by default.
+[1694.68 → 1695.96] Cloud free just takes care of all that.
+[1696.10 → 1698.90] That's why we like to give them a mention at cloudfree.shop.
+[1698.90 → 1702.48] And when you're over there, don't forget to use the coupon code self-hosted so that
+[1702.48 → 1703.28] they know we sent you.
+[1704.62 → 1706.18] All right, feedback time, I think.
+[1706.40 → 1707.28] Daniel writes in,
+[1707.36 → 1712.90] I'm currently using a Synology 216J with an EXT 4-volume mirrored on two drives.
+[1713.20 → 1718.22] I'm curious about how I might go about upgrading here and prioritize backup ergonomics.
+[1718.64 → 1723.84] Right now, I don't have snapshots, and I'm considering switching to ZFS or Butters.
+[1724.34 → 1724.76] Brackets.
+[1724.98 → 1725.80] Please don't fight.
+[1725.80 → 1731.74] How can I do this without purchasing a huge external hard drive to move everything over
+[1731.74 → 1733.02] whilst I build a new volume?
+[1733.72 → 1739.10] Also, NFS seems kind of antiquated, and I'm wondering if this is the fastest way to mount
+[1739.10 → 1740.28] things over the network.
+[1740.56 → 1741.40] Is there a better option?
+[1741.94 → 1742.14] Hmm.
+[1742.44 → 1743.76] A little NFS hate there, huh?
+[1744.08 → 1745.28] No, I used to think that too.
+[1745.74 → 1748.68] You know, actually, that's sort of the beauty of NFS is that it's so simple.
+[1748.82 → 1750.14] It is extremely efficient.
+[1750.14 → 1753.14] But there are lots of ways to transfer files over the network.
+[1753.62 → 1754.10] It is old.
+[1754.28 → 1759.24] But, you know, one way you could look at old is tested, you know, reliable.
+[1759.74 → 1759.88] Right.
+[1760.14 → 1760.50] Boring.
+[1761.06 → 1762.40] And it's still in production.
+[1762.72 → 1764.28] So this is an interesting question.
+[1764.38 → 1768.24] It's like, I want to do something that's kind of risky, like switch to ZFS or Butters,
+[1768.24 → 1773.54] but I don't want to have to purchase an external hard drive to back everything up to.
+[1773.94 → 1777.08] And there's definitely part of me that's like, that's just not how it works.
+[1777.24 → 1781.06] I just want to say, you know, when you're messing with important data, you do kind of
+[1781.06 → 1787.48] want to externalize it because you can convert an extended four partition in place to Butters.
+[1787.80 → 1789.22] I've done it a couple of times, actually.
+[1789.48 → 1793.52] I was just having a conversation with somebody earlier this morning about just that thing.
+[1793.52 → 1794.98] And it'll work.
+[1795.80 → 1798.48] But I can't tell you it's risk-free.
+[1798.76 → 1799.72] It is absolutely not.
+[1800.60 → 1802.26] And so I don't know how you get around that.
+[1802.32 → 1806.54] Do you have any ideas on maybe like pulling other disks on your LAN or I mean, something
+[1806.54 → 1807.24] out of the box?
+[1807.88 → 1808.28] Not really.
+[1808.64 → 1813.30] I mean, it's it goes back to that whole raid is not a backup type thing.
+[1813.44 → 1819.12] So even if you have a volume mirrored on two drives, unless that data exists somewhere
+[1819.12 → 1823.50] else as well, I would pretty much say that data doesn't actually exist at all.
+[1823.72 → 1827.10] Because if that mirror was to go pop, that data is gone.
+[1827.30 → 1830.18] So this is probably not what you want to hear.
+[1830.66 → 1835.58] But I would buy that external hard drive, mirror everything onto that external hard drive,
+[1835.84 → 1841.78] free up the two drives that you want to put ZFS or Butters onto, and then you should be
+[1841.78 → 1842.24] good to go.
+[1842.76 → 1844.28] That I completely agree with.
+[1844.50 → 1849.72] And now, as an aside, I want to just acknowledge that I do feel like we go about our daily lives
+[1849.72 → 1854.48] totally underutilizing lots of free space on the systems on our LAN.
+[1854.64 → 1858.10] And I know there are a couple of projects out there to crack this nut.
+[1858.16 → 1863.02] But if anybody listening is using something and has been using it for a little bit to take
+[1863.02 → 1867.54] advantage of maybe, you know, a machine over here that's connected via Ethernet that has
+[1867.54 → 1868.76] 120 gigs free.
+[1868.76 → 1871.08] And this machine over here that has a terabyte free.
+[1871.18 → 1874.20] And I have a machine over here that has 500 gigs and a machine over here that has four
+[1874.20 → 1874.98] terabytes free.
+[1875.42 → 1881.40] And I just need temporarily, I just need somewhere to store an extra seven terabytes a day.
+[1881.44 → 1887.30] It's like, could I pool everything somehow together and then somehow trust that this network
+[1887.30 → 1889.34] file system would work?
+[1889.34 → 1893.10] And you could, there are ways you could hack it together, especially with, you know, on
+[1893.10 → 1894.58] Linux with different mount points and all of that.
+[1894.64 → 1897.04] But I just don't, I just don't know of a solid one.
+[1897.16 → 1899.08] So self-hosted. Show slash contact.
+[1899.40 → 1903.98] If anyone out there has something just out of curiosity, just be a fun thought experiment
+[1903.98 → 1905.82] to pool the storage on my network.
+[1906.02 → 1909.28] I don't think I'd use it for anything in production or for backup though.
+[1909.64 → 1910.70] I just don't think I would.
+[1911.30 → 1916.94] The next one comes from Mike, and he's responding to a question I proposed last week about using
+[1916.94 → 1921.74] home assistant automations to cycle the charging of batteries on and off.
+[1921.80 → 1927.06] So that way devices don't sit at a hundred percent charged for days, or they don't stay
+[1927.06 → 1928.20] at zero percent charge.
+[1928.28 → 1931.24] You may be something in the 40 to 60 percent range.
+[1931.50 → 1935.48] It'd be lovely to have an option to say today, I want everything charged to a hundred percent
+[1935.48 → 1938.50] because we're going on a road trip today, and we need everything charged up.
+[1938.70 → 1942.90] And we got a couple ideas suggested, and I liked Mike's and I wanted to give it a read
+[1942.90 → 1943.08] here.
+[1943.12 → 1946.92] He says, since there's really no out of the box solution right now, I'm going to
+[1946.92 → 1951.78] I'm creating a script that scrapes my laptop's battery info, and then we'll publish it to
+[1951.78 → 1956.88] my home assistant's MQTT broker and then home assistant will act on that data to power
+[1956.88 → 1958.84] cycle my laptop's power supply.
+[1959.26 → 1960.10] Keep up the show.
+[1960.22 → 1960.48] Thanks.
+[1960.62 → 1962.48] And Mike, good idea.
+[1962.56 → 1963.66] That's great for the laptops.
+[1963.98 → 1970.28] The impossible nut that I'm trying to crack is like iOS devices, maybe even drone batteries,
+[1970.62 → 1975.40] things that don't even have an OS to scrape from, but you'd almost need like a time-based
+[1975.40 → 1975.86] system.
+[1975.86 → 1978.34] I suppose I'm still chewing on it right now.
+[1978.46 → 1984.86] I just kind of do it manually, and it's not bad, but an example of a system that I probably
+[1984.86 → 1990.68] don't unplug and cycle the battery as frequently as I should are those fire tablets that are
+[1990.68 → 1991.84] plugged in and mounted on the wall.
+[1992.02 → 1995.68] I do power cycle them on occasion, but not regularly.
+[1995.68 → 2000.50] And with the home assistant app on Android, like there is something I could do there, but
+[2000.50 → 2002.46] I'm not looking for onesie those solutions.
+[2002.58 → 2004.86] I'm kind of looking for something that would work for everything.
+[2005.20 → 2010.62] I'm going to plug something that our community started about six months ago called Halcyon,
+[2010.72 → 2012.86] home assistant Linux companion app.
+[2013.24 → 2016.42] And there's a link in the show notes, halcyon.CASA.
+[2016.42 → 2023.86] It's a Rust based application designed to run on Linux systems to present those metrics
+[2023.86 → 2024.56] to home assistant.
+[2025.26 → 2028.14] It's early days, and it needs some love and some works still.
+[2028.30 → 2032.70] But if you're interested in that, check out, there's a dedicated channel in the discord
+[2032.70 → 2033.68] for Halcyon as well.
+[2034.00 → 2035.04] And it's written in Rust.
+[2035.14 → 2035.94] So what more could you want?
+[2036.10 → 2036.78] I love that.
+[2037.24 → 2041.78] Now, Brad writes in, I'm looking into moving off Google photos like everybody else.
+[2041.78 → 2045.22] It seems I've landed on Plex photos as my solution.
+[2045.62 → 2051.66] I have some friends that are also self-hosted, and I've given them WireGuard access and they
+[2051.66 → 2056.94] said I can have a few hundred gigs of storage on their networks for my photos and vice versa.
+[2057.54 → 2061.54] What I'm stuck on though is an encrypted backup method for backups.
+[2061.76 → 2062.96] I've tried Duplicate.
+[2063.24 → 2066.26] I've tried some other backup solutions.
+[2066.54 → 2071.06] I don't really care about how it backs up file changes as the library is growing.
+[2071.06 → 2072.54] I'm not editing the photos.
+[2072.68 → 2074.30] So only incremental is needed.
+[2074.66 → 2078.50] They do need to be encrypted though, because they're going to be on a remote LAN.
+[2079.14 → 2082.52] Now, I haven't done a lot of research on this yet, but do you know of any software that
+[2082.52 → 2088.30] doesn't automate one way backup phone to server, for example, to get the photos off
+[2088.30 → 2092.46] my phone and onto the server where I can delete them off my phone, and they will stay on the
+[2092.46 → 2092.72] server.
+[2093.14 → 2094.48] Looking forward to future episodes.
+[2094.80 → 2095.82] Thanks, Brad.
+[2096.18 → 2097.24] This is a good question.
+[2097.38 → 2099.10] Duplicate is not quite cutting it.
+[2099.10 → 2101.64] And so what do you step up to essentially?
+[2101.88 → 2104.34] And you don't want something probably that's a lot to manage either.
+[2104.66 → 2108.36] Oh, Duplicate has just wound me up over the years.
+[2108.50 → 2113.36] You know, it just silently fails and stuff just breaks and there's no way to monitor it.
+[2113.42 → 2115.36] And you can only configure it through the GUI.
+[2115.72 → 2116.84] It's a great app.
+[2116.94 → 2121.76] It just isn't very reliable, which is not really suitable for a backup system.
+[2122.14 → 2122.30] Yeah.
+[2122.30 → 2127.90] I don't know where the failure process, when my backups failed, when my Google Drive payment
+[2127.90 → 2129.74] expired or switched.
+[2129.98 → 2131.94] I don't know where the failure was exactly.
+[2132.12 → 2134.14] I don't know if there wasn't a notification, but I don't know what.
+[2134.66 → 2135.96] It was ultimately it was my fault.
+[2136.40 → 2141.30] I thought about recommending Borg, which is a really solid backup open source solution.
+[2141.74 → 2143.28] It's pretty space efficient.
+[2143.28 → 2145.94] It gives you good encrypted backups.
+[2146.06 → 2149.62] It supports compression, and it'll use Fuse, too.
+[2149.66 → 2153.70] So you can do kind of creative ways to mount file systems, which could be kind of nice.
+[2154.24 → 2155.58] And it has a pretty large community.
+[2155.74 → 2157.70] You can find it at borgbackup.org.
+[2157.80 → 2159.16] That might be worth looking into.
+[2159.72 → 2160.46] Borg is an alternative.
+[2161.40 → 2162.40] Rustic is another one.
+[2162.46 → 2165.00] We mentioned autocratic and Rustic last episode.
+[2165.32 → 2166.18] That's another one.
+[2166.18 → 2172.44] But for getting the things off your phone, I've just been really happy with the Nextcloud app.
+[2172.70 → 2177.46] It backs up everything off my phone in full quality to my Nextcloud instance.
+[2177.92 → 2180.30] And then from there, I can do with them whatever I want to.
+[2180.76 → 2184.60] That's the one we hear the most often from the audience, too, is the Nextcloud solution.
+[2184.96 → 2189.48] We have gotten a recommendation a couple of times into the show about Photosync as well,
+[2189.54 → 2190.70] which is in the Android Play Store.
+[2190.82 → 2191.72] Photosync, one word.
+[2191.72 → 2198.08] And the nice thing about Photosync is it supports various different kinds of network backup options,
+[2198.18 → 2200.34] even Samba, if you want to go that route.
+[2200.78 → 2203.12] You could just back up your photos over Samba from Android.
+[2203.44 → 2205.22] So I'll put a link to that in the show notes as well.
+[2205.68 → 2208.08] Now, you mentioned in your question about Plex Photos,
+[2208.20 → 2213.84] and this is a terrible time to be adopting Plex Photos as a solution, unfortunately.
+[2214.74 → 2218.60] Plex document on their support pages that as of June 2021,
+[2219.52 → 2221.38] camera upload is going to be discontinued.
+[2221.38 → 2223.00] Womb, womb.
+[2223.08 → 2223.56] Yeah, boy.
+[2223.78 → 2228.22] And I think a lot of us are just getting, we're just getting a little Plex skeptical.
+[2228.96 → 2231.80] We're still Plex hopeful, but we're getting Plex skeptical.
+[2232.20 → 2237.94] And I do have to admit personally that Plex skepticism I'm feeling right now would probably,
+[2238.94 → 2242.08] I'd hesitate from using Plex Photos myself for a back,
+[2242.12 → 2243.86] and I'm not using it because of that reason.
+[2243.86 → 2247.10] Dare I say, Plex are becoming the Google of the self-hosted world,
+[2247.20 → 2253.08] just killing stuff randomly and not focusing on the core products like they should be?
+[2253.20 → 2253.64] I don't know.
+[2253.72 → 2255.06] I guess I feel it's kind of mean.
+[2255.32 → 2262.16] They are such a smaller team that they do have to be a little more conservative about where they spend their time and money,
+[2262.24 → 2268.24] where Google's like this, you know, this just financial monster powerhouse supplied by an endless amount of ad money.
+[2268.24 → 2271.38] So it's like, come on, you know, maybe you could keep this going.
+[2271.74 → 2273.36] Maybe you could invest a little more in Stadia.
+[2273.50 → 2274.84] You know, like right now they're killing Stadia.
+[2275.26 → 2275.98] Drives me crazy.
+[2276.26 → 2278.48] I know it's not a self-hosted thing, but dang it.
+[2278.72 → 2281.74] Well, everybody knew that was going to happen even before it launched.
+[2282.08 → 2282.34] I know.
+[2282.42 → 2284.12] Like, did you see like some big exec just left?
+[2284.18 → 2287.32] Like the top Stadia exec just left Google or something?
+[2287.74 → 2288.12] Oh, really?
+[2288.34 → 2290.20] Yeah, not good, not good.
+[2290.42 → 2294.16] I was a big fan of it, even though I often have no internet when I'm out travelling.
+[2294.34 → 2298.88] I just love the idea of being able to play Stadia on any machine I want, Alex.
+[2299.08 → 2301.82] You know, games on a machine with just a really crappy video card.
+[2301.90 → 2302.42] I don't care.
+[2303.30 → 2304.02] Here are some neat ideas.
+[2304.50 → 2309.06] Well, I'm actually thinking about building my own self-hosted gaming setup here in the studio just using Steam, though.
+[2309.06 → 2312.12] You know, just have it on the LAN and just stream it to the boxes that way.
+[2312.58 → 2316.48] Use Steam, use Parsec, Moonlight, all these different streaming protocols.
+[2316.88 → 2318.08] Lots of different ways to skin that.
+[2318.12 → 2318.40] Turkey.
+[2318.70 → 2322.00] I want to say thanks to our members at self-hosted. Show slash SRE.
+[2322.14 → 2323.58] Become a site reliability expert.
+[2323.74 → 2324.78] Keep the show on the air.
+[2324.88 → 2331.84] And as a thank you, as a special thank you, as a golden thank you, a limited ad feed, just nice, tight production.
+[2332.34 → 2333.66] It's a nice, tight, quicker show.
+[2334.14 → 2334.72] Isn't that great?
+[2334.98 → 2337.46] All the Drew loving, just fewer ads.
+[2337.64 → 2340.10] And you also get extra content.
+[2340.44 → 2341.30] A post show.
+[2341.52 → 2345.66] You get a post show where I'm going to try to propose, Alex, try something new for the summer.
+[2345.88 → 2346.80] We'll see how that goes.
+[2346.80 → 2347.74] Oh, no.
+[2347.82 → 2349.00] How much is this going to cost me?
+[2349.24 → 2350.58] Oh, yes, it will cost you.
+[2351.48 �� 2352.90] Also, thank you to a Cloud Guru.
+[2352.98 → 2354.24] You can find them on social media.
+[2354.36 → 2356.40] They're just slashed a Cloud Guru everywhere.
+[2356.86 → 2357.70] Pretty easy to find them.
+[2357.70 → 2361.48] Self-hosted. Show slash contact is the place to go to get in touch with us.
+[2361.60 → 2364.42] And you can find me on Discord at Alex.
+[2364.78 → 2365.56] I'm over there, too.
+[2365.62 → 2369.28] You can find me at Chris Lass on the Discord or on the Twitter.
+[2369.50 → 2372.32] And the show is on the Twitter, too, at Self Hosted Show.
+[2372.56 → 2373.52] Thanks for listening, everybody.
+[2373.52 → 2376.12] That was self-hosted. Show slash 44.

45： The Future of Home Assistant _summary.txt

@@ -0,0 +1,55 @@
+• Home Assistant's founder Paulus discusses the future of the platform and its expansion plans
+• The ESP home acquisition and its implications on Home Assistant's development
+• Plans for a more accessible and lower-cost successor to the Home Assistant Blue device
+• Integration with popular smart home protocols like Zigbee, Z-Wave, and Matter
+• Future support for running Home Assistant in containers or virtual machines
+• Addressing different user bases, including those who want to run Home Assistant on a server
+• Home Assistant managing entire system with benefits for users
+• Large number of dependencies in requirements.txt over 1,000
+• Using SDKs to translate protocols into Python objects for reusability
+• Docker containers install fresh dependencies, making updates easier
+• User preference for simplicity and convenience, with many using the OS stack
+• Analytics show 65% of users are on the OS stack, including 45,000 opted-in for Home Assistant Analytics
+• Features driven by user feedback and issues, prioritizing ease of use
+• Linode as a cloud service provider offering full control and customization options
+• Features of Linode's platform, including DNS manager, SSL certificates, and single-click application deployment
+• Using Linode for personal projects or large-scale applications
+• Testing hardware configurations with Linode's $100 credit
+• Home Assistant's shift towards turnkey solutions and future plans for the platform
+• ESP Home acquisition and efforts to make local control and privacy-friendly devices accessible
+• Made for Home Assistant program concept and certification process
+• The importance of an open API for integration with other projects
+• Companies' reluctance to partner and expose APIs, citing security concerns
+• The challenges of integrating with companies that have proprietary systems (e.g. Ring, Sonos)
+• The need for a balance between official partnerships and unofficial integrations
+• Home Assistant's goal to make it easier for users to handle the velocity of change
+• New features such as config flow to simplify integration setup through the UI
+• Changes to configuration handling to reduce breaking changes
+• Safe mode as an alternative to fully updating the system
+• Home Assistant and its development process
+• Unraid as a self-hosted server operating system
+• Use cases for Home Assistant and Plex media server
+• Storage capacity and management on LAN (Local Area Network)
+• Maintenance and troubleshooting of self-hosted services
+• Shucking drives: buying a USB hard drive and removing the internal SATA drive to use in other devices
+• Energy monitoring for solar installations: Home Assistant integration with SolarEdge API and potential uses of a Shelly energy monitor
+• Home Assistant's new statistics feature: tracking energy usage, temperature, and other data to generate dashboards and predictions
+• Gamifying energy efficiency: using color-coded light bulbs to encourage children to adjust their behavior based on energy usage
+• Victron Venus system integration with MQTT for van lifers
+• The user has set up a smart home system using Home Assistant and enjoys gamifying energy usage with their family.
+• They mentioned a product called Provado VPN, which is a zero-log VPN service that offers secure and fast connections worldwide.
+• Automations were discussed, specifically the use of YAML versus Node-RED for creating complex automations in Home Assistant.
+• The user expressed enthusiasm for a new Bluetooth spec being developed for ESP Home products and the Home Assistant app.
+• Setting up Home Assistant
+• Acquiring ESP Home and hiring Jesse to work on it full-time
+• Discussion of the company's size (13 employees) and workload
+• The power of open source and how it allows people from all over the world to contribute to Home Assistant
+• Funding model and being self-sustaining without investors or loans
+• Remote access features and potential future changes due to the pandemic
+• Discussion of Nebu Kasa's home assistance system
+• Origin and meaning of the name "Nebu"
+• Mention of a smartwatch called Nabu by Razer
+• Plans to use the name once the trademark lapses
+• Gratitude for software that has improved listener's quality of life
+• Upcoming episode discussing distributed file systems
+• Call for feedback on the topic

45： The Future of Home Assistant _transcript.txt

@@ -0,0 +1,645 @@
+[0.00 --> 3.28]  Well, we've got a special interview for episode 45 today.
+[3.48 --> 5.44]  We're going to have our guest coming up in just a moment.
+[5.50 --> 7.28]  So I want to thank our sponsor, A Cloud Guru.
+[7.52 --> 10.64]  They are the leader in learning for the cloud, Linux, and other modern tech skills.
+[11.04 --> 13.28]  Hundreds of courses and thousands of hands-on labs.
+[13.40 --> 17.74]  Get certified, get hired, get learning at acloudguru.com.
+[18.18 --> 22.22]  So today, instead of a bunch of different segments, we're really kind of just doing one thing.
+[22.50 --> 22.84]  Hey, Alex?
+[23.16 --> 23.68]  We are indeed.
+[23.80 --> 27.26]  Yes, we've got Paulus, who is the founder of Home Assistant, on the episode today.
+[27.26 --> 35.94]  And Chris and I talked to him about all sorts of different subjects, from how Home Assistant is becoming more turnkey ready, through to the ESP home acquisition.
+[36.34 --> 39.72]  And there's a couple of interesting tidbits about the future in there as well.
+[40.76 --> 50.84]  Well, I don't know if you remember, but you and I chatted back in 2017 on a Linux Action Show special about Home Assistant, what feels like 100 years ago now.
+[51.36 --> 52.28]  Yeah, no, I do remember.
+[52.34 --> 54.88]  Well, I remember it was somebody from Jupyter Broadcasting.
+[55.00 --> 55.94]  I didn't realize it was you.
+[55.94 --> 56.42]  Yeah.
+[57.20 --> 59.50]  And man, have things come a long way.
+[59.68 --> 62.52]  So thank you for joining us to catch us up on stuff.
+[63.18 --> 66.80]  I am the happy owner of a Home Assistant Blue device.
+[67.04 --> 67.68]  Love it.
+[67.96 --> 68.20]  Awesome.
+[68.62 --> 72.46]  I put the order in during the live stream, so I got it fairly early.
+[73.22 --> 77.42]  And I got to say, you know, months into it, the performance holds up compared to the Raspberry Pi 4.
+[77.54 --> 79.58]  I think it is outperforming the Raspberry.
+[79.92 --> 81.24]  I mean, it's a beast.
+[81.84 --> 83.68]  The N2 is just like, it's amazing.
+[83.68 --> 87.08]  So are there any plans for more expansions in that direction?
+[87.44 --> 89.74]  Is that going to be a focus going forward?
+[89.78 --> 92.00]  Because it really seems like a pretty sweet integration.
+[92.50 --> 92.68]  Yeah.
+[92.74 --> 94.26]  So there are definitely plans.
+[94.66 --> 96.36]  Nothing to announce just yet.
+[96.80 --> 101.42]  We realized with the N2+, like we only made the case, right?
+[101.46 --> 103.20]  So it's just a board.
+[103.52 --> 110.78]  And when people think of home automation, they obviously think of like Zigbee or Z-Wave or Chip or Matter, whatever it's going to be called.
+[110.78 --> 116.66]  And so that's something that we want to, you know, if we want to address, we want to include that as well.
+[116.74 --> 129.50]  And I think the, you know, the Home Assistant Blue was really like, you know, the ultimate race car, but it was not very accessible in that the price was not, the price was pretty steep for like, you know, a device.
+[129.60 --> 132.10]  And also you needed to add like a Zigbee stick and these kind of things.
+[132.10 --> 147.28]  So I think we are definitely going to look into something as a successor, nothing to announce just yet, but it will also be hopefully lower priced and more capable out of the gate to be like, you know, used for smart home.
+[147.80 --> 147.88]  Yeah.
+[148.06 --> 154.84]  I can absolutely see how that would be way simpler for new users to get into the space as well.
+[154.84 --> 155.24]  Yeah.
+[155.34 --> 162.56]  And I think, you know, when we look at these things, it's not just like, we don't just want to create a box that competes with like Philips Hue or anything, right?
+[162.56 --> 163.80]  Like we're Home Assistant.
+[164.00 --> 169.22]  So it needs to be, you know, kind of hackable, playful, open.
+[169.48 --> 173.22]  Like it just needs, you know, just like the Odoid N2 Plus or the Home Assistant Blue.
+[173.34 --> 175.70]  I mean, you can flash anything on it that you want, right?
+[175.76 --> 182.56]  We wouldn't, we're not interested in like building a lockdown box that like will just keep the users out.
+[182.56 --> 185.82]  Well, that is completely understandable, especially now having used one.
+[185.98 --> 191.56]  But so what about guys like me who will always have a use case where I'm going to want to run it on a server?
+[191.64 --> 194.32]  Like here at the studio, we have a server that's doing like a hundred other things.
+[194.42 --> 199.62]  And so running Home Assistant in a container is perfect for the use cases of just controlling studio lights.
+[199.62 --> 202.32]  And we're not really using any integrations and stuff like that.
+[202.62 --> 204.54]  How do you see that user base being addressed in the future?
+[204.92 --> 207.14]  Right now we have four installation types.
+[207.46 --> 211.08]  We have the Home Assistant operating system.
+[211.08 --> 217.88]  We have the Home Assistant supervised, the Home Assistant container, and then Home Assistant core, which is just like running it in Python yourself.
+[218.26 --> 223.10]  And all the other three installation approaches all rely on containers.
+[223.34 --> 224.80]  And so they all use the same image.
+[225.28 --> 227.60]  So it's like the core technologies are all very similar.
+[227.76 --> 229.22]  Yeah, it's all the same thing, really.
+[229.22 --> 236.92]  The only one that's different is core because you maintain your own Python virtual environment.
+[237.52 --> 238.92]  The other three are all Docker based.
+[239.02 --> 240.02]  So it's all the same thing.
+[240.54 --> 243.82]  So those four installation types are pretty much set in stone right now.
+[243.94 --> 252.28]  I think that if you, in your studio, you can either run the container or you can run a virtual machine with Home Assistant operating system.
+[252.28 --> 257.44]  You know, the benefit, of course, of the virtual machine is that you have one-click updates of Home Assistant.
+[257.96 --> 266.80]  Well, with the container, it really depends on like your container management software, which can be Unraid or Portainer or Synology or whatever.
+[267.28 --> 270.72]  You know, that software then has to do the update of the container.
+[271.14 --> 272.58]  I think that's the only real difference.
+[272.58 --> 276.38]  In the end, all of these containers, they're all run Alpine.
+[276.74 --> 278.50]  They run Python.
+[278.64 --> 279.80]  And we maintain that, right?
+[279.82 --> 282.54]  So we have a big wheel server.
+[282.76 --> 287.44]  We make sure that all the dependencies work and compiled and are just up to date and running.
+[287.90 --> 290.54]  And that's just, you know, a big benefit as a user.
+[290.66 --> 294.22]  And I think that moving forward, you just want to run Home Assistant container?
+[294.70 --> 295.74]  That will be possible.
+[296.26 --> 296.48]  I see.
+[296.56 --> 302.56]  So it's not like it's ever going to go away, but you just feel like there's a lot of benefits to Home Assistant managing the entire system.
+[302.58 --> 305.02]  Because of all of the interdependencies.
+[305.40 --> 305.52]  Yeah.
+[305.58 --> 307.20]  I mean, there's just so many moving parts.
+[307.38 --> 314.26]  I think that if you look at our requirements.txt, which is where we define like the Python dependencies, it's like over a thousand.
+[314.78 --> 314.92]  Right?
+[314.94 --> 319.62]  Because each integration comes with its own Python library, which is a requirement we made ourselves.
+[319.76 --> 322.78]  So it's obviously like, you know, our own guidelines.
+[322.96 --> 328.18]  But, you know, the reason we always do this is that we want integrations to rely on like an SDK.
+[328.28 --> 332.08]  So an SDK is a Python package of the standalone that translates.
+[332.58 --> 334.80]  The protocol into like Python objects.
+[335.08 --> 338.98]  And that way, other Python projects, not just Home Assistant, can also use this package.
+[339.14 --> 339.28]  Right?
+[339.34 --> 342.72]  So we don't want protocol-specific information inside Home Assistant.
+[343.22 --> 350.00]  Because we want to make sure that other Python-based home automation systems or just one-off scripts can use these protocols as well.
+[350.00 --> 350.44]  Wow.
+[350.44 --> 350.56]  Wow.
+[350.74 --> 355.56]  So it kind of sounds like to me what you guys did as a team is you looked at the kind of, if you will, the whole problem.
+[355.56 --> 367.00]  And you said, quite frankly, it is easier for us as a team to just do a whole OS than say, you must have considered, well, bless Ubuntu LTS as the supported Home Assistant platform.
+[367.00 --> 368.76]  And anything else is DIY.
+[369.08 --> 372.20]  But if you want our official way or our official image, it's all Ubuntu-based.
+[372.38 --> 372.58]  Yeah.
+[372.68 --> 380.96]  But the problem with that is that your virtual environment that runs Python is going to be, has to be maintained as well.
+[381.02 --> 383.12]  So, I mean, this is, of course, how Home Assistant started.
+[383.22 --> 386.08]  It was just a Python application that we distributed through PyPI.
+[386.50 --> 386.68]  Sure.
+[386.68 --> 390.00]  And people would run into, like, they would do pip upgrades.
+[390.30 --> 393.34]  And then, of course, some people will upgrade from the last release.
+[393.46 --> 395.84]  Some people will update from, like, six releases ago.
+[395.98 --> 398.32]  And people got stuck all the time.
+[398.42 --> 404.32]  And the way it works with our Docker containers is that we install all the Python dependencies fresh in each container.
+[405.26 --> 410.16]  And so when you update your container, all your dependencies are thrown away.
+[410.16 --> 414.56]  We make sure you have the latest and greatest dependencies all work together.
+[414.56 --> 417.82]  And that way it just works.
+[418.16 --> 418.74]  Yeah, that makes sense.
+[419.06 --> 423.64]  I can see how that also is just much more manageable and supportable by you guys as well.
+[423.80 --> 426.68]  And I got to say, you know, on the blue, it's working really great.
+[426.80 --> 431.14]  I kind of am, I'm a user of both use cases, just the core version and the whole OS stack.
+[431.42 --> 434.32]  And I do really like the snapshots.
+[434.46 --> 439.82]  I feel like the more recent updates that have also set it so you can have a snapshot right before you upgrade is brilliant.
+[439.96 --> 441.72]  All that kind of stuff just keeps getting better.
+[441.72 --> 445.50]  Yeah, and I think, you know, the features are really driven.
+[446.20 --> 448.40]  You know, we look at the way people use Home Assistant.
+[448.70 --> 452.76]  And we look at the issues we see on our forums and on our Discord.
+[453.08 --> 456.00]  And then we just ask ourselves, like, why is this?
+[456.12 --> 458.44]  What can we do to make it easier and better?
+[458.64 --> 461.88]  And we just constantly try to, like, kind of tackle this.
+[461.88 --> 471.52]  And, you know, we're really focused on making Home Assistant easier to use while still also, you know, making sure that our power users, of course, can do their things.
+[472.16 --> 474.76]  And, you know, it's been really paying off.
+[474.80 --> 479.40]  I think that, like, we launched Home Assistant Analytics, like, a month ago, two months ago already.
+[479.40 --> 479.72]  Right?
+[480.40 --> 484.82]  And I think, like, around, we didn't do much promo, but, like, 45,000 people have opted in.
+[485.20 --> 488.70]  And you can actually see our operating system is, like, 65% of our users.
+[488.92 --> 489.38]  Oh, okay.
+[489.76 --> 491.60]  I mean, that was pretty unexpected.
+[492.08 --> 493.86]  Like, we knew it was high.
+[494.02 --> 497.82]  I think, you know, internally we were like, ah, that's probably, like, 50%.
+[497.82 --> 499.48]  But it's actually 65%.
+[499.48 --> 503.26]  And I also understand it because it's just convenience, right?
+[503.26 --> 507.96]  Like, if you want to be a system administrator at home, you can be, of course.
+[508.04 --> 511.64]  But if you want to be, like, automating your home, you can be that, too.
+[513.26 --> 515.16]  Linode.com slash SSH.
+[515.22 --> 518.08]  Go there to get $100 in 60-day credit on your new account.
+[518.22 --> 520.68]  And you support the self-hosted podcast.
+[521.22 --> 522.80]  Linode is my playground to learn.
+[522.90 --> 524.84]  And it can be yours, too, without a $100 credit.
+[525.12 --> 528.80]  And, sure, maybe ultimately you decide to self-host something on your LAN.
+[528.80 --> 538.90]  But every now and then, and that's more and more these days, there's a job that's really perfect out in the cloud on a service provider you can trust and you have full control.
+[539.24 --> 545.58]  That's one of the things I like about Linode is, unlike entry-level hosting services, they don't try to lock you into their platform with gimmicks.
+[546.00 --> 549.94]  Linode gives you full back-end access to customize and control your server to fit your needs.
+[550.18 --> 553.32]  And their DNS manager allows you to easily switch your domain to your new server.
+[553.32 --> 560.08]  You can manage SSL certificates with Breeze and deploy applications with a single click or build the server up from scratch if you want.
+[560.30 --> 566.22]  If you need a simple personal server for a blog or portfolio or maybe a game server, in fact, they make that really straightforward,
+[566.62 --> 570.02]  or maybe you want to set yourself up a NextCloud server and sync your own files.
+[570.10 --> 573.94]  Whatever the scale of your task or your business or even when your app goes viral,
+[574.54 --> 577.74]  Linode is going to reliably serve to millions of users.
+[577.84 --> 581.98]  It can be just you and your friends and family or it can be millions of users.
+[581.98 --> 584.66]  And we've really put it to the test here at Jupyter Broadcasting.
+[584.86 --> 588.70]  And like I say, it really is a fantastic playground to learn as well.
+[588.96 --> 593.26]  And that $100 credit means you can play around with all kinds of different hardware and configuration stacks,
+[593.42 --> 595.26]  which has been a massive advantage for me.
+[595.70 --> 600.20]  Before I deploy something in production, I'll sometimes spin up a couple of versions of it on different stacks.
+[600.52 --> 602.62]  You know, maybe this one's on Nginx and this one's on Apache.
+[602.78 --> 603.62]  Maybe this one's on Ubuntu.
+[603.76 --> 604.80]  Maybe this one's on CentOS.
+[605.12 --> 606.60]  I'll try them out and test them right there.
+[606.86 --> 608.52]  And then I'll just keep the winner and destroy the others.
+[608.52 --> 614.28]  That kind of flexibility and not having to mess around with some slow VM software on my laptop to test that stuff out.
+[614.72 --> 615.44]  Well, it's just brilliant.
+[615.74 --> 619.00]  And then, of course, there's the perk as a listener of supporting this here podcast, too.
+[619.22 --> 622.84]  And we use their S3 compatible object storage as the back end storage for our next cloud,
+[622.98 --> 625.76]  which means we're not constantly managing disk space all the time.
+[626.02 --> 628.92]  They've really got this stuff dialed in because they've been doing it since 2003.
+[629.16 --> 630.26]  So I want you to go try it.
+[630.66 --> 632.88]  So go to linode.com slash SSH.
+[632.98 --> 636.00]  Go there, get that $100 in credit and support the show.
+[636.40 --> 637.52]  Linode.com slash SSH.
+[637.52 --> 644.74]  Yes, I mean, Home Assistant's been headed down the more turnkey route for quite a while now.
+[645.26 --> 648.92]  And I think HASSOS is, or am I calling it the right thing?
+[649.04 --> 650.76]  I'm still confused by the name change.
+[651.76 --> 655.10]  It's been headed down the turnkey route for quite a while.
+[655.90 --> 657.76]  What else do you have planned in that space?
+[657.84 --> 660.36]  I mean, there's been a lot of work around automations recently,
+[660.36 --> 664.32]  as well as some other aspects of the experience.
+[664.32 --> 668.30]  So I think that our goal really, like in the longer term,
+[668.34 --> 674.88]  is that we want to make sure that a lot of people have access to having like great home automation at home
+[674.88 --> 677.72]  that, you know, focuses on local control and privacy.
+[677.94 --> 681.44]  And so having Home Assistant be accessible is important to us.
+[681.50 --> 685.86]  But for example, we've also, you know, the company behind Home Assistant,
+[685.86 --> 689.08]  my company, Nabucasa, we've also recently acquired ESP Home.
+[689.82 --> 694.20]  ESP Home is a firmware for ESP devices that runs on a,
+[694.58 --> 698.50]  which is a firmware that can run on a lot of products that come from China,
+[698.66 --> 700.82]  like light switches, lights.
+[700.82 --> 705.38]  And with ESP Home, we are also trying to make it easier for people to get,
+[705.64 --> 711.52]  you know, access to devices that work locally and work private and work with Home Assistant.
+[712.52 --> 716.24]  So yeah, our long-term goal is really just to make it accessible to everybody.
+[716.38 --> 720.82]  And I think that launching hardware was a really obvious step.
+[721.08 --> 725.68]  I feel that for a long time, I didn't want to go down that route because logistics,
+[726.00 --> 727.50]  just like all that stuff.
+[727.50 --> 731.04]  But at the end of the day, we were looking at it and we were like,
+[731.32 --> 733.76]  we've been working on making it so much easier to use.
+[734.04 --> 737.78]  But then the first step of instructions is download Etcher,
+[737.98 --> 740.18]  download this image and flash it to an SD card.
+[740.42 --> 742.36]  And most people don't even know those words.
+[743.06 --> 743.74]  Yeah, it's true.
+[744.16 --> 747.48]  That has me thinking about something like, you know, the Made for iPhone program?
+[747.74 --> 747.92]  Yeah.
+[748.06 --> 752.32]  Makes me think with ESP Home in particular, I know it's aimed primarily at hackers
+[752.32 --> 756.60]  and people that want to build and make and solder and all that kind of stuff.
+[756.60 --> 759.04]  But it's got me thinking, it's acquisition of ESP Home.
+[759.16 --> 761.36]  Why isn't there a Made for Home Assistant program?
+[761.78 --> 769.26]  Well, I think that the main thing about Made for Home Assistant is that we don't have an API ourselves,
+[769.62 --> 769.78]  right?
+[769.80 --> 771.66]  Like we always integrate with the other products.
+[772.08 --> 778.42]  I did consider like starting one or like having like at least some certification and more official certification.
+[778.42 --> 786.66]  But we see that there's not much interest in it in a way that like, you know, manufacturers will come to us and be like,
+[786.96 --> 787.66]  well, what's your API?
+[787.80 --> 788.30]  We'll integrate.
+[788.90 --> 790.84]  And I'm always like, no, that's not what we want.
+[790.90 --> 792.72]  We want you to create an open API.
+[793.02 --> 794.14]  We will integrate with it.
+[794.14 --> 797.62]  But other projects should also be able to allow to be integrated with it.
+[798.08 --> 801.02]  And then we see a lot of companies be like, ah, that's not in our interest.
+[801.38 --> 808.46]  Or, you know, we were talking to Ring because, you know, they wanted to say like, hey, can we get like a partnership going?
+[808.92 --> 809.90]  And then we looked at it.
+[810.02 --> 814.00]  And the first step is sign NDA to make sure that you don't expose the APIs.
+[814.20 --> 814.46]  Right.
+[814.46 --> 815.88]  And like, we're open source.
+[816.02 --> 816.96]  This is not going to happen.
+[817.06 --> 822.64]  And the same thing happened to us with Sonos, who also was like, yeah, we want to keep it to partners only.
+[823.10 --> 825.08]  It's like, ah, okay, that doesn't work.
+[825.42 --> 827.46]  Oh, that's super frustrating to hear that kind of stuff.
+[827.52 --> 833.32]  Because some of those companies you listed, you know, Ring and Sonos, they're big players in this space.
+[833.34 --> 839.16]  And that's kind of frustrating to hear that they're not compatible with an open source ethos yet.
+[839.50 --> 840.76]  Well, their partnerships are not.
+[840.88 --> 842.38]  But I mean, we still integrate with them.
+[842.48 --> 842.68]  Right.
+[842.68 --> 842.92]  Right.
+[842.92 --> 848.64]  It's just less official because they still have APIs and people have been able to figure out those APIs.
+[849.54 --> 851.30]  And so we will still integrate with them.
+[851.60 --> 856.98]  It's just, if you are a partner, they will make sure it stays working or they will give you a heads up so you can adjust.
+[857.74 --> 859.00]  And that's something we don't have.
+[859.06 --> 859.24]  Right.
+[859.28 --> 861.28]  So we sometimes get caught off guard.
+[861.40 --> 863.98]  Like some, some brand will change an API.
+[864.64 --> 865.70]  Home Assistant stops working.
+[866.26 --> 869.10]  We have to update our code, ship a hotfix, and it will work again.
+[869.10 --> 872.78]  Which leads me nicely into my next question, which is about the velocity of change.
+[872.78 --> 875.92]  Now, I've been using Home Assistant for a couple of years myself.
+[875.92 --> 879.58]  So I've been through quite a few breaking config changes over that time.
+[880.32 --> 888.42]  I feel like, and this is just anecdotal personal experience, that that experience has gotten better, that the pace of change hasn't decreased.
+[888.42 --> 894.94]  But the amount of changes that break stuff, that has decreased significantly from my perspective.
+[894.94 --> 904.56]  What things are you doing from, you know, a Home Assistant side to make that velocity of change more easy for people to handle?
+[904.56 --> 912.10]  So the biggest change there, and it was actually, it started out with a policy change and then like it resulted also in code changes.
+[912.28 --> 913.88]  But so there's this thing called config flow.
+[914.04 --> 916.30]  So through the UI, you can set up an integration.
+[917.08 --> 921.34]  And what we said is that this is going to be mandatory moving forward.
+[921.54 --> 928.98]  So it used to be that you could like go into YAML and then, for example, let's say for your Philips U bridge, you would say this is the IP address.
+[928.98 --> 935.68]  And then, well, Philips U is maybe a bad example because you would still have to press a button in the UI and it was storing some extra data.
+[935.84 --> 940.90]  But for some things, you have to like, here's a username, password, and IP address of a device on my network.
+[941.34 --> 945.30]  But then when the IP address would change, Home Assistant wouldn't work.
+[945.42 --> 952.16]  And Home Assistant couldn't find the new IP address because you had it hardcoded in your configuration files and we're not changing your configuration files.
+[952.86 --> 957.08]  And so those cases, we really had to handle through a UI.
+[957.08 --> 960.94]  We had to like say, hey, this is a temporary IP address, but we still have an identifier.
+[961.36 --> 967.64]  So if your Chromecast changes IP address, we can still find it and we will set it up again or your Shelly or whatever you have.
+[968.36 --> 980.30]  And then we realized that, oh, actually, a lot of our breaking changes is because people are adding support to having to go from one device, support multiple devices or these kind of things.
+[980.42 --> 985.74]  And so when we go for a config flow, Home Assistant is responsible for how it is written to disk.
+[985.74 --> 988.28]  So Home Assistant knows exactly the configuration format.
+[989.06 --> 996.62]  And if we have to change it because we are going to support multiple devices, we can actually migrate that data because we own how it is stored.
+[997.30 --> 1004.92]  If it is a configuration file, and this is kind of silly, but we kind of programmed our way into like a corner we can't get out of.
+[1004.92 --> 1011.34]  Because if you look at configuration.yaml, we have all these advanced structures to break up your configuration files.
+[1011.46 --> 1016.34]  There's packages with includes and then include their name, include their list.
+[1016.50 --> 1018.36]  And there's all these different types.
+[1018.52 --> 1026.24]  And what that means is that Home Assistant cannot go update your configuration file anymore because it doesn't know where your configuration file is.
+[1026.24 --> 1029.36]  We would have to reverse track all your includes.
+[1029.54 --> 1036.08]  And then we need to find like a YAML writer that respects your comments and respects your indentations exactly how it was.
+[1036.72 --> 1038.32]  And it's just, it's impossible.
+[1038.92 --> 1040.80]  I think safe mode was a really good invention.
+[1041.16 --> 1043.02]  That, well, not invention, idea, right?
+[1043.08 --> 1047.06]  Where Home Assistant still starts and then just goes back to a safe mode.
+[1047.50 --> 1047.68]  Yeah.
+[1047.80 --> 1051.44]  So safe mode was really driven by the blue, right?
+[1051.44 --> 1055.72]  So we had the blue in mind and we were like, okay, we're going to have a box.
+[1055.82 --> 1056.76]  We're going to sell these people.
+[1056.98 --> 1061.60]  Like it will actually allow more people to use Home Assistant than previously were not using Home Assistant.
+[1061.80 --> 1066.02]  So how can we make sure that they can always boot and always have a UI?
+[1067.16 --> 1072.76]  That shows you just how long it takes to develop a product because they were released a long time apart, those two things.
+[1072.90 --> 1073.66]  Oh, yeah, yeah, yeah.
+[1073.66 --> 1076.42]  I mean, it took us a year to make that case for the blue.
+[1076.42 --> 1084.64]  So it's, I mean, a pandemic happened and like with other stuff, but yeah, it took us a year all in all to just get a case.
+[1084.96 --> 1088.22]  So I hope our next product will not take that long.
+[1088.56 --> 1090.18]  At least, I mean, we'll see.
+[1090.36 --> 1090.70]  But yeah.
+[1092.42 --> 1093.72]  Yeah, it is very tricky.
+[1093.86 --> 1094.06]  It is.
+[1094.42 --> 1101.92]  It's fascinating, though, how thinking about from a developer perspective, how to ship something for an end user, we got a feature like that.
+[1102.00 --> 1104.72]  I think that's kind of telling how created that use case.
+[1104.72 --> 1107.32]  So I'm curious, let's shift gears to the personal side.
+[1108.00 --> 1111.02]  If you do have some self-hosted services, what are you running on your LAN?
+[1111.54 --> 1115.72]  And roughly how much storage do you have on this set, quote unquote, LAN?
+[1115.90 --> 1125.50]  So I run Unraid at home and I made a server that must have been like six, seven, eight years ago or something.
+[1125.84 --> 1127.22]  Like now it's six years.
+[1127.30 --> 1128.32]  It's getting really old.
+[1128.36 --> 1129.94]  It's like a core i5 still.
+[1130.02 --> 1133.46]  And I think it takes up way too much power compared to what it does.
+[1134.72 --> 1139.88]  You know, I chose Unraid because this was during the beta phase of Unraid.
+[1140.02 --> 1141.74]  So beta phase of Unraid 5.
+[1142.24 --> 1144.96]  And Unraid 5 was where they introduced the Docker containers.
+[1146.14 --> 1152.54]  So that was like almost kind of right away, I kind of shifted into like this perfect world of having all these containers at home.
+[1152.60 --> 1156.80]  And so I'm actually still the maintainer of the Home Assistant core template for Unraid.
+[1157.02 --> 1157.46]  Love that.
+[1157.46 --> 1162.44]  So that's how I used to run Home Assistant for a long time.
+[1162.54 --> 1164.28]  I was like, I just have my container at home.
+[1165.24 --> 1168.90]  And then I have like, I have Plex running and some other stuff.
+[1169.22 --> 1171.90]  And then you had to go and make it a whole OS.
+[1172.06 --> 1172.34]  No, I'm kidding.
+[1172.52 --> 1172.60]  Yeah.
+[1173.38 --> 1174.72]  I hear Plex in there.
+[1174.82 --> 1175.18]  Interesting.
+[1175.50 --> 1176.30]  What's that setup like?
+[1176.30 --> 1184.40]  I mean, so I mainly use Plex because a bunch of the, so I'm in the, I'm from the Netherlands, but I live in the United States.
+[1184.40 --> 1188.08]  And there's a bunch of content from the Netherlands that is geo blocked.
+[1188.08 --> 1190.34]  And so I cannot access it in the United States.
+[1190.58 --> 1190.84]  Yeah.
+[1190.98 --> 1194.76]  So I have to jump on a VPN and download either stuff on YouTube or whatever.
+[1194.76 --> 1198.92]  And then I also don't want my son to be on YouTube, like unsupervised.
+[1198.92 --> 1205.72]  So that's also why I pull in some videos and then I'll just have a Plex account for my son and he can kind of just browse through it.
+[1206.06 --> 1207.46]  I do that same thing for my kids.
+[1207.66 --> 1207.84]  Yep.
+[1207.92 --> 1208.30]  Exactly.
+[1208.36 --> 1209.60]  It's a great use case for Plex.
+[1209.92 --> 1210.06]  Yeah.
+[1210.14 --> 1212.82]  Well, that's, and then how much storage roughly would you estimate?
+[1213.66 --> 1216.14]  I think it's like eight terabyte.
+[1216.14 --> 1222.06]  I just got some smart errors the other day, two months ago, some CRC smart check error.
+[1222.36 --> 1225.78]  So I just, but then, I mean, with Unraid, you have this parity disk.
+[1225.78 --> 1229.98]  Your parity disk needs to be the same size or bigger than your biggest disk.
+[1230.06 --> 1232.12]  And so my biggest disks were like four terabytes.
+[1232.30 --> 1235.62]  And so I was like, wow, I should really update to like eight terabyte disks.
+[1235.74 --> 1238.38]  And so I only updated my parity disk now.
+[1238.52 --> 1240.62]  And that took like more than a week, right?
+[1240.62 --> 1243.30]  Because you have to like pre-clear it and all that stuff.
+[1243.60 --> 1243.72]  Yeah.
+[1245.08 --> 1248.28]  And then I have, I still have one disk that is like on Riser FS.
+[1248.48 --> 1251.38]  And I think they stopped using Riser FS and they're using something else.
+[1251.38 --> 1253.72]  And I was looking into, should I migrate this?
+[1253.72 --> 1257.12]  And then I was like, no, this is just like, no, it's too much.
+[1257.52 --> 1258.50]  It still kind of works.
+[1258.62 --> 1261.20]  And so I actually only updated the parity disk.
+[1262.02 --> 1268.42]  And then I've, the old parity disk I installed now as in my rate, because there's only a couple of errors.
+[1268.42 --> 1271.36]  And then I read online that like, ah, it's okay if you have a couple of errors.
+[1271.62 --> 1274.16]  And that was, that was already after I did my whole process.
+[1274.36 --> 1275.10]  But of course, I mean.
+[1275.42 --> 1276.96]  That just means it's time to start shopping.
+[1277.46 --> 1277.74]  Yeah.
+[1278.08 --> 1278.48]  Exactly.
+[1278.82 --> 1279.20]  Yes.
+[1279.20 --> 1281.86]  I'm waiting for some like deals, right?
+[1281.94 --> 1284.10]  Because I, those disks are expensive.
+[1284.36 --> 1288.12]  I was like, I use the Western Digital Red, I think.
+[1288.42 --> 1290.30]  Are you familiar with shucking drives?
+[1290.44 --> 1292.02]  Is that of any interest to you?
+[1292.46 --> 1292.98]  What is that?
+[1293.52 --> 1298.54]  So you buy, you buy a USB hard drive from Amazon or Best Buy or something.
+[1298.68 --> 1300.36]  This is Alex's favorite thing to do.
+[1301.56 --> 1302.34]  I'll show you.
+[1302.40 --> 1303.46]  I've literally got one over here.
+[1303.46 --> 1305.62]  It's just like it sounds.
+[1305.74 --> 1308.82]  You grab the disk off Amazon and you shuck it out of the case.
+[1309.22 --> 1314.80]  I paid for this Iron Wolf NAS Pro $170 for a 10 terabyte drive.
+[1314.94 --> 1315.32]  Oh, wow.
+[1315.52 --> 1320.80]  And all I had to do to get this was buy a USB enclosure drive and pop it out the USB enclosure.
+[1320.94 --> 1322.46]  It took five minutes.
+[1323.14 --> 1325.38]  And it's a, it's a normal SATA drive.
+[1325.50 --> 1328.20]  There's nothing special about it once you get it out of the case.
+[1328.20 --> 1333.34]  If you look just on eBay, just for this drive on its own, I could sell this thing for $350.
+[1333.76 --> 1334.88]  In fact, why don't I do that?
+[1335.94 --> 1336.46]  There you go.
+[1336.60 --> 1338.08]  You got to pay for that solar setup somehow.
+[1340.68 --> 1341.04]  Yeah.
+[1341.14 --> 1342.84]  So the shucking technique is Alex's favorite.
+[1342.96 --> 1347.26]  Sometimes it requires a little more work than that, but it is a great way to get drives at a great price.
+[1347.58 --> 1348.80]  Oh, that's a good, a good tip.
+[1349.52 --> 1351.94]  Hey, I really talk about solar, Alex.
+[1352.14 --> 1352.40]  Yeah.
+[1352.64 --> 1356.28]  We're actually working or we have an intern at Home Assistant.
+[1356.28 --> 1362.10]  And, well, he actually, he's an intern at Nabokasa, but he's working on Home Assistant stuff.
+[1362.16 --> 1365.78]  And his focus right now is create a solution.
+[1366.04 --> 1372.98]  How do we get, use Home Assistant to give the user insight into their energy usage and allow optimizing it?
+[1373.62 --> 1380.26]  So, of course, Home Assistant has been very, always very focused on home control, home automation.
+[1380.26 --> 1381.58]  And it's been like our strength.
+[1382.20 --> 1384.38]  History has not been our strength that much, right?
+[1384.38 --> 1388.38]  Like our database has been clunky and it's pretty shitty.
+[1389.46 --> 1392.74]  So, I mean, we're actually changing this right now.
+[1392.82 --> 1395.22]  So in the next release, it's going to be what we call statistics.
+[1395.80 --> 1397.96]  And it's going to be a new table in our database.
+[1398.42 --> 1400.88]  And it will take like a snapshot every hour.
+[1401.06 --> 1403.96]  It will analyze like certain entities that you have.
+[1404.22 --> 1405.96]  Right now it's temperature and energy.
+[1405.96 --> 1410.50]  We calculate the min, the max, the mean, the sum, all that stuff.
+[1410.50 --> 1423.52]  And then the goal is to get like, start generating dashboards on your energy usage and to show like predictions and show, you know, comparing like current period, current week to last week, these kind of things.
+[1423.52 --> 1430.46]  Now that second part is not going to be in the next release, but we're already going to start generating statistics in the next release.
+[1430.46 --> 1431.46]  Sounds fantastic.
+[1431.68 --> 1437.18]  And I'll tell you, the solar company that's doing my install, it's a local one in North Carolina.
+[1437.52 --> 1442.22]  They want to charge me $800 for energy monitoring.
+[1442.66 --> 1447.68]  So I'm using the, I think SolarEdge is the manufacturer of the panels.
+[1447.68 --> 1454.66]  And they have a cloud API, which Home Assistant can poll every 15 minutes, I think, to get the data.
+[1454.82 --> 1457.20]  But I'm like, it's in my house.
+[1457.20 --> 1459.62]  Why do you need to go to the cloud to get this stuff?
+[1459.92 --> 1464.04]  So I'm thinking I might get one of these Shelly energy monitors.
+[1464.20 --> 1468.36]  And then, you know, with everything you've just said, I think I might be in business.
+[1468.60 --> 1468.96]  No kidding.
+[1469.42 --> 1469.68]  Right.
+[1470.16 --> 1473.22]  You know, Paul, I know too, I got to speak up for the van lifers out there.
+[1473.22 --> 1476.96]  The Victron Venus system speaks MQTT.
+[1477.64 --> 1483.00]  And so I know there's guys out there that are pulling that information into their Home Assistant setup as well.
+[1483.28 --> 1483.40]  Yeah.
+[1483.48 --> 1490.78]  And so we've really been looking at, or we have, I don't know if you, we tweeted it from the class, tweeted it like two weeks ago, I think.
+[1490.96 --> 1494.18]  But he has already, has a lot of paper mockups and he's been like playing.
+[1494.32 --> 1496.76]  I think he has interviewed like 20 different people.
+[1497.12 --> 1501.20]  And he's been really focusing on, can we kind of gamify it?
+[1501.20 --> 1509.52]  Where like, for example, if you know your yesterday's usage and we show your today's usage, can we tell you like, hey, tone it down a little?
+[1509.66 --> 1512.76]  Because otherwise you're going to use more than like yesterday.
+[1513.34 --> 1514.36]  I've actually had an idea.
+[1514.86 --> 1517.84]  A friend of mine, I've just had my first kid, by the way.
+[1517.84 --> 1523.48]  A friend of mine was telling me they were doing that automating nap time, a light in the nursery with Home Assistant.
+[1524.30 --> 1528.08]  You know, certain times if the light bulb's green, then the kids are allowed out of the room.
+[1528.12 --> 1529.08]  And if it's red, they're not.
+[1529.44 --> 1532.94]  I'm thinking we could play games with colored light bulbs and children at this point.
+[1533.06 --> 1534.38]  That's where my brain's going.
+[1534.90 --> 1535.34]  Oh, I do it.
+[1535.42 --> 1535.78]  I do it.
+[1535.84 --> 1539.28]  That's, you know, I train my kids with a series of light changes at night for bedtime.
+[1539.28 --> 1541.86]  And then noisemakers come on throughout the rig.
+[1542.34 --> 1542.96]  It's real.
+[1543.36 --> 1543.94]  It's brilliant.
+[1543.94 --> 1545.60]  I can't wait to play with that.
+[1545.68 --> 1549.94]  And gamifying, it feels like that's an idea that could be applied to a lot of things.
+[1550.40 --> 1562.04]  As somebody who uses Home Assistant to manage an off-grid setup, I would love something around energy history and a gamification system that would encourage the family to maybe conserve energy.
+[1562.04 --> 1570.64]  Because one of the things I did that really encouraged family adoption was we got a fire tablet and we just put Home Assistant up on it all the time.
+[1570.64 --> 1574.26]  It's on the wall and it's always there so the kids can see what's going on.
+[1574.32 --> 1577.58]  And once I did that, it like it clicked for everybody.
+[1577.70 --> 1582.66]  So to get something up on that screen would, man, they just take my off-grid game to like the next level.
+[1583.42 --> 1587.50]  Yeah, I think honestly, just getting people inside in it is like step one.
+[1587.58 --> 1593.76]  Then all of a sudden they start to realize it's like, oh, I can actually, you know, we can generate more energy than we used today.
+[1593.88 --> 1594.72]  Let's go for it.
+[1594.98 --> 1595.16]  Right.
+[1595.20 --> 1596.34]  I think that's going to be fun.
+[1596.34 --> 1600.18]  So my last question, I think, before we let you go is about automations.
+[1600.60 --> 1604.36]  This kind of goes back to the turnkey aspect, I suppose, and simplification.
+[1604.78 --> 1611.60]  There's been a lot of work around making the YAML automation interface built into Home Assistant easier.
+[1612.40 --> 1616.80]  But I always find myself for the more complex things reaching for Node-RED.
+[1616.94 --> 1621.04]  And I wondered how you felt about people like me doing that.
+[1621.28 --> 1624.68]  Do you want us to all be using YAML all the time or do you not really care?
+[1625.06 --> 1625.84]  I don't really care.
+[1625.84 --> 1641.34]  In fact, I think it's great that our APIs are so generous that you can get anything out, that you can actually build Node-RED and do a full automation engine without being part of the Home Assistant integrations.
+[1641.74 --> 1644.32]  And I think that, you know, each has their own.
+[1644.40 --> 1649.50]  And I think because Node-RED exists, we don't have to make a lot of things ourselves, right?
+[1649.50 --> 1654.10]  A lot of feature requests that would normally come to us are now, ah, I will just use Node-RED.
+[1654.10 --> 1656.66]  And I just saw a pull request.
+[1656.66 --> 1667.60]  I mean, I guess it's been like one and a half months ago from the maintainer of the Node-RED Home Assistant integration who makes like the nodes for Node-RED.
+[1668.00 --> 1674.34]  And I think he's been working on getting the triggers from the Home Assistant Animation YAML into Node-RED as well.
+[1674.34 --> 1678.28]  So we have a lot of triggers that are not very accessible yet.
+[1678.80 --> 1681.82]  A lot of advanced triggers that are not accessible in Node-RED yet.
+[1682.48 --> 1690.58]  But that would allow Node-RED to use anything that a normal YAML automation can would be possible inside Node-RED, which I think is really cool.
+[1690.58 --> 1695.88]  Because all of a sudden it makes Node-RED a lot more powerful or any other automation engine.
+[1696.78 --> 1703.34]  And, you know, in the end, one way or the other, if you have like local control, local data, we succeed.
+[1704.06 --> 1704.72]  Yeah, I totally agree.
+[1704.72 --> 1709.34]  And I think my number of input booleans could use some spring cleaning.
+[1709.52 --> 1711.02]  So I'm happy to hear that.
+[1711.02 --> 1728.02]  Go there to try out Provado for free and, of course, support the show.
+[1728.26 --> 1731.42]  Provado VPN is a zero log VPN.
+[1731.82 --> 1734.38]  That means there's no records of your activity.
+[1734.38 --> 1738.56]  We looked into this for you guys, and we wouldn't feature them unless it was this way.
+[1738.56 --> 1746.26]  And even in the event of a legitimate authority requesting logs associated with your activity when connected to Provado, they got nothing to give.
+[1746.68 --> 1749.10]  And even better, they're backed by Swiss privacy laws.
+[1749.26 --> 1753.74]  In addition to having that strict zero log policy, Provado VPN is based in Switzerland.
+[1754.28 --> 1758.82]  That means you're protected by the absolute strongest consumer privacy laws in the world.
+[1759.54 --> 1761.28]  And Provado has the tech where it matters.
+[1761.38 --> 1764.68]  They own and operate their own data centers and fiber lines.
+[1764.68 --> 1770.78]  And the network is composed of hundreds of servers physically located in 45 countries and 58 cities around the world.
+[1770.94 --> 1773.68]  What that means for you is you can connect in seconds.
+[1773.68 --> 1778.22]  And no matter what server you choose, you're going to get incredibly fast speeds every time you connect.
+[1778.80 --> 1782.96]  Provado VPN's network was built from the ground up and fully optimized for lightning fast speeds.
+[1783.04 --> 1788.36]  So visit provadovpn.com slash SSH and try it out right now for free.
+[1788.36 --> 1798.48]  The free account provides the same service level and unlimited speeds as the premium version, as well as 10 gigabytes a month of data transfer and access to the top 12 servers for one device.
+[1798.92 --> 1804.34]  And all Provado VPN users get access to their dedicated team of customer support that's 24-7.
+[1804.54 --> 1809.50]  And they also have an unlimited plan with hundreds of servers, P2P traffic support, and more.
+[1809.76 --> 1814.40]  So go check it all out at provadovpn.com slash SSH.
+[1814.40 --> 1822.18]  So, I mean, if you buy a Chromecast or whatever, then sometimes you have to, like, connect to an access point and then, like, your phone.
+[1822.28 --> 1826.96]  And then sometimes it crashes and you're, like, lost and you don't know how to set up the Wi-Fi.
+[1827.26 --> 1831.70]  So we're building a Bluetooth spec that is going to be built into ESP Home.
+[1831.92 --> 1833.52]  It's going to be built into the Home Assistant app.
+[1833.66 --> 1839.80]  So if you buy it, well, I mean, eventually we hope you're going to be able to buy ESP Home products.
+[1839.80 --> 1845.62]  But if you build an ESP Home product and you give it to your friend, they would just be able to go on with Bluetooth.
+[1845.92 --> 1847.48]  And we even have a web Bluetooth SDK.
+[1847.68 --> 1850.86]  So you can use, like, a Chrome browser to actually just set it up.
+[1851.76 --> 1852.88]  Oh, that is cool.
+[1853.52 --> 1853.80]  Yeah.
+[1853.82 --> 1854.24]  I like that.
+[1854.40 --> 1854.68]  Right?
+[1854.84 --> 1860.48]  And, I mean, I think I really want, like, you know, they're, like, on Tindy, people are selling their creations.
+[1860.74 --> 1863.94]  I just want, like, more of that because those products are way cooler.
+[1863.94 --> 1874.18]  Or, like, it's just, like, you know, we had the tech reader last year and there's, like, actually for the energy meters in the Netherlands, they actually have a protocol called P1.
+[1874.56 --> 1882.88]  And we're going to have an ESP Home-based device somebody's building that, like, you know, people can just plug it in and, boom, all the energy data is available in Home Assistant.
+[1883.48 --> 1884.38]  I'm sure you do.
+[1884.38 --> 1890.28]  But do you realize just how perfectly positioned you are to uniquely so to do this?
+[1890.96 --> 1891.74]  No, yeah, definitely.
+[1891.98 --> 1892.26]  Definitely.
+[1892.26 --> 1900.36]  It's because, you know, ESP Home, like, we acquired it mainly because, like, the original founder was, like, burned out.
+[1900.64 --> 1903.48]  But he was still getting, like, all these donations, right?
+[1903.50 --> 1907.80]  So we couldn't really say, hey, we're going to hire somebody full-time to make this great.
+[1908.60 --> 1910.00]  So we acquired it from him.
+[1910.12 --> 1911.88]  We have now Jesse working on it full-time.
+[1912.08 --> 1916.48]  And, like, you know, just we keep, you know, pumping out cool stuff.
+[1917.42 --> 1921.44]  Yeah, a full-time employee is going to, you know, they've got some time to fill.
+[1922.26 --> 1928.78]  You know, it's, yeah, well, the thing is, because we're so big, like, you know, we are 13 people full-time now.
+[1930.38 --> 1930.98]  That's crazy.
+[1931.50 --> 1932.18]  Yeah, thanks.
+[1932.74 --> 1933.48]  Lucky 13.
+[1933.48 --> 1938.46]  But the thing is, they work all over the place, right?
+[1938.48 --> 1939.94]  Like, we have the operating system guy.
+[1940.04 --> 1942.46]  We have the supervisor people.
+[1942.58 --> 1943.92]  We have the front-end people.
+[1944.04 --> 1948.08]  And so we're actually very thinly spread because there's just so much happening.
+[1948.82 --> 1949.46]  For sure.
+[1949.76 --> 1949.94]  Yeah.
+[1950.20 --> 1957.68]  Yeah, it's both a lot of people from when you started at one, but it's also not a lot of people for the scope of work there is out there.
+[1957.68 --> 1958.12]  Exactly.
+[1958.88 --> 1962.30]  Can you even imagine how many people, you know, a commercial entity?
+[1962.46 --> 1968.94]  Let's just hypothetically say you were owned by EA or some massive conglomerate like that, right?
+[1969.06 --> 1972.74]  How many people would they employ to write a piece of software like Home Assistant?
+[1972.94 --> 1976.10]  And it's just, to me, that speaks to the power of open source, right?
+[1976.18 --> 1980.64]  I mean, we couldn't have things in the world like Home Assistant without open source.
+[1980.64 --> 1982.02]  No, I think so.
+[1982.12 --> 1987.30]  I mean, there's just, you know, we get people from, like, all over the place.
+[1987.38 --> 1990.00]  They're brilliant programmers, but they have their day jobs.
+[1990.38 --> 1992.18]  And, like, you know, it's funny.
+[1992.30 --> 1993.72]  We have a couple of people.
+[1994.26 --> 1995.86]  One is a CEO of a company.
+[1996.12 --> 1998.20]  The other is, like, a director of software engineering.
+[1998.34 --> 1999.14]  So he's, like, a manager.
+[1999.68 --> 2002.40]  And, like, they just don't get to code at work anymore, right?
+[2002.44 --> 2004.16]  So they come home and they're like, well, f*** it.
+[2004.76 --> 2005.54]  I'm going to have it.
+[2006.58 --> 2007.36]  Yeah, absolutely.
+[2007.44 --> 2007.70]  I agree.
+[2007.70 --> 2020.24]  And also those sorts of people who have had a lot of training in programming and stuff like that in the past, they've got a lot that they can bring to the table, but their motivation might be sporadic.
+[2020.74 --> 2024.52]  And, you know, it's not really suitable to do a full-time job that way.
+[2024.62 --> 2030.08]  But absolutely, you can contribute, you know, a couple of weeks' worth of evenings of your brain to an open source project.
+[2030.54 --> 2033.92]  Well, I mean, that's how our core was originally all in threads.
+[2034.12 --> 2035.86]  And, like, we had, like, deadlocks all the time.
+[2035.86 --> 2040.82]  And then somebody came along who works in Mozilla, and he had a lot of Python experience.
+[2041.06 --> 2042.62]  He made, like, pylons in the past.
+[2042.86 --> 2047.10]  And, yeah, he rewrote our core to async.
+[2047.32 --> 2049.84]  And that's what we still run today, and that's why we're so fast.
+[2050.32 --> 2052.44]  So that's just a random guy that came along.
+[2053.04 --> 2065.14]  You know what else I love as well about the number of people you've just shared work for Nebukasa is the fact that that means that somebody like a Mozilla isn't needed to come out and buy you out to keep you sustainable.
+[2065.14 --> 2068.94]  It's a self-sustaining funding model you've created here.
+[2069.04 --> 2069.64]  I think that's great.
+[2069.96 --> 2070.10]  Yeah.
+[2070.10 --> 2071.30]  No, it's been really great.
+[2071.40 --> 2078.12]  I think, you know, we have no investors and no loans and these kind of stuff because it misaligns incentives, right?
+[2078.18 --> 2080.16]  Because, you know, they want, like, return on investment.
+[2081.52 --> 2081.72]  Yeah.
+[2081.80 --> 2083.68]  I mean, it's working great so far.
+[2083.68 --> 2091.76]  I mean, I expect as the pandemic, like, wees off that maybe people are spending less time at home, maybe spending less time on home assistance.
+[2091.92 --> 2092.36]  Who knows?
+[2092.94 --> 2094.70]  But they might need remote access.
+[2095.06 --> 2095.52]  That's true.
+[2096.36 --> 2096.72]  You know?
+[2096.72 --> 2114.10]  I mean, I happily, happily pay that because I think it's a – not only is it a fantastic service and I like how you are implementing it, but I also appreciate sort of the virtuous cycle of it incentivizes the company to make home assistance better, which just continues to drive more value to my subscription.
+[2114.54 --> 2118.12]  And it's legitimately one of those arrangements that I happily pay.
+[2118.58 --> 2118.94]  That's awesome.
+[2118.94 --> 2119.92]  Yeah, same.
+[2120.02 --> 2121.10]  I don't really need it.
+[2121.18 --> 2126.38]  I could quite happily set up my own reverse proxy with WireGuard and – in fact, I used to.
+[2126.52 --> 2127.74]  And then Nebu Kasa came on.
+[2128.00 --> 2128.26]  Yeah.
+[2128.26 --> 2129.56]  That's the origin of the name, by the way.
+[2129.64 --> 2132.10]  That word Nebu is quite unusual.
+[2132.10 --> 2139.64]  So Nebu is – it was some god of the wisdom in some – somewhere in some religion or language.
+[2141.28 --> 2142.84]  And so then we had, like, the word –
+[2142.84 --> 2143.06]  Yeah.
+[2143.56 --> 2143.82]  Okay.
+[2144.16 --> 2144.90]  I like it.
+[2145.14 --> 2148.12]  And then we also have the URL nabu.kasa, right?
+[2148.12 --> 2150.88]  Because that actually – we kind of set it on Nabu.
+[2150.96 --> 2153.46]  And then I was looking at domains and all of a sudden I said Nabu Kasa.
+[2153.56 --> 2154.86]  And I was like, that's it.
+[2155.38 --> 2157.80]  So it essentially comes down to Wise House.
+[2158.10 --> 2159.96]  Is that – that's great.
+[2160.22 --> 2160.60]  That is good.
+[2160.66 --> 2160.82]  Yeah.
+[2160.92 --> 2161.94]  And now we're waiting.
+[2162.12 --> 2166.96]  Razer had a smartwatch called Nabu in 2015 or 16 or something.
+[2167.38 --> 2169.62]  And we're just waiting for their trademark to lapse.
+[2170.22 --> 2171.12]  Maybe we can –
+[2172.26 --> 2175.06]  Get a little more mileage out of that name.
+[2175.36 --> 2176.20]  That's great.
+[2176.20 --> 2178.78]  I mean, I know lawyers have a reputation.
+[2179.04 --> 2183.36]  But can you confuse a house automation system and a watch?
+[2184.24 --> 2185.72]  You know, smartwatches.
+[2185.76 --> 2187.70]  Smartwatches you can talk to nowadays.
+[2189.08 --> 2189.92]  And so –
+[2189.92 --> 2190.14]  Yeah.
+[2190.20 --> 2191.58]  Who wants to even worry about a fight?
+[2191.72 --> 2192.42]  Why just – yeah.
+[2192.80 --> 2192.96]  Yeah.
+[2193.60 --> 2196.64]  But, boss, thank you so much for joining us and updating it on these things.
+[2196.64 --> 2205.44]  And also thank you and thanks to the team for making a piece of software that has improved my family's quality of life on a daily basis.
+[2205.70 --> 2208.80]  Not much actually touches our lives in that way.
+[2209.14 --> 2210.58]  So we're just really grateful for that too.
+[2210.80 --> 2210.98]  Awesome.
+[2211.08 --> 2211.62]  Well, you're welcome.
+[2211.62 --> 2214.80]  So I hope you enjoyed that interview with Paulus.
+[2214.96 --> 2218.66]  Now, we're not going to actually do any feedback this week just in the interest of time.
+[2218.88 --> 2226.48]  But next episode, we're going to discuss the distributed file system question that Chris posed last week.
+[2226.50 --> 2229.40]  We've had lots of feedback in the mailbag about that one.
+[2229.40 --> 2232.62]  Oh, I can't wait to see what people have suggested.
+[2233.10 --> 2235.36]  I feel like I'd be cheating if I read ahead.
+[2235.48 --> 2237.36]  But now I kind of want to go in there and take a look.
+[2237.90 --> 2238.70]  But I'll wait.
+[2238.80 --> 2239.14]  I'll wait.
+[2239.18 --> 2239.96]  I'll wait for the show.
+[2240.28 --> 2241.92]  So that way my reaction is fresh.
+[2242.06 --> 2242.34]  Awesome.
+[2242.76 --> 2242.88]  Yeah.
+[2242.90 --> 2252.94]  If you have any tips, selfhosted.show slash contact on how you could take advantage of the random amounts of free space on the hard drives all around your LAN.
+[2253.24 --> 2256.74]  And thank you to our members at selfhosted.show slash SRE.
+[2256.74 --> 2260.36]  You can support the show and become a member at selfhosted.show slash SRE.
+[2260.56 --> 2265.24]  And you get a limited ad feed, full production, just a little bit tighter and cleaner.
+[2265.70 --> 2269.88]  Extra content at the end of the show as well with a special members only post show.
+[2270.02 --> 2272.04]  And thanks to our sponsor, Cloud Guru.
+[2272.12 --> 2274.02]  You can find them on social media everywhere.
+[2274.20 --> 2275.74]  That's basically a social media site.
+[2276.04 --> 2277.64]  They're just slash a cloud guru.
+[2277.84 --> 2278.82]  That's really simple.
+[2279.24 --> 2282.82]  And as always, you can find me over on Twitter at ironicbadger.
+[2282.92 --> 2286.18]  And the show is selfhosted.show slash contact.
+[2286.18 --> 2286.66]  Indeed.
+[2286.88 --> 2289.58]  I'm over on the Twitter as well at Chris Elias.
+[2289.72 --> 2293.54]  And the podcast is over there too at selfhosted.show for news and announcements.
+[2294.04 --> 2294.88]  Thanks for listening, everybody.
+[2295.08 --> 2297.20]  That was selfhosted.show slash 45.

46： Pastebin Alternative _summary.txt

@@ -0,0 +1,67 @@
+• Bread-making as a stress reliever
+• Sourdough vs standard crusty loaf
+• Trader Joe's and its comparison to Aldi and Marks & Spencer's food hall
+• Cookie butter spread on bread
+• Cloud learning and cloudguru.com
+• Recent trip to Bozeman, Montana with family and RV upgrades
+• Industrial-grade internet setup in the RV
+• Establishing a connection between Wi-Fi and cellular networks for RV travel
+• Importance of maintaining connectivity in areas with limited or no cell signal
+• Pre-trip technology setup and maintenance, including:
+	+ T48 window (48 hours before trip): major tech changes allowed, backups, and sanity checks
+	+ T24 window (24 hours before trip): last-minute setup and preparations
+• Expanding the checklist beyond just technical aspects to include:
+	+ Gas stations and routes
+	+ Weather conditions and construction
+	+ Propane availability and reservation confirmation
+• Preparing for a road trip by updating and managing digital media
+• Managing media storage capacity in an RV
+• Tips for organizing and loading content on Plex server
+• Verifying LTE networks and router functionality before departure
+• Backing up data and preparing for offline access to essential information
+• Using Home Assistant dashboard on Fire tablets to manage devices remotely
+• Experiencing issues with voice assistants and GPS locations during previous trip
+• Comparing performance of different smart home devices
+• Home Assistant and power management system
+• Alex's setup with Raspberry Pis and Victron Venus
+• Gamifying family chores using Home Assistant Lovelace dashboard
+• Power system performance on recent trip, including solar power and alternator charging
+• Overheating issues with power system, including safety shutdowns
+• Cooling solutions for power bay and equipment
+• Infrastructure as code setup for Project Off Grid
+• Data collection from power system and integration with Home Assistant
+• The speaker installed a UniFi system with ease, avoiding the hassle of fishing cables through walls.
+• They promoted Linode as their cloud server provider, highlighting its competitive pricing, flexible tools, and excellent customer support.
+• The speaker prefers command-line interfaces (CLI) but has used GUI-based firewalls in the past.
+• He recently set up a Raspberry Pi 3B Plus to act as his DNS and DHCP server using Ansible for automation.
+• The speaker reflected on his enjoyment of writing code and the challenges he faced while working with Ansible, particularly checking for duplicate MAC addresses.
+• Using Ansible to automate tasks and generate config files for a Raspberry Pi
+• Controlling the flow of variables using facts with Ansible
+• Setting up an isolated network within ESXi lab to test DHCP
+• Introducing the Slexi tool and its shutdown announcement
+• Discussing alternative solutions, including self-hosting options like Xbin
+• A team's internal tool, Jupyter Broadcasting Pastebin (paste.docs.lol), is mentioned and demonstrated.
+• The tool is open-source (MIT licensed) and offers features such as a stats page for tracking public snippet views.
+• Self-hosting the tool is made easy with its implementation in Phoenix and Elixir, allowing it to run in Docker containers.
+• A demo of the tool's stats page shows that 11 public snippets have been viewed by eight people.
+• Xbin, another feature discussed, allows Netcat to pipe text to a self-hosted Pastebin solution and has a synced text mode for real-time collaboration.
+• ProvadoVPN is mentioned as a sponsor, offering zero log VPN services protected by Swiss privacy laws.
+• Kevin from Belgium discusses using Greyhole for pooling storage over the network
+• He compares it to MergerFS with Samba share, and notes that Greyhole also handles network layer and web UI organization
+• Alex expresses skepticism about Greyhole's relevance in today's context
+• Greg recommends Greyhole due to its ability to isolate each drive as a standalone file system, reducing data loss risk
+• Alex concludes that Greyhole feels like an old-school approach, built on outdated technology
+• Several listeners have shared positive experiences with Greyhole, but Alex remains unconvinced about its usefulness
+• Discussing the challenges of managing a remote system with unknown OS
+• ZFS licensing issues and potential container solutions
+• Rob's question about using containers for media management with Unraid
+• Advice on learning container technology, including resources like PerfectMediaServer.com and LinuxServer.io
+• The benefits of containers in allowing users to "walk before they can run" without needing extensive knowledge of sysadmin
+• Balancing the ease of use of pre-built containers with the importance of understanding how the system works for security reasons
+• Learning and tooling for better insight into what's being done
+• Unraid as a good product and helpful tool for getting data off Google and onto personal land
+• One-way phone backup, specifically on Android using Folder Sync app
+• Alternative to NextCloud clients for backing up mobile device files
+• Chat about Alex's first computer and how he got started with computers
+• Self-hosted show membership and benefits
+• Upcoming episode discussing self-hosted Google Photos alternatives

46： Pastebin Alternative _summary_corrected.txt

@@ -0,0 +1,67 @@
+• Bread-making as a stress reliever
+• Sourdough vs standard crusty loaf
+• Trader Joe's and its comparison to Aldi and Marks & Spencer's food hall
+• Cookie butter spread on bread
+• Cloud learning and cloudguru.com
+• Recent trip to Bozeman, Montana with family and RV upgrades
+• Industrial-grade internet setup in the RV
+• Establishing a connection between Wi-Fi and cellular networks for RV travel
+• Importance of maintaining connectivity in areas with limited or no cell signal
+• Pre-trip technology setup and maintenance, including:
+	+ T48 window (48 hours before trip): major tech changes allowed, backups, and sanity checks
+	+ T24 window (24 hours before trip): last-minute setup and preparations
+• Expanding the checklist beyond just technical aspects to include:
+	+ Gas stations and routes
+	+ Weather conditions and construction
+	+ Propane availability and reservation confirmation
+• Preparing for a road trip by updating and managing digital media
+• Managing media storage capacity in an RV
+• Tips for organizing and loading content on Plex server
+• Verifying LTE networks and router functionality before departure
+• Backing up data and preparing for offline access to essential information
+• Using Home Assistant dashboard on Fire tablets to manage devices remotely
+• Experiencing issues with voice assistants and GPS locations during previous trip
+• Comparing performance of different smart home devices
+• Home Assistant and power management system
+• Alex's setup with Raspberry Pis and Victory Venus
+• Gamifying family chores using Home Assistant Lovelace dashboard
+• Power system performance on recent trip, including solar power and alternator charging
+• Overheating issues with power system, including safety shutdowns
+• Cooling solutions for power bay and equipment
+• Infrastructure as code setup for Project Off Grid
+• Data collection from power system and integration with Home Assistant
+• The speaker installed a Unify system with ease, avoiding the hassle of fishing cables through walls.
+• They promoted Linde as their cloud server provider, highlighting its competitive pricing, flexible tools, and excellent customer support.
+• The speaker prefers command-line interfaces (CLI) but has used GUI-based firewalls in the past.
+• He recently set up a Raspberry Pi 3B Plus to act as his DNS and DHCP server using Ansible for automation.
+• The speaker reflected on his enjoyment of writing code and the challenges he faced while working with Ansible, particularly checking for duplicate MAC addresses.
+• Using Ansible to automate tasks and generate config files for a Raspberry Pi
+• Controlling the flow of variables using facts with Ansible
+• Setting up an isolated network within ESXi lab to test DHCP
+• Introducing the Lexi tool and its shutdown announcement
+• Discussing alternative solutions, including self-hosting options like Bin
+• A team's internal tool, Jupyter Broadcasting Pastebin (paste.docs.lol), is mentioned and demonstrated.
+• The tool is open-source (MIT licensed) and offers features such as a stats page for tracking public snippet views.
+• Self-hosting the tool is made easy with its implementation in Phoenix and Elixir, allowing it to run in Docker containers.
+• A demo of the tool's stats page shows that 11 public snippets have been viewed by eight people.
+• Bin, another feature discussed, allows Net cat to pipe text to a self-hosted Pastebin solution and has a synced text mode for real-time collaboration.
+• ProvadoVPN is mentioned as a sponsor, offering zero log VPN services protected by Swiss privacy laws.
+• Kevin from Belgium discusses using Grey hole for pooling storage over the network
+• He compares it to Mergers with Samba share, and notes that Grey hole also handles network layer and web UI organization
+• Alex expresses skepticism about Grey hole's relevance in today's context
+• Greg recommends Grey hole due to its ability to isolate each drive as a standalone file system, reducing data loss risk
+• Alex concludes that Grey hole feels like an old-school approach, built on outdated technology
+• Several listeners have shared positive experiences with Grey hole, but Alex remains unconvinced about its usefulness
+• Discussing the challenges of managing a remote system with unknown OS
+• ZFS licensing issues and potential container solutions
+• Rob's question about using containers for media management with Unpaid
+• Advice on learning container technology, including resources like PerfectMediaServer.com and LinuxServer.io
+• The benefits of containers in allowing users to "walk before they can run" without needing extensive knowledge of sysadmin
+• Balancing the ease of use of pre-built containers with the importance of understanding how the system works for security reasons
+• Learning and tooling for better insight into what's being done
+• Unpaid as a good product and helpful tool for getting data off Google and onto personal land
+• One-way phone backup, specifically on Android using Folder Sync app
+• Alternative to Nextcloud clients for backing up mobile device files
+• Chat about Alex's first computer and how he got started with computers
+• Self-hosted show membership and benefits
+• Upcoming episode discussing self-hosted Google Photos alternatives

46： Pastebin Alternative _transcript.txt

@@ -0,0 +1,735 @@
+[0.00 --> 3.28]  Been busy making tons and tons of bread this week.
+[3.58 --> 4.42]  Bread? Really?
+[4.86 --> 7.28]  Yeah, bread, like the dough stuff, right?
+[7.42 --> 9.00]  You know, flour, water, yeast.
+[9.36 --> 10.80]  Yeah, how's that? Okay, how's that going?
+[11.06 --> 16.40]  It's good. You know, it's a good way to work out some frustrations,
+[16.62 --> 18.20]  kneading that dough. I'll tell you what.
+[18.20 --> 21.96]  So are you telling me you've bought into the pandemic craze of making sourdough,
+[22.10 --> 23.48]  or is this bread for something else?
+[23.62 --> 27.72]  This isn't sourdough. I'm not a hipster, bro. I refute that allegation.
+[28.04 --> 28.88]  Sourdough is delicious.
+[28.88 --> 34.82]  It is, yeah. I tried sourdough last year and failed pretty spectacular.
+[35.10 --> 39.12]  I ended up with this soggy lump of what should have been delicious bread,
+[39.22 --> 42.80]  and it was, I mean, it tasted fine. It was just dense AF.
+[43.42 --> 46.40]  Doesn't sound very good. Yeah. I've seen those bad bread experiments.
+[46.52 --> 47.60]  It's not so good.
+[47.88 --> 51.96]  But this stuff, I'm just making standard crusty loaf,
+[52.40 --> 56.16]  and it's all in the kneading. It's all in the, you know, working.
+[56.16 --> 58.42]  You've got to work it, girl, you know?
+[58.84 --> 62.06]  Sure. Sure. I love to work it. And it's a sandwich bread?
+[62.22 --> 63.04]  Is that what you're doing with it?
+[63.28 --> 66.90]  Yeah, well, we actually went to Trader Joe's for the first time this week.
+[66.94 --> 68.20]  Do you have Trader Joe's up where you are?
+[68.70 --> 69.38]  Sure we do. Yeah.
+[69.38 --> 70.38]  Trader Joe's up where you are.
+[70.38 --> 73.54]  And we've discovered it's somewhat like, for the British audience,
+[73.88 --> 80.10]  it's like a cross between Aldi and Marks & Spencer's food hall.
+[80.10 --> 83.92]  It's, there's like only own brand products in this shop.
+[84.04 --> 86.90]  And we found this thing in there called cookie butter.
+[87.14 --> 88.94]  It's like peanut butter. It's a spread.
+[89.20 --> 90.74]  And it goes on bread.
+[90.86 --> 96.52]  And it's like, it's like gingerbread meets Nutella on,
+[96.58 --> 98.60]  on fresh crusty bread.
+[98.66 --> 99.88]  I'm telling you, man, there is,
+[100.20 --> 102.90]  there are a few meals that are more delicious than that one.
+[103.04 --> 104.38]  Man, you're making me hungry.
+[104.56 --> 107.42]  Well, if you want to spend your time learning something else,
+[107.42 --> 109.40]  maybe you should consider a cloud guru.
+[109.66 --> 111.84]  They are the leader in cloud learning,
+[111.84 --> 113.98]  and they have all kinds of modern tech skills,
+[114.06 --> 115.24]  including Linux that you can learn.
+[115.30 --> 117.72]  Hundreds of courses, thousands of hands-on labs,
+[117.80 --> 121.76]  get certified, get hired, get learning at a cloudguru.com.
+[122.16 --> 124.54]  Or, you know, you could learn bread too, or maybe both.
+[124.72 --> 126.12]  You mean this isn't the bread action show?
+[126.20 --> 126.92]  Is that what you're trying to say?
+[127.48 --> 128.52]  I mean, not yet.
+[129.52 --> 130.34]  It could be.
+[130.80 --> 132.54]  Now you just got back from a trip, right?
+[132.62 --> 133.28]  Welcome back.
+[133.56 --> 134.34]  Got back yesterday.
+[135.56 --> 137.16]  Still a little tired, you know,
+[137.16 --> 138.62]  went all the way to Bozeman, Montana,
+[138.70 --> 140.02]  which is one of our favorite destinations.
+[140.56 --> 141.66]  Just a beautiful spot.
+[142.10 --> 144.80]  Had the kids, had the dog, had the wife.
+[144.96 --> 146.34]  So it was a fully loaded bus.
+[147.12 --> 148.40]  And it's also, I think, Alex,
+[148.44 --> 151.24]  the first trip since the big project RV upgrades,
+[151.30 --> 153.18]  like all of them, including the internet setup,
+[153.66 --> 154.58]  have all been in place.
+[155.16 --> 155.44]  Yeah, nice.
+[155.48 --> 158.40]  I think the last one I recall you took was down to Texas.
+[159.22 --> 159.42]  Yeah.
+[159.78 --> 161.14]  And we didn't have the internet system then.
+[161.18 --> 162.72]  We had the solar system at that point,
+[162.72 --> 164.42]  but we did not have the internet.
+[164.42 --> 164.86]  Right.
+[164.86 --> 165.06]  Right.
+[165.12 --> 167.92]  You're industrial grade carrier busting.
+[168.28 --> 169.16]  How did that work out?
+[169.36 --> 170.76]  Well, you know, I'm pretty happy.
+[170.90 --> 171.48]  I'm pretty happy.
+[171.56 --> 174.74]  I mean, so the main goal when I'm traveling with the whole family
+[174.74 --> 176.84]  is to have my self-hosted system in my RV,
+[176.98 --> 179.56]  just be like out of the mind, out of the picture.
+[179.76 --> 181.26]  No hassle.
+[181.54 --> 183.20]  Just, I call it out of the way automation
+[183.20 --> 185.92]  because it's like facilitating the entire trip,
+[186.02 --> 188.20]  but I don't want to be managing it during the trip.
+[188.46 --> 189.14]  It's like hygiene.
+[189.28 --> 190.48]  You shouldn't have to think about it.
+[190.48 --> 193.62]  The minute you're thinking about someone else's hygiene,
+[193.80 --> 195.76]  like, you know, they need to step it up a bit.
+[196.38 --> 199.80]  And it definitely, it definitely, the setup passed that bar.
+[199.98 --> 202.84]  It was, it was pretty seamless, really.
+[203.40 --> 208.36]  I had, I had reception in areas that I've never had reception before.
+[208.46 --> 209.22]  And the whole thing is like,
+[209.26 --> 211.18]  I want the whole LAN to be really solid
+[211.18 --> 214.98]  because the kids are streaming videos off of a Raspberry Pi
+[214.98 --> 217.42]  or they're playing peer-to-peer networking games.
+[217.42 --> 219.76]  And I want that connection to remain up
+[219.76 --> 222.16]  regardless of what the cellular connection is doing.
+[222.28 --> 223.80]  So I've sort of separated it all out.
+[223.90 --> 226.42]  I have, I have Wi-Fi access points and I have a router
+[226.42 --> 228.44]  and I keep, and I keep that all separated.
+[228.44 --> 230.46]  So that way the router could even be offline theoretically,
+[230.46 --> 232.62]  because there are times legitimately
+[232.62 --> 234.52]  where we're driving through the Cascade mountains
+[234.52 --> 237.50]  or we're going through passes that we just don't have signal.
+[237.58 --> 239.76]  There's just, nobody has a cell tower on the mountain.
+[241.08 --> 242.50]  So we want stuff to work.
+[242.50 --> 245.44]  And even, and then when we get back into connectivity,
+[245.66 --> 247.38]  whichever cellular provider is available
+[247.38 --> 248.42]  and we have three on board,
+[248.50 --> 251.74]  I want that one to pick up and just start working.
+[252.24 --> 253.98]  That blew my mind the first time we took a trip
+[253.98 --> 257.36]  in the Southwest and the deserts around like Utah and stuff is,
+[257.78 --> 262.12]  we went sometimes an entire work day without any coverage.
+[262.46 --> 262.84]  Yeah.
+[263.14 --> 263.48]  Crazy.
+[264.14 --> 264.38]  Yeah.
+[264.58 --> 265.88]  It's, it is really,
+[266.16 --> 267.92]  Washington has gotten really good about it,
+[267.92 --> 268.58]  my home state.
+[268.58 --> 272.26]  Um, we have got towers everywhere except for the tops of the passes,
+[272.26 --> 275.22]  but there are absolutely parts of Montana
+[275.22 --> 277.94]  where there's just no signal we were at and same in Texas still.
+[278.22 --> 280.10]  So what I have for my technology stuff,
+[280.12 --> 281.86]  because I want it all to work really smooth
+[281.86 --> 283.70]  and I just want it to be a really good experience.
+[283.88 --> 286.98]  And it's, it's really when I just need it to be the most hassle free.
+[287.32 --> 289.68]  So I kind of have a regime before I go into a trip
+[289.68 --> 291.76]  and I have these windows of time.
+[291.76 --> 295.34]  And it, this is just something where it's for the entire RV,
+[295.60 --> 298.06]  but the technology stack is part of this.
+[298.06 --> 300.48]  And the first one is what I call my T48 window.
+[300.64 --> 304.58]  And that's 48 hours before a trip in this T48 window.
+[304.72 --> 307.26]  Major changes are allowed to the technology stack.
+[307.26 --> 311.42]  Like, uh, I did an Ubuntu 2104 update to get all the security fixes in.
+[311.50 --> 313.42]  I installed the latest home assistant upgrade.
+[314.04 --> 317.06]  And if I'm going to remove a node from the network
+[317.06 --> 318.80]  or add something to the network,
+[318.80 --> 321.60]  this T48 window is my last chance.
+[321.78 --> 322.78]  48 hours before we leave,
+[322.80 --> 325.16]  that's my last chance to make a major change like that.
+[325.16 --> 328.56]  Uh, it's also when I'll take snapshots of home assistant
+[328.56 --> 331.36]  and my boxes and make sure my backups are offsite.
+[331.84 --> 334.62]  It's a window of time to kind of just do a sanity check
+[334.62 --> 337.48]  on all of my, what if I lose the devices?
+[337.80 --> 339.92]  What if there's something that causes me to, you know,
+[339.92 --> 342.06]  completely lose the storage or something like that?
+[342.46 --> 344.74]  Do I have something in place, you know,
+[344.74 --> 345.94]  just to make sure before I go.
+[345.94 --> 348.12]  You know, what's so great about everything you've just said,
+[348.12 --> 350.56]  I think you actually have more pre-flight checks
+[350.56 --> 354.44]  than some customers of mine do deploying stuff into production.
+[355.44 --> 357.64]  Well, I, you know, I, you know,
+[357.66 --> 360.98]  I recently kind of decided to really treat these trips
+[360.98 --> 364.16]  as, uh, as kind of an operational thing.
+[364.16 --> 367.26]  And so, and that goes into like finding gas stations
+[367.26 --> 369.68]  that we can fit in and the best routes to take
+[369.68 --> 372.02]  and trying to identify weather conditions and construction.
+[372.02 --> 375.66]  And these, these concepts of a T48 checklist,
+[375.84 --> 379.02]  we expand that too to like making sure we have propane available,
+[379.56 --> 380.76]  a double checking reservations.
+[380.76 --> 383.24]  Like it's a, it's a lot outside of just the tech stack.
+[383.68 --> 385.90]  And, you know, we also will use this window of time
+[385.90 --> 388.30]  to make a go or no go call possibly on the trip.
+[388.42 --> 390.78]  Maybe something came up like this last trip,
+[390.78 --> 393.52]  we had something come up and we're like,
+[393.58 --> 395.60]  well, we should have added that to the T48 checklist.
+[395.74 --> 397.96]  And now that's part of what we're going to do from now on.
+[398.54 --> 399.16]  Hold on. Hold on.
+[399.36 --> 400.84]  Your checklist has a name.
+[401.16 --> 401.88]  Yeah. T48.
+[402.02 --> 403.42]  Yeah. Yeah. That's not just it.
+[403.46 --> 404.44]  We have it's yeah.
+[404.46 --> 406.46]  Cause that's T minus 48 hours until leaving.
+[406.56 --> 406.70]  Yeah.
+[406.98 --> 409.14]  Oh, okay. I like it.
+[409.44 --> 411.70]  And then we also have the T24 window.
+[411.84 --> 414.42]  Now that's the last like crunch time.
+[414.46 --> 416.36]  That's 24 hours before the trip.
+[416.74 --> 419.46]  That's when I break down my home office setup,
+[419.46 --> 420.72]  quote unquote in the RV.
+[420.92 --> 422.82]  So I no longer have a PC set up.
+[423.20 --> 427.02]  So I mostly transitioned to using my iPad for most of my work
+[427.02 --> 428.74]  or if I have to allow, I'll break out my laptop.
+[428.74 --> 432.80]  And this is where the change control committee,
+[433.02 --> 435.80]  AKA myself says no more big changes.
+[437.80 --> 440.12]  Just stop with your crazy updates.
+[440.58 --> 441.50]  I don't care.
+[441.76 --> 442.86]  I love this so much.
+[443.18 --> 444.08]  I can't even.
+[444.80 --> 444.92]  Yeah.
+[444.92 --> 446.36]  Oh, this is so good.
+[446.58 --> 447.46]  It works though.
+[447.54 --> 449.68]  It's like, and I've been in that window before.
+[449.76 --> 451.78]  I'm like, oh, I didn't install the home assistant update.
+[451.86 --> 454.32]  I'm probably going to be too behind by the time I'm on the road trip.
+[454.46 --> 457.22]  I should do it right before I leave because I'm going to be in a limited
+[457.22 --> 459.18]  or maybe no bandwidth situation on the road.
+[459.18 --> 464.40]  But when I'm in that T24 window, no, no major changes because I don't want to do anything
+[464.40 --> 468.22]  that's going to break and cause me to go on a big project right before we leave.
+[468.30 --> 468.50]  Right.
+[468.66 --> 471.36]  That's what we call in the biz, a change freeze window.
+[471.80 --> 472.10]  Yep.
+[472.22 --> 472.46]  Yep.
+[472.60 --> 476.42]  And that is an effect on once the T24 window is in effect.
+[476.98 --> 481.80]  But you know what I will do during this time is I will manage the media for the trip.
+[482.00 --> 486.12]  This is part of happy family, happy life where I go through,
+[486.12 --> 489.14]  because I have only two terabytes of media storage in the RV.
+[489.30 --> 492.50]  So I go through and I purge old movies and shows that we're not watching anymore.
+[493.14 --> 497.20]  And then I kind of load in the fresh stuff because I want content that the kids can watch
+[497.20 --> 501.52]  while we're going down the road that I know is kid friendly and will also keep them occupied.
+[501.78 --> 503.72]  So little tip for you dads out there.
+[504.06 --> 508.84]  What I start doing or you moms is I start collecting a show for them like weeks before the trip
+[508.84 --> 510.00]  and I don't tell them about it.
+[510.20 --> 512.84]  And I get it all organized like on an external hard drive.
+[512.84 --> 516.54]  And then I load it on the Plex server in this T24 window.
+[517.08 --> 519.92]  And then I tell Plex to immediately index and do its thing.
+[520.00 --> 523.82]  So that way when we set off for the trip, all of a sudden they've just got new content on Plex.
+[523.92 --> 524.62]  Oh, look at this.
+[524.66 --> 525.12]  It's great.
+[525.30 --> 529.04]  And then something else I'll do is I'll look for like a movie or a trilogy.
+[529.18 --> 532.56]  That's what I've been doing is finding family trilogies and loading them on there as well.
+[532.66 --> 535.08]  So while we're on the road, maybe we're at a rest stop for a night
+[535.08 --> 540.18]  or we're at some site where it's really bad weather and the kids are kind of stuck in the RV.
+[540.18 --> 541.92]  We've got movies to watch like this year.
+[542.00 --> 542.98]  I brought Jurassic Park.
+[543.08 --> 544.40]  Last year I brought Back to the Future.
+[544.64 --> 545.44]  I love the trilogies.
+[545.72 --> 547.30]  Who doesn't love a bit of Jeff Goldblum, eh?
+[547.62 --> 547.84]  Right.
+[548.04 --> 549.24]  Oh, my gosh.
+[549.52 --> 552.56]  I have not watched Jurassic Park in like forever.
+[552.80 --> 555.50]  And boy, Jeff Goldblum is laying it on thick in that movie.
+[556.62 --> 558.92]  It's thicker than my cookie butter on fresh bread.
+[558.92 --> 561.88]  No doubt about it.
+[562.44 --> 565.44]  So, you know, they get all that stuff sorted in my 24-hour window.
+[565.58 --> 571.60]  Verify that my LTE networks are all active, that one of my crazy carriers hasn't like canceled my account for some random reason.
+[572.00 --> 577.68]  I'll even reboot my router often just to make sure that comes up fresh and nice and snappy.
+[577.82 --> 579.54]  And then we set off.
+[579.66 --> 581.36]  And that's kind of my process every time.
+[581.36 --> 583.40]  And it forces me to go through and verify my backups.
+[583.80 --> 588.04]  Kind of forces me to do updates and figure out what needs updated and what I couldn't do.
+[588.16 --> 592.10]  And kind of makes me think about what do I need that I can store offline.
+[592.28 --> 594.84]  So that way when we don't have connectivity, life goes on as usual.
+[594.98 --> 596.58]  And I think it worked really well.
+[597.40 --> 602.76]  You know, this kind of trip to Montana was one of my use cases in my mind for this whole project off-grid.
+[602.76 --> 603.82]  That's awesome, man.
+[604.18 --> 613.04]  Like, last time you were trying to solve some issues around, was it the various voice tubes, the voice assistants?
+[613.46 --> 613.64]  Yeah.
+[613.76 --> 616.58]  And their GPS locations and stuff with them freaking out.
+[616.64 --> 617.48]  How was that this time?
+[617.78 --> 625.48]  So the HomePod does all right because it goes often, not always, but by the location of like the primary phone that set it up.
+[625.90 --> 628.46]  But the other stuff is really dumb about it.
+[628.46 --> 632.50]  And so what we just use the other stuff as is reference for what it's like back at home.
+[632.76 --> 638.08]  So when we ask for weather or we see the clock on there, we know that's what time at home is or what weather it is at home.
+[638.20 --> 646.20]  And that's just, you know, what really I think solved that problem for me was when I put up the Fire tablets that have the Home Assistant dashboard up all the time.
+[646.86 --> 650.06]  And the family can just, they kind of just prefer to do that anyways.
+[650.94 --> 652.64]  And then I still kind of use the tubes.
+[652.92 --> 655.00]  But you made a point the other day on Linux Unplugged.
+[655.00 --> 656.90]  There's actually a great interview on there.
+[657.24 --> 660.66]  And we were torn about whether to use that interview in this show or LUP.
+[660.66 --> 665.90]  And we ended up using it in LUP in the end with Aaron about his converted school bus.
+[666.48 --> 666.64]  Yeah.
+[667.10 --> 667.96]  Really cool project.
+[668.08 --> 670.32]  You know, and Alex, he's taken to the next level.
+[670.72 --> 675.54]  I'm still not there yet where I'm not pulling all of the metrics out of my electrical system and putting it into Home Assistant.
+[676.06 --> 676.84]  But he's done it.
+[677.30 --> 682.22]  He's done it with some Raspberry Pis and a little box that Victron makes called the Venus.
+[682.22 --> 684.92]  And he gets all that information in there.
+[685.02 --> 687.30]  And I love that idea.
+[687.30 --> 689.80]  And then what I want to do is kind of gamify it a little bit.
+[689.80 --> 696.04]  And I saw another post recently from a dad who took Home Assistant and put family chores in there.
+[696.08 --> 699.34]  And the family checks off the chores via the Home Assistant Lovelace dashboard.
+[699.54 --> 700.70]  And it generates points.
+[700.76 --> 701.32]  You saw that?
+[701.60 --> 702.36]  I saw that one, yeah.
+[702.44 --> 703.32]  It's such a great way.
+[703.32 --> 709.40]  I love to do that, but with power to kind of encourage and incentivize the family to conserve power.
+[710.06 --> 714.98]  Although on this trip, Alex, legitimately, the solar system was totally enough.
+[715.08 --> 720.86]  I was worried that 600 amp hours of lithium would not be enough power for a full family.
+[720.86 --> 725.48]  But when you get some good solar coming in like we had on this trip, we had good solar every day.
+[725.90 --> 729.54]  And you're doing just a little bit of driving so you also charge from the alternator.
+[730.18 --> 732.86]  I'm not exaggerating when I say we had unlimited power.
+[733.00 --> 735.90]  We had more power than we could use.
+[736.50 --> 742.12]  For the nearly two weeks, we just lived life as if we were hooked up to the grid.
+[742.78 --> 746.66]  And I never had to tell the kids, turn off the lights or don't turn that TV on.
+[747.06 --> 749.12]  I do still struggle with some overheating problems.
+[749.12 --> 753.46]  I had my power system overheat once when it was pretty hot out and we were really pushing it.
+[753.58 --> 756.50]  And I was really trying to see how hard I could push the system in general.
+[757.26 --> 763.08]  And it did like a safety shutdown on me and turned off the power to everything, including the servers.
+[763.60 --> 768.40]  Well, I mean, if you're doing a life hack where you're using the sun to power your air conditioner to cool you down,
+[768.44 --> 771.94]  as well as, you know, running a toaster or whatever else you're doing.
+[772.22 --> 776.26]  Yeah, it's a bit of one of those situations where when you have that much sun,
+[776.26 --> 778.64]  it creates enough heat that you need to run the air conditioning.
+[778.64 --> 780.60]  And you end up trying to balance it all out.
+[781.10 --> 782.42]  And I was really pushing it.
+[782.52 --> 783.50]  Oh, and we'd been driving.
+[783.74 --> 786.12]  And of course, the drivetrain itself gets hot.
+[786.22 --> 790.80]  So where our power bay is at, you know, there's heat from the drivetrain to adding to this whole thing.
+[790.86 --> 794.42]  It's just so, yeah, I'm very happy with it.
+[794.48 --> 799.74]  I do have to seriously figure out cooling, but it just is going to involve major cutting into the side of my RV.
+[799.74 --> 800.94]  And I just don't want to do that.
+[800.94 --> 803.72]  But one day, and I need to get that data into Home Assistant.
+[804.26 --> 805.88]  I've got to get that figured out as well.
+[806.42 --> 815.30]  And then ultimately, Alex, I would love to be managing this entire thing with some system that allows me to redeploy everything from scratch.
+[815.30 --> 826.12]  So if a Raspberry Pi died from heat or everything died and I had to pop in new units, when I'm on the road, it would be a minimal amount of downtime and just totally be able to redeploy my infrastructure from one central point.
+[826.18 --> 827.60]  And I know that's something we want to talk about today.
+[827.60 --> 834.18]  But it's been on my mind because that seems like the next level I could take this setup to, to make it even more trouble free.
+[834.32 --> 841.12]  And when there is a problem, a couple of Raspberry Pis in the drawer, I pop them in and I run some sort of system and they're back up and running.
+[841.58 --> 842.86]  Okay, I'm out 45 minutes.
+[843.02 --> 844.46]  That's where I want to take it next.
+[844.66 --> 853.04]  So data from the power system, figuring out cooling and doing some kind of infrastructure as code setup are my next goals for Project Off Grid.
+[853.04 --> 856.40]  I love your optimism that you've only got a couple of Pis in the drawer.
+[857.60 --> 862.26]  And I should probably have a switch and maybe a whole other router because that stuff gets hot.
+[862.54 --> 863.92]  Power supplies, don't forget those.
+[864.16 --> 864.56]  Yes.
+[865.10 --> 868.50]  Yeah, everything, the stuff in the telco cupboard.
+[868.64 --> 869.42]  How's the bench seat?
+[869.60 --> 870.24]  It gets hot.
+[870.32 --> 871.26]  It gets really hot.
+[871.36 --> 873.68]  The bench seat's also getting hot, but less equipment in there.
+[873.80 --> 879.24]  It's better now as I've moved, as I've dispersed stuff now that I have power over ethernet, I've kind of spread stuff out.
+[879.32 --> 879.66]  Yes.
+[879.66 --> 884.86]  So the thermal load is not as bad, but it's still not where it still needs a solution.
+[885.02 --> 885.68]  I'm still not happy.
+[885.90 --> 887.46]  POE is just so awesome.
+[887.60 --> 894.98]  I was putting a TV on the wall in my kitchen the other day, and I've got one of these UniFi units that's powered over ethernet.
+[895.36 --> 899.46]  And on the bottom, it's got a couple of ethernet jacks on the bottom.
+[899.46 --> 915.74]  And so rather than running a whole second ethernet cable from wherever in the house, which would have been a good couple of hundred feet's worth of cable, I just plugged one tiny little right angle jack into the bottom of this UniFi thing, fed it up through the drywall and out behind the TV just above it.
+[915.80 --> 917.42]  And it was so easy.
+[917.42 --> 924.06]  Yeah, those are the kinds of solutions that feel like life hacks because you just saved yourself an hour or two for running cable.
+[924.06 --> 927.14]  And who enjoys fishing cables through walls, man?
+[927.24 --> 928.24]  And crawl spaces?
+[928.52 --> 928.98]  Not me.
+[929.10 --> 929.70]  I'll tell you that.
+[929.70 --> 934.32]  Linode.com slash SSH.
+[934.40 --> 939.48]  Go there to get $100 in 60-day credit towards a new account and go there to support the show.
+[939.88 --> 941.70]  Linode.com slash SSH.
+[941.96 --> 943.54]  Linode is our cloud server provider.
+[943.72 --> 948.10]  And really, it's not just because the price is so great, although it is great.
+[948.10 --> 953.20]  It's also because the tools they have make it possible for a small team to have killer infrastructure.
+[953.72 --> 955.96]  Alex and I use it for our projects here on the show.
+[956.10 --> 958.92]  We use it for the backend infrastructure for JB 3.0.
+[959.34 --> 963.24]  And millions of projects and sites that we all love on the internet are using Linode.
+[963.44 --> 970.04]  They've been around since 2003 as one of the first companies in cloud computing, three years before AWS and other enterprise providers.
+[970.24 --> 973.34]  They're independently owned and founded on a love for Linux and open source.
+[974.06 --> 975.48]  I mean, they like to geek around with this stuff.
+[975.56 --> 976.84]  That's why they started so long ago.
+[976.84 --> 981.78]  Now that we live in the future, they're dedicated to offering the best virtualized cloud computing.
+[981.98 --> 985.00]  If it runs on Linux, well, it'll run on Linode.
+[985.38 --> 989.70]  And they have node balancers and, of course, a fantastic dashboard to make it all possible.
+[989.82 --> 992.12]  11 data centers around the world.
+[992.56 --> 997.26]  One-click deployments of the entire application stack, if that's how you roll or build the whole thing up from scratch.
+[997.32 --> 1002.10]  And if you like to manage it with some centralized tools like Terraform, they support that too.
+[1002.10 --> 1010.22]  And then, just kind of like the bow on top of it all, they have fantastic 24-7 customer support by phone or by ticket.
+[1010.40 --> 1012.88]  So you're going to be taken care of if you ever run into any problems.
+[1013.32 --> 1018.04]  Go see why a huge part of our community has started using Linode and why we use it ourselves.
+[1018.48 --> 1020.56]  Linode.com slash SSH.
+[1020.56 --> 1027.52]  Now, you know I have a bit of a thing about GUIs and I prefer to do things on the command line, don't you?
+[1027.78 --> 1029.00]  That is totally true.
+[1029.00 --> 1036.00]  The one exception to this rule for probably seven or eight years has been my firewall for some reason.
+[1036.34 --> 1040.28]  I've allowed myself to run PFSense and then I moved to OpenSense last year.
+[1040.44 --> 1043.24]  You know, I've thought about that and I've meant to ask you why that is.
+[1043.48 --> 1044.06]  I don't know.
+[1044.44 --> 1045.18]  It's not rational.
+[1045.64 --> 1049.54]  Maybe you always do something that way and so you go on doing it that way, perhaps.
+[1049.70 --> 1050.56]  Yeah, that must be it.
+[1050.56 --> 1056.38]  And I came to the conclusion that with my home lab setup where I'm spinning up and down OpenShift stuff all the time
+[1056.38 --> 1063.62]  and I'm constantly adding MAC address reservations for new smart devices that arrive, you know,
+[1063.68 --> 1068.26]  I get a new phone or a new Shelly device pops up or whatever it is.
+[1068.74 --> 1073.98]  I feel like I'm logging into OpenSense three or four times a week to make some small tweak for some reason.
+[1073.98 --> 1078.30]  Now, that's fine if you, you know, think about it.
+[1078.34 --> 1085.36]  It's not really that big of a deal, but I would prefer to just make one config line change in an Ansible repo or something
+[1085.36 --> 1087.68]  and then run a playbook and it's done.
+[1088.08 --> 1098.42]  So I've finally bitten the bullet and written a playbook to turn an old Raspberry Pi 3B Plus that I have into my DNS and DHCP server.
+[1098.42 --> 1100.80]  Very nice.
+[1100.90 --> 1105.32]  And you think a Raspberry, I mean, yeah, it should be powerful enough for what you've got.
+[1105.40 --> 1107.36]  How many devices on your network would you say?
+[1107.90 --> 1110.10]  I think I've got like 150 or so.
+[1110.80 --> 1119.14]  But I mean, it's not like, you know, the performance of a DHCP server, this is ancient history technology.
+[1119.14 --> 1125.02]  You know, those servers have been around as long as the internet has pretty much those technologies.
+[1125.40 --> 1128.28]  And they need such minimal resources.
+[1128.58 --> 1135.36]  The only thing I was worried about with the Raspberry Pi using that for DHCP and DNS was it's a Pi, right?
+[1135.42 --> 1144.20]  I mean, it's logging to an SD card, but then I can just USB boot and put logs into RAM and ship them off to some remote server if I really want to keep them.
+[1144.20 --> 1146.48]  So I think I can work around that.
+[1146.64 --> 1153.74]  But what I ended up doing was using this as an exercise to remind myself how much I enjoy writing code.
+[1154.38 --> 1156.68]  It's not something I do as much as I would like anymore.
+[1157.06 --> 1169.14]  And one of the most difficult challenges I found actually was making Ansible look at a list of MAC addresses that I'd supplied and check for any duplicates.
+[1169.14 --> 1171.86]  I mean, it sounds like a really simple thing.
+[1172.28 --> 1174.04]  And, you know, probably to some people it is.
+[1174.10 --> 1177.16]  But to me, I felt like I was working on the DaVinci code solving this one.
+[1178.06 --> 1186.70]  I have one big list of dictionaries with multiple sub keys and sub elements within them, right?
+[1186.74 --> 1194.38]  So it's, you know, name, IP and MAC address, for example, which corresponds to a specific device or a specific host on my network.
+[1194.38 --> 1208.42]  So I can go in and iterate over those keys using Ansible, over those sub elements using Ansible, and pull out the bits of information that I need to generate the config files, which then get deployed onto the Raspberry Pi using Ansible.
+[1209.12 --> 1219.64]  But what was really difficult was actually trying to control the flow of variables using facts using Ansible.
+[1219.64 --> 1234.62]  And there's a code snippet in the show notes if you're interested, but what I ended up doing was reading the list of MAC addresses into a fact and then comparing it against itself to be unique using one of Ansible's built-in filters.
+[1235.10 --> 1243.48]  And I'm sure very few people listening to this are going to ever want to solve the problem that I solved, but I'm incredibly proud of this bit of code.
+[1244.56 --> 1246.30]  So I thought I'd talk about it on the show.
+[1246.30 --> 1247.62]  That's a nice solution.
+[1248.18 --> 1259.14]  And kind of just works towards what I was talking about, how in a way what you've done is you've let the computer solve a problem for you that I would just spend human hours burning.
+[1260.02 --> 1269.56]  I spent probably two evenings whilst I was rocking a baby to sleep in one hand and trying to code in the other.
+[1269.84 --> 1270.72]  Productive right there.
+[1271.24 --> 1272.64]  Solving this problem, yeah.
+[1273.14 --> 1275.92]  Those late nights are productive for some reason.
+[1276.30 --> 1287.82]  What was really interesting actually was for my testing, I ended up using my ESXi lab and I created a second virtual network interface on that system.
+[1288.30 --> 1304.24]  And then I span up an isolated network within my network to test DHCP because obviously I didn't want to turn off my primary DHCP server because, well, I kind of need that for everything that goes on most days.
+[1304.24 --> 1317.48]  So I ended up with a completely separate subnet within VMware that I was able to test it and I was able to have OpenSense actually running as a firewall on this virtual network running within VMware.
+[1317.68 --> 1318.82]  It was really cool.
+[1318.82 --> 1330.52]  And I really think that if you're remotely interested in networking that there are just little projects like this you can do to kind of stretch yourself and challenge yourself where you can learn little bits and bobs here and there.
+[1330.92 --> 1332.14]  And I don't know.
+[1332.22 --> 1333.10]  I just had fun doing it.
+[1333.10 --> 1337.46]  Yeah, push yourself in a way that it solves a problem and you learn something.
+[1337.66 --> 1342.78]  And that solving a problem, something that's been on your mind for a while, is such a good motivator.
+[1342.88 --> 1346.90]  It's such a great way to get into something or, in your case, maybe take something to the next level.
+[1347.52 --> 1349.48]  People ask all the time, like, where should I get started?
+[1349.60 --> 1350.46]  How should I get started?
+[1350.60 --> 1351.12]  That's how.
+[1352.14 --> 1354.42]  It's a cliche to say it, but scratch that itch.
+[1354.82 --> 1355.74]  Absolutely true.
+[1356.18 --> 1361.60]  Now, speaking of, we've been using something called Slexi on JB for many, many years.
+[1361.64 --> 1363.40]  This goes back to Linux Action Show days.
+[1363.82 --> 1364.90]  Excuse me?
+[1365.98 --> 1366.80]  Yeah, it does.
+[1366.90 --> 1367.02]  Yeah.
+[1367.18 --> 1370.66]  It's a bad name, Slexi.org, but it was a good tool.
+[1370.84 --> 1371.26]  Yeah, dude.
+[1371.36 --> 1372.46]  You old, you know?
+[1372.92 --> 1373.72]  Yeah, I know.
+[1374.18 --> 1374.74]  I know.
+[1374.84 --> 1380.06]  And I could see the signs coming because every now and then the service would be offline for a couple of hours.
+[1380.32 --> 1382.38]  And then it came back strong for a bit.
+[1382.38 --> 1390.02]  It was just a clean paste bin that supported basically every language on the planet, including my beloved Markdown, even.
+[1390.62 --> 1401.92]  And it was really simple for us as a team to take, like, emails that come in or messages on Discord and throw them in something that we could link the other hosts to and link them in our show notes.
+[1402.38 --> 1408.16]  And it really wasn't something that was necessarily intended for public consumption, although it could be in some cases.
+[1408.16 --> 1416.80]  But it was mostly just so that way you have, like, you know, 15 different platforms, messages come in for a show, and we could take them and have one central spot.
+[1417.34 --> 1418.52]  And so it was Slexi.org.
+[1418.52 --> 1423.86]  And then, like, so many things, when the cloud giveth, the cloud taketh.
+[1424.28 --> 1427.26]  And at the beginning of March, they announced they were shutting down.
+[1427.26 --> 1436.04]  And I was beside myself, Alex, and I looked over to you, Alex, and I said, Alex, save us.
+[1436.36 --> 1438.42]  This is clearly something we should self-host.
+[1439.48 --> 1443.32]  Well, I think we might have found a solution in a project called Xbin.
+[1444.04 --> 1447.90]  And this is over on GitHub at midnight slash Xbin.
+[1448.16 --> 1450.92]  Midnight spelt with a one instead of an I.
+[1451.00 --> 1453.40]  Just look in the show notes so that there'll be a link there for you.
+[1454.00 --> 1455.52]  And this project is actually really interesting.
+[1455.86 --> 1461.16]  It's a very simple interface, which is, you know, what Chris needs after a late night, let's be honest.
+[1461.74 --> 1461.84]  Yeah.
+[1462.08 --> 1464.04]  And it just, boom, pops right up, and there's a text field.
+[1464.12 --> 1465.24]  You just paste the stuff in there.
+[1465.28 --> 1465.54]  Pow!
+[1465.72 --> 1466.10]  It's good.
+[1466.14 --> 1466.64]  It's really quick.
+[1466.72 --> 1468.32]  And I've actually been working with the developer.
+[1468.32 --> 1473.32]  I've opened probably more issues than I should have on his GitHub, and he's been honestly fantastic.
+[1474.02 --> 1483.10]  He's added, just for us, on our request, custom logo support, the ability to moderate comments, as well as a couple of other things as well.
+[1483.54 --> 1484.20]  That's neat.
+[1484.66 --> 1484.90]  Yeah.
+[1485.06 --> 1498.72]  You know, sometimes you just love open source so much that some random guy who I will probably never meet in person is willing to put some time and effort in to help us adopt his thing by adding features that we ask for.
+[1498.76 --> 1500.08]  It's just so cool.
+[1500.48 --> 1501.52]  It really is great to see.
+[1501.52 --> 1504.42]  It's actually so hard to overstate the point you just made.
+[1504.62 --> 1515.66]  There is an internal tool that we use as a team to produce our shows, and you contact the developer or developers, and they're actually going to implement those features.
+[1515.82 --> 1519.68]  Think about that in the context of, say, like subscription enterprise software.
+[1520.02 --> 1523.94]  You could be paying thousands of dollars a year and not get that kind of service level.
+[1523.94 --> 1532.20]  And it's MIT licensed, so it's a really permissible license, and I just think it's super wonderful to see it.
+[1532.40 --> 1534.30]  Do we have a demo for folks so they can check it out?
+[1534.58 --> 1535.16]  We do, yes.
+[1535.16 --> 1540.10]  We're actually using it for all of our feedback for this episode, so at paste.docs.lol.
+[1540.30 --> 1542.40]  That's now the Jupyter Broadcasting Pastebin.
+[1543.00 --> 1548.20]  We're going to just use it for show notes and, well, not show notes, feedback into shows and stuff like that.
+[1548.24 --> 1551.92]  So I think we're already using it on Coda, but you'll see it in other shows as we go forward.
+[1552.56 --> 1556.06]  There is an actual official project demo linked in the show notes as well.
+[1556.06 --> 1560.60]  It's really just a nice, easy-to-use Pastebin clone with some great features.
+[1561.08 --> 1568.18]  It's written in Phoenix and Elixir, and I think one of the things that's appealing to us is it's pretty easy and straightforward to self-host it.
+[1568.38 --> 1570.14]  Now, have you seen the stats page that it has?
+[1570.16 --> 1577.10]  So if you go to URL of your instance slash stats, you can see how many public snippets have been made
+[1577.10 --> 1581.58]  and the number of views they're getting, the most popular one, all that kind of stuff.
+[1581.68 --> 1584.86]  I mean, kind of pointless, but also, who doesn't love a good graph, eh?
+[1584.86 --> 1591.24]  If you want to see ours, you can go to paste.docs.lol, and then it's slash stats, like Alex said.
+[1591.72 --> 1593.56]  So we've had 11 public snippets.
+[1593.84 --> 1598.54]  I make most of mine public, so we've done, I guess, 11 emails on this thing so far.
+[1599.12 --> 1605.46]  It's interesting that what qualifies as popular is eight people viewed one of them, which is really just us.
+[1605.54 --> 1606.76]  It's just the people in JB.
+[1607.58 --> 1609.18]  But, you know, it's great that it shows that.
+[1609.42 --> 1610.92]  It runs in Docker, of course.
+[1611.12 --> 1613.58]  I wouldn't honestly have looked at it if it didn't.
+[1613.58 --> 1615.74]  I'm running it up on a Linode.
+[1615.90 --> 1621.30]  I think it's up to about 15 containers, that single $5 Linode now.
+[1621.78 --> 1624.30]  It's hard to overstate how awesome that is, really.
+[1624.50 --> 1624.60]  Yeah.
+[1624.80 --> 1628.26]  So please be nice to it and don't break it, because it's a tool we use for daily production.
+[1628.44 --> 1631.74]  And we're opening the Komodo a little bit, telling you about it.
+[1631.74 --> 1643.22]  And now in a feature that I think may well be aimed exclusively at Wes Payne, you can actually use Netcat to pipe text to Xbin.
+[1643.70 --> 1646.62]  When I saw that, I was like, this is so for Wes.
+[1646.88 --> 1647.84]  This is so great.
+[1647.90 --> 1649.62]  But it's actually just a very quick way.
+[1649.62 --> 1657.28]  And if you're already on the command line, the fact that you could Netcat something to your self-hosted Pastebin solution, that's a winning feature.
+[1657.64 --> 1658.22]  I'm sorry.
+[1658.32 --> 1658.86]  That's great.
+[1659.20 --> 1663.60]  Now, I know we use HedgeDoc for all of our show notes and stuff and our internal collaboration.
+[1663.60 --> 1668.42]  But Xbin also has a synced text mode.
+[1668.54 --> 1672.52]  So, you know, if you click on in the UI, there's a button that says synced.
+[1673.00 --> 1682.36]  It will give you a five-digit custom code in the URL you give to whoever you want to, you know, watch in real time what you're doing.
+[1682.84 --> 1684.66]  You know, and I can just type away.
+[1684.78 --> 1691.66]  And in real time, it will update whoever is looking at that URL, what I'm doing, which for like pair programming or something like that,
+[1691.66 --> 1693.68]  I can see this being absolutely awesome.
+[1696.08 --> 1698.44]  ProvadoVPN.com slash SSH.
+[1698.50 --> 1702.16]  P-R-V-A-D-O-V-P-N.com slash SSH.
+[1702.22 --> 1705.58]  Go there and try out Provado for free and support the show.
+[1706.06 --> 1708.66]  ProvadoVPN is a zero log VPN.
+[1708.66 --> 1713.16]  That means no records of your online activity are logged when connected to ProvadoVPN.
+[1713.92 --> 1718.64]  Even in the event of a legitimate authority request for logs associated with your activity when connected to the service,
+[1718.78 --> 1720.36]  there's just nothing to give.
+[1720.36 --> 1725.20]  And if that wasn't good enough, you can rest comfortable knowing they're protected by Swiss privacy laws.
+[1725.62 --> 1728.66]  They have a strict zero log policy and they're based in Switzerland.
+[1728.90 --> 1730.04]  That really mattered to us.
+[1730.10 --> 1733.26]  And that's why we picked ProvadoVPN for our sponsor.
+[1733.68 --> 1737.88]  It means you're protected by the absolute strongest consumer privacy laws in the world.
+[1738.18 --> 1741.40]  And they have a fantastic network to back it all up.
+[1741.60 --> 1745.08]  ProvadoVPN owns and operates its own data centers and fiber lines.
+[1745.08 --> 1751.70]  And the network is composed of hundreds of servers physically located in 45 countries and 58 cities around the world.
+[1752.10 --> 1753.50]  You can connect anywhere in seconds.
+[1753.58 --> 1757.68]  And no matter what server you choose, you'll get incredibly fast speeds every time you connect.
+[1758.10 --> 1763.68]  ProvadoVPN's network was built from the ground up, fully optimized for lightning fast speeds.
+[1763.68 --> 1768.46]  So visit provadovpn.com slash SSH and try it out for free.
+[1768.46 --> 1798.44]  ProvadoVPN.com slash SSH.
+[1798.46 --> 1802.82]  We've got some feedback from Kevin in Belgium.
+[1803.46 --> 1804.56]  Love the show, guys.
+[1804.72 --> 1805.22]  Keep it up.
+[1805.48 --> 1809.14]  In the last episode, there was some talk about pooling different bits of storage over the network.
+[1809.76 --> 1812.88]  In the past, I've used Greyhole to do this.
+[1813.06 --> 1817.80]  I was able to pool two different machines into one virtual storage presented via Samba.
+[1818.06 --> 1818.46]  Brackets.
+[1818.72 --> 1819.78]  Yes, I know.
+[1819.78 --> 1833.16]  It worked for me for many years until I switched to one new machine pooling all drives using MergerFS using the, I don't wish to blow my own trumpet here, but the now famous perfect media server guide.
+[1834.84 --> 1836.30]  Yeah, it is.
+[1836.58 --> 1837.40]  People love that.
+[1837.76 --> 1838.88]  It's a great guy.
+[1838.88 --> 1840.24]  So I took a look at Greyhole.
+[1840.34 --> 1841.70]  It's actually a pretty interesting project.
+[1842.30 --> 1845.94]  And yeah, pooling different bits of storage using Samba.
+[1846.22 --> 1847.28]  I mean, that's it.
+[1847.38 --> 1848.50]  That's the pitch for the product.
+[1848.92 --> 1855.88]  I wonder what you think of this, Alex, compared to just something like MergerFS with a Samba share on top, because ultimately you'd get similar results.
+[1855.88 --> 1869.14]  But the difference with Greyhole is it's taking care of the network layer for you and also the sort of the organization via the web UI, if you want, which I know triggers you sometimes, but it does have a web UI, if you want.
+[1869.56 --> 1870.38]  I love a good UI.
+[1870.50 --> 1871.22]  What are we talking about?
+[1871.34 --> 1871.90]  I love that.
+[1872.54 --> 1872.98]  Okay.
+[1873.10 --> 1873.38]  All right.
+[1873.42 --> 1873.64]  Fine.
+[1873.70 --> 1873.96]  Fine.
+[1874.26 --> 1875.46]  You won't engage, but I know.
+[1875.86 --> 1876.26]  I know.
+[1876.96 --> 1884.66]  So Greyhole, think of it as a way to pool a bunch of shares across your network into one big share, right?
+[1884.66 --> 1886.58]  Is that sort of a fair summary of it?
+[1886.84 --> 1887.42]  Yeah, pretty much.
+[1887.56 --> 1891.10]  And the underlying shares, it's a bit like GlusterFS in this regard.
+[1891.20 --> 1900.64]  So you've got different, effectively, bricks of storage, which you then concatenate together into one megatron of storage.
+[1901.20 --> 1901.30]  Yeah.
+[1901.64 --> 1905.54]  Nice feature is that you can set redundancy on a per share level.
+[1905.76 --> 1914.36]  So you can indicate how many copies of each file you want to keep as well, which, you know, if you've only got one copy of something, you may as well have zero copies of it.
+[1914.36 --> 1922.22]  I know this is popular with the audience because we got several emails about it as the recommendation when I put out the question of how are you pooling your storage.
+[1922.88 --> 1927.98]  I have to say, overall, it's a solution that feels kind of like an old school approach.
+[1928.04 --> 1930.18]  And it has been around forever, so that might be part of it.
+[1930.26 --> 1931.14]  But I'll give you an example.
+[1931.34 --> 1938.22]  Like, to get it up and going via their docs, you start by curling a shell script and then, you know, pseudo bashing that.
+[1938.22 --> 1942.60]  But you can do it manually, but either way, you end up just stalling a ton of stuff on your box.
+[1942.90 --> 1943.66]  It really does.
+[1943.72 --> 1945.48]  And that's just a thing I don't really enjoy anymore.
+[1946.08 --> 1958.38]  And then there's quite a bit of configuration to essentially build up a whole system based on finicky SambaShares, which I, again, totally appreciate and think there is a spot for that.
+[1958.38 --> 1970.78]  And I could even see it like if I was in if I was in like a condo with a couple of roommates like I was, you know, 20 years ago, I could definitely see us using each of our PCs in a system like this.
+[1970.90 --> 1972.82]  And it working really well for what we want.
+[1973.02 --> 1975.62]  But I just don't really see it today.
+[1976.12 --> 1980.06]  The way this setup works, Alex, it just doesn't seem doesn't quite seem like it's it.
+[1980.14 --> 1981.66]  Like, it's not quite the solution I was looking for.
+[1981.66 --> 1985.10]  So when I tried it, I that was my that was my impression.
+[1985.40 --> 1988.76]  We also had some feedback coming from Greg, also recommending Greyhole.
+[1989.12 --> 1993.10]  And his point was that each drive is a standalone file system.
+[1993.10 --> 1997.90]  So losing just one drive doesn't affect the data on the others, which is useful.
+[1998.42 --> 1999.68]  But I don't know.
+[1999.78 --> 2007.18]  To me, this is I know you asked the audience to send in their opinions, but it feels to me like this is a solution looking for a problem.
+[2007.18 --> 2010.48]  And then people have kind of built some reliance on it.
+[2010.48 --> 2012.90]  And it's kind of it's a Jeff Goldblum moment.
+[2012.90 --> 2013.12]  Right.
+[2013.16 --> 2014.58]  Just just because we can.
+[2014.68 --> 2016.60]  Your scientists were so obsessed with whether they could.
+[2016.92 --> 2018.88]  They didn't stop to think about whether they should.
+[2019.00 --> 2019.24]  Right.
+[2019.34 --> 2020.62]  And I think that's it.
+[2020.76 --> 2021.94]  I think that's my impression of it.
+[2021.96 --> 2024.52]  But I do like I do like hearing how it works for people.
+[2024.52 --> 2026.92]  And we did get several people that said it works well for them.
+[2026.96 --> 2029.98]  And that's kind of awesome because I know Greyhole's been around for a long time.
+[2029.98 --> 2032.04]  And I'm glad to see it's still going.
+[2032.34 --> 2034.34]  The Web UI does make it simple to get up and going.
+[2034.34 --> 2035.20]  You can go in there.
+[2035.26 --> 2039.20]  The first thing you do is you add some storage to it and then it lets you get things set up.
+[2039.20 --> 2040.44]  And that's nice.
+[2040.62 --> 2041.28]  That's good to see it.
+[2041.74 --> 2042.36]  But I don't know.
+[2042.44 --> 2045.30]  I guess this sounds really dumb when I go to say it out loud.
+[2045.36 --> 2058.88]  But you know what I'd really like is I'd love a solution at the ZFS level where there was some kind of service where you could you could dedicate any partition formatted in ZFS or any dedicated to ZFS could become part of some sort of network ZFS pool.
+[2059.54 --> 2061.18]  That's where I'd love to see that work get done.
+[2061.18 --> 2062.02]  That would be nice.
+[2062.12 --> 2062.26]  Yeah.
+[2062.48 --> 2067.10]  The tricky part of this I think is you don't know what OS the remote system is running.
+[2067.86 --> 2072.58]  And with ZFS in particular licensing is such a touchy subject.
+[2073.22 --> 2083.98]  Whether you could actually have ZFS running as some kind of a container on that remote system and then say here's 100 gig virtual disk a bit like Docker Desktop works like.
+[2084.60 --> 2085.72]  Maybe that's the way to do it.
+[2085.72 --> 2086.14]  All right.
+[2086.20 --> 2093.98]  Well, Rob writes in and Rob's been been using quite a few containers recently and been running with like 50 terabytes of content.
+[2094.34 --> 2097.58]  And while that's been fine for Rob, he kind of wants to take things to the next level.
+[2097.58 --> 2107.52]  And he says, so do you have any advice or resources for folks out there like me who maybe know just enough to be dangerous, but don't actually know how things are working under the hood of Unraid?
+[2107.84 --> 2114.68]  Like, do you have a beginner's guide for folks who maybe know just a bit, but not as much as they could or really should yet?
+[2114.94 --> 2115.96]  Thanks for the help, Rob.
+[2115.96 --> 2122.30]  Well, I think, Rob, you're exactly the type of person I had in mind when we were founding LinuxServer.io.
+[2123.16 --> 2128.06]  You know, it's all about finding some good sources of documentation.
+[2128.38 --> 2134.80]  And I think something like PerfectMediaServer.com may well be a good place to start if you're looking to build your own box.
+[2135.54 --> 2141.96]  But websites like LinuxServer.io, as well as there's a few other things like the self-hosted wiki, self-hosted subreddit.
+[2141.96 --> 2145.20]  But this is the magic of containers, right?
+[2145.30 --> 2147.36]  They allow you to walk before you can run.
+[2147.70 --> 2151.48]  And I think that is a huge tick in the pro column for containers.
+[2152.06 --> 2167.10]  Back in the day, I think a lot of people kind of gatekept Linux because they were like, well, you need to, you know, have your neckbeard badge to be able to do this particular thing on Linux and install these 59 packages in a specific order.
+[2167.10 --> 2172.44]  And then recite some incantations to do, you know, just to get a simple Samba server going.
+[2172.96 --> 2178.94]  Whereas nowadays, you can just, if you want to, run Samba in a container and type Docker run Samba.
+[2179.26 --> 2180.96]  And there's a little more to it than that.
+[2181.08 --> 2185.48]  But effectively, you are now piggybacking off the shoulders of giants, right?
+[2185.56 --> 2187.14]  That's the whole purpose of containers.
+[2187.14 --> 2195.30]  You're basically outsourcing a lot of the sysadmin stuff to other people, like building these containers.
+[2195.70 --> 2203.38]  You're outsourcing those decisions about what goes into them to other people who you maybe trust more than you trust yourself.
+[2203.52 --> 2207.10]  Which, you know, certainly as a newbie is probably a wise decision.
+[2207.10 --> 2214.66]  Maybe as you mature your approach to building systems, you'll decide that actually I know better and I want to go and build my own stuff.
+[2214.84 --> 2217.74]  But I wouldn't say what you're doing is necessarily wrong.
+[2217.88 --> 2221.04]  Just use the stuff that Unraid lets you use.
+[2221.18 --> 2223.00]  There's a reason you picked Unraid, right?
+[2223.08 --> 2226.60]  And that's because it has a simple to use user interface.
+[2226.84 --> 2229.86]  You can use their templates to click and install stuff.
+[2230.00 --> 2231.76]  I mean, keep doing what you're doing, man.
+[2231.92 --> 2232.52]  That's what I say.
+[2232.52 --> 2237.04]  Yeah, you could absolutely just keep using that and you can mess around with VMs on your local box.
+[2237.18 --> 2242.52]  Or if you are ready to build something, I'm going to double down on Alex's recommendation to go by the Perfect Media Guide,
+[2242.70 --> 2246.92]  which I don't know if he said, but is that perfectmediaserver.com?
+[2247.22 --> 2250.18]  Because that gives you the projects to really kind of branch off from there.
+[2250.84 --> 2255.70]  I'm not quite as pro Magic Server Sauce as Alex is.
+[2256.10 --> 2259.26]  That scares the crap out of me a little bit from just a security standpoint,
+[2259.26 --> 2263.66]  because ultimately it's not understanding how the system works that leads people to make security mistakes.
+[2263.78 --> 2266.70]  But I do agree with your point that in most cases,
+[2266.78 --> 2270.16]  the people designing the containers for popular applications and projects
+[2270.16 --> 2273.92]  probably know more about what's going on in there than Rob might.
+[2274.10 --> 2276.76]  You know, the people creating the application know a hell of a lot about it.
+[2276.82 --> 2280.06]  So you're generally going to be all right, but it's definitely worth learning.
+[2280.58 --> 2282.26]  But it's really easy to learn.
+[2282.38 --> 2286.68]  And Rob, I wish the built-in tooling was better at explaining to you,
+[2286.68 --> 2292.08]  like these four containers are using this same layer and it's all possible to discover.
+[2292.22 --> 2298.76]  But I wish it would tell you in terms of like, and that is these applications and this layer of libraries in Linux.
+[2298.86 --> 2303.28]  I wish it was more, if you could understand it in those terms, I think it'd start to click for you.
+[2303.32 --> 2306.96]  So what I would recommend you do is pick a container software of choice,
+[2307.04 --> 2309.48]  go out there and read about Podman, go out there and read about Docker,
+[2309.48 --> 2315.16]  and then start playing, get inside the containers, learn how to do that and explore them
+[2315.16 --> 2318.52]  and just see what that's like and understand what's inside there.
+[2318.60 --> 2321.22]  And then you start to realize, you know, it's good things.
+[2321.30 --> 2322.22]  It's easy to get going.
+[2322.38 --> 2327.40]  It's generally pretty well built, but there's also a lot of old libraries in there sometimes.
+[2327.40 --> 2333.08]  And you're relying on them to update the software and maintain the security for applications you're running on your stack.
+[2333.08 --> 2335.74]  And so you just need to be cognizant of the tradeoffs.
+[2336.16 --> 2337.92]  And I think the way you start that is by learning.
+[2338.08 --> 2343.64]  And then, you know, you can take advantage of tooling around that to maybe get a better insight into what they're doing.
+[2343.94 --> 2346.86]  But ultimately, don't feel bad for using Unraid.
+[2347.24 --> 2349.06]  They are building a good product.
+[2349.24 --> 2354.08]  I think both Alex and I are not currently Unraid users, but we think it's a pretty solid product.
+[2354.26 --> 2361.50]  And I think it's one of those tools that helps people get going and gets their data off of something like Google and gets it on their own land.
+[2361.50 --> 2363.86]  And that's ultimately something that we're both big fans of.
+[2364.22 --> 2365.68]  Yeah, Unraid was how I got started.
+[2366.00 --> 2371.30]  And then I ended up trying to build some packages for myself for some apps that weren't on the platform.
+[2371.64 --> 2381.76]  And like Chris says, trying to exec into a container, like figuring out what that means and sort of getting a shell inside a container and poking around and breaking some stuff.
+[2381.92 --> 2384.04]  You know, that's how I got started.
+[2384.28 --> 2386.24]  So absolutely a good route to go.
+[2386.24 --> 2390.66]  Now, Martin writes in that in the latest episode, you are wondering about one-way phone backup.
+[2391.50 --> 2394.40]  And for Android, he recommends an app called Folder Sync.
+[2394.60 --> 2395.88]  I can't recommend it enough.
+[2396.52 --> 2397.04]  Thank you, Martin.
+[2397.38 --> 2397.88]  Folder Sync.
+[2398.16 --> 2400.86]  We'll have a link to that in the Play Store, as you would imagine.
+[2401.48 --> 2402.12]  Surprise, surprise.
+[2402.42 --> 2408.66]  It allows simple sync to cloud-based storage from your local folders on your phone and SD card on your Android device.
+[2409.46 --> 2411.60]  It does exactly what it says on the tin.
+[2412.04 --> 2412.82]  And it's free.
+[2412.82 --> 2416.12]  It does offer, I guess, an in-app purchase to remove the ads.
+[2416.32 --> 2418.20]  But it looks pretty clean and straightforward.
+[2418.20 --> 2421.20]  Gosh, and it supports everything, it looks like.
+[2421.54 --> 2425.22]  Martin says it automatically recognizes where he is based on SSID.
+[2425.62 --> 2431.78]  And then it backs up to the appropriate local NAS system so that he has multiple physical copies, which is a really nice feature.
+[2432.12 --> 2434.30]  I think I've used an earlier version of this, actually.
+[2434.56 --> 2435.62]  I think I have, and I liked it.
+[2435.62 --> 2440.66]  Now, I use the NextCloud clients on my phones to back up all my photos and things like that.
+[2440.78 --> 2447.08]  Those are primarily the files that are created on my mobile devices that I want to get off of those devices.
+[2447.62 --> 2449.74]  It doesn't require any plugins in NextCloud.
+[2449.90 --> 2453.84]  It's just built into the standard iOS and Android clients as well.
+[2453.84 --> 2462.82]  But I think if I was creating something else regularly on my phone that wasn't a photo or a video, Folder Sync looks like it would be the solution.
+[2463.24 --> 2467.24]  A big thank you to our site reliability engineers at selfhosted.show.sre.
+[2467.36 --> 2469.88]  As a thank you, you get a limited ad version of the show.
+[2470.32 --> 2472.60]  And extra show, you get the post show.
+[2472.96 --> 2479.06]  Today, we're going to chat about Alex's very first computer and how he got his very start in computers.
+[2479.68 --> 2480.66]  I'm looking forward to that.
+[2480.70 --> 2481.90]  I don't think I've ever heard that story.
+[2481.90 --> 2491.38]  So if you would like to join our membership, support the show, and get access to the limited ad version with the post show, go to selfhosted.show.sre.
+[2491.64 --> 2499.12]  And join us next week on Linux Unplugged for a special episode where we go through some of the self-hosted Google Photos alternatives.
+[2499.12 --> 2501.02]  That'll be episode 409.
+[2501.82 --> 2505.14]  Now, for all the ways to get in touch with us, you can go to selfhosted.show.sre.
+[2505.76 --> 2508.44]  And you can find me on Twitter at Ironic Badger.
+[2508.80 --> 2509.72]  You can find me on Twitter.
+[2509.80 --> 2510.80]  I'm at Chris LAS.
+[2510.80 --> 2513.40]  You can find our sponsor, Cloud Guru, on social media.
+[2513.52 --> 2516.50]  They're just slash the Cloud Guru everywhere, like on Twitter.
+[2516.62 --> 2519.26]  The show is at selfhosted show as well.
+[2519.70 --> 2520.66]  And thanks for listening, everybody.
+[2520.94 --> 2523.38]  That was selfhosted.show slash 46.
+[2523.38 --> 2524.84]  Thanks for listening.
+[2524.84 --> 2525.12]  Thanks for listening.
+[2525.12 --> 2525.14]  Thanks for listening.
+[2529.14 --> 2530.10]  Thanks for listening.
+[2530.10 --> 2530.92]  Thema V coin.
+[2531.88 --> 2532.36]  How long is this?
+[2532.36 --> 2533.04]  Must haveith��on Auto 1a.
+[2533.04 --> 2534.02]  In a count image.
+[2534.02 --> 2534.86]  You can find ourselves at self-hosted.
+[2535.40 --> 2535.66]  This is still horsey with a sodium.
+[2536.04 --> 2536.54]  Now, we have a lows.
+[2536.58 --> 2537.62]  You can find ourselves on deck.
+[2537.84 --> 2538.22]  You can find ourselves in the next place.
+[2538.24 --> 2538.72] iqueą.
+[2538.72 --> 2540.14]  lamentableché.
+[2540.14 --> 2540.24]  You can find ourselves outside cosmetics.
+[2540.24 --> 2541.16] у became achoys and began.
+[2541.16 --> 2544.16]  The adding business to our own Fernando Pit face than the United States.
+[2544.28 --> 2545.16]  And this is the only way in order to find ourselves out in scope.
+[2545.16 --> 2546.16]  But would always be the next part of our world.
+[2546.18 --> 2547.06]  The answer is to reach out more questions that we do with us.
+[2547.08 --> 2547.70]  But whether we have some questions in their own włas及opsis because

47： Whose License Is It Anyway？ _summary.txt

@@ -0,0 +1,62 @@
+• Alex has a solar-powered podcasting setup with an 8 kilowatt system
+• The system can run everything, including AC units and servers, solely on solar power for about two hours
+• Alex is considering adding a battery solution to store excess energy
+• He's interested in building his own batteries from old electric car batteries using a DIY approach inspired by YouTube videos
+• Discussion of ZigBee technology for monitoring the solar setup and its use on Mars
+• Alex's solar system includes 24 panels from SolarEdge, with online monitoring and local communication through ZigBee
+• The speaker has issues with remote desktop control on their machines, specifically with TeamViewer
+• They have to reboot a machine remotely, which triggers an admin detection feature in TeamViewer that locks them out for 15 minutes
+• This creates a time crunch as they are trying to go live and can't access the stream despite giving it extra time
+• The speaker considers buying a commercial license for $670 to bypass the issue
+• They decide to purchase the license, feeling frustrated but ultimately wanting to get the show on the air
+• Issues with TeamViewer license activation
+• Alternatives to TeamViewer for remote access
+• Introduction to Rust Desk as a potential replacement
+• Features of Rust Desk, including open-source client and server components
+• Limitations of the free demo server and cost of paid options
+• Potential for community development of a self-hostable Rust Desk server
+• Performance comparison between TeamViewer and the open-source spec implementation
+• Discussion about VNC performance issues and its inclusion in the spec implementation
+• Spec implementation's features and user interface for remote support
+• Comparison to UltraVNC and its RDP support
+• Limitations of the spec implementation, including no Wayland support on Linux
+• TeamViewer's strengths and weaknesses compared to the spec implementation
+• Discussion of drive shucking and current storage market
+• Cryptocurrency and Chia coin affecting hard drive availability and prices
+• Host's plan to buy storage drives in bulk
+• Failure of two Seagate drives despite burn-in tests
+• Data protection measures, including SnapBread and ZFS
+• Promotion of Linode.com for web hosting and cloud services
+• Successful setup of FileRun on Linode using one-click Docker deployment
+• The host discusses Linode and its $100 credit offer for trying out their virtualized cloud computing system.
+• A controversy surrounding Home Assistant developer Frank's request to not have his package repackaged on NixOS.
+• Discussion of the complexities of open-source licensing and intellectual property.
+• Analysis of Frank's responses in GitHub, which were perceived as short, hostile, and snippy by others.
+• The host questions why Frank is concerned about support requests when it seems unlikely that users would contact him directly for help.
+• Concerns about Home Assistant's GPL licensing and potential conflicts with its use of open-source code
+• Paulus deleting a thread on the topic and "cleaning up" the conversation in the forum
+• Fears that the core developers, particularly Frank, are burned out and not able to handle community engagement
+• The issue going public beyond the Home Assistant community, including Hacker News, Reddit, and internal team Slack discussions
+• Discussion of potential scenarios: Home Assistant becoming a commercial product or burning out and abandoning the project
+• Mention of other projects that have made similar transitions (e.g. MB)
+• Analysis of the differences between open-source development and corporate communication, where emotional attachment and petulance are not publicly visible
+• The concept of a "halo engineer" who has too much knowledge and power
+• Concerns about reliance on one person for Home Assistant project's success
+• Discussion of ESP Home, its features and recent updates (version 1.19.0)
+• New tools and improvements in ESP Home, including command line experience and tooling
+• Attribute saving feature in ESP Home from Home Assistant entities
+• Tasmota release 9.5.0 with breaking change affecting MQTT Discovery Protocol
+• Cloud Guru sponsorship announcement for Podman containers on Linux course
+• Discussion of feedback and social interactions without social media
+• Discussion of a tech solution for managing relationships and projects through contact management
+• Introduction to Monica, a self-hosted customer relationship management system
+• Use of Monica for tracking friend's details and setting reminders
+• Water cooling of Raspberry Pis in an RV server seat without cutting holes
+• Exploring water cooling as a heat sink option
+• Electrical system issues with Victron equipment and batteries generating heat
+• Discussion about designing a project that combines water cooling with air circulation and fan usage
+• Mention of an upcoming episode milestone (50) and possibly dedicating time to the project
+• Introduction of an app called Tiny Home, a simple static homepage generator
+• Explanation of how Tiny Home works and its features
+• Brief mention of Google Photo alternatives and a previous podcast on the topic
+• Contact information for the show hosts and a call-out to cloudfree.shop customers about new smart plug availability

47： Whose License Is It Anyway？ _transcript.txt

@@ -0,0 +1,697 @@
+[0.00 --> 1.54]  I'm not sure what it is about you today, Alex.
+[1.58 --> 3.00]  You just kind of have a glow about you.
+[3.00 --> 7.22]  This episode of Self-Hosted is brought to you by the sun.
+[8.22 --> 10.14]  Solar-powered podcasting.
+[10.18 --> 11.22]  That is awesome.
+[11.34 --> 11.72]  Yeah, man.
+[12.10 --> 12.40]  Wow.
+[12.64 --> 18.30]  Yeah, and you've got quite the solar setup, I mean, compared to the one that I have on my RV roof, which is a lot smaller.
+[18.90 --> 20.36]  You've got a lot more roof to work with.
+[20.38 --> 22.64]  I don't have a need to drive it down the road, do I?
+[22.74 --> 25.52]  So, yeah, I've gone for an eight kilowatt solar system on my roof.
+[25.96 --> 26.46]  That's great.
+[26.56 --> 29.78]  And so it actually means, like, legitimately, it's running everything.
+[29.78 --> 44.62]  On a day like today in the middle of June, when the sun is beating down real hard all day, I can actually run both my AC units, all my servers, the fridges, the TVs, everything, 100% on solar for about two hours.
+[45.28 --> 50.94]  And I know something that's on your mind is, like, eventually putting some sort of battery solution in there.
+[51.36 --> 53.08]  There's, of course, reasonable solutions.
+[53.08 --> 61.48]  But if you could just Star Trek Q style, snap your fingers and have a battery solution materialize out of thin air, what would be your ideal setup?
+[61.94 --> 63.64]  You know how I like to make stuff.
+[63.64 --> 70.98]  I've been watching videos of this guy called, I think, is it Jerry Garcia or something like that on YouTube for years.
+[71.32 --> 77.78]  And he builds his own batteries, power walls, out of old electric car batteries.
+[78.60 --> 78.72]  Yeah.
+[78.80 --> 79.50]  That's what I want to do.
+[80.00 --> 80.16]  Yeah.
+[80.16 --> 86.86]  I just think that'd be the coolest thing in the world because cars need a very high peak voltage to accelerate the mass of the vehicle.
+[87.40 --> 91.66]  Whereas a house is a much more constant, much less peaky load than that.
+[91.72 --> 98.42]  So you can get away with old, air quotes, dead car batteries that are actually suitable for houses.
+[98.42 --> 102.44]  You know what I didn't even appreciate earlier is that you had your air conditioning going.
+[102.70 --> 109.44]  Two units as well because I live in one of these crazy big American houses that has a unit per story.
+[110.90 --> 112.12]  That's so cool, though.
+[112.20 --> 117.08]  I mean, you're, like, not even hitting, like, the power grid to run air conditioning.
+[117.38 --> 118.50]  That's awesome.
+[118.62 --> 118.76]  Yeah.
+[119.28 --> 124.94]  At one point today, the solar was reporting 6.4 kilowatts of power.
+[125.16 --> 127.26]  So 6,400 watts, I suppose.
+[127.26 --> 130.72]  I dream one day of building a big array.
+[131.16 --> 135.98]  Just something, even something around that size, I think, would be perfect for what I have envisioned for the future.
+[136.04 --> 136.72]  24 panels.
+[137.02 --> 140.06]  I think SolarEdge is the company that I went with.
+[141.04 --> 141.48]  Yeah.
+[141.60 --> 146.62]  And they've got an online monitoring platform, which Home Assistant, of course, talks to.
+[146.90 --> 152.80]  And there's a local ZigBee gateway that talks to the inverter as well to provide that information.
+[153.30 --> 155.14]  In fact, when they were installing it, it was kind of funny.
+[155.14 --> 158.78]  The installer knocked on my door and said, hey, where's your router?
+[159.26 --> 160.10]  And I'm like, hmm.
+[162.32 --> 163.40]  Is that your yank?
+[164.78 --> 164.98]  Router?
+[165.82 --> 168.22]  Why do you want access to my router?
+[168.84 --> 172.72]  And he was like, oh, I've got this ZigBee box I want to plug in.
+[172.90 --> 173.84]  And I'm like, why?
+[174.18 --> 176.26]  And he told me about everything it does.
+[176.34 --> 177.56]  And I thought, oh, that's so cool.
+[177.98 --> 179.04]  And I was like, what do you need?
+[179.10 --> 180.44]  He goes, I just need an Ethernet port.
+[180.44 --> 182.22]  I'm like, oh, oh, OK.
+[182.40 --> 183.18]  I got you covered.
+[184.26 --> 185.20]  That's pretty great.
+[185.80 --> 189.68]  So now it's connected up and it all talks back to the equipment over ZigBee.
+[189.78 --> 190.58]  Wow, that's wild.
+[190.96 --> 196.64]  That is, you know, we also learned recently that ZigBee is used on the Mars helicopter
+[196.64 --> 197.44]  opportunity.
+[197.68 --> 198.74]  Or no, I'm sorry, ingenuity.
+[199.08 --> 201.58]  And that's how it talks back to the Mars rover is over ZigBee.
+[201.58 --> 201.78]  Really?
+[201.90 --> 202.36]  That's cool.
+[203.02 --> 203.20]  Yeah.
+[203.20 --> 208.48]  So ZigBee's getting used on Mars to communicate with the little drone helicopter.
+[209.06 --> 209.72]  Well, that's pretty cool.
+[209.78 --> 213.22]  I'll be interested to follow your journey to see how that setup evolves.
+[213.76 --> 216.72]  And then eventually I can't wait to hear stories of you up there on the roof trying to clean
+[216.72 --> 218.48]  those panels after some storm or something.
+[218.66 --> 218.76]  Oh, God.
+[218.96 --> 219.74]  Yeah, you know it's coming.
+[221.26 --> 221.66]  Yeah.
+[222.12 --> 225.74]  Well, I have a confession to make before we get too far into the show.
+[225.82 --> 228.26]  So first, I want to tell you about our friends at A Cloud Guru.
+[228.64 --> 230.06]  This episode is brought to you by them.
+[230.06 --> 233.38]  They are the leader in learning for the cloud, for Linux and other modern tech skills.
+[233.58 --> 235.48]  Hundreds of courses, thousands of hands-on labs.
+[235.58 --> 238.98]  Get certified, get hired, get learning at acloudguru.com.
+[240.14 --> 248.76]  So while I was in Montana, I decided to be just, I guess, like extra challenging and give
+[248.76 --> 250.38]  myself more stress during my trip.
+[250.38 --> 255.30]  I decided to just to kind of throw a wrench at everything and do a episode of Coda Radio
+[255.30 --> 257.30]  live on the road.
+[257.30 --> 261.96]  Not that this is impossible, but when, you know, I've pre-recorded everything and I'm
+[261.96 --> 265.92]  only doing one live show on the road, like I'm not really in the right headspace.
+[266.04 --> 267.60]  I haven't really checked everything out.
+[267.68 --> 271.00]  I didn't really think through it methodically like I would if it was a whole series of shows
+[271.00 --> 272.04]  I'm going to produce.
+[272.04 --> 280.46]  And one of the things I didn't really have dialed in before I left for Montana was remote desktop
+[280.46 --> 281.06]  control.
+[281.16 --> 282.76]  And it has to be remote desktop.
+[282.90 --> 283.98]  It can't be SSH.
+[284.04 --> 287.76]  I actually have to see the console because of the audio tools we use in our mixer.
+[288.46 --> 289.76]  I have to see the console.
+[290.38 --> 292.96]  And I thought, well, you know what I'll do?
+[293.36 --> 295.44]  I know I shouldn't do this, but I don't have time.
+[295.44 --> 299.70]  I'm going to throw TeamViewer on these machines.
+[300.16 --> 303.52]  And when I'm in Montana, I'll pull up TeamViewer and I'll get everything working.
+[303.62 --> 304.86]  I'll get the stream up over TeamViewer.
+[304.92 --> 305.38]  It'll be fine.
+[306.92 --> 309.02]  And for about five minutes, it was.
+[309.20 --> 310.82]  I got I got remoted in.
+[310.98 --> 313.74]  I realized, oh, this machine, you know, it's not running quite right.
+[313.82 --> 314.98]  It needs to be rebooted.
+[314.98 --> 318.78]  So I restarted the machine I was remoted into, which is fine, right?
+[319.24 --> 319.76]  That's fine.
+[320.00 --> 321.22]  It comes back up.
+[322.14 --> 329.50]  And TeamViewer, it has like some detective code in there that detected that I was doing
+[329.50 --> 333.76]  admin like functions, remoting into a machine, rebooting and then trying to reconnect to
+[333.76 --> 334.70]  it after a few minutes.
+[334.84 --> 340.72]  And it detected that I was doing these admin like functions and then disabled my ability
+[340.72 --> 342.32]  to connect for like 15 minutes.
+[342.32 --> 347.92]  Now, that sucks because I'm an hour out from going live and I want to get the stream up.
+[348.16 --> 351.36]  I like to get the stream up about an hour before we start so people can start, you know,
+[351.38 --> 353.76]  assembling 15 minute timeout.
+[353.84 --> 355.36]  OK, so I go about and I do my other things.
+[355.42 --> 356.70]  I set other stuff up.
+[357.04 --> 359.80]  15 minutes goes by and I may be getting the time window wrong.
+[359.86 --> 362.34]  This was a few weeks ago, but that 15 minutes goes by.
+[362.44 --> 363.16]  I reconnect.
+[363.66 --> 364.40]  Nope, sorry.
+[365.30 --> 366.46]  Admin activity detected.
+[366.66 --> 367.82]  You have to wait 15 minutes.
+[368.70 --> 369.30]  Oh, man.
+[370.10 --> 371.62]  So I keep going, setting up.
+[371.62 --> 373.56]  Now I'm like a half hour.
+[373.94 --> 375.70]  Actually, I let extra time go by just in case.
+[375.76 --> 378.72]  And now I'm like I'm at the 40 minute mark.
+[379.34 --> 380.96]  Show starts at the top of the next hour.
+[381.64 --> 383.22]  So I'm like trying to get connected.
+[383.54 --> 384.70]  I gave it extra time.
+[384.78 --> 386.52]  I gave an extra like 5, 10 minutes.
+[386.80 --> 387.72]  I connect again.
+[388.40 --> 388.80]  Nope.
+[389.02 --> 389.68]  Admin detected.
+[390.18 --> 390.88]  Can't connect.
+[391.28 --> 392.46]  Now I'm starting to get panicked.
+[393.04 --> 394.02]  Now I can't get on.
+[394.08 --> 395.22]  Now I can't get on the internet.
+[395.28 --> 396.54]  I can't get on this live stream.
+[396.58 --> 397.40]  I can't get that going.
+[397.40 --> 400.80]  You know, Mike doesn't know he's going to be connecting, expecting me to be there.
+[400.80 --> 404.22]  The audience is starting to show up in the chat room asking where the stream's at.
+[404.28 --> 405.10]  It's starting to get stressful.
+[406.68 --> 412.88]  So, you know, I go into business mode and I think to myself, look, you jackass, it's like
+[412.88 --> 419.56]  $670 to just buy the commercial license and then you can get access to your machines and
+[419.56 --> 420.32]  you can do your show.
+[421.04 --> 422.78]  You're going to be traveling more this year.
+[423.40 --> 425.08]  Just just pay the damn price.
+[425.08 --> 427.76]  So I think about it.
+[427.84 --> 429.54]  I know I could self host this.
+[429.62 --> 430.92]  I know I shouldn't do this.
+[432.04 --> 433.58]  But I want to get on the air.
+[434.02 --> 436.16]  The show starts in just a few minutes.
+[436.64 --> 438.22]  So I head over to team viewer site.
+[438.38 --> 441.76]  I get all logged in, make sure it's all my account stuff is correct.
+[443.28 --> 447.18]  And I subscribe to the annual like $670 plan.
+[447.36 --> 448.52]  That's a lot of greenbacks.
+[449.30 --> 451.08]  Oh, it hurts so bad.
+[451.08 --> 457.10]  I mean, I've I've paid more for other subscriptions, but this one in particular, because of how
+[457.10 --> 458.14]  they got me into it.
+[459.28 --> 462.84]  And because I needed I needed to just do this once, you know, like the way they got me into
+[462.84 --> 465.28]  this, but I knew I OK, if I might need to do it more.
+[465.38 --> 465.94]  All right, I'll pay.
+[466.02 --> 467.04]  I'll pay their license.
+[467.68 --> 468.04]  Fine.
+[468.32 --> 470.32]  It says instant activation right at the top of the website.
+[470.32 --> 471.58]  So I think I'm going to be golden.
+[473.66 --> 479.72]  Well, it was Labor Day and the team viewer staff was off that day, Alex, and nobody was
+[479.72 --> 481.50]  there to issue me my license.
+[481.82 --> 482.92]  Wait, that's not automated.
+[483.82 --> 485.00]  That's not instant either.
+[485.30 --> 488.10]  And so the time comes.
+[488.20 --> 489.24]  We're like five minutes.
+[489.40 --> 490.60]  I still haven't gotten activated.
+[490.68 --> 492.72]  In fact, it took till the next day until I got activated.
+[493.00 --> 493.86]  I was so angry.
+[495.14 --> 500.70]  But I figured out that if I did a new install on a new Linux box and connected from the first
+[500.70 --> 504.72]  time from that machine to the other machine that I was getting blocked on, I could do it
+[504.72 --> 506.22]  from that machine with the free account.
+[506.22 --> 510.14]  And I got the stream up and running with like two minutes to spare.
+[510.78 --> 516.20]  And I had to then like just let all of that fade and just focus on the show and sit with
+[516.20 --> 520.26]  the fact that I spent that nearly $700 and still didn't have the license.
+[520.32 --> 522.06]  And I just had to sit with that while I did the show.
+[523.20 --> 530.72]  And so I in that moment resigned myself to find a free self-hostable replacement for team
+[530.72 --> 530.94]  viewer.
+[531.28 --> 533.12]  I would not let this happen to me again.
+[534.08 --> 535.42]  And I did some shopping.
+[535.42 --> 537.84]  I found a couple of different options.
+[538.38 --> 538.58]  I don't know.
+[538.62 --> 541.38]  Have you looked in this area yourself before a team viewer replacement?
+[541.56 --> 545.78]  No, they've never actually got me with that admin stuff detected.
+[545.90 --> 549.50]  I used to use it quite a bit to help family members back in the day.
+[549.64 --> 555.32]  But lately, I don't know, technology's matured to the point where I don't often need to remote
+[555.32 --> 556.42]  into their systems anymore.
+[556.42 --> 563.30]  Well, and in a lot of cases, something like WireGuard with VNC would do mostly what you
+[563.30 --> 564.84]  need in a lot of cases.
+[565.22 --> 567.98]  But in my case, I sometimes am behind a double NAT.
+[568.06 --> 569.32]  I need to be able to traverse that.
+[569.40 --> 570.92]  I need to do it from a mobile device.
+[570.98 --> 574.44]  I need to be able to do it from a Linux box, a Mac box, anything like that.
+[574.44 --> 576.04]  Yeah, that's where team view is really nice.
+[576.12 --> 577.90]  It just punches through everything.
+[578.76 --> 581.06]  So if you've never used it before, it's pretty slick, actually.
+[581.24 --> 585.92]  You type in a nine-digit code, which identifies the other person's server.
+[586.34 --> 589.52]  And then they give you a five or six-character password that you type in.
+[590.32 --> 592.26]  And yeah, that's how you do it.
+[592.28 --> 593.10]  You just connect like that.
+[593.18 --> 598.18]  It punches through every firewall, inbound, outbound, whatever, bounces off their servers
+[598.18 --> 598.94]  and just works.
+[598.94 --> 603.16]  And it makes those remote support situations so much more streamlined with that code.
+[603.64 --> 604.80]  And it's simple.
+[605.32 --> 612.36]  I tried a few things and Rust Desk came across my, I don't know, maybe it was an email, but
+[612.36 --> 613.40]  it came across my path.
+[613.66 --> 617.92]  And if you did send it to the show, thank you, because I eventually did get a chance to
+[617.92 --> 618.52]  try it out.
+[618.64 --> 621.10]  And I really, really like Rust Desk.
+[621.10 --> 633.20]  As the name implies, it is built in Rust.
+[633.76 --> 636.68]  The client, the front end, is open source.
+[636.88 --> 640.88]  They have one for basically every major OS, including your Linuxes out there.
+[641.34 --> 643.18]  The front end client is really clean and simple.
+[643.42 --> 647.02]  It's a lot like a simplified front end for TeamViewer.
+[647.02 --> 652.08]  It runs as a back end service on Linux, so you don't even necessarily have to have it
+[652.08 --> 653.20]  up and running on your screen.
+[653.28 --> 654.64]  It'll install itself as a service.
+[655.28 --> 656.50]  There is a server component.
+[656.92 --> 659.42]  Now, by default, you can use their server.
+[659.92 --> 661.90]  You can use their server.
+[662.14 --> 663.70]  I think there's really no restrictions on it.
+[663.72 --> 667.56]  I was able to connect to three machines simultaneously using their free server.
+[668.42 --> 672.84]  They do say, though, right on their front page, our server resources are limited, so please
+[672.84 --> 674.40]  set up your own server.
+[674.40 --> 677.38]  And that's where this gets a little tricky.
+[677.90 --> 686.48]  You can pay $200 a year, which is a lot less than $700 for their server, which is all set
+[686.48 --> 691.16]  up and nice and lets you do all kinds of connections, and you can run it on your own box for a year.
+[692.02 --> 694.72]  But, you know, $200 is a lot for some people.
+[694.82 --> 698.76]  So they've also made a demo server available is what they call it.
+[699.04 --> 701.64]  Now, this demo server is significantly limited.
+[701.64 --> 705.62]  Only one relay connection allowed, no NAT traversal.
+[706.14 --> 709.58]  You really kind of have to be prepared for like a very limited experience.
+[709.78 --> 712.18]  But it's a demo server that's quote unquote free.
+[712.32 --> 712.96]  It's open source.
+[713.46 --> 715.18]  You could run it on your machine right now.
+[715.26 --> 716.96]  They make a Docker container available for it.
+[717.74 --> 723.68]  But because it's open source, the community could, in theory, take their spec implementation
+[723.68 --> 729.24]  and build a more feature complete, self-hostable Rust desk server.
+[729.24 --> 734.00]  And I think if Rust desk continues to take off and really makes itself an appealing alternative
+[734.00 --> 738.04]  to TeamViewer, I could really see the community stepping up and taking the spec implementation
+[738.04 --> 740.92]  that they make available for free and building it into something else.
+[741.06 --> 742.26]  So I'm kind of going all in.
+[742.30 --> 745.42]  I loaded it on all the machines that I would need to build a remote support in the studio.
+[745.82 --> 746.48]  How's the performance?
+[746.66 --> 747.56]  A lot of these things.
+[747.64 --> 749.30]  You mentioned VNC a few minutes ago.
+[749.84 --> 755.04]  I just have memories of that thing just not working very well or not updating the cursor
+[755.04 --> 757.12]  unless something's moving elsewhere on the screen.
+[757.40 --> 758.06]  How's this work?
+[758.06 --> 758.68]  Oh, yeah.
+[758.74 --> 760.46]  So many old cursor problems with VNC.
+[761.08 --> 766.02]  And are watching like the screen paint as you wait.
+[766.74 --> 767.94]  No, it's good.
+[768.04 --> 768.46]  It's great.
+[768.54 --> 771.56]  In fact, I'd say it is absolutely comparable with TeamViewer's performance.
+[772.44 --> 775.40]  I didn't get a chance to dig in under the hood to see what they're using.
+[775.60 --> 781.48]  If they're using VNC, it is absolutely by far the fastest, bestest, most incredible
+[781.48 --> 783.28]  implementation of VNC I've ever seen.
+[783.60 --> 786.40]  I'd suspect it must be something else, though, because the performance is great.
+[786.40 --> 787.68]  There's no mouse ghosting.
+[788.54 --> 793.34]  And I was absolutely happy, even while having three connections going simultaneously.
+[794.02 --> 796.72]  Well, that's the beauty of it being open source, right?
+[797.42 --> 798.54]  We can go and have a look if we want.
+[798.96 --> 799.36]  You can.
+[799.50 --> 800.50]  We could go dig around it.
+[800.50 --> 804.02]  In fact, if the community has another one that they like, I know there's a few out there
+[804.02 --> 805.76]  that kind of are trying to solve this problem.
+[805.90 --> 806.36]  Let us know.
+[807.12 --> 808.96]  Selfhosted.show slash contact.
+[808.96 --> 813.14]  Now, just looking through the source code, I mean, there's a file in the source called
+[813.14 --> 818.32]  windows.cc, and it mentions UltraVNC has RDP support.
+[818.58 --> 822.64]  Do you need to use a normal VNC client for this, or do they provide everything that you
+[822.64 --> 822.90]  need?
+[823.16 --> 823.32]  Yep.
+[823.36 --> 828.60]  They bring you install the client on your OS, and you can set up a session ID.
+[828.70 --> 829.86]  You plug it in there, and it connects.
+[830.10 --> 834.24]  Once you connect once, it saves it in a recent sessions area, so you can just double click
+[834.24 --> 835.64]  to reconnect to the machine again.
+[835.64 --> 840.92]  Then once you're in there, you get a viewer that lets you scale the screen image or set
+[840.92 --> 845.12]  it to the actual resolution, and it has a little bar along the top that lets you switch between
+[845.12 --> 848.50]  multiple monitors if you're remoting into a system that has multiple screens.
+[848.88 --> 853.20]  It also gives you a few other quick options that you might want, like send a few keystrokes
+[853.20 --> 854.58]  and stuff like that.
+[855.22 --> 859.96]  And the UI, when you launch it, either to connect to someone or if you want to allow an inbound
+[859.96 --> 863.58]  connection, it's just that one UI, and it gives you your ID, and you set a password
+[863.58 --> 864.42]  right there.
+[864.42 --> 865.16]  Very cool.
+[865.28 --> 865.40]  Yeah.
+[865.40 --> 866.58]  That looks like a great project.
+[866.86 --> 868.08]  One caveat, though.
+[869.06 --> 873.78]  Unfortunately, at this time, it does not support Wayland on Linux.
+[874.04 --> 874.64]  Oh, God.
+[875.26 --> 877.46]  Why is there always a gotcha like this?
+[877.94 --> 880.36]  Well, it's the nature of the Linux desktop right now.
+[880.64 --> 882.88]  But thankfully, all of our studio systems...
+[882.88 --> 884.14]  TeamViewer works on Wayland.
+[884.36 --> 884.96]  Yes, it does.
+[885.08 --> 885.62]  It does.
+[885.78 --> 886.70]  And I'm actually...
+[886.70 --> 891.56]  That is one thing I have to give TeamViewer credit for, and why I went with it is, even
+[891.56 --> 894.12]  though it gets a lot of hate in the technical community.
+[894.12 --> 899.34]  Legitimately, they have been supporting a Linux release now for a very long time.
+[899.34 --> 901.50]  And they support Wayland.
+[901.50 --> 903.50]  They support Gnome Shell, Plasma.
+[903.74 --> 905.10]  Their integration is top-notch.
+[905.62 --> 906.58]  And I got to give them credit for it.
+[906.64 --> 907.62]  Like, they've built a good product.
+[907.70 --> 908.96]  That's why I was willing to pay for it.
+[909.44 --> 912.30]  It's just the way that went about the delay in it.
+[912.34 --> 915.88]  And then the fact that I have to pay that every single year, it's just not my bag.
+[916.22 --> 917.98]  And I always prefer to self-host if I can.
+[918.36 --> 920.60]  And now I just have to decide, do I want the spec server?
+[920.86 --> 924.00]  Or do I want to pay for the Rust desk server?
+[924.62 --> 925.56]  I got to make that decision.
+[925.76 --> 927.96]  But I'll play with it some more and decide in the future.
+[928.46 --> 928.64]  All right.
+[928.64 --> 929.04]  Very good.
+[929.04 --> 930.26]  Now, moving on.
+[930.38 --> 932.90]  Have you seen this website, shucks.top?
+[933.26 --> 934.68]  No, I've never heard of this.
+[934.84 --> 935.72]  What is this?
+[935.96 --> 938.22]  Somebody put it in the Discord, of course.
+[938.82 --> 944.24]  And this website lists you all the different drives that are suitable to be shucked.
+[944.30 --> 945.68]  You know how I like shucking drives.
+[945.86 --> 946.16]  I do.
+[946.50 --> 951.80]  And normally, it's a dashboard of which retailer has which shuckable drive on sale.
+[951.80 --> 966.24]  But right now, thanks to crypto and this annoying new Chia coin thing that you can mine coins on hard drives, apparently, hard drives, just like everything else now, are in short supply.
+[967.08 --> 967.86]  You've got to be kidding me.
+[967.92 --> 968.12]  Really?
+[968.52 --> 968.76]  Yeah.
+[968.98 --> 969.40]  No.
+[969.60 --> 975.20]  I want storage prices to be going down right now because I have a big plan to buy a lot of disk around November.
+[975.98 --> 976.70]  Dang it.
+[976.70 --> 981.40]  So, you know, yeah, you're a big shucker for those of you who don't know the term.
+[981.80 --> 987.96]  You get a USB enclosure hard drive and you shuck that enclosure and you get the disk out of it.
+[988.04 --> 988.90]  You know, it's like a coconut.
+[989.42 --> 991.68]  You get the husk off and you pull out the coconut.
+[992.36 --> 997.12]  And sometimes it's delicious and sometimes it's not so good.
+[997.40 --> 999.14]  Well, sometimes it isn't so good.
+[999.18 --> 1003.42]  Actually, this week, I've had two hard drives sale on me this week.
+[1003.50 --> 1005.24]  Both shucked Seagates.
+[1005.44 --> 1006.38]  Oh, no, man.
+[1006.38 --> 1012.40]  I've got a bunch of older Western digital drives that are approaching three years old.
+[1013.16 --> 1022.74]  And so what I wanted to start doing was buying a disk every quarter, give or take, to start kind of staggering their dates so that the bathtub curve, I don't fall victim to that.
+[1022.74 --> 1032.92]  Which is, you know, if everything's the same age with the same environmental life conditions, the chances that they're going to fail all at the same time is reasonably high.
+[1033.00 --> 1036.30]  So I wanted to try and protect myself from that a little bit.
+[1036.30 --> 1039.50]  And so I bought a couple of these Seagate drives earlier in the year.
+[1039.60 --> 1040.84]  I think I talked about it on the show.
+[1041.42 --> 1056.92]  And both of these Seagate 10 terabyte, what are they, Barracuda Pros, have both just decided this week, at exactly the same time, despite my burn-in tests and everything else, that this week was the week they were going to give up the ghost.
+[1057.62 --> 1058.04]  Oh, man.
+[1058.04 --> 1059.24]  I'm so sorry to hear that.
+[1060.04 --> 1061.64]  Nobody ever wants to deal with that.
+[1061.72 --> 1062.68]  Any data loss happen?
+[1062.94 --> 1063.94]  No, no data loss.
+[1063.94 --> 1067.10]  One of the drives was being used in ZFS and the other one was on MergerFS.
+[1067.46 --> 1071.10]  So SnapBread did its thing perfectly and so did ZFS.
+[1071.42 --> 1072.58]  So we're all good, baby.
+[1074.70 --> 1076.78]  Linode.com slash SSH.
+[1076.84 --> 1079.54]  Go there to get $100 in credit and support the show.
+[1079.68 --> 1084.96]  No matter what skill level you're at or what technology stack you use, Linode can help your ideas come to life on the web.
+[1085.32 --> 1086.32]  You're going to be impressed.
+[1086.58 --> 1089.58]  And when you get that $100, you can really try it out.
+[1089.72 --> 1092.40]  Alex, I don't think I told you yet, but I set up FileRun.
+[1092.40 --> 1094.72]  You recommended it to us on Linux Unplugged.
+[1094.94 --> 1095.48]  Oh, good.
+[1095.82 --> 1096.16]  Yeah.
+[1096.40 --> 1096.54]  Yeah.
+[1096.58 --> 1102.34]  I set up a Linode a couple of – well, it's been about a week now for the Elementary Development Summit.
+[1102.70 --> 1107.22]  And they're using FileRun to upload all of their videos and stuff for the summit.
+[1107.98 --> 1114.26]  We were going to do a NextCloud instance, but just FileRun seemed to make so much more sense, a lot more straightforward for the presenters too.
+[1114.66 --> 1115.40]  Way simpler.
+[1115.40 --> 1117.32]  And it was really easy.
+[1117.50 --> 1125.20]  I've told the story before, but it actually got – I got it all set up using Linode's one-click Docker deployment, which is – in my case, I chose Debian, but you got a couple options there.
+[1125.62 --> 1130.56]  Debian, Docker Basic setup with Docker Compose pre-installed and all of the right repos set up.
+[1130.56 --> 1140.14]  And so I deploy that, and then I just grab the Docker Compose from the project for FileRun and had it up and running before the DNS had switched over for the website.
+[1140.76 --> 1142.76]  And it was just like a no-brainer.
+[1142.90 --> 1145.22]  And then later on, of course, Wes.
+[1145.22 --> 1146.34]  Wes is always like, you know what we could do?
+[1147.06 --> 1155.42]  We could mount the S3 object storage and then use that for the storage for FileRun so we don't have to worry about them filling up the disk.
+[1155.42 --> 1157.56]  And I'm like, of course, I'm on board with that.
+[1157.78 --> 1160.24]  I love stacking those Linode services together.
+[1160.68 --> 1162.80]  Their dashboard makes us really simple and straightforward.
+[1162.96 --> 1165.12]  You can use their cloud firewall to protect your system.
+[1165.44 --> 1167.44]  Then you can deploy a Linode to run your application.
+[1167.76 --> 1174.00]  And then you can use object storage on the back end to essentially have addressable storage that expands as you need it.
+[1174.26 --> 1178.04]  Now, there's a lot of ways to crack that, and if any of that sounds complicated, don't worry.
+[1178.12 --> 1183.38]  It's also really simple to just get started with a standard box, really easy with just a couple of clicks.
+[1183.38 --> 1186.84]  It's a great opportunity to learn with that $100 credit as well.
+[1187.14 --> 1190.22]  They have this powerful system with this simple interface.
+[1190.74 --> 1195.38]  So many people make that claim, but it's actually extremely hard to get that balance right.
+[1195.64 --> 1200.46]  And the reason why Linode gets it right is because they've been attempting this since 2003.
+[1200.94 --> 1204.94]  And through just working at this and listening to their customers and building it,
+[1205.10 --> 1211.20]  just focused on delivering the best virtualized cloud computing and having that focus since 2003,
+[1211.20 --> 1214.98]  they've gotten to this point where they have this marvelous system now.
+[1214.98 --> 1219.60]  So go use our $100 credit at linode.com slash SSH to try it out.
+[1219.96 --> 1221.92]  And yeah, the performance is fantastic too.
+[1222.20 --> 1223.34]  We love getting your stories.
+[1223.48 --> 1225.24]  So let us know how your switch to Linode has gone.
+[1225.62 --> 1227.70]  Linode.com slash SSH.
+[1227.70 --> 1232.32]  Now I'm reluctant to even bring this up, to be honest with you,
+[1232.38 --> 1239.24]  because the open source community is well known for over-egging the pudding when it comes to drama.
+[1240.02 --> 1245.04]  But the more I dug into this story, the more I felt like it was worth the discussion on the show.
+[1245.04 --> 1252.60]  So this week, Home Assistant developer Frank, you've probably seen his name everywhere over Home Assistant.
+[1252.74 --> 1258.38]  He is a prolific contributor to the project, spelled F-R-E-N-C-K.
+[1258.90 --> 1267.24]  He jumped into a NixOS GitHub pull request and made what seems on the face of it like a really simple request.
+[1267.24 --> 1274.48]  He says, as the author of the package, I'm asking it to not be repackaged here.
+[1275.44 --> 1276.64]  Sounds straightforward enough, right?
+[1277.32 --> 1277.72]  I suppose.
+[1277.98 --> 1282.84]  I mean, it's MIT licensed, so he doesn't really have the authority to make that request.
+[1283.10 --> 1284.08]  Well, that's just it, isn't it?
+[1284.28 --> 1284.50]  Yeah.
+[1284.58 --> 1286.94]  I mean, there's the spirit of the developer's intention.
+[1287.48 --> 1291.18]  And then there's the letter of the law, which says that NixOS,
+[1291.18 --> 1300.90]  which is a Linux distribution that's very technical, very niche, and very awesome if you're into declared systems that are kind of just super, super niche.
+[1301.42 --> 1306.60]  NixOS is great, but it is a Linux distribution just like Ubuntu or Debian.
+[1306.84 --> 1308.70]  They package these things up into their own repos.
+[1309.22 --> 1313.62]  Well, here's the thing as well, right, is that NixOS is all about reproducible builds.
+[1314.12 --> 1320.96]  But for some reason, Fedora felt the need to package this ambi Python library as well.
+[1321.42 --> 1330.16]  And as the thread transpired on GitHub, Frank started to get a little more petulant, dare I say, as time went by.
+[1330.46 --> 1336.26]  You know, he started off by saying, I have no emotional investment, no emotional attachment to this issue.
+[1336.88 --> 1343.90]  And then a few posts later, this is, this, by the way, has moved out of GitHub onto the Home Assistant forum by this point.
+[1343.90 --> 1352.80]  He goes from saying, I've got no emotional attachment to saying, sorry to hear you don't respect requests from authors who wrote the source you rely on,
+[1353.16 --> 1356.16]  the author that has put in the effort to create it in the first place.
+[1356.58 --> 1358.66]  Always good to know a project doesn't care.
+[1359.52 --> 1360.90]  I mean, come on.
+[1360.90 --> 1366.60]  In my opinion, I would characterize a lot of his responses as short and somewhat hostile and snippy.
+[1367.30 --> 1373.94]  People ask him, like, they come back with very reasonable counter suggestions and proposals that are well thought out.
+[1374.28 --> 1380.22]  And he responds with trite one sentence responses that are sort of demeaning.
+[1380.22 --> 1380.70]  Yeah.
+[1380.98 --> 1388.54]  One example of that is that Nick's OS offered, we will set a config flag in the OS that reads,
+[1389.28 --> 1396.98]  accept that this package is not supported by upstream developers and I will go to Nick's packages to report any issues equals true.
+[1397.98 --> 1400.20]  And Frank was still unhappy with that.
+[1400.20 --> 1410.12]  So here's what I think here, Alex, because the core argument that Frank had was he was concerned this would lead to user support requests on him.
+[1410.42 --> 1416.00]  He was concerned that people would install Home Assistant and all of these packages and dependencies on Nick's OS,
+[1416.52 --> 1421.24]  run into some problem with their setup at some point that led them to the Ambi library.
+[1421.24 --> 1434.46]  And then from there, they would dissect the source code and the original author suss out his contact information or his GitHub and then file a issue support request or email with Frank after that process.
+[1434.76 --> 1449.20]  Now, I've been in this for quite a while and I could tell you, I'd bet you a good steak dinner that the totality of people that would do that over, say, like a five to 10 year period would probably be a handful, you know, under a dozen.
+[1449.20 --> 1454.78]  Because let's be honest, Nick's OS is an extremely niche Linux distribution.
+[1455.78 --> 1458.28]  Then the ability to ascertain who the developer is.
+[1458.36 --> 1465.42]  Well, actually, the ability to ascertain what particular library is even causing you a problem is a niche skill set.
+[1465.54 --> 1471.86]  The ability to ascertain which developer created that one library that's creating you a problem is also a niche skill set.
+[1471.94 --> 1472.58]  So you get my point?
+[1472.66 --> 1478.40]  Like it's his main concern was that he'd be getting support requests when in reality that just doesn't seem likely.
+[1478.40 --> 1481.38]  That's not going to that's not going to result from this inclusion in Nick's OS.
+[1481.78 --> 1489.80]  Which raises the question, you know, if you don't want your stuff to be used and packaged by other people like this.
+[1489.86 --> 1494.94]  I mean, the whole point of open source licensing is that you're giving your code away.
+[1495.10 --> 1497.32]  You still retain intellectual property over it.
+[1497.40 --> 1499.40]  You still, air quotes, own it.
+[1499.40 --> 1503.10]  But you don't own what people can do with it.
+[1503.60 --> 1511.24]  And for me, that raises the question, why is he even publishing it as open source code in the first place if he doesn't want people to do this?
+[1511.50 --> 1512.88]  Yeah, that's that's a good question.
+[1513.02 --> 1520.18]  It's a tricky one, because if you think about the way in which Home Assistant itself is licensed, that uses the permissive Apache 2 license.
+[1520.18 --> 1525.22]  And that doesn't really impose very many restrictions at all on derivative works.
+[1525.44 --> 1536.58]  If Home Assistant then includes any GPL licensed stuff, at that point, you then have a whole other can of worms about what would what would happen next.
+[1536.58 --> 1546.94]  And I think for me, I get a little concerned when I see how Paulus, who was on the show a couple of episodes ago, jumped into that Home Assistant thread.
+[1547.14 --> 1549.30]  All of these links will be in the show notes, by the way.
+[1550.50 --> 1556.86]  And basically just locked the thread, closed it and then delisted it, like sweeping the whole thing under the rug.
+[1556.86 --> 1566.62]  I think all of this is that behavior of shutting down the forms and not really wanting to engage in a conversation about it, trying to reduce the amount of heat that Frank is taking.
+[1567.10 --> 1576.34]  And Frank's response and being so concerned about additional support requests that he would go to those, you know, he would essentially get that argument in that thread.
+[1576.34 --> 1593.68]  I think all of these are symptomatic of what you and I have worried about the project for a long time, and that is that the core developers who are some of, as you mentioned, the most important developers to the project are beyond what we would consider burned out and that they are on their very last nerve.
+[1593.68 --> 1604.04]  And every time we see a public interaction, we witness what appears to be an individual who is so far at the end of his rope, he has no time to deal with people talking back to him.
+[1604.36 --> 1607.50]  He has no time for the possibility that he might get additional emails.
+[1607.72 --> 1611.76]  The idea that he might get more emails is upsetting to him.
+[1611.76 --> 1616.28]  And then you see Paul is going around and cleaning up the conversation in the form.
+[1616.38 --> 1626.34]  So that way it doesn't inundate Frank with all of this, you know, peanut gallery chatter about it and just to try to get away from the issue as quickly as possible because he doesn't have time to deal with it.
+[1626.40 --> 1627.28]  He wants to stay focused.
+[1627.64 --> 1637.10]  And I don't really know what the solution here is, because that just seems to be even if it's not the case, even if this is just Chris's wild opinion, it's what the public sees every time.
+[1637.10 --> 1641.70]  And the issue here is this made it out beyond just the home assistant community this time.
+[1641.76 --> 1645.18]  It made it onto Hacker News and you had a very robust conversation over there.
+[1645.42 --> 1647.14]  It was fired up on the forums like Alex said.
+[1647.16 --> 1647.74]  It made it to Reddit.
+[1648.38 --> 1651.18]  It was in our team Slack where we were discussing this back and forth.
+[1651.38 --> 1654.18]  Like it made its rounds around the Internet.
+[1654.60 --> 1656.18]  And it's not a good look.
+[1656.24 --> 1659.74]  It looks like everybody's hot take is, well, they don't know what open source is.
+[1659.80 --> 1661.66]  They don't understand how Linux distributions work.
+[1661.72 --> 1663.14]  Don't they know it's MIT licensed?
+[1663.92 --> 1665.64]  And it's clear they're smart guys.
+[1665.64 --> 1667.20]  They know all of those things.
+[1667.52 --> 1669.20]  There's something else going on here.
+[1669.60 --> 1671.92]  And we're just getting little glimpses of it.
+[1672.24 --> 1673.40]  See, I think you have a different take.
+[1673.52 --> 1680.92]  You worry that maybe one day these guys, because they don't appreciate and understand open source, are going to take their cake and their ball and they're going to go home and eat it.
+[1681.00 --> 1681.58]  Does that make sense?
+[1681.60 --> 1683.18]  And they're going to convert it to a commercial product.
+[1683.24 --> 1685.18]  And we're going to be sitting here going, well, wait, now what do we do?
+[1685.48 --> 1690.92]  My concern is more the development team just totally burns out and leaves the project and it bans and says, well, it's open source.
+[1691.30 --> 1692.02]  You take care of it.
+[1692.02 --> 1695.58]  I think both scenarios are probably equally likely at this point.
+[1695.58 --> 1701.48]  Although perhaps going closed source, I mean, we've got precedent for that with MB.
+[1701.70 --> 1703.70]  We've seen other projects do that before.
+[1704.38 --> 1713.52]  I do think Home Assistant is slightly less likely to do that because just because of the sheer volume of open source contributions over the years.
+[1713.52 --> 1724.86]  I think if there was any talk of Home Assistant itself going closed source, that would get forked in a heartbeat and, you know, Home Lover would come out of it instead or whatever you want to call it.
+[1725.38 --> 1730.68]  And then Home Assistant just wouldn't be able to keep up with changes without that open source support.
+[1730.68 --> 1744.50]  So I don't think it's hugely likely, but I feel like, you know, all the moves and it's a difficult one because we talked to Paulus recently and he paints a very rosy picture about the future of the product.
+[1744.74 --> 1746.14]  And it's a sustainable one as well.
+[1746.24 --> 1758.30]  You know, Frank and Paulus and these guys are getting paid through Nebukasa, which oftentimes is a reason that these developers burn out is because it's a side hustle or a side project.
+[1758.30 --> 1761.10]  For these guys, it is their job, you know.
+[1761.30 --> 1772.08]  So I do think we've come to expect a certain level of access to open source developers like this because of the way we conduct all of our business in public.
+[1772.08 --> 1784.18]  I'm sure if we went and looked in some internal, you know, company email thread at name Big Corp here, we'd see similar levels of emotional attachment and petulance at times.
+[1784.78 --> 1788.00]  But the difference here is that it's out for the world to see.
+[1788.30 --> 1791.88]  And there is a bit of a spirit of cooperation in the open source community.
+[1792.02 --> 1795.28]  A lot of home assistant is built on top of a lot of other great code.
+[1795.46 --> 1803.06]  And so when somebody comes along and says, yeah, but don't use our open source code in your project, it doesn't really sit well and it gets noticed.
+[1803.30 --> 1807.26]  And I think to your point that, you know, they are full-time employees of Nebukasa.
+[1807.82 --> 1810.68]  Money is only part of the solution.
+[1810.68 --> 1817.74]  It is likely that Frank is such a talented developer and what he works on is so crucial to home assistant.
+[1818.32 --> 1824.84]  I bet you there is just an unrelenting, never-ending amount of work for him to take on.
+[1825.36 --> 1828.36]  And, you know, he did some work with the new ESP home release that we'll talk about.
+[1828.60 --> 1829.18]  He did, yeah.
+[1829.18 --> 1832.60]  Yeah, he's involved in more things than ever now.
+[1833.02 --> 1836.94]  And I think there is only so much that maybe one developer can take on.
+[1837.36 --> 1840.78]  And when you're talented like he is, you're going to get worked.
+[1841.46 --> 1842.40]  And I don't know.
+[1842.40 --> 1861.78]  If you've ever read The Phoenix Project, which is a book about DevOps, it talks about this concept of a halo engineer who people are afraid of upsetting or touching systems because this one guy knows all of the different incantations you have to say to make something work.
+[1862.06 --> 1868.56]  I kind of feel like Frank's manoeuvring into that position and the home assistant project's very dependent on him because of his skills.
+[1868.56 --> 1876.48]  It's a difficult problem to solve and it is not unique to home assistant that you end up with this reliance on one talented guy.
+[1876.62 --> 1878.84]  But I don't know what the solution is either.
+[1879.06 --> 1881.74]  Do we all stop collectively emailing Frank all at once?
+[1882.36 --> 1882.60]  Maybe?
+[1883.08 --> 1884.46]  Yeah, that might help.
+[1886.70 --> 1889.40]  Well, why don't we just really quickly talk about ESP home?
+[1889.86 --> 1893.04]  It's now part of home assistant, so they're kind of related.
+[1893.04 --> 1900.54]  And for those of you who don't recall, there was those little ESP, what is it, 8266 and the ESP32?
+[1901.06 --> 1901.88]  Yeah, there's a couple of them.
+[1902.46 --> 1903.32]  They're made out of China.
+[1903.48 --> 1910.22]  There's a company there called Espressif and they make ESP8266 and ESP32 devices.
+[1910.68 --> 1916.22]  Little Arduino compatible single board systems that have a Wi-Fi chip in them.
+[1916.22 --> 1921.90]  You can use them for all kinds of things like sensors or controllers, little MQTT devices.
+[1922.34 --> 1930.30]  And now it's sort of a perfect fit, as you can imagine, with home assistant because that's a lot of things you'd want to do with a home assistant installation.
+[1930.66 --> 1933.74]  And so they've rolled out version 1.19.0.
+[1934.36 --> 1944.52]  And I think the biggest thing in here is they've added a feature that's very similar to commercial smart plugs where you can give it your Wi-Fi information over Bluetooth LE and give it the Wi-Fi credentials.
+[1944.64 --> 1945.38]  That's a huge feature.
+[1945.38 --> 1946.00]  That's slick.
+[1946.10 --> 1948.92]  Yeah, I remember Paulus telling us about that a couple of weeks ago.
+[1949.30 --> 1951.00]  It's nice to see it actually land in a release.
+[1951.64 --> 1960.60]  Now, another improvement they've made is that they've been working hard on some new tooling to make it easier for everyone to install ESP Home and other firmwares on their devices.
+[1961.32 --> 1966.48]  And to do that, they've created something called ESP Web Tools linked in the show notes.
+[1966.90 --> 1971.74]  Yeah, that's nice to see and going to make it even simpler for people to approach.
+[1971.74 --> 1972.48]  But don't worry.
+[1973.08 --> 1975.62]  They're also improving the command line experience.
+[1975.62 --> 1978.52]  So both got some love, which is great to see.
+[1978.52 --> 1987.16]  And then the other thing that I think puts this into now I'm very much going to consider devices based on this is – and this is something I've been waiting for desperately.
+[1987.16 --> 1994.20]  They're going to add attributes from Home Assistant now that you're going to be able to save them into the local sensor on ESP Home.
+[1994.20 --> 2002.16]  So, for example, the brightness of a light, so when the light turns on, it resumes the original brightness or the current temperature for a climate device.
+[2002.28 --> 2004.56]  So that way it doesn't have to keep checking in with Home Assistant all the time.
+[2004.80 --> 2010.30]  To be able to read attributes from Home Assistant entities right into the local sensor, I feel like, is a game-changing feature.
+[2010.60 --> 2012.26]  For them, it's just a bullet point in the new release.
+[2012.98 --> 2014.28]  And I'm like, yes!
+[2014.64 --> 2015.60]  I'm so happy.
+[2015.80 --> 2020.14]  I've got this like Jonah Hill kind of I'm-so-happy gif playing right now.
+[2020.22 --> 2020.48]  Yes.
+[2020.90 --> 2021.22]  Right.
+[2021.32 --> 2021.68]  Exactly.
+[2021.68 --> 2023.14]  I think that's pretty great.
+[2023.32 --> 2026.84]  So a new ESP Home makes me happy.
+[2027.24 --> 2031.56]  Now, in the spirit of embedded devices, Tasmota has a new release this week.
+[2031.74 --> 2034.14]  They've just released 9.5.0.
+[2034.62 --> 2042.68]  Now, there is a breaking change in this release, and lights using the MQTT Discovery Protocol will not work correctly in recent versions of Home Assistant.
+[2043.56 --> 2049.32]  So upgrade to 9.5 and use the Tasmota integration to work around that problem.
+[2049.32 --> 2060.74]  We want to thank our friends over at Cloud Guru for sponsoring this year's program and let you know about their hands-on with Podman containers on Linux course, which is free for the month of June.
+[2061.18 --> 2063.88]  And, of course, they'll still be available for members when you go over there.
+[2064.14 --> 2067.42]  This course, you're going to learn what containers are, so you're going to get some basics there.
+[2067.42 --> 2074.42]  But also then how to manage them and specifically how to manage them using Podman, how Podman interoperates with Kubernetes and Systemd.
+[2074.84 --> 2084.34]  And, of course, because it's the new way now, how to manage Podman using Cockpit, which is the web graphical interface that I actually think is pretty great.
+[2084.44 --> 2085.56]  But don't mention it to Alex.
+[2085.64 --> 2086.40]  It upsets him.
+[2086.40 --> 2087.04]  But you can go over there.
+[2087.08 --> 2088.14]  We'll have a link in the show notes.
+[2089.04 --> 2094.42]  And you can check out Hands-On with Podman containers on Linux for a Cloud Guru, which is free in June.
+[2094.48 --> 2096.00]  But then, of course, will be available on the platform.
+[2096.36 --> 2097.44]  Link in the show notes.
+[2099.88 --> 2101.38]  Probably time we need some feedback, eh?
+[2102.06 --> 2103.18]  Yeah, I think so.
+[2103.32 --> 2104.08]  I feel like it.
+[2104.48 --> 2105.26]  Corey wrote in.
+[2105.82 --> 2108.58]  He wants to get social, but he wants to do it without social media.
+[2108.58 --> 2112.20]  He says, hey, long-time listener and even long-timer self-hoster.
+[2112.48 --> 2113.18]  I love the show.
+[2113.18 --> 2119.60]  And he says, with more and more things going online only, in-person interactions are getting to be more sparse.
+[2120.14 --> 2129.86]  I found lately I need to put conscious effort into keeping up with friends and family, checking in from time to time, and or even taking notes about something they've mentioned to follow up on.
+[2130.70 --> 2131.04]  Wow.
+[2131.44 --> 2132.10]  You know what, Corey?
+[2132.72 --> 2134.92]  I'm just realizing I should be doing that.
+[2135.74 --> 2140.44]  He says, Corey goes on to say, I was curious if anyone had a tech solution for this.
+[2140.44 --> 2146.10]  Some sort of, like, contact management thing where you could make notes about a project or a vacation they mentioned.
+[2146.26 --> 2153.30]  So you could ask them about it later on or even set reminders like, hey, self, you haven't talked to X in four weeks.
+[2153.44 --> 2159.16]  Maybe check in on them or maybe some sort of reminder about their vacation and asking them how it went.
+[2159.68 --> 2165.90]  Perhaps it sounds a bit dumb, but I think I could put it to use, especially after college or school when friends kind of go their own way.
+[2166.26 --> 2167.80]  So is there something out there?
+[2167.86 --> 2168.62]  What would you guys do?
+[2168.90 --> 2169.20]  Thanks.
+[2169.20 --> 2177.92]  Well, at first I thought the question was about social media, and I kind of had a sinking feeling that self-hosting your own social media kind of defeats the point of social media.
+[2178.46 --> 2187.12]  And then as the question carried on, I sort of was listening and realized that actually what he's looking for is basically a customer relationship management system.
+[2187.90 --> 2194.40]  And there is a really good one in this space, in the self-hosted space called Monica, monicahq.com.
+[2194.40 --> 2208.62]  And this essentially lets you set reminders for all sorts of things, like the names of the children of all of your friends, wedding anniversaries, the last time you called them and talked to them about the weather or whatever it might be.
+[2209.44 --> 2216.08]  Monica lets you quickly and easily log all that information so you can be a better friend, family member or spouse.
+[2216.08 --> 2219.16]  I kind of think this is a great idea, actually.
+[2219.54 --> 2225.08]  Or I could see it, you know, for like keeping track of what you guys have going on, you know, for the JBT members.
+[2225.18 --> 2229.44]  So that way I'm not like rude and just forgetting the important things that you guys have going on.
+[2229.68 --> 2233.02]  You know, like this could make me a better team member.
+[2233.36 --> 2233.86]  Well, good news.
+[2233.96 --> 2236.30]  They have an official Docker image over at Docker Hub.
+[2236.52 --> 2237.32]  I might give it a look.
+[2237.40 --> 2239.30]  If I remember after the show, I might give it a try.
+[2239.30 --> 2242.14]  Yeah, essentially it's a digital Rolodex.
+[2242.50 --> 2244.28]  Yeah, I think that should be pretty useful.
+[2244.64 --> 2252.66]  OK, so the Hom writes in and this is about cooling Raspberry Pis in your famous RV server seat without cutting big holes in it.
+[2253.24 --> 2260.48]  He's got a couple of suggestions about using water cooling, actually, to cool the air inside the box rather than the Pis themselves.
+[2260.84 --> 2261.10]  Hmm.
+[2261.76 --> 2265.16]  Yeah, I had not even considered water cooling a Raspberry Pi before.
+[2265.88 --> 2268.64]  That'd actually be a pretty cool project, wouldn't it?
+[2268.64 --> 2270.10]  So how would that work?
+[2270.14 --> 2275.24]  If you think about it, you'd put a radiator inside the seat that would act as a heat sink?
+[2275.56 --> 2275.84]  I suppose.
+[2276.16 --> 2280.24]  Because the thing about water cooling rigs that I always, I mean, I've never done water cooling in my life.
+[2280.28 --> 2284.72]  I've always wanted to, but it's always just been that notch more expensive than I'm willing to go.
+[2285.38 --> 2285.54]  Yeah.
+[2286.28 --> 2296.26]  Whenever I see like Linus Tech Tips or whoever mucking about water cooling, they've got these big, shiny copper heat sinks directly attached to the motherboard or whatever, to the CPU.
+[2296.26 --> 2303.12]  How would you transfer the heat from the seat to the radiator, I guess, is the question.
+[2303.52 --> 2304.30]  That is a good question.
+[2304.30 --> 2307.46]  I think the way you'd have to do it is you'd have to get something that sits on the Pi.
+[2307.58 --> 2313.38]  So I'd have to get rid of my flirt cases that I like and get something that affixes to the hot components on the Pi.
+[2313.58 --> 2316.92]  Affix it to the flirt cases because they are a heat sink themselves, right?
+[2316.92 --> 2318.48]  Maybe, maybe, maybe.
+[2319.00 --> 2322.10]  You'd want, I'd also want like a plate that I could attach to a router.
+[2322.28 --> 2324.36]  You know, you'd want a couple of different or maybe something for the switch.
+[2324.84 --> 2331.36]  And then you'd run water cooling through those plates into a radiator that I guess you could maybe put it in the booth.
+[2331.44 --> 2334.60]  But I think for better cooling, you'd need the radiator outside the booth.
+[2334.88 --> 2334.98]  Yeah.
+[2335.32 --> 2337.20]  Clearly, this needs better planning.
+[2337.50 --> 2339.18]  But I like where the home's going with this.
+[2339.30 --> 2341.10]  It's an idea I actually had not considered.
+[2341.60 --> 2345.66]  And anything would be better than cutting a hole in the side of my RV.
+[2345.66 --> 2354.40]  However, the Pis are only part of the problem because the other situation I have is the electrical system with the Victron equipment and the batteries.
+[2355.04 --> 2363.20]  When I'm running solar and so I'm taking in a whole bunch of solar, which generates heat, surprisingly, and then also running air conditioning.
+[2363.20 --> 2369.00]  So I'm inverting solar power into air conditioning when it's really hot out.
+[2369.00 --> 2374.92]  So like, say, above 95 degrees or 90 ish, even that just generates a lot of heat in itself.
+[2374.92 --> 2381.56]  Then you combine that with when I've been driving, the drivetrain is very hot, which is behind the power bay.
+[2382.00 --> 2383.80]  So it's a lot of ambient heat.
+[2384.26 --> 2387.84]  And what I have to do to keep it running is I have to get airflow going through there.
+[2388.12 --> 2390.48]  So I don't think I could water cool the Victron equipment.
+[2390.58 --> 2394.56]  So it would only solve the Raspberry Pi problem, but definitely worth considering.
+[2394.66 --> 2397.12]  I'm going to actually go do a little Googling tonight and see what I can find.
+[2397.12 --> 2403.26]  Yeah, I mean, like maybe with hard drives, you don't need a huge amount of airflow over them.
+[2403.34 --> 2404.58]  You just need some.
+[2405.10 --> 2413.64]  And maybe you could make that fan pull double duty of doing the water cooling and also blowing air over the drivetrain and battery bay.
+[2413.92 --> 2418.48]  Well, Alex, I think you better come out here and set a few weeks aside so we can start getting to work on this project.
+[2419.20 --> 2419.60]  Maybe.
+[2419.86 --> 2421.52]  Yeah, it's episode 50 before we know it.
+[2422.22 --> 2422.74]  Yeah, maybe.
+[2422.84 --> 2423.86]  That would be fun, wouldn't it?
+[2423.86 --> 2425.40]  I don't know, though.
+[2425.40 --> 2426.58]  I'm pretty nervous about it.
+[2426.66 --> 2427.92]  Pretty nervous about cutting holes.
+[2429.00 --> 2430.48]  I'll come to some solution.
+[2430.78 --> 2431.80]  And when I do, I'll share it.
+[2431.90 --> 2434.72]  But in the meantime, let's talk about something that'd be simple.
+[2434.96 --> 2437.32]  Something maybe I won't have to mess too much with.
+[2437.56 --> 2440.26]  Yeah, we've got an app pick for you all this week called Tiny Home.
+[2440.44 --> 2443.16]  This is a simple static homepage generator.
+[2443.88 --> 2445.30]  There's a link to it in the show notes.
+[2445.58 --> 2449.40]  And if you head on over there, you'll see there's a link to an example demo site.
+[2449.76 --> 2452.82]  And the demo site is just, it's so simple.
+[2452.82 --> 2455.02]  It's just headings with a couple of buttons on it.
+[2455.16 --> 2464.88]  So if you want to put all of your different self-hosted web apps, it's basically a collection of links, like Heimdall, like Homer, like Organizer, all those kind of things.
+[2464.92 --> 2469.80]  Except this is a statically generated, super simple little website.
+[2470.38 --> 2473.12]  Yeah, and I think it just generates it from Bash scripts or some kind of script.
+[2473.38 --> 2476.96]  So it's really easy for you to manage it and just spit out a static website.
+[2477.46 --> 2478.30]  That's pretty nice.
+[2478.62 --> 2479.28]  That's pretty nice.
+[2479.28 --> 2483.66]  Yeah, just generate a little CSV file and a static generator will do the rest.
+[2484.70 --> 2485.78]  Gosh, that is easy.
+[2486.26 --> 2491.82]  If you're still mulling over Google Photo alternatives, check out Alex on Linux Unplugged 409.
+[2491.94 --> 2497.42]  He joined us to talk about some of his favorites and some of the ones we've covered on this show before, but with a few updates.
+[2497.78 --> 2500.84]  That's at linuxunplugged.com slash 409.
+[2501.22 --> 2505.08]  And for all the places to get in touch with us, you can go to selfhosted.show slash contact.
+[2505.08 --> 2506.72]  You can find Alex on the Twitter.
+[2506.82 --> 2507.92]  He's at ironicbadger.
+[2508.06 --> 2509.40]  I am at Chris Elias.
+[2509.54 --> 2512.60]  And this here show is at selfhosted show.
+[2512.60 --> 2518.82]  Thanks to our site reliability engineers who keep the show going at selfhosted.show slash SRE.
+[2519.16 --> 2522.54]  Stick around if you're a member for your exclusive post show.
+[2523.24 --> 2528.58]  And I have a bit of exciting news for those of you who are cloudfree.shop customers.
+[2528.96 --> 2531.96]  There will be some new smart plugs coming in stock this week.
+[2532.04 --> 2536.86]  Version 2 with energy monitoring as well as all the existing TAS motor features.
+[2537.60 --> 2541.44]  And you can still use the coupon code selfhosted to get 10% off over there.
+[2541.44 --> 2542.86]  And thanks for listening, everyone.
+[2543.08 --> 2545.56]  That was selfhosted.show slash 47.

48： A Solution Looking for a Problem _summary.txt

@@ -0,0 +1,47 @@
+• Discussion of Morgan's experience with a cloud-free doorbell
+• Issue with the camera dying due to heat
+• Investigation into possible causes and troubleshooting efforts
+• Comparison of different doorbell models (EasyVis, Wyze, RCA)
+• Concerns about the limitations and reliability of current doorbell options
+• Expansion of Wyze's product line and potential implications for the market
+• Affordability and value of little cameras with RTSP firmware
+• Planned obsolescence in smart home devices, including doorbells
+• Need for open devices and firmwares to reduce e-waste
+• Right to repair bill passed in the UK and its limitations
+• Incentivizing companies to consider their environmental footprint
+• Criticism of manufacturers' lack of accountability for product waste
+• Discussion of Home Assistant's official two-year integration with smart home devices
+• Excitement about a product integrating its firmware and cloud API
+• Discussion of local APIs vs cloud-connected systems
+• Comparison of latency between cloud-connected and local systems
+• Personal anecdote about automating light control with Shelleys
+• Benefits of home servers for hosting services and streaming media
+• Explanation of MergerFS tools and their use in rebalancing drives
+• MergerFS permissions and ownerships in a mergerfs.mount
+• MergerFS.dupe tool for duplicating files across different branches
+• Fsoc or fs.check discussion
+• MergerFS balance feature to balance data equally across pools
+• MergerFS.consolidate feature to co-locate files onto one drive using rsync
+• Linode cloud provider and its features, including 24/7 customer support
+• KVM setup issues with multiple server connections
+• Exploring modern alternatives to traditional KVM solutions
+• Pi KVM solution using a Raspberry Pi 4 as a KVM unit
+• Using an HDMI switcher with keyboard shortcuts for input switching
+• Recording capabilities and potential for streaming output
+• Email gateway issues and SMTP relay concerns
+• MailRise app as an SMTP gateway for notifications
+• MailRise allows users to send emails from their computer using an SMTP gateway
+• CloudFree.shop has released version 2 smart plugs with energy monitoring and TASMOTOR integration
+• A listener, Mike, asks about best practices for using Docker containers in production environments
+• The hosts discuss the benefits of Docker, including ease of use and declarative builds
+• They also mention that containers are not a solution for every problem, and sometimes it's easier to install services manually
+• The conversation touches on issues related to container management, such as versioning and dependencies
+• Containers and Docker
+• Organizing container volumes on ZFS
+• Hosting own email server vs using Gmail
+• VLANs for home network security, especially with IoT devices
+• The importance of using VLANs (Virtual Local Area Networks) to segment and organize a home network
+• VLANs are often misunderstood or intimidating due to the need for specialized hardware and configuration
+• Segmenting a network with VLANs requires careful planning and setup, but can provide benefits such as improved security and organization
+• Using existing equipment that supports VLANs can simplify the process of implementing VLANs in a home lab
+• The importance of having a well-organized and segmented network is discussed, with VLANs being one solution for achieving this.

48： A Solution Looking for a Problem _transcript.txt

@@ -0,0 +1,544 @@
+[0.00 --> 6.40]  This episode is brought to you by the all-new A Cloud Guru, the leader in learning for cloud, Linux and other modern tech skills.
+[6.78 --> 13.12]  Hundreds of courses, thousands of hands-on labs. Get certified, get hired, get learning at acloudguru.com.
+[14.62 --> 22.78]  This is a bit of an awkward one. Chris just messaged me and said that he's poured 15 gallons of water all over his MacBook Pro for some reason.
+[23.00 --> 24.86]  I don't know why he'd go ahead and do that.
+[25.12 --> 29.86]  So we have a backup post today. We have Morgan joining us from Florida. Hello, Morgan. How are you?
+[30.24 --> 33.84]  You know, a little hot, a little sweaty, but it's what I'm used to.
+[34.16 --> 36.54]  Nothing compared to the Pacific Northwest this week.
+[37.08 --> 39.06]  Yeah, I can't complain about that. At least I have AC.
+[39.62 --> 42.96]  Yeah, yeah. Down in Florida, I mean, you kind of have to have it, right?
+[43.12 --> 47.80]  So, Morgan, you last joined us on episode 18 to talk about doorbells.
+[47.80 --> 50.10]  So does that make you our resident doorbell correspondent?
+[50.34 --> 56.56]  Well, seeing how the doorbell died on me, and I think it was actually the heat that killed it, maybe.
+[56.56 --> 60.06]  All right. Well, let's talk about doorbells, shall we?
+[60.10 --> 66.00]  Last time you were on, you were testing one of the cloud-free doorbells for us.
+[66.26 --> 67.60]  And how's that been going?
+[67.60 --> 77.66]  So a couple months ago, I would say back in April, I went to check to see if a package was left at my door, and I noticed I couldn't connect to the doorbell.
+[77.66 --> 85.54]  So I fired up the, you know, Unify app, and I noticed it disconnected at about seven-something in the morning the day before.
+[86.18 --> 88.50]  You check the actual doorbell itself.
+[88.68 --> 89.68]  It still has power.
+[89.80 --> 90.38]  It works.
+[91.06 --> 92.54]  But the camera doesn't work.
+[92.66 --> 94.76]  So, you know, I go on the website.
+[95.34 --> 96.24]  No real help.
+[96.36 --> 100.56]  There's a forum, because as you guys know, this is a generic relabeled camera.
+[100.56 --> 109.42]  So I go on the website, the EasyViz website, and I start taking a look, and there's like 10 or 12 different ways to save it, to bring it back.
+[110.08 --> 110.44]  Nothing.
+[110.76 --> 112.26]  You know, I couldn't get it to come back.
+[112.70 --> 118.04]  You know, we were super concerned about heat, and it just died on me.
+[118.18 --> 123.56]  You know, I pulled out the SD card, and I threw it in there, and, you know, I had it set to just record nonstop.
+[123.56 --> 127.24]  And sure enough, like right at 7 a.m. in the morning, it just died on me.
+[127.86 --> 130.64]  You know, the SD card's fine, but it just died.
+[131.50 --> 134.82]  To check that it wasn't the transformer, I replaced the transformer.
+[135.48 --> 137.66]  I replaced the electronic doorbell itself.
+[138.26 --> 139.84]  Everything was fine, just the camera.
+[140.04 --> 144.62]  So I don't know if, you know, I just got unlucky.
+[145.16 --> 147.26]  You know, the model I had had an issue with it.
+[147.26 --> 153.52]  And I've seen other people talk about how they have them in Arizona, and they reach, you know, temperatures a lot higher than what I have.
+[153.64 --> 155.86]  But unfortunately for me, it died.
+[156.66 --> 157.66]  Is yours in direct sunlight?
+[158.20 --> 161.94]  It is in direct sunlight for the last hour or two of the day.
+[162.66 --> 167.62]  Luckily, my front door faces west, and, you know, the houses are two stories.
+[167.62 --> 171.22]  So with the trees, usually the last two hours of the day.
+[171.54 --> 174.32]  And it doesn't get enough direct sunlight to get too hot.
+[174.32 --> 178.52]  But again, as we mentioned on the original show, it's hot to the touch, you know.
+[178.60 --> 179.78]  So that was a concern.
+[180.26 --> 182.78]  And maybe that's the reason why it bit the bullet.
+[183.16 --> 190.58]  Well, I mean, on the flip side, I've been using the EasyVis branded version of this doorbell for the last year or so at my house.
+[191.04 --> 197.46]  And as you say, it runs a bit warm, but I've not had any issues with it dropping out or stopping working or anything like that.
+[197.46 --> 201.36]  I guess it's just based on your field research.
+[201.52 --> 202.62]  It's just a matter of time, hey?
+[202.62 --> 208.38]  The downside is there's not a lot of options out there other than these EasyVis clones.
+[209.36 --> 214.78]  RCA makes an EasyVis clone, and a lot of people are saying that the firmware is actually a little bit better.
+[215.70 --> 218.08]  You know, Wyze just came out with a camera.
+[218.42 --> 221.70]  And unfortunately, you know, Wyze did a little bit of trickery.
+[222.02 --> 226.90]  You know, there's a USB port that they cover with a sticker that they don't tell you that's there.
+[226.90 --> 230.20]  You know, there's a YouTube video that shows you how to access that.
+[230.54 --> 233.74]  And it's actually really great for, you know, places like an RV.
+[233.74 --> 236.38]  But it's cloud storage only.
+[237.10 --> 241.12]  You know, there's no SD card port.
+[241.12 --> 245.70]  So you're in a situation where you're really being forced into the cloud.
+[246.28 --> 250.80]  And the only viable option that I can find is back to the EasyVis clone.
+[251.26 --> 259.72]  And to be honest with you, I've run without a doorbell camera for a while because I don't want to buy something that I know is not going to be good.
+[259.72 --> 266.60]  So I may find myself again in the next few days with yet another EasyVis clone.
+[267.10 --> 269.08]  Or I may go with the RCA.
+[269.30 --> 272.74]  The RCA one, it seems to be the one that everybody recommends.
+[273.42 --> 273.96]  Yeah, it's interesting.
+[274.08 --> 278.38]  Looking at the Wyze website, they've started making pretty much everything.
+[279.00 --> 284.84]  I've seen a smartwatch from them recently and doorbell on top of the cameras and all that kind of stuff.
+[284.94 --> 289.18]  So they're really expanding their business pretty aggressively at the moment.
+[289.18 --> 292.00]  And I'm not sure how to feel about it.
+[292.26 --> 301.10]  Like, they obviously made their name with these really cheap, affordable $20 little cameras that most people use.
+[301.14 --> 304.50]  And I've still got a couple in this house that have got the RTSP firmware on them.
+[305.06 --> 305.68]  They work great.
+[306.10 --> 313.68]  But the version 3s, the company says the RTSP firmware is, air quotes, coming soon.
+[314.18 --> 315.94]  And that was six months ago.
+[316.18 --> 318.48]  And yeah, it hasn't come soon yet.
+[318.48 --> 319.96]  So I don't know.
+[320.04 --> 321.46]  Why is it kind of on thin ice with me?
+[321.56 --> 326.36]  So I'd be wary of going down that route just for that reason alone.
+[326.94 --> 335.68]  There's definitely a market right now for somebody to come in and make a doorbell that is just bare bones.
+[336.00 --> 336.98]  It does what you need.
+[337.24 --> 341.70]  SD slot powered either by batteries or powered by a transformer.
+[341.70 --> 345.88]  And has the ability to be connected to, you know, to stream.
+[346.68 --> 349.00]  The future is getting you into that monthly payment.
+[349.50 --> 354.78]  And the more features they strip out, the better chance that you're going to make that monthly payment.
+[355.18 --> 356.60]  And it's really unfortunate.
+[356.60 --> 360.08]  And it makes home labs and self-hosting even harder.
+[360.08 --> 364.22]  I don't know what's going to happen if EasyViz stops selling the clones.
+[364.50 --> 366.98]  I mean, that model is, I think, a little over two years now.
+[367.04 --> 369.62]  It doesn't look like they're looking to come out with a new one.
+[370.24 --> 372.02]  Planned obsolescence is a real problem.
+[372.02 --> 386.26]  And I think one of the things we can do to kind of help the environment in that respect from, you know, pointless e-waste is, I suppose, on the one hand is consume less, right?
+[386.38 --> 387.76]  Buy less stuff that we don't need.
+[387.84 --> 395.18]  I mean, our doorbells have functioned fine for 30 years as just a little switch with a wire going to a little bell in the hallway.
+[395.18 --> 404.92]  Anyway, the fact that we're sat here talking about them having a camera in them and all sorts of circuitry and stuff when there's a global chip crisis is very much a first world problem.
+[405.60 --> 414.12]  But on the other hand, I think these companies can do a lot more to help us, help them, really, in having open devices and open firmwares.
+[414.12 --> 420.94]  And I saw some news today come out of the UK about this right to repair bill that they've passed.
+[420.94 --> 433.88]  And how it's unbelievable, the right to repair bill they've passed doesn't include laptops and phones, which are two of the most important devices that people upgrade regularly.
+[434.06 --> 446.32]  I mean, fridges and washing machines and all that kind of stuff are important, of course, because they're very bulky and, you know, refrigerant and all that kind of stuff is, it's not endless to manufacture this stuff.
+[446.32 --> 457.26]  But yeah, I think there's some kind of ethical responsibility that these manufacturers have to start playing, you know, playing the game.
+[457.64 --> 460.38]  But it's all about where's the incentive?
+[460.58 --> 466.36]  Like if, let's take Samsung, for example, if they make a smartphone and it lasts three years,
+[466.36 --> 474.38]  they foot exactly 0% of the bill to recycle, to, you know, dispose of that item.
+[475.00 --> 478.60]  They sell me the phone, I use it for a little bit and I throw it in the bin.
+[479.50 --> 483.50]  The transaction so far as Samsung is concerned is I've bought the phone.
+[483.80 --> 490.70]  There's no consequence for them if I throw it in the bin after a day or after three years.
+[490.70 --> 502.74]  And I think until we have a way of getting companies attached to their environmental footprint, if that's even the right word,
+[502.88 --> 508.88]  that, you know, the waste that their products generate by failing prematurely, this cycle is just going to perpetuate.
+[509.42 --> 509.84]  That's a good point.
+[509.84 --> 520.72]  The other thing you're taking consideration is you have CEOs of major car manufacturers who are guilt tripping cryptocurrency miners for wasting electricity
+[520.72 --> 527.66]  without taking into consideration of how does the electricity get produced that then powers the very car he sells.
+[528.34 --> 530.32]  I wonder who you could be talking about there.
+[530.40 --> 532.92]  I think his name begins with E and ends with Lon, right?
+[533.42 --> 534.02]  Possibly.
+[534.18 --> 535.90]  But that's another topic for another day.
+[536.24 --> 539.68]  And I don't want to get attacked on a Twitter account I don't have.
+[539.84 --> 547.68]  Well, speaking of Twitter, Home Assistant announced this week that they're going to be working on an official two-year integration.
+[548.18 --> 548.90]  This is pretty cool.
+[549.00 --> 556.02]  So two-year, the manufacturer, are going to be actually writing software that is compatible out of the box with Home Assistant.
+[556.60 --> 559.04]  I've struggled to deploy Home Assistant.
+[559.60 --> 561.30]  And it's not because I don't want to use it.
+[561.78 --> 566.32]  It's because I just can't make up my mind what product to go with.
+[566.32 --> 575.00]  And I think the biggest issue that I'm having is I want to host my own solutions, but I don't want to get vendor lock-in.
+[575.48 --> 580.40]  I don't want to go with something that requires me to do a hack install.
+[580.40 --> 583.00]  I want something that's just going to be easy.
+[583.16 --> 584.30]  I can take it out of the box.
+[584.46 --> 585.86]  I can connect it to my Wi-Fi.
+[586.20 --> 587.98]  I can wire it into my device.
+[588.20 --> 589.68]  And then I can go into Home Assistant.
+[589.92 --> 591.18]  I click a wizard and it's done.
+[591.84 --> 595.02]  And I've talked to a lot of other people who are in the same situation.
+[595.38 --> 599.92]  We have a lot of really intelligent people who are out there that are very tech savvy,
+[599.92 --> 608.12]  but they don't want the hassle of having to configure XML files or JSON or installing firmware, etc., etc.
+[608.38 --> 609.48]  It is a pain.
+[609.72 --> 616.12]  And it's the biggest roadblock that I see to get people to adapt.
+[616.46 --> 621.34]  So to hear that somebody is going to come out and design something that is going to work directly with Home Assistant
+[621.34 --> 625.04]  and is integrated into their firmware is phenomenal.
+[625.04 --> 632.96]  What's really exciting about this piece of news is that they say that they're going to do the cloud API first with a local API to follow.
+[633.40 --> 638.84]  Now, I love me a good local API because I don't see why, if I have a light bulb next to me on my desk,
+[639.16 --> 645.38]  why does it need to go all the way to a data center in outer Mongolia and then come back to my desk again?
+[645.54 --> 647.74]  I mean, it's got to travel six feet.
+[647.92 --> 649.96]  So why don't we just do that?
+[650.28 --> 651.54]  Why do we need to go out and in again?
+[652.10 --> 653.82]  So that's very exciting to me, too.
+[653.82 --> 655.12]  Yeah, I totally agree.
+[655.38 --> 657.52]  And it's interesting what you're saying about a local API.
+[658.18 --> 664.22]  When you got me hooked on Shelleys and I wired a couple of Shelleys in to control some lights around the house,
+[664.68 --> 667.04]  the first thing I did is I timed it.
+[667.36 --> 674.68]  How long does it take to tell Alexa to turn off the light compared to how long does it take to open the app?
+[674.74 --> 677.82]  And I click the lights off and they turn off.
+[678.42 --> 681.72]  And these are seconds that we're talking about.
+[681.72 --> 685.92]  But just the idea that it's instantaneous, right?
+[685.96 --> 687.88]  We're not having to transverse the internet.
+[688.22 --> 694.32]  I have no idea who's looking at my packets, what Amazon is trying to do with what I just said.
+[694.78 --> 698.48]  But the idea that it's local, it's in your house.
+[698.72 --> 702.68]  If you lose internet, you can still control your lights.
+[702.94 --> 704.50]  Can't do that when you're cloud connected.
+[704.50 --> 708.28]  We've probably got some people listening that are going, yeah, what was wrong with a light switch?
+[708.36 --> 710.90]  I mean, you could control your lights without the internet with a light switch.
+[711.52 --> 714.88]  But, you know, you can't automate a light switch particularly well.
+[715.06 --> 717.76]  I suppose you could have a child and get them to walk over and flick the switch.
+[717.88 --> 720.38]  But that's quite an expensive solution, really, isn't it?
+[720.38 --> 726.80]  Yeah, and I have six lights that are embedded in the ceiling where I watch our movies.
+[727.26 --> 731.24]  And sometimes I want four of them on or I want the two behind me on.
+[731.58 --> 734.62]  And previously, they were all wired to an on and off switch.
+[734.94 --> 740.26]  And I really don't want to be in a situation where I need to run six, eight switches to get what I want.
+[740.72 --> 744.08]  But I spent a day, ran some wires, installed some Shelleys.
+[744.08 --> 749.86]  When I say turn off one, two, three, and four, they turn off.
+[750.32 --> 751.16]  Bada bing, bada boom.
+[751.84 --> 759.40]  A couple months ago, I finally decided that I was going to pull out the wallet and make some purchases and build a home server.
+[759.82 --> 763.74]  Now, I had a home lab that I previously talked about before, but it was just that.
+[763.82 --> 764.42]  It was a lab.
+[764.64 --> 766.80]  I tore it up, broke it a lot.
+[767.10 --> 768.06]  It broke a lot.
+[768.06 --> 777.54]  So it wasn't something that I could reliably count on to host services that my kids need every day.
+[777.88 --> 783.36]  To watch movies, TV, to listen to music, all that good stuff.
+[783.64 --> 785.02]  Really important stuff, right?
+[785.46 --> 787.90]  The things that keep them from driving me insane.
+[788.92 --> 794.88]  So, Alex, you had a UNAZ that you had bought and you didn't need it anymore.
+[794.88 --> 798.86]  So I graciously, for a decent price, took that off your hands.
+[799.76 --> 807.14]  And, you know, I set it up, got it all built, slapped in a bunch of spinning disks, set up MergerFS.
+[807.68 --> 812.62]  Well, I didn't go to perfectmediaserver.com and I didn't read the directions.
+[813.02 --> 815.46]  So I totally didn't set up MergerFS properly.
+[815.72 --> 822.54]  And I found out that we really couldn't stream two or three movies at a time because they just weren't handling the bandwidth.
+[822.70 --> 824.02]  And I was like, what did I do wrong?
+[824.02 --> 826.74]  And then I realized, ah, genius.
+[827.48 --> 828.76]  Everything's going to one disk.
+[828.90 --> 831.40]  You're trying to stream a bunch of movies at one time.
+[831.58 --> 833.12]  People are trying to listen to music.
+[833.24 --> 834.14]  It's just not going to work.
+[834.44 --> 839.46]  So I had to find something that would let me properly rebalance, right?
+[839.78 --> 841.44]  And off to Google I went.
+[841.68 --> 843.98]  And so I fell upon MergerFS-tools.
+[844.68 --> 846.56]  You know, it's over on GitHub.
+[847.26 --> 847.70]  Fantastic.
+[848.04 --> 848.88]  Easy to set up.
+[849.72 --> 850.58]  Clone the repository.
+[850.58 --> 855.12]  Within seconds, everything's being rebalanced across my drives.
+[855.12 --> 857.14]  Yeah, these tools are really great, actually.
+[857.38 --> 858.36]  And there's a few of them.
+[858.58 --> 862.40]  It's mergerfs.ctl.fsoc.dupe.
+[862.40 --> 865.78]  And the first one is mergerfs.ctl.
+[866.08 --> 869.70]  This is a wrapper around the MergerFS-x-atra interface.
+[870.54 --> 876.02]  Essentially what this lets you do is add and remove drives as well as get info about the array that's in there.
+[876.70 --> 880.14]  And, you know, print things like your version and your mount point and stuff like that.
+[880.52 --> 881.72]  Pretty useful if you need it.
+[882.08 --> 885.22]  Probably most people won't need that one, but it's there if you do.
+[885.22 --> 889.52]  The next one is mergerfs.fsoc.
+[890.04 --> 892.22]  So mergerfs.fsoc.
+[893.50 --> 897.80]  Audit's permissions, ownerships of files and directories in a mergerfs.mount.
+[898.08 --> 902.72]  And then one of the great tools that I really like is mergerfs.dupe.
+[902.88 --> 903.38]  No, no, no.
+[903.42 --> 903.68]  Hold on.
+[903.90 --> 906.90]  Before we sweep this under the carpet, we've got to clear this up.
+[907.40 --> 908.78]  Fsoc or fs.check.
+[909.04 --> 913.98]  If you have an opinion on this, let us know at self-hosted show on Twitter, please.
+[913.98 --> 914.58]  I don't know.
+[914.70 --> 916.58]  I think fsoc sounds a little dirty.
+[917.44 --> 917.84]  fs.ck.
+[919.50 --> 921.24]  All right, mergerfs.dupe.
+[921.26 --> 925.46]  This one duplicates files and directories across different branches in a pool.
+[926.22 --> 930.00]  The selected file can be duplicated using the dupe option.
+[930.32 --> 936.74]  So this could be useful if you're not using something like SnapRaid for kind of parity type redundancy.
+[937.00 --> 942.58]  This one would literally physically duplicate a file across X number of disks.
+[942.58 --> 946.12]  And then, of course, you have the follow-up to that, which is mergerfs.dupe.
+[946.62 --> 948.10]  Ddupe does as it says.
+[948.18 --> 950.26]  It finds removed duplicate files across pools.
+[950.92 --> 955.88]  You know, you can set up ignore, ddupe, and strict options to target specific use cases.
+[955.88 --> 964.28]  I can tell you, this one I used right away because as I was copying pictures over, you know, I copied them from my Mac.
+[964.38 --> 965.94]  I copied them from my Fedora box.
+[966.16 --> 970.28]  And I knew that I had them in multiple places because, as they say, if you don't have three copies...
+[970.28 --> 971.34]  It may as well not exist.
+[971.58 --> 971.72]  Yeah.
+[971.72 --> 977.30]  The first thing I did is I ran the ddupe, you know, because this became my fourth copy.
+[977.54 --> 980.60]  And there was no point in having multiple of the same files everywhere.
+[980.86 --> 982.12]  And it was really quick.
+[982.20 --> 983.10]  I was really surprised.
+[983.68 --> 989.12]  One of the things I like about the ddupe tool is, by default, it doesn't actually delete anything.
+[989.32 --> 997.42]  You have to explicitly set execute mode, which, you know, for fat-fingered people who don't read the docs like me on occasion, that's a good thing.
+[997.42 --> 1004.60]  And then again, as I originally mentioned, there's the MergerFS balance, you know, probably the best feature you're going to run into.
+[1004.80 --> 1008.48]  It's going to make sure that your data is balanced equally across the pool.
+[1008.90 --> 1010.92]  You know, you can set a defined range.
+[1011.02 --> 1012.62]  I think the default is like 2%.
+[1012.62 --> 1016.16]  So the last one is MergerFS.consolidate.
+[1016.24 --> 1018.86]  And this does the complete opposite of balance, really.
+[1018.94 --> 1023.94]  It takes things from multiple places and puts them and co-locates them all onto one single drive.
+[1024.90 --> 1026.60]  That one requires rsync.
+[1026.60 --> 1028.86]  I think there's a couple of others that require rsync as well.
+[1029.32 --> 1033.06]  But obviously under the hood, it's just doing some rsync magic to copy that stuff around.
+[1033.80 --> 1034.30]  It's definitely great.
+[1034.36 --> 1038.50]  Like I said, if you're running MergerFS in your home lab, definitely check it out.
+[1038.96 --> 1042.10]  You know, I'm sure there's going to be at least one tool in there that's going to help you out.
+[1043.98 --> 1045.84]  Linode.com slash SSH.
+[1045.98 --> 1049.34]  Go there to get a $100 60-day credit on your new Linode account.
+[1049.86 --> 1052.20]  Linode is the largest independent cloud provider.
+[1052.60 --> 1056.06]  Now, no matter what skill level you're at, what technology stack you use,
+[1056.06 --> 1058.58]  Linode can help your ideas come to life on the web.
+[1058.78 --> 1060.74]  If you run into any trouble getting set up,
+[1060.90 --> 1064.80]  Linode comes with amazing 24-7 customer support by phone or ticket,
+[1065.30 --> 1068.22]  along with hundreds of guides and tutorials to help you get started.
+[1069.10 --> 1071.68]  Linode has an easy-to-use and powerful cloud dashboard,
+[1072.24 --> 1073.82]  S3-compatible object storage,
+[1074.02 --> 1075.04]  cloud firewalls,
+[1075.20 --> 1077.50]  simple one-click application deployments,
+[1078.00 --> 1078.92]  super-fast networking,
+[1079.14 --> 1080.20]  and so much more.
+[1081.06 --> 1084.42]  Linode started in 2003 as one of the first companies in cloud computing,
+[1084.42 --> 1087.38]  three years before AWS and other enterprise providers.
+[1087.88 --> 1090.70]  They're independently owned and founded on a love for Linux.
+[1091.06 --> 1092.02]  And I tell you,
+[1092.10 --> 1095.50]  when you use Linode and you dig into some of their more advanced stuff,
+[1096.34 --> 1096.92]  by the way,
+[1096.96 --> 1099.42]  did you know they will let you boot your own ISOs?
+[1099.56 --> 1100.12]  Oh, yes.
+[1100.36 --> 1104.02]  If you want to run some esoteric thing from 20 years ago,
+[1104.20 --> 1105.98]  you can try and do that on Linode.
+[1105.98 --> 1111.76]  So go to linode.com slash SSH and get a $100 60-day credit on your new Linode account.
+[1112.00 --> 1114.50]  That's linode.com slash SSH.
+[1116.80 --> 1123.24]  One of the downsides of having a home lab and then a media server is I needed permission to buy it
+[1123.24 --> 1125.46]  and I needed permission to where to put it.
+[1125.76 --> 1129.26]  So the downside is it's next to my desk and it's in a small little hole.
+[1129.26 --> 1135.16]  And I have my three monitors and my MacBook and then I have my desktop for work.
+[1136.04 --> 1138.40]  And I have so many cables, you know,
+[1138.44 --> 1142.44]  and I'm constantly in a situation where when I need to hook up to the UNAZ,
+[1142.56 --> 1144.14]  I'm unplugging a cable.
+[1144.46 --> 1146.18]  Same thing with the ESXi box.
+[1146.68 --> 1147.82]  And I need a solution.
+[1148.70 --> 1151.46]  But I need a solution that really works.
+[1151.58 --> 1156.22]  I don't want the old style KVM where you're running all these cables and you're pushing a button.
+[1156.22 --> 1161.52]  You know, I want something that works with a modern monitor, HDMI, you know,
+[1161.84 --> 1163.86]  and something that just works.
+[1164.48 --> 1168.68]  Well, I was actually talking with Wendell about this the other night because he did a video on Pi KVM
+[1168.68 --> 1170.44]  and I sort of messaged him afterwards and said,
+[1170.52 --> 1178.58]  you know what would be really great is if I could take that single Pi 4 that I've got acting as a KVM unit
+[1178.58 --> 1182.58]  and control three or four systems with it.
+[1182.58 --> 1186.62]  I'm like, well, surely this should be possible with an HDMI switcher.
+[1187.04 --> 1190.82]  But I tried a couple in the past and they need you to actually be physically present
+[1190.82 --> 1195.18]  to push the button on the front of the damn thing to change the input from system one,
+[1195.34 --> 1197.12]  system two, three, four, whatever.
+[1198.00 --> 1201.24]  But the really nice thing about the unit that I've put in the show notes,
+[1201.50 --> 1205.10]  it's a four port HDMI switch.
+[1205.24 --> 1206.00]  It was about $60.
+[1206.00 --> 1211.28]  And this thing lets you use a keyboard shortcut to change inputs.
+[1211.40 --> 1214.42]  So I just press control, control, one, control, control, two,
+[1214.74 --> 1218.12]  and that changes the input on the KVM switch.
+[1218.42 --> 1222.44]  So how I've got it wired up is the HDMI goes from the server
+[1222.44 --> 1228.28]  out into the input of input one on the switch.
+[1228.28 --> 1236.96]  And then it comes from the switch output port into the capture port on the Raspberry Pi 4 through the CSI bridge.
+[1237.34 --> 1239.74]  Now, I've written a blog post about this, of course,
+[1239.88 --> 1242.74]  because that's what I seem to spend my spare time doing.
+[1243.16 --> 1245.50]  And I put a link to it in the show notes with a little diagram
+[1245.50 --> 1249.46]  in case that is a little confusing to follow by my talking.
+[1249.64 --> 1252.90]  But it takes about five minutes to wire up and put together.
+[1253.96 --> 1255.82]  And yeah, it just works, Morgan.
+[1255.82 --> 1257.04]  That's the really cool thing.
+[1257.14 --> 1263.14]  I can now switch between my server and my other server and my Raspberry Pi 3 that's doing DNS.
+[1263.62 --> 1266.30]  And they all just appear in the browser.
+[1266.54 --> 1267.56]  It's like magic.
+[1268.10 --> 1269.26]  Does it have the ability to record?
+[1269.66 --> 1270.62]  Can you record the output?
+[1271.00 --> 1272.08]  I don't think it does.
+[1272.20 --> 1273.56]  You can record macros.
+[1273.62 --> 1277.44]  So you can record different keyboard sequences and mouse sequences and that kind of thing.
+[1277.66 --> 1280.16]  But I don't think it will let you record the actual stream.
+[1280.86 --> 1283.60]  Although it's a WebRTC based system.
+[1283.60 --> 1289.58]  So I would wonder if there's some kind of a stream that we could hook into with VLC or something and maybe do it like that.
+[1289.90 --> 1294.14]  If you know the answer to that, again, write in and let us know at selfhosted.show slash contact.
+[1295.26 --> 1299.18]  Now, you're much more of a sysadmin than I am, I would say.
+[1299.24 --> 1304.82]  You've got a bit of a background working in all sorts of different places, cruise ships and hospitals and all sorts of places, right?
+[1304.82 --> 1311.24]  So you've probably run into email gateway issues when servers are trying to notify you that they've failed.
+[1311.82 --> 1314.68]  That's always been one of the fun parts about working in a data center.
+[1315.22 --> 1318.10]  Most of my employment has been with Exchange.
+[1318.26 --> 1321.24]  And you always run into these systems that just need an open relay.
+[1322.06 --> 1325.12]  As anybody knows, open relays are a little bit dangerous in the world.
+[1325.12 --> 1332.90]  So you're always looking for a good solution for, you know, an SMTP gateway that isn't expensive.
+[1333.30 --> 1338.30]  Or you can do what most people do and just copy their Gmail password around onto various boxes and have it connect that way.
+[1338.38 --> 1340.26]  I mean, what's the worst that can happen?
+[1340.58 --> 1342.06]  Yeah, when you're working from your home.
+[1342.18 --> 1344.62]  But, you know, what happens when you're working in a data center?
+[1345.12 --> 1346.64]  You're probably going to get that blocked.
+[1346.92 --> 1347.74]  Probably, yeah.
+[1347.74 --> 1350.76]  So I have an app pick for you that might tickle your fancy.
+[1350.90 --> 1352.10]  This one's called MailRise.
+[1352.28 --> 1355.44]  And this is an SMTP gateway for notifications.
+[1355.80 --> 1359.40]  Essentially, it plugs into an app we've mentioned before called AppRise.
+[1359.86 --> 1367.70]  So this MailRise application kind of sits in the middle, listening for emails, you know, syslog emails, whatever it might be.
+[1367.78 --> 1370.40]  Failures coming in from various different system services.
+[1370.92 --> 1376.22]  And when it receives the email, it reacts to that and then connects to AppRise.
+[1376.22 --> 1382.06]  So you can talk to any of the 60 plus notification services that AppRise supports.
+[1382.30 --> 1385.68]  So, you know, Telegram, Slack, Discord, you name it.
+[1386.44 --> 1397.36]  For those of you who are new to the show or possibly missed that episode, AppRise is a great tool that allows you to send notifications to almost all the most popular notification services today.
+[1397.86 --> 1403.06]  Think Telegram, Discord, Slack, you know, Reddit for those people who are really cool.
+[1403.18 --> 1405.68]  You know, it's a one notification library to rule them all.
+[1406.22 --> 1413.46]  And what's great is, is the tool MailRise, as Alex said, sits in front of that and is an SMTP gateway.
+[1413.88 --> 1419.80]  So there's a lot of applications that really don't have the ability to have that newer feature.
+[1420.52 --> 1425.68]  And MailRise gives you that by allowing you to send emails to the SMTP gateway and then you can send it off.
+[1425.68 --> 1434.86]  So when your laundry is done, you can send an email and post it on Reddit to let everybody know I now have clean clothes.
+[1435.64 --> 1436.60]  Hooray for that.
+[1436.92 --> 1438.40]  And that, you know, we live in the future.
+[1438.76 --> 1442.90]  We can monitor Morgan's laundry schedule via Reddit.
+[1442.90 --> 1451.04]  And speaking of the cloud, CloudFree.shop has some exciting news this week.
+[1451.26 --> 1454.58]  They have released their version 2 smart plugs.
+[1454.70 --> 1455.46]  So these are really cool.
+[1455.56 --> 1457.56]  They've got energy monitoring built right in.
+[1458.16 --> 1461.10]  And of course, they run TASMOTOR out of the box.
+[1461.10 --> 1467.36]  And, you know, the best thing about the company, it's a small family owned business run by one of our very own listeners.
+[1467.60 --> 1472.26]  Now you can go to CloudFree.shop and use the coupon code self-hosted so that they know that we sent you.
+[1472.82 --> 1475.72]  And you also get a dollar off per plug as well.
+[1476.08 --> 1479.16]  So that's CloudFree.shop with the coupon code self-hosted.
+[1479.16 --> 1481.98]  Mike writes to us,
+[1481.98 --> 1483.72]  Hey guys, love the show.
+[1484.12 --> 1485.82]  I'm a longtime Linux user and administrator.
+[1486.26 --> 1489.46]  But I have to admit, I've fallen a little behind on the whole container craze.
+[1489.86 --> 1490.86]  That's understandable, Mike.
+[1491.36 --> 1492.96]  I'm very comfortable with VMs.
+[1493.22 --> 1494.84]  They always made logical sense to me.
+[1495.30 --> 1501.40]  You have a virtual disk image, probably something with some metadata in it, and you get to run as a full-fledged system.
+[1501.96 --> 1507.98]  Something about the whole Docker runs X and it just magically happens without specifying any parameters
+[1507.98 --> 1509.46]  just struck me as creepy.
+[1510.44 --> 1513.82]  Regardless, I've used them a little bit inside of Firewall for LAN services,
+[1514.16 --> 1517.08]  but I'm wondering if there are best practices that either of you use.
+[1517.44 --> 1522.42]  For instance, when you're running multiple containers with persistence, where would you put the compose file?
+[1522.84 --> 1525.96]  Do you have any tips for organizing container volumes on CFS?
+[1526.56 --> 1528.72]  I've looked around and I haven't found any good articles.
+[1528.72 --> 1534.54]  Just lots of run Docker compose up and magic happens, which is disconcerting in a production environment to me.
+[1534.54 --> 1538.24]  That's the beautiful thing of Docker is it is just magic.
+[1538.76 --> 1541.44]  And for some people, that's exactly what they need.
+[1541.80 --> 1550.72]  You know, for your average person running an Unraid box or a small Raspberry Pi who's not working in this stuff day-to-day,
+[1550.72 --> 1556.82]  being able to do Docker run Plex or whatever it is without having to juggle half a dozen Bash scripts
+[1556.82 --> 1560.12]  and eight different versions of Java and all this kind of crap.
+[1561.10 --> 1563.62]  That's exactly where Docker is going to win.
+[1564.28 --> 1571.80]  Also, developers, if they're trying to do multiple different versions of an application development lifecycle all at once.
+[1571.80 --> 1578.70]  You know, I've got three different builds and I'm trying to figure out which one is causing my production systems to go down.
+[1579.36 --> 1584.18]  It's very easy to isolate and roll back a container that way because it's a declarative build.
+[1585.84 --> 1595.12]  But I understand there are some more old school people around that don't like that approach because it is a little more opaque than you've been used to.
+[1595.12 --> 1605.86]  However, I would say the reason it appears opaque is because perhaps you haven't quite taken the amount of time you need to to look into where that container originated from.
+[1607.52 --> 1614.74]  And sometimes you can go and look at the Docker file in the open source community and see basically a Docker file is like a recipe.
+[1615.08 --> 1617.88]  It's a glorified Bash script, essentially.
+[1618.74 --> 1624.06]  And say apt install this package, create this user, install this particular library.
+[1624.06 --> 1628.66]  And on the whole, those containers work pretty well.
+[1629.30 --> 1636.32]  And this is a problem that used to exist that I haven't seen really be a problem for quite some time now.
+[1636.86 --> 1641.34]  Is a lot of containers used to get uploaded to Docker Hub without a Docker file.
+[1641.52 --> 1645.62]  So you had to just trust that they weren't going to run a crypto miner on you or something like that.
+[1645.70 --> 1648.00]  And that problem largely seems to have gone away.
+[1649.00 --> 1651.20]  There are lots of different places you can go.
+[1651.32 --> 1652.84]  Linux server.io is one of them.
+[1652.84 --> 1657.34]  You can go to obviously Docker's website as well for some documentation there.
+[1657.90 --> 1660.66]  I'm going to say something that's probably not going to be popular.
+[1661.14 --> 1664.12]  But I don't think containers are solution for everything.
+[1665.60 --> 1669.64]  And it's Alex and I know containers are what puts roof over our heads.
+[1670.00 --> 1674.28]  And I will honestly tell you again, I don't think containers are the solution for everything.
+[1674.28 --> 1681.26]  You don't always need to build a server and install Docker or Podman and run a container on it.
+[1681.60 --> 1687.80]  Sometimes you can just install the Debian, the dev files or the RPM files and configure it yourself.
+[1687.80 --> 1694.76]  However, what containers do is it makes it easier to install services that work together.
+[1695.30 --> 1703.60]  You know, if you have a service that goes out and queries, it does a search for a file, injects that download file into the download service.
+[1703.86 --> 1705.80]  The download service then downloads the file.
+[1705.80 --> 1710.18]  Another service grabs the file, reads the metadata, processes it.
+[1710.58 --> 1711.90]  That's going to be really difficult.
+[1712.56 --> 1716.02]  How do we know that all three of those services require the same version of LibC?
+[1716.42 --> 1721.54]  How do we know that they require a specific version of Go, et cetera, et cetera?
+[1721.86 --> 1725.74]  You don't want to run into the situation where you're constantly looking at dependencies.
+[1725.94 --> 1727.24]  And that's what containers do.
+[1727.24 --> 1735.06]  So if you're doing a standalone box or standalone application, yeah, you know, doing the FAD install is perfectly fine.
+[1735.36 --> 1742.38]  But whenever you want to make sure that everything's going to work together and they're not going to butt heads, that's the real reason why containers were created.
+[1742.94 --> 1754.54]  Now, to answer your question about Docker compose files, the way I do it, and I'm sure Alex does it his way, is if the services need to speak to each other, they're in the same compose file.
+[1754.54 --> 1758.26]  I run 10 or 12 containers on my home lab.
+[1758.74 --> 1763.02]  And if the service does not need to talk to each other, it gets its own compose.
+[1763.60 --> 1764.98]  That's the way that I've always done it.
+[1765.36 --> 1771.74]  There's no reason for me to do a Docker compose up with AdGuard in the same exact compose as Plex.
+[1772.22 --> 1773.40]  They don't need to talk to each other.
+[1773.54 --> 1775.12]  They don't need to be on the same Docker network.
+[1775.36 --> 1777.36]  They can live in different Docker compose files.
+[1778.16 --> 1782.06]  I once had a colleague tell me that Docker was a solution looking for a problem.
+[1782.06 --> 1793.86]  Back then, this was like six years ago, I got really hot and steamy under the collar about this because Docker was the new hotness and I could see that it was going to solve all the world's problems.
+[1794.74 --> 1798.18]  And with a little bit of hindsight, I think I kind of agree with him in some ways.
+[1798.96 --> 1805.96]  It definitely has its use cases, but there are also places where VMs are probably better.
+[1805.96 --> 1812.74]  Now coming to another part of Mike's question, he asks about tips for organizing container volumes on ZFS.
+[1813.60 --> 1816.14]  I just create a data set per app, Mike.
+[1816.36 --> 1817.26]  It's as simple as that.
+[1817.40 --> 1818.36]  You can set quotas.
+[1818.68 --> 1823.12]  You can do snapshots, you know, using Jim Salter's Sanoid tool.
+[1823.58 --> 1831.18]  I have it set to do, I think, four hours worth of app data snapshots and then keep a daily snapshot and a monthly and an annual snapshot.
+[1831.18 --> 1846.60]  So the only thing to be aware of there is if you're doing something like InfluxDB or some kind of really chatty time series container or database that generates a lot of data, those snapshots will take up a lot of space because of how copy on write works.
+[1846.78 --> 1851.18]  So just make sure you're familiar with that concept before you dive into that one.
+[1852.18 --> 1854.72]  Ivan writes in, do you guys host your own email server?
+[1855.10 --> 1856.46]  And what are your thoughts on this?
+[1857.26 --> 1859.04]  This might be a good idea for the show.
+[1859.04 --> 1863.14]  I can tell you on a personal note, I love Gmail.
+[1863.70 --> 1864.62]  Why do I love Gmail?
+[1865.54 --> 1866.28]  It's easy.
+[1866.80 --> 1867.96]  They read my emails.
+[1868.36 --> 1869.94]  They tell me what I want to buy.
+[1870.36 --> 1873.70]  It works on my phone and they give me a bunch of storage.
+[1874.78 --> 1879.46]  But I can also tell you my private email is for my family only.
+[1880.04 --> 1883.70]  I don't give it out to anybody who isn't related to me by marriage or by blood.
+[1884.58 --> 1887.26]  And I run, therefore, my own email server.
+[1887.26 --> 1888.96]  It's been $5 a month.
+[1889.10 --> 1889.92]  It's on Linode.
+[1890.32 --> 1891.92]  I recommend everybody use it.
+[1893.08 --> 1895.34]  Do you, I want you to contact me for a job offer?
+[1896.10 --> 1896.88]  I have a Gmail.
+[1897.32 --> 1899.08]  Do I want to sign up for FPNL?
+[1899.70 --> 1900.02]  Gmail.
+[1900.58 --> 1903.86]  Do I want to send pictures to my mom, my kids?
+[1904.54 --> 1905.16]  Personal email.
+[1905.16 --> 1907.66]  I know that no one's ever going to get a hold of it.
+[1908.56 --> 1911.30]  I know that I'm not going to have to worry about getting spam.
+[1912.14 --> 1914.96]  Because, again, that's what Gmail is for.
+[1915.20 --> 1916.08]  It's for spam filtering.
+[1916.98 --> 1919.28]  My email that I host is for family only.
+[1919.86 --> 1922.22]  It's for things that I want for me and only my family.
+[1923.04 --> 1925.30]  And I recommend everybody to do the same.
+[1925.64 --> 1927.14]  Again, it's $5 a month.
+[1927.76 --> 1928.92]  Super easy to set up.
+[1928.92 --> 1930.14]  I like Gmail, too.
+[1930.56 --> 1931.52]  It just works.
+[1932.38 --> 1935.08]  So Thomas writes in with networking on his mind.
+[1935.56 --> 1939.10]  I wondered if either of you have touched VLANs on home networks.
+[1939.44 --> 1941.94]  I just got two Netgear Smart PoE switches.
+[1942.08 --> 1944.28]  And I'm thinking about how best to segment my network.
+[1944.70 --> 1947.40]  I've got a NUC with Fedora on it and a Windows laptop.
+[1947.68 --> 1949.78]  I've also got a NAS running some containers.
+[1949.78 --> 1954.74]  And I make use of WireGuard and Plex on there as well.
+[1955.80 --> 1959.62]  I've also got a Wi-Fi network that has a Google Nest and a pair of smart scales.
+[1960.48 --> 1963.28]  Thanks for an interesting show and inspiration for my home network.
+[1963.58 --> 1963.86]  Thomas.
+[1964.56 --> 1968.10]  VLANs and the home network is an interesting topic.
+[1969.12 --> 1973.20]  I think for 90 plus percentage of the world, you don't need them.
+[1974.14 --> 1977.84]  Until you start considering IoT devices and how insecure they are.
+[1977.84 --> 1979.96]  And who can get access to them.
+[1980.86 --> 1987.04]  And the second you have IoT devices that are a huge gaping security hole, you need to segment them.
+[1987.24 --> 1988.36]  And that's where VLANs come in.
+[1988.66 --> 1989.96]  And that's the number one thing I do.
+[1990.58 --> 1993.64]  My Wyze cameras, they're on separate VLAN and SSID.
+[1994.88 --> 2000.96]  My EcoVac Smart Vacuum on its own SSID and its own VLAN.
+[2001.36 --> 2007.32]  Because I want to segment anything on my network that is going to potentially open me up to attack.
+[2008.08 --> 2012.16]  The other reason why I use VLANs is, again, as I mentioned, I have a home lab.
+[2012.64 --> 2013.94]  I have all these services running.
+[2014.36 --> 2017.16]  Sometimes I have multiple THCP that I'm testing, etc.
+[2017.56 --> 2020.42]  I don't want that to conflict with my home network.
+[2020.96 --> 2022.24]  So that's where VLANs come in.
+[2022.92 --> 2024.42]  I use VLANs for DMZ.
+[2024.62 --> 2027.20]  Things that I want to expose outside my network.
+[2027.90 --> 2029.04]  VLANs are really about segmentation.
+[2030.74 --> 2034.12]  Take what you need that needs to talk to each other and put it on its own VLAN.
+[2034.12 --> 2036.70]  And that's the way that you should think about it.
+[2037.34 --> 2041.76]  Somehow I've managed to avoid the temptation of VLANs this whole time.
+[2041.76 --> 2045.00]  Because it requires a bit of extra hardware or a bit more advanced hardware.
+[2045.14 --> 2047.90]  So you've got to have a couple of switches that support VLANs.
+[2048.18 --> 2053.74]  And something to configure them at the router level as well.
+[2054.14 --> 2055.76]  So it's not just a plug and play thing.
+[2055.80 --> 2057.80]  You've got to have a bit more about you to do it.
+[2057.80 --> 2062.82]  And I've just kind of swept that one under the carpet and just opened up a bigger subnet
+[2062.82 --> 2066.30]  and put things in different subnets and just kind of prayed and hoped for the best, really.
+[2067.02 --> 2068.02]  That's been my approach.
+[2069.02 --> 2075.04]  I'm sure that most people who are running home labs, you know, they have Ubiquity, Microtech.
+[2075.76 --> 2078.20]  You know, a lot of the equipment that we already have can do it.
+[2078.66 --> 2079.26]  That's a good point.
+[2079.68 --> 2085.08]  I think the biggest issue is that people look at VLANs and they're a little hesitant
+[2085.08 --> 2087.20]  because they're afraid of what it can do.
+[2087.84 --> 2092.62]  I can definitely tell you I've gotten VLANs wrong and I've made a mess of things.
+[2093.14 --> 2094.46]  But that's what a home lab is for.
+[2094.88 --> 2095.62]  Break some eggs, eh?
+[2096.70 --> 2097.14]  All right.
+[2097.16 --> 2099.18]  Well, thank you very much for joining us this week, Morgan.
+[2099.32 --> 2102.38]  It was a very, very last minute that we had to call upon you.
+[2102.80 --> 2106.12]  Because we generally record the night before the show goes out on the Friday morning.
+[2106.12 --> 2109.50]  So we didn't have much time after Chris's laptop got flooded.
+[2110.22 --> 2114.84]  And also a big thank you to our members over at selfhosted.show.sre.
+[2115.08 --> 2116.74]  You can go over there and support the show.
+[2116.88 --> 2121.72]  And obviously we do appreciate that because it goes straight into the JB coffers to support
+[2121.72 --> 2122.62]  the network directly.
+[2122.62 --> 2125.14]  So we don't have to have as many sponsors on the shows.
+[2125.80 --> 2127.92]  Speaking of which, we have to thank A Cloud Guru.
+[2128.18 --> 2130.56]  And you can find them just about anywhere on social media.
+[2130.72 --> 2135.64]  They are slash A Cloud Guru on Facebook, YouTube, Twitter, just about everywhere.
+[2136.64 --> 2140.72]  So for all the different ways to go and get in touch with us, you can go to selfhosted.show
+[2140.72 --> 2143.20]  slash contact is the place to go to get in touch with us.
+[2143.20 --> 2145.42]  And you can find me on Twitter at ironicbadger.
+[2146.10 --> 2148.94]  And I don't have social media because I don't want to be cancelled.
+[2152.14 --> 2156.04]  Oh, well, I know you troll people on Reddit on a regular basis, but you can also find the
+[2156.04 --> 2157.60]  show at selfhosted.show.
+[2158.00 --> 2159.10]  Thanks for listening, everybody.
+[2159.10 --> 2161.74]  That was selfhosted.show slash 48.

49： Update Roulette _summary.txt

@@ -0,0 +1,68 @@
+• Chris Fisher's laptop gets wet while driving
+• Water damages electronics and floods the RV
+• Cause of flood: laptop fell into sink, turned on faucet, and soaked basket of electronics
+• Damage to devices and RV
+• Chris spends 2 hours drying up the water damage
+• MacBook survives the incident despite being exposed to water
+• The host has a phone with a low battery and can't use it in water
+• Discusses feeling frustrated with devices having non-removable batteries
+• Introduces Orthalia, an open-source single sign-on service for managing multiple logins
+• Describes how Orthalia uses rules to determine which services to authenticate for
+• Explains that Orthalia supports two-factor authentication and can add 2FA to services without native support
+• Mentions the benefits of using a service like Orthalia for streamlined login management
+• Discusses the trade-offs between self-hosting and commercial services, with the host sharing his personal frustration with technical issues
+• Touches on the idea that there may be a balance between self-hosting and using commercial services.
+• Docker Hub tagging and updating Nextcloud major versions
+• Resolving a Nextcloud issue due to character encoding problems
+• Troubleshooting with container logs and MySQL command line
+• Deleting data types and tables in MySQL database
+• Upgrading to Nextcloud 22 and resolving issues
+• Backing up data after experiencing multiple hardware and software failures
+• Appreciating the value of cloud providers and their ability to mine user information
+• The importance of having control over digital services and data
+• The trade-off between using cloud services and self-hosting solutions
+• Benefits of hosting own wiki and other information in-house for proprietary purposes
+• Desire to feel a sense of control and confidence when managing personal projects
+• Growing market demand for self-hosted services and increased competition among companies offering this solution
+• Using manual window fans with smart plugs to automate temperature control
+• Discussion of rebuilding infrastructure and using Linode for cloud hosting
+• Linode's features and benefits, including automatic backup service and one-click deployment options
+• Use case example: Milwaukee Linux users group migrating from Zoom to Jitsi on Linode
+• Announcements about upcoming meetups in Denver and Salt Lake City
+• Introduction of a live tracker in the host's RV for meetup attendees
+• Own Tracks API integration with Home Assistant for real-time location tracking
+• Using MQTT for communication between devices and systems
+• Deprecation of commands in ValiTudo robot vacuum firmware update
+• Concerns about system updates and potential disruptions to infrastructure
+• Virtualization as a solution for safety net and backup capabilities
+• Hypervisors and containerization options (e.g. Proxmox)
+• New versions of ZFS (2.04), QEMU (6), and kernel (5.11) in Proxmox
+• Proxmox pushing updates to core systems, addressing Debian's reputation for being "old and crusty"
+• Recent ButterFS support and near-parity with ZFS in Proxmox
+• Importance of taking ButterFS seriously due to its adoption by large companies like Facebook
+• Combination of ButterFS and ZFS in Proxmox for reliable home servers
+• New feature in Proxmox 7: downloading ISOs from the web UI, including automatic verification via MD5 hash
+• Proxmox is open-source and free as in cost (both "free" and "beer")
+• Topics on Ansible exam and managing inventory
+• Nvidia Shield's recent update with ads at top of screen
+• Custom launchers available as alternative to Google provided launcher
+• Switching to Apple TV due to better performance and UI consistency
+• Comparison of Kodi app on Android TV vs InFuse on Apple TV
+• Advertisements on Nvidia Shield driving the user crazy
+• Argument that Nvidia Shield is a premium device despite being $200
+• Nvidia Shield TV users are upset about recent updates that add ads to their interface
+• Some users feel this is a monetization tactic by Nvidia, possibly due to affiliate revenue from streaming subscriptions
+• Alternative solutions mentioned include custom launchers and flashing a different OS (Lineage)
+• Solar panel integration with Home Assistant was discussed, including the process of setting it up with the SolarEdge system
+• Discussing a dashboard and mobile app for monitoring solar activity
+• Security implications of sharing Ansible playbooks publicly on GitHub
+• Using Ansible Vault to encrypt sensitive information
+• A listener's comment about a passwords.txt file being left unencrypted on the hoster's GitHub repository
+• The importance of treating private repositories as if they were public and following good security hygiene practices
+• Upcoming episode topics, including the future of gasoline engines and internal combustion engines
+• The host's personal experience with a restored Union Pacific steam loco, the Big Boy
+• Discussion of a long road trip to Denver
+• Recap of a previous 5,000 mile road trip from Orlando to DC and then to Denver in 2018
+• Invitation to attend meetups for the Jupyter Broadcasting show
+• Reminder about the upcoming episode (50) with possible swag giveaways
+• Host contact information on Twitter and the show's website

49： Update Roulette _transcript.txt

@@ -0,0 +1,588 @@
+[0.00 --> 3.68]  Well, I'm pleased to welcome back to the show, Mr. Chris Fisher. Welcome back, Chris.
+[3.92 --> 7.34]  Thank you, Alex. I just got done drying everything off only a few moments ago.
+[7.64 --> 12.78]  We missed you, man. So it's story time. I need to stay a while and listen.
+[13.24 --> 19.18]  Yes. And first of all, thank you to Morgan for filling in. I, at the last minute, had to jump
+[19.18 --> 26.16]  out when I realized that my laptop had got soaked and I didn't want to turn it on. And so I told
+[26.16 --> 31.14]  Alex, you got to find somebody to fill in for me. All right. So I was setting up to go camp out in
+[31.14 --> 35.66]  the woods, brief story. And I wanted to get out to the woods and get set up in time for the show.
+[35.86 --> 41.12]  And so I was in a bit of a rush and I thought, cause I'm an idiot. I thought, Hey, you know,
+[41.12 --> 46.44]  it'd be a great idea is I'll do some updates on this laptop. And I've got this really old 2013
+[46.44 --> 52.20]  Mac book that runs Arch Linux, by the way. And so it's, for me, it's like this thrill to boot it up
+[52.20 --> 57.16]  about once every six months and see if when I do an update, if the installation explodes or not.
+[57.16 --> 61.36]  Right. So I thought, well, I'm running around packing up the RV. I'll set this thing to do
+[61.36 --> 65.86]  some updates just so I can, you know, have like a little thing to do for my ADD brain
+[65.86 --> 71.08]  and check in on it. And so I'm packing up and I go around and I collect all of my electronics
+[71.08 --> 75.58]  because I, my kids and I had been going through some stuff. And so we had, the fire tablets were
+[75.58 --> 80.38]  down off the wall that we use to control home assistant, our front end and some game controllers
+[80.38 --> 84.02]  were out and we're going down the road and we want to get there quick. So I just took this basket
+[84.02 --> 88.76]  and like a good little boy, I picked up everything and put it in my basket. Now, of course, I don't
+[88.76 --> 94.70]  want that basket to spill. So I, I set it in the back in the bathroom and finished up my laptop and
+[94.70 --> 100.62]  closed the lid and went about packing up the rest of the RV. I'm driving down the road for probably
+[100.62 --> 106.74]  20, 25 minutes. And I realized I should probably get gas because I'm going to be off grid for a while.
+[106.74 --> 110.02]  And if for some reason we don't get good solar, I'm going to need to be able to run my
+[110.02 --> 115.62]  generator. So I, I, I pull up to a gas station and I start to pull in, which is a downhill kind
+[115.62 --> 120.44]  of turn in. And as I pull into the gas station and begin to decline down into the parking lot,
+[120.56 --> 126.48]  I hear like, like a wave sound behind me. Like, I'm like, is there a noise maker on? And I,
+[126.56 --> 131.76]  I turn around and look over my shoulder, Alex, and I see this wave of water coming down the middle
+[131.76 --> 137.88]  of the hallway of my RV. It sloshes down into the, into the, into the step. Well, it's all over the
+[137.88 --> 141.22]  place. It's coming down into my feet while I'm driving. It was everywhere.
+[141.68 --> 147.94]  How tight did your asshole pucker when you saw that Alex in like one motion, I like grabbed the
+[147.94 --> 152.62]  radio and I radio to my wife. Cause she's chasing me in the car behind there. You got to get in here
+[152.62 --> 159.96]  quick. We got an emergency. I throw the radio down. I parked the RV stand up and I began just walking
+[159.96 --> 166.22]  straight to the back. And as I approach the back of the RV, I hear a sound. I immediately recognize
+[166.22 --> 175.78]  it's my water pump and it's pumping and it's pumping and it's pumping. It shouldn't be on,
+[175.84 --> 182.52]  but in our rush to leave, I had left it on and didn't notice. And so I flip it off as I opened
+[182.52 --> 188.06]  the door and I look right at the sink or where I just instinctively knew the problem was going to be
+[188.06 --> 193.84]  somehow I knew. And I could immediately see the entire chain of events. I had left that big old
+[193.84 --> 200.58]  heavy MacBook on the counter. And when I went down the road, it slid down the counter, slid just right
+[200.58 --> 208.86]  and fell into the sink. And as it fell, it turned the faucet on, which is where my basket full of
+[208.86 --> 215.30]  electronics was sitting. Oh no. That be turned that, that Alex, it turned into a bathtub. Alex, it was,
+[215.40 --> 220.62]  it was so bad, Alex. It soaked everything. And then proceeded to spill out from there into the rest
+[220.62 --> 227.48]  of the RV at about, about, about 17, 17, 15, 20 gallons ish. It's hard to say. Yeah. Got the
+[227.48 --> 233.24]  laptop, got all the fire tablets, got the game controllers, got all the charging bricks, everything,
+[233.36 --> 241.16]  not to mention flooded the RV. I, I, I had to act quick. And so thankfully I was able to position the
+[241.16 --> 245.56]  RV in such a way that it kind of tilted it. So I could just get all the water to pour out into one
+[245.56 --> 251.44]  direction. And then I just spent like two hours drying it up. And then we moved out to our spot
+[251.44 --> 256.54]  in the woods and then spent another couple of hours trying to dry it all out. I lost a lot of devices.
+[256.86 --> 264.96]  A lot of good devices died that day, Alex, but not that stupid old MacBook. It's still kicking,
+[265.10 --> 268.40]  even though it got water in the event in the vents and all of that, it's still kicking.
+[268.40 --> 274.10]  So the device that caused the problem just ran away going, tee, not today.
+[274.28 --> 278.44]  It's doing great. Yep. Although it's power adapter bit the dust. So I don't know exactly
+[278.44 --> 279.80]  what its long-term plan was.
+[279.90 --> 282.00]  That's like cutting your nose off to spite your face, isn't it?
+[282.16 --> 286.50]  That's why you should plan and plan to learn. Visit our sponsor, Cloud Guru,
+[286.64 --> 289.18]  the leader of learning for the cloud, Linux, and other modern tech skills,
+[289.52 --> 293.74]  hundreds of courses, and thousands of hands-on labs. Get certified, get hired,
+[293.82 --> 295.78]  get learning at a cloudguru.com.
+[295.78 --> 301.82]  That story just hurts me so deeply because water and electronics, you just have this
+[301.82 --> 308.52]  pathological thing that they don't go, they just don't mix. I've probably missed out on
+[308.52 --> 312.30]  several experiences in my life because I had a phone in my pocket. I'm like, well,
+[312.48 --> 317.14]  I'm not going to go and run in the ocean or whatever it is because I've got a phone in my pocket.
+[317.54 --> 323.36]  And so many devices, obvious statement time, but I really was feeling this. So many devices
+[323.36 --> 326.78]  have the battery built in. And so there's just nothing I can do.
+[326.98 --> 329.40]  Yeah. Damn, man. I feel your pain.
+[329.62 --> 330.24]  I really do.
+[331.50 --> 335.44]  It was rough. It was rough. And so now I have to selectively choose what I'm going to replace
+[335.44 --> 337.24]  and what I'm just going to try to live without.
+[337.62 --> 339.04]  Oh yeah. And you just missed Prime Day.
+[339.94 --> 344.12]  I know. I crossed my mind because I had a couple of fire tablets in the mix.
+[344.62 --> 344.90]  Gone.
+[345.54 --> 346.36]  Womp womp.
+[346.36 --> 349.74]  All right. So you got something to cheer me up.
+[350.12 --> 354.46]  Well, I was watching YouTube the other day, as is often the case in my household. And I was
+[354.46 --> 360.60]  watching a video by Techno Tim and he did an Orthalia introduction. It is a single sign on
+[360.60 --> 368.64]  service that basically allows you to have one login cookie get set, which then allows you to log into
+[368.64 --> 374.62]  all of the services that you select through a set of rules that you configure to say, right, if I want
+[374.62 --> 381.82]  to access NextCloud, as long as I've got this token set, then I'm all good. And then you could do it for
+[381.82 --> 388.10]  a wiki or any of the services that are running on your system. And the really nice thing is it's
+[388.10 --> 394.14]  configured with a single line of Docker Compose configuration. So you just add a single line to
+[394.14 --> 398.34]  declare that you want to use Orthalia as what's called a piece of middleware in the traffic
+[398.34 --> 402.26]  configuration. And you're good to go. And that's it.
+[402.88 --> 408.54]  I see. So it is, first of all, we should mention it's open source. And it essentially takes
+[408.54 --> 414.14]  authentication requests using Nginx and provides the authorization for those authentication requests.
+[414.84 --> 419.92]  Yeah, not just Nginx, it supports traffic as well as a bunch of others. And it actually,
+[420.20 --> 425.30]  more recently, supports Kubernetes ingress controllers, which is nice as well.
+[425.62 --> 427.88]  All right, I'm checking it out right now. And it actually looks like it has a pretty
+[427.88 --> 435.42]  good interface too. So this will have linked in the show notes, or you can go to A-U-T-H-E-L-I-A.com.
+[435.58 --> 439.78]  Yeah, you don't really need a whole bunch of interface for a login client. Essentially,
+[439.86 --> 444.00]  what happens when you have a service that's backed by this, let's say I go to wiki,
+[444.40 --> 449.30]  my personal wiki, my tiddly wiki, traffic will detect that I've set that piece of middleware as
+[449.30 --> 454.56]  part of the chain of traffic that it wants to go through. And so Orthalia will then pop up a
+[454.56 --> 459.26]  standard web form. I'll type in my username and password. It does support two-factor authentication.
+[459.72 --> 465.94]  So even for services that don't have 2FA natively, I can use Orthalia to add
+[465.94 --> 472.74]  2FA to those services as well. And then just transparently, that token lasts for the length
+[472.74 --> 477.08]  and duration of your session. You can figure how long it is. I think it's five minutes by default.
+[477.62 --> 482.94]  Any other service that has the same rule on your system, it will reuse that authentication token.
+[482.94 --> 486.14]  So if you're switching between a bunch of different services on your system,
+[486.92 --> 490.50]  log in once and you're logged into all of them all at once automatically.
+[491.10 --> 494.10]  Boy, that does seem nice. It has a lot of great features in here.
+[494.72 --> 499.20]  All right. Well, it sounds like something to check out. We talk about this kind of stuff. Also,
+[499.40 --> 504.00]  when we talk about things like hosting your own password manager or hosting your own email,
+[504.26 --> 507.72]  I wonder if there's an audience and I wonder if you out there too, I wonder if there's a portion of
+[507.72 --> 514.74]  the audience that thinks, I'd never want to host this. This crosses a line. This breaks and things
+[514.74 --> 520.52]  get hosed. And so I wonder if there isn't just a discussion to be had there, Alex, about where
+[520.52 --> 524.28]  that line is for us. And if we ever consider dropping something and saying, you know what,
+[524.40 --> 526.20]  I'll just go with a commercial service for this.
+[526.20 --> 533.16]  Is this grumpy old man, Alex, coming out here? But my tolerance for stuff breaking,
+[533.94 --> 541.26]  be it an update, be it a dodgy power cable, whatever the reason, my tolerance is so low these days.
+[541.62 --> 546.48]  And a couple of episodes ago, I mentioned I had my server on the desk next to me because I was
+[546.48 --> 551.60]  troubleshooting some issues with hard drives failing. Turns out it wasn't the hard drives failing.
+[551.60 --> 557.76]  And I wasted maybe three weeks on trying all sorts of different drives and cables and disc controllers.
+[558.22 --> 563.90]  No, it was the power cable from the power supply to the drives. No kidding. I wasted three weeks on
+[563.90 --> 569.38]  that damn thing. And that just left me with a huge bitter taste in my mouth. And, you know,
+[569.40 --> 575.76]  I'm not going to stop self-hosting. Don't, don't worry, audience. We're okay. But there were just
+[575.76 --> 581.16]  moments in that three week period. I was like, screw this. I just want to throw the towel in and just be
+[581.16 --> 586.24]  done and just pay Netflix or whoever it is. Wow. You know, in that same period of time,
+[586.28 --> 590.18]  I think you also had a certain Home Assistant update not go so well, too. So you were really
+[590.18 --> 594.76]  getting it from both ends. Yeah, that's the thing. And, you know, this week, another example is
+[594.76 --> 601.08]  Nextcloud just stopped working for some reason. I have no idea why. I've been sat on Nextcloud 19
+[601.08 --> 607.98]  for the last year plus. I haven't touched it. I pull in the regular updates that they provide
+[607.98 --> 616.08]  to the 19 branch through Docker Hub tagging. But I don't update major versions on Nextcloud unless I
+[616.08 --> 621.38]  have a good reason to because I don't want all of the new stuff. I just use it for documents. That's
+[621.38 --> 625.48]  pretty much it. Right. I actually figured this out because I got a notification on my phone
+[625.48 --> 630.26]  because photo upload stopped working. It said this server is in maintenance mode. And I'm like,
+[630.64 --> 637.34]  OK, yeah, I remember. I've had this before. So you Google it. First result says go into the config file
+[637.34 --> 644.26]  and edit a single line that says change maintenance mode from true to false in the config.php file.
+[645.42 --> 651.62]  So I did that. It was already set to maintenance mode false. So I'm like, OK, well,
+[651.62 --> 656.64]  clearly something's going on here. So I then start looking into the Nextcloud container logs.
+[657.40 --> 666.12]  And then it said something about character encoding, UTF-8 char sets. And I just at that point,
+[666.16 --> 671.30]  I was like, oh, no, here we go. This is going to be a long evening. Long story short, I ended up
+[671.30 --> 679.40]  having to go into the MySQL container itself with a Docker exec command, get into the MySQL nitty gritty
+[679.40 --> 687.52]  details, delete and change a couple of data types from Varchar to text fields and all this, you know,
+[688.12 --> 694.18]  stuff that's way over the head of most people doing self-hosting unless this is your day job.
+[695.04 --> 700.44]  And I just thought to myself, who is this stuff targeted at? If I was paying for Nextcloud as a
+[700.44 --> 707.72]  hosted service, I mean, these things exist. Like Google Drive is similar. OneDrive, you know,
+[707.72 --> 713.24]  all these different cloud file repositories. If these things broke and I had to jump through all
+[713.24 --> 718.94]  these different hoops to fix them, I would just migrate to a different service. And yet, because
+[718.94 --> 726.54]  I feel a certain sense of obligation, partly because of this show, but also partly because of my beliefs
+[726.54 --> 733.94]  towards self-hosting in general, I power through it. But sometimes I just want to throw the towel in,
+[733.94 --> 738.24]  you know. Did you ever get to the root of why that Nextcloud issue just cropped up?
+[738.90 --> 743.26]  I think it was because of the character encoding. So what I ended up doing as part of the
+[743.26 --> 746.64]  troubleshooting process was like, right, okay, well, I'm in the weeds here. I may as well go to
+[746.64 --> 748.22]  Nextcloud 22 whilst I'm here.
+[748.66 --> 750.48]  Yeah, that would be my line of thinking too.
+[751.38 --> 756.82]  Yeah. And then I thought it didn't start because I thought, oh, some database schema changes have
+[756.82 --> 763.30]  probably happened and it's just not tested properly on 19. Okay, fine. I'll go to the next major release.
+[763.30 --> 769.66]  That's stable. Yeah. And so like I said to you, I had to drop to the MySQL command line,
+[769.96 --> 776.14]  delete a couple of tables that were failing the repair because there's an OCC command. So you can
+[776.14 --> 783.94]  log into the Nextcloud container and run, there's like a shell, like a CLI tool built into it called
+[783.94 --> 790.42]  OCC. OwnCloud Client, I would imagine is what it stands for. Don't quote me on that. And you can do a
+[790.42 --> 793.66]  bunch of maintenance stuff, like you can turn maintenance mode on and off, you can repair
+[793.66 --> 797.96]  things, et cetera, et cetera. And it kept failing on this line item to do with news articles,
+[797.96 --> 802.42]  which is a plugin I don't even use anymore. I think I enabled it for testing and then forgot
+[802.42 --> 808.74]  about it. And much like my Home Assistant update, I probably missed it in the logs because I don't
+[808.74 --> 815.18]  necessarily look at the logs every day because I've got other stuff to do. And yeah, once I deleted the
+[815.18 --> 820.44]  news, once I'd gone into the correct database table and then deleted the three or four lines
+[820.44 --> 825.92]  that were causing the schema migrations to fail, then the upgrade proceeded and it was all fine.
+[826.04 --> 827.54]  But it took me a couple of hours.
+[828.00 --> 833.46]  I've had those moments where I thought maybe like a server was dead and gone. And I thought,
+[833.56 --> 838.96]  I don't, I don't know if I, I don't know if I ever want to rebuild this. And then thankfully
+[838.96 --> 841.78]  they came back and then I thought, okay, I better get my backup game.
+[841.78 --> 846.86]  I better get my backup figured out. Yeah. Cause I mean, you really got it. I mean,
+[846.88 --> 850.74]  you got a hardware failure in your server. You got a software failure in Nextcloud,
+[851.14 --> 856.38]  a Home Assistant, a pretty dramatic Home Assistant failure based on some deprecation and changes.
+[856.80 --> 863.38]  I mean, you got it one after another. I recently also had a Home Assistant update go south when the
+[863.38 --> 868.82]  OS update didn't complete correctly. The system locked up and then rebooted. And then it couldn't
+[868.82 --> 874.08]  get an IP until I had fiddled with it for quite a while. And for a brief moment, I thought to myself,
+[874.08 --> 879.52]  should I just bail on this and maybe just go back to a traditional server and Home Assistant core
+[879.52 --> 884.34]  container and just keep it simple. And then it gets working again. And then I think, okay, no,
+[884.40 --> 889.42]  this is better. And I like this. And I think to myself in the grand scheme of things, this is the
+[889.42 --> 895.92]  cost of having full control over these services. And, and it does give me a better appreciation of the
+[895.92 --> 902.64]  value that the cloud providers are offering. And it makes me also understand how valuable my data
+[902.64 --> 908.10]  must be if they can pay for these services based on mining my information. Like, wow, there must be
+[908.10 --> 913.76]  some real value there because it's not cheap. And to keep something reliable like file services for,
+[914.18 --> 918.04]  you know, a 10 year streak actually takes an incredible amount of effort.
+[918.38 --> 922.40]  Yeah, you're not wrong. I mean, these, these guys, they're our entire jobs, you know,
+[922.40 --> 928.18]  site reliability engineers. That's the name of our, you know, supporters club that we have. And
+[928.18 --> 935.26]  there's an entire job dedicated to keeping things up and stable and reliable. And these guys,
+[935.36 --> 940.30]  they write software, they write scripts, they do all sorts of ninja magic to keep these services online.
+[940.88 --> 945.50]  I think part of it, Alex, is giving yourself, and you've done this, you know, the ability to rebuild
+[945.50 --> 950.66]  fairly quickly. Like you do that. You make, you make, if you adopt something, you make sure that
+[950.66 --> 957.84]  you can redeploy it as necessary. And those kinds of things, I think they help a lot. But I think
+[957.84 --> 962.70]  this show should ask the question more often, is there a cloud service that could do this?
+[963.16 --> 968.00]  And if there is, why are we not choosing to use it? Because it is a big trade-off every time.
+[968.34 --> 972.66]  And the more critical the service is to you, I think the more serious you have to consider that.
+[972.98 --> 975.72]  I'm trying to think of a good example. I suppose wiki would be a decent one.
+[975.72 --> 981.44]  Because you can probably throw some stuff up on GitHub in a random repository,
+[981.76 --> 990.98]  a bunch of text files, and call that a wiki if you want to. You could also go to some random website
+[990.98 --> 996.96]  and buy probably wiki capabilities. But there's nothing quite like hosting your own and keeping
+[996.96 --> 1005.12]  that kind of information in-house. Because the role a wiki in particular fulfills often is to store
+[1005.12 --> 1011.52]  proprietary, you know, custom information, you know, maybe Wi-Fi passwords for your house or
+[1011.52 --> 1016.42]  something, or the code to the safe so that your wife can open it when you're out or something. I don't
+[1016.42 --> 1023.66]  know what people store in their, you know, wikis. But there could be some sensitive information in there.
+[1023.66 --> 1028.48]  Sounds like you have a code for a safe that if I was ever on your LAN, I should try to get that code.
+[1028.82 --> 1030.26]  I've got to buy the safe first.
+[1031.26 --> 1035.42]  I was like, he has a safe? Oh, okay. But it's a good example. You're right. I have been thinking,
+[1035.60 --> 1042.02]  like, how could I leave my wife notes in a way that is fully secure? And there is this feeling
+[1042.02 --> 1047.98]  that I think is actually pretty special. And it's this total feel of control. And I feel this when I
+[1047.98 --> 1054.36]  am off-grid, and I'm generating my own power, and I've brought my own food, and I don't need anyone
+[1054.36 --> 1061.90]  to do anything. For a brief moment, I feel like I'm truly in control. And I have that same sense when
+[1061.90 --> 1069.04]  it comes to everything being offline in my RV, and being self-contained to the RV, and having
+[1069.04 --> 1074.30]  gone through this project off-grid where I offloaded a bunch of services and got everything running
+[1074.30 --> 1082.44]  locally. When I get access to that stuff, it's like this feeling of confidence that we get so
+[1082.44 --> 1086.88]  sparingly now. With so many cloud services that are integrated with our mobile devices,
+[1087.06 --> 1093.42]  or integrated with commercial desktops, less and less consumers and technology users have control.
+[1093.60 --> 1098.32]  Less and less. They have less control than ever of modifying their devices, of controlling their
+[1098.32 --> 1103.74]  devices, or even determining who has access to their data, or if it can be scanned, or any of that.
+[1103.74 --> 1109.46]  And so when we have these areas, we can actually exercise that control. We have to keep doing it,
+[1109.56 --> 1115.66]  or else it will go away. If there's no users of these self-hosted services, and if there's no
+[1115.66 --> 1124.00]  market demand for this control, eventually the developers and the companies that serve that niche
+[1124.00 --> 1129.42]  will dry up. And so it's like you have to always be looking like, where can I exercise that control?
+[1129.50 --> 1132.94]  Where does it matter the most? And that's kind of where I've come down on it. It's like, okay,
+[1132.94 --> 1137.70]  this information, like secret stuff I want to give my wife, that is always going to be
+[1137.70 --> 1143.06]  on my land. Like, I'm just never going to put it anywhere else. And thankfully, you know,
+[1143.08 --> 1146.24]  I've come up with a little system where it's just some markdown files. It's really simple. It's not,
+[1146.28 --> 1148.66]  it's not, it's not a big effort to actually do it.
+[1149.18 --> 1155.66]  You are right. There are an increasing number of companies doing stuff for this marketplace. You know,
+[1155.66 --> 1161.12]  Tuya, we talked about it last episode with Morgan, have announced a native home assistant
+[1161.12 --> 1166.12]  integration as part of their product line. You know, so these things are happening and you see,
+[1166.22 --> 1171.66]  what's his name? Linus Sebastian has just bought a new house and he was talking about how he's going to
+[1172.30 --> 1177.62]  implement smart dampers in every room. So he's not air conditioning every room and how there is lots of
+[1177.62 --> 1181.86]  proprietary services that could do this stuff and how it's just all so overwhelming. And
+[1181.86 --> 1186.38]  I think that's largely what I'm feeling too. It's just a bit overwhelmed by the amount of stuff I
+[1186.38 --> 1192.64]  could do. You know, it's not even necessarily just when stuff breaks. It's, it's that feeling of once
+[1192.64 --> 1196.80]  I put my daughter to bed or something in the evening of, okay, I've got a couple of hours before I go to
+[1196.80 --> 1202.90]  sleep now. I don't want to just sit and veg and watch cartoons necessarily. I'll do that whilst I'm
+[1202.90 --> 1207.96]  doing something else. But what out of my huge long list of ideas that I've got, should I pick and
+[1207.96 --> 1213.60]  oh, I can't be bothered. I'll just watch cartoons. You know, what I've been doing is like the really
+[1213.60 --> 1221.84]  simple stuff. Uh, I went through my, uh, home assistant dashboard and I made individual, I chose
+[1221.84 --> 1227.28]  like individual icons for each entity. So each light bulb has like a unique light bulb icon, really just
+[1227.28 --> 1234.52]  slow kind of paced work while I was watching Rick and Morty, you know, and so it's like not very high
+[1234.52 --> 1239.44]  cognitive load, but I can sit there and fiddle with something. Um, and then the other thing that
+[1239.44 --> 1243.32]  I did recently, it was, it was one of those moments where I was like, I don't need to build something
+[1243.32 --> 1249.12]  complicated here. I could just get a couple of window fans off of Amazon that have manual controls,
+[1249.76 --> 1254.56]  plug them into some smart plugs, and I could have some set to input and I could have some set to output.
+[1255.56 --> 1260.08]  And then I could just set up automations to turn the smart plugs on and off. And it was one of those
+[1260.08 --> 1265.30]  moments where I was like, I could just do something very simple for cooling and it would probably take
+[1265.30 --> 1271.14]  me 35 minutes to set it all up. And I was so down in the weeds with all of these things. Like I could
+[1271.14 --> 1276.36]  build a new virtualization backend and then I could set up individual host OSs and then put containers
+[1276.36 --> 1280.04]  in there. Like I was going through this entire thing about how I wanted to rebuild all of the
+[1280.04 --> 1283.74]  infrastructure. And then I thought, you know what else I could do is I could just spend 30 minutes
+[1283.74 --> 1288.26]  doing this tonight and I'll spend 30 minutes doing that tomorrow. And over a couple of nights,
+[1288.26 --> 1290.76]  I got it all done. If it works, it ain't stupid.
+[1292.38 --> 1299.26]  Linode.com slash SSH. Go there to support the show and get $100 in credit on a new account.
+[1299.82 --> 1303.18]  Linode is our cloud hosting provider. When we're building something that we want to experiment
+[1303.18 --> 1307.54]  with, we do it on Linode. There's a lot of quick ways to deploy. They have 11 data centers to choose
+[1307.54 --> 1312.30]  from. They have crazy fast network connections and a whole range of types of servers. So if we want
+[1312.30 --> 1318.12]  something simple, we'll get like a $5 a month system. But sometimes we want some dedicated CPUs or GPUs.
+[1318.26 --> 1323.54]  They have a lot of choices. Roger wrote into the show to say that he used Linode to replace
+[1323.54 --> 1328.88]  Zoom with something he can host himself. He says, along with just about everybody else,
+[1328.96 --> 1334.74]  the Milwaukee Linux users group had to go to virtual due to COVID-19. And as you might expect
+[1334.74 --> 1339.82]  from a group of Linux users, they weren't a big fan of using Zoom. They wanted to use Jitsi.
+[1340.04 --> 1345.90]  So they looked around at different providers and they chose Linode. They picked the $5 a month
+[1345.90 --> 1350.86]  machine and they also chose to do the automatic backup service. So that way there's just backups
+[1350.86 --> 1356.74]  that are just taken care of. They installed Jitsi Meet on that system and they're now using it with
+[1356.74 --> 1362.92]  NextCloud Talk to do the video calls for their lug, all running on Linode. You know, what's really nice
+[1362.92 --> 1369.92]  about this too is, is Roger was able to prototype Jitsi and NextCloud and try them all out really quickly
+[1369.92 --> 1374.80]  in environments that are production style environments. So you could really get a sense
+[1374.80 --> 1380.14]  for how it's going to perform. And it's pretty great because at one point they made a change to
+[1380.14 --> 1387.64]  NextCloud just before the lug meeting and it broke. So Roger says they were able to use the snapshots
+[1387.64 --> 1393.12]  that they got with the automatic backups and just roll it back. So it was basically a non-issue.
+[1393.12 --> 1397.86]  And then after the lug was over, they were able to continue on with the NextCloud update.
+[1398.38 --> 1402.52]  And that's just an example of how you can use Linode, you know, to run your own Zoom instance.
+[1402.70 --> 1407.88]  Or they also have a one-click deployment for Owncast, which is essentially a Twitch in a box.
+[1408.56 --> 1413.18]  You can use it for that as well. There's so many different choices from hosting your website to
+[1413.18 --> 1418.56]  their object storage. Like I use it for like a sync thing instance. Just go try it out,
+[1418.56 --> 1424.76]  learn something, and experiment with that $100 and support the show at linode.com slash SSH.
+[1426.82 --> 1432.42]  Now, in case you haven't heard, we're getting together in Denver. I'm looking forward to this.
+[1432.96 --> 1437.58]  And not only is Alex going to be there, but he's going to be our trivia master at the meetup.
+[1437.98 --> 1439.90]  So you got to come just to say hi to Alex.
+[1440.24 --> 1443.80]  Looking forward to that. I've been working hard on the trivia questions. I promise you.
+[1444.22 --> 1448.02]  There'll be a bunch of Linux questions. There'll be some, you know, general knowledge stuff,
+[1448.02 --> 1453.20]  but there's also going to be some like older, more esoteric hardware questions as well. I've been
+[1453.20 --> 1459.06]  having a real fun digging out some of these questions. I'm looking forward to that. So we'll
+[1459.06 --> 1463.34]  have the meetup details. We have two meetups actually planned. Alex is going to be the Denver
+[1463.34 --> 1468.28]  meetup, but there's also a Salt Lake City meetup on the books. Details are over at meetup.com
+[1468.28 --> 1474.86]  slash Jupiter Broadcasting. And then additionally, in Lady Joupes, my RV, I will have a live tracker.
+[1474.86 --> 1479.46]  And if there, and there will be more details. And if it works out, we'll do a little micro meetup.
+[1479.62 --> 1484.66]  Could just be, you know, just come by and say hi. And we'll have this embedded webpage that you'll
+[1484.66 --> 1490.02]  be able to view over at colony tracker dot live. That'll show you right where we are at. It's all
+[1490.02 --> 1496.04]  in the works right now. Just in this last week, we got the backend set up for own tracks to record
+[1496.04 --> 1498.98]  where I'm actually going to be at. And that's a pretty neat deal, Alex.
+[1499.22 --> 1500.98]  How are you doing that? Is that on Linode or something?
+[1500.98 --> 1504.22]  Oh yeah, of course. Naturally.
+[1504.74 --> 1512.20]  Yeah, of course. Yeah. Yeah. In fact, we just decided to do a dedicated lower end Linode because
+[1512.20 --> 1515.68]  what we want to do is put a little website on there that has the details and stuff. And then
+[1515.68 --> 1520.36]  own tracks itself is kind of like in multiple components. And so the recorder is a Docker
+[1520.36 --> 1525.32]  image that you can deploy. And that's like a lightweight backend that stores the location
+[1525.32 --> 1530.96]  data. And you can publish your location information to it in two different ways, either over
+[1530.98 --> 1537.34]  HTTP or over MQTT. And then the recorder, as the name implies, records the information
+[1537.34 --> 1543.12]  and then makes your location data available, which is all completely under your control
+[1543.12 --> 1549.28]  via a various set of APIs, some of which can integrate directly into home assistant. So
+[1549.28 --> 1554.06]  you can actually use own tracks to provide home assistant with your real time location, which
+[1554.06 --> 1559.20]  is a fantastic way to control automations. And one way that we use this, not with own tracks
+[1559.20 --> 1565.18]  today, but soon is when no one is at home. If some of the lights, which always happens,
+[1565.30 --> 1571.46]  get left on, which never fails to get left on, then if no one's home and it's, and a certain
+[1571.46 --> 1576.10]  amount of time has passed, the lights just automatically turn off. And that's just a simple way to use
+[1576.10 --> 1582.28]  the automations. Or in the winter, if we're approaching and it's cold, the heating turns on.
+[1582.52 --> 1585.34]  Really simple stuff, that stuff that we just don't want to even have to think about.
+[1585.34 --> 1591.76]  And, but the key is getting your location into home assistant and own tracks can essentially
+[1591.76 --> 1598.24]  be that source of information. I'm using it for a live embedded map on a webpage. So that way you
+[1598.24 --> 1602.84]  guys can find me and we can meet up and I'll be running the own tracks client, which publishes
+[1602.84 --> 1605.40]  that information to the recorder on my pixel.
+[1605.86 --> 1608.20]  That's so cool. And it uses MQTT to do that.
+[1608.44 --> 1612.80]  Yeah, isn't it? It's clever. It seems like it actually a great use of it because you could see
+[1612.80 --> 1617.40]  how, when you have maybe a loss of connectivity, it could queue up. And then when you connect,
+[1617.44 --> 1622.28]  it can just transmit the bits that were queued while you had no signal. It's, it's really smart.
+[1622.66 --> 1628.18]  Perfect. It's exactly what it was designed for. Now my favorite robot vacuum firmware,
+[1628.32 --> 1632.98]  ValiTudo, had a big release last month and I finally got around to updating it and installing
+[1632.98 --> 1637.76]  it this week. I'm a glutton for punishment, aren't I? There's lots of stuff breaking and I still
+[1637.76 --> 1641.12]  go ahead and install these updates. And guess what?
+[1641.36 --> 1641.52]  What?
+[1642.72 --> 1643.72]  Did it break?
+[1644.28 --> 1649.78]  Well, I mean, no, the updates went fine, but there'd been some changes to how the,
+[1649.78 --> 1656.38]  the vacuums get communicated with from Home Assistant. They've deprecated the vacuum.send
+[1656.38 --> 1661.76]  command, which was what I used to say, hey robot, go, you know, hoover the bedroom or something.
+[1661.76 --> 1670.68]  Um, and they've deprecated it for an MQTT publish command. So we're both using MQTT here in wildly
+[1670.68 --> 1674.44]  different use cases, but I just think that's so cool how it's the same technology.
+[1675.00 --> 1680.24]  It is pretty neat. And I, just as a side note, I, I hate it when stuff like that gets deprecated.
+[1680.24 --> 1685.56]  Like I think, I think the whole Z-Wave stack that I'm using in Home Assistant has been deprecated
+[1685.56 --> 1690.86]  and I just don't want to reset up my Z-Wave network. And I don't know what that migration process
+[1690.86 --> 1694.84]  is like, and I just don't want to deal with it. And that kind of goes back to your topic earlier.
+[1694.84 --> 1700.46]  It's like, it's working. It's just, I don't, I don't want to break it. I don't want to have to
+[1700.46 --> 1705.24]  do anything with it because it's just so part of my infrastructure. Now it no longer feels like a
+[1705.24 --> 1709.94]  separate system. It feels like it is part of my home and I don't like messing with that stuff
+[1709.94 --> 1716.48]  anymore. And equally, because it is part of the house, the uptime needs to be as close to a hundred
+[1716.48 --> 1721.70]  percent as possible. Yeah. And then you have to balance that off against applying updates because
+[1721.70 --> 1725.96]  it's part of your house. You don't want to not update it for 10 years. I mean, some people would
+[1725.96 --> 1731.14]  just say if it's working, leave it, but I keep it up to date because I feel like I want to be
+[1731.14 --> 1735.46]  compatible with future technology and future functionality. I mentioned to you earlier,
+[1735.46 --> 1740.12]  I was like, maybe I should rebuild the whole setup and I should base it on virtualization because the
+[1740.12 --> 1745.46]  safety that a virtual machine gives me, that's that snapshot capability. And that, that holistic
+[1745.46 --> 1750.26]  restoring of a system or, or taking a copy of it and setting it on a shelf and saying,
+[1750.38 --> 1756.70]  this is known good. That is so appealing to me. And it feels like it gives me a safety net to what,
+[1757.18 --> 1761.32]  what seems like a risky proposition to keep updating all of these systems all the time.
+[1761.84 --> 1765.76]  That's where I keep thinking, maybe I got to rethink the way I'm doing stuff. And that's where I,
+[1765.88 --> 1769.40]  that's where I go down the rabbit hole and go, oh, it's too much. Not right now.
+[1769.40 --> 1772.58]  Do you use a hypervisor at all for, for anything?
+[1772.58 --> 1777.44]  No, right now the system's built around these Raspberry Pis. There's not a lot of overhead
+[1777.44 --> 1783.94]  there. So I'm just running containers on Ubuntu LTS on Pi 4, but I would be willing to replace,
+[1784.14 --> 1790.66]  you know, the two or three Raspberry Pis it takes to do this with one fairly low energy x86 machine.
+[1790.66 --> 1795.10]  And then I'd have sort of my, my, you know, my, my choice of virtualizers at that point.
+[1795.10 --> 1800.32]  Well, good news for you. Proxmox have just had a big release. Version seven was released on the 6th of
+[1800.32 --> 1807.30]  July, 2021, and it's based on Debian bullseye number 11. I'm sure most of you know this bit
+[1807.30 --> 1811.76]  of trivia, but, uh, those of you coming to the Denver meetup might want to pay attention.
+[1812.10 --> 1814.24]  I might've given a question away there. Damn it.
+[1815.28 --> 1818.70]  I love it. No, that's good. That's good. Cause if they're a listener,
+[1818.82 --> 1820.98]  they get a heads up and no one else will know.
+[1821.18 --> 1827.16]  Free trivia question coming your way. Which kids movie does Debian name its releases after?
+[1827.16 --> 1831.44]  Maybe you'll know, maybe you won't. Uh, it's just the sort of thing you'll have to come to the
+[1831.44 --> 1836.28]  meetup and find out about. All right. Now what else is included in this release? They've got a bunch
+[1836.28 --> 1844.78]  of new versions of stuff. So ZFS is now 2.04, uh, QEMU has been bumped to version six and the,
+[1844.78 --> 1850.78]  there's a new kernel 5.11. So it's, it's really good to see that Proxmox are pushing the envelope
+[1850.78 --> 1856.34]  here and updating lots of their core systems. The reason I say that in particular is because Debian has a
+[1856.34 --> 1861.38]  bit of a reputation for being a bit old and crusty. And you look at the versions of some of these
+[1861.38 --> 1867.46]  packages and they're not that far off what is shipping in Arch, right? I mean, a 5.11 kernel
+[1867.46 --> 1871.48]  is older than what's in Arch, but it's newer than what's in most LTS distros right now.
+[1871.82 --> 1876.58]  And they've rolled out more recent ButterFS support, which I think is kind of a big deal.
+[1876.64 --> 1881.76]  It's nice to see essentially ButterFS and ZFS get near parity support in Proxmox.
+[1881.76 --> 1886.28]  It absolutely is. And I think this, this comes back to a point that, uh, I hear quite frequently
+[1886.28 --> 1892.62]  on Linux Unplugged actually, is that we need to start taking ButterFS seriously and, uh, stop just
+[1892.62 --> 1897.56]  treating it as a bit of a joke because, you know, Facebook and all these other massive companies
+[1897.56 --> 1904.24]  that have things at significant scale are putting a lot of, uh, blood, sweat and tears into the ButterFS
+[1904.24 --> 1910.18]  subsystems. And it does seem to be cropping up in more and more places. And, you know, for me,
+[1910.18 --> 1917.02]  I'm actually starting to use Proxmox as my default distro, you know, for, for server OSs because
+[1917.02 --> 1926.32]  it has ZFS baked in. So I don't need to futz about with DKMS or an AUR package to install a custom
+[1926.32 --> 1931.66]  kernel. I don't have to worry about the licensing. It's just taken care of. I mean, the same is true
+[1931.66 --> 1938.74]  of Ubuntu, but the thing that Proxmox gives me most out of all of this other stuff is a really slick
+[1938.74 --> 1945.40]  web UI to manage virtual machines and LXC containers. Great point. And I think that is
+[1945.40 --> 1951.64]  something that you and I probably underplay. I think for a lot of new users, that's like the
+[1951.64 --> 1957.78]  biggest deal, right? Yeah, absolutely. Yeah. I, I completely agree on your points about ButterFS
+[1957.78 --> 1963.80]  too. I think the thing that you have to remember is what ButterFS offers is a file system that does
+[1963.80 --> 1969.64]  copy on write transparent compression. It can offer encryption. It can offer SSD trim support
+[1969.64 --> 1975.50]  and it's extremely low memory. So it works really good. Say like in a Raspberry Pi situation
+[1975.50 --> 1981.72]  or in a laptop with a single SSD. Those are some use cases where ZFS is, is really not a great choice
+[1981.72 --> 1989.70]  there. And, and I, I really love the combination of the two. I think it makes for a really reliable home
+[1989.70 --> 1996.18]  server. And the way I use it now is ButterFS is on the root file system. So the system can boot
+[1996.18 --> 2002.20]  regardless of what's going on with ZFS. If, if your DKMS module fails to build for some weird reason,
+[2002.20 --> 2008.38]  which has happened to me, your system still boots because the core system, the file system is ButterFS.
+[2008.76 --> 2013.78]  And then your really large datasets with your multiple disks that are in some sort of RAID configuration,
+[2013.78 --> 2019.26]  that's where I go ZFS. And that mounts almost every time the system reboots. But if it doesn't,
+[2019.26 --> 2024.10]  because the root is ButterFS, it's guaranteed I can get in there and get the system repaired
+[2024.10 --> 2028.76]  and we can then get in, you know, then get other things online, like getting ZFS to mount.
+[2029.12 --> 2033.26]  And perhaps the biggest feature that we haven't touched on the single most important improvement
+[2033.26 --> 2038.74]  in Proxmox 7, I can now download ISOs in the web UI. Hooray!
+[2039.42 --> 2043.88]  Oh yeah. Dun, dun, dun, dun. So you give them a URL and it downloads it or does that mean you can
+[2043.88 --> 2044.70]  download it to your machine?
+[2045.12 --> 2049.38]  Both. So what happens is you plug the URL into the, uh, the little form that says,
+[2049.44 --> 2053.46]  I want to download it to this particular area of storage. And then at the bottom,
+[2053.54 --> 2058.92]  this is a really nice feature. It has an optional box at the bottom for you to fill in the MD5
+[2058.92 --> 2065.74]  hash in there. So it will automatically verify the download for you as part of its automated process.
+[2066.12 --> 2071.68]  Now, a lot of people seem to think that Proxmox isn't free as in cost. Uh, it's,
+[2071.68 --> 2078.14]  it's open source. So it's free as in speech and it is also free as in beer. Um, the reason I thought
+[2078.14 --> 2083.20]  it wasn't free is because it has this little nag screen that says you do not have a valid
+[2083.20 --> 2088.56]  subscription for this server. And all that simply means is you have the enterprise repos enabled,
+[2088.56 --> 2094.92]  which are some air quotes, better tested packages. I don't know quite what that testing entails,
+[2094.92 --> 2099.96]  but that's what the Proxmox team say anyway. Um, and so you can support the project and give
+[2099.96 --> 2106.16]  them money and they will enable your server to get rid of that nag message, or you could use
+[2106.16 --> 2110.70]  automation. You could use, I've written an Ansible role, which several of our community
+[2110.70 --> 2115.88]  have now contributed to as well, because open source is just that awesome. And what that does
+[2115.88 --> 2121.10]  is it goes in and removes the repos for you, changes a couple of lines in the, uh, web UI
+[2121.10 --> 2127.66]  files on the Proxmox system and removes the nag for you automatically. Just one more use case for
+[2127.66 --> 2134.24]  automation. And speaking of automation, we want to mention our friends over to Cloud Guru have a
+[2134.24 --> 2138.80]  course that we'll have linked in the show notes just for you. It's the Red Hat certified specialist
+[2138.80 --> 2144.52]  in advanced automation and Ansible best practices. In this course, they're going to cover the topics
+[2144.52 --> 2150.02]  on the EX447 exam as well to make sure you're ready to take that. If you're planning on expanding
+[2150.02 --> 2153.36]  your Ansible knowledge, this is a great course for you. You'll have a better understanding
+[2153.36 --> 2158.96]  of the topics on the exam and around Ansible and Ansible tower and managing and Ansible inventory.
+[2159.02 --> 2163.72]  And of course, templates as well. So you'll have to go over to our show notes to get the link to go
+[2163.72 --> 2169.68]  directly to this course. That of course is over at selfhosted.show slash 49. You'll see the link for
+[2169.68 --> 2174.50]  ACG and that'll take you to the Red Hat certified specialist in advanced automation for Ansible best
+[2174.50 --> 2184.84]  practices. Did you get the update to your shield yet? Alex, I am so, so disappointed in this. I loved
+[2184.84 --> 2190.20]  the Nvidia shield so much. I've bought three of them in total. I've recommended them to the audience.
+[2190.20 --> 2198.04]  And I know that some people out there have also noticed that Nvidia has decided to improve your
+[2198.04 --> 2203.86]  experience by taking the top row, which used to be reserved for your favorite applications,
+[2203.86 --> 2213.68]  and now put full wide advertisements right there at the top, including folks in bondage,
+[2214.12 --> 2219.64]  folks doing all kinds of like crazy things like, you know, guns and violence and smoking. Like I've seen
+[2219.64 --> 2225.46]  the whole range. Thankfully, you know, we're not really that kind of, uh, we, we don't, it doesn't
+[2225.46 --> 2229.12]  really bother me that much. And it's in my bedroom. It's not like it's a, the family uses it all the
+[2229.12 --> 2235.52]  time, but I really do not like the fact that I cannot turn it off. And, um, I think it's on my
+[2235.52 --> 2239.82]  list to replace now, Alex. It's really disappointed. It's such a great device. Yeah. It's, it's been a
+[2239.82 --> 2246.24]  really interesting one to watch the, uh, kind of cancel culture online react to this one. I mean,
+[2246.24 --> 2253.10]  on the one hand, I don't really care that much. Um, they, they've taken an interface that was
+[2253.10 --> 2259.48]  very clean and just got the job done and didn't really have any cruft to it whatsoever.
+[2260.14 --> 2263.12]  And then, as you say, they've polluted it with a bunch of ads. I mean, that,
+[2263.60 --> 2268.78]  that on the one hand sounds pretty terrible, but I mean, on the, on the other hand, I don't,
+[2268.88 --> 2273.54]  I just don't find myself really caring all that much. I, uh, I, I've been browsing the,
+[2273.54 --> 2280.66]  the subreddits, um, the Nvidia shield subreddit for the last few years. And there's lots of people
+[2280.66 --> 2286.20]  now posting custom launches that you can install on the Nvidia shield. I mean, it's just Android
+[2286.20 --> 2291.26]  underneath, right? So you can install a custom launcher if you want to. And I think all this
+[2291.26 --> 2297.68]  is going to serve to do is motivate those who do care about such things to release better quality
+[2297.68 --> 2301.58]  third party launches rather than relying on the, the Google provided one.
+[2301.58 --> 2306.86]  I think I'll probably just switch it to an Apple TV. I have found that the Apple TVs perform even
+[2306.86 --> 2311.52]  better than the Nvidia shield, which I felt like was pretty well performant. This is the exact kind
+[2311.52 --> 2316.22]  of thing that will never happen on the Apple TV platform. And it, you know, it's been, the UI has
+[2316.22 --> 2323.92]  been very consistent now for years. The other thing is it, it wakes and it controls the TV more
+[2323.92 --> 2327.36]  consistently than the Nvidia shield has too. So I think I'm just going to switch it out.
+[2327.36 --> 2333.86]  I wanted to keep it because I liked the idea of having both. And I really love Cody. You know,
+[2333.88 --> 2339.96]  that's a big reason why I keep the shield is I really love Cody, but in fuse on Apple TV,
+[2339.96 --> 2345.64]  it replaces Cody. In fact, I actually have to say, I think maybe in fuse is, is probably better
+[2345.64 --> 2351.98]  because it's just a newer app built with more modern technologies and they've just steadily added
+[2351.98 --> 2357.08]  the features you need. It doesn't quite have the plugin ecosystem that Cody does, but in fuse
+[2357.08 --> 2362.10]  is a really great local file playback, play from your file shares, all that kind of stuff.
+[2362.64 --> 2369.50]  And it syncs via iCloud to your other Apple TVs. So your settings, you set it up once and it's,
+[2369.82 --> 2376.44]  Oh, and also out of the box supports syncing play status with Plex. And I can't remember if it does
+[2376.44 --> 2381.86]  Jellyfin, but it's, it's a really good app. And so it does the job that Cody does. And so I think
+[2381.86 --> 2385.62]  it's just time to, I think I'm done with Android TV. I'm going to keep a couple of Chromecasts around
+[2385.62 --> 2388.44]  and that's going to be it. Well, if there's one thing we've learned from the internet,
+[2388.44 --> 2394.12]  it's the adverts always make everything better. I mean, YouTube's better because of all the ads.
+[2395.12 --> 2401.74]  Radio is better because of adverts, right? I mean, I struggle to think of a single example where
+[2401.74 --> 2406.32]  an advert makes things better. I think I wouldn't have even minded as much if it was only
+[2406.32 --> 2412.34]  showing ads for services that I maybe have active logins for on the device, but right. But it's
+[2412.34 --> 2416.30]  showing me advertisements for services that I don't have and will never subscribe to. So that
+[2416.30 --> 2421.08]  drives me crazy. And then I think the other thing is if it was at the bottom of the UI,
+[2421.48 --> 2426.82]  if they hadn't, if they hadn't taken the row of icons and lowered it. And so now you have to
+[2426.82 --> 2431.78]  navigate down and that would have been better as well. What do you make of the argument that the
+[2431.78 --> 2436.26]  Nvidia shield was a premium device? This, this is quite a pervasive argument on
+[2436.26 --> 2442.14]  Reddit that, you know, it's a $200 device. It's a premium device. I've chosen this over
+[2442.14 --> 2446.64]  something like the Google Chromecast, you know, the new one with the remote that has this same UI,
+[2446.72 --> 2452.04]  by the way. What do you make of that argument? Because to me, I think I kind of agree with it
+[2452.04 --> 2457.24]  in, in the, yeah, one of the reasons I paid for the shield, I pay the extra money for two of them in
+[2457.24 --> 2463.08]  this house was because it was so blazing fast. And because I didn't have this stuff kind of rammed down
+[2463.08 --> 2467.54]  my throat, you know, without, without asking for it. Nvidia have just patched this thing for years
+[2467.54 --> 2473.66]  and years and years. And it's, it's just been very reliable. And unlike you, I'm, I'm left feeling
+[2473.66 --> 2480.36]  rather deflated about it. Yeah. It feels like a play to get affiliate revenue for stream signups.
+[2480.44 --> 2484.52]  And it's like, they have a user base out there. They're not selling them as much anymore because
+[2484.52 --> 2488.06]  they're not as competitive as they used to be. And there's cheaper options out there.
+[2488.06 --> 2492.82]  And I think the Apple TV is starting to eat up some of its market share as well, because I think
+[2492.82 --> 2497.54]  other people have realized it's a better box as well. And so I think Nvidia felt let's monetize
+[2497.54 --> 2501.58]  what we've got here because they get some ongoing affiliate revenue from those subscriptions,
+[2501.58 --> 2505.96]  depending on the deals that work out. That's too tempting, I think for them to say no to.
+[2506.90 --> 2511.78]  And I do agree that it is a premium device. It absolutely is. I think $200 is on the cheap end.
+[2511.86 --> 2515.62]  I think if you buy the, like I, the first one I ever bought was the one with like the big hard drive
+[2515.62 --> 2520.30]  and all of that. And the controller, I want to say that was like $300 or something.
+[2520.88 --> 2528.16]  I bought that box because Roku's and cheaper boxes had that kind of crap. It's one of the
+[2528.16 --> 2533.08]  reasons I didn't get a fire is because the Amazon fire does this as well. It's rows of advertisement.
+[2533.74 --> 2538.56]  And so I didn't buy an Amazon fire. And so I didn't buy a Roku. I bought an Nvidia shield
+[2538.56 --> 2546.80]  specifically because it didn't have this crap on it. Right. And so to have them retroactively add
+[2546.80 --> 2552.50]  that, like that wasn't the deal, bro. When I spent $300 on your kit, that's, this wasn't the deal.
+[2553.92 --> 2559.32]  I just hate it. And I think the custom launcher solution is not a bad one and maybe one I will
+[2559.32 --> 2564.40]  explore, but it's unfortunate. It's sort of like when people tell you to solve the problems with an
+[2564.40 --> 2569.14]  Android phone by flashing a custom ROM on there. It's like, come on, man. Yeah, I know you can do
+[2569.14 --> 2574.16]  that, but most consumers aren't going to do that. They're just not. On that note, Will actually wrote
+[2574.16 --> 2578.86]  in, and that's why we're talking about this, asking if you could put lineage on the shield. And I think
+[2578.86 --> 2583.86]  that's a pretty interesting idea, actually. I don't think it's supported today, but certainly moving
+[2583.86 --> 2589.82]  forward, I could see a much more motivated community emerging around this kind of stuff now.
+[2590.16 --> 2593.14]  I tell you what, if a decent lineage image showed up for that thing, I'd try it.
+[2593.14 --> 2596.64]  Yeah, me too. And I mean, I, even though I just said most people aren't going to,
+[2596.76 --> 2600.54]  the vast majority of consumers who bought this won't, I'd still, I'd use it.
+[2600.66 --> 2606.62]  Now, another option you've got is to replace the tvlauncher.apk via Team Win Recovery Project
+[2606.62 --> 2611.78]  to one of the old versions of the launcher that doesn't have ads on the home screen.
+[2612.14 --> 2616.72]  You'll need to unlock your bootloader to do that, but it doesn't require root or anything like that.
+[2616.94 --> 2621.02]  Well, David from North Carolina wrote in, he said, I'd love to know a little more details
+[2621.02 --> 2625.22]  around the solar panels that Alex recently had installed, especially since they seem
+[2625.22 --> 2628.50]  to integrate with Home Assistant. I've been trying to convince my wife that it would
+[2628.50 --> 2632.62]  be a worthwhile investment, love the show, and keep up the work. Thanks, David. And I
+[2632.62 --> 2635.72]  think he's like extra excited because he's from your home state.
+[2635.98 --> 2637.84]  Yeah, North Carolina. Hey, David, how you doing?
+[2638.16 --> 2640.74]  Is it called a home state now? I mean, your new home state?
+[2641.92 --> 2646.84]  Well, is it? I don't know. I still refer to England as home, and I still watched England
+[2646.84 --> 2651.42]  crash out of the Euros in the final, and I still wept like a small child when that happened,
+[2651.54 --> 2656.38]  but you know. But you also have the first state that you called home in the US.
+[2656.58 --> 2660.46]  It's also the first state where I, it's the first place in the world where I had a child,
+[2660.60 --> 2664.08]  so you know, there is that. So it's your home, I think it's like, as far as states go,
+[2664.16 --> 2666.40]  it's your home state. Yeah, yeah, it probably is.
+[2667.98 --> 2669.70]  So what do you think? You got details for them?
+[2669.92 --> 2673.70]  I've got a few, yeah, not, I don't have, you know, specific model numbers or anything like
+[2673.70 --> 2678.76]  that, but I went to a company called NC Solar Now. I looked at Tesla and a few others, but
+[2678.76 --> 2684.74]  the NC Solar Now folks were the ones that came out with the, you know, the best overall price
+[2684.74 --> 2690.72]  and package and service and financing and all that kind of stuff. And I ended up going for a
+[2690.72 --> 2696.22]  SolarEdge system, and this has a home assistant integration which connects to the, they've got
+[2696.22 --> 2701.98]  this website, and it will connect through the API to the website for up to 15 times an hour,
+[2701.98 --> 2707.56]  I think it can pull the website through the API. And it was just a case of providing an API key.
+[2707.76 --> 2713.28]  It took literally five minutes to set it up. I had to spend an extra few hundred dollars on the
+[2713.28 --> 2721.06]  little Zigbee monitoring device to enable the inverter that's outside to talk to the internet,
+[2721.06 --> 2726.06]  because by default it doesn't come with any Wi-Fi capabilities. But apart from that, you know,
+[2726.32 --> 2731.52]  extra few hundred dollars to get the monitoring capabilities. Yeah, it's been very straightforward
+[2731.52 --> 2737.44]  to set it up. And not only does it talk to home assistant, but the SolarEdge company also provides
+[2737.44 --> 2744.40]  a really nice dashboard and a really pretty slick mobile app as well. So I've got a little widget on
+[2744.40 --> 2749.02]  my Android home screen that tells me exactly what my solar is doing right now, which is pretty cool.
+[2749.02 --> 2757.44]  That's great. Yeah. I love that they're using Zigbee for that. Just the thing, Zigbee's all over the
+[2757.44 --> 2762.32]  place here. Nate wrote into the show asking about security implications for sharing Ansible playbooks
+[2762.32 --> 2766.96]  publicly. You know, he sees them on GitHub, all of that. He got thinking about this after he listened
+[2766.96 --> 2770.52]  to an episode of the Darknet Diaries, and he wondered if you have any thoughts on it.
+[2770.52 --> 2778.10]  Well, all of my stuff's open source on github.com slash ironicbadger slash infra. You know, I have
+[2778.10 --> 2783.72]  open sourced everything for years now. That's kind of my default policy. So I sure hope there isn't a
+[2783.72 --> 2786.44]  privacy implication of doing that. You know?
+[2787.72 --> 2788.66]  Good answer.
+[2788.66 --> 2795.94]  Yeah. I do encrypt everything using Ansible Vault. So all of my secrets and things like that are stuck
+[2795.94 --> 2803.08]  behind AES-256 encryption. So hopefully, unless I commit a secret directly in clear text, I think
+[2803.08 --> 2806.66]  I'm okay. Yeah. I just, you know, when I go through your GitHub, I just look at it. I think, you know,
+[2806.66 --> 2810.40]  everything looks pretty good except for that passwords.txt file where you just put all your
+[2810.40 --> 2816.72]  passwords in there. Well, funny story on that. I actually published my Gmail password one time to
+[2816.72 --> 2824.46]  that repo. And I had a guy, a listener in Australia message me. Like, it must have been first thing in
+[2824.46 --> 2828.62]  the morning for him because it was just before I went to bed saying, hey, by the way, did you know
+[2828.62 --> 2833.92]  that commit you pushed 12 minutes ago has your Gmail password in it? And I'm like, okay, first of all,
+[2834.06 --> 2840.20]  thank you for letting me know. Secondly, it was 12 minutes ago. Like, were you just waiting for me to
+[2840.20 --> 2840.90]  push something?
+[2841.78 --> 2843.92]  Yes. He's got some sort of like alert.
+[2843.92 --> 2851.12]  Uh, so to get around that, uh, Nick Busey from the HomeLab OS project, uh, helped me out with a
+[2851.12 --> 2857.72]  pre-commit, uh, hook that I have in my Git repo that just checks that my secrets file is encrypted
+[2857.72 --> 2863.48]  before I push and do a Git commit and push. That's been very, very useful. It doesn't protect against
+[2863.48 --> 2868.88]  me actually putting API keys and variables and stuff like that directly into other files, which,
+[2868.88 --> 2874.14]  you know, there comes a point where you've got to be like, right, okay, this, you know, my safety net
+[2874.14 --> 2880.72]  is checking that file is encrypted or not. It's not going to go and scan every single file. Um, so
+[2880.72 --> 2885.78]  yeah, I guess it's up to you whether you feel comfortable with that risk or not. And, uh, I,
+[2885.84 --> 2891.04]  I tend to think that even if you're using a private repo on GitHub, you may as well treat that as a public
+[2891.04 --> 2895.04]  repository anyway, because one day it will be whether you like it or not. So.
+[2895.04 --> 2899.00]  And it really just means, can you stick to like a good hygiene with that kind of stuff?
+[2899.26 --> 2903.28]  If you'd like to get your question in or have a comment or something you think we should check out,
+[2903.66 --> 2906.98]  let us know, go over to selfhosted.show slash contact.
+[2907.46 --> 2911.26]  And you can go to selfhosted.show slash SRE to show your support for the show.
+[2911.52 --> 2916.40]  Yeah. Become a member, get access to the post show. And of course, uh, help us keep the show
+[2916.40 --> 2917.68]  on the tracks.
+[2918.04 --> 2921.52]  I think this episode, we're going to talk about the future of the gasoline engine
+[2921.52 --> 2923.16]  and the internal combustion engine.
+[2923.16 --> 2925.26]  Oh, I have thoughts on that. Interesting.
+[2925.60 --> 2931.08]  Yeah, me too. Now I was browsing some, I always seem to come up with YouTube on these things,
+[2931.16 --> 2936.48]  don't I? But anyway, uh, about steam trains the other week. And, uh, I found this union Pacific
+[2936.48 --> 2942.40]  steam loco called the big boy. And this thing is freaking enormous. And it was designed, uh,
+[2942.40 --> 2948.42]  in the early, uh, part of last century to get over some of the Rocky mountain passes because
+[2948.42 --> 2954.82]  they're just so vast here and the trains are so heavy. And so Union Pacific have actually restored
+[2954.82 --> 2960.36]  one of these big boy steam locos, which is essentially two massive steam locos glued together.
+[2960.58 --> 2967.40]  This thing has basically two sets of drive wheels and two, two full sets of pistons. And it's just
+[2967.40 --> 2973.90]  awesome. Just go look it up. Big boy Union Pacific steam loco. And it's going on tour in August around
+[2973.90 --> 2980.66]  the US. So it's, it's leaving Cheyenne, Wyoming and going all the way down to Houston past, uh,
+[2981.08 --> 2984.10]  our beloved cheese bacon's hometown of Beaumont.
+[2984.50 --> 2986.12]  I know he lives in Denver now, doesn't he?
+[2986.40 --> 2988.28]  Okay. Well, so much for that.
+[2988.28 --> 2990.26]  You could say it's his original hometown though.
+[2990.62 --> 2997.28]  So much for that plug. Um, so yeah, it's going up to, I think, uh, through Dallas at some point
+[2997.28 --> 3002.02]  and then up through Kansas city and St. Louis. So if you're in the center of the country,
+[3002.02 --> 3006.98]  by all means go take some pictures for me, cause I'm not going to be able to make that one. But,
+[3007.02 --> 3009.02]  uh, throughout August, it's traversing the country.
+[3009.48 --> 3013.04]  That does look like an incredible route. Actually. We'll have a link in the show notes.
+[3013.10 --> 3016.12]  And when you go there, they have a map that shows you the route that they're going to be on.
+[3016.46 --> 3020.68]  Well, you know, it's either side of our Denver meetup, don't you? So I reckon if you were creative
+[3020.68 --> 3023.16]  with your schedule, Chris, you could probably find it for a day.
+[3023.20 --> 3029.04]  Our route for the Denver meetup in total is a good, it's going to be just over 5,000 miles.
+[3029.04 --> 3036.40]  That's a long way. I drove that myself in 2018. We flew into Orlando, drove up to DC,
+[3036.62 --> 3042.06]  drove down to Austin to meet you for the first time and then, uh, up to Denver. And that was
+[3042.06 --> 3047.66]  about 5,000 miles. And we did that in three weeks in a car. I mean, it wasn't, it wasn't our house.
+[3048.14 --> 3051.84]  Now I'm going to be in a land yacht. Yeah, that's for sure. But if you're going to be in the area,
+[3051.84 --> 3054.82]  don't forget that we have those meetups coming up and you can get details
+[3054.82 --> 3059.82]  at meetup.com slash Jupyter Broadcasting. Make sure you don't miss the next episode,
+[3059.92 --> 3065.82]  episode 50. We've got some cool stuff lined up for you and rumor has it there might be some swag.
+[3067.12 --> 3072.12]  Hmm. In the meantime, you can find Alex on Twitter. He is at Ironic Badger. I'm at Chris
+[3072.12 --> 3075.48]  LES and the show is at self-hosted show. And thanks for listening, everybody.
+[3075.48 --> 3078.30]  That was self-hosted.show slash 49.

49： Update Roulette _transcript_corrected.txt

@@ -0,0 +1,588 @@
+[0.00 → 3.68] Well, I'm pleased to welcome back to the show, Mr. Chris Fisher. Welcome back, Chris.
+[3.92 → 7.34] Thank you, Alex. I just got done drying everything off only a few moments ago.
+[7.64 → 12.78] We missed you, man. So it's story time. I need to stay a while and listen.
+[13.24 → 19.18] Yes. And first, thank you to Morgan for filling in. I, at the last minute, had to jump
+[19.18 → 26.16] out when I realized that my laptop had got soaked, and I didn't want to turn it on. And so I told
+[26.16 → 31.14] Alex, you got to find somebody to fill in for me. All right. So I was setting up to go camp out in
+[31.14 → 35.66] the woods, brief story. And I wanted to get out to the woods and get set up in time for the show.
+[35.86 → 41.12] And so I was in a bit of a rush and I thought, because I'm an idiot. I thought, Hey, you know,
+[41.12 → 46.44] it'd be a great idea is I'll do some updates on this laptop. And I've got this ancient 2013
+[46.44 → 52.20] MacBook that runs Arch Linux, by the way. And so it's, for me, it's like this thrill to boot it up
+[52.20 → 57.16] about once every six months and see if when I do an update, if the installation explodes or not.
+[57.16 → 61.36] Right. So I thought, well, I'm running around packing up the RV. I'll set this thing to do
+[61.36 → 65.86] some updates just so I can, you know, have like a little thing to do for my ADD brain
+[65.86 → 71.08] and check in on it. And so I'm packing up, and I go around, and I collect all of my electronics
+[71.08 → 75.58] because I, my kids and I had been going through some stuff. And so we had, the fire tablets were
+[75.58 → 80.38] down off the wall that we use to control home assistant, our front end and some game controllers
+[80.38 → 84.02] were out, and we're going down the road, and we want to get there quick. So I just took this basket
+[84.02 → 88.76] and like a good little boy, I picked up everything and put it in my basket. Now, of course, I don't
+[88.76 → 94.70] want that basket to spill. So I, I set it in the back in the bathroom and finished up my laptop and
+[94.70 → 100.62] closed the lid and went about packing up the rest of the RV. I'm driving down the road for probably
+[100.62 → 106.74] 20, 25 minutes. And I realized I should probably get gas because I'm going to be off grid for a while.
+[106.74 → 110.02] And if for some reason we don't get good solar, I'm going to need to be able to run my
+[110.02 → 115.62] generator. So I, I, I pull up to a gas station and I start to pull in, which is a downhill kind
+[115.62 → 120.44] of turn in. And as I pull into the gas station and begin to decline down into the parking lot,
+[120.56 → 126.48] I hear like, like a wave sound behind me. Like, I'm like, is there a noisemaker on? And I,
+[126.56 → 131.76] I turn around and look over my shoulder, Alex, and I see this wave of water coming down the middle
+[131.76 → 137.88] of the hallway of my RV. It sloshes down into the, into the, into the step. Well, it's all over the
+[137.88 → 141.22] place. It's coming down into my feet while I'm driving. It was everywhere.
+[141.68 → 147.94] How tight did your asshole pucker when you saw that Alex in like one motion, I like grabbed the
+[147.94 → 152.62] radio and I radio to my wife. Because she's chasing me in the car behind there. You got to get in here
+[152.62 → 159.96] quick. We got an emergency. I throw the radio down. I parked the RV stand up, and I began just walking
+[159.96 → 166.22] straight to the back. And as I approach the back of the RV, I hear a sound. I immediately recognize
+[166.22 → 175.78] it's my water pump, and it's pumping, and it's pumping, and it's pumping. It shouldn't be on,
+[175.84 → 182.52] but in our rush to leave, I had left it on and didn't notice. And so I flip it off as I opened
+[182.52 → 188.06] the door and I look right at the sink or where I just instinctively knew the problem was going to be
+[188.06 → 193.84] somehow I knew. And I could immediately see the entire chain of events. I had left that big old
+[193.84 → 200.58] heavy MacBook on the counter. And when I went down the road, it slid down the counter, slid just right
+[200.58 → 208.86] and fell into the sink. And as it fell, it turned the faucet on, which is where my basket full of
+[208.86 → 215.30] electronics was sitting. Oh, no. That be turned that, that Alex, it turned into a bathtub. Alex, it was,
+[215.40 → 220.62] it was so bad, Alex. It soaked everything. And then proceeded to spill out from there into the rest
+[220.62 → 227.48] of the RV at about, about, about 17, 17, 15, 20 gallons is. It's hard to say. Yeah. Got the
+[227.48 → 233.24] laptop, got all the fire tablets, got the game controllers, got all the charging bricks, everything,
+[233.36 → 241.16] not to mention flooded the RV. I, I, I had to act quick. And so thankfully I was able to position the
+[241.16 → 245.56] RV in such a way that it kind of tilted it. So I could just get all the water to pour out into one
+[245.56 → 251.44] direction. And then I just spent like two hours drying it up. And then we moved out to our spot
+[251.44 → 256.54] in the woods and then spent another couple of hours trying to dry it all out. I lost a lot of devices.
+[256.86 → 264.96] A lot of good devices died that day, Alex, but not that stupid old MacBook. It's still kicking,
+[265.10 → 268.40] even though it got water in the event in the vents and all of that, it's still kicking.
+[268.40 → 274.10] So the device that caused the problem just ran away going, tee, not today.
+[274.28 → 278.44] It's doing great. Yep. Although its power adapter bit the dust. So I don't know exactly
+[278.44 → 279.80] what its long-term plan was.
+[279.90 → 282.00] That's like cutting your nose off to spite your face, isn't it?
+[282.16 → 286.50] That's why you should plan and plan to learn. Visit our sponsor, Cloud Guru,
+[286.64 → 289.18] the leader of learning for the cloud, Linux, and other modern tech skills,
+[289.52 → 293.74] hundreds of courses, and thousands of hands-on labs. Get certified, get hired,
+[293.82 → 295.78] get learning at a cloudguru.com.
+[295.78 → 301.82] That story just hurts me so deeply because water and electronics, you just have this
+[301.82 → 308.52] pathological thing that they don't go, they just don't mix. I've probably missed out on
+[308.52 → 312.30] several experiences in my life because I had a phone in my pocket. I'm like, well,
+[312.48 → 317.14] I'm not going to go and run in the ocean or whatever it is because I've got a phone in my pocket.
+[317.54 → 323.36] And so many devices, obvious statement time, but I really was feeling this. So many devices
+[323.36 → 326.78] have the battery built in. And so there's just nothing I can do.
+[326.98 → 329.40] Yeah. Damn, man. I feel your pain.
+[329.62 → 330.24] I really do.
+[331.50 → 335.44] It was rough. It was rough. And so now I have to selectively choose what I'm going to replace
+[335.44 → 337.24] and what I'm just going to try to live without.
+[337.62 → 339.04] Oh yeah. And you just missed Prime Day.
+[339.94 → 344.12] I know. I crossed my mind because I had a couple of fire tablets in the mix.
+[344.62 → 344.90] Gone.
+[345.54 → 346.36] Womp.
+[346.36 → 349.74] All right. So you got something to cheer me up.
+[350.12 → 354.46] Well, I was watching YouTube the other day, as is often the case in my household. And I was
+[354.46 → 360.60] watching a video by Techno Tim, and he did an Thalia introduction. It is a single sign on
+[360.60 → 368.64] service that basically allows you to have one login cookie get set, which then allows you to log into
+[368.64 → 374.62] all the services that you select through a set of rules that you configure to say, right, if I want
+[374.62 → 381.82] to access Nextcloud, as long as I've got this token set, then I'm all good. And then you could do it for
+[381.82 → 388.10] a wiki or any of the services that are running on your system. And the really nice thing is it's
+[388.10 → 394.14] configured with a single line of Docker Compose configuration. So you just add a single line to
+[394.14 → 398.34] declare that you want to use Thalia as what's called a piece of middleware in the traffic
+[398.34 → 402.26] configuration. And you're good to go. And that's it.
+[402.88 → 408.54] I see. So it is, first, we should mention its open source. And it essentially takes
+[408.54 → 414.14] authentication requests using Nginx and provides the authorization for those authentication requests.
+[414.84 → 419.92] Yeah, not just Nginx, it supports traffic as well as a bunch of others. And it actually,
+[420.20 → 425.30] more recently, supports Kubernetes ingress controllers, which is nice as well.
+[425.62 → 427.88] All right, I'm checking it out right now. And it actually looks like it has a pretty
+[427.88 → 435.42] good interface too. So this will have linked in the show notes, or you can go to A-U-T-H-E-L-I-A.com.
+[435.58 → 439.78] Yeah, you don't really need a whole bunch of interfaces for a login client. Essentially,
+[439.86 → 444.00] what happens when you have a service that's backed by this, let's say I go to wiki,
+[444.40 → 449.30] my personal wiki, my tiddly wiki, traffic will detect that I've set that piece of middleware as
+[449.30 → 454.56] part of the chain of traffic that it wants to go through. And so Thalia will then pop up a
+[454.56 → 459.26] standard web form. I'll type in my username and password. It does support two-factor authentication.
+[459.72 → 465.94] So even for services that don't have 2FA natively, I can use Thalia to add
+[465.94 → 472.74] 2FA to those services as well. And then just transparently, that token lasts for the length
+[472.74 → 477.08] and duration of your session. You can figure how long it is. I think it's five minutes by default.
+[477.62 → 482.94] Any other service that has the same rule on your system, it will reuse that authentication token.
+[482.94 → 486.14] So if you're switching between a bunch of different services on your system,
+[486.92 → 490.50] log in once, and you're logged into all of them all at once automatically.
+[491.10 → 494.10] Boy, that does seem nice. It has a lot of great features in here.
+[494.72 → 499.20] All right. Well, it sounds like something to check out. We talk about this kind of stuff. Also,
+[499.40 → 504.00] when we talk about things like hosting your own password manager or hosting your own email,
+[504.26 → 507.72] I wonder if there's an audience and I wonder if you out there too, I wonder if there's a portion of
+[507.72 → 514.74] the audience that thinks, I'd never want to host this. This crosses a line. These breaks and things
+[514.74 → 520.52] get hosed. And so I wonder if there isn't just a discussion to be had there, Alex, about where
+[520.52 → 524.28] that line is for us. And if we ever consider dropping something and saying, you know what,
+[524.40 → 526.20] I'll just go with a commercial service for this.
+[526.20 → 533.16] Is this grumpy old man, Alex, coming out here? But my tolerance for stuff breaking,
+[533.94 → 541.26] be it an update, be it a dodgy power cable, whatever the reason, my tolerance is so low these days.
+[541.62 → 546.48] And a couple of episodes ago, I mentioned I had my server on the desk next to me because I was
+[546.48 → 551.60] troubleshooting some issues with hard drives failing. Turns out it wasn't the hard drives failing.
+[551.60 → 557.76] And I wasted maybe three weeks on trying all sorts of different drives and cables and disc controllers.
+[558.22 → 563.90] No, it was the power cable from the power supply to the drives. No kidding. I wasted three weeks on
+[563.90 → 569.38] that damn thing. And that just left me with a huge bitter taste in my mouth. And, you know,
+[569.40 → 575.76] I'm not going to stop self-hosting. Don't, don't worry, audience. We're okay. But there were just
+[575.76 → 581.16] moments in that three-week period. I was like, screw this. I just want to throw the towel in and just be
+[581.16 → 586.24] done and just pay Netflix or whoever it is. Wow. You know, in that same period of time,
+[586.28 → 590.18] I think you also had a certain Home Assistant update not go so well, too. So you were really
+[590.18 → 594.76] getting it from both ends. Yeah, that's the thing. And, you know, this week, another example is
+[594.76 → 601.08] Nextcloud just stopped working for some reason. I have no idea why. I've been sat on Nextcloud 19
+[601.08 → 607.98] for the last year plus. I haven't touched it. Furthermore, I pull in the regular updates that they provide
+[607.98 → 616.08] to the 19 branch through Docker Hub tagging. But I don't update major versions on Nextcloud unless I
+[616.08 → 621.38] have a good reason to because I don't want all the new stuff. I just use it for documents. That's
+[621.38 → 625.48] pretty much it. Right. I actually figured this out because I got a notification on my phone
+[625.48 → 630.26] because photo upload stopped working. It said this server is in maintenance mode. And I'm like,
+[630.64 → 637.34] OK, yeah, I remember. I've had this before. So you Google it. First result says go into the config file
+[637.34 → 644.26] and edit a single line that says change maintenance mode from true to false in the config.php file.
+[645.42 → 651.62] So I did that. It was already set to maintenance mode false. So I'm like, OK, well,
+[651.62 → 656.64] clearly something's going on here. So I then start looking into the Nextcloud container logs.
+[657.40 → 666.12] And then it said something about character encoding, UTF-8 char sets. And I just at that point,
+[666.16 → 671.30] I was like, oh, no, here we go. This is going to be a long evening. Long story short, I ended up
+[671.30 → 679.40] having to go into the MySQL container itself with a Docker exec command, get into the MySQL nitty-gritty
+[679.40 → 687.52] details, delete and change a couple of data types from Var char to text fields and all this, you know,
+[688.12 → 694.18] stuff that's way over the head of most people doing self-hosting unless this is your day job.
+[695.04 → 700.44] And I just thought to myself, who is this stuff targeted at? If I was paying for Nextcloud as a
+[700.44 → 707.72] hosted service, I mean, these things exist. Like Google Drive is similar. OneDrive, you know,
+[707.72 → 713.24] all these different cloud file repositories. If these things broke, and I had to jump through all
+[713.24 → 718.94] these different hoops to fix them, I would just migrate to a different service. And yet, because
+[718.94 → 726.54] I feel a certain sense of obligation, partly because of this show, but also partly because of my beliefs
+[726.54 → 733.94] towards self-hosting in general, I power through it. But sometimes I just want to throw the towel in,
+[733.94 → 738.24] you know. Did you ever get to the root of why that Nextcloud issue just cropped up?
+[738.90 → 743.26] I think it was because of the character encoding. So what I ended up doing as part of the
+[743.26 → 746.64] troubleshooting process was like, right, okay, well, I'm in the weeds here. I may as well go to
+[746.64 → 748.22] Nextcloud 22 whilst I'm here.
+[748.66 → 750.48] Yeah, that would be my line of thinking too.
+[751.38 → 756.82] Yeah. And then I thought it didn't start because I thought, oh, some database schema changes have
+[756.82 → 763.30] probably happened, and it's just not tested properly on 19. Okay, fine. I'll go to the next major release.
+[763.30 → 769.66] That's stable. Yeah. And so like I said to you, I had to drop to the MySQL command line,
+[769.96 → 776.14] delete a couple of tables that were failing the repair because there's an OCC command. So you can
+[776.14 → 783.94] log into the Nextcloud container and run, there's like a shell, like a CLI tool built into it called
+[783.94 → 790.42] OCC. OwnCloud Client, I would imagine is what it stands for. Don't quote me on that. And you can do a
+[790.42 → 793.66] bunch of maintenance stuff, like you can turn maintenance mode on and off, you can repair
+[793.66 → 797.96] things, et cetera, et cetera. And it kept failing on this line item to do with news articles,
+[797.96 → 802.42] which is a plugin I don't even use anymore. I think I enabled it for testing and then forgot
+[802.42 → 808.74] about it. And much like my Home Assistant update, I probably missed it in the logs because I don't
+[808.74 → 815.18] necessarily look at the logs every day because I've got other stuff to do. And yeah, once I deleted the
+[815.18 → 820.44] news, once I'd gone into the correct database table and then deleted the three or four lines
+[820.44 → 825.92] that were causing the schema migrations to fail, then the upgrade proceeded and it was all fine.
+[826.04 → 827.54] But it took me a couple of hours.
+[828.00 → 833.46] I've had those moments where I thought maybe like a server was dead and gone. And I thought,
+[833.56 → 838.96] I don't, I don't know if I, I don't know if I ever want to rebuild this. And then thankfully
+[838.96 → 841.78] they came back, and then I thought, okay, I better get my backup game.
+[841.78 → 846.86] I better get my backup figured out. Yeah. Because I mean, you really got it. I mean,
+[846.88 → 850.74] you got a hardware failure in your server. You got a software failure in Nextcloud,
+[851.14 → 856.38] a Home Assistant, a pretty dramatic Home Assistant failure based on some deprecation and changes.
+[856.80 → 863.38] I mean, you got it one after another. I recently also had a Home Assistant update go south when the
+[863.38 → 868.82] OS update didn't complete correctly. The system locked up and then rebooted. And then it couldn't
+[868.82 → 874.08] get an IP until I had fiddled with it for quite a while. And for a brief moment, I thought to myself,
+[874.08 → 879.52] should I just bail on this and maybe just go back to a traditional server and Home Assistant core
+[879.52 → 884.34] container and just keep it simple. And then it gets working again. And then I think, okay, no,
+[884.40 → 889.42] this is better. And I like this. And I think to myself in the grand scheme of things, this is the
+[889.42 → 895.92] cost of having full control over these services. And, and it does give me a better appreciation of the
+[895.92 → 902.64] value that the cloud providers are offering. And it makes me also understand how valuable my data
+[902.64 → 908.10] must be if they can pay for these services based on mining my information. Like, wow, there must be
+[908.10 → 913.76] some real value there because it's not cheap. And to keep something reliable like file services for,
+[914.18 → 918.04] you know, a 10-year streak actually takes an incredible amount of effort.
+[918.38 → 922.40] Yeah, you're not wrong. I mean, these, these guys, they're our entire jobs, you know,
+[922.40 → 928.18] site reliability engineers. That's the name of our, you know, supporters club that we have. And
+[928.18 → 935.26] there's an entire job dedicated to keeping things up and stable and reliable. And these guys,
+[935.36 → 940.30] they write software, they write scripts, they do all sorts of ninja magic to keep these services online.
+[940.88 → 945.50] I think part of it, Alex, is giving yourself, and you've done this, you know, the ability to rebuild
+[945.50 → 950.66] fairly quickly. Like you do that. You make, you make, if you adopt something, you make sure that
+[950.66 → 957.84] you can redeploy it as necessary. And those kinds of things, I think they help a lot. But I think
+[957.84 → 962.70] this show should ask more often, is there a cloud service that could do this?
+[963.16 → 968.00] And if there is, why are we not choosing to use it? Because it is a big trade-off every time.
+[968.34 → 972.66] And the more critical the service is to you, I think the more serious you have to consider that.
+[972.98 → 975.72] I'm trying to think of a good example. I suppose wiki would be a decent one.
+[975.72 → 981.44] Because you can probably throw some stuff up on GitHub in a random repository,
+[981.76 → 990.98] a bunch of text files, and call that a wiki if you want to. You could also go to some random website
+[990.98 → 996.96] and buy probably wiki capabilities. But there's nothing quite like hosting your own and keeping
+[996.96 → 1005.12] that kind of information in-house. Because the role a wiki in particular fulfills often is to store
+[1005.12 → 1011.52] proprietary, you know, custom information, you know, maybe Wi-Fi passwords for your house or
+[1011.52 → 1016.42] something, or the code to the safe so that your wife can open it when you're out or something. I don't
+[1016.42 → 1023.66] know what people store in their, you know, wikis. But there could be some sensitive information in there.
+[1023.66 → 1028.48] Sounds like you have a code for a safe that if I was ever on your LAN, I should try to get that code.
+[1028.82 → 1030.26] I've got to buy the safe first.
+[1031.26 → 1035.42] I was like, he has a safe? Oh, okay. But it's a good example. You're right. I have been thinking,
+[1035.60 → 1042.02] like, how could I leave my wife notes in a way that is fully secure? And there is this feeling
+[1042.02 → 1047.98] that I think is actually pretty special. And it's this total feel of control. And I feel this when I
+[1047.98 → 1054.36] am off-grid, and I'm generating my own power, and I've brought my own food, and I don't need anyone
+[1054.36 → 1061.90] to do anything. For a brief moment, I feel like I'm truly in control. And I have that same sense when
+[1061.90 → 1069.04] it comes to everything being offline in my RV, and being self-contained to the RV, and having
+[1069.04 → 1074.30] gone through this project off-grid where I offloaded a bunch of services and got everything running
+[1074.30 → 1082.44] locally. When I get access to that stuff, it's like this feeling of confidence that we get so
+[1082.44 → 1086.88] sparingly now. With so many cloud services that are integrated with our mobile devices,
+[1087.06 → 1093.42] or integrated with commercial desktops, less and fewer consumers and technology users have control.
+[1093.60 → 1098.32] Less and less. They have less control than ever of modifying their devices, of controlling their
+[1098.32 → 1103.74] devices, or even determining who has access to their data, or if it can be scanned, or any of that.
+[1103.74 → 1109.46] And so when we have these areas, we can actually exercise that control. We have to keep doing it,
+[1109.56 → 1115.66] or else it will go away. If there are no users of these self-hosted services, and if there's no
+[1115.66 → 1124.00] market demand for this control, eventually the developers and the companies that serve that niche
+[1124.00 → 1129.42] will dry up. And so it's like you have to always be looking like, where can I exercise that control?
+[1129.50 → 1132.94] Where does it matter the most? And that's kind of where I've come down on it. It's like, okay,
+[1132.94 → 1137.70] this information, like secret stuff I want to give my wife, that is always going to be
+[1137.70 → 1143.06] on my land. Like, I'm just never going to put it anywhere else. And thankfully, you know,
+[1143.08 → 1146.24] I've come up with a little system where it's just some markdown files. It's really simple. It's not,
+[1146.28 → 1148.66] it's not, it's not a big effort to actually do it.
+[1149.18 → 1155.66] You are right. There are an increasing number of companies doing stuff for this marketplace. You know,
+[1155.66 → 1161.12] Tuna, we talked about it last episode with Morgan, have announced a native home assistant
+[1161.12 → 1166.12] integration as part of their product line. You know, so these things are happening, and you see,
+[1166.22 → 1171.66] what's his name? Linus Sebastian has just bought a new house, and he was talking about how he's going to
+[1172.30 → 1177.62] implement smart dampers in every room. So he's not air conditioning every room and how there is lots of
+[1177.62 → 1181.86] proprietary services that could do this stuff and how it's just all so overwhelming. And
+[1181.86 → 1186.38] I think that's largely what I'm feeling too. It's just a bit overwhelmed by the amount of stuff I
+[1186.38 → 1192.64] could do. You know, it's not even necessarily just when stuff breaks. It's, it's that feeling of once
+[1192.64 → 1196.80] I put my daughter to bed or something in the evening of, okay, I've got a couple of hours before I go to
+[1196.80 → 1202.90] sleep now. I don't want to just sit and veg and watch cartoons necessarily. I'll do that whilst I'm
+[1202.90 → 1207.96] doing something else. But what out of my huge long list of ideas that I've got, should I pick and
+[1207.96 → 1213.60] oh, I can't be bothered. I'll just watch cartoons. You know, what I've been doing is like the really
+[1213.60 → 1221.84] simple stuff. Uh, I went through my, uh, home assistant dashboard and I made individual, I chose
+[1221.84 → 1227.28] like individual icons for each entity. So each light bulb has like a unique light bulb icon, really just
+[1227.28 → 1234.52] slow kind of paced work while I was watching Rick and Morty, you know, and so it's like not very high
+[1234.52 → 1239.44] cognitive load, but I can sit there and fiddle with something. Um, and then the other thing that
+[1239.44 → 1243.32] I did recently, it was, it was one of those moments where I was like, I don't need to build something
+[1243.32 → 1249.12] complicated here. I could just get a couple of window fans off of Amazon that have manual controls,
+[1249.76 → 1254.56] plug them into some smart plugs, and I could have some set to input and I could have some set to output.
+[1255.56 → 1260.08] And then I could just set up automations to turn the smart plugs on and off. And it was one of those
+[1260.08 → 1265.30] moments where I was like, I could just do something very simple for cooling, and it would probably take
+[1265.30 → 1271.14] me 35 minutes to set it all up. And I was so down in the weeds with all of these things. Like I could
+[1271.14 → 1276.36] build a new virtualization backend, and then I could set up individual host OSes and then put containers
+[1276.36 → 1280.04] in there. Like I was going through this entire thing about how I wanted to rebuild all the
+[1280.04 → 1283.74] infrastructure. And then I thought, you know what else I could do is I could just spend 30 minutes
+[1283.74 → 1288.26] doing this tonight, and I'll spend 30 minutes doing that tomorrow. And over a couple of nights,
+[1288.26 → 1290.76] I got it all done. If it works, it ain't stupid.
+[1292.38 → 1299.26] Linode.com slash SSH. Go there to support the show and get $100 in credit on a new account.
+[1299.82 → 1303.18] Linde is our cloud hosting provider. When we're building something that we want to experiment
+[1303.18 → 1307.54] with, we do it on Linde. There are a lot of quick ways to deploy. They have 11 data centres to choose
+[1307.54 → 1312.30] from. They have crazy fast network connections and a whole range of types of servers. So if we want
+[1312.30 → 1318.12] something simple, we'll get like a $5 a month system. But sometimes we want some dedicated CPUs or GPUs.
+[1318.26 → 1323.54] They have a lot of choices. Roger wrote into the show to say that he used Linde to replace
+[1323.54 → 1328.88] Zoom with something he can host himself. He says, along with just about everybody else,
+[1328.96 → 1334.74] the Milwaukee Linux users group had to go to virtual due to COVID-19. And as you might expect
+[1334.74 → 1339.82] from a group of Linux users, they weren't a big fan of using Zoom. They wanted to use Jitsi.
+[1340.04 → 1345.90] So they looked around at different providers, and they chose Linde. They picked the $5 a month
+[1345.90 → 1350.86] machine, and they also chose to do the automatic backup service. So that way there's just backups
+[1350.86 → 1356.74] that are just taken care of. They installed Jitsi Meet on that system, and they're now using it with
+[1356.74 → 1362.92] Nextcloud Talk to do the video calls for their lug, all running on Linde. You know, what's really nice
+[1362.92 → 1369.92] about this too is, is Roger was able to prototype Jitsi and Nextcloud and try them all out really quickly
+[1369.92 → 1374.80] in environments that are production style environments. So you could really get a sense
+[1374.80 → 1380.14] for how it's going to perform. And it's pretty great because at one point they made a change to
+[1380.14 → 1387.64] Nextcloud just before the lug meeting and it broke. So Roger says they were able to use the snapshots
+[1387.64 → 1393.12] that they got with the automatic backups and just roll it back. So it was basically a non-issue.
+[1393.12 → 1397.86] And then after the lug was over, they were able to continue on with the Nextcloud update.
+[1398.38 → 1402.52] And that's just an example of how you can use Linde, you know, to run your own Zoom instance.
+[1402.70 → 1407.88] Or they also have a one-click deployment for Downcast, which is essentially a Twitch in a box.
+[1408.56 → 1413.18] You can use it for that as well. There are so many different choices from hosting your website to
+[1413.18 → 1418.56] their object storage. Like I use it for like a sync thing instance. Just go try it out,
+[1418.56 → 1424.76] learn something, and experiment with that $100 and support the show at linode.com slash SSH.
+[1426.82 → 1432.42] Now, in case you haven't heard, we're getting together in Denver. I'm looking forward to this.
+[1432.96 → 1437.58] And not only is Alex going to be there, but he's going to be our trivia master at the meetup.
+[1437.98 → 1439.90] So you got to come just to say hi to Alex.
+[1440.24 → 1443.80] Looking forward to that. I've been working hard on the trivia questions. I promise you.
+[1444.22 → 1448.02] There'll be a bunch of Linux questions. There'll be some, you know, general knowledge stuff,
+[1448.02 → 1453.20] but there's also going to be some like older, more esoteric hardware questions as well. I've been
+[1453.20 → 1459.06] having a real fun digging out some of these questions. I'm looking forward to that. So we'll
+[1459.06 → 1463.34] have the meetup details. We have two meetups actually planned. Alex is going to be the Denver
+[1463.34 → 1468.28] meetup, but there's also a Salt Lake City meetup on the books. Details are over at meetup.com
+[1468.28 → 1474.86] slash Jupiter Broadcasting. And then additionally, in Lady Coupes, my RV, I will have a live tracker.
+[1474.86 → 1479.46] And if there, and there will be more details. And if it works out, we'll do a little micro meetup.
+[1479.62 → 1484.66] Could just be, you know, just come by and say hi. And we'll have this embedded webpage that you'll
+[1484.66 → 1490.02] be able to view over at colony tracker dot live. That'll show you right where we are at. It's all
+[1490.02 → 1496.04] in the works right now. Just in this last week, we got the backend set up for own tracks to record
+[1496.04 → 1498.98] where I'm actually going to be at. And that's a pretty neat deal, Alex.
+[1499.22 → 1500.98] How are you doing that? Is that on Linde or something?
+[1500.98 → 1504.22] Oh yeah, of course. Naturally.
+[1504.74 → 1512.20] Yeah, of course. Yeah. Yeah. In fact, we just decided to do a dedicated lower end Linde because
+[1512.20 → 1515.68] what we want to do is put a little website on there that has the details and stuff. And then
+[1515.68 → 1520.36] own tracks itself is kind of like in multiple components. And so the recorder is a Docker
+[1520.36 → 1525.32] image that you can deploy. And that's like a lightweight backend that stores the location
+[1525.32 → 1530.96] data. And you can publish your location information to it in two different ways, either over
+[1530.98 → 1537.34] HTTP or over MQTT. And then the recorder, as the name implies, records the information
+[1537.34 → 1543.12] and then makes your location data available, which is all completely under your control
+[1543.12 → 1549.28] via a various set of APIs, some of which can integrate directly into home assistant. So
+[1549.28 → 1554.06] you can actually use own tracks to provide home assistant with your real time location, which
+[1554.06 → 1559.20] is a fantastic way to control automations. And one way that we use this, not with own tracks
+[1559.20 → 1565.18] today, but soon is when no one is at home. If some of the lights, which always happens,
+[1565.30 → 1571.46] get left on, which never fails to get left on, then if no one's home, and it's, and a certain
+[1571.46 → 1576.10] amount of time has passed, the lights just automatically turn off. And that's just a simple way to use
+[1576.10 → 1582.28] the automations. Or in the winter, if we're approaching, and it's cold, the heating turns on.
+[1582.52 → 1585.34] Really simple stuff, that stuff that we just don't want to even have to think about.
+[1585.34 → 1591.76] And, but the key is getting your location into home assistant and own tracks can essentially
+[1591.76 → 1598.24] be that source of information. I'm using it for a live embedded map on a webpage. So that way you
+[1598.24 → 1602.84] guys can find me, and we can meet up, and I'll be running the own tracks' client, which publishes
+[1602.84 → 1605.40] that information to the recorder on my pixel.
+[1605.86 → 1608.20] That's so cool. And it uses MQTT to do that.
+[1608.44 → 1612.80] Yeah, isn't it? It's clever. It seems like it actually a great use of it because you could see
+[1612.80 → 1617.40] how, when you have maybe a loss of connectivity, it could queue up. And then when you connect,
+[1617.44 → 1622.28] it can just transmit the bits that were queued while you had no signal. It's, it's really smart.
+[1622.66 → 1628.18] Perfect. It's exactly what it was designed for. Now my favourite robot vacuum firmware,
+[1628.32 → 1632.98] Altitude, had a big release last month and I finally got around to updating it and installing
+[1632.98 → 1637.76] it this week. I'm a glutton for punishment, aren't I? There's lots of stuff breaking and I still
+[1637.76 → 1641.12] go ahead and install these updates. And guess what?
+[1641.36 → 1641.52] What?
+[1642.72 → 1643.72] Did it break?
+[1644.28 → 1649.78] Well, I mean, no, the updates went fine, but there'd been some changes to how the
+[1649.78 → 1656.38] the vacuums get communicated with from Home Assistant. They've deprecated the vacuum. Send
+[1656.38 → 1661.76] command, which was what I used to say, hey robot, go, you know, hoover the bedroom or something.
+[1661.76 → 1670.68] Um, and they've deprecated it for an MQTT publish command. So we're both using MQTT here in wildly
+[1670.68 → 1674.44] different use cases, but I just think that's so cool how it's the same technology.
+[1675.00 → 1680.24] It is pretty neat. And I, just as a side note, I, I hate it when stuff like that gets deprecated.
+[1680.24 → 1685.56] Like I think, I think the whole Z-Wave stack that I'm using in Home Assistant has been deprecated
+[1685.56 → 1690.86] and I just don't want to reset up my Z-Wave network. And I don't know what that migration process
+[1690.86 → 1694.84] is like, and I just don't want to deal with it. And that kind of goes back to your topic earlier.
+[1694.84 → 1700.46] It's like, it's working. It's just, I don't, I don't want to break it. I don't want to have to
+[1700.46 → 1705.24] do anything with it because it's just so part of my infrastructure. Now it no longer feels like a
+[1705.24 → 1709.94] separate system. It feels like it is part of my home and I don't like messing with that stuff
+[1709.94 → 1716.48] anymore. And equally, because it is part of the house, the uptime needs to be as close to a hundred
+[1716.48 → 1721.70] percent as possible. Yeah. And then you have to balance that off against applying updates because
+[1721.70 → 1725.96] it's part of your house. You don't want to not update it for 10 years. I mean, some people would
+[1725.96 → 1731.14] just say if it's working, leave it, but I keep it up to date because I feel like I want to be
+[1731.14 → 1735.46] compatible with future technology and future functionality. I mentioned to you earlier,
+[1735.46 → 1740.12] I was like, maybe I should rebuild the whole setup and I should base it on virtualization because the
+[1740.12 → 1745.46] safety that a virtual machine gives me, that's that snapshot capability. And that, that holistic
+[1745.46 → 1750.26] restoring of a system or, or taking a copy of it and setting it on a shelf and saying,
+[1750.38 → 1756.70] this is known good. That is so appealing to me. And it feels like it gives me a safety net to what,
+[1757.18 → 1761.32] what seems like a risky proposition to keep updating all of these systems all the time.
+[1761.84 → 1765.76] That's where I keep thinking, maybe I got to rethink the way I'm doing stuff. And that's where I,
+[1765.88 → 1769.40] that's where I go down the rabbit hole and go, oh, it's too much. Not right now.
+[1769.40 → 1772.58] Do you use a hypervisor at all for, for anything?
+[1772.58 → 1777.44] No, right now the system's built around these Raspberry Pis. There's not a lot of overhead
+[1777.44 → 1783.94] there. So I'm just running containers on Ubuntu LTS on Pi 4, but I would be willing to replace,
+[1784.14 → 1790.66] you know, the two or three Raspberry Pis it takes to do this with one fairly low energy x86 machine.
+[1790.66 → 1795.10] And then I'd have sort of my, my, you know, my, my choice of virtualizes at that point.
+[1795.10 → 1800.32] Well, good news for you. Proxmox have just had a big release. Version seven was released on the 6th of
+[1800.32 → 1807.30] July 2021, and it's based on Debian bullseye number 11. I'm sure most of you know this bit
+[1807.30 → 1811.76] of trivia, but, uh, those of you coming to the Denver meetup might want to pay attention.
+[1812.10 → 1814.24] I might've given a question away there. Damn it.
+[1815.28 → 1818.70] I love it. No, that's good. That's good. Cause if they're a listener,
+[1818.82 → 1820.98] they get a heads-up and no one else will know.
+[1821.18 → 1827.16] Free trivia question coming your way. Which kids movie does Debian name its releases after?
+[1827.16 → 1831.44] Maybe you'll know, maybe you won't. Uh, it's just the sort of thing you'll have to come to the
+[1831.44 → 1836.28] meetup and find out about. All right. Now what else is included in this release? They've got a bunch
+[1836.28 → 1844.78] of new versions of stuff. So ZFS is now 2.04, uh, QEMU has been bumped to version six and the
+[1844.78 → 1850.78] there's a new kernel 5.11. So it's, it's perfect to see that Proxmox are pushing the envelope
+[1850.78 → 1856.34] here and updating lots of their core systems. The reason I say that in particular is that Debian has a
+[1856.34 → 1861.38] bit of a reputation for being a bit old and crusty. And you look at the versions of some of these
+[1861.38 → 1867.46] packages, and they're not that far off what is shipping in Arch, right? I mean, a 5.11 kernel
+[1867.46 → 1871.48] is older than what's in Arch, but it's newer than what's in most LTS distros right now.
+[1871.82 → 1876.58] And they've rolled out more recent Butters support, which I think is kind of a big deal.
+[1876.64 → 1881.76] It's nice to see essentially Butters and ZFS get near parity support in Proxmox.
+[1881.76 → 1886.28] It absolutely is. And I think this, this comes back to a point that, uh, I hear quite frequently
+[1886.28 → 1892.62] on Linux Unplugged actually, is that we need to start taking Butters seriously and, uh, stop just
+[1892.62 → 1897.56] treating it as a bit of a joke because, you know, Facebook and all these other massive companies
+[1897.56 → 1904.24] that have things at significant scale are putting a lot of, uh, blood, sweat and tears into the Butters
+[1904.24 → 1910.18] subsystems. And it does seem to be cropping up in more and more places. And, you know, for me,
+[1910.18 → 1917.02] I'm actually starting to use Proxmox as my default distro, you know, for, for server OSes because
+[1917.02 → 1926.32] it has ZFS baked in. So I don't need to Fitz about with DKMS or an AUR package to install a custom
+[1926.32 → 1931.66] kernel. I don't have to worry about the licensing. It's just taken care of. I mean, the same is true
+[1931.66 → 1938.74] of Ubuntu, but the thing that Proxmox gives me most out of all of this other stuff is a real slick
+[1938.74 → 1945.40] web UI to manage virtual machines and LXC containers. Great point. And I think that is
+[1945.40 → 1951.64] something that you and I probably underplay. I think for a lot of new users, that's like the
+[1951.64 → 1957.78] the biggest deal, right? Yeah, absolutely. Yeah. I, I completely agree on your points about Butters
+[1957.78 → 1963.80] too. I think the thing that you have to remember is what Butters offers is a file system that does
+[1963.80 → 1969.64] copy on write transparent compression. It can offer encryption. It can offer SSD trim support
+[1969.64 → 1975.50] and it's extremely low memory. So it works perfect. Say like in a Raspberry Pi situation
+[1975.50 → 1981.72] or in a laptop with a single SSD. Those are some use cases where ZFS is, is really not a great choice
+[1981.72 → 1989.70] there. And, and I, I really love the combination of the two. I think it makes for a really reliable home
+[1989.70 → 1996.18] server. And the way I use it now is Butters is on the root file system. So the system can boot
+[1996.18 → 2002.20] regardless of what's going on with ZFS. If, if your DKMS module fails to build for some weird reason,
+[2002.20 → 2008.38] which has happened to me, your system still boots because the core system, the file system is Butters.
+[2008.76 → 2013.78] And then your really large datasets with your multiple disks that are in some sort of RAID configuration,
+[2013.78 → 2019.26] that's where I go ZFS. And that mounts almost every time the system reboots. But if it doesn't,
+[2019.26 → 2024.10] because the root is Butters, it's guaranteed I can get in there and get the system repaired
+[2024.10 → 2028.76] and we can then get in, you know, then get other things online, like getting ZFS to mount.
+[2029.12 → 2033.26] And perhaps the biggest feature that we haven't touched on the single most important improvement
+[2033.26 → 2038.74] in Proxmox 7, I can now download ISOs on the web UI. Hooray!
+[2039.42 → 2043.88] Oh yeah. Dun, dun, dun, dun. So you give them a URL, and it downloads it or does that mean you can
+[2043.88 → 2044.70] download it to your machine?
+[2045.12 → 2049.38] Both. So what happens is you plug the URL into the, uh, the little form that says,
+[2049.44 → 2053.46] I want to download it to this particular area of storage. And then at the bottom,
+[2053.54 → 2058.92] this is a really nice feature. It has an optional box at the bottom for you to fill in the MD5
+[2058.92 → 2065.74] hash in there. So it will automatically verify the download for you as part of its automated process.
+[2066.12 → 2071.68] Now, a lot of people seem to think that Proxmox isn't free as in cost. Uh, it's,
+[2071.68 → 2078.14] it's open source. So it's free as in speech and it is also free as in beer. Um, the reason I thought
+[2078.14 → 2083.20] it wasn't free is because it has this little nag screen that says you do not have a valid
+[2083.20 → 2088.56] subscription for this server. And all that simply means is you have the enterprise repos enabled,
+[2088.56 → 2094.92] which are some air quotes, better tested packages. I don't know quite what that testing entails,
+[2094.92 → 2099.96] but that's what the Proxmox team say anyway. Um, and so you can support the project and give
+[2099.96 → 2106.16] them money, and they will enable your server to get rid of that nag message, or you could use
+[2106.16 → 2110.70] automation. You could use, I've written an Ansible role, which several of our community
+[2110.70 → 2115.88] have now contributed to as well, because open source is just that awesome. And what that does
+[2115.88 → 2121.10] is it goes in and removes the repos for you, changes a couple of lines in the, uh, web UI
+[2121.10 → 2127.66] files on the Proxmox system and removes the nag for you automatically. Just one more use case for
+[2127.66 → 2134.24] automation. And speaking of automation, we want to mention our friends over to Cloud Guru have a
+[2134.24 → 2138.80] course that we'll have linked in the show notes just for you. It's the Red Hat certified specialist
+[2138.80 → 2144.52] in advanced automation and Ansible best practices. In this course, they're going to cover the topics
+[2144.52 → 2150.02] on the EX447 exam as well to make sure you're ready to take that. If you're planning on expanding
+[2150.02 → 2153.36] your Ansible knowledge, this is a great course for you. You'll have a better understanding
+[2153.36 → 2158.96] of the topics on the exam and around Ansible and Ansible tower and managing and Ansible inventory.
+[2159.02 → 2163.72] And of course, templates as well. So you'll have to go over to our show notes to get the link to go
+[2163.72 → 2169.68] directly to this course. That of course is over at self-hosted. Show slash 49. You'll see the link for
+[2169.68 → 2174.50] ACG and that'll take you to the Red Hat certified specialist in advanced automation for Ansible best
+[2174.50 → 2184.84] practices. Did you get the update to your shield yet? Alex, I am so, so disappointed in this. I loved
+[2184.84 → 2190.20] the Nvidia shield so much. I've bought three of them in total. Furthermore, I've recommended them to the audience.
+[2190.20 → 2198.04] And I know that some people out there have also noticed that Nvidia has decided to improve your
+[2198.04 → 2203.86] experience by taking the top row, which used to be reserved for your favourite applications,
+[2203.86 → 2213.68] and now put full wide advertisements right there at the top, including folks in bondage,
+[2214.12 → 2219.64] folks doing all kinds of like crazy things like, you know, guns and violence and smoking. Like I've seen
+[2219.64 → 2225.46] the whole range. Thankfully, you know, we're not really that kind of, uh, we, we don't, it doesn't
+[2225.46 → 2229.12] really bother me that much. And it's in my bedroom. It's not like it's a the family uses it all the
+[2229.12 → 2235.52] time, but I really do not like the fact that I cannot turn it off. And, um, I think it's on my
+[2235.52 → 2239.82] list to replace now, Alex. It's really disappointed. It's such a great device. Yeah. It's, it's been a
+[2239.82 → 2246.24] fascinating one to watch the, uh, kind of cancel culture online react to this one. I mean,
+[2246.24 → 2253.10] on the one hand, I don't really care that much. Um, they, they've taken an interface that was
+[2253.10 → 2259.48] very clean and just got the job done and didn't really have any cruft to it whatsoever.
+[2260.14 → 2263.12] And then, as you say, they've polluted it with a bunch of ads. I mean, that,
+[2263.60 → 2268.78] that on the one hand sounds pretty terrible, but I mean, on the, on the other hand, I don't,
+[2268.88 → 2273.54] I just don't find myself really caring all that much. I, uh, I, I've been browsing the
+[2273.54 → 2280.66] the Subreddits, um, the Nvidia shield Subreddit for the last few years. And there's lots of people
+[2280.66 → 2286.20] now posting custom launches that you can install on the Nvidia shield. I mean, it's just Android
+[2286.20 → 2291.26] underneath, right? So you can install a custom launcher if you want to. And I think all this
+[2291.26 → 2297.68] is going to serve to do is motivate those who do care about such things to release better quality
+[2297.68 → 2301.58] third party launches rather than relying on the, the Google provided one.
+[2301.58 → 2306.86] I think I'll probably just switch it to an Apple TV. I have found that the Apple TVs perform even
+[2306.86 → 2311.52] better than the Nvidia shield, which I felt like was pretty well performant. This is the exact kind
+[2311.52 → 2316.22] of thing that will never happen on the Apple TV platform. And it, you know, it's been, the UI has
+[2316.22 → 2323.92] been very consistent now for years. The other thing is it, it wakes, and it controls the TV more
+[2323.92 → 2327.36] consistently than the Nvidia shield has too. So I think I'm just going to switch it out.
+[2327.36 → 2333.86] I wanted to keep it because I liked the idea of having both. And I really love Cody. You know,
+[2333.88 → 2339.96] that's a big reason why I keep the shield is I really love Cody, but in fuse on Apple TV,
+[2339.96 → 2345.64] it replaces Cody. In fact, I actually have to say, I think maybe in fuse is, is probably better
+[2345.64 → 2351.98] because it's just a newer app built with more modern technologies, and they've just steadily added
+[2351.98 → 2357.08] the features you need. It doesn't quite have the plugin ecosystem that Cody does, but in fuse
+[2357.08 → 2362.10] is a really great local file playback, play from your file shares, all that kind of stuff.
+[2362.64 → 2369.50] And it syncs via iCloud to your other Apple TVs. So your settings, you set it up once, and it's,
+[2369.82 → 2376.44] Oh, and also out of the box supports syncing play status with Plex. And I can't remember if it does
+[2376.44 → 2381.86] Jellyfin, but it's, it's a perfect app. And so it does the job that Cody does. And so I think
+[2381.86 → 2385.62] it's just time to, I think I'm done with Android TV. I'm going to keep a couple of Chromecast's around
+[2385.62 → 2388.44] and that's going to be it. Well, if there's one thing we've learned from the internet,
+[2388.44 → 2394.12] it's the adverts always make everything better. I mean, YouTube's better because of all the ads.
+[2395.12 → 2401.74] Radio is better because of adverts, right? I mean, I struggle to think of a single example where
+[2401.74 → 2406.32] an advert makes things better. I think I wouldn't have even minded as much if it was only
+[2406.32 → 2412.34] showing ads for services that I maybe have active logins for on the device, but right. But it's
+[2412.34 → 2416.30] showing me advertisements for services that I don't have and will never subscribe to. So that
+[2416.30 → 2421.08] drives me crazy. And then I think the other thing is if it was at the bottom of the UI,
+[2421.48 → 2426.82] if they hadn't, if they hadn't taken the row of icons and lowered it. And so now you have to
+[2426.82 → 2431.78] navigate down and that would have been better as well. What do you make of the argument that the
+[2431.78 → 2436.26] Nvidia shield was a premium device? This, this is quite a pervasive argument on
+[2436.26 → 2442.14] Reddit that, you know, it's a $200 device. It's a premium device. I've chosen this over
+[2442.14 → 2446.64] something like the Google Chromecast, you know, the new one with the remote that has this same UI,
+[2446.72 → 2452.04] by the way. What do you make of that argument? Because to me, I think I kind of agree with it
+[2452.04 → 2457.24] in, in the yeah, one of the reasons I paid for the shield, I pay the extra money for two of them in
+[2457.24 → 2463.08] this house was because it was so blazing fast. And because I didn't have this stuff kind of rammed down
+[2463.08 → 2467.54] my throat, you know, without, without asking for it. Nvidia have just patched this thing for years
+[2467.54 → 2473.66] and years and years. And it's, it's just been very reliable. And unlike you, I'm, I'm left feeling
+[2473.66 → 2480.36] rather deflated about it. Yeah. It feels like a play to get affiliate revenue for stream signups.
+[2480.44 → 2484.52] And it's like, they have a user base out there. They're not selling them as much anymore because
+[2484.52 → 2488.06] they're not as competitive as they used to be. And there are cheaper options out there.
+[2488.06 → 2492.82] And I think the Apple TV is starting to eat up some of its market share as well, because I think
+[2492.82 → 2497.54] other people have realized it's a better box as well. And so I think Nvidia felt let's monetize
+[2497.54 → 2501.58] what we've got here because they get some ongoing affiliate revenue from those subscriptions,
+[2501.58 → 2505.96] depending on the deals that work out. That's too tempting, I think for them to say no to.
+[2506.90 → 2511.78] And I do agree that it is a premium device. It absolutely is. I think $200 is on the cheap end.
+[2511.86 → 2515.62] I think if you buy the like I, the first one I ever bought was the one with like the big hard drive
+[2515.62 → 2520.30] and all of that. And the controller, I want to say that was like $300 or something.
+[2520.88 → 2528.16] I bought that box because ROK's and cheaper boxes had that kind of crap. It's one of the
+[2528.16 → 2533.08] reasons I didn't get a fire is because the Amazon fire does this as well. It's rows of advertisement.
+[2533.74 → 2538.56] And so I didn't buy an Amazon fire. And so I didn't buy a ROK. I bought an Nvidia shield
+[2538.56 → 2546.80] specifically because it didn't have this crap on it. Right. And so to have them retroactively add
+[2546.80 → 2552.50] that, like that wasn't the deal, bro. When I spent $300 on your kit, that's, this wasn't the deal.
+[2553.92 → 2559.32] I just hate it. And I think the custom launcher solution is not a bad one and maybe one I will
+[2559.32 → 2564.40] explore, but it's unfortunate. It's sort of like when people tell you to solve the problems with an
+[2564.40 → 2569.14] Android phone by flashing a custom ROM on there. It's like, come on, man. Yeah, I know you can do
+[2569.14 → 2574.16] that, but most consumers aren't going to do that. They're just not. On that note, Will actually wrote
+[2574.16 → 2578.86] in, and that's why we're talking about this, asking if you could put lineage on the shield. And I think
+[2578.86 → 2583.86] that's a pretty interesting idea, actually. I don't think it's supported today, but certainly moving
+[2583.86 → 2589.82] forward, I could see a much more motivated community emerging around this kind of stuff now.
+[2590.16 → 2593.14] I tell you what, if a decent lineage image showed up for that thing, I'd try it.
+[2593.14 → 2596.64] Yeah, me too. And I mean, I, even though I just said most people aren't going to,
+[2596.76 → 2600.54] the vast majority of consumers who bought this won't, I'd still, I'd use it.
+[2600.66 → 2606.62] Now, another option you've got is to replace the launcher.APK via Team Win Recovery Project
+[2606.62 → 2611.78] to one of the old versions of the launcher that doesn't have ads on the home screen.
+[2612.14 → 2616.72] You'll need to unlock your bootloader to do that, but it doesn't require root or anything like that.
+[2616.94 → 2621.02] Well, David from North Carolina wrote in, he said, I'd love to know a little more details
+[2621.02 → 2625.22] around the solar panels that Alex recently had installed, especially since they seem
+[2625.22 → 2628.50] to integrate with Home Assistant. I've been trying to convince my wife that it would
+[2628.50 → 2632.62] be a worthwhile investment, love the show, and keep up the work. Thanks, David. And I
+[2632.62 → 2635.72] think he's like extra excited because he's from your home state.
+[2635.98 → 2637.84] Yeah, North Carolina. Hey, David, how are you doing?
+[2638.16 → 2640.74] Is it called a home state now? I mean, your new home state?
+[2641.92 → 2646.84] Well, is it? I don't know. I still refer to England as home, and I still watched England
+[2646.84 → 2651.42] crash out of the Euros in the final, and I still wept like a small child when that happened,
+[2651.54 → 2656.38] but you know. But you also have the first state that you called home in the US.
+[2656.58 → 2660.46] It's also the first state where I, it's the first place in the world where I had a child,
+[2660.60 → 2664.08] so you know, there is that. So it's your home, I think it's like, as far as states go,
+[2664.16 → 2666.40] it's your home state. Yeah, yeah, it probably is.
+[2667.98 → 2669.70] So what do you think? You got details for them?
+[2669.92 → 2673.70] I've got a few, yeah, not, I don't have, you know, specific model numbers or anything like
+[2673.70 → 2678.76] that, but I went to a company called NC Solar Now. I looked at Tesla and a few others, but
+[2678.76 → 2684.74] the NC Solar Now folks were the ones that came out with the, you know, the best overall price
+[2684.74 → 2690.72] and package and service and financing and all that kind of stuff. And I ended up going for a
+[2690.72 → 2696.22] SolarEdge system, and this has a home assistant integration which connects to the they've got
+[2696.22 → 2701.98] this website, and it will connect through the API to the website for up to 15 times an hour,
+[2701.98 → 2707.56] I think it can pull the website through the API. And it was just a case of providing an API key.
+[2707.76 → 2713.28] It took literally five minutes to set it up. I had to spend an extra few hundred dollars on the
+[2713.28 → 2721.06] little Zigbee monitoring device to enable the inverter that's outside to talk to the internet,
+[2721.06 → 2726.06] because by default it doesn't come with any Wi-Fi capabilities. But apart from that, you know,
+[2726.32 → 2731.52] extra few hundred dollars to get the monitoring capabilities. Yeah, it's been very straightforward
+[2731.52 → 2737.44] to set it up. And not only does it talk to home assistant, but the SolarEdge company also provides
+[2737.44 → 2744.40] a really nice dashboard and a really pretty slick mobile app as well. So I've got a little widget on
+[2744.40 → 2749.02] my Android home screen that tells me exactly what my solar is doing right now, which is pretty cool.
+[2749.02 → 2757.44] That's great. Yeah. I love that they're using Zigbee for that. Just the thing, Zigbee's all over the
+[2757.44 → 2762.32] place here. Nate wrote into the show asking about security implications for sharing Ansible playbooks
+[2762.32 → 2766.96] publicly. You know, he sees them on GitHub, all of that. He got thinking about this after he listened
+[2766.96 → 2770.52] to an episode of the Dark net Diaries, and he wondered if you have any thoughts on it.
+[2770.52 → 2778.10] Well, all of my stuff's open source on GitHub.com slash ironic badger slash infra. You know, I have
+[2778.10 → 2783.72] open sourced everything for years now. That's kind of my default policy. So I sure hope there isn't a
+[2783.72 → 2786.44] privacy implication of doing that. You know?
+[2787.72 → 2788.66] Good answer.
+[2788.66 → 2795.94] Yeah. I do encrypt everything using Ansible Vault. So all of my secrets and things like that are stuck
+[2795.94 → 2803.08] behind AES-256 encryption. So hopefully, unless I commit a secret directly in clear text, I think
+[2803.08 → 2806.66] I'm okay. Yeah. I just, you know, when I go through your GitHub, I just look at it. I think, you know,
+[2806.66 → 2810.40] everything looks pretty good except for that passwords.txt file where you just put all your
+[2810.40 → 2816.72] passwords in there. Well, funny story on that. I actually published my Gmail password one time to
+[2816.72 → 2824.46] that repo. And I had a guy, a listener in Australia message me. Like, it must have been first thing in
+[2824.46 → 2828.62] the morning for him because it was just before I went to bed saying, hey, by the way, did you know
+[2828.62 → 2833.92] that commit you pushed 12 minutes ago has your Gmail password in it? And I'm like, okay, first,
+[2834.06 → 2840.20] thank you for letting me know. Secondly, it was 12 minutes ago. Like, were you just waiting for me to
+[2840.20 → 2840.90] push something?
+[2841.78 → 2843.92] Yes. He's got some sort of like alert.
+[2843.92 → 2851.12] Uh, so to get around that, uh, Nick Busy from the Home Lab OS project, uh, helped me out with a
+[2851.12 → 2857.72] pre-commit, uh, hook that I have in my Git repo that just checks that my secrets file is encrypted
+[2857.72 → 2863.48] before I push and do a Git commit and push. That's been very, very useful. It doesn't protect against
+[2863.48 → 2868.88] me actually putting API keys and variables and stuff like that directly into other files, which,
+[2868.88 → 2874.14] you know, there comes a point where you've got to be like, right, okay, this, you know, my safety net
+[2874.14 → 2880.72] is checking that file is encrypted or not. It's not going to go and scan every single file. Um, so
+[2880.72 → 2885.78] yeah, I guess it's up to you whether you feel comfortable with that risk or not. And, uh, I,
+[2885.84 → 2891.04] I tend to think that even if you're using a private repo on GitHub, you may as well treat that as a public
+[2891.04 → 2895.04] repository anyway, because one day it will be whether you like it or not. So.
+[2895.04 → 2899.00] And it really just means, can you stick to like a good hygiene with that kind of stuff?
+[2899.26 → 2903.28] If you'd like to get your question in or have a comment or something you think we should check out,
+[2903.66 → 2906.98] let us know, go over to self-hosted. Show slash contact.
+[2907.46 → 2911.26] And you can go to self-hosted. Show slash SRE to show your support for the show.
+[2911.52 → 2916.40] Yeah. Become a member, get access to the post show. And of course, uh, help us keep the show
+[2916.40 → 2917.68] on the tracks.
+[2918.04 → 2921.52] I think this episode, we're going to talk about the future of the gasoline engine
+[2921.52 → 2923.16] and the internal combustion engine.
+[2923.16 → 2925.26] Oh, I have thoughts on that. Interesting.
+[2925.60 → 2931.08] Yeah, me too. Now I was browsing some, I always seem to come up with YouTube on these things,
+[2931.16 → 2936.48] don't I? But anyway, uh, about steam trains the other week. And, uh, I found this Union Pacific
+[2936.48 → 2942.40] steam loco called the big boy. And this thing is freaking enormous. And it was designed, uh,
+[2942.40 → 2948.42] in the early, uh, part of last century to get over some of the Rocky mountain passes because
+[2948.42 → 2954.82] they're just so vast here and the trains are so heavy. And so Union Pacific have actually restored
+[2954.82 → 2960.36] one of these big boy steam locos, which is essentially two massive steam locos glued together.
+[2960.58 → 2967.40] This thing has basically two sets of drive wheels and two, two full sets of pistons. And it's just
+[2967.40 → 2973.90] awesome. Just go look it up. Big boy Union Pacific steam loco. And it's going on tour in August around
+[2973.90 → 2980.66] the US. So it's, it's leaving Cheyenne, Wyoming and going all the way down to Houston past, uh,
+[2981.08 → 2984.10] our beloved cheese bacon's hometown of Beaumont.
+[2984.50 → 2986.12] I know he lives in Denver now, doesn't he?
+[2986.40 → 2988.28] Okay. Well, so much for that.
+[2988.28 → 2990.26] You could say it's his original hometown though.
+[2990.62 → 2997.28] So much for that plug. Um, so yeah, it's going up to, I think, uh, through Dallas at some point
+[2997.28 → 3002.02] and then up through Kansas City and St. Louis. So if you're in the centre of the country,
+[3002.02 → 3006.98] by all means go take some pictures for me, because I'm not going to be able to make that one. But,
+[3007.02 → 3009.02] uh, throughout August, it's traversing the country.
+[3009.48 → 3013.04] That does look like an incredible route. Actually. We'll have a link in the show notes.
+[3013.10 → 3016.12] And when you go there, they have a map that shows you the route that they're going to be on.
+[3016.46 → 3020.68] Well, you know, it's either side of our Denver meetup, don't you? So I reckon if you were creative
+[3020.68 → 3023.16] with your schedule, Chris, you could probably find it for a day.
+[3023.20 → 3029.04] Our route for the Denver meetup in total is a good, it's going to be just over 5,000 miles.
+[3029.04 → 3036.40] That's a long way. I drove that myself in 2018. We flew into Orlando, drove up to DC,
+[3036.62 → 3042.06] drove down to Austin to meet you for the first time and then, uh, up to Denver. And that was
+[3042.06 → 3047.66] about 5,000 miles. And we did that in three weeks in a car. I mean, it wasn't, it wasn't our house.
+[3048.14 → 3051.84] Now I'm going to be in a land yacht. Yeah, that's for sure. But if you're going to be in the area,
+[3051.84 → 3054.82] don't forget that we have those meetups coming up, and you can get details
+[3054.82 → 3059.82] at meetup.com slash Jupyter Broadcasting. Make sure you don't miss the next episode,
+[3059.92 → 3065.82] episode 50. We've got some cool stuff lined up for you and rumour has it there might be some swag.
+[3067.12 → 3072.12] Hmm. In the meantime, you can find Alex on Twitter. He is at Ironic Badger. I'm at Chris
+[3072.12 → 3075.48] LES and the show is at self-hosted show. And thanks for listening, everybody.
+[3075.48 → 3078.30] That was self-hosted. Show slash 49.

50： Perfect Plex Setup _summary.txt

@@ -0,0 +1,66 @@
+• The podcast, Chris and the Badger, is celebrating its 50th episode.
+• Hosts Chris and Alex discuss their long-term relationship with their show and their audience.
+• They mention a special intro made by their Discord community to celebrate the milestone.
+• A merchandise line has been created for fans, including shirts and stickers, available at jupitergarage.com.
+• The hosts express gratitude to their listeners and sponsors, particularly Cloud Guru.
+• Chris shares some lessons learned from his recent experience with the "great flood" of a few weeks ago.
+• Power adapters and charging station for the kids' devices
+• Upgrading charging system in preparation for road trip
+• Considering 3D printing custom inserts for devices
+• Discussing cheap 3D printers, specifically Prusa Mini and Ender
+• Upcoming meetup in Denver on August 20th and Salt Lake City
+• Planning for road trip, including flight arrangements and Brent's role as a "precious resource"
+• The speaker mentions making good on a promise to visit Salt Lake City, Utah
+• The speaker references the Book of Mormon and its depiction of the city
+• A discussion about a venue in Salt Lake City that had strict rules regarding alcohol
+• The speaker's experience with Amazon Fire tablets for home automation and their desire for an easy solution
+• The discovery of Wall Panel, an Android app for web-based dashboards like Home Assistant
+• Using Wall Panel to enable features on the Amazon Fire tablet, such as motion detection and screen sleep/wake functionality
+• Alternative options for customizing or reflashing the Amazon Fire tablet, including the Amazon Fire Toolbox
+• The speaker discusses a Visual Basic app that allows users to "lobotomize" their Amazon Fire tablets and remove unwanted software.
+• The app requires access to a Windows machine, which may not be feasible for some users.
+• A Linux version is reportedly in development, but the current lack of support limits its accessibility.
+• The speaker expresses frustration with Amazon's aggressive marketing tactics on Fire tablets.
+• He notes that modifying devices like this does not necessarily void warranties if done properly.
+• The conversation shifts to discussing home automation and the use of a dashboard setup for controlling devices.
+• The speaker mentions an "on-wall dashboard" feature in the Wall Panel app, which allows users to create a custom interface for their devices.
+• He suggests that replacing the OS on an Amazon Fire tablet is the next step towards making it fully functional.
+• The speaker uses a Python script to scrape data from Fireside and generate Markdown files for show notes
+• The show notes are then ingested by MKDocs to create the website at notes.jupiterbroadcasting.com
+• The website is automatically updated daily using GitHub Actions and con job
+• Linode's infrastructure and services, including their API and command line client, are used for hosting and sharing files
+• The speaker uses Linode for its affordability, ease of use, and high-quality infrastructure, which has been reliable since 2003.
+• Linode's features and benefits for hosting and managing cloud infrastructure
+• Using Linode as part of a multi-cloud strategy to save money compared to relying on one hyperscaler
+• Customer service and community support provided by Linode
+• A Reddit thread discussing an ISP blocking Plex due to suspected malicious activity, revealing how the Plex web app works and potential implications for streaming services
+• ISPs interfering with video streaming quality profiles to encourage users to pay more for faster speeds
+• Frustration with Shaw's decision to block Plex due to copyright concerns
+• Discussion of copyright law and the difference between downloading and streaming content
+• Introduction to the Plex Meta Manager script, which organizes metadata and creates collections based on genres and other criteria
+• Explanation of how the script works and its features, including refreshing critic ratings and creating trending collections
+• Personal experience with setting up the script using Docker and systemd timers
+• Discussion of the benefits of using the script to manage metadata and improve the Plex user experience
+• Discussion of using Plex API token to authenticate and access Plex features
+• Introduction of Movie Match, an app that helps groups choose movies to watch together
+• Personal anecdotes about Star Wars and pod racing
+• Explanation of how Movie Match works with Plex library and swiping mechanism
+• Announcement of a new feature in Plex client to blur out future episodes for better user experience
+• Prediction that Plex will introduce this feature in the future
+• Using Infuse to watch Plex on Apple TV
+• NVIDIA Shield update issues
+• Considering getting an Apple TV due to the update problems with NVIDIA Shield
+• Sponsored by CloudGuru and Cloudfree.shop
+• Listener feedback, including a question about Docker updates from Greg
+• Alex provides advice on managing Docker image updates and security
+• Concerns about cloud-based security systems requiring expensive hardware
+• Discussion of Blue Iris as a recommended Windows app for surveillance needs
+• Recommended hardware setup: HP 290 Slim box, PoE switch, and PoE cameras
+• Comparison of wired vs Wi-Fi cameras for reliability and performance
+• Mention of Wyze system limitations due to unreliable Wi-Fi cameras
+• Brief mention of Arlo camera system as an alternative
+• Discussion of a security camera system with base station unit and local video storage
+• Comparison of Wyze cameras, noting limitations of V2 and lack of RTSP firmware for V3
+• Recommendation to hold off on purchasing Wyze cameras until further testing is done
+• Promotion of Jupiter Garage merchandise sale and special discount for members
+• Goodbyes exchanged between two individuals.

50： Perfect Plex Setup _transcript.txt

@@ -0,0 +1,796 @@
+[1.00 --> 8.72]  You're now listening to Chris and the Badger, a presentation of the self-hosted podcast with Chris.
+[9.16 --> 13.64]  A lot of options out there, but you can use this stack. I've tested this. I've refined it over the years.
+[13.72 --> 14.44]  And Alex.
+[14.58 --> 17.82]  I don't think there's a better solution, really, if you're willing to put the effort in.
+[17.90 --> 20.16]  And featuring special guests.
+[20.96 --> 22.42]  Morgan the doorbell guy.
+[22.60 --> 23.98]  Wes Payne.
+[24.22 --> 24.90]  An RV.
+[25.50 --> 25.98]  JDM.
+[26.20 --> 26.54]  What?
+[27.54 --> 28.72]  Jonathan from Unraid.
+[28.72 --> 30.46]  Hang on a sec. This goes on for a while.
+[31.82 --> 32.26]  Geerling.
+[32.68 --> 33.92]  And your hosts.
+[34.38 --> 36.40]  Who are celebrating episode...
+[36.40 --> 37.50]  Oh, come on.
+[38.12 --> 38.64]  Hang tank.
+[39.42 --> 39.74]  All right.
+[40.26 --> 41.04]  And Jeff Geerling.
+[41.22 --> 42.48]  Okay, now your hosts.
+[42.62 --> 43.90]  Snap Raid and Merger FS.
+[44.32 --> 46.10]  And I endorse this media server build here.
+[46.32 --> 48.14]  Celebrating episode number 50.
+[48.38 --> 50.62]  A long-term relationship with same thing.
+[50.78 --> 51.88]  I think, what else could I do with it?
+[51.92 --> 54.68]  And that single spark is a huge rabbit hole.
+[54.68 --> 55.50]  Huge rabbit hole.
+[56.08 --> 57.30]  Chris and Alex.
+[58.72 --> 61.00]  Well, welcome to episode 50, everybody.
+[61.24 --> 65.44]  I hope you liked our special intro to celebrate the 50th episode.
+[66.02 --> 66.58]  Yeah, that's great.
+[67.00 --> 68.94]  Congratulations, Alex, to episode 50.
+[69.04 --> 73.08]  And thank you to, oh, yeah, in our Discord for making that awesome intro.
+[73.66 --> 77.70]  Now he's got to make a special edition show themes all the time.
+[77.76 --> 78.90]  That was amazing.
+[79.40 --> 80.36]  And it's here, Alex.
+[80.92 --> 81.74]  50 episodes.
+[81.80 --> 84.32]  And it takes a while when you're doing them only twice a month.
+[84.64 --> 85.56]  It's been a long haul.
+[85.56 --> 87.12]  Yeah, 50, huh?
+[87.46 --> 91.06]  It means, what, nearly two years of doing this with you.
+[91.50 --> 96.18]  And to celebrate, we've actually got some merch available for the first time.
+[97.96 --> 100.94]  This really was all really driven by Alex.
+[101.00 --> 102.06]  He wanted to see this done.
+[102.74 --> 103.90]  Of course, I wanted to see it too.
+[104.12 --> 108.62]  But Alex really took the lead and made sure we got something special for you guys for episode 50.
+[109.02 --> 111.54]  We have it up at jupitergarage.com.
+[111.54 --> 118.32]  We've got a couple of special shirts, a Chris and the Badger shirt and a self-hosted logo shirt, if you'd like that.
+[118.44 --> 127.42]  And we also have a couple exclusive stickers, a self-hosted square sticker, and of course, a Chris and the Badger sticker, which would look great on your machine, I got to say.
+[127.82 --> 128.70]  Yeah, I think it would too.
+[128.70 --> 135.88]  I mean, I think it was when Drew, who's our editor, sent me a little electronics project full of parts.
+[135.88 --> 140.78]  And it said, to the Badger on the corner, I was like, we need to lean into this a bit more, don't we?
+[140.82 --> 142.10]  Yeah, we are leaning into it.
+[142.42 --> 144.96]  I think with episode 50, we're just like, we're doing it.
+[145.36 --> 146.00]  We're doing it.
+[146.00 --> 148.80]  And it's because, you know, people kind of came together and helped us make it special.
+[149.54 --> 151.54]  So that's up there right now.
+[151.54 --> 158.70]  And if you are a self-hosted SRE, one of our members, then check out the post show and check out your member feed.
+[158.78 --> 163.60]  We will have a special promo code for you to take a little bit off the gear.
+[163.76 --> 165.94]  But it's all actually at a really great price right now.
+[166.00 --> 171.04]  We're basically running it pretty close to cost as it is because we just wanted to have something special out there for episode 50.
+[171.40 --> 174.26]  So all of it is up at jupitergarage.com.
+[174.26 --> 181.22]  And if I could just take a moment to interject and just say a huge thank you personally to all of you for listening to all these episodes.
+[181.54 --> 192.50]  It's a real privilege to do this show with you, Chris, but also be able to present to the audience that we have who engage on Discord so well and on Twitter and all that kind of stuff as well.
+[192.58 --> 195.90]  So it's been a huge privilege for me and a big, big thank you.
+[196.42 --> 201.18]  And we want to say thank you to a cloud guru, the leader in learning for the cloud, Linux and other modern tech skills.
+[201.18 --> 203.84]  They have hundreds of courses and thousands of hands-on labs.
+[204.26 --> 208.66]  So go get certified, get hired and get learning at a cloudguru.com.
+[209.22 --> 213.60]  Well, I'd imagine that you're still rebuilding from the great flood of a few weeks ago.
+[213.70 --> 214.26]  How's that going?
+[214.70 --> 217.12]  It is indeed an ongoing process, Alex.
+[217.66 --> 219.10]  We'll just say that, I guess.
+[219.52 --> 225.04]  I actually did pick up a couple of quick tips that I'll share in a bit in the show from this entire experience.
+[225.04 --> 228.00]  And so I guess there's a bit of a silver lining there to it.
+[228.32 --> 229.90]  But I haven't replaced everything.
+[230.26 --> 233.28]  I have successfully saved a couple of items.
+[233.44 --> 234.42]  So that's awesome.
+[235.06 --> 238.84]  But for the most part, I'd say like 90% of everything was a loss.
+[239.44 --> 240.12]  Oh, damn.
+[240.64 --> 241.82]  I mean, I hope you had insurance.
+[242.24 --> 244.10]  Well, some of it's just old gear, you know.
+[244.10 --> 246.74]  Some of it's just old stuff like chargers and whatnot.
+[246.88 --> 249.12]  I suppose I could probably try to do the insurance thing.
+[249.86 --> 254.28]  I have a box in the attic full of old English for some reason.
+[254.62 --> 255.90]  They made it across the channel.
+[256.44 --> 256.84]  Channel?
+[257.16 --> 257.52]  Ocean.
+[258.04 --> 260.06]  I have a box full of English power adapters.
+[260.34 --> 262.66]  And so they're the sort of things that just hang around forever.
+[262.66 --> 267.94]  So maybe it's a good thing that you douse them all with, you know, 17 gallons worth of water.
+[268.58 --> 270.96]  And I do need to kind of like change up my charging situation.
+[271.08 --> 279.78]  See, what I got going in this area is a charging station, you could say, for all of the kids' iPads and switches and controllers.
+[280.28 --> 290.44]  And so this whole situation has actually inspired the wife and I to cap the water pipes at that area, remove the faucet completely.
+[290.44 --> 299.54]  And then after we get back on the impending Denver road trip, we're going to build a shelving system in there where the kids can slide their devices into shelves and they'll have power cords pre-run.
+[299.90 --> 305.98]  So the whole incident's actually inspired us to really kind of up our game instead of just having like this loose area where we stash stuff near a sink.
+[307.46 --> 310.08]  But it just took the disaster to kick our butts into gear, I guess.
+[310.26 --> 317.58]  You know, one of these days I might convince you to get a 3D printer and custom print the right size inserts for the devices.
+[317.58 --> 328.40]  And there's been a couple of fixes and a couple of projects for this road trip a couple of times now, because this is one of the bigger trips, because we're going to be on the road for probably about 40 days straight.
+[328.58 --> 335.68]  If you think about that in terms of just wear and tear on a vehicle and the house box that is running on top of that vehicle, that's a lot.
+[335.78 --> 338.36]  And so there's been a lot of things we're doing to prepare for it.
+[338.36 --> 346.16]  And I've thought a couple of times, a few things I'm replacing, like trying to get a magnet on my door so that lines up with the sensor and trying to just position that magnet just right.
+[346.62 --> 351.64]  If I could have built a little 3D housing for that to just position it where I needed it, it would have been job done.
+[352.44 --> 353.26]  It's on my mind.
+[353.64 --> 354.28]  It may happen.
+[354.64 --> 356.40]  You have a few options of cheap 3D printers.
+[356.64 --> 359.06]  I mean, there's a Prusa one that's the Prusa Mini.
+[359.16 --> 360.82]  It's about 400 bucks delivered.
+[361.82 --> 363.10]  Ender makes some.
+[363.26 --> 364.42]  Creality makes some as well.
+[364.42 --> 368.18]  But I had bad experiences with the Chineseian printers.
+[368.86 --> 371.90]  And personally, I'm a huge fanboy of Prusa because they open source everything.
+[372.30 --> 378.10]  And nine times out of ten, the print just works, which is what I'm in 3D printing for.
+[378.20 --> 382.34]  I'm not really in it to tinker and 3D print new parts for my printer.
+[382.44 --> 383.94]  I want to print cool stuff, you know.
+[384.48 --> 388.62]  I just figured I'd wait for you to upgrade your current rig and then I'd buy this one off you used.
+[389.74 --> 390.98]  That does tend to happen.
+[392.00 --> 392.64]  Yeah, yeah.
+[392.68 --> 393.14]  We'll see.
+[393.14 --> 393.76]  We'll see.
+[393.76 --> 395.78]  But we will be in Denver soon.
+[395.86 --> 396.52]  We're going to have a meetup.
+[396.60 --> 398.72]  Alex is going to be there running trivia night.
+[399.00 --> 401.62]  So go to meetup.com slash Jupiter Broadcasting.
+[401.82 --> 405.60]  I think it's August 20th, a Friday that we're going to be in Denver doing the meetup.
+[405.82 --> 407.70]  There's also a meetup coming up in Salt Lake City.
+[407.94 --> 408.96]  Just only I will be there.
+[409.06 --> 410.36]  Alex won't be making it to that one.
+[410.64 --> 413.24]  But details for that are at meetup.com slash Jupiter Broadcasting.
+[413.78 --> 415.80]  It's going to be weird getting on a plane, I'll tell you that.
+[416.28 --> 418.24]  How long of a flight is it to Denver for you guys?
+[418.66 --> 420.60]  About three or four hours, I think.
+[420.60 --> 424.88]  It really is just the perfect midpoint between you and me, isn't it?
+[425.02 --> 426.66]  It's like right there smack dab in the middle.
+[426.98 --> 428.80]  Yeah, it's either that or the middle of Arkansas.
+[430.46 --> 436.80]  Most of the crew is flying out with the exception of myself, of course, my wife and Brent.
+[437.64 --> 446.52]  Brent, you know, from Brunch with Brent is flying into Seattle and then he is going to caravan out with the family and I in Lady Joops.
+[446.52 --> 448.30]  Oh, I'm so jealous.
+[448.78 --> 451.70]  Brent is a precious resource that we have to share out carefully.
+[451.94 --> 452.84]  We do, yeah.
+[453.36 --> 455.74]  Yeah, well, he'll have his fill of us, I think, by the time.
+[457.22 --> 458.20]  I mean, you know.
+[458.56 --> 459.68]  It's actually going to be pretty great.
+[459.76 --> 460.50]  The kids are excited.
+[461.66 --> 466.72]  This is going to totally, this is going to, like, enshrine him as Uncle Brent at the end of this road trip, you know.
+[466.88 --> 467.88]  So that'll be pretty great.
+[468.38 --> 469.48]  And I'm really looking forward to it.
+[469.68 --> 471.28]  Well, I'm extremely jealous of that.
+[471.42 --> 473.96]  And I hope you have a great time on the road.
+[473.96 --> 476.04]  I've always wanted to do Salt Lake City.
+[476.24 --> 478.40]  I never quite made it that far north in Utah.
+[478.62 --> 484.50]  We did Arches and Dead Horse State Park and that kind of stuff near Moab a couple of years ago.
+[484.74 --> 485.80]  That was amazing.
+[486.06 --> 488.44]  If you're ever in that area, amazing, amazing stuff.
+[488.90 --> 489.70]  Absolutely love it.
+[489.86 --> 490.12]  Totally.
+[490.24 --> 490.84]  You're absolutely right.
+[490.88 --> 491.98]  It's like another world.
+[492.06 --> 494.28]  It feels like you're on a set of Star Trek when you're in Moab.
+[494.48 --> 494.78]  Mars.
+[494.86 --> 499.20]  You know, Salt Lake City was a promise I made to the audience because it's not, like, exactly on our way to Denver.
+[499.20 --> 504.50]  But I made a promise to the audience that when we could, we'd return to Salt Lake City because we had to skip it.
+[504.72 --> 505.58]  We had a whole thing planned.
+[505.68 --> 506.26]  We had to skip it.
+[506.30 --> 509.74]  So this is making good on a promise to the audience in Salt Lake City.
+[510.34 --> 518.62]  Perhaps this is an entirely gross misrepresentation of Salt Lake City, but it's kind of colored to me by the Book of Mormon, if you've seen that.
+[518.62 --> 523.70]  I mean, you know, it gets a lot.
+[524.28 --> 533.38]  Actually, just sort of tangentially related to that, when we were trying to book a venue, we had to listen to a whole bunch of rules about alcohol that we have never had to sit through from any other state.
+[535.08 --> 535.80]  It's a thing.
+[536.04 --> 536.60]  It's a thing.
+[536.60 --> 547.02]  Well, when you've had one too many beers after a meetup, the last thing you want is to be fumbling around for a phone in your pocket or trying to remember what voice command you programmed into the lady cylinder this week.
+[547.10 --> 549.28]  Have you got a solution to that?
+[549.64 --> 553.42]  I had a fire tablet that worked pretty well before I got water destroyed because it fell out.
+[553.50 --> 554.34]  It was off the wall.
+[554.46 --> 555.80]  It fell into the water bath.
+[556.34 --> 562.36]  But also, you know, Brent's going to be on board and he doesn't know all those special commands and he's going to want to control things.
+[562.36 --> 573.54]  So I wanted to get that tablet on the wall replaced, which runs my home assistant dashboard 24-7 because it makes it easier for the family and it makes it easier for guests.
+[574.08 --> 578.04]  And, yeah, it makes it easier when you just can't remember what, you know, what did I call that group of lights again?
+[578.10 --> 578.72]  I can't remember.
+[579.72 --> 588.28]  So at a bit of, I'd say, maybe laziness and at a bit of budget concerns, I've been picking up the Amazon Fire tablets.
+[588.28 --> 594.54]  And I don't really want to invest in a system where I need to reflash these things.
+[594.70 --> 595.78]  It's not that I'm against it.
+[595.80 --> 597.08]  I used to love doing that.
+[597.50 --> 602.26]  It's just kind of, it crosses an effort line for me that I'm willing to put into this kind of device.
+[602.78 --> 604.96]  Beyond that, I'd rather just get like a used iPad.
+[605.52 --> 610.06]  Well, we talked a little bit about flashing lineage on my old Kindle Fire a little while ago.
+[610.38 --> 610.66]  Right.
+[610.74 --> 613.96]  And for me, it's just, it's just not quite worth the effort.
+[614.50 --> 615.98]  The tablets kind of suck already.
+[615.98 --> 621.84]  And so if I have to do all this extra work, it just, it kind of like loses the value for me a little bit.
+[622.04 --> 627.44]  I wanted to see if I could find a nice sweet spot where I could still pick up a Fire tablet for a great price off of Amazon.
+[628.24 --> 635.50]  And then just easily and quickly modify it for my needs, which is mount it to a wall and run Home Assistant dashboard all day.
+[636.00 --> 641.38]  And so a couple of projects that I found made it exactly what I was shooting for that kind of like that sweet spot in the middle.
+[641.78 --> 644.14]  And I picked up a 10 inch Amazon Fire tablet.
+[644.14 --> 648.24]  I opted to go for the ad free one because again, I'm not going to reflash this thing.
+[648.56 --> 657.84]  But if you were going to reflash the thing, you could, you could save a few bucks and you could get the version that comes with ads on the lock screen, which is so obnoxious.
+[658.18 --> 663.12]  In fact, I've bought the no ads version in the past and still received the version that comes with the ad.
+[663.12 --> 666.14]  So I could totally understand if you wanted to reflash it.
+[666.20 --> 667.78]  But I, that wasn't what I wanted to do.
+[668.10 --> 670.66]  I wanted to use this app that I found called Wall Panel.
+[670.90 --> 674.82]  It's an Android application for web-based dashboards like Home Assistant.
+[674.98 --> 676.24]  Like that's what's in a lot of their screenshots.
+[676.98 --> 678.64]  And you could sideload it if you want.
+[678.64 --> 687.58]  But they've also submitted Wall Panel to the Google Play Store and to the Amazon App Store, which means it makes it stupid easy to get it up and going on a Fire tablet.
+[687.86 --> 690.94]  It has really great fast camera motion detection too.
+[691.08 --> 693.82]  So now what I can do is sleep my screen.
+[694.24 --> 698.34]  And then when the front facing camera detects motion, it wakes the screen up.
+[698.46 --> 701.10]  And that's actually surprisingly handy.
+[701.38 --> 704.82]  You approach the tablet and as you're approaching it, the screen just becomes available.
+[705.08 --> 707.18]  And then I have it set to like a three minute sleep window.
+[707.18 --> 713.22]  You can have a pin code option in there to kind of lock the screen out if you don't want to just give anyone access to your dashboard.
+[713.94 --> 727.44]  And with the ease of access and installing this thing and the power options for keeping the screen awake and all that kind of stuff, it gets me 90% of the way there with a stock Amazon Fire tablet.
+[727.76 --> 728.58]  So it's Wall Panel.
+[728.72 --> 730.14]  I'll have a link in the show notes for that.
+[730.84 --> 733.18]  So what if I did want to reflash it or tinker with it?
+[733.38 --> 734.18]  What can I do there?
+[734.62 --> 735.94]  There are a couple of options there.
+[735.94 --> 739.82]  The one that I think I'd recommend like the next step up from Wall Panel.
+[740.38 --> 742.26]  You may have seen this over at the XDA forums.
+[742.36 --> 744.06]  It's called the Amazon Fire Toolbox.
+[744.54 --> 762.08]  And this uses the Android debug bridge to apply tweaks to the Fire tablet from completely reflashing them to just doing things like maybe installing Google Play or removing some of Amazon's annoying software that's on there to just completely replacing the version of Android.
+[762.08 --> 766.52]  If you like the downside is you got to use Windows.
+[766.52 --> 769.42]  And I just don't really have access to a Windows machine.
+[769.50 --> 770.66]  It's a Visual Basic app.
+[771.06 --> 772.84]  They say they're going to work on Linux support.
+[772.84 --> 777.64]  But Datastream33 who kind of hangs out over the XDA forums.
+[777.72 --> 778.98]  He's a senior member over there.
+[779.38 --> 781.12]  It's his project or their project.
+[781.54 --> 783.18]  And they're a Windows user right now.
+[783.24 --> 784.14]  So they're making it for Windows.
+[784.14 --> 788.00]  So it's not really something that I have quick access to.
+[788.12 --> 792.42]  But the idea is you plug your Fire tablet into your Windows box.
+[792.50 --> 793.72]  You load this toolbox up.
+[793.72 --> 806.08]  And then that gives you a GUI with a bunch of options in there that just kind of can go in there and lobotomize the Amazon stuff out of the tablet if you want and give it actual genuine Google Play Store APIs.
+[806.88 --> 808.84]  Who doesn't want to lobotomize a tablet, huh?
+[809.34 --> 812.92]  Well, I mean, have you seen the nag where they put on these things?
+[812.92 --> 826.60]  They want you to buy everything that Amazon makes and they want to turn it into an Alexa and they also want you to turn it into an Audible station and they also want you to turn it into a Prime streaming machine and they put all this stuff all over it.
+[826.68 --> 828.40]  And I just wanted to run one single app.
+[828.88 --> 836.86]  You know, I was worried about this kind of thing because in days past you had to route things and reflash bootloaders and that kind of stuff.
+[836.86 --> 845.54]  And I read a long time ago that warranty claims were refused if people had done modifications like this to these ad-supported devices.
+[845.72 --> 847.36]  Is that still the case now?
+[848.04 --> 857.36]  So the nice thing about the toolbox that we were just talking about from XDA, that's not messing with like the system restore partition on your Fire tablet.
+[857.54 --> 861.26]  So you could go in there and like lobotomize the Amazon stuff out of the image.
+[861.66 --> 866.50]  And then if you needed to, reset it to factory defaults and it just restores it to a stock Fire tablet.
+[866.50 --> 869.74]  So your warranty is good if you just did that before you sent it in.
+[870.10 --> 870.62]  Yeah, that makes sense.
+[870.72 --> 871.96]  I mean, it's just software, isn't it?
+[872.08 --> 878.38]  I mean, unless there's like an intrusion detection in the firmware, I don't see how they'd ever know.
+[878.68 --> 880.08]  Well, yeah, they could do that, I suppose.
+[880.16 --> 881.10]  But thankfully they're not.
+[881.56 --> 885.60]  But that's where wall panel is kind of this nice starting point.
+[885.80 --> 888.98]  And you could just start with that for these on-wall dashboard.
+[889.30 --> 895.64]  This is, I think, such a great way to make home automation more accessible to your family is a visual way for them to control things.
+[895.64 --> 899.96]  And with the Home Assistant dashboard setup, you could make something really appealing to people.
+[900.08 --> 902.22]  And it renders really great on a 10-inch tablet.
+[903.18 --> 907.72]  And wall panel has an option to turn on by default when the tablet boot.
+[907.80 --> 913.78]  So it kind of just launches immediately and kind of papers over all that Amazon stuff.
+[914.02 --> 918.00]  And it really gets you like 90% of the way there super quick.
+[918.60 --> 919.50]  What's the last 10%?
+[919.98 --> 922.26]  I think the last 10% would be replacing the OS.
+[922.26 --> 925.02]  You know, because then you could put something a little more modern on there.
+[925.48 --> 930.74]  Because Amazon's Fire Android OS space is often behind mainline Android.
+[931.24 --> 931.38]  Well, yeah.
+[931.44 --> 941.26]  I mean, I saw today just in the JB Telegram chat that people were talking about the, I think it's like a 12-year-old Kindle is getting internet access revoked or something by Amazon.
+[942.22 --> 943.76]  Turning it into e-waste, essentially.
+[944.34 --> 945.44]  You know, that's a tricky one.
+[945.68 --> 947.48]  The cellular networks eventually get shut down.
+[947.58 --> 950.04]  I think that's things like on the 3G network or something, right?
+[950.04 --> 951.94]  Because it's pretty old, I mean.
+[952.38 --> 953.92]  Yeah, eventually they got to shut down the network.
+[953.92 --> 963.52]  But it really kind of does make you think, like, if you want something to last a really, really long time, you've got to look at ways of self-hosting it.
+[964.16 --> 967.76]  And maybe some devices just aren't the right fit.
+[967.88 --> 972.52]  Although you could argue 12 years is a pretty good value proposition when you consider new Kindles are like $100.
+[972.84 --> 974.60]  Like, back then those Kindles were not that cheap.
+[974.86 --> 976.14]  But new Kindles are a lot cheaper.
+[976.94 --> 977.48]  Well, very good.
+[977.48 --> 986.40]  I think next time there's a Black Friday sale or some kind of Amazon invented Prime Day thing, I might pick up a Fire tablet and just give that a go.
+[986.92 --> 991.80]  The one that I flashed with Lineage a little while ago has been doing perfect duty, actually,
+[991.90 --> 1002.14]  as we've been using one of the Wyze Cam V3s with that Lineage OS 7-inch Fire tablet from half a decade plus ago as our baby monitor.
+[1002.14 --> 1003.90]  And it's been working brilliantly well.
+[1004.20 --> 1009.10]  So you can breathe new life into old dogs with this stuff.
+[1009.76 --> 1019.20]  As part of the episode 50 festivities, I wanted to complete a project that I've been kind of working on in the evenings, off and on over the last six months or so,
+[1019.26 --> 1022.74]  which was a searchable archive of our show notes.
+[1022.74 --> 1048.54]  And huge thanks goes out to the orange one from Discord, who rewrote, I think, something like all but three lines of my code to scrape the fireside website and ingest the HTML and the XML feeds and spit out what eventually turns out to be an MKDocs-based searchable archive of the entire Jupyter broadcasting suite of shows.
+[1048.54 --> 1053.48]  That's so great. And, you know, I feel like he kept those three lines of code in there just to be nice to you.
+[1053.68 --> 1061.60]  But it's so quick and snappy, and it makes it really quick to find stuff that eventually this is going to get integrated into the site itself.
+[1061.74 --> 1068.02]  But for right now, it's just a great way to, like, I know we talked about something. When did we talk about it? Like, it's good for that kind of stuff.
+[1068.02 --> 1072.26]  I can't tell you how many times a week I get pinged with, when did you talk about X?
+[1072.26 --> 1079.04]  Or when did you, you know, great example is the lineage flashing of the seven-inch fire tablet.
+[1079.32 --> 1086.86]  As we were talking just then, I just typed into the search bar, lineage OS, and boom, up came episode 44 of Self Hosted.
+[1087.76 --> 1090.20]  There we go. Job done. So it's already working for me.
+[1090.20 --> 1094.62]  Now, you can find this thing at notes.jupiterbroadcasting.com.
+[1094.90 --> 1103.70]  We've got Coda Radio, Jupyter Extras, Linux Action News, Linux Unplugged, and, of course, this here self-hosted podcast.
+[1104.48 --> 1108.58]  All right. Well, this is the self-hosted show, so you've got to tell us a little bit about how you set it up and what's running.
+[1109.06 --> 1113.96]  Well, one of the coolest things that Orange managed to do was dynamic theming between a different show.
+[1114.06 --> 1118.24]  So I don't know if you're on the site right now, but if you click between the different shows,
+[1118.24 --> 1122.66]  you'll notice the top header changes, so self-hosted is Orange, Coda Radio.
+[1123.16 --> 1125.16]  I do like that. Yeah, that's so cool.
+[1125.42 --> 1126.72]  Linux Action News is Red.
+[1128.52 --> 1134.34]  It's all backed by MKDocs, and he's done a bit of dynamic CSS switching between the different tabs, which is pretty cool.
+[1134.98 --> 1140.34]  But what we're doing is we scrape all of the show information that's on Fireside,
+[1140.40 --> 1146.16]  and we use Fireside as our podcasting publishing platform, and we use that as a source of truth.
+[1146.16 --> 1156.58]  And this Python script then takes that scraped data, uses what's called a Ginger2 template to substitute things like the tags in there,
+[1156.66 --> 1163.92]  the hosts, any of the links that we put in the episodes, that kind of thing, and it spits out a plain markdown file.
+[1164.98 --> 1171.20]  MKDocs then ingests that plain markdown file, and bada-bing, bada-boom, we have an MKDocs site.
+[1171.44 --> 1172.08]  Very nice.
+[1172.08 --> 1177.54]  But we are relying on a small element of non-self-hosted software.
+[1177.70 --> 1183.52]  We're using GitHub Actions, and we're running it through a con job, so at 5 or 6 a.m. every day,
+[1183.64 --> 1185.56]  it just goes and scrapes the JB site.
+[1185.74 --> 1189.38]  So you'll see that these show notes are getting automatically updated.
+[1189.58 --> 1194.06]  This website gets automatically updated every day, so it's never out of date.
+[1194.06 --> 1198.16]  Linode.com slash SSH.
+[1198.24 --> 1202.42]  Go there to get $100 in 60-day credit towards a new account, and you go there to support the show.
+[1202.50 --> 1205.46]  So that's Linode.com slash SSH.
+[1205.82 --> 1209.92]  And yeah, of course, notes.jupiterbroadcasting.com is running on Linode.
+[1210.04 --> 1214.30]  Everything we build that we want the audience to be able to use, we host that on Linode,
+[1214.38 --> 1216.42]  because their infrastructure is killer.
+[1216.96 --> 1218.42]  And the price is great, too.
+[1218.42 --> 1227.20]  In fact, Linode is 30% to 50% less than the other big hyperscalers out there, and they've been around since 2003 doing this.
+[1227.32 --> 1236.34]  So for 18 years, they have remained focused on building out the greatest cloud that you could possibly ever want as a Linux geek.
+[1236.42 --> 1238.00]  I mean, it's like a playground.
+[1238.42 --> 1242.88]  I go up there, and sometimes when I just want to try out a couple of different projects for talking about on the show,
+[1242.98 --> 1246.70]  like, how do you know if something is worth proceeding with?
+[1246.70 --> 1249.54]  Like, this is true for you when you're building out something like you have a project.
+[1249.62 --> 1251.72]  Like, how do you know if this is the stack you want to use?
+[1252.92 --> 1257.70]  Well, I deploy it on Linode, often with some of their one-click deployments, and I'll test it out,
+[1257.82 --> 1260.44]  and I'll run it for a couple of days and see how it works.
+[1260.68 --> 1266.30]  And often, I keep one out of two or three things, and that eventually turns into a show.
+[1266.38 --> 1268.78]  And then we create a project around it, and we end up putting it in production.
+[1269.04 --> 1272.22]  And the entire time, from beginning to end, we're doing it all with Linode,
+[1272.22 --> 1277.40]  because they just make it simple, it's affordable, and it's easy to work with the team, too.
+[1277.60 --> 1282.84]  And then on top of that, they have a really handy API that you can either use directly yourself,
+[1282.92 --> 1288.20]  chromatically, or do like I do and just kind of take the lazy route and use their command line client.
+[1288.80 --> 1293.06]  So I'll do this to, like, pop a file up on their S3-compatible object storage,
+[1293.36 --> 1297.40]  and I can mark it public and generate the URL in, like, three or four seconds.
+[1297.40 --> 1300.64]  And this is awesome when we're trying to get clips ready for a show or something like that,
+[1300.68 --> 1305.82]  or we're collaborating on a project, or recently I sent a big batch of files to somebody,
+[1305.86 --> 1309.00]  and we were going back and forth, like, how are we going to even share this file?
+[1309.42 --> 1312.02]  I'm like, oh, hold on a second here, I'll get you a little zip file with a URL.
+[1312.36 --> 1316.32]  I did that with a video of my daughter the other day that was, like, 170 meg to a parent,
+[1316.48 --> 1317.90]  and Telegram was like, nope.
+[1318.54 --> 1320.74]  So I just used the object storage, and it worked great.
+[1321.24 --> 1325.06]  Yeah, and the command line client is, like, the pro way to get things up there,
+[1325.06 --> 1330.12]  because what I do, because I'm such a nerd, is I have a Uake dropdown terminal
+[1330.12 --> 1335.24]  where it's always, like, in one of the tabs, so it's, like, up, up, change a couple of things, hit enter.
+[1335.60 --> 1336.48]  It's great.
+[1336.86 --> 1340.76]  But on top of that, they've got cloud firewalls, they've got VLAN support,
+[1340.82 --> 1345.24]  they have a really powerful DNS manager, they're beginning to roll out bare metal servers,
+[1345.50 --> 1347.52]  and they also work with infrastructure management.
+[1347.68 --> 1349.78]  So if you want to plug in with Kubernetes and Terraform,
+[1349.88 --> 1353.48]  maybe you want to even just use Linode as part of a multi-cloud strategy.
+[1353.48 --> 1354.78]  They're great for that, too.
+[1354.84 --> 1360.12]  In fact, 66% of companies will save money working with a mix of alternative cloud providers
+[1360.12 --> 1362.78]  instead of just relying on, like, one big hyperscaler.
+[1362.86 --> 1364.58]  So it's worth just looking into that.
+[1365.08 --> 1366.96]  Linode could be part of your multi-cloud strategy.
+[1367.30 --> 1370.02]  And if you ever run into any trouble, you ever need any help,
+[1370.08 --> 1372.44]  they've got the best customer service in the business.
+[1373.14 --> 1376.72]  And when your business is running on Linode, it's nice to know that's available.
+[1377.22 --> 1379.16]  And their support for the community runs deep.
+[1379.28 --> 1382.56]  They're making it possible for our team to get together in Denver.
+[1382.56 --> 1384.48]  They're making the whole road trip possible.
+[1385.28 --> 1385.98]  And that's pretty awesome.
+[1386.06 --> 1389.66]  And not only that, but they're going to be bringing swag and giveaways like raspberry pies
+[1389.66 --> 1392.88]  and all kinds of awesome shirts they've made just for the trip.
+[1393.00 --> 1396.20]  And it's just going to be a whole party made possible by Linode.
+[1396.26 --> 1399.12]  And they're doing that just to have a chance to connect because, like us,
+[1399.50 --> 1400.44]  they miss seeing people.
+[1400.58 --> 1401.26]  It's been a while.
+[1401.68 --> 1404.68]  And Linode has been so enthusiastic about supporting our reunion.
+[1405.78 --> 1407.30]  But there's so many things I could go on about.
+[1407.34 --> 1408.84]  You just got to go check it out for yourself.
+[1408.96 --> 1411.00]  You got to get your hands on it and see it.
+[1411.00 --> 1412.38]  So go use that $100.
+[1413.30 --> 1414.40]  Maybe learn something.
+[1415.62 --> 1416.70]  And support the show.
+[1417.50 --> 1419.70]  Linode.com slash SSH.
+[1419.70 --> 1428.50]  Now, I came across a thread on Reddit a couple of weeks ago that Shaw, who's an ISP in Canada,
+[1428.76 --> 1435.12]  was blocking Plex because it thought it was suspicious, which tingled my spidey sense a little bit.
+[1435.62 --> 1440.04]  Because I often tell people that I share my Plex server with that the ISPs don't care.
+[1440.16 --> 1442.02]  It's all just encrypted traffic.
+[1442.18 --> 1444.46]  They have no idea what is going on, right?
+[1444.46 --> 1446.42]  And so I dug into it a little bit.
+[1446.48 --> 1451.30]  And one of the comments has some really interesting information about how the Plex web app works,
+[1451.36 --> 1453.68]  which I thought might be interesting to share with you all.
+[1454.62 --> 1461.36]  Now, Shaw Protected Browsing uses a service called Zvelo, which happens to flag app.plex.tv.
+[1461.36 --> 1469.06]  And the way that the Plex app works in your web browser is it downloads the code to the browser and then runs it locally.
+[1469.36 --> 1477.40]  So if you can't access or the web URL is blocked by an ad blocker or some kind of safe browsing plugin,
+[1478.48 --> 1481.18]  it just can't download the code and you can't run it.
+[1482.04 --> 1489.80]  And because of this, you know, it could affect things running, you know, a web app on a TV, for example, might suffer the same fate.
+[1489.80 --> 1495.38]  And I just thought it was really interesting that these apps aren't local.
+[1495.66 --> 1501.44]  They're not locally rendered, which is why when Plex update their UI, you don't have to download anything.
+[1501.68 --> 1503.46]  It just automatically happens.
+[1504.90 --> 1509.22]  Plex clients for Android, Android TV, iOS, tvOS, etc.
+[1510.12 --> 1512.84]  aren't affected because they are full versions of the app.
+[1512.84 --> 1524.06]  So if you have a smart TV or a hosted Plex web app.plex.tv, you're probably going to want to find a way to route it around something like Zvelo,
+[1524.18 --> 1527.52]  which is what Shaw uses to avoid this issue.
+[1528.24 --> 1530.20]  It's hard to not be skeptical.
+[1530.64 --> 1531.60]  Safe browsing.
+[1531.78 --> 1535.00]  This just sounds like they're trying to reduce load on their network, doesn't it?
+[1535.02 --> 1538.10]  Or perhaps encourage people to sign up for streaming packages.
+[1538.10 --> 1551.38]  I absolutely find it abhorrent that Verizon or AT&T, they all do it here, have different quality profiles of Netflix videos or YouTube videos.
+[1551.52 --> 1557.26]  And they lock you into certain quality profiles unless you pay them more money.
+[1557.26 --> 1563.52]  This is one of the reasons I decided to set up my PepWave with their Fusion Hub VPN solution,
+[1563.72 --> 1570.82]  because it routes my traffic through a VPN and they can't tell what it is, and so they don't re-encode the video for me.
+[1571.28 --> 1575.46]  Actually, what AT&T does, each provider does a little bit differently.
+[1576.10 --> 1580.04]  And AT&T is particularly frustrating because they just sort of brute force it.
+[1580.04 --> 1586.98]  So that way, the YouTube client and the Netflix client, they just sit there and bang their head against the video streaming service,
+[1587.06 --> 1590.24]  asking for the best quality, and it keeps failing and failing and failing.
+[1590.56 --> 1596.78]  And then when the client finally says, okay, fine, I'll go down to the next lower quality, it tries that, that fails.
+[1596.86 --> 1599.84]  And then when it finally goes down to 480p, then it plays.
+[1599.94 --> 1604.74]  So you just sit there waiting while your carrier is blocking these connections.
+[1604.74 --> 1607.96]  You wait with your little spinner on the screen.
+[1608.14 --> 1609.10]  It's so frustrating.
+[1609.34 --> 1613.88]  And to see Shaw do this for Plex, it really, it stinks.
+[1614.24 --> 1614.98]  It stinks.
+[1615.10 --> 1618.96]  Because the reality is they know what's going on over that Plex port.
+[1619.06 --> 1622.70]  They know it's not some sort of attack or some sort of weird malware.
+[1622.90 --> 1624.26]  They know it's video streaming.
+[1625.10 --> 1629.82]  And my reading of the law is the copyright violation really happens when you download the file.
+[1629.82 --> 1636.32]  I think, I don't know, I could be wrong if anybody wants to let me know in a clear, explain it to me like I'm a five-year-old way,
+[1636.64 --> 1637.92]  cell phone.show slash contact.
+[1638.04 --> 1641.40]  But my understanding is you're not actually violating copyright if you stream it.
+[1642.10 --> 1643.10]  That can't be right.
+[1643.44 --> 1647.50]  But either way, I don't know how Plex scoots around that particular issue.
+[1647.90 --> 1652.20]  But regardless, it's not Shaw's place to enforce copyright law.
+[1652.36 --> 1654.44]  It's just not, or IP law.
+[1654.54 --> 1656.72]  It's just, they should just be passing the bits.
+[1656.72 --> 1661.38]  Yeah, I don't expect my water company to choose which bits of water I get.
+[1663.00 --> 1665.56]  Yeah, although you do want them to keep the bad stuff out of the water.
+[1665.74 --> 1667.34]  So that might be a bad analogy.
+[1668.74 --> 1673.48]  I know, Alex, you are, you are very organized compared to me in your Plex collection.
+[1673.48 --> 1675.98]  Like you have collections for everything.
+[1675.98 --> 1678.42]  You've got nice, consistent album art.
+[1678.58 --> 1684.42]  Like at some point in time, you must have just sat back, had a drink and spent like hours organizing all of your metadata.
+[1684.76 --> 1685.70]  Well, I am now.
+[1685.70 --> 1689.90]  This week I've found possibly my new favorite Plex pick of the year.
+[1690.50 --> 1691.82]  Plex Meta Manager.
+[1692.18 --> 1695.26]  This is a Python script and it is awesome.
+[1695.80 --> 1700.86]  So this thing will go through using the Plex API of your local Plex server.
+[1700.86 --> 1707.98]  It uses the token that you can generate by going to Vue XML and get the little token from up the address bar.
+[1707.98 --> 1718.52]  And what it will do is it will basically match the TMDB ID of the movie against a list of different collections.
+[1718.52 --> 1725.52]  So it's built me in my Plex library, for example, a bunch of different collections based on genres.
+[1725.52 --> 1729.86]  Okay, yes, I already had genre filtering, but this is using Plex's smart search.
+[1730.30 --> 1731.30]  It's just really cool.
+[1731.34 --> 1732.20]  You've got to go check it out.
+[1732.20 --> 1739.60]  I've got now a 90s, a noughties, a tensies, a twenties collection in my Plex library as well.
+[1740.36 --> 1742.62]  It's just really, really cool.
+[1742.62 --> 1746.96]  But what got me looking at this in the first place was my wife and I were browsing through.
+[1747.04 --> 1751.30]  I've got a thousand movies or so on my server and we were just browsing through the other night saying,
+[1751.40 --> 1752.04]  what should we watch?
+[1752.12 --> 1758.16]  And neither of us could come to any kind of agreement about what we should watch.
+[1758.54 --> 1759.62]  I know, it's so true.
+[1759.86 --> 1764.88]  Well, first of all, why don't I have a bunch of collections of stuff that's, you know, recently added?
+[1764.88 --> 1775.10]  And it's one thing that Plex does out the box, but there's no real kind of, you know, trending kind of collection like there is through the Plex Meta Manager,
+[1775.82 --> 1778.00]  like a Netflix or Amazon Prime would give me.
+[1778.20 --> 1783.16]  And with this, I'm able to sort of say, oh, hey, yeah, that new Wonder Woman movie.
+[1783.32 --> 1783.88]  Okay, cool.
+[1783.94 --> 1785.14]  I could go and watch that tonight.
+[1785.88 --> 1787.84]  So that was really the motivation behind it.
+[1787.88 --> 1790.76]  But this script takes a little bit of elbow grease to get set up.
+[1790.76 --> 1794.78]  The documentation is very good, but it's also very verbose.
+[1795.16 --> 1798.16]  So it almost put me off, but I'm very glad it didn't.
+[1798.74 --> 1805.82]  You need to configure a couple of YAML files and then they actually provide a Docker container that you can run the Python script out of,
+[1806.00 --> 1808.04]  which just floats my boat.
+[1808.66 --> 1811.56]  I have it set to run every day through a systemd timer.
+[1812.38 --> 1820.18]  And the main reason that actually we wanted to go into refreshing all the metadata every day was because of the critic ratings that Plex has.
+[1820.18 --> 1833.90]  I noticed that several of the movies that I had, the critics rating and the Ross and Tomatoes rating didn't really seem to line up with what I thought the movie was, like not even a little bit.
+[1833.96 --> 1838.38]  And it turns out that it was just a few thousand votes on those really early scores.
+[1838.38 --> 1843.42]  And so the Plex Meta Manager goes through every day and refreshes things like critic ratings.
+[1843.64 --> 1845.36]  It has a cache, which you can configure.
+[1845.52 --> 1847.22]  And I think I've got mine set to 30 days.
+[1847.56 --> 1851.76]  So it's not going to go and scrape every movie every day.
+[1852.06 --> 1855.90]  But, you know, once a month, I think updating my critic ratings is probably worthwhile.
+[1855.90 --> 1866.06]  So this Python script, you set it up to run through systemd every night, and then it goes out and gets all the updated information, and then it writes it to the Plex database directly?
+[1866.66 --> 1866.92]  Yeah.
+[1867.08 --> 1870.68]  So if you're running Plex in a container, are you running this script in that container?
+[1870.82 --> 1871.82]  How's that working?
+[1872.20 --> 1873.94]  You supply the Plex server URL.
+[1874.22 --> 1879.30]  So in my case, it was just 192.168.port32400.
+[1879.44 --> 1880.56]  So it's talking Plex.
+[1880.64 --> 1882.12]  It's not like crawling the file system.
+[1882.42 --> 1882.64]  No.
+[1883.02 --> 1883.34]  Gotcha.
+[1883.52 --> 1885.46]  And then how does it get access to the database, though?
+[1885.46 --> 1886.24]  Through a token.
+[1886.54 --> 1890.68]  So when you go into your media library, there is a Plex token that you can get.
+[1890.78 --> 1894.20]  You can click on, I think it's Get Info, and then View Raw XML.
+[1895.02 --> 1901.50]  And as part of that XML payload, up in the address bar, there is a 20-character long token.
+[1902.06 --> 1907.68]  You give this script that token, and then it authenticates against the Plex API, and off it goes.
+[1908.20 --> 1910.52]  That is so cool, Alex.
+[1910.52 --> 1915.42]  Man, I love the idea of going out and getting the updated ratings, because I have observed that same exact.
+[1915.46 --> 1920.66]  And I'm really glad you dug into it, because I had wondered, how exactly does that work?
+[1921.14 --> 1924.36]  That is so cool that it goes out there and gets the trending stuff, too.
+[1924.70 --> 1929.66]  I noticed, too, that you came across Movie Match, which is what I actually thought was going to do some of this.
+[1930.12 --> 1932.02]  Yeah, it's like Tinder, this thing.
+[1932.14 --> 1934.68]  Not that I've ever used Tinder, because I've been married for 10 years.
+[1934.92 --> 1936.12]  Now you're more of a grinder guy.
+[1940.36 --> 1941.12]  Oh, man.
+[1942.42 --> 1942.78]  No.
+[1944.26 --> 1944.90]  I'm not.
+[1945.48 --> 1945.92]  Oh, okay.
+[1945.92 --> 1946.00]  Yeah.
+[1946.36 --> 1952.14]  But it is like, it's actually more of like, it's more of matching taste up with a group, right?
+[1952.18 --> 1954.62]  It's more about like, hey, what do we all want to watch together?
+[1955.28 --> 1960.82]  And when, again, going back to that problem, when you've got like a thousand movies in your library, it's harder.
+[1960.82 --> 1973.98]  If a group of us were here in the studio, legitimately, if we were all just hanging out, you, me, and everybody were hanging out on the couch, and we were just flipping through live TV, and like Star Wars was like on one of the cable channels, we would just watch it.
+[1974.34 --> 1975.68]  There wouldn't even really be a debate.
+[1975.80 --> 1976.76]  That's what we would put on.
+[1977.26 --> 1983.96]  But when you actually have to choose, and you want a group of people to decide, it's a real first world problem.
+[1984.36 --> 1985.48]  Mesa likes Star Wars.
+[1985.68 --> 1986.54]  Oh, no.
+[1986.78 --> 1987.58]  Those ones even?
+[1987.58 --> 1990.18]  Yeah, I was a kid when that came out.
+[1990.28 --> 1995.42]  Episode one, I was like nine or ten when that came out.
+[1995.86 --> 2002.76]  And I remember we were on, this is one for the British audience, we were on a Norfolk Broads holiday, and we were in Lowest Off that night.
+[2002.92 --> 2009.18]  And I remember walking down the road with my dad to go to the cinema from the boat to go and watch episode one.
+[2009.44 --> 2011.22]  And it's just one of those things that stuck in my memory.
+[2011.42 --> 2012.08]  Ah, that's great.
+[2012.28 --> 2013.60]  How can you not love pod racing?
+[2013.70 --> 2014.84]  It's just the coolest thing ever.
+[2015.12 --> 2015.86]  Yeah, that's true.
+[2015.86 --> 2017.66]  The pod racing was super awesome.
+[2018.20 --> 2020.10]  Yeah, I mean, I enjoy the Star Wars movies.
+[2020.24 --> 2021.86]  The prequels, not as much.
+[2022.02 --> 2023.20]  I think the writing's horrible.
+[2023.56 --> 2024.92]  But I'm more of a Star Trek guy.
+[2025.20 --> 2028.18]  I've kind of lost track of what's going on these days.
+[2028.78 --> 2037.80]  So speaking of this movie match thing, essentially what you do is you and your partner or your group of friends set up this app to talk to your Plex library.
+[2037.80 --> 2043.66]  And it presents you with a random bunch of movies that you swipe right, swipe left if you like it or don't like it.
+[2043.66 --> 2049.08]  And if you and your group end up with a common set of movies, it will show you at the bottom.
+[2049.18 --> 2052.96]  Here are the three movies that you all thought were worth watching.
+[2053.34 --> 2055.64]  So it just narrows things down for you.
+[2055.98 --> 2058.90]  You could set up like a group chat, like movie night group chat.
+[2058.90 --> 2065.46]  And you drop that link in there a couple of nights before and have everybody go through and swipe right and left.
+[2065.78 --> 2069.70]  And then when it comes time, use the new Plex watch feature and just watch it all together.
+[2070.12 --> 2071.28]  Socially distanced movie night.
+[2071.52 --> 2072.70]  Hey, it could be a thing again.
+[2072.70 --> 2075.66]  And now we have the tools we need.
+[2076.08 --> 2076.92]  This is really cool.
+[2077.04 --> 2080.50]  So we'll have a link in the show notes or you could just Google search for movie match.
+[2080.54 --> 2084.06]  It's just one word, but links will be at self-hosted.show slash 50.
+[2084.74 --> 2088.70]  Now, my final Plex pick for this week is a no spoilers script.
+[2088.70 --> 2094.72]  Have you ever been watching a TV show and seen an episode, three or four episodes ahead in Plex,
+[2094.94 --> 2101.72]  and you see a character whose current storyline doesn't fit with that thumbnail?
+[2102.18 --> 2102.46]  Yes.
+[2102.70 --> 2106.58]  Well, this script will blur out the future episodes you haven't yet watched.
+[2106.98 --> 2107.56]  That's great.
+[2107.78 --> 2112.14]  So it must be going through finding that JPEG and actually like applying a blur to it.
+[2112.76 --> 2113.58]  That's funny.
+[2113.92 --> 2114.88]  That's really funny.
+[2115.26 --> 2118.84]  It will blur out the episodes based on the user who sets it up.
+[2119.02 --> 2123.22]  So, for example, my server, let's say Catherine had her own account, my wife.
+[2123.68 --> 2127.58]  All the episodes I hadn't watched would be blurred even if she'd watched them.
+[2127.80 --> 2130.16]  So it's not perfect, but it's better than nothing.
+[2130.60 --> 2132.42]  Mark my words, Plex will...
+[2132.70 --> 2134.38]  Introduce this feature to the Plex client.
+[2135.06 --> 2137.02]  My prediction right here on self-hosted 50.
+[2137.02 --> 2143.56]  Because Infuse, what I've been raving about recently, which is also a Plex compatible client, does this.
+[2143.60 --> 2144.66]  It's an option in the settings.
+[2145.30 --> 2146.44]  And it's a game changer.
+[2146.50 --> 2148.54]  It's what actually switched it over using Infuse.
+[2148.60 --> 2150.44]  And now I've just stuck for all of the other reasons.
+[2150.44 --> 2154.04]  But it pre-blurs the image and the description.
+[2154.80 --> 2157.20]  Once you've watched it, it unblurs all that stuff.
+[2157.90 --> 2160.14]  And it just goes based on the watch status.
+[2160.14 --> 2161.76]  And there's just one user with Infuse.
+[2162.12 --> 2169.02]  But if you are on an Apple TV platform and you want to use Infuse to watch Plex and would like to do that, it's just in the settings.
+[2169.24 --> 2171.16]  And we love this feature.
+[2171.16 --> 2175.84]  So I've got to imagine this is something Plex is going to implement, too, just because it's so freaking handy.
+[2176.40 --> 2179.12]  Yeah, I'm still butthurt about this NVIDIA Shield update.
+[2179.68 --> 2181.10]  I thought I'd get used to it.
+[2181.14 --> 2182.72]  And I thought I wouldn't care too much.
+[2182.80 --> 2186.64]  But I tell you what, my Shield downstairs doesn't have the update.
+[2186.72 --> 2187.86]  But the one upstairs does.
+[2188.20 --> 2190.74]  And the one upstairs is really beginning to grate on me.
+[2190.84 --> 2193.56]  So I might have to get an Apple TV soon.
+[2193.56 --> 2198.76]  I want to take a moment and thank our friends over to Cloud Guru for their support.
+[2198.96 --> 2201.74]  And I want to mention to you they have a Linux file sharing course.
+[2201.90 --> 2204.20]  It's a deep dive on Linux file sharing.
+[2204.54 --> 2212.08]  It's a standalone course, but it's also part of a learning path intended to prepare you for the LPIC 2 Engineer 202 and 450 exam.
+[2212.56 --> 2216.78]  In this course, they're going to cover the basics and advanced configurations for Samba and NFS,
+[2217.24 --> 2223.40]  including configuring file servers, exporting file shares, user authentication, client configuration, and mount options.
+[2223.80 --> 2225.52]  We'll have a link for that in the show notes.
+[2225.84 --> 2227.36]  Or you can go to cloudguru.com.
+[2228.06 --> 2231.06]  And also, we have cloudfree.shop sponsoring this week's episode.
+[2231.56 --> 2235.08]  You can go to cloudfree.shop to get a pre-flashed TASMOTOR smart plug.
+[2235.46 --> 2238.76]  Use the coupon code self-hosted to get a dollar off per smart plug.
+[2239.26 --> 2242.70]  And of note, the new version 2 smart plug has been released recently.
+[2243.44 --> 2245.82]  And this one's really cool because it features energy monitoring.
+[2245.82 --> 2250.22]  So not only do you have a free and open source firmware on this thing from the factory,
+[2250.22 --> 2257.12]  but I can now also monitor how much power my server is using without needing to tie up my kilowatt, for example.
+[2257.64 --> 2258.10]  Super cool.
+[2258.48 --> 2261.74]  So go to cloudfree.shop and use the coupon code self-hosted.
+[2261.74 --> 2264.84]  Greg writes into the show,
+[2264.92 --> 2266.62]  Chris and the Badger, love the show.
+[2266.68 --> 2271.62]  It inspired me to learn Docker this past April and convert all of my self-hosted services to Docker.
+[2271.62 --> 2275.90]  I built one big Docker Compose that provides the MariahDB for various components,
+[2276.06 --> 2280.36]  plus the Swag and SSL for all my external services.
+[2280.80 --> 2286.04]  And I've moved over to AirSonic Advanced and BookSonic and Ghost as well.
+[2286.04 --> 2287.66]  All tips from the show.
+[2287.74 --> 2288.98]  But here's my question.
+[2290.10 --> 2292.90]  How do I manage updates for the various service images?
+[2293.52 --> 2296.54]  Most of the Compose entries are built with the latest tag.
+[2297.06 --> 2301.94]  Should I move to a specific version and definition and then rebuild it on a regular basis?
+[2303.06 --> 2305.28]  And for in-container security updates,
+[2305.68 --> 2308.58]  how often should I repull the images to keep them up to date?
+[2309.14 --> 2311.88]  Perhaps there is a guide or a white paper on different approaches.
+[2312.60 --> 2314.22]  I think Greg just needs some help, Alex.
+[2314.22 --> 2318.42]  Well, my advice would be straight off the bat,
+[2319.34 --> 2323.34]  don't run latest because it's just a disaster waiting to happen.
+[2323.48 --> 2327.98]  As I found out with my next cloud this week, which broke again.
+[2328.18 --> 2329.14]  No, no, no way.
+[2329.26 --> 2331.66]  Even though I talk about it in the last episode,
+[2331.76 --> 2335.18]  and I've pinned it to a specific version, you know, a major version.
+[2335.36 --> 2338.86]  So 19, 20, 21, something like that.
+[2338.98 --> 2340.80]  But within those certain tags,
+[2340.88 --> 2343.10]  sometimes you've got to watch the developers as well even.
+[2343.10 --> 2346.94]  Because they all just released all the security patches and all the updates
+[2346.94 --> 2350.06]  for the entire lifecycle of that major version.
+[2350.96 --> 2354.72]  So you will get a lot of updates even sometimes when you pin specific versions.
+[2354.96 --> 2359.96]  So the only way to be sure is to go to the Docker Hub page for a specific image
+[2359.96 --> 2362.20]  and look at the list of tags that are available.
+[2362.20 --> 2369.26]  And some providers, some developers offer specific tags to the exact specific version,
+[2369.40 --> 2371.06]  which ties to a specific commit.
+[2371.66 --> 2376.16]  Others, like Nextcloud, offer a stable version of a major version.
+[2376.84 --> 2379.32]  Lots of different ways to do this particular thing.
+[2379.62 --> 2384.52]  But for apps that don't matter, maybe you'll get away with latest.
+[2384.76 --> 2387.20]  You know, things like traffic, for example, is probably a good idea
+[2387.20 --> 2390.40]  to run that on latest because that's public facing.
+[2390.80 --> 2394.38]  So you want the latest, you know, CVEs and things patched in that one.
+[2395.26 --> 2398.58]  But for the rest of them, I would probably steer away from latest
+[2398.58 --> 2402.10]  just because at some point or other, it will bite you.
+[2402.66 --> 2407.66]  Bevan writes in, and he is looking for a security camera system for a vacation house.
+[2407.72 --> 2410.28]  So I think one that he probably isn't intending to be at very often.
+[2410.28 --> 2416.14]  He writes, most of the options seem to need a cloud component in order to operate,
+[2416.68 --> 2420.00]  which is a bit concerning since the systems are not cheap to install.
+[2420.42 --> 2425.24]  I'd be interested to know what you guys use and maybe what other listeners might have installed.
+[2425.48 --> 2425.72]  Cheers.
+[2425.98 --> 2426.58]  Love the show.
+[2427.00 --> 2430.16]  Well, let me just fire up notes.jupiterbroadcasting.com
+[2430.16 --> 2434.64]  and type in blue iris because that's going to be my recommendation.
+[2434.92 --> 2437.34]  We've got a couple of episodes where we've talked about it in the past.
+[2437.34 --> 2441.46]  Episode 43, episode 28, 36.
+[2442.42 --> 2443.94]  Now, we've talked about it quite a few times.
+[2444.64 --> 2449.64]  The too long didn't listen, though, is Blue Iris is a Windows app.
+[2449.82 --> 2454.46]  So you're going to want to have some kind of a system that has a quick sync enabled CPU.
+[2455.12 --> 2460.74]  So something like the HP 290 Slim box, which you can pick up off eBay for about $130
+[2460.74 --> 2462.84]  at the time of recording.
+[2463.20 --> 2467.04]  That has an 8th gen Intel CPU in it, which has quick sync.
+[2467.34 --> 2468.98]  You install Windows on there.
+[2469.30 --> 2469.94]  Yes, I know.
+[2470.06 --> 2470.68]  Sorry, Windows.
+[2471.32 --> 2473.24]  And then Blue Iris on top of that.
+[2473.82 --> 2480.30]  And then what you will need to power the hardware is a PoE switch connected to PoE cameras.
+[2480.64 --> 2485.96]  And you can usually get those for anywhere from $10 or $20 from Alibaba
+[2485.96 --> 2491.02]  all the way up to $300, $400 each if you want to buy a Unify gear.
+[2491.02 --> 2496.22]  What I tend to stick with is the price point of around $50 a camera unless I absolutely
+[2496.22 --> 2497.22]  need 4K.
+[2497.80 --> 2499.62]  And then it's about $100 a camera.
+[2500.30 --> 2502.14]  But it's not terribly expected.
+[2502.22 --> 2503.90]  The cameras are the cheap part, essentially.
+[2504.54 --> 2509.28]  Running Ethernet is going to be something of a consideration because that's how the cameras
+[2509.28 --> 2510.00]  get their power.
+[2510.86 --> 2515.76]  And then also you might want to upgrade a couple of things in the HP box I recommended.
+[2515.76 --> 2520.06]  It comes, I think, the one on eBay with a 500 gig spinning drive, for example.
+[2520.56 --> 2522.22]  So you might want an SSD for that as well.
+[2522.98 --> 2524.62]  But that's a pretty solid setup.
+[2524.72 --> 2527.20]  And there are lots of guides on YouTube on how to set up Blue Iris.
+[2528.00 --> 2532.88]  And recently, they've got some really cool features in there with deep stack to do object
+[2532.88 --> 2534.36]  detection and that kind of stuff.
+[2534.52 --> 2536.42]  So Blue Iris gets my vote.
+[2536.96 --> 2537.02]  Right.
+[2537.08 --> 2540.78]  And those cameras going over Ethernet are going to be a rock solid setup.
+[2540.78 --> 2548.02]  And I think that's really key is a lot of the cloud solutions are all Wi-Fi cameras.
+[2548.26 --> 2550.64]  And Wi-Fi cameras are going to work 90% of the time.
+[2551.48 --> 2554.98]  But wired cameras are going to work 100% until there's like a hardware failure.
+[2555.24 --> 2559.78]  Now with Blue Iris, Alex, because I'm unfamiliar with it, is there a remote viewing component so
+[2559.78 --> 2561.30]  we could pull it up on a mobile device?
+[2561.80 --> 2562.50]  It's so cool.
+[2562.98 --> 2569.98]  There's an app for all the major mobile platforms as well as a web browser, like a web interface.
+[2569.98 --> 2575.92]  So I can just type the URL of my server, which happens to go through my traffic reverse
+[2575.92 --> 2576.28]  proxy.
+[2577.18 --> 2580.98]  And straight away, I'm thrown into a web interface that is HTML5.
+[2581.34 --> 2584.24]  And I can see all six of my cameras, boom, right there.
+[2584.34 --> 2591.58]  So if I hear a noise or the doorbell goes or something like that, I just type in bi.mydomain.com
+[2591.58 --> 2593.90]  and boom, straight in a browser.
+[2594.12 --> 2594.70]  I'm good to go.
+[2595.12 --> 2598.78]  And that's another thing about the local wired systems is those camera feeds are going to
+[2598.78 --> 2599.58]  come up a lot quicker.
+[2599.58 --> 2602.58]  The cloud-based systems are going to have to connect to the service first.
+[2602.88 --> 2606.62]  There's usually somewhere like on a good day, a three-second delay.
+[2606.74 --> 2608.22]  Sometimes it can be a 30-second delay.
+[2608.68 --> 2609.60]  I don't like it.
+[2609.94 --> 2613.60]  Now, I normally would sit here and I'd tell you about my Wyze system.
+[2613.92 --> 2617.88]  I have the WYZE cams that are going into a Shinobi box.
+[2617.88 --> 2623.30]  But I don't love the solution because the cameras are not super reliable.
+[2623.30 --> 2627.84]  And so I would not recommend them for a security system like what you have here.
+[2627.98 --> 2632.90]  I have it for we're off grid somewhere and we come back and somebody's broken into our
+[2632.90 --> 2633.20]  rig.
+[2633.20 --> 2635.58]  I want to have a good shot that I've caught something on camera.
+[2635.70 --> 2637.30]  That's really what I have my system for.
+[2637.62 --> 2642.02]  But I don't know if I would trust it to run 24-7 because they're Wi-Fi cameras.
+[2642.32 --> 2645.08]  They're doing it over RTMP or RTSP.
+[2645.26 --> 2646.88]  It's just not super reliable.
+[2647.50 --> 2650.94]  Now, I've never used the next system I'm about to talk about.
+[2650.98 --> 2652.70]  So I would not normally recommend it.
+[2652.70 --> 2658.18]  However, I have gotten a couple of emails in people have said that if you want a system
+[2658.18 --> 2663.72]  that's kind of like a Midway system, I have heard that the Arlo camera system is good for
+[2663.72 --> 2664.50]  that kind of thing.
+[2664.72 --> 2668.00]  You can get it like on Amazon and like a three to six camera kit.
+[2668.36 --> 2672.24]  And what's kind of different about this is it has a base station unit that the cameras
+[2672.24 --> 2674.06]  connect back to locally on your LAN.
+[2674.28 --> 2675.84]  And that's where the video is stored.
+[2676.50 --> 2679.18]  And so that does seem compelling to me.
+[2679.50 --> 2682.14]  And I guess it has a pretty flexible setup system.
+[2682.14 --> 2688.34]  And you can get a three camera kit for 385 bucks off of Amazon when it's not on sale.
+[2688.96 --> 2693.22]  And I don't know how great it is, but the people who've written into the show seem to
+[2693.22 --> 2693.66]  really like it.
+[2693.70 --> 2695.64]  The cameras seem to work indoors and outdoors.
+[2695.84 --> 2696.66]  Never tested it myself.
+[2696.80 --> 2702.68]  But if I had 385 bucks to burn, I may give this a go one day because I do like the idea
+[2702.68 --> 2704.74]  of making this as much of an appliance as I can.
+[2704.78 --> 2709.04]  And I am not really in a situation to run Ethernet and do PoE.
+[2709.04 --> 2712.82]  Now, I do have a couple of those Wyze cameras plugged into Blue Iris as well.
+[2713.38 --> 2719.30]  One thing of note, though, is that the new V3 cameras don't support the RTSP firmware yet.
+[2719.50 --> 2728.18]  So if you're thinking about getting those cheap $20, $25 Wyze Cam V2 cameras, just be aware
+[2728.18 --> 2729.76]  you'll need to put a custom firmware on there.
+[2729.98 --> 2730.12]  Yeah.
+[2730.12 --> 2731.78]  My advice would be don't do Wyze right now.
+[2732.18 --> 2737.10]  The Wyze 2 is just not fast enough to do the feed reliably.
+[2737.80 --> 2742.34]  And the V3, while it has a faster processor and better optics, doesn't have the firmware
+[2742.34 --> 2743.16]  yet, like you were saying.
+[2743.62 --> 2747.82]  And I would hold off on purchasing a Wyze camera system until then, because what I like
+[2747.82 --> 2750.82]  to do is bring all those feeds back into Shinobi running on my Raspberry Pi.
+[2750.82 --> 2755.34]  But with the V2 Wises, they drop off several times an hour right now.
+[2755.56 --> 2756.70]  It's no good.
+[2756.94 --> 2757.58]  There's gaps.
+[2758.00 --> 2761.60]  And I think the V3s would be a lot better, but you have to wait.
+[2761.80 --> 2762.74]  So I'd say, hold up.
+[2762.78 --> 2765.04]  When we come back on the show and say we've tested it, go for it.
+[2765.04 --> 2768.06]  But in the meantime, if you can, Wired is the way to go.
+[2768.50 --> 2771.90]  And don't forget, as we talked about at the top of the show, we have a big Jupiter
+[2771.90 --> 2776.66]  broadcasting meetup coming up very, very soon, both Salt Lake City and Denver.
+[2776.66 --> 2781.58]  And don't forget to go to jupitergarage.com and grab some self-hosted 50 merch.
+[2782.14 --> 2787.50]  For the next couple of weeks, we're running member pricing on the store to celebrate episode
+[2787.50 --> 2787.96]  50.
+[2788.46 --> 2791.98]  So you got a limited amount of time to get over to jupitergarage.com and pick yourself
+[2791.98 --> 2794.46]  up some stickers or shirts or I don't know.
+[2794.64 --> 2795.76]  There's all kinds of stuff over there.
+[2795.86 --> 2796.36]  I'm not you.
+[2796.78 --> 2797.46]  I don't know what you do.
+[2798.18 --> 2801.34]  And if you want to support the show, you can get a self-hosted.show slash SRE.
+[2801.78 --> 2806.26]  I got a memo the other day that we might be doing a special discount for all original
+[2806.26 --> 2806.80]  merch.
+[2807.12 --> 2807.64]  That's right.
+[2807.74 --> 2809.92]  Crazy self-hosted is giving away prices.
+[2810.14 --> 2811.04]  We're dropping prices.
+[2811.16 --> 2813.24]  We're slashing prices for members only.
+[2813.64 --> 2819.24]  We'll have a discount code that will take a little bit off any original merchandise items.
+[2819.30 --> 2822.96]  And when you go to jupitergarage.com, there's a products drop down menu.
+[2822.98 --> 2827.10]  And if you choose original merch, members are going to get a percentage off all that.
+[2827.18 --> 2829.40]  We'll have details in the members only post show coming up.
+[2830.04 --> 2830.40]  Absolutely.
+[2830.72 --> 2833.88]  Now, for all the ways to go and get in touch with us, you can go to self-hosted.show
+[2833.88 --> 2834.78]  slash contact.
+[2835.14 --> 2837.50]  And you can find me on Twitter at Ironic Badger.
+[2837.92 --> 2839.24]  I'm there too at Chris LAS.
+[2839.50 --> 2843.60]  And this here show for news announcements and whatnots at self-hosted show.
+[2843.88 --> 2844.76]  Thanks for listening, everybody.
+[2845.02 --> 2846.88]  That was a special episode 50.
+[2846.88 --> 2851.18]  You're welcome.
+[2851.22 --> 2855.44]  Bye.
+[2855.50 --> 2856.66]  Bye.
+[2857.74 --> 2858.62]  Bye.
+[2863.94 --> 2864.40]  Bye.
+[2865.04 --> 2865.48]  Bye.
+[2866.28 --> 2866.50]  Bye.
+[2866.86 --> 2866.94]  Bye.
+[2867.20 --> 2868.04]  Bye.
+[2868.04 --> 2868.18]  Bye.
+[2868.24 --> 2868.54]  Bye.
+[2868.56 --> 2868.78]  Bye.
+[2868.88 --> 2868.98]  Bye.
+[2869.34 --> 2869.60]  Bye.
+[2869.60 --> 2870.50]  Bye.
+[2870.66 --> 2871.28]  Bye.
+[2871.28 --> 2871.34]  Bye.
+[2871.34 --> 2871.58]  Bye.
+[2871.60 --> 2871.80]  Bye.
+[2871.86 --> 2872.72]  Bye.
+[2872.96 --> 2873.14]  Bye.
+[2873.14 --> 2873.82]  Bye.
+[2874.02 --> 2874.68]  Bye.
+[2874.68 --> 2875.06]  Bye.
+[2875.14 --> 2876.12]  Bye.
+[2876.12 --> 2876.60]  Bye.

51： Apple's Rotten Scanning _summary.txt

@@ -0,0 +1,77 @@
+• Introduction of Brent and a discussion about his presence on the show
+• Discussion of a favorite beverage, Robinson's squash, an imported British drink
+• Mention of care packages sent by family with British treats and Robinson's squash
+• Conversation about off-grid living and experiences on the road
+• Advertising for CloudGuru.com and its learning resources
+• Questions asked to Brent about his experience using Home Assistant automation system
+• The speaker's wife has had trouble with verbal syntax in the automation system they're using.
+• The speaker thinks that getting familiar with the system through a smaller setup in their studio was helpful for transitioning to the larger RV system.
+• The RV system is more complex, but has advantages like simplicity and categorization of systems.
+• The speaker considers retrofitting their own cabin with similar automation technology after seeing its benefits.
+• The main barrier to self-hosting is setting up a stable and secure server.
+• The Home Assistant Blue device could be an "easy on-ramp" for those new to the system.
+• Big companies rolling out overreaching measures, like Apple's plan to scan iCloud photos, raises concerns about data privacy.
+• Apple announced plans to scan devices for CSAM (Child Sexual Abuse Material) using a new neural processing area in their processors
+• The scanning will occur on-device, checking iCloud Photo Library for matches with the CSAM database
+• Siri search results will be censored if they match CSAM-related content
+• The difference in reported CSAM incidents between Apple (a few hundred per year) and Facebook Messenger (20 million) is noted
+• The effectiveness of CSAM detection on-device is questioned due to limitations in hash-based matching and user ability to turn off iCloud Photo Library
+• Concerns are raised about the potential for expanded surveillance and "slippery slope" implications
+• Apple's decision may be seen as a capitulation to external pressures, such as government requests for backdoors in encryption algorithms
+• Apple's CSAM database and on-device scanning
+• Limitations and benefits of on-device scanning vs cloud service
+• Responsibility of platform owners in detecting child abuse content
+• Comparison with other companies like Facebook and Microsoft
+• Self-hosting as an alternative to avoid content scanning
+• The "de-Google-ification" challenge to reduce reliance on Google services
+• Planning to de-Googleify a device and using an old OnePlus 6 as the test subject
+• Discussing challenges of replacing ROM on Android devices, specifically with Pixel 3
+• Concerns about abandoning Google apps like Jupyter Broadcasting and Google Calendar
+• Mention of Nextcloud as a viable alternative for calendaring and contact syncing
+• Brent's personal experience with de-googling and encouraging others to do the same
+• Difficulty in giving up Google Maps due to its accuracy and reliability
+• Concept of gradual de-Googleification, aiming for 80-90% reduction in reliance on Google services
+• Accepting that it may not be possible to achieve 100% de-Googleification
+• The host proposes a challenge to drop Google Maps and explore alternative mapping services
+• The guest considers trying to reduce his footprint at Google by switching to Apple Maps or other alternatives
+• The guest is hesitant to increase his footprint elsewhere if he drops Google services
+• The host suggests that the goal should be to take control of personal data rather than just switching to another service
+• A sponsor, Linode, is mentioned for cloud computing and hosting services
+• Discussing Linode's features and benefits
+• Using cloud storage for control and security
+• Upgrading to new PyHole version with Docker
+• Troubleshooting issues with PyHole setup
+• Pausing devices' internet access using PyHole
+• Announcing a meetup in Denver next week, sponsored by Linode
+• Blocking ads at the network level to conserve bandwidth
+• Issues with PyHole, specifically pausing internet access for kids
+• Discussion of AdGuard Home and its ability to block individual services or devices
+• Alternative solutions such as sending devices to a dud DNS server or creating a separate Wi-Fi network
+• 1Password's transition to a subscription-only service and potential loss of functionality
+• Discussion about 1Password's decision to switch from native Mac apps to Electron and the resulting backlash from users
+• Comparison between Bitwarden and KeyPass, with the host expressing his preference for Bitwarden due to its simplicity and ease of use
+• Mention of Vault Warden as a self-hosted Bitwarden server and the hosted service that costs $12 a year
+• Personal anecdotes about using password managers and syncing devices
+• Brief mention of cloudfree.shop, a store offering smart plugs with built-in energy monitoring
+• Zigbee devices and smart plug from LocalBytes
+• Cloudfree.shop shipping to UK available at mylocalbytes.com
+• Alternative to WallPanel: Fully Kiosk browser for Home Assistant integration
+• Listener's question on setting up tech infrastructure in a newly purchased apartment
+• Running Cat 7 or Fiber cabling for stable Wi-Fi and Ethernet setup
+• Importance of multiple Wi-Fi access points with Ethernet run to them
+• Listener's story about building their own house and making tech decisions from scratch
+• Similar journey being undertaken by Matt and his family on their YouTube channel "Adventurous Way"
+• Discussing the idea of a "JB commune" and imagining a future community with friends
+• Sharing personal experience retrofitting homes with modern technologies, including Ethernet and Wi-Fi
+• Considering the cost and feasibility of installing cable versus future-proofing with conduit
+• Recommending MicroTik hardware and software for networking and wireless solutions
+• Discussion of mesh network options and cloud connectivity requirements
+• Mechanical keyboards and mention of a podcast called Top Clack
+• Personal experiences with driving in Scotland and watching The Grand Tour episode
+• Podcasting and its influence, with numerous people attending meetups having their own podcasts
+• Linux Unplugged episode 418 discussing WireGuard user interfaces and kernel space implementation
+• Gratitude for self-hosted show members and SREs who support the show
+• The show will be retired in a couple of weeks and might make future special edition appearances.
+• A discount code is being extended for two more weeks.
+• An invitation to attend the Jupiter Broadcasting meetup in Denver was mentioned.
+• The host encouraged listeners to provide feedback through selfhosted.show/contact.

51： Apple's Rotten Scanning _transcript.txt

@@ -0,0 +1,935 @@
+[0.00 --> 5.28]  We're doing the show from Cheyenne, Wyoming, and Brent is here in Lady Joops with me, Alex.
+[5.70 --> 6.22]  Hello, Brent.
+[6.60 --> 7.64]  Hello, guys.
+[7.96 --> 10.40]  I brought him with, you know, he's been with us the whole trip, Alex.
+[10.62 --> 12.22]  We're in for such a treat tonight.
+[12.38 --> 18.60]  I have two of my best friends in the whole world, one of my favorite beverages, and a self-hosted podcast.
+[19.26 --> 21.18]  This is going to be a perfect episode.
+[21.92 --> 22.26]  Wow.
+[22.38 --> 22.90]  Wait a minute, though.
+[22.90 --> 24.46]  What's the favorite beverage?
+[24.62 --> 26.36]  I feel like you've got to give us more information.
+[26.86 --> 28.78]  Well, this particular one is non-alcoholic.
+[28.78 --> 29.80]  It's an import.
+[30.34 --> 30.70]  Okay.
+[30.88 --> 34.16]  So I've gone to a lot of effort for this particular beverage.
+[34.66 --> 36.72]  Import from Canada or somewhere further?
+[37.08 --> 39.84]  The British people in the audience are going to laugh their faces off in a minute.
+[40.06 --> 42.40]  It's Robinson's squash.
+[43.52 --> 44.44]  Do you know what that is?
+[44.78 --> 45.60]  No, I've got to look it up.
+[45.64 --> 46.12]  Tell me about it.
+[46.20 --> 46.44]  Okay.
+[46.64 --> 48.44]  So it's just flavored water, essentially.
+[48.64 --> 53.98]  It's a bit of sugar with apple and blackcurrant flavoring in it.
+[53.98 --> 59.90]  And every six months or so, someone in my family sends me a care package with a few British treats in.
+[60.00 --> 64.32]  So some, you know, British style Kit Kats, because the Kit Kats you have over here are garbage.
+[64.32 --> 68.94]  And then also a few of these Robinson squashed.
+[70.92 --> 74.24]  It's the word squash with an apostrophe in D after the end.
+[74.32 --> 78.02]  These little, you know, water flavoring packets you can get.
+[78.18 --> 80.74]  And I end up with a, you know, a taste of home.
+[80.90 --> 83.12]  It's just a little treat I have every now and again.
+[83.64 --> 84.56]  That does sound kind of nice.
+[85.00 --> 89.20]  We have some things just like that on board today, actually.
+[89.32 --> 91.08]  The kids love to drink it while we're going down the road.
+[91.72 --> 93.72]  We've been off-grid in two, killing it.
+[94.46 --> 103.68]  In fact, in some ways, I think I've been, not in some ways, in every single way, I've enjoyed our off-grid random spots that we've stayed along the way more than any of the campgrounds.
+[104.16 --> 107.14]  Some have been forced and some have been planned, but they've all been good.
+[107.48 --> 110.30]  Yeah, there was a time where we had to pull over for a bit.
+[110.30 --> 114.66]  And, you know, the power system was great, although we were a little short on water.
+[114.82 --> 116.90]  The mobile internet system has been killing it, though.
+[117.32 --> 118.08]  It's been fantastic.
+[118.20 --> 120.82]  We've had connectivity the entire time, everywhere we've went.
+[121.20 --> 128.38]  Sometimes better or worse connectivity, like here in Cheyenne, Wyoming, we have kind of moderate connectivity right now.
+[129.18 --> 135.50]  But even with moderate connectivity, you can still use a Cloud Guru and become a Cloud Guru.
+[135.50 --> 140.72]  Go over to CloudGuru.com, the leader in learning for cloud and Linux and other modern tech skills.
+[140.82 --> 142.62]  Hundreds of courses, thousands of hands-on labs.
+[143.14 --> 146.80]  Get certified, get hired, get learning at a CloudGuru.com.
+[147.28 --> 155.64]  So, Alex, with our special guest in studio, as it were, do you have any questions for our exclusive access to Brent?
+[155.72 --> 158.46]  I mean, when's the last time we've had a chance to sit down and ask him a question?
+[158.76 --> 159.58]  It's been too long.
+[159.58 --> 165.64]  For those of you that don't know, Brent is the host of Brunch with Brent, which you can find over at extras.show.
+[166.12 --> 170.82]  Now, I wanted to ask you, Brent, you spent a few days now in Lady Dupes with Chris and the fam.
+[171.58 --> 180.92]  He often goes on about accessibility of the Home Assistant interface and how he's got these tablets mounted to the wall and how easy it is to use and blah, blah, blah.
+[181.42 --> 187.12]  I was curious as to how you found using someone else's automation system.
+[187.12 --> 194.98]  Well, as you know, I don't have an automation system at home, so I'm pretty fresh when it comes to experiencing these things.
+[195.54 --> 199.44]  However, I will say my experience on day one started actually in the studio.
+[200.10 --> 206.34]  He very kindly set up the exact same tablet system in the studio as he did here in Lady Dupes.
+[206.66 --> 210.54]  So, night one, I slept over there and had to figure it out.
+[210.98 --> 215.04]  He gave me a 37-second tour, but actually that was enough.
+[215.04 --> 223.74]  It had a familiar enough on-off switch interface with very kind labels that were identical to the voice commands.
+[224.46 --> 226.22]  And so, I was able to play a little bit, actually.
+[226.44 --> 235.66]  I could sort of run over there and go see the tablet and what things were named and then use some of the voice commands and, I guess, learn myself.
+[235.66 --> 240.14]  The other thing I did is I got one of those wall mount socket mounts for the HomePod mini.
+[240.46 --> 243.50]  So, it's plugged in and mounted right there at the wall socket.
+[243.70 --> 245.78]  And so, it's in that guest room.
+[246.20 --> 250.96]  So, once you learn the names, you can just ask the HomePod to turn things on and off.
+[250.96 --> 255.20]  I do remember when my mother-in-law came to stay once a couple of years ago now.
+[255.94 --> 259.42]  I was just in the throes of doing Home Assistant, you know, the first few months.
+[259.62 --> 266.06]  So, everything I could possibly put behind automation was behind automation, including, you know, the light switches.
+[266.26 --> 267.72]  The light switches no longer worked.
+[268.42 --> 270.60]  And I just remember hearing through the wall,
+[270.98 --> 274.10]  Hey, Google, turn off the sodding lights!
+[274.10 --> 274.58]  Yeah.
+[277.86 --> 278.80]  Yeah, you got it.
+[279.48 --> 281.14]  Memorizing the names is the hardest part.
+[281.54 --> 285.20]  I mean, my wife's been using the automation system for a couple of years now.
+[285.26 --> 289.14]  She still has some troubles with the verbal syntax.
+[289.52 --> 292.86]  And in part, that's because I've tried all the different assistant tubes.
+[292.96 --> 295.32]  And so, they sometimes have various different syntaxes.
+[295.42 --> 296.92]  But the real system's in the RV.
+[297.10 --> 298.20]  That's like the bigger system.
+[298.30 --> 301.58]  I feel like that system in the studio was really the training.
+[301.58 --> 306.44]  It was like step one to the system in the RV.
+[306.70 --> 310.76]  And so, what was nice about that was that getting here into the RV, it was like,
+[310.82 --> 312.24]  Oh, yeah, you know this tablet thing.
+[312.30 --> 315.84]  It just has a heck of a lot more on the screen.
+[316.30 --> 318.22]  But the same kind of systems apply.
+[318.50 --> 324.90]  And so, what I appreciate, I think, the most about that interface is its simplicity and its categorization.
+[324.90 --> 331.64]  So, Chris has the systems categorized by either living space or what their use is.
+[332.26 --> 337.54]  And so, the first few nights, I would walk all the way back there just to turn the lights on.
+[337.60 --> 339.38]  But these days, it feels a lot easier.
+[339.70 --> 340.64]  Now you know the names.
+[341.22 --> 342.90]  And you can just bark it into the air.
+[344.14 --> 350.14]  Are you tempted at all to retrofit the cabin that you live in with any of this stuff?
+[350.14 --> 352.40]  That's a very good question.
+[352.54 --> 354.10]  So, that hadn't quite hit me yet.
+[354.28 --> 358.50]  But now I'm beginning to realize all of the advantages.
+[359.28 --> 362.30]  So, for instance, Chris has shown me, you know, he gave me the geek tour.
+[362.50 --> 363.88]  And he's given other people the geek tour.
+[363.96 --> 365.08]  So, I've been on it a few times.
+[365.58 --> 371.26]  And there are sensors in various bays on the RV that give temperature.
+[371.26 --> 376.38]  And in my home, I've got these thermometers all over the place.
+[376.52 --> 381.04]  But I've got to actually, you know, go up the stairs into my loft to go check out if the fire is too hot up there or not.
+[381.06 --> 381.78]  Like an animal.
+[382.00 --> 382.46]  I know.
+[382.64 --> 383.42]  Like a caveman.
+[383.88 --> 385.96]  So, yeah, I know.
+[386.32 --> 394.26]  I could see now the two systems in juxtaposition where I could really gain some currency there.
+[394.26 --> 400.82]  Because we've talked a lot about how you, in particular, can dip your toes into more self-hosting stuff.
+[400.90 --> 404.44]  And I feel like you're curious and you want to do this stuff.
+[404.50 --> 409.90]  But you just don't quite know how to break down that first barrier and kind of get going.
+[410.46 --> 416.58]  I think if I had to pick the very first barrier that's keeping me from it the most, it would be the server side.
+[416.58 --> 425.62]  It would be getting in there and creating a server that's stable enough and safe enough that I feel like I'm not getting myself in more trouble than not.
+[425.94 --> 434.72]  This is where I think the Home Assistant Blue or something like it eventually is going to be such an easy on-ramp for a guy like you.
+[434.80 --> 436.48]  Because you know about Home Assistant.
+[436.72 --> 438.74]  Now you've seen my Home Assistant set up.
+[439.36 --> 445.74]  And the fact that there is an official Home Assistant device that runs the whole stack, that's pretty compelling.
+[445.74 --> 449.94]  I don't know if the price point's right yet or if it's quite the right device yet.
+[450.10 --> 452.64]  But I could definitely see that being a good starting spot, though.
+[453.30 --> 455.90]  You know, I think that maybe you guys are on to something.
+[456.16 --> 462.40]  I have at least two very good mentors who can walk me through some of the glitches, if any.
+[462.82 --> 467.22]  But it sounds also like these days, you know, I've been hearing you guys talk about this for years.
+[467.32 --> 469.36]  But it sounds like these days, things are pretty solid.
+[469.78 --> 473.50]  So I feel like for me, maybe now is a nice time to jump in.
+[474.04 --> 475.06]  Yeah, and you could always start small.
+[475.06 --> 480.48]  You'd be surprised, too, how many things Home Assistant might just pick up on a LAN automatically and suggest integrations for.
+[481.08 --> 484.52]  And it's never been a better time to take local stuff seriously.
+[484.70 --> 491.32]  I mean, I don't know if you saw the Apple news that broke over the last week or two about their expanded protections for children.
+[491.58 --> 495.28]  In other words, they're going to scan all of your pictures for kiddie porn, right?
+[495.28 --> 496.88]  And it always starts this way.
+[496.94 --> 510.26]  And I really hate this kind of insidious way that big companies will roll out overreaching, egregious things like this in the name of, you know, child porn.
+[510.34 --> 512.58]  Because who could possibly disagree with child porn?
+[512.58 --> 522.68]  The other thing about those integrations, it feels to me like it is affecting many people to solve the problems of few.
+[523.12 --> 523.62]  Absolutely.
+[523.82 --> 524.72]  I wonder about that.
+[525.18 --> 525.40]  Yeah.
+[525.40 --> 531.76]  I mean, so as Apple put it, our goal is to create technology that empowers people and enriches their lives.
+[531.76 --> 543.26]  We want to help protect children from predators and those who use communication tools to recruit and exploit them and limit the spread of CSAM, you know, child sexual abuse material.
+[543.90 --> 545.42]  Obviously, that's a laudable goal.
+[545.58 --> 549.52]  And we can't legitimately sit here and say that that is not a laudable goal.
+[550.24 --> 553.86]  However, the way in which they're doing it, I have significant issues with.
+[553.86 --> 566.78]  So what they're doing is they're taking every photo that you have on your iPhone or iPad that is linked to an iCloud account and scanning it on your local device.
+[567.28 --> 572.60]  And this entire announcement has been extremely complicated and confusing because they've really announced three things.
+[572.74 --> 578.24]  They've announced iMessage image detection for child accounts in a family plan.
+[578.24 --> 584.54]  They've announced iCloud photo library scanning on your local device.
+[584.54 --> 592.40]  In other words, if you have iCloud photo library turned on locally on your device, it will scan and check for matches in the CSAM database.
+[592.64 --> 599.08]  And then the third thing they've announced is they're also going to start censoring results in Siri search.
+[599.24 --> 604.20]  So if you search for something like child porn and it matches that stuff, Siri is going to block that.
+[604.20 --> 611.22]  And this is all happening using that new neural processing area in the Apple processors that they love to brag so much.
+[611.28 --> 612.32]  It's accelerating this.
+[613.04 --> 616.28]  And I find this to be an extremely, extremely slippery slope.
+[616.76 --> 620.44]  And I know that the other side of the argument is that child harm is real.
+[620.82 --> 629.14]  So one interesting stat, you've probably seen this floating around, is Apple reports a couple of hundred incidents of child porn in iMessage a year.
+[629.60 --> 630.94]  A couple hundred a year.
+[630.94 --> 636.96]  And Facebook Messenger, because they are already using the CSAM scanner, reports 20 million.
+[638.48 --> 639.84]  It's a huge difference.
+[640.50 --> 644.94]  And you've got to figure, people that are using Facebook are probably on iPhones or Android devices.
+[645.60 --> 648.32]  So there's probably a lot of iPhone users.
+[648.46 --> 654.22]  If 20 million Facebook messaging flags have happened, whatever that is, whatever that metric is,
+[654.54 --> 658.80]  there's a good chance that they were using iPhones and that that stuff's on their phone.
+[658.80 --> 663.18]  Now, the thing is, is it's not going to matter if they don't turn on iPhoto library.
+[663.82 --> 670.70]  And if you are a big child porn collector, I wouldn't imagine you're probably using iCloud's photo library feature.
+[670.78 --> 673.72]  You probably wouldn't be auto-uploading your child porn to their server, right?
+[674.14 --> 675.94]  I think you might be surprised, actually.
+[676.08 --> 680.56]  I bet you there's a lot of people out there using technology just for the bare minimum,
+[680.74 --> 684.54]  just to get what they need done and not understanding, like we do, the underlying principles.
+[684.54 --> 686.62]  Yeah, I guess.
+[686.68 --> 688.38]  And I suppose it's so easy to turn that stuff on.
+[688.46 --> 690.06]  You turn on iCloud when you get your phone.
+[690.46 --> 692.16]  You don't realize every picture you're taking.
+[692.36 --> 694.74]  I suppose, especially if you're taking the pictures with the phone.
+[695.36 --> 702.02]  But an important thing to realize is the CSAM detection is only looking for images that are in the database.
+[702.02 --> 709.16]  It's not doing like some sort of flesh recognition algorithm and detecting 80% nakedness on a 10-year-old.
+[709.24 --> 710.38]  Like it's not doing that.
+[710.68 --> 717.56]  It is looking at a hash that has been provided by CSAM, which they then only look for those images.
+[717.56 --> 720.38]  And so it doesn't really feel that effective.
+[720.38 --> 723.80]  If you combine the fact that people can just turn off iCloud Photo Library,
+[724.16 --> 727.88]  and it's only looking for the CSAM photos that exist today,
+[728.78 --> 735.96]  it seems like a limited reach, a limited return for a massive increase in surveillance on people's devices.
+[736.36 --> 741.12]  And Alex, I think it sounds like it bothers you that it's actually happening on device.
+[741.24 --> 744.30]  Like you'd almost be more comfortable if it was happening up in the cloud, it sounds like.
+[744.94 --> 745.54]  I think I would.
+[745.54 --> 753.00]  And for me, this feels like a capitulation to wider pressures that are at play.
+[753.00 --> 760.00]  You know, if you're Apple, you probably get a lot of requests from different governments,
+[760.22 --> 764.98]  different organizations to put back doors into your end-to-end encryption algorithms.
+[765.54 --> 770.12]  And for me, I think this is their way of saying, no, we're not going to do that.
+[770.12 --> 777.76]  But what we are going to do is say we have some protections in place for the stuff that you say is actually bad,
+[777.84 --> 782.50]  as opposed to terrorists or whatever the next excuse is going to be.
+[782.50 --> 788.30]  Right. You say you need a backdoor for child porn, so we are going to build a system that automatically detects it,
+[788.36 --> 790.82]  and then your excuse for a backdoor goes away.
+[791.16 --> 792.08]  It's nullified.
+[792.24 --> 793.58]  And then you have to move on to the next one.
+[794.00 --> 798.66]  But what bothers me most is there was an ad campaign not that long ago that says,
+[798.92 --> 803.66]  what happens on your iPhone stays on your phone as part of their privacy message.
+[803.66 --> 809.28]  This feels to me like it crosses a line because the scanning's happening on the local device.
+[809.78 --> 817.32]  I don't necessarily opt in quite as obviously as I would if, say, my stuff was being uploaded to a remote server.
+[817.88 --> 819.08]  Like Facebook is a good example.
+[819.22 --> 824.40]  If I upload something to Facebook, in my mind, I consider that now public domain,
+[825.14 --> 828.24]  whatever the privacy controls that Facebook say is there.
+[828.68 --> 830.08]  And it was an implicit action as well.
+[830.16 --> 832.14]  You're choosing to upload to Facebook.
+[832.14 --> 837.12]  It's a manual action you're taking where iCloud Photo Library is kind of a built-in default.
+[837.26 --> 840.82]  You have to be an iCloud user, and you can go in there and turn it on and off.
+[840.94 --> 844.48]  But, you know, if you sign up for the whole shebang, you're going to get iCloud Photo,
+[844.70 --> 846.78]  and every photo you take goes in there.
+[847.30 --> 850.56]  Like you said, it's just a very, very slippery slope.
+[850.78 --> 852.90]  This year, it's child pornography.
+[853.12 --> 854.22]  Next year, it's terrorists.
+[854.92 --> 861.18]  In 20 years' time, it's monitoring a social credit score because you said something bad about the president, you know?
+[862.14 --> 862.98]  That's what I worry about.
+[863.06 --> 866.76]  It's also true that these are only the things that they're saying they're scanning for.
+[867.52 --> 869.54]  We don't know about the things they are not saying.
+[869.66 --> 869.92]  Right.
+[869.98 --> 876.02]  And if you go by the docs that Apple has released, they don't even have input in that CSAM database.
+[876.20 --> 878.66]  They're basically just being handed a list of hashes.
+[879.12 --> 880.40]  Here, put this in your database.
+[880.40 --> 884.96]  Now, I have to say, I am actually more comfortable with this being on-device.
+[885.92 --> 890.00]  I think because it limits the scale and scope of something when it's on-device,
+[890.10 --> 893.82]  a big database update or a feature like this is going to have to come through a software update,
+[893.96 --> 898.22]  where if it was a cloud service, they would just push the update, and one day I would be subject to it.
+[898.76 --> 903.72]  So I kind of prefer those aspects, and I think it also does help with the privacy aspect.
+[904.12 --> 906.86]  They're not having to unencrypt everything on iCloud to do this.
+[906.86 --> 912.04]  They're doing it on your device that already has access, and then they're pinging Apple with a,
+[912.18 --> 913.76]  hey, we think we found a match here.
+[914.44 --> 918.18]  Apple then has to have some sort of human interact with that alert.
+[918.38 --> 922.70]  There's various descriptions of what kind of alert they get, and then Apple flags the authorities.
+[923.26 --> 925.36]  And it does seem like they've taken a lot of steps here.
+[925.84 --> 927.66]  They've limited the way they check this.
+[927.74 --> 931.82]  They're looking for specific fingerprints, and then they have this cryptographic signature
+[931.82 --> 935.00]  that they assign to it when they think they have found one, and that's what they send up to Apple.
+[935.00 --> 936.84]  Then it's reviewed by a human.
+[937.06 --> 942.70]  It's happening on your device instead of at cloud, and you can turn it off by turning off iCloud Photo Library.
+[943.30 --> 948.52]  Is this a reasonable compromise if the platform, let's just say for the sake of argument,
+[949.02 --> 954.76]  is really being used for child abuse at some massive scale because of the popularity of the platform?
+[955.22 --> 957.06]  Is this a reasonable thing for them to do?
+[957.28 --> 962.28]  Do they have some responsibility as a platform owner with a billion devices out there
+[962.28 --> 966.06]  to take some action to try to maybe stop something like this?
+[966.58 --> 969.88]  Well, I look at that 20 million figure that you came out with for Facebook,
+[970.68 --> 975.72]  divide that by 365, and that's 55,000 flags a day.
+[975.86 --> 978.98]  Who is reviewing 55,000 flags a day?
+[979.82 --> 983.64]  That's just a crazy amount of signal-to-noise ratio, isn't it?
+[984.00 --> 984.52]  No kidding.
+[985.02 --> 986.88]  Well, and can you imagine when they turn this on,
+[986.88 --> 991.54]  the initial, if this is going to be a thing and it's a real big problem,
+[991.64 --> 996.10]  you would think they're going to have just this massive deluge of alerts,
+[996.34 --> 998.22]  and I just wouldn't want that job.
+[998.70 --> 1004.22]  Well, I've certainly been on the other end of logging overload or alert overload.
+[1004.38 --> 1006.20]  You just stop looking after a while.
+[1006.68 --> 1009.54]  And you know, the other reality is several cloud providers,
+[1009.54 --> 1012.62]  I think many, I don't want to name them off the top of my head,
+[1012.62 --> 1016.40]  but I know Facebook and Microsoft are already doing this scanning.
+[1016.74 --> 1017.82]  They're already doing this.
+[1018.50 --> 1020.24]  Apple was one of sort of the holdouts here.
+[1020.86 --> 1023.62]  So it really comes back to, if you're not comfortable with this,
+[1024.12 --> 1026.64]  you really have to self-host.
+[1026.88 --> 1028.72]  And you have to advocate self-hosting,
+[1028.78 --> 1031.14]  because that's the only way you can avoid this kind of content scanning.
+[1031.46 --> 1034.24]  And if you're worried about the slippery slope of what could be added to this database,
+[1034.90 --> 1037.58]  then I think people should really be, I don't know,
+[1037.58 --> 1042.38]  like when you can self-host, like invest in self-hosting, use it,
+[1042.54 --> 1044.06]  make an audience for it out there.
+[1044.56 --> 1044.64]  Absolutely.
+[1044.92 --> 1046.70]  And on that note, actually,
+[1046.94 --> 1050.20]  I thought we might try doing a new challenge in the show.
+[1051.26 --> 1054.38]  The de-Google-ification challenge.
+[1054.68 --> 1056.76]  I need to come up with a better name than that, don't I?
+[1057.20 --> 1058.12]  Well, I don't know.
+[1058.20 --> 1060.98]  I actually kind of like it because I know what you mean immediately.
+[1061.86 --> 1062.12]  Yeah.
+[1062.30 --> 1067.32]  So the idea is I'm not going to be able to just cold turkey drop Google from my life,
+[1067.32 --> 1071.28]  because I use Gmail and I have done for 15 years or however long.
+[1071.80 --> 1074.08]  I've been using it a long time since the beta anyway.
+[1074.86 --> 1076.30]  I use Google Photos a lot.
+[1076.44 --> 1079.80]  I use Google, you know, it's going to be tricky.
+[1079.90 --> 1081.78]  I'm not going to, I'm not going to pull any punches.
+[1081.92 --> 1082.80]  It's going to be very difficult.
+[1082.80 --> 1085.62]  But the idea is one day a week,
+[1085.94 --> 1088.98]  I am going to go completely cold turkey from Google.
+[1089.16 --> 1090.56]  That's, you know, DuckDuckGo.
+[1091.14 --> 1093.48]  That's, you know, a self-hosted note service,
+[1093.58 --> 1097.02]  a self-hosted photo service, completely no Google Photo backup.
+[1097.02 --> 1098.06]  Et cetera, et cetera.
+[1098.18 --> 1098.70]  No Gmail.
+[1099.68 --> 1101.52]  And no Android.
+[1102.00 --> 1105.02]  Well, technically I'm going to be using Lineage OS.
+[1105.30 --> 1114.04]  And I think the only thing that I will allow in terms of de-Google-ifying is the micro G apps thing through.
+[1114.04 --> 1118.18]  So for the very first iteration of this,
+[1118.36 --> 1120.82]  it'll probably be in episode 53.
+[1121.22 --> 1122.06]  This is 51.
+[1122.32 --> 1125.82]  Just because I'm going to Denver next week to see you two fine gentlemen.
+[1126.38 --> 1129.22]  And I probably won't have time to do the full research on this.
+[1129.30 --> 1131.20]  But I have an old OnePlus 6 in a drawer.
+[1131.54 --> 1136.04]  I'm going to designate that as my de-Google-ify device.
+[1137.08 --> 1137.60]  What do you think?
+[1138.00 --> 1138.30]  Hmm.
+[1138.66 --> 1140.14]  I mean, I love this idea.
+[1140.74 --> 1142.08]  I have an Android device.
+[1142.20 --> 1143.10]  It's a Pixel 3.
+[1143.80 --> 1151.58]  But I've always struggled with replacing the ROM on there because the reason I have it is to kind of know what the Google experience is like.
+[1152.04 --> 1153.20]  But I'd be down for it.
+[1153.32 --> 1154.50]  I'd give it a try.
+[1155.84 --> 1157.82]  I feel like there's – I'm trying to run through my head.
+[1157.82 --> 1167.20]  My biggest area and where I worry this is going to lead to is I use Google apps for Jupyter Broadcasting for like email and calendar and stuff like that.
+[1167.66 --> 1169.76]  And I think it's kind of a decent service.
+[1170.12 --> 1171.02]  I hate to say it.
+[1171.34 --> 1171.82]  Oh, right.
+[1172.04 --> 1172.44]  Calendar.
+[1172.94 --> 1174.50]  Oh, I'd forgotten about calendar.
+[1174.62 --> 1176.02]  I use that all the time.
+[1176.44 --> 1178.24]  Even stupid stuff like contacts.
+[1178.36 --> 1181.42]  You kind of forget that they're just managing my contacts for me on that, you know?
+[1181.82 --> 1182.52]  Oh, gentlemen.
+[1182.70 --> 1184.08]  You guys are so behind the times.
+[1184.38 --> 1185.14]  Oh, what?
+[1185.42 --> 1186.64]  You all in the next cloud over there?
+[1186.64 --> 1190.90]  Well, I ran through this very experiment many years ago.
+[1191.14 --> 1191.70]  I'll have you know.
+[1191.96 --> 1193.94]  Could you sound any more smug right now?
+[1194.48 --> 1201.02]  Well, it's only because you guys are both typically far ahead of me in most other realms.
+[1201.32 --> 1203.68]  He's enjoying this moment too much, Alex.
+[1203.86 --> 1205.50]  He's enjoying this.
+[1206.68 --> 1207.40]  Well, good.
+[1207.44 --> 1208.08]  I want to hear it.
+[1208.32 --> 1209.82]  I did a similar challenge.
+[1210.40 --> 1212.40]  I didn't have anyone else to challenge.
+[1212.66 --> 1213.82]  I just challenged myself.
+[1213.82 --> 1217.94]  And I will say it's been actually a few years now.
+[1218.16 --> 1220.54]  I think two, two and a half, something like that.
+[1221.22 --> 1224.68]  And Nextcloud, I will say, is the underpinning of most of it.
+[1224.96 --> 1229.18]  Most of the hard stuff, which was calendaring and context syncing.
+[1229.68 --> 1233.44]  You know, when it comes to file syncing, I can figure that out in a whole bunch of different ways.
+[1233.44 --> 1238.14]  But I will strongly encourage you both to take it pretty seriously.
+[1238.14 --> 1248.38]  Because on the other side is a fairly liberating feeling to know that you have control of all of your own deeply personal information.
+[1248.68 --> 1249.96]  I mean, something like contacts.
+[1249.96 --> 1262.92]  If you think about the people you know and the sensitive information that's in there, it's a little bit surprising to think about what might happen if that got into someone else's hands that would like to mix up your life a little bit.
+[1263.26 --> 1264.94]  Well, you heard it here first, ladies and gentlemen.
+[1265.14 --> 1267.60]  Brent is our de-googlification referee.
+[1268.10 --> 1268.34]  Yeah.
+[1268.78 --> 1275.20]  He'll be our correspondent in the de-googled universe, reporting live from an alternative universe.
+[1275.20 --> 1278.56]  So the thing is, I mean, there's so many things to this.
+[1278.74 --> 1279.58]  There's Maps.
+[1279.98 --> 1281.96]  There's Google Maps is so priceless.
+[1282.76 --> 1283.12]  Maps.
+[1284.38 --> 1285.12]  Oh, no.
+[1285.36 --> 1285.72]  I know.
+[1286.36 --> 1289.44]  And you could, like, if you're on the iPhone, you could use Apple Maps.
+[1289.70 --> 1290.14]  You could.
+[1290.84 --> 1292.32]  And in the RV, I've got a Garmin.
+[1292.62 --> 1301.86]  But I tell you what, when I get to a new town, and, like, legitimately has happened several times on this road trip, I trust Google Maps to have the most up-to-date information.
+[1302.58 --> 1304.36]  That's going to be really hard for me to kick.
+[1304.36 --> 1305.88]  I really haven't thought this through.
+[1305.96 --> 1307.40]  This is going to be so hard.
+[1307.66 --> 1311.84]  Well, I can give you a few pointers based on what I've gone through.
+[1312.04 --> 1313.32]  Are you not using Google Maps?
+[1313.64 --> 1317.96]  Well, so that's a really good example of, I think, the concept I'm about to explain.
+[1318.12 --> 1318.26]  Okay.
+[1318.62 --> 1326.96]  And so I'll start with saying that I use the exact same concept with my dietary choices.
+[1326.96 --> 1330.60]  So when people say, oh, how do you eat, Brent?
+[1330.68 --> 1338.64]  I say, well, I'm, like, trying my very best to eat as vegan as possible, but that never always works out.
+[1338.64 --> 1349.16]  So what I would say for you both in de-Google-fying is you'll never likely get to 100%, and you need to be okay with that.
+[1349.16 --> 1370.26]  Because if you can do it even 80%, 90%, 95% of the time and only rely on Google in certain instances, maybe when Maps in Google has the only updated information on this new ring road around your city and nobody else does or something like that, then I think you're already making a massive difference in your life.
+[1370.26 --> 1374.44]  And you shouldn't feel bad about that 5% or whatever it may be.
+[1374.82 --> 1374.94]  Amen.
+[1375.30 --> 1376.08]  Yeah, absolutely.
+[1376.34 --> 1381.94]  So the idea behind this challenge is to do exactly what we've just done, you know, pick a service.
+[1381.94 --> 1385.64]  In this case, it was Google as a whole, but let's take Maps as an example.
+[1386.20 --> 1388.94]  Discuss what would be required to drop that service.
+[1389.48 --> 1394.80]  Figure out in the intervening two weeks some options we could use to try and replace it with.
+[1394.80 --> 1401.38]  And then in the following episode, repeat that cycle, pick a new service and report back on how the old one went.
+[1401.80 --> 1405.98]  I mean, I kind of feel like if I was going to do it, I could try Maps while I'm on the road.
+[1406.12 --> 1410.76]  Like, this is an opportunity to try alternative mapping and routing.
+[1410.86 --> 1419.02]  I know there's a few apps I could give a go, so maybe I'll try just, this is going to be crazy, but while I'm on the road trip, I'll try for the next two weeks not to use Google Maps.
+[1419.28 --> 1420.08]  See how that goes.
+[1420.32 --> 1420.94]  Go for it, yeah.
+[1420.94 --> 1423.64]  I have a question about your choices of alternatives.
+[1423.64 --> 1431.26]  Will you try to make them free and open source or just try to be an equivalent replacement?
+[1431.56 --> 1432.54]  What's the name of the show, Brent?
+[1433.92 --> 1438.00]  I'm thinking, like, for mapping, I don't know what would be even equivalent, right?
+[1438.12 --> 1440.38]  So then I think it's, like, not so much equivalent.
+[1440.50 --> 1441.84]  It's about just core functionality.
+[1442.18 --> 1443.20]  There's always MapQuest.
+[1443.50 --> 1447.86]  Yeah, and I feel like switching to Google Search to look things up isn't an alternative that I can accept either.
+[1448.12 --> 1449.52]  So I'll have to give it some thought.
+[1449.62 --> 1450.66]  I will have to give it some thought.
+[1450.66 --> 1458.64]  I'm going to look into a couple of different apps for it, and I'm also going to look into how Apple Maps works and see what the privacy situation is there, because that's also already on my device.
+[1459.06 --> 1460.06]  That's a factor, too.
+[1460.62 --> 1461.52]  It's like you're saying.
+[1461.68 --> 1465.04]  I love your point about you could just reduce your footprint at Google.
+[1465.72 --> 1468.10]  If that's the goal, I think that's something I could get behind.
+[1468.78 --> 1472.76]  But it doesn't necessarily mean I want to increase my footprint somewhere else, right?
+[1472.76 --> 1474.60]  So that's the math I'm going to have to do.
+[1474.92 --> 1481.24]  I don't mind taking two steps forward and one step back with this over the next few years, because that's how long I genuinely think it will take.
+[1481.62 --> 1482.46]  I just worry.
+[1482.58 --> 1492.68]  You know, you see people like Apple who were genuinely supposed to be the privacy-first people rolling out stuff like this, CSAM protections.
+[1492.68 --> 1496.72]  And you just think, yeah, it's never going to get any better.
+[1497.02 --> 1498.56]  It's up to me to take control.
+[1498.70 --> 1500.62]  It's up to me to host this stuff.
+[1500.80 --> 1507.00]  And if I, you know, take my daughter, for example, I think there's one photograph of her on Facebook.
+[1507.32 --> 1509.14]  One in the last six months.
+[1509.34 --> 1511.34]  And I want to keep it as low as that.
+[1511.42 --> 1512.22]  One every six months.
+[1512.32 --> 1516.32]  I mean, why does Facebook need all of that data to mine on her?
+[1516.32 --> 1518.30]  So it's not her choice.
+[1518.38 --> 1520.80]  She can't make that choice yet because she's six months old, you know.
+[1521.04 --> 1525.64]  When she's old enough to make that choice for herself and understand the implications, then fair enough.
+[1525.78 --> 1529.12]  But it's not really my place to share her pictures everywhere, is it?
+[1530.88 --> 1532.96]  Leno.com slash SSH.
+[1533.04 --> 1536.24]  Go there to get $100 in 60-day credit on a new account.
+[1536.32 --> 1538.56]  And you go there to support this here podcast.
+[1539.12 --> 1545.88]  You know, this show is made possible independent content like this by our listeners taking advantage of our sponsor's offer.
+[1545.88 --> 1549.18]  And Linode is one that we can enthusiastically endorse.
+[1549.82 --> 1550.26]  We use it.
+[1550.38 --> 1551.00]  We love it.
+[1551.10 --> 1554.62]  It is powering our live tracker right now as we go down the road.
+[1555.12 --> 1558.56]  Linode started in 2003 as one of the very first companies in cloud computing.
+[1559.08 --> 1560.68]  You know, that was 18 years ago.
+[1561.98 --> 1563.42]  That's like a whole other internet.
+[1563.52 --> 1565.14]  And the entire time, they've stayed competitive.
+[1565.58 --> 1571.54]  They've increased the capabilities, the performance, the smooth slickness of the dashboard.
+[1572.00 --> 1574.08]  Over time, they became their own ISP.
+[1574.08 --> 1576.78]  They've built out to 11 data centers around the world.
+[1577.26 --> 1578.66]  Super crazy fast systems.
+[1578.78 --> 1582.90]  They're always investing in the disk I.O., in the CPUs, in the network connections.
+[1583.02 --> 1587.40]  And now, they've got nearly a million customers and businesses around the globe.
+[1587.52 --> 1590.20]  But yet, Linode's core focus remains.
+[1590.56 --> 1596.50]  They're making cloud computing simple, affordable, and really accessible to all of us.
+[1596.56 --> 1599.76]  If you're a sysadmin that's been doing this for years, or if you've never set up a server,
+[1599.76 --> 1601.64]  you can get started at Linode.
+[1602.06 --> 1607.82]  And I think that focus has really led to the best-in-class dashboard, speed, and more importantly,
+[1608.00 --> 1608.76]  customer service.
+[1608.76 --> 1611.74]  When you do need it, they've got the very best in the business.
+[1612.12 --> 1615.94]  And then, as you start to use Linode, or something you could use that $100 credit to
+[1615.94 --> 1620.58]  check out, is some of their nice features, like the S3-compatible object storage.
+[1621.00 --> 1625.14]  Think about all of the software, like the backup software you have, or different ways you can
+[1625.14 --> 1629.52]  mount file systems that support S3-compatible object storage.
+[1629.80 --> 1632.94]  Start thinking about what you could do with that, not even from a server standpoint, but
+[1632.94 --> 1635.06]  just a cloud storage standpoint that you control.
+[1635.18 --> 1637.00]  You encrypt, and then you upload.
+[1637.40 --> 1638.62]  Plus, they have cloud firewalls.
+[1638.66 --> 1641.00]  VLAN support a very powerful DNS manager.
+[1641.44 --> 1642.76]  Block storage as well.
+[1643.56 --> 1645.50]  I know some of you still prefer the traditional disk.
+[1645.56 --> 1646.12]  They've got that.
+[1646.12 --> 1652.68]  And they also support things like Terraform and Kubernetes, if that's the direction you're
+[1652.68 --> 1652.86]  going.
+[1652.86 --> 1657.56]  They got all of that, and you combine that with the fact that you can get $100 and support
+[1657.56 --> 1658.58]  the self-hosted podcast.
+[1659.24 --> 1662.90]  Well, what kind of maniac wouldn't go to linode.com slash SSH?
+[1663.26 --> 1667.06]  Get that $100 60-day credit on your new account, and you support the show.
+[1667.16 --> 1672.34]  And by the way, if you're coming to our Denver meetup next week, Linode will be there.
+[1672.42 --> 1676.24]  They're going to be giving out prizes, Linode credit, raspberry pies.
+[1676.42 --> 1680.58]  I mean, Linode is going all in on our road trip, and they're helping support it.
+[1680.82 --> 1681.32]  It's great.
+[1681.32 --> 1682.62]  And we'd love to see you at the meetup.
+[1683.02 --> 1688.22]  That's linode.com slash SSH to get $100 in 60-day credit on a new account and to support
+[1688.22 --> 1688.62]  the show.
+[1689.18 --> 1691.24]  Linode.com slash SSH.
+[1692.92 --> 1697.84]  I know you've got this whole road trip prep ritual where you update things a couple of
+[1697.84 --> 1701.66]  nights before in critical systems the week before and all this kind of stuff.
+[1701.66 --> 1703.56]  What did you upgrade this time?
+[1704.08 --> 1705.54]  You are correct.
+[1705.68 --> 1707.40]  And yes, I did do some updates.
+[1709.04 --> 1713.84]  This time, you know what I wanted to do is I wanted to try out the new PyHole because I
+[1713.84 --> 1714.68]  was sniffing around.
+[1715.22 --> 1718.52]  You know, PyHole is one of these things, for those of you who maybe are not familiar, PyHole
+[1718.52 --> 1724.28]  is it's like a nice DNS manager that can block ads, maybe block adult material.
+[1724.28 --> 1726.10]  It has a lot of advantages.
+[1726.10 --> 1730.68]  It's also a DHCP server, so it can hand out addressing and then give your systems on your
+[1730.68 --> 1731.52]  network names.
+[1731.64 --> 1734.06]  And it gives you a beautiful dashboard to see everything on there.
+[1734.14 --> 1735.82]  It just, you know, checks all my boxes.
+[1736.18 --> 1739.88]  And you can run it as a Docker container, which is what I'm doing on a Raspberry Pi.
+[1739.88 --> 1744.78]  And I have version four on there forever, since I talked about it on the show.
+[1744.84 --> 1745.58]  And it's just been running.
+[1745.78 --> 1746.76]  You know, I don't even mess with it.
+[1747.48 --> 1750.06]  But I thought, you know what I want to do on this road trip?
+[1750.12 --> 1754.82]  Because I'm an old man and I go to bed, as Brent could attest, really early.
+[1755.62 --> 1755.98]  Quite.
+[1756.26 --> 1756.54]  Yeah.
+[1756.88 --> 1758.12]  I've had to change my schedule.
+[1758.22 --> 1759.40]  When do you normally go to bed?
+[1759.58 --> 1764.26]  Well, if left to my own devices, I drift deep into the night.
+[1764.28 --> 1764.46]  Yeah.
+[1765.02 --> 1767.38]  But that doesn't serve most people around me.
+[1767.38 --> 1769.88]  Yeah, we're doing like, what, 9, 10 p.m. at the latest?
+[1770.26 --> 1774.54]  And so I don't want the kids up much later than that, browsing the internet.
+[1774.54 --> 1778.54]  Because they can just, you know, get their devices after dad nods off and start browsing
+[1778.54 --> 1779.00]  the web.
+[1779.10 --> 1782.26]  And so we're watching YouTube more likely, let's be honest.
+[1782.66 --> 1784.82]  And so I wanted to be able to pause their devices.
+[1784.82 --> 1786.94]  And I had read that you could do that in PyHole.
+[1787.06 --> 1791.04]  But I logged into my PyHole setup, and I had just done a Docker poll.
+[1791.32 --> 1793.82]  You know, so it should be totally up to date.
+[1794.18 --> 1796.78]  And I log in, and it's several versions behind.
+[1796.78 --> 1802.30]  And I'm looking at my Docker compose file, and I see it's using the latest tag, you know,
+[1802.34 --> 1803.04]  for the latest image.
+[1803.12 --> 1805.18]  And I think, okay, well, why aren't I getting that?
+[1805.20 --> 1808.08]  I'm starting to think maybe there's some compatibility problem.
+[1808.48 --> 1812.24]  So I start looking into it, and it turns out, no, I'm using the wrong tag.
+[1812.58 --> 1816.92]  I was supposed to be using PyHole master, ARM64 buster, because I'm on a buster-based
+[1816.92 --> 1817.18]  Debian.
+[1818.12 --> 1819.90]  And so I set the right tag in there.
+[1819.94 --> 1820.86]  I get the right image.
+[1820.96 --> 1822.42]  I pull down version 5.
+[1822.46 --> 1824.08]  It's like version 5.3 or whatever.
+[1824.24 --> 1824.92]  Working great.
+[1824.92 --> 1826.30]  The upgrade goes super smooth.
+[1826.68 --> 1829.14]  You know, congrats to the PyHole team for making that easy.
+[1829.92 --> 1833.12]  And yet I can't pause the devices like I read, like I should be able to.
+[1833.84 --> 1835.96]  I grouped up the kids' devices by MAC addresses.
+[1836.16 --> 1837.02]  I go into their group.
+[1837.10 --> 1837.82]  I say disable.
+[1838.42 --> 1840.98]  And I think what I'm just doing is disabling the PyHole filtering.
+[1841.08 --> 1842.72]  I don't think I'm disabling their internet access.
+[1843.18 --> 1846.78]  So I went through this whole rigmarole, getting this whole system updated, so that way we'd
+[1846.78 --> 1848.74]  have the latest PyHole while we're going down the road.
+[1848.74 --> 1852.98]  Because my theory is, let's block the ads at the network level, so that way I'm not wasting
+[1852.98 --> 1854.56]  network bandwidth, you know?
+[1854.62 --> 1855.76]  Because we have limited network bandwidth.
+[1855.86 --> 1856.70]  Anything I can do.
+[1857.26 --> 1860.92]  So PyHole, it's working great, but it's not giving me the results I wanted.
+[1861.22 --> 1864.90]  I wanted to be able to pause the kids' internet when I go to bed, and I cannot do it.
+[1864.94 --> 1870.22]  If anybody out there knows a way to do this with PyHole, or a relatively straightforward
+[1870.22 --> 1874.76]  way to just accomplish this that doesn't require a specific router software or whatever,
+[1874.76 --> 1875.70]  I'd love to know.
+[1876.20 --> 1877.66]  Selfhost.show.contact.
+[1878.04 --> 1885.32]  But the upshot is, upgrading from PyHole 4 to PyHole 5.3.whatever, super smooth, totally
+[1885.32 --> 1885.72]  flawless.
+[1886.26 --> 1887.56]  Once I got the right tag in there.
+[1888.22 --> 1889.18]  I have a question.
+[1889.28 --> 1894.44]  Would you be able to tie that into your Home Assistant goodnight kids recipe?
+[1894.88 --> 1895.70]  Oh, I could imagine.
+[1895.92 --> 1899.38]  I do pull in Home Assistant, there is a PyHole integration.
+[1899.38 --> 1907.82]  And so I do pull into Home Assistant the amount of active network clients and some DNS stats
+[1907.82 --> 1908.70]  for the day.
+[1908.98 --> 1913.08]  And I graph them in Home Assistant on the dashboard, just for my own fun.
+[1913.94 --> 1918.32]  And I don't know, but I bet you there is a way you could totally do that, is when I run
+[1918.32 --> 1921.70]  that script, it also would pause their devices.
+[1922.50 --> 1922.60]  Right.
+[1922.76 --> 1923.60]  Have a look in your Telegram.
+[1923.70 --> 1924.62]  I've just sent you a picture.
+[1924.62 --> 1924.74]  Yeah.
+[1925.12 --> 1927.36]  This is of the AdGuard Home interface.
+[1927.86 --> 1932.10]  And just look at all the different services that you can toggle on and toggle off.
+[1932.28 --> 1936.86]  And then also look at the top of this page where it says, select the tags that correspond
+[1936.86 --> 1938.08]  to a specific client.
+[1938.44 --> 1940.92]  You know, the tag being child or whatever it is.
+[1941.38 --> 1942.56]  Doesn't this do what you need?
+[1943.38 --> 1943.78]  Ah.
+[1944.32 --> 1944.74]  Yeah.
+[1944.82 --> 1949.94]  You know, the only thing that's funny thing about it is it felt like this, this approach
+[1949.94 --> 1952.92]  with AdGuard, because I actually gave AdGuard about a 20 minute try.
+[1952.92 --> 1956.72]  It didn't have like, just turn off everything.
+[1957.50 --> 1963.64]  You can go in and block individual services like eBay, Hulu, Discord, Amazon, Instagram,
+[1963.94 --> 1969.66]  Facebook, Telegram, Twitch, YouTube, all which actually would basically do the job, to be
+[1969.66 --> 1970.16]  honest with you.
+[1970.18 --> 1972.90]  If I just turned off YouTube, that did 90% of it.
+[1973.58 --> 1975.86]  But I just want turn off internet access.
+[1976.32 --> 1977.90]  Like, just don't route them.
+[1978.56 --> 1980.60]  Could you send them to a dud DNS server?
+[1981.04 --> 1982.60]  I was wondering about that.
+[1982.60 --> 1988.46]  You know, it would have to be a pretty short DHCP lease that somehow switched around bedtime
+[1988.46 --> 1989.74]  or something like that.
+[1990.34 --> 1990.86]  I don't know.
+[1991.40 --> 1993.34]  Or maybe reboot the Wi-Fi access point.
+[1993.46 --> 1995.74]  Then every client gets a new IP.
+[1995.92 --> 1998.14]  And at that point, they all get ratted to like nowhere.
+[1999.24 --> 2004.86]  I mean, I think the AdGuard solution may be just simpler because if you turn off, it's
+[2004.86 --> 2006.86]  funny that Cloudflare is one of the services in here.
+[2006.94 --> 2011.28]  I mean, if you turn off Cloudflare, you're going to break a lot of the internet right there.
+[2011.28 --> 2014.12]  And then if I turn off YouTube, that's going to do pretty much the rest of it for them.
+[2014.44 --> 2014.50]  Yeah.
+[2014.64 --> 2016.16]  So maybe I'll go back to AdGuard.
+[2016.48 --> 2020.64]  I think I liked the DHCP server setup better in PyHole when I was looking at the two, though.
+[2021.10 --> 2025.72]  One option might just be throw them on a different Wi-Fi network and switch that off.
+[2026.02 --> 2026.94]  Yeah, that's true.
+[2027.04 --> 2028.28]  I could have a kid Wi-Fi network.
+[2028.56 --> 2029.32]  That's the one, Brent.
+[2029.54 --> 2031.52]  The simple solutions are always the best.
+[2031.52 --> 2032.82]  Simplicity, gentlemen.
+[2033.36 --> 2035.88]  You know, I do need another Wi-Fi network in this thing.
+[2036.30 --> 2037.86]  I've got like six or something.
+[2038.34 --> 2038.82]  I don't know.
+[2038.86 --> 2039.38]  It's ridiculous.
+[2039.52 --> 2041.48]  But yeah, that would probably work, huh?
+[2041.80 --> 2045.42]  If you have a better idea, let us know at selfhosted.show slash contact.
+[2045.80 --> 2050.54]  Now, in the meantime, 1Password had been busy this week and released version 8.
+[2051.16 --> 2055.76]  Yeah, version 8 of what I used to think was one of the best password managers out there.
+[2055.76 --> 2062.96]  And they recently released a Linux desktop version and they announced that the backend was written in Rust.
+[2063.04 --> 2065.10]  And I thought, hey, isn't that just fantastic?
+[2065.78 --> 2070.72]  But version 8 is switching to a subscription-only service, Alex.
+[2070.76 --> 2073.40]  And I think there's kind of a big loss in functionality with that.
+[2073.96 --> 2075.98]  $3 a month to manage your passwords.
+[2076.96 --> 2081.74]  Why do we need a password manager to be a subscription service?
+[2081.74 --> 2087.40]  Not only that, why do we need a password manager that can no longer handle local vaults?
+[2088.10 --> 2091.32]  My mind is just blowing out right now.
+[2091.46 --> 2096.70]  When I read this news this week, I just couldn't believe they would make such a dumb move.
+[2097.28 --> 2104.24]  And then I saw that they took a $200 million Series A funding late in 2019 and suddenly all became clear.
+[2104.76 --> 2105.52]  Oh, yeah.
+[2105.60 --> 2107.66]  Okay, that does kind of connect the dots, doesn't it?
+[2107.70 --> 2108.10]  Unfortunately.
+[2108.10 --> 2112.60]  I hate to see it that way, but that's pretty tough not to see.
+[2112.68 --> 2114.44]  And then when you combine the changes they're making.
+[2114.54 --> 2118.10]  So that Linux Electron app they created with the Rust backend.
+[2118.68 --> 2119.10]  Surprise!
+[2119.60 --> 2121.74]  Turns out to be what they're switching everybody to.
+[2121.84 --> 2124.46]  So now the new Mac version is also Electron.
+[2124.60 --> 2133.18]  And the Mac users are pissed because 1Password started as kind of a exclusive to the Apple ecosystem with native applications.
+[2133.18 --> 2135.28]  That was what 1Password was special for.
+[2135.28 --> 2141.00]  And so now to switch over to Electron, the Mac users are just pissed.
+[2141.10 --> 2145.72]  And I don't mean to laugh, but Linux users, we've had to live with that for a while already.
+[2146.40 --> 2148.30]  But it's two whammies at once.
+[2148.98 --> 2154.40]  An Electron swapperoo and the removal of a local vault.
+[2154.80 --> 2159.12]  That's just, well, that's game over right there.
+[2159.12 --> 2164.30]  I have 1Password installed on my machine because I was playing around with it to compare it to Bitwarden.
+[2164.76 --> 2166.40]  And they just disqualified themselves.
+[2166.84 --> 2170.68]  I remember 1Password, I think, was the first password manager I used.
+[2171.20 --> 2174.34]  It must have been, because I was still working at the Apple Store at the time.
+[2174.46 --> 2177.30]  So it was 2013, I want to say.
+[2177.98 --> 2182.40]  And at the time, I thought it was absolutely crazy, the idea of putting all my passwords in one place.
+[2182.40 --> 2188.66]  I thought, how can this possibly be more secure than me remembering the password in my head?
+[2189.24 --> 2190.04]  Yeah, I remember.
+[2190.28 --> 2191.78]  I think I thought that way, too.
+[2192.14 --> 2193.68]  Very early on, I was very skeptical.
+[2194.00 --> 2196.42]  Yeah, but over time, I mean, my approach has matured.
+[2196.48 --> 2198.50]  And everything now lives in my Bitwarden.
+[2198.56 --> 2199.64]  And I do mean everything.
+[2200.00 --> 2201.54]  WireGuard configs live in there.
+[2202.14 --> 2203.34]  A bit of a tangent for a second.
+[2203.34 --> 2212.32]  We had a right old chat this week about encrypted storage vaults on Discord with a couple of the guys on there.
+[2212.38 --> 2215.56]  One was talking about Cryptomator, which I'll talk about in a future episode.
+[2216.06 --> 2219.04]  And another one was talking about Veracrypt.
+[2219.70 --> 2221.82]  And both of those are great fun.
+[2222.18 --> 2225.18]  But honestly, nothing beats the simplicity of Bitwarden for me.
+[2225.30 --> 2227.12]  Just you can store files in there.
+[2227.20 --> 2229.96]  You can do all your two-factor stuff in there and all your passwords.
+[2229.96 --> 2234.00]  I mean, if you know my master password, I've never said it out loud.
+[2235.10 --> 2236.18]  Good for you.
+[2236.32 --> 2236.66]  Well done.
+[2236.86 --> 2239.24]  I mean, you deserve to crack some of my stuff, I guess.
+[2239.86 --> 2243.62]  Bitwarden should totally sponsor this show because I am a big Bitwarden fan now, too.
+[2243.98 --> 2245.50]  They totally won out in my tests.
+[2245.92 --> 2250.64]  And the fact that there's that Rust implementation of the server that's super easy to get up and running, I'm just all about it.
+[2250.68 --> 2251.46]  Have you tried Bitwarden?
+[2251.84 --> 2253.50]  You know, I will admit I haven't.
+[2253.50 --> 2259.46]  I got onto password managers even earlier than Alex, I will admit.
+[2259.46 --> 2259.94]  Wow.
+[2260.90 --> 2263.10]  He's really taking this opportunity, Alex.
+[2263.58 --> 2266.40]  You don't have me on the show that often, so I got to take it all.
+[2266.82 --> 2267.74]  I love it.
+[2267.86 --> 2272.22]  So I landed on a great many years ago onto KeyPass databases.
+[2272.78 --> 2276.16]  And I will say that they are simpler.
+[2277.10 --> 2280.30]  And I have to sync them myself with some other solution.
+[2280.54 --> 2282.38]  However, they've been solid.
+[2282.78 --> 2286.10]  And my father thinks they're his favorite application ever.
+[2286.60 --> 2288.40]  And that says something.
+[2288.40 --> 2294.56]  So everyone I've shown it to has enjoyed their simplicity and hasn't needed to think about it much more than that.
+[2294.70 --> 2300.04]  So I think Bitwarden, if I was getting into it today, would be the perfect solution for me.
+[2300.12 --> 2301.46]  But I don't really have a reason to change.
+[2301.46 --> 2304.48]  KeyPass and KeyPass, was it XC, I think?
+[2304.78 --> 2306.04]  Very popular options.
+[2306.26 --> 2309.30]  But you touched on the reason why I won't consider it.
+[2309.38 --> 2312.26]  And that, for me, is the fact that you have to sync it.
+[2312.26 --> 2316.04]  With Vault Warden, which is a self-hosted Bitwarden server.
+[2316.54 --> 2319.94]  And the hosted service that costs $12 a year.
+[2320.58 --> 2321.92]  I never have to think about it.
+[2322.06 --> 2333.56]  And for passwords, when I have way too many devices in my life, and I have often got more than one phone and a tablet and a laptop and a desktop and a server and wife's phone and blah, blah, blah.
+[2333.56 --> 2335.80]  I just don't need that extra complexity in my life.
+[2335.80 --> 2365.78]  Thank you.
+[2365.80 --> 2371.78]  And you're all familiar with cloudfree.shop at this point.
+[2371.88 --> 2376.28]  You can go over there and use the coupon code self-hosted to get $1 off a smart plug.
+[2376.62 --> 2381.26]  The version 2 smart plugs from CloudFree have just launched with built-in energy monitoring.
+[2381.94 --> 2384.66]  But some good news for the British people in the audience.
+[2385.04 --> 2390.04]  One of our other listeners on the other side of the pond has launched a similar store in England.
+[2390.58 --> 2393.10]  This is at mylocalbytes.com.
+[2393.10 --> 2400.12]  And to start with, he has launched a couple of Zigbee devices as well as a branded smart plug for LocalBytes.
+[2400.12 --> 2403.42]  Again, you can use the coupon code self-hosted to get a pound off that.
+[2404.30 --> 2414.86]  But for all of those of you that have been asking me about cloudfree.shop shipping to the UK, well, here's your answer at mylocalbytes.com.
+[2414.86 --> 2416.24]  Wow, that's so great.
+[2416.30 --> 2418.52]  Now, we have no affiliation with them other than they are listeners.
+[2419.00 --> 2420.60]  But this is incredible.
+[2420.72 --> 2422.72]  They even have an LED light strip thing there.
+[2423.20 --> 2424.06]  What a cool idea.
+[2424.56 --> 2425.36]  What a cool idea.
+[2425.80 --> 2426.80]  Mylocalbytes.com.
+[2427.00 --> 2428.84]  And I love that there's some Zigbee tech in there.
+[2428.90 --> 2429.92]  I've been thinking more and more.
+[2430.02 --> 2431.74]  I think I'm going to quit getting Wi-Fi devices.
+[2431.86 --> 2433.80]  I'm going to go Z-Wave and Zigbee on stuff.
+[2433.80 --> 2439.80]  We got an email in about my usage of WallPanel.
+[2439.90 --> 2440.90]  The Linux trucker writes,
+[2440.98 --> 2443.78]  I was listening to your last episode and heard you talking about WallPanel.
+[2444.12 --> 2446.80]  Although it is great software, I feel there is a better option.
+[2446.80 --> 2455.56]  The Fully Kiosk browser does everything that WallPanel does, including motion detection, auto launch, and will even function with the Home button on Android.
+[2455.94 --> 2459.50]  However, for use with Home Assistant, it takes it a step further.
+[2460.32 --> 2466.58]  Fully Kiosk will connect to MQTT and send battery, temperature, and some of the other information to Home Assistant.
+[2466.96 --> 2471.94]  I'm using this in combination with a smart outlet to cycle the battery in hopes it will last a little bit longer.
+[2473.06 --> 2474.32]  Man, I've been talking about doing that.
+[2474.40 --> 2475.36]  That's awesome.
+[2475.88 --> 2477.26]  Linux trucker goes on to say,
+[2477.36 --> 2481.86]  It also gives you one more device you can use for automations and tinkering in Home Assistant.
+[2482.60 --> 2489.08]  This is a very small $5 fee to unlock all of the features, and I don't mind supporting great software that I use every day.
+[2489.50 --> 2492.92]  Give it a look before you settle for WallPanel, the Linux trucker.
+[2492.92 --> 2495.36]  And we have an anonymous person who wrote in saying,
+[2495.66 --> 2496.28]  Hi, Chris Nellix.
+[2496.40 --> 2500.66]  I recently bought my first apartment, and construction will take about two years.
+[2501.12 --> 2504.56]  My wife is going to focus on the kitchen, the living room, and the bathroom.
+[2504.94 --> 2508.28]  Whilst what I'm thinking about are the tech parts of the project.
+[2508.56 --> 2509.04]  Of course.
+[2509.20 --> 2513.02]  I have many things I'm wondering about, and I'm not entirely sure what to prioritize.
+[2513.74 --> 2518.52]  I mean, laying cables and other electrical work is probably going to be one of the more important things,
+[2518.52 --> 2524.32]  but I'm already wondering, for example, whether PoE is the right tech or not.
+[2525.00 --> 2527.72]  A totally different topic is IoT and home appliances.
+[2528.06 --> 2532.82]  You can buy washing machines and ovens and all sorts of things with Wi-Fi built in these days,
+[2533.02 --> 2538.40]  but some of this stuff is going to be in a basement where Wi-Fi might not be the best choice.
+[2539.10 --> 2541.76]  I am hoping that there is some compromise for all this.
+[2542.64 --> 2543.40]  Can you help me?
+[2543.40 --> 2548.38]  This is an opportunity because he is so early in the stage of planning.
+[2548.52 --> 2550.56]  He can run Cat 7.
+[2550.76 --> 2552.82]  He could run Fiber if he wanted to.
+[2552.94 --> 2554.94]  I mean, he could really go all out.
+[2555.06 --> 2558.28]  And he could also run Ethernet to Wi-Fi access points.
+[2558.84 --> 2561.34]  This is how you get your Wi-Fi rock solid, by the way,
+[2561.42 --> 2564.84]  is you have multiple Wi-Fi access points that have Ethernet run to them.
+[2565.02 --> 2568.66]  And that stuff just works nearly like Ethernet.
+[2568.66 --> 2572.54]  I won't say like Ethernet because nothing works like Ethernet, but it's pretty close.
+[2573.08 --> 2579.84]  And if you're in this, man, if you're in this stage right now, Anonymous, you are in such a great position.
+[2580.10 --> 2584.50]  I mean, imagine, Alex, if you could have been two years before your house was even finished building.
+[2584.70 --> 2588.42]  Like, oh, what a great, so many choices, but what a great position to be in.
+[2588.80 --> 2591.90]  Well, it's the ultimate conclusion of being a self-hoster, isn't it?
+[2591.90 --> 2593.06]  It's to be a self-builder.
+[2593.06 --> 2598.22]  So I think in my life plan at some point, it might be 10 years away,
+[2598.38 --> 2602.88]  but I really want to build my own house and do all of this stuff and make all these decisions.
+[2603.70 --> 2610.12]  And to that point, another one of our listeners is embarking on a similar journey himself up in Vermont.
+[2610.74 --> 2613.78]  His name is Matt, and they have a YouTube channel called Adventurous Way.
+[2613.88 --> 2615.16]  There'll be a link to it in the show notes.
+[2615.54 --> 2619.52]  They've literally only just closed on the 40-acre plot of land up in Vermont.
+[2619.52 --> 2621.34]  And currently, Chris, they live in an RV.
+[2621.34 --> 2626.94]  So, you know, there's a lot of stuff, a lot of synergy between his approach to stuff and yours right now.
+[2627.64 --> 2629.58]  So I'm really curious to see what they're doing.
+[2629.66 --> 2633.66]  I've just watched a video tonight where they're cutting back all the trees on the land, for example.
+[2633.66 --> 2638.02]  So they're doing it all themselves pretty much right from the very beginning.
+[2638.20 --> 2640.84]  And man, does that fill me with some excitement.
+[2640.98 --> 2644.12]  I think in the future, you've got to do it.
+[2644.12 --> 2644.80]  I've just got to do it.
+[2644.96 --> 2645.56]  I feel the same way.
+[2645.62 --> 2646.74]  I feel exactly the same way.
+[2646.76 --> 2648.22]  So I'm definitely going to check out their channel.
+[2648.22 --> 2651.74]  I could see parking Lady Joupes on some land and building from there.
+[2652.06 --> 2655.34]  I think that'd be the ultimate final destination for Lady Joupes if I could.
+[2655.82 --> 2657.70]  It'd be some piece of land that we park her on.
+[2657.94 --> 2661.02]  I can imagine a JB commune right now.
+[2661.14 --> 2663.64]  Brent in his little house in the corner.
+[2664.10 --> 2664.54]  Totally.
+[2665.32 --> 2665.76]  Yes.
+[2666.66 --> 2666.92]  Yeah.
+[2667.12 --> 2667.32]  Yeah.
+[2667.48 --> 2668.18]  You'd be there.
+[2668.26 --> 2669.04]  Wes would be there.
+[2669.12 --> 2669.74]  It'd be great.
+[2670.08 --> 2670.58]  Yeah, man.
+[2670.58 --> 2677.30]  You know, I've retrofitted many homes in the last few decades with the technologies of the day.
+[2677.30 --> 2688.06]  And I think part of my advice would be to look at the cost of laying a bunch of cable versus what you think the future might bring in the next even five years.
+[2688.06 --> 2694.98]  Because some of the homes that I've lived in that have been retrofitted with Ethernet to every room.
+[2695.14 --> 2697.78]  Actually, my parents' home right now, we didn't do this.
+[2697.88 --> 2700.12]  But there's Ethernet run to every toilet.
+[2700.96 --> 2704.92]  You know, just in case you need the best speeds possible.
+[2704.92 --> 2707.64]  I don't know why, but I love that idea, actually.
+[2707.78 --> 2709.28]  I think I see nothing wrong with that.
+[2709.64 --> 2710.38]  That seems reasonable.
+[2711.92 --> 2713.98]  But it turns out they never get used.
+[2714.54 --> 2723.14]  And nothing ever gets plugged in because the Wi-Fi, even in the basement, is good enough for most of the activities that ever happen in that home.
+[2723.28 --> 2730.82]  So I would use some imagination and think about where Wi-Fi is going to be in the next, you know, five to ten years and think about if the cost is worth it.
+[2730.82 --> 2734.94]  I know there are people tapping in their keyboards furiously right now.
+[2735.14 --> 2735.92]  Run Conduit.
+[2736.68 --> 2739.62]  And I think that's probably the best future-proof thing you can do.
+[2739.80 --> 2740.00]  Right.
+[2740.06 --> 2745.36]  Is to make sure there's plenty of Conduit so you can upgrade the cables later without having to fish through walls.
+[2745.94 --> 2748.02]  Jonas writes in along the same line.
+[2748.14 --> 2750.16]  He says, I know you guys talk about networking a lot.
+[2750.74 --> 2752.24]  We're renovating our house.
+[2752.24 --> 2755.12]  We ran Cat7 cables almost to every room.
+[2755.26 --> 2759.38]  But we've discovered, to Brent's point, we're still using Wi-Fi a ton.
+[2759.82 --> 2764.08]  And so now I'm looking at what are the right APs and switches to use here.
+[2764.36 --> 2768.92]  I heard you guys mention recently that you don't think you'd recommend Unify gear anymore.
+[2769.32 --> 2770.30]  So now I'm kind of stuck.
+[2770.38 --> 2771.54]  Do I go with cheap stuff?
+[2771.62 --> 2772.44]  Do I do unmanaged?
+[2772.50 --> 2773.58]  Do I do managed switches?
+[2774.12 --> 2778.80]  You know, I'm looking for stuff in the range of maybe $1,000, somewhere in there.
+[2779.18 --> 2781.10]  Slightly professional gear, but not too crazy.
+[2781.10 --> 2782.70]  And he wants to know if we have any recommendations.
+[2783.26 --> 2784.44]  This is a good point.
+[2784.50 --> 2787.08]  Like, what do you do if you want really great Wi-Fi right now?
+[2787.36 --> 2794.86]  I mean, the reality of the situation is I bought the Unify access point I'm looking at right now from my desk in 2015.
+[2795.12 --> 2799.78]  And it has just done the job extremely well since then.
+[2800.02 --> 2805.30]  Despite all of Unify's wackiness with their policies over the last year or two,
+[2805.30 --> 2811.10]  the hardware and the performance of what I put in has just been great.
+[2811.44 --> 2813.58]  I can't really fault the actual device.
+[2813.94 --> 2817.40]  So with regards to would I purchase it again?
+[2817.86 --> 2819.76]  I'm already in the Unify ecosystem.
+[2820.16 --> 2822.72]  The pragmatist in me is going, yes, I probably would.
+[2822.76 --> 2825.10]  If I needed a third access point in this house, for example,
+[2825.34 --> 2828.52]  just to make sure it all meshed and talked together properly,
+[2829.10 --> 2830.50]  I'd probably just buy another one.
+[2830.50 --> 2835.90]  I know that TP-Link makes some good devices, and Jim Salter's written about those on Ars Technica a little bit.
+[2836.50 --> 2841.46]  There are lots of people over at smallnetbuilder.com that regularly review this stuff.
+[2841.54 --> 2847.10]  So if you're looking at what the best mesh system is or the best Ethernet backhaul system is,
+[2847.36 --> 2850.52]  that's where I'd go for all that advice rather than listening to what I know.
+[2851.46 --> 2855.10]  Now, I won't pretend to be an expert, but I do know some people who are.
+[2855.10 --> 2866.10]  And I will notably say my older brother, Chris, he very, very, very strongly recommends the MicroTik hardware and software in this area.
+[2866.58 --> 2876.16]  He's explored a bunch of it, and he has been very happy over many years with just how powerful their software is,
+[2876.26 --> 2878.68]  but also how it can be simple if you need it to be.
+[2879.08 --> 2884.82]  And the software that's available is their professional software that gets sent to all of their devices.
+[2884.82 --> 2888.16]  So even if you buy their low-end hardware, you get the same software.
+[2888.38 --> 2889.92]  So I would recommend looking into that.
+[2890.06 --> 2895.98]  I can't make any specific recommendations, but when I asked him, that's what he told me.
+[2896.16 --> 2897.34]  So passing that along.
+[2897.98 --> 2899.70]  This is an area I'd love to hear what people are using.
+[2899.90 --> 2903.78]  What are you actually using out there, and how has it worked for you?
+[2903.96 --> 2907.02]  Because I'm also trying to find something else.
+[2907.02 --> 2916.38]  And there's so many mesh options out there, but I think all of them, if I'm not mistaken, require cloud connectivity or some sort of cloud account.
+[2917.04 --> 2918.30]  And I just don't want any of that.
+[2919.52 --> 2923.70]  Unify, I feel like I've already made that concession once before for the stuff we have in the studio.
+[2923.96 --> 2924.42]  So, okay.
+[2924.98 --> 2926.36]  That's already a concession I've made.
+[2926.48 --> 2927.64]  But I'd love some tips.
+[2928.10 --> 2930.44]  And if you're sticking with Unify, I'd love to know why, too.
+[2930.96 --> 2932.48]  Selfhosted.show slash contact.
+[2932.48 --> 2936.60]  And did you see that The Grand Tour aired an episode this week in Scotland?
+[2937.18 --> 2938.42]  We watched it on the road, actually.
+[2938.88 --> 2941.50]  As a family, we all sat down and watched it and had a great time.
+[2941.56 --> 2943.64]  It was more of like a classic episode, I felt, Alex.
+[2943.66 --> 2944.64]  Did you get that sense?
+[2944.96 --> 2950.90]  Yeah, for my stag do, actually, a buddy of mine and my dad, we rented three cars.
+[2951.08 --> 2955.44]  And we did our own mini Top Gear road trip from Edinburgh, actually.
+[2955.48 --> 2957.06]  We started in Edinburgh and finished in Edinburgh.
+[2957.06 --> 2966.12]  But in the intervening three or four days, we went up to Inverness, drove down the side of Loch Ness, out to the Isle of Skye, and then back through the Trossax.
+[2966.26 --> 2972.56]  And, oh, man, I tell you what, Scotland has some of the best driving roads, not cliche, in the world.
+[2972.76 --> 2974.38]  It was just a phenomenal trip.
+[2974.72 --> 2983.92]  And to watch that episode feeling as homesick as I am at the moment, you know, dude, it was just so perfectly timed.
+[2984.48 --> 2985.78]  Yeah, they really made it beautiful, too.
+[2985.78 --> 2988.34]  So, yeah, those had to be some of the same roads, right?
+[2988.48 --> 2989.58]  Some of them were, yeah.
+[2989.82 --> 2999.62]  And I'll tell you what brought me onto this topic was I've been looking at mechanical keyboards lately, and I came across a podcast named Top Clack, you know, like Top Gear.
+[2999.92 --> 3001.00]  I just thought that was fun.
+[3001.38 --> 3003.82]  TopClack.com if you're a MEC keyboard enthusiast.
+[3004.20 --> 3005.08]  Oh, my goodness.
+[3005.22 --> 3006.12]  There is a podcast.
+[3006.42 --> 3007.04]  Are you kidding me?
+[3007.12 --> 3007.88]  Of course there is.
+[3007.96 --> 3008.84]  Why am I surprised at all?
+[3009.14 --> 3010.08]  Why am I surprised by that?
+[3010.10 --> 3011.10]  I shouldn't be surprised by that.
+[3011.20 --> 3013.24]  Almost everyone we've met on this trip has had a podcast.
+[3013.70 --> 3014.64]  That's true, actually.
+[3014.64 --> 3019.28]  I was listening to your podcasting adventures about concrete in Idaho, so.
+[3019.68 --> 3019.90]  Yeah.
+[3021.00 --> 3027.44]  We did a couple of micro meetups, and we had a group of five at one of them, and literally every single person there had a podcast.
+[3027.84 --> 3031.80]  Then we did the Salt Lake City meetup, and there was a handful of people there that had a podcast.
+[3032.30 --> 3033.72]  It's the influence you both had.
+[3034.92 --> 3035.76]  I don't know.
+[3036.22 --> 3037.56]  I don't know, but it was pretty crazy.
+[3037.56 --> 3046.46]  And Brent joined you for episode 418 of Linux Unplugged, where there was an absolutely excellent rundown of WireGuard user interfaces.
+[3046.98 --> 3052.26]  Yeah, and not only the tools to manage WireGuard, but big news for people that want to use WireGuard on Windows.
+[3052.48 --> 3054.64]  There is an alternative to that user space implementation.
+[3054.92 --> 3061.80]  There is now a kernel space implementation, and the performance difference is huge.
+[3061.80 --> 3070.08]  So Jim Salter from Ars Technica and Two and a Half Admins joined us to talk about that on Unplugged 418 at linuxunplugged.com slash 418.
+[3070.44 --> 3072.94]  That's huge with a Y at the beginning, by the way.
+[3073.06 --> 3078.80]  Yeah, that's going to be a big deal for people that want to have interconnected Windows and Linux machines or just Windows to Windows machines.
+[3079.34 --> 3080.58]  And to be able to use WireGuard, too.
+[3080.58 --> 3087.68]  You feel like this is probably going to take WireGuard up to the next level in the enterprise, and you're going to see adoption now just across the board once they get this code done.
+[3087.74 --> 3088.50]  It's early days.
+[3089.06 --> 3091.52]  It's still experimental, and Jim goes through all the details.
+[3092.04 --> 3100.46]  Also, we want to say a special thank you to our members who support this show, our site reliability engineers who sign up at selfhosted.show slash SRE.
+[3101.02 --> 3103.14]  You are very special to us in my heart.
+[3103.38 --> 3103.98]  Remember that?
+[3104.06 --> 3105.06]  You are in my heart right now.
+[3105.06 --> 3110.14]  And I say thank you because, you know, as we're out here meeting people and we're doing a road trip like this and all of it.
+[3110.24 --> 3114.90]  Oh, and we're also, this is the other big part, is we're almost at a year now of being independent again.
+[3114.90 --> 3119.04]  And all of this stuff about how critical our members have been and all that has just been on my mind.
+[3119.16 --> 3120.02]  So thank you very much.
+[3120.06 --> 3122.86]  And if you'd like to support the show, selfhosted.show slash SRE.
+[3123.54 --> 3131.24]  And don't forget, if you're an SRE to listen to the post show, there's going to be an exclusive discount code in there for the merch that we launched last episode.
+[3131.74 --> 3133.96]  The Chris and the Badger t-shirts are flying off the shelves.
+[3133.96 --> 3140.80]  And just to make sure that everybody that wants one gets one, we're going to keep that up for another couple of weeks and then we're going to retire it.
+[3141.22 --> 3145.22]  And then after that, it might make some future special edition appearances.
+[3145.46 --> 3145.90]  Who knows?
+[3146.04 --> 3152.56]  But if you want one, make sure you go over there and pick one up now because who knows when it will ever come back.
+[3152.64 --> 3155.60]  So we're going to extend that discount code for two more weeks.
+[3156.12 --> 3160.16]  And come say hi to Chris, Brent and myself in Denver at the meetup.
+[3160.26 --> 3162.76]  Go to meetup.com slash Jupiter Broadcasting.
+[3162.76 --> 3165.42]  And I've mentioned a couple of times, it matters a lot.
+[3165.52 --> 3167.72]  Your feedback, selfhosted.show slash contact.
+[3167.92 --> 3169.36]  That's the place to get in touch with us.
+[3169.74 --> 3171.06]  You can follow me on Twitter.
+[3171.16 --> 3172.36]  I'm at Chris LAS.
+[3172.60 --> 3174.10]  And I'm there at Ironic Badger.
+[3174.24 --> 3177.76]  And this here show is there at selfhosted.show.
+[3178.04 --> 3180.48]  And I want to extend a big thanks to everybody for listening.
+[3180.80 --> 3182.94]  That was selfhosted.show slash 51.
+[3182.94 --> 3187.54]  See you next time.
+[3187.54 --> 3188.44]  I'll see you next time.
+[3188.44 --> 3190.92]  Be back.
+[3195.78 --> 3195.82]  Bye.
+[3195.82 --> 3196.40]  Bye.
+[3196.40 --> 3196.56]  Bye.
+[3196.56 --> 3196.94]  Bye.
+[3196.94 --> 3197.42]  Bye.
+[3197.42 --> 3197.72]  Bye.
+[3197.72 --> 3197.98]  Bye.
+[3197.98 --> 3199.16]  Bye.
+[3199.40 --> 3199.56]  Bye.
+[3199.56 --> 3199.66]  Bye.
+[3199.66 --> 3199.86]  Bye.
+[3199.86 --> 3199.88]  Bye.
+[3200.06 --> 3200.18]  Bye.
+[3200.18 --> 3201.72]  Bye.
+[3201.72 --> 3202.26]  Bye.
+[3202.26 --> 3202.68]  Bye.
+[3202.68 --> 3203.28]  Bye.
+[3203.28 --> 3204.34]  Bye.
+[3204.34 --> 3204.76]  Bye-bye.
+[3204.78 --> 3205.42]  Bye.
+[3205.42 --> 3207.42]  Bye-bye.
+[3207.42 --> 3207.62]  Bye.
+[3207.64 --> 3208.48]  Bye.
+[3208.76 --> 3209.82]  Bye.
+[3209.82 --> 3210.18]  Bye.
+[3210.18 --> 3210.66]  Bye.
+[3210.66 --> 3210.98]  Bye-bye.
+[3210.98 --> 3211.06]  Bye.
+[3211.06 --> 3211.10]  Bye.
+[3211.18 --> 3211.70]  Bye.
+[3211.70 --> 3212.06]  Bye.

52： Navigating DeGoogling _summary.txt

@@ -0,0 +1,99 @@
+• Discussion of the host's de-Googling experience and its challenges
+• News that Cobalt has pulled out of manufacturing the Helios 64 Ultimate Arm-Powered NAS due to manufacturing difficulties and over-expansion
+• System76 factory tour and its relevance to Cobalt's situation
+• Possibility of Alex starting a company to build an ultimate NAS
+• Discussion on 3D printing vs metal prototypes
+• Appreciation of manufacturing work
+• Visit to a factory showing intricate process
+• Discussion with Carl, founder of System76, on details in manufacturing
+• Realization of the complexity involved in replicating manufacturing processes
+• Comparison to podcast production and manufacturing pipeline
+• Concern about potential lack of support for Cobol due to review
+• Wyze cameras' RTMP firmware and RTSP functionality
+• Docker container "Docker Wyze Bridge" to enable RTSP streaming
+• Using Docker Wyze Bridge with Blue Iris software
+• Compatibility issues with older Wyze V2 firmware
+• Recent changes to Wyze V3 firmware affecting compatibility
+• Links to compatible firmware in show notes
+• Introduction of Raspberry Pi KVM v3 hat on Kickstarter
+• Price concerns for a device that costs $145 without the Raspberry Pi and over $200 with it
+• Comparison to built-in IPMI on motherboards, which may be a more cost-effective option
+• Discussion of external devices versus built-in options
+• Value added by being able to control multiple devices from one Raspberry Pi
+• Potential use cases for devices that don't have built-in IPMI options
+• Raspberry Pi console access
+• Airflow in a server cupboard
+• Temperature in an RV while recording
+• Linode's cloud computing services and benefits
+• Anniversary of the show going independent with support from Linode
+• Features and capabilities of Linode, including S3 compatible object storage and DNS manager
+• Cloud providers and multi-cloud strategies
+• Linode as a cloud provider option
+• Password management with KeePass XC vs Bitwarden
+• Server security measures for hosting password managers
+• Security of the box
+• Limited internet access
+• Local encryption used by Bitwarden
+• Peace of mind with encrypted data at rest on servers
+• Being a "tall nail" and potential security issues
+• Personal anecdote about running remote desktop open to internet with weak password
+• Importance of firewalls and NATs for network security
+• Detecting issues in a system
+• Using top to identify resource-intensive processes
+• Checking logs for anomalies and tracking back through the system
+• Network monitoring tools like Snort
+• Containerization of services, potentially making some security situations worse but also offering better process isolation and control.
+• The benefits of running applications in containers, such as limiting the blast radius in case of a security breach
+• Comparison between containerized and non-containerized environments, highlighting the increased security of contained systems
+• Discussion on Wi-Fi system setup options, including mesh networks and multiple access points
+• Recommendations for specific products, such as Unify and Microtik routers, and services like cloudfree.shop
+• New smart plugs with energy monitoring built-in
+• Shipping to UK now available through Mylocalbytes.com or Cloudfree.shop
+• De-googling efforts: listener shares their own experience and progress
+	+ Replaced G Suite with Fastmail for mail, contacts, and calendar
+	+ Using Joplin for notes and docs synced with Nextcloud
+	+ Switched to iPhone SE 2020 for phone, using NextDNS for DNS
+	+ Using Apple Maps and OpenStreetMaps app for maps
+	+ Sticking with Firefox and Safari for browser
+	+ Replaced Chromebook with ThinkPad X260 running Arch and Fedora
+• The speaker discusses their use of FreeTube to bypass YouTube and the challenges they've faced with it
+• They mention Fastmail, but note it's not self-hosting
+• The speaker reflects on feedback from others, including a two-year journey to implement a solution
+• Maps are discussed, including HereMaps, Open Street Maps, Waze, and Magic Earth
+• The speaker shares their negative experience with Waze during a road trip in Denver rush hour
+• They mention the critical flaw of many mapping apps: poor search functionality
+• A user had trouble with Magic Earth and Apple Maps, being directed to the wrong location
+• Google Maps was used as a reference for comparison, showing superior search capabilities
+• The user looked into Apple Maps' privacy and security features due to concerns about cloud footprint
+• Apple Maps does not require an Apple ID or iCloud login to use
+• The data collected by Apple Maps is associated with a randomly generated identifier that resets frequently
+• Personalized features on Apple Maps are stored locally on the device, not sent to servers
+• Voice routing is clear about which lane to be in and intersections
+• Navigation app provides clear instructions for complex intersections, such as stacked lights
+• App integrates with wearable device to tap arm for turns
+• User found it helpful to look at watch for next turn during the trip
+• User initially struggled but eventually became proficient using the navigation app
+• User considered uninstalling Google Maps and sticking with the new app
+• Search functionality issues with OpenStreetMap
+• Pros and cons of using OpenStreetMap
+• Downloading maps offline feature on OpenStreetMap Plus
+• Cost comparison between OpenStreetMap Plus and F-Droid
+• ViewRanger app discussed as a alternative for hiking navigation
+• Discussion about alternative stores like Aurora Store and F-Droid
+• Use of ProtonMail instead of Gmail mentioned
+• Contact syncing and management
+• NextCloud as a contact syncing solution
+• E-T-E-Sync (Etsy Sync) as an alternative for secure end-to-end encrypted sync of contacts, calendars, tasks, and notes
+• Apps and availability for various platforms (Apple App Store, Google Play, F-Droid)
+• Integration with Android through DevX5
+• Recommendation for DevX5
+• Availability of DevX5 in F-Droid and other stores
+• Upcoming link to show notes for the podcast
+• Recap of a meetup event where listeners met the hosts
+• Mention of Optimus Grey wearing Chris and the Badger merchandise
+• Discussion of free donuts provided by Linode at the meetup
+• Story about the difficulty of getting 150 donuts in downtown Denver during rush hour
+• Interference on the left-hand side during a donut run
+• Appreciation for SelfHosted members and SREs
+• Promotion of sponsor Cloud Guru and their social media presence
+• Contact information for the show's hosts and producers

52： Navigating DeGoogling _transcript.txt

@@ -0,0 +1,1821 @@
+[0.00 --> 4.32]  Well, here we are, fresh back from Denver. We're joined by Brent again, who's still hanging around.
+[4.56 --> 6.52]  And Chris, hey, hi, how are you doing, gentlemen?
+[7.12 --> 8.74]  Hello. Hey, Brent, thanks for coming in again.
+[8.96 --> 10.36]  Hey, thanks. It's good to be here.
+[10.40 --> 14.46]  You're like our de-Google correspondent, and we're going to be talking a lot about that this week.
+[14.76 --> 15.44]  Beep-de-beep, beep-de-beep.
+[15.50 --> 16.34]  Beep-beep-beep-beep-beep.
+[18.38 --> 22.52]  Yeah, well, my dumbass mentioned de-Googling just the week before.
+[22.64 --> 26.36]  We're taking a massive trip, and I'd have zero hours to actually do any prep for the episode.
+[26.96 --> 33.50]  Luckily, the audience saw fit to write in with about 800 emails telling us all the different ways that they're doing it.
+[33.56 --> 37.20]  So we're going to come across some of those later on in the show.
+[37.72 --> 39.40]  But in the meantime...
+[39.40 --> 44.72]  This episode is brought to you by a Cloud Guru, the leader in learning for the cloud, Linux, and other modern tech skills.
+[44.98 --> 47.06]  Hundreds of courses and thousands of hands-on labs.
+[47.34 --> 50.66]  Get certified, get hired, get learning at a cloudguru.com.
+[51.14 --> 52.88]  I followed through on my challenge, Alex.
+[52.88 --> 65.00]  I de-Googled my map experience, which was crazy because we are on the road, and I was navigating Denver and now Colorado Springs for the entire time, the duration of this challenge.
+[65.36 --> 69.06]  So I will report back on my results when we get to the feedback.
+[69.50 --> 73.84]  But I think we should start with this news story that, I don't know, it's kind of a bummer, actually.
+[74.24 --> 75.64]  I was really sad to see this, yes.
+[75.64 --> 83.84]  Back in episode 33, we did a review of the Helios 64 Ultimate Arm-Powered NAS.
+[84.64 --> 88.70]  And unfortunately, the Cobalt team today have announced on their blog that they're pulling the plug.
+[89.20 --> 90.50]  Yeah, no more.
+[90.60 --> 94.28]  They're not even going to do the next batch that there's already orders in the pipeline for.
+[94.36 --> 96.50]  They say it really comes down to just two key points.
+[96.50 --> 103.88]  There's ongoing difficulties with manufacturing and procuring parts and costs of getting higher and higher.
+[104.56 --> 105.42]  That's been a problem.
+[105.50 --> 107.52]  And they say, number two, they made a rookie mistake.
+[107.70 --> 109.12]  They stretched themselves too thin.
+[109.64 --> 112.92]  They essentially went into the Helios 64 while just being a three-man show.
+[113.12 --> 115.14]  And they should have brought more people on board.
+[115.42 --> 116.36]  And they burned out.
+[116.36 --> 123.62]  You know, we got a really interesting insight into this manufacturing difficulties during our System76 factory tour last week,
+[123.82 --> 131.88]  where Jeremy, who is the guy that designed some of the firmware chips and some of the firmware itself for the launch keyboard,
+[132.04 --> 139.34]  was saying that they had to redesign on the fly two or three times some of the circuitry in that keyboard
+[139.34 --> 142.36]  because parts would go out of stock within hours.
+[142.36 --> 149.88]  And that he decided in the end to go ahead and order several, you know, hundred units of the parts they needed
+[149.88 --> 155.20]  before he'd actually finished the firmware so that it didn't go out of stock before he finished writing the code.
+[155.38 --> 161.72]  So if that's what System76 are up against, then they're probably a much larger player in this space than COBOL.
+[162.60 --> 164.94]  I can only imagine some of the issues that those guys are having.
+[165.20 --> 169.36]  It's a shame, though, because I think there's a lot of passion for an ARM-powered NAS,
+[169.36 --> 172.88]  specifically for those of us who are looking for low-power solutions.
+[173.54 --> 177.18]  We had some hopes that Helios was going to produce that for us.
+[177.44 --> 180.96]  Well, I think this speaks to some motivations that I've been feeling lately,
+[181.12 --> 185.12]  particularly after the last week getting the tour of the factory and seeing all the CNC machines
+[185.12 --> 187.22]  and all the powder coating stuff.
+[187.40 --> 191.56]  And, I mean, if ever you get the chance to be in Denver and do a tour of System76,
+[192.44 --> 194.08]  I'm not affiliated with them in any way.
+[194.20 --> 195.86]  You know, they're not a sponsor of the show or anything,
+[196.36 --> 198.22]  although they do sponsor other JB shows.
+[198.22 --> 199.62]  Just Coder, but yeah.
+[200.12 --> 201.42]  Oh, just Coder. That's right.
+[201.88 --> 203.74]  I mean, you know, maybe we should have them sponsor this show,
+[203.82 --> 207.86]  because those Thaleoses would make great NASes, so maybe they should be.
+[208.70 --> 211.20]  It was a truly inspirational experience for me.
+[211.24 --> 216.40]  So I'm sat here thinking, okay, COBOL, who was my hope, my light in this space,
+[216.46 --> 218.20]  has just bowed out.
+[218.30 --> 223.16]  Maybe Alex should start a company and build the ultimate NAS.
+[223.36 --> 224.68]  You know, maybe I should do that.
+[224.68 --> 226.98]  I think you've got a little bit of experience, Alex,
+[227.08 --> 229.96]  and some trials and tribulations that you've gone through already,
+[230.08 --> 231.20]  so maybe you're perfectly suited.
+[231.46 --> 234.16]  You could prototype 3D print the enclosure.
+[234.52 --> 236.26]  Well, you know, that was one of the things that struck me.
+[236.32 --> 239.26]  I know this is turning into a System76 factory tour recap,
+[239.56 --> 242.70]  but this is one of the things that struck me most during that tour, actually.
+[242.78 --> 245.50]  I asked them, you know, do you use 3D printing for your prototypes?
+[245.94 --> 249.16]  And they were like, well, no, it's just easier to do it in metal, isn't it?
+[249.52 --> 250.36]  And I'm like, is it?
+[250.36 --> 251.96]  Yeah, they used to.
+[252.20 --> 253.48]  Back in the day, they did.
+[253.68 --> 256.40]  I think one of the realities is that it's, with the equipment they have,
+[256.44 --> 258.12]  it's faster to make it out of metal.
+[258.30 --> 260.88]  It is really, you know, I think the reason why you keep coming back to it, Alex,
+[260.94 --> 266.40]  is because it is so hard to appreciate the amount of work that goes into manufacturing,
+[266.68 --> 268.08]  and that's an obvious thing to say.
+[268.50 --> 273.80]  But when you go to the factory, and you see every little thing they had to consider,
+[273.80 --> 277.90]  and when they're bringing things in as a block of aluminum,
+[277.90 --> 280.76]  and what's coming out on the other end is a keyboard or a case,
+[281.44 --> 286.04]  you really have no idea how intricate that process is until you see it.
+[286.52 --> 290.54]  And I think that's what is probably, I mean, that's what's resonated with me and stuck with me,
+[290.56 --> 292.10]  and I got to imagine probably for you, too.
+[292.66 --> 296.16]  Yeah, well, one example was Carl, who is the founder of System76.
+[296.58 --> 300.40]  I was just stood next to a shelf with loads of different parts in it,
+[300.40 --> 304.26]  and I picked up, like, an innocuous little nameplate, you know,
+[304.28 --> 306.28]  about the size of a dog tag or something like that,
+[306.62 --> 310.22]  and he jumped straight into a five-minute discussion telling me about all the different,
+[310.38 --> 312.80]  you know, reasons why they pick that particular size,
+[313.26 --> 315.58]  how it goes through their laser etching machine,
+[315.74 --> 318.20]  and how they're considering doing direct engraving instead,
+[318.32 --> 319.12]  and all that kind of stuff.
+[319.14 --> 323.50]  And I'm like, wow, if that's the amount of thought that goes into a nameplate,
+[323.50 --> 324.92]  or a serial number plate,
+[325.80 --> 330.38]  this is going to be a big mountain to solve if I want to try and do it myself.
+[330.68 --> 332.44]  That's what I take from it.
+[332.48 --> 335.02]  You take from it, hmm, maybe Alex could make a Nash.
+[335.06 --> 335.72]  That could be cool.
+[335.82 --> 338.80]  I take from it, oh, my God, I would have to build a factory,
+[338.80 --> 340.70]  and I would have to learn all this stuff.
+[341.12 --> 342.70]  Oh, well, that sounds fun, doesn't it?
+[342.96 --> 344.18]  Daunting, but fun.
+[344.66 --> 346.88]  Yeah, if I had another life,
+[347.52 --> 350.60]  if I had, like, you know, another hundred years,
+[350.68 --> 352.74]  I definitely would get into it for sure.
+[353.20 --> 355.46]  But you manufacture stuff every week as well,
+[355.50 --> 357.04]  and you ship podcasts every week.
+[357.04 --> 361.46]  Okay, you're not manufacturing aluminium into, you know, computer cases,
+[362.00 --> 364.68]  but you ship and manufacture stuff just the same.
+[364.92 --> 366.02]  That's true, and there have been many times
+[366.02 --> 367.82]  when we refer to our production pipeline
+[367.82 --> 369.42]  as kind of a manufacturing pipeline.
+[369.66 --> 374.92]  And if one component is delayed or, you know, gets out of order,
+[375.34 --> 376.46]  it does cause a jam up.
+[376.54 --> 379.10]  There is a lot of that kind of building tech around that.
+[379.18 --> 381.20]  Maybe that's why I don't have the appetite to do it again,
+[381.20 --> 383.34]  but I definitely would sit here and encourage you.
+[383.64 --> 385.12]  I'll be customer number one.
+[386.92 --> 387.80]  I'll be number two.
+[388.28 --> 390.68]  Well, there's a lot of roadblocks to overcome,
+[391.30 --> 393.58]  but if I could just bring it back to Cobol for a minute,
+[393.84 --> 395.80]  you know, one of the things I picked up on in my review
+[395.80 --> 398.56]  was that the product wasn't 100% finished,
+[398.62 --> 400.32]  and I've got to believe that with this news
+[400.32 --> 403.56]  that some of the issues that were present with that NAS now
+[403.56 --> 405.10]  will never be solved.
+[405.24 --> 407.24]  You know, things like the backplane breaking,
+[407.24 --> 410.24]  some of the plastic tabs, you know,
+[410.28 --> 411.64]  the power connector and data connector
+[411.64 --> 413.82]  on three of my hard drives, it turned out eventually.
+[414.74 --> 417.06]  Problems with the two and a half gigabit network adapter.
+[417.70 --> 419.20]  There was a bunch of other stuff as well.
+[419.36 --> 420.82]  You know, you can go and listen to episode 33
+[420.82 --> 421.84]  if you want the full review.
+[422.52 --> 424.74]  Well, I worry now this means that some of this stuff's
+[424.74 --> 425.84]  never going to get fixed.
+[426.48 --> 427.32]  Do you think you killed them?
+[427.46 --> 429.24]  Do you think that bad review killed them, Alex?
+[430.36 --> 431.26]  You murdered them.
+[431.74 --> 432.76]  Oh, don't say that.
+[432.82 --> 433.82]  I mean, I didn't mean to.
+[433.88 --> 434.94]  I was just trying to be honest.
+[434.94 --> 438.26]  It was presented in a way that I felt was constructive
+[438.26 --> 439.44]  to say that there are these,
+[439.92 --> 441.52]  it's a very promising piece of hardware.
+[441.64 --> 444.26]  I mean, the aluminium chassis was really lovely.
+[444.90 --> 446.78]  There was just a couple of key things that let it down,
+[446.84 --> 448.52]  you know, in terms of manufacturing tolerances
+[448.52 --> 449.88]  and a couple of firmware things.
+[450.04 --> 452.28]  But overall, they did a really great job.
+[452.32 --> 455.70]  And I wish there was some way we could tell them that,
+[455.74 --> 458.00]  you know, even though we weren't 100% positive,
+[458.00 --> 459.82]  it was just because we loved the idea,
+[459.92 --> 462.06]  not because we didn't want them to carry on and succeed.
+[462.64 --> 463.26]  I agree completely.
+[463.26 --> 466.52]  And they don't completely close the door in their blog post.
+[466.60 --> 468.10]  We'll have that linked in the show notes if you want.
+[468.16 --> 469.78]  They do kind of leave it cracked a little bit,
+[469.82 --> 470.76]  like maybe it'll come back.
+[471.14 --> 474.10]  But I wanted to shift gears and talk about something
+[474.10 --> 476.12]  that could solve a big problem for me.
+[476.20 --> 478.30]  I actually went out and I pre-ordered
+[478.30 --> 481.14]  a bunch of Wyze 3 cameras a long time ago.
+[481.18 --> 483.74]  And I have a box of Wyze 3 cameras
+[483.74 --> 485.36]  that I haven't installed
+[485.36 --> 489.30]  because they do not yet have an RTMP firmware
+[489.30 --> 491.72]  or an RTSP firmware for Wyze 3.
+[492.06 --> 493.92]  But Alex, I think you've solved that this week.
+[494.14 --> 495.86]  Yeah, I don't know where I came across this,
+[495.98 --> 497.76]  but I found a Docker container
+[497.76 --> 500.62]  that is called Docker Wyze Bridge.
+[500.84 --> 502.12]  Link in the show notes, of course.
+[502.48 --> 504.08]  And essentially what this does
+[504.08 --> 507.62]  is you give it your Wyze username and password
+[507.62 --> 509.86]  and it goes and sort of acts as an intermediary
+[509.86 --> 512.18]  between the Wyze API and the cameras.
+[512.18 --> 514.80]  And somehow it hooks into the local feed
+[514.80 --> 516.00]  on the cameras on your LAN
+[516.00 --> 520.22]  and then presents you with a normal RTSP stream.
+[520.44 --> 522.26]  So I've just got that feeding into Blue Iris
+[522.26 --> 524.28]  and it just works.
+[524.78 --> 525.52]  That's fascinating.
+[525.78 --> 528.18]  And yeah, it can actually do both.
+[528.26 --> 530.52]  It can pull from the Wyze servers
+[530.52 --> 531.68]  using your credentials.
+[532.24 --> 534.00]  Or with your credentials, it can use that.
+[534.10 --> 535.88]  There's a library that the app uses
+[535.88 --> 538.50]  and it essentially does a discovery on your network.
+[539.22 --> 541.04]  And the Wyze app does this as well.
+[541.04 --> 544.24]  And if it detects the camera, it uses LAN mode
+[544.24 --> 546.10]  and it just does that locally
+[546.10 --> 548.20]  and avoids the cloud relay.
+[548.92 --> 551.02]  And you can also in your Docker Compose,
+[551.10 --> 553.30]  there is an environment variable you can pass through
+[553.30 --> 555.82]  that says LAN underscore only that says,
+[556.00 --> 557.84]  don't even try the remote thing.
+[558.30 --> 560.66]  Only stream if you can locally detect them.
+[561.06 --> 562.72]  And that was the piece I was curious about.
+[562.78 --> 563.84]  That's why I dug into this.
+[563.92 --> 566.04]  And that means I could absolutely do this here in the RV,
+[566.22 --> 567.94]  which means I could replace these Wyze cams
+[567.94 --> 568.88]  that have been giving me trouble.
+[568.88 --> 570.20]  The version two was good,
+[570.20 --> 572.20]  but just didn't have enough horsepower,
+[572.44 --> 574.26]  didn't really work so great at night.
+[574.58 --> 576.14]  And the Wyze 3 solves those.
+[576.60 --> 578.54]  And with this Docker Wyze bridge,
+[578.58 --> 581.32]  which seems to have a decent community around it as well
+[581.32 --> 582.50]  and some active development,
+[583.10 --> 585.54]  I think my problems have been solved.
+[585.82 --> 587.46]  And I'll give this a go, I think,
+[587.48 --> 589.28]  once we get back into our home base.
+[589.28 --> 591.14]  So far as I can tell,
+[591.24 --> 593.56]  it only works on the V3 cameras.
+[593.80 --> 596.92]  So I've got a couple of V2s flashed with the RTSP firmware
+[596.92 --> 599.02]  and a couple of V3s.
+[599.12 --> 601.24]  And the app will, in its logs,
+[601.36 --> 603.58]  show me a bunch of errors for the two V2 cameras.
+[604.04 --> 605.68]  I don't know if that's because I'm running the,
+[605.74 --> 608.60]  you know, custom firmware or whatever it is.
+[609.30 --> 612.56]  But the performance with the V3s is great.
+[612.66 --> 614.74]  We've been using it as a baby monitor for my daughter.
+[614.74 --> 617.16]  And the night vision on there is just,
+[617.50 --> 618.66]  it's like daytime.
+[618.94 --> 619.86]  It's wonderful.
+[620.44 --> 621.78]  They blew it out of the park with the night vision.
+[622.00 --> 623.48]  It's tricky with the firmwares.
+[623.62 --> 625.22]  So this is an issue.
+[625.34 --> 626.30]  And I'm glad you brought it up
+[626.30 --> 627.68]  because we need to mention this on the show.
+[628.28 --> 630.06]  And they have it on their GitHub page.
+[630.20 --> 635.24]  There is a slightly older version of the firmware for V2
+[635.24 --> 637.24]  that is compatible with the bridge.
+[637.38 --> 640.16]  But if you use the latest firmware for V2,
+[640.68 --> 641.56]  it doesn't work.
+[641.56 --> 646.82]  And that actually holds true for some instances of the V3 model too.
+[646.90 --> 648.22]  So there's a version that does work
+[648.22 --> 649.92]  and there's a version that doesn't work with the V3
+[649.92 --> 651.90]  and the pan camera as well.
+[652.28 --> 653.92]  Anyways, the links in the show notes,
+[654.02 --> 655.40]  you do need to check into that
+[655.40 --> 659.34]  because I may have a really old firmware.
+[659.60 --> 660.60]  And so I'm going to have a hard time
+[660.60 --> 663.12]  getting just the right compatible firmware in some cases,
+[663.26 --> 665.20]  but they have all the information you need.
+[665.92 --> 668.80]  Back in episode 48, we talked about the Pi KVM,
+[668.80 --> 671.36]  you know, that wonderful Raspberry Pi
+[671.36 --> 677.22]  that captures HDMI and basically acts like a BMC KVM type thing.
+[677.64 --> 678.44]  Well, good news.
+[678.62 --> 682.34]  Their version 3 hat has finally entered Kickstarter mode.
+[682.86 --> 684.52]  It is a little pricey.
+[684.78 --> 688.24]  So the main hat, which doesn't include a Raspberry Pi,
+[688.80 --> 690.12]  costs $145.
+[690.52 --> 693.38]  So by the time you've added a Pi as well and a case,
+[693.38 --> 696.02]  it's going to be north of $200.
+[697.20 --> 699.16]  But you do get a lot of useful stuff in there,
+[699.22 --> 702.34]  like a USB-C bridge and CSI, you know, cables,
+[702.44 --> 703.18]  all that kind of stuff.
+[703.94 --> 706.82]  Now, Wendell's done a video about this on his channel on YouTube.
+[707.20 --> 707.86]  So if you're curious,
+[707.90 --> 709.80]  you can go and find out more about it over there.
+[710.72 --> 712.12]  I do wonder about the price.
+[712.14 --> 713.04]  And what do you think, Chris,
+[713.24 --> 715.06]  at that sort of $200 level?
+[715.06 --> 717.56]  Is that too much?
+[718.40 --> 720.10]  So it looks like right now on Kickstarter,
+[720.50 --> 723.90]  it's $145 and you'd get it by October 2021,
+[724.20 --> 725.72]  which seems pretty reasonable to me.
+[726.28 --> 731.42]  The price is, yeah, it feels high for a hat.
+[732.10 --> 734.72]  Now, I think the price is a little more reasonable
+[734.72 --> 736.16]  if you make the assumption
+[736.16 --> 738.54]  that just about everybody already has a Raspberry Pi 4
+[738.54 --> 740.80]  that would want to use something like this, right?
+[740.80 --> 743.40]  If you're going to use a Raspberry Pi-powered
+[743.40 --> 745.92]  keyboard video mouse switcher,
+[745.92 --> 748.80]  you probably already got a couple of Pis laying around.
+[749.26 --> 749.98]  So I don't think,
+[750.18 --> 751.50]  I think you just kind of null that out
+[751.50 --> 752.90]  because that's already a sunk cost.
+[753.00 --> 754.62]  And so it really is just the $145.
+[755.30 --> 758.34]  Now, you tell me, Alex, like how solid is this?
+[758.40 --> 760.60]  Is this, are you still using it?
+[760.66 --> 763.72]  Is it worth $145 now that you've used it for a bit?
+[764.84 --> 768.72]  I'm thinking I probably couldn't get a good KVM at that price.
+[769.18 --> 769.92]  I probably couldn't.
+[770.02 --> 772.50]  So I'd have to go with your word though,
+[772.50 --> 773.14]  if it's worth that.
+[773.44 --> 775.86]  Well, I'll tell you what I'm comparing it to in my mind, at least.
+[775.92 --> 779.40]  And that is a motherboard with IPMI built in.
+[779.78 --> 783.34]  So I'm actually going back to England in a couple of weeks
+[783.34 --> 786.44]  to go and introduce granddaughter to grandparents.
+[786.96 --> 788.32]  So hello, if you're listening.
+[789.12 --> 790.38]  And as part of that, I was thinking,
+[790.48 --> 791.82]  well, it would be nice to upgrade my,
+[791.98 --> 794.26]  you know, nearly 10 year old server in England
+[794.26 --> 795.78]  with a slightly more modern motherboard
+[795.78 --> 797.90]  and a slightly more modern IPMI implementation
+[797.90 --> 799.42]  that isn't based around Java.
+[799.42 --> 805.64]  And an eighth gen motherboard costs me around $150,
+[806.28 --> 808.72]  give or take, depending on the features that I want.
+[809.06 --> 811.56]  And I was looking at some ASRock rack stuff,
+[811.80 --> 814.96]  which thanks to, you know, the current chip shortage
+[814.96 --> 818.70]  seems to be in the $300, $250 to $300 range.
+[818.70 --> 821.40]  And so if I look at that and think,
+[821.52 --> 826.48]  I've got a built-in IPMI directly on the motherboard
+[826.48 --> 829.56]  that I know is going to be absolutely rock solid
+[829.56 --> 831.64]  versus an external device,
+[831.74 --> 834.68]  which in my experience has been good,
+[834.76 --> 836.38]  but it's still an external device.
+[836.50 --> 837.82]  And, you know, it's another power supply.
+[837.98 --> 840.44]  It's another operating system to keep updated,
+[840.68 --> 841.52]  et cetera, et cetera,
+[841.52 --> 844.18]  which in some respects could be a good thing.
+[844.18 --> 846.00]  In other respects could be a bad thing.
+[846.72 --> 848.68]  So the cost is kind of a wash, you know,
+[848.72 --> 850.56]  it's about the same to get a built-in
+[850.56 --> 852.36]  versus this external unit.
+[853.88 --> 855.46]  Probably just go for the built-in one,
+[855.60 --> 856.58]  to be honest with you.
+[857.36 --> 861.06]  Except for the fact that this Pi version
+[861.06 --> 862.98]  using the HDMI switch,
+[863.14 --> 865.54]  which is linked in the blog post in episode 48
+[865.54 --> 868.38]  that I talked about in that episode,
+[869.00 --> 870.78]  I've actually got three devices
+[870.78 --> 873.08]  hanging off this single Pi.
+[873.08 --> 875.10]  And that has actually worked really, really well.
+[875.30 --> 877.66]  So if you're able to spit that $150
+[877.66 --> 879.74]  between three devices,
+[880.18 --> 882.68]  suddenly that tips the scales quite a bit.
+[883.30 --> 883.50]  Hmm.
+[883.92 --> 885.38]  I also could see some value in there
+[885.38 --> 886.96]  if you needed to add it to devices
+[886.96 --> 888.86]  that IPMI wouldn't be an option.
+[889.30 --> 890.04]  Like, you know,
+[890.08 --> 892.44]  I'd love to have console-level access
+[892.44 --> 893.90]  to my studio machines right now
+[893.90 --> 894.68]  while I'm remote,
+[894.76 --> 895.50]  while I'm here in Denver.
+[895.92 --> 896.98]  For your other Raspberry Pis?
+[897.36 --> 898.20]  Yeah, that too.
+[898.40 --> 899.34]  It would be a great way
+[899.34 --> 901.22]  to get console access to my Raspberry Pis.
+[901.22 --> 902.00]  Oh, okay.
+[902.58 --> 903.02]  All right.
+[903.08 --> 904.66]  Now you're making me think
+[904.66 --> 906.08]  maybe I should back this.
+[907.60 --> 908.42]  Damn it, Alex.
+[908.74 --> 910.62]  Well, now I've actually been in Lady Dupes.
+[911.52 --> 913.42]  I've seen how you cool your
+[913.42 --> 914.72]  air quotes server cupboard.
+[916.74 --> 917.70]  It's pretty cool.
+[920.04 --> 921.50]  Hey man, I just got to get airflow.
+[921.70 --> 922.48]  That's all that matters.
+[922.58 --> 923.80]  I just got to get airflow.
+[924.42 --> 926.92]  How hot was it in the RV
+[926.92 --> 929.08]  whilst you were parked at System76 last week?
+[929.18 --> 930.40]  A hundred and seven?
+[930.72 --> 931.92]  Yeah, it was a hundred and seven.
+[932.04 --> 933.58]  I think the hottest we ever got in here,
+[933.62 --> 934.58]  though, was actually Nebraska.
+[934.78 --> 936.64]  I think it got near to 120 in here
+[936.64 --> 937.72]  while we were recording.
+[938.12 --> 939.40]  Which actually, it was impressive
+[939.40 --> 940.90]  because the server, quote,
+[941.10 --> 942.64]  room was the coolest place
+[942.64 --> 944.02]  in the whole RV at that time.
+[947.22 --> 949.50]  Leno.com slash SSH.
+[949.50 --> 952.28]  Go there to get $100 in 60-day credit
+[952.28 --> 952.90]  on a new account.
+[953.22 --> 954.60]  And you go there to support the show.
+[954.84 --> 955.96]  Hey guys, guess what?
+[956.04 --> 957.36]  This week's episode marks
+[957.36 --> 958.50]  our one-year anniversary
+[958.50 --> 959.94]  going independent again.
+[960.42 --> 960.70]  Yay!
+[961.12 --> 961.58]  How about that?
+[961.62 --> 962.38]  How awesome is that?
+[962.74 --> 964.02]  It's so cool
+[964.02 --> 965.90]  because Linode helped make that possible.
+[966.06 --> 967.84]  Amongst our member support
+[967.84 --> 968.58]  and those of you
+[968.58 --> 969.52]  who went over to
+[969.52 --> 971.16]  linode.com slash SSH.
+[971.16 --> 972.16]  We're here now,
+[972.34 --> 973.66]  rocking a year of independence.
+[974.00 --> 974.76]  And Linode,
+[974.96 --> 977.10]  they've been independent since 2003.
+[977.48 --> 980.12]  So they've really figured this out.
+[980.22 --> 982.34]  Like that's 18 years of focusing
+[982.34 --> 984.22]  on just being awesome
+[984.22 --> 985.56]  at cloud computing.
+[985.76 --> 987.48]  They started when it was new
+[987.48 --> 988.80]  and they have just evolved with it
+[988.80 --> 990.06]  and they have remained competitive
+[990.06 --> 991.12]  and sharp.
+[991.40 --> 992.96]  They have 11 global data centers
+[992.96 --> 994.60]  serving nearly a million customers
+[994.60 --> 996.22]  and businesses around the globe.
+[996.22 --> 997.00]  But really,
+[997.20 --> 998.98]  their mission remains unchanged
+[998.98 --> 1000.38]  since 18 years ago.
+[1000.86 --> 1002.36]  Make cloud computing simple,
+[1002.62 --> 1002.94]  affordable,
+[1003.10 --> 1004.04]  and accessible to all.
+[1004.36 --> 1005.74]  If you set up thousands of servers
+[1005.74 --> 1006.86]  or if you've never set up
+[1006.86 --> 1007.58]  a server before,
+[1008.00 --> 1009.06]  Linode can make that work.
+[1009.16 --> 1010.18]  I know it sounds like
+[1010.18 --> 1011.04]  an impossible task.
+[1011.48 --> 1012.78]  That's why I rave about them.
+[1012.82 --> 1014.00]  They've really done a great job.
+[1014.36 --> 1015.18]  We've been using
+[1015.18 --> 1016.80]  the absolute schmeck
+[1016.80 --> 1018.16]  out of their S3 compatible
+[1018.16 --> 1019.08]  object storage.
+[1019.52 --> 1021.20]  We created a Denver bucket
+[1021.20 --> 1023.26]  and we created a System76 bucket
+[1023.26 --> 1024.78]  and all of the media
+[1024.78 --> 1026.40]  across multiple cameras,
+[1026.56 --> 1027.46]  multiple recorders,
+[1027.54 --> 1028.46]  all gets uploaded
+[1028.46 --> 1029.64]  to those buckets.
+[1029.96 --> 1031.02]  And then our next cloud instance,
+[1031.12 --> 1031.72]  what we put on there,
+[1031.78 --> 1032.90]  also saves to their S3
+[1032.90 --> 1033.96]  compatible object storage.
+[1034.26 --> 1035.10]  And then my system's
+[1035.10 --> 1036.00]  back up there as well,
+[1036.46 --> 1037.90]  right here from the RV.
+[1038.24 --> 1039.04]  It's pretty awesome
+[1039.04 --> 1040.62]  and it's really just a great way
+[1040.62 --> 1041.34]  to use Linode
+[1041.34 --> 1042.34]  and not even have to have
+[1042.34 --> 1043.40]  a server running in front of it.
+[1043.82 --> 1045.56]  It's sort of like,
+[1045.94 --> 1046.82]  it feels like a power move.
+[1047.06 --> 1048.94]  They also have a great DNS manager.
+[1048.94 --> 1050.04]  They have Kubernetes
+[1050.04 --> 1051.24]  and Terraform support.
+[1051.36 --> 1052.46]  They have super fast networking
+[1052.46 --> 1054.44]  because they are their own ISP.
+[1054.78 --> 1057.02]  And their pricing is 30 to 50% cheaper
+[1057.02 --> 1058.42]  than other major cloud providers
+[1058.42 --> 1058.88]  out there.
+[1059.40 --> 1060.72]  You know, it's also a great way
+[1060.72 --> 1062.26]  to go with a multi-cloud strategy.
+[1062.42 --> 1063.62]  Perhaps you want something local
+[1063.62 --> 1065.86]  and you want something up in the cloud
+[1065.86 --> 1067.40]  or maybe you want something
+[1067.40 --> 1068.90]  across multiple cloud providers
+[1068.90 --> 1070.26]  and then network them
+[1070.26 --> 1071.54]  using something like Nebula.
+[1072.08 --> 1073.06]  Linode can be part
+[1073.06 --> 1074.16]  of that strategy as well.
+[1074.38 --> 1075.48]  They made our Jupiter Colony
+[1075.48 --> 1077.48]  reunion road trip possible as well.
+[1077.70 --> 1079.96]  Our meetups were powered by Linode
+[1079.96 --> 1081.52]  and it has been a hoot.
+[1081.98 --> 1082.76]  So go sign up today
+[1082.76 --> 1083.76]  and see what I've been talking about.
+[1083.76 --> 1085.06]  That $100 you're going to get,
+[1085.36 --> 1086.44]  you can really use that
+[1086.44 --> 1087.36]  to try the service out.
+[1087.44 --> 1088.40]  You can really get a feel
+[1088.40 --> 1089.38]  for what it's capable of.
+[1089.74 --> 1091.44]  That's $100 to really try something
+[1091.44 --> 1092.22]  or learn something.
+[1092.64 --> 1094.54]  Linode.com slash SSH.
+[1094.72 --> 1097.00]  That's Linode.com slash SSH.
+[1098.50 --> 1099.84]  Here's an email from Hans.
+[1100.28 --> 1100.88]  Hans says,
+[1101.00 --> 1101.64]  Hey guys,
+[1101.82 --> 1103.66]  you touched upon password managers
+[1103.66 --> 1105.30]  and Bitwarden in episode 51.
+[1105.50 --> 1106.02]  Like Brent,
+[1106.02 --> 1107.66]  I'm using KeePass XC.
+[1108.60 --> 1109.48]  Good choice.
+[1109.48 --> 1110.82]  What I like about it
+[1110.82 --> 1112.18]  is that it's easy to back up
+[1112.18 --> 1113.20]  because the whole database
+[1113.20 --> 1114.46]  is just a single file.
+[1115.02 --> 1115.86]  Currently sync it
+[1115.86 --> 1116.74]  between my devices
+[1116.74 --> 1118.60]  via self-hosted sync thing instance
+[1118.60 --> 1119.96]  running on an ARM board
+[1119.96 --> 1121.58]  in our laundry room.
+[1122.06 --> 1122.86]  Laundry room servers.
+[1123.00 --> 1123.36]  Very nice.
+[1124.04 --> 1124.76]  That being said,
+[1124.86 --> 1126.38]  this setup is a few years old
+[1126.38 --> 1127.92]  and if I would start from scratch
+[1127.92 --> 1129.68]  or if I had to share the password
+[1129.68 --> 1130.42]  with other people,
+[1130.58 --> 1132.16]  I'd definitely give Bitwarden a look.
+[1132.72 --> 1133.74]  One thing I wonder though,
+[1133.84 --> 1135.32]  when you host your passwords
+[1135.32 --> 1136.98]  in a more complex application
+[1136.98 --> 1137.74]  like Bitwarden,
+[1138.04 --> 1139.82]  are you taking any extra measures
+[1139.82 --> 1141.16]  to secure your servers?
+[1141.80 --> 1142.82]  I suppose it's reasonable
+[1142.82 --> 1144.42]  to trust the security
+[1144.42 --> 1146.60]  of Bitwarden itself,
+[1146.78 --> 1147.54]  but if an attacker
+[1147.54 --> 1148.94]  would gain access to your server,
+[1149.10 --> 1150.32]  would it be easier for them
+[1150.32 --> 1151.04]  to do harm
+[1151.04 --> 1152.58]  as compared to what you would
+[1152.58 --> 1154.12]  just host an encrypted
+[1154.12 --> 1155.78]  KeePass database file to?
+[1156.40 --> 1157.76]  Thanks and keep on going.
+[1157.96 --> 1158.14]  Hans.
+[1158.54 --> 1159.34]  Well, I think it depends
+[1159.34 --> 1161.38]  on how open your server is.
+[1161.50 --> 1162.74]  If it's connected to the internet,
+[1162.90 --> 1163.46]  you've got to assume
+[1163.46 --> 1164.16]  at some point,
+[1164.64 --> 1164.90]  you know,
+[1165.02 --> 1166.54]  it's possible it might get
+[1166.54 --> 1167.36]  compromised.
+[1168.52 --> 1170.40]  But it speaks to a larger
+[1170.40 --> 1172.60]  philosophy that I tend
+[1172.60 --> 1173.42]  to subscribe to
+[1173.42 --> 1174.24]  with this kind of stuff
+[1174.24 --> 1176.00]  of don't be the tallest nail.
+[1176.42 --> 1176.56]  You know,
+[1176.74 --> 1178.54]  take some basic precautions.
+[1178.74 --> 1180.10]  Have things like fail to ban
+[1180.10 --> 1182.50]  installed on your SSH logins.
+[1183.04 --> 1184.26]  Open as few ports
+[1184.26 --> 1184.86]  in your firewall
+[1184.86 --> 1185.92]  as you possibly can.
+[1186.38 --> 1187.84]  Use something like WireGuard
+[1187.84 --> 1188.60]  or TailScale
+[1188.60 --> 1189.48]  or something like that
+[1189.48 --> 1190.30]  to actually connect
+[1190.30 --> 1191.40]  to the service in question
+[1191.40 --> 1192.98]  so that all the data
+[1192.98 --> 1194.28]  that travels between
+[1194.28 --> 1195.28]  everything is encrypted.
+[1195.28 --> 1196.72]  You know,
+[1196.76 --> 1198.20]  and use things like SSH keys
+[1198.20 --> 1199.10]  instead of passwords.
+[1199.40 --> 1200.54]  Just those things alone
+[1200.54 --> 1201.08]  are going to make you
+[1201.08 --> 1202.26]  more secure than the average
+[1202.26 --> 1203.30]  server administrator.
+[1203.92 --> 1205.00]  Vault Warden is the new
+[1205.00 --> 1205.92]  hotness these days.
+[1206.04 --> 1207.70]  Bitwarden RS is the old name.
+[1208.10 --> 1209.58]  And I do agree with everything
+[1209.58 --> 1210.56]  you just said, Alex.
+[1211.12 --> 1212.32]  Don't be the tallest nail.
+[1212.42 --> 1213.00]  But also,
+[1213.28 --> 1214.44]  consider the security
+[1214.44 --> 1215.22]  of the box
+[1215.22 --> 1215.80]  if possible.
+[1215.90 --> 1216.94]  Limited internet access.
+[1217.42 --> 1217.86]  And also,
+[1218.08 --> 1218.82]  keep in mind,
+[1219.38 --> 1220.76]  Bitwarden is using
+[1220.76 --> 1222.22]  local encryption.
+[1222.22 --> 1223.68]  So it encrypts
+[1223.68 --> 1224.54]  and hashes your data
+[1224.54 --> 1225.82]  on your local device
+[1225.82 --> 1227.06]  before it sends it
+[1227.06 --> 1227.92]  to the cloud server,
+[1228.06 --> 1229.46]  even if it's their service
+[1229.46 --> 1231.22]  or your self-hosted service.
+[1231.54 --> 1232.42]  So that gives you
+[1232.42 --> 1233.60]  some peace of mind
+[1233.60 --> 1234.30]  knowing that the data
+[1234.30 --> 1235.18]  that's at rest
+[1235.18 --> 1235.66]  on the server
+[1235.66 --> 1236.28]  is encrypted.
+[1236.84 --> 1237.14]  Now, Alex,
+[1237.18 --> 1237.68]  you mentioned
+[1237.68 --> 1239.10]  being a shorter nail.
+[1239.98 --> 1241.60]  Have either of you
+[1241.60 --> 1242.84]  in all of your years
+[1242.84 --> 1243.86]  encountered situations
+[1243.86 --> 1244.96]  when you were
+[1244.96 --> 1245.82]  one of the taller nails
+[1245.82 --> 1246.84]  and ran into issues?
+[1247.62 --> 1247.86]  You mean,
+[1247.90 --> 1248.80]  like had a server compromised?
+[1249.06 --> 1249.44]  Basically,
+[1249.52 --> 1250.14]  that's what I'm asking.
+[1250.14 --> 1250.58]  Yeah,
+[1250.70 --> 1251.70]  it's never very exciting.
+[1252.28 --> 1253.44]  It's usually like
+[1253.44 --> 1254.12]  a server gets turned
+[1254.12 --> 1255.50]  into an FTP box
+[1255.50 --> 1257.44]  or somebody gets a process
+[1257.44 --> 1258.20]  on your machine.
+[1258.30 --> 1258.40]  I mean,
+[1258.42 --> 1259.18]  I think I've had
+[1259.18 --> 1260.32]  maybe a client or two
+[1260.32 --> 1261.30]  that that's happened to.
+[1262.16 --> 1263.38]  It's never anything
+[1263.38 --> 1264.48]  more exciting
+[1264.48 --> 1265.06]  than somebody trying
+[1265.06 --> 1265.84]  to mine crypto
+[1265.84 --> 1266.80]  or something these days.
+[1267.86 --> 1268.98]  Can I admit something
+[1268.98 --> 1269.62]  to you both?
+[1269.92 --> 1270.38]  Oh, yeah.
+[1270.62 --> 1271.64]  I used to run
+[1271.64 --> 1273.32]  remote desktop
+[1273.32 --> 1274.38]  open to the internet
+[1274.38 --> 1275.36]  with the password
+[1275.36 --> 1276.16]  22.
+[1277.76 --> 1279.08]  You maniac.
+[1279.08 --> 1280.88]  for like three years.
+[1281.02 --> 1282.18]  And how'd that go, Alex?
+[1283.42 --> 1283.82]  Well,
+[1284.10 --> 1285.40]  it didn't end well,
+[1285.82 --> 1286.06]  Brent.
+[1286.32 --> 1287.54]  It didn't end well at all.
+[1287.80 --> 1288.18]  No.
+[1289.76 --> 1290.52]  What happened?
+[1290.72 --> 1291.08]  Tell us.
+[1292.08 --> 1293.42]  They decided
+[1293.42 --> 1294.96]  to wipe my hard drives.
+[1295.46 --> 1296.12]  Oh, no.
+[1297.06 --> 1297.94]  Oh, that sucks.
+[1298.06 --> 1298.58]  That sucks.
+[1298.68 --> 1299.36]  I suppose maybe
+[1299.36 --> 1300.00]  that's better than
+[1300.00 --> 1301.20]  using it for something nefarious
+[1301.20 --> 1301.92]  or maybe they did
+[1301.92 --> 1302.64]  and then they wiped it
+[1302.64 --> 1303.44]  so there's no track.
+[1303.52 --> 1304.14]  So maybe they did
+[1304.14 --> 1305.08]  do something nefarious.
+[1305.26 --> 1306.08]  I have no idea.
+[1306.08 --> 1306.50]  I mean,
+[1306.52 --> 1307.04]  if your password
+[1307.04 --> 1307.56]  is 22,
+[1307.80 --> 1310.22]  maybe old Alex
+[1310.22 --> 1311.14]  didn't know how to check.
+[1313.06 --> 1313.42]  Yeah.
+[1313.52 --> 1313.72]  I mean,
+[1313.74 --> 1314.36]  back in the day,
+[1314.50 --> 1316.54]  that was something
+[1316.54 --> 1317.90]  you just didn't really think of
+[1317.90 --> 1318.74]  way back in the day.
+[1318.82 --> 1319.32]  Things were just
+[1319.32 --> 1319.92]  on the internet.
+[1320.10 --> 1322.14]  When I first got exposure
+[1322.14 --> 1324.12]  to TCP IP networking,
+[1324.68 --> 1325.82]  everything had a public
+[1325.82 --> 1326.56]  internet address
+[1326.56 --> 1327.32]  on the network.
+[1327.72 --> 1328.84]  And it wasn't until
+[1328.84 --> 1330.18]  sometime later
+[1330.18 --> 1331.36]  that we had firewalls
+[1331.36 --> 1332.12]  and NATs.
+[1332.20 --> 1333.04]  And so for a short period
+[1333.04 --> 1333.30]  of time,
+[1333.34 --> 1333.90]  you could basically
+[1333.90 --> 1334.80]  connect to everything.
+[1336.30 --> 1337.58]  There was some crazy stuff
+[1337.58 --> 1338.32]  we did back then.
+[1338.88 --> 1339.58]  I didn't want to put you guys
+[1339.58 --> 1339.98]  on the spot,
+[1340.08 --> 1341.00]  but I would be curious
+[1341.00 --> 1343.14]  about how to go about
+[1343.14 --> 1344.30]  detecting some of this stuff,
+[1344.54 --> 1344.76]  you know,
+[1344.78 --> 1345.62]  even from a most
+[1345.62 --> 1347.00]  very basic level.
+[1347.68 --> 1348.00]  Hmm.
+[1348.18 --> 1348.42]  Well,
+[1348.48 --> 1348.82]  I mean,
+[1348.82 --> 1349.24]  I'm sure Alex,
+[1349.26 --> 1350.10]  you probably have a few ideas.
+[1350.26 --> 1351.18]  My first couple
+[1351.18 --> 1351.78]  that come to mind
+[1351.78 --> 1353.40]  would be know what processes
+[1353.40 --> 1353.94]  should be writing
+[1353.94 --> 1354.58]  on your box,
+[1354.72 --> 1355.60]  check your logs.
+[1355.96 --> 1356.46]  I mean,
+[1356.48 --> 1358.16]  almost every single time
+[1358.16 --> 1359.70]  that a client machine
+[1359.70 --> 1360.10]  or something
+[1360.10 --> 1361.56]  was behaving poorly,
+[1362.24 --> 1363.18]  I could almost immediately
+[1363.18 --> 1364.14]  just suss it out
+[1364.14 --> 1364.84]  by running top.
+[1365.10 --> 1365.54]  I mean,
+[1365.58 --> 1365.90]  really,
+[1366.18 --> 1366.40]  because,
+[1366.54 --> 1366.64]  you know,
+[1366.70 --> 1367.52]  you know what that machine
+[1367.52 --> 1368.40]  is supposed to be doing.
+[1368.60 --> 1369.58]  And if there's some process
+[1369.58 --> 1370.50]  going crazy on there
+[1370.50 --> 1371.34]  that has nothing to do
+[1371.34 --> 1372.28]  with the responsibilities
+[1372.28 --> 1373.18]  of that box,
+[1373.28 --> 1374.38]  you got a pretty good idea
+[1374.38 --> 1374.98]  of what it is.
+[1375.66 --> 1376.56]  And then you look
+[1376.56 --> 1377.18]  at your logs,
+[1377.26 --> 1377.42]  right?
+[1377.42 --> 1378.96]  You look at the active users
+[1378.96 --> 1380.42]  that are logged onto the system
+[1380.42 --> 1381.96]  and you kind of start
+[1381.96 --> 1382.62]  tracing it back.
+[1382.70 --> 1383.22]  Usually you'll look
+[1383.22 --> 1383.80]  at the process
+[1383.80 --> 1384.32]  and there'll be like
+[1384.32 --> 1386.08]  some weird path
+[1386.08 --> 1386.64]  or URL
+[1386.64 --> 1387.86]  for a process
+[1387.86 --> 1388.72]  that looks normal,
+[1388.82 --> 1389.92]  but it's in the wrong place
+[1389.92 --> 1390.68]  or it's being run
+[1390.68 --> 1391.56]  by the wrong user
+[1391.56 --> 1392.92]  and you kind of track
+[1392.92 --> 1393.54]  it back from there.
+[1394.40 --> 1395.44]  Depends where
+[1395.44 --> 1396.98]  your expertise lies.
+[1397.48 --> 1399.12]  If you're a networking guy,
+[1399.38 --> 1400.24]  you could use something
+[1400.24 --> 1401.32]  like Snort,
+[1401.84 --> 1402.64]  which is essentially
+[1402.64 --> 1404.52]  a packet filter
+[1404.52 --> 1405.78]  and it looks for certain
+[1405.78 --> 1406.80]  patterns of packets.
+[1406.96 --> 1407.12]  Yeah,
+[1407.16 --> 1408.50]  or bandwidth charts as well.
+[1408.58 --> 1408.72]  You know,
+[1408.74 --> 1409.34]  that sometimes
+[1409.34 --> 1410.32]  will be an indication
+[1410.32 --> 1410.98]  something's up
+[1410.98 --> 1411.40]  as you'll see
+[1411.40 --> 1412.22]  your bandwidth usage
+[1412.22 --> 1412.86]  spikes up.
+[1414.14 --> 1415.14]  And would you guys say
+[1415.14 --> 1416.02]  that containerizing
+[1416.02 --> 1417.24]  some of your services
+[1417.24 --> 1418.14]  is a way to
+[1418.14 --> 1419.06]  help this situation?
+[1419.06 --> 1421.56]  No.
+[1421.94 --> 1422.30]  No.
+[1424.72 --> 1425.08]  No,
+[1425.18 --> 1425.38]  I mean,
+[1425.40 --> 1425.62]  really,
+[1425.68 --> 1425.96]  in a way,
+[1426.02 --> 1426.70]  it makes it worse.
+[1426.84 --> 1427.56]  I think it makes it worse
+[1427.56 --> 1428.74]  because there's more processes
+[1428.74 --> 1429.80]  and more things going on
+[1429.80 --> 1430.96]  on a box in some cases.
+[1431.48 --> 1432.18]  But you do have
+[1432.18 --> 1432.76]  better security
+[1432.76 --> 1433.58]  in terms of networking
+[1433.58 --> 1434.22]  control
+[1434.22 --> 1435.70]  and process isolation
+[1435.70 --> 1436.84]  and the ability
+[1436.84 --> 1437.68]  to just destroy
+[1437.68 --> 1438.20]  a container
+[1438.20 --> 1439.00]  and recreate it
+[1439.00 --> 1439.46]  if something did
+[1439.46 --> 1439.88]  go sideways.
+[1440.02 --> 1440.36]  So it's,
+[1440.68 --> 1440.96]  I mean,
+[1440.96 --> 1441.40]  it's a mix.
+[1441.48 --> 1442.28]  I think it's good and bad.
+[1442.40 --> 1442.74]  But I'm sure,
+[1442.82 --> 1442.96]  Alex,
+[1443.00 --> 1443.58]  you must have thoughts.
+[1443.66 --> 1444.24]  You must have thoughts.
+[1444.58 --> 1444.70]  Well,
+[1444.88 --> 1445.52]  containers good,
+[1445.60 --> 1446.40]  everything else bad,
+[1446.52 --> 1446.76]  right?
+[1446.76 --> 1447.52]  That's my viewpoint.
+[1447.52 --> 1451.56]  But I think containers
+[1451.56 --> 1452.66]  are better in this situation
+[1452.66 --> 1453.40]  because let's say
+[1453.40 --> 1454.82]  you've got an NGINX web server
+[1454.82 --> 1456.44]  listening with your
+[1456.44 --> 1458.46]  vault warden behind it
+[1458.46 --> 1459.88]  or whatever the web server is
+[1459.88 --> 1461.18]  that's exposing your passwords
+[1461.18 --> 1462.38]  to you.
+[1462.90 --> 1464.46]  If somebody was to compromise
+[1464.46 --> 1466.46]  something in that code
+[1466.46 --> 1468.04]  and do a buffer overflow
+[1468.04 --> 1468.76]  or do something
+[1468.76 --> 1469.76]  that meant they could get
+[1469.76 --> 1470.56]  something out of memory
+[1470.56 --> 1471.30]  that they shouldn't
+[1471.30 --> 1473.58]  and extrapolate some data
+[1473.58 --> 1474.94]  that they shouldn't get,
+[1474.94 --> 1476.98]  the blast radius of that
+[1476.98 --> 1477.80]  is going to be limited
+[1477.80 --> 1478.76]  to the scope
+[1478.76 --> 1480.32]  that that container
+[1480.32 --> 1481.48]  has access to.
+[1482.22 --> 1483.72]  And so running things
+[1483.72 --> 1484.22]  in a container
+[1484.22 --> 1485.20]  is more secure
+[1485.20 --> 1486.74]  simply by virtue
+[1486.74 --> 1487.26]  of the fact
+[1487.26 --> 1488.46]  that you are scoping
+[1488.46 --> 1489.48]  what that container
+[1489.48 --> 1490.44]  has access to
+[1490.44 --> 1491.60]  on the host system.
+[1492.36 --> 1492.38]  Yeah,
+[1492.46 --> 1492.68]  I mean,
+[1492.68 --> 1493.32]  it will have access
+[1493.32 --> 1494.24]  to any of the data
+[1494.24 --> 1495.02]  that the container
+[1495.02 --> 1495.78]  has access to
+[1495.78 --> 1496.92]  which is likely
+[1496.92 --> 1497.64]  important data
+[1497.64 --> 1498.72]  but it's contained
+[1498.72 --> 1499.84]  to that region.
+[1500.06 --> 1500.94]  That's inherently more safe
+[1500.94 --> 1501.84]  than say running Apache
+[1501.84 --> 1502.92]  or NGINX on a box
+[1502.92 --> 1504.02]  and you pop Apache
+[1504.02 --> 1505.20]  and now you've got
+[1505.20 --> 1506.08]  access to anything
+[1506.08 --> 1506.98]  on that host
+[1506.98 --> 1508.12]  that Apache had access to
+[1508.12 --> 1509.18]  which if you're lucky
+[1509.18 --> 1509.80]  is not much
+[1509.80 --> 1511.22]  but sometimes
+[1511.22 --> 1511.74]  is way more
+[1511.74 --> 1512.30]  than it should be.
+[1512.74 --> 1513.56]  So yeah,
+[1514.40 --> 1516.24]  it's going to be different
+[1516.24 --> 1517.04]  every time too.
+[1517.30 --> 1519.08]  There's not a one-size-fits-all solution.
+[1519.24 --> 1520.50]  It's trying to make sure
+[1520.50 --> 1521.18]  you're secure
+[1521.18 --> 1522.24]  and monitoring
+[1522.24 --> 1523.74]  in multiple locations.
+[1524.96 --> 1526.30]  We got a lot of email
+[1526.30 --> 1527.98]  about people's Wi-Fi systems.
+[1528.10 --> 1528.72]  We got some people
+[1528.72 --> 1529.80]  who love mesh setups,
+[1530.26 --> 1531.24]  some people who hate
+[1531.24 --> 1532.16]  mesh setups
+[1532.16 --> 1533.62]  but we got one email
+[1533.62 --> 1534.56]  in about a
+[1534.56 --> 1536.54]  free mesh wireless solution.
+[1536.78 --> 1537.16]  It's at
+[1537.16 --> 1538.74]  freemeshwireless.com.
+[1539.14 --> 1540.12]  It's an open source package
+[1540.12 --> 1541.18]  that you load
+[1541.18 --> 1541.80]  onto hardware
+[1541.80 --> 1543.54]  and then we got some people
+[1543.54 --> 1544.34]  that said don't do it.
+[1544.44 --> 1546.22]  Just deploy multiple APs.
+[1546.36 --> 1547.34]  So I'm still collecting
+[1547.34 --> 1548.20]  information
+[1548.20 --> 1549.00]  and taking it all in
+[1549.00 --> 1550.02]  and I got a few devices
+[1550.02 --> 1550.90]  to research too
+[1550.90 --> 1552.10]  so I wanted to say
+[1552.10 --> 1552.76]  thank you to everybody
+[1552.76 --> 1553.80]  who sent in suggestions
+[1553.80 --> 1555.12]  for different Wi-Fi setups.
+[1555.66 --> 1555.96]  Wow,
+[1556.54 --> 1557.50]  there's a lot out there
+[1557.50 --> 1558.40]  including some of you
+[1558.40 --> 1558.72]  who said,
+[1558.78 --> 1559.08]  you know what,
+[1559.10 --> 1560.02]  just stick with Unify.
+[1560.20 --> 1560.64]  It's fine.
+[1560.96 --> 1561.40]  It's fine.
+[1561.40 --> 1562.34]  Well, okay,
+[1562.34 --> 1562.84]  just one guy.
+[1564.52 --> 1565.46]  And several folks,
+[1565.58 --> 1565.78]  Brent,
+[1565.86 --> 1566.76]  were happy with your
+[1566.76 --> 1567.82]  recommendation of checking
+[1567.82 --> 1568.72]  out Microtik.
+[1568.98 --> 1569.90]  It's almost like I know
+[1569.90 --> 1570.30]  something.
+[1572.92 --> 1574.14]  At the meetup in Denver,
+[1574.32 --> 1575.54]  several of you let me know
+[1575.54 --> 1577.64]  that you are massive fans
+[1577.64 --> 1579.02]  of cloudfree.shop
+[1579.02 --> 1580.00]  and they are sponsoring
+[1580.00 --> 1580.82]  today's episode.
+[1581.28 --> 1582.28]  Use the coupon code
+[1582.28 --> 1583.04]  self-hosted
+[1583.04 --> 1584.16]  and get a dollar off
+[1584.16 --> 1585.14]  one of their new version
+[1585.14 --> 1586.36]  two smart plugs
+[1586.36 --> 1587.32]  with energy monitoring
+[1587.32 --> 1587.88]  built in.
+[1587.88 --> 1589.10]  Also,
+[1589.54 --> 1590.50]  those of you in the UK
+[1590.50 --> 1591.54]  who have let me know
+[1591.54 --> 1592.52]  that you wish
+[1592.52 --> 1593.48]  that cloudfree.shop
+[1593.48 --> 1594.32]  shipped to the UK,
+[1594.66 --> 1594.82]  well,
+[1594.98 --> 1595.80]  good news!
+[1596.56 --> 1597.60]  Mylocalbytes.com
+[1597.60 --> 1598.74]  have launched in the UK
+[1598.74 --> 1600.60]  offering a very similar thing.
+[1601.00 --> 1602.10]  You can use the coupon code
+[1602.10 --> 1602.68]  self-hosted
+[1602.68 --> 1604.04]  at both cloudfree.shop
+[1604.04 --> 1605.74]  and mylocalbytes.com
+[1605.74 --> 1607.04]  to get a dollar
+[1607.04 --> 1607.70]  or a pound
+[1607.70 --> 1609.46]  off each smart plug.
+[1609.86 --> 1610.62]  Both of these stores
+[1610.62 --> 1611.40]  are owned
+[1611.40 --> 1612.08]  and operated
+[1612.08 --> 1613.64]  by a couple of our listeners,
+[1613.64 --> 1614.96]  so head over there,
+[1615.06 --> 1615.80]  support the community
+[1615.80 --> 1617.00]  and check out
+[1617.00 --> 1618.02]  their cool stuff.
+[1619.80 --> 1621.28]  We had a lot of emails
+[1621.28 --> 1623.36]  in regards to de-googling
+[1623.36 --> 1625.02]  and it really ran
+[1625.02 --> 1625.96]  the whole spectrum.
+[1626.12 --> 1626.52]  We're going to try
+[1626.52 --> 1628.38]  to get to some of them,
+[1628.88 --> 1629.76]  but legitimately,
+[1630.04 --> 1630.16]  Brett,
+[1630.20 --> 1630.84]  you saw the list.
+[1630.92 --> 1631.56]  There's just no way
+[1631.56 --> 1632.00]  we could read
+[1632.00 --> 1632.64]  all those emails.
+[1633.06 --> 1633.24]  Yeah,
+[1633.30 --> 1633.86]  you gave me
+[1633.86 --> 1634.82]  a little sneak peek
+[1634.82 --> 1635.72]  at just the number
+[1635.72 --> 1637.06]  of the sheer number of emails.
+[1637.08 --> 1637.50]  I just scrolled
+[1637.50 --> 1638.16]  through the list.
+[1638.44 --> 1638.46]  Oh,
+[1638.58 --> 1639.38]  we did our best,
+[1639.64 --> 1640.06]  but we've...
+[1640.06 --> 1640.88]  It's a lot of email.
+[1641.36 --> 1641.62]  Yeah,
+[1642.36 --> 1643.10]  but Dustin was one
+[1643.10 --> 1644.40]  of the first to write in
+[1644.40 --> 1645.40]  and Dustin was at
+[1645.40 --> 1646.00]  the Boise meetup
+[1646.00 --> 1646.36]  with us,
+[1646.44 --> 1646.60]  Brent.
+[1647.16 --> 1647.56]  He says,
+[1647.62 --> 1648.60]  on today's self-hosted,
+[1648.62 --> 1649.16]  you guys talked
+[1649.16 --> 1649.98]  about de-googling.
+[1650.44 --> 1651.38]  This is my journey
+[1651.38 --> 1651.94]  and it has been
+[1651.94 --> 1652.70]  for two years
+[1652.70 --> 1653.12]  and I'd say I'm
+[1653.12 --> 1654.24]  about 90%
+[1654.24 --> 1655.44]  of the way there.
+[1655.92 --> 1656.48]  Dustin goes on
+[1656.48 --> 1656.64]  to say,
+[1656.72 --> 1657.28]  this includes
+[1657.28 --> 1658.18]  replacing G Suite
+[1658.18 --> 1658.94]  for my podcast
+[1658.94 --> 1659.86]  and I've also gone
+[1659.86 --> 1660.46]  with the model
+[1660.46 --> 1661.52]  of self-hosting
+[1661.52 --> 1662.24]  when it makes sense.
+[1662.68 --> 1663.50]  So here's what he's done.
+[1663.60 --> 1664.00]  For mail,
+[1664.12 --> 1664.48]  contacts,
+[1664.56 --> 1665.14]  and calendar,
+[1665.56 --> 1666.06]  he switched
+[1666.06 --> 1666.78]  from G Suite
+[1666.78 --> 1667.68]  to Fastmail.
+[1668.08 --> 1669.48]  For notes and docs,
+[1669.54 --> 1670.70]  he's using Joplin,
+[1671.30 --> 1672.12]  using Nextcloud
+[1672.12 --> 1672.70]  to sync it,
+[1673.10 --> 1674.30]  for photo sync,
+[1674.36 --> 1675.26]  he's using Nextcloud.
+[1675.62 --> 1676.28]  For his phone,
+[1676.36 --> 1676.78]  he's gone with
+[1676.78 --> 1677.96]  the iPhone SE 2020,
+[1678.26 --> 1678.80]  so he's not dealing
+[1678.80 --> 1679.44]  with Google there.
+[1679.90 --> 1680.44]  For DNS,
+[1680.72 --> 1681.78]  he's using NextDNS.
+[1681.86 --> 1682.50]  We got another vote
+[1682.50 --> 1683.56]  for NextDNS as well.
+[1684.10 --> 1684.98]  For maps,
+[1685.34 --> 1686.32]  he's using a combination
+[1686.32 --> 1687.36]  of Apple Maps
+[1687.36 --> 1689.02]  and the OpenStreetMaps
+[1689.02 --> 1690.46]  app on the App Store.
+[1690.98 --> 1691.82]  And for the browser,
+[1691.98 --> 1692.50]  he's sticking with
+[1692.50 --> 1693.56]  Firefox and Safari.
+[1694.28 --> 1695.30]  And for his Chromebook,
+[1695.40 --> 1695.52]  well,
+[1695.54 --> 1696.32]  he's replaced that
+[1696.32 --> 1698.04]  with the ThinkPad X260
+[1698.04 --> 1698.62]  with Arch
+[1698.62 --> 1699.88]  and now Fedora on there.
+[1700.10 --> 1700.96]  He's still working
+[1700.96 --> 1701.74]  on the home assistance.
+[1701.74 --> 1702.54]  He's going to maybe
+[1702.54 --> 1703.60]  consider the HomePods
+[1703.60 --> 1705.26]  and look at Mycroft.
+[1705.58 --> 1705.92]  He says,
+[1706.00 --> 1706.56]  Google Photos
+[1706.56 --> 1707.20]  has been working great
+[1707.20 --> 1708.04]  for my wife,
+[1708.30 --> 1709.70]  but I'm not using it.
+[1710.12 --> 1711.04]  And he's using
+[1711.04 --> 1711.68]  FreeTube
+[1711.68 --> 1713.50]  to bypass YouTube,
+[1713.50 --> 1714.36]  but it has been
+[1714.36 --> 1715.10]  a bit of a challenge,
+[1715.18 --> 1715.58]  I suspect.
+[1716.28 --> 1717.40]  Some good tips there,
+[1717.48 --> 1719.04]  although Fastmail
+[1719.04 --> 1720.76]  isn't self-hosting.
+[1720.84 --> 1721.34]  It is,
+[1721.54 --> 1721.80]  you know,
+[1721.80 --> 1722.88]  having somebody else host it.
+[1722.90 --> 1723.28]  But if you're going
+[1723.28 --> 1724.08]  to have somebody host something,
+[1724.20 --> 1725.54]  email's a good one to do.
+[1726.22 --> 1727.32]  Don't really do.
+[1727.66 --> 1728.22]  Don't do.
+[1728.50 --> 1729.38]  Don't do email.
+[1730.48 --> 1731.10]  What I noticed
+[1731.10 --> 1731.78]  from that feedback
+[1731.78 --> 1732.82]  is that it took him,
+[1733.44 --> 1733.66]  well,
+[1733.98 --> 1735.06]  he's on a two-year journey.
+[1735.50 --> 1735.98]  And so,
+[1736.24 --> 1736.52]  gentlemen,
+[1736.86 --> 1738.42]  what does that tell you
+[1738.42 --> 1739.62]  about what you've just got on?
+[1739.86 --> 1741.50]  That Alex has really,
+[1741.60 --> 1742.34]  really gotten us
+[1742.34 --> 1742.82]  into something.
+[1742.94 --> 1743.58]  What have I done?
+[1744.08 --> 1745.42]  I've opened Pandora's box
+[1745.42 --> 1745.66]  here,
+[1745.74 --> 1746.02]  aren't I?
+[1747.32 --> 1747.76]  Oh,
+[1747.76 --> 1748.36]  man.
+[1749.48 --> 1750.06]  All right.
+[1750.16 --> 1750.36]  So,
+[1750.46 --> 1751.18]  Carson and others
+[1751.18 --> 1752.52]  wrote in about maps.
+[1752.68 --> 1753.24]  Carson says
+[1753.24 --> 1754.52]  he settled on HereMaps
+[1754.52 --> 1755.34]  as a replacement,
+[1755.54 --> 1756.80]  wego.here.com.
+[1756.80 --> 1758.22]  A lot of people wrote in
+[1758.22 --> 1759.16]  about open street maps.
+[1759.32 --> 1759.42]  Brent,
+[1759.48 --> 1760.40]  that's what you use?
+[1760.76 --> 1760.94]  Yeah,
+[1761.02 --> 1762.50]  that's what I have been using
+[1762.50 --> 1763.58]  until all these suggestions
+[1763.58 --> 1764.18]  came in.
+[1764.40 --> 1765.16]  And I,
+[1765.78 --> 1766.10]  well,
+[1766.76 --> 1767.76]  maybe I'll keep that
+[1767.76 --> 1768.52]  until we talk about
+[1768.52 --> 1769.60]  the maps a little bit more.
+[1769.78 --> 1769.90]  Well,
+[1769.92 --> 1770.56]  I want to talk about it
+[1770.56 --> 1771.22]  right now because
+[1771.22 --> 1772.52]  that's the route
+[1772.52 --> 1773.34]  I decided to go
+[1773.34 --> 1774.00]  during a
+[1774.00 --> 1775.50]  freaking road trip.
+[1775.76 --> 1776.96]  And I even really
+[1776.96 --> 1778.12]  briefly tried Waze,
+[1778.20 --> 1778.62]  even though I know
+[1778.62 --> 1779.18]  it's owned by Google,
+[1779.22 --> 1779.76]  I just wanted to
+[1779.76 --> 1780.66]  just do a comparison.
+[1781.04 --> 1781.92]  And Waze actually
+[1781.92 --> 1782.98]  screwed us up the worst
+[1782.98 --> 1783.88]  out of all of them
+[1783.88 --> 1785.12]  during the middle
+[1785.12 --> 1786.26]  of Denver rush hour.
+[1786.26 --> 1787.00]  It had me get off
+[1787.00 --> 1787.46]  the highway
+[1787.46 --> 1788.76]  to bypass the traffic.
+[1789.18 --> 1789.88]  And then I got off
+[1789.88 --> 1790.18]  the highway
+[1790.18 --> 1790.74]  and I was stuck
+[1790.74 --> 1791.38]  in more traffic.
+[1791.54 --> 1792.00]  And then it did
+[1792.00 --> 1792.70]  a quick update
+[1792.70 --> 1793.04]  and it said,
+[1793.20 --> 1793.76]  get on the highway.
+[1794.28 --> 1794.36]  Yeah,
+[1794.42 --> 1795.18]  it felt to me
+[1795.18 --> 1796.28]  like an attempt
+[1796.28 --> 1797.58]  at a Dukes of Hazzard
+[1797.58 --> 1799.04]  style walk around
+[1799.04 --> 1799.70]  the traffic,
+[1800.04 --> 1801.26]  but it didn't work
+[1801.26 --> 1802.04]  out too well for us.
+[1802.88 --> 1803.28]  Oh,
+[1803.52 --> 1803.88]  goodness.
+[1804.30 --> 1804.80]  So I know
+[1804.80 --> 1805.24]  a lot of you
+[1805.24 --> 1806.02]  wrote in with
+[1806.02 --> 1807.26]  the apps that you love
+[1807.26 --> 1808.22]  and I tried them
+[1808.22 --> 1809.64]  and boy,
+[1809.70 --> 1810.30]  do they stink.
+[1810.44 --> 1811.08]  Magic Earth
+[1811.08 --> 1812.16]  was one that I liked
+[1812.16 --> 1813.82]  and that uses
+[1813.82 --> 1814.64]  open street maps
+[1814.64 --> 1816.04]  with a proprietary GUI
+[1816.04 --> 1816.70]  on top,
+[1816.88 --> 1817.68]  Magic Earth,
+[1818.02 --> 1818.40]  have a link
+[1818.40 --> 1819.22]  in the show notes.
+[1820.12 --> 1822.28]  But they all have
+[1822.28 --> 1823.52]  one critical flaw.
+[1823.70 --> 1824.44]  Even Apple Maps
+[1824.44 --> 1825.44]  has this critical flaw
+[1825.44 --> 1826.62]  and it's search.
+[1827.88 --> 1828.68]  For example,
+[1828.78 --> 1829.80]  I'm here in Colorado Springs
+[1829.80 --> 1830.82]  and I searched
+[1830.82 --> 1831.66]  for Pikes Peak,
+[1831.78 --> 1833.52]  which is a very popular
+[1833.52 --> 1834.38]  tourist destination.
+[1835.56 --> 1836.82]  Apple Maps sent me
+[1836.82 --> 1838.36]  in the wrong direction.
+[1838.46 --> 1838.80]  They sent me
+[1838.80 --> 1839.80]  to some like business
+[1839.80 --> 1840.42]  that was named
+[1840.42 --> 1841.08]  Pikes Peak
+[1841.08 --> 1841.84]  that was like
+[1841.84 --> 1842.90]  10 miles
+[1842.90 --> 1843.66]  in the wrong direction,
+[1843.96 --> 1845.42]  literally the opposite direction.
+[1846.86 --> 1848.20]  The Magic Earth
+[1848.20 --> 1849.40]  using open street maps
+[1849.40 --> 1850.50]  wanted to send me
+[1850.50 --> 1851.22]  to a location
+[1851.22 --> 1852.78]  5,200 miles away
+[1852.78 --> 1853.88]  from my current location.
+[1854.44 --> 1855.64]  I was 25,
+[1855.84 --> 1856.50]  30 minutes away
+[1856.50 --> 1857.08]  when I started
+[1857.08 --> 1857.90]  from Pikes Peak
+[1857.90 --> 1858.78]  and after I was done
+[1858.78 --> 1859.22]  trying to use
+[1859.22 --> 1860.02]  these other nav apps,
+[1860.14 --> 1861.42]  I ended up an hour away
+[1861.42 --> 1863.24]  and I was really bad.
+[1864.00 --> 1864.44]  Eventually,
+[1864.56 --> 1865.00]  what happened
+[1865.00 --> 1866.00]  is my wife
+[1866.00 --> 1866.56]  looked it up
+[1866.56 --> 1867.20]  on her phone
+[1867.20 --> 1867.98]  on Google Maps
+[1867.98 --> 1870.08]  and got an address
+[1870.08 --> 1871.44]  and then telegrammed it to me
+[1871.44 --> 1872.22]  and then I put that
+[1872.22 --> 1873.28]  into Apple Maps
+[1873.28 --> 1875.48]  and manually did it that way.
+[1875.48 --> 1875.94]  You're an animal.
+[1876.78 --> 1877.16]  Yeah,
+[1877.20 --> 1877.60]  it was interesting
+[1877.60 --> 1879.12]  because she kept using
+[1879.12 --> 1880.12]  Google Maps
+[1880.12 --> 1880.88]  during this.
+[1881.30 --> 1882.12]  Anytime I drove
+[1882.12 --> 1882.90]  or anytime I was looking
+[1882.90 --> 1883.50]  anything up
+[1883.50 --> 1883.88]  or looking,
+[1884.00 --> 1885.28]  I used anything
+[1885.28 --> 1885.98]  but Google Maps
+[1885.98 --> 1886.48]  and she stuck
+[1886.48 --> 1886.96]  with Google Maps
+[1886.96 --> 1887.38]  so I was always
+[1887.38 --> 1888.20]  comparing the two
+[1888.20 --> 1890.14]  and they clearly
+[1890.14 --> 1891.64]  have the superior
+[1891.64 --> 1894.02]  search.
+[1894.72 --> 1895.16]  However,
+[1896.32 --> 1897.00]  Apple Maps
+[1897.00 --> 1897.86]  surprised me
+[1897.86 --> 1898.34]  and I looked
+[1898.34 --> 1899.10]  into the privacy
+[1899.10 --> 1899.82]  and security
+[1899.82 --> 1900.54]  of Apple Maps
+[1900.54 --> 1901.24]  because that was
+[1901.24 --> 1901.84]  really what part
+[1901.84 --> 1902.36]  of this was about
+[1902.36 --> 1903.38]  was reducing
+[1903.38 --> 1904.20]  my cloud footprint
+[1904.20 --> 1904.70]  with this.
+[1904.98 --> 1906.28]  The thing I liked
+[1906.28 --> 1906.94]  about Apple Maps
+[1906.94 --> 1907.54]  is surprisingly
+[1907.54 --> 1908.04]  you don't even
+[1908.04 --> 1908.62]  have to be signed
+[1908.62 --> 1909.80]  into any Apple ID
+[1909.80 --> 1910.30]  or iCloud
+[1910.30 --> 1910.94]  to use it.
+[1911.52 --> 1911.92]  The data
+[1911.92 --> 1912.86]  that they do collect
+[1912.86 --> 1913.84]  is associated
+[1913.84 --> 1914.60]  with a randomly
+[1914.60 --> 1915.68]  generated identifier.
+[1915.96 --> 1916.46]  They reset
+[1916.46 --> 1917.66]  like every few minutes
+[1917.66 --> 1919.06]  and it is not tied
+[1919.06 --> 1919.68]  to your Apple ID.
+[1920.42 --> 1921.34]  They convert
+[1921.34 --> 1922.64]  precise locations
+[1922.64 --> 1924.22]  into less exact locations
+[1924.22 --> 1925.34]  before they store them
+[1925.34 --> 1926.46]  and then they apply
+[1926.46 --> 1927.34]  that to your current
+[1927.34 --> 1928.02]  device location
+[1928.02 --> 1928.58]  information
+[1928.58 --> 1929.16]  and origin
+[1929.16 --> 1930.68]  within 24 hours
+[1930.68 --> 1933.24]  and any of the
+[1933.24 --> 1934.32]  personalized features
+[1934.32 --> 1935.56]  like where your car
+[1935.56 --> 1936.08]  is parked
+[1936.08 --> 1937.26]  or suggested
+[1937.26 --> 1938.54]  departure times
+[1938.54 --> 1940.52]  your favorite locations
+[1940.52 --> 1942.06]  any of that kind
+[1942.06 --> 1942.36]  of stuff
+[1942.36 --> 1943.04]  that you generate
+[1943.04 --> 1944.18]  it's all stored
+[1944.18 --> 1944.70]  on device.
+[1944.82 --> 1945.52]  They don't send it up
+[1945.52 --> 1946.14]  to the Apple servers
+[1946.14 --> 1946.42]  at all.
+[1947.24 --> 1947.66]  It seems to me
+[1947.66 --> 1948.28]  the way they've
+[1948.28 --> 1949.04]  defined how
+[1949.04 --> 1950.00]  Apple Maps works
+[1950.00 --> 1951.24]  is sort of
+[1951.24 --> 1951.90]  their privacy
+[1951.90 --> 1952.96]  first approach
+[1952.96 --> 1954.08]  that they've been
+[1954.08 --> 1955.00]  sharing
+[1955.00 --> 1956.26]  throughout the years.
+[1956.50 --> 1956.66]  Yeah.
+[1956.78 --> 1957.40]  I'm not going to say
+[1957.40 --> 1958.02]  it's perfect.
+[1958.26 --> 1958.98]  But it feels like
+[1958.98 --> 1960.00]  they got most of it right
+[1960.00 --> 1961.54]  considering all of the
+[1961.54 --> 1962.76]  sort of technical stuff
+[1962.76 --> 1963.66]  that has to happen
+[1963.66 --> 1964.60]  to get you around
+[1964.60 --> 1965.58]  on a Maps app.
+[1965.76 --> 1967.82]  Or another way
+[1967.82 --> 1969.18]  is it feels like
+[1969.18 --> 1970.04]  they designed a product
+[1970.04 --> 1971.40]  to say screw you
+[1971.40 --> 1971.82]  to Google
+[1971.82 --> 1972.84]  on data collection
+[1972.84 --> 1973.56]  and stuff like that.
+[1973.62 --> 1974.14]  And did it work?
+[1974.54 --> 1974.76]  Well,
+[1974.94 --> 1976.26]  the display
+[1976.26 --> 1977.28]  is probably the best.
+[1977.36 --> 1977.82]  The other thing
+[1977.82 --> 1978.18]  that I found
+[1978.18 --> 1979.20]  surprisingly good
+[1979.20 --> 1981.48]  is the voice routing.
+[1981.82 --> 1983.42]  It has really good
+[1983.42 --> 1983.82]  clear,
+[1983.98 --> 1984.94]  like very clear
+[1984.94 --> 1985.58]  about which lane
+[1985.58 --> 1986.02]  to be in,
+[1986.10 --> 1986.98]  which isn't too uncommon.
+[1987.72 --> 1989.32]  And it's very clear
+[1989.32 --> 1990.44]  about intersections.
+[1990.78 --> 1992.10]  And here in the
+[1992.10 --> 1993.28]  Colorado-Denver area,
+[1993.46 --> 1994.78]  they stack the intersections.
+[1995.16 --> 1996.46]  So you drive
+[1996.46 --> 1997.12]  through an intersection
+[1997.12 --> 1998.56]  and then three
+[1998.56 --> 1999.44]  or four car lengths
+[1999.44 --> 1999.78]  later,
+[1999.88 --> 2001.24]  there is another intersection.
+[2001.88 --> 2002.54]  And so when you look
+[2002.54 --> 2003.14]  on a map,
+[2003.26 --> 2004.04]  you're not really sure
+[2004.04 --> 2004.72]  like what light
+[2004.72 --> 2005.36]  to turn on.
+[2005.52 --> 2006.96]  And the voice prompt
+[2006.96 --> 2007.70]  is very clear.
+[2007.80 --> 2008.26]  It'll say,
+[2008.26 --> 2009.96]  go through this light
+[2009.96 --> 2011.06]  and at the next light,
+[2011.52 --> 2012.12]  take a left,
+[2012.38 --> 2013.38]  be in the middle lane.
+[2014.06 --> 2014.88]  And when you're,
+[2014.88 --> 2015.50]  when you're new
+[2015.50 --> 2016.40]  to an area
+[2016.40 --> 2017.08]  and it's dark
+[2017.08 --> 2018.18]  and you're coming up
+[2018.18 --> 2018.96]  on two intersections
+[2018.96 --> 2019.40]  and you know
+[2019.40 --> 2020.42]  you've got a left turn
+[2020.42 --> 2021.50]  or a right turn,
+[2021.64 --> 2022.66]  that kind of clarity
+[2022.66 --> 2024.52]  just makes it low stress.
+[2024.62 --> 2025.28]  Then additionally,
+[2025.52 --> 2026.76]  they tie in with the watch
+[2026.76 --> 2027.78]  so it taps your arm
+[2027.78 --> 2028.92]  when you need to turn.
+[2029.36 --> 2030.62]  And when you were driving,
+[2031.00 --> 2031.68]  I was able to just
+[2031.68 --> 2032.36]  look at my watch
+[2032.36 --> 2032.78]  and tell you
+[2032.78 --> 2033.62]  what the next turn is.
+[2033.84 --> 2033.92]  Yeah,
+[2033.96 --> 2034.64]  that was really handy.
+[2034.92 --> 2036.36]  I will admit that
+[2036.36 --> 2037.56]  halfway through the trip,
+[2037.56 --> 2038.46]  I kind of gave up
+[2038.46 --> 2039.12]  on my phone
+[2039.12 --> 2040.30]  and my map app
+[2040.30 --> 2040.74]  because,
+[2041.08 --> 2041.18]  well,
+[2041.22 --> 2041.82]  we were doing this,
+[2041.86 --> 2042.52]  this experiment
+[2042.52 --> 2044.84]  and my methods
+[2044.84 --> 2045.32]  were failing.
+[2045.70 --> 2047.30]  So you were in the nav seat
+[2047.30 --> 2048.42]  and you were helping me out
+[2048.42 --> 2049.22]  and that actually
+[2049.22 --> 2049.92]  worked out all right.
+[2050.16 --> 2050.54]  I think I'm going
+[2050.54 --> 2051.14]  to stick with it.
+[2051.34 --> 2052.14]  I don't think I'm after the,
+[2052.26 --> 2052.46]  I mean,
+[2052.48 --> 2053.38]  I said I'd do it for two weeks
+[2053.38 --> 2053.82]  and I think I'm going
+[2053.82 --> 2054.48]  to stick with it.
+[2055.20 --> 2055.86]  I'll let my,
+[2055.98 --> 2056.14]  you know,
+[2056.18 --> 2056.90]  my wife will still have
+[2056.90 --> 2057.80]  Google Maps as a backup,
+[2058.08 --> 2058.76]  but for me,
+[2059.16 --> 2060.22]  I'm uninstalling Google Maps
+[2060.22 --> 2060.64]  off the phone.
+[2061.26 --> 2061.58]  Wow.
+[2061.80 --> 2061.92]  Yeah.
+[2061.92 --> 2063.14]  So that's quite a success.
+[2063.34 --> 2063.52]  Yeah.
+[2063.58 --> 2064.92]  It's not open street maps,
+[2065.14 --> 2066.12]  although I am playing
+[2066.12 --> 2066.74]  with those still
+[2066.74 --> 2067.58]  and I do really like
+[2067.58 --> 2068.28]  the way Magic Earth
+[2068.28 --> 2069.18]  displays things.
+[2069.76 --> 2070.96]  So for some circumstances,
+[2070.96 --> 2071.68]  like if I already know
+[2071.68 --> 2072.30]  the address
+[2072.30 --> 2073.28]  and I'm not searching
+[2073.28 --> 2073.92]  up something,
+[2074.66 --> 2075.88]  they may have a place still.
+[2076.24 --> 2077.62]  But I,
+[2077.70 --> 2078.28]  I was,
+[2078.46 --> 2079.42]  I was pretty impressed.
+[2080.20 --> 2080.76]  You know,
+[2080.82 --> 2081.76]  if you only could have
+[2081.76 --> 2082.24]  one app
+[2082.24 --> 2083.82]  and you didn't care
+[2083.82 --> 2084.80]  about Google tracking you,
+[2085.20 --> 2086.26]  I'd probably still suggest
+[2086.26 --> 2086.98]  you use Google Maps.
+[2087.84 --> 2088.40]  You know,
+[2088.52 --> 2088.78]  I,
+[2088.96 --> 2089.40]  for the trip,
+[2089.48 --> 2091.18]  used the same app
+[2091.18 --> 2091.86]  that I've been using
+[2091.86 --> 2093.24]  for probably the last two years
+[2093.24 --> 2094.36]  since I've tried this
+[2094.36 --> 2095.58]  de-googling a while ago,
+[2096.06 --> 2098.06]  mostly successfully.
+[2098.58 --> 2100.14]  And so I'm on Android
+[2100.14 --> 2100.92]  and I've been using
+[2100.92 --> 2102.38]  OpenStreetMap,
+[2102.46 --> 2103.44]  the OSM,
+[2103.60 --> 2104.46]  and plus.
+[2105.64 --> 2106.32]  There are things
+[2106.32 --> 2106.94]  I love about it
+[2106.94 --> 2107.88]  and things I hate about it.
+[2108.32 --> 2109.14]  The one thing,
+[2109.22 --> 2110.20]  you mentioned search.
+[2110.72 --> 2112.22]  I find it's great
+[2112.22 --> 2113.28]  if you know
+[2113.28 --> 2114.00]  approximately
+[2114.00 --> 2114.84]  where you want to go.
+[2115.00 --> 2115.70]  If you're trying to find
+[2115.70 --> 2116.70]  an exact business
+[2116.70 --> 2117.82]  or even
+[2117.82 --> 2119.06]  an exact address
+[2119.06 --> 2120.46]  on a popular street,
+[2120.92 --> 2122.86]  it's not necessarily
+[2122.86 --> 2123.46]  going to have it.
+[2123.52 --> 2124.26]  It might have some
+[2124.26 --> 2125.16]  of the street numbers,
+[2125.60 --> 2126.76]  but certainly not all of them.
+[2126.82 --> 2127.68]  I found that to be
+[2127.68 --> 2128.52]  a little bit frustrating,
+[2128.80 --> 2129.02]  but
+[2129.02 --> 2131.40]  it gets me there.
+[2132.06 --> 2132.88]  I will say
+[2132.88 --> 2133.84]  90% of the time
+[2133.84 --> 2134.52]  it works for me,
+[2134.60 --> 2135.82]  but I like getting lost
+[2135.82 --> 2136.60]  in new cities,
+[2136.76 --> 2137.58]  so maybe that's
+[2137.58 --> 2138.44]  a unique approach.
+[2138.86 --> 2139.48]  Well, there's that
+[2139.48 --> 2140.34]  if you don't mind getting lost.
+[2140.42 --> 2141.00]  That's a feature.
+[2141.42 --> 2142.16]  Yeah, for Brent.
+[2142.64 --> 2143.48]  The thing I liked
+[2143.48 --> 2144.58]  about the OpenStreetMaps app
+[2144.58 --> 2145.56]  is that you could download
+[2145.56 --> 2146.52]  your maps offline.
+[2146.70 --> 2147.24]  Hold on a minute.
+[2147.50 --> 2148.04]  Hold on a minute.
+[2148.96 --> 2149.68]  OSM and Plus
+[2149.68 --> 2150.84]  is $25.
+[2152.04 --> 2152.74]  That's quite a lot,
+[2152.80 --> 2153.06]  isn't it,
+[2153.06 --> 2153.46]  for an app?
+[2153.76 --> 2154.20]  Well, you know,
+[2154.30 --> 2156.42]  it's not $25 for me
+[2156.42 --> 2157.26]  when I get it from
+[2157.26 --> 2157.96]  F-Droid.
+[2158.62 --> 2159.78]  Ah, there you go,
+[2159.82 --> 2160.12]  you see.
+[2161.70 --> 2162.44]  I've been using
+[2162.44 --> 2163.04]  ViewRanger
+[2163.04 --> 2164.40]  for quite a number
+[2164.40 --> 2164.72]  of years.
+[2164.78 --> 2165.68]  Whenever I take a hike
+[2165.68 --> 2166.50]  or something like that,
+[2166.60 --> 2166.88]  I actually,
+[2167.14 --> 2168.24]  this is a very
+[2168.24 --> 2169.12]  long-term usage
+[2169.12 --> 2169.62]  for me
+[2169.62 --> 2170.92]  from back
+[2170.92 --> 2171.58]  when I lived in England.
+[2171.58 --> 2173.52]  It supports things
+[2173.52 --> 2174.76]  like Ordnance Survey Maps
+[2174.76 --> 2175.66]  and you can download
+[2175.66 --> 2177.16]  US Geological Survey Maps.
+[2177.26 --> 2178.02]  You can buy them
+[2178.02 --> 2179.58]  and actually buy the tiles
+[2179.58 --> 2181.00]  directly in ViewRanger.
+[2181.54 --> 2182.78]  They're changing their name
+[2182.78 --> 2184.10]  to Outdoor Active
+[2184.10 --> 2185.96]  so you can find them
+[2185.96 --> 2186.92]  at ViewRanger.com.
+[2187.22 --> 2188.20]  I've found that one
+[2188.20 --> 2188.62]  pretty good.
+[2189.18 --> 2190.02]  Brent there mentioned
+[2190.02 --> 2190.70]  F-Droid.
+[2191.16 --> 2192.44]  We got several people,
+[2192.62 --> 2193.42]  including Ross,
+[2193.48 --> 2194.36]  who wrote in and said,
+[2194.48 --> 2195.58]  I like the Aurora Store.
+[2196.00 --> 2196.68]  It's an alternative
+[2196.68 --> 2197.90]  front-end for Google Play
+[2197.90 --> 2199.14]  which keeps your data away
+[2199.14 --> 2200.08]  while giving you access
+[2200.08 --> 2200.78]  to those apps
+[2200.78 --> 2201.54]  that are exclusive.
+[2202.98 --> 2203.46]  He's like,
+[2203.50 --> 2203.98]  that's the only way
+[2203.98 --> 2205.08]  I could get the Starlink app.
+[2205.96 --> 2206.64]  I will admit,
+[2206.78 --> 2208.24]  I have Aurora Droid installed
+[2208.24 --> 2209.00]  and I prefer it
+[2209.00 --> 2209.48]  over F-Droid
+[2209.48 --> 2210.50]  most of the time.
+[2210.80 --> 2211.16]  It has a few
+[2211.16 --> 2211.92]  little tiny bugs,
+[2212.04 --> 2212.58]  but I didn't know
+[2212.58 --> 2213.28]  that was a feature,
+[2213.46 --> 2214.20]  so that's great to hear.
+[2214.62 --> 2215.80]  Ross says that he switched
+[2215.80 --> 2217.14]  to ProtonMail from Gmail
+[2217.14 --> 2218.66]  and I've used ProtonMail
+[2218.66 --> 2219.48]  and I like it a lot.
+[2220.72 --> 2221.68]  So there's something there.
+[2222.46 --> 2223.30]  There was also,
+[2223.56 --> 2224.90]  a lot of people wrote in
+[2224.90 --> 2225.88]  about their different approaches
+[2225.88 --> 2226.94]  to contact syncing
+[2226.94 --> 2227.76]  and Brent,
+[2227.80 --> 2228.30]  did you cover
+[2228.30 --> 2229.06]  in last week's episode
+[2229.06 --> 2229.60]  how you do that?
+[2229.78 --> 2230.32]  I think I did,
+[2230.38 --> 2231.00]  but I'll do it again.
+[2231.34 --> 2232.30]  I'm using NextCloud
+[2232.30 --> 2233.08]  for contact syncing
+[2233.08 --> 2234.16]  and I've found that
+[2234.16 --> 2235.50]  to be pretty bulletproof actually.
+[2235.66 --> 2236.66]  I was worried at first
+[2236.66 --> 2237.82]  when I did it a while ago
+[2237.82 --> 2239.36]  because contacts
+[2239.36 --> 2241.44]  is arguably the thing
+[2241.44 --> 2242.46]  that's most important to me
+[2242.46 --> 2244.12]  getting all of that right
+[2244.12 --> 2245.32]  and it's been bulletproof.
+[2246.20 --> 2247.04]  Well, Dale writes in,
+[2247.14 --> 2248.66]  I just listened to episode 51
+[2248.66 --> 2250.46]  and I think Brent mentioned
+[2250.46 --> 2251.12]  NextCloud.
+[2251.54 --> 2252.46]  Yes, confirmed.
+[2252.66 --> 2253.64]  We just had that confirmed
+[2253.64 --> 2254.02]  by Brent.
+[2254.10 --> 2254.44]  Thank you.
+[2254.98 --> 2256.20]  And I wondered if any of you
+[2256.20 --> 2258.06]  have heard or used Etsy Sync,
+[2258.10 --> 2260.16]  that's E-T-E-Sync.com.
+[2260.54 --> 2262.12]  It's a self-hostable project
+[2262.12 --> 2263.24]  whose value proposition
+[2263.24 --> 2264.18]  is secure,
+[2264.40 --> 2265.42]  end-to-end encrypted
+[2265.42 --> 2267.44]  and privacy respecting sync
+[2267.44 --> 2268.20]  for your contacts,
+[2268.42 --> 2268.84]  calendars,
+[2269.02 --> 2270.24]  tasks and notes.
+[2270.66 --> 2271.56]  I've been using it
+[2271.56 --> 2272.88]  for about two years now
+[2272.88 --> 2274.24]  and more recently
+[2274.24 --> 2274.94]  I've been using it
+[2274.94 --> 2275.84]  on my GNOME desktop.
+[2275.84 --> 2276.98]  I pay for them
+[2276.98 --> 2277.90]  to manage the hosting
+[2277.90 --> 2278.42]  and syncing
+[2278.42 --> 2279.30]  but you could absolutely
+[2279.30 --> 2280.14]  host it yourself.
+[2280.58 --> 2281.58]  Highly recommend it.
+[2281.70 --> 2282.46]  Thanks for the great show
+[2282.46 --> 2283.04]  and all the best.
+[2283.30 --> 2283.52]  Dale.
+[2284.58 --> 2285.72]  E-T-E-Sync.com
+[2285.72 --> 2286.44]  We'll have a link to that
+[2286.44 --> 2286.92]  in the show notes.
+[2286.96 --> 2287.64]  I looked at it
+[2287.64 --> 2289.00]  before the show
+[2289.00 --> 2290.40]  and it's a solution
+[2290.40 --> 2291.34]  that really is kind of
+[2291.34 --> 2292.94]  targeted at just
+[2292.94 --> 2295.02]  a end-to-end
+[2295.02 --> 2296.40]  encrypted sync
+[2296.40 --> 2297.82]  of contact calendar
+[2297.82 --> 2298.48]  task notes.
+[2298.60 --> 2299.38]  Like it just solves
+[2299.38 --> 2300.02]  that problem.
+[2300.20 --> 2301.26]  That's what they focus on.
+[2301.54 --> 2302.54]  And they've got apps
+[2302.54 --> 2303.66]  in the Apple App Store,
+[2304.14 --> 2304.62]  Google Play,
+[2304.62 --> 2305.72]  they're on F-Droid too
+[2305.72 --> 2307.20]  and of course
+[2307.20 --> 2307.88]  you can get it
+[2307.88 --> 2308.36]  on your desktop.
+[2308.90 --> 2310.32]  It looks pretty legit actually.
+[2310.54 --> 2311.54]  I think I just decrypted
+[2311.54 --> 2312.62]  what their name means.
+[2312.76 --> 2313.48]  E-to-E-Sync
+[2313.48 --> 2314.36]  is end-to-end sync
+[2314.36 --> 2314.88]  isn't it?
+[2315.08 --> 2316.74]  Ah, I was wondering.
+[2317.08 --> 2317.42]  Duh.
+[2318.58 --> 2319.42]  It's one of those moments
+[2319.42 --> 2320.02]  you figure it out
+[2320.02 --> 2320.38]  and you're like
+[2320.38 --> 2321.48]  oh I feel like a dummy now.
+[2323.18 --> 2324.18]  You know if I could
+[2324.18 --> 2325.00]  mention one thing
+[2325.00 --> 2325.80]  about Nextcloud
+[2325.80 --> 2327.74]  on Android at least
+[2327.74 --> 2328.66]  that made it
+[2328.66 --> 2330.28]  possible for me
+[2330.28 --> 2331.42]  and integrates it
+[2331.42 --> 2332.34]  at a system level
+[2332.34 --> 2332.94]  everywhere
+[2332.94 --> 2334.58]  is this little app
+[2334.58 --> 2335.68]  called DevX5.
+[2336.06 --> 2337.46]  It takes the Nextcloud
+[2337.46 --> 2337.96]  syncing
+[2337.96 --> 2339.64]  which is CalDev
+[2339.64 --> 2341.00]  and CardDev
+[2341.00 --> 2341.96]  and just
+[2341.96 --> 2342.70]  sort of
+[2342.70 --> 2343.42]  makes that
+[2343.42 --> 2343.96]  available
+[2343.96 --> 2344.90]  at a system level
+[2344.90 --> 2346.10]  in the same exact
+[2346.10 --> 2346.60]  places
+[2346.60 --> 2347.42]  and ways
+[2347.42 --> 2348.20]  that all of the
+[2348.20 --> 2349.08]  Google stuff
+[2349.08 --> 2349.62]  appears
+[2349.62 --> 2350.70]  so it's just seamless.
+[2351.16 --> 2351.60]  So that would be
+[2351.60 --> 2352.30]  a huge recommendation
+[2352.30 --> 2352.88]  from me.
+[2353.04 --> 2353.88]  Say it again for me.
+[2355.02 --> 2355.54]  DevX5
+[2355.54 --> 2357.06]  available in F-Droid
+[2357.06 --> 2358.20]  and maybe
+[2358.20 --> 2359.10]  in other stores.
+[2359.20 --> 2359.70]  Can you put a link
+[2359.70 --> 2360.22]  in the show notes
+[2360.22 --> 2360.76]  for us Brent?
+[2361.24 --> 2361.86]  Oh probably.
+[2362.56 --> 2363.26]  So what did you guys
+[2363.26 --> 2364.10]  think of the meetup?
+[2364.56 --> 2365.18]  It was pretty cool
+[2365.18 --> 2366.14]  to meet some of our
+[2366.14 --> 2367.06]  listeners huh?
+[2367.34 --> 2368.18]  Yeah we saw
+[2368.18 --> 2369.16]  a Chris and the Badger
+[2369.16 --> 2369.70]  shirt there
+[2369.70 --> 2370.80]  which was exciting
+[2370.80 --> 2371.24]  because I hadn't
+[2371.24 --> 2371.86]  considered that
+[2371.86 --> 2372.48]  somebody would get
+[2372.48 --> 2372.96]  a shirt with the
+[2372.96 --> 2373.54]  intention of bringing
+[2373.54 --> 2374.08]  it to the meetup.
+[2374.18 --> 2374.68]  That was great.
+[2374.90 --> 2375.68]  That was Optimus Grey
+[2375.68 --> 2376.36]  rocking the Chris
+[2376.36 --> 2376.92]  and the Badger.
+[2377.44 --> 2377.88]  Yeah I thought
+[2377.88 --> 2378.52]  that was super cool.
+[2378.62 --> 2379.28]  He posed for a picture
+[2379.28 --> 2379.88]  with us and we had
+[2379.88 --> 2380.44]  to stand on the
+[2380.44 --> 2381.28]  correct sides as well.
+[2381.38 --> 2381.72]  You know I was
+[2381.72 --> 2382.50]  on the Badger side
+[2382.50 --> 2382.96]  and you were on
+[2382.96 --> 2383.56]  the Chris side.
+[2383.84 --> 2383.98]  Right.
+[2384.04 --> 2384.60]  My daughter thought
+[2384.60 --> 2385.48]  it was so cool
+[2385.48 --> 2386.10]  that people wanted
+[2386.10 --> 2387.02]  to take selfies
+[2387.02 --> 2387.76]  with us.
+[2387.86 --> 2388.06]  So I was like
+[2388.06 --> 2388.96]  really that's the
+[2388.96 --> 2389.66]  thing you think
+[2389.66 --> 2390.24]  is cool?
+[2390.50 --> 2390.80]  Alright.
+[2391.20 --> 2391.60]  Okay.
+[2391.94 --> 2392.44]  Well I thought
+[2392.44 --> 2393.42]  the free donuts
+[2393.42 --> 2394.12]  were pretty cool.
+[2394.36 --> 2395.10]  Linode put on
+[2395.10 --> 2396.04]  a heck of a show
+[2396.04 --> 2396.52]  for us.
+[2396.78 --> 2397.54]  Yeah you know
+[2397.54 --> 2398.62]  Brent and I
+[2398.62 --> 2399.30]  and Wes went
+[2399.30 --> 2400.30]  to grab those donuts
+[2400.30 --> 2401.04]  and that was
+[2401.04 --> 2401.64]  quite the journey
+[2401.64 --> 2402.08]  because it was
+[2402.08 --> 2403.44]  150 donuts
+[2403.44 --> 2404.62]  and it was in
+[2404.62 --> 2405.50]  downtown Denver
+[2405.50 --> 2406.80]  during Friday
+[2406.80 --> 2407.42]  rush hour.
+[2407.54 --> 2407.90]  I don't know
+[2407.90 --> 2408.42]  what we were
+[2408.42 --> 2408.80]  thinking.
+[2409.80 --> 2410.62]  And so at a
+[2410.62 --> 2411.16]  certain point
+[2411.16 --> 2412.12]  I saw a little
+[2412.12 --> 2412.86]  bit of Canadian
+[2412.86 --> 2414.06]  road rage emerge
+[2414.06 --> 2414.60]  out of Brent
+[2414.60 --> 2415.44]  when this truck
+[2415.44 --> 2416.92]  Brent had gotten
+[2416.92 --> 2417.46]  into a battle
+[2417.46 --> 2418.04]  with a truck
+[2418.04 --> 2418.40]  downtown
+[2418.40 --> 2419.86]  and he had
+[2419.86 --> 2420.18]  to kind of
+[2420.18 --> 2420.56]  cut in front
+[2420.56 --> 2420.94]  of the truck
+[2420.94 --> 2421.64]  because a lane
+[2421.64 --> 2422.14]  was ending
+[2422.14 --> 2422.80]  and the truck
+[2422.80 --> 2423.54]  driver never
+[2423.54 --> 2424.16]  forgave him
+[2424.16 --> 2424.74]  for it.
+[2426.00 --> 2426.72]  Does Brent
+[2426.72 --> 2427.40]  get angry?
+[2427.82 --> 2428.12]  I mean
+[2428.12 --> 2428.96]  disgruntled?
+[2429.28 --> 2430.14]  I got slightly
+[2430.14 --> 2430.72]  more aggressive
+[2430.72 --> 2431.42]  in my driving.
+[2431.70 --> 2431.98]  Oh wow.
+[2432.28 --> 2433.06]  It was one
+[2433.06 --> 2433.82]  of those situations
+[2433.82 --> 2434.34]  where you just
+[2434.34 --> 2434.88]  got to get over
+[2434.88 --> 2435.30]  and you got to
+[2435.30 --> 2435.62]  do everything
+[2435.62 --> 2436.10]  you can
+[2436.10 --> 2437.06]  and it wasn't
+[2437.06 --> 2437.60]  too bad
+[2437.60 --> 2438.40]  actually I thought
+[2438.40 --> 2439.52]  but that truck
+[2439.52 --> 2440.28]  decided to
+[2440.28 --> 2441.94]  very aggressively
+[2441.94 --> 2442.74]  pass us
+[2442.74 --> 2443.18]  on the right
+[2443.18 --> 2443.78]  hand side.
+[2443.92 --> 2444.12]  You had to
+[2444.12 --> 2444.94]  work at it too.
+[2445.14 --> 2445.46]  Oh yeah.
+[2445.46 --> 2446.88]  and promptly
+[2446.88 --> 2447.82]  cut us off
+[2447.82 --> 2449.30]  again on the
+[2449.30 --> 2449.70]  left hand side.
+[2449.70 --> 2450.24]  We're just trying
+[2450.24 --> 2450.76]  to make a donut
+[2450.76 --> 2451.06]  run.
+[2451.62 --> 2452.58]  I don't think he
+[2452.58 --> 2453.22]  realized what we
+[2453.22 --> 2453.66]  were trying to
+[2453.66 --> 2454.08]  accomplish.
+[2454.38 --> 2454.72]  I know.
+[2454.96 --> 2455.28]  I know.
+[2455.46 --> 2456.12]  Hey before we go
+[2456.12 --> 2456.54]  I want to say
+[2456.54 --> 2457.30]  thank you to our
+[2457.30 --> 2457.62]  members.
+[2458.00 --> 2459.16]  Our SREs make
+[2459.16 --> 2460.18]  this show possible.
+[2460.80 --> 2461.54]  Selfhosted.show
+[2461.54 --> 2462.62]  slash SRE if you'd
+[2462.62 --> 2463.34]  like to sign up.
+[2463.72 --> 2464.42]  You get a discount
+[2464.42 --> 2465.32]  on our merch
+[2465.32 --> 2466.70]  at jupitergarage.com
+[2466.70 --> 2467.84]  and you get
+[2467.84 --> 2468.50]  access to the
+[2468.50 --> 2469.48]  exclusive post show
+[2469.48 --> 2470.32]  with your own
+[2470.32 --> 2471.08]  RSS feed
+[2471.08 --> 2472.36]  at selfhosted.show
+[2472.36 --> 2473.26]  slash SRE.
+[2473.26 --> 2474.52]  And I want to
+[2474.52 --> 2475.00]  mention you can
+[2475.00 --> 2475.64]  find our sponsor
+[2475.64 --> 2476.38]  at Cloud Guru
+[2476.38 --> 2477.40]  on social media.
+[2477.78 --> 2478.36]  Essentially any
+[2478.36 --> 2479.18]  social media site
+[2479.18 --> 2479.54]  they're just
+[2479.54 --> 2480.44]  slash at Cloud Guru.
+[2480.84 --> 2481.54]  YouTube, Twitter,
+[2481.66 --> 2482.30]  the Facebooks,
+[2482.38 --> 2483.10]  you know, the
+[2483.10 --> 2483.68]  social medias
+[2483.68 --> 2484.60]  slash at Cloud Guru.
+[2485.24 --> 2485.70]  And as you all
+[2485.70 --> 2486.42]  well know by this
+[2486.42 --> 2486.66]  point,
+[2486.82 --> 2487.80]  selfhosted.show
+[2487.80 --> 2488.46]  slash contact
+[2488.46 --> 2489.20]  is the place to
+[2489.20 --> 2489.62]  go to get in
+[2489.62 --> 2490.14]  touch with us.
+[2490.30 --> 2491.32]  You can find me
+[2491.32 --> 2491.82]  on Twitter
+[2491.82 --> 2492.98]  at ironicbadger.
+[2493.20 --> 2493.96]  I'm at Chris
+[2493.96 --> 2494.48]  LAS.
+[2494.94 --> 2495.98]  And I'm at
+[2495.98 --> 2496.70]  Brent Jervais.
+[2497.00 --> 2497.70]  And the show
+[2497.70 --> 2498.34]  is at
+[2498.34 --> 2499.44]  selfhosted show.
+[2499.74 --> 2500.18]  Thanks for
+[2500.18 --> 2500.70]  listening everyone.
+[2500.70 --> 2501.20]  That was
+[2501.20 --> 2502.24]  selfhosted.show
+[2502.24 --> 2503.34]  slash 52.

53： Adventurous Build _summary.txt

@@ -0,0 +1,52 @@
+• Matt from Adventurous Way joins the show to discuss his experience with RV travel and automation
+• He and his wife are building a smart home on 40 acres in Vermont from scratch
+• Discussion about similarities between their projects, including use of Home Assistant and Victron
+• Matt explains how he built his initial smart RV system using a Raspberry Pi and later upgraded to an Intel NUC
+• They discuss how automation and self-hosting can make life more comfortable in small spaces
+• Home Assistant is mentioned as the "gateway drug" for people getting into self-hosting and automation
+• Details about their systems and experiences with boondocking and heating are discussed
+• Challenges in boondocking and the need for power solutions
+• Home automation priorities and implementing auto dump feature
+• Using Victron inverter and Sonoff devices for smart RV control
+• Integrating MQTT data from Victron with Home Assistant
+• Collecting electrical system data in InfluxDB for long-term analysis
+• Gaining insights into battery health and solar panel performance
+• Adding solar power to an RV system and its impact on energy production
+• Graphing location vs. power intake for optimal charging
+• Sharing electrical data with Battleborn battery manufacturers for real-world performance insights
+• Automating breaker tripping prevention using Home Assistant and Victron systems
+• Using MQTT protocol to collect and utilize Victron system data in Home Assistant
+• Discussing the potential for a Victron integration within Home Assistant
+• Exploring open-source software and APIs from Victron, including documentation and coding guides
+• Setting up MQTT and connecting to a ColorGX device
+• Recommending MQTT Explorer as a tool for monitoring MQTT messages in real-time
+• Discussing the use of Homebrew (Brew) on an M1 Mac for installing various applications, including Chrome and VS Code
+• Experiencing difficulties with internet connectivity while traveling and using Little Snitch to block unwanted network activity
+• Comparing internet speeds between a cellular connection and cable internet in an RV
+• Discussing challenges of living in an RV and the importance of efficient online tasks, such as updating Docker containers
+• Announcing that MQTT Explorer is available on multiple platforms, including Linux, Mac, and Windows
+• The untrippable breaker has been the most impactful daily improvement
+• GPS dongle connected to Victron system for location tracking and geofencing
+• Integration with Node.RED, Home Assistant, and NQTT broker for data collection and automation
+• Discussion of Linode's cloud computing services and its benefits for self-hosting projects
+• Plans to self-build a house or live on the 40 acres in Vermont purchased by Matt
+• Purchased 40 acres of raw land in central Vermont with specific requirements for a rural location with fiber internet
+• Building process has started, including installing a driveway and laying groundwork for the house site
+• Prioritizing self-hosting and incorporating smart technology into the new home
+• Current RV is being used as a test lab for various technologies that will be implemented in the new house
+• Planning to build a separate standalone mechanical building for utilities, noise control, and server infrastructure
+• Aiming for a completely net zero house with passive design and Living Building Challenge requirements
+• Inverters and electric grid tie-off points for a large property
+• Running fiber as a backbone between buildings to support high-speed internet and server needs
+• Future-proofing infrastructure with fiber installation
+• Self-hosting servers and media services, including Plex, on-premises and syncing with Starlink
+• Managing redundant systems and ensuring reliability when traveling or leaving a site unattended
+• Determining "good enough" levels of redundancy and component quality (e.g. dual power supplies, SSDs in RAID)
+• Planning for remote server management and redundancy
+• Reviewing current setup on an old super micro board with Java-based IPMI KVM
+• Considering replacement options, including Raspberry Pi and ASRock boards
+• Discussing the importance of reliability and having a plan B in case of system failure
+• Exploring technologies such as Karp for redundancy and load balancing
+• Availability of show notes at cloudguru.com
+• Social media handles: Alex (Ironic Badger), Chris LES, Self Hosted Show
+• Episode reference: episode #53 on selfhosted.show/slash 53

53： Adventurous Build _transcript.txt

@@ -0,0 +1,578 @@
+[0.00 --> 2.32]  Well, I'm pretty excited because I get to geek out this week.
+[2.46 --> 6.98]  Matt from Adventurous Way, a YouTube channel that Alex and I watch, is joining us.
+[7.14 --> 11.02]  And Matt, you've got a ton of videos about RV travel, automation, self-hosting.
+[11.16 --> 17.16]  And just recently, you and the wife bought 40 acres of raw land in central Vermont
+[17.16 --> 22.56]  and are starting the long work of building a smart home from the ground up.
+[22.64 --> 23.54]  Matt, welcome to the show.
+[23.94 --> 24.86]  Thank you so much for having me.
+[25.32 --> 26.12]  Are you crazy?
+[26.12 --> 30.94]  I watch your videos and it looks like years of work ahead of you.
+[31.96 --> 32.56]  It really is.
+[32.62 --> 35.70]  Yeah, this is the start of a pretty long journey.
+[35.84 --> 38.62]  I think we are just at the very beginning of it.
+[38.86 --> 42.12]  And yeah, I think we are probably a little bit crazy.
+[42.96 --> 46.10]  I'm sure you've noticed, Chris, that I've managed to coerce another Brit onto the shows.
+[46.22 --> 50.20]  I wanted to bring the average, you know, raise the standard a bit.
+[50.54 --> 51.56]  Yeah, it wasn't lost on me.
+[51.68 --> 53.28]  It wasn't lost on me at all.
+[53.28 --> 57.06]  But, you know, Alex, there's like a ton of stuff we could talk to Matt about.
+[57.18 --> 59.76]  But I thought maybe we'd start with what he and I have in common.
+[60.18 --> 65.14]  When I first started watching your channel, you were doing a smart RV system similar to mine.
+[65.26 --> 67.60]  Home Assistant, Victron, the whole work.
+[67.74 --> 69.94]  So can you walk us through a little bit of what you built?
+[70.46 --> 74.54]  Yeah, so we've been living full time in our RV now for about three years.
+[74.54 --> 83.58]  We moved out of a perfectly good four bedroom home in the Bay Area, California, and into a 180 square foot box on wheels.
+[84.36 --> 89.30]  So imagine about half the size of the average like master bedroom in the US.
+[89.56 --> 92.10]  And that's been our entire home for the last three years.
+[92.10 --> 96.28]  And so pretty quickly, we realized that we're both technologists.
+[96.48 --> 100.98]  My partner and I are both former software engineers and tech people.
+[101.58 --> 107.20]  We kind of realized there's an opportunity here to use technology to make ourselves more comfortable.
+[107.66 --> 110.52]  And that was really where this whole journey began.
+[110.52 --> 117.32]  And so what started off as just like a hobby, it's pretty hard to have hobbies when you live in such a small space.
+[117.32 --> 121.30]  If they're physical, we obviously don't have a backyard to go and do gardening.
+[121.30 --> 123.50]  And I've given up my woodworking shop and things.
+[123.72 --> 126.64]  So we really focused on digital hobbies.
+[127.24 --> 133.18]  And so although I've been into some elements of self-hosting and tech for many, many years,
+[133.84 --> 139.06]  this for me really was an opportunity to go deep into tech.
+[139.06 --> 141.82]  And the home automation side of things.
+[142.46 --> 148.58]  So starting almost three years ago, I had a Raspberry Pi and I loaded Home Assistant onto it.
+[148.80 --> 150.40]  And that was kind of where I started.
+[151.20 --> 157.46]  And within a matter of weeks, I was already overwhelming the Raspberry Pi.
+[157.76 --> 160.18]  It must have been a Model 3, I guess, back then.
+[161.34 --> 163.44]  Completely overwhelming what it was able to do.
+[164.20 --> 167.60]  And I was like, I think it's time for an upgrade.
+[167.60 --> 172.04]  Again, space, big concern for us here, as you know, living in an RV.
+[172.68 --> 173.96]  And power draw as well, right?
+[174.02 --> 175.08]  And that's the nice thing about the Pi.
+[175.48 --> 175.84]  Yeah.
+[175.98 --> 179.14]  And so the Pi was great because it could run off the DC voltage.
+[179.42 --> 181.90]  And that was something that I wanted to stick with.
+[182.16 --> 185.92]  So we upgraded to an 8th gen Intel NUC.
+[185.92 --> 188.12]  It runs an i3 processor.
+[189.02 --> 201.40]  And because it runs, I think it's like 19 volts that it actually runs on, I was able to avoid using the normal AC power brick and instead run it straight off DC using a DC boost converter.
+[201.40 --> 206.50]  That has been running flawlessly now for almost three years, 24-7.
+[206.88 --> 207.50]  Ah, nice.
+[208.24 --> 209.96]  It's interesting you say that, Matt.
+[210.12 --> 217.02]  I think a few years ago, maybe five plus, Plex was the gateway drug for a lot of people that got them into self-hosting.
+[217.54 --> 219.10]  I know you're a proponent of that as well.
+[219.90 --> 221.98]  Home Assistant is the new gateway drug, don't you think?
+[221.98 --> 223.56]  I think it is.
+[223.80 --> 228.60]  And it's literally the hub of the entire experience in our RV.
+[229.26 --> 232.82]  It is even when we're consuming media, I've got Plex plugged into Home Assistant.
+[233.26 --> 237.02]  And so it really is that kind of entrance point for me.
+[237.40 --> 247.44]  But I think it's becoming so accessible and so easy to get up and running with that it's just attracting more and more people to this kind of lifestyle and this hobby.
+[248.04 --> 249.64]  Well, I have a ton of questions for you, Matt.
+[249.64 --> 252.58]  And in fact, I want to get into some of the details about your system.
+[252.66 --> 255.22]  But I want to mention this episode is brought to you by a Cloud Guru.
+[255.34 --> 258.32]  They are the leader in learning for Cloud, Linux, and other modern tech skills.
+[258.76 --> 261.00]  Hundreds of courses and thousands of hands-on labs.
+[261.32 --> 261.74]  Get certified.
+[262.04 --> 262.36]  Get hired.
+[262.58 --> 265.08]  Get learning at a CloudGuru.com.
+[265.56 --> 274.80]  Matt, something you said there was that it was what struck you was, well, we could use some of this technology to make life more comfortable in our tiny home.
+[275.36 --> 276.92]  That's kind of how I got into it, too.
+[276.92 --> 279.60]  And I'm curious, what was some of your very first automations?
+[279.76 --> 281.74]  Was it around enabling boondocking?
+[281.94 --> 282.64]  Was it around heating?
+[282.78 --> 283.40]  Where did you start?
+[283.84 --> 283.98]  Yeah.
+[284.06 --> 288.04]  So for us, the scarcity of resources was one of our biggest challenges.
+[288.94 --> 291.80]  Much like you, we have battle-borne lithium batteries.
+[292.10 --> 292.96]  We have solar.
+[293.66 --> 294.82]  But they're still finite.
+[295.38 --> 298.90]  In three years on the road, we do not and have never owned a generator.
+[299.52 --> 302.74]  So one of my big first priorities was how do I get power?
+[302.74 --> 306.82]  We prefer to boondock rather than stay in RV parks.
+[307.46 --> 310.82]  I think start of last year, we did 100 days in a row of boondocking.
+[311.18 --> 312.26]  Just totally off-grid.
+[312.64 --> 312.96]  Wow.
+[313.24 --> 313.90]  100 days.
+[313.96 --> 314.70]  That's impressive.
+[314.86 --> 315.52]  Very nice.
+[315.60 --> 315.70]  Yeah.
+[315.76 --> 316.00]  Wow.
+[316.08 --> 322.60]  So when the pandemic first hit, we were just every 10 to 14 days, we would run into town to go and dump our tanks and fill up again.
+[322.60 --> 325.86]  And then back out into the middle of nowhere and carry on.
+[326.16 --> 326.72]  Oh, look at you.
+[326.78 --> 327.52]  You big show-off.
+[327.52 --> 334.24]  So one of the priorities with the home automation was how do I make this more achievable?
+[335.28 --> 343.62]  And for me, I've never got into the scripts so much, just the trigger a thing and then things happen all at once.
+[343.84 --> 350.78]  I was always into the how can I make the RV smarter in the first place so I don't have to interact with it at all.
+[350.78 --> 357.28]  So one of my favorites, I call it the auto dump feature and has nothing to do with dumping tanks.
+[358.06 --> 359.54]  This is all about electricity.
+[360.14 --> 364.28]  And the idea is to say, let's say it's a sunny day outside.
+[365.12 --> 366.16]  It's spring.
+[366.42 --> 367.02]  I'm in the desert.
+[367.28 --> 369.32]  I've got plenty of solar coming in.
+[370.04 --> 371.78]  At some point, my battery is going to fill up.
+[372.22 --> 374.02]  So what do I do with that excess?
+[374.28 --> 375.28]  How can I use it?
+[375.28 --> 385.80]  So I set up an automation that as the batteries reached higher and higher voltage levels and higher and higher percent charge, it would begin to turn on or enable certain devices.
+[386.72 --> 392.04]  So as you've probably noticed, the Victron inverter has a fairly high background power draw.
+[392.30 --> 394.96]  And so we keep it turned off most of the time.
+[395.62 --> 399.52]  Once the batteries reach 80%, I would turn the inverter on automatically.
+[399.52 --> 406.20]  Once the batteries reach 90%, it would switch the fridge over from propane to AC electric.
+[407.10 --> 412.24]  And once the batteries reach 95%, it would switch the electric water heater on.
+[412.86 --> 423.18]  So on a good sunny day, without us doing anything at all, we would end the day with full batteries, a full tank of hot water, and having saved some propane from the fridge.
+[423.72 --> 424.40]  I love that.
+[424.58 --> 425.36]  That's so great.
+[425.48 --> 426.38]  And that's really cool.
+[426.38 --> 432.58]  You must be then going through and replacing those basic DC switches that came with the RV with something smarter.
+[432.98 --> 437.48]  One of the challenges in the RV is nothing is designed for RVs in the smart world.
+[438.02 --> 440.66]  So we don't use a lot of 110 volts.
+[441.10 --> 442.48]  DC is king.
+[443.04 --> 448.42]  And so the Sonoff SV has been my choice for a lot of this and a couple of the other Sonoff devices.
+[448.70 --> 451.26]  The 4chan Pro has been another one I've used.
+[451.26 --> 456.58]  And then a couple of things are running on Sonoff.
+[456.72 --> 462.00]  I think it's the POW R2, the energy monitoring hardwired one, or the Sonoff S31.
+[462.92 --> 465.08]  And those have really been the heart of it.
+[465.32 --> 471.60]  I started off with TASMOTOR running on those and then switched over to ESP Home a little while later.
+[471.94 --> 473.62]  I actually use one of those Sonoff SVs.
+[473.70 --> 475.28]  I'm holding it up to the camera for you both.
+[475.28 --> 477.50]  For my garage doors.
+[477.78 --> 479.82]  And yeah, it's worked absolutely flawlessly.
+[479.92 --> 481.00]  It's got a little relay on it.
+[481.24 --> 483.26]  It runs on low voltage, like you said, Matt.
+[484.02 --> 484.96]  I really like it.
+[485.00 --> 486.84]  I put TASMOTOR on mine, of course.
+[487.98 --> 488.94]  Fantastic little board.
+[488.94 --> 498.52]  And then it sounds like another key piece of insight that's coming into Home Assistant is you are making Home Assistant aware of your electrical system.
+[498.62 --> 502.10]  Sounds like battery state, power generation from solar.
+[502.84 --> 506.36]  So Home Assistant must be getting a lot of information off of your Victron setup.
+[506.52 --> 508.72]  How are you supplying that to Home Assistant?
+[509.08 --> 509.62]  Yeah, you're right.
+[509.62 --> 519.36]  So we are using the Victron CCGX, the Color Control GX, which is one of their family of products that has a built-in MQTT broker.
+[520.08 --> 529.76]  So this is actually one of the original reasons, I guess, that we chose Victron versus some of the other vendors out there that do solar for RVs.
+[530.26 --> 538.62]  We basically shlurp up all of that MQTT data, throw it into Home Assistant, and also then collect it all in InfluxDB as well.
+[538.62 --> 544.20]  And for me, it was actually the data collection side of things that was really why I started this in the first place.
+[544.60 --> 551.10]  We wanted to see the long-term trends of our batteries, of our solar, all these sorts of things.
+[551.84 --> 562.66]  And we've now got, I think, almost three years' worth of data at about a one to ten second resolution across dozens and dozens and dozens of data points on the electrical system.
+[562.66 --> 567.88]  So you're getting real insights to how the health of your batteries are, if they're still delivering the same way.
+[568.04 --> 573.36]  And probably even, like, you could start to see maybe something's wrong with one of our solar panels because of this data.
+[573.76 --> 574.16]  Exactly.
+[574.16 --> 582.36]  So we've used it ourselves to answer questions like, if we added 200 more watts of solar, what would that do to our system?
+[582.98 --> 586.86]  Or how many watts of solar do we need to get through winter at a given latitude?
+[586.86 --> 593.80]  Because we can graph the location of the RV versus the amount of power that we bring in during the day.
+[594.44 --> 594.92]  I love this.
+[594.98 --> 599.72]  You've got to come on board as a road trip consultant for me, you know, running operations.
+[599.72 --> 600.20]  Yeah.
+[600.84 --> 603.86]  So a lot of the stuff that we've done in that sense has been quite selfish.
+[604.12 --> 607.30]  It's informed decisions that we've made ourselves.
+[608.40 --> 613.38]  But I think one of the things that's really excited me the most is being able to share this data with others.
+[613.78 --> 620.08]  So we've actually shared all of our electrical data with Battleborn, who make our batteries, with Dennis, the CEO.
+[620.08 --> 627.52]  And he's then able to look at that data and from that get real-world insight into how their batteries actually perform in the wild.
+[627.52 --> 637.52]  Because no lab can recreate an RV in temperature fluctuations and casually turning on the AC and then boondocking for...
+[638.16 --> 638.86]  A hundred days.
+[639.32 --> 639.70]  Exactly.
+[640.10 --> 642.18]  So we've been able to share all that data with them.
+[642.40 --> 649.20]  And that really helps them to then understand how their batteries perform in different conditions and hopefully then improve their products.
+[649.20 --> 653.66]  Yeah, I could show them how their batteries perform while they're cooking because it's so dang hot here.
+[653.78 --> 662.34]  But something else that strikes me is that you could do is you could watch for the total draw of the RV and prevent tripping a breaker when you're set up to shore power.
+[662.44 --> 665.88]  And you're actually maybe not boondocking, but you're at an RV park or something like that.
+[665.92 --> 668.36]  So there's utilities for when you're not off-grid as well, I would imagine.
+[668.82 --> 672.74]  We actually added that exact automation about 10 months ago.
+[673.00 --> 674.32]  We arrived here in Vermont.
+[674.32 --> 677.72]  We had full hookups and we knew we were going to be here during the winter.
+[678.32 --> 688.60]  And we're only in a 30-amp RV, which means that our main breaker in the RV can only handle 30 amps, which means it's really, really easy for us to trip that breaker.
+[688.76 --> 698.72]  If we ran an electric water heater, an electric space heater, if we then happened to turn on the microwave or electric kettle or something else, that would trip the breaker.
+[698.72 --> 713.70]  So I was able to use a home assistant automation to look at what I'd set the Victron system to allow as the input current, so 30 amps usually, and then deduct from that whatever the current total power draw was.
+[713.70 --> 735.68]  And then if I was exceeding the 30 amps, it would then automatically pause either the electric water heater or the electric space heater so that I can run the microwave or run the electric kettle, because I need my cup of tea, and pause those things until the microwave or the kettle has shut off and then return them back to their original state.
+[735.86 --> 738.90]  And thanks to that, we didn't trip a breaker all winter long.
+[738.90 --> 750.86]  So, Matt, are you telling me that my Color Control GX is collecting all the information I need and I just need to go into the settings and tell it an MQTT endpoint or something?
+[751.06 --> 752.50]  Do I already have it?
+[752.62 --> 753.64]  It's even simpler than that.
+[753.72 --> 756.18]  It actually has a built-in MQTT broker.
+[756.34 --> 756.64]  No!
+[757.18 --> 763.82]  So you can just connect to it on port 1883 and pull the data straight off.
+[764.02 --> 765.36]  You're doing it right now, aren't you, Chris?
+[765.40 --> 765.80]  Be honest.
+[765.80 --> 771.54]  I just don't understand why nobody's built a Victron integration for Home Assistant.
+[771.86 --> 773.26]  Like, get on it, somebody.
+[773.44 --> 774.68]  So I actually looked at doing it.
+[774.80 --> 781.44]  I posted on the Victron forums late last year and said I'd be really interested in making a Victron integration.
+[781.78 --> 783.32]  That was probably your forum post I read.
+[783.94 --> 785.40]  I just, I don't know Python.
+[785.98 --> 794.90]  And so for me, like, there's a decent barrier to entry to go straight from, like, not knowing a language to writing an integration with this massive kind of project.
+[794.90 --> 797.48]  But yeah, I mean, all the data's there on MQTT.
+[797.92 --> 808.06]  It feels like this is a great example of if you had somebody who was a Python developer and had a Victron system, it would be pretty, it wouldn't take long until we had an integration.
+[808.26 --> 811.40]  But it's just those two paths have not yet crossed.
+[811.64 --> 817.90]  But these Victron systems are crazy popular in van builds, bus builds, modern RVs.
+[817.90 --> 821.24]  RVs, like, this is going to be, these things are going everywhere.
+[821.52 --> 822.96]  And Victron makes some great stuff.
+[823.32 --> 823.78]  They really do.
+[823.92 --> 829.34]  And one of the things that I like the most about Victron is they are open sourcing nearly all of their software.
+[829.90 --> 834.32]  So all the APIs they use are all completely publicly documented.
+[834.54 --> 836.76]  But all the source code is also there as well.
+[836.88 --> 837.30]  Hell yeah.
+[837.30 --> 838.68]  And you'll like this one.
+[839.24 --> 848.80]  They've even got a literal how-to guide on GitHub along with all the software you need to run the CCGX software on a Raspberry Pi.
+[849.16 --> 850.20]  Yeah, I really like that.
+[850.22 --> 853.62]  I know some of their boxes internally are running Linux, too, which I think is just great.
+[854.18 --> 855.58]  I'm a huge fan of that as well.
+[855.86 --> 859.16]  We should reach out to Victron and have them on the show.
+[859.62 --> 860.04]  We should.
+[860.14 --> 860.42]  You're right.
+[860.42 --> 864.42]  I should give them enough publicity on there for heck's sake.
+[865.32 --> 866.02]  But yeah.
+[866.36 --> 866.68]  All right.
+[866.72 --> 867.06]  Well, yeah.
+[867.12 --> 871.66]  So I am setting up MQTT and pointing it at my ColorGX right now.
+[872.02 --> 875.88]  So I'm going to get that going.
+[876.46 --> 881.38]  Top tip, if you want to, my favorite MQTT kind of tool is something called MQTT Explorer.
+[881.72 --> 882.38]  Ah, OK.
+[882.58 --> 886.64]  This thing lets you log into a broker and see all the messages that it's getting in real time.
+[886.98 --> 889.34]  Oh, and is, I see, it's a Mac app.
+[889.34 --> 890.28]  Is that a Mac app?
+[890.96 --> 894.22]  Brew install MQTT-explorer, I think.
+[894.58 --> 895.16]  No kidding.
+[895.46 --> 895.72]  Really?
+[895.88 --> 896.08]  OK.
+[896.32 --> 900.60]  You can actually, so you can use Brew to install practically everything these days.
+[901.08 --> 904.12]  When I set this, I got an M1 Mac about a month ago.
+[904.84 --> 914.50]  And I've religiously used Brew for absolutely everything, including Chrome, VS Code, Audacity, everything.
+[914.80 --> 914.92]  Yeah.
+[915.12 --> 916.58]  I legitimately had no idea.
+[916.72 --> 917.10]  No, I know.
+[917.10 --> 920.36]  It's come a really, really long way in the last five years or so.
+[920.92 --> 921.06]  Yeah.
+[921.16 --> 926.54]  You know, I have to say, you know, my Mac experiment here on the road trip has been, it's been good.
+[926.54 --> 936.72]  I mean, once I got, and Matt, I don't know if you've ever run into this, but I had this problem where like NSURL session D just would consume all of my bandwidth.
+[936.72 --> 939.22]  Because I was in a pretty crappy signal area.
+[939.22 --> 942.22]  And I had like hardly any signal.
+[942.22 --> 948.22]  And I'd fire up the Mac and it would just sit there and run and run and run in part because the download speeds were slow.
+[948.30 --> 948.98]  So it took longer.
+[948.98 --> 950.82]  And I'm sitting there trying to do a live show.
+[952.90 --> 953.72]  It's just horrible.
+[953.98 --> 959.28]  So once everybody yelled at me to try Little Snitch out again, which I had tried out a hundred years ago.
+[959.70 --> 966.84]  I gave Little Snitch a go and set up an outbound firewall for, you know, and blocked basically everything except for the apps I'm using to do the shows.
+[966.84 --> 968.60]  It's been pretty solid since then.
+[969.10 --> 971.30]  Seemed a little hacky, but sure works.
+[971.62 --> 971.70]  Yeah.
+[971.70 --> 983.04]  There's a load of little tricks like that you can use when you're on a really constrained bandwidth situation just to make sure that your devices are only doing the things you really, really want them to do.
+[983.14 --> 985.94]  And not just those like background tasks that can wait.
+[986.22 --> 989.24]  Are you doing any of that at the firewall level now?
+[989.24 --> 992.20]  The big one for us is actually just the ad blocker.
+[992.28 --> 995.72]  Just having AdGuard Home on there just cuts out so much stuff.
+[995.88 --> 1003.34]  I will say we are completely spoiled having been running on like bonded cellular connections for the past kind of couple of years.
+[1003.78 --> 1008.38]  We actually have cable internet plugged into the side of our RV.
+[1008.68 --> 1011.46]  So we're sitting on 400 meg cable internet right now.
+[1012.02 --> 1012.16]  Nice.
+[1012.30 --> 1013.10]  Yeah, that's a treat.
+[1013.42 --> 1013.56]  Yeah.
+[1013.56 --> 1019.48]  Yeah, the one nice thing about this spot we are in Tucson right now is we have pretty dang good signal.
+[1019.64 --> 1023.56]  It's not like that good, but you know, it's not wired good, but it's been pretty good.
+[1023.80 --> 1028.50]  So that's been nice because some points on this trip I have just had horrendously bad signal.
+[1029.48 --> 1031.60]  It's amazing what you can actually still get done.
+[1032.00 --> 1041.52]  We actually found that in all our time kind of boondocking around the southwest, I think it was only one spot we ended up in where we didn't have usable cellular internet.
+[1041.52 --> 1043.34]  And we sort of knew that going into it.
+[1043.38 --> 1046.80]  So we just made sure that all the work we had to do, we didn't need anything online.
+[1047.56 --> 1057.50]  But a big part of living in the RV is you find all of these challenges, I think, a lot quicker than when you live in a house.
+[1057.72 --> 1058.10]  No kidding.
+[1058.46 --> 1058.60]  Yeah.
+[1058.78 --> 1063.86]  And a good one for us is when I want to update our website, let's say I've got a new Docker container I want to push.
+[1064.68 --> 1070.04]  If you're sitting in an office, you think nothing of going Docker push and uploading that image.
+[1070.04 --> 1071.02]  Of course, right.
+[1071.02 --> 1079.46]  I spent a long time optimizing hours so that it was pushing just the tiniest little delta of that layer at the top that had to change.
+[1079.86 --> 1082.18]  And it was otherwise as static as possible.
+[1082.56 --> 1084.14]  And all these little things you find.
+[1084.52 --> 1085.20]  That's a great point.
+[1085.38 --> 1089.68]  It's like, boy, sometimes updating Docker images takes freaking forever over cellular.
+[1089.96 --> 1092.00]  Like, it's clearly not many people doing that.
+[1092.80 --> 1095.22]  Hey, Alex, hot, hot update here.
+[1095.22 --> 1100.88]  It looks like MQTT Explorer is available for Linux as an app image and a snap.
+[1101.24 --> 1105.40]  So you can get it on GNU slash Linux and a Mac and the App Store and a DMG.
+[1105.56 --> 1106.38]  And, of course, on Windows.
+[1106.38 --> 1115.40]  I think I've spent more time nodding and smiling and looking impressed in the last 20 minutes than I have in the last 20 months.
+[1115.76 --> 1118.04]  Some seriously, seriously cool stuff.
+[1118.12 --> 1126.38]  I wonder how much we could apply to people's houses and make people more cognizant of the energy they're using and maybe make that into some kind of sustainable movement.
+[1126.38 --> 1126.98]  Movement.
+[1127.88 --> 1128.88]  Really interesting.
+[1129.04 --> 1131.98]  So what's your favorite automation that you've done?
+[1132.76 --> 1137.70]  The untrippable breaker has probably been the most impactful day to day.
+[1138.06 --> 1147.94]  One of the ones that was so simple yet made a huge difference to our quality of life was we have a GPS dongle that we have plugged into the Victron CCGX,
+[1148.18 --> 1152.18]  which means the Victron system is aware of the trailer's location at any point in time.
+[1152.18 --> 1158.62]  It can use that for some geofencing and things through the Victron software, through their dashboard.
+[1159.72 --> 1165.30]  But once you then plug that GPS dongle in, it's then also exposing its data on the NQTT broker,
+[1165.56 --> 1173.94]  which means I can then collect that data with Node.RED and Home Assistant, about maybe 18 months or so ago, I guess,
+[1174.52 --> 1180.08]  added a new service allowing you to set the home location through the Home Assistant API.
+[1180.08 --> 1185.94]  So then as we're driving down the road, every 60 seconds, Node.RED will ping Home Assistant and say,
+[1186.38 --> 1187.50]  oh, by the way, we're now here.
+[1188.04 --> 1191.76]  And that way, as we cross time zones or state borders or whatever,
+[1192.52 --> 1194.70]  Home Assistant always has our latest information.
+[1195.70 --> 1197.90]  Schedules based on time all continue to work.
+[1198.62 --> 1201.06]  Yeah, that was a real simple one, but really worked well.
+[1201.64 --> 1204.36]  I know that's a problem you've been trying to solve, Chris, for some time now.
+[1204.74 --> 1205.56]  Yeah, it's so silly.
+[1205.56 --> 1212.64]  Here I am in Tucson right now, and my evening automation for lighting is based on the sunset in the Pacific Northwest.
+[1213.22 --> 1216.22]  And I used to go in there and update it, but I just kind of stopped.
+[1216.28 --> 1217.52]  I just kind of said, ah, screw it.
+[1217.54 --> 1218.56]  I'm done updating it.
+[1218.62 --> 1219.34]  It's close enough.
+[1219.42 --> 1220.58]  It's about an hour off.
+[1222.78 --> 1224.24]  So I should totally look into that.
+[1225.94 --> 1227.82]  Linode.com slash SSH.
+[1227.90 --> 1232.56]  Go there to get $100 in 60-day credit on your account and go there to support this show.
+[1232.56 --> 1234.72]  You know, Linode started in 2003.
+[1234.84 --> 1238.98]  It's one of the very first companies in cloud computing before we called it cloud computing.
+[1239.18 --> 1242.70]  And now, 18 years later, they haven't launched a trillion different services.
+[1242.86 --> 1245.68]  They've remained focused in building out their core service.
+[1245.96 --> 1251.50]  Not only do they have the best servers in the business with incredible performance, fast networking, 11 data centers around the world,
+[1251.50 --> 1260.42]  but they've added services that matter, things that impact the quality of your life, like DDoS protection, VLAN support, a powerful DNS manager,
+[1260.82 --> 1266.00]  and, of course, block storage and S3-compatible object storage, which I absolutely love.
+[1266.36 --> 1270.92]  But I know there's people, you know, like Alex, who like things like the Terraform support and the Kubernetes support.
+[1271.74 --> 1272.42]  Yeah, yeah, yeah.
+[1272.44 --> 1274.16]  I'm sure that's great for some of you out there.
+[1274.34 --> 1275.12]  So shoot me.
+[1275.12 --> 1284.70]  But what I like about Linode is they have really just remained focused on building something really great for those of us who want something fast and reliable.
+[1285.02 --> 1289.92]  And then they back that with the best customer support in the business, phone, ticket, email, even social.
+[1290.02 --> 1291.06]  They're going to take care of you.
+[1291.44 --> 1293.02]  And there's tons of one-click deployments.
+[1293.12 --> 1296.22]  If you just want to get started with something, that can be a great way to learn.
+[1296.60 --> 1299.96]  You can also just DIY, which is often the way I prefer to go.
+[1299.96 --> 1306.78]  Or sometimes they'll do something in the middle where I'll deploy a base system that has just the runtime for the container information.
+[1306.94 --> 1309.48]  I'll install all that junk that you'd normally have to set up.
+[1309.58 --> 1311.06]  And it has the right repos.
+[1311.16 --> 1313.62]  You're getting the right versions of the packages and the GPG keys.
+[1313.92 --> 1315.34]  And then we'll just build on top of that.
+[1315.58 --> 1318.14]  And that takes like, I don't know, eight seconds to deploy.
+[1318.26 --> 1319.10]  It's pretty fast.
+[1319.14 --> 1319.76]  It's pretty amazing.
+[1320.20 --> 1322.48]  So go over to linode.com slash SSH.
+[1322.56 --> 1323.64]  Get that $100.
+[1324.10 --> 1326.36]  Support the show and see what we've been talking about.
+[1326.36 --> 1330.12]  Every time we're working on a project, we'll try something out on Linode real quick.
+[1330.82 --> 1332.38]  It's a great way to R&D stuff.
+[1332.60 --> 1334.78]  And, you know, that $100 can help you do that as well.
+[1335.16 --> 1336.48]  So you've got to go check it out for yourself.
+[1336.60 --> 1340.70]  Take advantage of that $100 and see why Linode is better than the rest.
+[1340.78 --> 1343.62]  There's a lot of choices out there, but nobody does it like Linode.
+[1344.00 --> 1346.12]  Linode.com slash SSH.
+[1348.66 --> 1349.28]  Right then.
+[1349.38 --> 1356.08]  So the ultimate conclusion of self-hosting, at least in my opinion, is probably to self-build, you know, a house.
+[1356.36 --> 1358.00]  Or somewhere you're going to live, right?
+[1358.84 --> 1364.08]  Tell us a little bit about your plans, Matt, for the 40 acres in Vermont that you've just bought.
+[1364.70 --> 1364.98]  Yes.
+[1365.14 --> 1369.96]  So I am, like you, sort of a Brit here in the US.
+[1370.28 --> 1374.56]  And as we've been traveling around the US, we've been looking for where we might want to live one day.
+[1375.14 --> 1380.40]  We don't have family in the US, so we're really free to kind of choose wherever it is we want to live.
+[1380.40 --> 1383.74]  And we have spent a lot of time in a lot of different places.
+[1383.84 --> 1386.60]  We've eventually settled on Vermont as a place.
+[1387.52 --> 1396.98]  So about two or three months ago, we closed our sale or our purchase on 40 acres of completely raw land in central Vermont.
+[1397.86 --> 1401.88]  And when I say raw land, this is literally like trees and dirt.
+[1402.14 --> 1403.30]  There really is nothing there.
+[1403.30 --> 1404.66]  It's a hill with some trees on it.
+[1404.84 --> 1405.90]  You know, you can say it.
+[1405.90 --> 1406.86]  You can be honest.
+[1407.30 --> 1408.70]  It's a hill with some trees on it.
+[1409.74 --> 1410.70]  It really is.
+[1410.90 --> 1412.34]  And there is not a lot there.
+[1412.64 --> 1416.14]  But when we went into this, we had some very specific requirements of what we wanted.
+[1416.74 --> 1418.58]  We didn't want to be in a city or a town.
+[1418.66 --> 1419.92]  We wanted to be somewhere more rural.
+[1419.92 --> 1426.52]  And one of the things that made that requirement a little bit more challenging is we said a must-have is fiber internet.
+[1427.12 --> 1433.54]  So even though we're in the middle of nowhere in central Vermont, we will have 800 meg symmetric fiber to the property.
+[1434.08 --> 1434.48]  You bastard.
+[1434.92 --> 1436.02]  Good for you, man.
+[1436.20 --> 1436.90]  Nicely done.
+[1438.06 --> 1439.48]  In the woods with fiber?
+[1439.62 --> 1440.26]  Yes, please.
+[1440.76 --> 1441.08]  Yeah.
+[1441.24 --> 1443.68]  So we are now at the start of this journey.
+[1443.98 --> 1446.24]  Last week, we had our driveway put in.
+[1446.24 --> 1453.40]  We're building the house site about 1,000 feet back from the road, and building that driveway was just beyond what Diana and I could possibly take on.
+[1453.84 --> 1454.10]  I don't know.
+[1454.16 --> 1455.46]  I've been watching your videos, dude.
+[1455.56 --> 1459.12]  You have been felling trees like a proper lumberjack.
+[1459.42 --> 1460.74]  It's really impressive.
+[1461.36 --> 1463.18]  There's a lot of new skills that we're picking up.
+[1463.52 --> 1475.88]  It's kind of surreal to, like today, I was out there with a chainsaw working on the property and then came home writing a blog post, compiling some stuff and working on some programming and some automations and things.
+[1475.88 --> 1480.38]  It's a very surreal kind of contrast, I guess, between the two things.
+[1480.74 --> 1482.16]  What a cool existence there, huh?
+[1482.50 --> 1483.60]  Yeah, we have a lot of fun doing it.
+[1483.96 --> 1490.82]  And how great that you have the RV there with you with all this stuff kind of done and now taking care of itself so you can focus on other stuff.
+[1491.10 --> 1491.74]  Yeah, exactly.
+[1491.96 --> 1502.38]  And in many ways, this house that we want to build, it should probably go without saying that we want to have a load of smart technology in there and things and obviously self-host a lot of things inside there.
+[1502.38 --> 1508.38]  The RV in many ways has been our test lab and still continues to be our test lab for a lot of those things.
+[1508.88 --> 1520.48]  So even though we're running with just like one little Intel NUC and could serve that all with like a little travel router and would probably be fine in here, we sort of push the boundaries to learn some of the things we might need for the house.
+[1521.06 --> 1521.90]  The RV is staging.
+[1522.32 --> 1523.34]  It basically is, yeah.
+[1523.34 --> 1529.22]  I'm sure you're already daydreaming of ideas for the new house, but this is something you get to build from scratch.
+[1529.34 --> 1532.32]  So I imagine you're thinking Ethernet throughout.
+[1532.54 --> 1535.04]  You're already picturing a spot where you'll probably run a server.
+[1535.18 --> 1540.90]  Walk us through a little bit of what you're now considering now that you got a crack to build something from scratch, even if it is a bit off.
+[1541.34 --> 1542.40]  I'm learning so much.
+[1542.46 --> 1547.24]  And I think the community around the self-hosted Discord and things has been a fantastic resource already.
+[1547.24 --> 1551.20]  As I learn more, I keep evolving my plans.
+[1551.44 --> 1564.40]  But some of the things that I've picked up so far are things like if you want to run your own hardware, there's usually a tradeoff of like heat and noise and cost and power efficiency in these things.
+[1565.06 --> 1568.12]  We've learned so much about resource management in the RV.
+[1568.28 --> 1570.20]  We want to have a completely net zero house.
+[1570.20 --> 1581.64]  We're trying to build a passive house and hit the living building challenge, which are a set of requirements that basically mean a very, very high quality, sustainable, comfortable home.
+[1582.08 --> 1586.10]  How do I now then host servers and things within that is kind of the challenge.
+[1586.84 --> 1593.54]  So one of the things that we're going to do because we're self-building, the priority is to get utilities onto the property.
+[1593.54 --> 1603.96]  So electricity and fiber, bring those up the driveway, make sure we've got our solar and our batteries installed, bring the well truck up and dig a well, all those sorts of things.
+[1604.28 --> 1606.16]  I love that water came after internet.
+[1606.50 --> 1607.46]  I noticed that too.
+[1608.04 --> 1612.92]  Someone asked us a few days ago if we had a phone line at the property and I'm like, I have no idea.
+[1613.12 --> 1613.98]  I have never checked.
+[1614.94 --> 1616.50]  No, why would you?
+[1616.64 --> 1618.36]  Yeah, it's gone now.
+[1618.36 --> 1625.54]  But no, so because we need to bring those things on and get them done quickly, most people would put those in a basement.
+[1626.28 --> 1629.12]  But to have a basement implies you already got a house and we don't.
+[1629.66 --> 1645.24]  So we're actually going to build a separate standalone mechanical building, bring all of the utilities into there, which gives us this big advantage that we've then got a separate building where noise and environmental controls can be tailored to whatever we want inside.
+[1645.24 --> 1649.12]  And that's where we're going to run all of our servers and switches and all that kind of stuff.
+[1649.26 --> 1651.20]  And it can be as loud as it wants to be.
+[1651.84 --> 1652.52]  It doesn't matter.
+[1652.90 --> 1654.96]  We can then have a separate building for that.
+[1655.58 --> 1655.60]  Right.
+[1655.64 --> 1657.14]  With an ethernet cable going to the house.
+[1657.66 --> 1664.40]  So that's where you're going to put all your solar batteries and inverters and electric grid tie off points.
+[1665.22 --> 1665.66]  Exactly.
+[1666.26 --> 1668.28]  So it'll have as much power as it needs.
+[1668.28 --> 1675.78]  We're thinking because the property is quite large, the distances between some of the buildings could also therefore be quite large.
+[1676.08 --> 1679.02]  For example, we want to run cameras along the driveway.
+[1679.56 --> 1682.34]  We're sort of pushing the limits of what ethernet can do.
+[1682.58 --> 1693.90]  So we're then probably going to run fiber as a backbone between the buildings and run fiber from the road to the house site and then our own fibers back down to the road and then tap in there.
+[1694.46 --> 1694.94]  Might as well.
+[1694.94 --> 1700.90]  And at this stage, and if you're building this property in 2021, actually fiber does seem like a pretty smart way to go.
+[1700.98 --> 1702.12]  It sort of future proofs it a bit.
+[1702.54 --> 1703.06]  Yeah, exactly.
+[1703.34 --> 1706.58]  And it's one of those things where we have a YouTube channel.
+[1706.92 --> 1709.54]  We're moving around big media files all the time.
+[1710.52 --> 1716.60]  And so having an ability to do that at greater than one gig speed is something that we would actually really find valuable.
+[1717.26 --> 1718.94]  Can I rent some space in your mech room?
+[1720.88 --> 1721.06]  Yeah.
+[1721.34 --> 1722.92]  Forest data center, colo hosting.
+[1723.02 --> 1723.80]  I can see it now.
+[1723.80 --> 1725.76]  Vermont Rural, yeah.
+[1726.00 --> 1726.22]  Yeah.
+[1726.32 --> 1727.64]  What did we coin it on Discord?
+[1727.84 --> 1729.80]  VT Rural, like AWS do.
+[1731.76 --> 1732.72]  That's pretty great.
+[1733.30 --> 1738.76]  That sounds like almost exactly, although at a larger scale and distance than what I had vision.
+[1738.76 --> 1749.12]  My ultimate goal for RV Lady Joops would be to park her on a piece of property that we've bought with a shed that has solar.
+[1749.32 --> 1749.98]  It has the inverter.
+[1750.10 --> 1750.80]  It has the batteries.
+[1751.64 --> 1753.04]  Maybe it has a washer and dryer in it.
+[1753.04 --> 1761.28]  And it has some on-premises servers that have been, you know, theoretically syncing over Starlink or something with media ready to go or whatever.
+[1761.60 --> 1766.16]  And I love the idea of separating out the noisy stuff into its own building.
+[1766.38 --> 1767.52]  I mean, why not?
+[1767.60 --> 1769.84]  That's such a great way to go.
+[1769.84 --> 1774.22]  And so I imagine you're considering a whole new generation of home assistant build.
+[1774.30 --> 1775.82]  You're not going to take the one out of the RV.
+[1775.96 --> 1776.80]  You're going to leave that.
+[1776.92 --> 1778.62]  And I would imagine a whole new build.
+[1779.02 --> 1779.18]  Yeah.
+[1779.40 --> 1782.30]  And this is an area now that I'm learning so much about.
+[1782.40 --> 1786.90]  The hardware side of running servers is pretty new to me.
+[1786.90 --> 1798.14]  And so although I'm comfortable, like, with the concepts, the specifics of exactly what to run is all new, but you actually touch on something there that's a real challenge that I'm battling with.
+[1798.42 --> 1802.72]  The concept of self-hosting is that you have your own little private island of stuff.
+[1803.42 --> 1807.52]  It doesn't matter what goes on elsewhere, out in the cloud or whatever.
+[1808.12 --> 1811.60]  You are insulated from that because you have your own little private island.
+[1812.26 --> 1816.26]  Well, when we have a house, we sort of then have two islands.
+[1816.26 --> 1817.00]  Mm-hmm.
+[1817.36 --> 1819.36]  You have things like take Plex as an example.
+[1819.82 --> 1824.70]  Do I run Plex in the house, in the RV, both?
+[1825.02 --> 1827.22]  Like, how do I sort of manage those things?
+[1827.54 --> 1827.74]  Right.
+[1828.02 --> 1828.38]  In there.
+[1828.56 --> 1828.86]  Yes.
+[1829.16 --> 1829.40]  Yeah.
+[1829.70 --> 1832.58]  So that's an area for me that's, I think, really exciting.
+[1833.00 --> 1835.36]  There's some places where it's a huge asset, like backups.
+[1835.64 --> 1835.84]  Great.
+[1836.06 --> 1837.92]  I've now got a really easy way to do that.
+[1838.22 --> 1841.46]  But for things like media sharing, do I have two copies?
+[1841.90 --> 1843.06]  It becomes tricky.
+[1843.06 --> 1867.24]  And then there's the angle as well of, for you in particular, I think this will be a unique challenge, is when you are driving around in your RV for potentially six months and you're leaving the rural pad empty for six months, you want to make sure that that stuff is reliable and has decent redundancy and all that kind of stuff.
+[1867.24 --> 1873.70]  And I think one of the things that I've heard you struggling with, you sort of brought up on the Discord, is how good is good enough?
+[1873.82 --> 1875.80]  And do I need to have dual power supplies?
+[1876.18 --> 1883.38]  And, you know, how many SSDs do I need to put in RAID to make sure that that doesn't, you know, kick things over and that kind of thing?
+[1883.38 --> 1885.16]  So there's a lot to consider.
+[1885.72 --> 1889.70]  And I'll add to that, Alex, you know, lesson learned here.
+[1889.78 --> 1891.46]  I thought I had a fairly good setup.
+[1891.88 --> 1903.16]  And as I'm on the road at this point, my main server at the studio is offline, which does a ton of lifting for me and then syncs the results to the RV.
+[1903.16 --> 1909.22]  And I feel like I'm, like, operating with one hand tied behind my back while that server's down.
+[1909.28 --> 1912.82]  And now I'm running through my head of, like, what am I going to do to rebuild that?
+[1912.86 --> 1914.62]  Because it really, it is a tricky problem.
+[1914.62 --> 1919.52]  And this is on, you know, a pretty nice actual server box.
+[1920.24 --> 1921.70]  It's a nice little box.
+[1922.14 --> 1930.50]  See, the thing is, I don't think we really fully admit to ourselves just how much light tinkering we do on the average week to these servers to keep them tended,
+[1930.50 --> 1937.14]  to keep the, you know, the leaves in the correct space, you know, to coin a gardening kind of analogy, you know?
+[1937.68 --> 1942.10]  I probably SSH into my server just out of habit, well, at least once or twice a day.
+[1942.20 --> 1943.62]  I don't really know why sometimes.
+[1943.68 --> 1944.20]  I just do.
+[1945.90 --> 1948.54]  Yeah, I mean, you touched on it there with the dual PSUs.
+[1948.54 --> 1954.38]  And I would just say, imagine the situation where you don't have physical access to your server,
+[1954.62 --> 1958.14]  nor would anybody else have physical access to your server for three months.
+[1958.14 --> 1963.46]  How do you give yourself the best chance of being okay and everything working?
+[1963.82 --> 1969.44]  I've gone through exactly this this week, because as you both know, I'm going back to England at the weekend.
+[1970.14 --> 1972.46]  It will be probably the day after this airs, actually.
+[1972.88 --> 1981.78]  And the server that lives in England, for me, has been running on an old super micro board with a Java-based IPMI KVM built in.
+[1982.32 --> 1985.88]  Works okay, but I prefer it was a little more modern, that kind of stuff.
+[1985.88 --> 1991.84]  And I thought to myself, could I just make do by taking in a Raspberry Pi 4 over there and put Pi KVM on it?
+[1991.96 --> 1999.68]  And I'm like, no, actually, I need this to be 100% as close as is possible, reliable.
+[2000.16 --> 2007.20]  Because the last thing I want to do is have to call my dad up and say, hey, can you go and push this widget into this particular orifice?
+[2007.20 --> 2012.82]  And, you know, wave your hands at three o'clock on Sunday, you know, and make it work.
+[2013.64 --> 2019.72]  So I've bought a new ASRock board, which I've written a blog post about, which I'll put a link to in the show notes.
+[2020.08 --> 2023.46]  I think that might be the perfect media server motherboard for me moving forward.
+[2023.78 --> 2024.30]  We'll see.
+[2024.88 --> 2027.42]  But there's just so much to consider.
+[2027.42 --> 2034.82]  And I think you have to get to a point where you're like, okay, I'm willing to risk a single power supply in this system.
+[2034.94 --> 2038.90]  If that goes boom, okay, what's my plan B?
+[2039.24 --> 2046.66]  You know, my plan B might be Linode, something like that, with some ZFS datasets replicated or something like that.
+[2047.20 --> 2053.10]  It's too bad about the Pi KVM, though, because that was one of my thoughts, was if I had Pi KVM at the studio,
+[2053.10 --> 2055.48]  I could at least see what's going on on the console right now.
+[2056.10 --> 2058.22]  But really, an IPMI system would be better.
+[2058.80 --> 2066.30]  I was actually thinking, although I don't really know how to pull it off, is like a redundant Pi KVM system or a redundant Pi system for WireGuard.
+[2067.22 --> 2073.06]  When I'm back, when I do get back to Washington, addressing that redundancy is one of my to-do items.
+[2073.24 --> 2075.10]  Because I know exactly what you mean, Matt.
+[2075.14 --> 2079.20]  It's like I'm sort of helpless down here in Tucson when the server's up in Seattle.
+[2079.20 --> 2084.48]  Yeah, I mean, one of the technologies I've been researching and playing with some more recently is Karp.
+[2085.28 --> 2093.50]  So this gives you essentially the ability to have two devices that can fight between themselves, let's say, for an IP address on the network.
+[2094.20 --> 2096.16]  So OpenSense supports this out of the box.
+[2096.26 --> 2098.96]  You can run two separate machines with OpenSense on.
+[2099.64 --> 2104.00]  And if one of them dies, the other will automatically kind of pick up and run with that.
+[2104.68 --> 2108.34]  And maybe there's a similar thing you can do with Raspberry Pis with other services.
+[2108.34 --> 2112.36]  So you can have essentially a redundant Raspberry Pi sitting there idle.
+[2112.86 --> 2118.86]  And if the first one drops off the network for any reason or just doesn't respond, the second one would pick up.
+[2119.18 --> 2122.54]  But you've got this vision of two fish flopping around on the deck fighting each other.
+[2125.22 --> 2125.66]  Right?
+[2126.88 --> 2127.74]  It might be fun.
+[2127.86 --> 2128.76]  That could be good to watch.
+[2129.44 --> 2135.62]  Well, Matt, there's so many things we could talk about, but we should probably leave some of it for your YouTube channel.
+[2135.62 --> 2139.12]  But thank you for coming on the show today and chatting with us about some of this.
+[2139.24 --> 2143.92]  And best of luck to you and the wife building your new home.
+[2144.08 --> 2145.62]  I think it's going to be quite the project to watch.
+[2145.74 --> 2146.20]  Thank you so much.
+[2146.28 --> 2146.42]  Yeah.
+[2146.46 --> 2148.48]  And I'm looking forward to learning a lot more.
+[2148.62 --> 2152.22]  And I've been binging all of the podcasts recently.
+[2152.34 --> 2156.12]  So over the last three and a half weeks, I've just got through all 50-something episodes.
+[2156.12 --> 2160.24]  I'm looking forward to learning a lot more from the group and the Discord as well.
+[2160.58 --> 2160.80]  Yes.
+[2160.88 --> 2161.94]  Good plug for the Discord there.
+[2162.04 --> 2163.68]  Selfhosted.show slash Discord.
+[2164.04 --> 2164.64]  You can go over there.
+[2164.70 --> 2167.62]  Also, if you want to give us an email, there's selfhosted.show slash contact.
+[2168.04 --> 2172.52]  And if you want to find more of Matt, you can go and search on YouTube for Adventurous Way.
+[2173.00 --> 2179.50]  And we'll have a link to Matt's YouTube channel in the show notes as well as Instagram and other things like that.
+[2179.50 --> 2181.10]  Big thanks for listening, everybody.
+[2181.58 --> 2187.46]  Huge thanks, actually, to our site reliability engineers over at selfhosted.show slash SRE.
+[2188.36 --> 2190.48]  Loads of you have been buying the Chris and the Badger t-shirts.
+[2190.62 --> 2192.32]  I think we're going to be taking those down soon.
+[2192.70 --> 2194.12]  Uh-oh, better go get them soon.
+[2194.48 --> 2199.08]  Do feel free to go over there and give those a quick once-over before they've gone for good.
+[2199.38 --> 2201.44]  Yep, that's at jupytergarage.com.
+[2201.54 --> 2204.28]  And also, go check out our friends at A Cloud Guru.
+[2204.28 --> 2210.12]  They have a course on setting up, learning, configuring, and managing Linux web services.
+[2210.60 --> 2212.46]  Apache, Nginx, and Squid.
+[2212.60 --> 2217.94]  Yeah, reverse proxy servers as well as HTTPS, SSL stuff, load balancing, all of that goodness.
+[2218.50 --> 2219.92]  Linux web services with the Cloud Guru.
+[2220.08 --> 2223.00]  We'll have a link in the show notes, or you can find them at a cloudguru.com.
+[2223.14 --> 2224.52]  You can find Alex on Twitter.
+[2224.62 --> 2225.76]  He's at Ironic Badger.
+[2225.86 --> 2226.90]  I'm at Chris LES.
+[2227.02 --> 2229.54]  And the show, the whole show, it's at Self Hosted Show.
+[2229.84 --> 2230.94]  A big thanks for listening, everybody.
+[2230.94 --> 2233.56]  That was selfhosted.show slash 53.
+[2234.28 --> 2236.04]  중纸

54： Ultimate Off-Site Setup _summary.txt

@@ -0,0 +1,65 @@
+• The speaker returns to England after a pandemic-related delay
+• They discuss their poor internet connection at their mother-in-law's rural home
+• The speaker's family travels from the East Coast to London, facing a delayed flight due to wind conditions
+• The speaker recounts a humorous anecdote about accidentally using an expired passport for travel documents, causing a day of stress and explanation to their family
+• They reflect on their own fault in the mistake and acknowledge opportunities for others to have helped them
+• Discussion of a recent flight on a Boeing Dreamliner
+• Reflections on traveling with family, including a new baby and adjusting to life in the UK after emigrating
+• Noticing a lack of culture shock or adjustment period upon returning to the UK
+• Discussing technology and home setup preparations for trips and self-hosting infrastructure
+• Mention of off-site backup opportunities and re-evaluating digital setups during trips
+• Replaced motherboard in UK server with an ASRock Rack board
+• Reason for replacement was old Supermicro 1366 LGA socket Xeon and requirement for IPMI through Java
+• New motherboard has HTML5-based IPMI implementation and three PCIe expansion slots
+• Added NVMe drive and Intel QuickSync capabilities to improve performance
+• Using Plex for TV streaming, eliminating need for WireGuard VPN
+• Upgraded to i5-8500 CPU from previous experimentation with GVTG
+• Bringing a motherboard and Synology NAS through airport security
+• Dealing with TSA questioning about the NAS
+• Legally ripping movies and TV shows using Creative Commons content
+• Importance of IPMI and IGPU support in motherboards
+• Using the ASRock board for remote server management and QuickSync support
+• Motherboard price and value during a parts shortage
+• Setting up hardware parity between UK and US servers
+• Using Proxmox as host OS for consistency across locations
+• Issues with ZFS version differences on different systems
+• Installing Home Assistant on Proxmox VM to control home automation system
+• Using Zigbee devices, including smart plugs and buttons, for home automation
+• Comparison of Zigbee vs. Wi-Fi devices for reliability and cost
+• Discussion on the benefits and drawbacks of using physical controls vs automation in home systems
+• Explanation of why some people prefer to use switches and physical buttons over voice control or apps
+• Personal anecdote about Chris's experience with his Hollywood server going down due to a power outage
+• Description of Chris's plans to upgrade his server and potentially change its configuration
+• Discussion of high availability and redundancy in systems
+• Suspecting power supply issues with a system
+• Mention of WireGuard and TailScale for VPN solutions
+• Comparison of AdGuard Home, Pi Hole, and OpenSense for DNS and firewall management
+• Plans to consolidate devices and reduce power consumption at the studio
+• Consideration of moving WireGuard to its own device
+• Introduction to TailScale as a solution for secure tunneling between devices
+• Discussion of Tailscale VPN service and its underlying technology (WireGuard)
+• Description of how Tailscale uses an intermediary "witness node" to facilitate network connections
+• Alternative self-hosted implementation of witness nodes using HeadScale open source software
+• Comparison of Linode's cloud infrastructure with other providers, highlighting its speed and reliability
+• Personal anecdote about using a Linode server as a backup during a road trip
+• Promotion of Linode's one-click deployment feature for various services (Nextcloud, Discourse, Jitsi)
+• Discussion of Linode's services and ease of use for development and game servers
+• Road trip experiences and managing heat while traveling (especially in hot climates)
+• Home Assistant automations and controlling heating systems
+• Overhauling traditional automations to use the generic thermostat entity instead
+• Home Assistant monitors temperature and provides a thermostat interface
+• Customizable temperature settings with minimum cycle length option
+• Ability to turn off automated cycling of heaters via Home Assistant dashboard or HomeKit app
+• Integration with HomeKit allows verbal control with Siri, including setting temperatures and viewing current temperature
+• Automation options, such as adjusting temperature based on sun rise/set times
+• Generic thermostat setup requires only a smart switch and temperature sensor
+• Self-hosting smart gear pre-flashed with Tasmota from sponsors cloudfree.shop and mylocalbytes.com
+• Setting up remote backup system using Synology, Autorestick, Restic, and Minio for off-site data protection
+• Configuring traffic to route data through NAT to the remote backup location on the Synology box at the host's mother's house
+• Discussing the benefits of having multiple, separate backup systems in different ecosystems
+• Mentioning the hosts' trip back to the UK and meeting up with listeners
+• Meetup announced at Breckland Lodge on A11 outside Attleborough near Norwich on September 28th at 6pm UK time
+• Meeting is impromptu and will be kept small for COVID safety reasons
+• Attendees can recognize the host (Gary) by his Chris and the Badger t-shirt
+• Feedback, ideas, and show topics can be submitted through self-hosted.show/contact or on Twitter (@ChrisLAS and @IronicBadger)
+• Previous episode released as #54

54： Ultimate Off-Site Setup _transcript.txt

@@ -0,0 +1,838 @@
+[0.00 --> 3.70]  I'm looking out tonight over a beautiful Norfolk sky.
+[3.92 --> 6.52]  I'm finally, finally back in England.
+[6.84 --> 10.80]  Oh, that must feel amazing after having to wait with the whole pandemic and everything.
+[11.00 --> 14.82]  And how ironic is it that now that I'm back in my studio, you're traveling.
+[15.38 --> 16.06]  I know, right?
+[16.48 --> 21.34]  And I'm talking to you over a 4G LTE connection because the house I'm staying in at my mother-in-law's
+[21.34 --> 25.38]  is so rural, she can only get two meg down on DSL.
+[25.56 --> 27.56]  Well, now the shoe's on the other foot.
+[27.56 --> 29.94]  But I'm with the good connection and you've got cellular.
+[30.74 --> 30.92]  Yeah.
+[31.10 --> 31.94]  How was it though?
+[32.04 --> 37.14]  I mean, traveling with the baby plus, that's no short flight from, even from the East Coast
+[37.14 --> 37.86]  to London.
+[37.96 --> 40.76]  That must have been six hour flight, something like that.
+[41.06 --> 47.50]  It's seven going to Europe because you're with the wind, what they call the jet stream.
+[47.98 --> 49.80]  But coming back, it's an hour longer.
+[49.80 --> 51.28]  I guess it must be uphill or something.
+[52.26 --> 53.58]  Oh, so, right.
+[54.18 --> 55.36]  It's story time.
+[55.90 --> 56.34]  All right.
+[56.44 --> 57.28]  It's story time.
+[57.56 --> 59.58]  I was a colossal idiot.
+[60.36 --> 61.24]  Let's put it that way.
+[61.44 --> 61.92]  No.
+[62.56 --> 67.94]  The night before our flight to England from the States, I was logging onto the American
+[67.94 --> 72.82]  Airlines website, putting in all my passport information and I put in my wife's passport
+[72.82 --> 75.84]  information and my daughter's passport information.
+[76.02 --> 76.78]  It was all fine.
+[77.28 --> 78.20]  Got to mine.
+[78.40 --> 79.50]  And, you know, I have both.
+[79.50 --> 81.68]  I have the British and the American one.
+[82.62 --> 86.30]  And I put in my British one and then it said, you don't have a visa for this passport.
+[86.48 --> 87.84]  Please enter your US one.
+[87.96 --> 89.04]  I'm like, okay.
+[89.24 --> 92.58]  I was going to enter Britain on my British one, but sure.
+[92.78 --> 93.00]  Fine.
+[93.62 --> 95.32]  Went to get my US passport out the drawer.
+[96.04 --> 97.14]  It expired in July.
+[97.68 --> 98.50]  Oh, no.
+[98.94 --> 99.30]  Uh-huh.
+[99.50 --> 101.80]  You can't just get that taken care of like overnight.
+[102.00 --> 102.86]  Like that's a process.
+[103.10 --> 103.20]  No.
+[103.30 --> 104.02]  And bear in mind.
+[104.14 --> 107.90]  So we were due to fly out on Labor Day, which is like a bank holiday in the States.
+[108.66 --> 109.76]  You know, this was Sunday night.
+[109.76 --> 114.28]  I found out for a Monday night flight on Labor Day.
+[114.40 --> 116.86]  So the entire government was closed on the Monday.
+[117.32 --> 123.86]  So I just had to sit there stewing in my own filth and shame for an entire day, explaining
+[123.86 --> 127.70]  to my entire family why they weren't going to get to meet their granddaughter on time
+[127.70 --> 129.50]  and yada, yada, yada.
+[130.12 --> 133.82]  I mean, that does feel like a quintessential dad experience where like you're, you're so
+[133.82 --> 136.04]  worried about like, how are we going to fly with a baby?
+[136.46 --> 137.36]  What do we need to do?
+[137.36 --> 141.22]  Like, do we have devices to entertain ourselves, sync the media, pack everything?
+[141.42 --> 144.30]  You think of all that stuff except for your own passport.
+[145.06 --> 151.12]  Do you know what makes this absolutely asinently stupid is that we had to apply for my daughter's
+[151.12 --> 152.76]  first passport in August.
+[152.90 --> 155.20]  So she had her appointment on August 8th.
+[155.80 --> 160.36]  We paid for the expedited processing and it was there by August the 22nd.
+[160.46 --> 162.78]  That was pretty fast, I think, for a first passport.
+[162.78 --> 167.32]  They used my American passport in that application.
+[167.84 --> 172.98]  And at no point did anybody say to me, hey, Mr. Kretschmar, your passport's expired.
+[173.48 --> 174.48]  Hey, man, just so you know.
+[174.58 --> 175.20]  Just so you know.
+[175.40 --> 176.54]  Looks like you might be preparing to travel.
+[176.80 --> 181.08]  I mean, look, it's totally my fault and I hold my hands up that I screwed up.
+[181.82 --> 185.78]  But there were a couple of opportunities where other people could have helped me as well.
+[185.78 --> 186.86]  Oh boy, no kidding.
+[187.40 --> 189.94]  Well, you can always help yourself by going to a Cloud Guru, eh?
+[190.04 --> 192.52]  The leader in learning for Cloud, Linux and other modern tech skills.
+[192.86 --> 197.92]  And right now, everyone can get into the game with discounts on learning plans.
+[198.06 --> 202.08]  Hundreds of certification courses, thousands of labs and hands-on learning and free cloud
+[202.08 --> 203.46]  sandboxes to develop your skills.
+[203.72 --> 205.20]  A CloudGuru.com.
+[205.20 --> 211.02]  So the Tuesday morning rolls around and I end up calling the State Department and booking
+[211.02 --> 213.30]  an appointment, an emergency passport appointment.
+[213.70 --> 217.22]  The only one they have within two weeks is in Chicago.
+[218.50 --> 220.50]  And of course, you're in North Carolina.
+[220.64 --> 222.58]  So that's a bit of a track.
+[222.68 --> 223.46]  Well, actually, I tell a lie.
+[223.52 --> 225.06]  They had one in Buffalo as well.
+[225.06 --> 230.18]  But given the size of O'Hare in Chicago, I figured actually what we'd do is we'd fly
+[230.18 --> 230.82]  out to Chicago.
+[231.38 --> 233.92]  I'd go and get my emergency passport taken care of.
+[233.92 --> 236.44]  And then they give it to you within two or three hours.
+[236.82 --> 238.60]  And then we'd just fly to London from Chicago.
+[238.78 --> 243.36]  So in the end, my wife got her birthday in Chicago and she got to go around all the art
+[243.36 --> 244.64]  museums, all that kind of stuff.
+[245.00 --> 247.80]  And then we flew out to Heathrow direct from O'Hare.
+[247.98 --> 252.20]  We went on one of those really nice new Dreamliners, those Boeing Dreamliners.
+[252.56 --> 253.06]  Oh, really?
+[253.46 --> 253.70]  Yeah.
+[253.92 --> 255.10]  Lives up to the hype, man.
+[255.20 --> 259.34]  I tell you what, they say they pressurize the cabin at 6,000 feet, not eight.
+[259.34 --> 264.26]  And I was super comfortable on that plane, even with a mask on.
+[265.04 --> 268.46]  It's hard to explain, but I just didn't feel as fatigued at the other end.
+[268.70 --> 270.88]  Boy, if you're going to go on a long flight, that seems like the way to go.
+[270.98 --> 273.22]  And how nice is that for the wife lady?
+[273.30 --> 277.80]  She got to spend the anniversary in Denver during our meetup and the birthday in Chicago.
+[278.02 --> 278.90]  Yeah, I know, right?
+[279.36 --> 281.26]  After a year and a half of not traveling.
+[281.58 --> 282.36]  It's a bit strange.
+[282.36 --> 288.14]  So anyway, here I am sat in my mother-in-law's house in England, and it's actually pretty
+[288.14 --> 290.94]  much three years to the day since I emigrated.
+[291.72 --> 291.74]  Wow.
+[292.06 --> 293.12]  A lot to catch up on.
+[293.32 --> 298.42]  There's so much that's happened in that three years from, you know, new career, new houses,
+[298.80 --> 299.56]  new baby.
+[301.08 --> 306.50]  You know, the weird thing is, is that when we emigrated, child, having a child was just
+[306.50 --> 308.28]  not something we were even thinking about.
+[308.34 --> 311.50]  And here we are coming back the first time with her in tow.
+[311.50 --> 312.40]  It's very strange.
+[312.98 --> 313.14]  Wow.
+[313.44 --> 317.44]  Well, you're getting that baby adapted to travel early, which I hear is the way to do
+[317.44 --> 317.64]  it.
+[317.76 --> 319.80]  So hopefully she'll be a travel pro.
+[320.04 --> 320.46]  Hopefully.
+[320.66 --> 321.48]  You know, right away.
+[321.72 --> 325.18]  You know, the weirdest thing, though, you'd think after three years, it would feel weird
+[325.18 --> 330.60]  to come back to a different country that drives on the correct side of the road, that measures
+[330.60 --> 331.48]  everything correctly.
+[332.18 --> 335.84]  But, you know, the weirdest thing actually is that it doesn't feel weird at all.
+[335.94 --> 337.72]  It doesn't even feel like we ever left.
+[338.12 --> 341.26]  It's just picking right back up where we left off.
+[341.26 --> 342.62]  It's bizarre.
+[343.22 --> 346.58]  For me, you know, just even after this road trip, we were gone for about 40 days.
+[346.78 --> 351.68]  For the first two days that I was back in the Seattle area, it felt a little strange,
+[351.74 --> 354.04]  like, oh, this doesn't quite click anymore.
+[354.30 --> 357.54]  But now that I've been here for, you know, a little bit more than a week, it just feels
+[357.54 --> 359.22]  totally normal back into the swing of things.
+[359.26 --> 360.02]  Is it kind of like that?
+[360.28 --> 360.44]  Yeah.
+[360.70 --> 360.92]  Yeah.
+[360.92 --> 364.52]  I mean, I've still got a couple of British bank accounts, so I've got all the correct
+[364.52 --> 366.72]  credit cards to pay for things with.
+[366.94 --> 368.96]  You know, I can just pay for petrol and it's no problem.
+[369.36 --> 371.48]  And you're no longer the one with the accent anymore.
+[372.54 --> 374.20]  It is so nice.
+[374.32 --> 377.72]  I can't lie to just not have that be a talking.
+[377.94 --> 378.72]  Oh, my God.
+[378.72 --> 379.78]  I love your accent.
+[380.44 --> 380.84]  Yeah.
+[381.16 --> 381.38]  Yeah.
+[381.42 --> 383.78]  I bet you get that all the time, especially in the South.
+[383.82 --> 384.90]  That must be very common.
+[385.16 --> 385.96]  Oh, my gosh.
+[385.96 --> 390.52]  Of course, my go-to line to them is, well, you're the one with the accent.
+[391.40 --> 395.82]  And you can just see people stop and look at me like, oh, yeah, I suppose I do have
+[395.82 --> 396.92]  an accent to you, don't I?
+[398.52 --> 405.42]  I imagine, much like myself, you must go through a lot tech-wise and with your home setup to
+[405.42 --> 406.60]  get ready for a trip like this.
+[406.78 --> 407.20]  Well, yeah.
+[407.26 --> 410.70]  I mean, I've got three years worth of tech debt that I wanted to try and address on this
+[410.70 --> 410.98]  trip.
+[411.58 --> 414.14]  A bunch of stuff to my old UK server.
+[414.14 --> 419.66]  I wanted to try and improve things for my parents as well, who have a bunch of old laptops
+[419.66 --> 424.76]  that are just sat around gathering dust that they'd love to get the data off of and find
+[424.76 --> 430.98]  ways to manage all their photos, all this kind of stuff, and try and bring some of the
+[430.98 --> 437.32]  self-hosting stuff that I've learned over the last three years since I left back with
+[437.32 --> 439.50]  me and try and improve their setups.
+[439.50 --> 445.06]  I imagine it's an opportunity for you to also maybe rethink your off-site backup because
+[445.06 --> 446.06]  you're at these machines now.
+[446.18 --> 449.30]  If you want to change something when it comes to any of that kind of stuff, this is kind
+[449.30 --> 449.96]  of your opportunity.
+[450.12 --> 450.60]  This is it.
+[450.76 --> 451.08]  Exactly.
+[451.26 --> 451.42]  Yeah.
+[451.56 --> 455.92]  I mean, we will be coming back next summer because of my sister's wedding, but it's not
+[455.92 --> 456.40]  often.
+[457.54 --> 458.28]  Who knows?
+[458.34 --> 459.40]  Maybe there'll be another COVID.
+[459.80 --> 460.80]  God, I do hope not.
+[460.80 --> 463.76]  But you just don't know when you're going to get these opportunities.
+[464.10 --> 470.32]  So I've gone ahead and replaced the motherboard in my UK server that was six or seven years
+[470.32 --> 471.24]  old when I left.
+[471.54 --> 473.96]  So now it's knocking on the door of being 10 years old.
+[474.10 --> 474.44]  Oh, yeah.
+[474.50 --> 481.10]  It's a really old Supermicro 1366 LGA socket Xeon, I think.
+[481.52 --> 482.00]  Good box, though.
+[482.02 --> 482.72]  That's a good board.
+[483.08 --> 483.78]  Oh, yeah, absolutely.
+[483.78 --> 491.02]  But it ran IPMI through Java, so I had to have a special VM around just for that, which
+[491.02 --> 491.98]  was a pain in the ass.
+[492.44 --> 492.52]  Yep.
+[493.34 --> 494.92]  So I've gone ahead and replaced that.
+[495.00 --> 499.72]  I put a link in the show notes to the ASRock Rack motherboard that I've picked out.
+[500.52 --> 506.62]  And I picked this one out for a few reasons, mostly because I actually already had an i5-8500
+[506.62 --> 509.30]  CPU lying around.
+[509.30 --> 514.68]  And I had that because of all the experimentation I did in January with the GVTG stuff.
+[515.58 --> 518.26]  So that's just been sat on a shelf gathering dust for a little while.
+[518.76 --> 521.54]  I mean, this looks like a board that should last you a good number of years.
+[521.54 --> 524.32]  And especially if it's one you already had, that's a major win.
+[524.42 --> 526.70]  And I'm impressed that you've already got the work done.
+[526.90 --> 527.82]  You got right to it.
+[528.68 --> 531.68]  You know, I waited to decompress and de-jet lag for a couple of days.
+[532.00 --> 533.64]  And then I got to swapping out the motherboard.
+[534.26 --> 535.92]  And, you know, there's a few nice upgrades.
+[536.02 --> 537.34]  I put an NVMe drive in there.
+[537.34 --> 539.86]  The i5 that's in there obviously has QuickSync as well.
+[540.04 --> 544.96]  So if there's any, you know, I use that server for a lot of TV streaming.
+[545.12 --> 549.62]  So like when the Olympics were on, when the World Cup is going to be on next year, the
+[549.62 --> 550.90]  Euros, all that kind of stuff.
+[551.00 --> 554.62]  I watched the BBC coverage through Plex from my UK server.
+[555.12 --> 555.42]  I see.
+[555.52 --> 555.84]  I see.
+[556.26 --> 559.12]  So you don't even have to pop in over WireGuard because you're using Plex.
+[559.22 --> 560.40]  You can just bring up Plex.
+[560.78 --> 561.14]  Correct.
+[561.34 --> 561.50]  Yeah.
+[561.56 --> 562.54]  Just for the TV.
+[562.54 --> 564.18]  And it works really nicely.
+[564.36 --> 569.94]  But the old Xeon, when it was transcoding, that content would suck down the juice, which,
+[570.26 --> 571.48]  you know, it's not my electricity bill.
+[571.56 --> 577.24]  So I'm trying to be a good citizen and replaced it with a more power efficient system with the
+[577.24 --> 578.34]  Intel QuickSync stuff.
+[579.66 --> 583.24]  But this motherboard in particular has a couple of really interesting things.
+[583.24 --> 586.96]  I think if you're looking at a media server motherboard, you should be aware of.
+[587.64 --> 590.90]  First of all, it's a micro ATX board, which may not be for everybody.
+[591.58 --> 591.62]  Yeah.
+[591.74 --> 599.14]  But it does have three PCIe expansion slots on it, plus one NVMe drive slot.
+[599.38 --> 602.26]  So there's plenty of expansion options in there should you need it.
+[602.96 --> 610.20]  It also has a really very, very nice HTML5 based IPMI implementation, which is really nice.
+[610.20 --> 617.18]  So I've got OpenSense running on an APU2 at my dad's, and then I use that as my WireGuard endpoint.
+[617.60 --> 624.26]  So once I've got the site-to-site VPN up and running, or just connect through the client
+[624.26 --> 630.02]  on my laptop to that site, I can then just access it through an IP address directly in
+[630.02 --> 630.42]  the browser.
+[630.66 --> 632.04]  There's no Java crap needed.
+[632.24 --> 633.66]  It's really, really nice.
+[634.30 --> 635.88]  Oh, that's going to be great, Alex.
+[635.88 --> 640.96]  I mean, it really sounds like a great ideal board and setup for what you're doing.
+[641.08 --> 646.82]  My only knock against it would be, it's kind of a bummer it only has one NVMe slot, because
+[646.82 --> 650.22]  it would be really nice to have, you know, maybe in a mirror or something like that, like
+[650.22 --> 652.16]  a couple of drives and have that speed still.
+[652.48 --> 657.76]  Well, it would, but luckily the primary PCIe port supports by FUcation.
+[657.76 --> 665.78]  So what I've been able to do is buy an M.2 NVMe PCIe card that has four NVMe slots on it
+[665.78 --> 672.70]  and split that up, split that port up essentially into not four, unfortunately, but three extra
+[672.70 --> 673.70]  NVMe slots.
+[674.08 --> 680.86]  So I don't need it for this server in the UK, but for my server back at home in the US, I'm
+[680.86 --> 681.40]  going to do this.
+[681.52 --> 685.02]  I'm going to, I've been testing it for the last few weeks and it works pretty well.
+[685.02 --> 690.12]  Now, the main slot supports eight by four by four.
+[690.46 --> 695.66]  So what that means is it splits that 16X link into three segments.
+[695.90 --> 703.16]  So I can just have effectively three of the four slots on that NVMe card will work just
+[703.16 --> 705.14]  as if they were plugged directly in through the motherboard.
+[705.62 --> 705.78]  All right.
+[705.82 --> 706.30]  That's pretty cool.
+[706.36 --> 709.90]  I'll toss a link to that, although it might be sold out on Amazon right now, but I'll put
+[709.90 --> 712.26]  a link to it in the show notes if people want to see this Asus.
+[712.42 --> 712.64]  Yeah.
+[712.70 --> 713.30]  What isn't?
+[713.30 --> 714.02]  Yeah, really?
+[714.02 --> 717.44]  That's part of why it was nice that you could use a board you already had, really.
+[717.78 --> 719.12]  Well, I didn't, I didn't already have the motherboard.
+[719.22 --> 719.88]  I had the CPU.
+[720.44 --> 725.66]  I think I bought the boards through Newegg because, you know, in the US and brought them
+[725.66 --> 726.38]  over with me.
+[726.66 --> 727.04]  I see.
+[727.14 --> 727.90]  Much cheaper that way.
+[728.00 --> 730.44]  Also, I could do all the testing at home where I have all my gear.
+[730.72 --> 732.80]  So you brought this motherboard through TSA?
+[733.46 --> 733.82]  Yes.
+[733.94 --> 736.74]  I also brought a Synology NAS, which I'll come on to later.
+[737.14 --> 737.58]  Ah, okay.
+[737.76 --> 743.12]  The guys in Raleigh didn't care about the Synology, but the guys in Chicago gave me the 20 questions
+[743.12 --> 743.66]  about it.
+[744.80 --> 746.12]  It's a bomb and an ass.
+[747.38 --> 750.48]  Well, they were, they were saying, so what is this thing?
+[750.62 --> 751.58]  What do you need it for?
+[751.64 --> 752.66]  I'm like, it's a computer.
+[752.84 --> 754.30]  And they said, what does it do?
+[754.32 --> 755.90]  And I said, it stores data.
+[756.48 --> 757.68]  And they went, what data?
+[757.68 --> 760.72]  And I said, movies, TV shows.
+[760.86 --> 764.86]  And they looked at me, looked at each other and just went, yeah, whatever.
+[765.26 --> 766.16]  And just let me go.
+[766.98 --> 768.66]  Thank goodness they didn't ask any more questions.
+[769.04 --> 769.22]  Yeah.
+[769.30 --> 774.00]  Like I was kind of thinking, so where do you get these movies and TV shows from, sir?
+[774.70 --> 775.58]  I'll be like, hmm.
+[776.26 --> 778.88]  Uh, yes, I legally rip all of these things.
+[779.22 --> 779.64]  Wink, wink.
+[779.64 --> 783.66]  Uh, it's all Creative Commons content, actually.
+[783.76 --> 784.58]  Let me tell you about.
+[784.66 --> 785.80]  Yeah, it's all Big Buck Bunny.
+[786.56 --> 787.92]  And then going to, yeah, yeah, right.
+[788.00 --> 789.68]  Just lots of different rips of Big Bunny.
+[789.74 --> 792.96]  And then you just go into like a whole explanation of Creative Commons and hope they just glaze over.
+[793.40 --> 793.64]  Yeah.
+[794.60 --> 798.54]  So going back to the motherboard briefly, one other thing that was really difficult to find
+[798.54 --> 803.64]  out before I purchased that's actually really important is this motherboard is one of the only,
+[804.10 --> 811.08]  or one of the few that I could find that actually supports IPMI and IGPU at the same time.
+[811.16 --> 816.12]  So what that means is the graphics card that's built into the CPU, which is where QuickSync lives,
+[816.80 --> 823.30]  some IPMI implementations grab that monitor and then don't let you use it for QuickSync.
+[824.24 --> 828.30]  Basically, you need to go into a secret BIOS menu on this ASRock board.
+[828.30 --> 831.10]  And enable IGPU multi-monitor support.
+[831.74 --> 834.24]  Once you've done that, it just works.
+[834.38 --> 838.84]  You get a BIOS screen through the terminal window in the browser.
+[839.26 --> 846.04]  And you also get QuickSync support, hardware transcoding support through Plex and Intel GPU top as well.
+[846.54 --> 848.48]  Oh, I could really use something like that here in the studio.
+[848.70 --> 853.54]  You know, the server went down, the studio server went down about a week and a half,
+[853.84 --> 855.08]  two weeks, three weeks into the trip.
+[855.14 --> 855.56]  I can't remember.
+[855.56 --> 861.98]  But basically, the last two weeks of the trip, I didn't have the server and it drove me crazy not to be able to see the console.
+[862.38 --> 862.44]  Yeah.
+[862.70 --> 865.92]  I love that it supports IGPU and IPMI at the same time.
+[866.50 --> 872.54]  I mean, when you're looking at all the stuff this thing does, especially if you add that ASUS PCI NVMe expansion card in there,
+[873.00 --> 875.42]  I mean, it's $260 for this board on Newegg.
+[875.50 --> 875.62]  Yeah.
+[875.62 --> 883.00]  I mean, that's kind of, it's expensive, but a good motherboard right now during a parts shortage, not that bad, really.
+[883.10 --> 883.60]  $260.
+[884.04 --> 884.50]  Exactly.
+[884.72 --> 887.26]  COVID has me reframing what is expensive.
+[887.26 --> 895.88]  And if it's $50 more than what I'm comfortable spending, I mean, I was looking for something under $200, ideally.
+[897.52 --> 905.52]  But if it's in stock at this point in history, that extra $60 is kind of worth it, right?
+[905.90 --> 908.62]  Well, and it really kind of, it depends on how you frame it, too.
+[908.62 --> 912.26]  If you think of it as a server motherboard, it's a pretty good price.
+[912.40 --> 918.68]  If you think of it as like a gaming PC desktop motherboard, that's just sort of an average motherboard, it's expensive.
+[919.00 --> 920.16]  But it doesn't have any LEDs.
+[921.12 --> 923.00]  So gamers aren't interested.
+[924.70 --> 931.38]  I mean, it's not like it's, it's not like it's the be all end all server solution, especially because it's a, you know, it's a micro ATX.
+[931.58 --> 933.90]  But, geez, it's pretty great.
+[933.90 --> 940.06]  And the fact that you have iGPU, you get QuickSync, and you have IPMI, that's a great choice, Alex.
+[940.12 --> 942.50]  I mean, that seems like a board that's going to run a box for you for years.
+[942.50 --> 947.72]  And that if you ever have any troubles, you're going to be able to remotely figure out what's going on through IPMI.
+[948.10 --> 948.18]  Yeah.
+[948.22 --> 952.22]  And the nice thing is, I think I'm going to have that board in the UK and the US.
+[952.30 --> 954.92]  I'm going to have hardware parity between two systems.
+[956.38 --> 963.60]  32 gigs of RAM in the UK and 64 in the US, just because, you know, at home, I do a lot more stuff than I will do.
+[963.90 --> 965.56]  With a remote backup box.
+[966.04 --> 968.08]  And then are you doing Proxmox as the host OS?
+[968.22 --> 969.84]  I am actually in both places, yes.
+[970.04 --> 984.30]  And the reason being is I've run into a couple of issues, and I do only mean a couple, where I use ZFS, as you all know, to do my remote backups and Jim Salter's Syncoid tool to kind of manage the snapshot replication.
+[984.30 --> 991.54]  I've run into a couple of issues where, when I had the old server set up, it was running Ubuntu.
+[991.92 --> 999.74]  And therefore, the version of ZFS that was shipping in there wasn't exactly the same as the version that was running on Proxmox on my US server.
+[999.74 --> 1008.56]  And so I ran into a couple of issues where Syncoid failed because it was trying to send across a data set with feature flags that didn't exist on the target system.
+[1009.10 --> 1017.92]  And so just having Proxmox in both places means that I'm a lot less likely to run into any idiosyncrasies like that between the two systems.
+[1017.92 --> 1025.18]  The other thing as well is that I've been trying to get my dad on the home automation train for a long, long, long time.
+[1025.88 --> 1035.40]  And I think when I arrived, he gave me a whole rundown of how to turn off all the lamps in his kitchen, which is where we all hang out in his house.
+[1036.52 --> 1037.78]  You mean like for all the switches?
+[1038.26 --> 1042.96]  Yeah, there were six individually switched lamps I'd have to walk around and turn off one by one.
+[1042.96 --> 1050.86]  You know, having to walk somebody through how to use physical switches makes me feel a little bit better about walking people through how to use the automated home assistant system.
+[1051.22 --> 1054.60]  Yeah, I mean, we're talking I would have to walk to each different corner of the room.
+[1054.68 --> 1057.38]  It's not even like it's six switches on a single panel next to each other.
+[1057.94 --> 1061.68]  So as you can imagine, I was like, hmm, I can do better than this.
+[1062.08 --> 1069.96]  So I went on to our sponsor, My Local Bytes, and hit him up and he gave me a discount code, self-hosted, by the way, it's a discount code on that.
+[1070.54 --> 1072.66]  And I ordered some gear from him.
+[1072.66 --> 1076.80]  I ordered six smart plugs, a Zigbee transmitter, and a couple of Zigbee buttons.
+[1077.94 --> 1087.88]  And my dad now has all of his lights in his kitchen, well, the lamps anyway, turn on 45 minutes before sunset automatically, and they turn off at midnight.
+[1088.10 --> 1091.72]  But I also thought it would be nice to give them a button to control these things.
+[1092.82 --> 1100.38]  So I'm running the VM for Home Assistant on the UK server, on Proxmox, much like I do back in the US.
+[1100.38 --> 1103.36]  And running their whole OS stack?
+[1103.66 --> 1104.48]  Yeah, yeah.
+[1104.56 --> 1105.84]  I actually really like it.
+[1105.94 --> 1113.34]  I know conceptually and fundamentally I have some issues with people making their own operating systems, but damn, is it convenient.
+[1113.82 --> 1114.02]  Right.
+[1114.08 --> 1117.20]  The supervisor, the snapshots, all of that is, it's really great.
+[1117.26 --> 1120.38]  And it makes it super easy to restore if something goes wrong.
+[1120.44 --> 1120.84]  I get it.
+[1120.84 --> 1122.96]  I think running in a VM is the way to go.
+[1123.52 --> 1126.56]  And so now he has a couple of Zigbee buttons that are magnetic.
+[1126.70 --> 1137.30]  I went to Ikea, actually, just down the road from where he lives, and bought a couple of the trad-free Ikea Zigbee buttons, paired them up with the Zigbee stick that I got from my local bytes.
+[1137.30 --> 1140.20]  And it just worked.
+[1140.32 --> 1147.76]  You kind of pick out this, it's like a MAC address, but it's like an ID that looks like a MAC address on the Zigbee network that's created.
+[1148.36 --> 1158.08]  And the ZHA plugin that's built into Home Assistant picks up the Zigbee device, and then you just create an automation that is triggered by that button press.
+[1158.38 --> 1159.64]  And you went Zigbee, not Z-Wave.
+[1159.68 --> 1160.72]  I think that's a good call.
+[1160.72 --> 1166.92]  Was it just because that's what was available, or did you actually actively choose Zigbee over Z-Wave or Wi-Fi devices?
+[1167.32 --> 1171.40]  Well, I guess I did actively choose it, but not through much research.
+[1171.50 --> 1177.08]  I was just speaking to the guy behind my local bytes, and he said, you know, we sell Zigbee buttons, right?
+[1177.48 --> 1177.66]  Yeah.
+[1177.90 --> 1179.12]  I think Zigbee's the way to go.
+[1179.28 --> 1184.84]  And I think they're more reliable than Wi-Fi devices, and you can take down your Wi-Fi network, and that stuff all still works.
+[1184.84 --> 1192.60]  And, of course, I'm a fan of Zigbee because it's an open protocol, and it's what they use on Mars to communicate between the rover and the helicopter.
+[1193.06 --> 1194.14]  It is, absolutely, yeah.
+[1194.90 --> 1200.42]  It's, you know, those trad-free buttons from Ikea, they're six pounds a pop.
+[1200.54 --> 1203.28]  I think they're about eight or nine dollars in the U.S. each.
+[1203.62 --> 1203.72]  Yeah.
+[1203.90 --> 1207.56]  You know, for that price, I could have 20 in my house without really much thought.
+[1207.56 --> 1215.60]  I think there's two philosophies when it comes to home automation, and I think one philosophy is design it in such a way that you never have to touch it.
+[1215.74 --> 1220.08]  Like, the whole thing's automated, and you should really never need to interfere with it.
+[1220.12 --> 1221.10]  If you ever do, there's a dashboard.
+[1221.60 --> 1227.74]  But then the other, I think, very valid approach to home automation is using buttons for stuff.
+[1227.74 --> 1236.80]  And I think that's why there are some brands out there that specifically sell solutions where there's still switches, and that's why you and I have looked into devices that we can install on the wall so we can still use switches.
+[1236.98 --> 1243.36]  Because when you have physical controls, it adds a whole other dimension of what you can do with these buttons.
+[1243.46 --> 1249.20]  Like, you can set things so that if you three-tap that button, it could do a totally different set of functions.
+[1249.20 --> 1253.44]  And you have all of this kind of flexibility when you add physical buttons.
+[1253.44 --> 1258.70]  And people have written into the show and laughed, like, you guys, you automate all this stuff, and then you add buttons back in there.
+[1258.80 --> 1260.38]  Because I've talked about this in Lady Joops.
+[1260.80 --> 1265.22]  And it's like, nah, man, you add it where it makes sense, and you remove it where it doesn't make sense.
+[1265.36 --> 1269.02]  And, you know, your folks are going to be used to buttons.
+[1269.10 --> 1271.42]  They've had buttons their entire life in their home.
+[1271.42 --> 1280.64]  And so if you left that place and didn't put those things in, they'd probably rip it all out and just go back to using buttons again and turn stuff off and the automation be screwed up.
+[1280.76 --> 1283.46]  And it just wouldn't work because they're used to it.
+[1284.08 --> 1289.90]  I'm comfortable with pulling a phone out my pocket and opening an app and swiping and swiping and tapping.
+[1290.32 --> 1294.44]  Or shouting to an assistant in the air, you know, hey, hey, tube, turn on this light.
+[1294.52 --> 1295.78]  I mean, you could do that too.
+[1296.16 --> 1296.32]  Yeah.
+[1296.46 --> 1299.34]  And also, you know, think about the Home Assistant cloud subscription.
+[1299.50 --> 1301.10]  I pay that at home out of my own pocket.
+[1301.10 --> 1308.46]  I don't necessarily want to have to do that for my parents as well to get the Google Assistant support put in there.
+[1308.66 --> 1310.88]  And neither do I want to open up their firewall.
+[1311.74 --> 1317.40]  Even port 80 or 443, whatever, would be required to make that work for Google that way.
+[1317.56 --> 1321.84]  So whilst all those things are possible, I haven't enabled Google support for them.
+[1322.04 --> 1323.86]  I kind of don't want to either.
+[1323.94 --> 1325.18]  I want to keep it super simple.
+[1325.30 --> 1327.30]  Like you push this button, your lamps turn off.
+[1327.92 --> 1329.08]  I mean, it's that simple.
+[1329.08 --> 1339.00]  You know what I appreciate about you, Chris, is that I woke up on British time to a bunch of messages in our private JB chat team chat that we have.
+[1339.36 --> 1342.68]  And I know your Hollywood server has been offline for a couple of weeks.
+[1342.82 --> 1343.12]  Yeah.
+[1343.12 --> 1345.76]  You'd been home for, what, an hour?
+[1346.06 --> 1347.42]  And you'd fix that bad boy.
+[1347.84 --> 1348.38]  That's right.
+[1348.46 --> 1351.84]  We basically got our RV lady Joops parked.
+[1352.12 --> 1353.64]  We got her hooked up to power.
+[1353.86 --> 1355.44]  And then I jumped in the car.
+[1355.82 --> 1357.20]  I ran down to the studio.
+[1357.28 --> 1358.56]  I'm like, what's going on?
+[1358.58 --> 1359.72]  And I think, you know, I don't know, Alex.
+[1359.76 --> 1363.92]  It's like maybe it's the ex-server admin in me from years past.
+[1363.92 --> 1368.16]  But just knowing that my server's down drove me nuts.
+[1368.20 --> 1380.48]  Even though, like, I had taken steps to replicate the essential functionality, just knowing it was down and not knowing what state it was in and was in some weird state where the fans were blasting or what, you know?
+[1380.48 --> 1383.44]  And so I very much wanted to solve it.
+[1383.54 --> 1385.40]  And I clearly have to get rid of it.
+[1385.64 --> 1387.14]  And I think I have a plan.
+[1387.28 --> 1389.20]  I'm still waiting to put all the pieces together.
+[1389.34 --> 1395.64]  But I feel like in the next month or two, I'm probably going to build or buy a new server and go through this whole process.
+[1395.64 --> 1400.54]  And then I got to ask myself, like, do I want to put Arch back on there?
+[1400.66 --> 1402.88]  Do I want to do Proxmox like you're doing?
+[1403.70 --> 1406.82]  Do I want to put WireGuard on a separate machine?
+[1406.82 --> 1410.12]  So that way, when my server goes down, I can still get into the network.
+[1410.48 --> 1411.88]  A lot of things to think about.
+[1411.96 --> 1413.26]  So I'm just starting that process.
+[1413.84 --> 1414.58]  What went wrong with it?
+[1414.94 --> 1416.82]  There was a power outage at the studio.
+[1417.16 --> 1418.38]  So there's two power supplies.
+[1419.10 --> 1422.50]  And one is plugged into a UPS and one is plugged into the wall.
+[1422.56 --> 1425.58]  And there's a funky old tech debt reason why.
+[1426.28 --> 1432.46]  And I think when the power went out, it got in some sort of funky state where one power supply was down, but the other one stayed on for a while.
+[1432.46 --> 1435.82]  But then eventually the UPS ran out of power and it shut off.
+[1436.50 --> 1437.80]  Or maybe it didn't shut off.
+[1437.92 --> 1439.52]  I'm not exactly sure because I wasn't here.
+[1439.52 --> 1442.52]  But when I got back, it was frozen.
+[1442.76 --> 1451.14]  The system was locked up and it was just a constant beep, an air message, just a solid air message, like a hardware air.
+[1451.46 --> 1453.36]  And there was a red light on the front of the chassis.
+[1453.48 --> 1454.18]  It's a super micro.
+[1454.92 --> 1457.12]  And when I turned it off, the beep persisted.
+[1457.24 --> 1462.92]  So I actually physically unplugged the power supplies and then I plugged them back in and then booted it back up.
+[1463.56 --> 1464.48]  And it's been fine.
+[1464.48 --> 1466.52]  And I just think it's dying, slow death.
+[1466.72 --> 1472.62]  And so it has been unreliable for about five to almost six months now.
+[1472.82 --> 1477.54]  And so I think this is just part of a old server's slow death.
+[1478.28 --> 1484.10]  You know, what's funny is we were talking to Matt last episode about high availability and redundancy and all that kind of thing.
+[1484.10 --> 1490.44]  And it's interesting, you know, you have dual power supplies in there, presumably for that exact reason.
+[1490.44 --> 1492.56]  And yet you suspect that might be the issue.
+[1492.88 --> 1493.38]  Who knows?
+[1493.78 --> 1500.32]  We don't really have like great like intel or information from the system logs because everything that was happening was external to the box.
+[1500.32 --> 1504.12]  But yeah, that's going to be a project for sure.
+[1504.48 --> 1505.88]  And so you mentioned WireGuard.
+[1506.12 --> 1510.32]  I'm going to walk you through what I've been doing in a minute with WireGuard and TailScale.
+[1510.52 --> 1513.00]  But before I do, what are you planning on doing?
+[1513.14 --> 1516.56]  Or suppose I should ask, what do you do for a firewall at the studio now?
+[1516.56 --> 1519.30]  We have a Comcast business router that's the firewall.
+[1519.50 --> 1520.18]  It's nothing special.
+[1520.60 --> 1526.06]  I have thought in the past about replacing it with like a PFSense box or something like that.
+[1526.06 --> 1530.94]  However, as time has gone on, I've really found it fairly acceptable.
+[1531.66 --> 1533.00]  So I haven't replaced it yet.
+[1533.50 --> 1539.30]  You know, the only thing I would say is go ahead and do OpenSense or PFSense for a little bit.
+[1540.06 --> 1549.96]  There is a community plugins repository maintained by the same guy, I think, that writes the WireGuard plugin for OpenSense that lets you put AdGuard home directly on the firewall as well.
+[1550.54 --> 1551.88]  So that's what I've been doing for the last few weeks.
+[1551.88 --> 1556.96]  So I've been running AdGuard home on the same box as OpenSense as the primary DNS server.
+[1557.06 --> 1562.66]  So I've disabled Unbound on OpenSense and I'm now just using AdGuard home and it works fine for me.
+[1563.04 --> 1572.72]  But the real advantage, the real advantage is I've got my DNS, my DHCP and my VPN endpoints all on the same box.
+[1572.82 --> 1579.66]  Now, I suppose you could argue it's a very large single point of failure, but it's actually incredibly convenient.
+[1579.66 --> 1581.88]  Oh, for sure. And you don't need 100 boxes.
+[1582.32 --> 1586.10]  I'm a little done running a separate Raspberry Pi that has Pi Hole.
+[1586.20 --> 1587.54]  I love it. I think Pi Hole is great.
+[1587.66 --> 1589.70]  I actually like it a little better than AdGuard myself.
+[1590.26 --> 1598.66]  However, it's drawing power and I just don't need three Raspberry Pis running 24-7 when I'm running off a battery.
+[1599.16 --> 1601.66]  And I would much prefer to consolidate that down here.
+[1601.72 --> 1604.84]  Now, at the studio, power is not as much of a consideration.
+[1605.38 --> 1608.16]  It's then just more about functionality and flexibility.
+[1608.56 --> 1609.40]  Stability, surely.
+[1609.40 --> 1611.40]  And stability, and stability for sure.
+[1611.54 --> 1615.12]  I have been thinking about moving WireGuard off on its own device.
+[1615.70 --> 1623.64]  And if I did do an OpenSense box, and it'd be pretty nice to have AdGuard on there too, and then also do WireGuard, I'd be checking a few boxes.
+[1624.16 --> 1625.54]  So I think I may consider it.
+[1625.92 --> 1629.14]  I was actually originally planning to set up a Raspberry Pi.
+[1629.70 --> 1636.38]  And I was even thinking of trying to come up with some sort of failover capability for the Raspberry Pis to do WireGuard, which I think would be particularly tricky.
+[1636.38 --> 1637.10]  All right.
+[1637.14 --> 1640.28]  Well, here's another idea for you to bounce around your noodle.
+[1640.28 --> 1643.78]  I've been looking at something called TailScale for the last few weeks.
+[1643.88 --> 1650.50]  Now, this is born out of a requirement to run on a Synology box, which, as I'm sure you know, are quite restrictive.
+[1650.84 --> 1655.66]  And they're not full Linux, but they're sort of kind of Linux, and they sort of kind of do some things.
+[1655.66 --> 1661.98]  And anyway, it's a bit of a mess, to be honest, as a Linux guy to try and come and make this system do what I want.
+[1663.08 --> 1670.98]  They run Docker, so I can run, you know, Minio to do autorestick backups, all that kind of stuff to Synology remotely.
+[1671.30 --> 1675.48]  But that's no good if I can't connect to the damn thing over some kind of a secure tunnel.
+[1675.48 --> 1683.44]  So I've been taking a look at something called TailScale, and this project is absolutely awesome.
+[1684.44 --> 1689.56]  It has clients for Mac, Windows, Android, iOS, Linux, you name it.
+[1690.14 --> 1701.48]  And this thing, I got further in about 10 minutes connecting up all of my different devices and servers than I had in, I don't know, a year plus of trying to futz around with WireGuard configs.
+[1701.48 --> 1708.66]  And this thing lets you advertise different routes and different subnets, just with one simple command on the command line.
+[1709.10 --> 1716.06]  So, for example, I'm sat in Raleigh, and I want to connect to a host that's in my dad's network in England.
+[1716.88 --> 1723.28]  I don't have a direct connection from my laptop to that host, but what I can do is I can bounce the traffic through my UK server,
+[1723.56 --> 1727.94]  which routes through the TailScale network using something they call Magic DNS.
+[1727.94 --> 1730.18]  And then it pops out the other side.
+[1730.48 --> 1737.78]  The remote server then goes, oh, yeah, you've allowed access to 192.168.whatever the subnet is in that LAN.
+[1738.56 --> 1745.18]  And it lets the traffic out from my local laptop to the device on the network in the remote side.
+[1745.40 --> 1749.20]  I can also then advertise what's called an exit node.
+[1749.20 --> 1755.28]  If I want to route my traffic over the internet to come out in England rather than the US, for example, for iPlayer,
+[1756.30 --> 1760.62]  I can just, with a click of one button in the TailScale client on my laptop,
+[1761.04 --> 1763.62]  change between the different endpoints that I'm exiting at.
+[1764.20 --> 1767.04]  It's really, really simple and really slick.
+[1767.12 --> 1767.80]  You should give it a look.
+[1768.18 --> 1771.02]  So is it essentially then creating a mesh network between your machines?
+[1771.38 --> 1771.58]  Yep.
+[1771.96 --> 1772.38]  Aha.
+[1772.98 --> 1776.26]  And do they have a server component that they're running that is involved?
+[1776.82 --> 1778.34]  It uses WireGuard under the hood.
+[1778.34 --> 1779.68]  This sounds pretty slick.
+[1779.78 --> 1786.28]  So they must have a component that is doing some of the client negotiation, maybe key exchange.
+[1786.38 --> 1789.92]  They must have a server side to this that's involved to help coordinate all of this?
+[1790.18 --> 1790.62]  They do.
+[1790.82 --> 1791.96]  It runs on their servers.
+[1792.34 --> 1800.08]  And it's an intermediary that you have to trust, I suppose, as part of the product that comes out of the box.
+[1800.08 --> 1809.92]  However, there is an open source self-hosted implementation of these third-party witness nodes, whatever you want to call them, called HeadScale.
+[1810.04 --> 1811.60]  We'll put a link to that in the show notes.
+[1811.80 --> 1813.06]  And you can self-host this thing.
+[1813.28 --> 1817.20]  And this will become something you would, for example, run on Linode.
+[1817.20 --> 1822.32]  And then all of your different devices would talk back to that central host for discovery.
+[1822.64 --> 1825.48]  And then from there, they do all their clever routing between each other.
+[1825.48 --> 1829.90]  And it looks like the way the system works is the private keys are generated on each node.
+[1830.02 --> 1832.00]  So it's not like they have access to those private keys.
+[1832.08 --> 1836.20]  And then it's using WireGuard as the backend implementation.
+[1836.44 --> 1839.96]  And it looks like on some operating systems or maybe all they're using the WireGuard Go client.
+[1840.62 --> 1841.90]  I mean, all that's really solid.
+[1841.98 --> 1846.50]  And I find WireGuard to be extremely trustworthy and very performant as well.
+[1846.58 --> 1847.50]  So that's kind of a win-win.
+[1847.64 --> 1850.58]  So it's tailscale.com to see more.
+[1850.58 --> 1854.10]  I would have accidentally locked myself out of my US network a few days ago.
+[1854.26 --> 1856.46]  I was working on the site-to-site WireGuard VPN.
+[1857.12 --> 1861.14]  And for some reason, when I brought up the interface in Raleigh on OpenSense,
+[1861.68 --> 1867.38]  the second WireGuard interface would cause the primary WireGuard interface to go down.
+[1867.64 --> 1869.20]  I still haven't figured out why.
+[1869.98 --> 1875.62]  But without tailscale running on a VM inside my network, I would have been totally locked out.
+[1875.92 --> 1877.98]  There would have been nothing I could have done.
+[1877.98 --> 1882.10]  But luckily, I was able to route all my traffic through the tailscale system,
+[1882.62 --> 1885.60]  get shell access back to OpenSense, and then fix it from there.
+[1886.12 --> 1886.78]  Nicely done.
+[1886.92 --> 1888.48]  That's a good little score, Alex.
+[1888.78 --> 1890.62]  Tailscale, I'll have a link to that in the show notes.
+[1890.64 --> 1892.84]  And I think I'm going to try it out after the show today because
+[1892.84 --> 1896.34]  they have a ARM version for Linux on the Raspberry Pi.
+[1896.56 --> 1898.72]  I knew you'd like it just because it has Raspberry Pi support.
+[1898.90 --> 1900.36]  You know, you're a cheap date.
+[1901.26 --> 1902.48]  You do know me well.
+[1902.64 --> 1903.46]  That's very true.
+[1905.26 --> 1907.08]  linode.com slash SSH.
+[1907.08 --> 1910.66]  Go there to get $100 in 60-day credit on a new account.
+[1910.76 --> 1912.68]  And of course, you go there to support the show.
+[1912.80 --> 1915.36]  And we love using the cloud where it makes sense.
+[1915.44 --> 1917.06]  We're all about self-hosting on the show.
+[1917.26 --> 1919.50]  But there's clearly a role for cloud.
+[1919.96 --> 1924.72]  And we just practically make use of that whenever it seems like the way to go.
+[1924.80 --> 1927.44]  And Linode is always the place we deploy.
+[1927.78 --> 1929.32]  They have super fast infrastructure.
+[1929.52 --> 1933.22]  In fact, they've just recently invested more in the infrastructure.
+[1933.22 --> 1939.52]  And in their block storage, they've put in brand new screaming fast MBME drives.
+[1939.94 --> 1941.50]  They are their own ISP.
+[1941.64 --> 1945.48]  So they own the links between their 11 data centers around the world.
+[1945.60 --> 1951.36]  On their dedicated CPU rigs, they have super high-end AMD EPYC processors that kick the butts
+[1951.36 --> 1952.76]  of all the other cloud providers.
+[1952.76 --> 1956.30]  I mean, they take the infrastructure really seriously.
+[1956.62 --> 1961.02]  And I had a server outage here at the studio, our physical server here in the garage.
+[1961.28 --> 1963.20]  And I knew things were looking kind of bad.
+[1963.38 --> 1967.82]  So I just set up a Linode with the very bare essentials that this box does.
+[1967.94 --> 1969.64]  I just set it up ready to go powered off.
+[1969.64 --> 1974.86]  And sure enough, turned out, like, it sat there for a few weeks.
+[1975.10 --> 1976.90]  And I thought, oh, maybe I'll go through this whole road trip.
+[1976.94 --> 1977.88]  I don't ever need to fire it up.
+[1978.06 --> 1982.72]  But no, the last two weeks of the road trip, I ended up signing to my Linode dashboard and
+[1982.72 --> 1983.92]  firing up that backup machine.
+[1984.00 --> 1985.74]  And I was so thankful I had it.
+[1985.76 --> 1990.36]  And when you look at Linode's pricing, 30% to 50% cheaper than, like, the big duopoly
+[1990.36 --> 1993.18]  hyperscalers, that's a great value.
+[1993.64 --> 1997.02]  And if you want to deploy Nextcloud, for example, and you want to see if it works for you, and
+[1997.02 --> 2002.30]  maybe you don't want to spend several days learning how to set up the entire Nextcloud stack.
+[2003.04 --> 2006.94]  Well, if you go to linode.com slash SSH and you create an account and you get that $100
+[2006.94 --> 2009.56]  credit, you could deploy Nextcloud in seconds.
+[2009.66 --> 2011.64]  They have, like, a one-click deployment for Nextcloud.
+[2011.96 --> 2015.46]  They have one-click deployment for Discourse if you want to go build a community.
+[2015.92 --> 2019.34]  Or maybe you're looking at replacing Zoom with something self-hosted.
+[2019.60 --> 2021.92]  They have a one-click deployment for Jitsi as well.
+[2021.92 --> 2026.92]  And I think you'd be shocked at how great a self-hosted Jitsi instance is and how
+[2026.92 --> 2028.68]  much better it can be than using Zoom.
+[2029.16 --> 2032.90]  And it's way cheaper if you want, like, the pro Zoom stuff and you're in control.
+[2033.14 --> 2036.88]  They have a lot, way more than I could ever list, just one-click stacks.
+[2037.06 --> 2038.64]  Or you can go the DIY route.
+[2038.76 --> 2039.76]  It's up to you.
+[2040.14 --> 2041.62]  Development tools, game servers.
+[2041.76 --> 2043.32]  Linode makes it easy to get going.
+[2043.66 --> 2047.32]  And then they have a bunch of great services like S3-compatible object storage, which is
+[2047.32 --> 2051.48]  fantastic for backups, DDoS protection, VLAN support, a powerful DNS manager.
+[2051.48 --> 2053.92]  I mean, on and on and on, you guys.
+[2054.60 --> 2058.38]  So I'll just leave it to you to go figure it out, to go try it for yourself, because I
+[2058.38 --> 2059.26]  know that's how I learn.
+[2059.58 --> 2065.14]  So go to linode.com slash SSH, get that $100 in 60-day credit on your new account, and you
+[2065.14 --> 2065.78]  support the show.
+[2066.26 --> 2068.58]  Linode.com slash SSH.
+[2070.66 --> 2074.78]  So after road trips, I always like to ask you what your learnings have been and stuff like
+[2074.78 --> 2074.96]  that.
+[2075.02 --> 2079.04]  And I would imagine the primary theme from this trip was managing heat.
+[2079.04 --> 2080.64]  Oh my goodness, yes.
+[2081.12 --> 2086.82]  When you were on your way to Chicago, I was trapped in Tucson, where I think every day
+[2086.82 --> 2088.60]  was at least 105 degrees.
+[2089.00 --> 2092.44]  It just, you know, maybe we'd get down to 88 Fahrenheit at night.
+[2092.86 --> 2096.84]  It was so brutal, Alex, that we would go 5,000 feet up.
+[2097.12 --> 2101.46]  We would drive up Mount Lemmon, and we would stay at the top of Mount Lemmon, where it would
+[2101.46 --> 2103.90]  be about the temperature of the Pacific Northwest.
+[2104.58 --> 2107.02]  We would just sit there and wait for the data pass.
+[2107.70 --> 2108.84]  It was really hot.
+[2109.04 --> 2110.10]  How tall is that sucker?
+[2110.50 --> 2112.56]  I think it goes all the way up to 8,000 feet.
+[2113.04 --> 2115.24]  Oh, I bet that was really nice in that climate too.
+[2115.60 --> 2115.90]  Yeah.
+[2116.38 --> 2117.02]  Oh man.
+[2117.10 --> 2120.98]  Because at the bottom, it would literally be 105, and at the top, it'd be like 66 degrees.
+[2121.18 --> 2124.86]  Did you do that thing where you got in the car at the top of the mountain with the AC
+[2124.86 --> 2125.22]  running?
+[2125.32 --> 2129.68]  And then when you get out at the bottom of the mountain, you're like, oh my god, what is
+[2129.68 --> 2130.10]  this?
+[2130.78 --> 2131.14]  Boom.
+[2131.38 --> 2132.66]  Hits you in the face too.
+[2132.66 --> 2135.44]  And they were also experiencing record humidity as well.
+[2136.04 --> 2137.84]  So it was just gross.
+[2138.18 --> 2141.70]  And all of my automations around heating had to be disabled.
+[2142.02 --> 2143.08]  Everything had to go.
+[2143.78 --> 2149.70]  And I realized this was an opportunity to kind of redo how I automate heat with Home Assistant.
+[2149.70 --> 2155.80]  So traditionally, I've had a series of automations that would have conditions like sunset and
+[2155.80 --> 2156.38]  sunrise.
+[2156.76 --> 2161.48]  And then depending on the state of the sun, they would either kick on or they would kick
+[2161.48 --> 2161.82]  off.
+[2161.82 --> 2168.44]  And this also kind of fell apart because I don't yet actively update Home Assistant's
+[2168.44 --> 2170.58]  location when I'm going down the road.
+[2170.80 --> 2172.04]  I need to do that.
+[2172.40 --> 2174.96]  I have a couple of different ways I could solve that problem.
+[2175.46 --> 2181.98]  But right now, when I'm in Denver, Home Assistant still thinks I'm in the Pacific Northwest.
+[2182.36 --> 2185.10]  And when I'm in Tucson, it thinks I'm in the Pacific Northwest.
+[2185.10 --> 2189.36]  So it is going by the state of the sun in the Pacific Northwest.
+[2189.36 --> 2194.00]  And so all of my automations were offset around heating for that reason as well.
+[2194.18 --> 2196.08]  I realized I needed more control.
+[2196.58 --> 2199.70]  And over time, my wife has said sometimes she's like, you know, the automations work really
+[2199.70 --> 2199.94]  well.
+[2200.02 --> 2203.08]  But sometimes I'm just in a mood where I just want it really toasty in here.
+[2203.28 --> 2207.06]  And I find it hard to do that because the system will turn off the heaters once it reaches.
+[2207.42 --> 2211.98]  I have like a 75 degree cutoff where all the heat turns off an automation for that.
+[2212.34 --> 2216.58]  So I decided to take this opportunity after I disabled everything while we were on the road and
+[2216.58 --> 2222.36]  definitely did not need heat to instead of reimplement the traditional automations I created
+[2222.36 --> 2227.86]  almost two years ago now, I would instead replace them with the Home Assistant generic
+[2227.86 --> 2229.28]  thermostat entity.
+[2229.52 --> 2232.84]  And this is something the audience has written in and told me to do for a while.
+[2232.96 --> 2234.16]  I've been intending to do it.
+[2234.20 --> 2237.48]  And I am so, so glad I did this.
+[2237.80 --> 2241.18]  It's like I have my own homemade Nest thermostat.
+[2241.18 --> 2246.14]  Now, all it requires is you need a sensor to give it an input.
+[2246.28 --> 2247.42]  And I have sensors in every room.
+[2247.80 --> 2252.26]  And so you tell it which sensor to monitor and which what numbers you want.
+[2252.36 --> 2255.62]  You know, when the sensor returns this number, turn it on and turn off.
+[2256.26 --> 2258.96]  And what smart switch you want it to flip on and flip off.
+[2259.10 --> 2261.34]  So you need a sensor and a smart switch.
+[2261.54 --> 2262.08]  That's it.
+[2262.16 --> 2265.84]  And then anything that you plug into that smart switch will get cycled on and off.
+[2265.84 --> 2271.86]  And so I have oil heaters, these really nice, small, portable, compact oil heaters that
+[2271.86 --> 2274.04]  give off this wonderful radiant heat.
+[2275.26 --> 2281.28]  And Home Assistant now monitors the temperature and it gives you an interface that is a thermostat
+[2281.28 --> 2281.70]  interface.
+[2281.82 --> 2285.02]  And you set what you want the temperature to be.
+[2285.26 --> 2289.90]  And it will cycle the power to the heaters to maintain that.
+[2289.96 --> 2294.30]  And you can define things like make sure the minimum cycle length is 90 seconds.
+[2294.30 --> 2296.08]  So they're not just flipping on and flipping off.
+[2296.44 --> 2300.72]  And then you also have a really nice interface to just turn them off completely.
+[2301.16 --> 2305.90]  Sometimes in an RV specifically, when you're cooking and you've got a lot of high voltage
+[2305.90 --> 2310.92]  appliances going, maybe a toaster oven and a slow, you know, an instant pot.
+[2311.00 --> 2314.12]  And you got a toaster that is, you know, pulling a thousand watts.
+[2314.16 --> 2315.70]  You got an instant pot that's pulling a thousand watts.
+[2316.10 --> 2319.74]  You don't necessarily want your space heater kicking on that also pulls a thousand watts because
+[2319.74 --> 2320.50]  you'll trip a breaker.
+[2320.50 --> 2326.46]  And so now in Home Assistant, we have a tab in the dashboard that is just all of the
+[2326.46 --> 2328.12]  thermostats, which are there are four of them.
+[2328.44 --> 2333.90]  And you can turn them off so they do not automatically cycle, which was never really an option that
+[2333.90 --> 2337.22]  my wife had before because she wasn't familiar with going into the automations and turning
+[2337.22 --> 2338.42]  automations on and off manually.
+[2338.88 --> 2343.16]  So now she can just hit the little button to make sure the heaters don't automatically
+[2343.16 --> 2344.86]  cycle on, which is great.
+[2345.08 --> 2346.88]  She also has a nice UI to turn up the heat.
+[2346.88 --> 2353.12]  But then the brilliant thing about Home Assistant is if you connect it with HomeKit, you really
+[2353.12 --> 2356.30]  take things up to the next level for all of the users in your home.
+[2356.84 --> 2364.50]  So now Home Assistant automatically publishes these thermostats to HomeKit on all of our devices
+[2364.50 --> 2366.16]  that are in an iCloud family plan.
+[2366.60 --> 2372.44]  So my wife, the moment I turned these on, had those buttons on her iPhone.
+[2372.72 --> 2374.30]  She just pulls down the control center.
+[2374.94 --> 2376.02]  There's the thermostat buttons.
+[2376.02 --> 2378.14]  I mean, it just made it crazy easy for her.
+[2378.64 --> 2383.92]  Additionally, now all of those things are verbally addressable with Siri.
+[2384.38 --> 2389.94]  So she can say, Siri, set the bedroom heater to 75 degrees.
+[2390.08 --> 2392.42]  Or Siri, what is the bedroom heater temperature?
+[2393.28 --> 2396.68]  And Siri will read back the sensor information to her.
+[2396.74 --> 2397.72]  It's very simple.
+[2397.84 --> 2403.14]  And it displays the temperature now in her control center on her iPhone when she pulls that down.
+[2403.14 --> 2404.10]  Right there.
+[2404.24 --> 2405.14]  She taps on it.
+[2405.20 --> 2408.84]  It gives her this really nice UI because it's a HomeKit UI.
+[2409.04 --> 2413.74]  So it's all built in to manage the thermostat temperature with colors for when it's getting
+[2413.74 --> 2415.00]  hot and all that kind of stuff.
+[2415.46 --> 2418.62]  And she doesn't even have to touch the Home Assistant dashboard if she doesn't want to.
+[2419.26 --> 2424.30]  And anyone now in the family can ask the Siri tube to make it warmer for them.
+[2424.30 --> 2428.12]  I didn't even consider that when I set up this generic thermostat, but it's great.
+[2428.46 --> 2430.10]  But then I capped it all off.
+[2430.60 --> 2436.18]  And I would love the audience's feedback on how they do this with two automations that monitor
+[2436.18 --> 2437.96]  the sun, sunset and sunrise.
+[2437.96 --> 2445.78]  And so two hours after the sun rises, the automation sets all of the thermostats to 65 degrees.
+[2446.98 --> 2454.80]  And then an hour before the sun sets, the automation sets all the thermostats to 71 degrees.
+[2455.36 --> 2458.38]  So that way during the day, we're not running the heat more than we need to.
+[2458.86 --> 2460.88]  And I'm thinking about layering on top of that.
+[2461.04 --> 2464.80]  Once I get accurate location information, I'm thinking about layering on top of that.
+[2464.80 --> 2468.14]  When we're away, just turn them off, those kinds of conditions.
+[2468.56 --> 2471.12]  But Alex, there's lots of thermostats.
+[2471.34 --> 2476.10]  There's lots, lots of different integration options, lots with thermostats and Home Assistant.
+[2476.10 --> 2482.16]  But this generic thermostat is so flipping brilliant because all you need is a switch,
+[2482.90 --> 2485.30]  a smart switch and a temperature sensor.
+[2485.58 --> 2486.58]  That's all you need.
+[2486.62 --> 2490.42]  And you can turn anything into essentially like a Nest-like heater.
+[2490.80 --> 2493.92]  So my thermostat already has an API that I could call via curl.
+[2494.80 --> 2501.12]  Can I use the generic thermostat thing paired with those Xiaomi sensors that I have?
+[2501.44 --> 2501.74]  Sure.
+[2501.96 --> 2507.24]  If you, when you curl it, if you get the temperature and you can parse that and pass that through
+[2507.24 --> 2509.58]  as sensor data, you absolutely could.
+[2510.12 --> 2510.52]  Interesting.
+[2510.78 --> 2512.64]  Well, I will give that a try when I get back home.
+[2512.64 --> 2515.18]  I'm going to do this in the studio for the smart.
+[2515.58 --> 2521.46]  I have fans in the windows that are connected to smart plugs and I just manually turn them
+[2521.46 --> 2525.02]  on and off with Home Assistant, but I can manually turn them on and off.
+[2525.42 --> 2526.70]  This would be great to have a temperature.
+[2527.26 --> 2530.44]  Just swipe down from your control center and use it home kit, darling.
+[2530.76 --> 2530.94]  Right?
+[2531.36 --> 2531.56]  Yeah.
+[2531.56 --> 2539.06]  Now, if you're looking for a great place to go and get some self-hosting smart gear pre-flashed
+[2539.06 --> 2544.38]  with Tasmota, check out our sponsors, cloudfree.shop and mylocalbytes.com.
+[2544.66 --> 2549.20]  Both of these guys are listeners of the show who have started small businesses and we want
+[2549.20 --> 2551.58]  to help support them running these small businesses.
+[2551.58 --> 2554.82]  They have a whole bunch of gear pre-flashed with Tasmota.
+[2555.24 --> 2559.88]  Like I said earlier in the show, I actually this week bought a bunch of stuff from mylocalbytes.com
+[2559.88 --> 2564.94]  to kickstart my father's home automation desires.
+[2565.86 --> 2571.94]  Spent less than £100 and I was able to automate a good chunk of his kitchen lighting experience.
+[2572.42 --> 2574.96]  It's well worth taking a look at this stuff and it's running Tasmota.
+[2575.66 --> 2579.28]  So, you know, there's no setup or configuration required out the box.
+[2579.28 --> 2581.70]  It's broadcasting a Wi-Fi access point.
+[2581.80 --> 2582.54]  You connect to that.
+[2582.80 --> 2587.46]  You put in your Wi-Fi information, your MQTT broker information and boom, you're off to
+[2587.46 --> 2587.82]  the races.
+[2588.36 --> 2593.36]  So go over to mylocalbytes.com and cloudfree.shop and check out what those guys have to offer.
+[2593.84 --> 2597.60]  Don't forget to use the coupon code self-hosted so that you get a simple discount off your
+[2597.60 --> 2599.34]  order and that they know that we sent you.
+[2601.02 --> 2604.96]  You mentioned it earlier, but it sounds like you were doing some work on that Synology to
+[2604.96 --> 2605.84]  get ready for the trip too.
+[2605.90 --> 2606.48]  What'd you do there?
+[2606.48 --> 2610.84]  The Synology box is going to my mum's house, which will be yet another off-site backup.
+[2611.34 --> 2617.82]  But the reason I wanted to do this was I have ZFS doing its thing, you know, snapshots and
+[2617.82 --> 2619.04]  replicating to the UK.
+[2619.82 --> 2625.10]  If for some reason that whole ZFS system goes tits up, I thought to myself, it would be nice
+[2625.10 --> 2630.10]  if I had a completely separate versioned backup that's in a totally separate ecosystem.
+[2630.10 --> 2633.90]  And so I've been looking at the project Autorestick.
+[2634.04 --> 2639.52]  Well, actually, technically, Autorestick is a wrapper around Restic, which is a tool to
+[2639.52 --> 2644.28]  do remote backups and versioned backups to a whole bunch of different endpoints.
+[2644.54 --> 2651.56]  But the one that I'm going to be using is called Minio, which is a local S3 API server,
+[2651.78 --> 2652.12]  effectively.
+[2652.30 --> 2654.82]  So I'm sure you've all heard of S3 storage on Amazon.
+[2654.82 --> 2660.26]  It's, you know, what Linode calls, I forgot the name, S3 compatible object storage.
+[2660.64 --> 2661.76]  Oh, well, that's a good name, isn't it?
+[2661.84 --> 2662.02]  Yeah.
+[2662.12 --> 2663.06]  I wonder why they came up with that.
+[2664.20 --> 2666.32]  Digilotion, all the rest of them have that kind of thing as well.
+[2666.44 --> 2670.74]  So most people offer some kind of S3 compatible API.
+[2671.34 --> 2676.72]  Essentially, what it means is it stores data in objects, small little blocks of data.
+[2677.40 --> 2681.80]  Now, I wanted this data to be encrypted on the remote endpoint and Restic handles that
+[2681.80 --> 2682.92]  totally transparently.
+[2682.92 --> 2689.08]  But the really nice thing about Autorestick is using a simple, probably about 20 line YAML
+[2689.08 --> 2695.56]  file, I've been able to configure the rotation policies, the pruning policies, all the different
+[2695.56 --> 2697.44]  data sets that I want backed up.
+[2697.68 --> 2703.36]  And it's not a data set in Restic land, it's just a directory that I wanted backed up to
+[2703.36 --> 2704.08]  the remote system.
+[2704.36 --> 2710.72]  And then I'm running Minio as a container behind traffic on the Synology, which is running
+[2710.72 --> 2711.60]  DSM-7.
+[2712.24 --> 2716.98]  And I've written a blog post, which I'll put in the show notes about how to configure
+[2716.98 --> 2720.34]  traffic to do a whole bunch of stuff with Synology DSM-7.
+[2721.36 --> 2726.44]  So I've got Minio running through traffic on the Synology, which I then have a DNS entry
+[2726.44 --> 2732.52]  on my US server through Tailscale, which is then able to route all the traffic and punch
+[2732.52 --> 2738.18]  holes through NAT, all the way through to the Synology box that's living at my mom's house
+[2738.18 --> 2738.46]  now.
+[2739.10 --> 2745.88]  And so I just have two separate UK, totally separate UK backup systems on totally different
+[2745.88 --> 2746.90]  paradigms.
+[2746.90 --> 2752.98]  Alex, that might be the ultimate offsite setup with when you consider you have both locations
+[2752.98 --> 2756.60]  and one location is like an exact hardware match.
+[2756.78 --> 2761.34]  And so you can do A-B testing and another location is a totally different ecosystem that
+[2761.34 --> 2764.04]  still well managed, going to run forever.
+[2764.38 --> 2767.76]  Like, yeah, you are set for years, I think.
+[2768.12 --> 2768.70]  It's one of those things.
+[2768.78 --> 2774.26]  I think I'm probably over-egging the pudding at the likelihood of Basingstoke and Lancaster
+[2774.26 --> 2779.32]  and Raleigh all going, you know, south at the same time is probably very unlikely.
+[2780.44 --> 2783.96]  But if it happens, I'll be okay now.
+[2784.72 --> 2786.98]  You can go find our friends at CloudGuru on social media.
+[2787.08 --> 2791.78]  They're just slash a CloudGuru everywhere, like YouTube and Twitter and the Facebook and
+[2791.78 --> 2793.10]  pretty much anything that's a social network.
+[2793.60 --> 2794.10]  Go find them.
+[2794.48 --> 2795.52]  Social network slash a CloudGuru.
+[2795.96 --> 2799.70]  Now, I know I've been banging on about it all episode, but I'm back in the UK this week
+[2799.70 --> 2801.16]  and it is glorious.
+[2801.16 --> 2805.10]  So I'm actually going to be meeting up with a couple of listeners in the Norwich area,
+[2805.28 --> 2810.50]  a place called Breckland Lodge on the A11 just outside Attleborough near Norwich.
+[2811.04 --> 2816.28]  We're going to be doing that on Tuesday, the 28th of September at 6pm UK time.
+[2816.86 --> 2820.68]  So if you want to come say hi to me, Gary, who was on Late Night Linux a couple of weeks
+[2820.68 --> 2824.48]  ago, a couple of other people said they were already going to be there.
+[2824.60 --> 2825.98]  It's a bit of an impromptu meetup.
+[2826.06 --> 2828.84]  We hope it'll be nice and small just for COVID safety, that kind of thing.
+[2828.84 --> 2833.48]  But if you want to come say hi, I'll be there and I'll be wearing my Chris and the Badger
+[2833.48 --> 2833.84]  t-shirt.
+[2834.46 --> 2834.70]  Nice.
+[2834.88 --> 2837.32]  Boy, you guys have the best names for places over there.
+[2837.48 --> 2838.26]  They're so adorable.
+[2838.64 --> 2842.58]  We'd love to hear your feedback, your ideas, anything that caught your attention.
+[2842.86 --> 2844.34]  Self-hosted.show slash contact.
+[2844.54 --> 2845.84]  That's the place to get in touch with us.
+[2846.30 --> 2847.90]  And of course, you can find me on Twitter.
+[2848.02 --> 2849.18]  I'm at Chris LAS.
+[2849.66 --> 2851.14]  And I'm there at Ironic Badger.
+[2851.30 --> 2853.10]  And as always, thanks for listening, everybody.
+[2853.32 --> 2855.62]  That was self-hosted.show slash 54.
+[2855.62 --> 2855.74]  Cool.

55： Home Assistant Turns Amber _summary.txt

@@ -0,0 +1,87 @@
+• Starlink kit arrival and expectations
+• Setup requirements for Starlink at home, including a dedicated PC
+• Geographic restrictions on Starlink usage, such as grid reference points and service address updates
+• Potential issues with high power consumption of the dish (150 watts)
+• Cost of the Starlink kit ($485) and monthly service fees
+• Benefits of reliable internet, especially for remote work and online learning
+• Ping times and latency expectations for Starlink (40-60 ms)
+• Comparison to LTE connectivity and potential advantages of Starlink
+• Concerns about rural internet access and the limitations of current options
+• Starlink as a potential solution for reliable internet connectivity
+• The impact of limited internet access on remote work and personal life
+• Excitement about Home Assistant's official Tuya integration, but concerns about cloud dependence
+• Preference for local control protocols such as Zigbee or Matter over cloud-dependent solutions
+• Discussion of Z-Wave and Zigbee devices
+• Release update for Home Assistant
+• Statistics on Home Assistant usage and user behavior
+• New features in Z-Wave.js integration, including improved security and reliability
+• Migration to Z-Wave.js from OpenZW or original Z-Wave setup
+• Developers' confidence in the new Z-Wave.js integration
+• Potential official certification of Z-Wave.js from the Z-Wave group
+• Improved pairing process for Z-Wave devices
+• The host discusses opening a repository in VS Code using the browser on github.com
+• Features of VS Code in the browser are demonstrated, including automatic commit and merge requests
+• The Linux kernel course on A Cloud Guru is announced
+• Home Assistant releases a new hardware project called Amber based on the Compute Module 4
+• Concerns about upgrading to a future CM5 module are raised due to the Raspberry Pi 4's lifecycle
+• I/O limitations of the Raspberry Pi 4 are mentioned and how EMMC or SSD solves this issue
+• The speaker discusses their experience with a device that is no longer available, the "blue", and notes its limitations compared to other devices.
+• They speculate about the future of the blue board, which may be phased out in favor of newer models.
+• The conversation turns to Home Assistant and its software updates, including the addition of 400 new icons.
+• The speaker expresses enthusiasm for the updated icons and mentions a rumored icon picker feature.
+• A sponsor advertisement is inserted, promoting Linode's cloud computing services.
+• Linode cloud computing services, including VLAN support, DNS manager, Terraform, and Kubernetes integration
+• Benefits of using Linode, such as lower pricing (30-50% cheaper) and flexibility in deployment across multiple clouds
+• Importance of avoiding vendor lock-in and having a multi-cloud strategy
+• Discussion of recent Facebook outage and its impact on user experience
+• Comparison of the Facebook outage to other tech companies' outages, including speculation about intentional sabotage or whistle-blower-related motives
+• Home Assistant energy monitoring support and setup for smart plug integration
+• User has difficulty getting energy monitoring working in Home Assistant
+• Home Assistant wants data in kilowatt hours, but user's smart plugs report in watts
+• Need to use a math integration to convert watts to kilowatt hours
+• Must create template sensors for each smart plug to format data correctly
+• Process is more complex than expected and requires learning about templating and sensor creation
+• Energy utilities built into Home Assistant can then pull stats from the formatted devices
+• The speaker felt overwhelmed by the complexity of Home Assistant and the introduction of new energy monitoring features
+• Many resources for Home Assistant are outdated due to its fast-paced development
+• Setting up utility meters and history stats integrations allowed the speaker to collect and display historical power usage data
+• Virtual sensors were created using these integrations, enabling dashboards that provide valuable insights into energy consumption patterns
+• The speaker prefers their custom-built solution over the built-in energy support in Home Assistant
+• Discussion of TubeSync, a tool that pulls down YouTube videos and provides a dashboard with features such as video source tracking and upcoming content.
+• Mention of MediaCMS.io, a self-hosted YouTube front-end clone that allows for curation of approved channels and playlists.
+• Potential use of TubeSync to download videos from YouTube and then importing them into Plex for archiving.
+• Discussion of using MediaCMS.io to create a pseudo-Youtube instance for personal use.
+• Review of MediaCMS.io features, including dark mode, light mode, and multiple transcoding profiles.
+• Experimental support for remote workers
+• Backing up iPhone photos using iCloud and a tool called Gimme-iPhotos
+• iOS restrictions on background APIs
+• Comparing iOS to Android in terms of device management
+• Using Python to automate tasks with the Gimme-iPhotos tool
+• Two-factor authentication mechanism supported by the tool
+• Discussion of a tool that can download photos from iCloud
+• Tool uses an official Apple API and can run on a NAS box
+• Killer use case: accessing iOS phones' photos via a NAS box, especially for elderly relatives who struggle to transfer photos
+• Uncertainty about two-factor authentication token expiration time
+• Proposal to test the tool with parents' devices and report back in 6 months
+• Backblaze's 30-day money-back guarantee and return policy
+• Peace of mind with physical hard drive backup via FedEx
+• Additional features, including retention history extension and mobile apps for accessing files on-the-go
+• Reviews and recommendations from reputable sources such as New York Times, Macworld, and Tom's Guide
+• Availability of a free 15-day trial at backblaze.com/SSH
+• Company background and growth, with over 500,000 customers in 175 countries
+• Mention of Tailscale and its availability on Synology
+• Discussion of Tailscale and its ease of use compared to WireGuard
+• Setting up Tailscale with Synology NAS devices for remote access
+• Positive feedback from listeners about using Tailscale
+• Comparison between setting up Tailscale and setting up WireGuard
+• Various ways to install and use Tailscale (e.g. on phone, desktop, server)
+• ZeroTier, a distributed WAN solution and alternative to Nebula
+• Comparison with Tailscale and WireGuard protocols
+• Discussion of self-hosted options for networking solutions
+• Mention of upcoming DNS solution from ZeroTier
+• Plug for Nebula and discussion of various networking projects
+• Home Assistant setup for energy monitoring and automation
+• Z-Wave device updates and potential lag issues
+• Using Matrix, Discord, or Telegram for community support
+• Integrating devices to avoid circuit overloading concerns
+• Solutions for energy monitoring in self-hosting communities

55： Home Assistant Turns Amber _transcript.txt

@@ -0,0 +1,1373 @@
+[0.00 --> 6.10]  Alex, I'm checking my email every single day right now because my Starlink kit is on its way.
+[6.22 --> 7.70]  This is going to be a game changer for me.
+[8.52 --> 9.48]  I think so, yeah.
+[9.74 --> 14.88]  You've unlocked a level, you've one-upped life if you've got Starlink.
+[15.04 --> 19.64]  You know what's funny is I started thinking, now I need to get serious about a home PC setup.
+[20.06 --> 24.10]  I'm always like, my work laptop will do or an iPad will do.
+[24.10 --> 29.66]  But if I'm going to have real internet at home now, I got to have a real PC to connect to that.
+[30.00 --> 30.88]  So how's it going to work?
+[30.92 --> 33.90]  Because my understanding of Starlink is reasonably limited.
+[34.30 --> 35.86]  I watched a couple of Jeff Geerling videos.
+[36.12 --> 37.70]  I think that's about as far as it goes.
+[38.64 --> 44.80]  Don't you have to tie it to a specific grid reference so that they have enough satellite bandwidth for you to talk to?
+[44.88 --> 47.88]  Like it won't work if you drive 50 miles west or something, right?
+[47.88 --> 54.58]  Yeah, I think it mostly turns out to be like a 30-mile area around your service address that you've put on your account is where it's functional.
+[55.14 --> 56.10]  I don't know yet.
+[56.20 --> 59.46]  This is something I'm going to play with, but it sounds like it's pretty straightforward.
+[60.00 --> 63.40]  In most cases, to just update your service address.
+[63.70 --> 68.72]  And then like it takes effect in like 15 minutes and then you can start setting up in your new location.
+[69.10 --> 72.70]  I imagine that's actually not as smooth as it's going to go.
+[72.98 --> 75.96]  Like I'll try to do it and be like too many users in this area.
+[75.96 --> 85.74]  Yeah, I recall I was watching a guy on YouTube who was an RVer and was proclaiming that he had hacked the Starlink algorithm to let him use it anywhere.
+[86.18 --> 93.22]  In actual fact, what he was doing was he was pre-staging his location in the Starlink app before he got there.
+[93.28 --> 99.16]  So the systems had time to catch up or if where he got to didn't have connection to update his service address.
+[99.16 --> 103.38]  I mean, I could see that because I generally know where I'm going to end up parking at, you know, before I go there.
+[103.42 --> 104.86]  So I could plug that in before I arrive.
+[105.34 --> 112.48]  The other tricky thing is, is I think the little dishy takes like 150 watts pretty much consistently once it's up and running.
+[112.60 --> 114.32]  That's a significant amount of power.
+[114.38 --> 116.04]  In fact, it's like running a whole PC.
+[116.36 --> 117.16]  It is pretty much, isn't it?
+[117.16 --> 118.16]  And they're not cheap either.
+[118.16 --> 122.46]  So there was the $99 deposit, which I felt was fair.
+[122.70 --> 123.02]  Okay.
+[123.22 --> 123.78]  All right, fine.
+[124.42 --> 130.22]  And then there's like a separate $485 fee to get the kit.
+[130.30 --> 131.66]  And the kit is everything you need.
+[131.72 --> 136.02]  It's like the router, Ethernet, the POE injector, the dish, all of it.
+[136.72 --> 138.32]  But every time I check, it just says pending.
+[138.98 --> 141.20]  So you're $600 in the hole for this thing then?
+[141.56 --> 143.40]  And then the monthly service, of course, as well.
+[143.66 --> 144.86]  Oh, what does that cost?
+[144.86 --> 147.20]  I think it's going to be in the $100 range.
+[147.20 --> 154.58]  When you don't have good, solid bandwidth, almost any price that you can conceivably afford to pay is worth it.
+[155.02 --> 155.10]  Yeah.
+[155.28 --> 156.94]  Slow internet is worse than no internet.
+[157.58 --> 158.54]  That's what they say.
+[159.02 --> 161.44]  And then once you get that good internet, head over to a Cloud Guru.
+[161.56 --> 164.44]  They are the leader in learning for the cloud, Linux, and other modern tech skills.
+[165.38 --> 171.96]  Thousands of hands-on labs, hundreds of certifications and courses, and free cloud sandboxes on their credit card, not yours.
+[172.06 --> 173.62]  Go to cloudguru.com.
+[174.04 --> 175.80]  Get certified, get hired, get learning.
+[175.80 --> 180.92]  So I can only imagine how having decent, low ping internet.
+[181.04 --> 185.38]  Do you have any sense of the Starlink kind of ping times yet?
+[185.54 --> 188.02]  I have done a little bit of meta-analysis of the reviews.
+[188.44 --> 193.80]  And also, to their credit, the Starlink folks kind of give you that information in the sign-up process when they're like,
+[193.86 --> 194.62]  hey, this is a beta.
+[195.10 --> 196.66]  It's going to go down sometime.
+[196.66 --> 202.12]  You're probably going to get ping somewhere in the 40 millisecond range is what they kind of warn you for.
+[202.22 --> 204.82]  And that's kind of what I've seen from the meta-analysis of the reviews.
+[205.24 --> 207.76]  I have seen some reviewers get it as low as 20.
+[207.76 --> 217.24]  Something in the 20 to 40 would be great because 40 is about the best case I'm ever going to get ever on LTE is about 40 milliseconds.
+[217.24 --> 230.04]  And I know from having done these shows with you now for a long time, an LTE connection is workable, but we end up stepping on each other quite often and makes life for our editor more difficult.
+[230.22 --> 232.32]  So lower the ping time for us, certainly the better.
+[232.32 --> 249.38]  And also, I would imagine, although we'll see, I'll get a sense of this, is it would hopefully, I know it drifts, but hopefully it drifts either less or more consistently than LTE, where LTE is kind of all over the board depending on all the other users that are in that area.
+[250.04 --> 253.94]  Are there any constraints around the amount of bandwidth you can consume?
+[254.04 --> 255.70]  Because with LTE, that's a big concern.
+[256.02 --> 256.22]  Right.
+[256.28 --> 257.88]  And as far as I know, there's no limits either.
+[257.88 --> 262.38]  I don't know if eventually when they go public, if they'll have tiered plans, but that's a huge deal.
+[263.02 --> 265.10]  No, no, no, no, no, no.
+[265.16 --> 265.54]  I know.
+[265.80 --> 266.18]  I know.
+[267.22 --> 274.02]  Even with my quote unquote unlimited LTE plans, I'm really kind of in the doghouse after 300 gigs.
+[274.02 --> 276.96]  And around 400 gigs, they're looking at what I'm doing.
+[277.26 --> 280.52]  And, you know, I get deprioritized and all that kind of stuff.
+[280.52 --> 283.14]  And that is like on the extremely high end.
+[283.14 --> 288.20]  Like these are elite rare plans where I can even get that far along before they start getting mad at me.
+[288.44 --> 288.92]  That's crazy.
+[289.16 --> 299.94]  Where I was staying last week at my mother-in-law's in rural Norfolk, the only decent internet that she can get is through 4G LTE from EE in the UK.
+[299.94 --> 305.00]  And she gets 200 gigabytes a month bandwidth for her home internet.
+[305.00 --> 311.60]  And for me, that was a real adjustment, you know, dealing with that ping time, dealing with that lack of bandwidth availability.
+[312.02 --> 312.64]  Welcome to my world.
+[312.92 --> 315.58]  I honestly don't know how you cope with it full time.
+[315.92 --> 316.62]  I know.
+[316.92 --> 317.28]  I know.
+[317.32 --> 324.30]  That's why I'm really excited about Starlink, even though there's the downside of putting more junk up in space, which is a serious problem.
+[324.30 --> 330.86]  And these may actually be visible from the ground and maybe, you know, there's, we're not going to be happy about that long term.
+[331.18 --> 342.76]  But it's so obvious that at least here in the States, we need a solution to this because my other options are duopoly cell providers or a monopoly cable provider.
+[342.94 --> 345.36]  Those are my options here.
+[345.36 --> 356.54]  And it just isn't, it is not long-term sustainable or tenable for something as important as our connectivity, which is how I organize, manage, and run my entire business.
+[356.54 --> 359.46]  And most of my personal life is all online now.
+[359.48 --> 362.12]  And that's true for probably nearly everyone listening to this show.
+[362.24 --> 369.50]  And so access to the internet just is so critical that I think it's kind of necessary that we have something like Starlink as an option.
+[369.50 --> 381.08]  And if they can get these prices down to below what I'm paying for these ridiculous LTE plans, I mean, that's going to make it more available to more people and, you know, eventually to folks like Alex's mom.
+[381.72 --> 384.56]  It's going to be a game changer for a lot of people.
+[384.88 --> 389.70]  There are remote mountain properties that you look at these days on Zillow or Rightmove or whatever.
+[390.06 --> 394.24]  And you think, oh, I'd love to, no, it's going to have two meg ADSL.
+[394.50 --> 397.14]  I can't, I just can't even consider it, you know?
+[397.14 --> 415.46]  Yeah, and I think ultimately, Alex, it's going to make something like my end dream, building some off-grid property a lot more feasible because all of the areas I've looked at in the Pacific Northwest that I could even begin to remotely afford that have water or something like that, they're all outside of cellular range.
+[415.54 --> 416.48]  There's nothing around.
+[416.56 --> 417.74]  There's no services.
+[417.74 --> 428.30]  And the idea that I could go out there with my solar-powered RV and set up a little Dishy and get a connection to the internet from space, it's just amazing.
+[428.66 --> 429.18]  I mean, it's huge.
+[429.86 --> 430.18]  Dishy.
+[430.34 --> 431.50]  What an adorable little name.
+[432.10 --> 434.24]  Did you see that Home Assistant had a release this week?
+[434.44 --> 435.28]  It seems like a big one.
+[435.38 --> 441.92]  You know, it's hard to tell from the outside, like, which ones are kind of just the minor updates and which ones are the big ones.
+[441.92 --> 447.88]  And the one that came out as we're recording is the October release that came out on October 6th.
+[448.46 --> 450.12]  There's a big thing in here, Alex.
+[450.20 --> 454.48]  They got official Tuya integration from the folks at Tuya.
+[454.88 --> 462.60]  The people that organize all the Tuya devices and run the Tuya infrastructure have now created an official integration for Home Assistant.
+[463.34 --> 464.38]  So here's the thing about this.
+[464.50 --> 470.86]  I mean, I think it's awesome that we're starting to get actual vendors looking at Home Assistant and going, yes, I want to support that.
+[470.86 --> 478.96]  But also, you know, we've got stuff like cloudfree.shop and mylocalbytes.com and that kind of thing.
+[479.08 --> 486.80]  And there's other things coming along with pre-Tasmodo Flash devices that this becomes less important to me.
+[487.56 --> 490.78]  Well, even more so because this is the cloud integration.
+[491.38 --> 495.24]  They worked with the cloud API team, not with, like, the firmware team.
+[495.54 --> 498.26]  And so this doesn't work for local integration.
+[498.26 --> 500.16]  This uses the cloud connectivity.
+[500.54 --> 502.28]  It looks like it's doing a really good job.
+[502.36 --> 504.82]  In fact, it's much better than before, much quicker, all of that.
+[505.42 --> 506.40]  It's what you'd want.
+[506.46 --> 507.12]  And it's official.
+[507.58 --> 514.66]  But it does require their cloud API, which means it requires an internet connection, which means it's a disqualifier for me.
+[514.86 --> 517.50]  Just like you said, I'd rather get a device I could control locally.
+[517.84 --> 520.60]  In fact, I'd rather get a device that's not on Wi-Fi.
+[521.10 --> 522.46]  What's your preferred poison these days?
+[522.54 --> 524.38]  Are you a Z-Wave or a Zigbee type of chat?
+[524.38 --> 528.22]  If you go by the number of devices I have, it'd be Z-Wave.
+[528.44 --> 534.48]  But if you go by where I plan to go to, it'd be Zigbee and Matter because that's going to be one and the same, I think, eventually.
+[535.04 --> 542.24]  Matter, I think, is really kind of exciting because if a vendor adopts the Matter protocol, then there is a local API.
+[542.58 --> 545.20]  If you use Matter, then you've got a local API.
+[545.44 --> 547.40]  And that, to me, is like, well, that's a no-brainer.
+[547.40 --> 553.36]  But right now, I invested pretty early in Z-Wave, and I've been very happy with my Z-Wave devices.
+[553.50 --> 555.34]  In fact, I'll talk about that in a little bit more.
+[555.60 --> 562.10]  But for me, Wi-Fi, it's just I like to be able to reboot my access points and maintain control of my devices.
+[562.60 --> 565.76]  I don't like putting that load on my Wi-Fi network.
+[565.76 --> 571.50]  And if it works with Z-Wave or Zigbee, I almost am guaranteed I can make it work somehow with Home Assistant.
+[571.86 --> 572.56]  That's very true.
+[573.04 --> 579.36]  The stuff I talked about in the last episode at my dad's house, the Zigbee buttons I put in here, he's been delighted with them.
+[579.60 --> 583.10]  The little IKEA Trad Free buttons, I think is what they're called.
+[584.00 --> 585.04]  They're working great.
+[585.28 --> 588.80]  So you get a plus one on Zigbee from me anyway.
+[589.16 --> 591.56]  I'm going to hold out with my Z-Wave devices for now.
+[592.04 --> 594.74]  And then when the Matter stuff settles, I may make a transition.
+[594.74 --> 599.50]  But Alex, with the release, they had a live stream, kind of like a release party with the developers.
+[599.50 --> 602.46]  And they brought on some of the developers from Tuya.
+[602.76 --> 609.66]  And they talked about some stats, the opt-in stats that people can get into and then send their information off anonymously.
+[609.86 --> 615.38]  They said that for the people that have opted in, they now show 90,000 active Home Assistant users.
+[615.82 --> 621.80]  That's just since April when they launched this statistics package and the people who have opted into it.
+[621.80 --> 626.04]  Also, the data shows that a lot of people have not updated since that April release.
+[628.82 --> 630.36]  Oh boy, that's a lot.
+[630.64 --> 632.68]  That's a lot of updates since they're doing a monthly now.
+[633.12 --> 637.32]  Also, their analytics show that 40% of Home Assistant users have a Chromecast.
+[637.32 --> 641.52]  40% is a huge, huge number for that kind of thing.
+[642.40 --> 644.54]  HomeKit also shows as quite popular.
+[644.80 --> 654.06]  And the most popular hardware was the Raspberry Pi, followed closely by running Home Assistant in a VM like you do.
+[654.58 --> 657.78]  Now, do they take statistics on how many of those Raspberry Pi users are you?
+[657.78 --> 661.72]  Very fair, very fair.
+[662.20 --> 668.54]  All those stats are public at analytics.home-assistant.io, or we'll put a link in the show notes.
+[669.04 --> 675.46]  This is also the release for us Z-Wave users where it's time to migrate to Z-Wave.js.
+[676.02 --> 680.66]  As of this release, it now supports S2, which is the improved security model.
+[681.16 --> 682.78]  And it's short for security too.
+[682.96 --> 683.54]  Surprise, surprise.
+[683.54 --> 687.44]  Besides improved security, devices are also more reliable.
+[687.68 --> 693.86]  They provide greater battery life and less latency compared to the original security mode that was supported by Z-Wave.js.
+[694.70 --> 699.24]  The integration will now automatically pick the best and optimal security method available.
+[699.42 --> 702.66]  They have a whole new wizard for adding new devices, and it looks sharp.
+[703.06 --> 711.00]  Oh, and speaking of wizards, there is now a migration wizard to migrate you from your old Z-Wave setup to the new Z-Wave.js, which is what I was waiting for.
+[711.00 --> 717.44]  However, when I go in my home assistant, it actually is still asking me to migrate to OpenZW or whatever it was.
+[717.50 --> 720.46]  I don't know why, but I'm still getting a migration offer to OpenZW.
+[720.62 --> 725.50]  And I don't know if I'm supposed to install Z-Wave.js first or what.
+[725.60 --> 726.98]  Like, they don't give you any information on that.
+[727.10 --> 731.92]  But if your system isn't wonky like mine, they're saying go ahead and make the migration now.
+[732.00 --> 733.16]  It's been pretty refined.
+[733.44 --> 736.12]  It'll walk you through what it's going to do and what's going to change.
+[736.12 --> 741.24]  And then, Alex, the developers in the stream kind of doubled down, which made me feel good about using Z-Wave.
+[741.36 --> 745.44]  They said this Z-Wave.js integration is well-written.
+[745.98 --> 750.00]  It's well-built, and it is well-maintained, and they think it's good code.
+[750.64 --> 751.48]  And so it's solid.
+[751.74 --> 752.90]  It's a good...
+[752.90 --> 754.26]  In fact, they're going to go for...
+[754.26 --> 754.68]  They're thinking.
+[755.20 --> 763.08]  They haven't said they're going to do this, but they're thinking seriously about going for official Z-Wave certification from the Z-Wave group because they're so proud of how this has turned out.
+[763.08 --> 765.82]  Oh, really? That'd be a huge success.
+[766.06 --> 776.22]  I bought a Z-Wave smart door lock on some kind of sale on Black Friday, and it's been sat in a box ever since because I couldn't ever get it to pair.
+[776.84 --> 779.64]  So maybe now is the time I can...
+[779.64 --> 783.44]  With that new S2 security support that's in there, maybe I should give that another go.
+[783.80 --> 790.34]  Yeah, and it gives you a little more information, and it's a little more clear about when you should go hit the pair button on the device.
+[790.34 --> 793.60]  Like, all of that whole process is a little smoother now.
+[793.96 --> 795.26]  It looks with Z-Wave.js.
+[795.50 --> 798.22]  They did a little live demonstration of a migration on the stream.
+[798.48 --> 802.08]  I just remember it being frustrating as anything, you know, when I tried it.
+[802.94 --> 805.14]  Yeah, it feels a bit like a black box, doesn't it?
+[805.38 --> 808.44]  But no, I think they're doing good things.
+[808.62 --> 814.00]  So if you are a Z-Wave device user, which, you know, I probably have somewhere near...
+[814.00 --> 815.82]  I think I have like a dozen Z-Wave devices.
+[815.82 --> 821.78]  It's not like an unbelievable number that I can eventually migrate off of, but I'll be using them still for a while.
+[822.52 --> 828.60]  All right, I've got a low-key, genuinely awesome feature that's come to GitHub, I think, in the last two or three months.
+[829.24 --> 831.50]  Load up a GitHub repository right now.
+[832.20 --> 833.10]  You can do this live.
+[833.68 --> 836.24]  And open a repository.
+[836.62 --> 837.58]  You just need to be logged in.
+[837.62 --> 838.46]  That's the important thing.
+[839.06 --> 844.14]  When you have that page open, press full stop, the period key on your keyboard, and watch what happens.
+[844.14 --> 847.00]  Oh, that's pretty nice.
+[847.18 --> 848.32]  Oh, look at them.
+[848.46 --> 849.06]  Yeah, right?
+[849.48 --> 851.20]  Straight into VS Code Web.
+[851.38 --> 854.04]  Suddenly, Electron doesn't look so bad now, huh, does it?
+[854.24 --> 856.98]  It's that repository opened up in VS Code, isn't it?
+[857.04 --> 857.24]  Right?
+[857.30 --> 857.84]  It better be.
+[857.90 --> 858.14]  Yep.
+[858.26 --> 859.42]  Oh, that's slick.
+[859.56 --> 860.64]  Okay, impressive.
+[860.98 --> 872.22]  And then you open a file, you make an edit, you press save, and it then is because it's part of Git, the Git plugin in VS Code, you just commit it directly in there, and boom, you're done.
+[872.54 --> 873.38]  Oh my gosh.
+[873.38 --> 886.44]  If you're opening a third-party repository, though, and you make a change and you save it, it asks you then if you want to fork it, and then automatically helps you with the pull merge request model that GitHub has.
+[886.84 --> 887.20]  Wow.
+[887.30 --> 889.92]  It is so cool in the browser.
+[890.42 --> 892.12]  When did they sneak this in?
+[892.24 --> 892.68]  I don't know.
+[892.76 --> 896.74]  I mean, I first found it, someone on our Discord told me a couple of months ago about it, I think.
+[896.84 --> 897.36]  Of course.
+[897.36 --> 901.02]  But I've been using it a lot for my notes in the last few weeks, actually.
+[901.10 --> 909.82]  I've got a private repository on GitHub I use for notes, and I've actually just ended up using VS Code in the browser on github.com.
+[909.96 --> 911.38]  It's not very self-hosted, is it?
+[911.44 --> 913.10]  But it works very well.
+[913.10 --> 918.32]  And I want to mention our friends at A Cloud Guru have a course on the Linux kernel.
+[918.44 --> 923.00]  It's a standalone course, but it's also part of a learning path to prepare you for the LPIC 201 exam.
+[923.70 --> 927.56]  You'll learn how the Linux kernel provides an interface between hardware and software.
+[927.78 --> 929.84]  You'll compile a kernel from start to finish.
+[930.20 --> 937.22]  And of course, you'll cover kernel runtime management, troubleshooting, adding and removing modules, and modifying the modules on boot.
+[937.22 --> 941.40]  We'll have a link in our show notes where you can go to a Cloud Guru and search for the Linux kernel.
+[943.70 --> 946.90]  So we were just talking about ZigBee and Z-Wave and all that kind of stuff.
+[947.04 --> 951.18]  And I was really excited to see that the Home Assistant has a new hardware project out.
+[951.54 --> 952.36]  Yeah, and it's been funded.
+[952.96 --> 958.06]  The Home Assistant Amber, which is based around the Compute Module 4, with their own board.
+[958.14 --> 959.36]  It's got an SSD connector.
+[959.52 --> 961.14]  It has ZigBee built in.
+[961.58 --> 963.22]  In fact, the devs on the stream said,
+[963.38 --> 964.68]  no SD cards.
+[964.82 --> 966.28]  We hate SD cards.
+[966.28 --> 969.90]  So you can either use an SSD or it'll come with eMMC built into it.
+[970.42 --> 973.04]  They're going to ship it with a transparent case.
+[973.66 --> 975.78]  I think maybe in part for radio.
+[976.12 --> 977.56]  It's plastic for radio transparency.
+[977.68 --> 980.24]  And then they have a whole post on why they chose transparent.
+[980.68 --> 983.38]  Some models will come with a POE hat as well.
+[984.34 --> 985.32]  It's pretty nice looking.
+[985.74 --> 989.42]  Although I don't know if it's going to be as fast as the Home Assistant Blue.
+[989.90 --> 992.32]  Well, no, I mean, my only concern about this box,
+[992.32 --> 996.40]  and let me just preface everything I'm about to say with the fact,
+[996.46 --> 1001.08]  I think that these kind of projects from Home Assistant themselves are wonderful.
+[1001.08 --> 1003.24]  And I'm so happy to see that they're doing it.
+[1003.70 --> 1011.62]  My only concern is that putting the Compute Module 4 into a product at this stage in the Raspberry Pi 4's lifecycle
+[1011.62 --> 1017.66]  feels like we're getting towards the end of the Pi 4 cycle, maybe.
+[1018.40 --> 1022.32]  Are we going to be able to upgrade this to a CM5 one day?
+[1022.42 --> 1023.10]  Probably not.
+[1023.24 --> 1027.06]  Will there be a Home Assistant burnt Sienna instead or something?
+[1027.14 --> 1027.52]  I don't know.
+[1027.60 --> 1029.46]  But that's my only reservation.
+[1029.64 --> 1030.78]  Everything else looks great.
+[1030.78 --> 1033.36]  Yeah, perhaps that could be an issue.
+[1033.78 --> 1036.90]  I don't know if we know for sure if there will be a Compute Module 5.
+[1037.10 --> 1039.32]  This may be a, you know, once every few years.
+[1039.64 --> 1040.62]  That's a good point, Christopher.
+[1041.04 --> 1048.30]  The other thing that holds the Raspberry Pi 4 back right now is absolutely the I.O. situation.
+[1048.68 --> 1052.74]  And they solve that with EMMC or an SSD.
+[1053.24 --> 1053.44]  Yeah.
+[1053.44 --> 1055.64]  I mean, it's no x86 box, right?
+[1055.64 --> 1062.88]  Like, I've got jobs where I need more powerful systems, but I am doing more than ever with my Pi 4.
+[1063.08 --> 1068.28]  I mean, now it's doing MQTT and it's doing energy metric collection and graphing.
+[1068.64 --> 1071.88]  And it's still just chugging right along.
+[1072.32 --> 1076.52]  Like, it's just, oh, and also for a short period of time, I even ran the Wise Bridge on it.
+[1076.78 --> 1077.18]  Really?
+[1077.18 --> 1078.60]  It was still doing just, yeah.
+[1079.00 --> 1080.54]  Oh, that thing chomps the CPU.
+[1080.90 --> 1082.34]  Only with two camera feeds, let me be clear.
+[1082.42 --> 1083.22]  And I turned it off.
+[1083.30 --> 1083.88]  I did turn it off.
+[1083.88 --> 1086.08]  But Home Assist and everything was still working.
+[1086.26 --> 1089.00]  Like, it still has a little bit of oomph to spare.
+[1089.80 --> 1099.56]  And I could see the Compute 4 module being enough machine for most people until you get into more advanced logging and graphing and stuff like that.
+[1099.74 --> 1102.84]  So what does this mean for the blue then, moving forward?
+[1103.10 --> 1106.38]  Well, it seems like the blue is kind of going to phase out over time.
+[1107.06 --> 1112.66]  I think the words used were, we're going to take the lessons learned and we're applying that to the amber.
+[1112.66 --> 1121.48]  One thing about the blue that was noted by the developers is that it's a board that they took that already existed.
+[1122.18 --> 1125.10]  And then, you know, they flashed Home Assistant onto it.
+[1125.20 --> 1129.72]  But if you want Zigbee or Z-Wave or Matter Support, you got to add a dongle.
+[1129.72 --> 1138.54]  And it's not really flexible in that regard where this is a device that they kind of control the board that the compute module is going to sit in.
+[1138.84 --> 1140.82]  They can integrate things like Zigbee.
+[1141.08 --> 1142.96]  They can do things like PoE.
+[1142.96 --> 1152.66]  And it seems like when you look at also their hardware stats we talked about earlier and you see so many, so many users are using the Raspberry Pi.
+[1153.04 --> 1162.94]  It probably makes sense from like a software end user reliability stability standpoint to base your core product on that same platform if you can.
+[1163.30 --> 1170.24]  Because then improvements you make there are going to benefit everybody else also using the Raspberry Pi that isn't running on an amber.
+[1170.34 --> 1171.06]  They're just on a pi.
+[1171.06 --> 1172.84]  Yeah, I hadn't considered that angle.
+[1173.00 --> 1173.88]  That's an interesting one.
+[1174.46 --> 1181.50]  And Alex, if you'll allow me, there's one small update in this October Home Assistant release that I wanted to talk about.
+[1182.10 --> 1184.34]  It wasn't initially going to cover it, so I feel kind of embarrassed.
+[1184.50 --> 1185.48]  But it's icons.
+[1185.74 --> 1189.14]  They updated the material design icons to version 6.
+[1189.50 --> 1191.30]  They've added 400 new icons.
+[1191.30 --> 1207.60]  And if you haven't done this yet to your Home Assistant update, I know all this has been very Home Assistant specific, but I tell you what, it made me love my dashboard a little bit more when I went in there and just tweaked the icons for all the different entities.
+[1207.60 --> 1210.42]  So they all have unique individual icons that represent what they are.
+[1210.42 --> 1223.04]  And rumor has it, based on what the devs accidentally said on the live stream, they're going to include in the Lovelace wizard a new icon picker soon that lets you easily pick from these icons.
+[1223.20 --> 1224.28]  Oh, good.
+[1224.34 --> 1233.70]  Because the MDI website that you pick the icons from is the slowest damn web page to load on the entire freaking internet, I swear.
+[1233.76 --> 1234.20]  So slow.
+[1234.42 --> 1234.78]  So bad.
+[1234.98 --> 1235.02]  Yeah.
+[1235.02 --> 1237.74]  I'm glad they have it, but it's so slow.
+[1238.38 --> 1238.52]  Yeah.
+[1238.58 --> 1239.88]  So they're going to have an icon picker.
+[1239.98 --> 1240.80]  It'll be built in.
+[1241.06 --> 1243.88]  And these material design icons are in Home Assistant.
+[1244.04 --> 1249.24]  And there's so many for your different devices that just kind of give you a nice visual indicator what it do.
+[1249.70 --> 1249.98]  Mm-hmm.
+[1250.58 --> 1251.84]  You've got to know what it do.
+[1253.66 --> 1255.70]  Leno.com slash SSH.
+[1255.76 --> 1257.82]  Talk about people who know what they are doing.
+[1258.00 --> 1260.66]  They've been doing this since 2003.
+[1260.66 --> 1262.88]  One of the very first companies in cloud computing.
+[1262.88 --> 1265.30]  I mean, that's knowing what you're doing.
+[1265.42 --> 1273.38]  And 18 years later, Linode is the largest independent open cloud provider in the world with 11 different data centers around the world.
+[1273.52 --> 1275.88]  So it's linode.com slash SSH.
+[1275.96 --> 1279.78]  You go there to get $100 in 60-day credit on a new account.
+[1280.16 --> 1281.76]  And, of course, you support the show.
+[1281.90 --> 1285.22]  This show is made possible by you taking advantage of our sponsor offers.
+[1285.40 --> 1286.88]  We're an independent operation.
+[1286.88 --> 1288.66]  A couple of guys doing our thing here.
+[1288.78 --> 1292.30]  And you taking advantage of something great like this linode.com slash SSH.
+[1292.30 --> 1294.28]  Man, that's the circle of life for us.
+[1294.58 --> 1297.04]  Plus, you can go in there and just see how great it is.
+[1297.26 --> 1299.96]  It really is a fantastic service with great performance.
+[1299.96 --> 1306.40]  And they've really invested in the dashboard and the hardware and the networking and, well, the whole stack, really.
+[1306.70 --> 1311.16]  Like, if you want to switch over from Zoom to Jitsi, they've got a one-click deployment for that.
+[1311.66 --> 1315.06]  And it's like a great opportunity to take advantage of our $100 credit.
+[1315.06 --> 1320.58]  They really have the best-in-class experience because they've been focusing on making this great for the last 18 years.
+[1320.88 --> 1322.54]  Their mission has remained unchanged.
+[1323.24 --> 1326.94]  Making cloud computing accessible, affordable for all.
+[1327.44 --> 1330.72]  And once you get in, you'll see that they have things like S3-compatible object storage.
+[1330.84 --> 1332.58]  There's so much you can do with that.
+[1332.96 --> 1335.88]  They have bare metal servers if your application load requires that.
+[1336.00 --> 1336.92]  DDoS protection.
+[1337.30 --> 1338.14]  VLAN support.
+[1338.44 --> 1339.98]  A powerful DNS manager.
+[1339.98 --> 1348.30]  And if you like to do your infrastructure by code, they've got Terraform and Kubernetes support to help you, well, integrate with everything else you're doing.
+[1348.46 --> 1353.10]  And with pricing 30% to 50% cheaper, maybe it's a great opportunity to go multi-cloud.
+[1353.36 --> 1354.76]  Why get locked into a single vendor?
+[1355.88 --> 1359.96]  Linode can help you spread that out so you're not just dependent on one hyperscaler.
+[1360.24 --> 1364.84]  And as we've seen just the week that we're recording, sometimes, sometimes they go down.
+[1365.12 --> 1369.16]  And if you ever get stuck, Linode has the best customer support in the industry.
+[1369.16 --> 1373.52]  They really have amazing 24-7 customer support by phone, ticket, or social.
+[1373.94 --> 1378.20]  And then they back all that up with hundreds of guides and thousands of tutorials.
+[1379.02 --> 1382.06]  Linode is dedicated to offering the best in virtualized cloud computing.
+[1382.30 --> 1385.00]  If it runs on Linux, it runs on Linode.
+[1385.52 --> 1388.14]  Sign up today at linode.com slash SSH.
+[1388.22 --> 1392.08]  Get $100 in 60-day credit on your new account and you support the show.
+[1392.96 --> 1395.52]  Linode.com slash SSH.
+[1395.52 --> 1399.26]  Now, what were you doing earlier in the week?
+[1399.38 --> 1402.44]  You weren't, you know, messing about with BGP routes, were you?
+[1403.76 --> 1406.74]  No, no, I'm not pushing out changes to remove DNS entries.
+[1407.38 --> 1411.62]  Just, you know, of course, listeners are probably picking up on the fact that this is the week that Facebook went down.
+[1411.88 --> 1414.30]  And Alex and I are watching this with popcorn going,
+[1414.30 --> 1418.68]  oh, could you imagine what it's like to be on site right now where they can't even badge in,
+[1418.78 --> 1421.24]  let alone figure out why everything's down?
+[1421.70 --> 1422.50]  What a nightmare.
+[1422.50 --> 1423.92]  Or send each other an email.
+[1424.16 --> 1424.66]  That's the thing.
+[1424.80 --> 1427.96]  Like, you know, bob at facebook.com would no longer work, would it?
+[1428.54 --> 1428.94]  Man.
+[1429.30 --> 1433.48]  If I didn't know any better, I'd think somebody probably lost their job.
+[1433.86 --> 1436.74]  Well, I mean, this conspiracy theorist in me wonders,
+[1437.08 --> 1443.98]  it's all a little fishy that it happened on the exact same week as the testimony whistleblower thing.
+[1444.80 --> 1449.36]  You know, is it a deflection tactic or is it just genuinely a screw up?
+[1449.36 --> 1452.50]  I don't know, but you got to wonder sometimes.
+[1453.12 --> 1454.46]  I don't think it was a deflection tactic.
+[1454.60 --> 1458.34]  I mean, it was, if it was, that was a very significant self-inflicted wound.
+[1459.00 --> 1459.56]  Yeah, true.
+[1459.92 --> 1463.04]  I actually saw one of my neighbors sharing on Facebook today,
+[1463.64 --> 1466.08]  10 Facebook alternatives for 2021.
+[1466.58 --> 1467.88]  I just thought that was so funny.
+[1468.30 --> 1468.48]  Yeah.
+[1468.52 --> 1471.00]  And Telegram saw a massive rush of new users.
+[1471.14 --> 1476.44]  You know, I'd buy an insider job before I'd buy an intentional screw up,
+[1476.44 --> 1478.74]  you know, like a rage quit kind of thing.
+[1479.36 --> 1479.72]  Yeah, maybe.
+[1480.40 --> 1483.60]  Maybe the Zuck didn't give somebody the smoked meats they were after.
+[1484.58 --> 1487.24]  I've been a little too distracted to really pay attention, though.
+[1487.34 --> 1490.60]  I got sucked into the rabbit hole of energy monitoring.
+[1490.84 --> 1492.42]  Right, yeah, because you're back home now,
+[1492.48 --> 1495.40]  so you've actually got some free time instead of just driving all day.
+[1495.98 --> 1498.16]  And Home Assistant, while I was on the roads,
+[1498.20 --> 1499.76]  I didn't have a chance to really look at it,
+[1499.94 --> 1501.86]  added energy monitoring support,
+[1501.86 --> 1506.24]  where you can actually, like, get some good stats and whatnot in Home Assistant
+[1506.24 --> 1509.96]  and identify batteries and utility sources
+[1509.96 --> 1512.80]  and even, like, you know, fuel consumption costs
+[1512.80 --> 1514.56]  if you want to monitor that.
+[1515.58 --> 1517.50]  So I thought, okay, I got to try this.
+[1517.94 --> 1521.30]  And I have a couple of Z-Wave smart plugs that do energy monitoring.
+[1521.60 --> 1523.20]  I've never really used that.
+[1523.56 --> 1527.52]  So that is sort of the route that I looked at this like,
+[1527.58 --> 1531.82]  well, why don't I try to see if I can get my existing smart plugs to work?
+[1532.30 --> 1535.32]  And for listeners that don't remember, I have two setups.
+[1535.50 --> 1539.70]  I have a home automation setup in my RV, which is pretty extensive.
+[1540.10 --> 1542.84]  And then I have, like, a mini version at the studio.
+[1543.66 --> 1548.22]  It's like a smaller instance of Home Assistant.
+[1548.48 --> 1550.12]  It runs on the Home Assistant Blue.
+[1550.46 --> 1553.62]  And in a way, it's often kind of like a good testing ground
+[1553.62 --> 1554.90]  because it's so much simpler.
+[1555.10 --> 1557.40]  There's just, there's less entities to go through
+[1557.40 --> 1558.42]  and all that kind of stuff.
+[1558.52 --> 1561.18]  And I noticed after the update,
+[1561.86 --> 1563.98]  to the Home Assistant Blues version of Home Assistant,
+[1564.08 --> 1566.22]  which comes out at the same time everybody else does,
+[1567.12 --> 1569.50]  that I just had energy monitoring.
+[1569.66 --> 1572.48]  Like my Belkin Wemo plugs that I happen to have
+[1572.48 --> 1573.68]  that I only use here in the studio
+[1573.68 --> 1576.34]  were just reporting their energy usage.
+[1576.88 --> 1579.32]  And Home Assistant had like a little diagram
+[1579.32 --> 1580.92]  of where power was going
+[1580.92 --> 1582.94]  and how much power had been used that day.
+[1583.08 --> 1586.32]  And I thought, wow, that looks great.
+[1586.32 --> 1589.60]  I'd love to have that at home where I actually care about my power
+[1589.60 --> 1591.42]  and all of that kind of stuff, I thought to myself.
+[1591.84 --> 1594.22]  So I go home and I don't have any of that.
+[1595.04 --> 1597.74]  My plugs are monitoring their draw.
+[1598.08 --> 1600.26]  They're seeing how many watts are being used.
+[1600.76 --> 1602.30]  But Home Assistant couldn't care less.
+[1602.38 --> 1603.54]  Like if I bring up the sensor,
+[1603.66 --> 1606.10]  yeah, it knows how many watts are being used.
+[1606.52 --> 1608.68]  But when I go to configure an energy device,
+[1608.74 --> 1610.56]  it's just whatever, bro.
+[1610.80 --> 1612.36]  There's no device that's giving you any stats.
+[1612.36 --> 1615.74]  For some reason, I've just got this picture of Home Assistant
+[1615.74 --> 1620.36]  being like this beavis and butthead style character
+[1620.36 --> 1623.14]  sat on a couch in the corner with a backwards baseball cap
+[1623.14 --> 1624.52]  and a cigarette in the other hand going,
+[1624.94 --> 1626.94]  whatever, bro, I don't care.
+[1627.14 --> 1627.88]  Yeah, you can't have that.
+[1628.30 --> 1628.94]  I don't care.
+[1629.54 --> 1631.56]  And so to me, it's like, okay, there's something wrong.
+[1631.64 --> 1634.18]  Obviously, these devices are like not giving Home Assistant
+[1634.18 --> 1635.72]  the information you need.
+[1635.76 --> 1637.12]  But when you go into the developer tools
+[1637.12 --> 1639.10]  and you look at the state attributes
+[1639.10 --> 1640.36]  and the states it's sending back,
+[1640.36 --> 1644.64]  it's clearly saying this is the amount of power being consumed.
+[1644.96 --> 1648.42]  It's in the watts format and it is this many watts.
+[1648.56 --> 1650.98]  Like it's easily readable by the human eye.
+[1651.06 --> 1653.46]  And I'm thinking to myself, what's going on here?
+[1653.50 --> 1655.18]  Why can't I see this power draw?
+[1655.50 --> 1658.42]  And I want to not only get an overview of my power draw,
+[1658.48 --> 1660.66]  but I want to start building automations that say,
+[1660.78 --> 1663.62]  hey, when two appliances, when these two smart plugs,
+[1663.70 --> 1665.64]  because I can just say these two together,
+[1666.34 --> 1667.20]  they're on one circuit.
+[1667.20 --> 1667.80]  I know that.
+[1667.80 --> 1671.36]  So when these two smart plugs both have a draw over 500 watts,
+[1671.92 --> 1673.46]  turn off the heater smart plug.
+[1673.56 --> 1674.26]  Always turn it off.
+[1674.32 --> 1675.70]  So that way the wife can turn on the toaster.
+[1675.98 --> 1677.96]  And when it starts drawing a thousand watts,
+[1678.08 --> 1680.20]  it turns off the heater that's drawing 800 watts.
+[1680.52 --> 1682.56]  And that's essentially what I want.
+[1682.62 --> 1684.82]  And if anybody has a blueprint or a good advice
+[1684.82 --> 1686.48]  on how to set that up, please let me know.
+[1686.98 --> 1688.58]  Ultimately, that's what I'm trying to get to.
+[1688.70 --> 1689.74]  I haven't gotten there yet.
+[1689.74 --> 1693.92]  But what I did do is I managed to get my damn energy monitored.
+[1693.92 --> 1696.52]  And it took quite a journey, I have to say,
+[1696.58 --> 1701.14]  because ultimately you have to get the data in the format
+[1701.14 --> 1702.42]  that Home Assistant wants.
+[1702.84 --> 1706.96]  So first, you got to have Home Assistant 2021.8 or newer,
+[1707.20 --> 1711.52]  and you need a smart plug or an energy monitoring device,
+[1711.52 --> 1713.42]  like one of those clamp devices or a Shelly
+[1713.42 --> 1716.54]  that reports in kilowatt hours.
+[1716.54 --> 1720.14]  All my plugs report in watts,
+[1720.94 --> 1724.22]  as in watts currently being consumed.
+[1724.98 --> 1727.00]  Home Assistant wants kilowatt hours,
+[1727.22 --> 1729.42]  and then it'll do all the math for you from there.
+[1729.78 --> 1733.24]  So what you have to do is you have to get an integration
+[1733.24 --> 1735.54]  called integration.
+[1735.96 --> 1737.44]  It's a math integration,
+[1737.44 --> 1739.94]  which will take the watts
+[1739.94 --> 1742.34]  and convert them into kilowatt hours for you,
+[1742.34 --> 1744.84]  and then produce a new sensor
+[1744.84 --> 1748.06]  that shows that energy information in kilowatt hours.
+[1748.56 --> 1752.00]  I have a configuration.yaml entry example in the show notes.
+[1752.70 --> 1754.12]  Then once you have that,
+[1754.70 --> 1757.72]  the new energy utilities that are built into Home Assistant
+[1757.72 --> 1760.22]  will see this device as something it can pull stats from
+[1760.22 --> 1762.32]  and will start giving you your usage.
+[1762.80 --> 1764.98]  So I have to go through for each one of my smart plugs,
+[1765.24 --> 1766.70]  and I have to do this.
+[1766.76 --> 1770.56]  I have to create this template sensor
+[1770.56 --> 1775.12]  that takes information from the state of my smart plug
+[1775.12 --> 1778.16]  and formats it in a way that Home Assistant wants.
+[1778.20 --> 1779.56]  And I have the examples in the show notes,
+[1779.66 --> 1780.76]  but I had to go deep
+[1780.76 --> 1782.92]  because I had to learn a little bit of how templating works.
+[1783.00 --> 1786.14]  I had to learn about creating new kinds of sensors.
+[1787.32 --> 1789.06]  It was really quite the journey.
+[1789.06 --> 1792.82]  I naively expected to just do the update,
+[1792.92 --> 1793.74]  get energy monitoring,
+[1793.98 --> 1795.74]  and see my smart plugs report in there.
+[1796.14 --> 1797.70]  Boy, was I wrong.
+[1797.98 --> 1800.34]  Sometimes we get a bit spoiled with Home Assistant,
+[1800.34 --> 1800.74]  don't we?
+[1800.76 --> 1801.70]  It picks up so much.
+[1801.76 --> 1802.42]  It does so much.
+[1802.60 --> 1804.10]  And then occasionally,
+[1804.10 --> 1807.24]  we actually have to break out some DaVinci code
+[1807.24 --> 1808.80]  to find out what we actually wanted.
+[1809.24 --> 1810.44]  I think this is one of those examples.
+[1810.94 --> 1812.68]  And I felt like there was so much out there
+[1812.68 --> 1815.80]  that didn't apply since the new energy monitoring
+[1815.80 --> 1816.74]  was introduced.
+[1816.84 --> 1819.50]  So like a lot of the help was old
+[1819.50 --> 1821.06]  and no longer relevant.
+[1821.06 --> 1823.68]  And because my smart plugs,
+[1823.74 --> 1824.02]  I guess,
+[1824.06 --> 1824.74]  aren't as common,
+[1825.28 --> 1827.10]  there's not as many people
+[1827.10 --> 1828.70]  that have solved this problem.
+[1829.32 --> 1829.74]  So I just,
+[1830.20 --> 1830.42]  yeah,
+[1830.54 --> 1830.80]  it was,
+[1831.02 --> 1833.52]  I felt like I was searching niche resources
+[1833.52 --> 1835.04]  and it took me a while
+[1835.04 --> 1836.32]  to even just try to figure out
+[1836.32 --> 1837.40]  the language I need
+[1837.40 --> 1838.92]  and figure out what the requirements were
+[1838.92 --> 1839.56]  of Home Assistant
+[1839.56 --> 1840.30]  and all of that.
+[1840.30 --> 1841.52]  That is a real problem
+[1841.52 --> 1842.94]  with projects like Home Assistant
+[1842.94 --> 1843.96]  that move so fast.
+[1844.04 --> 1845.98]  I see it a lot with Kubernetes at work as well
+[1845.98 --> 1851.64]  is that kind of Google entropy of stuff.
+[1852.04 --> 1853.38]  Like a post,
+[1853.60 --> 1853.74]  you know,
+[1853.84 --> 1856.12]  Google will think a year old post
+[1856.12 --> 1859.10]  isn't too old to surface as the top result
+[1859.10 --> 1861.02]  when in actual fact in Home Assistant
+[1861.02 --> 1862.66]  that may as well be 10 years ago.
+[1863.24 --> 1863.64]  Yeah,
+[1863.74 --> 1864.72]  that's exactly right.
+[1865.34 --> 1865.96]  And then,
+[1866.10 --> 1866.40]  you know,
+[1866.46 --> 1866.68]  Alex,
+[1866.74 --> 1867.78]  when I got it all kind of done,
+[1868.30 --> 1870.60]  I realized it's okay.
+[1870.84 --> 1872.34]  It's pretty basic at this point
+[1872.34 --> 1873.38]  because I don't have
+[1873.38 --> 1874.94]  all of my battery
+[1874.94 --> 1876.30]  and solar information in there.
+[1876.60 --> 1878.56]  It really wasn't worth the journey.
+[1878.76 --> 1880.72]  I actually like the dashboards
+[1880.72 --> 1883.38]  I created myself better.
+[1883.80 --> 1885.34]  And I'll have a few links in the show notes.
+[1885.34 --> 1887.76]  It involved setting up
+[1887.76 --> 1889.18]  a history stats integration
+[1889.18 --> 1891.52]  so I could collect historical information
+[1891.52 --> 1892.58]  about my power usage.
+[1893.20 --> 1894.02]  And then I used
+[1894.02 --> 1895.50]  a utility meter integration
+[1895.50 --> 1897.86]  and that let my
+[1897.86 --> 1899.78]  virtual energy monitors
+[1899.78 --> 1900.32]  I'd set up
+[1900.32 --> 1901.38]  that produce kilowatt hours
+[1901.38 --> 1902.66]  show up as a utility source.
+[1902.78 --> 1902.90]  Now,
+[1903.58 --> 1905.66]  that lets me do all kinds of things
+[1905.66 --> 1907.48]  like now I have a dashboard
+[1907.48 --> 1909.38]  that shows me
+[1909.38 --> 1910.98]  if today
+[1910.98 --> 1913.86]  my heaters are using more power
+[1913.86 --> 1914.84]  than they were,
+[1914.84 --> 1915.04]  say,
+[1915.10 --> 1915.68]  three days ago.
+[1915.72 --> 1916.70]  I have a three-day window
+[1916.70 --> 1919.18]  on my power usage of my heaters
+[1919.18 --> 1921.06]  and I can kind of tell
+[1921.06 --> 1923.98]  when I'm kind of using more power
+[1923.98 --> 1925.70]  and maybe I can make adjustments
+[1925.70 --> 1926.54]  based on that if I want.
+[1926.58 --> 1927.38]  I actually haven't decided
+[1927.38 --> 1928.40]  to take any action on that.
+[1928.46 --> 1929.18]  Right now I'm just collecting
+[1929.18 --> 1929.72]  the information
+[1929.72 --> 1931.34]  and collecting historical information.
+[1932.20 --> 1933.72]  And so when summer comes around,
+[1933.78 --> 1934.36]  I'll have a totally,
+[1934.58 --> 1934.82]  you know,
+[1934.98 --> 1935.78]  different set of data
+[1935.78 --> 1936.76]  and then when the whole year
+[1936.76 --> 1937.20]  is completed,
+[1937.30 --> 1938.30]  I think the information
+[1938.30 --> 1939.38]  is going to be pretty fascinating
+[1939.38 --> 1941.10]  and I'll probably be able
+[1941.10 --> 1941.70]  to overlay it
+[1941.70 --> 1942.66]  with temperature information
+[1942.66 --> 1943.52]  and all kinds of stuff.
+[1943.88 --> 1945.22]  So I brought together
+[1945.22 --> 1947.78]  the history stats integration
+[1947.78 --> 1950.00]  with the utility meter integration
+[1950.00 --> 1951.10]  and I have,
+[1951.36 --> 1951.62]  again,
+[1951.74 --> 1953.46]  an example of what that looks like
+[1953.46 --> 1954.90]  in your configuration.yaml
+[1954.90 --> 1955.96]  linked in the show notes.
+[1956.44 --> 1957.30]  So now what that's done
+[1957.30 --> 1957.78]  is it's created
+[1957.78 --> 1958.82]  these virtual sensors
+[1958.82 --> 1960.16]  that I've built dashboards around
+[1960.16 --> 1960.98]  in Home Assistant
+[1960.98 --> 1962.60]  that give me all this information
+[1962.60 --> 1963.86]  that I think
+[1963.86 --> 1964.80]  that's where they're going
+[1964.80 --> 1966.32]  with the built-in energy support,
+[1966.48 --> 1967.78]  but I like my version better
+[1967.78 --> 1968.70]  than I built myself.
+[1969.40 --> 1970.22]  It's not too bad, actually.
+[1970.30 --> 1971.52]  17 lines of code
+[1971.52 --> 1973.30]  to do all that history stat stuff.
+[1973.40 --> 1974.70]  It's not unreasonable.
+[1975.26 --> 1976.18]  And it's very readable.
+[1976.30 --> 1977.12]  Like it all makes sense
+[1977.12 --> 1977.64]  when you read it.
+[1977.66 --> 1978.52]  You can see what I'm doing.
+[1978.66 --> 1980.00]  There's nothing tricky about it.
+[1980.30 --> 1981.08]  Yeah, that's very true.
+[1981.24 --> 1981.42]  Now,
+[1981.58 --> 1982.68]  something else we've talked about
+[1982.68 --> 1983.58]  on the show previously
+[1983.58 --> 1985.48]  is de-Google-ifying.
+[1986.22 --> 1986.96]  I'll be honest,
+[1987.16 --> 1988.06]  whilst I've been in England,
+[1988.16 --> 1989.06]  I haven't been paying
+[1989.06 --> 1990.72]  much attention to that.
+[1990.80 --> 1991.94]  I've just been getting on
+[1991.94 --> 1993.04]  with the business of traveling.
+[1993.58 --> 1993.98]  However,
+[1994.44 --> 1996.30]  you mentioned in LUP this week,
+[1996.68 --> 1997.86]  linuxonplugged.com
+[1997.86 --> 1998.88]  slash 426,
+[1999.42 --> 2001.46]  a tool called TubeSync.
+[2001.68 --> 2001.98]  Yeah,
+[2002.04 --> 2002.68]  think of TubeSync
+[2002.68 --> 2004.20]  as a PVR for YouTube.
+[2004.42 --> 2006.22]  You give it channels
+[2006.22 --> 2006.94]  and playlists,
+[2007.06 --> 2007.88]  or if you're familiar
+[2007.88 --> 2008.56]  with Sonar,
+[2008.64 --> 2009.82]  it's like Sonar for YouTube.
+[2010.06 --> 2011.54]  And then it goes out
+[2011.54 --> 2012.84]  and pulls down the videos
+[2012.84 --> 2013.32]  and it gives you
+[2013.32 --> 2014.46]  a dashboard to tell you
+[2014.46 --> 2015.76]  how many video sources
+[2015.76 --> 2016.70]  you're pulling from,
+[2016.96 --> 2018.28]  what's coming up next,
+[2018.66 --> 2019.78]  exactly like you might expect
+[2019.78 --> 2021.00]  from something like Sonar.
+[2021.00 --> 2023.14]  It's a pretty advanced UI
+[2023.14 --> 2024.84]  and there's a Docker Compose
+[2024.84 --> 2026.04]  that gets most of it
+[2026.04 --> 2026.88]  set up for you too, Alex,
+[2026.94 --> 2028.14]  including the Elasticsearch
+[2028.14 --> 2028.86]  stuff you might need.
+[2029.16 --> 2030.24]  The reason I brought this up
+[2030.24 --> 2030.92]  on this show
+[2030.92 --> 2033.28]  is this isn't Linux
+[2033.28 --> 2034.30]  unplugged extras,
+[2034.60 --> 2036.72]  but I actually found
+[2036.72 --> 2037.44]  something called
+[2037.44 --> 2039.36]  MediaCMS.io
+[2039.36 --> 2040.94]  and this is essentially
+[2040.94 --> 2043.72]  a YouTube front-end clone.
+[2044.40 --> 2045.24]  So what I was thinking
+[2045.24 --> 2046.68]  about doing was,
+[2046.90 --> 2047.84]  originally anyway,
+[2047.84 --> 2049.38]  I was going to use TubeSync
+[2049.38 --> 2050.44]  to download the videos
+[2050.44 --> 2051.14]  from YouTube
+[2051.14 --> 2052.90]  just as an archiving
+[2052.90 --> 2055.16]  type utility.
+[2055.56 --> 2057.06]  Bring them into Plex maybe
+[2057.06 --> 2058.36]  because there are some people
+[2058.36 --> 2059.70]  on the Plex forums
+[2059.70 --> 2062.16]  that have YouTube metadata agents
+[2062.16 --> 2063.02]  and that kind of thing.
+[2063.48 --> 2065.28]  But I think what I might end up doing
+[2065.28 --> 2067.78]  is using this MediaCMS.io
+[2067.78 --> 2069.44]  to self-host my own
+[2069.44 --> 2071.82]  kind of pseudo YouTube
+[2071.82 --> 2073.18]  instance thing.
+[2073.34 --> 2074.02]  Have you seen this?
+[2074.48 --> 2075.96]  Oh, this is neat, yes.
+[2076.08 --> 2077.64]  And it is obviously
+[2077.64 --> 2079.42]  inspired by the YouTube UI,
+[2079.66 --> 2080.20]  but good on them.
+[2080.44 --> 2081.80]  They've taken the best elements
+[2081.80 --> 2082.26]  in this
+[2082.26 --> 2084.26]  and I think it looks
+[2084.26 --> 2084.78]  really solid.
+[2084.94 --> 2086.38]  They got dark mode,
+[2086.52 --> 2087.46]  they got light mode
+[2087.46 --> 2090.10]  and it could really end up
+[2090.10 --> 2091.94]  making a perfect curated YouTube.
+[2092.36 --> 2094.02]  And while I could see it
+[2094.02 --> 2094.54]  being a lot of work
+[2094.54 --> 2095.52]  for what you want to do,
+[2096.18 --> 2096.86]  man, this could be
+[2096.86 --> 2098.68]  a slam dunk for parents.
+[2099.20 --> 2100.70]  This could be a great way.
+[2101.10 --> 2102.26]  You could take TubeSync
+[2102.26 --> 2104.18]  and pull in the approved channels
+[2104.18 --> 2104.88]  that you're comfortable
+[2104.88 --> 2105.84]  with your kids watching,
+[2105.84 --> 2107.30]  have TubeSync pull it
+[2107.30 --> 2108.22]  down to the file system
+[2108.22 --> 2110.38]  and then point MediaCMS
+[2110.38 --> 2111.26]  right at that
+[2111.26 --> 2112.50]  and it's a curated YouTube.
+[2112.86 --> 2114.40]  I wonder how they handle
+[2114.40 --> 2115.72]  video transcoding
+[2115.72 --> 2116.48]  because obviously YouTube
+[2116.48 --> 2118.60]  has a whole bunch of stuff
+[2118.60 --> 2119.96]  when you upload video to it,
+[2119.96 --> 2120.78]  it transcodes
+[2120.78 --> 2121.94]  to all the different formats
+[2121.94 --> 2123.08]  and then you just switch
+[2123.08 --> 2124.18]  on the fly
+[2124.18 --> 2125.64]  the quality that you're streaming.
+[2125.90 --> 2128.40]  Does this have any function for that?
+[2128.46 --> 2129.96]  I don't see any quality options
+[2129.96 --> 2130.62]  in the playback.
+[2131.18 --> 2131.60]  Oh yeah, no,
+[2131.68 --> 2132.50]  it's under the settings.
+[2132.50 --> 2133.12]  It's right there.
+[2133.54 --> 2134.30]  And it says it has
+[2134.30 --> 2135.94]  multiple transcoding profiles.
+[2136.14 --> 2137.14]  Same defaults, it says,
+[2137.18 --> 2138.10]  for multiple dimensions
+[2138.10 --> 2141.52]  from 240p up to 1080p.
+[2142.22 --> 2143.04]  Experimental support
+[2143.04 --> 2144.04]  for remote workers.
+[2144.18 --> 2145.70]  So I guess there's a bunch of stuff
+[2145.70 --> 2146.68]  we could figure out there.
+[2147.00 --> 2148.50]  This could be a fun project.
+[2148.84 --> 2150.30]  That's something to put on our list
+[2150.30 --> 2151.86]  after I get done solving energy.
+[2153.12 --> 2154.44]  Yeah, and then world hunger
+[2154.44 --> 2155.42]  and world peace
+[2155.42 --> 2157.20]  and COVID
+[2157.20 --> 2158.38]  is where you've got to solve
+[2158.38 --> 2158.96]  that one too.
+[2159.06 --> 2160.76]  And then we'll get on
+[2160.76 --> 2161.92]  redoingjb.com.
+[2161.92 --> 2163.40]  But we do have one thing
+[2163.40 --> 2164.46]  we can solve for people
+[2164.46 --> 2166.36]  if they are an iCloud
+[2166.36 --> 2168.16]  slash iPhone user
+[2168.16 --> 2169.70]  and you got your pictures up there.
+[2169.80 --> 2170.72]  You came across
+[2170.72 --> 2172.04]  a really handy tool
+[2172.04 --> 2174.06]  to help pull all of your
+[2174.06 --> 2175.20]  iCloud photos down
+[2175.20 --> 2176.42]  locally to your machine.
+[2176.98 --> 2178.02]  Yeah, we were talking about this.
+[2178.08 --> 2178.48]  Where was it?
+[2178.52 --> 2180.16]  In the Jupyter Broadcasting
+[2180.16 --> 2181.60]  Telegram chat, actually.
+[2182.36 --> 2183.38]  Someone was asking,
+[2183.84 --> 2184.06]  you know,
+[2184.10 --> 2185.34]  how do you back up your iPhone
+[2185.34 --> 2187.22]  pictures and stuff like that?
+[2187.56 --> 2188.72]  Because of the way that iOS
+[2188.72 --> 2190.26]  has very restrictive
+[2190.26 --> 2191.56]  background API,
+[2191.96 --> 2192.38]  kind of,
+[2192.54 --> 2193.98]  it kills anything
+[2193.98 --> 2194.68]  in the background
+[2194.68 --> 2197.18]  that's going to drain battery,
+[2197.32 --> 2198.04]  unlike Android
+[2198.04 --> 2199.26]  that's a lot more permissive.
+[2199.60 --> 2201.16]  It means you can't run
+[2201.16 --> 2202.08]  stuff like
+[2202.08 --> 2203.50]  Resilio Sync
+[2203.50 --> 2204.46]  or Sync thing
+[2204.46 --> 2205.48]  very effectively,
+[2205.74 --> 2206.46]  or there's another one
+[2206.46 --> 2206.84]  on Android
+[2206.84 --> 2207.90]  called Folder Sync.
+[2207.90 --> 2209.46]  And so,
+[2209.92 --> 2211.54]  this neat app
+[2211.54 --> 2212.30]  is actually called
+[2212.30 --> 2214.34]  Gimme-iPhotos,
+[2214.42 --> 2215.64]  which is kind of a funny name.
+[2216.20 --> 2217.44]  And this sidesteps
+[2217.44 --> 2219.02]  all of iOS's problems
+[2219.02 --> 2221.26]  with backgrounding APIs
+[2221.26 --> 2222.08]  and on-device,
+[2222.42 --> 2222.76]  you know,
+[2223.36 --> 2224.10]  image management
+[2224.10 --> 2224.98]  and stuff like that,
+[2225.10 --> 2226.56]  because it hooks
+[2226.56 --> 2228.46]  directly into iCloud.
+[2229.02 --> 2229.74]  The only caveat being
+[2229.74 --> 2230.40]  is you've got to be okay
+[2230.40 --> 2231.20]  with putting your photos
+[2231.20 --> 2232.24]  up in iCloud.
+[2232.38 --> 2233.06]  But I think what Alex
+[2233.06 --> 2233.74]  is driving at there,
+[2233.80 --> 2233.98]  it's like,
+[2234.04 --> 2234.74]  that's the only one
+[2234.74 --> 2235.68]  that's really going to work
+[2235.68 --> 2236.66]  reliably with the way
+[2236.66 --> 2238.04]  the iPhone backgrounding works.
+[2238.36 --> 2239.02]  If you want them
+[2239.02 --> 2239.94]  off the phone reliably,
+[2240.24 --> 2240.68]  automatically,
+[2240.94 --> 2241.64]  it's going to have to be
+[2241.64 --> 2242.82]  iCloud Photo on an iPhone.
+[2243.18 --> 2244.42]  So that's why this is so great.
+[2244.70 --> 2245.76]  And because it's Python,
+[2246.34 --> 2247.62]  you don't have to be on a Mac.
+[2247.82 --> 2249.24]  You could run it on a Linux box
+[2249.24 --> 2250.26]  or a Windows box too.
+[2250.82 --> 2251.34]  Yeah, I ran this
+[2251.34 --> 2253.02]  just on a normal Linux server.
+[2253.14 --> 2254.42]  I think I ran it out of a container
+[2254.42 --> 2257.22]  because that's just who I am.
+[2257.82 --> 2259.30]  The really nice thing about it,
+[2259.34 --> 2260.62]  and I didn't expect this at all,
+[2260.72 --> 2262.32]  I didn't even think about this
+[2262.32 --> 2263.38]  until I tried it,
+[2263.78 --> 2266.12]  it uses a Python library underneath,
+[2266.12 --> 2267.82]  which actually supports
+[2267.82 --> 2269.54]  the iCloud two-factor
+[2269.54 --> 2271.42]  authentication mechanisms.
+[2271.96 --> 2273.24]  So when I brought this up
+[2273.24 --> 2274.16]  for the first time,
+[2274.58 --> 2275.62]  a little pop-up appeared
+[2275.62 --> 2276.60]  on my Mac to say,
+[2276.94 --> 2278.14]  hey, someone's trying to log in
+[2278.14 --> 2279.50]  as you back in Raleigh.
+[2279.56 --> 2280.08]  Is this you?
+[2280.16 --> 2281.34]  And here's your two-factor code.
+[2281.40 --> 2281.90]  And I was like,
+[2282.30 --> 2283.94]  huh, did not expect that.
+[2284.40 --> 2284.96]  Yeah, that made me feel
+[2284.96 --> 2285.62]  a little bit better
+[2285.62 --> 2286.80]  that it was kind of legit
+[2286.80 --> 2288.10]  about how it's authorizing
+[2288.10 --> 2289.20]  against the iCloud servers.
+[2289.28 --> 2289.96]  It seems to be using
+[2289.96 --> 2291.96]  like an official Apple API for that.
+[2292.40 --> 2293.46]  And I think it's great
+[2293.46 --> 2294.74]  for running on your NAS.
+[2294.74 --> 2295.88]  If you've got a NAS box
+[2295.88 --> 2297.14]  that you can shell into,
+[2297.70 --> 2299.28]  you could go into your directory
+[2299.28 --> 2300.22]  of choice on your NAS
+[2300.22 --> 2301.28]  and execute this thing,
+[2301.32 --> 2302.14]  and it's just going to sit there
+[2302.14 --> 2303.34]  and download photos all day long.
+[2304.00 --> 2304.70]  And I think for me,
+[2304.78 --> 2307.34]  the absolute killer use case
+[2307.34 --> 2309.34]  are like my parents' phones.
+[2309.76 --> 2310.92]  You know, a couple of parents
+[2310.92 --> 2311.40]  use Android,
+[2311.52 --> 2313.14]  a couple use iOS.
+[2313.88 --> 2315.12]  And the iOS ones,
+[2315.18 --> 2315.86]  I've really struggled
+[2315.86 --> 2316.78]  to get the photos
+[2316.78 --> 2317.64]  out of iCloud
+[2317.64 --> 2319.66]  into anything meaningful,
+[2319.82 --> 2320.46]  off their phones,
+[2320.56 --> 2321.40]  into anything meaningful,
+[2321.52 --> 2322.58]  like NextCloud even
+[2322.58 --> 2324.30]  is a bit of a crapshoot on iOS.
+[2325.06 --> 2326.26]  And this just solves
+[2326.26 --> 2327.86]  that problem altogether.
+[2328.26 --> 2328.72]  I'm not,
+[2328.86 --> 2329.68]  the only thing I'm not
+[2329.68 --> 2330.76]  totally certain on
+[2330.76 --> 2331.96]  is how long
+[2331.96 --> 2333.30]  that two-factor authentication
+[2333.30 --> 2334.72]  token lasts for.
+[2335.18 --> 2336.42]  And I guess time will tell,
+[2336.54 --> 2338.30]  but I'm going to set this up
+[2338.30 --> 2339.46]  for my parents this week
+[2339.46 --> 2340.10]  whilst I'm here
+[2340.10 --> 2341.82]  and then report back
+[2341.82 --> 2342.22]  when it,
+[2343.22 --> 2343.42]  you know,
+[2343.44 --> 2343.94]  in six months
+[2343.94 --> 2344.64]  and let you know
+[2344.64 --> 2345.46]  how it's gone.
+[2345.98 --> 2346.36]  And are you thinking
+[2346.36 --> 2347.16]  just chron it
+[2347.16 --> 2348.34]  so it just runs automatically
+[2348.34 --> 2349.76]  every night or something?
+[2349.76 --> 2351.16]  Yeah, exactly.
+[2351.32 --> 2352.28]  Put it on a timer
+[2352.28 --> 2353.12]  and then let it download
+[2353.12 --> 2354.24]  every day,
+[2354.34 --> 2354.84]  every week,
+[2354.92 --> 2355.42]  whatever, yeah.
+[2355.74 --> 2356.60]  Yeah, that will be interesting
+[2356.60 --> 2357.08]  to see how long
+[2357.08 --> 2358.28]  that two-factor authentication,
+[2358.60 --> 2358.92]  if it is,
+[2359.10 --> 2360.14]  I bet you it must have
+[2360.14 --> 2361.30]  some time expiration.
+[2361.76 --> 2362.76]  So you'll have to check back in
+[2362.76 --> 2363.94]  and see if either
+[2363.94 --> 2365.40]  A, it generates a new prompt
+[2365.40 --> 2366.76]  or B, just breaks quietly.
+[2370.44 --> 2372.30]  Backblaze.com slash SSH.
+[2372.56 --> 2373.62]  Go there to get a free trial,
+[2373.76 --> 2375.12]  no credit card required.
+[2375.24 --> 2376.28]  Just get peace of mind
+[2376.28 --> 2377.14]  knowing your files
+[2377.14 --> 2378.06]  are backed up securely
+[2378.06 --> 2378.74]  in the cloud
+[2378.74 --> 2379.94]  with Backblaze.
+[2380.24 --> 2381.36]  It's $7 a month,
+[2381.48 --> 2382.16]  no gimmicks.
+[2382.42 --> 2383.66]  You get unlimited backup
+[2383.66 --> 2384.80]  for your Mac or your PC,
+[2385.14 --> 2385.62]  your movies,
+[2385.76 --> 2386.14]  your music,
+[2386.26 --> 2386.76]  your photos,
+[2386.98 --> 2387.44]  your videos,
+[2387.54 --> 2388.06]  your projects,
+[2388.40 --> 2389.22]  all the data.
+[2389.58 --> 2390.80]  And Backblaze now has
+[2390.80 --> 2391.90]  over an exabyte
+[2391.90 --> 2392.90]  of customer data
+[2392.90 --> 2393.86]  backed up and counting
+[2393.86 --> 2395.44]  with 50 billion files
+[2395.44 --> 2396.48]  restored for their customers.
+[2396.96 --> 2398.04]  You can do web restores
+[2398.04 --> 2399.64]  if that's how you like to roll.
+[2400.00 --> 2401.02]  You can restore files
+[2401.02 --> 2401.68]  by the app
+[2401.68 --> 2402.60]  if that's how you want
+[2402.60 --> 2403.98]  to get to files on the go.
+[2404.14 --> 2404.82]  I don't know how you do.
+[2405.08 --> 2406.16]  And they also offer
+[2406.16 --> 2407.36]  restore by mail.
+[2407.62 --> 2408.44]  Check this out.
+[2408.68 --> 2409.40]  A flash key
+[2409.40 --> 2410.16]  or a hard drive
+[2410.16 --> 2410.92]  that you can grab
+[2410.92 --> 2411.58]  from them.
+[2412.12 --> 2412.96]  Ship to your door
+[2412.96 --> 2414.14]  overnight with your data
+[2414.14 --> 2414.86]  restored to it.
+[2415.06 --> 2416.22]  But here's the best part.
+[2416.68 --> 2417.76]  If you send the hard drive
+[2417.76 --> 2419.04]  back within 30 days,
+[2419.40 --> 2420.42]  you get a full refund.
+[2420.82 --> 2422.14]  Now that's some peace of mind.
+[2422.22 --> 2423.02]  If you lose your data
+[2423.02 --> 2424.28]  and you've got a lot of things
+[2424.28 --> 2425.16]  you're going to need to recover,
+[2425.68 --> 2426.54]  it's nice having
+[2426.54 --> 2427.68]  a physical hard drive
+[2427.68 --> 2428.88]  mailed to you overnight
+[2428.88 --> 2429.98]  by FedEx.
+[2430.44 --> 2431.06]  And if you're worried
+[2431.06 --> 2432.72]  about accidentally deleting files
+[2432.72 --> 2434.06]  for an extra $2 a month,
+[2434.14 --> 2434.72]  you can increase
+[2434.72 --> 2435.68]  your retention history
+[2435.68 --> 2436.78]  to one year.
+[2437.22 --> 2437.82]  Their mobile apps
+[2437.82 --> 2438.62]  mean you can get access
+[2438.62 --> 2439.54]  to those same files
+[2439.54 --> 2440.36]  when you're out and about
+[2440.36 --> 2441.00]  on the go.
+[2441.56 --> 2441.90]  And of course,
+[2442.00 --> 2443.16]  Backblaze has been recommended
+[2443.16 --> 2444.38]  by New York Times,
+[2444.64 --> 2445.24]  by Macworld,
+[2445.34 --> 2446.06]  by Tom's Guide,
+[2446.52 --> 2447.20]  9to5Mac,
+[2447.42 --> 2448.04]  and many more.
+[2448.50 --> 2449.34]  But why not go see it
+[2449.34 --> 2449.82]  for yourself?
+[2450.18 --> 2451.72]  Get a free 15-day trial
+[2451.72 --> 2453.36]  at backblaze.com
+[2453.36 --> 2454.96]  slash SSH.
+[2455.28 --> 2456.26]  15 days means
+[2456.26 --> 2457.32]  plenty of time
+[2457.32 --> 2458.10]  to upload
+[2458.10 --> 2459.26]  and download some files
+[2459.26 --> 2460.14]  and get a real feel
+[2460.14 --> 2460.86]  for the service.
+[2461.18 --> 2461.90]  And you know,
+[2462.06 --> 2462.86]  Backblaze has been around
+[2462.86 --> 2463.38]  for a while.
+[2463.64 --> 2465.16]  They started 14 years ago
+[2465.16 --> 2466.02]  to create a business
+[2466.02 --> 2467.12]  that's equally fair
+[2467.12 --> 2468.06]  and good for its customers,
+[2468.56 --> 2468.84]  partners,
+[2469.32 --> 2469.72]  employees,
+[2470.20 --> 2470.58]  investors,
+[2470.78 --> 2472.20]  and the greater community.
+[2472.20 --> 2473.86]  And since 2013,
+[2474.36 --> 2475.34]  they've been publishing
+[2475.34 --> 2476.60]  their hard drive reports.
+[2477.12 --> 2477.56]  That's a report
+[2477.56 --> 2478.10]  we make sure
+[2478.10 --> 2479.02]  to never miss.
+[2479.10 --> 2480.20]  And it's a real value
+[2480.20 --> 2481.54]  to the entire industry too
+[2481.54 --> 2482.44]  because of the amount
+[2482.44 --> 2482.94]  of disks,
+[2483.36 --> 2484.20]  the real scale
+[2484.20 --> 2484.84]  that Backblaze
+[2484.84 --> 2485.50]  is working with.
+[2485.70 --> 2486.22]  They can get
+[2486.22 --> 2487.44]  some genuine insights.
+[2488.16 --> 2488.62]  And now,
+[2489.00 --> 2490.12]  after 14 years,
+[2490.12 --> 2491.50]  they have over
+[2491.50 --> 2492.94]  500,000 customers
+[2492.94 --> 2495.72]  in 175 countries.
+[2496.24 --> 2497.10]  Backblaze.com
+[2497.10 --> 2498.22]  slash SSH.
+[2498.34 --> 2499.38]  No credit card required.
+[2499.70 --> 2500.10]  Get started
+[2500.10 --> 2501.34]  on a free 15-day trial
+[2501.34 --> 2503.00]  and start backing up
+[2503.00 --> 2503.42]  your data.
+[2503.88 --> 2504.28]  Start getting
+[2504.28 --> 2505.16]  some peace of mind.
+[2505.66 --> 2506.58]  Backblaze.com
+[2506.58 --> 2508.02]  slash SSH.
+[2510.22 --> 2510.70]  Now,
+[2510.76 --> 2511.74]  I mentioned Tailscale
+[2511.74 --> 2513.00]  in the last episode,
+[2513.16 --> 2514.68]  which was a brand new
+[2514.68 --> 2515.36]  project to me,
+[2515.42 --> 2516.12]  but it turns out
+[2516.12 --> 2516.96]  a lot of you guys
+[2516.96 --> 2517.66]  had already figured
+[2517.66 --> 2518.26]  this one out
+[2518.26 --> 2519.22]  well ahead of me.
+[2519.86 --> 2521.00]  And Zahid writes in,
+[2521.12 --> 2521.28]  Hello,
+[2521.46 --> 2522.32]  I was just listening
+[2522.32 --> 2523.32]  to your latest episode
+[2523.32 --> 2524.10]  and heard about
+[2524.10 --> 2525.34]  your love for Tailscale.
+[2525.86 --> 2527.04]  Not sure if you're aware,
+[2527.16 --> 2527.64]  but there are
+[2527.64 --> 2528.52]  Synology packages
+[2528.52 --> 2529.78]  available for it as well.
+[2530.34 --> 2531.24]  Keep up the great work.
+[2531.54 --> 2532.70]  Cheers, Zahid.
+[2532.94 --> 2533.82]  Hey, that's handy.
+[2534.24 --> 2535.06]  Yeah, it really is.
+[2535.10 --> 2535.24]  I mean,
+[2535.28 --> 2535.70]  that was actually
+[2535.70 --> 2536.26]  the only reason
+[2536.26 --> 2536.96]  I ended up looking
+[2536.96 --> 2538.10]  at Tailscale
+[2538.10 --> 2539.00]  in the first place
+[2539.00 --> 2540.34]  was I was futzing
+[2540.34 --> 2541.00]  about with that
+[2541.00 --> 2541.80]  Synology Naz,
+[2542.16 --> 2542.74]  ready to put it
+[2542.74 --> 2543.52]  at my mom's house,
+[2543.82 --> 2544.92]  and I was like,
+[2545.46 --> 2546.94]  what's this Tailscale thing?
+[2546.98 --> 2547.38]  I'm pretty sure
+[2547.38 --> 2547.98]  I've heard of it.
+[2548.06 --> 2548.46]  And then I did
+[2548.46 --> 2549.32]  a bit of research,
+[2549.50 --> 2550.16]  figured out it was
+[2550.16 --> 2550.80]  WireGuard,
+[2550.88 --> 2551.40]  and was like,
+[2552.12 --> 2553.56]  I'll just give this a go.
+[2554.10 --> 2555.20]  And then within 10 minutes,
+[2555.24 --> 2556.16]  I'd built out everything
+[2556.16 --> 2557.30]  I was trying to achieve
+[2557.30 --> 2557.98]  with WireGuard
+[2557.98 --> 2559.44]  for several days prior.
+[2559.90 --> 2560.78]  No kidding.
+[2560.94 --> 2561.96]  Huge fan of Tailscale.
+[2562.24 --> 2562.38]  And it,
+[2562.74 --> 2562.98]  you know,
+[2563.12 --> 2564.40]  real success story.
+[2564.92 --> 2565.96]  My mom took it back
+[2565.96 --> 2567.22]  from my mother-in-law's house
+[2567.22 --> 2567.70]  where she,
+[2567.82 --> 2568.04]  you know,
+[2568.10 --> 2569.58]  came to meet my daughter
+[2569.58 --> 2570.50]  and stuff like that.
+[2571.10 --> 2572.02]  Took it back
+[2572.02 --> 2573.00]  to her house,
+[2573.18 --> 2574.62]  plugged in one Ethernet cable,
+[2574.78 --> 2575.36]  a power cable,
+[2575.52 --> 2576.46]  pressed the on button
+[2576.46 --> 2577.06]  on the Synology.
+[2577.72 --> 2579.24]  And within a couple of minutes,
+[2579.32 --> 2580.04]  it had booted,
+[2580.44 --> 2581.88]  and Tailscale had registered it.
+[2582.04 --> 2582.66]  It didn't have to do
+[2582.66 --> 2583.54]  any dynamic DNS,
+[2584.44 --> 2585.74]  no firewall changes.
+[2585.74 --> 2587.42]  It was just magic.
+[2587.66 --> 2589.20]  I swear it was awesome.
+[2589.88 --> 2591.12]  That's why we've been seeing
+[2591.12 --> 2592.70]  so much love this week.
+[2592.88 --> 2593.72]  Erno writes in,
+[2593.90 --> 2594.84]  I'm beyond ecstatic.
+[2595.24 --> 2596.52]  I listened to episode 54
+[2596.52 --> 2597.24]  of Self-Hosted
+[2597.24 --> 2598.38]  on my way to my morning
+[2598.38 --> 2599.02]  mountain biking,
+[2599.44 --> 2600.58]  and as soon as I came home,
+[2600.66 --> 2601.96]  I had to try Tailscale.
+[2602.70 --> 2603.40]  It was pretty cool
+[2603.40 --> 2604.62]  based on Alex's explanation,
+[2604.84 --> 2605.94]  but now that I tried it,
+[2606.22 --> 2607.20]  it's even cooler.
+[2607.58 --> 2609.04]  They make it super easy
+[2609.04 --> 2609.54]  to set up.
+[2609.62 --> 2610.62]  I think I've been setting up
+[2610.62 --> 2611.86]  WireGuard for weeks,
+[2612.18 --> 2612.50]  but this,
+[2612.94 --> 2613.04]  well,
+[2613.08 --> 2613.70]  this just takes care
+[2613.70 --> 2614.60]  of all of it for me.
+[2615.12 --> 2615.80]  I have it installed
+[2615.80 --> 2616.34]  on my phone,
+[2616.72 --> 2617.38]  Kubuntu desktop,
+[2617.56 --> 2618.48]  and my Linode server.
+[2618.48 --> 2619.72]  I plan on installing it
+[2619.72 --> 2620.48]  on my Odroid,
+[2620.64 --> 2621.74]  running an Armbian,
+[2621.88 --> 2622.92]  and I'm planning on setting up
+[2622.92 --> 2624.04]  some kind of sync thing.
+[2624.78 --> 2625.44]  We'll see.
+[2625.76 --> 2626.40]  But so far,
+[2626.66 --> 2627.70]  I am super ecstatic.
+[2627.84 --> 2628.50]  Thank you so much
+[2628.50 --> 2629.44]  for your mention of Tailscale.
+[2630.28 --> 2630.74]  And Chris,
+[2631.08 --> 2631.72]  glad you made it back
+[2631.72 --> 2632.26]  to Washington.
+[2632.68 --> 2632.94]  Alex,
+[2633.06 --> 2633.66]  I hope you're enjoying
+[2633.66 --> 2634.18]  the motherland.
+[2634.46 --> 2634.82]  Sincerely,
+[2635.26 --> 2636.12]  Erno from Virginia.
+[2636.58 --> 2637.34]  I think I weigh
+[2637.34 --> 2638.84]  at least 90%
+[2638.84 --> 2639.78]  of fish and chips now.
+[2639.86 --> 2640.42]  Good for you.
+[2640.48 --> 2641.18]  Having been back here
+[2641.18 --> 2641.82]  for a month.
+[2642.12 --> 2643.14]  That's what I'd do too.
+[2643.28 --> 2643.84]  I'd have to.
+[2644.06 --> 2645.00]  Fish and chips and curry.
+[2645.68 --> 2646.50]  So Taylor writes in,
+[2646.90 --> 2647.48]  thanks so much
+[2647.48 --> 2648.20]  for the amazing show
+[2648.20 --> 2649.18]  that is self-hosted.
+[2649.28 --> 2650.06]  Every two weeks,
+[2650.14 --> 2651.46]  I'm refreshing my podcatcher
+[2651.46 --> 2652.30]  like a madman.
+[2652.86 --> 2653.72]  I was just catching up
+[2653.72 --> 2654.70]  on episode 54
+[2654.70 --> 2655.70]  and could relate
+[2655.70 --> 2657.54]  to Alex's remote access woes.
+[2658.06 --> 2659.00]  Tailscale's a solution
+[2659.00 --> 2659.98]  that seems to be popular
+[2659.98 --> 2661.40]  on Reddit and IRC,
+[2661.66 --> 2662.84]  but I wanted to mention
+[2662.84 --> 2663.74]  something that has been
+[2663.74 --> 2665.24]  working really well for me,
+[2665.44 --> 2666.82]  and that is ZeroTier.
+[2667.32 --> 2667.52]  Now,
+[2667.58 --> 2669.04]  ZeroTier is a distributed
+[2669.04 --> 2669.92]  WAN solution
+[2669.92 --> 2671.20]  that essentially creates
+[2671.20 --> 2672.96]  a global overlay network,
+[2672.96 --> 2674.86]  kind of like Nebula does.
+[2675.38 --> 2676.50]  It's open source
+[2676.50 --> 2677.40]  and self-hostable
+[2677.40 --> 2678.98]  with NAS packages,
+[2679.30 --> 2680.50]  third-party web management
+[2680.50 --> 2681.00]  GUIs,
+[2681.10 --> 2681.66]  and so on.
+[2682.16 --> 2682.96]  They just released
+[2682.96 --> 2684.50]  a DNS solution as well,
+[2684.70 --> 2686.24]  which sounds very similar
+[2686.24 --> 2687.16]  to the Tailscale
+[2687.16 --> 2688.40]  Magic DNS offering,
+[2688.82 --> 2690.24]  and I just wanted to give you guys
+[2690.24 --> 2691.54]  another self-hosted option.
+[2691.90 --> 2692.46]  Thanks for the show.
+[2692.46 --> 2693.88]  I definitely want to give
+[2693.88 --> 2694.88]  Headscale a try.
+[2694.98 --> 2696.72]  That's why I'm kind of waiting
+[2696.72 --> 2697.84]  to replace Nebula
+[2697.84 --> 2698.78]  with Tailscale,
+[2699.02 --> 2699.82]  is I want to see
+[2699.82 --> 2701.26]  how viable it is
+[2701.26 --> 2702.54]  to use Headscale
+[2702.54 --> 2704.18]  and self-host
+[2704.18 --> 2705.06]  the server component
+[2705.06 --> 2705.64]  of Tailscale,
+[2705.76 --> 2706.42]  but that also looks
+[2706.42 --> 2706.84]  really great.
+[2706.90 --> 2707.24]  It does.
+[2707.46 --> 2708.60]  There's so many options.
+[2708.72 --> 2709.74]  I just had to give a plug
+[2709.74 --> 2710.46]  for Nebula, too.
+[2711.12 --> 2711.30]  Now,
+[2711.34 --> 2713.22]  the only thing about ZeroTier
+[2713.22 --> 2715.26]  that kind of gives me,
+[2715.50 --> 2718.44]  it's just a 1% or 2% pause,
+[2719.04 --> 2720.26]  is that the protocol
+[2720.26 --> 2721.08]  is custom,
+[2721.08 --> 2723.16]  whereas the Tailscale protocol
+[2723.16 --> 2725.14]  is based around WireGuard.
+[2725.36 --> 2725.48]  So,
+[2726.50 --> 2726.88]  I mean,
+[2726.92 --> 2727.62]  who's to say one
+[2727.62 --> 2728.48]  is better than the other,
+[2728.66 --> 2730.76]  but I love me some WireGuard.
+[2731.14 --> 2732.10]  If I were betting,
+[2732.22 --> 2732.70]  man, Alex,
+[2732.80 --> 2733.46]  I know which one
+[2733.46 --> 2734.04]  I would bet on.
+[2734.46 --> 2736.16]  It's not one
+[2736.16 --> 2736.90]  that's been made up.
+[2737.72 --> 2738.56]  I really,
+[2738.70 --> 2739.94]  I respect the WireGuard
+[2739.94 --> 2741.06]  project immensely,
+[2741.40 --> 2742.68]  so it's just clearly
+[2742.68 --> 2743.16]  like the one
+[2743.16 --> 2744.00]  I would put my trust in
+[2744.00 --> 2744.74]  if my data was
+[2744.74 --> 2745.90]  truly critical.
+[2746.30 --> 2746.98]  I want to mention,
+[2747.20 --> 2747.88]  thank you everybody
+[2747.88 --> 2748.40]  who went to
+[2748.40 --> 2749.16]  self-hosted.show
+[2749.16 --> 2749.78]  slash contact
+[2749.78 --> 2751.02]  and sent in their question
+[2751.02 --> 2751.62]  we also have
+[2751.62 --> 2752.64]  the Discord community,
+[2752.78 --> 2753.44]  self-hosted.show
+[2753.44 --> 2754.06]  slash Discord,
+[2754.22 --> 2755.28]  which is always popping off.
+[2755.72 --> 2757.26]  And our Matrix community
+[2757.26 --> 2758.24]  is also growing.
+[2758.60 --> 2759.78]  There's a good conversation
+[2759.78 --> 2761.06]  of self-hosters going on.
+[2761.36 --> 2762.34]  You can find our Matrix server.
+[2762.46 --> 2762.66]  We have a
+[2762.66 --> 2764.08]  jupiterbroadcasting.com
+[2764.08 --> 2764.66]  Matrix server.
+[2764.94 --> 2766.80]  And probably the easiest way
+[2766.80 --> 2768.26]  to just get like a quick guide
+[2768.26 --> 2769.48]  is to actually go to
+[2769.48 --> 2770.56]  linuxunplugged.com
+[2770.56 --> 2771.10]  slash Matrix.
+[2771.24 --> 2771.90]  I haven't put that up
+[2771.90 --> 2772.56]  anywhere else yet.
+[2773.06 --> 2774.20]  But there is a community
+[2774.20 --> 2775.08]  growing out there
+[2775.08 --> 2776.00]  in Matrix land
+[2776.00 --> 2776.60]  of self-hosters.
+[2777.18 --> 2777.60]  Oh, Chris,
+[2777.64 --> 2778.26]  what have you done?
+[2778.26 --> 2778.88]  You've invited
+[2778.88 --> 2780.02]  another set of notifications
+[2780.02 --> 2781.14]  into my life.
+[2781.24 --> 2782.12]  Thank you so much.
+[2782.58 --> 2784.38]  Oh, oh, I know, Alex.
+[2784.46 --> 2785.60]  I know so well.
+[2786.52 --> 2787.18]  But you know,
+[2787.24 --> 2788.64]  I'm trying to assemble
+[2788.64 --> 2789.10]  the troops
+[2789.10 --> 2790.48]  because I'm so close
+[2790.48 --> 2791.36]  to getting
+[2791.36 --> 2793.18]  this automation bliss
+[2793.18 --> 2794.48]  where, you know,
+[2794.54 --> 2795.90]  my goal is to
+[2795.90 --> 2796.90]  make it so my wife
+[2796.90 --> 2798.06]  no longer has to worry
+[2798.06 --> 2799.26]  about blowing
+[2799.26 --> 2801.22]  a 15 amp circuit.
+[2801.22 --> 2802.22]  If we have a heater going
+[2802.22 --> 2802.68]  and she wants
+[2802.68 --> 2803.46]  to run the toaster,
+[2803.96 --> 2804.82]  I want Home Assistant
+[2804.82 --> 2805.60]  to figure it out.
+[2806.06 --> 2806.52]  And I know,
+[2806.66 --> 2807.70]  like our guest Matt
+[2807.70 --> 2808.46]  and others out there
+[2808.46 --> 2809.04]  have done this,
+[2809.10 --> 2809.74]  but I could use
+[2809.74 --> 2810.28]  some wisdom.
+[2810.84 --> 2811.86]  So the Matrix server
+[2811.86 --> 2812.52]  is a great spot
+[2812.52 --> 2813.30]  to let me know
+[2813.30 --> 2814.64]  because I'm trying
+[2814.64 --> 2815.36]  to drop in
+[2815.36 --> 2815.84]  on the Matrix
+[2815.84 --> 2816.46]  from time to time.
+[2816.54 --> 2817.30]  The Discord's also
+[2817.30 --> 2817.86]  really great.
+[2818.14 --> 2818.94]  Or Telegram.
+[2819.34 --> 2820.12]  How have you solved
+[2820.12 --> 2821.08]  this particular problem?
+[2821.28 --> 2822.00]  What should I do?
+[2822.10 --> 2823.40]  And will my Z-Wave devices
+[2823.40 --> 2824.56]  update fast enough?
+[2825.20 --> 2825.90]  Because it seems like
+[2825.90 --> 2826.40]  there's sometimes
+[2826.40 --> 2827.60]  like a 20-second lag.
+[2828.10 --> 2828.66]  All these things.
+[2828.72 --> 2829.32]  Share your wisdom.
+[2829.32 --> 2830.16]  Let's get this energy
+[2830.16 --> 2830.94]  monitoring figured out
+[2830.94 --> 2831.60]  because I think this is
+[2831.60 --> 2832.14]  going to be big
+[2832.14 --> 2833.28]  in the self-hosting community.
+[2833.90 --> 2834.38]  And as always,
+[2834.54 --> 2835.36]  I want to give a big
+[2835.36 --> 2837.14]  thank you to our SRE subscribers.
+[2837.38 --> 2838.56]  You make this show possible.
+[2839.16 --> 2839.62]  You can go to
+[2839.62 --> 2840.76]  selfhosted.show
+[2840.76 --> 2841.78]  slash SRE
+[2841.78 --> 2842.90]  to support the show.
+[2843.56 --> 2844.40]  And you can find us
+[2844.40 --> 2844.96]  on Twitter.
+[2845.10 --> 2845.84]  Alex is over there
+[2845.84 --> 2846.82]  at Ironic Badger.
+[2846.94 --> 2847.96]  I'm at Chris LAS
+[2847.96 --> 2848.58]  and the show
+[2848.58 --> 2849.94]  at Self Hosted Show.
+[2850.30 --> 2851.18]  And as usual,
+[2851.30 --> 2851.86]  thanks for listening,
+[2851.98 --> 2852.28]  everybody.
+[2852.50 --> 2852.78]  That was
+[2852.78 --> 2853.82]  selfhosted.show
+[2853.82 --> 2854.96]  slash 55.
+[2854.96 --> 2860.36]  was
+[2860.36 --> 2861.26]  thanks for listening.
+[2861.74 --> 2862.68]  And I
+[2862.68 --> 2871.42]  Operation
+[2871.42 --> 2873.22]  might
+[2873.22 --> 2873.24]  have

56： Feeling Wyze _summary.txt

@@ -0,0 +1,75 @@
+• Apple's new MacBook event
+• Google's Pixel event overshadowed by Apple announcement
+• Discussion of M1 Max and M1 Pro chips and their potential for use as a home server
+• Author's decision to sell their 16-inch MacBook Pro and switch to an M1 MacBook Air
+• Purchase of a 14-inch MacBook Pro with M1 Max chip and discussion of its features
+• Discussion of laptops and their features
+• USB-A port availability on new laptops
+• Importance of SD card slot and its uses
+• Running Linux on M1 Macs using Asahi Linux team's support
+• Compatibility with Apple devices and potential for future updates
+• Comparison between Raspberry Pi 4 and Home Assistant Blue setup
+• Slowdown in Raspberry Pi 4 performance due to increased automations
+• Exploring router hardware alternatives, including temporary solutions
+• Using VLANs on Raspberry Pi 4 as WAN and LAN ports
+• OpenSense firewall configuration and plugins
+• Replaced built-in OpenSense DNS with AdGuard Home for improved performance
+• Set up AdGuard Home to run alongside WireGuard on the same box
+• Discussed a community-created repository of plugins and packages for OpenSense, including:
+	+ Cloudflare D
+	+ Influx
+	+ Mosquito
+	+ Smoke Ping
+	+ Tail Scale
+• Utilized Uptime Kuma as a status page tool to monitor network availability and notify team members in case of outages
+• Discussed alternative monitoring tools, including StatPing and its fork, StatPing-NG
+• Linode's infrastructure and features
+• One-click deployment and scalability options
+• Block storage with NVMe disks and cost savings
+• Object storage and flexibility for growing projects
+• Tutorials, guides, and customer support from Linode
+• Using Linode for experimenting with new applications
+• Running public-facing services on Linode (e.g. Jupyter broadcasting)
+• Linode's history and reputation as a hosting provider
+• Discussion of transcoding using QuickSync and iGPU for three camera feeds
+• Introduction to Frigate software for real-time object detection using Google TensorFlow library
+• Personal anecdote about Frigate detecting a stray cat at the doorbell, potentially saving the owner's life
+• Similar story from another user with a cat under an RV that was detected by their Wi-Fi camera
+• Recommendation of Coral device for Frigate setup to avoid CPU-intensive processing
+• Challenges in finding Coral devices due to supply chain shortages
+• Detection of dogs and people by Frigate
+• False negatives and misidentifications
+• Wise Bridge setup with RTSP firmware
+• Encoding delay when using RTSP directly on cameras
+• Concerns about feature removal and dependence on Wise's support
+• Use of SD cards for camera storage
+• Home Assistant integration and media browser features
+• Discussion of using beta version for extra features
+• Introduction of Google Coral device for machine learning tasks
+• Review of its capabilities and size
+• Appreciation for dedicated silicon in computing
+• Mention of Apple's new CPUs with ProRes encoding circuitry
+• Preview of new Wyze Doorbell Pro and potential review
+• Links to Morgan's create configs and promotion of Backblaze.com
+• Recommendation of Backblaze for unlimited computer backup
+• Backblaze.com/SSH for a free 15-day trial
+• Alternative to Wall Panel: Fully Kiosk Browser, with similar features and a small $5 fee
+• Maintainer change for Wall Panel, and Alarm MQTT project looking for a new maintainer
+• Discussion of using Fire tablets as baby monitors, including the use of Lineage OS
+• Communication between Wall Panel and Home Assistant over MQTT
+• Issues with Amazon Fire tablets crashing and performance issues
+• Solution to slow and leggy Echo-like performance on Fire tablets
+• Self-hosted Plex library setup and issue with wife preferring Netflix's curated experience
+• Collections in Plex media library
+• Using Plex Meta Manager for automated collection creation
+• Customizing collections with filters (e.g., by studio, actor)
+• Script setup and running on a cron job overnight
+• Average processing time: 1 hour for 1000 movies
+• Warning for 2U device users upgrading to Home Assistant October release
+• Z-Wave migration issues and switching to Matter integration
+• Discussion of Home Assistant's migration process and potential issues
+• Need for careful consideration in community-driven open-source projects
+• Importance of maintaining old systems vs adopting new ones
+• Gratitude for existing integration working despite limitations
+• Call to action for listeners to share their experiences and questions
+• Promotion of the show, network, and social media handles

56： Feeling Wyze _transcript.txt

@@ -0,0 +1,757 @@
+[0.00 --> 7.86]  Well, I know this isn't the Apple Today podcast, but we've got to acknowledge that there was an event this week which has put a big hole in my wallet.
+[8.40 --> 9.74]  Oh, did it?
+[10.04 --> 16.68]  Yeah, this is one of those tech events that sucked all the air out of the tech room for the entire week that we're recording.
+[16.82 --> 17.76]  There's just no way around it.
+[17.84 --> 20.42]  So you get a big boy, you get one of them Max Max.
+[20.60 --> 28.64]  I actually felt really sorry for Google, just to digress for a second, because they held their Pixel event the day after Apple announced all these MacBooks.
+[28.64 --> 29.08]  Yeah.
+[29.08 --> 33.94]  And you could just tell all the tech press were like, yeah, we've already heard all about this Pixel thing.
+[34.40 --> 36.58]  MacBook, MacBook, MacBook, let's just cover the MacBook.
+[36.92 --> 41.00]  I know, and Google announced their Tensor SoC and it really didn't get much interest in it.
+[41.16 --> 41.64]  Not at all.
+[41.76 --> 50.12]  You know, like I told you after the event, like one of my first thoughts was like, oh man, you know, Alex, what I'm kind of excited about is the idea of one of these as a home server.
+[50.26 --> 51.56]  I've been thinking of this more and more.
+[51.56 --> 56.38]  You know, when a Mac mini is just sitting there not doing much, the processor's taking hardly any power.
+[56.66 --> 58.80]  12 watts is like an average load.
+[58.80 --> 59.88]  Like that's incredible.
+[59.88 --> 67.06]  And you could really see if they're building an H.264 accelerated encoding and decoding in these chips.
+[67.06 --> 70.74]  And these things are low power and they have Thunderbolt expansion.
+[71.18 --> 73.16]  And who knows if they'll make desktop models.
+[73.52 --> 75.92]  I could see these being a pretty legitimate home server.
+[76.32 --> 77.20]  Replacing Pies.
+[77.54 --> 77.74]  Yeah.
+[77.88 --> 81.94]  I was thinking the biggest problem with it would be connecting disks up to the damn thing.
+[82.04 --> 89.28]  But if you have Thunderbolt, I suppose you could be baller and spend thousands of dollars on a Thunderbolt shelf and connect disks that way if you like.
+[89.28 --> 91.82]  You know, I'd much prefer real expansion.
+[92.20 --> 92.36]  Right.
+[92.44 --> 96.46]  But in my, like for my situation, I'm doing USB storage.
+[97.16 --> 100.70]  I never thought I would do USB storage in a million years.
+[100.84 --> 105.60]  But here I am with the Raspberry Pi 4 and I have pooled USB storage.
+[105.68 --> 109.04]  So Thunderbolt, external Thunderbolt would actually be an upgrade for me.
+[109.54 --> 111.38]  I see you like to live dangerously.
+[111.46 --> 111.86]  I do.
+[112.30 --> 115.76]  You know, that's why I like to stay trained just in case I ever need a plan B.
+[115.76 --> 117.96]  And you can too if you go to a cloudguru.com.
+[118.20 --> 120.18]  Yes, this episode is brought to you by a cloud guru.
+[120.52 --> 124.22]  The leader in learning for the cloud, Linux and other modern tech skills.
+[124.66 --> 127.24]  Hundreds of courses and thousands of hands-on labs.
+[127.58 --> 128.06]  Get certified.
+[128.34 --> 128.72]  Get hired.
+[129.06 --> 131.32]  Get learning at a cloudguru.com.
+[131.80 --> 135.58]  A couple of months ago, I sold my 16-inch MacBook Pro.
+[135.72 --> 140.58]  I had an i9 model with a 5600M Radeon GPU in it.
+[140.66 --> 144.32]  It was, you know, like a $4,000, $4,500 laptop.
+[144.32 --> 146.22]  Kind of crazy, actually, when you think about it.
+[146.34 --> 146.44]  Yeah.
+[146.84 --> 152.14]  And I sold it to somebody two months ago because we've known this event's been coming for a while.
+[152.50 --> 160.70]  And I thought, right, can I live with just an M1 MacBook Air as my primary system for two or three months until these new MacBooks come out?
+[160.88 --> 163.10]  And you also have a desktop system as well.
+[163.12 --> 164.58]  So it's not like your only computer.
+[165.04 --> 165.28]  True.
+[165.58 --> 170.26]  But I do 99% of my work now on this MacBook Air, the fanless MacBook Air.
+[170.60 --> 170.70]  Do you?
+[170.70 --> 173.56]  It is a phenomenal system, truly.
+[174.56 --> 176.42]  And I'm very excited.
+[176.54 --> 179.88]  I've ordered one of the M1 Max 14-inch MacBook Pros.
+[180.58 --> 181.02]  Oh, yeah.
+[181.10 --> 183.40]  You know, the 14-inch seems like a pretty sweet rig.
+[183.46 --> 185.94]  A lot of horsepower for a pretty small footprint.
+[186.20 --> 187.86]  64 gigs of RAM in that bad boy.
+[187.94 --> 190.72]  I have no idea why I need 64 gigs of RAM.
+[191.28 --> 194.76]  But, hey, you know, in for a penny, in for a pound.
+[195.00 --> 196.02]  That's a tough one, huh?
+[196.46 --> 198.38]  Because it's like you can't change it after the fact.
+[198.70 --> 204.42]  So if you think maybe you're going to use a lot of RAM, you might as well go all the way in.
+[204.54 --> 210.44]  But, and I don't really know how this works, but I think that also means then you've got 64 gigs of video RAM addressable or something like that.
+[210.44 --> 211.80]  Because I know it's a unified memory space.
+[211.80 --> 213.10]  Something like that, yeah.
+[213.72 --> 219.54]  Yeah, 32-core GPU and the M1 Max, you know, 10-core, whatever it is.
+[219.66 --> 220.56]  I'm not entirely sure.
+[220.60 --> 228.22]  Honestly, I watched the event and I pressed go on my purchase after the store went live within about three or four minutes, honestly.
+[228.22 --> 233.34]  I really didn't spend very long because it's 2021 and everything is in short supply.
+[233.50 --> 238.14]  And I knew if I waited even an hour, it was going to take weeks extra.
+[238.38 --> 239.20]  Yep, yep, yep, yep.
+[239.26 --> 239.72]  I know it.
+[239.84 --> 247.26]  And I'll tell you, I would, that instant, I would have been there with that instant buy if they had announced everything that's in that 14-inch MacBook in a mini.
+[248.34 --> 251.26]  A little headless Mac mini, that would have been the way for me.
+[251.38 --> 254.70]  That, like I said, that just wouldn't make it, that would just be such an incredible server.
+[254.70 --> 258.14]  But also, with that kind of horsepower, you could also have it be your desktop.
+[258.46 --> 260.04]  Like, that's, for me, a consolidation.
+[260.24 --> 260.72]  That'd be nice.
+[261.52 --> 268.10]  The only thing missing from this new set of laptops for me was a single USB-A port.
+[268.48 --> 272.16]  I think it was possibly asking a bit too much for them to put that one back in.
+[272.26 --> 280.16]  But I was hoping because, you know, being back in England last month, I was doing a lot of stuff with old tech.
+[280.16 --> 284.04]  You know, I was taking files off my mom's old Windows XP laptops.
+[284.70 --> 287.80]  I needed USB-A, so I had to have a dongle for that.
+[287.86 --> 289.38]  So I'm still going to have to keep that one around.
+[289.86 --> 292.92]  But thank the Lord, there's an SD card slot.
+[292.94 --> 293.70]  Yes, there is.
+[293.86 --> 294.50]  Yes, there is.
+[294.56 --> 294.90]  Hallelujah.
+[295.38 --> 295.68]  Yes.
+[295.88 --> 297.36]  And, you know, people say, why do you need SD?
+[297.62 --> 298.54]  It's like, come on, man.
+[298.54 --> 302.48]  Even if you don't have a camera that uses it, you could use it for external storage, portable storage.
+[303.04 --> 304.28]  It's great for backup.
+[304.60 --> 305.68]  It's, yeah, yeah.
+[306.24 --> 307.50]  Yeah, I think they set the bar.
+[307.50 --> 309.38]  I really think they set the bar with this one.
+[309.38 --> 321.30]  And I'm really kind of looking forward to see where the Asahi Linux team gets with support for Linux because I could see running these things with macOS and then trying to do Docker on top of all of that.
+[321.38 --> 325.96]  But it seems like a lot of pain in the knee when you could just run Linux directly on there.
+[326.06 --> 327.84]  And I think they're making good progress.
+[328.00 --> 328.80]  We'll see where that goes.
+[329.46 --> 332.00]  I have an M1 Mac Mini now.
+[332.00 --> 334.64]  I haven't gotten through, like, setting it up yet.
+[335.04 --> 338.52]  But my intention is to try Asahi on it and see how it goes.
+[338.74 --> 342.26]  And, of course, I ordered the Mac Mini.
+[342.84 --> 343.68]  I thought, all right, fine.
+[343.84 --> 347.20]  I know Asahi Linux will support this because that's what the developers are using.
+[347.46 --> 355.30]  So even though I know Apple's about, even though I knew, I knew Apple was about to announce new machines, I ordered the Mini M1.
+[355.92 --> 359.50]  Even risking there might have been an updated Mini because I knew that would have the best compatibility.
+[359.50 --> 364.82]  But I have to say, the next day Apple announced the event and it still hurt.
+[364.96 --> 367.00]  It still felt like I should have waited.
+[367.70 --> 368.76]  But it's good.
+[368.82 --> 369.38]  It's here now.
+[369.50 --> 370.18]  I've already got it.
+[370.34 --> 373.10]  But they didn't announce anything in the Mac Mini form factor.
+[373.46 --> 374.98]  So in a way you have indicated.
+[375.28 --> 375.72]  That's true.
+[375.78 --> 376.36]  I suppose so.
+[376.86 --> 377.72]  I suppose so.
+[378.08 --> 386.24]  I've been trying to, I've just been trying to think of my setup and how I'm going to redo it because now that I am doing so much more on my Raspberry Pi in Home Assistant,
+[386.24 --> 398.78]  I'm running MQTT now and I've got a lot more automations going and I'm now doing power statistical tracking for a lot of different devices and it has noticeably slowed down.
+[398.78 --> 409.18]  The speed difference now between my Home Assistant Blue, which is doing a lot less, and the Raspberry Pi 4 in the RV is extremely noticeable.
+[409.46 --> 410.86]  It's night and day.
+[411.00 --> 418.54]  We're talking like 10 minutes, 15 minutes to do a snapshot on the Raspberry Pi and two minutes to do a snapshot on the Home Assistant Blue.
+[418.72 --> 418.84]  Oh.
+[418.84 --> 424.84]  So you were thinking about doing some stuff with your router at the studio.
+[425.08 --> 427.44]  Have you gotten any further with that yet?
+[428.10 --> 429.08]  Not necessarily.
+[429.94 --> 432.52]  We hit a wall on a hardware wall.
+[432.92 --> 440.38]  But one thing we're thinking about trying in the meantime until we get the right hardware because we wanted to, we found this nice little x86 box that we thought would work really well.
+[440.88 --> 443.28]  But there's just, we just can't, we cannot get it.
+[443.46 --> 444.74]  Nobody has it available right now.
+[444.82 --> 445.04]  Yeah.
+[445.04 --> 445.24]  Yeah.
+[445.34 --> 445.74]  Yeah.
+[445.92 --> 450.00]  So we are thinking about just in the interim trying a Raspberry Pi just as a temporary solution.
+[450.18 --> 464.12]  I saw an interesting post on this, which I'll try and find and put in the show notes, where people were using VLANs to actually use a Raspberry Pi 4 and its single Ethernet port as both a WAN and a LAN port.
+[464.20 --> 467.48]  So I thought that might be an interesting experiment for you to try.
+[467.48 --> 467.78]  Hmm.
+[468.62 --> 475.14]  My thought was just put the WAN on a USB Ethernet because the USB 3 is pretty good, you know, and it's just Comcast.
+[475.50 --> 480.68]  So I could put that on a USB Ethernet and then the LAN side would be connected to the actual Ethernet port.
+[480.68 --> 490.22]  Well, if you try out OpenSense, which is my current favorite firewall of choice for the self builders, I've come across a really cool repo.
+[490.32 --> 493.48]  I think I've mentioned it briefly on the show, but I'm going to go into a bit more detail today.
+[493.48 --> 499.86]  This is from a guy on Twitter who goes by the handle MIMU underscore MUC.
+[500.06 --> 501.44]  That rolls off the tongue, doesn't it?
+[501.84 --> 504.26]  There's a link to his Twitter in the show notes.
+[504.80 --> 514.06]  But essentially what this does, this repo, is it provides a whole bunch of plugins for OpenSense that aren't officially supported.
+[514.24 --> 520.14]  So there's stuff in there like Traffic, Speedtest, Caddy, Unify Controller.
+[520.14 --> 526.36]  But for me, the killer app is that I can now run AdGuard Home directly on my OpenSense instance as well.
+[526.60 --> 534.08]  So I've completely disabled the unbound DNS that's built into OpenSense and just replaced it completely with AdGuard Home.
+[534.80 --> 537.50]  And for me, that's been really solid.
+[537.92 --> 544.26]  And when I'm coming in over WireGuard, I can now get AdGuard Home straight away on the same box as WireGuard.
+[544.80 --> 546.34]  It's just really nice.
+[546.64 --> 547.12]  Hmm.
+[547.12 --> 547.32]  Hmm.
+[548.04 --> 551.08]  Yeah, I have to say that that is a very compelling setup.
+[551.54 --> 558.72]  And this kind of reminds me a little bit of Hacks for Home Assistant, where it's a community-created set of repositories that you can add on.
+[558.80 --> 560.14]  It's a very similar deal, yeah.
+[560.26 --> 561.42]  And it's nice to see this.
+[561.46 --> 562.62]  Like, the essentials are in there.
+[562.82 --> 566.12]  I also noticed that, of course, you've got Speedtest is in there.
+[566.20 --> 566.64]  Makes sense.
+[566.74 --> 567.86]  Grafana, Influx.
+[567.86 --> 571.72]  So that's all really nice to have as, you know, an easy-to-install add-on.
+[572.04 --> 572.68]  That's great.
+[572.68 --> 576.58]  If you wanted to, you could even run Mosquito, MQTT.
+[577.36 --> 577.72]  There's a...
+[577.72 --> 579.84]  So it's split into two halves, right?
+[579.90 --> 583.26]  There's a bunch of plugins which have a bit more about them.
+[583.38 --> 585.96]  So they require graphical configuration and that kind of thing.
+[586.24 --> 591.54]  But there's also a list of packages, which if you install those, you'll need to drop to the terminal to configure those.
+[591.54 --> 593.94]  And there's a few that stand out for me in here.
+[594.80 --> 596.74]  Cloudflare D, which is pretty useful.
+[598.34 --> 599.20]  Influx is in there.
+[599.40 --> 599.76]  Mosquito.
+[600.26 --> 600.98]  Smoke Ping.
+[601.08 --> 601.28]  Yeah.
+[601.28 --> 603.16]  You can actually run that directly on your firewall.
+[603.72 --> 606.06]  Tail Scale, which you know I love these days.
+[606.76 --> 612.38]  So, yeah, I've found this repository to be an incredibly valuable asset to make open sense.
+[612.44 --> 614.04]  It just takes it to that next level for me.
+[614.12 --> 615.70]  And really makes it that all-in-one box.
+[616.10 --> 616.50]  Absolutely.
+[616.50 --> 620.80]  I mean, you could argue it's now a single point of failure for a bit more stuff.
+[620.80 --> 622.80]  But it was doing DNS and internet anyway.
+[622.96 --> 626.22]  So if that went out when I was in England, I was out of luck anyway.
+[626.42 --> 628.56]  So am I bothered?
+[628.96 --> 630.56]  You're not a thousand-person enterprise.
+[630.96 --> 633.36]  You know, like, yes, there is more risk to having it on one box.
+[633.46 --> 639.08]  But when you're in a home, there's also advantages to simplifying and reducing power usage.
+[639.66 --> 639.98]  Absolutely.
+[640.20 --> 644.70]  Now, talking of, you know, monitoring and keeping things available and stuff like that,
+[644.82 --> 650.34]  we've set up a new status page for the network using one of my new favorite tools in the world
+[650.34 --> 651.98]  called Uptime Kuma.
+[652.36 --> 654.84]  And isn't this just, isn't this nice and clean?
+[654.96 --> 655.94]  And we're putting it all out there.
+[656.10 --> 658.62]  You know, like if there's an outage, you're going to know about it.
+[658.74 --> 660.68]  Status.jupiterbroadcasting.com.
+[660.88 --> 664.74]  I mean, I used to use StatPing for a little while, but then there was a new version came
+[664.74 --> 666.20]  along and it broke a bunch of stuff.
+[666.28 --> 670.48]  And then the developer kind of got bored and just quit, I think is what happened.
+[670.48 --> 675.20]  I mean, if you go to the StatPing repository now, the last update was about 10 months ago.
+[675.48 --> 681.32]  I did see on Reddit this week that there's a StatPing-NG fork appeared, a StatPing.
+[681.42 --> 682.96]  So we'll have to keep our eye on that one.
+[683.60 --> 688.82]  But Uptime Kuma is designed after Uptime Robot, if you're familiar with that one.
+[689.30 --> 692.68]  There's a live demo on their GitHub page, which is linked in the show notes.
+[692.68 --> 696.32]  And this thing is, it's just simple.
+[696.82 --> 702.40]  You know, it monitors an endpoint, so it could be an API, or in our case, it could be an RSS
+[702.40 --> 705.86]  feed for all the shows that we have as a network.
+[705.98 --> 710.60]  And then I've got a group with me, Chris and Wes in it, that we all get a notification
+[710.60 --> 713.82]  if these pings fail for more than three minutes.
+[714.44 --> 717.92]  So it supports Telegram, Discord, Gotify.
+[718.10 --> 720.04]  There's a bunch of stuff it supports out of the box.
+[720.04 --> 728.02]  And I've just run it in a container on a separate Linode instance, and it just works great.
+[728.92 --> 734.24]  Yeah, and it's given us a nice, just easy, no-brainer overview of what's going on.
+[734.30 --> 738.10]  In fact, just recently we had a listener say, hey, is such and such RSS feed down, or was
+[738.10 --> 738.84]  there no show today?
+[739.24 --> 740.30]  You go, wait, let me go check.
+[741.04 --> 741.80]  Pull the status feed.
+[742.26 --> 743.06]  Nope, it's up.
+[744.56 --> 746.04]  Linode.com slash SSH.
+[746.04 --> 750.24]  Go there to receive $100 in 60-day credit, and you support the show.
+[750.74 --> 752.64]  Linode can be your lab in the cloud.
+[752.74 --> 753.64]  That's how I use them.
+[753.76 --> 757.50]  I'm always trying things out because their infrastructure is super fast.
+[757.60 --> 759.82]  They're constantly investing in that.
+[760.24 --> 764.40]  They are their own ISP, so all of their connections between data centers and out to the internet
+[764.40 --> 765.32]  are super fast.
+[765.86 --> 768.54]  The hypervisors have 40 gigabit connections coming in.
+[768.54 --> 774.92]  And Linode just recently revamped their block storage with NVMe super fast PCIe disks, and
+[774.92 --> 778.48]  they cost 30% to 50% less than the major cloud providers out there.
+[779.24 --> 784.22]  So it's just a great way to experiment and try something out, and then grow it and scale
+[784.22 --> 787.96]  it up because they make it really straightforward to expand the RAM, the storage, and you can
+[787.96 --> 789.44]  utilize things like object storage.
+[789.80 --> 793.70]  They have S3-compatible object storage that you can use to increase storage as much as
+[793.70 --> 794.00]  you like.
+[794.08 --> 797.34]  I mean, that kind of stuff makes it super flexible, but it's just a great way to learn, too.
+[797.34 --> 799.80]  And if you've never set anything up before, don't worry.
+[800.54 --> 805.82]  Not only do they have great guides, super good tutorials, but they also just have one-click
+[805.82 --> 806.26]  deployment.
+[806.40 --> 811.06]  So you could do a one-click deployment of NextCloud and see if you like it or anything,
+[811.26 --> 816.18]  really, because you can start with a pretty base image of just the OS you like, some container
+[816.18 --> 819.92]  runtime stuff, and then you add the container on top of that and try it out.
+[820.52 --> 825.86]  And I know for some of us, you're willing to invest the time to learn something, but you
+[825.86 --> 827.30]  want to see if it's worth it first.
+[827.48 --> 829.24]  And Linode is great for that kind of thing.
+[830.00 --> 830.94]  I'll do a one-click.
+[831.52 --> 834.94]  I'll figure out how it's set up and how it's running, if I like the application, if it's
+[834.94 --> 835.72]  worth all the effort.
+[836.28 --> 841.34]  And then I'll often rebuild it either locally or on Linode with a DIY setup or in my existing
+[841.34 --> 842.16]  application server.
+[842.24 --> 846.24]  One of the things that we do here is we run all of our Jupyter broadcasting services up
+[846.24 --> 848.62]  on Linode for anything that's public-facing.
+[848.62 --> 855.10]  And there's a lot of catch-all services that just do things like supply us a pasteboard
+[855.10 --> 861.10]  for us to put our emails from our listeners or check the uptime of a server or host our
+[861.10 --> 864.26]  HedgeDoc Markdown collaborative editing instance.
+[864.52 --> 865.70]  And there's applications.
+[865.86 --> 869.90]  And you can put all of that just on one Linode because they're so crazy powerful and fast.
+[870.14 --> 872.64]  If it runs on Linux, it's going to run on Linode.
+[872.80 --> 875.72]  They started in 2003 as one of the first in this business.
+[875.72 --> 878.00]  And they have refined and honed it ever since.
+[878.32 --> 879.50]  And nobody does it like them.
+[879.64 --> 882.10]  And they back it up with the best customer service in the business.
+[882.36 --> 884.82]  I've been a customer for more than two years now.
+[884.88 --> 886.86]  And I've been happy every single day.
+[887.10 --> 888.38]  They haven't let me down yet.
+[888.74 --> 889.46]  Go try them out.
+[889.76 --> 890.40]  Support the show.
+[890.54 --> 891.32]  And get yourself $100.
+[892.12 --> 894.22]  Linode.com slash SSH.
+[896.38 --> 902.34]  Well, it's time to welcome back to the show our resident doorbell expert, Morgan the doorbell guy.
+[902.84 --> 903.80]  Welcome back, Morgan.
+[903.90 --> 904.34]  How are you doing?
+[904.78 --> 905.28]  Thank you.
+[905.28 --> 908.80]  I'm not sure how I feel about the doorbell guy, but it's a pleasure joining back.
+[909.68 --> 911.76]  Hey, we had a jingle with that phrase in it.
+[911.82 --> 913.54]  So, I mean, that name's going to stick now.
+[914.14 --> 914.54]  Yeah, I think.
+[914.66 --> 915.06]  That's true.
+[915.26 --> 915.84]  That is true.
+[915.96 --> 918.64]  I think it's time to actually join Twitter as the doorbell guy.
+[921.22 --> 923.28]  Yeah, although today we're not just talking doorbells.
+[924.12 --> 924.64]  We aren't.
+[924.72 --> 932.10]  No, we thought we'd finally bring up Frigate, which is a new NVR network video recorder piece of software.
+[932.10 --> 934.20]  It's free and open source.
+[934.42 --> 935.94]  And, Morgan, you've been playing with it.
+[936.58 --> 936.98]  Yeah.
+[936.98 --> 938.84]  So, I went ahead and I got it set up.
+[938.84 --> 945.50]  Based on the previous episode where you mentioned WiseBridge, I was able to get WiseBridge set up really quickly.
+[946.30 --> 947.80]  It found my doorbell.
+[947.94 --> 950.50]  It found, you know, all my V3s.
+[950.50 --> 956.88]  And I was able to pipe using RTSP from WiseBridge over into a frigate.
+[957.38 --> 962.32]  It was a little difficult to get set up, mainly because I couldn't read the docs very well.
+[962.40 --> 965.18]  But once I got it up and running, it was pretty good.
+[965.72 --> 970.56]  One thing I would recommend, though, and I know this is pretty crazy, go with the beta.
+[970.82 --> 974.78]  The beta seems to be where the software writer is going.
+[974.78 --> 976.28]  He did a lot of changes.
+[977.60 --> 981.30]  24-7 recording, for example, is now standard in the 9 beta.
+[981.74 --> 988.80]  But the biggest improvement that I saw over 0.8 was GPU acceleration worked, which was huge.
+[989.42 --> 992.32]  You know, obviously, it recommends you have a Coral device.
+[992.62 --> 998.50]  You definitely want a GPU accelerator if you're running a Wise doorbell, because the Wise doorbell comes in at 90 degrees.
+[998.50 --> 1005.86]  So you either rotate it at the WiseBridge, which I don't recommend, doesn't support GPU acceleration, or you do it and frig it.
+[1006.32 --> 1011.50]  So that little adjustment of just 90 degrees is going to eat up your CPU.
+[1012.02 --> 1013.54]  Yeah, that's just what I was going to say, actually.
+[1013.62 --> 1019.26]  You were using the iGPU built into your CPU with QuickSync to do all of that transcoding, right?
+[1019.66 --> 1020.26]  That's correct.
+[1020.26 --> 1028.12]  Yeah, so as I mentioned when I was on the show not too long ago, I purchased the U-NAS from you running an i5-8500T.
+[1028.52 --> 1036.10]  Switching over to the GPU QuickSync, I think my CPUs are at 41, 42C steady, and that's monitoring three cameras.
+[1036.42 --> 1042.40]  So for those that aren't familiar, Frigate is a real-time object detection piece of software.
+[1042.40 --> 1051.94]  It uses the Google TensorFlow library to perform real-time object detection, so it can do stuff like pick out cars, people, bears, dogs, cats.
+[1052.46 --> 1056.34]  And actually, Morgan, you told me the other day that you think it saved your cat's life.
+[1056.62 --> 1058.42]  Yeah, so I have kids.
+[1058.52 --> 1060.08]  I mentioned before on the show that I have kids.
+[1060.54 --> 1065.56]  And the downside of kids is that they're often, you know, they can be careless without realizing it.
+[1066.12 --> 1069.14]  We came back from dinner one night, one of the rare outings, you know.
+[1069.14 --> 1076.58]  We come back in, the kids are messing around outside, they get yelled at to come inside, and somebody doesn't close the front door properly.
+[1077.04 --> 1081.94]  We hear the door open about an hour later from the alarm, somebody goes and shuts it, no big deal.
+[1082.62 --> 1083.84]  Getting ready to go to bed.
+[1084.20 --> 1089.64]  So I quickly grabbed my phone, I looked at Telegram, and I noticed that it said a cat was detected at the doorbell.
+[1090.24 --> 1091.80]  We have a couple stray cats in the neighborhood.
+[1092.16 --> 1095.54]  Didn't think anything of it, but for some reason I decided to look at the video.
+[1095.54 --> 1102.04]  And in the video, I see these two yellow eyes peering out of the bushes, and out comes my 10-month-old cat.
+[1103.06 --> 1104.46]  Babe, wake up, the cat's outside.
+[1104.78 --> 1109.38]  We go outside, we spent 30 minutes looking for the cat, and we find the cat across the street under the Naples car.
+[1110.18 --> 1117.38]  You know, it was, it's pretty crazy to think that home automation and, you know, AI and ML potentially saved my cat's life.
+[1117.82 --> 1120.60]  Right, you had to get it, that was part of it too, is you have to get it in front of your face.
+[1120.60 --> 1123.12]  It's just really kind of a funny, ironic thing.
+[1123.60 --> 1127.42]  I also had a situation with a cat just the other day.
+[1127.76 --> 1134.56]  I decided to put a little Wi-Fi camera under the RV just to watch what was going on while we were parked out in the woods.
+[1135.16 --> 1141.86]  And the morning we were leaving, I checked my camera vents and found out that a cat was living under the RV.
+[1142.38 --> 1146.52]  And I don't know what would have happened if we would have fired up and started rolling because we were packing up and getting ready to go.
+[1146.52 --> 1156.16]  And the cameras and the alert that there was motion down there, in my case it wasn't as nice and fancy as yours, but it alerted me and I thought, you know what, I better check this.
+[1156.22 --> 1159.06]  I don't always check these because anything can set it off really.
+[1159.46 --> 1161.64]  But that one time I thought, I'm going to check that.
+[1162.12 --> 1165.78]  And man was I surprised when I pulled that up and saw a cat.
+[1166.52 --> 1167.08]  Stem away alert.
+[1167.08 --> 1167.56]  You were too.
+[1168.14 --> 1168.44]  Yeah.
+[1168.44 --> 1176.40]  So to talk more about Frigate, one of the things that I would recommend, obviously I mentioned this and the project mentions it as well.
+[1176.52 --> 1178.60]  You definitely want to get a Coral device.
+[1179.42 --> 1181.80]  They do not recommend using CPU for the detection.
+[1182.22 --> 1186.44]  And as I found when I first set it up, it is variant CPU intensive.
+[1186.96 --> 1189.76]  Even with GPU acceleration, you think you still need a Coral?
+[1190.42 --> 1192.20]  Yes, you definitely want to get a Coral.
+[1192.44 --> 1193.92]  The downside is finding them.
+[1193.92 --> 1196.70]  I had to purchase mine off eBay for twice the MSRP.
+[1197.06 --> 1200.72]  That is the reality right now of the supply chain shortages.
+[1201.20 --> 1202.36]  But it's fantastic.
+[1202.62 --> 1203.76]  You plug it in through USB.
+[1203.96 --> 1205.38]  You pass it in through your Docker file.
+[1205.48 --> 1206.42]  It detects it right away.
+[1206.48 --> 1207.80]  And you're good to go.
+[1208.38 --> 1211.00]  Unless you're Alex and it makes your instance crash every time.
+[1211.76 --> 1212.16]  Yeah.
+[1212.60 --> 1217.14]  I've just been trying to run it on a Raspberry Pi 4 I've got just for testing for this episode.
+[1217.68 --> 1219.12]  And I've been having kernel panics.
+[1219.40 --> 1221.42]  So goodness knows what's happening over here.
+[1221.42 --> 1223.90]  But it's not working terribly well for me.
+[1224.00 --> 1226.00]  But I know that you've had some success.
+[1226.12 --> 1227.78]  So why don't you tell us more about it?
+[1228.46 --> 1232.42]  So my doorbell sits on that infamous 45 degree angle.
+[1232.88 --> 1238.48]  You know, I went out and bought the Wise doorbell specifically because of the Wise Bridge that came out.
+[1238.98 --> 1240.26]  And I'm on a corner.
+[1240.26 --> 1245.70]  So I'm able to see two of my neighbor's houses because of the way the house curves.
+[1246.42 --> 1252.18]  And I get alerts from Telegram that says a human, you know, a person has been detected on the doorbell.
+[1252.28 --> 1253.64]  So I, of course, watch the video.
+[1254.12 --> 1261.20]  And I kid you not, all the way across the street, this itty little, bitty little speck of a human being walking their dog.
+[1261.24 --> 1263.40]  So it detects the dog and the person.
+[1264.00 --> 1265.58]  You know, you do have some false negatives.
+[1265.58 --> 1268.34]  Like sometimes it tells me my cat is a dog.
+[1268.54 --> 1271.58]  But in the end of the day, the detection quality of Frigate is really good.
+[1272.28 --> 1279.04]  I have it set up to only retain, you know, to retain one day worth of video since I send all the clips to Telegram.
+[1279.34 --> 1282.32]  I abuse the free Telegram, you know, storage.
+[1282.32 --> 1292.94]  So I think right now with the three cameras, they're all running HD, you know, streamed from Wise Bridge, seven or eight gigs a day and it auto refreshes.
+[1293.24 --> 1295.20]  It really just needs an RTSP feed.
+[1295.34 --> 1298.58]  You use Wise Bridge, but any camera that had RTMP would work.
+[1299.10 --> 1299.38]  Correct.
+[1299.52 --> 1303.96]  So I actually had a brand new Wise V3 sitting in the box.
+[1304.30 --> 1309.62]  I pulled it out, set it up, flashed the new RTSP firmware, and it did work.
+[1309.62 --> 1314.02]  I have not migrated any of the other cameras.
+[1314.14 --> 1315.74]  This one is still sitting on my desk.
+[1315.96 --> 1321.44]  So the idea is I will move all of the V3s over to the RTSP.
+[1321.62 --> 1327.24]  The downside is I don't see the doorbell camera getting RTSP.
+[1327.60 --> 1328.48]  Yeah, I don't think so.
+[1328.58 --> 1330.96]  I also think there may be more of an encoding delay.
+[1331.02 --> 1333.00]  I'm not sure, but I've been testing this.
+[1333.00 --> 1344.74]  It is possible Wise Bridge may actually be faster than running the RTSP firmware directly on the Wise camera because right now with – and I'm very grateful Wise released the RTSP firmware for the V3.
+[1344.84 --> 1345.56]  Thank you, Wise.
+[1345.74 --> 1353.28]  But I'm getting about a two and a half, three second encoding delay when I pull it directly off the camera, whereas with Wise Bridge, it's nearly immediate.
+[1354.14 --> 1354.64]  Correct.
+[1354.82 --> 1357.82]  That is one of the best features, right?
+[1357.82 --> 1359.68]  It detects the cameras.
+[1359.82 --> 1361.26]  You don't have to modify anything.
+[1362.16 --> 1367.40]  But then again, as we all know, that is the inherent fear, how long before they turn it off.
+[1368.04 --> 1370.22]  There are only certain firmwares that are supported.
+[1371.00 --> 1374.12]  The V2s were working and a new firmware came out and then they stopped working.
+[1374.76 --> 1381.98]  And in all honesty, we are at the mercy of Wise, whereas you flash the RTSP, you know, it does work.
+[1381.98 --> 1386.06]  They do have a LAN mode only on the Wise Bridge, which is great.
+[1386.56 --> 1388.50]  But again, you still have to authenticate.
+[1389.26 --> 1393.96]  And I'm pretty sure it's not going to take long before they say this is eating into our money.
+[1394.98 --> 1401.40]  One of the big issues I saw personally, especially with the Wise app, just to talk about how they steal features away from you.
+[1401.90 --> 1405.60]  You used to have the ability to save video clips to your phone.
+[1405.60 --> 1410.82]  And I was trying to save a video clip from the Wise app to send to the wife last night.
+[1411.04 --> 1413.14]  And I realized that I don't have that option anymore.
+[1413.80 --> 1415.22]  Do you have an SD card in the camera?
+[1415.98 --> 1416.34]  No.
+[1416.44 --> 1417.88]  So I don't run the SD cards.
+[1418.70 --> 1422.22]  I actually took all the SD cards out since I'm now using Frigate.
+[1422.26 --> 1422.46]  Right.
+[1422.88 --> 1423.82]  There is that feature.
+[1423.90 --> 1427.00]  You can still do like the playback thing if you have an SD card and that kind of stuff.
+[1427.36 --> 1427.48]  Yeah.
+[1427.56 --> 1430.58]  The question is, how many customers are actually really running the SD card?
+[1431.02 --> 1431.24]  Yeah.
+[1431.30 --> 1432.20]  And it's more expensive too.
+[1432.20 --> 1435.30]  I mean, one of the nice advantages is they're pretty low cost cameras.
+[1435.30 --> 1437.92]  But you had an SD card and you almost doubled the price.
+[1438.66 --> 1441.74]  You mentioned briefly that you're not using the Home Assistant integration.
+[1442.08 --> 1446.90]  But I got to be honest with you, Morgan, that seems like that's why I would want to use Frigate.
+[1446.96 --> 1452.92]  Because it creates sensor entities and camera entities and switch entities in Home Assistant for me.
+[1452.98 --> 1459.78]  And it uses Home Assistant's media browser to show me the still clips from motion from the camera feeds that it detects.
+[1459.78 --> 1464.04]  Like the Home Assistant integration seems like the perfect aspect of this.
+[1464.08 --> 1466.22]  But you said, no, I don't actually like it.
+[1466.28 --> 1467.08]  Was it not working well?
+[1467.12 --> 1467.66]  What happened there?
+[1468.00 --> 1469.34]  Well, it's not that I didn't like it.
+[1469.42 --> 1472.06]  It was the version it was using was the stable version.
+[1472.80 --> 1475.98]  You didn't have the option to use whenever I set it up.
+[1476.00 --> 1476.88]  And I'll be honest with you.
+[1477.24 --> 1478.26]  I'm like a lot of people.
+[1478.26 --> 1480.04]  So it's working right now.
+[1480.12 --> 1483.20]  So I haven't revisited it because it works.
+[1483.72 --> 1486.82]  But at the time, .9 was still in beta.
+[1487.18 --> 1494.84]  And when you did the 8, when you installed the Home Assistant, when you installed the Home Assistant integration, .8 was the only one that was there.
+[1495.00 --> 1500.54]  And again, the .8 was not working for me at all with GPU acceleration.
+[1500.74 --> 1501.88]  And that was definitely a need.
+[1501.88 --> 1504.10]  The features were great.
+[1504.24 --> 1506.12]  It was super easy to set up Telegram.
+[1506.98 --> 1510.98]  You know, whenever you had the Home Assistant integration, it was easy to set up Telegram.
+[1511.88 --> 1519.38]  But definitely when he gets .9 or he gets the 1.0 release up and running, use the Home Assistant integration.
+[1519.60 --> 1530.80]  But for right now, if it currently doesn't support .9, the beta, you know, you want to get some of these extra features, the 24-7 recording, the GPU acceleration.
+[1530.80 --> 1534.52]  And you're definitely going to have to look at doing it outside and Docker Compose separately.
+[1535.00 --> 1544.36]  And then it sounds like to really make it sing, getting one of those Google Coral devices to do the specific machine learning required for the quick object identification.
+[1544.56 --> 1545.96]  That's really the cherry on top.
+[1546.28 --> 1546.66]  It is.
+[1546.82 --> 1550.02]  So that thing is like a machine learning AI.
+[1550.72 --> 1551.12]  I don't know.
+[1551.16 --> 1556.04]  It's about the size of two fingers, like next to each other, like a very small candy bar or something.
+[1556.96 --> 1560.16]  And this thing is, it's pretty cool if you think about it.
+[1560.16 --> 1563.38]  It's basically a machine learning chip on a USB stick.
+[1563.86 --> 1565.02]  It's essentially what it is.
+[1565.14 --> 1567.74]  And it just accelerated everything.
+[1567.88 --> 1572.90]  Like Morgan said, the CPU usage just disappeared when we plugged this thing in.
+[1573.00 --> 1573.72]  It was pretty incredible.
+[1574.24 --> 1578.24]  It makes me really appreciate the impact of dedicated silicon.
+[1578.24 --> 1587.34]  So like when I look at the Apple silicon announcement this week, and they're talking about the dedicated ProRes encoding circuitry that's in their new CPUs.
+[1587.52 --> 1589.16]  It's a similar thing here, right?
+[1589.22 --> 1591.74]  We're kind of entering a new era in computing.
+[1591.90 --> 1600.96]  We're kind of leaving the general purpose CPU only stuff behind and moving into sort of more ASIC dedicated hardware territory.
+[1600.96 --> 1604.20]  And it's very impressive what this little thing can do.
+[1604.20 --> 1609.10]  So one last update before I go, and Alex will truly enjoy this.
+[1609.56 --> 1611.34]  I have the worst luck possible.
+[1611.96 --> 1616.16]  I always wait until the last minute and say, okay, let me just go ahead and buy this.
+[1616.64 --> 1619.44]  I buy it, and a month later, they come out with a new version.
+[1620.14 --> 1621.96]  Wyze just announced the new Doorbell Pro.
+[1622.54 --> 1623.14]  It's bigger.
+[1623.14 --> 1627.02]  It has the higher, the fisheye, and I really like it.
+[1627.42 --> 1632.84]  And I'm probably going to buy it, which means I'll be back to then review that doorbell.
+[1633.24 --> 1634.48]  And I'll take the doorbell.
+[1635.40 --> 1636.08]  Very good.
+[1636.16 --> 1637.20]  That's the doorbell guy.
+[1637.60 --> 1638.24]  You see?
+[1638.62 --> 1638.92]  Good.
+[1639.16 --> 1639.94]  It's just how it works.
+[1641.50 --> 1647.22]  Well, we'll also have links to Morgan's create configs in the show notes, too, if anybody out there needs a few pointers.
+[1647.32 --> 1648.56]  Thanks for sharing those with us, Morgan.
+[1648.92 --> 1649.44]  Yeah, definitely.
+[1649.64 --> 1651.14]  And thanks for having me back on the show, guys.
+[1651.16 --> 1651.80]  It's always fun.
+[1651.80 --> 1656.18]  And maybe I'll come back with a different review that isn't a doorbell.
+[1656.50 --> 1657.30]  Nah, not interested.
+[1657.66 --> 1658.32]  Not interested.
+[1658.94 --> 1660.54]  Only interested in doorbell reviews.
+[1664.90 --> 1666.88]  Backblaze.com slash SSH.
+[1666.94 --> 1670.74]  Go there to get a free trial, no credit card required, and start backing things up.
+[1670.78 --> 1672.90]  This is also the way I go for all my friends and family.
+[1672.98 --> 1674.70]  For people that ask me, Chris, how should I back up?
+[1675.82 --> 1677.48]  Don't fuss with all the details.
+[1677.88 --> 1680.72]  Don't mess with all the different crazy plans out there from all the different providers.
+[1680.72 --> 1682.36]  Just focus on Backblaze.
+[1682.50 --> 1683.54]  This is what they do.
+[1683.62 --> 1685.06]  And you know them for storage.
+[1685.34 --> 1687.24]  And they have an awesome deal for you.
+[1687.74 --> 1691.80]  Unlimited computer backup for Macs and PCs for just $7 a month.
+[1692.22 --> 1693.44]  This is incredible.
+[1693.60 --> 1698.60]  And I just gave this to my mom, too, to get all of her documents backed up off her old Mac and her music and all of her photos.
+[1698.60 --> 1702.14]  She only had that stuff on, like, spread out external drives.
+[1702.30 --> 1703.82]  It was just no good.
+[1704.26 --> 1709.18]  And, you know, if she ever has any problems, she can restore files from anywhere using the web or a mobile app.
+[1709.64 --> 1711.84]  And, you know, my mom is also a graphic artist.
+[1711.94 --> 1715.98]  So some of her Photoshop files are huge, ginormous.
+[1715.98 --> 1722.36]  Not only does Backblaze have no problem with that, but if you ever need to restore, like, a big chunk, they'll let you restore by mail.
+[1722.72 --> 1723.26]  Snail mail.
+[1723.58 --> 1725.62]  You can purchase a disk from them and restore.
+[1725.94 --> 1728.86]  They'll restore everything you need right to that, and you can use that to restore at home.
+[1729.26 --> 1731.32]  And then you can send it back to them for a refund.
+[1732.34 --> 1733.30]  How great is that?
+[1733.84 --> 1734.80]  I think that's pretty nice.
+[1734.80 --> 1745.84]  And, you know, if mom's ever worried about maybe deleting files and she wants to go back a few revisions with her Photoshop projects, which this is actually something that has happened to her in the past, for $2 a month, she's good to go.
+[1745.94 --> 1748.16]  And I like that, too, for myself for, like, business documents.
+[1748.28 --> 1748.86]  I think that's great.
+[1748.92 --> 1750.26]  You get retention for up to a year.
+[1750.92 --> 1752.74]  And the mobile apps are really well done.
+[1753.38 --> 1757.34]  And Backblaze has proven it for 50 billion files that have been restored with their customers.
+[1757.44 --> 1758.38]  I mean, you know Backblaze.
+[1758.48 --> 1759.54]  You know they're good for this.
+[1759.88 --> 1760.94]  This is what they do.
+[1761.22 --> 1762.90]  But you've been waiting for a great opportunity.
+[1762.90 --> 1770.94]  Now you can support the show and get a fully featured, no credit card required trial by going to Backblaze.com slash SSH.
+[1771.04 --> 1771.22]  Yep.
+[1771.82 --> 1773.94]  Visit Backblaze.com slash SSH.
+[1774.00 --> 1776.94]  That way they know you came from the show and you support us and all of that.
+[1777.24 --> 1781.24]  And you'll get a free 15-day trial at Backblaze.com slash SSH.
+[1781.40 --> 1786.14]  Go there, play around with it, and start protecting your data, your friends' data, and your family's data.
+[1786.52 --> 1788.44]  Start today and take advantage of that free trial.
+[1788.82 --> 1791.02]  Backblaze.com slash SSH.
+[1792.90 --> 1794.28]  The Linux Trucker writes in,
+[1794.36 --> 1797.68]  I was listening to your last episode and heard you talking about Wall Panel.
+[1798.16 --> 1800.82]  Although it's great software, I feel there's a better option.
+[1801.08 --> 1809.82]  The fully kiosk browser does everything that Wall Panel does, including motion detection, auto launch, and it will even function with the home button on Android.
+[1809.82 --> 1817.06]  There's a very small $5 fee to unlock all of the features, but I don't mind supporting great software that I use every single day.
+[1817.88 --> 1825.40]  Now, I was looking into this as part of the research for this episode and noticed that there's been an announcement around Wall Panel, Chris, right?
+[1825.40 --> 1825.50]  Indeed.
+[1826.02 --> 1826.42]  Indeed.
+[1826.62 --> 1832.06]  And, yes, Wall Panel is great software, but it seems that it's just recently had a maintainer change.
+[1832.52 --> 1838.62]  One of those kind of classic open source situations, if you will, where the maintainer kind of came up and said,
+[1838.86 --> 1840.14]  gosh, I think I'm done.
+[1840.36 --> 1842.10]  After all these years, I think I'm burned out.
+[1842.10 --> 1848.14]  Somebody stepped up right away, and we'll have the new GitHub for that in the show notes.
+[1848.20 --> 1849.40]  It now has a new maintainer.
+[1849.88 --> 1857.36]  But it looks like, also, if you were a user of the Alarm MQTT project that's a similar project that helps, you know,
+[1857.44 --> 1863.06]  you set up alarm panels with your own home automation system, that's still looking for a maintainer.
+[1863.12 --> 1864.44]  That was another one of his projects.
+[1864.78 --> 1869.38]  So perhaps, you know, it's worth keeping an eye on Wall Panel for a little while and see where it goes.
+[1869.38 --> 1874.92]  I love it because it's in the Amazon App Store and the Google Play Store and other places, of course.
+[1875.26 --> 1880.52]  But being in the Amazon App Store means that you can go pick up a Fire tablet when they're on cheap sales
+[1880.52 --> 1884.96]  and just, you know, toss that app on there via their App Store, and you're good to go.
+[1885.16 --> 1889.34]  But it seems like maybe Fully Kiosk Browser is a pretty good contender and worth looking into.
+[1889.42 --> 1890.38]  So I'll give that a try soon.
+[1891.14 --> 1896.10]  Yeah, when we stop using our Fire tablet as a baby monitor, I'm going to put the Fully Kiosk Browser on that.
+[1896.48 --> 1899.32]  Remember I put Lineage on that tablet a little while ago?
+[1899.64 --> 1900.60]  It's been super solid.
+[1901.00 --> 1904.26]  We just leave it plugged in all the time because the battery is completely knackered anyway.
+[1905.04 --> 1907.86]  And we just use it as a Wyze Cam baby monitor.
+[1908.34 --> 1909.66]  You know, we can pull it up on our phones.
+[1909.84 --> 1910.74]  It's really useful.
+[1911.36 --> 1914.20]  The one thing that Wall Panel does, and I'd be curious to see if Kiosk does this,
+[1914.54 --> 1918.76]  Wall Panel communicates back to Home Assistant over MQTT, which is really nice,
+[1918.76 --> 1925.58]  and also can turn the front-facing or rear camera into a camera that you can feed into Home Assistant.
+[1925.84 --> 1926.60]  Oh, okay.
+[1927.34 --> 1928.26]  That's pretty legit.
+[1928.60 --> 1929.32]  That's pretty cool.
+[1929.48 --> 1935.18]  It is nice because it turns every tablet into a camera that's feeding Home Assistant.
+[1935.64 --> 1936.26]  I love that.
+[1936.32 --> 1940.26]  But I have to say, so I've bought a lot of these Fire tablets, probably half a dozen.
+[1941.00 --> 1943.46]  And thrown half of them in the sink as well, I might add.
+[1943.46 --> 1945.58]  Yeah, there was that.
+[1946.06 --> 1948.76]  Because, you know, I have some here at the studio and I have some at home.
+[1949.08 --> 1954.24]  And this most recent one I got, which I think is like a 7-inch or something like that, I can't remember.
+[1955.14 --> 1957.06]  And I've had another 7-inch or 4 from them.
+[1957.24 --> 1959.14]  It crashes almost every day.
+[1960.10 --> 1961.16]  It's a piece of garbage.
+[1961.34 --> 1964.26]  So sometimes these, so maybe if I did put Lineage on there, it'd be in better shape.
+[1964.34 --> 1966.04]  I think it's the OS and all that crap.
+[1966.04 --> 1971.34]  And the fact that it acts as an echo, I think also, which I thought would be neat.
+[1971.72 --> 1975.14]  I thought that'd be neat, but it's too slow and leggy.
+[1975.58 --> 1979.62]  I saw this going around online, Alex, and I think you already have the solution for it.
+[1979.66 --> 1981.64]  But I don't know if we've ever mentioned it on the air.
+[1981.84 --> 1983.40]  So I thought this would be an opportunity.
+[1983.40 --> 1993.36]  Essentially, and we all have been through this, a self-hoster goes through a lot of effort to set up a beautiful Plex library.
+[1993.60 --> 1999.60]  In this particular case, he has 8,000 movies, curated movies in his Plex library.
+[2000.12 --> 2001.76]  Everything's beautifully set up.
+[2002.38 --> 2003.76]  All of the art's working.
+[2004.48 --> 2009.04]  Gigabit Ethernet from the video player back to the NAS that has everything on it.
+[2009.04 --> 2013.86]  But when the wife sits down on the couch, she goes to Netflix every single time.
+[2014.58 --> 2018.96]  And so he said, OK, so I'm just curious, you know, what is it about Netflix that you like more?
+[2019.06 --> 2024.96]  And she tells him that she likes that Netflix kind of just tells her this is what's trendy right now.
+[2025.58 --> 2026.82]  You'll probably like these.
+[2027.10 --> 2029.88]  And there's too much choice when she's using Plex.
+[2030.10 --> 2034.46]  And he wanted to know if there was a way to create her a curated experience.
+[2034.46 --> 2038.22]  Now, you and I happen to share Plex instances, and I've been on your server.
+[2038.22 --> 2044.70]  And I know that you really have taken or at least put some effort into curating collections.
+[2044.70 --> 2048.16]  And you can go to your collection screen and you have collections of everything.
+[2048.26 --> 2049.52]  And it looks like you automated that.
+[2049.56 --> 2056.66]  And I thought that'd probably be the solution for this individual who's trying to come up with a way to curate the experience for family members.
+[2057.36 --> 2058.32]  Collections for days, bro.
+[2058.52 --> 2059.68]  Yeah, I've got loads of them.
+[2060.00 --> 2061.00]  Yeah, you do.
+[2061.14 --> 2063.44]  I use this thing called Plex Meta Manager.
+[2063.78 --> 2065.16]  I'll put a link to it in the show notes.
+[2065.16 --> 2066.72]  It's a Python script.
+[2067.00 --> 2071.90]  And this thing basically just runs through your Plex library using the Plex API.
+[2072.52 --> 2080.08]  Looks at the different TMDB IDs, IMDB IDs, and creates collections based on those IDs.
+[2080.76 --> 2085.78]  And the really nice thing about this is it has a whole bunch of predetermined collections.
+[2085.78 --> 2088.98]  So if I go to my movies right now, I've got a popular section.
+[2090.00 --> 2093.66]  And in there, it looks at what's popular on IMDB, for example.
+[2094.24 --> 2100.10]  And right now, I look at my top four on here, and I've got the Tomorrow War, Mortal Kombat, The Matrix.
+[2100.50 --> 2104.80]  I guess a lot of people are catching up on The Matrix ahead of the version four coming out.
+[2104.94 --> 2105.80]  And The Wrath of Man.
+[2105.80 --> 2112.68]  I didn't have to do anything to create this collection except set up Plex Meta Manager in the first place.
+[2113.06 --> 2116.88]  I've got an Ansible role that I use to do this linked in the show notes as well.
+[2117.26 --> 2120.52]  And essentially, all it does is it puts a couple of config files in YAML,
+[2120.98 --> 2125.02]  and I can set up collections based on stuff that I want.
+[2125.08 --> 2127.68]  So I want a bunch of collections based on decades, say.
+[2128.30 --> 2130.50]  I've got that set up in my config file.
+[2130.50 --> 2136.26]  But honestly, the defaults it comes with, you've got popular, top-rated Oscars,
+[2136.40 --> 2139.46]  and then it starts doing things like by studio, by actor,
+[2140.04 --> 2144.74]  all sorts of different filters, basically, that it creates these collections with.
+[2145.04 --> 2146.28]  That's exactly what he needs.
+[2146.52 --> 2149.14]  And that's actually something I think I want to take advantage of, too,
+[2149.18 --> 2152.98]  because I've done a few manual collections, and I just don't keep up with it.
+[2153.38 --> 2154.78]  It's a pain to keep up with, absolutely.
+[2155.32 --> 2158.34]  Now, this script, I have it set on a cron job to run every night.
+[2158.34 --> 2161.42]  And let me just go and look in my health checks instance,
+[2161.54 --> 2164.36]  because I've started monitoring how long it takes these jobs to run.
+[2164.80 --> 2166.22]  Ah, a nice metric.
+[2166.44 --> 2170.10]  Plex Meta Manager, it takes, on average, let me have a look,
+[2170.46 --> 2175.78]  anywhere from an hour to the longest, I think was the first one,
+[2175.82 --> 2177.18]  was about four hours to run.
+[2177.72 --> 2179.64]  So it's something you want to set up to run overnight,
+[2179.74 --> 2182.66]  because it will churn through your library every single time it does it.
+[2183.02 --> 2186.08]  And if you have a lot of content, obviously that could take a while.
+[2186.08 --> 2188.82]  So just be aware of that.
+[2188.94 --> 2192.10]  But yeah, I mean, looking at the average time here, it's about an hour for me,
+[2192.12 --> 2194.50]  and I've got about a thousand movies in my collection.
+[2194.72 --> 2196.26]  So just be aware of that.
+[2196.90 --> 2199.30]  Also, just a note, people have been writing in and letting us know,
+[2199.38 --> 2202.16]  and we also saw after we recorded last week's episode,
+[2202.16 --> 2204.18]  we mentioned that there was a big change in the way
+[2204.18 --> 2206.32]  2U devices were handled with Home Assistant.
+[2206.88 --> 2208.40]  And it seems like for a lot of people,
+[2208.42 --> 2210.50]  when they're upgrading to the October release,
+[2210.96 --> 2213.12]  the 2021 October release of Home Assistant,
+[2213.64 --> 2214.86]  it's nuking their 2U setups.
+[2214.86 --> 2218.26]  So if you're a 2U user, be careful.
+[2218.42 --> 2219.60]  Make sure you got your backups.
+[2220.12 --> 2222.84]  They have moved over to an official built-in integration,
+[2223.12 --> 2224.58]  but it's cloud only.
+[2225.04 --> 2226.98]  And so it's a common thread,
+[2227.28 --> 2229.52]  and I hate this because this has happened to me too,
+[2229.94 --> 2232.34]  is people were just going along, they hit the update button,
+[2233.20 --> 2235.88]  and all of their local 2U control was wiped out.
+[2236.22 --> 2238.30]  And man, have I been there when something like that's happened.
+[2238.40 --> 2240.90]  I just recently tried to do the Z-Wave migration myself,
+[2240.90 --> 2243.50]  and that was a dumpster fire.
+[2243.50 --> 2246.02]  I had to restore from backup and just get out of there.
+[2246.10 --> 2250.72]  And I have just determined I am sticking with the old Z-Wave integration
+[2250.72 --> 2251.94]  for as long as possible,
+[2251.94 --> 2255.68]  and I'm going to hope to just switch to Matter sometime next year.
+[2255.82 --> 2258.10]  And then I went online, Alex, and I looked it up,
+[2258.10 --> 2263.72]  and man, people said they were spending like 6 days fixing their setups
+[2263.72 --> 2266.76]  after they migrated to the new Z-Wave JS integration.
+[2267.02 --> 2267.76]  I love Home Assistant.
+[2268.38 --> 2271.28]  You all know this, and it is a universal truth in my life.
+[2271.84 --> 2275.16]  But it feels to me a lot like Alex as a teenager.
+[2275.48 --> 2277.38]  I used to come along to my parents and say,
+[2277.72 --> 2280.50]  I've got this cool idea about how you can make your life easier.
+[2280.50 --> 2282.16]  All you do is this.
+[2282.28 --> 2283.38]  You just do this.
+[2283.48 --> 2284.44]  You just do that.
+[2284.66 --> 2288.46]  And I kind of feel like Home Assistant is in that kind of adolescent phase
+[2288.46 --> 2293.62]  at the moment where you just need to do this migration just this once,
+[2293.64 --> 2295.12]  and then it will just be fine.
+[2295.28 --> 2298.50]  And six days later, you're just still picking up the pieces.
+[2298.72 --> 2299.34]  You know, it's...
+[2299.34 --> 2300.06]  Yeah.
+[2300.20 --> 2302.32]  Sometimes I understand it's a necessary evil,
+[2302.48 --> 2307.58]  but also I do think we need to be careful somehow as a community.
+[2308.16 --> 2309.52]  I don't know what the solution is,
+[2309.78 --> 2311.60]  because if people don't maintain the old stuff,
+[2311.68 --> 2312.96]  we've got to move to new stuff, right?
+[2313.34 --> 2314.64]  Yeah, it's tricky too with open source,
+[2314.74 --> 2317.00]  because, you know, you only have so many contributors
+[2317.00 --> 2318.18]  and they only have so much time.
+[2318.32 --> 2319.40]  And yeah, I do get it.
+[2319.44 --> 2321.64]  And I am actually just grateful they've kept the old integration
+[2321.64 --> 2323.30]  working for as long as it does,
+[2323.38 --> 2325.50]  and I'm hopeful it makes it until next year,
+[2325.50 --> 2326.94]  because that's when I'll probably switch over.
+[2327.54 --> 2328.92]  And there were plenty of resources,
+[2329.16 --> 2331.98]  but you have to have a few people that take a dive and try it
+[2331.98 --> 2333.54]  and report back on how it goes.
+[2333.96 --> 2336.24]  And maybe if you've got any success stories, let us know.
+[2336.24 --> 2337.78]  In fact, we love all of your stories,
+[2338.26 --> 2340.34]  your war stories, your success stories,
+[2340.46 --> 2341.90]  and your questions and suggestions
+[2341.90 --> 2344.46]  at selfhosted.show slash contact.
+[2345.04 --> 2348.22]  And of course, a big thank you to our site reliability engineers,
+[2348.44 --> 2349.18]  our subscribers.
+[2349.36 --> 2353.06]  You make this show possible over at selfhosted.show slash SRE.
+[2353.88 --> 2355.26]  Every single episode,
+[2355.52 --> 2360.16]  we do a little bit of shenanigans in the post show for our subscribers.
+[2360.42 --> 2364.22]  We talk about cars, barbecue, all sorts of stuff.
+[2364.22 --> 2366.06]  Selfhosted.show slash SRE.
+[2366.18 --> 2367.26]  Go find Alex on Twitter.
+[2367.44 --> 2368.52]  He's at Ironic Badger.
+[2368.62 --> 2369.58]  I'm at Chris LAS.
+[2369.78 --> 2372.70]  And the show for like, you know, events, news, stuff like that,
+[2372.82 --> 2374.00]  at selfhosted show.
+[2374.14 --> 2375.64]  And the network is at Jupyter Signal.
+[2376.16 --> 2377.02]  Thanks for listening, everybody.
+[2377.32 --> 2379.74]  That was selfhosted.show slash 56.
+[2379.74 --> 2380.66]  1066.
+[2380.66 --> 2380.84]  1066.
+[2380.84 --> 2381.10]  11 spun.
+[2381.10 --> 2381.30]  1666.
+[2381.30 --> 2381.52]  1666.
+[2381.52 --> 2381.70]  1666.
+[2381.70 --> 2381.72]  1766.
+[2381.72 --> 2383.54]  1786.
+[2383.54 --> 2384.04]  17 Sims 5.
+[2384.04 --> 2384.44]  1766.
+[2384.44 --> 2385.88]  1776.
+[2385.88 --> 2386.34]  1766.
+[2386.34 --> 2386.88]  18 vase siguiente.
+[2386.88 --> 2387.08]  185.
+[2387.08 --> 2387.52]  1729.
+[2387.52 --> 2388.18]  1865.
+[2388.18 --> 2388.54]  1836.
+[2389.06 --> 2389.98]  1865.
+[2390.02 --> 2390.08]  1877.
+[2390.08 --> 2390.62]  17 tuleg.
+[2390.62 --> 2390.98]  1936.
+[2391.28 --> 2391.36]  1875.
+[2391.36 --> 2392.04]  2064.
+[2392.06 --> 2392.50]  2060.
+[2392.50 --> 2393.44]  19 Uma.
+[2393.44 --> 2393.48]  1916.
+[2393.48 --> 2393.92]  2060.
+[2394.32 --> 2394.38]  2273.
+[2394.42 --> 2394.50]  2064.
+[2394.50 --> 2395.06]  2040.
+[2395.06 --> 2395.22]  21.
+[2395.40 --> 2396.16]  28,,
+[2396.16 --> 2396.46]  2615.
+[2396.58 --> 2397.44]  1936.
+[2397.44 --> 2398.34]  2260.
+[2398.34 --> 2398.90]  2160.
+[2398.90 --> 2399.42]  2260.
+[2399.42 --> 2400.46]  2160.
+[2400.46 --> 2401.38]  2160.
+[2401.38 --> 2402.26]  2165.
+[2402.46 --> 2402.50]  2190.
+[2402.50 --> 2403.56]  2160.
+[2403.56 --> 2404.30]  2260.
+[2404.30 --> 2405.48]  2260.

57： Alex Deletes it All _summary.txt

@@ -0,0 +1,73 @@
+• Refrigerator's compressor kicking in
+• Garage freezer's defrost issue
+• Temperature sensor idea for monitoring fridge temperature
+• Wife suggests using a temperature sensor with Home Assistant
+• Installing Akara sensors using Zigbee protocol
+• Testing battery life of Akara sensors at -17°C
+• Concerns about DIY solutions for fridge repairs due to RV constraints
+• Using an ESP board to simplify smart home setup
+• Eliminating the Hue hub from Philips Hue lights
+• Troubleshooting a low-range issue with a Sonoff CC2531 Zigbee stick
+• Repurposing existing Philips Hue bulbs as mesh repeaters for improved range
+• Ordering a Con B version 2 device as an alternative solution
+• Experiencing delays on Z-Wave network due to added devices and limited bandwidth
+• Discussion of the Sigma Design's Z-Wave USB adapter
+• Overloading network concerns with 14 Z-Wave nodes
+• Matters' potential benefits, including increased bandwidth and support from vendors like Amazon
+• Skepticism about Matter's impact and likelihood of success
+• Comparison of Matter to USB as a standard for IoT devices
+• Discussion of shucking external drives during Black Friday sales
+• The bathtub curve phenomenon in hard drive failure rates
+• Mitigating drive failures by purchasing multiple drives at once and staggering upgrades
+• Setting a budget for new drives ($200 per unit) and considering factors like ZFS mirroring and SnapRaid parity requirements
+• Concerns about buying "shucked" (already opened) drives from retailers, including warranty claims and potential cost savings
+• Speculation that manufacturers may be selling lower-quality or QA-affected drives in retail packaging to avoid warranty issues
+• Discussion about drives with QA testing failures being used as replacement parts
+• Personal anecdotal evidence suggesting these drives do not lead to less reliable disks
+• Comparison of costs between shucked drives and commercial ones, including warranty differences
+• Mention of custom power connectors for SATA drives and the impact on reliability
+• Advertisement for a Linux Web Services course at A Cloud Guru
+• Discussion about rebuilding servers with new drives and planning upgrades
+• The speaker had issues with their motherboard's PCIe slots, particularly the fourth slot, which caused bifurcation to fail
+• They discovered that when something is plugged into the fourth slot, the first slot's speed changes from 16x to 8x
+• This was not indicated by any lights or warnings and required reading the manual and understanding the chipset layout
+• The speaker believes this is an edge case but a bug in the BIOS or PCIe routing issue on their motherboard
+• They speculate that the manufacturer "cheaped out" on PCIe lanes, which is a concern for server-grade motherboards
+• As a result, they had to downgrade from a ZFS mirror with two terabyte NVMe drives to a single drive
+• Discussion of a backup test that highlighted the importance of having both on-site and off-site backups
+• Restoration time comparison between LAN and off-site restoration
+• The consequences of not having up-to-date backups, including lost data and system downtime
+• A personal anecdote about accidentally wiping out a ZFS pool and losing several months' worth of IRC history
+• Discussion of the ease of restoring from Google Drive using Proxmox and proxmox's Google drive backup plugin
+• Promotion of Backblaze.com for secure cloud backups.
+• Restore from anywhere feature with Backblaze
+• Obsidian documentation app and its features
+• Comparison of Obsidian with Notion and other note-taking apps
+• Discussion of data ownership and security in cloud-based services
+• Review of LogSec, a similar app to Obsidian
+• Joplin's file naming system and its limitations
+• Author's experience with Notion for sharing notes and collaborating with others
+• Using Obsidian with mkdocs and a continuous integration build system
+• Connecting Obsidian to Drone CI and GitT
+• Creating a self-hosted wiki using mkdocs
+• Integrating plugins in mkdocs for linking and backlinking
+• Using Obsidian as a long-term wiki solution
+• Replicating the pipeline for off-grid use
+• Comparing Obsidian to other note-taking apps, including TiddlyWiki and Emacs
+• Exploring the community plug-in ecosystem around Obsidian
+• Discussing the pricing model and free personal use option
+• Linode hosting and promotions
+• New Home Assistant release with significant changes and contributions
+• Frank's dedication to user experience and troubleshooting efforts
+• Update on Tuya integration issues and their resolution in the new release
+• Link sharing feature for devices within Home Assistant
+• Features added to Home Assistant include the ability to add custom icons to entries and support for WebRTC video streams
+• The Amber device has been funded with over 2,500 backers and is a prototype of a hardware component for Home Assistant
+• Next month's release will be the State of the Union on December 11th at 11 a.m. Pacific time
+• Entity screens have been reorganized in the latest update
+• Improvements have been made to the automatically generated Lovelace dashboard
+• Discussion of a software update affecting the auto-generated dashboard layout
+• Problem with incorrect ink levels reported for an HP OfficeJet Pro printer
+• Gratitude expressed towards site reliability engineers (SREs) who support the show
+• Upcoming post-show discussion about Starlink for a listener's father's potential new home
+• Call to email or contact the show with feedback and project ideas