add all 2021 summaries

35： The Perfect Media Server _summary.txt

@@ -1,92 +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
+• 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

36： Google Docs Replacement _summary.txt

@@ -1,49 +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
+• 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

37： Security Growing Pains _summary.txt

@@ -1,60 +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
+• 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

38： Crouching Pi, Hidden Server _summary.txt

@@ -1,54 +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
+• 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

39： We run Arch BTW _summary.txt

@@ -1,76 +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)
+• 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)

40： Password Shaming _summary.txt

@@ -1,62 +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
+• 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)

41： The One with Jeff Geerling _summary.txt

@@ -1,45 +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
+• 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.

42： Don't Panic _summary.txt

@@ -1,53 +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
+• 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

43： A New Solution for Backups _summary.txt

@@ -1,77 +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
+• 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

44： Plex Skeptics _summary.txt

@@ -1,62 +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
+• 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

45： The Future of Home Assistant _summary.txt

@@ -1,55 +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
+• 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

46： Pastebin Alternative _summary.txt

@@ -1,67 +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
+• 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

47： Whose License Is It Anyway？ _summary.txt

@@ -1,62 +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
+• 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

48： A Solution Looking for a Problem _summary.txt

@@ -1,47 +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
+• 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.

49： Update Roulette _summary.txt

@@ -1,68 +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
+• 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

50： Perfect Plex Setup _summary.txt

@@ -1,66 +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
+• 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.

51： Apple's Rotten Scanning _summary.txt

@@ -1,77 +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.
+• 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.

52： Navigating DeGoogling _summary.txt

@@ -1,99 +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
+• 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

53： Adventurous Build _summary.txt

@@ -1,52 +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
+• 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

54： Ultimate Off-Site Setup _summary.txt

@@ -1,65 +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)
+• 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

55： Home Assistant Turns Amber _summary.txt

@@ -1,87 +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
+• 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

56： Feeling Wyze _summary.txt

@@ -1,75 +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
+• 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

57： Alex Deletes it All _summary.txt

@@ -1,73 +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
+• 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

58： Pi Server Upgrade _summary.txt

@@ -1,82 +1,82 @@
-• The Prusa XL is a large 3D printer with a build volume of 14 inches square, exceeding the standard size dictated by the Prusa Mark III
-• The Prusa XL uses a Core XY design, where the extruder moves and the bed remains stationary
-• The printer features five interchangeable tool heads and starts at a price of $2,000
-• Alex discusses the challenges of making money with 3D printing, including the cost of materials and time
-• A new router for the studio is needed that supports WireGuard, prompting a discussion about a Raspberry Pi compute module powered router
-• The discussed board has two gigabit ethernet interfaces but requires custom configuration due to USB-connected interface limitations
-• The speaker had issues with an SD card on a device, finding it frustrating to use due to its placement.
-• They tried using OpenWrt but found a GitHub thread warning against using stock OpenWrt with certain router boards.
-• Instead, they downloaded a custom build of OpenWrt from Seed Studios' wiki and installed it successfully.
-• The speaker was interested in the Raspberry Pi compute module for running a server due to its eMMC storage option, which is more reliable than an SD card.
-• They had issues flashing the eMMC with a pre-built image, requiring manual jumper settings and driver installation.
-• The speaker chose to use OpenSUSE Tumbleweed's ISO image instead, booting it from a USB drive and installing it to the eMMC without any issues.
-• The install process was slow due to package checks and hardware scanning, but the final result was successful.
-• The speaker did some benchmarking on the eMMC and found its performance to be mediocre (80-200 MB/s).
-• Comparison with spinning hard drives and NVMe slots
-• Limitations in performance due to thermals (heat)
-• Alternative solutions such as external USB SSDs
-• Possibility of using an IO board with a PCI-1X express slot
-• Discussion of thermal throttling and potential fixes (e.g. heat sinks, cases with fans)
-• Network transfer performance tests
-• Discussion about a Raspberry Pi setup and potential upgrades with the compute module
-• Comparison of power draw between current Pi setup and the new compute module
-• Dual network ports and additional IO capabilities on the compute module
-• Availability of various operating systems (Arch, Fedora, Alma Linux, CentOS, RHEL, Ubuntu) for ARM64 ISO image
-• Future implications for Raspberry Pi 5 and potential need for esoteric builds
-• Mention of another board with NICs on PCI bus and its potential for server platform building
-• Discussion about the compute module's compact size and versatility with breakout boards
-• Recommendation to check out Seed Studio website for compute module availability
-• Advertising for Linode.com and its services, including $100 in 60-day credit for new accounts
-• The speaker discusses their positive experience with Linode, a cloud hosting platform, mentioning its speed and affordability.
-• They highlight the benefits of using Linode, including control over their account and excellent customer support.
-• The speaker invites listeners to try out Linode's $100 free trial offer.
-• The conversation shifts to the speaker's frustrations with Android 12 on their Pixel 6 phone, citing issues with UI, fingerprint reader, and call screening.
-• They praise Google Assistant's built-in call screening feature, but criticize the lack of similar functionality for users outside of the US.
-• The speaker also discusses a new outbound "on-hold" mode in Google Assistant, which provides text-based transcription of phone calls.
-• They express dissatisfaction with Android 12 and mention their efforts to de-Google services, including switching from Google Maps.
-• Apple's right to repair and parts availability
-• Customizing devices and personal preferences for customization
-• Comparing Apple's stance on privacy, specifically tracking
-• Discussion of the trade-offs with Apple's policies (e.g. library scanning)
-• Importance of modularity in device design
-• Author's own experiences with Android devices and their desire to customize
-• Separating work and personal apps on a phone
-• Customizing alerts and icons in iOS
-• Fingerprint readers, including issues with the Pixel 6 and OnePlus devices
-• Android 12 and its Material U interface redesign
-• Notification center toggle swipe down features and customization options
-• The speaker discusses their frustration with Android's user interface changes and how they are becoming more complicated.
-• The speaker compares iOS to Android and notes that iOS is changing in a direction towards a control center with multiple options, whereas Android is simplifying its UI.
-• The speaker questions the idea of designing for "new users" and notes that Google frequently changes the layout and features of their OS, making it difficult for new users to adapt.
-• The speaker shares their experience with family members who are more competent in using iOS than Android, despite having used both platforms over time.
-• The speaker expresses their desire for a stable and consistent user interface that doesn't change or become cluttered.
-• The speaker notes that people generally don't like radical changes to their software or hardware, citing examples of users reacting negatively to new features and designs.
-• Android and iOS user experiences
-• Web apps accessible across multiple platforms
-• Sideloaded app issues with Apple devices
-• Sponsor Block YouTube extension on Android
-• Integration of Home Assistant with iOS HomeKit system
-• Control and automation possibilities through Home Assistant and iOS integration
-• Developer's achievement in creating a great iOS Home Assistant app
-• iOS is considered superior to Android for automations with HomeKit devices
-• The speaker thinks Android with Home Assistant has significant issues and limitations
-• There's room for a third player to disrupt the mobile OS space
-• The speaker considers switching to an iPhone due to its camera capabilities
-• Backblaze is promoted as a secure cloud backup service, offering unlimited storage for $7/month
-• The show discusses listener feedback about Home Assistant's 100,000 users participating in analytics
-• Discussion of using Frigate with Home Assistant for camera integration and object detection
-• Feedback from listener Brandon on his experience with Frigate and suggestions for custom models
-• Mention of Double Take app for facial recognition in Home Assistant and potential for vehicle detection model
-• Plan to explore custom models in a live stream with the author of Double Take
-• Explanation of double-natting (two network address translated networks) and its implications on network setup and security
-• Wireless ISPs often use private IP addresses for cost savings
-• This can lead to "double-natting" issues, where software like VPNs struggle to connect
-• Tailscale is a solution that helps with double-natting by hosting a witness node and facilitating peer-to-peer connections
-• Nebula is an alternative that offers full control and trustworthiness, but may be more complex
-• Double-natting is common on cell networks, mobile networks, and satellite internet
-• Tailscale's ease of use and simplicity make it a preferred choice for some users
-• Sponsorship of the podcast was mentioned
-• Invitation for audience feedback and project submissions on selfhost.show/contact
-• A Cloud Guru sponsorship and social media presence
-• Upcoming live stream event with site reliability engineers (SRE)
+• The Prusa XL is a large 3D printer with a build volume of 14 inches square, exceeding the standard size dictated by the Prusa Mark III
+• The Prusa XL uses a Core XY design, where the extruder moves and the bed remains stationary
+• The printer features five interchangeable tool heads and starts at a price of $2,000
+• Alex discusses the challenges of making money with 3D printing, including the cost of materials and time
+• A new router for the studio is needed that supports WireGuard, prompting a discussion about a Raspberry Pi compute module powered router
+• The discussed board has two gigabit ethernet interfaces but requires custom configuration due to USB-connected interface limitations
+• The speaker had issues with an SD card on a device, finding it frustrating to use due to its placement.
+• They tried using OpenWrt but found a GitHub thread warning against using stock OpenWrt with certain router boards.
+• Instead, they downloaded a custom build of OpenWrt from Seed Studios' wiki and installed it successfully.
+• The speaker was interested in the Raspberry Pi compute module for running a server due to its eMMC storage option, which is more reliable than an SD card.
+• They had issues flashing the eMMC with a pre-built image, requiring manual jumper settings and driver installation.
+• The speaker chose to use OpenSUSE Tumbleweed's ISO image instead, booting it from a USB drive and installing it to the eMMC without any issues.
+• The install process was slow due to package checks and hardware scanning, but the final result was successful.
+• The speaker did some benchmarking on the eMMC and found its performance to be mediocre (80-200 MB/s).
+• Comparison with spinning hard drives and NVMe slots
+• Limitations in performance due to thermals (heat)
+• Alternative solutions such as external USB SSDs
+• Possibility of using an IO board with a PCI-1X express slot
+• Discussion of thermal throttling and potential fixes (e.g. heat sinks, cases with fans)
+• Network transfer performance tests
+• Discussion about a Raspberry Pi setup and potential upgrades with the compute module
+• Comparison of power draw between current Pi setup and the new compute module
+• Dual network ports and additional IO capabilities on the compute module
+• Availability of various operating systems (Arch, Fedora, Alma Linux, CentOS, RHEL, Ubuntu) for ARM64 ISO image
+• Future implications for Raspberry Pi 5 and potential need for esoteric builds
+• Mention of another board with NICs on PCI bus and its potential for server platform building
+• Discussion about the compute module's compact size and versatility with breakout boards
+• Recommendation to check out Seed Studio website for compute module availability
+• Advertising for Linode.com and its services, including $100 in 60-day credit for new accounts
+• The speaker discusses their positive experience with Linode, a cloud hosting platform, mentioning its speed and affordability.
+• They highlight the benefits of using Linode, including control over their account and excellent customer support.
+• The speaker invites listeners to try out Linode's $100 free trial offer.
+• The conversation shifts to the speaker's frustrations with Android 12 on their Pixel 6 phone, citing issues with UI, fingerprint reader, and call screening.
+• They praise Google Assistant's built-in call screening feature, but criticize the lack of similar functionality for users outside of the US.
+• The speaker also discusses a new outbound "on-hold" mode in Google Assistant, which provides text-based transcription of phone calls.
+• They express dissatisfaction with Android 12 and mention their efforts to de-Google services, including switching from Google Maps.
+• Apple's right to repair and parts availability
+• Customizing devices and personal preferences for customization
+• Comparing Apple's stance on privacy, specifically tracking
+• Discussion of the trade-offs with Apple's policies (e.g. library scanning)
+• Importance of modularity in device design
+• Author's own experiences with Android devices and their desire to customize
+• Separating work and personal apps on a phone
+• Customizing alerts and icons in iOS
+• Fingerprint readers, including issues with the Pixel 6 and OnePlus devices
+• Android 12 and its Material U interface redesign
+• Notification center toggle swipe down features and customization options
+• The speaker discusses their frustration with Android's user interface changes and how they are becoming more complicated.
+• The speaker compares iOS to Android and notes that iOS is changing in a direction towards a control center with multiple options, whereas Android is simplifying its UI.
+• The speaker questions the idea of designing for "new users" and notes that Google frequently changes the layout and features of their OS, making it difficult for new users to adapt.
+• The speaker shares their experience with family members who are more competent in using iOS than Android, despite having used both platforms over time.
+• The speaker expresses their desire for a stable and consistent user interface that doesn't change or become cluttered.
+• The speaker notes that people generally don't like radical changes to their software or hardware, citing examples of users reacting negatively to new features and designs.
+• Android and iOS user experiences
+• Web apps accessible across multiple platforms
+• Sideloaded app issues with Apple devices
+• Sponsor Block YouTube extension on Android
+• Integration of Home Assistant with iOS HomeKit system
+• Control and automation possibilities through Home Assistant and iOS integration
+• Developer's achievement in creating a great iOS Home Assistant app
+• iOS is considered superior to Android for automations with HomeKit devices
+• The speaker thinks Android with Home Assistant has significant issues and limitations
+• There's room for a third player to disrupt the mobile OS space
+• The speaker considers switching to an iPhone due to its camera capabilities
+• Backblaze is promoted as a secure cloud backup service, offering unlimited storage for $7/month
+• The show discusses listener feedback about Home Assistant's 100,000 users participating in analytics
+• Discussion of using Frigate with Home Assistant for camera integration and object detection
+• Feedback from listener Brandon on his experience with Frigate and suggestions for custom models
+• Mention of Double Take app for facial recognition in Home Assistant and potential for vehicle detection model
+• Plan to explore custom models in a live stream with the author of Double Take
+• Explanation of double-natting (two network address translated networks) and its implications on network setup and security
+• Wireless ISPs often use private IP addresses for cost savings
+• This can lead to "double-natting" issues, where software like VPNs struggle to connect
+• Tailscale is a solution that helps with double-natting by hosting a witness node and facilitating peer-to-peer connections
+• Nebula is an alternative that offers full control and trustworthiness, but may be more complex
+• Double-natting is common on cell networks, mobile networks, and satellite internet
+• Tailscale's ease of use and simplicity make it a preferred choice for some users
+• Sponsorship of the podcast was mentioned
+• Invitation for audience feedback and project submissions on selfhost.show/contact
+• A Cloud Guru sponsorship and social media presence
+• Upcoming live stream event with site reliability engineers (SRE)
 • Discussion of a new microphone for the live stream event

59： I Tried to Love Portainer _summary.txt

@@ -1,90 +1,90 @@
-• The speaker has made a life decision to move away from suburbia and potentially buy land in the Appalachians.
-• They've decided to buy an RV to facilitate this move, allowing them to explore potential properties without needing hotels or other accommodations.
-• The RV will also provide a mobile workspace with internet connectivity, enabling remote work.
-• They're planning for a medium-sized Class C RV or camper van.
-• They're aware of the benefits of having a solid internet connection and are considering using Starlink.
-• Discussion of Starlink internet and its USB Ethernet capabilities
-• Managing multiple internet connections with a single router
-• Use of Dishy's built-in features, including DHCP relay and modem functions
-• Comparison between self-hosted services and company-hosted services
-• Use of ZFS for remote replication and disk management
-• Use of Tailscale for secure access to servers and devices
-• Self-hosted server issues with Juice SSH and HedgeDoc
-• Importance of monitoring and alerting systems
-• Consideration of switching to object storage for backend data
-• Discussion of matrix protocol and its decentralized, federated nature
-• Author's experience with self-hosted services, including Matrix server setup issues
-• Logo image issue causing display problems for some users
-• Need for software to handle resizing images automatically
-• Difficulty with storing and managing large amounts of data (images, videos, chat logs)
-• Frequent updates required for Synapse server
-• Challenges with self-hosting Matrix instance compared to Discord or Slack
-• Recommendation to limit public access and encourage users to sign up at Matrix.org
-• Matrix server deployment decision and its implications
-• Discord as a compromise over self-hosted options
-• Production infrastructure outage and maintenance responsibilities
-• Jellyfin alternative to Plex, with positive review and recommendation
-• Linode cloud hosting sponsorship and service benefits
-• Linode's new storage, MVME, is a game-changer for high-performance applications
-• Benefits of MVME include higher IOPS per gigabyte than traditional storage
-• Linode's data centers and customer support are highlighted as advantages for users
-• The speaker praises Linode's system updates and package caching capabilities
-• Portainer, a Docker GUI, is introduced and its features and uses are discussed
-• Discussion of Portainer management instance
-• Number of containers and applications being managed (30-40)
-• Challenges with staying on top of updates for internal software
-• User's experience with Portainer: frustration, tediousness, and restrictive features
-• Comparison to Docker Swarm: more complicated and restrictive
-• Paid version of Portainer vs. community edition
-• Historical issue with company's templates being featured in Portainer
-• Docker GUIs add complexity
-• Users should manage container definitions in a version-controlled Git repository
-• Current solutions (e.g. Portainer) don't offer much value beyond what can be done manually
-• Some tools (e.g. OpenSense, Compose) are solving the wrong problem or offering unnecessary complexity
-• The speaker has successfully implemented Portainer on a Raspberry Pi and is impressed with its simplicity
-• However, the speaker suggests that spending time learning configuration management tools like Git and Ansible could be more beneficial
-• The speaker shares an example of using Ansible to generate Docker Compose YAML files for multiple servers
-• They emphasize the power of configuration management in automating repetitive tasks and reducing the need to think about specific settings for each server
-• Discussion about GUIs and non-repeatable UX flows
-• Promotion of Backblaze.com for cloud backup services
-• Features and benefits of using Backblaze, including web restore, app restore, and restore by mail programs
-• Mobile app for accessing files securely in the cloud
-• Statistics on number of files restored for Backblaze customers
-• Trial offer for a fully featured account with no credit card required
-• Another GUI (Lazy Docker) mentioned briefly
-• LazyDocker GUI interface is available on Mac, Windows, Linux, and can be installed via curl
-• The GUI provides an overview of running services, containers, images, and volumes in a NCURSIS style clickable interface
-• Users can interact with the GUI using mouse or keyboard, and perform tasks such as viewing config information, Docker compose files, process information, and logs
-• LazyDocker was praised for its ability to quickly identify issues, such as containers restarting constantly, without needing to actively check logs or investigate further
-• The GUI is seen as a useful tool for getting an overview of system status and identifying potential problems, particularly in cases where there is limited time to explore the system.
-• The speaker talks about using Lazy Docker to reconnect with a container
-• Docker stats command for viewing container information and resource usage
-• Analyzing container performance and identifying memory hogs, specifically Java applications
-• Using Docker Compose to limit RAM usage of specific containers (e.g. BookSonic)
-• Discussion of a master process that opens a port on behalf of a service and leaves the service stopped until a connection is received
-• Need for similar functionality for Docker containers to save resources
-• Examples of projects where containers are running 24/7 unnecessarily
-• Mention of Dazzle.dev, a real-time Docker container log viewer in the browser
-• Overview of Dazzle.dev's features and security considerations
-• The speaker is discussing their experience with the log search function of an application.
-• They mention using Dozzle to search through logs and finding useful real-time search functionality.
-• Docker Compose is changing from a standalone Python thing to being inside Docker itself.
-• Existing Docker Compose commands will map to new Docker Compose commands, but with a different invocation (Docker space-Compose).
-• The change is largely tech debt being addressed by bringing the separate project in-house.
-• There may be some small changes to the Docker Compose spec and backwards compatibility issues.
-• Tech debt release with minimal new features for normal users
-• Developers are excited about the tech debt release
-• Docker Compose is a key feature that made it click for the speaker
-• The ability to visualize infrastructure and application dependencies in plain text using Docker Compose files
-• Docker Compose has become an official part of the main Docker app, with support in other tools like Podman
-• Docker Compose V2 profiles allow addressing multiple services within a single file
-• Profiles can be used to categorize containers, such as test or prod environments
-• New feature in Docker Compose V2 allows listing different stacks and their containers
-• User wrote a blog post about the new features and linked it in the show notes
-• Upcoming live stream will cover building an ESP-based device with ESP Home
-• Plans to hang out with members and update on tech progress
-• Promise to have more information by the end of 2021
-• Discussion of goals and Alex's goal
-• Instructions for sending feedback through self-hosted.show/contact
-• Contact information for podcast creators (Twitter handles)
+• The speaker has made a life decision to move away from suburbia and potentially buy land in the Appalachians.
+• They've decided to buy an RV to facilitate this move, allowing them to explore potential properties without needing hotels or other accommodations.
+• The RV will also provide a mobile workspace with internet connectivity, enabling remote work.
+• They're planning for a medium-sized Class C RV or camper van.
+• They're aware of the benefits of having a solid internet connection and are considering using Starlink.
+• Discussion of Starlink internet and its USB Ethernet capabilities
+• Managing multiple internet connections with a single router
+• Use of Dishy's built-in features, including DHCP relay and modem functions
+• Comparison between self-hosted services and company-hosted services
+• Use of ZFS for remote replication and disk management
+• Use of Tailscale for secure access to servers and devices
+• Self-hosted server issues with Juice SSH and HedgeDoc
+• Importance of monitoring and alerting systems
+• Consideration of switching to object storage for backend data
+• Discussion of matrix protocol and its decentralized, federated nature
+• Author's experience with self-hosted services, including Matrix server setup issues
+• Logo image issue causing display problems for some users
+• Need for software to handle resizing images automatically
+• Difficulty with storing and managing large amounts of data (images, videos, chat logs)
+• Frequent updates required for Synapse server
+• Challenges with self-hosting Matrix instance compared to Discord or Slack
+• Recommendation to limit public access and encourage users to sign up at Matrix.org
+• Matrix server deployment decision and its implications
+• Discord as a compromise over self-hosted options
+• Production infrastructure outage and maintenance responsibilities
+• Jellyfin alternative to Plex, with positive review and recommendation
+• Linode cloud hosting sponsorship and service benefits
+• Linode's new storage, MVME, is a game-changer for high-performance applications
+• Benefits of MVME include higher IOPS per gigabyte than traditional storage
+• Linode's data centers and customer support are highlighted as advantages for users
+• The speaker praises Linode's system updates and package caching capabilities
+• Portainer, a Docker GUI, is introduced and its features and uses are discussed
+• Discussion of Portainer management instance
+• Number of containers and applications being managed (30-40)
+• Challenges with staying on top of updates for internal software
+• User's experience with Portainer: frustration, tediousness, and restrictive features
+• Comparison to Docker Swarm: more complicated and restrictive
+• Paid version of Portainer vs. community edition
+• Historical issue with company's templates being featured in Portainer
+• Docker GUIs add complexity
+• Users should manage container definitions in a version-controlled Git repository
+• Current solutions (e.g. Portainer) don't offer much value beyond what can be done manually
+• Some tools (e.g. OpenSense, Compose) are solving the wrong problem or offering unnecessary complexity
+• The speaker has successfully implemented Portainer on a Raspberry Pi and is impressed with its simplicity
+• However, the speaker suggests that spending time learning configuration management tools like Git and Ansible could be more beneficial
+• The speaker shares an example of using Ansible to generate Docker Compose YAML files for multiple servers
+• They emphasize the power of configuration management in automating repetitive tasks and reducing the need to think about specific settings for each server
+• Discussion about GUIs and non-repeatable UX flows
+• Promotion of Backblaze.com for cloud backup services
+• Features and benefits of using Backblaze, including web restore, app restore, and restore by mail programs
+• Mobile app for accessing files securely in the cloud
+• Statistics on number of files restored for Backblaze customers
+• Trial offer for a fully featured account with no credit card required
+• Another GUI (Lazy Docker) mentioned briefly
+• LazyDocker GUI interface is available on Mac, Windows, Linux, and can be installed via curl
+• The GUI provides an overview of running services, containers, images, and volumes in a NCURSIS style clickable interface
+• Users can interact with the GUI using mouse or keyboard, and perform tasks such as viewing config information, Docker compose files, process information, and logs
+• LazyDocker was praised for its ability to quickly identify issues, such as containers restarting constantly, without needing to actively check logs or investigate further
+• The GUI is seen as a useful tool for getting an overview of system status and identifying potential problems, particularly in cases where there is limited time to explore the system.
+• The speaker talks about using Lazy Docker to reconnect with a container
+• Docker stats command for viewing container information and resource usage
+• Analyzing container performance and identifying memory hogs, specifically Java applications
+• Using Docker Compose to limit RAM usage of specific containers (e.g. BookSonic)
+• Discussion of a master process that opens a port on behalf of a service and leaves the service stopped until a connection is received
+• Need for similar functionality for Docker containers to save resources
+• Examples of projects where containers are running 24/7 unnecessarily
+• Mention of Dazzle.dev, a real-time Docker container log viewer in the browser
+• Overview of Dazzle.dev's features and security considerations
+• The speaker is discussing their experience with the log search function of an application.
+• They mention using Dozzle to search through logs and finding useful real-time search functionality.
+• Docker Compose is changing from a standalone Python thing to being inside Docker itself.
+• Existing Docker Compose commands will map to new Docker Compose commands, but with a different invocation (Docker space-Compose).
+• The change is largely tech debt being addressed by bringing the separate project in-house.
+• There may be some small changes to the Docker Compose spec and backwards compatibility issues.
+• Tech debt release with minimal new features for normal users
+• Developers are excited about the tech debt release
+• Docker Compose is a key feature that made it click for the speaker
+• The ability to visualize infrastructure and application dependencies in plain text using Docker Compose files
+• Docker Compose has become an official part of the main Docker app, with support in other tools like Podman
+• Docker Compose V2 profiles allow addressing multiple services within a single file
+• Profiles can be used to categorize containers, such as test or prod environments
+• New feature in Docker Compose V2 allows listing different stacks and their containers
+• User wrote a blog post about the new features and linked it in the show notes
+• Upcoming live stream will cover building an ESP-based device with ESP Home
+• Plans to hang out with members and update on tech progress
+• Promise to have more information by the end of 2021
+• Discussion of goals and Alex's goal
+• Instructions for sending feedback through self-hosted.show/contact
+• Contact information for podcast creators (Twitter handles)
 • Self-deprecation about plugging Twitter and consideration of discontinuing it

60： Someone Else's Computer _summary.txt

@@ -1,87 +1,87 @@
-• Congratulatory tone towards Sir Lewis Hamilton's eighth World Drivers title
-• Criticism of Formula One management for "shenanigans" and "corrupt" behavior
-• Discussion of Amazon Web Services (AWS) outage and its impact on various services
-• Analysis of the "butterfly effect" of AWS outage on smart home users
-• Comparison of sports (Formula One and FIFA) with technology outages (AWS)
-• Critique of Amazon's response to the outage, particularly their status page
-• Discussion of unrelated API outage affecting WISE devices
-• Amazon's Route 53 DNS service is based out of a single US East 1 location
-• Single points of failure can impact availability even with highly available systems
-• Dependence on cloud services like Amazon, Cloudflare, and Google creates centralized internet issues
-• Homogenization of the internet leads to single points of failure and decreased decentralization
-• Architecting for high availability is challenging when relying on cloud services
-• TCP/IP's design allows for decentralized routing around failures, but this has been largely ignored in favor of convenience and quality of service
-• Decentralization and self-hosting are being explored as alternatives to reduce dependence on centralized services
-• The use of IPFS and other decentralized technologies is becoming more prevalent
-• Discusses internet bandwidth management, preferring to use LAN for less critical tasks
-• Mentions a log4j vulnerability in Java and its potential impact on remote code execution
-• Notes that Linuxserver.io has posted an info notice about the vulnerability
-• Warns users who self-host with Unify controller about its vulnerability and recommends updating
-• Advises listeners using Airsonic to be aware of its current vulnerability
-• Shares personal anecdote about internet outages when self-hosting
-• Discusses finding a website change detection app called ChangeDetection.io
-• Monitoring and notification service features
-• COVID UK government page monitoring example
-• Apprise integration for push notifications
-• Linode hosting and infrastructure security
-• Deckbot testimonial about Linode's performance
-• Minecraft server setup on Linode
-• New Home Assistant update (2021.12)
-• State of the stream project live stream event
-• Virtual reality meetings using Oculus Quest 2
-• Discussion of VR technology being faster due to lower latency and data transfer
-• Idea of using VR for podcasting, including potential hardware requirements and costs
-• Mention of the Home Assistant Yellow device, previously known as Amber, and its availability for order
-• Comments on current tech shortages and supply chain issues, citing specific examples such as graphics cards and diesel exhaust fluid
-• Discussion of repurposing old PCs and finding creative ways to reuse technology instead of buying new equipment
-• The speaker's home systems and servers use eighth gen Intel CPUs for consistency
-• Upgrading to newer CPU generations may not be worth it due to relatively small performance differences
-• PCIe gen 4 is a slight change but doesn't significantly impact daily experience
-• Apple M1 Mac Mini is of interest as a potential home server, with low power consumption
-• The speaker uses older gear for home systems and servers, including a Raspberry Pi, and has recently upgraded Home Assistant on their Blue device
-• Home Assistant OS snapshot functionality
-• Concerns about updating potentially harming Z-Wave controller or network
-• New configuration panel and button entity features
-• Integration of local users who can only log in from the local network
-• Jellyfin integration with music support (potential for future video support)
-• Hue integration updated to support API version 2
-• Pie Hole integration update
-• ESP home project updates, including easier flashing process
-• The host mentions issues with automations at their studio and decides to wait before upgrading their RV system.
-• A listener asks about naming conventions for Home Assistant automations, and the hosts discuss different approaches.
-• One of the hosts shares their own experience trying various naming schemes, including grouping by type or location.
-• Another listener asks how to approach a company about building a Home Assistant integration based on their API.
-• The hosts discuss possible approaches, including contacting the company for permission versus releasing an open-source library.
-• The government can issue cease and desist letters for publicly available API data
-• Companies may not understand that public APIs are intended to be accessed by anyone
-• Responsible disclosure is a better approach than posting findings on social media first
-• Some companies have been contacted about integrating their products with Home Assistant, but progress has been slow
-• Examples of companies that could benefit from Home Assistant integration include Victron and Portainer
-• Portainer provides benefits for discovering containers and access control in Docker environments
-• Discussing the value of Portainer for managing containers
-• OpenShift as a hybrid cloud solution for presenting a cohesive single pane of glass across different clouds
-• Using GUIs, bash aliases, and documentation to solve container management problems
-• Exploring alternative solutions like K3S, a lightweight Kubernetes system, for on-premise and cloud systems
-• Discussing the need for centralized management of JB core services and access control
-• Mentioning Backblaze as an unlimited computer backup solution
-• Backblaze was promoted as a cloud backup service with a free trial
-• A listener shared a science fiction analogy for self-hosting, describing it as rescuing captives from proprietary platforms
-• The host discussed his reasons for hosting Matrix on his own infrastructure, citing independence and control
-• Charles wrote in with the idea of discussing self-hosting Git versus using cloud services like GitHub or GitLab
-• Guest mentions using GitT for notes and struggling with time management as a parent.
-• Discussion of infrastructure as code, including the benefits of treating servers as cattle rather than pets.
-• Recommendation of resources for learning Ansible, such as Jeff Geerling's YouTube series and Keith Morris' book "Infrastructure as Code".
-• Host explains their personal approach to infrastructure as code, focusing on saving time and documenting infrastructure for future deployments.
-• Debate about whether servers should be treated as pets or cattle, with pros and cons of each approach discussed.
-• January 2nd meetup at the studio
-• Trial of Get Together as a meetup alternative
-• New server christening party on January 2nd (tentative)
-• Network-wide membership launch, including ad-free option for Linux Action News
-• How to access member feeds and customize subscriptions
-• Membership benefits and features
-• Contact information: self-hosted.show/contact, Discord (self-hosted.show/Discord), Matrix room on colony.jupyterbroadcasting.com
-• Stopping Twitter plugs due to Jack's departure
-• Discussing personal use of Twitter vs liking it
-• Seeking old hardware for benchmarking article
-• Connection made through Twitter with listener
+• Congratulatory tone towards Sir Lewis Hamilton's eighth World Drivers title
+• Criticism of Formula One management for "shenanigans" and "corrupt" behavior
+• Discussion of Amazon Web Services (AWS) outage and its impact on various services
+• Analysis of the "butterfly effect" of AWS outage on smart home users
+• Comparison of sports (Formula One and FIFA) with technology outages (AWS)
+• Critique of Amazon's response to the outage, particularly their status page
+• Discussion of unrelated API outage affecting WISE devices
+• Amazon's Route 53 DNS service is based out of a single US East 1 location
+• Single points of failure can impact availability even with highly available systems
+• Dependence on cloud services like Amazon, Cloudflare, and Google creates centralized internet issues
+• Homogenization of the internet leads to single points of failure and decreased decentralization
+• Architecting for high availability is challenging when relying on cloud services
+• TCP/IP's design allows for decentralized routing around failures, but this has been largely ignored in favor of convenience and quality of service
+• Decentralization and self-hosting are being explored as alternatives to reduce dependence on centralized services
+• The use of IPFS and other decentralized technologies is becoming more prevalent
+• Discusses internet bandwidth management, preferring to use LAN for less critical tasks
+• Mentions a log4j vulnerability in Java and its potential impact on remote code execution
+• Notes that Linuxserver.io has posted an info notice about the vulnerability
+• Warns users who self-host with Unify controller about its vulnerability and recommends updating
+• Advises listeners using Airsonic to be aware of its current vulnerability
+• Shares personal anecdote about internet outages when self-hosting
+• Discusses finding a website change detection app called ChangeDetection.io
+• Monitoring and notification service features
+• COVID UK government page monitoring example
+• Apprise integration for push notifications
+• Linode hosting and infrastructure security
+• Deckbot testimonial about Linode's performance
+• Minecraft server setup on Linode
+• New Home Assistant update (2021.12)
+• State of the stream project live stream event
+• Virtual reality meetings using Oculus Quest 2
+• Discussion of VR technology being faster due to lower latency and data transfer
+• Idea of using VR for podcasting, including potential hardware requirements and costs
+• Mention of the Home Assistant Yellow device, previously known as Amber, and its availability for order
+• Comments on current tech shortages and supply chain issues, citing specific examples such as graphics cards and diesel exhaust fluid
+• Discussion of repurposing old PCs and finding creative ways to reuse technology instead of buying new equipment
+• The speaker's home systems and servers use eighth gen Intel CPUs for consistency
+• Upgrading to newer CPU generations may not be worth it due to relatively small performance differences
+• PCIe gen 4 is a slight change but doesn't significantly impact daily experience
+• Apple M1 Mac Mini is of interest as a potential home server, with low power consumption
+• The speaker uses older gear for home systems and servers, including a Raspberry Pi, and has recently upgraded Home Assistant on their Blue device
+• Home Assistant OS snapshot functionality
+• Concerns about updating potentially harming Z-Wave controller or network
+• New configuration panel and button entity features
+• Integration of local users who can only log in from the local network
+• Jellyfin integration with music support (potential for future video support)
+• Hue integration updated to support API version 2
+• Pie Hole integration update
+• ESP home project updates, including easier flashing process
+• The host mentions issues with automations at their studio and decides to wait before upgrading their RV system.
+• A listener asks about naming conventions for Home Assistant automations, and the hosts discuss different approaches.
+• One of the hosts shares their own experience trying various naming schemes, including grouping by type or location.
+• Another listener asks how to approach a company about building a Home Assistant integration based on their API.
+• The hosts discuss possible approaches, including contacting the company for permission versus releasing an open-source library.
+• The government can issue cease and desist letters for publicly available API data
+• Companies may not understand that public APIs are intended to be accessed by anyone
+• Responsible disclosure is a better approach than posting findings on social media first
+• Some companies have been contacted about integrating their products with Home Assistant, but progress has been slow
+• Examples of companies that could benefit from Home Assistant integration include Victron and Portainer
+• Portainer provides benefits for discovering containers and access control in Docker environments
+• Discussing the value of Portainer for managing containers
+• OpenShift as a hybrid cloud solution for presenting a cohesive single pane of glass across different clouds
+• Using GUIs, bash aliases, and documentation to solve container management problems
+• Exploring alternative solutions like K3S, a lightweight Kubernetes system, for on-premise and cloud systems
+• Discussing the need for centralized management of JB core services and access control
+• Mentioning Backblaze as an unlimited computer backup solution
+• Backblaze was promoted as a cloud backup service with a free trial
+• A listener shared a science fiction analogy for self-hosting, describing it as rescuing captives from proprietary platforms
+• The host discussed his reasons for hosting Matrix on his own infrastructure, citing independence and control
+• Charles wrote in with the idea of discussing self-hosting Git versus using cloud services like GitHub or GitLab
+• Guest mentions using GitT for notes and struggling with time management as a parent.
+• Discussion of infrastructure as code, including the benefits of treating servers as cattle rather than pets.
+• Recommendation of resources for learning Ansible, such as Jeff Geerling's YouTube series and Keith Morris' book "Infrastructure as Code".
+• Host explains their personal approach to infrastructure as code, focusing on saving time and documenting infrastructure for future deployments.
+• Debate about whether servers should be treated as pets or cattle, with pros and cons of each approach discussed.
+• January 2nd meetup at the studio
+• Trial of Get Together as a meetup alternative
+• New server christening party on January 2nd (tentative)
+• Network-wide membership launch, including ad-free option for Linux Action News
+• How to access member feeds and customize subscriptions
+• Membership benefits and features
+• Contact information: self-hosted.show/contact, Discord (self-hosted.show/Discord), Matrix room on colony.jupyterbroadcasting.com
+• Stopping Twitter plugs due to Jack's departure
+• Discussing personal use of Twitter vs liking it
+• Seeking old hardware for benchmarking article
+• Connection made through Twitter with listener
 • Alternate contact methods: Twitter (@ironicbadger), Matrix, Telegram channel (jupiterbroadcasting.com/Telegram)

61： That First Layer Squish _summary.txt

@@ -1,71 +1,71 @@
-• Introduction to a special episode on 3D printing with guests Cheese and Drew
-• Backgrounds of guests: Cheese works for System76 in marketing, Drew works for Community College System handling high-end IT needs
-• Overview of guests' experiences with 3D printing: Drew is a beginner who recently purchased his first printer, Cheese has been printing for about 2 years and wants to expand his capabilities
-• Discussion on what is 3D printing (FDM or fused deposition modeling) and how it works
-• Basic premise of 3D printing involves using G-code to control movement of nozzle to form layers of plastic
-• Limitations of 3D printing include layer-by-layer construction and inability to print certain shapes with overhangs without support
-• First layer adhesion is a major issue in 3D printing, especially when using exotic filaments
-• Temperature control and environment are crucial factors affecting 3D printing success
-• Different types of filaments have unique characteristics, such as PLA being beginner-friendly but brittle and prone to warping in warm environments
-• The speaker created custom cup holders for a friend's above-ground pool
-• They used PETG filament to print the cup holders due to its heat-resistant properties
-• PETG is a hybrid material that combines the best of PLA and ABS, but can be finicky to work with
-• It requires higher temperatures (up to 250°C) than PLA to flow well and can stick to glass beds
-• Manufacturer-specific settings and calibration may be necessary for optimal results
-• Slicers like Cura and Prusa Slicer are used to convert 3D models into G-code that guides the printer's nozzle
-• Different slicers have varying capabilities, but Prusa Slicer is specifically optimized for Prusa printers
-• The effects of humidity on PETG filament at different altitudes
-• Using Cura settings and adjusting them for better results
-• Storing filaments to prevent absorption of moisture from the air
-• Experiences with PLA and PETG filaments in Colorado vs Texas
-• Introduction to Octoprint, a software for controlling 3D printers remotely
-• Discussion of plugins available for Octoprint, such as webcam monitoring and cost estimation tools
-• Octoprint and its uses for Raspberry Pi and 3D printing
-• Linode's cloud hosting and benefits for R&D and project setup
-• Comparison of direct drive and Bowden tube extruders for flexible filaments like TPU
-• Overview of entry-level filaments (PLA, PETG, TPU) and considerations for beginners
-• Advertisement for Linode's services and promotions
-• Linode's service is mentioned as a reliable and improving option for hosting projects.
-• The discussion turns to 3D printing, with the topic of whether an enclosure is needed.
-• Factors influencing the need for an enclosure include containing heat and environmental variables in the area where the printer will be used.
-• Personal experience shared about using an enclosure to prevent pet hair interference with prints.
-• Enclosures can also help with temperature control for certain plastics like ABS.
-• Various uses for an enclosure beyond just dust, noise, and fume control are mentioned.
-• The discussion shifts to sharing and discussing different 3D printers and upgrades each person has made.
-• Drew shares their experience upgrading parts on the Ender 3 Pro, including replacing the hot end and switching from a Bowden tube setup to direct drive.
-• Auto bed leveling is also discussed as a valuable upgrade that helps improve print quality.
-• The speaker upgraded their Ender 3 Pro printer with various components
-• They mention buying a Nozzle X and replacing the cheap brass nozzles
-• The total cost of upgrades is under $500
-• The speaker compares their experience with an entry-level 3D printer (Ender) to a high-end one (Prusa i3 Mark III)
-• They discuss the benefits of building a Prusa, including learning about electronics and 3D printing capabilities
-• The speaker values the turnkey experience of the Prusa, which comes with extensive documentation and customer support
-• Prusa's open-source approach to hardware designs
-• Comparison of Prusa and Creality's business practices
-• Open-source movement in 3D printing industry
-• Ender 3 from Creality being open-sourced due to public pressure
-• Benefits of auto bed leveling and direct drive extruder in Prusa printers
-• Importance of accurate and true hardware components
-• Upgrades to the Ender 3 Pro printer significantly reduced noise levels
-• Printers are used for various projects, including cases and stands for household items, musical instruments, and electronics
-• The speakers discuss their journey with 3D printing, from basic prints to designing and selling objects through their stores
-• They mention using microcontrollers and other technologies in conjunction with 3D printing
-• The hobby of 3D printing can be addictive, drawing people into designing and creating their own items instead of just buying them
-• Printers are used for baby-proofing the house, making corner protectors and outlet prong protectors.
-• The Prusa XL printer is a large format machine with automatic extruder tool head changes and multiple filament loading capabilities.
-• It has a significantly larger build volume than the standard Prusa printer and comes at a higher price point, starting at $2,000.
-• The Prusa XL features a new bed technology that includes segmented beds with cooling and expansion channels to reduce warping of prints.
-• Discussion on weighing filament before printing, with some users relying on their printer's filament runout sensor or a manual "cross and clench" method.
-• Use cases for the Prusa XL's multiple extruder feature, including printing different materials and dissolvable filaments.
-• Discussion of modifying spools of filament by fusing and filing them
-• Comparison of safety between using isopropyl alcohol vs. glue stick on print bed
-• Importance of regular printer maintenance, such as cleaning the nozzle and bed
-• Frequency of maintenance needed for printers, depending on usage
-• Various methods for wiping down the print bed after use
-• Discussion of a past experience or project
-• Recommendation to use high-quality glue stick for DIY upgrades
-• Introduction and thank-yous from guests and host
-• Promotion of network membership at Jupiter.party and selfhosted.show/sre
-• Details about the benefits of network membership, including ad-free content and behind-the-scenes material
-• Explanation of how network membership funding allows for picky sponsor selection
+• Introduction to a special episode on 3D printing with guests Cheese and Drew
+• Backgrounds of guests: Cheese works for System76 in marketing, Drew works for Community College System handling high-end IT needs
+• Overview of guests' experiences with 3D printing: Drew is a beginner who recently purchased his first printer, Cheese has been printing for about 2 years and wants to expand his capabilities
+• Discussion on what is 3D printing (FDM or fused deposition modeling) and how it works
+• Basic premise of 3D printing involves using G-code to control movement of nozzle to form layers of plastic
+• Limitations of 3D printing include layer-by-layer construction and inability to print certain shapes with overhangs without support
+• First layer adhesion is a major issue in 3D printing, especially when using exotic filaments
+• Temperature control and environment are crucial factors affecting 3D printing success
+• Different types of filaments have unique characteristics, such as PLA being beginner-friendly but brittle and prone to warping in warm environments
+• The speaker created custom cup holders for a friend's above-ground pool
+• They used PETG filament to print the cup holders due to its heat-resistant properties
+• PETG is a hybrid material that combines the best of PLA and ABS, but can be finicky to work with
+• It requires higher temperatures (up to 250°C) than PLA to flow well and can stick to glass beds
+• Manufacturer-specific settings and calibration may be necessary for optimal results
+• Slicers like Cura and Prusa Slicer are used to convert 3D models into G-code that guides the printer's nozzle
+• Different slicers have varying capabilities, but Prusa Slicer is specifically optimized for Prusa printers
+• The effects of humidity on PETG filament at different altitudes
+• Using Cura settings and adjusting them for better results
+• Storing filaments to prevent absorption of moisture from the air
+• Experiences with PLA and PETG filaments in Colorado vs Texas
+• Introduction to Octoprint, a software for controlling 3D printers remotely
+• Discussion of plugins available for Octoprint, such as webcam monitoring and cost estimation tools
+• Octoprint and its uses for Raspberry Pi and 3D printing
+• Linode's cloud hosting and benefits for R&D and project setup
+• Comparison of direct drive and Bowden tube extruders for flexible filaments like TPU
+• Overview of entry-level filaments (PLA, PETG, TPU) and considerations for beginners
+• Advertisement for Linode's services and promotions
+• Linode's service is mentioned as a reliable and improving option for hosting projects.
+• The discussion turns to 3D printing, with the topic of whether an enclosure is needed.
+• Factors influencing the need for an enclosure include containing heat and environmental variables in the area where the printer will be used.
+• Personal experience shared about using an enclosure to prevent pet hair interference with prints.
+• Enclosures can also help with temperature control for certain plastics like ABS.
+• Various uses for an enclosure beyond just dust, noise, and fume control are mentioned.
+• The discussion shifts to sharing and discussing different 3D printers and upgrades each person has made.
+• Drew shares their experience upgrading parts on the Ender 3 Pro, including replacing the hot end and switching from a Bowden tube setup to direct drive.
+• Auto bed leveling is also discussed as a valuable upgrade that helps improve print quality.
+• The speaker upgraded their Ender 3 Pro printer with various components
+• They mention buying a Nozzle X and replacing the cheap brass nozzles
+• The total cost of upgrades is under $500
+• The speaker compares their experience with an entry-level 3D printer (Ender) to a high-end one (Prusa i3 Mark III)
+• They discuss the benefits of building a Prusa, including learning about electronics and 3D printing capabilities
+• The speaker values the turnkey experience of the Prusa, which comes with extensive documentation and customer support
+• Prusa's open-source approach to hardware designs
+• Comparison of Prusa and Creality's business practices
+• Open-source movement in 3D printing industry
+• Ender 3 from Creality being open-sourced due to public pressure
+• Benefits of auto bed leveling and direct drive extruder in Prusa printers
+• Importance of accurate and true hardware components
+• Upgrades to the Ender 3 Pro printer significantly reduced noise levels
+• Printers are used for various projects, including cases and stands for household items, musical instruments, and electronics
+• The speakers discuss their journey with 3D printing, from basic prints to designing and selling objects through their stores
+• They mention using microcontrollers and other technologies in conjunction with 3D printing
+• The hobby of 3D printing can be addictive, drawing people into designing and creating their own items instead of just buying them
+• Printers are used for baby-proofing the house, making corner protectors and outlet prong protectors.
+• The Prusa XL printer is a large format machine with automatic extruder tool head changes and multiple filament loading capabilities.
+• It has a significantly larger build volume than the standard Prusa printer and comes at a higher price point, starting at $2,000.
+• The Prusa XL features a new bed technology that includes segmented beds with cooling and expansion channels to reduce warping of prints.
+• Discussion on weighing filament before printing, with some users relying on their printer's filament runout sensor or a manual "cross and clench" method.
+• Use cases for the Prusa XL's multiple extruder feature, including printing different materials and dissolvable filaments.
+• Discussion of modifying spools of filament by fusing and filing them
+• Comparison of safety between using isopropyl alcohol vs. glue stick on print bed
+• Importance of regular printer maintenance, such as cleaning the nozzle and bed
+• Frequency of maintenance needed for printers, depending on usage
+• Various methods for wiping down the print bed after use
+• Discussion of a past experience or project
+• Recommendation to use high-quality glue stick for DIY upgrades
+• Introduction and thank-yous from guests and host
+• Promotion of network membership at Jupiter.party and selfhosted.show/sre
+• Details about the benefits of network membership, including ad-free content and behind-the-scenes material
+• Explanation of how network membership funding allows for picky sponsor selection
 • Call to action to support the show through membership or other means (downloads, community support, reviews)