Datasets:
add all 2022 summaries
Browse files- 62: Succumbing to the Ecosystem _summary.txt +97 -97
- 63: Pulling the Rug Out _summary.txt +62 -62
- 64: Analysis Paralysis _summary.txt +86 -86
- 65: Failing at Scale _summary.txt +59 -59
- 66: Mmm. Pi. _summary.txt +91 -91
- 67: The No Container Theory _summary.txt +102 -102
- 68: Unwyze Choices _summary.txt +101 -101
- 69: Get Off My Lawn, The Robot's Got It _summary.txt +67 -67
- 70: Plausible Deniability _summary.txt +86 -86
- 71: Recipe for Success _summary.txt +112 -112
- 72: First Account is Free _summary.txt +65 -65
- 73: 100 Days of HomeLab _summary.txt +59 -59
- 74: A Pi For Every Problem _summary.txt +93 -93
- 75: In-Flight Changes _summary.txt +94 -94
- 76: Solid as a Rock _summary.txt +104 -104
- 77: Automations Gone Wrong _summary.txt +95 -95
- 78: We Should Know Better _summary.txt +82 -82
- 79: Google is a Hostile Actor _summary.txt +100 -100
- 80: Solving Whole Home Audio _summary.txt +85 -85
- 81: The Badger Stack _summary.txt +124 -124
- 82: Roon Ready Ruh-Roh _summary.txt +105 -105
- 83: Unintended Upgrades _summary.txt +110 -110
- 84: Hidden NAS _summary.txt +57 -57
- 85: Wendell's Hot Pi _summary.txt +82 -82
- 86: Disqus-ting Tracking _summary.txt +69 -69
- 87: Jellyfin January _summary.txt +103 -103
62: Succumbing to the Ecosystem _summary.txt
CHANGED
|
@@ -1,98 +1,98 @@
|
|
| 1 |
-
• Welcome back to a show after a holiday break
|
| 2 |
-
• Discussion of game Anno 1800 and its gameplay mechanics
|
| 3 |
-
• Mention of a possible follow-up on Linux Unplugged predictions episode
|
| 4 |
-
• Update on the availability of 20 terabyte hard drives for $250 at Best Buy, which did not happen due to supply chain issues and Chia cryptocurrency's impact on market
|
| 5 |
-
• Discussion of the cost of new graphics cards (3080) and used storage drives
|
| 6 |
-
• Discussing hard drive reliability and potential failures
|
| 7 |
-
• Considering alternative backup solutions, including shipping drives to an off-site location
|
| 8 |
-
• Mention of the possibility of a catastrophic event (nuclear attack) and its potential impact on data storage and backup systems
|
| 9 |
-
• Discussion of off-site backups and decentralizing data storage
|
| 10 |
-
• Prediction of a 20 terabyte easy store for $250 or less
|
| 11 |
-
• Alex's possible success rate with his project being 0%
|
| 12 |
-
• Concerns about diminishing returns with hard drive capacity
|
| 13 |
-
• Physical limitations of hard drives and innovations in the field
|
| 14 |
-
• Discussion of HomeKit and its capabilities
|
| 15 |
-
• Integration of HomeKit with Siri, Apple TV remote, and Shortcuts app
|
| 16 |
-
• Ecosystem limitations as a "sandbox" with walls
|
| 17 |
-
• Seamless control experience through iOS devices
|
| 18 |
-
• Compatibility with non-HomeKit devices (e.g., LG TV)
|
| 19 |
-
• Robustness of HomeKit security features, including encryption and partnership with Matter
|
| 20 |
-
• Integration with Home Assistant for expanded capabilities
|
| 21 |
-
• HomeBridge was used to connect non-HomeKit devices to Apple's HomeKit
|
| 22 |
-
• LG TVs were controlled using this bridge before official HomeKit support
|
| 23 |
-
• The bridge translates proprietary device protocols to HomeKit format
|
| 24 |
-
• HomeBridge is no longer necessary for most users since LG added HomeKit support
|
| 25 |
-
• It can still be useful for controlling non-HomeKit compatible devices
|
| 26 |
-
• Linode is mentioned as a cloud hosting service and sponsor of the podcast
|
| 27 |
-
• Linking Home Assistant with HomeKit
|
| 28 |
-
• Connecting non-HomeKit devices to HomeKit through integration
|
| 29 |
-
• Adding camera feeds and automations as HomeKit devices
|
| 30 |
-
• Importing existing HomeKit devices into Home Assistant
|
| 31 |
-
• Setting up a central hub for family devices to access and control shared devices
|
| 32 |
-
• Integration of smart devices with HomeKit
|
| 33 |
-
• Apple TV as a hub for HomeKit integration
|
| 34 |
-
• Issues with certain device types (e.g. robot vacuum) and their integration
|
| 35 |
-
• Curation process to disable unnecessary devices in HomeKit
|
| 36 |
-
• Comparison between HomeKit and other smart home platforms (e.g. Home Assistant)
|
| 37 |
-
• Philips Hue ecosystem and its replacement with Zigbee bridge and buttons
|
| 38 |
-
• Integration of HomeKit with Home Assistant
|
| 39 |
-
• Use of Siri as voice control for home automation
|
| 40 |
-
• Comparison with Google and Amazon services
|
| 41 |
-
• Apple's LAN-based protocol vs cloud-based API
|
| 42 |
-
• Nebu Casa cloud service and its limitations
|
| 43 |
-
• HomeKit integration bypassing need for complicated setup
|
| 44 |
-
• Easy setup and use of HomeKit devices with Siri
|
| 45 |
-
• The speaker is looking to acquire a mini DV camcorder at a cost lower than $150
|
| 46 |
-
• They are also seeking suggestions on how to digitize the tapes properly
|
| 47 |
-
• Tailscale VPN service is recommended, which allows secure network connections between devices and provides features such as multi-factor authentication and stable IP addresses
|
| 48 |
-
• Tailscale offers support for up to 20 machines
|
| 49 |
-
• NVIDIA Shield has been updated to Android TV 11 with a Stadia button
|
| 50 |
-
• Update does not eliminate ads from interface
|
| 51 |
-
• User experiences buffering issue while watching Deadwood on NVIDIA Shield due to Plex transcoding audio codec
|
| 52 |
-
• Discussion of differences in hardware capabilities between NVIDIA Shield and Apple TV
|
| 53 |
-
• Discussion of the Nintendo Switch and NVIDIA devices
|
| 54 |
-
• Comparison of Apple TV to NVIDIA Shield
|
| 55 |
-
• Use cases for a media streaming device, including iPlayer and Kodi
|
| 56 |
-
• Concerns about getting WireGuard VPN to work on an Apple TV
|
| 57 |
-
• Difficulty replicating certain features or settings on the Apple TV compared to other devices
|
| 58 |
-
• Discussion of video player software for Apple TV
|
| 59 |
-
• Comparison of Plex and Jellyfin on Apple TV
|
| 60 |
-
• Use of WireGuard VPN with Apple TV
|
| 61 |
-
• Rooting the Apple TV and installing third-party apps
|
| 62 |
-
• Kodi vs Infuse as a set-top interface for video playback
|
| 63 |
-
• Infuse's features, including codec support and syncing capabilities
|
| 64 |
-
• Development teams behind Plex and Infuse
|
| 65 |
-
• XBMC (Kodi) on a PlayStation 3
|
| 66 |
-
• DLP televisions and their technology
|
| 67 |
-
• Nostalgia for old tech and software design
|
| 68 |
-
• Review of Kodi's evolution and comparison to other media players like Plex
|
| 69 |
-
• Features of Kodi, including video playback engine and blur effect for spoilers
|
| 70 |
-
• Installing Kodi on Mac and Apple TV with iCloud sync settings
|
| 71 |
-
• Comparison of media server devices
|
| 72 |
-
• Discussion of Jellyfin's performance and features
|
| 73 |
-
• Brent's personal experience with Jellyfin and its impact on his household setup
|
| 74 |
-
• Comparison between Jellyfin and Plex as a media server software
|
| 75 |
-
• The advantages of using Jellyfin for centralized media management
|
| 76 |
-
• The speaker is using Jellyfin on their Android phone to browse and stream media content to their TV
|
| 77 |
-
• They experience occasional connection drops and glitches with Jellyfin compared to Plex
|
| 78 |
-
• This leads the speaker to consider alternative solutions, such as a set-top box with a dedicated client
|
| 79 |
-
• Apple TV and Infuse are mentioned as an alternative solution that provides a more stable streaming experience
|
| 80 |
-
• The speaker is excited about exploring Docker and its potential for opening up new possibilities for app development and deployment
|
| 81 |
-
• The speaker was initially frustrated with the blurring of lines between application and data on a home server.
|
| 82 |
-
• They found that using containers (specifically Docker) provided a solid way to separate applications from data.
|
| 83 |
-
• Containers allow for easy recreation of an environment, making disaster recovery simpler and easier to manage.
|
| 84 |
-
• The speaker's experience with troubleshooting a container failure had an "aha moment" where they realized the power of recreating a container from scratch.
|
| 85 |
-
• The speaker is interested in using containers, particularly Docker and Docker Compose
|
| 86 |
-
• They have questions about troubleshooting and interacting with containers
|
| 87 |
-
• The importance of understanding that each container has its own contained environment
|
| 88 |
-
• Docker Compose as a tool for launching apps and viewing logs
|
| 89 |
-
• Accessing logs is key to understanding what's happening within a container
|
| 90 |
-
• The benefits and usage of a command that prints the last 50 lines of a container's standard output
|
| 91 |
-
• Challenges with container logs, including some applications not logging by default
|
| 92 |
-
• Ways to troubleshoot and increase log verbosity for problematic containers
|
| 93 |
-
• Introduction to Dozzle, a tool for viewing container logs in a browser
|
| 94 |
-
• Upcoming meetup at the studio on January 30th and promotion of new network membership
|
| 95 |
-
• Apologies for not being able to attend a birthday party in person
|
| 96 |
-
• Scheduling issues due to weather conditions (frozen tundra vs warm location)
|
| 97 |
-
• Discussion of Seattle's rough winters
|
| 98 |
• Invitation for feedback on content ideas, apps, and self-hosted projects
|
|
|
|
| 1 |
+
• Welcome back to a show after a holiday break
|
| 2 |
+
• Discussion of game Anno 1800 and its gameplay mechanics
|
| 3 |
+
• Mention of a possible follow-up on Linux Unplugged predictions episode
|
| 4 |
+
• Update on the availability of 20 terabyte hard drives for $250 at Best Buy, which did not happen due to supply chain issues and Chia cryptocurrency's impact on market
|
| 5 |
+
• Discussion of the cost of new graphics cards (3080) and used storage drives
|
| 6 |
+
• Discussing hard drive reliability and potential failures
|
| 7 |
+
• Considering alternative backup solutions, including shipping drives to an off-site location
|
| 8 |
+
• Mention of the possibility of a catastrophic event (nuclear attack) and its potential impact on data storage and backup systems
|
| 9 |
+
• Discussion of off-site backups and decentralizing data storage
|
| 10 |
+
• Prediction of a 20 terabyte easy store for $250 or less
|
| 11 |
+
• Alex's possible success rate with his project being 0%
|
| 12 |
+
• Concerns about diminishing returns with hard drive capacity
|
| 13 |
+
• Physical limitations of hard drives and innovations in the field
|
| 14 |
+
• Discussion of HomeKit and its capabilities
|
| 15 |
+
• Integration of HomeKit with Siri, Apple TV remote, and Shortcuts app
|
| 16 |
+
• Ecosystem limitations as a "sandbox" with walls
|
| 17 |
+
• Seamless control experience through iOS devices
|
| 18 |
+
• Compatibility with non-HomeKit devices (e.g., LG TV)
|
| 19 |
+
• Robustness of HomeKit security features, including encryption and partnership with Matter
|
| 20 |
+
• Integration with Home Assistant for expanded capabilities
|
| 21 |
+
• HomeBridge was used to connect non-HomeKit devices to Apple's HomeKit
|
| 22 |
+
• LG TVs were controlled using this bridge before official HomeKit support
|
| 23 |
+
• The bridge translates proprietary device protocols to HomeKit format
|
| 24 |
+
• HomeBridge is no longer necessary for most users since LG added HomeKit support
|
| 25 |
+
• It can still be useful for controlling non-HomeKit compatible devices
|
| 26 |
+
• Linode is mentioned as a cloud hosting service and sponsor of the podcast
|
| 27 |
+
• Linking Home Assistant with HomeKit
|
| 28 |
+
• Connecting non-HomeKit devices to HomeKit through integration
|
| 29 |
+
• Adding camera feeds and automations as HomeKit devices
|
| 30 |
+
• Importing existing HomeKit devices into Home Assistant
|
| 31 |
+
• Setting up a central hub for family devices to access and control shared devices
|
| 32 |
+
• Integration of smart devices with HomeKit
|
| 33 |
+
• Apple TV as a hub for HomeKit integration
|
| 34 |
+
• Issues with certain device types (e.g. robot vacuum) and their integration
|
| 35 |
+
• Curation process to disable unnecessary devices in HomeKit
|
| 36 |
+
• Comparison between HomeKit and other smart home platforms (e.g. Home Assistant)
|
| 37 |
+
• Philips Hue ecosystem and its replacement with Zigbee bridge and buttons
|
| 38 |
+
• Integration of HomeKit with Home Assistant
|
| 39 |
+
• Use of Siri as voice control for home automation
|
| 40 |
+
• Comparison with Google and Amazon services
|
| 41 |
+
• Apple's LAN-based protocol vs cloud-based API
|
| 42 |
+
• Nebu Casa cloud service and its limitations
|
| 43 |
+
• HomeKit integration bypassing need for complicated setup
|
| 44 |
+
• Easy setup and use of HomeKit devices with Siri
|
| 45 |
+
• The speaker is looking to acquire a mini DV camcorder at a cost lower than $150
|
| 46 |
+
• They are also seeking suggestions on how to digitize the tapes properly
|
| 47 |
+
• Tailscale VPN service is recommended, which allows secure network connections between devices and provides features such as multi-factor authentication and stable IP addresses
|
| 48 |
+
• Tailscale offers support for up to 20 machines
|
| 49 |
+
• NVIDIA Shield has been updated to Android TV 11 with a Stadia button
|
| 50 |
+
• Update does not eliminate ads from interface
|
| 51 |
+
• User experiences buffering issue while watching Deadwood on NVIDIA Shield due to Plex transcoding audio codec
|
| 52 |
+
• Discussion of differences in hardware capabilities between NVIDIA Shield and Apple TV
|
| 53 |
+
• Discussion of the Nintendo Switch and NVIDIA devices
|
| 54 |
+
• Comparison of Apple TV to NVIDIA Shield
|
| 55 |
+
• Use cases for a media streaming device, including iPlayer and Kodi
|
| 56 |
+
• Concerns about getting WireGuard VPN to work on an Apple TV
|
| 57 |
+
• Difficulty replicating certain features or settings on the Apple TV compared to other devices
|
| 58 |
+
• Discussion of video player software for Apple TV
|
| 59 |
+
• Comparison of Plex and Jellyfin on Apple TV
|
| 60 |
+
• Use of WireGuard VPN with Apple TV
|
| 61 |
+
• Rooting the Apple TV and installing third-party apps
|
| 62 |
+
• Kodi vs Infuse as a set-top interface for video playback
|
| 63 |
+
• Infuse's features, including codec support and syncing capabilities
|
| 64 |
+
• Development teams behind Plex and Infuse
|
| 65 |
+
• XBMC (Kodi) on a PlayStation 3
|
| 66 |
+
• DLP televisions and their technology
|
| 67 |
+
• Nostalgia for old tech and software design
|
| 68 |
+
• Review of Kodi's evolution and comparison to other media players like Plex
|
| 69 |
+
• Features of Kodi, including video playback engine and blur effect for spoilers
|
| 70 |
+
• Installing Kodi on Mac and Apple TV with iCloud sync settings
|
| 71 |
+
• Comparison of media server devices
|
| 72 |
+
• Discussion of Jellyfin's performance and features
|
| 73 |
+
• Brent's personal experience with Jellyfin and its impact on his household setup
|
| 74 |
+
• Comparison between Jellyfin and Plex as a media server software
|
| 75 |
+
• The advantages of using Jellyfin for centralized media management
|
| 76 |
+
• The speaker is using Jellyfin on their Android phone to browse and stream media content to their TV
|
| 77 |
+
• They experience occasional connection drops and glitches with Jellyfin compared to Plex
|
| 78 |
+
• This leads the speaker to consider alternative solutions, such as a set-top box with a dedicated client
|
| 79 |
+
• Apple TV and Infuse are mentioned as an alternative solution that provides a more stable streaming experience
|
| 80 |
+
• The speaker is excited about exploring Docker and its potential for opening up new possibilities for app development and deployment
|
| 81 |
+
• The speaker was initially frustrated with the blurring of lines between application and data on a home server.
|
| 82 |
+
• They found that using containers (specifically Docker) provided a solid way to separate applications from data.
|
| 83 |
+
• Containers allow for easy recreation of an environment, making disaster recovery simpler and easier to manage.
|
| 84 |
+
• The speaker's experience with troubleshooting a container failure had an "aha moment" where they realized the power of recreating a container from scratch.
|
| 85 |
+
• The speaker is interested in using containers, particularly Docker and Docker Compose
|
| 86 |
+
• They have questions about troubleshooting and interacting with containers
|
| 87 |
+
• The importance of understanding that each container has its own contained environment
|
| 88 |
+
• Docker Compose as a tool for launching apps and viewing logs
|
| 89 |
+
• Accessing logs is key to understanding what's happening within a container
|
| 90 |
+
• The benefits and usage of a command that prints the last 50 lines of a container's standard output
|
| 91 |
+
• Challenges with container logs, including some applications not logging by default
|
| 92 |
+
• Ways to troubleshoot and increase log verbosity for problematic containers
|
| 93 |
+
• Introduction to Dozzle, a tool for viewing container logs in a browser
|
| 94 |
+
• Upcoming meetup at the studio on January 30th and promotion of new network membership
|
| 95 |
+
• Apologies for not being able to attend a birthday party in person
|
| 96 |
+
• Scheduling issues due to weather conditions (frozen tundra vs warm location)
|
| 97 |
+
• Discussion of Seattle's rough winters
|
| 98 |
• Invitation for feedback on content ideas, apps, and self-hosted projects
|
63: Pulling the Rug Out _summary.txt
CHANGED
|
@@ -1,63 +1,63 @@
|
|
| 1 |
-
• Discussing rat infestations and prevention methods in the Pacific Northwest
|
| 2 |
-
• Introducing ultrasonic noise-making devices for critter control
|
| 3 |
-
• Exploring alternative solutions using smart plugs and home assistants
|
| 4 |
-
• Sharing personal experiences with high-pitched sounds and their effects on hearing
|
| 5 |
-
• Mentioning the controversy surrounding Neil Young's Spotify ultimatum over Joe Rogan
|
| 6 |
-
• Analyzing the implications of streaming services, catalog content removal, and artist concerns
|
| 7 |
-
• Corporate games harm customers
|
| 8 |
-
• Companies prioritize exclusives over customer interests
|
| 9 |
-
• Paramount's decision to remove Star Trek from Netflix is an example of this trend
|
| 10 |
-
• The speaker's personal experience with Spotify and their concerns about the platform's direction
|
| 11 |
-
• Spotify's attempted takeover of podcasting, including offering exclusive deals and dynamic ads
|
| 12 |
-
• The speaker's decision to unsubscribe from Spotify and promote decentralized solutions for podcast hosting
|
| 13 |
-
• The impact of Spotify on the podcast industry and the decision to cancel it
|
| 14 |
-
• The issue of COVID misinformation spread by Joe Rogan and Neil's ultimatum
|
| 15 |
-
• The importance of owning one's own digital content, including music, due to potential platform changes or deletions
|
| 16 |
-
• A tool called LiDAR and a plugin called Automatic Music Downloader that download lossless audio from Deezer
|
| 17 |
-
• The ethics of using this method versus piracy and the value of paying for a $15/month subscription to Deezer HiFi
|
| 18 |
-
• Plexamp as an alternative to Spotify, its features, and user experience
|
| 19 |
-
• The speaker discusses their positive experience with Plex Amp, a music player that provides tailored recommendations based on user behavior
|
| 20 |
-
• Comparison of Plex Amp with Finamp, an open-source alternative, which is considered less effective but still offers the ability to use Jellyfin as a backend server
|
| 21 |
-
• Promotion of Linode.com, a cloud hosting service, and its benefits for hosting various services, including Nextcloud
|
| 22 |
-
• Discussion of Google's announcement to shut down free G Suite accounts unless users pay for them, causing upset among some listeners who rely on these accounts for personal and business use
|
| 23 |
-
• Discussion of Google's surprise at how many users were affected by their recent shutdown announcement
|
| 24 |
-
• Criticism of Google's handling of user data and metrics on active users
|
| 25 |
-
• Mention of class action lawsuit against Google for the shutdown
|
| 26 |
-
• Announcement of a new survey to gather information from affected G Suite users
|
| 27 |
-
• Benefits and drawbacks of using non-Google services, such as ProtonMail and FastMail, for email hosting
|
| 28 |
-
• Discussion of self-hosting and limiting exposure to Google services
|
| 29 |
-
• Comparison of de-Googling options, including Lineage OS and F-Droid for Android replacement
|
| 30 |
-
• Criticism of Google's data mining practices
|
| 31 |
-
• Public safety announcement: Let's Encrypt is revoking SSL certificates
|
| 32 |
-
• Tailscale sponsorship and promotion of their zero-config VPN solution
|
| 33 |
-
• Update on the host's dad moving to a new location with limited internet speed
|
| 34 |
-
• Exploring options for improving internet connectivity at the host's dad's house
|
| 35 |
-
• Rural Norfolk mother-in-law uses EE 4G mobile broadband with a fixed antenna for reliable internet
|
| 36 |
-
• Comparison of EE's 4G and 5G plans, including limited bandwidth quotas on 4G plans
|
| 37 |
-
• Discussion of multi-WAN connections and the potential benefits of bonding multiple internet sources
|
| 38 |
-
• Overview of PepWave/PepLink routers and their ability to bond multiple connections over a VPN
|
| 39 |
-
• Concerns about Wi-Fi range and limitations with consumer-grade Wi-Fi devices
|
| 40 |
-
• Review of Speedify's internet bonding capabilities, but concerns about paid plans after initial free allocation
|
| 41 |
-
• Hardware and software bundles for US users
|
| 42 |
-
• Cellular signal improvement options, including MiFi devices and external antennas
|
| 43 |
-
• Concerns about EE solution's modem limitations
|
| 44 |
-
• Potential solutions for improved connectivity, such as replacing EE router with better hardware
|
| 45 |
-
• Starlink availability and potential use cases
|
| 46 |
-
• Mini DV camcorder issues and efforts to find suitable hardware
|
| 47 |
-
• Issues with importing mini DV tapes from Europe due to NTSC/PAL format differences
|
| 48 |
-
• Discussion of using HDMI capture devices and USB adapters to import the tapes
|
| 49 |
-
• Mention of region locking and PAL/NTSC formats
|
| 50 |
-
• Exploring options for digitizing the tapes, including purchasing a mini DV player
|
| 51 |
-
• Talking about encoding options (H.264) and plans to use M1 Macs for video encoding
|
| 52 |
-
• Discussion about computer systems and CPUs
|
| 53 |
-
• Comparison of Apple M-series chips with Intel cores
|
| 54 |
-
• Mention of iStat's visualization limitations for neural and efficiency cores
|
| 55 |
-
• Plans to host a meetup in Raleigh, NC in the spring
|
| 56 |
-
• Idea of having a central operation hub in Colorado or other location
|
| 57 |
-
• Discussion of future meetups and events
|
| 58 |
-
• Discussion about better weather at a different location
|
| 59 |
-
• Feedback and links to previous topic
|
| 60 |
-
• Self-hosted website URL (selfhosted.show)
|
| 61 |
-
• Specific episode link (selfhosted.show/63)
|
| 62 |
-
• Contact page URL (selfhosted.show/contact)
|
| 63 |
• End of podcast, thanking listeners
|
|
|
|
| 1 |
+
• Discussing rat infestations and prevention methods in the Pacific Northwest
|
| 2 |
+
• Introducing ultrasonic noise-making devices for critter control
|
| 3 |
+
• Exploring alternative solutions using smart plugs and home assistants
|
| 4 |
+
• Sharing personal experiences with high-pitched sounds and their effects on hearing
|
| 5 |
+
• Mentioning the controversy surrounding Neil Young's Spotify ultimatum over Joe Rogan
|
| 6 |
+
• Analyzing the implications of streaming services, catalog content removal, and artist concerns
|
| 7 |
+
• Corporate games harm customers
|
| 8 |
+
• Companies prioritize exclusives over customer interests
|
| 9 |
+
• Paramount's decision to remove Star Trek from Netflix is an example of this trend
|
| 10 |
+
• The speaker's personal experience with Spotify and their concerns about the platform's direction
|
| 11 |
+
• Spotify's attempted takeover of podcasting, including offering exclusive deals and dynamic ads
|
| 12 |
+
• The speaker's decision to unsubscribe from Spotify and promote decentralized solutions for podcast hosting
|
| 13 |
+
• The impact of Spotify on the podcast industry and the decision to cancel it
|
| 14 |
+
• The issue of COVID misinformation spread by Joe Rogan and Neil's ultimatum
|
| 15 |
+
• The importance of owning one's own digital content, including music, due to potential platform changes or deletions
|
| 16 |
+
• A tool called LiDAR and a plugin called Automatic Music Downloader that download lossless audio from Deezer
|
| 17 |
+
• The ethics of using this method versus piracy and the value of paying for a $15/month subscription to Deezer HiFi
|
| 18 |
+
• Plexamp as an alternative to Spotify, its features, and user experience
|
| 19 |
+
• The speaker discusses their positive experience with Plex Amp, a music player that provides tailored recommendations based on user behavior
|
| 20 |
+
• Comparison of Plex Amp with Finamp, an open-source alternative, which is considered less effective but still offers the ability to use Jellyfin as a backend server
|
| 21 |
+
• Promotion of Linode.com, a cloud hosting service, and its benefits for hosting various services, including Nextcloud
|
| 22 |
+
• Discussion of Google's announcement to shut down free G Suite accounts unless users pay for them, causing upset among some listeners who rely on these accounts for personal and business use
|
| 23 |
+
• Discussion of Google's surprise at how many users were affected by their recent shutdown announcement
|
| 24 |
+
• Criticism of Google's handling of user data and metrics on active users
|
| 25 |
+
• Mention of class action lawsuit against Google for the shutdown
|
| 26 |
+
• Announcement of a new survey to gather information from affected G Suite users
|
| 27 |
+
• Benefits and drawbacks of using non-Google services, such as ProtonMail and FastMail, for email hosting
|
| 28 |
+
• Discussion of self-hosting and limiting exposure to Google services
|
| 29 |
+
• Comparison of de-Googling options, including Lineage OS and F-Droid for Android replacement
|
| 30 |
+
• Criticism of Google's data mining practices
|
| 31 |
+
• Public safety announcement: Let's Encrypt is revoking SSL certificates
|
| 32 |
+
• Tailscale sponsorship and promotion of their zero-config VPN solution
|
| 33 |
+
• Update on the host's dad moving to a new location with limited internet speed
|
| 34 |
+
• Exploring options for improving internet connectivity at the host's dad's house
|
| 35 |
+
• Rural Norfolk mother-in-law uses EE 4G mobile broadband with a fixed antenna for reliable internet
|
| 36 |
+
• Comparison of EE's 4G and 5G plans, including limited bandwidth quotas on 4G plans
|
| 37 |
+
• Discussion of multi-WAN connections and the potential benefits of bonding multiple internet sources
|
| 38 |
+
• Overview of PepWave/PepLink routers and their ability to bond multiple connections over a VPN
|
| 39 |
+
• Concerns about Wi-Fi range and limitations with consumer-grade Wi-Fi devices
|
| 40 |
+
• Review of Speedify's internet bonding capabilities, but concerns about paid plans after initial free allocation
|
| 41 |
+
• Hardware and software bundles for US users
|
| 42 |
+
• Cellular signal improvement options, including MiFi devices and external antennas
|
| 43 |
+
• Concerns about EE solution's modem limitations
|
| 44 |
+
• Potential solutions for improved connectivity, such as replacing EE router with better hardware
|
| 45 |
+
• Starlink availability and potential use cases
|
| 46 |
+
• Mini DV camcorder issues and efforts to find suitable hardware
|
| 47 |
+
• Issues with importing mini DV tapes from Europe due to NTSC/PAL format differences
|
| 48 |
+
• Discussion of using HDMI capture devices and USB adapters to import the tapes
|
| 49 |
+
• Mention of region locking and PAL/NTSC formats
|
| 50 |
+
• Exploring options for digitizing the tapes, including purchasing a mini DV player
|
| 51 |
+
• Talking about encoding options (H.264) and plans to use M1 Macs for video encoding
|
| 52 |
+
• Discussion about computer systems and CPUs
|
| 53 |
+
• Comparison of Apple M-series chips with Intel cores
|
| 54 |
+
• Mention of iStat's visualization limitations for neural and efficiency cores
|
| 55 |
+
• Plans to host a meetup in Raleigh, NC in the spring
|
| 56 |
+
• Idea of having a central operation hub in Colorado or other location
|
| 57 |
+
• Discussion of future meetups and events
|
| 58 |
+
• Discussion about better weather at a different location
|
| 59 |
+
• Feedback and links to previous topic
|
| 60 |
+
• Self-hosted website URL (selfhosted.show)
|
| 61 |
+
• Specific episode link (selfhosted.show/63)
|
| 62 |
+
• Contact page URL (selfhosted.show/contact)
|
| 63 |
• End of podcast, thanking listeners
|
64: Analysis Paralysis _summary.txt
CHANGED
|
@@ -1,87 +1,87 @@
|
|
| 1 |
-
• The speaker visited the dentist for the first time in 15 years
|
| 2 |
-
• They had a rough experience with a cleaning procedure
|
| 3 |
-
• The speaker's daughter wore VR goggles during her dentist visit
|
| 4 |
-
• The speaker bought a Valve Index VR headset and is considering playing Beat Saber
|
| 5 |
-
• They discussed the possibility of using VR to hang out virtually while recording podcasts
|
| 6 |
-
• The speaker compared the Index to other VR options, such as the Quest
|
| 7 |
-
• They mentioned the benefits and drawbacks of each option
|
| 8 |
-
• The narrator discusses their experience playing Flight Sim in VR and being transported to a familiar location in Scotland.
|
| 9 |
-
• They compare the graphics in Flight Sim to earlier versions of the game and express amazement at how far they have come.
|
| 10 |
-
• The team behind Flight Sim is praised for accurately recreating Pacific Northwest regions, including the narrator's hometown area.
|
| 11 |
-
• The use of photogrammetry technology is mentioned as a key factor in achieving high-quality graphics.
|
| 12 |
-
• A listener's email sparks a discussion about handheld gaming and retro gaming with the upcoming Steam Deck release.
|
| 13 |
-
• The potential of the Steam Deck to run emulators and play various games on different platforms is explored.
|
| 14 |
-
• The RetroNAS project is introduced, which allows Linux computers to be used as network storage devices for gaming consoles and emulators.
|
| 15 |
-
• The speaker is discussing retro gaming and how one can play classic games on modern devices using old protocols.
|
| 16 |
-
• A specific example is given of playing PlayStation 3 games without the disc using an NAS device and streaming the ISO.
|
| 17 |
-
• The speaker mentions that this method allows for "DRM-free" gaming and recalls his early experiences with hacking consoles to improve gameplay.
|
| 18 |
-
• The conversation then shifts to a discussion of the list of supported consoles, which includes MS-DOS, Apple GS, Atari ST, and Nintendo 3DS among others.
|
| 19 |
-
• The speakers share their personal preferences for retro games, with one speaker mentioning that he prefers PC games with LAN play features.
|
| 20 |
-
• They also reminisce about early gaming experiences, including using NetBui, IPX, and WINS for networking, as well as playing classic games on older computers.
|
| 21 |
-
• Nostalgia for old TV listings and interactive services
|
| 22 |
-
• Memories of playing "Where in the World is Carmen Sandiego?" on DOS and Windows
|
| 23 |
-
• Discussion of low-graphics games being acceptable due to safety concerns
|
| 24 |
-
• Promotion of Linode cloud hosting and its features (fast, reliable, 11 data centers, customer support)
|
| 25 |
-
• Description of Linode's infrastructure upgrades (bare metal systems, PCIe storage) and tools (API, command line client)
|
| 26 |
-
• Use case for Linode in a small business or studio setting for balance of security, performance, and ownership
|
| 27 |
-
• Mention of backup options and automatic backups on Linode
|
| 28 |
-
• The host is organizing a Matrix setup party for this weekend
|
| 29 |
-
• Discussion of what Matrix is and its potential benefits
|
| 30 |
-
• Explanation of how to self-host a Matrix server at your own domain
|
| 31 |
-
• Description of the features and capabilities of Matrix, including bridging with other services
|
| 32 |
-
• Comparison of Matrix to Discord and acknowledgement that Matrix is more complex but offers greater appeal due to decentralization
|
| 33 |
-
• Home Assistant pricing increase from $5 to $6.50 per month for optional cloud features
|
| 34 |
-
• New annual tier of $65 per year
|
| 35 |
-
• Opinions on price fairness and potential future donations or donation drives
|
| 36 |
-
• Discussion of heavy use of Home Assistant in multiple locations (RV and studio)
|
| 37 |
-
• Thoughts on sustainability of current project and desire to see it succeed
|
| 38 |
-
• Idea of a plan that would allow connecting two Home Assistant instances for $9 per month
|
| 39 |
-
• Hiring of two new individuals working on different aspects of Home Assistant, including content creation
|
| 40 |
-
• Concerns about direct involvement in content creation by the project itself
|
| 41 |
-
• Home Assistant release discussion
|
| 42 |
-
• Price increase grandfathering for existing accounts
|
| 43 |
-
• New features in latest Home Assistant release (backup size display, Apple TV integration updates)
|
| 44 |
-
• Google Assistant integration with local fulfillment
|
| 45 |
-
• Delayed Home Assistant Yellow/Amber update timeline
|
| 46 |
-
• Promotion of Talescale.com and its benefits for self-hosted devices
|
| 47 |
-
• The user has a positive experience with Talescale, using it to connect to their system through a dedicated IP address and DNS feature.
|
| 48 |
-
• The user discusses balancing progress and perfection in self-hosting, citing the importance of documentation to revisit projects later.
|
| 49 |
-
• The user shares their personal experience of overlearning and forgetting information, leading to the realization that documenting knowledge at peak is essential.
|
| 50 |
-
• Documentation is emphasized as crucial for future reference and revisiting projects.
|
| 51 |
-
• The conversation touches on the topic of retaining information and expertise, with the user wondering how others (like Wendell) can recall complex details.
|
| 52 |
-
• Memories and recall
|
| 53 |
-
• Documenting shortcomings and setup to gain clarity
|
| 54 |
-
• Analysis paralysis and procrastination
|
| 55 |
-
• Learning through making mistakes and failing faster
|
| 56 |
-
• Importance of starting small and building on real problems
|
| 57 |
-
• Navigating complex decisions and trade-offs in projects and infrastructure
|
| 58 |
-
• The speaker is discussing how to automate tasks
|
| 59 |
-
• They mention a popular deploy matrix on a system using Ansible and consider using it in the future
|
| 60 |
-
• The conversation takes an unrelated turn when one of them mentions eating their first PB&J sandwich
|
| 61 |
-
• Details about the sandwich are discussed, including type of bread, peanut butter, jelly, and ratio of ingredients
|
| 62 |
-
• Making a peanut butter and jelly sandwich
|
| 63 |
-
• Discussing the optimal thickness of PB and J layers
|
| 64 |
-
• Measuring jam thickness (37 microns)
|
| 65 |
-
• Comparing American measurement systems to international standards
|
| 66 |
-
• Toasting techniques for elevating the sandwich experience
|
| 67 |
-
• Reviewing the benefits of the sandwich (delicious, budget-friendly, quick to make)
|
| 68 |
-
• Discussion about not being able to attend an event or activity
|
| 69 |
-
• Mention of tactical pants and their benefits, including phone storage capacity and wallet placement
|
| 70 |
-
• Comparison between Subsonic and Jellyfin self-hosted music options
|
| 71 |
-
• Recommendation for using a mobile media server during a trip with unreliable cell service
|
| 72 |
-
• Discussion of setting up a quick and dirty mobile media server using Raspberry Pis and USB hard drives
|
| 73 |
-
• Portable power units for charging devices while driving
|
| 74 |
-
• LTE routers for internet access during the trip
|
| 75 |
-
• Networking equipment to connect devices to the TV
|
| 76 |
-
• Power options for the Raspberry Pi, including USB storage with ButterFS
|
| 77 |
-
• Alternative solutions such as a laptop or tablet for simplicity
|
| 78 |
-
• Discussing media streaming options for a van without TV or tablet
|
| 79 |
-
• Using an iPad with speakers and Plex sync for video playback
|
| 80 |
-
• Infuse app on iPad for playing videos from USB storage
|
| 81 |
-
• Setting up Kodi or similar software on a Raspberry Pi as an alternative to a set-top box
|
| 82 |
-
• Planning an East Coast Spring Meetup in Raleigh, possibly at a brewery
|
| 83 |
-
• Discussion of the current weather in April
|
| 84 |
-
• Mention of Linux fest being cancelled and proposal to hold a Linux meetup in April instead
|
| 85 |
-
• Gratitude expressed for members, SREs, and sponsors (Linode and Tailscale) who support the show
|
| 86 |
-
• Information about membership benefits, including ad-free versions of the show and access to network shows
|
| 87 |
• Contact information for the host (self-hosted.show/contact, Twitter (@ironicbadger), Matrix (@Chris LAS))
|
|
|
|
| 1 |
+
• The speaker visited the dentist for the first time in 15 years
|
| 2 |
+
• They had a rough experience with a cleaning procedure
|
| 3 |
+
• The speaker's daughter wore VR goggles during her dentist visit
|
| 4 |
+
• The speaker bought a Valve Index VR headset and is considering playing Beat Saber
|
| 5 |
+
• They discussed the possibility of using VR to hang out virtually while recording podcasts
|
| 6 |
+
• The speaker compared the Index to other VR options, such as the Quest
|
| 7 |
+
• They mentioned the benefits and drawbacks of each option
|
| 8 |
+
• The narrator discusses their experience playing Flight Sim in VR and being transported to a familiar location in Scotland.
|
| 9 |
+
• They compare the graphics in Flight Sim to earlier versions of the game and express amazement at how far they have come.
|
| 10 |
+
• The team behind Flight Sim is praised for accurately recreating Pacific Northwest regions, including the narrator's hometown area.
|
| 11 |
+
• The use of photogrammetry technology is mentioned as a key factor in achieving high-quality graphics.
|
| 12 |
+
• A listener's email sparks a discussion about handheld gaming and retro gaming with the upcoming Steam Deck release.
|
| 13 |
+
• The potential of the Steam Deck to run emulators and play various games on different platforms is explored.
|
| 14 |
+
• The RetroNAS project is introduced, which allows Linux computers to be used as network storage devices for gaming consoles and emulators.
|
| 15 |
+
• The speaker is discussing retro gaming and how one can play classic games on modern devices using old protocols.
|
| 16 |
+
• A specific example is given of playing PlayStation 3 games without the disc using an NAS device and streaming the ISO.
|
| 17 |
+
• The speaker mentions that this method allows for "DRM-free" gaming and recalls his early experiences with hacking consoles to improve gameplay.
|
| 18 |
+
• The conversation then shifts to a discussion of the list of supported consoles, which includes MS-DOS, Apple GS, Atari ST, and Nintendo 3DS among others.
|
| 19 |
+
• The speakers share their personal preferences for retro games, with one speaker mentioning that he prefers PC games with LAN play features.
|
| 20 |
+
• They also reminisce about early gaming experiences, including using NetBui, IPX, and WINS for networking, as well as playing classic games on older computers.
|
| 21 |
+
• Nostalgia for old TV listings and interactive services
|
| 22 |
+
• Memories of playing "Where in the World is Carmen Sandiego?" on DOS and Windows
|
| 23 |
+
• Discussion of low-graphics games being acceptable due to safety concerns
|
| 24 |
+
• Promotion of Linode cloud hosting and its features (fast, reliable, 11 data centers, customer support)
|
| 25 |
+
• Description of Linode's infrastructure upgrades (bare metal systems, PCIe storage) and tools (API, command line client)
|
| 26 |
+
• Use case for Linode in a small business or studio setting for balance of security, performance, and ownership
|
| 27 |
+
• Mention of backup options and automatic backups on Linode
|
| 28 |
+
• The host is organizing a Matrix setup party for this weekend
|
| 29 |
+
• Discussion of what Matrix is and its potential benefits
|
| 30 |
+
• Explanation of how to self-host a Matrix server at your own domain
|
| 31 |
+
• Description of the features and capabilities of Matrix, including bridging with other services
|
| 32 |
+
• Comparison of Matrix to Discord and acknowledgement that Matrix is more complex but offers greater appeal due to decentralization
|
| 33 |
+
• Home Assistant pricing increase from $5 to $6.50 per month for optional cloud features
|
| 34 |
+
• New annual tier of $65 per year
|
| 35 |
+
• Opinions on price fairness and potential future donations or donation drives
|
| 36 |
+
• Discussion of heavy use of Home Assistant in multiple locations (RV and studio)
|
| 37 |
+
• Thoughts on sustainability of current project and desire to see it succeed
|
| 38 |
+
• Idea of a plan that would allow connecting two Home Assistant instances for $9 per month
|
| 39 |
+
• Hiring of two new individuals working on different aspects of Home Assistant, including content creation
|
| 40 |
+
• Concerns about direct involvement in content creation by the project itself
|
| 41 |
+
• Home Assistant release discussion
|
| 42 |
+
• Price increase grandfathering for existing accounts
|
| 43 |
+
• New features in latest Home Assistant release (backup size display, Apple TV integration updates)
|
| 44 |
+
• Google Assistant integration with local fulfillment
|
| 45 |
+
• Delayed Home Assistant Yellow/Amber update timeline
|
| 46 |
+
• Promotion of Talescale.com and its benefits for self-hosted devices
|
| 47 |
+
• The user has a positive experience with Talescale, using it to connect to their system through a dedicated IP address and DNS feature.
|
| 48 |
+
• The user discusses balancing progress and perfection in self-hosting, citing the importance of documentation to revisit projects later.
|
| 49 |
+
• The user shares their personal experience of overlearning and forgetting information, leading to the realization that documenting knowledge at peak is essential.
|
| 50 |
+
• Documentation is emphasized as crucial for future reference and revisiting projects.
|
| 51 |
+
• The conversation touches on the topic of retaining information and expertise, with the user wondering how others (like Wendell) can recall complex details.
|
| 52 |
+
• Memories and recall
|
| 53 |
+
• Documenting shortcomings and setup to gain clarity
|
| 54 |
+
• Analysis paralysis and procrastination
|
| 55 |
+
• Learning through making mistakes and failing faster
|
| 56 |
+
• Importance of starting small and building on real problems
|
| 57 |
+
• Navigating complex decisions and trade-offs in projects and infrastructure
|
| 58 |
+
• The speaker is discussing how to automate tasks
|
| 59 |
+
• They mention a popular deploy matrix on a system using Ansible and consider using it in the future
|
| 60 |
+
• The conversation takes an unrelated turn when one of them mentions eating their first PB&J sandwich
|
| 61 |
+
• Details about the sandwich are discussed, including type of bread, peanut butter, jelly, and ratio of ingredients
|
| 62 |
+
• Making a peanut butter and jelly sandwich
|
| 63 |
+
• Discussing the optimal thickness of PB and J layers
|
| 64 |
+
• Measuring jam thickness (37 microns)
|
| 65 |
+
• Comparing American measurement systems to international standards
|
| 66 |
+
• Toasting techniques for elevating the sandwich experience
|
| 67 |
+
• Reviewing the benefits of the sandwich (delicious, budget-friendly, quick to make)
|
| 68 |
+
• Discussion about not being able to attend an event or activity
|
| 69 |
+
• Mention of tactical pants and their benefits, including phone storage capacity and wallet placement
|
| 70 |
+
• Comparison between Subsonic and Jellyfin self-hosted music options
|
| 71 |
+
• Recommendation for using a mobile media server during a trip with unreliable cell service
|
| 72 |
+
• Discussion of setting up a quick and dirty mobile media server using Raspberry Pis and USB hard drives
|
| 73 |
+
• Portable power units for charging devices while driving
|
| 74 |
+
• LTE routers for internet access during the trip
|
| 75 |
+
• Networking equipment to connect devices to the TV
|
| 76 |
+
• Power options for the Raspberry Pi, including USB storage with ButterFS
|
| 77 |
+
• Alternative solutions such as a laptop or tablet for simplicity
|
| 78 |
+
• Discussing media streaming options for a van without TV or tablet
|
| 79 |
+
• Using an iPad with speakers and Plex sync for video playback
|
| 80 |
+
• Infuse app on iPad for playing videos from USB storage
|
| 81 |
+
• Setting up Kodi or similar software on a Raspberry Pi as an alternative to a set-top box
|
| 82 |
+
• Planning an East Coast Spring Meetup in Raleigh, possibly at a brewery
|
| 83 |
+
• Discussion of the current weather in April
|
| 84 |
+
• Mention of Linux fest being cancelled and proposal to hold a Linux meetup in April instead
|
| 85 |
+
• Gratitude expressed for members, SREs, and sponsors (Linode and Tailscale) who support the show
|
| 86 |
+
• Information about membership benefits, including ad-free versions of the show and access to network shows
|
| 87 |
• Contact information for the host (self-hosted.show/contact, Twitter (@ironicbadger), Matrix (@Chris LAS))
|
65: Failing at Scale _summary.txt
CHANGED
|
@@ -1,60 +1,60 @@
|
|
| 1 |
-
• The user is experiencing issues with their Starlink connection in an area they frequently visit
|
| 2 |
-
• The user is located near the border of two service areas, resulting in inconsistent connectivity
|
| 3 |
-
• A website (satellitemap.space) was mentioned that shows the country divided into hexagons representing different Starlink cells
|
| 4 |
-
• The user notes that this representation may be oversimplified and actual cell boundaries are more nuanced
|
| 5 |
-
• The user discusses the issue of moving with Starlink, as it's designed to be stationary and can't accommodate frequent relocations
|
| 6 |
-
• The conversation also touches on the potential for a mobile version of Starlink and its implications for rural areas
|
| 7 |
-
• 5G technology is mentioned as another option that could potentially compete with or complement Starlink in terms of connectivity
|
| 8 |
-
• Government contract worker lives on a boat and uses 4G
|
| 9 |
-
• RV owner struggles with integrating Home Assistant for their vehicle
|
| 10 |
-
• Z-Wave support in Home Assistant will be deprecated due to Python version updates
|
| 11 |
-
• Migrating to Z-Wave.js has been problematic and may require re-pairing devices one by one
|
| 12 |
-
• Matter protocol is expected to arrive soon, but Home Assistant's planned deprecation of Z-Wave support may make it difficult for users to wait
|
| 13 |
-
• Mixed messaging from developers about recommended upgrades to Home Assistant
|
| 14 |
-
• Breaking changes causing user fatigue and hesitation to upgrade
|
| 15 |
-
• Comparison of Home Assistant's complexity to other smart home systems like Apple's HomeKit
|
| 16 |
-
• Discussion on the need for better documentation, education, and accessibility for users
|
| 17 |
-
• Acknowledgment that Home Assistant's modular design is a strength, but also a challenge
|
| 18 |
-
• Hope for future improvements in automation and user experience as the project matures
|
| 19 |
-
• Recognition of the importance of considering the needs of new users who will arrive with hardware devices
|
| 20 |
-
• Home Assistant compatibility with various devices and platforms
|
| 21 |
-
• Comparison between Apple, Echo, Google smart home systems
|
| 22 |
-
• Maintenance and updating of Home Assistant Core and its impact on security
|
| 23 |
-
• Linode cloud services and their benefits for hosting Home Assistant
|
| 24 |
-
• TrueNAS Scale release and its shift from FreeBSD to Debian 11
|
| 25 |
-
• TrueNAS product still focuses on ZFS as primary storage file system
|
| 26 |
-
• Can scale out storage across multiple systems with Gluster and Helm management
|
| 27 |
-
• Use case is for companies that need high-performance storage, potentially larger than home users or small businesses
|
| 28 |
-
• May target companies with similar needs to Linus Media Group, such as KVM virtualization and GPU pass-through
|
| 29 |
-
• Comparison made to Unraid, another popular NAS software option
|
| 30 |
-
• The speaker is discussing a local backup system using TrueNAS Scale on a LAN box to duplicate a ZFS array between two locations in their home.
|
| 31 |
-
• The speaker installed TrueNAS Scale and noticed an available update, but the update also required a significant amount of additional updates (2GB).
|
| 32 |
-
• The speaker encountered issues with importing a ZFS pool after updating, which seemed to resolve itself after a reboot.
|
| 33 |
-
• The speaker experienced further difficulties attempting to import the pool via the command line, requiring multiple reboots and attempts.
|
| 34 |
-
• The speaker expresses frustration with the lack of documentation and support for TrueNAS Scale.
|
| 35 |
-
• The speaker returns to using Proxmox after struggling with TrueNAS scale
|
| 36 |
-
• They prefer simple and basic setups, managing them with Ansible for ease of recovery from failure
|
| 37 |
-
• Tailscale is mentioned as a zero-config VPN solution for secure remote access to devices and servers
|
| 38 |
-
• A listener asks about maintaining Nextcloud in a home lab, seeking advice on monitoring and security measures
|
| 39 |
-
• The speaker advises loading only necessary apps in Nextcloud and double-checking their usage
|
| 40 |
-
• Importance of two-factor authentication for Nextcloud
|
| 41 |
-
• Keeping Nextcloud up-to-date with regular updates and SSL enabled
|
| 42 |
-
• Challenges of updating multiple instances of Nextcloud
|
| 43 |
-
• Using containers (e.g. Docker Compose) for repeatable deployment methods
|
| 44 |
-
• Deploying Nextcloud using different methods (Snap, container, host)
|
| 45 |
-
• Need to keep track of deployment settings to avoid data loss
|
| 46 |
-
• Unraid as a GUI-based option for containerization and self-hosting
|
| 47 |
-
• Unraid and its simplicity in data management
|
| 48 |
-
• The community support for Unraid, including YouTube tutorials
|
| 49 |
-
• Potential drawbacks of Unraid as user complexity increases
|
| 50 |
-
• Alternative options for managing disks and applications, such as FreeNAS Scale and Docker Desktop on Mac OS
|
| 51 |
-
• The possibility of using Home Assistant for app management and containerization
|
| 52 |
-
• Other alternatives like CentOS or Ubuntu with Cockpit, and the importance of aligning with one's values in software choice
|
| 53 |
-
• Plans for a JB East Coast meetup and potential crowdfunding options
|
| 54 |
-
• Planning a meetup in Raleigh, NC on April 9th
|
| 55 |
-
• Proposed event will take place at Prime Barbecue and Oak City Brewing
|
| 56 |
-
• Details to be posted on meetup.com closer to the time
|
| 57 |
-
• COVID-safe location with outdoor space for gathering
|
| 58 |
-
• Weather in Raleigh expected to be pleasant in April
|
| 59 |
-
• Invitation extended to join the meetup and Jupyter Broadcasting group
|
| 60 |
• Sponsorship and support options mentioned, including Tailscale and network support at jupiter.party
|
|
|
|
| 1 |
+
• The user is experiencing issues with their Starlink connection in an area they frequently visit
|
| 2 |
+
• The user is located near the border of two service areas, resulting in inconsistent connectivity
|
| 3 |
+
• A website (satellitemap.space) was mentioned that shows the country divided into hexagons representing different Starlink cells
|
| 4 |
+
• The user notes that this representation may be oversimplified and actual cell boundaries are more nuanced
|
| 5 |
+
• The user discusses the issue of moving with Starlink, as it's designed to be stationary and can't accommodate frequent relocations
|
| 6 |
+
• The conversation also touches on the potential for a mobile version of Starlink and its implications for rural areas
|
| 7 |
+
• 5G technology is mentioned as another option that could potentially compete with or complement Starlink in terms of connectivity
|
| 8 |
+
• Government contract worker lives on a boat and uses 4G
|
| 9 |
+
• RV owner struggles with integrating Home Assistant for their vehicle
|
| 10 |
+
• Z-Wave support in Home Assistant will be deprecated due to Python version updates
|
| 11 |
+
• Migrating to Z-Wave.js has been problematic and may require re-pairing devices one by one
|
| 12 |
+
• Matter protocol is expected to arrive soon, but Home Assistant's planned deprecation of Z-Wave support may make it difficult for users to wait
|
| 13 |
+
• Mixed messaging from developers about recommended upgrades to Home Assistant
|
| 14 |
+
• Breaking changes causing user fatigue and hesitation to upgrade
|
| 15 |
+
• Comparison of Home Assistant's complexity to other smart home systems like Apple's HomeKit
|
| 16 |
+
• Discussion on the need for better documentation, education, and accessibility for users
|
| 17 |
+
• Acknowledgment that Home Assistant's modular design is a strength, but also a challenge
|
| 18 |
+
• Hope for future improvements in automation and user experience as the project matures
|
| 19 |
+
• Recognition of the importance of considering the needs of new users who will arrive with hardware devices
|
| 20 |
+
• Home Assistant compatibility with various devices and platforms
|
| 21 |
+
• Comparison between Apple, Echo, Google smart home systems
|
| 22 |
+
• Maintenance and updating of Home Assistant Core and its impact on security
|
| 23 |
+
• Linode cloud services and their benefits for hosting Home Assistant
|
| 24 |
+
• TrueNAS Scale release and its shift from FreeBSD to Debian 11
|
| 25 |
+
• TrueNAS product still focuses on ZFS as primary storage file system
|
| 26 |
+
• Can scale out storage across multiple systems with Gluster and Helm management
|
| 27 |
+
• Use case is for companies that need high-performance storage, potentially larger than home users or small businesses
|
| 28 |
+
• May target companies with similar needs to Linus Media Group, such as KVM virtualization and GPU pass-through
|
| 29 |
+
• Comparison made to Unraid, another popular NAS software option
|
| 30 |
+
• The speaker is discussing a local backup system using TrueNAS Scale on a LAN box to duplicate a ZFS array between two locations in their home.
|
| 31 |
+
• The speaker installed TrueNAS Scale and noticed an available update, but the update also required a significant amount of additional updates (2GB).
|
| 32 |
+
• The speaker encountered issues with importing a ZFS pool after updating, which seemed to resolve itself after a reboot.
|
| 33 |
+
• The speaker experienced further difficulties attempting to import the pool via the command line, requiring multiple reboots and attempts.
|
| 34 |
+
• The speaker expresses frustration with the lack of documentation and support for TrueNAS Scale.
|
| 35 |
+
• The speaker returns to using Proxmox after struggling with TrueNAS scale
|
| 36 |
+
• They prefer simple and basic setups, managing them with Ansible for ease of recovery from failure
|
| 37 |
+
• Tailscale is mentioned as a zero-config VPN solution for secure remote access to devices and servers
|
| 38 |
+
• A listener asks about maintaining Nextcloud in a home lab, seeking advice on monitoring and security measures
|
| 39 |
+
• The speaker advises loading only necessary apps in Nextcloud and double-checking their usage
|
| 40 |
+
• Importance of two-factor authentication for Nextcloud
|
| 41 |
+
• Keeping Nextcloud up-to-date with regular updates and SSL enabled
|
| 42 |
+
• Challenges of updating multiple instances of Nextcloud
|
| 43 |
+
• Using containers (e.g. Docker Compose) for repeatable deployment methods
|
| 44 |
+
• Deploying Nextcloud using different methods (Snap, container, host)
|
| 45 |
+
• Need to keep track of deployment settings to avoid data loss
|
| 46 |
+
• Unraid as a GUI-based option for containerization and self-hosting
|
| 47 |
+
• Unraid and its simplicity in data management
|
| 48 |
+
• The community support for Unraid, including YouTube tutorials
|
| 49 |
+
• Potential drawbacks of Unraid as user complexity increases
|
| 50 |
+
• Alternative options for managing disks and applications, such as FreeNAS Scale and Docker Desktop on Mac OS
|
| 51 |
+
• The possibility of using Home Assistant for app management and containerization
|
| 52 |
+
• Other alternatives like CentOS or Ubuntu with Cockpit, and the importance of aligning with one's values in software choice
|
| 53 |
+
• Plans for a JB East Coast meetup and potential crowdfunding options
|
| 54 |
+
• Planning a meetup in Raleigh, NC on April 9th
|
| 55 |
+
• Proposed event will take place at Prime Barbecue and Oak City Brewing
|
| 56 |
+
• Details to be posted on meetup.com closer to the time
|
| 57 |
+
• COVID-safe location with outdoor space for gathering
|
| 58 |
+
• Weather in Raleigh expected to be pleasant in April
|
| 59 |
+
• Invitation extended to join the meetup and Jupyter Broadcasting group
|
| 60 |
• Sponsorship and support options mentioned, including Tailscale and network support at jupiter.party
|
66: Mmm. Pi. _summary.txt
CHANGED
|
@@ -1,92 +1,92 @@
|
|
| 1 |
-
• The host attended a meetup event in Raleigh and tried barbecue at the new meetup spot.
|
| 2 |
-
• The event location was Nightdale Station, which has a park with a brewery, Texas-style barbecue joint, and local brewing company.
|
| 3 |
-
• The host and his co-hosts are attending an upcoming East Coast meetup on April 9th in Raleigh (or more specifically, Nightdale).
|
| 4 |
-
• The Raspberry Pi is celebrating its 10-year anniversary and the host reflects on how it helped him get involved with Linux.
|
| 5 |
-
• Eben Upton, the founder of Raspberry Pi, launched the project expecting to sell only 1,000-5,000 units but has since sold millions.
|
| 6 |
-
• Discussion of the Raspberry Pi's evolution over the past 10 years
|
| 7 |
-
• The Pi's initial purpose in schools, its current status as a hobbyist-grade tinkerer device, and its widespread adoption
|
| 8 |
-
• Eben Upton's mention of the Foundation putting two Pis on the International Space Station and other products using Pis in space
|
| 9 |
-
• Criticism that the Raspberry Pi Foundation is not necessarily beholden to Linux community expectations, which has led to some issues with code drops and repository management
|
| 10 |
-
• Discussion of the Pi's hardware being integrated into the mainline kernel and the importance of this development
|
| 11 |
-
• Concerns about energy use and potential cost savings by optimizing setup configuration
|
| 12 |
-
• Energy usage of old computers and hard drives
|
| 13 |
-
• Comparison of energy prices (15p vs 50-60p per kilowatt hour)
|
| 14 |
-
• Considerations for Raspberry Pi energy efficiency
|
| 15 |
-
• Optimization for power savings over performance
|
| 16 |
-
• Re-evaluation of storage needs and requirements
|
| 17 |
-
• Simplification of systems with lower power consumption in mind
|
| 18 |
-
• Reassessing personal performance requirements and priorities
|
| 19 |
-
• Comparison of past computing capabilities (e.g. x86 box vs Raspberry Pi)
|
| 20 |
-
• Discussing the cost and trade-offs of digital storage and data management (e.g. hard drive size, energy consumption)
|
| 21 |
-
• Introducing Linode.com as a cloud hosting service with fast and reliable options
|
| 22 |
-
• Exploring different plans and features available on Linode, including MVME PCIe storage and AMD epic CPUs
|
| 23 |
-
• UI and dashboard features for system information
|
| 24 |
-
• Recommendation for Wi-Fi based leak detection sensors
|
| 25 |
-
• Comparison of Z-Wave and Zigbee options vs. Wi-Fi
|
| 26 |
-
• Discussion of energy usage with Wi-Fi devices
|
| 27 |
-
• Review of a specific Zigbee water sensor model
|
| 28 |
-
• Promotion of supporting the show through subscription or donation
|
| 29 |
-
• Discussion of Raspberry Pi projects, including a media center PC use case
|
| 30 |
-
• The speaker talks about hooking up a device to a monitor in HDMI and using it for countdown clocks and IRC chatrooms
|
| 31 |
-
• The Raspberry Pi was used for this purpose and became the basis for open source media center OSMC
|
| 32 |
-
• A new case called the Eon, made by the company that makes the Argon case, is discussed on Kickstarter
|
| 33 |
-
• The Eon case has a cyberpunk-inspired design with space-grade aluminum and can hold four SATA hard drives
|
| 34 |
-
• The speaker mentions that the Eon case looks great but is pricey, costing $730 without the Raspberry Pi.
|
| 35 |
-
• Cost of a budget machine with Pi and drives adds up to $1,500
|
| 36 |
-
• Consideration of long-term power savings (80% less) over 5 years
|
| 37 |
-
• The Raspberry Pi 4 compute module is seen as an upgrade option
|
| 38 |
-
• Carrier boards offer more connectivity options, such as PCI slots and SATA ports
|
| 39 |
-
• The Argon Pi NAS should be its own carrier board with future-proofed components.
|
| 40 |
-
• The speaker mentions that the GPIO pins on Raspberry Pi devices have remained largely unchanged since the first model.
|
| 41 |
-
• They discuss the potential of the CM4 (Compute Module 4) and its application in various markets.
|
| 42 |
-
• The speaker states that the current supply chain shortage has hindered adoption of the CM4, making it difficult to obtain.
|
| 43 |
-
• They mention that they will not build a Pi-based server system without the CM4 and prefer using CM4 over standard Raspberry Pi for carrier boards.
|
| 44 |
-
• The conversation turns to the personal collections of Raspberry Pis, with both speakers discussing their own numbers of devices.
|
| 45 |
-
• The idea of building a giant Pi cluster is proposed.
|
| 46 |
-
• The use case of Raspberry Pis as Kubernetes clusters like compute units is discussed.
|
| 47 |
-
• Provisioning devices at scale
|
| 48 |
-
• Raspberry Pi racks and their use cases
|
| 49 |
-
• Kubernetes training and provisionning machines with a few clicks
|
| 50 |
-
• Comparing the cost of using Raspberry Pis versus x86 boxes
|
| 51 |
-
• Bare metal provisioning and fun projects with Raspberry Pis
|
| 52 |
-
• The genesis of the Heimdall Docker dashboard
|
| 53 |
-
• The speaker mentions using a home dashboard on their personal server and the proliferation of home dashboards in recent years
|
| 54 |
-
• They mention setting up a Homer dashboard for their father, which allows him to access various services with ease
|
| 55 |
-
• The speaker discusses other dashboard options, including Flame, which is highly customizable but lacks interactivity, and Organizer, which organizes apps behind tabs
|
| 56 |
-
• They express concerns about technical debt and configuration drift affecting dashboard effectiveness
|
| 57 |
-
• The speaker highlights the advantages of Flame's integration with Docker engine for live updates based on running containers
|
| 58 |
-
• Tailscale is a zero-configuration VPN that installs on any device in minutes.
|
| 59 |
-
• It's easy to manage firewall rules and access devices from anywhere.
|
| 60 |
-
• The speaker uses Tailscale to connect their devices directly, using WireGuard and noise protocol encryption.
|
| 61 |
-
• They appreciate the ease of creating a secure mesh network between servers, computers, and cloud instances.
|
| 62 |
-
• Tailscale allows remote access with consistent IP addresses and device authentication.
|
| 63 |
-
• Tailscale's flexibility in managing machines remotely
|
| 64 |
-
• Ability to deauthorize machines without physical presence
|
| 65 |
-
• DNS friendliness of Tailscale for easy network setup
|
| 66 |
-
• User experience with camera systems, including Blue Iris
|
| 67 |
-
• Importance of monitoring and backups, particularly for server snapshots
|
| 68 |
-
• Discussion of a listener's fix for damaged wiring in a project
|
| 69 |
-
• The user is seeking a tool to read snapshot logs and send an email in case of an error
|
| 70 |
-
• Health checks.io is mentioned as a possible solution for monitoring cron jobs and detecting errors
|
| 71 |
-
• The user describes how health checks can be used to ping a server, append logs, and monitor job duration
|
| 72 |
-
• The self-hosted version of health checks is also discussed
|
| 73 |
-
• The importance of keeping the system simple and not over-complicating it with unnecessary features
|
| 74 |
-
• A listener, Norm, writes in to express appreciation for the show and offers support by purchasing a membership.
|
| 75 |
-
• Discussing the pros and cons of waiting for Matter, a new smart home standard
|
| 76 |
-
• Failing at scale episode mentioning Home Assistant and Z-Wave breaking changes
|
| 77 |
-
• Waiting for Matter vs buying Zigbee devices now
|
| 78 |
-
• Compatibility between Matter and existing Zigbee devices
|
| 79 |
-
• Using Home Kit as an alternative to Zigbee or Matter
|
| 80 |
-
• Importance of choosing a reliable Zigbee bridge
|
| 81 |
-
• Researching upgradable Zigbee controllers to future-proof smart home setup
|
| 82 |
-
• Z-Wave migration issues in Home Assistant
|
| 83 |
-
• Timing of Z-Wave JS transition causing problems for early adopters
|
| 84 |
-
• Use of Z-Wave devices still viable and supported by Home Assistant team
|
| 85 |
-
• RV integration with Home Assistant (Lady Jupes)
|
| 86 |
-
• Potential episode idea: detailing setup and devices used in RV
|
| 87 |
-
• Future self-hosted show topics, projects, and contact information
|
| 88 |
-
• Price of fish and its relation to a British film
|
| 89 |
-
• Becoming a network member for ad-free access to various shows and live streams
|
| 90 |
-
• Supporting independent podcasting at jupiter.party
|
| 91 |
-
• Upcoming meetup event on April 9th, an East Coast mystery tour
|
| 92 |
• Social media presence: Twitter, Telegram group, and website
|
|
|
|
| 1 |
+
• The host attended a meetup event in Raleigh and tried barbecue at the new meetup spot.
|
| 2 |
+
• The event location was Nightdale Station, which has a park with a brewery, Texas-style barbecue joint, and local brewing company.
|
| 3 |
+
• The host and his co-hosts are attending an upcoming East Coast meetup on April 9th in Raleigh (or more specifically, Nightdale).
|
| 4 |
+
• The Raspberry Pi is celebrating its 10-year anniversary and the host reflects on how it helped him get involved with Linux.
|
| 5 |
+
• Eben Upton, the founder of Raspberry Pi, launched the project expecting to sell only 1,000-5,000 units but has since sold millions.
|
| 6 |
+
• Discussion of the Raspberry Pi's evolution over the past 10 years
|
| 7 |
+
• The Pi's initial purpose in schools, its current status as a hobbyist-grade tinkerer device, and its widespread adoption
|
| 8 |
+
• Eben Upton's mention of the Foundation putting two Pis on the International Space Station and other products using Pis in space
|
| 9 |
+
• Criticism that the Raspberry Pi Foundation is not necessarily beholden to Linux community expectations, which has led to some issues with code drops and repository management
|
| 10 |
+
• Discussion of the Pi's hardware being integrated into the mainline kernel and the importance of this development
|
| 11 |
+
• Concerns about energy use and potential cost savings by optimizing setup configuration
|
| 12 |
+
• Energy usage of old computers and hard drives
|
| 13 |
+
• Comparison of energy prices (15p vs 50-60p per kilowatt hour)
|
| 14 |
+
• Considerations for Raspberry Pi energy efficiency
|
| 15 |
+
• Optimization for power savings over performance
|
| 16 |
+
• Re-evaluation of storage needs and requirements
|
| 17 |
+
• Simplification of systems with lower power consumption in mind
|
| 18 |
+
• Reassessing personal performance requirements and priorities
|
| 19 |
+
• Comparison of past computing capabilities (e.g. x86 box vs Raspberry Pi)
|
| 20 |
+
• Discussing the cost and trade-offs of digital storage and data management (e.g. hard drive size, energy consumption)
|
| 21 |
+
• Introducing Linode.com as a cloud hosting service with fast and reliable options
|
| 22 |
+
• Exploring different plans and features available on Linode, including MVME PCIe storage and AMD epic CPUs
|
| 23 |
+
• UI and dashboard features for system information
|
| 24 |
+
• Recommendation for Wi-Fi based leak detection sensors
|
| 25 |
+
• Comparison of Z-Wave and Zigbee options vs. Wi-Fi
|
| 26 |
+
• Discussion of energy usage with Wi-Fi devices
|
| 27 |
+
• Review of a specific Zigbee water sensor model
|
| 28 |
+
• Promotion of supporting the show through subscription or donation
|
| 29 |
+
• Discussion of Raspberry Pi projects, including a media center PC use case
|
| 30 |
+
• The speaker talks about hooking up a device to a monitor in HDMI and using it for countdown clocks and IRC chatrooms
|
| 31 |
+
• The Raspberry Pi was used for this purpose and became the basis for open source media center OSMC
|
| 32 |
+
• A new case called the Eon, made by the company that makes the Argon case, is discussed on Kickstarter
|
| 33 |
+
• The Eon case has a cyberpunk-inspired design with space-grade aluminum and can hold four SATA hard drives
|
| 34 |
+
• The speaker mentions that the Eon case looks great but is pricey, costing $730 without the Raspberry Pi.
|
| 35 |
+
• Cost of a budget machine with Pi and drives adds up to $1,500
|
| 36 |
+
• Consideration of long-term power savings (80% less) over 5 years
|
| 37 |
+
• The Raspberry Pi 4 compute module is seen as an upgrade option
|
| 38 |
+
• Carrier boards offer more connectivity options, such as PCI slots and SATA ports
|
| 39 |
+
• The Argon Pi NAS should be its own carrier board with future-proofed components.
|
| 40 |
+
• The speaker mentions that the GPIO pins on Raspberry Pi devices have remained largely unchanged since the first model.
|
| 41 |
+
• They discuss the potential of the CM4 (Compute Module 4) and its application in various markets.
|
| 42 |
+
• The speaker states that the current supply chain shortage has hindered adoption of the CM4, making it difficult to obtain.
|
| 43 |
+
• They mention that they will not build a Pi-based server system without the CM4 and prefer using CM4 over standard Raspberry Pi for carrier boards.
|
| 44 |
+
• The conversation turns to the personal collections of Raspberry Pis, with both speakers discussing their own numbers of devices.
|
| 45 |
+
• The idea of building a giant Pi cluster is proposed.
|
| 46 |
+
• The use case of Raspberry Pis as Kubernetes clusters like compute units is discussed.
|
| 47 |
+
• Provisioning devices at scale
|
| 48 |
+
• Raspberry Pi racks and their use cases
|
| 49 |
+
• Kubernetes training and provisionning machines with a few clicks
|
| 50 |
+
• Comparing the cost of using Raspberry Pis versus x86 boxes
|
| 51 |
+
• Bare metal provisioning and fun projects with Raspberry Pis
|
| 52 |
+
• The genesis of the Heimdall Docker dashboard
|
| 53 |
+
• The speaker mentions using a home dashboard on their personal server and the proliferation of home dashboards in recent years
|
| 54 |
+
• They mention setting up a Homer dashboard for their father, which allows him to access various services with ease
|
| 55 |
+
• The speaker discusses other dashboard options, including Flame, which is highly customizable but lacks interactivity, and Organizer, which organizes apps behind tabs
|
| 56 |
+
• They express concerns about technical debt and configuration drift affecting dashboard effectiveness
|
| 57 |
+
• The speaker highlights the advantages of Flame's integration with Docker engine for live updates based on running containers
|
| 58 |
+
• Tailscale is a zero-configuration VPN that installs on any device in minutes.
|
| 59 |
+
• It's easy to manage firewall rules and access devices from anywhere.
|
| 60 |
+
• The speaker uses Tailscale to connect their devices directly, using WireGuard and noise protocol encryption.
|
| 61 |
+
• They appreciate the ease of creating a secure mesh network between servers, computers, and cloud instances.
|
| 62 |
+
• Tailscale allows remote access with consistent IP addresses and device authentication.
|
| 63 |
+
• Tailscale's flexibility in managing machines remotely
|
| 64 |
+
• Ability to deauthorize machines without physical presence
|
| 65 |
+
• DNS friendliness of Tailscale for easy network setup
|
| 66 |
+
• User experience with camera systems, including Blue Iris
|
| 67 |
+
• Importance of monitoring and backups, particularly for server snapshots
|
| 68 |
+
• Discussion of a listener's fix for damaged wiring in a project
|
| 69 |
+
• The user is seeking a tool to read snapshot logs and send an email in case of an error
|
| 70 |
+
• Health checks.io is mentioned as a possible solution for monitoring cron jobs and detecting errors
|
| 71 |
+
• The user describes how health checks can be used to ping a server, append logs, and monitor job duration
|
| 72 |
+
• The self-hosted version of health checks is also discussed
|
| 73 |
+
• The importance of keeping the system simple and not over-complicating it with unnecessary features
|
| 74 |
+
• A listener, Norm, writes in to express appreciation for the show and offers support by purchasing a membership.
|
| 75 |
+
• Discussing the pros and cons of waiting for Matter, a new smart home standard
|
| 76 |
+
• Failing at scale episode mentioning Home Assistant and Z-Wave breaking changes
|
| 77 |
+
• Waiting for Matter vs buying Zigbee devices now
|
| 78 |
+
• Compatibility between Matter and existing Zigbee devices
|
| 79 |
+
• Using Home Kit as an alternative to Zigbee or Matter
|
| 80 |
+
• Importance of choosing a reliable Zigbee bridge
|
| 81 |
+
• Researching upgradable Zigbee controllers to future-proof smart home setup
|
| 82 |
+
• Z-Wave migration issues in Home Assistant
|
| 83 |
+
• Timing of Z-Wave JS transition causing problems for early adopters
|
| 84 |
+
• Use of Z-Wave devices still viable and supported by Home Assistant team
|
| 85 |
+
• RV integration with Home Assistant (Lady Jupes)
|
| 86 |
+
• Potential episode idea: detailing setup and devices used in RV
|
| 87 |
+
• Future self-hosted show topics, projects, and contact information
|
| 88 |
+
• Price of fish and its relation to a British film
|
| 89 |
+
• Becoming a network member for ad-free access to various shows and live streams
|
| 90 |
+
• Supporting independent podcasting at jupiter.party
|
| 91 |
+
• Upcoming meetup event on April 9th, an East Coast mystery tour
|
| 92 |
• Social media presence: Twitter, Telegram group, and website
|
67: The No Container Theory _summary.txt
CHANGED
|
@@ -1,103 +1,103 @@
|
|
| 1 |
-
• East Coast meetup has 69 people signed up so far
|
| 2 |
-
• Concerns about barbecue restaurant having enough meat for attendees
|
| 3 |
-
• Solutions being considered to mitigate potential shortages, including preordering on the website and providing numbers beforehand
|
| 4 |
-
• Importance of accurate headcount for planning purposes
|
| 5 |
-
• Upcoming meetup in Raleigh, North Carolina on April 9th
|
| 6 |
-
• Discussion of Docker performance issues on M1 Silicon Macs
|
| 7 |
-
• Asahi Linux team's discovery about Apple's NVMe drivers being slow on macOS
|
| 8 |
-
• Potential fix for Docker performance issue discovered by a community member and implemented by the Docker team
|
| 9 |
-
• Linux installation on M1 Macs can be straightforward with minimal file system problems
|
| 10 |
-
• Early benchmarks show good performance, except for GPU-heavy tasks
|
| 11 |
-
• Jeff Geerling's video comparing power consumption between Ryzen and Mac Studio systems shows interesting results
|
| 12 |
-
• Mac Studio has a significantly lower idle power draw (6 watts) compared to Ryzen systems (38-40 watts)
|
| 13 |
-
• Discussion about fsync changes in Docker Desktop 2 and potential impact on data integrity
|
| 14 |
-
• macOS "cheats" by only flushing writes to the drive itself, rather than also updating the file system tables
|
| 15 |
-
• The user has experienced no issues with APFS and praises Apple's migration process
|
| 16 |
-
• The user notes that APFS still lacks widespread adoption and production-grade usage in edge cases
|
| 17 |
-
• The user expresses a desire to see more users deploying APFS in their own environments for it to be considered truly safe and reliable
|
| 18 |
-
• The user recommends Linode as a cloud computing platform for server deployment, citing its ease of use and lack of lock-in
|
| 19 |
-
• The user discloses a sponsorship arrangement with Linode and provides a promo code (linode.com/SSH)
|
| 20 |
-
• The narrator discusses using Paperless-NG to manage digital documents and the recent development of a new project called Paperless-NGX.
|
| 21 |
-
• Jonas Winkler took over the original Paperless project, but it was abandoned, leading to the creation of Paperless-NGX as a community-driven fork.
|
| 22 |
-
• The current state of Paperless-NGX is that it has dropped support for Python 3.7 and Ansible playbooks, but updated documentation and containers.
|
| 23 |
-
• The community is looking for contributors to help with ongoing maintenance and development, including updating Ansible playbook support.
|
| 24 |
-
• The project is open-source and self-hosted, allowing users to escape the issues that come with commercial services going down.
|
| 25 |
-
• Paperless NGX system
|
| 26 |
-
• Implementing the system for tax season and expense tracking
|
| 27 |
-
• Using scan apps to upload documents
|
| 28 |
-
• Setting up ingestion rules for automatic tagging
|
| 29 |
-
• Streamlining processes with Paperless, such as downloading PDFs and logging into separate systems
|
| 30 |
-
• Matter Group's announced delay of the Matter Standard
|
| 31 |
-
• Industry unity expected at launch
|
| 32 |
-
• Chip shortages affecting smart home devices
|
| 33 |
-
• Delayed release of Matter protocol causing uncertainty
|
| 34 |
-
• Z-Wave integration issues and migration problems
|
| 35 |
-
• Smart home setup disaster due to hardware and software incompatibilities
|
| 36 |
-
• Advice to buy existing smart home devices rather than waiting for new technology
|
| 37 |
-
• The speaker is considering redoing a Z-Wave JS migration due to the amount of work involved
|
| 38 |
-
• They compare this situation to implementing a VLAN setup in their home, which would require a lot of effort and potentially lead to procrastination
|
| 39 |
-
• The speaker recommends using tailscale.com/self-hosted for Zero Config VPN solutions that support up to 20 devices and can manage firewall rules
|
| 40 |
-
• The benefits of tailscale include simplicity in setting up a mesh network between machines and supporting two-factor authentication, single sign-on, and the noise protocol used by WireGuard
|
| 41 |
-
• Setting up bookmarks for Tailscale
|
| 42 |
-
• Discussing the power of using Tailscale with multiple machines
|
| 43 |
-
• Mentioning a potential new direction for duplicating (dupes) setups, specifically "no container theory"
|
| 44 |
-
• Recapping current setup on Raspberry Pi 4s with Ubuntu 2004 and Home Assistant
|
| 45 |
-
• Outlining issues with current setup, such as health states preventing updates
|
| 46 |
-
• Considering alternative directions for future setup, including x86 machines with Proxmox
|
| 47 |
-
• Running Home Assistant in a dedicated virtual machine
|
| 48 |
-
• Considering an M1 Mac Mini as a headless home server running Linux
|
| 49 |
-
• Identifying two main problems to solve with this next round: performance and reproducibility
|
| 50 |
-
• Desiring reproducibility due to the difficulty of remembering current setup and potential future rebuilds
|
| 51 |
-
• Evaluating Ansible for config management, but ultimately deciding against it in favor of Nix
|
| 52 |
-
• Nix provides a way to build systems from config files
|
| 53 |
-
• Using Nix OS is similar to using Nix as a package manager, but it offers more control over the system
|
| 54 |
-
• Nix OS can build entire systems, including containers, with simple syntax
|
| 55 |
-
• The Nix system figures out software dependencies and services automatically
|
| 56 |
-
• Nix documentation provides reproducibility and ease of deployment
|
| 57 |
-
• Nix is useful for containerized systems, such as Home Assistant and Plex
|
| 58 |
-
• Nix allows for rolling updates and recreation of entire systems
|
| 59 |
-
• The benefits of using Nix OS for managing systems and dependencies
|
| 60 |
-
• Comparison between Nix OS and containerization (e.g. Docker)
|
| 61 |
-
• Use cases where Nix OS's ability to manage entire software environments is beneficial
|
| 62 |
-
• Concerns about the overhead of running an entire OS environment in a container
|
| 63 |
-
• Isolating data and application stuff with Nix
|
| 64 |
-
• Performance benefits of using M1 processors with Nix
|
| 65 |
-
• Availability of Nix OS on M1 Mini devices
|
| 66 |
-
• Comparison between Nix and container-based solutions (e.g. Ansible)
|
| 67 |
-
• Reproducibility and redeployment capabilities of Nix
|
| 68 |
-
• Ease of understanding and use of Nix's configuration language
|
| 69 |
-
• Discussion on using Nix as a package manager for Linux systems
|
| 70 |
-
• Comparison with Ansible and its role in deploying and managing systems
|
| 71 |
-
• Nix's version control and reproducibility features
|
| 72 |
-
• The potential future of Linux development and the adoption of Nix-like systems
|
| 73 |
-
• Red Hat's Core OS operating system and Fedora Core OS as counterpoints to Nix
|
| 74 |
-
• Upstream version of a system tried out
|
| 75 |
-
• Configuration is done declaratively and through an ignition config file
|
| 76 |
-
• NICs operate in a similar space to the operating system being read-only
|
| 77 |
-
• Rolling back to a specific snapshot can be simple with ZFS backend storage
|
| 78 |
-
• NICS has two methods: building and deploying without testing, or using a "build dash dash test" command that fails if it detects any issues
|
| 79 |
-
• Discussion of using Nix for home automation
|
| 80 |
-
• Comparison with Home Assistant core and potential minimal rebuild
|
| 81 |
-
• Consideration of switching to Node-RED for automation
|
| 82 |
-
• Transitioning to MQTT protocol
|
| 83 |
-
• Managing data silos and integrating various systems (e.g. Z-Wave JS) through MQTT
|
| 84 |
-
• Complexity of automations and programming logic
|
| 85 |
-
• Comparison of Home Assistant vs Node-Red for automation
|
| 86 |
-
• Use of MQTT protocol for power information from Victron system
|
| 87 |
-
• Desire to rebuild and migrate existing automation systems
|
| 88 |
-
• Plan to do a "bro build" episode with Wes at an RV
|
| 89 |
-
• Plans for episode 70
|
| 90 |
-
• Discussion about Panda Express and Chinese food preferences
|
| 91 |
-
• Correction on the Argon Aeon 4-Bay Raspberry Pi NAS case price
|
| 92 |
-
• Mention of temperature issues in the studio garage server room
|
| 93 |
-
• Introduction to a Wi-Fi sensor built by Gene using ESP home
|
| 94 |
-
• Home Assistant setup and monitoring
|
| 95 |
-
• Fever app for video recording and integration with Frigate and Home Assistant
|
| 96 |
-
• Bearded Tech's GitHub page and contribution to the community
|
| 97 |
-
• Coral AI USB sticks and their increasing price (over $200)
|
| 98 |
-
• Docker Compose for containerized applications
|
| 99 |
-
• New project being worked on is mentioned as good and GPL-licensed
|
| 100 |
-
• Host will be giving away Bitcoin to help with setting up Matrix
|
| 101 |
-
• Upcoming AMA session at jblive.tv, March 31st
|
| 102 |
-
• Mention of Fountain and its boost feature
|
| 103 |
• Event for meetup in Raleigh on April 9th
|
|
|
|
| 1 |
+
• East Coast meetup has 69 people signed up so far
|
| 2 |
+
• Concerns about barbecue restaurant having enough meat for attendees
|
| 3 |
+
• Solutions being considered to mitigate potential shortages, including preordering on the website and providing numbers beforehand
|
| 4 |
+
• Importance of accurate headcount for planning purposes
|
| 5 |
+
• Upcoming meetup in Raleigh, North Carolina on April 9th
|
| 6 |
+
• Discussion of Docker performance issues on M1 Silicon Macs
|
| 7 |
+
• Asahi Linux team's discovery about Apple's NVMe drivers being slow on macOS
|
| 8 |
+
• Potential fix for Docker performance issue discovered by a community member and implemented by the Docker team
|
| 9 |
+
• Linux installation on M1 Macs can be straightforward with minimal file system problems
|
| 10 |
+
• Early benchmarks show good performance, except for GPU-heavy tasks
|
| 11 |
+
• Jeff Geerling's video comparing power consumption between Ryzen and Mac Studio systems shows interesting results
|
| 12 |
+
• Mac Studio has a significantly lower idle power draw (6 watts) compared to Ryzen systems (38-40 watts)
|
| 13 |
+
• Discussion about fsync changes in Docker Desktop 2 and potential impact on data integrity
|
| 14 |
+
• macOS "cheats" by only flushing writes to the drive itself, rather than also updating the file system tables
|
| 15 |
+
• The user has experienced no issues with APFS and praises Apple's migration process
|
| 16 |
+
• The user notes that APFS still lacks widespread adoption and production-grade usage in edge cases
|
| 17 |
+
• The user expresses a desire to see more users deploying APFS in their own environments for it to be considered truly safe and reliable
|
| 18 |
+
• The user recommends Linode as a cloud computing platform for server deployment, citing its ease of use and lack of lock-in
|
| 19 |
+
• The user discloses a sponsorship arrangement with Linode and provides a promo code (linode.com/SSH)
|
| 20 |
+
• The narrator discusses using Paperless-NG to manage digital documents and the recent development of a new project called Paperless-NGX.
|
| 21 |
+
• Jonas Winkler took over the original Paperless project, but it was abandoned, leading to the creation of Paperless-NGX as a community-driven fork.
|
| 22 |
+
• The current state of Paperless-NGX is that it has dropped support for Python 3.7 and Ansible playbooks, but updated documentation and containers.
|
| 23 |
+
• The community is looking for contributors to help with ongoing maintenance and development, including updating Ansible playbook support.
|
| 24 |
+
• The project is open-source and self-hosted, allowing users to escape the issues that come with commercial services going down.
|
| 25 |
+
• Paperless NGX system
|
| 26 |
+
• Implementing the system for tax season and expense tracking
|
| 27 |
+
• Using scan apps to upload documents
|
| 28 |
+
• Setting up ingestion rules for automatic tagging
|
| 29 |
+
• Streamlining processes with Paperless, such as downloading PDFs and logging into separate systems
|
| 30 |
+
• Matter Group's announced delay of the Matter Standard
|
| 31 |
+
• Industry unity expected at launch
|
| 32 |
+
• Chip shortages affecting smart home devices
|
| 33 |
+
• Delayed release of Matter protocol causing uncertainty
|
| 34 |
+
• Z-Wave integration issues and migration problems
|
| 35 |
+
• Smart home setup disaster due to hardware and software incompatibilities
|
| 36 |
+
• Advice to buy existing smart home devices rather than waiting for new technology
|
| 37 |
+
• The speaker is considering redoing a Z-Wave JS migration due to the amount of work involved
|
| 38 |
+
• They compare this situation to implementing a VLAN setup in their home, which would require a lot of effort and potentially lead to procrastination
|
| 39 |
+
• The speaker recommends using tailscale.com/self-hosted for Zero Config VPN solutions that support up to 20 devices and can manage firewall rules
|
| 40 |
+
• The benefits of tailscale include simplicity in setting up a mesh network between machines and supporting two-factor authentication, single sign-on, and the noise protocol used by WireGuard
|
| 41 |
+
• Setting up bookmarks for Tailscale
|
| 42 |
+
• Discussing the power of using Tailscale with multiple machines
|
| 43 |
+
• Mentioning a potential new direction for duplicating (dupes) setups, specifically "no container theory"
|
| 44 |
+
• Recapping current setup on Raspberry Pi 4s with Ubuntu 2004 and Home Assistant
|
| 45 |
+
• Outlining issues with current setup, such as health states preventing updates
|
| 46 |
+
• Considering alternative directions for future setup, including x86 machines with Proxmox
|
| 47 |
+
• Running Home Assistant in a dedicated virtual machine
|
| 48 |
+
• Considering an M1 Mac Mini as a headless home server running Linux
|
| 49 |
+
• Identifying two main problems to solve with this next round: performance and reproducibility
|
| 50 |
+
• Desiring reproducibility due to the difficulty of remembering current setup and potential future rebuilds
|
| 51 |
+
• Evaluating Ansible for config management, but ultimately deciding against it in favor of Nix
|
| 52 |
+
• Nix provides a way to build systems from config files
|
| 53 |
+
• Using Nix OS is similar to using Nix as a package manager, but it offers more control over the system
|
| 54 |
+
• Nix OS can build entire systems, including containers, with simple syntax
|
| 55 |
+
• The Nix system figures out software dependencies and services automatically
|
| 56 |
+
• Nix documentation provides reproducibility and ease of deployment
|
| 57 |
+
• Nix is useful for containerized systems, such as Home Assistant and Plex
|
| 58 |
+
• Nix allows for rolling updates and recreation of entire systems
|
| 59 |
+
• The benefits of using Nix OS for managing systems and dependencies
|
| 60 |
+
• Comparison between Nix OS and containerization (e.g. Docker)
|
| 61 |
+
• Use cases where Nix OS's ability to manage entire software environments is beneficial
|
| 62 |
+
• Concerns about the overhead of running an entire OS environment in a container
|
| 63 |
+
• Isolating data and application stuff with Nix
|
| 64 |
+
• Performance benefits of using M1 processors with Nix
|
| 65 |
+
• Availability of Nix OS on M1 Mini devices
|
| 66 |
+
• Comparison between Nix and container-based solutions (e.g. Ansible)
|
| 67 |
+
• Reproducibility and redeployment capabilities of Nix
|
| 68 |
+
• Ease of understanding and use of Nix's configuration language
|
| 69 |
+
• Discussion on using Nix as a package manager for Linux systems
|
| 70 |
+
• Comparison with Ansible and its role in deploying and managing systems
|
| 71 |
+
• Nix's version control and reproducibility features
|
| 72 |
+
• The potential future of Linux development and the adoption of Nix-like systems
|
| 73 |
+
• Red Hat's Core OS operating system and Fedora Core OS as counterpoints to Nix
|
| 74 |
+
• Upstream version of a system tried out
|
| 75 |
+
• Configuration is done declaratively and through an ignition config file
|
| 76 |
+
• NICs operate in a similar space to the operating system being read-only
|
| 77 |
+
• Rolling back to a specific snapshot can be simple with ZFS backend storage
|
| 78 |
+
• NICS has two methods: building and deploying without testing, or using a "build dash dash test" command that fails if it detects any issues
|
| 79 |
+
• Discussion of using Nix for home automation
|
| 80 |
+
• Comparison with Home Assistant core and potential minimal rebuild
|
| 81 |
+
• Consideration of switching to Node-RED for automation
|
| 82 |
+
• Transitioning to MQTT protocol
|
| 83 |
+
• Managing data silos and integrating various systems (e.g. Z-Wave JS) through MQTT
|
| 84 |
+
• Complexity of automations and programming logic
|
| 85 |
+
• Comparison of Home Assistant vs Node-Red for automation
|
| 86 |
+
• Use of MQTT protocol for power information from Victron system
|
| 87 |
+
• Desire to rebuild and migrate existing automation systems
|
| 88 |
+
• Plan to do a "bro build" episode with Wes at an RV
|
| 89 |
+
• Plans for episode 70
|
| 90 |
+
• Discussion about Panda Express and Chinese food preferences
|
| 91 |
+
• Correction on the Argon Aeon 4-Bay Raspberry Pi NAS case price
|
| 92 |
+
• Mention of temperature issues in the studio garage server room
|
| 93 |
+
• Introduction to a Wi-Fi sensor built by Gene using ESP home
|
| 94 |
+
• Home Assistant setup and monitoring
|
| 95 |
+
• Fever app for video recording and integration with Frigate and Home Assistant
|
| 96 |
+
• Bearded Tech's GitHub page and contribution to the community
|
| 97 |
+
• Coral AI USB sticks and their increasing price (over $200)
|
| 98 |
+
• Docker Compose for containerized applications
|
| 99 |
+
• New project being worked on is mentioned as good and GPL-licensed
|
| 100 |
+
• Host will be giving away Bitcoin to help with setting up Matrix
|
| 101 |
+
• Upcoming AMA session at jblive.tv, March 31st
|
| 102 |
+
• Mention of Fountain and its boost feature
|
| 103 |
• Event for meetup in Raleigh on April 9th
|
68: Unwyze Choices _summary.txt
CHANGED
|
@@ -1,102 +1,102 @@
|
|
| 1 |
-
• Introduction to episode 68 of Self-Hosted and welcome to Chris and Wes Payne
|
| 2 |
-
• Discussion of the upcoming Jupiter Broadcasting East Coast meetup on Saturday
|
| 3 |
-
• Description of the town event happening during the meetup, including food trucks and activities
|
| 4 |
-
• Tour of Alex's new house, including its size and layout
|
| 5 |
-
• Explanation of Alex's solar setup, including an 8 kilowatt array and monitoring system
|
| 6 |
-
• Technical details of how power is brought into the house through a metal conduit and SolarEdge inverter
|
| 7 |
-
• Discussion of a Wi-Fi bridge and its connection to the internet
|
| 8 |
-
• Mention of a Zigbee bridge that kept dropping out
|
| 9 |
-
• Explanation of how devices are connected using Ethernet cables and solar panels
|
| 10 |
-
• Reference to Home Assistant software and API access
|
| 11 |
-
• Discussion of smart breaker panels and energy monitoring technology
|
| 12 |
-
• Analysis of home power usage using machine learning
|
| 13 |
-
• Comparison between different appliances' power consumption
|
| 14 |
-
• Proposal for a whole house UPS system
|
| 15 |
-
• Inspection of a server basement with custom-built rack
|
| 16 |
-
• APC UPSs
|
| 17 |
-
• Modem and router setup
|
| 18 |
-
• Server rack with multiple disks (spec not mentioned)
|
| 19 |
-
• OpenSense firewall
|
| 20 |
-
• Network switches (POE switch with cameras and access points)
|
| 21 |
-
• Temperature sensor (ESP8266 and DHT22) and future placement consideration
|
| 22 |
-
• Zigbee setup (Combi USB and connections to UPS)
|
| 23 |
-
• Proxmox box and its components
|
| 24 |
-
• Home assistant installation on i5-8500 system
|
| 25 |
-
• KVM switch and H-top keyboard sharing software
|
| 26 |
-
• Future projects: rewiring, Ethernet upgrade, camera additions, wall mounting switches
|
| 27 |
-
• Server location and backup systems
|
| 28 |
-
• Potential damage to servers in case of a natural disaster
|
| 29 |
-
• Storage for equipment and gear
|
| 30 |
-
• Backup power supplies and switch gear
|
| 31 |
-
• HD tuner and over-the-air TV setup
|
| 32 |
-
• Blue Iris server and automation system
|
| 33 |
-
• Temperature sensors and control buttons
|
| 34 |
-
• The speaker is using an ESP32 to connect Bluetooth sensors throughout a building
|
| 35 |
-
• Various objects have been augmented with 3D printing solutions
|
| 36 |
-
• The speaker has many projects in progress or to-do, including home automation gear and Wyze cameras
|
| 37 |
-
• There are multiple Raspberry Pi computers within arm's reach of the speaker
|
| 38 |
-
• A vulnerability was discovered in the Wyze V1 camera, prompting concerns about security
|
| 39 |
-
• Wyze camera vulnerability allows remote access
|
| 40 |
-
• Wyze responded to the issue, stating local network access is required to exploit
|
| 41 |
-
• V1 cameras were vulnerable, while V2 and 3 had an update released months ago
|
| 42 |
-
• Wyze handled the situation poorly by discontinuing the model without proper communication or support for users
|
| 43 |
-
• The company's handling of the vulnerability could harm their reputation and aspirations as a major IoT vendor
|
| 44 |
-
• Discussion of Wyze cameras' quality and price
|
| 45 |
-
• Concerns about data collection and monetization by Wyze
|
| 46 |
-
• Using a blocked DNS request as a workaround for camera internet access
|
| 47 |
-
• Trade-offs between convenience, cost, and functionality
|
| 48 |
-
• Wyze's expansion into the smart home ecosystem and its implications
|
| 49 |
-
• Discussion of Linode's support for running Matrix server
|
| 50 |
-
• Upgrading Linode to 96 gigs of RAM and 48 CPU cores
|
| 51 |
-
• Using WiseBridge on Linode for remote access
|
| 52 |
-
• Comparison of Linode pricing to other hyperscalers
|
| 53 |
-
• Features of Linode's command line tool and API
|
| 54 |
-
• Availability of 24-7 customer support by phone or ticket
|
| 55 |
-
• Introduction to Plex's new universal watch list feature
|
| 56 |
-
• Discussion of Plex's transition from Plex Pass to ad-supported model
|
| 57 |
-
• Concerns about data upload to servers
|
| 58 |
-
• Client-side changes in Plex app
|
| 59 |
-
• Business model and feasibility of searching across multiple streaming services
|
| 60 |
-
• Challenges with DRM (Digital Rights Management) and maintaining a smooth user experience
|
| 61 |
-
• Comparison to other apps like Trakt.tv and JustWatch.com
|
| 62 |
-
• Features and functionality of the new Plex search feature
|
| 63 |
-
• Discussion of Plex and its evolution, with the speaker noting that it's no longer primarily focused on pirated content
|
| 64 |
-
• Comparison of Plex to Jellyfin as a viable alternative for media streaming and home entertainment
|
| 65 |
-
• New features in recent Jellyfin releases, including transcode fixes and DLNA improvements
|
| 66 |
-
• Criticism of Jellyfin being written in C# and its potential impact on community contributions
|
| 67 |
-
• Discussion of music hosting and playback options outside of the Plex ecosystem, specifically Sonic XD and Symphomium
|
| 68 |
-
• Personal experience with Plex Amp and its limitations for large music collections
|
| 69 |
-
• Reflections on Spotify and other music streaming services, including a personal decision to remain cancelled.
|
| 70 |
-
• The speaker used to use Google Play Music and now uses Plex Amp
|
| 71 |
-
• Discussion about uploading personal music collections to streaming services (Google Play, Apple Music)
|
| 72 |
-
• Snoop Dogg removing his album "Doggy Style" from Spotify to sell as an NFT on Plex Amp
|
| 73 |
-
• New version of Home Assistant released with various new features, including group management and entity hiding
|
| 74 |
-
• The speaker is unhappy that their Z-Wave integration was dropped in the latest version, preventing them from upgrading
|
| 75 |
-
• Upgrading to a new version of Home Assistant is required but difficult due to Z-Wave migration issues
|
| 76 |
-
• User is frustrated with the timing of the upgrade, which coincides with their travel and need for remote work setup
|
| 77 |
-
• Learning Python or alternative solutions like Tailscale and Node-Red are considered to maintain control over system
|
| 78 |
-
• Migration wizard failed to assist in upgrading to supported versions
|
| 79 |
-
• Alternative VPN solution (Tailscale) is promoted as a convenient option for secure remote access
|
| 80 |
-
• Tailscale network setup for kids' computers
|
| 81 |
-
• Device compatibility with Tailscale (Arch x86 boxes, Raspberry Pi, iPads, Android devices)
|
| 82 |
-
• Benefits of using Tailscale (consistent network IP, single sign-on provider integration, two-factor authentication)
|
| 83 |
-
• Feedback from Josh on self-hosting and SBC-based NAS
|
| 84 |
-
• Discussion on power consumption and compromise between low power and small form factor solution
|
| 85 |
-
• Introduction to Compute Module 4 and its advantages for building a reliable NAS
|
| 86 |
-
• Wildcard TLS certificate distribution across multiple Linode servers
|
| 87 |
-
• Propagating certificates automatically each month using various methods (SSH, Ansible Vault, cron jobs)
|
| 88 |
-
• Ensuring security and protection of SSH keys, certificates, and connection credentials
|
| 89 |
-
• Exploring alternative solutions such as S3 object storage for storing and distributing secrets
|
| 90 |
-
• Discussion of secure authentication mechanisms for accessing stored secrets
|
| 91 |
-
• Discussing a hypothetical solution to a problem
|
| 92 |
-
• Decryption password stored in plain text on remote systems
|
| 93 |
-
• Difficulty with synchronizing data across multiple systems
|
| 94 |
-
• Seeking listener suggestions and solutions for the mentioned problems
|
| 95 |
-
• Shoutouts and thank yous to SRE subscribers, Boosters, and listeners
|
| 96 |
-
• Discussion of the show's contact page and social media presence (Twitter and Discord)
|
| 97 |
-
• Mention of a self-hosted matrix server and its community
|
| 98 |
-
• The host shares horror stories about self-hosting Matrix in Linux Unplugged
|
| 99 |
-
• Self-hosting is manageable for small groups of people (5-100) but can be problematic for larger groups (hundred+)
|
| 100 |
-
• A specific episode on Linux Unplugged covers issues with default config settings (link provided: linuxunplugged.com/452)
|
| 101 |
-
• The host mentions Coda Radio and its show notes website (notes.jupiterbroadcasting.com) for more information
|
| 102 |
• The podcast is self-hosted and the current episode can be found at self-hosted.show/68
|
|
|
|
| 1 |
+
• Introduction to episode 68 of Self-Hosted and welcome to Chris and Wes Payne
|
| 2 |
+
• Discussion of the upcoming Jupiter Broadcasting East Coast meetup on Saturday
|
| 3 |
+
• Description of the town event happening during the meetup, including food trucks and activities
|
| 4 |
+
• Tour of Alex's new house, including its size and layout
|
| 5 |
+
• Explanation of Alex's solar setup, including an 8 kilowatt array and monitoring system
|
| 6 |
+
• Technical details of how power is brought into the house through a metal conduit and SolarEdge inverter
|
| 7 |
+
• Discussion of a Wi-Fi bridge and its connection to the internet
|
| 8 |
+
• Mention of a Zigbee bridge that kept dropping out
|
| 9 |
+
• Explanation of how devices are connected using Ethernet cables and solar panels
|
| 10 |
+
• Reference to Home Assistant software and API access
|
| 11 |
+
• Discussion of smart breaker panels and energy monitoring technology
|
| 12 |
+
• Analysis of home power usage using machine learning
|
| 13 |
+
• Comparison between different appliances' power consumption
|
| 14 |
+
• Proposal for a whole house UPS system
|
| 15 |
+
• Inspection of a server basement with custom-built rack
|
| 16 |
+
• APC UPSs
|
| 17 |
+
• Modem and router setup
|
| 18 |
+
• Server rack with multiple disks (spec not mentioned)
|
| 19 |
+
• OpenSense firewall
|
| 20 |
+
• Network switches (POE switch with cameras and access points)
|
| 21 |
+
• Temperature sensor (ESP8266 and DHT22) and future placement consideration
|
| 22 |
+
• Zigbee setup (Combi USB and connections to UPS)
|
| 23 |
+
• Proxmox box and its components
|
| 24 |
+
• Home assistant installation on i5-8500 system
|
| 25 |
+
• KVM switch and H-top keyboard sharing software
|
| 26 |
+
• Future projects: rewiring, Ethernet upgrade, camera additions, wall mounting switches
|
| 27 |
+
• Server location and backup systems
|
| 28 |
+
• Potential damage to servers in case of a natural disaster
|
| 29 |
+
• Storage for equipment and gear
|
| 30 |
+
• Backup power supplies and switch gear
|
| 31 |
+
• HD tuner and over-the-air TV setup
|
| 32 |
+
• Blue Iris server and automation system
|
| 33 |
+
• Temperature sensors and control buttons
|
| 34 |
+
• The speaker is using an ESP32 to connect Bluetooth sensors throughout a building
|
| 35 |
+
• Various objects have been augmented with 3D printing solutions
|
| 36 |
+
• The speaker has many projects in progress or to-do, including home automation gear and Wyze cameras
|
| 37 |
+
• There are multiple Raspberry Pi computers within arm's reach of the speaker
|
| 38 |
+
• A vulnerability was discovered in the Wyze V1 camera, prompting concerns about security
|
| 39 |
+
• Wyze camera vulnerability allows remote access
|
| 40 |
+
• Wyze responded to the issue, stating local network access is required to exploit
|
| 41 |
+
• V1 cameras were vulnerable, while V2 and 3 had an update released months ago
|
| 42 |
+
• Wyze handled the situation poorly by discontinuing the model without proper communication or support for users
|
| 43 |
+
• The company's handling of the vulnerability could harm their reputation and aspirations as a major IoT vendor
|
| 44 |
+
• Discussion of Wyze cameras' quality and price
|
| 45 |
+
• Concerns about data collection and monetization by Wyze
|
| 46 |
+
• Using a blocked DNS request as a workaround for camera internet access
|
| 47 |
+
• Trade-offs between convenience, cost, and functionality
|
| 48 |
+
• Wyze's expansion into the smart home ecosystem and its implications
|
| 49 |
+
• Discussion of Linode's support for running Matrix server
|
| 50 |
+
• Upgrading Linode to 96 gigs of RAM and 48 CPU cores
|
| 51 |
+
• Using WiseBridge on Linode for remote access
|
| 52 |
+
• Comparison of Linode pricing to other hyperscalers
|
| 53 |
+
• Features of Linode's command line tool and API
|
| 54 |
+
• Availability of 24-7 customer support by phone or ticket
|
| 55 |
+
• Introduction to Plex's new universal watch list feature
|
| 56 |
+
• Discussion of Plex's transition from Plex Pass to ad-supported model
|
| 57 |
+
• Concerns about data upload to servers
|
| 58 |
+
• Client-side changes in Plex app
|
| 59 |
+
• Business model and feasibility of searching across multiple streaming services
|
| 60 |
+
• Challenges with DRM (Digital Rights Management) and maintaining a smooth user experience
|
| 61 |
+
• Comparison to other apps like Trakt.tv and JustWatch.com
|
| 62 |
+
• Features and functionality of the new Plex search feature
|
| 63 |
+
• Discussion of Plex and its evolution, with the speaker noting that it's no longer primarily focused on pirated content
|
| 64 |
+
• Comparison of Plex to Jellyfin as a viable alternative for media streaming and home entertainment
|
| 65 |
+
• New features in recent Jellyfin releases, including transcode fixes and DLNA improvements
|
| 66 |
+
• Criticism of Jellyfin being written in C# and its potential impact on community contributions
|
| 67 |
+
• Discussion of music hosting and playback options outside of the Plex ecosystem, specifically Sonic XD and Symphomium
|
| 68 |
+
• Personal experience with Plex Amp and its limitations for large music collections
|
| 69 |
+
• Reflections on Spotify and other music streaming services, including a personal decision to remain cancelled.
|
| 70 |
+
• The speaker used to use Google Play Music and now uses Plex Amp
|
| 71 |
+
• Discussion about uploading personal music collections to streaming services (Google Play, Apple Music)
|
| 72 |
+
• Snoop Dogg removing his album "Doggy Style" from Spotify to sell as an NFT on Plex Amp
|
| 73 |
+
• New version of Home Assistant released with various new features, including group management and entity hiding
|
| 74 |
+
• The speaker is unhappy that their Z-Wave integration was dropped in the latest version, preventing them from upgrading
|
| 75 |
+
• Upgrading to a new version of Home Assistant is required but difficult due to Z-Wave migration issues
|
| 76 |
+
• User is frustrated with the timing of the upgrade, which coincides with their travel and need for remote work setup
|
| 77 |
+
• Learning Python or alternative solutions like Tailscale and Node-Red are considered to maintain control over system
|
| 78 |
+
• Migration wizard failed to assist in upgrading to supported versions
|
| 79 |
+
• Alternative VPN solution (Tailscale) is promoted as a convenient option for secure remote access
|
| 80 |
+
• Tailscale network setup for kids' computers
|
| 81 |
+
• Device compatibility with Tailscale (Arch x86 boxes, Raspberry Pi, iPads, Android devices)
|
| 82 |
+
• Benefits of using Tailscale (consistent network IP, single sign-on provider integration, two-factor authentication)
|
| 83 |
+
• Feedback from Josh on self-hosting and SBC-based NAS
|
| 84 |
+
• Discussion on power consumption and compromise between low power and small form factor solution
|
| 85 |
+
• Introduction to Compute Module 4 and its advantages for building a reliable NAS
|
| 86 |
+
• Wildcard TLS certificate distribution across multiple Linode servers
|
| 87 |
+
• Propagating certificates automatically each month using various methods (SSH, Ansible Vault, cron jobs)
|
| 88 |
+
• Ensuring security and protection of SSH keys, certificates, and connection credentials
|
| 89 |
+
• Exploring alternative solutions such as S3 object storage for storing and distributing secrets
|
| 90 |
+
• Discussion of secure authentication mechanisms for accessing stored secrets
|
| 91 |
+
• Discussing a hypothetical solution to a problem
|
| 92 |
+
• Decryption password stored in plain text on remote systems
|
| 93 |
+
• Difficulty with synchronizing data across multiple systems
|
| 94 |
+
• Seeking listener suggestions and solutions for the mentioned problems
|
| 95 |
+
• Shoutouts and thank yous to SRE subscribers, Boosters, and listeners
|
| 96 |
+
• Discussion of the show's contact page and social media presence (Twitter and Discord)
|
| 97 |
+
• Mention of a self-hosted matrix server and its community
|
| 98 |
+
• The host shares horror stories about self-hosting Matrix in Linux Unplugged
|
| 99 |
+
• Self-hosting is manageable for small groups of people (5-100) but can be problematic for larger groups (hundred+)
|
| 100 |
+
• A specific episode on Linux Unplugged covers issues with default config settings (link provided: linuxunplugged.com/452)
|
| 101 |
+
• The host mentions Coda Radio and its show notes website (notes.jupiterbroadcasting.com) for more information
|
| 102 |
• The podcast is self-hosted and the current episode can be found at self-hosted.show/68
|
69: Get Off My Lawn, The Robot's Got It _summary.txt
CHANGED
|
@@ -1,68 +1,68 @@
|
|
| 1 |
-
• Discussing hosting a live stream and interacting with viewers
|
| 2 |
-
• Introducing guests Chris Fisher and Brent
|
| 3 |
-
• Announcing the creation of a new podcast called officehours.hair
|
| 4 |
-
• Recalling the East Coast Raleigh meetup and discussing feedback from attendees
|
| 5 |
-
• Talking about future community meetups and organizing events
|
| 6 |
-
• Open Mower project: an autonomous lawn mower using open source software and GPS
|
| 7 |
-
• Project allows for efficient mowing patterns, eliminating random paths
|
| 8 |
-
• Uses walking technique to teach mower optimal routes
|
| 9 |
-
• No perimeter wire needed, unlike traditional automated mowers
|
| 10 |
-
• Potential for metrics tracking yard state and optimizing mowing efficiency
|
| 11 |
-
• Weather monitoring integration discussed as a feature to be explored
|
| 12 |
-
• Hardware components of the project have sold out due to high demand
|
| 13 |
-
• Project creator plans to target rebranded main boards from various manufacturers
|
| 14 |
-
• Insteon has abruptly shut down, breaking users' cloud-dependent smart home setups
|
| 15 |
-
• No official warning or notice was given to users before the shutdown
|
| 16 |
-
• Insteon's status page is manually updated and no longer reflects the actual state of services
|
| 17 |
-
• Insteon devices are now essentially "paperweights" except for their wall switches
|
| 18 |
-
• Home Assistant has provided a workaround for users who accidentally factory reset their hub
|
| 19 |
-
• The shutdown highlights issues with cloud-dependent smart home systems and the need for self-sufficient alternatives
|
| 20 |
-
• Companies often don't commit to maintaining services, leaving consumers vulnerable to rug pulls
|
| 21 |
-
• There is a need for legislation or regulations that hold companies responsible for the lifecycle of their devices
|
| 22 |
-
• Discussion of Sonos V1 hub/bridge not receiving firmware updates or alternative open-source solution
|
| 23 |
-
• Problematic devices being sold at retailers and consumers' experiences with them not working as expected
|
| 24 |
-
• Examples of devices losing functionality due to manufacturer support discontinuation (e.g., D-Link cameras and water sensors)
|
| 25 |
-
• Home Assistant compatibility and its potential for device integration
|
| 26 |
-
• Linode infrastructure promotion, including pricing, features, and benefits for hosting servers and applications
|
| 27 |
-
• The speaker discusses their experience with Plex and Jellyfin media servers
|
| 28 |
-
• They mention setting up Tract Sync plugin to sync watched status between Plex and Jellyfin
|
| 29 |
-
• Discussion of pros and cons of using the plugin, including setup difficulties
|
| 30 |
-
• Benefits of using a local solution like Jellyfin for accessing media without internet connection
|
| 31 |
-
• Details on how Tract Sync plugin works, including API communication and authentication
|
| 32 |
-
• The speaker shares their experience with initial syncing process, including time taken to sync data between Plex and Jellyfin
|
| 33 |
-
• The speaker is considering switching from Plex to Jellyfin due to its reliability and features
|
| 34 |
-
• They mention that Plex has some attractive features, such as the Discover feature, which makes them hesitate about making a switch
|
| 35 |
-
• Android TV client for Jellyfin is still not reliable enough
|
| 36 |
-
• The speaker is looking for a solution for audiobooks and mentions Prolog on iOS and BookSonic, but both have issues
|
| 37 |
-
• They found an alternative called Audiobookshelf that has potential, but it's still in its early days
|
| 38 |
-
• The speaker compares the new app to the old iBooks application from Apple
|
| 39 |
-
• Issues with audiobooks not loading from library
|
| 40 |
-
• Update installed, syncing between browser and phone improved but not perfect
|
| 41 |
-
• Sharing media server with others using Tailscale
|
| 42 |
-
• Using Tailscale for zero-config VPN and to access home network remotely
|
| 43 |
-
• Features of Tailscale, including Android TV support and single sign-on provider integration
|
| 44 |
-
• Self-hosted.show and SRE (Site Reliability Engineer) subscribers are thanked for making the show possible
|
| 45 |
-
• The origin of the pseudo logo from XKCD is discussed
|
| 46 |
-
• Quick tips are shared, including using Docker stats to monitor container performance
|
| 47 |
-
• Feedback from listeners includes a boost from remaking Eden discussing their use of Wyze cameras with Defang hacks firmware and alternative methods of capturing video locally
|
| 48 |
-
• Podcasting 2.0 features and benefits
|
| 49 |
-
• Setup and implementation of new podcast apps supporting the standard
|
| 50 |
-
• Warning against syncing certificates to multiple servers using S3
|
| 51 |
-
• Use of Let's Encrypt and Acme for SSL certificate management
|
| 52 |
-
• Feedback from listeners on SSL certificate management and networking upgrades
|
| 53 |
-
• Discussion on the benefits of upgrading from 2.5Gbps to 10Gbps networking
|
| 54 |
-
• Comparison of different Ethernet cable standards, including CAT 6A
|
| 55 |
-
• Evaluation of whether 2.5Gbps is sufficient for current needs and potential future requirements
|
| 56 |
-
• Sharing personal experiences with fiber installation and upgrade considerations
|
| 57 |
-
• Mention of e-waste implications and the idea of "doing it once and doing it right"
|
| 58 |
-
• Discussion of running fiber in a home, including conduit installation and switching gear requirements
|
| 59 |
-
• Discussing cable vs fiber options for networking
|
| 60 |
-
• Contacting the hosts of the podcast for feedback and support
|
| 61 |
-
• Upcoming meetup event and community discussion
|
| 62 |
-
• Personal updates and interactions with listeners
|
| 63 |
-
• Technical discussions and network setup planning
|
| 64 |
-
• Community engagement and outreach efforts
|
| 65 |
-
• Introduction and welcome
|
| 66 |
-
• Potential future self-hosted events with good turnout
|
| 67 |
-
• Reference to "self-hosted dot show slash 69 420 edition"
|
| 68 |
• Repeated thank yous and goodbyes
|
|
|
|
| 1 |
+
• Discussing hosting a live stream and interacting with viewers
|
| 2 |
+
• Introducing guests Chris Fisher and Brent
|
| 3 |
+
• Announcing the creation of a new podcast called officehours.hair
|
| 4 |
+
• Recalling the East Coast Raleigh meetup and discussing feedback from attendees
|
| 5 |
+
• Talking about future community meetups and organizing events
|
| 6 |
+
• Open Mower project: an autonomous lawn mower using open source software and GPS
|
| 7 |
+
• Project allows for efficient mowing patterns, eliminating random paths
|
| 8 |
+
• Uses walking technique to teach mower optimal routes
|
| 9 |
+
• No perimeter wire needed, unlike traditional automated mowers
|
| 10 |
+
• Potential for metrics tracking yard state and optimizing mowing efficiency
|
| 11 |
+
• Weather monitoring integration discussed as a feature to be explored
|
| 12 |
+
• Hardware components of the project have sold out due to high demand
|
| 13 |
+
• Project creator plans to target rebranded main boards from various manufacturers
|
| 14 |
+
• Insteon has abruptly shut down, breaking users' cloud-dependent smart home setups
|
| 15 |
+
• No official warning or notice was given to users before the shutdown
|
| 16 |
+
• Insteon's status page is manually updated and no longer reflects the actual state of services
|
| 17 |
+
• Insteon devices are now essentially "paperweights" except for their wall switches
|
| 18 |
+
• Home Assistant has provided a workaround for users who accidentally factory reset their hub
|
| 19 |
+
• The shutdown highlights issues with cloud-dependent smart home systems and the need for self-sufficient alternatives
|
| 20 |
+
• Companies often don't commit to maintaining services, leaving consumers vulnerable to rug pulls
|
| 21 |
+
• There is a need for legislation or regulations that hold companies responsible for the lifecycle of their devices
|
| 22 |
+
• Discussion of Sonos V1 hub/bridge not receiving firmware updates or alternative open-source solution
|
| 23 |
+
• Problematic devices being sold at retailers and consumers' experiences with them not working as expected
|
| 24 |
+
• Examples of devices losing functionality due to manufacturer support discontinuation (e.g., D-Link cameras and water sensors)
|
| 25 |
+
• Home Assistant compatibility and its potential for device integration
|
| 26 |
+
• Linode infrastructure promotion, including pricing, features, and benefits for hosting servers and applications
|
| 27 |
+
• The speaker discusses their experience with Plex and Jellyfin media servers
|
| 28 |
+
• They mention setting up Tract Sync plugin to sync watched status between Plex and Jellyfin
|
| 29 |
+
• Discussion of pros and cons of using the plugin, including setup difficulties
|
| 30 |
+
• Benefits of using a local solution like Jellyfin for accessing media without internet connection
|
| 31 |
+
• Details on how Tract Sync plugin works, including API communication and authentication
|
| 32 |
+
• The speaker shares their experience with initial syncing process, including time taken to sync data between Plex and Jellyfin
|
| 33 |
+
• The speaker is considering switching from Plex to Jellyfin due to its reliability and features
|
| 34 |
+
• They mention that Plex has some attractive features, such as the Discover feature, which makes them hesitate about making a switch
|
| 35 |
+
• Android TV client for Jellyfin is still not reliable enough
|
| 36 |
+
• The speaker is looking for a solution for audiobooks and mentions Prolog on iOS and BookSonic, but both have issues
|
| 37 |
+
• They found an alternative called Audiobookshelf that has potential, but it's still in its early days
|
| 38 |
+
• The speaker compares the new app to the old iBooks application from Apple
|
| 39 |
+
• Issues with audiobooks not loading from library
|
| 40 |
+
• Update installed, syncing between browser and phone improved but not perfect
|
| 41 |
+
• Sharing media server with others using Tailscale
|
| 42 |
+
• Using Tailscale for zero-config VPN and to access home network remotely
|
| 43 |
+
• Features of Tailscale, including Android TV support and single sign-on provider integration
|
| 44 |
+
• Self-hosted.show and SRE (Site Reliability Engineer) subscribers are thanked for making the show possible
|
| 45 |
+
• The origin of the pseudo logo from XKCD is discussed
|
| 46 |
+
• Quick tips are shared, including using Docker stats to monitor container performance
|
| 47 |
+
• Feedback from listeners includes a boost from remaking Eden discussing their use of Wyze cameras with Defang hacks firmware and alternative methods of capturing video locally
|
| 48 |
+
• Podcasting 2.0 features and benefits
|
| 49 |
+
• Setup and implementation of new podcast apps supporting the standard
|
| 50 |
+
• Warning against syncing certificates to multiple servers using S3
|
| 51 |
+
• Use of Let's Encrypt and Acme for SSL certificate management
|
| 52 |
+
• Feedback from listeners on SSL certificate management and networking upgrades
|
| 53 |
+
• Discussion on the benefits of upgrading from 2.5Gbps to 10Gbps networking
|
| 54 |
+
• Comparison of different Ethernet cable standards, including CAT 6A
|
| 55 |
+
• Evaluation of whether 2.5Gbps is sufficient for current needs and potential future requirements
|
| 56 |
+
• Sharing personal experiences with fiber installation and upgrade considerations
|
| 57 |
+
• Mention of e-waste implications and the idea of "doing it once and doing it right"
|
| 58 |
+
• Discussion of running fiber in a home, including conduit installation and switching gear requirements
|
| 59 |
+
• Discussing cable vs fiber options for networking
|
| 60 |
+
• Contacting the hosts of the podcast for feedback and support
|
| 61 |
+
• Upcoming meetup event and community discussion
|
| 62 |
+
• Personal updates and interactions with listeners
|
| 63 |
+
• Technical discussions and network setup planning
|
| 64 |
+
• Community engagement and outreach efforts
|
| 65 |
+
• Introduction and welcome
|
| 66 |
+
• Potential future self-hosted events with good turnout
|
| 67 |
+
• Reference to "self-hosted dot show slash 69 420 edition"
|
| 68 |
• Repeated thank yous and goodbyes
|
70: Plausible Deniability _summary.txt
CHANGED
|
@@ -1,87 +1,87 @@
|
|
| 1 |
-
• Discussion of Star Wars Day and the host's limited enthusiasm for the franchise
|
| 2 |
-
• Introduction to Chris, Brent, and guest Fuzzy Mistborn from Linux Unplugged
|
| 3 |
-
• Update on Chris' new show festival and the JB website rebuild project
|
| 4 |
-
• Need to replace WordPress hosting due to Scale Engine's departure
|
| 5 |
-
• Discussion of self-hosting options and rebuilding the JB website
|
| 6 |
-
• Call for community input and feedback on the JB website redesign
|
| 7 |
-
• The host and Fuzzy Mistborn discuss their shared interests and friendship in a Discord community.
|
| 8 |
-
• Fuzzy Mistborn shares his experience owning an Ioniq 5, including a long road trip and testing its rapid charging capabilities.
|
| 9 |
-
• They discuss potential improvements to the car's data collection and integration with Home Assistant, which is limited by Hyundai's API calls per day.
|
| 10 |
-
• The host mentions using a better route planner that takes into account factors like weather, wind, and battery percentage to optimize charging stops.
|
| 11 |
-
• Real-time car charging updates
|
| 12 |
-
• Electric cars' OBD-II ports
|
| 13 |
-
• Old vs new data tracking methods (canvas vs Torque app)
|
| 14 |
-
• Uploading car data to Home Assistant
|
| 15 |
-
• Efficient car charging habits
|
| 16 |
-
• Renovate bot and GitOps for infrastructure management
|
| 17 |
-
• Customizing Renovate bot's features
|
| 18 |
-
• Top Gear style leaderboard storage question
|
| 19 |
-
• Setting rules for storing data on LAN
|
| 20 |
-
• Calculating total available storage space (80 terabytes)
|
| 21 |
-
• Leaderboard results and rankings
|
| 22 |
-
• Introduction to drone.io, a CI/CD system
|
| 23 |
-
• Author's experience with drone.io, including its capabilities and automation features
|
| 24 |
-
• Deploying Nextcloud ISO image for constantly updated cloud-init setup
|
| 25 |
-
• Issues with Drone: build stopping unexpectedly, requiring deletion and recreation to resolve
|
| 26 |
-
• Poor documentation in Drone leading to issues with cron jobs and time zone configuration
|
| 27 |
-
• Home Assistant setup running on Proxmox server with Z-Wave backbone and integration of Zigbee sensors
|
| 28 |
-
• Z-Wave migration from openZWave to Z-Wave JS due to performance and stability issues with rebooting network
|
| 29 |
-
• Using Z-Wave JS for improved functionality and avoiding need for separate instance
|
| 30 |
-
• Implementing a one-time guest code system with Z-Wave that recycles every week
|
| 31 |
-
• Discussion of the maintainer of Z-Wave JS now working full-time for Nebukasa
|
| 32 |
-
• Building a new house and using Z-Wave switches due to lack of affordable Zigbee options
|
| 33 |
-
• Using a Raspberry Pi as a sound machine for kids, with automatic start and stop times
|
| 34 |
-
• Creating an "OK to wake" system using a Z-wave bulb and color changing lights to signal morning time
|
| 35 |
-
• Installing an ESP board under a child's bed with red lighting to discourage nighttime movement
|
| 36 |
-
• The speaker discusses a DIY project that uses pressure-sensitive cardboard to detect movement and trigger an ESP (electronic switch).
|
| 37 |
-
• The speaker praises Linode, a cloud hosting service, for its ease of use, fast networking, and excellent customer support.
|
| 38 |
-
• The speaker mentions Plausible, a lightweight open-source web analytics engine that is an alternative to Google Analytics.
|
| 39 |
-
• The speaker notes that Plausible is GDPR-compliant and does not require user-acceptable cookies.
|
| 40 |
-
• Setting up self-hosted version of plausible analytics
|
| 41 |
-
• Container setup and configuration issues
|
| 42 |
-
• Using RealOrange1's GitHub repository to get it working
|
| 43 |
-
• Features and capabilities of plausible analytics
|
| 44 |
-
• Comparison with Google Analytics
|
| 45 |
-
• Privacy-focused design and minimal tracking
|
| 46 |
-
• Potential uses for plausible analytics in self-hosting
|
| 47 |
-
• Discussion about self-hosted analytics alternatives to Google Analytics
|
| 48 |
-
• Mention of Umami as a possible solution, which is simpler to set up than Plausible
|
| 49 |
-
• Criticism of Plausible's complex container architecture and comparison to other applications like Unify and Plex
|
| 50 |
-
• Explanation of Plausible's queuing engine and workers that process requests in real-time
|
| 51 |
-
• Discussion about the benefits of separating database containers from application containers for scalability and manageability
|
| 52 |
-
• Comparison of load times before and after installing analytics tools on a website
|
| 53 |
-
• Discussion of Google Analytics and Plausible as alternatives
|
| 54 |
-
• Comparison of script sizes and performance between Google Analytics and Plausible
|
| 55 |
-
• Environmental benefits of switching to Plausible
|
| 56 |
-
• Promotion of Tailscale, a zero-config VPN, for personal use and support of the show
|
| 57 |
-
• Personal experience with Tailscale's customer service and philosophy on sustainable infrastructure
|
| 58 |
-
• Story about troubleshooting a hard drive issue and poking fun at DIY solutions
|
| 59 |
-
• Server had multiple spinning drives causing excessive vibration
|
| 60 |
-
• SATA cable was suspected as the issue, replaced with a new one, but it didn't solve the problem
|
| 61 |
-
• The drive was taken out and run on a diagnostic station to test its functionality
|
| 62 |
-
• XFS errors were occurring and smart data wasn't showing any issues
|
| 63 |
-
• The drive's log/journal was rebuilt, which took around 5-10 minutes
|
| 64 |
-
• After rebuilding the log, the drive mounted perfectly and behaved normally
|
| 65 |
-
• The issue may be related to power supply or a bad cable, but further testing is needed to confirm
|
| 66 |
-
• A shucked drive, still within warranty, was used, and its original packaging and documentation were not kept
|
| 67 |
-
• The speaker had a faulty SATA cable that caused problems with their computer's drives.
|
| 68 |
-
• They solved the issue by cutting the three-volt wire in the SATA cable, allowing the drives to run off separate power sources.
|
| 69 |
-
• The speaker discussed safety precautions when working with electrical components and mentioned a personal experience where they shorted out a customer's motherboard at an Apple store.
|
| 70 |
-
• They also shared a story about damaging their wedding ring during a similar incident.
|
| 71 |
-
• The topic of boosting items into the show was briefly mentioned, including a character named Rubic-man.
|
| 72 |
-
• Installing security cameras in a new apartment
|
| 73 |
-
• Recommendation for affordable camera options with Home Assistant compatibility
|
| 74 |
-
• Discussion of Wise cams and their features (RTMP server, tail scale, USB Ethernet adapters)
|
| 75 |
-
• Comparison of Eufy cams vs. Wise cams
|
| 76 |
-
• Safety concerns about autonomous lawn mowers running unsupervised
|
| 77 |
-
• Robo mowers with safety features discussed
|
| 78 |
-
• Feedback from Crash Master 18 on live format and open mower idea
|
| 79 |
-
• Kars P. Lend's donation of 3,690 sats and possible reference to graphics cards
|
| 80 |
-
• Review of Frigate NVR by JVP, including ease of setup and integration with Home Assistant
|
| 81 |
-
• Call for model number of cameras used in review
|
| 82 |
-
• Gratitude to site reliability engineers and network-wide membership
|
| 83 |
-
• Promotion of podcasting 2.0 app and new podcast apps
|
| 84 |
-
• The speaker's birthday is mentioned and they decide to discuss an initiative on the day before their actual birthday.
|
| 85 |
-
• The show is now live every other Wednesday.
|
| 86 |
-
• A new initiative is being proposed to improve the "awesome self-hosted list" by reviewing it as a community in between live shows.
|
| 87 |
• The plan is to gather on the live stream, try out apps, and identify which ones work or don't, and suggest additions or removals from the list.
|
|
|
|
| 1 |
+
• Discussion of Star Wars Day and the host's limited enthusiasm for the franchise
|
| 2 |
+
• Introduction to Chris, Brent, and guest Fuzzy Mistborn from Linux Unplugged
|
| 3 |
+
• Update on Chris' new show festival and the JB website rebuild project
|
| 4 |
+
• Need to replace WordPress hosting due to Scale Engine's departure
|
| 5 |
+
• Discussion of self-hosting options and rebuilding the JB website
|
| 6 |
+
• Call for community input and feedback on the JB website redesign
|
| 7 |
+
• The host and Fuzzy Mistborn discuss their shared interests and friendship in a Discord community.
|
| 8 |
+
• Fuzzy Mistborn shares his experience owning an Ioniq 5, including a long road trip and testing its rapid charging capabilities.
|
| 9 |
+
• They discuss potential improvements to the car's data collection and integration with Home Assistant, which is limited by Hyundai's API calls per day.
|
| 10 |
+
• The host mentions using a better route planner that takes into account factors like weather, wind, and battery percentage to optimize charging stops.
|
| 11 |
+
• Real-time car charging updates
|
| 12 |
+
• Electric cars' OBD-II ports
|
| 13 |
+
• Old vs new data tracking methods (canvas vs Torque app)
|
| 14 |
+
• Uploading car data to Home Assistant
|
| 15 |
+
• Efficient car charging habits
|
| 16 |
+
• Renovate bot and GitOps for infrastructure management
|
| 17 |
+
• Customizing Renovate bot's features
|
| 18 |
+
• Top Gear style leaderboard storage question
|
| 19 |
+
• Setting rules for storing data on LAN
|
| 20 |
+
• Calculating total available storage space (80 terabytes)
|
| 21 |
+
• Leaderboard results and rankings
|
| 22 |
+
• Introduction to drone.io, a CI/CD system
|
| 23 |
+
• Author's experience with drone.io, including its capabilities and automation features
|
| 24 |
+
• Deploying Nextcloud ISO image for constantly updated cloud-init setup
|
| 25 |
+
• Issues with Drone: build stopping unexpectedly, requiring deletion and recreation to resolve
|
| 26 |
+
• Poor documentation in Drone leading to issues with cron jobs and time zone configuration
|
| 27 |
+
• Home Assistant setup running on Proxmox server with Z-Wave backbone and integration of Zigbee sensors
|
| 28 |
+
• Z-Wave migration from openZWave to Z-Wave JS due to performance and stability issues with rebooting network
|
| 29 |
+
• Using Z-Wave JS for improved functionality and avoiding need for separate instance
|
| 30 |
+
• Implementing a one-time guest code system with Z-Wave that recycles every week
|
| 31 |
+
• Discussion of the maintainer of Z-Wave JS now working full-time for Nebukasa
|
| 32 |
+
• Building a new house and using Z-Wave switches due to lack of affordable Zigbee options
|
| 33 |
+
• Using a Raspberry Pi as a sound machine for kids, with automatic start and stop times
|
| 34 |
+
• Creating an "OK to wake" system using a Z-wave bulb and color changing lights to signal morning time
|
| 35 |
+
• Installing an ESP board under a child's bed with red lighting to discourage nighttime movement
|
| 36 |
+
• The speaker discusses a DIY project that uses pressure-sensitive cardboard to detect movement and trigger an ESP (electronic switch).
|
| 37 |
+
• The speaker praises Linode, a cloud hosting service, for its ease of use, fast networking, and excellent customer support.
|
| 38 |
+
• The speaker mentions Plausible, a lightweight open-source web analytics engine that is an alternative to Google Analytics.
|
| 39 |
+
• The speaker notes that Plausible is GDPR-compliant and does not require user-acceptable cookies.
|
| 40 |
+
• Setting up self-hosted version of plausible analytics
|
| 41 |
+
• Container setup and configuration issues
|
| 42 |
+
• Using RealOrange1's GitHub repository to get it working
|
| 43 |
+
• Features and capabilities of plausible analytics
|
| 44 |
+
• Comparison with Google Analytics
|
| 45 |
+
• Privacy-focused design and minimal tracking
|
| 46 |
+
• Potential uses for plausible analytics in self-hosting
|
| 47 |
+
• Discussion about self-hosted analytics alternatives to Google Analytics
|
| 48 |
+
• Mention of Umami as a possible solution, which is simpler to set up than Plausible
|
| 49 |
+
• Criticism of Plausible's complex container architecture and comparison to other applications like Unify and Plex
|
| 50 |
+
• Explanation of Plausible's queuing engine and workers that process requests in real-time
|
| 51 |
+
• Discussion about the benefits of separating database containers from application containers for scalability and manageability
|
| 52 |
+
• Comparison of load times before and after installing analytics tools on a website
|
| 53 |
+
• Discussion of Google Analytics and Plausible as alternatives
|
| 54 |
+
• Comparison of script sizes and performance between Google Analytics and Plausible
|
| 55 |
+
• Environmental benefits of switching to Plausible
|
| 56 |
+
• Promotion of Tailscale, a zero-config VPN, for personal use and support of the show
|
| 57 |
+
• Personal experience with Tailscale's customer service and philosophy on sustainable infrastructure
|
| 58 |
+
• Story about troubleshooting a hard drive issue and poking fun at DIY solutions
|
| 59 |
+
• Server had multiple spinning drives causing excessive vibration
|
| 60 |
+
• SATA cable was suspected as the issue, replaced with a new one, but it didn't solve the problem
|
| 61 |
+
• The drive was taken out and run on a diagnostic station to test its functionality
|
| 62 |
+
• XFS errors were occurring and smart data wasn't showing any issues
|
| 63 |
+
• The drive's log/journal was rebuilt, which took around 5-10 minutes
|
| 64 |
+
• After rebuilding the log, the drive mounted perfectly and behaved normally
|
| 65 |
+
• The issue may be related to power supply or a bad cable, but further testing is needed to confirm
|
| 66 |
+
• A shucked drive, still within warranty, was used, and its original packaging and documentation were not kept
|
| 67 |
+
• The speaker had a faulty SATA cable that caused problems with their computer's drives.
|
| 68 |
+
• They solved the issue by cutting the three-volt wire in the SATA cable, allowing the drives to run off separate power sources.
|
| 69 |
+
• The speaker discussed safety precautions when working with electrical components and mentioned a personal experience where they shorted out a customer's motherboard at an Apple store.
|
| 70 |
+
• They also shared a story about damaging their wedding ring during a similar incident.
|
| 71 |
+
• The topic of boosting items into the show was briefly mentioned, including a character named Rubic-man.
|
| 72 |
+
• Installing security cameras in a new apartment
|
| 73 |
+
• Recommendation for affordable camera options with Home Assistant compatibility
|
| 74 |
+
• Discussion of Wise cams and their features (RTMP server, tail scale, USB Ethernet adapters)
|
| 75 |
+
• Comparison of Eufy cams vs. Wise cams
|
| 76 |
+
• Safety concerns about autonomous lawn mowers running unsupervised
|
| 77 |
+
• Robo mowers with safety features discussed
|
| 78 |
+
• Feedback from Crash Master 18 on live format and open mower idea
|
| 79 |
+
• Kars P. Lend's donation of 3,690 sats and possible reference to graphics cards
|
| 80 |
+
• Review of Frigate NVR by JVP, including ease of setup and integration with Home Assistant
|
| 81 |
+
• Call for model number of cameras used in review
|
| 82 |
+
• Gratitude to site reliability engineers and network-wide membership
|
| 83 |
+
• Promotion of podcasting 2.0 app and new podcast apps
|
| 84 |
+
• The speaker's birthday is mentioned and they decide to discuss an initiative on the day before their actual birthday.
|
| 85 |
+
• The show is now live every other Wednesday.
|
| 86 |
+
• A new initiative is being proposed to improve the "awesome self-hosted list" by reviewing it as a community in between live shows.
|
| 87 |
• The plan is to gather on the live stream, try out apps, and identify which ones work or don't, and suggest additions or removals from the list.
|
71: Recipe for Success _summary.txt
CHANGED
|
@@ -1,113 +1,113 @@
|
|
| 1 |
-
• Host is recording from a parking lot while getting work done on their vehicle
|
| 2 |
-
• Starlink situation discussed, including issues with the motor and replacement process
|
| 3 |
-
• Mention of visiting Best Buy to shop for home automation gear and tech products
|
| 4 |
-
• Discussion of e-ink displays and prices at Best Buy
|
| 5 |
-
• Pricing comparison of Lenovo smart clock stands with Google Assistant
|
| 6 |
-
• Host's frustration with Starlink dish design and lack of repairability
|
| 7 |
-
• Concerns about transporting the Starlink dish safely
|
| 8 |
-
• The cellular signal is holding but not perfect
|
| 9 |
-
• Discord milestone: 4,500 members
|
| 10 |
-
• Discussion on self-hosted chat platforms (Matrix vs Discord)
|
| 11 |
-
• Plans for UK meetup in early August, possibly in London
|
| 12 |
-
• Ideas for venue, such as BrewDog pubs with outdoor areas
|
| 13 |
-
• Fosdem plans and future episodes discussing projects
|
| 14 |
-
• Importing recipes from websites and blogs
|
| 15 |
-
• Creating a family-facing meal plan dashboard
|
| 16 |
-
• Integrating with Instacart's API for self-hosted meal planning
|
| 17 |
-
• Advanced import feature for extracting recipe information from web pages
|
| 18 |
-
• Shopping list functionality and grocery store compatibility
|
| 19 |
-
• Recipe database management and organization
|
| 20 |
-
• Comment and log features for tracking cooking progress and techniques
|
| 21 |
-
• Tandor Recipes features a meal planner and shopping list generator
|
| 22 |
-
• The app has a cookbooks feature for grouping recipes by categories
|
| 23 |
-
• Tandor is free and open-source software available on GitHub
|
| 24 |
-
• Setup process involves installing three containers: Postgres, Django app, and Nginx front-end
|
| 25 |
-
• Discussion of Docker administration and potential improvements to the setup process
|
| 26 |
-
• Developer feedback and appreciation for the application's features and development
|
| 27 |
-
• Different users have different setups for running virtual machines (Unraid, TrueNAS, Docker Compose)
|
| 28 |
-
• Reducing deployment complexity increases adoption
|
| 29 |
-
• New Proxmox release (7.2) with support for accelerated VertIO GL display driver improves performance
|
| 30 |
-
• Software-only solution allows for easy implementation without hardware pass-through requirements
|
| 31 |
-
• User experiences significant performance improvement (10x) with the new display driver
|
| 32 |
-
• The Proxmox community is growing and gaining a strong reputation
|
| 33 |
-
• New features in Proxmox include setting default VM ID ranges
|
| 34 |
-
• Discussion of Linode's services and benefits, including pricing and accessibility
|
| 35 |
-
• The use of Linode for hosting applications and websites
|
| 36 |
-
• A personal anecdote about automating electrical work with a server
|
| 37 |
-
• A disk failure led the speaker to replace their drive with a new one and transfer data using MergerFS.
|
| 38 |
-
• The speaker expresses skepticism about adopting new file systems, but is interested in BcacheFS if it performs well.
|
| 39 |
-
• BcacheFS is mentioned as potentially meeting the needs of users who require high-performance file systems.
|
| 40 |
-
• The speaker shares their experience with various file systems over the years, including AUFS, MHDDFS, ZFS, and MergerFS.
|
| 41 |
-
• The possibility of BcacheFS entering the Linux kernel in six months or so is discussed.
|
| 42 |
-
• The speaker's experience with storage solutions, specifically trying ButterFS and ZFS on a Raspberry Pi
|
| 43 |
-
• Discussion of BcacheFS and its potential, but the speaker's preference for established solutions like ZFS due to their long-term reliability
|
| 44 |
-
• Personal anecdote about learning ZFS, including comments on its complexity and reputation
|
| 45 |
-
• The failure of a 12 terabyte Western Digital drive and plans to return it under warranty, mentioning the Magnuson Moss Act
|
| 46 |
-
• Brief mention of Ansible and potential future discussion on the show
|
| 47 |
-
• Reference to Bitwarden Drive and combining it with Ansible
|
| 48 |
-
• Using Bitwarden as a credential store for Ansible Vault encryption password
|
| 49 |
-
• Storing encrypted secrets in a file version controlled in Git
|
| 50 |
-
• Connecting to Bitwarden using the CLI to decrypt Ansible Vault files
|
| 51 |
-
• New option to use Bitwarden CLI to insert passwords into Ansible deployments
|
| 52 |
-
• Using the Lookup plugin or a script with Bitwarden CLI export lookup
|
| 53 |
-
• Migrating vault password from local text file to Bitwarden
|
| 54 |
-
• Easy integration process, requiring only a few lines of code changes.
|
| 55 |
-
• Implementing DNS automation from Docker Compose generator
|
| 56 |
-
• Over-engineered Ansible tasks for traffic label management
|
| 57 |
-
• Automatically adding DNS records to Cloudflare based on labels
|
| 58 |
-
• Continuous integration and deployment using GitHub actions
|
| 59 |
-
• The speaker discusses using Ansible to automate tasks
|
| 60 |
-
• They mention using JSON queries and ternary operators to achieve specific outcomes
|
| 61 |
-
• A problem is identified with true/false values being treated as "present" or "absent"
|
| 62 |
-
• The ternary operator is used to resolve the issue by mapping true/false to present/absent
|
| 63 |
-
• Tailscale VPN is promoted, offering zero-config setup and device management
|
| 64 |
-
• The speaker shares a use case of sharing access to a specific host using Tailscale's sharing settings
|
| 65 |
-
• Tailscale and WireGuard are mentioned as tools for creating a flat mesh network between machines
|
| 66 |
-
• Tailscale has an authorization backplane that proxies connections to set up users, but allows direct communication after initial setup
|
| 67 |
-
• Tailscale supports single sign-on and two-factor authentication
|
| 68 |
-
• The host mentions having successfully set up Tailscale on various devices including Raspberry Pis and servers
|
| 69 |
-
• A listener writes in asking for alternatives to Raspberry Pi due to chip shortages
|
| 70 |
-
• The host solicits feedback from listeners on what they are using as alternatives
|
| 71 |
-
• Discussion of using a laptop with QuickSync for Plex
|
| 72 |
-
• Challenges of running Plex on laptops due to IO limitations
|
| 73 |
-
• Potential alternatives to Raspberry Pi, including old ThinkPads and Wyze thin client boxes
|
| 74 |
-
• Pros and cons of using old Thin Client boxes, including availability and cost on eBay
|
| 75 |
-
• Discussion about small and cheap computers (e.g. X86 Atoms) that can run anything
|
| 76 |
-
• Oliver writes in with a question about self-hosted podcast solutions
|
| 77 |
-
• Audiobookshelf mentioned as a promising solution for hosting podcasts
|
| 78 |
-
• Alex has not tried podcasting on Audiobookshelf but suggests doing a live test
|
| 79 |
-
• Discussion about the benefits of hosting podcasts locally on a phone or device, such as reduced data usage and battery drain.
|
| 80 |
-
• Creating a dedicated podcast folder
|
| 81 |
-
• Using the audio bookshelf to organize podcasts
|
| 82 |
-
• Discussing the use of iTunes for metadata, despite being self-hosted
|
| 83 |
-
• Mention of using alternative metadata providers (PodPing and Podcast Index)
|
| 84 |
-
• Adding an RSS feed from Self-Hosted.show/RSS
|
| 85 |
-
• Experimenting with submitting the RSS feed to the podcast platform
|
| 86 |
-
• Discussion of auto-downloading episodes and adding podcasts
|
| 87 |
-
• Testing a new solution for podcast management
|
| 88 |
-
• Discussion about receiving a silicon wedding ring
|
| 89 |
-
• Receipt of a cryptocurrency boost (3,690 sats) from Cospiland
|
| 90 |
-
• Explanation of Tesla numbers and their significance
|
| 91 |
-
• Inquiry about SUS servers (none found)
|
| 92 |
-
• Discussion about podcasting 2.0 and the Castopod platform
|
| 93 |
-
• Explanation of the features and benefits of Castopod, including support for podcasting 2.0 namespace and value-for-value model
|
| 94 |
-
• Discussion about voice assistants (e.g. Alexa, Siri, Google Home)
|
| 95 |
-
• Experiences with inconsistent voice recognition and accuracy
|
| 96 |
-
• Suggestions for improving voice assistant interactions (e.g. changing voice settings)
|
| 97 |
-
• Concerns about Amazon Echo devices inserting ads and disrupting use
|
| 98 |
-
• Comparison of different voice assistant devices (e.g. Amazon Echo vs. Apple HomePod)
|
| 99 |
-
• The host experiences issues with their HomePods not recognizing voice commands accurately
|
| 100 |
-
• They discuss alternative systems, such as Almond and Ada powered by Home Assistant, which may offer better accuracy
|
| 101 |
-
• The host shares personal experience of deploying a podcasting system for family use and feeling embarrassed when it fails to work properly
|
| 102 |
-
• A new podcast app is promoted at newpodcastapps.com
|
| 103 |
-
• Sats (satoshis) are mentioned as being on sale, with the host noting that they can be bought cheaper while still retaining their value
|
| 104 |
-
• The price of Bitcoin is mentioned briefly
|
| 105 |
-
• Discussion of audiobookshelf's features, including specifying a date range for downloading episodes
|
| 106 |
-
• Mention of cloudfree.shop and mylocalbytes.com as sponsorship deals with discounts available using the "self-hosted" coupon code
|
| 107 |
-
• Plans to donate affiliate revenue from these sponsorships to open source projects
|
| 108 |
-
• Announcement that EU.cloudfree.shop has launched, an EU-specific shop from a sponsor
|
| 109 |
-
• Ad-free version of the show and bonus post-show for subscribers
|
| 110 |
-
• Discussion about the host's new soldering iron, Pine Seal
|
| 111 |
-
• Upcoming London meetup on August 6th (provisional date)
|
| 112 |
-
• Invitation to join live shows every other Wednesday and participate in Discord chat
|
| 113 |
• Request for listener ideas for the London meetup and episode feedback
|
|
|
|
| 1 |
+
• Host is recording from a parking lot while getting work done on their vehicle
|
| 2 |
+
• Starlink situation discussed, including issues with the motor and replacement process
|
| 3 |
+
• Mention of visiting Best Buy to shop for home automation gear and tech products
|
| 4 |
+
• Discussion of e-ink displays and prices at Best Buy
|
| 5 |
+
• Pricing comparison of Lenovo smart clock stands with Google Assistant
|
| 6 |
+
• Host's frustration with Starlink dish design and lack of repairability
|
| 7 |
+
• Concerns about transporting the Starlink dish safely
|
| 8 |
+
• The cellular signal is holding but not perfect
|
| 9 |
+
• Discord milestone: 4,500 members
|
| 10 |
+
• Discussion on self-hosted chat platforms (Matrix vs Discord)
|
| 11 |
+
• Plans for UK meetup in early August, possibly in London
|
| 12 |
+
• Ideas for venue, such as BrewDog pubs with outdoor areas
|
| 13 |
+
• Fosdem plans and future episodes discussing projects
|
| 14 |
+
• Importing recipes from websites and blogs
|
| 15 |
+
• Creating a family-facing meal plan dashboard
|
| 16 |
+
• Integrating with Instacart's API for self-hosted meal planning
|
| 17 |
+
• Advanced import feature for extracting recipe information from web pages
|
| 18 |
+
• Shopping list functionality and grocery store compatibility
|
| 19 |
+
• Recipe database management and organization
|
| 20 |
+
• Comment and log features for tracking cooking progress and techniques
|
| 21 |
+
• Tandor Recipes features a meal planner and shopping list generator
|
| 22 |
+
• The app has a cookbooks feature for grouping recipes by categories
|
| 23 |
+
• Tandor is free and open-source software available on GitHub
|
| 24 |
+
• Setup process involves installing three containers: Postgres, Django app, and Nginx front-end
|
| 25 |
+
• Discussion of Docker administration and potential improvements to the setup process
|
| 26 |
+
• Developer feedback and appreciation for the application's features and development
|
| 27 |
+
• Different users have different setups for running virtual machines (Unraid, TrueNAS, Docker Compose)
|
| 28 |
+
• Reducing deployment complexity increases adoption
|
| 29 |
+
• New Proxmox release (7.2) with support for accelerated VertIO GL display driver improves performance
|
| 30 |
+
• Software-only solution allows for easy implementation without hardware pass-through requirements
|
| 31 |
+
• User experiences significant performance improvement (10x) with the new display driver
|
| 32 |
+
• The Proxmox community is growing and gaining a strong reputation
|
| 33 |
+
• New features in Proxmox include setting default VM ID ranges
|
| 34 |
+
• Discussion of Linode's services and benefits, including pricing and accessibility
|
| 35 |
+
• The use of Linode for hosting applications and websites
|
| 36 |
+
• A personal anecdote about automating electrical work with a server
|
| 37 |
+
• A disk failure led the speaker to replace their drive with a new one and transfer data using MergerFS.
|
| 38 |
+
• The speaker expresses skepticism about adopting new file systems, but is interested in BcacheFS if it performs well.
|
| 39 |
+
• BcacheFS is mentioned as potentially meeting the needs of users who require high-performance file systems.
|
| 40 |
+
• The speaker shares their experience with various file systems over the years, including AUFS, MHDDFS, ZFS, and MergerFS.
|
| 41 |
+
• The possibility of BcacheFS entering the Linux kernel in six months or so is discussed.
|
| 42 |
+
• The speaker's experience with storage solutions, specifically trying ButterFS and ZFS on a Raspberry Pi
|
| 43 |
+
• Discussion of BcacheFS and its potential, but the speaker's preference for established solutions like ZFS due to their long-term reliability
|
| 44 |
+
• Personal anecdote about learning ZFS, including comments on its complexity and reputation
|
| 45 |
+
• The failure of a 12 terabyte Western Digital drive and plans to return it under warranty, mentioning the Magnuson Moss Act
|
| 46 |
+
• Brief mention of Ansible and potential future discussion on the show
|
| 47 |
+
• Reference to Bitwarden Drive and combining it with Ansible
|
| 48 |
+
• Using Bitwarden as a credential store for Ansible Vault encryption password
|
| 49 |
+
• Storing encrypted secrets in a file version controlled in Git
|
| 50 |
+
• Connecting to Bitwarden using the CLI to decrypt Ansible Vault files
|
| 51 |
+
• New option to use Bitwarden CLI to insert passwords into Ansible deployments
|
| 52 |
+
• Using the Lookup plugin or a script with Bitwarden CLI export lookup
|
| 53 |
+
• Migrating vault password from local text file to Bitwarden
|
| 54 |
+
• Easy integration process, requiring only a few lines of code changes.
|
| 55 |
+
• Implementing DNS automation from Docker Compose generator
|
| 56 |
+
• Over-engineered Ansible tasks for traffic label management
|
| 57 |
+
• Automatically adding DNS records to Cloudflare based on labels
|
| 58 |
+
• Continuous integration and deployment using GitHub actions
|
| 59 |
+
• The speaker discusses using Ansible to automate tasks
|
| 60 |
+
• They mention using JSON queries and ternary operators to achieve specific outcomes
|
| 61 |
+
• A problem is identified with true/false values being treated as "present" or "absent"
|
| 62 |
+
• The ternary operator is used to resolve the issue by mapping true/false to present/absent
|
| 63 |
+
• Tailscale VPN is promoted, offering zero-config setup and device management
|
| 64 |
+
• The speaker shares a use case of sharing access to a specific host using Tailscale's sharing settings
|
| 65 |
+
• Tailscale and WireGuard are mentioned as tools for creating a flat mesh network between machines
|
| 66 |
+
• Tailscale has an authorization backplane that proxies connections to set up users, but allows direct communication after initial setup
|
| 67 |
+
• Tailscale supports single sign-on and two-factor authentication
|
| 68 |
+
• The host mentions having successfully set up Tailscale on various devices including Raspberry Pis and servers
|
| 69 |
+
• A listener writes in asking for alternatives to Raspberry Pi due to chip shortages
|
| 70 |
+
• The host solicits feedback from listeners on what they are using as alternatives
|
| 71 |
+
• Discussion of using a laptop with QuickSync for Plex
|
| 72 |
+
• Challenges of running Plex on laptops due to IO limitations
|
| 73 |
+
• Potential alternatives to Raspberry Pi, including old ThinkPads and Wyze thin client boxes
|
| 74 |
+
• Pros and cons of using old Thin Client boxes, including availability and cost on eBay
|
| 75 |
+
• Discussion about small and cheap computers (e.g. X86 Atoms) that can run anything
|
| 76 |
+
• Oliver writes in with a question about self-hosted podcast solutions
|
| 77 |
+
• Audiobookshelf mentioned as a promising solution for hosting podcasts
|
| 78 |
+
• Alex has not tried podcasting on Audiobookshelf but suggests doing a live test
|
| 79 |
+
• Discussion about the benefits of hosting podcasts locally on a phone or device, such as reduced data usage and battery drain.
|
| 80 |
+
• Creating a dedicated podcast folder
|
| 81 |
+
• Using the audio bookshelf to organize podcasts
|
| 82 |
+
• Discussing the use of iTunes for metadata, despite being self-hosted
|
| 83 |
+
• Mention of using alternative metadata providers (PodPing and Podcast Index)
|
| 84 |
+
• Adding an RSS feed from Self-Hosted.show/RSS
|
| 85 |
+
• Experimenting with submitting the RSS feed to the podcast platform
|
| 86 |
+
• Discussion of auto-downloading episodes and adding podcasts
|
| 87 |
+
• Testing a new solution for podcast management
|
| 88 |
+
• Discussion about receiving a silicon wedding ring
|
| 89 |
+
• Receipt of a cryptocurrency boost (3,690 sats) from Cospiland
|
| 90 |
+
• Explanation of Tesla numbers and their significance
|
| 91 |
+
• Inquiry about SUS servers (none found)
|
| 92 |
+
• Discussion about podcasting 2.0 and the Castopod platform
|
| 93 |
+
• Explanation of the features and benefits of Castopod, including support for podcasting 2.0 namespace and value-for-value model
|
| 94 |
+
• Discussion about voice assistants (e.g. Alexa, Siri, Google Home)
|
| 95 |
+
• Experiences with inconsistent voice recognition and accuracy
|
| 96 |
+
• Suggestions for improving voice assistant interactions (e.g. changing voice settings)
|
| 97 |
+
• Concerns about Amazon Echo devices inserting ads and disrupting use
|
| 98 |
+
• Comparison of different voice assistant devices (e.g. Amazon Echo vs. Apple HomePod)
|
| 99 |
+
• The host experiences issues with their HomePods not recognizing voice commands accurately
|
| 100 |
+
• They discuss alternative systems, such as Almond and Ada powered by Home Assistant, which may offer better accuracy
|
| 101 |
+
• The host shares personal experience of deploying a podcasting system for family use and feeling embarrassed when it fails to work properly
|
| 102 |
+
• A new podcast app is promoted at newpodcastapps.com
|
| 103 |
+
• Sats (satoshis) are mentioned as being on sale, with the host noting that they can be bought cheaper while still retaining their value
|
| 104 |
+
• The price of Bitcoin is mentioned briefly
|
| 105 |
+
• Discussion of audiobookshelf's features, including specifying a date range for downloading episodes
|
| 106 |
+
• Mention of cloudfree.shop and mylocalbytes.com as sponsorship deals with discounts available using the "self-hosted" coupon code
|
| 107 |
+
• Plans to donate affiliate revenue from these sponsorships to open source projects
|
| 108 |
+
• Announcement that EU.cloudfree.shop has launched, an EU-specific shop from a sponsor
|
| 109 |
+
• Ad-free version of the show and bonus post-show for subscribers
|
| 110 |
+
• Discussion about the host's new soldering iron, Pine Seal
|
| 111 |
+
• Upcoming London meetup on August 6th (provisional date)
|
| 112 |
+
• Invitation to join live shows every other Wednesday and participate in Discord chat
|
| 113 |
• Request for listener ideas for the London meetup and episode feedback
|
72: First Account is Free _summary.txt
CHANGED
|
@@ -1,66 +1,66 @@
|
|
| 1 |
-
• The speaker has bought six Volkswagen Golfs, and the current one is identical to a previous Golf R model.
|
| 2 |
-
• They have been test-driving other vehicles but are drawn back to the Golf due to its price point and features.
|
| 3 |
-
• The speaker's friend Alex also owns a VW Golf and sold it when prices rose.
|
| 4 |
-
• The speaker misses driving their previous Golf R and would like to take it on long drives with Alex in the future.
|
| 5 |
-
• They have considered shipping the car to Alex for an event, and are interested in doing some canyon carving together.
|
| 6 |
-
• Plans for a meetup in August are discussed
|
| 7 |
-
• A person wants to buy a Volkswagen Golf Mark 4 R32 with a VR6 engine
|
| 8 |
-
• The meetup's date and location may be changed due to travel issues
|
| 9 |
-
• The airlines have cancelled some flights, including the person's original flight
|
| 10 |
-
• The meetup will likely take place on Friday instead of Saturday
|
| 11 |
-
• An update on Scrutiny, an open-source hard drive monitoring utility, is provided
|
| 12 |
-
• Developer adds InfluxDB support to Scrutiny, allowing automatic data downsampling and reducing database size
|
| 13 |
-
• Thresholds for failure detection are now tweakable
|
| 14 |
-
• Dev enabled additional disk identification features via label and other methods
|
| 15 |
-
• Cartridge: a self-hosted game library for ROMs, targeted at those with classic games and handheld devices like Steam Deck
|
| 16 |
-
• Retro gaming scene and apps
|
| 17 |
-
• Self-hosted bookmark management tool called Service
|
| 18 |
-
• Workflow for managing bookmarks and links across multiple platforms
|
| 19 |
-
• Mobile workflow for discovering and saving content on mobile devices
|
| 20 |
-
• Pinboard as a current solution for managing bookmarks and links
|
| 21 |
-
• Comparison of Pinboard to self-hosted bookmark manager Service
|
| 22 |
-
• Dogsheep: a personal analytics tool that collects data from various cloud services and stores it in a SQLite database
|
| 23 |
-
• Linode: a cloud hosting platform offering $100 for 60 days on new accounts, with one-click applications and object storage capabilities
|
| 24 |
-
• PeerTube: a self-hosted video platform used by the host, deployed using Nix OS and Docker
|
| 25 |
-
• AlmaLinux and other distributions available on Linode's marketplace
|
| 26 |
-
• Object storage benefits and use of Linode's S3 compatible storage for backing services like NextCloud
|
| 27 |
-
• The CI (Continuous Integration) works when manually building, but a webhook issue was previously broken.
|
| 28 |
-
• A new feature in GitT version 1.16 introduced a webhook allowed host list variable that caused the issue.
|
| 29 |
-
• The fix was a simple one-line change in the app.ini file and took about 10 minutes to resolve.
|
| 30 |
-
• Rocket Chat announced they will be switching to using Matrix protocols for standards-based interoperable federation.
|
| 31 |
-
• This will allow Rocket Chat users to natively interoperate with the wider Matrix network, including over 12 million users.
|
| 32 |
-
• The switch is seen as a positive development, allowing for better encryption and reduced need for multiple communication protocols.
|
| 33 |
-
• XMPP being considered for podcasting 2.0 as a back-end for real-time comments
|
| 34 |
-
• Olive Tin project allowing safe access to commands via web browser for less technical users
|
| 35 |
-
• Google's reversal of their plan to end free version of G Suite, citing public backlash and possibly unfinished development work
|
| 36 |
-
• Discussion of de-Google strategy and self-hosting infrastructure alternatives (e.g. Peertube)
|
| 37 |
-
• Review of the impact on businesses (e.g. sponsor Tailscale) due to Google's decision
|
| 38 |
-
• Early adoption of technology by smart individuals can lead to trickle-down effects in the enterprise.
|
| 39 |
-
• Self-hosted solutions like Fastmail may benefit from people using them at home, which then leads to adoption in work environments.
|
| 40 |
-
• A survey found that 85% of consumers consider their privacy not worth giving up for convenience.
|
| 41 |
-
• The lack of options and skills required to self-host technology are significant barriers to widespread adoption.
|
| 42 |
-
• Self-hosting enthusiasts like the speaker may be a dying breed as mainstream consumers prioritize ease over control.
|
| 43 |
-
• Self-hosting is becoming more important for people due to issues with big tech, censorship, and government control.
|
| 44 |
-
• The trend of self-hosting will continue to grow as more people reject centralized services.
|
| 45 |
-
• There are many open-source software options available that can help individuals set up their own servers and networks.
|
| 46 |
-
• TailScale is a VPN service that allows users to connect multiple devices securely and easily, with features such as zero-config and real-time network switching.
|
| 47 |
-
• The service has a free account option for up to 20 devices and uses WireGuard's noise protocol for added security.
|
| 48 |
-
• Promotion of TailScale.com for free machines and support
|
| 49 |
-
• Listener's request for more 3D printing content on the show
|
| 50 |
-
• Discussion about potentially creating special episodes or a spin-off show focused on maker topics, such as electronics and 3D printing
|
| 51 |
-
• Boosters and listeners sharing their thoughts and experiences with self-hosting, meetups, and related topics
|
| 52 |
-
• Criticism of bundled containers in a previous episode
|
| 53 |
-
• Response to criticism from Marcel, discussing the difference between monolithic containers and smaller, self-hosted applications
|
| 54 |
-
• Discussion of Wi-Fi enabled e-ink displays
|
| 55 |
-
• E-ink display options for Raspberry Pi and ESP devices
|
| 56 |
-
• Power usage and battery life considerations for e-ink displays
|
| 57 |
-
• Alternative uses for Kindle Fire tablets with Lineage OS
|
| 58 |
-
• Performance comparison between stock Amazon Android image and Lineage OS
|
| 59 |
-
• Considerations for buying a Kindle Fire with ad-supported version in mind
|
| 60 |
-
• Rarity and preciousness of Raspberry Pis
|
| 61 |
-
• Importance of job opportunities related to self-hosted projects
|
| 62 |
-
• Sponsorship requests from companies wanting to be interviewed on the show
|
| 63 |
-
• Creation of an ad-free version of the show for members
|
| 64 |
-
• Introduction of a live feed option for members
|
| 65 |
-
• Details about live show schedule (every 2 weeks, 7:30 PM Eastern/Pacific)
|
| 66 |
• Contact information and community links (selfhosted.show/contact, Twitter handles)
|
|
|
|
| 1 |
+
• The speaker has bought six Volkswagen Golfs, and the current one is identical to a previous Golf R model.
|
| 2 |
+
• They have been test-driving other vehicles but are drawn back to the Golf due to its price point and features.
|
| 3 |
+
• The speaker's friend Alex also owns a VW Golf and sold it when prices rose.
|
| 4 |
+
• The speaker misses driving their previous Golf R and would like to take it on long drives with Alex in the future.
|
| 5 |
+
• They have considered shipping the car to Alex for an event, and are interested in doing some canyon carving together.
|
| 6 |
+
• Plans for a meetup in August are discussed
|
| 7 |
+
• A person wants to buy a Volkswagen Golf Mark 4 R32 with a VR6 engine
|
| 8 |
+
• The meetup's date and location may be changed due to travel issues
|
| 9 |
+
• The airlines have cancelled some flights, including the person's original flight
|
| 10 |
+
• The meetup will likely take place on Friday instead of Saturday
|
| 11 |
+
• An update on Scrutiny, an open-source hard drive monitoring utility, is provided
|
| 12 |
+
• Developer adds InfluxDB support to Scrutiny, allowing automatic data downsampling and reducing database size
|
| 13 |
+
• Thresholds for failure detection are now tweakable
|
| 14 |
+
• Dev enabled additional disk identification features via label and other methods
|
| 15 |
+
• Cartridge: a self-hosted game library for ROMs, targeted at those with classic games and handheld devices like Steam Deck
|
| 16 |
+
• Retro gaming scene and apps
|
| 17 |
+
• Self-hosted bookmark management tool called Service
|
| 18 |
+
• Workflow for managing bookmarks and links across multiple platforms
|
| 19 |
+
• Mobile workflow for discovering and saving content on mobile devices
|
| 20 |
+
• Pinboard as a current solution for managing bookmarks and links
|
| 21 |
+
• Comparison of Pinboard to self-hosted bookmark manager Service
|
| 22 |
+
• Dogsheep: a personal analytics tool that collects data from various cloud services and stores it in a SQLite database
|
| 23 |
+
• Linode: a cloud hosting platform offering $100 for 60 days on new accounts, with one-click applications and object storage capabilities
|
| 24 |
+
• PeerTube: a self-hosted video platform used by the host, deployed using Nix OS and Docker
|
| 25 |
+
• AlmaLinux and other distributions available on Linode's marketplace
|
| 26 |
+
• Object storage benefits and use of Linode's S3 compatible storage for backing services like NextCloud
|
| 27 |
+
• The CI (Continuous Integration) works when manually building, but a webhook issue was previously broken.
|
| 28 |
+
• A new feature in GitT version 1.16 introduced a webhook allowed host list variable that caused the issue.
|
| 29 |
+
• The fix was a simple one-line change in the app.ini file and took about 10 minutes to resolve.
|
| 30 |
+
• Rocket Chat announced they will be switching to using Matrix protocols for standards-based interoperable federation.
|
| 31 |
+
• This will allow Rocket Chat users to natively interoperate with the wider Matrix network, including over 12 million users.
|
| 32 |
+
• The switch is seen as a positive development, allowing for better encryption and reduced need for multiple communication protocols.
|
| 33 |
+
• XMPP being considered for podcasting 2.0 as a back-end for real-time comments
|
| 34 |
+
• Olive Tin project allowing safe access to commands via web browser for less technical users
|
| 35 |
+
• Google's reversal of their plan to end free version of G Suite, citing public backlash and possibly unfinished development work
|
| 36 |
+
• Discussion of de-Google strategy and self-hosting infrastructure alternatives (e.g. Peertube)
|
| 37 |
+
• Review of the impact on businesses (e.g. sponsor Tailscale) due to Google's decision
|
| 38 |
+
• Early adoption of technology by smart individuals can lead to trickle-down effects in the enterprise.
|
| 39 |
+
• Self-hosted solutions like Fastmail may benefit from people using them at home, which then leads to adoption in work environments.
|
| 40 |
+
• A survey found that 85% of consumers consider their privacy not worth giving up for convenience.
|
| 41 |
+
• The lack of options and skills required to self-host technology are significant barriers to widespread adoption.
|
| 42 |
+
• Self-hosting enthusiasts like the speaker may be a dying breed as mainstream consumers prioritize ease over control.
|
| 43 |
+
• Self-hosting is becoming more important for people due to issues with big tech, censorship, and government control.
|
| 44 |
+
• The trend of self-hosting will continue to grow as more people reject centralized services.
|
| 45 |
+
• There are many open-source software options available that can help individuals set up their own servers and networks.
|
| 46 |
+
• TailScale is a VPN service that allows users to connect multiple devices securely and easily, with features such as zero-config and real-time network switching.
|
| 47 |
+
• The service has a free account option for up to 20 devices and uses WireGuard's noise protocol for added security.
|
| 48 |
+
• Promotion of TailScale.com for free machines and support
|
| 49 |
+
• Listener's request for more 3D printing content on the show
|
| 50 |
+
• Discussion about potentially creating special episodes or a spin-off show focused on maker topics, such as electronics and 3D printing
|
| 51 |
+
• Boosters and listeners sharing their thoughts and experiences with self-hosting, meetups, and related topics
|
| 52 |
+
• Criticism of bundled containers in a previous episode
|
| 53 |
+
• Response to criticism from Marcel, discussing the difference between monolithic containers and smaller, self-hosted applications
|
| 54 |
+
• Discussion of Wi-Fi enabled e-ink displays
|
| 55 |
+
• E-ink display options for Raspberry Pi and ESP devices
|
| 56 |
+
• Power usage and battery life considerations for e-ink displays
|
| 57 |
+
• Alternative uses for Kindle Fire tablets with Lineage OS
|
| 58 |
+
• Performance comparison between stock Amazon Android image and Lineage OS
|
| 59 |
+
• Considerations for buying a Kindle Fire with ad-supported version in mind
|
| 60 |
+
• Rarity and preciousness of Raspberry Pis
|
| 61 |
+
• Importance of job opportunities related to self-hosted projects
|
| 62 |
+
• Sponsorship requests from companies wanting to be interviewed on the show
|
| 63 |
+
• Creation of an ad-free version of the show for members
|
| 64 |
+
• Introduction of a live feed option for members
|
| 65 |
+
• Details about live show schedule (every 2 weeks, 7:30 PM Eastern/Pacific)
|
| 66 |
• Contact information and community links (selfhosted.show/contact, Twitter handles)
|
73: 100 Days of HomeLab _summary.txt
CHANGED
|
@@ -1,60 +1,60 @@
|
|
| 1 |
-
• The host is filling in for Chris Fisher who may have COVID-19
|
| 2 |
-
• Techno Tim joins the episode as a guest and has recently reached 100,000 subscribers on YouTube
|
| 3 |
-
• Tim launched "100 Days of HomeLab" initiative where participants will complete a task related to home automation and self-hosting every day for 100 days
|
| 4 |
-
• The host mentions upcoming UK meetup in August with a tentative date of August 5th and encourages listeners to suggest venues in London
|
| 5 |
-
• Discussion of DevOps and the need for generalists who know a little about everything
|
| 6 |
-
• Mention of home labbing and the launch of a YouTube series "100 days of home lab"
|
| 7 |
-
• Creation of a hashtag #100daysofhome lab to get people motivated and share their experiences
|
| 8 |
-
• Comparison between daily standup updates in software development and the updates being shared on the hashtag
|
| 9 |
-
• Discussion of the long-term plan for the initiative, which is not clearly defined but focused on creating a community and helping people with infrastructure challenges
|
| 10 |
-
• The speaker's experience with their YouTube video on Kubernetes and the unexpected response from viewers
|
| 11 |
-
• Defining what a "home lab" means, as it can have different interpretations for various people
|
| 12 |
-
• The concept of home labs as a place to experiment and test new technologies in a safe environment
|
| 13 |
-
• Common issues that arise when working in home labs, such as accidental destruction of production environments or equipment failures
|
| 14 |
-
• The speaker's own experiences with making mistakes while working on production systems, including deleting a load balancer and causing alerts to fire
|
| 15 |
-
• The importance of self-hosting and experimentation for developers, even if it means taking on additional responsibilities at home
|
| 16 |
-
• Setting up a home lab for experimenting and testing without affecting production services
|
| 17 |
-
• Using existing equipment or upgrading current PC to create a home lab
|
| 18 |
-
• Importance of memory in a home lab setup
|
| 19 |
-
• Various options for creating a home lab, from Raspberry Pis to enterprise-grade servers
|
| 20 |
-
• Showcased storage capacities of guests on the wiki.selfhosted.show leaderboard
|
| 21 |
-
• The speaker praises Linode's customer support and services
|
| 22 |
-
• The speaker uses Linode's cloud dashboard and S3 object storage to run Nextcloud for their network
|
| 23 |
-
• The speaker discusses the benefits of using Linode over other major cloud providers due to its pricing (30-50% cheaper)
|
| 24 |
-
• The speaker expresses interest in learning about Kubernetes and K3S, a lightweight way to run containers on the edge
|
| 25 |
-
• The speaker shares personal experiences with setting up and managing Kubernetes clusters and notes the complexity involved
|
| 26 |
-
• Challenges of setting up a highly available Kubernetes setup
|
| 27 |
-
• Lowest barrier of entry for a home lab scenario
|
| 28 |
-
• Comparison of using etcd vs MySQL as the backend database
|
| 29 |
-
• Complexity of replication and load balancing
|
| 30 |
-
• Industry standard practices vs custom setups
|
| 31 |
-
• Importance of choosing storage solutions before running services
|
| 32 |
-
• Stateful applications in Kubernetes require management of persistent state and storage
|
| 33 |
-
• NFS and other solutions can be used for storage, but introduce single points of failure
|
| 34 |
-
• Highly available services should not rely on a single point of failure for storage or databases
|
| 35 |
-
• Stateless applications can scale more easily in Kubernetes
|
| 36 |
-
• Kubernetes can automatically recover from node failures by recreating pods on other nodes
|
| 37 |
-
• 12 factor app architecture is recommended for dev shops to manage complexity and ensure scalability
|
| 38 |
-
• Overview of Helm charts and their use in running applications on Kubernetes clusters
|
| 39 |
-
• Discussion of the challenges and "gotchas" of managing user permissions and other configurations in Kubernetes
|
| 40 |
-
• Introduction to GitOps and its principles for declaratively defining cluster state through Git
|
| 41 |
-
• Explanation of how GitOps works, including the use of manifests and pull requests to influence cluster state
|
| 42 |
-
• Benefits of using GitOps, including reproducibility and accountability of changes
|
| 43 |
-
• Comparison of GitOps with other DevOps practices, such as Ansible
|
| 44 |
-
• GitOps approach to Kubernetes management
|
| 45 |
-
• Declarative vs imperative configuration
|
| 46 |
-
• Benefits of GitOps: simplicity, ease of rebuilding, and version control
|
| 47 |
-
• Drawbacks of GitOps: additional process steps for minor changes
|
| 48 |
-
• Argo CD as a tool for implementing GitOps
|
| 49 |
-
• Talescale.com: a zero-config VPN with firewall rules and subnet router technology
|
| 50 |
-
• Pine Note developer edition review and discussion
|
| 51 |
-
• E-ink display technology and costs
|
| 52 |
-
• Linus (security tool) and other security scanning tools
|
| 53 |
-
• Cybersecurity best practices for systems and networks
|
| 54 |
-
• Tailscale and port management in firewalls
|
| 55 |
-
• Alternatives to Raspberry Pi, including Orange Pi boards
|
| 56 |
-
• The host mentions their YouTube channel "Techno Tim" and provides ways to access it
|
| 57 |
-
• The host thanks Site Reliability Engineers (SRE) for making the show possible
|
| 58 |
-
• The host promotes supporting the Jupiter Broadcasting Network and its website Jupiter.party
|
| 59 |
-
• Upcoming events are mentioned, including a London Meetup on August 5th
|
| 60 |
• Contact information is provided for reaching out to the host or the show
|
|
|
|
| 1 |
+
• The host is filling in for Chris Fisher who may have COVID-19
|
| 2 |
+
• Techno Tim joins the episode as a guest and has recently reached 100,000 subscribers on YouTube
|
| 3 |
+
• Tim launched "100 Days of HomeLab" initiative where participants will complete a task related to home automation and self-hosting every day for 100 days
|
| 4 |
+
• The host mentions upcoming UK meetup in August with a tentative date of August 5th and encourages listeners to suggest venues in London
|
| 5 |
+
• Discussion of DevOps and the need for generalists who know a little about everything
|
| 6 |
+
• Mention of home labbing and the launch of a YouTube series "100 days of home lab"
|
| 7 |
+
• Creation of a hashtag #100daysofhome lab to get people motivated and share their experiences
|
| 8 |
+
• Comparison between daily standup updates in software development and the updates being shared on the hashtag
|
| 9 |
+
• Discussion of the long-term plan for the initiative, which is not clearly defined but focused on creating a community and helping people with infrastructure challenges
|
| 10 |
+
• The speaker's experience with their YouTube video on Kubernetes and the unexpected response from viewers
|
| 11 |
+
• Defining what a "home lab" means, as it can have different interpretations for various people
|
| 12 |
+
• The concept of home labs as a place to experiment and test new technologies in a safe environment
|
| 13 |
+
• Common issues that arise when working in home labs, such as accidental destruction of production environments or equipment failures
|
| 14 |
+
• The speaker's own experiences with making mistakes while working on production systems, including deleting a load balancer and causing alerts to fire
|
| 15 |
+
• The importance of self-hosting and experimentation for developers, even if it means taking on additional responsibilities at home
|
| 16 |
+
• Setting up a home lab for experimenting and testing without affecting production services
|
| 17 |
+
• Using existing equipment or upgrading current PC to create a home lab
|
| 18 |
+
• Importance of memory in a home lab setup
|
| 19 |
+
• Various options for creating a home lab, from Raspberry Pis to enterprise-grade servers
|
| 20 |
+
• Showcased storage capacities of guests on the wiki.selfhosted.show leaderboard
|
| 21 |
+
• The speaker praises Linode's customer support and services
|
| 22 |
+
• The speaker uses Linode's cloud dashboard and S3 object storage to run Nextcloud for their network
|
| 23 |
+
• The speaker discusses the benefits of using Linode over other major cloud providers due to its pricing (30-50% cheaper)
|
| 24 |
+
• The speaker expresses interest in learning about Kubernetes and K3S, a lightweight way to run containers on the edge
|
| 25 |
+
• The speaker shares personal experiences with setting up and managing Kubernetes clusters and notes the complexity involved
|
| 26 |
+
• Challenges of setting up a highly available Kubernetes setup
|
| 27 |
+
• Lowest barrier of entry for a home lab scenario
|
| 28 |
+
• Comparison of using etcd vs MySQL as the backend database
|
| 29 |
+
• Complexity of replication and load balancing
|
| 30 |
+
• Industry standard practices vs custom setups
|
| 31 |
+
• Importance of choosing storage solutions before running services
|
| 32 |
+
• Stateful applications in Kubernetes require management of persistent state and storage
|
| 33 |
+
• NFS and other solutions can be used for storage, but introduce single points of failure
|
| 34 |
+
• Highly available services should not rely on a single point of failure for storage or databases
|
| 35 |
+
• Stateless applications can scale more easily in Kubernetes
|
| 36 |
+
• Kubernetes can automatically recover from node failures by recreating pods on other nodes
|
| 37 |
+
• 12 factor app architecture is recommended for dev shops to manage complexity and ensure scalability
|
| 38 |
+
• Overview of Helm charts and their use in running applications on Kubernetes clusters
|
| 39 |
+
• Discussion of the challenges and "gotchas" of managing user permissions and other configurations in Kubernetes
|
| 40 |
+
• Introduction to GitOps and its principles for declaratively defining cluster state through Git
|
| 41 |
+
• Explanation of how GitOps works, including the use of manifests and pull requests to influence cluster state
|
| 42 |
+
• Benefits of using GitOps, including reproducibility and accountability of changes
|
| 43 |
+
• Comparison of GitOps with other DevOps practices, such as Ansible
|
| 44 |
+
• GitOps approach to Kubernetes management
|
| 45 |
+
• Declarative vs imperative configuration
|
| 46 |
+
• Benefits of GitOps: simplicity, ease of rebuilding, and version control
|
| 47 |
+
• Drawbacks of GitOps: additional process steps for minor changes
|
| 48 |
+
• Argo CD as a tool for implementing GitOps
|
| 49 |
+
• Talescale.com: a zero-config VPN with firewall rules and subnet router technology
|
| 50 |
+
• Pine Note developer edition review and discussion
|
| 51 |
+
• E-ink display technology and costs
|
| 52 |
+
• Linus (security tool) and other security scanning tools
|
| 53 |
+
• Cybersecurity best practices for systems and networks
|
| 54 |
+
• Tailscale and port management in firewalls
|
| 55 |
+
• Alternatives to Raspberry Pi, including Orange Pi boards
|
| 56 |
+
• The host mentions their YouTube channel "Techno Tim" and provides ways to access it
|
| 57 |
+
• The host thanks Site Reliability Engineers (SRE) for making the show possible
|
| 58 |
+
• The host promotes supporting the Jupiter Broadcasting Network and its website Jupiter.party
|
| 59 |
+
• Upcoming events are mentioned, including a London Meetup on August 5th
|
| 60 |
• Contact information is provided for reaching out to the host or the show
|
74: A Pi For Every Problem _summary.txt
CHANGED
|
@@ -1,94 +1,94 @@
|
|
| 1 |
-
• Josh Laskar from Red Hat joins the show
|
| 2 |
-
• Introduction and warning about Josh's large collection of Raspberry Pis
|
| 3 |
-
• Upcoming London meetup on August 5th at Jubilee Gardens
|
| 4 |
-
• Discussion of meeting location and timing (BST vs GMT)
|
| 5 |
-
• Creation of a new leaderboard for the number of Raspberry Pis owned
|
| 6 |
-
• Organizing self-hosted events, including meetups and virtual events
|
| 7 |
-
• Announcement of a JB Meetups matrix space for organizing location-specific chat rooms
|
| 8 |
-
• Discussion of pre-drinks or pre-eats before the main meetup
|
| 9 |
-
• Thanks to Tim for filling in on the previous episode
|
| 10 |
-
• Discussion about receiving a MyBook drive instead of an original Easy Store drive after shucking
|
| 11 |
-
• Shucking and upgrading hard drives for use in Synology boxes
|
| 12 |
-
• Deleting old movies and shows to free up space on a media server
|
| 13 |
-
• Comparison of internet-sourced video quality vs. locally ripped content (Blu-rays)
|
| 14 |
-
• Home Assistant voice control using HomePods, with discussion of local LAN execution
|
| 15 |
-
• Siri is not responding correctly to voice commands
|
| 16 |
-
• Voice assistant settings have changed unexpectedly
|
| 17 |
-
• Personalized results and voice recognition have been enabled
|
| 18 |
-
• Devices are being controlled incorrectly when commanded by different users
|
| 19 |
-
• Home automation system is malfunctioning
|
| 20 |
-
• Importance of security in home automation systems was discussed
|
| 21 |
-
• Local control and API access were highlighted as desirable features
|
| 22 |
-
• Local API vs cloud-based APIs
|
| 23 |
-
• Experiences with Nanoleaf and Govi smart lights integrations
|
| 24 |
-
• Issues with Govi's rate-limited API requests and impact on Home Assistant
|
| 25 |
-
• Discussion of data collection by vendors and ecosystem building
|
| 26 |
-
• Observations on multiple product lines and logo branding by companies
|
| 27 |
-
• Introduction to Tailscale VPN technology and its features
|
| 28 |
-
• Comparison of local API approach to cloud-based APIs
|
| 29 |
-
• Tailscale.com/self-hosted: a platform for creating a flat network across devices and services
|
| 30 |
-
• Josh's Raspberry Pi collection: 43 Pis and 8 Pi Picos
|
| 31 |
-
• Reasons for collecting Raspberry Pis: interest in Linux, early adoption of the platform, community support
|
| 32 |
-
• Experimenting with alternative devices (Libre boards) but finding the Raspberry Pi to be more suitable due to open source and community factors
|
| 33 |
-
• Limitations of using Raspberry Pis for specific tasks (e.g. Plex server)
|
| 34 |
-
• Virtualization servers vs individual Raspberry Pi devices
|
| 35 |
-
• Personal experience with virtualizing everything but switching to individual Pis due to ease of use and cost
|
| 36 |
-
• Using multiple Raspberry Pis for various projects and tasks (e.g. Pi Hole, network monitoring)
|
| 37 |
-
• Heat management and case choices for Raspberry Pis in hot environments
|
| 38 |
-
• Alternative thermal cases (Villarose and Geekworm) compared to others
|
| 39 |
-
• Unused vs used Raspberry Pis and the emotional attachment to them
|
| 40 |
-
• Various security-related projects using Raspberry Pis (e.g. pen testing, Wi-Fi hacking)
|
| 41 |
-
• Onboarding children with computing through Raspberry Pi projects
|
| 42 |
-
• Discussion of software-defined radio (SDR) monitor stations
|
| 43 |
-
• Using SDR for tracking aircraft and other signals
|
| 44 |
-
• Implementing SDR with Home Assistant and Zigbee
|
| 45 |
-
• Analyzing data from SDR monitoring for home security applications
|
| 46 |
-
• Tracking traffic and mapping frequencies
|
| 47 |
-
• Exploring use cases for SDR, including measuring tank levels and recording audio
|
| 48 |
-
• Comparison of using commercial products versus DIY solutions
|
| 49 |
-
• Raspberry Pi projects discussed:
|
| 50 |
-
• Lap deck project
|
| 51 |
-
• Implementing Kubernetes on the Pi
|
| 52 |
-
• Discussion about moving OpenShift clusters to Raspberry Pis
|
| 53 |
-
• Power efficiency comparison between Raspberry Pi and traditional hardware
|
| 54 |
-
• Limitations of using Kubernetes at home for learning purposes
|
| 55 |
-
• Storage leaderboard on a self-hosted wiki website
|
| 56 |
-
• Debate over whether 20 terabytes is a significant amount of storage
|
| 57 |
-
• File system discussion, including Synology file system and ButterFS
|
| 58 |
-
• Conversation about the Raspberry Ninja project and remote camera streaming with Raspberry Pi
|
| 59 |
-
• Promotion for Linode.com cloud solution
|
| 60 |
-
• The advantages and features of using Linode for cloud infrastructure
|
| 61 |
-
• Comparison of Linode's performance to hyperscalers
|
| 62 |
-
• Availability and reliability of Linode's services (99.99% uptime)
|
| 63 |
-
• Alternative to hyperscalers, potential use in hybrid cloud setup
|
| 64 |
-
• Feedback on Orange Pi boards and the Armbian OS project
|
| 65 |
-
• Discussion on operating systems for Raspberry Pis, including Raspbian/Raspberry Pi OS and Armbian
|
| 66 |
-
• Discussion about using SQLite database vs. MariaDB
|
| 67 |
-
• Benefits of using a time-series database like Influx for storing data
|
| 68 |
-
• Home Assistant team improving database performance in recent releases
|
| 69 |
-
• Authentic (Authentik) authentication system mentioned as an alternative to other solutions
|
| 70 |
-
• Josh's approach to authentication, using FreeIPA and wiping/reinstalling when necessary
|
| 71 |
-
• Discussing challenges with mirroring and use of Synology
|
| 72 |
-
• High signal compliment from CastPlan and Boostergram show feedback
|
| 73 |
-
• Discussion on Discord vs Matrix self-hosting and community dynamics
|
| 74 |
-
• Weighing security and ease of use in communication platforms
|
| 75 |
-
• Considering the impact of onboarding process on user adoption
|
| 76 |
-
• Reflecting on the size of the Discord community and potential for Matrix growth
|
| 77 |
-
• Discussion about self-hosting chat servers and using Discord vs Matrix
|
| 78 |
-
• Comparison of growth and user base between Matrix and Discord
|
| 79 |
-
• Mention of Red Hat's increasing presence in the Matrix community
|
| 80 |
-
• Question from a listener about storing two-factor authentication codes alongside passwords
|
| 81 |
-
• Response to the question on the trade-off between convenience and security
|
| 82 |
-
• Threat model and physical security
|
| 83 |
-
• Balance between protection and convenience
|
| 84 |
-
• Authentication methods (face/ thumb recognition)
|
| 85 |
-
• Bitcoin price discussion ($20,000)
|
| 86 |
-
• Show boost and membership options
|
| 87 |
-
• Live feed development and site reliability engineering
|
| 88 |
-
• Meetup event in London on August 5th
|
| 89 |
-
• Contact information for writing into the show
|
| 90 |
-
• Upcoming podcast episode details
|
| 91 |
-
• Changes to the show's schedule and live stream format
|
| 92 |
-
• Online presence and links to social media and podcast platforms (Twitter, GitHub, Jupiter Broadcasting)
|
| 93 |
-
• Potential issues with internet connectivity while traveling due to Starlink usage
|
| 94 |
• Final thank you message and closing notes
|
|
|
|
| 1 |
+
• Josh Laskar from Red Hat joins the show
|
| 2 |
+
• Introduction and warning about Josh's large collection of Raspberry Pis
|
| 3 |
+
• Upcoming London meetup on August 5th at Jubilee Gardens
|
| 4 |
+
• Discussion of meeting location and timing (BST vs GMT)
|
| 5 |
+
• Creation of a new leaderboard for the number of Raspberry Pis owned
|
| 6 |
+
• Organizing self-hosted events, including meetups and virtual events
|
| 7 |
+
• Announcement of a JB Meetups matrix space for organizing location-specific chat rooms
|
| 8 |
+
• Discussion of pre-drinks or pre-eats before the main meetup
|
| 9 |
+
• Thanks to Tim for filling in on the previous episode
|
| 10 |
+
• Discussion about receiving a MyBook drive instead of an original Easy Store drive after shucking
|
| 11 |
+
• Shucking and upgrading hard drives for use in Synology boxes
|
| 12 |
+
• Deleting old movies and shows to free up space on a media server
|
| 13 |
+
• Comparison of internet-sourced video quality vs. locally ripped content (Blu-rays)
|
| 14 |
+
• Home Assistant voice control using HomePods, with discussion of local LAN execution
|
| 15 |
+
• Siri is not responding correctly to voice commands
|
| 16 |
+
• Voice assistant settings have changed unexpectedly
|
| 17 |
+
• Personalized results and voice recognition have been enabled
|
| 18 |
+
• Devices are being controlled incorrectly when commanded by different users
|
| 19 |
+
• Home automation system is malfunctioning
|
| 20 |
+
• Importance of security in home automation systems was discussed
|
| 21 |
+
• Local control and API access were highlighted as desirable features
|
| 22 |
+
• Local API vs cloud-based APIs
|
| 23 |
+
• Experiences with Nanoleaf and Govi smart lights integrations
|
| 24 |
+
• Issues with Govi's rate-limited API requests and impact on Home Assistant
|
| 25 |
+
• Discussion of data collection by vendors and ecosystem building
|
| 26 |
+
• Observations on multiple product lines and logo branding by companies
|
| 27 |
+
• Introduction to Tailscale VPN technology and its features
|
| 28 |
+
• Comparison of local API approach to cloud-based APIs
|
| 29 |
+
• Tailscale.com/self-hosted: a platform for creating a flat network across devices and services
|
| 30 |
+
• Josh's Raspberry Pi collection: 43 Pis and 8 Pi Picos
|
| 31 |
+
• Reasons for collecting Raspberry Pis: interest in Linux, early adoption of the platform, community support
|
| 32 |
+
• Experimenting with alternative devices (Libre boards) but finding the Raspberry Pi to be more suitable due to open source and community factors
|
| 33 |
+
• Limitations of using Raspberry Pis for specific tasks (e.g. Plex server)
|
| 34 |
+
• Virtualization servers vs individual Raspberry Pi devices
|
| 35 |
+
• Personal experience with virtualizing everything but switching to individual Pis due to ease of use and cost
|
| 36 |
+
• Using multiple Raspberry Pis for various projects and tasks (e.g. Pi Hole, network monitoring)
|
| 37 |
+
• Heat management and case choices for Raspberry Pis in hot environments
|
| 38 |
+
• Alternative thermal cases (Villarose and Geekworm) compared to others
|
| 39 |
+
• Unused vs used Raspberry Pis and the emotional attachment to them
|
| 40 |
+
• Various security-related projects using Raspberry Pis (e.g. pen testing, Wi-Fi hacking)
|
| 41 |
+
• Onboarding children with computing through Raspberry Pi projects
|
| 42 |
+
• Discussion of software-defined radio (SDR) monitor stations
|
| 43 |
+
• Using SDR for tracking aircraft and other signals
|
| 44 |
+
• Implementing SDR with Home Assistant and Zigbee
|
| 45 |
+
• Analyzing data from SDR monitoring for home security applications
|
| 46 |
+
• Tracking traffic and mapping frequencies
|
| 47 |
+
• Exploring use cases for SDR, including measuring tank levels and recording audio
|
| 48 |
+
• Comparison of using commercial products versus DIY solutions
|
| 49 |
+
• Raspberry Pi projects discussed:
|
| 50 |
+
• Lap deck project
|
| 51 |
+
• Implementing Kubernetes on the Pi
|
| 52 |
+
• Discussion about moving OpenShift clusters to Raspberry Pis
|
| 53 |
+
• Power efficiency comparison between Raspberry Pi and traditional hardware
|
| 54 |
+
• Limitations of using Kubernetes at home for learning purposes
|
| 55 |
+
• Storage leaderboard on a self-hosted wiki website
|
| 56 |
+
• Debate over whether 20 terabytes is a significant amount of storage
|
| 57 |
+
• File system discussion, including Synology file system and ButterFS
|
| 58 |
+
• Conversation about the Raspberry Ninja project and remote camera streaming with Raspberry Pi
|
| 59 |
+
• Promotion for Linode.com cloud solution
|
| 60 |
+
• The advantages and features of using Linode for cloud infrastructure
|
| 61 |
+
• Comparison of Linode's performance to hyperscalers
|
| 62 |
+
• Availability and reliability of Linode's services (99.99% uptime)
|
| 63 |
+
• Alternative to hyperscalers, potential use in hybrid cloud setup
|
| 64 |
+
• Feedback on Orange Pi boards and the Armbian OS project
|
| 65 |
+
• Discussion on operating systems for Raspberry Pis, including Raspbian/Raspberry Pi OS and Armbian
|
| 66 |
+
• Discussion about using SQLite database vs. MariaDB
|
| 67 |
+
• Benefits of using a time-series database like Influx for storing data
|
| 68 |
+
• Home Assistant team improving database performance in recent releases
|
| 69 |
+
• Authentic (Authentik) authentication system mentioned as an alternative to other solutions
|
| 70 |
+
• Josh's approach to authentication, using FreeIPA and wiping/reinstalling when necessary
|
| 71 |
+
• Discussing challenges with mirroring and use of Synology
|
| 72 |
+
• High signal compliment from CastPlan and Boostergram show feedback
|
| 73 |
+
• Discussion on Discord vs Matrix self-hosting and community dynamics
|
| 74 |
+
• Weighing security and ease of use in communication platforms
|
| 75 |
+
• Considering the impact of onboarding process on user adoption
|
| 76 |
+
• Reflecting on the size of the Discord community and potential for Matrix growth
|
| 77 |
+
• Discussion about self-hosting chat servers and using Discord vs Matrix
|
| 78 |
+
• Comparison of growth and user base between Matrix and Discord
|
| 79 |
+
• Mention of Red Hat's increasing presence in the Matrix community
|
| 80 |
+
• Question from a listener about storing two-factor authentication codes alongside passwords
|
| 81 |
+
• Response to the question on the trade-off between convenience and security
|
| 82 |
+
• Threat model and physical security
|
| 83 |
+
• Balance between protection and convenience
|
| 84 |
+
• Authentication methods (face/ thumb recognition)
|
| 85 |
+
• Bitcoin price discussion ($20,000)
|
| 86 |
+
• Show boost and membership options
|
| 87 |
+
• Live feed development and site reliability engineering
|
| 88 |
+
• Meetup event in London on August 5th
|
| 89 |
+
• Contact information for writing into the show
|
| 90 |
+
• Upcoming podcast episode details
|
| 91 |
+
• Changes to the show's schedule and live stream format
|
| 92 |
+
• Online presence and links to social media and podcast platforms (Twitter, GitHub, Jupiter Broadcasting)
|
| 93 |
+
• Potential issues with internet connectivity while traveling due to Starlink usage
|
| 94 |
• Final thank you message and closing notes
|
75: In-Flight Changes _summary.txt
CHANGED
|
@@ -1,95 +1,95 @@
|
|
| 1 |
-
• The host and guests discuss a lady badger artwork created for their stream.
|
| 2 |
-
• They mention the arrival of guest Brent, who was supposed to join them but is now expected tomorrow morning.
|
| 3 |
-
• Alex will be flying out tomorrow night, possibly missing Brent's arrival.
|
| 4 |
-
• Nebukasa has announced its "Works with Home Assistant" program, which allows manufacturers to show support for Home Assistant and its community.
|
| 5 |
-
• The host shares their experience trying to find compatible Zigbee devices for Home Assistant, finding the process difficult and time-consuming.
|
| 6 |
-
• They believe the new "Works with Home Assistant" program could make it easier for users to find compatible devices.
|
| 7 |
-
• The speaker discusses the new "Works with Home Assistant" certification program and its potential benefits.
|
| 8 |
-
• The program guarantees manufacturers an interface to develop against, similar to how Apple has maintained a consistent connector type for their devices.
|
| 9 |
-
• Manufacturers will be required to maintain integration of their products in Home Assistant and provide product samples and engineering contacts for escalation.
|
| 10 |
-
• The program's terms are enforced by an agreement signed by Nebu Casa and the manufacturer.
|
| 11 |
-
• The speaker expresses excitement about the potential revenue stream for Home Assistant and its ability to improve the user experience.
|
| 12 |
-
• They also discuss the challenges of integration and the importance of a cohesive user experience, citing Apple as an example of how this can be achieved.
|
| 13 |
-
• Home Assistant community growth and local API/local controls
|
| 14 |
-
• Concerns about potential future incompatibility with open standards
|
| 15 |
-
• Self-hosted to-do apps and their features
|
| 16 |
-
• Discussion of Vikunja as a self-hostable to-do app option
|
| 17 |
-
• Personal experiences with using Todoist and other productivity tools
|
| 18 |
-
• Discussion of self-hosted app options
|
| 19 |
-
• Linode as a cloud hosting option for Linux applications
|
| 20 |
-
• Features and benefits of using Linode
|
| 21 |
-
• Community support and customer service
|
| 22 |
-
• Promotion of Linode and special offer
|
| 23 |
-
• Update on Brent's travel plans
|
| 24 |
-
• Baggage handling and tracking experience
|
| 25 |
-
• Remote backup setup and recent changes
|
| 26 |
-
• The speaker's personal data and equipment were left behind in England after they immigrated.
|
| 27 |
-
• They had a server set up with ZFS and OpenVPN for secure remote access.
|
| 28 |
-
• The server was upgraded, but the internet connection at their father's house (where it was initially located) became too slow.
|
| 29 |
-
• The speaker's mother-in-law has since obtained fiber internet with a 500 Mbps connection, making it an ideal location for the server.
|
| 30 |
-
• The server is being moved to the mother-in-law's house and will be connected via Ethernet.
|
| 31 |
-
• Setting up a server at a friend's house with proper walls
|
| 32 |
-
• Using TailScale for remote access and backups instead of WireGuard
|
| 33 |
-
• Comparison of old VPN methods (point-to-point VPN with SSH) vs. new methods (TailScale)
|
| 34 |
-
• Backup setup using Synology box at the speaker's mother's house over slow internet connection
|
| 35 |
-
• Plans for a meetup in London on August 5th, including requirements for being outdoors
|
| 36 |
-
• Meetup timing discussed, noting that the meetup page is in JB's local time and the correct meeting time is 6pm BST
|
| 37 |
-
• Plans for a road trip to JPL in September, including stops in Oregon and California
|
| 38 |
-
• Invitation to meet with Tim Canham at JPL and a personal tour of the facility
|
| 39 |
-
• Upcoming meetups and events, including the London Colony meetup and the West Coast road trip
|
| 40 |
-
• Promotion of Humio's centralized log management and observability platform
|
| 41 |
-
• Discussion of the RV's arrival in Pasadena for the JPL visit
|
| 42 |
-
• Humio's cost-effectiveness compared to competing platforms like Splunk or Elastic
|
| 43 |
-
• The features and benefits of the Humio Community Edition, including no-cost data ingestion and 7-day retention
|
| 44 |
-
• How Humio can help self-hosters bring together various logs from different systems and apps in one place for easier troubleshooting
|
| 45 |
-
• A user's experience with using Humio to monitor power consumption and other home-related metrics
|
| 46 |
-
• Lawrence's question about transitioning from being a solicitor/attorney to a cloud career, and seeking advice on where to start
|
| 47 |
-
• Importance of documenting work and projects on GitHub as an example of work ethic and community participation
|
| 48 |
-
• Value of self-study and taking initiative to learn new skills, even outside of one's day job
|
| 49 |
-
• Skepticism about the value of certifications, focusing instead on passion and demonstrated expertise
|
| 50 |
-
• Discussion on the importance of finding a specific area of interest and becoming knowledgeable in that area, rather than trying to be a generalist
|
| 51 |
-
• Recommendation to focus on developing a specialty or passion, and using it as a guide for career goals
|
| 52 |
-
• The discussion begins with the concept of business cards and the idea of having electronic versions.
|
| 53 |
-
• One speaker mentions projects that allow building custom business cards, but expresses skepticism about their adoption.
|
| 54 |
-
• The Palm Pilot is mentioned as an example of an early attempt at electronic contact sharing.
|
| 55 |
-
• Several vendors' lack of incentive to interoperate creates obstacles for universal electronic cards.
|
| 56 |
-
• A QR code scanning method was previously considered, but led to tracking concerns.
|
| 57 |
-
• A listener writes in to thank the show for Linux content and asks about home automation and security devices.
|
| 58 |
-
• Leak detectors and related devices (Aqara, Aotec water leak sensor)
|
| 59 |
-
• Home Assistant compatibility
|
| 60 |
-
• Z-Wave devices (Ring leak detectors)
|
| 61 |
-
• Matrix ecosystem vs Discord
|
| 62 |
-
• Self-hosting and community building (Raleigh IoT community)
|
| 63 |
-
• Tech industry standards and competition (Apple-Microsoft analogy)
|
| 64 |
-
• Discussion of Authentic's capabilities and comparison to Orphalia
|
| 65 |
-
• Issues with Siri tubes not recognizing voice commands on HomePods in certain environments
|
| 66 |
-
• Theory that profile building by assistants may be contributing to declining performance
|
| 67 |
-
• Suggestion to test deleting profiles as a potential solution
|
| 68 |
-
• Comparison of Home Assistant to other voice recognition systems, including Mycroft
|
| 69 |
-
• Nostalgic discussion about early voice recognition technology
|
| 70 |
-
• A listener's favorite podcast episode and appreciation for the topics discussed
|
| 71 |
-
• Listener agrees to contribute to Brent's gas money
|
| 72 |
-
• Reference to a sign on Alex's chair that warns against touching it, and how people still try to touch it anyway
|
| 73 |
-
• Discussion of having a party while others are away, with concerns about possible mishaps
|
| 74 |
-
• Mention of Archie being a bad influence and the dog's drinking habits
|
| 75 |
-
• Listener asks for advice on improving Wi-Fi speeds in their townhouse
|
| 76 |
-
• Optimus Grey discusses his own Wi-Fi issues, using Unify tools and Ethernet connections
|
| 77 |
-
• Discussion of Wi-Fi 6 and its potential benefits
|
| 78 |
-
• Reference to a RoboVac that generates Wi-Fi heat maps
|
| 79 |
-
• Alternative methods for creating Wi-Fi heat maps without a fancy vacuum
|
| 80 |
-
• Discussion of channel overlap and potential solutions
|
| 81 |
-
• Wi-Fi signal issues with RoboVac heatmap
|
| 82 |
-
• Use of UniFi in-wall APs for IoT network optimization
|
| 83 |
-
• Importance of a dedicated IoT network
|
| 84 |
-
• Discussion of boosters and satellite boosts for podcast
|
| 85 |
-
• Upcoming changes to member feed and website upgrade
|
| 86 |
-
• Importance of independent media funding and authenticity
|
| 87 |
-
• Self-hosted community on Discord
|
| 88 |
-
• Matrix space linked in show notes
|
| 89 |
-
• Upcoming events:
|
| 90 |
-
+ London Meetup on August 5th
|
| 91 |
-
+ Chris's JPL JB super road trip in September
|
| 92 |
-
• Contact methods:
|
| 93 |
-
+ selfhosted.show/contact
|
| 94 |
-
+ Twitter (@Ironic Badger and @Chris LAS)
|
| 95 |
+ Jupiter Signal network
|
|
|
|
| 1 |
+
• The host and guests discuss a lady badger artwork created for their stream.
|
| 2 |
+
• They mention the arrival of guest Brent, who was supposed to join them but is now expected tomorrow morning.
|
| 3 |
+
• Alex will be flying out tomorrow night, possibly missing Brent's arrival.
|
| 4 |
+
• Nebukasa has announced its "Works with Home Assistant" program, which allows manufacturers to show support for Home Assistant and its community.
|
| 5 |
+
• The host shares their experience trying to find compatible Zigbee devices for Home Assistant, finding the process difficult and time-consuming.
|
| 6 |
+
• They believe the new "Works with Home Assistant" program could make it easier for users to find compatible devices.
|
| 7 |
+
• The speaker discusses the new "Works with Home Assistant" certification program and its potential benefits.
|
| 8 |
+
• The program guarantees manufacturers an interface to develop against, similar to how Apple has maintained a consistent connector type for their devices.
|
| 9 |
+
• Manufacturers will be required to maintain integration of their products in Home Assistant and provide product samples and engineering contacts for escalation.
|
| 10 |
+
• The program's terms are enforced by an agreement signed by Nebu Casa and the manufacturer.
|
| 11 |
+
• The speaker expresses excitement about the potential revenue stream for Home Assistant and its ability to improve the user experience.
|
| 12 |
+
• They also discuss the challenges of integration and the importance of a cohesive user experience, citing Apple as an example of how this can be achieved.
|
| 13 |
+
• Home Assistant community growth and local API/local controls
|
| 14 |
+
• Concerns about potential future incompatibility with open standards
|
| 15 |
+
• Self-hosted to-do apps and their features
|
| 16 |
+
• Discussion of Vikunja as a self-hostable to-do app option
|
| 17 |
+
• Personal experiences with using Todoist and other productivity tools
|
| 18 |
+
• Discussion of self-hosted app options
|
| 19 |
+
• Linode as a cloud hosting option for Linux applications
|
| 20 |
+
• Features and benefits of using Linode
|
| 21 |
+
• Community support and customer service
|
| 22 |
+
• Promotion of Linode and special offer
|
| 23 |
+
• Update on Brent's travel plans
|
| 24 |
+
• Baggage handling and tracking experience
|
| 25 |
+
• Remote backup setup and recent changes
|
| 26 |
+
• The speaker's personal data and equipment were left behind in England after they immigrated.
|
| 27 |
+
• They had a server set up with ZFS and OpenVPN for secure remote access.
|
| 28 |
+
• The server was upgraded, but the internet connection at their father's house (where it was initially located) became too slow.
|
| 29 |
+
• The speaker's mother-in-law has since obtained fiber internet with a 500 Mbps connection, making it an ideal location for the server.
|
| 30 |
+
• The server is being moved to the mother-in-law's house and will be connected via Ethernet.
|
| 31 |
+
• Setting up a server at a friend's house with proper walls
|
| 32 |
+
• Using TailScale for remote access and backups instead of WireGuard
|
| 33 |
+
• Comparison of old VPN methods (point-to-point VPN with SSH) vs. new methods (TailScale)
|
| 34 |
+
• Backup setup using Synology box at the speaker's mother's house over slow internet connection
|
| 35 |
+
• Plans for a meetup in London on August 5th, including requirements for being outdoors
|
| 36 |
+
• Meetup timing discussed, noting that the meetup page is in JB's local time and the correct meeting time is 6pm BST
|
| 37 |
+
• Plans for a road trip to JPL in September, including stops in Oregon and California
|
| 38 |
+
• Invitation to meet with Tim Canham at JPL and a personal tour of the facility
|
| 39 |
+
• Upcoming meetups and events, including the London Colony meetup and the West Coast road trip
|
| 40 |
+
• Promotion of Humio's centralized log management and observability platform
|
| 41 |
+
• Discussion of the RV's arrival in Pasadena for the JPL visit
|
| 42 |
+
• Humio's cost-effectiveness compared to competing platforms like Splunk or Elastic
|
| 43 |
+
• The features and benefits of the Humio Community Edition, including no-cost data ingestion and 7-day retention
|
| 44 |
+
• How Humio can help self-hosters bring together various logs from different systems and apps in one place for easier troubleshooting
|
| 45 |
+
• A user's experience with using Humio to monitor power consumption and other home-related metrics
|
| 46 |
+
• Lawrence's question about transitioning from being a solicitor/attorney to a cloud career, and seeking advice on where to start
|
| 47 |
+
• Importance of documenting work and projects on GitHub as an example of work ethic and community participation
|
| 48 |
+
• Value of self-study and taking initiative to learn new skills, even outside of one's day job
|
| 49 |
+
• Skepticism about the value of certifications, focusing instead on passion and demonstrated expertise
|
| 50 |
+
• Discussion on the importance of finding a specific area of interest and becoming knowledgeable in that area, rather than trying to be a generalist
|
| 51 |
+
• Recommendation to focus on developing a specialty or passion, and using it as a guide for career goals
|
| 52 |
+
• The discussion begins with the concept of business cards and the idea of having electronic versions.
|
| 53 |
+
• One speaker mentions projects that allow building custom business cards, but expresses skepticism about their adoption.
|
| 54 |
+
• The Palm Pilot is mentioned as an example of an early attempt at electronic contact sharing.
|
| 55 |
+
• Several vendors' lack of incentive to interoperate creates obstacles for universal electronic cards.
|
| 56 |
+
• A QR code scanning method was previously considered, but led to tracking concerns.
|
| 57 |
+
• A listener writes in to thank the show for Linux content and asks about home automation and security devices.
|
| 58 |
+
• Leak detectors and related devices (Aqara, Aotec water leak sensor)
|
| 59 |
+
• Home Assistant compatibility
|
| 60 |
+
• Z-Wave devices (Ring leak detectors)
|
| 61 |
+
• Matrix ecosystem vs Discord
|
| 62 |
+
• Self-hosting and community building (Raleigh IoT community)
|
| 63 |
+
• Tech industry standards and competition (Apple-Microsoft analogy)
|
| 64 |
+
• Discussion of Authentic's capabilities and comparison to Orphalia
|
| 65 |
+
• Issues with Siri tubes not recognizing voice commands on HomePods in certain environments
|
| 66 |
+
• Theory that profile building by assistants may be contributing to declining performance
|
| 67 |
+
• Suggestion to test deleting profiles as a potential solution
|
| 68 |
+
• Comparison of Home Assistant to other voice recognition systems, including Mycroft
|
| 69 |
+
• Nostalgic discussion about early voice recognition technology
|
| 70 |
+
• A listener's favorite podcast episode and appreciation for the topics discussed
|
| 71 |
+
• Listener agrees to contribute to Brent's gas money
|
| 72 |
+
• Reference to a sign on Alex's chair that warns against touching it, and how people still try to touch it anyway
|
| 73 |
+
• Discussion of having a party while others are away, with concerns about possible mishaps
|
| 74 |
+
• Mention of Archie being a bad influence and the dog's drinking habits
|
| 75 |
+
• Listener asks for advice on improving Wi-Fi speeds in their townhouse
|
| 76 |
+
• Optimus Grey discusses his own Wi-Fi issues, using Unify tools and Ethernet connections
|
| 77 |
+
• Discussion of Wi-Fi 6 and its potential benefits
|
| 78 |
+
• Reference to a RoboVac that generates Wi-Fi heat maps
|
| 79 |
+
• Alternative methods for creating Wi-Fi heat maps without a fancy vacuum
|
| 80 |
+
• Discussion of channel overlap and potential solutions
|
| 81 |
+
• Wi-Fi signal issues with RoboVac heatmap
|
| 82 |
+
• Use of UniFi in-wall APs for IoT network optimization
|
| 83 |
+
• Importance of a dedicated IoT network
|
| 84 |
+
• Discussion of boosters and satellite boosts for podcast
|
| 85 |
+
• Upcoming changes to member feed and website upgrade
|
| 86 |
+
• Importance of independent media funding and authenticity
|
| 87 |
+
• Self-hosted community on Discord
|
| 88 |
+
• Matrix space linked in show notes
|
| 89 |
+
• Upcoming events:
|
| 90 |
+
+ London Meetup on August 5th
|
| 91 |
+
+ Chris's JPL JB super road trip in September
|
| 92 |
+
• Contact methods:
|
| 93 |
+
+ selfhosted.show/contact
|
| 94 |
+
+ Twitter (@Ironic Badger and @Chris LAS)
|
| 95 |
+ Jupiter Signal network
|
76: Solid as a Rock _summary.txt
CHANGED
|
@@ -1,105 +1,105 @@
|
|
| 1 |
-
• Introduction from England and hello to British listeners
|
| 2 |
-
• Discussion of the host's setup for recording, including a mouth organ and microphone placement
|
| 3 |
-
• Upcoming meetup in London on August 5th at Jubilee Park Gardens
|
| 4 |
-
• Plans for the meetup, including presence of Joe Ressington and 100 other attendees
|
| 5 |
-
• Mention of a listener attending the meetup after flying from the US
|
| 6 |
-
• Details about the meetup location and registration through meetup.com/jupiterbroadcasting
|
| 7 |
-
• Host's travel plans, including staying with family members in England and using their internet connections
|
| 8 |
-
• Discussion of internet speeds at various locations and experience with Starlink
|
| 9 |
-
• Discussion of the author's experience with Starlink internet in a rural area
|
| 10 |
-
• Observations of the dish's performance, including movement and motor adjustments
|
| 11 |
-
• Ping times and speeds achieved through Starlink, including consistency issues
|
| 12 |
-
• Comparison to other internet options, such as LTE and reseller packages
|
| 13 |
-
• Concerns about overburdening the Starlink network with residential use
|
| 14 |
-
• Implications for rural real estate and the author's personal experience with Starlink
|
| 15 |
-
• Starlink's router is criticized for being "crappy" and requiring an additional Ethernet adapter
|
| 16 |
-
• Overlapping subnets with Tailscale cause issues with DNS queries
|
| 17 |
-
• Customizing the subnet in the Starlink router is not possible
|
| 18 |
-
• The Square Dishy setup has a dependency on the Starlink router, which is seen as unnecessary
|
| 19 |
-
• The setup takes less power than the circular dish but still requires a separate device
|
| 20 |
-
• The user's mother-in-law's home has fiber internet with 500 down and 70 up speeds
|
| 21 |
-
• Running Ethernet through the house was necessary to cope with the new speeds and improve connectivity
|
| 22 |
-
• CAT 6A vs CAT 6 cabling
|
| 23 |
-
• Pass-through Ethernet connectors for easier cable management
|
| 24 |
-
• Crimping tools and crimping process
|
| 25 |
-
• Firewall situation with PPPOE fiber connection
|
| 26 |
-
• Building an OpenSense router with custom parts from eBay
|
| 27 |
-
• Installation of OpenSense operating system
|
| 28 |
-
• Experience with buying parts online from eBay
|
| 29 |
-
• Reviewing eBay listings and seller reviews in an airport with family members present
|
| 30 |
-
• Installing a 60 gig mSATA SSD and 8 gigs of RAM on the system
|
| 31 |
-
• Running Tailscale and AdGuard Home directly on the router for security and ad-blocking purposes
|
| 32 |
-
• Communicating changes to the network setup to family members, including not announcing changes to avoid blame when issues arise
|
| 33 |
-
• Setting up a standardized three-node Tailscale OpenSense network across multiple locations with consistent DNS rewrites
|
| 34 |
-
• Using AdGuard as primary DNS with Unbound and Cloudflare for recursive DNS resolution
|
| 35 |
-
• AdGuard is used for DNS and ad blocking on the system
|
| 36 |
-
• Tailscale is mentioned as a secure alternative for accessing devices remotely
|
| 37 |
-
• The host is considering using OpenSense with AdGuard for network security
|
| 38 |
-
• A discussion about creating documentation for family members and friends who may need to access or manage the network if something happens to the primary user
|
| 39 |
-
• Linode's cloud services are promoted as a way to support the show and provide hosting options
|
| 40 |
-
• One-click stacks for easy deployment on Linode
|
| 41 |
-
• High performance and reliability of Linode services
|
| 42 |
-
• Linode's own network infrastructure
|
| 43 |
-
• New features such as NVMe storage, database as a service, and object storage
|
| 44 |
-
• Importance of directed airflow to prevent hard drive overheating
|
| 45 |
-
• Backblaze's annual report on hard drive reliability and its findings
|
| 46 |
-
• Discussion of the dominance of a few major companies in the hard drive market
|
| 47 |
-
• Criticism of people's opinions and biases towards specific brands (e.g. Seagate, Western Digital)
|
| 48 |
-
• Explanation of how hard drives are often mislabeled or rebranded by manufacturers
|
| 49 |
-
• Mention of Backblaze's data on hard drive reliability and lifespan
|
| 50 |
-
• Discussion of the need for regular hard drive replacement to maintain data integrity
|
| 51 |
-
• Suggestions for creative reuse of old hard drives (e.g. making clocks, coasters)
|
| 52 |
-
• Proposal for dollar averaging or "disk averaging" to smooth out price fluctuations
|
| 53 |
-
• Recommendation to buy hard drives during sale periods (e.g. Black Friday) to get the best value
|
| 54 |
-
• Discussion of hard drive prices and reliability
|
| 55 |
-
• Review of a listener's feedback on leak detectors from DeckBot
|
| 56 |
-
• Comparison of DeckBot's leak detector tape to other options
|
| 57 |
-
• Recommendation of Shelly flood sensors for home use
|
| 58 |
-
• Personal experience with setting up Shelly flood sensor in Home Assistant
|
| 59 |
-
• Considering replacing Z-Wave devices with Shelly Wi-Fi capable devices
|
| 60 |
-
• Planning to eliminate some HomeKit devices as well
|
| 61 |
-
• Exploring the Shelly devices for their features and battery life
|
| 62 |
-
• Discussing potential improvements in Home Assistant's user experience, specifically with integrations and notifications
|
| 63 |
-
• Suggesting that Nebukasa integration could provide push notifications automatically for Home Assistant members
|
| 64 |
-
• Mentioning need for time-sensitive notifications on iOS to break through do not disturb mode
|
| 65 |
-
• Considering Shelly devices' potential inclusion in the Works with Home Assistant program
|
| 66 |
-
• Discussion of MQTT and Wi-Fi vs BLE sensors
|
| 67 |
-
• Review of the Shelley Plus H&T device with e-ink display
|
| 68 |
-
• Comparison to Xiaomi BLE sensors
|
| 69 |
-
• Discussion of battery life and USB power option
|
| 70 |
-
• Introduction to the Shelley plug, a small Wi-Fi enabled smart plug
|
| 71 |
-
• Analysis of regulatory shortcuts taken by the manufacturer
|
| 72 |
-
• Features and capabilities of the Shelley plug (up to 2500 watts, power metering)
|
| 73 |
-
• Planning for home automation system with Shelley devices
|
| 74 |
-
• Discussion of firmware modifications (TAS motor, ESP Home)
|
| 75 |
-
• Fully open firmware and its implications
|
| 76 |
-
• Home Assistant announcement of their first works with a partner (Leviton)
|
| 77 |
-
• Humio log management platform, including its features and benefits
|
| 78 |
-
• Using Humio for log management in Home Assistant environments
|
| 79 |
-
• Smoke detector suggestions and discussion of Z-Wave limitations
|
| 80 |
-
• Personal experiences with Z-Wave smoke detectors and false alarms
|
| 81 |
-
• Discussion about smoke detectors, specifically issues with alerts when not home
|
| 82 |
-
• Mention of Shelly's Wi-Fi hubless smoke detector and their available gas detector
|
| 83 |
-
• Sharing of an idea to customize Jellyfin branding for personal use
|
| 84 |
-
• Discussion of Plex vs. Jellyfin, with the user expressing preference for Plex despite progress with Jellyfin
|
| 85 |
-
• Boosts from listeners, and a discussion of the peer-to-peer messaging network used by boosts
|
| 86 |
-
• Advice on shipping items overseas during international moves, including a personal anecdote about using Seven Seas Worldwide
|
| 87 |
-
• Shipping process from England to the US
|
| 88 |
-
• Loading and sealing of cargo in van
|
| 89 |
-
• Semi-regular shipping updates on arrival times and customs clearance
|
| 90 |
-
• Pickup of shipment at destination with rented van
|
| 91 |
-
• Selling or getting rid of items upon arrival due to space limitations and need for essentials
|
| 92 |
-
• Walmart shopping experience during hurricane
|
| 93 |
-
• Stressful but ultimately positive experience with moving process
|
| 94 |
-
• The person had a frustrating experience at a car park due to overcrowding and long lines.
|
| 95 |
-
• They discussed remote work and the difficulty of staying focused in traffic.
|
| 96 |
-
• The conversation turned to their previous experiences living in England and why they don't plan to move back.
|
| 97 |
-
• Ankh Bussin wrote in with a question about setting up a self-hosted podcast, including instructions for others to manage it in case of their death.
|
| 98 |
-
• The speakers discussed the challenge of leaving behind digital media, such as family photos and documents, for others to access.
|
| 99 |
-
• They mentioned potential solutions, like writing clear instructions or using specific software, but acknowledged that most people won't be interested in inheriting someone's digital collection.
|
| 100 |
-
• Development of a photo album selection tool
|
| 101 |
-
• PhotoPRISM and its features
|
| 102 |
-
• Meetup in London with AlexKTZ
|
| 103 |
-
• Promotion of Boosted by TrevDev and CastPlan
|
| 104 |
-
• Thank you to SREs (site reliability engineers) and members for supporting the show
|
| 105 |
• Upcoming meetups, including JPL tour with limited spots available
|
|
|
|
| 1 |
+
• Introduction from England and hello to British listeners
|
| 2 |
+
• Discussion of the host's setup for recording, including a mouth organ and microphone placement
|
| 3 |
+
• Upcoming meetup in London on August 5th at Jubilee Park Gardens
|
| 4 |
+
• Plans for the meetup, including presence of Joe Ressington and 100 other attendees
|
| 5 |
+
• Mention of a listener attending the meetup after flying from the US
|
| 6 |
+
• Details about the meetup location and registration through meetup.com/jupiterbroadcasting
|
| 7 |
+
• Host's travel plans, including staying with family members in England and using their internet connections
|
| 8 |
+
• Discussion of internet speeds at various locations and experience with Starlink
|
| 9 |
+
• Discussion of the author's experience with Starlink internet in a rural area
|
| 10 |
+
• Observations of the dish's performance, including movement and motor adjustments
|
| 11 |
+
• Ping times and speeds achieved through Starlink, including consistency issues
|
| 12 |
+
• Comparison to other internet options, such as LTE and reseller packages
|
| 13 |
+
• Concerns about overburdening the Starlink network with residential use
|
| 14 |
+
• Implications for rural real estate and the author's personal experience with Starlink
|
| 15 |
+
• Starlink's router is criticized for being "crappy" and requiring an additional Ethernet adapter
|
| 16 |
+
• Overlapping subnets with Tailscale cause issues with DNS queries
|
| 17 |
+
• Customizing the subnet in the Starlink router is not possible
|
| 18 |
+
• The Square Dishy setup has a dependency on the Starlink router, which is seen as unnecessary
|
| 19 |
+
• The setup takes less power than the circular dish but still requires a separate device
|
| 20 |
+
• The user's mother-in-law's home has fiber internet with 500 down and 70 up speeds
|
| 21 |
+
• Running Ethernet through the house was necessary to cope with the new speeds and improve connectivity
|
| 22 |
+
• CAT 6A vs CAT 6 cabling
|
| 23 |
+
• Pass-through Ethernet connectors for easier cable management
|
| 24 |
+
• Crimping tools and crimping process
|
| 25 |
+
• Firewall situation with PPPOE fiber connection
|
| 26 |
+
• Building an OpenSense router with custom parts from eBay
|
| 27 |
+
• Installation of OpenSense operating system
|
| 28 |
+
• Experience with buying parts online from eBay
|
| 29 |
+
• Reviewing eBay listings and seller reviews in an airport with family members present
|
| 30 |
+
• Installing a 60 gig mSATA SSD and 8 gigs of RAM on the system
|
| 31 |
+
• Running Tailscale and AdGuard Home directly on the router for security and ad-blocking purposes
|
| 32 |
+
• Communicating changes to the network setup to family members, including not announcing changes to avoid blame when issues arise
|
| 33 |
+
• Setting up a standardized three-node Tailscale OpenSense network across multiple locations with consistent DNS rewrites
|
| 34 |
+
• Using AdGuard as primary DNS with Unbound and Cloudflare for recursive DNS resolution
|
| 35 |
+
• AdGuard is used for DNS and ad blocking on the system
|
| 36 |
+
• Tailscale is mentioned as a secure alternative for accessing devices remotely
|
| 37 |
+
• The host is considering using OpenSense with AdGuard for network security
|
| 38 |
+
• A discussion about creating documentation for family members and friends who may need to access or manage the network if something happens to the primary user
|
| 39 |
+
• Linode's cloud services are promoted as a way to support the show and provide hosting options
|
| 40 |
+
• One-click stacks for easy deployment on Linode
|
| 41 |
+
• High performance and reliability of Linode services
|
| 42 |
+
• Linode's own network infrastructure
|
| 43 |
+
• New features such as NVMe storage, database as a service, and object storage
|
| 44 |
+
• Importance of directed airflow to prevent hard drive overheating
|
| 45 |
+
• Backblaze's annual report on hard drive reliability and its findings
|
| 46 |
+
• Discussion of the dominance of a few major companies in the hard drive market
|
| 47 |
+
• Criticism of people's opinions and biases towards specific brands (e.g. Seagate, Western Digital)
|
| 48 |
+
• Explanation of how hard drives are often mislabeled or rebranded by manufacturers
|
| 49 |
+
• Mention of Backblaze's data on hard drive reliability and lifespan
|
| 50 |
+
• Discussion of the need for regular hard drive replacement to maintain data integrity
|
| 51 |
+
• Suggestions for creative reuse of old hard drives (e.g. making clocks, coasters)
|
| 52 |
+
• Proposal for dollar averaging or "disk averaging" to smooth out price fluctuations
|
| 53 |
+
• Recommendation to buy hard drives during sale periods (e.g. Black Friday) to get the best value
|
| 54 |
+
• Discussion of hard drive prices and reliability
|
| 55 |
+
• Review of a listener's feedback on leak detectors from DeckBot
|
| 56 |
+
• Comparison of DeckBot's leak detector tape to other options
|
| 57 |
+
• Recommendation of Shelly flood sensors for home use
|
| 58 |
+
• Personal experience with setting up Shelly flood sensor in Home Assistant
|
| 59 |
+
• Considering replacing Z-Wave devices with Shelly Wi-Fi capable devices
|
| 60 |
+
• Planning to eliminate some HomeKit devices as well
|
| 61 |
+
• Exploring the Shelly devices for their features and battery life
|
| 62 |
+
• Discussing potential improvements in Home Assistant's user experience, specifically with integrations and notifications
|
| 63 |
+
• Suggesting that Nebukasa integration could provide push notifications automatically for Home Assistant members
|
| 64 |
+
• Mentioning need for time-sensitive notifications on iOS to break through do not disturb mode
|
| 65 |
+
• Considering Shelly devices' potential inclusion in the Works with Home Assistant program
|
| 66 |
+
• Discussion of MQTT and Wi-Fi vs BLE sensors
|
| 67 |
+
• Review of the Shelley Plus H&T device with e-ink display
|
| 68 |
+
• Comparison to Xiaomi BLE sensors
|
| 69 |
+
• Discussion of battery life and USB power option
|
| 70 |
+
• Introduction to the Shelley plug, a small Wi-Fi enabled smart plug
|
| 71 |
+
• Analysis of regulatory shortcuts taken by the manufacturer
|
| 72 |
+
• Features and capabilities of the Shelley plug (up to 2500 watts, power metering)
|
| 73 |
+
• Planning for home automation system with Shelley devices
|
| 74 |
+
• Discussion of firmware modifications (TAS motor, ESP Home)
|
| 75 |
+
• Fully open firmware and its implications
|
| 76 |
+
• Home Assistant announcement of their first works with a partner (Leviton)
|
| 77 |
+
• Humio log management platform, including its features and benefits
|
| 78 |
+
• Using Humio for log management in Home Assistant environments
|
| 79 |
+
• Smoke detector suggestions and discussion of Z-Wave limitations
|
| 80 |
+
• Personal experiences with Z-Wave smoke detectors and false alarms
|
| 81 |
+
• Discussion about smoke detectors, specifically issues with alerts when not home
|
| 82 |
+
• Mention of Shelly's Wi-Fi hubless smoke detector and their available gas detector
|
| 83 |
+
• Sharing of an idea to customize Jellyfin branding for personal use
|
| 84 |
+
• Discussion of Plex vs. Jellyfin, with the user expressing preference for Plex despite progress with Jellyfin
|
| 85 |
+
• Boosts from listeners, and a discussion of the peer-to-peer messaging network used by boosts
|
| 86 |
+
• Advice on shipping items overseas during international moves, including a personal anecdote about using Seven Seas Worldwide
|
| 87 |
+
• Shipping process from England to the US
|
| 88 |
+
• Loading and sealing of cargo in van
|
| 89 |
+
• Semi-regular shipping updates on arrival times and customs clearance
|
| 90 |
+
• Pickup of shipment at destination with rented van
|
| 91 |
+
• Selling or getting rid of items upon arrival due to space limitations and need for essentials
|
| 92 |
+
• Walmart shopping experience during hurricane
|
| 93 |
+
• Stressful but ultimately positive experience with moving process
|
| 94 |
+
• The person had a frustrating experience at a car park due to overcrowding and long lines.
|
| 95 |
+
• They discussed remote work and the difficulty of staying focused in traffic.
|
| 96 |
+
• The conversation turned to their previous experiences living in England and why they don't plan to move back.
|
| 97 |
+
• Ankh Bussin wrote in with a question about setting up a self-hosted podcast, including instructions for others to manage it in case of their death.
|
| 98 |
+
• The speakers discussed the challenge of leaving behind digital media, such as family photos and documents, for others to access.
|
| 99 |
+
• They mentioned potential solutions, like writing clear instructions or using specific software, but acknowledged that most people won't be interested in inheriting someone's digital collection.
|
| 100 |
+
• Development of a photo album selection tool
|
| 101 |
+
• PhotoPRISM and its features
|
| 102 |
+
• Meetup in London with AlexKTZ
|
| 103 |
+
• Promotion of Boosted by TrevDev and CastPlan
|
| 104 |
+
• Thank you to SREs (site reliability engineers) and members for supporting the show
|
| 105 |
• Upcoming meetups, including JPL tour with limited spots available
|
77: Automations Gone Wrong _summary.txt
CHANGED
|
@@ -1,96 +1,96 @@
|
|
| 1 |
-
• Jet lag discussed and its effects on Alex's daily routine
|
| 2 |
-
• Difficulty adjusting to eastward travel from America due to red eye flights and lost sleep
|
| 3 |
-
• Benefits of having a trusted person (Brent) take care of home responsibilities while away
|
| 4 |
-
• Discussion about the World Excel Championships, competitive spreadsheet writing, and potential for self-hosted trivia nights
|
| 5 |
-
• Plans for the JPL meetup and tour
|
| 6 |
-
• Brent's experience living in Alex's automated smart home system during his stay
|
| 7 |
-
• The speaker met Alex and others at an airport due to flight delays
|
| 8 |
-
• They discussed home automation systems, including Home Assistant
|
| 9 |
-
• The speaker was initially familiar with the system thanks to a meetup in Raleigh
|
| 10 |
-
• The speaker mentioned specific routines they wanted to replicate, such as bedtime countdowns and shutdowns
|
| 11 |
-
• The speaker described their own automated routines for bedtime, last call, and a hard cutoff at 2:30am
|
| 12 |
-
• Alex's automation system and its complexities
|
| 13 |
-
• Brent's experience with Alex's system and finding bugs
|
| 14 |
-
• The importance of modular logic in automations
|
| 15 |
-
• Delays and timers in automations
|
| 16 |
-
• Personalized buttons for tasks (e.g., bedtime routines)
|
| 17 |
-
• Home automation challenges and edge cases
|
| 18 |
-
• Reliability issues with certain devices (e.g., Xiaomi temperature sensors)
|
| 19 |
-
• Difficulty in noticing automation success due to its subtlety
|
| 20 |
-
• Discussion of a specific kitchen light automation setup using Hue and Conbee devices
|
| 21 |
-
• Edge cases in user behavior (e.g., Brent spending extended periods in a cozy chair)
|
| 22 |
-
• Challenges in setting optimal timeout values for automated systems
|
| 23 |
-
• Importance of understanding user behavior for effective automation design
|
| 24 |
-
• Mood lighting in Alex's bonus room/lounge area
|
| 25 |
-
• Implementation of automated lighting system based on sun elevation, not time of day
|
| 26 |
-
• The speaker discusses their plan to control a Velux rooflight using a remote control
|
| 27 |
-
• They express frustration with the difficulty of hacking the remote's encryption protocol
|
| 28 |
-
• The speaker recommends using an ESP device to mimic button presses on the remote
|
| 29 |
-
• They suggest getting a replacement remote for safety
|
| 30 |
-
• The speaker promotes Humio, a centralized log management and observability platform
|
| 31 |
-
• They discuss its features, including index-free architecture and reduced hardware footprint
|
| 32 |
-
• The speaker recommends starting with Humio's Community Edition for self-hosters
|
| 33 |
-
• They mention that it can ingest up to 16 gigs per day with seven days of retention
|
| 34 |
-
• The speaker expresses sympathy for Jeff Geerling, a friend of the show who has been dealing with health issues
|
| 35 |
-
• Introduction to new Shelly devices and their features
|
| 36 |
-
• Discussion on replacing Z-Wave devices with Wi-Fi devices for easier setup
|
| 37 |
-
• Review of the Shelly H&T sensor, its e-ink display, and USB-C power capabilities
|
| 38 |
-
• Concerns about the need for sleep mode causing disconnections from Home Assistant
|
| 39 |
-
• Comparison to using an ESP8266 and a cheap temperature sensor as an alternative
|
| 40 |
-
• Designing and considerations for 3D printed enclosures of ESP devices
|
| 41 |
-
• Comparison between Shelley and AOTech temperature sensors
|
| 42 |
-
• Limitations of Wi-Fi in IoT devices and potential issues with scalability
|
| 43 |
-
• Advantages of Zigbee mesh networks over Wi-Fi
|
| 44 |
-
• Discussion of specific temperature sensor models and their performance
|
| 45 |
-
• Need for continuous data from temperature sensors without gaps or hour-long intervals
|
| 46 |
-
• Potential use of Zigbee-based devices that can provide real-time data without MQTT requirements
|
| 47 |
-
• Temperature sensors and Shelly devices being used together
|
| 48 |
-
• Discussion of cheap smart plug options from China (e.g. AliExpress)
|
| 49 |
-
• Plans to create custom cases for Shelly devices with a 3D printer
|
| 50 |
-
• Comparison of different smart plugs, including the Shelly Power device
|
| 51 |
-
• Benefits of the Shelly Power device, such as no low-power issues and accurate power monitoring
|
| 52 |
-
• Shelly smart plugs being used in an RV to control lights and appliances
|
| 53 |
-
• Discussion of connectivity and reliability issues with the devices
|
| 54 |
-
• Mention of wiring Shelly devices into wall switches for additional functionality
|
| 55 |
-
• Review of Shelly's products, specifically the smart plugs, and their integration with Home Assistant
|
| 56 |
-
• Linode cloud hosting services and features (data centers, performance, pricing)
|
| 57 |
-
• Personal experience with migrating services to Linode during a hot summer
|
| 58 |
-
• Recap of London meetup
|
| 59 |
-
• Remaining stickers from London meetup will be distributed on West Coast road tour
|
| 60 |
-
• Plans to hide geocaches along route of West Coast road tour
|
| 61 |
-
• Upcoming meetups in Pasadena and LA area around time of West Coast road tour
|
| 62 |
-
• Opportunity for listeners to attend a tour at the Jet Propulsion Laboratory (JPL)
|
| 63 |
-
• Plans for Linux trivia or self-hosting trivia during meetups
|
| 64 |
-
• Meetups help reconnect with listeners and are medically necessary
|
| 65 |
-
• Matrix space for meetups and coordinating details is being used
|
| 66 |
-
• West Coast crew chat for discussing meetup plans
|
| 67 |
-
• New rules for boosts: 2000 sat limit to get read on air
|
| 68 |
-
• Experimenting with boost segment, want to keep it tight and moving
|
| 69 |
-
• Make good boost this week was accidentally sent into the wrong show
|
| 70 |
-
• The user's Echo device is malfunctioning and giving unwanted responses
|
| 71 |
-
• HomePods are also experiencing similar issues
|
| 72 |
-
• Sentience of AI devices is being discussed as a possible explanation for the problems
|
| 73 |
-
• Siri on the phone is still working normally
|
| 74 |
-
• A Google Home device was used in an unconventional way by someone, turning it into a Bluetooth speaker
|
| 75 |
-
• The user is considering using Pihole or AdGuard to improve their internet security and reduce ads
|
| 76 |
-
• Syncing DNS between multiple sites with Gravity Sync and AdGuard Home is being discussed as a potential setup for redundancy
|
| 77 |
-
• DNS server setup on LAN for local performance and reduced latency
|
| 78 |
-
• OpenSense operating system, its installation and configuration experiences
|
| 79 |
-
• Subnet issues due to overlapping IP ranges from remote networks (e.g., Starlink)
|
| 80 |
-
• Consideration of using a different operating system or approach for firewall management
|
| 81 |
-
• Desire for automated infrastructure as code solutions (e.g., Ansible) to simplify maintenance
|
| 82 |
-
• Discussion of the OpenSense idea and its potential benefits
|
| 83 |
-
• Reflection on how the conversation has evolved over time, including a mention of discovering Shelley
|
| 84 |
-
• Consideration of switching from PFSense/OpenSense to a different firewall solution
|
| 85 |
-
• Explanation of the current setup and concerns about responsibility for any changes
|
| 86 |
-
• Mention of DNS and DHCP services and their co-location
|
| 87 |
-
• Audience questions and discussion of passing on secrets after death
|
| 88 |
-
• Use of Bitwarden's emergency contact feature and encrypted USB for secure data transfer
|
| 89 |
-
• Thanking audience members who boosted in under 2,000 sats
|
| 90 |
-
• Discussion of Brentley's upcoming availability and potential van life considerations
|
| 91 |
-
• The host mentions a listener's need for a "short bus" and jokes about their life
|
| 92 |
-
• A discussion of the host vicariously living through listeners' experiences and squandering single life opportunities
|
| 93 |
-
• Promotion of upcoming meetups and events, including JPL and Jupiter Broadcasting gatherings
|
| 94 |
-
• Gratitude to site reliability engineers and members for supporting the show
|
| 95 |
-
• Announcement of an ad-free feed with additional features for supporting members
|
| 96 |
• Encouragement to attend meetups and provide feedback on various topics, including snaps
|
|
|
|
| 1 |
+
• Jet lag discussed and its effects on Alex's daily routine
|
| 2 |
+
• Difficulty adjusting to eastward travel from America due to red eye flights and lost sleep
|
| 3 |
+
• Benefits of having a trusted person (Brent) take care of home responsibilities while away
|
| 4 |
+
• Discussion about the World Excel Championships, competitive spreadsheet writing, and potential for self-hosted trivia nights
|
| 5 |
+
• Plans for the JPL meetup and tour
|
| 6 |
+
• Brent's experience living in Alex's automated smart home system during his stay
|
| 7 |
+
• The speaker met Alex and others at an airport due to flight delays
|
| 8 |
+
• They discussed home automation systems, including Home Assistant
|
| 9 |
+
• The speaker was initially familiar with the system thanks to a meetup in Raleigh
|
| 10 |
+
• The speaker mentioned specific routines they wanted to replicate, such as bedtime countdowns and shutdowns
|
| 11 |
+
• The speaker described their own automated routines for bedtime, last call, and a hard cutoff at 2:30am
|
| 12 |
+
• Alex's automation system and its complexities
|
| 13 |
+
• Brent's experience with Alex's system and finding bugs
|
| 14 |
+
• The importance of modular logic in automations
|
| 15 |
+
• Delays and timers in automations
|
| 16 |
+
• Personalized buttons for tasks (e.g., bedtime routines)
|
| 17 |
+
• Home automation challenges and edge cases
|
| 18 |
+
• Reliability issues with certain devices (e.g., Xiaomi temperature sensors)
|
| 19 |
+
• Difficulty in noticing automation success due to its subtlety
|
| 20 |
+
• Discussion of a specific kitchen light automation setup using Hue and Conbee devices
|
| 21 |
+
• Edge cases in user behavior (e.g., Brent spending extended periods in a cozy chair)
|
| 22 |
+
• Challenges in setting optimal timeout values for automated systems
|
| 23 |
+
• Importance of understanding user behavior for effective automation design
|
| 24 |
+
• Mood lighting in Alex's bonus room/lounge area
|
| 25 |
+
• Implementation of automated lighting system based on sun elevation, not time of day
|
| 26 |
+
• The speaker discusses their plan to control a Velux rooflight using a remote control
|
| 27 |
+
• They express frustration with the difficulty of hacking the remote's encryption protocol
|
| 28 |
+
• The speaker recommends using an ESP device to mimic button presses on the remote
|
| 29 |
+
• They suggest getting a replacement remote for safety
|
| 30 |
+
• The speaker promotes Humio, a centralized log management and observability platform
|
| 31 |
+
• They discuss its features, including index-free architecture and reduced hardware footprint
|
| 32 |
+
• The speaker recommends starting with Humio's Community Edition for self-hosters
|
| 33 |
+
• They mention that it can ingest up to 16 gigs per day with seven days of retention
|
| 34 |
+
• The speaker expresses sympathy for Jeff Geerling, a friend of the show who has been dealing with health issues
|
| 35 |
+
• Introduction to new Shelly devices and their features
|
| 36 |
+
• Discussion on replacing Z-Wave devices with Wi-Fi devices for easier setup
|
| 37 |
+
• Review of the Shelly H&T sensor, its e-ink display, and USB-C power capabilities
|
| 38 |
+
• Concerns about the need for sleep mode causing disconnections from Home Assistant
|
| 39 |
+
• Comparison to using an ESP8266 and a cheap temperature sensor as an alternative
|
| 40 |
+
• Designing and considerations for 3D printed enclosures of ESP devices
|
| 41 |
+
• Comparison between Shelley and AOTech temperature sensors
|
| 42 |
+
• Limitations of Wi-Fi in IoT devices and potential issues with scalability
|
| 43 |
+
• Advantages of Zigbee mesh networks over Wi-Fi
|
| 44 |
+
• Discussion of specific temperature sensor models and their performance
|
| 45 |
+
• Need for continuous data from temperature sensors without gaps or hour-long intervals
|
| 46 |
+
• Potential use of Zigbee-based devices that can provide real-time data without MQTT requirements
|
| 47 |
+
• Temperature sensors and Shelly devices being used together
|
| 48 |
+
• Discussion of cheap smart plug options from China (e.g. AliExpress)
|
| 49 |
+
• Plans to create custom cases for Shelly devices with a 3D printer
|
| 50 |
+
• Comparison of different smart plugs, including the Shelly Power device
|
| 51 |
+
• Benefits of the Shelly Power device, such as no low-power issues and accurate power monitoring
|
| 52 |
+
• Shelly smart plugs being used in an RV to control lights and appliances
|
| 53 |
+
• Discussion of connectivity and reliability issues with the devices
|
| 54 |
+
• Mention of wiring Shelly devices into wall switches for additional functionality
|
| 55 |
+
• Review of Shelly's products, specifically the smart plugs, and their integration with Home Assistant
|
| 56 |
+
• Linode cloud hosting services and features (data centers, performance, pricing)
|
| 57 |
+
• Personal experience with migrating services to Linode during a hot summer
|
| 58 |
+
• Recap of London meetup
|
| 59 |
+
• Remaining stickers from London meetup will be distributed on West Coast road tour
|
| 60 |
+
• Plans to hide geocaches along route of West Coast road tour
|
| 61 |
+
• Upcoming meetups in Pasadena and LA area around time of West Coast road tour
|
| 62 |
+
• Opportunity for listeners to attend a tour at the Jet Propulsion Laboratory (JPL)
|
| 63 |
+
• Plans for Linux trivia or self-hosting trivia during meetups
|
| 64 |
+
• Meetups help reconnect with listeners and are medically necessary
|
| 65 |
+
• Matrix space for meetups and coordinating details is being used
|
| 66 |
+
• West Coast crew chat for discussing meetup plans
|
| 67 |
+
• New rules for boosts: 2000 sat limit to get read on air
|
| 68 |
+
• Experimenting with boost segment, want to keep it tight and moving
|
| 69 |
+
• Make good boost this week was accidentally sent into the wrong show
|
| 70 |
+
• The user's Echo device is malfunctioning and giving unwanted responses
|
| 71 |
+
• HomePods are also experiencing similar issues
|
| 72 |
+
• Sentience of AI devices is being discussed as a possible explanation for the problems
|
| 73 |
+
• Siri on the phone is still working normally
|
| 74 |
+
• A Google Home device was used in an unconventional way by someone, turning it into a Bluetooth speaker
|
| 75 |
+
• The user is considering using Pihole or AdGuard to improve their internet security and reduce ads
|
| 76 |
+
• Syncing DNS between multiple sites with Gravity Sync and AdGuard Home is being discussed as a potential setup for redundancy
|
| 77 |
+
• DNS server setup on LAN for local performance and reduced latency
|
| 78 |
+
• OpenSense operating system, its installation and configuration experiences
|
| 79 |
+
• Subnet issues due to overlapping IP ranges from remote networks (e.g., Starlink)
|
| 80 |
+
• Consideration of using a different operating system or approach for firewall management
|
| 81 |
+
• Desire for automated infrastructure as code solutions (e.g., Ansible) to simplify maintenance
|
| 82 |
+
• Discussion of the OpenSense idea and its potential benefits
|
| 83 |
+
• Reflection on how the conversation has evolved over time, including a mention of discovering Shelley
|
| 84 |
+
• Consideration of switching from PFSense/OpenSense to a different firewall solution
|
| 85 |
+
• Explanation of the current setup and concerns about responsibility for any changes
|
| 86 |
+
• Mention of DNS and DHCP services and their co-location
|
| 87 |
+
• Audience questions and discussion of passing on secrets after death
|
| 88 |
+
• Use of Bitwarden's emergency contact feature and encrypted USB for secure data transfer
|
| 89 |
+
• Thanking audience members who boosted in under 2,000 sats
|
| 90 |
+
• Discussion of Brentley's upcoming availability and potential van life considerations
|
| 91 |
+
• The host mentions a listener's need for a "short bus" and jokes about their life
|
| 92 |
+
• A discussion of the host vicariously living through listeners' experiences and squandering single life opportunities
|
| 93 |
+
• Promotion of upcoming meetups and events, including JPL and Jupiter Broadcasting gatherings
|
| 94 |
+
• Gratitude to site reliability engineers and members for supporting the show
|
| 95 |
+
• Announcement of an ad-free feed with additional features for supporting members
|
| 96 |
• Encouragement to attend meetups and provide feedback on various topics, including snaps
|
78: We Should Know Better _summary.txt
CHANGED
|
@@ -1,83 +1,83 @@
|
|
| 1 |
-
• Loss of Brent
|
| 2 |
-
• The hosts' experiences with their Canadian friend Brent's eating habits and lifestyle
|
| 3 |
-
• Discovery of a Plex data breach
|
| 4 |
-
• Concerns about relying on cloud-based services for media playback, particularly Plex
|
| 5 |
-
• Discussion of alternative options like Jellyfin
|
| 6 |
-
• Comparison of the ecosystems of Plex and Jellyfin
|
| 7 |
-
• The user is having trouble connecting to their Plex server and local files.
|
| 8 |
-
• They mention the app Tautooli, which tracks playback stats for users.
|
| 9 |
-
• The user discusses using Tautooli for cleaning up unused library items.
|
| 10 |
-
• They mention a "Better Call Saul" binge and how it's part of the ecosystem they're discussing.
|
| 11 |
-
• The user introduces Overseer, an app that helps discover trending and popular content with great UI integration.
|
| 12 |
-
• Overseer has full Plex library integration and can integrate with local accounts or Plex user accounts.
|
| 13 |
-
• The user compares Overseer to other apps in the space and notes that it's not impossible to use Jellyfin with it.
|
| 14 |
-
• Discussion about a tool called "third rail" and its potential uses
|
| 15 |
-
• Linode.com services, including cloud hosting and infrastructure options
|
| 16 |
-
• Importance of Linux skills for cybersecurity
|
| 17 |
-
• Features and benefits of using Linode for web development and deployment
|
| 18 |
-
• Article in the New York Times about Google's automatic photo backup and data sharing with law enforcement
|
| 19 |
-
• Google's auto-flagging system for child abuse material flagged a man's photos in his Google Photos account
|
| 20 |
-
• The police were notified, and the man's Google account was disabled, including his cell phone service
|
| 21 |
-
• This led to issues with the police being able to contact him, and he was presumed guilty without due process
|
| 22 |
-
• Another case of this happening was reported around the same time in a New York Times article
|
| 23 |
-
• Google refuses to turn off the accounts even after the police have cleared them
|
| 24 |
-
• The man's entire Google account data was sent to the cops for review, including emails, text messages, and location information
|
| 25 |
-
• This raises concerns about user manipulation, surveillance, and the power of tech companies over individuals
|
| 26 |
-
• The speaker expresses concern about the extent of Google's data collection and potential sharing with law enforcement
|
| 27 |
-
• The Fourth Amendment protections apply only to government actions, not private companies like Google
|
| 28 |
-
• The lines between what is acceptable for Google and what is not are unclear, creating a "just not-my-problem-legal situation"
|
| 29 |
-
• The speaker believes that both Google and the state benefit from this arrangement, making it unlikely to change
|
| 30 |
-
• A specific case of someone having their Gmail account suspended despite being cleared by law enforcement is cited as an example of the problem
|
| 31 |
-
• The speaker advises users to have valid backups for important data and considers switching away from Google services due to these concerns.
|
| 32 |
-
• Risks of data collection by companies such as Plex and Google
|
| 33 |
-
• Importance of backing up online data, particularly Gmail
|
| 34 |
-
• Alternative methods for backing up Gmail data, including using Thunderbird and offline IMAP
|
| 35 |
-
• Specific tool called Got Your Back (GYB) for backing up Gmail data via command line
|
| 36 |
-
• Discussion of the project's maturity and potential issues with unverified binaries
|
| 37 |
-
• The speaker mentions a potential project to delete unwanted Gmail features
|
| 38 |
-
• Image, a self-hosted photo app, is discussed as an alternative to Google Photos
|
| 39 |
-
• Humio, a log management platform, is introduced with its unique architecture and cost-effectiveness
|
| 40 |
-
• The Humio community edition is highlighted as a no-cost option for data ingestion and log management
|
| 41 |
-
• Zigbee and home automation setup are briefly mentioned
|
| 42 |
-
• The user has found a new temperature sensor that works well with Home Assistant: the Aquara temperature and humidity sensor.
|
| 43 |
-
• It is Zigbee-based, battery-powered, and provides real-time data updates as the temperature changes.
|
| 44 |
-
• It has two years of battery life and is extremely small in size.
|
| 45 |
-
• The user likes the idea of using Zigbee devices to replace Z-Wave ones and appreciates its features, including wired device repeaters and a 100-meter line-of-sight range.
|
| 46 |
-
• Permanently powered devices such as smart plugs and light bulbs can be used as repeaters to extend the Zigbee network.
|
| 47 |
-
• The user has had good experiences with other users' temperature sensors, including one in their fridge that still works on its original battery after being installed for a while.
|
| 48 |
-
• The speaker discusses their experience with a lithium Duracell battery and its smaller size compared to the CR2032 battery.
|
| 49 |
-
• The speaker mentions a handy circular double-sided tape included in the box for easy installation of the sensor.
|
| 50 |
-
• The conversation shifts to the topic of smart home devices and wireless standards, specifically Zigbee, Matter, and Z-Wave.
|
| 51 |
-
• The speaker explains their decision to transition from Z-Wave to Zigbee due to its open-source nature and long-term potential.
|
| 52 |
-
• They mention the benefits of Zigbee over Wi-Fi for IoT devices, including improved battery life and network performance.
|
| 53 |
-
• The conversation ends with the speaker discussing their enthusiasm for using Zigbee devices in their home automation setup.
|
| 54 |
-
• Mountable LED light for wheel well
|
| 55 |
-
• Weatherproof requirements for the mountable LED light
|
| 56 |
-
• Conversion to Zigbee lighting system
|
| 57 |
-
• Replacing Z-Wave devices with Zigbee ones
|
| 58 |
-
• Temperature sensors and their benefits
|
| 59 |
-
• Upcoming West Coast meetups and events
|
| 60 |
-
• Matrix chat room discussions for meetup planning
|
| 61 |
-
• Discussion about attending a meetup in LA/Pasadena area
|
| 62 |
-
• Mention of the Southern meetup and JPL event
|
| 63 |
-
• Talk about boosting for a top five list of boosts this week
|
| 64 |
-
• Conversation about Home Assistant and potential alternatives like Hubitat
|
| 65 |
-
• Discussion about self-hosting and user preferences, including mention of Linux, Seuss, and AutoYest
|
| 66 |
-
• Boosters are announced, including Prozac and Kaspilin
|
| 67 |
-
• Discussion of Seuss and its use in home labs
|
| 68 |
-
• Colin's positive review of OpenSeuss
|
| 69 |
-
• Aquara Zigbee temp sensors recommended by Colin
|
| 70 |
-
• Shelly one device struggles with e-ink display integration
|
| 71 |
-
• Purple Dog boosts 2,500 sats after narrowly avoiding injury
|
| 72 |
-
• Row of ducks donated by user 604 recommends Microtik routers and Ansible management
|
| 73 |
-
• Deck bot suggests using Pi 4 compute module 4 with OpenWrt for a router
|
| 74 |
-
• Discussion about Fountain FM's transcription and clip sharing
|
| 75 |
-
• Recommendation to try new podcast apps that support clips and boosting
|
| 76 |
-
• Pre-ordering of the ASRock A380 GPU from Newegg and its features with QuickSync hardware and AV1 codex
|
| 77 |
-
• Excitement for Intel Arc GPUs due to their ability to handle tasks like transcoding and pass-through with Windows VMs
|
| 78 |
-
• Plans to test the new GPU's capabilities on the show
|
| 79 |
-
• Discussion of a scenario likely to start with
|
| 80 |
-
• Mention of a post-show bonus for members
|
| 81 |
-
• Promotion of membership and its benefits, including ad-free feed and special features
|
| 82 |
-
• Announcement of upcoming meetups on the West Coast
|
| 83 |
• Invitation to contact the show through selfhosted.show or Twitter
|
|
|
|
| 1 |
+
• Loss of Brent
|
| 2 |
+
• The hosts' experiences with their Canadian friend Brent's eating habits and lifestyle
|
| 3 |
+
• Discovery of a Plex data breach
|
| 4 |
+
• Concerns about relying on cloud-based services for media playback, particularly Plex
|
| 5 |
+
• Discussion of alternative options like Jellyfin
|
| 6 |
+
• Comparison of the ecosystems of Plex and Jellyfin
|
| 7 |
+
• The user is having trouble connecting to their Plex server and local files.
|
| 8 |
+
• They mention the app Tautooli, which tracks playback stats for users.
|
| 9 |
+
• The user discusses using Tautooli for cleaning up unused library items.
|
| 10 |
+
• They mention a "Better Call Saul" binge and how it's part of the ecosystem they're discussing.
|
| 11 |
+
• The user introduces Overseer, an app that helps discover trending and popular content with great UI integration.
|
| 12 |
+
• Overseer has full Plex library integration and can integrate with local accounts or Plex user accounts.
|
| 13 |
+
• The user compares Overseer to other apps in the space and notes that it's not impossible to use Jellyfin with it.
|
| 14 |
+
• Discussion about a tool called "third rail" and its potential uses
|
| 15 |
+
• Linode.com services, including cloud hosting and infrastructure options
|
| 16 |
+
• Importance of Linux skills for cybersecurity
|
| 17 |
+
• Features and benefits of using Linode for web development and deployment
|
| 18 |
+
• Article in the New York Times about Google's automatic photo backup and data sharing with law enforcement
|
| 19 |
+
• Google's auto-flagging system for child abuse material flagged a man's photos in his Google Photos account
|
| 20 |
+
• The police were notified, and the man's Google account was disabled, including his cell phone service
|
| 21 |
+
• This led to issues with the police being able to contact him, and he was presumed guilty without due process
|
| 22 |
+
• Another case of this happening was reported around the same time in a New York Times article
|
| 23 |
+
• Google refuses to turn off the accounts even after the police have cleared them
|
| 24 |
+
• The man's entire Google account data was sent to the cops for review, including emails, text messages, and location information
|
| 25 |
+
• This raises concerns about user manipulation, surveillance, and the power of tech companies over individuals
|
| 26 |
+
• The speaker expresses concern about the extent of Google's data collection and potential sharing with law enforcement
|
| 27 |
+
• The Fourth Amendment protections apply only to government actions, not private companies like Google
|
| 28 |
+
• The lines between what is acceptable for Google and what is not are unclear, creating a "just not-my-problem-legal situation"
|
| 29 |
+
• The speaker believes that both Google and the state benefit from this arrangement, making it unlikely to change
|
| 30 |
+
• A specific case of someone having their Gmail account suspended despite being cleared by law enforcement is cited as an example of the problem
|
| 31 |
+
• The speaker advises users to have valid backups for important data and considers switching away from Google services due to these concerns.
|
| 32 |
+
• Risks of data collection by companies such as Plex and Google
|
| 33 |
+
• Importance of backing up online data, particularly Gmail
|
| 34 |
+
• Alternative methods for backing up Gmail data, including using Thunderbird and offline IMAP
|
| 35 |
+
• Specific tool called Got Your Back (GYB) for backing up Gmail data via command line
|
| 36 |
+
• Discussion of the project's maturity and potential issues with unverified binaries
|
| 37 |
+
• The speaker mentions a potential project to delete unwanted Gmail features
|
| 38 |
+
• Image, a self-hosted photo app, is discussed as an alternative to Google Photos
|
| 39 |
+
• Humio, a log management platform, is introduced with its unique architecture and cost-effectiveness
|
| 40 |
+
• The Humio community edition is highlighted as a no-cost option for data ingestion and log management
|
| 41 |
+
• Zigbee and home automation setup are briefly mentioned
|
| 42 |
+
• The user has found a new temperature sensor that works well with Home Assistant: the Aquara temperature and humidity sensor.
|
| 43 |
+
• It is Zigbee-based, battery-powered, and provides real-time data updates as the temperature changes.
|
| 44 |
+
• It has two years of battery life and is extremely small in size.
|
| 45 |
+
• The user likes the idea of using Zigbee devices to replace Z-Wave ones and appreciates its features, including wired device repeaters and a 100-meter line-of-sight range.
|
| 46 |
+
• Permanently powered devices such as smart plugs and light bulbs can be used as repeaters to extend the Zigbee network.
|
| 47 |
+
• The user has had good experiences with other users' temperature sensors, including one in their fridge that still works on its original battery after being installed for a while.
|
| 48 |
+
• The speaker discusses their experience with a lithium Duracell battery and its smaller size compared to the CR2032 battery.
|
| 49 |
+
• The speaker mentions a handy circular double-sided tape included in the box for easy installation of the sensor.
|
| 50 |
+
• The conversation shifts to the topic of smart home devices and wireless standards, specifically Zigbee, Matter, and Z-Wave.
|
| 51 |
+
• The speaker explains their decision to transition from Z-Wave to Zigbee due to its open-source nature and long-term potential.
|
| 52 |
+
• They mention the benefits of Zigbee over Wi-Fi for IoT devices, including improved battery life and network performance.
|
| 53 |
+
• The conversation ends with the speaker discussing their enthusiasm for using Zigbee devices in their home automation setup.
|
| 54 |
+
• Mountable LED light for wheel well
|
| 55 |
+
• Weatherproof requirements for the mountable LED light
|
| 56 |
+
• Conversion to Zigbee lighting system
|
| 57 |
+
• Replacing Z-Wave devices with Zigbee ones
|
| 58 |
+
• Temperature sensors and their benefits
|
| 59 |
+
• Upcoming West Coast meetups and events
|
| 60 |
+
• Matrix chat room discussions for meetup planning
|
| 61 |
+
• Discussion about attending a meetup in LA/Pasadena area
|
| 62 |
+
• Mention of the Southern meetup and JPL event
|
| 63 |
+
• Talk about boosting for a top five list of boosts this week
|
| 64 |
+
• Conversation about Home Assistant and potential alternatives like Hubitat
|
| 65 |
+
• Discussion about self-hosting and user preferences, including mention of Linux, Seuss, and AutoYest
|
| 66 |
+
• Boosters are announced, including Prozac and Kaspilin
|
| 67 |
+
• Discussion of Seuss and its use in home labs
|
| 68 |
+
• Colin's positive review of OpenSeuss
|
| 69 |
+
• Aquara Zigbee temp sensors recommended by Colin
|
| 70 |
+
• Shelly one device struggles with e-ink display integration
|
| 71 |
+
• Purple Dog boosts 2,500 sats after narrowly avoiding injury
|
| 72 |
+
• Row of ducks donated by user 604 recommends Microtik routers and Ansible management
|
| 73 |
+
• Deck bot suggests using Pi 4 compute module 4 with OpenWrt for a router
|
| 74 |
+
• Discussion about Fountain FM's transcription and clip sharing
|
| 75 |
+
• Recommendation to try new podcast apps that support clips and boosting
|
| 76 |
+
• Pre-ordering of the ASRock A380 GPU from Newegg and its features with QuickSync hardware and AV1 codex
|
| 77 |
+
• Excitement for Intel Arc GPUs due to their ability to handle tasks like transcoding and pass-through with Windows VMs
|
| 78 |
+
• Plans to test the new GPU's capabilities on the show
|
| 79 |
+
• Discussion of a scenario likely to start with
|
| 80 |
+
• Mention of a post-show bonus for members
|
| 81 |
+
• Promotion of membership and its benefits, including ad-free feed and special features
|
| 82 |
+
• Announcement of upcoming meetups on the West Coast
|
| 83 |
• Invitation to contact the show through selfhosted.show or Twitter
|
79: Google is a Hostile Actor _summary.txt
CHANGED
|
@@ -1,101 +1,101 @@
|
|
| 1 |
-
• Planning a road trip and doing pre-flight checks on home assistant and other systems
|
| 2 |
-
• Avoiding updating or fixing issues during the trip by doing it beforehand
|
| 3 |
-
• Celebrating three years of self-hosted episodes and considering future episode themes based on decade-specific music
|
| 4 |
-
• Discussing the possibility of being acquired by Google and later unmerging
|
| 5 |
-
• Joking about marriage and relationships
|
| 6 |
-
• Sharing experiences with a new Intel Arc GPU, including using it for server pass-through and hardware encoding
|
| 7 |
-
• Difficulty in getting pass-through functionality for a Linux VM
|
| 8 |
-
• New graphics card is very new and Intel drivers are included in the kernel
|
| 9 |
-
• Motivation vs waiting for driver support
|
| 10 |
-
• Testing media server performance with AV1 encoders and various software
|
| 11 |
-
• Potential to upgrade old hardware with new graphics cards
|
| 12 |
-
• Discussion of Steam Deck, including its limitations for certain games
|
| 13 |
-
• Impressed with Steam Deck's casual gaming capabilities and retro emulator
|
| 14 |
-
• The Steam Deck is praised for being a first-generation device with significant progress in furthering the Linux narrative.
|
| 15 |
-
• Battery life and charging are discussed as areas for improvement.
|
| 16 |
-
• The value of supporting Valve's efforts through purchasing the Steam Deck is emphasized.
|
| 17 |
-
• Comparison to proprietary gaming ecosystems, such as Nintendo Switch, highlights the benefits of running on an open system like Linux.
|
| 18 |
-
• Integrated use of the Steam Deck in home lab setups and its capabilities with USB-C monitors are showcased.
|
| 19 |
-
• Feedback from listeners about a previous topic (episode 78) discusses Google's actions regarding user data.
|
| 20 |
-
• Concerns about Google services and their potential for tracking and data collection
|
| 21 |
-
• Plans to cancel Google Fi and switch to T-Mobile
|
| 22 |
-
• Use of Tailscale and consideration of moving to Headscale for self-hosted authentication
|
| 23 |
-
• Understanding of the trade-off between convenience and privacy when using online services
|
| 24 |
-
• Discussion of the implications of not participating in large-scale systems and being a target for surveillance
|
| 25 |
-
• The concept of being flagged by machine learning algorithms and avoiding "traps"
|
| 26 |
-
• The dystopian future where individuals are forced to use certain tech companies' services (e.g. Amazon Prime) due to lack of alternatives
|
| 27 |
-
• The idea of "not putting all eggs in one basket" and spreading risk with alternative services (e.g. Fastmail, Protonmail)
|
| 28 |
-
• A discussion about a self-hosted email user who stopped hosting their own mail server after 23 years due to issues with deliverability and competition stifling
|
| 29 |
-
• Concerns about net neutrality and oligarchies controlling the internet, including big companies cutting off residential IPs, VPSs, and self-hosters
|
| 30 |
-
• The importance of owning one's domain name as a way to maintain control over online services
|
| 31 |
-
• The guest and host discuss email being a centralized system with large tech companies controlling it
|
| 32 |
-
• Matrix is mentioned as a decentralized alternative for communication and data storage
|
| 33 |
-
• Image, a self-hosted photo and video backup solution, is discussed
|
| 34 |
-
• The Fourth Amendment's protection against government searches may not apply to EULAs allowing company searches
|
| 35 |
-
• Background APIs on iOS are a challenge for developers trying to create self-hosted solutions like Image
|
| 36 |
-
• The benefits and drawbacks of using cloud services vs self-hosted applications
|
| 37 |
-
• Concerns about data privacy and the role of big tech companies in collecting and sharing user data
|
| 38 |
-
• Discussion of alternative funding models, such as GitHub sponsorships or "buy me a coffee" platforms
|
| 39 |
-
• Introduction to Linode, a cloud platform with 11 data centers and robust support for Linux users
|
| 40 |
-
• Comparison of Linode's features and benefits to other cloud services
|
| 41 |
-
• The speaker discusses their positive experience with Linode and recommends it for hosting websites.
|
| 42 |
-
• Home Assistant celebrates its ninth birthday, with version 22.9 being released as a birthday release.
|
| 43 |
-
• The new release includes improvements to the user interface, including collapsible cards for triggers, conditions, and actions.
|
| 44 |
-
• Bluetooth improvements allow for faster communication, and ESP-232 devices can be used as Bluetooth proxies.
|
| 45 |
-
• Zigbee users will appreciate the new backup and restore option in Home Assistant.
|
| 46 |
-
• The speaker's physical Home Assistant device is delayed and will not arrive until they return from a trip.
|
| 47 |
-
• Home Assistant now supports restoring and migrating Zigbee devices
|
| 48 |
-
• New UI updates for monitoring processor and memory usage on hardware devices
|
| 49 |
-
• Integration of Android IP webcam app allows easy setup of tablets as cameras feeding into Home Assistant
|
| 50 |
-
• Integration with Fully Kiosk browser enables controlling and monitoring tablet activity within Home Assistant
|
| 51 |
-
• User experience of ease of use and integrations is highlighted, including an "aha moment" with the Elgato key light integration
|
| 52 |
-
• Other notable mentions include Shelly devices integrating seamlessly with Home Assistant.
|
| 53 |
-
• Running power usage benchmarks with a kilowatt meter and logging results
|
| 54 |
-
• Using Home Assistant for monitoring and reviewing historical data
|
| 55 |
-
• Exporting data to InfluxDB for time-series analysis and graphing
|
| 56 |
-
• Tips for using Influx, including SSD storage and split DNS functionality
|
| 57 |
-
• Installing the Tail Scale integration in Home Assistant OS
|
| 58 |
-
• Remote access to Home Assistant instances via Nebukasa Cloud and Tail Scale
|
| 59 |
-
• Differences between official and community tail scale versions
|
| 60 |
-
• Importance of home assistant OS-based system for tail scale network integration
|
| 61 |
-
• Humio, a centralized log management and observability platform
|
| 62 |
-
• Humio Community Edition, a no-cost data ingestion offering with up to 16 gigs per day retention
|
| 63 |
-
• Personal experience with iOS 16 beta on iPad
|
| 64 |
-
• Discussion of satellite calling and its potential uses
|
| 65 |
-
• Mention of the Pixel 3's "Always On Display" feature
|
| 66 |
-
• Joking about ordering a pizza in Death Valley via DoorDash
|
| 67 |
-
• Upcoming meetups for Jupiter Broadcasting, including a tour of JPL
|
| 68 |
-
• Plans to have swag bags and other items at meetups
|
| 69 |
-
• Discussion of using Matrix for chat rooms and organizing meetups
|
| 70 |
-
• Inquiry about self-hosted meetup apps
|
| 71 |
-
• Adding new devices to a network is made easy with certain brands
|
| 72 |
-
• Recommendations for reliable devices, including Aquara and KiwiSet
|
| 73 |
-
• Discussion on MQTT and Zigbee connectivity
|
| 74 |
-
• Comparison of iPhone versus Android operating systems
|
| 75 |
-
• Personal experiences with OnePlus 7T and preference for Android features
|
| 76 |
-
• Observations on the usability and quirks of both iPhone and Android
|
| 77 |
-
• Control Center on iOS is not considered intuitive
|
| 78 |
-
• Personal preference plays a role in UI choices
|
| 79 |
-
• iPhone camera performance in low-light conditions is superior
|
| 80 |
-
• Switching between iOS and Android platforms is easy
|
| 81 |
-
• iOS is generally more stable than Android
|
| 82 |
-
• Apps on iOS are often native, polished, and performant
|
| 83 |
-
• Apple's privacy policies are considered better than those of other companies
|
| 84 |
-
• Jellyfin has several client options for streaming content, including Jellyamp and the Jellyfin audio player
|
| 85 |
-
• Discussion of switching from Plex to Jellyfin for audio books
|
| 86 |
-
• Search for alternative audiobook solutions in the Jellyfin ecosystem
|
| 87 |
-
• Introduction to and recommendation of Podverse as a podcast player
|
| 88 |
-
• Mention of other free software options such as Fountain, Albie, and Breeze
|
| 89 |
-
• Discussion of Boosts and sending sats to creators
|
| 90 |
-
• Independent podcasting and support for independent creators
|
| 91 |
-
• Criticism of dynamic ads in podcasting
|
| 92 |
-
• Promotion of subscribing to the JB Network
|
| 93 |
-
• Upcoming Jupiter.Tube broadcast on a Wednesday
|
| 94 |
-
• Update on new website jupiterbroadcasting.com, including:
|
| 95 |
-
• Dynamic live embedding on the live page
|
| 96 |
-
• Built in Hugo and self-hosted on Linode
|
| 97 |
-
• GitHub repository for contribution
|
| 98 |
-
• Meetups at meetup.com/jupiterbroadcasting
|
| 99 |
-
• Contact information:
|
| 100 |
-
• self-hosted.show/contact
|
| 101 |
• Twitter handles: Ironic Badger, Chris LAS
|
|
|
|
| 1 |
+
• Planning a road trip and doing pre-flight checks on home assistant and other systems
|
| 2 |
+
• Avoiding updating or fixing issues during the trip by doing it beforehand
|
| 3 |
+
• Celebrating three years of self-hosted episodes and considering future episode themes based on decade-specific music
|
| 4 |
+
• Discussing the possibility of being acquired by Google and later unmerging
|
| 5 |
+
• Joking about marriage and relationships
|
| 6 |
+
• Sharing experiences with a new Intel Arc GPU, including using it for server pass-through and hardware encoding
|
| 7 |
+
• Difficulty in getting pass-through functionality for a Linux VM
|
| 8 |
+
• New graphics card is very new and Intel drivers are included in the kernel
|
| 9 |
+
• Motivation vs waiting for driver support
|
| 10 |
+
• Testing media server performance with AV1 encoders and various software
|
| 11 |
+
• Potential to upgrade old hardware with new graphics cards
|
| 12 |
+
• Discussion of Steam Deck, including its limitations for certain games
|
| 13 |
+
• Impressed with Steam Deck's casual gaming capabilities and retro emulator
|
| 14 |
+
• The Steam Deck is praised for being a first-generation device with significant progress in furthering the Linux narrative.
|
| 15 |
+
• Battery life and charging are discussed as areas for improvement.
|
| 16 |
+
• The value of supporting Valve's efforts through purchasing the Steam Deck is emphasized.
|
| 17 |
+
• Comparison to proprietary gaming ecosystems, such as Nintendo Switch, highlights the benefits of running on an open system like Linux.
|
| 18 |
+
• Integrated use of the Steam Deck in home lab setups and its capabilities with USB-C monitors are showcased.
|
| 19 |
+
• Feedback from listeners about a previous topic (episode 78) discusses Google's actions regarding user data.
|
| 20 |
+
• Concerns about Google services and their potential for tracking and data collection
|
| 21 |
+
• Plans to cancel Google Fi and switch to T-Mobile
|
| 22 |
+
• Use of Tailscale and consideration of moving to Headscale for self-hosted authentication
|
| 23 |
+
• Understanding of the trade-off between convenience and privacy when using online services
|
| 24 |
+
• Discussion of the implications of not participating in large-scale systems and being a target for surveillance
|
| 25 |
+
• The concept of being flagged by machine learning algorithms and avoiding "traps"
|
| 26 |
+
• The dystopian future where individuals are forced to use certain tech companies' services (e.g. Amazon Prime) due to lack of alternatives
|
| 27 |
+
• The idea of "not putting all eggs in one basket" and spreading risk with alternative services (e.g. Fastmail, Protonmail)
|
| 28 |
+
• A discussion about a self-hosted email user who stopped hosting their own mail server after 23 years due to issues with deliverability and competition stifling
|
| 29 |
+
• Concerns about net neutrality and oligarchies controlling the internet, including big companies cutting off residential IPs, VPSs, and self-hosters
|
| 30 |
+
• The importance of owning one's domain name as a way to maintain control over online services
|
| 31 |
+
• The guest and host discuss email being a centralized system with large tech companies controlling it
|
| 32 |
+
• Matrix is mentioned as a decentralized alternative for communication and data storage
|
| 33 |
+
• Image, a self-hosted photo and video backup solution, is discussed
|
| 34 |
+
• The Fourth Amendment's protection against government searches may not apply to EULAs allowing company searches
|
| 35 |
+
• Background APIs on iOS are a challenge for developers trying to create self-hosted solutions like Image
|
| 36 |
+
• The benefits and drawbacks of using cloud services vs self-hosted applications
|
| 37 |
+
• Concerns about data privacy and the role of big tech companies in collecting and sharing user data
|
| 38 |
+
• Discussion of alternative funding models, such as GitHub sponsorships or "buy me a coffee" platforms
|
| 39 |
+
• Introduction to Linode, a cloud platform with 11 data centers and robust support for Linux users
|
| 40 |
+
• Comparison of Linode's features and benefits to other cloud services
|
| 41 |
+
• The speaker discusses their positive experience with Linode and recommends it for hosting websites.
|
| 42 |
+
• Home Assistant celebrates its ninth birthday, with version 22.9 being released as a birthday release.
|
| 43 |
+
• The new release includes improvements to the user interface, including collapsible cards for triggers, conditions, and actions.
|
| 44 |
+
• Bluetooth improvements allow for faster communication, and ESP-232 devices can be used as Bluetooth proxies.
|
| 45 |
+
• Zigbee users will appreciate the new backup and restore option in Home Assistant.
|
| 46 |
+
• The speaker's physical Home Assistant device is delayed and will not arrive until they return from a trip.
|
| 47 |
+
• Home Assistant now supports restoring and migrating Zigbee devices
|
| 48 |
+
• New UI updates for monitoring processor and memory usage on hardware devices
|
| 49 |
+
• Integration of Android IP webcam app allows easy setup of tablets as cameras feeding into Home Assistant
|
| 50 |
+
• Integration with Fully Kiosk browser enables controlling and monitoring tablet activity within Home Assistant
|
| 51 |
+
• User experience of ease of use and integrations is highlighted, including an "aha moment" with the Elgato key light integration
|
| 52 |
+
• Other notable mentions include Shelly devices integrating seamlessly with Home Assistant.
|
| 53 |
+
• Running power usage benchmarks with a kilowatt meter and logging results
|
| 54 |
+
• Using Home Assistant for monitoring and reviewing historical data
|
| 55 |
+
• Exporting data to InfluxDB for time-series analysis and graphing
|
| 56 |
+
• Tips for using Influx, including SSD storage and split DNS functionality
|
| 57 |
+
• Installing the Tail Scale integration in Home Assistant OS
|
| 58 |
+
• Remote access to Home Assistant instances via Nebukasa Cloud and Tail Scale
|
| 59 |
+
• Differences between official and community tail scale versions
|
| 60 |
+
• Importance of home assistant OS-based system for tail scale network integration
|
| 61 |
+
• Humio, a centralized log management and observability platform
|
| 62 |
+
• Humio Community Edition, a no-cost data ingestion offering with up to 16 gigs per day retention
|
| 63 |
+
• Personal experience with iOS 16 beta on iPad
|
| 64 |
+
• Discussion of satellite calling and its potential uses
|
| 65 |
+
• Mention of the Pixel 3's "Always On Display" feature
|
| 66 |
+
• Joking about ordering a pizza in Death Valley via DoorDash
|
| 67 |
+
• Upcoming meetups for Jupiter Broadcasting, including a tour of JPL
|
| 68 |
+
• Plans to have swag bags and other items at meetups
|
| 69 |
+
• Discussion of using Matrix for chat rooms and organizing meetups
|
| 70 |
+
• Inquiry about self-hosted meetup apps
|
| 71 |
+
• Adding new devices to a network is made easy with certain brands
|
| 72 |
+
• Recommendations for reliable devices, including Aquara and KiwiSet
|
| 73 |
+
• Discussion on MQTT and Zigbee connectivity
|
| 74 |
+
• Comparison of iPhone versus Android operating systems
|
| 75 |
+
• Personal experiences with OnePlus 7T and preference for Android features
|
| 76 |
+
• Observations on the usability and quirks of both iPhone and Android
|
| 77 |
+
• Control Center on iOS is not considered intuitive
|
| 78 |
+
• Personal preference plays a role in UI choices
|
| 79 |
+
• iPhone camera performance in low-light conditions is superior
|
| 80 |
+
• Switching between iOS and Android platforms is easy
|
| 81 |
+
• iOS is generally more stable than Android
|
| 82 |
+
• Apps on iOS are often native, polished, and performant
|
| 83 |
+
• Apple's privacy policies are considered better than those of other companies
|
| 84 |
+
• Jellyfin has several client options for streaming content, including Jellyamp and the Jellyfin audio player
|
| 85 |
+
• Discussion of switching from Plex to Jellyfin for audio books
|
| 86 |
+
• Search for alternative audiobook solutions in the Jellyfin ecosystem
|
| 87 |
+
• Introduction to and recommendation of Podverse as a podcast player
|
| 88 |
+
• Mention of other free software options such as Fountain, Albie, and Breeze
|
| 89 |
+
• Discussion of Boosts and sending sats to creators
|
| 90 |
+
• Independent podcasting and support for independent creators
|
| 91 |
+
• Criticism of dynamic ads in podcasting
|
| 92 |
+
• Promotion of subscribing to the JB Network
|
| 93 |
+
• Upcoming Jupiter.Tube broadcast on a Wednesday
|
| 94 |
+
• Update on new website jupiterbroadcasting.com, including:
|
| 95 |
+
• Dynamic live embedding on the live page
|
| 96 |
+
• Built in Hugo and self-hosted on Linode
|
| 97 |
+
• GitHub repository for contribution
|
| 98 |
+
• Meetups at meetup.com/jupiterbroadcasting
|
| 99 |
+
• Contact information:
|
| 100 |
+
• self-hosted.show/contact
|
| 101 |
• Twitter handles: Ironic Badger, Chris LAS
|
80: Solving Whole Home Audio _summary.txt
CHANGED
|
@@ -1,86 +1,86 @@
|
|
| 1 |
-
• Frustration with CalDigit TS4 Thunderbolt dock
|
| 2 |
-
• Firmware update issues for Mac users
|
| 3 |
-
• Use of Windows to update firmware due to lack of Mac-based utility
|
| 4 |
-
• Difficulty updating firmware from a Thunderbolt 3 device to a Thunderbolt 4 device
|
| 5 |
-
• Experience with multiple docks and comparison between CalDigit and OWC
|
| 6 |
-
• Discussion of Thunderbolt 4 and its benefits vs. USB
|
| 7 |
-
• Discussion of USB hubs and switches for Thunderbolt 2 implementation
|
| 8 |
-
• Comparing Firewire and Thunderbolt technology
|
| 9 |
-
• Continuing the trend of de-Googleing devices, including Google Photos and Google Maps
|
| 10 |
-
• Using decentralized storage solutions like Storage-A with Duplicati for backups
|
| 11 |
-
• Trying out Graphene OS on a Pixel 3 phone
|
| 12 |
-
• Discussing alternative mapping apps like Apple Maps
|
| 13 |
-
• Focusing on whole-home audio solution using Google Home Minis and Chromecast audios
|
| 14 |
-
• Struggling to integrate amplifiers into Home Assistant for smart home control
|
| 15 |
-
• Plex Amp endpoint
|
| 16 |
-
• Using Raspberry Pi for media streaming
|
| 17 |
-
• Logitech Media Server (LMS) and its history
|
| 18 |
-
• Snapcast and other alternatives to LMS
|
| 19 |
-
• PyCore Player as a solution for running LMS on Raspberry Pi
|
| 20 |
-
• Issues with PyCore Player's interface
|
| 21 |
-
• Frustration with Pi Core Player interface
|
| 22 |
-
• Desire for easy spousal approval setup
|
| 23 |
-
• Comparison of Pi Core Player with RPi Audio Receiver
|
| 24 |
-
• Difficulty setting up Pi Core Player on a Raspberry Pi 4
|
| 25 |
-
• Success with RPi Audio Receiver on an older Raspberry Pi 2
|
| 26 |
-
• Discussion of ease of use and configuration of RPi Audio Receiver
|
| 27 |
-
• The speaker had issues with controlling dumb amplifiers using infrared blasters, specifically with the Broadlink RM4 Mini.
|
| 28 |
-
• The issue was caused by a bug in the Broadlink integration where it would not send the correct command to change the inputs on the amplifier.
|
| 29 |
-
• The speaker also discussed the reliability of the solution, stating that when it works, it works, but when it doesn't, it doesn't, and estimated the success rate at around 80%.
|
| 30 |
-
• The speaker considered replacing the amplifiers with new ones that have RS-232 ports, but did not want to spend the money.
|
| 31 |
-
• A listener suggested using HomePods as a solution, which the speaker jokingly accepted as a "filthy iOS ecosystem user".
|
| 32 |
-
• The speaker ended by promoting Linode's cloud computing services and offering $100 in credit for new customers.
|
| 33 |
-
• Linode's flexibility and pricing make it a unique cloud provider
|
| 34 |
-
• Features include custom VPN Linux, S3-compatible object storage, VLAN support, and powerful DNS manager
|
| 35 |
-
• Alex has been experiencing hard drive issues with his server case and is trying to solve the problem by installing hot swap hard drive cages
|
| 36 |
-
• Matter protocol update discussed, with Chris being optimistic about its potential
|
| 37 |
-
• Matter standard has the potential to succeed due to its open-source nature
|
| 38 |
-
• Multiple controllers and manufacturers can run the same code
|
| 39 |
-
• Paulus from Home Assistant is excited about the prospect of Matter's success
|
| 40 |
-
• Concerns that Matter may not be a success, with comparisons to previous standards that failed
|
| 41 |
-
• Discussion of the current state of home automation, where no single vendor dominates the market
|
| 42 |
-
• Mention of cheap Chinese clones and their impact on the industry
|
| 43 |
-
• Paulus' excitement about the release of version 1.0 of Matter on GitHub
|
| 44 |
-
• Joking speculation about when Matter will hit the market
|
| 45 |
-
• Upcoming plans to work on a Zigbee device project
|
| 46 |
-
• The speaker discusses the effectiveness of toggle wheels as a UI for simple actions like adjusting brightness and audio.
|
| 47 |
-
• There was a mock-up of an iPhone with a click wheel that was considered before the final design.
|
| 48 |
-
• The original iPhone project had two parallel tracks: one based on macOS and another using the iPod OS, which ultimately won out.
|
| 49 |
-
• Old iPod Classics can be upgraded to use SD cards, significantly increasing their battery life to months instead of hours.
|
| 50 |
-
• The speaker wants multiple screens for Home Assistant control throughout their home.
|
| 51 |
-
• They successfully figured out how to use a tablet with icons for voice commands but notes it was somewhat intuitive due to experience with similar systems.
|
| 52 |
-
• Discussing potential uses for older Android devices as home assistant screens
|
| 53 |
-
• Mentioning specific models and prices (e.g. iPad mini, $75)
|
| 54 |
-
• Exploring the possibility of using kiosk browser and camera functionality on tablets
|
| 55 |
-
• Describing Humio.com as a centralized log management platform
|
| 56 |
-
• Highlighting features of Humio, including index-free architecture and reduced hardware footprint
|
| 57 |
-
• Introducing Humio Community Edition as a no-cost data ingestion offering
|
| 58 |
-
• Discussing potential uses for Humio in home environments, including logging and monitoring
|
| 59 |
-
• Announcing upcoming meetups in Sacramento, Southern California, and Portland
|
| 60 |
-
• Discussion on meetup.com limitations and alternatives
|
| 61 |
-
• Recommendation to check out Z-Wave light switches, specifically the ones Dr. Pepper Shaker mentioned
|
| 62 |
-
• Comparison of smart switches with built-in smarts vs. devices like Shelly
|
| 63 |
-
• Concerns about complexity and added value when leaving smart home devices for future homeowners
|
| 64 |
-
• Switching to Zigbee and finding benefits in Z-Wave devices
|
| 65 |
-
• Note on Z-Wave switches requiring a neutral wire in older houses
|
| 66 |
-
• Discussion of self-hosted email vs business connection for internet service
|
| 67 |
-
• Bandwidth issues and potential solutions with static IP, customer service, and no bandwidth caps
|
| 68 |
-
• Comparison of self-hosted email with using a real email provider (Fastmail)
|
| 69 |
-
• Mention of Bitwarden's new alias support for Fastmail
|
| 70 |
-
• Praise for Fastmail from audience members and the host
|
| 71 |
-
• Donations to the show (5,000 sats each from Ahanaga and Frozer)
|
| 72 |
-
• Plug for Podverse, a cross-platform podcast player that syncs between devices
|
| 73 |
-
• Integrating the Podverse player on the website resolved issues and created a positive collaboration between communities.
|
| 74 |
-
• Contributors to Podverse include listeners from Jupyter Broadcasting, fostering cross-community connections.
|
| 75 |
-
• Listener gifts and shoutouts were acknowledged, including Prozac's row of ducks, young dookie's full home assistant setup, and Shim's sat experiments.
|
| 76 |
-
• The host discussed boosts and their nostalgic value, reminiscent of IRC culture.
|
| 77 |
-
• He promoted new podcast apps and invited listeners to try Podverse.
|
| 78 |
-
• The host mentioned his old Dual Xeon motherboard for sale and its potential uses in a home lab or VM setup.
|
| 79 |
-
• Discussion of membership benefits and ad-free feed
|
| 80 |
-
• Brent Gervais' appearance on the show
|
| 81 |
-
• Announcement of a new computer and upcoming episode about it
|
| 82 |
-
• Frankenstein-ing an old computer (X250) with upgrades
|
| 83 |
-
• Benchmarks comparison between computers, including the new Thalio model
|
| 84 |
-
• System76's products and a mention of Cheese Bacon attending All Things Open
|
| 85 |
-
• Upcoming meetup details to be posted on the Element Room meetup page
|
| 86 |
• Call for feedback and contact information
|
|
|
|
| 1 |
+
• Frustration with CalDigit TS4 Thunderbolt dock
|
| 2 |
+
• Firmware update issues for Mac users
|
| 3 |
+
• Use of Windows to update firmware due to lack of Mac-based utility
|
| 4 |
+
• Difficulty updating firmware from a Thunderbolt 3 device to a Thunderbolt 4 device
|
| 5 |
+
• Experience with multiple docks and comparison between CalDigit and OWC
|
| 6 |
+
• Discussion of Thunderbolt 4 and its benefits vs. USB
|
| 7 |
+
• Discussion of USB hubs and switches for Thunderbolt 2 implementation
|
| 8 |
+
• Comparing Firewire and Thunderbolt technology
|
| 9 |
+
• Continuing the trend of de-Googleing devices, including Google Photos and Google Maps
|
| 10 |
+
• Using decentralized storage solutions like Storage-A with Duplicati for backups
|
| 11 |
+
• Trying out Graphene OS on a Pixel 3 phone
|
| 12 |
+
• Discussing alternative mapping apps like Apple Maps
|
| 13 |
+
• Focusing on whole-home audio solution using Google Home Minis and Chromecast audios
|
| 14 |
+
• Struggling to integrate amplifiers into Home Assistant for smart home control
|
| 15 |
+
• Plex Amp endpoint
|
| 16 |
+
• Using Raspberry Pi for media streaming
|
| 17 |
+
• Logitech Media Server (LMS) and its history
|
| 18 |
+
• Snapcast and other alternatives to LMS
|
| 19 |
+
• PyCore Player as a solution for running LMS on Raspberry Pi
|
| 20 |
+
• Issues with PyCore Player's interface
|
| 21 |
+
• Frustration with Pi Core Player interface
|
| 22 |
+
• Desire for easy spousal approval setup
|
| 23 |
+
• Comparison of Pi Core Player with RPi Audio Receiver
|
| 24 |
+
• Difficulty setting up Pi Core Player on a Raspberry Pi 4
|
| 25 |
+
• Success with RPi Audio Receiver on an older Raspberry Pi 2
|
| 26 |
+
• Discussion of ease of use and configuration of RPi Audio Receiver
|
| 27 |
+
• The speaker had issues with controlling dumb amplifiers using infrared blasters, specifically with the Broadlink RM4 Mini.
|
| 28 |
+
• The issue was caused by a bug in the Broadlink integration where it would not send the correct command to change the inputs on the amplifier.
|
| 29 |
+
• The speaker also discussed the reliability of the solution, stating that when it works, it works, but when it doesn't, it doesn't, and estimated the success rate at around 80%.
|
| 30 |
+
• The speaker considered replacing the amplifiers with new ones that have RS-232 ports, but did not want to spend the money.
|
| 31 |
+
• A listener suggested using HomePods as a solution, which the speaker jokingly accepted as a "filthy iOS ecosystem user".
|
| 32 |
+
• The speaker ended by promoting Linode's cloud computing services and offering $100 in credit for new customers.
|
| 33 |
+
• Linode's flexibility and pricing make it a unique cloud provider
|
| 34 |
+
• Features include custom VPN Linux, S3-compatible object storage, VLAN support, and powerful DNS manager
|
| 35 |
+
• Alex has been experiencing hard drive issues with his server case and is trying to solve the problem by installing hot swap hard drive cages
|
| 36 |
+
• Matter protocol update discussed, with Chris being optimistic about its potential
|
| 37 |
+
• Matter standard has the potential to succeed due to its open-source nature
|
| 38 |
+
• Multiple controllers and manufacturers can run the same code
|
| 39 |
+
• Paulus from Home Assistant is excited about the prospect of Matter's success
|
| 40 |
+
• Concerns that Matter may not be a success, with comparisons to previous standards that failed
|
| 41 |
+
• Discussion of the current state of home automation, where no single vendor dominates the market
|
| 42 |
+
• Mention of cheap Chinese clones and their impact on the industry
|
| 43 |
+
• Paulus' excitement about the release of version 1.0 of Matter on GitHub
|
| 44 |
+
• Joking speculation about when Matter will hit the market
|
| 45 |
+
• Upcoming plans to work on a Zigbee device project
|
| 46 |
+
• The speaker discusses the effectiveness of toggle wheels as a UI for simple actions like adjusting brightness and audio.
|
| 47 |
+
• There was a mock-up of an iPhone with a click wheel that was considered before the final design.
|
| 48 |
+
• The original iPhone project had two parallel tracks: one based on macOS and another using the iPod OS, which ultimately won out.
|
| 49 |
+
• Old iPod Classics can be upgraded to use SD cards, significantly increasing their battery life to months instead of hours.
|
| 50 |
+
• The speaker wants multiple screens for Home Assistant control throughout their home.
|
| 51 |
+
• They successfully figured out how to use a tablet with icons for voice commands but notes it was somewhat intuitive due to experience with similar systems.
|
| 52 |
+
• Discussing potential uses for older Android devices as home assistant screens
|
| 53 |
+
• Mentioning specific models and prices (e.g. iPad mini, $75)
|
| 54 |
+
• Exploring the possibility of using kiosk browser and camera functionality on tablets
|
| 55 |
+
• Describing Humio.com as a centralized log management platform
|
| 56 |
+
• Highlighting features of Humio, including index-free architecture and reduced hardware footprint
|
| 57 |
+
• Introducing Humio Community Edition as a no-cost data ingestion offering
|
| 58 |
+
• Discussing potential uses for Humio in home environments, including logging and monitoring
|
| 59 |
+
• Announcing upcoming meetups in Sacramento, Southern California, and Portland
|
| 60 |
+
• Discussion on meetup.com limitations and alternatives
|
| 61 |
+
• Recommendation to check out Z-Wave light switches, specifically the ones Dr. Pepper Shaker mentioned
|
| 62 |
+
• Comparison of smart switches with built-in smarts vs. devices like Shelly
|
| 63 |
+
• Concerns about complexity and added value when leaving smart home devices for future homeowners
|
| 64 |
+
• Switching to Zigbee and finding benefits in Z-Wave devices
|
| 65 |
+
• Note on Z-Wave switches requiring a neutral wire in older houses
|
| 66 |
+
• Discussion of self-hosted email vs business connection for internet service
|
| 67 |
+
• Bandwidth issues and potential solutions with static IP, customer service, and no bandwidth caps
|
| 68 |
+
• Comparison of self-hosted email with using a real email provider (Fastmail)
|
| 69 |
+
• Mention of Bitwarden's new alias support for Fastmail
|
| 70 |
+
• Praise for Fastmail from audience members and the host
|
| 71 |
+
• Donations to the show (5,000 sats each from Ahanaga and Frozer)
|
| 72 |
+
• Plug for Podverse, a cross-platform podcast player that syncs between devices
|
| 73 |
+
• Integrating the Podverse player on the website resolved issues and created a positive collaboration between communities.
|
| 74 |
+
• Contributors to Podverse include listeners from Jupyter Broadcasting, fostering cross-community connections.
|
| 75 |
+
• Listener gifts and shoutouts were acknowledged, including Prozac's row of ducks, young dookie's full home assistant setup, and Shim's sat experiments.
|
| 76 |
+
• The host discussed boosts and their nostalgic value, reminiscent of IRC culture.
|
| 77 |
+
• He promoted new podcast apps and invited listeners to try Podverse.
|
| 78 |
+
• The host mentioned his old Dual Xeon motherboard for sale and its potential uses in a home lab or VM setup.
|
| 79 |
+
• Discussion of membership benefits and ad-free feed
|
| 80 |
+
• Brent Gervais' appearance on the show
|
| 81 |
+
• Announcement of a new computer and upcoming episode about it
|
| 82 |
+
• Frankenstein-ing an old computer (X250) with upgrades
|
| 83 |
+
• Benchmarks comparison between computers, including the new Thalio model
|
| 84 |
+
• System76's products and a mention of Cheese Bacon attending All Things Open
|
| 85 |
+
• Upcoming meetup details to be posted on the Element Room meetup page
|
| 86 |
• Call for feedback and contact information
|
81: The Badger Stack _summary.txt
CHANGED
|
@@ -1,125 +1,125 @@
|
|
| 1 |
-
• The narrator experiences a hardware failure with their Raspberry Pi home server, which runs multiple instances including Home Assistant.
|
| 2 |
-
• The narrator is unsure why the Raspberry Pi died and whether it was due to an unattended upgrade or other factors such as a live patch.
|
| 3 |
-
• The failed device controls many automations in the RV, causing inconvenience for the users.
|
| 4 |
-
• The narrator considers using a dedicated hardware device for Home Assistant instead of the Raspberry Pi.
|
| 5 |
-
• Discussion about the Home Assistant Yellow device and its expected delivery date
|
| 6 |
-
• Power and heat considerations for the device
|
| 7 |
-
• Comparison to a potential x86 system with BMC chip
|
| 8 |
-
• Issues with Raspberry Pi availability due to industrial demand
|
| 9 |
-
• Concerns about Home Assistant shipping devices after long delays and possible lack of future stock
|
| 10 |
-
• Suggested alternative payment methods, similar to Valve's queue system
|
| 11 |
-
• The Raspberry Pi Foundation's product has become incredibly popular and ubiquitous
|
| 12 |
-
• Broadcom is reportedly unhappy with the foundation due to their plans to commercialize the product
|
| 13 |
-
• This may lead to slower supply from Broadcom and changed licensing rates for the company
|
| 14 |
-
• The M1 platform from Apple could be a worthy successor for home labbers, especially if it gains decent Linux support
|
| 15 |
-
• Current limitations in macOS Server and Docker Desktop on Mac are mentioned as issues to be addressed
|
| 16 |
-
• Discussion around choosing an M1 chip or other options for a computer system
|
| 17 |
-
• Concerns about power consumption and space limitations in the RV environment
|
| 18 |
-
• Consideration of building a custom x86 box with hosting capabilities
|
| 19 |
-
• Decentralization and portability as desirable features
|
| 20 |
-
• Mention of Intel NUC and tiny mini micro computers as alternatives
|
| 21 |
-
• Discussion of video decoding requirements, including QuickSync support and transcoding options
|
| 22 |
-
• Use of pre-encoding tools like TDAR or Handbrake to bypass transcoding requirements
|
| 23 |
-
• Storage needs, with a preference for 4 terabytes in the Joops environment
|
| 24 |
-
• Discussing current TV show season on a streaming device
|
| 25 |
-
• Researching affordable SSD options for data storage
|
| 26 |
-
• Exploring the idea of using low-cost Leven SSDs in a RAID configuration
|
| 27 |
-
• Describing a modular approach to building and maintaining a media server setup
|
| 28 |
-
• Brainstorming ideas for a custom-built studio setup with mixing board, storage, and production capacity
|
| 29 |
-
• Matter's stability is uncertain
|
| 30 |
-
• Home Assistant is going all-in on Zigbee
|
| 31 |
-
• They've hired a Z-Wave integration specialist, causing mixed messages about their direction
|
| 32 |
-
• It seems they'll support multiple protocols, but it's unclear how well each will be supported
|
| 33 |
-
• The user is considering whether to invest in Zigbee or Z-Wave devices
|
| 34 |
-
• Linode services mentioned as reliable and cost-effective compared to hyperscalers
|
| 35 |
-
• Multiple data centers available globally, with more coming soon
|
| 36 |
-
• Performance and support balance makes Linode a recommended choice
|
| 37 |
-
• $100 offer for users to try Linode
|
| 38 |
-
• Invoice Ninja app discussed for creating customisable invoices and quotes
|
| 39 |
-
• Using Invoice Ninja software for freelance work
|
| 40 |
-
• Creating customers and products in the software
|
| 41 |
-
• Generating invoices based on customer and product information
|
| 42 |
-
• Sending invoices via email through the software (optional)
|
| 43 |
-
• Self-hosting options for the software
|
| 44 |
-
• User's experience with the software over two years
|
| 45 |
-
• The speaker is using a self-hosted invoicing system on their server.
|
| 46 |
-
• The system requires three containers: app, database (using MySQL), and front-end (using Nginx).
|
| 47 |
-
• The speaker likes the user interface and features of the system, including a chart that displays pending invoices.
|
| 48 |
-
• The system is useful for those who send many invoices daily, but still provides benefits to users with lower invoice volumes.
|
| 49 |
-
• The speaker appreciates the ability to tweak settings and customize the system's functionality.
|
| 50 |
-
• The pricing of hosted invoicing services can be expensive, with some options costing around $50-60 per month.
|
| 51 |
-
• The self-hosted system offers cost savings compared to traditional invoicing solutions like QuickBooks.
|
| 52 |
-
• Invoicing capabilities, including quotes and proposals
|
| 53 |
-
• Ability to track different vendors and manage transactions
|
| 54 |
-
• Reporting features for tracking invoices and financial data
|
| 55 |
-
• Comparison with other invoicing software, such as Invoice Plane
|
| 56 |
-
• User's experience switching from a Google sheet to Invoice Ninja
|
| 57 |
-
• Difficulty in extracting data from software
|
| 58 |
-
• Importing and exporting database options
|
| 59 |
-
• CSV export as a viable solution for invoicing
|
| 60 |
-
• Catherine's experience with the software
|
| 61 |
-
• Import options, including CSV, JSON, XLS, and others
|
| 62 |
-
• What are YubiKeys
|
| 63 |
-
• How they work for 2-factor authentication
|
| 64 |
-
• Benefits of using a YubiKey (e.g., security, no need to store secrets online)
|
| 65 |
-
• Disadvantages of using a YubiKey (e.g., physical access required, inconvenient placement in the house)
|
| 66 |
-
|
| 67 |
-
• YubiKey promotion by Cloudflare for affordable pricing
|
| 68 |
-
• Discussion of the benefits and usefulness of YubiKeys in workplaces
|
| 69 |
-
• Cloudflare's offer to provide security keys at discounted prices
|
| 70 |
-
• Personal anecdotes about using YubiKeys and their accessibility on various devices
|
| 71 |
-
• Discussion of trying out a $10 entry price for NFC devices
|
| 72 |
-
• Comparison of different features and methods of authentication (FIDO)
|
| 73 |
-
• Complexity and difficulty of choosing the right authenticator
|
| 74 |
-
• Recent advancements in simplifying authentication processes
|
| 75 |
-
• Debate about the best approach: hardware device vs. software app
|
| 76 |
-
• Potential benefits of combining two-factor code with a hardware device
|
| 77 |
-
• The speaker has shared a password on GitHub and acknowledges it was not the best decision.
|
| 78 |
-
• The conversation shifts to discussing useful strings of text that are generated by various services, but are limited in their utility due to being tied to specific time periods or services.
|
| 79 |
-
• The speaker expresses interest in learning more about an automatic archiver for Reddit called Expanse, which creates a self-hosted web app that allows users to store and organize their Reddit activity.
|
| 80 |
-
• Expanse has the ability to bypass Reddit's 1000 item listing limit, and the speaker is impressed by its functionality after watching a short YouTube video demonstration.
|
| 81 |
-
• Discussion of a hypothetical feature where everything read on Reddit automatically goes to Pocket
|
| 82 |
-
• Comparison with other services and desire for similar functionality
|
| 83 |
-
• Introduction to RSS and Bitwarden features, including email aliasing with FastMail integration
|
| 84 |
-
• Explanation of how the FastMail integration allows users to create genuine email aliases instead of semi-obfuscated addresses
|
| 85 |
-
• Discussion of password management and unique email addresses for each service
|
| 86 |
-
• Thoughts on bridging the gap between advanced security practices and everyday user behavior
|
| 87 |
-
• Discussion of whether NetBird is a suitable alternative to TailScale
|
| 88 |
-
• Analysis of NetBird's features and how they compare to TailScale
|
| 89 |
-
• Mention of the proliferation of VPN solutions based on WireGuard
|
| 90 |
-
• Prediction that there will be multiple options for users, with some possibly being more popular than others
|
| 91 |
-
• Tail Scale and subnet routing
|
| 92 |
-
• Using Tail Scale with non-PC devices (e.g. Victron solar equipment)
|
| 93 |
-
• Setting up subnet routing at different locations (e.g. Airbnb, home)
|
| 94 |
-
• Pulse Audio Network Streaming as an alternative for whole-home audio
|
| 95 |
-
• Comparison of Netbird and Tail Scale
|
| 96 |
-
• Plan to discuss subnet routing in a future episode
|
| 97 |
-
• Discussion of audio streaming solutions, including PulseAudio and Volumio
|
| 98 |
-
• Recommendation of Rune Audio as a paid solution for multiple-room music streaming
|
| 99 |
-
• Troubles with IR blaster reliability and potential alternatives using ESP devices
|
| 100 |
-
• Intersection of hardware and software in home entertainment systems
|
| 101 |
-
• Request for tips on content request systems for music
|
| 102 |
-
• Discussion of reliable smart switches, specifically the Z-Wave 700 series
|
| 103 |
-
• Discussion of a favorite radio frequency (900 megahertz)
|
| 104 |
-
• Smart home setup and recommendations for Zigbee router
|
| 105 |
-
• Comparison of two Zigbee gateways, Con Be 2 and Zalish Zigbee 3.0 stick
|
| 106 |
-
• Coupon code offered by Cloudfree.shop
|
| 107 |
-
• Alex's Proxmox and Docker setup on a server
|
| 108 |
-
• Documentation for setting up similar server configuration available at perfectmediaserver.com
|
| 109 |
-
• Discussion of a Proxmox setup, including how it's used and its simplicity
|
| 110 |
-
• Overview of setting up Proxmox on Debian, with options for direct installation or installing Debian first
|
| 111 |
-
• Mention of John's decision to set up his own email server after listening to the last episode
|
| 112 |
-
• Comments from listeners who have also set up their own email servers, including one using Comcast
|
| 113 |
-
• Discussion of new podcast apps, specifically Podverse and Calyx, and a mention of Graphene
|
| 114 |
-
• Alternatives to popular podcast apps
|
| 115 |
-
• Alby as an option for web-based podcast listening
|
| 116 |
-
• Office Hours' recent episode and their trip to JPL
|
| 117 |
-
• The Europa Clipper mission and live cam stream on YouTube
|
| 118 |
-
• Linux Unplugged's audience and meetup experience
|
| 119 |
-
• A guest from JPL bringing a prototype computer from the Mars copter
|
| 120 |
-
• Gratitude expressed to Tim, JB, and Linode for support
|
| 121 |
-
• Discussion of swag distribution at JPL meetups
|
| 122 |
-
• Thanks to members who make the show possible
|
| 123 |
-
• Promotion of self-hosted.show's site reliability engineers and ad-free version
|
| 124 |
-
• Announcement of final meetup and future meetups
|
| 125 |
• Mention of attending All Things Open in Raleigh
|
|
|
|
| 1 |
+
• The narrator experiences a hardware failure with their Raspberry Pi home server, which runs multiple instances including Home Assistant.
|
| 2 |
+
• The narrator is unsure why the Raspberry Pi died and whether it was due to an unattended upgrade or other factors such as a live patch.
|
| 3 |
+
• The failed device controls many automations in the RV, causing inconvenience for the users.
|
| 4 |
+
• The narrator considers using a dedicated hardware device for Home Assistant instead of the Raspberry Pi.
|
| 5 |
+
• Discussion about the Home Assistant Yellow device and its expected delivery date
|
| 6 |
+
• Power and heat considerations for the device
|
| 7 |
+
• Comparison to a potential x86 system with BMC chip
|
| 8 |
+
• Issues with Raspberry Pi availability due to industrial demand
|
| 9 |
+
• Concerns about Home Assistant shipping devices after long delays and possible lack of future stock
|
| 10 |
+
• Suggested alternative payment methods, similar to Valve's queue system
|
| 11 |
+
• The Raspberry Pi Foundation's product has become incredibly popular and ubiquitous
|
| 12 |
+
• Broadcom is reportedly unhappy with the foundation due to their plans to commercialize the product
|
| 13 |
+
• This may lead to slower supply from Broadcom and changed licensing rates for the company
|
| 14 |
+
• The M1 platform from Apple could be a worthy successor for home labbers, especially if it gains decent Linux support
|
| 15 |
+
• Current limitations in macOS Server and Docker Desktop on Mac are mentioned as issues to be addressed
|
| 16 |
+
• Discussion around choosing an M1 chip or other options for a computer system
|
| 17 |
+
• Concerns about power consumption and space limitations in the RV environment
|
| 18 |
+
• Consideration of building a custom x86 box with hosting capabilities
|
| 19 |
+
• Decentralization and portability as desirable features
|
| 20 |
+
• Mention of Intel NUC and tiny mini micro computers as alternatives
|
| 21 |
+
• Discussion of video decoding requirements, including QuickSync support and transcoding options
|
| 22 |
+
• Use of pre-encoding tools like TDAR or Handbrake to bypass transcoding requirements
|
| 23 |
+
• Storage needs, with a preference for 4 terabytes in the Joops environment
|
| 24 |
+
• Discussing current TV show season on a streaming device
|
| 25 |
+
• Researching affordable SSD options for data storage
|
| 26 |
+
• Exploring the idea of using low-cost Leven SSDs in a RAID configuration
|
| 27 |
+
• Describing a modular approach to building and maintaining a media server setup
|
| 28 |
+
• Brainstorming ideas for a custom-built studio setup with mixing board, storage, and production capacity
|
| 29 |
+
• Matter's stability is uncertain
|
| 30 |
+
• Home Assistant is going all-in on Zigbee
|
| 31 |
+
• They've hired a Z-Wave integration specialist, causing mixed messages about their direction
|
| 32 |
+
• It seems they'll support multiple protocols, but it's unclear how well each will be supported
|
| 33 |
+
• The user is considering whether to invest in Zigbee or Z-Wave devices
|
| 34 |
+
• Linode services mentioned as reliable and cost-effective compared to hyperscalers
|
| 35 |
+
• Multiple data centers available globally, with more coming soon
|
| 36 |
+
• Performance and support balance makes Linode a recommended choice
|
| 37 |
+
• $100 offer for users to try Linode
|
| 38 |
+
• Invoice Ninja app discussed for creating customisable invoices and quotes
|
| 39 |
+
• Using Invoice Ninja software for freelance work
|
| 40 |
+
• Creating customers and products in the software
|
| 41 |
+
• Generating invoices based on customer and product information
|
| 42 |
+
• Sending invoices via email through the software (optional)
|
| 43 |
+
• Self-hosting options for the software
|
| 44 |
+
• User's experience with the software over two years
|
| 45 |
+
• The speaker is using a self-hosted invoicing system on their server.
|
| 46 |
+
• The system requires three containers: app, database (using MySQL), and front-end (using Nginx).
|
| 47 |
+
• The speaker likes the user interface and features of the system, including a chart that displays pending invoices.
|
| 48 |
+
• The system is useful for those who send many invoices daily, but still provides benefits to users with lower invoice volumes.
|
| 49 |
+
• The speaker appreciates the ability to tweak settings and customize the system's functionality.
|
| 50 |
+
• The pricing of hosted invoicing services can be expensive, with some options costing around $50-60 per month.
|
| 51 |
+
• The self-hosted system offers cost savings compared to traditional invoicing solutions like QuickBooks.
|
| 52 |
+
• Invoicing capabilities, including quotes and proposals
|
| 53 |
+
• Ability to track different vendors and manage transactions
|
| 54 |
+
• Reporting features for tracking invoices and financial data
|
| 55 |
+
• Comparison with other invoicing software, such as Invoice Plane
|
| 56 |
+
• User's experience switching from a Google sheet to Invoice Ninja
|
| 57 |
+
• Difficulty in extracting data from software
|
| 58 |
+
• Importing and exporting database options
|
| 59 |
+
• CSV export as a viable solution for invoicing
|
| 60 |
+
• Catherine's experience with the software
|
| 61 |
+
• Import options, including CSV, JSON, XLS, and others
|
| 62 |
+
• What are YubiKeys
|
| 63 |
+
• How they work for 2-factor authentication
|
| 64 |
+
• Benefits of using a YubiKey (e.g., security, no need to store secrets online)
|
| 65 |
+
• Disadvantages of using a YubiKey (e.g., physical access required, inconvenient placement in the house)
|
| 66 |
+
• Two-factor authentication and security keys
|
| 67 |
+
• YubiKey promotion by Cloudflare for affordable pricing
|
| 68 |
+
• Discussion of the benefits and usefulness of YubiKeys in workplaces
|
| 69 |
+
• Cloudflare's offer to provide security keys at discounted prices
|
| 70 |
+
• Personal anecdotes about using YubiKeys and their accessibility on various devices
|
| 71 |
+
• Discussion of trying out a $10 entry price for NFC devices
|
| 72 |
+
• Comparison of different features and methods of authentication (FIDO)
|
| 73 |
+
• Complexity and difficulty of choosing the right authenticator
|
| 74 |
+
• Recent advancements in simplifying authentication processes
|
| 75 |
+
• Debate about the best approach: hardware device vs. software app
|
| 76 |
+
• Potential benefits of combining two-factor code with a hardware device
|
| 77 |
+
• The speaker has shared a password on GitHub and acknowledges it was not the best decision.
|
| 78 |
+
• The conversation shifts to discussing useful strings of text that are generated by various services, but are limited in their utility due to being tied to specific time periods or services.
|
| 79 |
+
• The speaker expresses interest in learning more about an automatic archiver for Reddit called Expanse, which creates a self-hosted web app that allows users to store and organize their Reddit activity.
|
| 80 |
+
• Expanse has the ability to bypass Reddit's 1000 item listing limit, and the speaker is impressed by its functionality after watching a short YouTube video demonstration.
|
| 81 |
+
• Discussion of a hypothetical feature where everything read on Reddit automatically goes to Pocket
|
| 82 |
+
• Comparison with other services and desire for similar functionality
|
| 83 |
+
• Introduction to RSS and Bitwarden features, including email aliasing with FastMail integration
|
| 84 |
+
• Explanation of how the FastMail integration allows users to create genuine email aliases instead of semi-obfuscated addresses
|
| 85 |
+
• Discussion of password management and unique email addresses for each service
|
| 86 |
+
• Thoughts on bridging the gap between advanced security practices and everyday user behavior
|
| 87 |
+
• Discussion of whether NetBird is a suitable alternative to TailScale
|
| 88 |
+
• Analysis of NetBird's features and how they compare to TailScale
|
| 89 |
+
• Mention of the proliferation of VPN solutions based on WireGuard
|
| 90 |
+
• Prediction that there will be multiple options for users, with some possibly being more popular than others
|
| 91 |
+
• Tail Scale and subnet routing
|
| 92 |
+
• Using Tail Scale with non-PC devices (e.g. Victron solar equipment)
|
| 93 |
+
• Setting up subnet routing at different locations (e.g. Airbnb, home)
|
| 94 |
+
• Pulse Audio Network Streaming as an alternative for whole-home audio
|
| 95 |
+
• Comparison of Netbird and Tail Scale
|
| 96 |
+
• Plan to discuss subnet routing in a future episode
|
| 97 |
+
• Discussion of audio streaming solutions, including PulseAudio and Volumio
|
| 98 |
+
• Recommendation of Rune Audio as a paid solution for multiple-room music streaming
|
| 99 |
+
• Troubles with IR blaster reliability and potential alternatives using ESP devices
|
| 100 |
+
• Intersection of hardware and software in home entertainment systems
|
| 101 |
+
• Request for tips on content request systems for music
|
| 102 |
+
• Discussion of reliable smart switches, specifically the Z-Wave 700 series
|
| 103 |
+
• Discussion of a favorite radio frequency (900 megahertz)
|
| 104 |
+
• Smart home setup and recommendations for Zigbee router
|
| 105 |
+
• Comparison of two Zigbee gateways, Con Be 2 and Zalish Zigbee 3.0 stick
|
| 106 |
+
• Coupon code offered by Cloudfree.shop
|
| 107 |
+
• Alex's Proxmox and Docker setup on a server
|
| 108 |
+
• Documentation for setting up similar server configuration available at perfectmediaserver.com
|
| 109 |
+
• Discussion of a Proxmox setup, including how it's used and its simplicity
|
| 110 |
+
• Overview of setting up Proxmox on Debian, with options for direct installation or installing Debian first
|
| 111 |
+
• Mention of John's decision to set up his own email server after listening to the last episode
|
| 112 |
+
• Comments from listeners who have also set up their own email servers, including one using Comcast
|
| 113 |
+
• Discussion of new podcast apps, specifically Podverse and Calyx, and a mention of Graphene
|
| 114 |
+
• Alternatives to popular podcast apps
|
| 115 |
+
• Alby as an option for web-based podcast listening
|
| 116 |
+
• Office Hours' recent episode and their trip to JPL
|
| 117 |
+
• The Europa Clipper mission and live cam stream on YouTube
|
| 118 |
+
• Linux Unplugged's audience and meetup experience
|
| 119 |
+
• A guest from JPL bringing a prototype computer from the Mars copter
|
| 120 |
+
• Gratitude expressed to Tim, JB, and Linode for support
|
| 121 |
+
• Discussion of swag distribution at JPL meetups
|
| 122 |
+
• Thanks to members who make the show possible
|
| 123 |
+
• Promotion of self-hosted.show's site reliability engineers and ad-free version
|
| 124 |
+
• Announcement of final meetup and future meetups
|
| 125 |
• Mention of attending All Things Open in Raleigh
|
82: Roon Ready Ruh-Roh _summary.txt
CHANGED
|
@@ -1,106 +1,106 @@
|
|
| 1 |
-
• The speaker tuned their Volkswagen Golf R to increase its horsepower from 280 to 370 with a software update
|
| 2 |
-
• They discussed tuning options, including Cobb Access ports and Equilibrium Tuning services
|
| 3 |
-
• The speaker mentioned that they also have a similar setup on their RV and saw an improvement in performance
|
| 4 |
-
• They talked about the possibility of flashing their GTI's ECU for a potential horsepower increase
|
| 5 |
-
• The speaker reminisced about upgrading their RV's ECU and mentioned recent issues with Wi-Fi and internet connectivity at home
|
| 6 |
-
• Discussion of alternative hardware for a home automation system
|
| 7 |
-
• Intel Atom system from a Tesla solar wall mentioned as an option
|
| 8 |
-
• Arrival and review of Home Assistant Yellow device
|
| 9 |
-
• Comparison with other devices and plans for dedicated machine and application server setup
|
| 10 |
-
• Introduction to Odroid H3 Plus device with various features and ports
|
| 11 |
-
• Discussion of RAM requirements for the new device
|
| 12 |
-
• The speaker is excited about receiving a new hardware shipment that they were looking forward to.
|
| 13 |
-
• They plan to load desktop Linux and then wipe the device and build a Nix OS server.
|
| 14 |
-
• The device has a passive heatsink, allowing it to run silently.
|
| 15 |
-
• The speaker mentions their preference for Intel NICs over Realtek 2.5 gig NICs due to hardware compatibility reasons.
|
| 16 |
-
• They discuss running Proxmox and virtualizing services like Home Assistant on the new device.
|
| 17 |
-
• Plex and containerization (LXC vs Docker) are mentioned as topics to be discussed later in the show.
|
| 18 |
-
• The speaker shares news about Apple shipping iOS 16.1, Matter devices, and updates to their ecosystem.
|
| 19 |
-
• They speculate on how this may impact accessibility of Apple's remote control features in Home Assistant.
|
| 20 |
-
• New sensors and devices
|
| 21 |
-
• Comparison of Rev1 devices to newer models (e.g., Odroid H3)
|
| 22 |
-
• Energy monitoring and power consumption testing (e.g., pie vs. Odroid H3)
|
| 23 |
-
• Discussion of Linode.com and its features (e.g., $100 credit, app marketplace, NextCloud deployment)
|
| 24 |
-
• Home audio exploration and trying out different systems (e.g., Volumio, Rune)
|
| 25 |
-
• Discussion of Rune as an audiophile music player
|
| 26 |
-
• Running software on NAS, computer, or server to catalog and organize audio files
|
| 27 |
-
• Performance and indexing of large collections (250,000+ files)
|
| 28 |
-
• Cost and pricing model ($10/month for access to own files)
|
| 29 |
-
• Integration with Tidal and CoBuzz for high-res gap filling and automatic track prioritization
|
| 30 |
-
• Unique metadata presentation features, including magazine-style album views and linked credits
|
| 31 |
-
• Multi-room audio capabilities, including synchronization across devices
|
| 32 |
-
• The speaker discusses the capabilities of a music streaming service called RAT Ready, which allows for simultaneous audio playback across multiple devices and operating systems.
|
| 33 |
-
• The speaker notes that while RAT Ready can stream to various devices, there are limitations to grouping devices from different ecosystems (e.g. RAT Ready, Chromecast, AirPlay).
|
| 34 |
-
• The speaker expresses disappointment that the Nucleus Plus server, a $2,600 device sold by Rune, cannot group all compatible devices together.
|
| 35 |
-
• The speaker questions the technical specifications of the Nucleus Plus and other Rune products, as there is limited information provided about their internal components.
|
| 36 |
-
• The speaker discusses the high cost of Rune's products and services, including a lifetime pass option for $1,500 or more, and notes that even if purchased at launch in 2015, it would take 7 years to break even on the monthly subscription.
|
| 37 |
-
• Host's favorable opinion on Plex
|
| 38 |
-
• New release from Rune (version 2) and its features, including the equivalent app called Rune Arc for remote music access
|
| 39 |
-
• Criticism of Rune's new model, which requires internet connection to play back files
|
| 40 |
-
• Allegation that Rune is "eating their own face" by charging users $10/month and restricting offline playback
|
| 41 |
-
• Discussion with Johnny Darko, a trusted audiophile source, who also criticizes Rune's move
|
| 42 |
-
• Analysis of the motivations behind Rune's shift towards cloud-based processing
|
| 43 |
-
• Concerns about self-hosting capabilities and potential issues with internet connectivity
|
| 44 |
-
• Starlink customers may be using alternative solutions for multi-room audio
|
| 45 |
-
• Review of Rune, a software-based solution for multi-room audio
|
| 46 |
-
• Criticism of Rune's limitations and potential obsolescence compared to hardware-based solutions like Sonos
|
| 47 |
-
• Alternative solutions mentioned: Volumio, Plexamp Headless, and dedicated hardware devices like Raspberry Pi
|
| 48 |
-
• Discussion of the importance of having a reliable solution with a decent grace period before phoning home for updates
|
| 49 |
-
• Upcoming product releases: Cloudfree lightswitches and potential future plans to integrate Zigbee
|
| 50 |
-
• Discussion of using Docker vs LXC for containerization
|
| 51 |
-
• Alex's preference for using Docker and Docker Compose
|
| 52 |
-
• Benefits of Docker, including ease of use and separation of application and data
|
| 53 |
-
• Drawbacks of LXC, including added complexity and potential anti-patterns in design
|
| 54 |
-
• Issues with passing hardware through to containers with LXC
|
| 55 |
-
• Comparison of using QuickSync in a Docker container vs an LXC
|
| 56 |
-
• Comparison between VMs and LXCs
|
| 57 |
-
• Advantages of modern virtualization software for VM performance
|
| 58 |
-
• Discussion on the popularity of LXCs in Ubuntu ecosystem
|
| 59 |
-
• Mention of Podman as an alternative to Docker, with current limitations
|
| 60 |
-
• Observations on system architecture and design of Podman compared to Docker
|
| 61 |
-
• Discussion on Reddit about preparing for a time when you're tired of tinkering with Home Assistant
|
| 62 |
-
• Importance of being honest with yourself and acknowledging that automation can lose its appeal over time
|
| 63 |
-
• Tips for preparing infrastructure for when interest wanes, including breaking down tasks into small steps and completing them before moving on to new projects
|
| 64 |
-
• The difficulty of loading context into a system
|
| 65 |
-
• Breaking down tasks into atomic blocks for efficient completion
|
| 66 |
-
• The importance of motivation and self-motivation in completing tasks
|
| 67 |
-
• Using device binding to allow devices to control each other without a central coordinator
|
| 68 |
-
• Writing down important information to avoid forgetting it
|
| 69 |
-
• Difficulty with physical installation of smart devices due to wall thickness
|
| 70 |
-
• Need for a solution like binding to keep Home Assistant working even when server is down
|
| 71 |
-
• Discussion of serverless IoT and self-hosting
|
| 72 |
-
• Mention of Philips Hue integration with binding
|
| 73 |
-
• Importance of owning firmware and hardware, not relying on cloud-based services
|
| 74 |
-
• Chatroom discussion about boosts and show popularity
|
| 75 |
-
• Smart bulb issue with light switch
|
| 76 |
-
• RTFM (Read The Fine Manual) discussion
|
| 77 |
-
• Funk Whale project and its features
|
| 78 |
-
• Comparison of Funk Whale with Jellyfin
|
| 79 |
-
• Discussion on music service solutions for personal library exposure
|
| 80 |
-
• Boost address on Jupiter Broadcasting is in the RSS feed
|
| 81 |
-
• Requires new podcast app or browser extension (Alby) for access
|
| 82 |
-
• Saturn platform allows users to have their own node and split sats
|
| 83 |
-
• Jupiter Broadcasting plans to generate its own RSS feeds independently
|
| 84 |
-
• Future features include transcripts, host information, and richer context
|
| 85 |
-
• Discussing alternative podcast enclosures (e.g., MP4, Opus files)
|
| 86 |
-
• Benefits of using Podcasting 2.0, which allows multiple formats in one RSS feed entry
|
| 87 |
-
• Decentralization and self-hosting as key to keeping podcasting healthy
|
| 88 |
-
• Consolidation trends in the podcasting industry, including Spotify's control over hosting and ad insertion
|
| 89 |
-
• Introduction to R-Clone features, specifically Docker plugin for mounting local/cloud storage as a Docker volume
|
| 90 |
-
• Potential uses of this feature (e.g., host isolation, separation)
|
| 91 |
-
• Tips for use case scenarios or cool projects to run on an Ubuntu home server
|
| 92 |
-
• Recommended apps from perfectmediaserver.com for a media server
|
| 93 |
-
• Other user recommendations, with links to contact the show and share ideas
|
| 94 |
-
• Discussion of Smokeping, a legacy app that can be run in a container
|
| 95 |
-
• Mention of Mood, a multi-room audio system that runs on a Pi
|
| 96 |
-
• Fatigue with music situation and potential return to Spotify
|
| 97 |
-
• Mention of shipping HomePods and thanking John A for sats donation
|
| 98 |
-
• Discussion of new podcast app Podverse, GPL and open-source
|
| 99 |
-
• Schmitzfeld's first boost and O-Droid H3 Plus device test results
|
| 100 |
-
• Ideas for mounting old Powerwall or Solarwall device
|
| 101 |
-
• Future project ideas and SRE subscriber appreciation
|
| 102 |
-
• Discussion of self-hosted.show contact page and social media handles
|
| 103 |
-
• Upcoming event "All Things Open" in Raleigh, NC around Halloween
|
| 104 |
-
• Possible meetup at the event and mention of a System76 booth
|
| 105 |
-
• Invitation to connect on Discord and Matrix chat rooms
|
| 106 |
• Final thanks and appreciation for listeners
|
|
|
|
| 1 |
+
• The speaker tuned their Volkswagen Golf R to increase its horsepower from 280 to 370 with a software update
|
| 2 |
+
• They discussed tuning options, including Cobb Access ports and Equilibrium Tuning services
|
| 3 |
+
• The speaker mentioned that they also have a similar setup on their RV and saw an improvement in performance
|
| 4 |
+
• They talked about the possibility of flashing their GTI's ECU for a potential horsepower increase
|
| 5 |
+
• The speaker reminisced about upgrading their RV's ECU and mentioned recent issues with Wi-Fi and internet connectivity at home
|
| 6 |
+
• Discussion of alternative hardware for a home automation system
|
| 7 |
+
• Intel Atom system from a Tesla solar wall mentioned as an option
|
| 8 |
+
• Arrival and review of Home Assistant Yellow device
|
| 9 |
+
• Comparison with other devices and plans for dedicated machine and application server setup
|
| 10 |
+
• Introduction to Odroid H3 Plus device with various features and ports
|
| 11 |
+
• Discussion of RAM requirements for the new device
|
| 12 |
+
• The speaker is excited about receiving a new hardware shipment that they were looking forward to.
|
| 13 |
+
• They plan to load desktop Linux and then wipe the device and build a Nix OS server.
|
| 14 |
+
• The device has a passive heatsink, allowing it to run silently.
|
| 15 |
+
• The speaker mentions their preference for Intel NICs over Realtek 2.5 gig NICs due to hardware compatibility reasons.
|
| 16 |
+
• They discuss running Proxmox and virtualizing services like Home Assistant on the new device.
|
| 17 |
+
• Plex and containerization (LXC vs Docker) are mentioned as topics to be discussed later in the show.
|
| 18 |
+
• The speaker shares news about Apple shipping iOS 16.1, Matter devices, and updates to their ecosystem.
|
| 19 |
+
• They speculate on how this may impact accessibility of Apple's remote control features in Home Assistant.
|
| 20 |
+
• New sensors and devices
|
| 21 |
+
• Comparison of Rev1 devices to newer models (e.g., Odroid H3)
|
| 22 |
+
• Energy monitoring and power consumption testing (e.g., pie vs. Odroid H3)
|
| 23 |
+
• Discussion of Linode.com and its features (e.g., $100 credit, app marketplace, NextCloud deployment)
|
| 24 |
+
• Home audio exploration and trying out different systems (e.g., Volumio, Rune)
|
| 25 |
+
• Discussion of Rune as an audiophile music player
|
| 26 |
+
• Running software on NAS, computer, or server to catalog and organize audio files
|
| 27 |
+
• Performance and indexing of large collections (250,000+ files)
|
| 28 |
+
• Cost and pricing model ($10/month for access to own files)
|
| 29 |
+
• Integration with Tidal and CoBuzz for high-res gap filling and automatic track prioritization
|
| 30 |
+
• Unique metadata presentation features, including magazine-style album views and linked credits
|
| 31 |
+
• Multi-room audio capabilities, including synchronization across devices
|
| 32 |
+
• The speaker discusses the capabilities of a music streaming service called RAT Ready, which allows for simultaneous audio playback across multiple devices and operating systems.
|
| 33 |
+
• The speaker notes that while RAT Ready can stream to various devices, there are limitations to grouping devices from different ecosystems (e.g. RAT Ready, Chromecast, AirPlay).
|
| 34 |
+
• The speaker expresses disappointment that the Nucleus Plus server, a $2,600 device sold by Rune, cannot group all compatible devices together.
|
| 35 |
+
• The speaker questions the technical specifications of the Nucleus Plus and other Rune products, as there is limited information provided about their internal components.
|
| 36 |
+
• The speaker discusses the high cost of Rune's products and services, including a lifetime pass option for $1,500 or more, and notes that even if purchased at launch in 2015, it would take 7 years to break even on the monthly subscription.
|
| 37 |
+
• Host's favorable opinion on Plex
|
| 38 |
+
• New release from Rune (version 2) and its features, including the equivalent app called Rune Arc for remote music access
|
| 39 |
+
• Criticism of Rune's new model, which requires internet connection to play back files
|
| 40 |
+
• Allegation that Rune is "eating their own face" by charging users $10/month and restricting offline playback
|
| 41 |
+
• Discussion with Johnny Darko, a trusted audiophile source, who also criticizes Rune's move
|
| 42 |
+
• Analysis of the motivations behind Rune's shift towards cloud-based processing
|
| 43 |
+
• Concerns about self-hosting capabilities and potential issues with internet connectivity
|
| 44 |
+
• Starlink customers may be using alternative solutions for multi-room audio
|
| 45 |
+
• Review of Rune, a software-based solution for multi-room audio
|
| 46 |
+
• Criticism of Rune's limitations and potential obsolescence compared to hardware-based solutions like Sonos
|
| 47 |
+
• Alternative solutions mentioned: Volumio, Plexamp Headless, and dedicated hardware devices like Raspberry Pi
|
| 48 |
+
• Discussion of the importance of having a reliable solution with a decent grace period before phoning home for updates
|
| 49 |
+
• Upcoming product releases: Cloudfree lightswitches and potential future plans to integrate Zigbee
|
| 50 |
+
• Discussion of using Docker vs LXC for containerization
|
| 51 |
+
• Alex's preference for using Docker and Docker Compose
|
| 52 |
+
• Benefits of Docker, including ease of use and separation of application and data
|
| 53 |
+
• Drawbacks of LXC, including added complexity and potential anti-patterns in design
|
| 54 |
+
• Issues with passing hardware through to containers with LXC
|
| 55 |
+
• Comparison of using QuickSync in a Docker container vs an LXC
|
| 56 |
+
• Comparison between VMs and LXCs
|
| 57 |
+
• Advantages of modern virtualization software for VM performance
|
| 58 |
+
• Discussion on the popularity of LXCs in Ubuntu ecosystem
|
| 59 |
+
• Mention of Podman as an alternative to Docker, with current limitations
|
| 60 |
+
• Observations on system architecture and design of Podman compared to Docker
|
| 61 |
+
• Discussion on Reddit about preparing for a time when you're tired of tinkering with Home Assistant
|
| 62 |
+
• Importance of being honest with yourself and acknowledging that automation can lose its appeal over time
|
| 63 |
+
• Tips for preparing infrastructure for when interest wanes, including breaking down tasks into small steps and completing them before moving on to new projects
|
| 64 |
+
• The difficulty of loading context into a system
|
| 65 |
+
• Breaking down tasks into atomic blocks for efficient completion
|
| 66 |
+
• The importance of motivation and self-motivation in completing tasks
|
| 67 |
+
• Using device binding to allow devices to control each other without a central coordinator
|
| 68 |
+
• Writing down important information to avoid forgetting it
|
| 69 |
+
• Difficulty with physical installation of smart devices due to wall thickness
|
| 70 |
+
• Need for a solution like binding to keep Home Assistant working even when server is down
|
| 71 |
+
• Discussion of serverless IoT and self-hosting
|
| 72 |
+
• Mention of Philips Hue integration with binding
|
| 73 |
+
• Importance of owning firmware and hardware, not relying on cloud-based services
|
| 74 |
+
• Chatroom discussion about boosts and show popularity
|
| 75 |
+
• Smart bulb issue with light switch
|
| 76 |
+
• RTFM (Read The Fine Manual) discussion
|
| 77 |
+
• Funk Whale project and its features
|
| 78 |
+
• Comparison of Funk Whale with Jellyfin
|
| 79 |
+
• Discussion on music service solutions for personal library exposure
|
| 80 |
+
• Boost address on Jupiter Broadcasting is in the RSS feed
|
| 81 |
+
• Requires new podcast app or browser extension (Alby) for access
|
| 82 |
+
• Saturn platform allows users to have their own node and split sats
|
| 83 |
+
• Jupiter Broadcasting plans to generate its own RSS feeds independently
|
| 84 |
+
• Future features include transcripts, host information, and richer context
|
| 85 |
+
• Discussing alternative podcast enclosures (e.g., MP4, Opus files)
|
| 86 |
+
• Benefits of using Podcasting 2.0, which allows multiple formats in one RSS feed entry
|
| 87 |
+
• Decentralization and self-hosting as key to keeping podcasting healthy
|
| 88 |
+
• Consolidation trends in the podcasting industry, including Spotify's control over hosting and ad insertion
|
| 89 |
+
• Introduction to R-Clone features, specifically Docker plugin for mounting local/cloud storage as a Docker volume
|
| 90 |
+
• Potential uses of this feature (e.g., host isolation, separation)
|
| 91 |
+
• Tips for use case scenarios or cool projects to run on an Ubuntu home server
|
| 92 |
+
• Recommended apps from perfectmediaserver.com for a media server
|
| 93 |
+
• Other user recommendations, with links to contact the show and share ideas
|
| 94 |
+
• Discussion of Smokeping, a legacy app that can be run in a container
|
| 95 |
+
• Mention of Mood, a multi-room audio system that runs on a Pi
|
| 96 |
+
• Fatigue with music situation and potential return to Spotify
|
| 97 |
+
• Mention of shipping HomePods and thanking John A for sats donation
|
| 98 |
+
• Discussion of new podcast app Podverse, GPL and open-source
|
| 99 |
+
• Schmitzfeld's first boost and O-Droid H3 Plus device test results
|
| 100 |
+
• Ideas for mounting old Powerwall or Solarwall device
|
| 101 |
+
• Future project ideas and SRE subscriber appreciation
|
| 102 |
+
• Discussion of self-hosted.show contact page and social media handles
|
| 103 |
+
• Upcoming event "All Things Open" in Raleigh, NC around Halloween
|
| 104 |
+
• Possible meetup at the event and mention of a System76 booth
|
| 105 |
+
• Invitation to connect on Discord and Matrix chat rooms
|
| 106 |
• Final thanks and appreciation for listeners
|
83: Unintended Upgrades _summary.txt
CHANGED
|
@@ -1,111 +1,111 @@
|
|
| 1 |
-
• The host has been experimenting with new home server setups
|
| 2 |
-
• They're looking for a Discord bot to help with title suggestions for their show
|
| 3 |
-
• The bot would allow viewers to suggest titles by typing "bang!" followed by a suggestion, and then publishing the top-voted options on a web page
|
| 4 |
-
• The host has attended an open source conference and shares his thoughts on its quality, noting that it's semi-commercial and had both good and bad sessions
|
| 5 |
-
• Jim Salter was scheduled to speak about ZFS but cancelled due to illness.
|
| 6 |
-
• Microsoft's shift in focus towards Linux and open-source development tools
|
| 7 |
-
• Scott Hanselman's presentation on WSL2 and its integration with GitHub and VS Code
|
| 8 |
-
• Criticism of Windows' limitations and "corporate tax" strategy
|
| 9 |
-
• Comparison of WSL2 to running a native Linux system
|
| 10 |
-
• Acknowledgment that there are situations where Linux does not cut it, but WSL provides an alternative for developers who must use Windows
|
| 11 |
-
• Development containers as a solution to encapsulated development environments
|
| 12 |
-
• Scott's talk on development containers, which provide a JSON manifest for project requirements
|
| 13 |
-
• Microsoft's creation of the Windows Terminal and its recognition as an open-source project
|
| 14 |
-
• The presenter's own experience with Docker containers during their master's degree program
|
| 15 |
-
• The presenter's friend Michael Dominick's journey from Mac to Windows, including using WSL and VS Code
|
| 16 |
-
• A meetup at All Things Open conference, where attendees met up in the lobby using a Matrix chat
|
| 17 |
-
• Burnout and stress management
|
| 18 |
-
• All Things Open conference sessions and content
|
| 19 |
-
• Red Hat Tower and meeting with listeners
|
| 20 |
-
• Boar's Head sauce and its commercial availability
|
| 21 |
-
• LearnNixTV and Jay's talk on RetroPie and retro gaming
|
| 22 |
-
• CM4 module and its uses in home lab setup
|
| 23 |
-
• Discussion about the fun projects that open-source developers want to work on
|
| 24 |
-
• Event at All Things Open, including meeting cool people and networking
|
| 25 |
-
• Introducing Sync Thing as a great tool for ambient file system sync
|
| 26 |
-
• Using Sync Thing to keep progress in sync between devices
|
| 27 |
-
• Advertising Linode.com as a sponsor of Jupyter Broadcasting and offering $100 off new accounts
|
| 28 |
-
• Discussing the importance of trying out a product before committing to it
|
| 29 |
-
• Introducing Linode.com and encouraging users to sign up with the SSH option
|
| 30 |
-
• Announcing the arrival of Home Assistant Yellow, a year after crowdfunding
|
| 31 |
-
• Experiencing issues with the device's storage and performance, including:
|
| 32 |
-
+ Not using the MVME disk as expected
|
| 33 |
-
+ Moving data from EMMC to MVME through a migration process
|
| 34 |
-
+ Initial stress due to lack of understanding of the process
|
| 35 |
-
• Outlining the benefits of resetting and starting fresh on Home Assistant devices
|
| 36 |
-
• The speaker had a difficult time setting up Home Assistant in the past
|
| 37 |
-
• They were able to recover their configuration from an old backup and made adjustments manually
|
| 38 |
-
• Z-Wave migration was easier than expected, with devices still paired to the new controller
|
| 39 |
-
• The speaker suggests that Home Assistant could benefit from an onboarding wizard or assistant for new device setup
|
| 40 |
-
• The interface has become much more user-friendly over time, making it easier to set up and manage devices
|
| 41 |
-
• They have a significantly reduced number of automations compared to previous setup, relying more on scheduling cards instead
|
| 42 |
-
• The user discusses their positive experience with Home Assistant Yellow using NVMe storage, noting significant improvements in speed and performance.
|
| 43 |
-
• They mention that the generic thermostat and scheduler card features have greatly simplified automations and saved time.
|
| 44 |
-
• The user describes the benefits of using a leaner system, including smaller backup sizes (now 70-80 megabytes vs. 1.2 gigabytes).
|
| 45 |
-
• A problem with their Shelley device is described, where it was rebooting and resetting itself every 30-60 seconds when under load.
|
| 46 |
-
• The user replaced the stock firmware on their Shelly device with an open firmware using a tool called MG2X for over-the-air firmware upload.
|
| 47 |
-
• Discussion of the Shelly smart plug's update process and its integration with custom firmware
|
| 48 |
-
• Concerns about a Shelly smart plug going offline in the speaker's new setup
|
| 49 |
-
• Investigation into possible causes, including temperature limits set by Mongoose OS
|
| 50 |
-
• Comparison of different smart home ecosystems (HomeKit vs. Zigbee) and devices (ESP Home vs. TAS motor)
|
| 51 |
-
• Review of a Zenglid Zigbee Smart LED light strip for use with Home Assistant
|
| 52 |
-
• The speaker is trying out a new setup with Nix OS and Jellyfin media server
|
| 53 |
-
• They set up Infuse on Apple TV for streaming
|
| 54 |
-
• The speaker had an issue with the Jellyfin app not working due to incompatible server version
|
| 55 |
-
• The issue was caused by Jellyfin being out of date on NixOS, but it's close to getting updated
|
| 56 |
-
• The speaker notes that Nix is a rolling distribution and depends on maintainers
|
| 57 |
-
• Discussing the need for intro detection plugins in Jellyfin
|
| 58 |
-
• Comparing Plex and Jellyfin media setups
|
| 59 |
-
• Mention of issues with TV breaking at inconvenient moments
|
| 60 |
-
• Adoption of Plex and NVIDIA Shield as default media setup due to reliability
|
| 61 |
-
• Real-time updates on Hia's face in Discord chat
|
| 62 |
-
• The speaker is having trouble with Netflix on their NVIDIA Shield TV due to an auto-update of the Jellyfin app.
|
| 63 |
-
• They mention the irony that if they were using Apple TV and Infuse, the issue wouldn't exist.
|
| 64 |
-
• The speaker expresses optimism about Jellyfin's future improvements and believes it will be "good enough" within a year or two.
|
| 65 |
-
• They plan to use Jellyfin at home and keep Plex running on their studio server for archived media.
|
| 66 |
-
• A plugin is mentioned that allows for skipping intros in Jellyfin, with some limitations.
|
| 67 |
-
• Comparison of Jellyfin and Plex media libraries
|
| 68 |
-
• Discussion of Jellyfin's progress and potential as an alternative to commercial projects like Plex
|
| 69 |
-
• Mention of Rune and its limitations in offline playback
|
| 70 |
-
• Reference to XBMC and the potential for Jellyfin to be a modern version of that project
|
| 71 |
-
• Promotion of jupiter.party and membership benefits
|
| 72 |
-
• Comparison of home assistants for privacy and functionality
|
| 73 |
-
• Integration of Mycroft with Home Assistant and potential issues with Google speech-to-text
|
| 74 |
-
• Concerns about relying on cloud-based services for voice transcription
|
| 75 |
-
• Alternative text-to-speech service through Nebukasa Cloud offering improved sound quality
|
| 76 |
-
• Use of Nebukasa's service for nighttime scripts in Home Assistant setup
|
| 77 |
-
• Discussion of bedtime mode and its limitations
|
| 78 |
-
• Desire for a local solution to tie into speakers and control devices
|
| 79 |
-
• Introduction to Mycroft integration and request for user feedback
|
| 80 |
-
• Boost from Gene Bean and his question about backing up Nextcloud
|
| 81 |
-
• Explanation of the speaker's backup strategy using ZFS, replication, and other tools
|
| 82 |
-
• The cost of backing up large amounts of data (25 terabytes) and the limitations of current backup options
|
| 83 |
-
• AWS Glacier as a potential backup solution, but expensive for large data sets
|
| 84 |
-
• Alternative option: building a server to store data at a friend's house or on-site
|
| 85 |
-
• Use of Jupyter.tube for live streaming and recording podcasts
|
| 86 |
-
• Fountain app for value-for-value podcast boosting, with mixed reviews from users
|
| 87 |
-
• The Rune Lifetime used to cost $499, but is now $699.
|
| 88 |
-
• The CEO threatened to pull the product due to unsustainable costs.
|
| 89 |
-
• A listener bought the lifetime subscription because they prefer a one-time payment over monthly fees.
|
| 90 |
-
• Feature voting on the Rune forum showed that users want the offline grace period for servers re-enabled.
|
| 91 |
-
• This may be a defining moment for the company, and how they respond will impact future decisions.
|
| 92 |
-
• The Zimra board was mentioned as an alternative to Raspberry Pi, but the speaker is skeptical about buying one.
|
| 93 |
-
• Device is designed for installation in a vehicle due to its ruggedized features
|
| 94 |
-
• Concerns about company viability and potential Kickstarter pitfalls
|
| 95 |
-
• Discussion of device's performance, storage, and compatibility with peripherals
|
| 96 |
-
• Comparison to Odroid solution and concerns about form factor and design intent
|
| 97 |
-
• Potential uses and customizations of the device despite reservations
|
| 98 |
-
• Great submissions and boosts from community members, including MG, J-Cube, Nev, Acorn, and Thumbs
|
| 99 |
-
• Discussion of terminal emulators and apps, with user recommending Hollywood as a favorite app
|
| 100 |
-
• User memories of listening to the podcast in specific places and how it brought back memories
|
| 101 |
-
• Conversation about careers and life-changing moments sparked by listening to the podcast
|
| 102 |
-
• Discussion of an old interview where Docker wasn't yet called Docker
|
| 103 |
-
• Mentions of boosts and messages sent by "Ninja Mort" with no context or explanation
|
| 104 |
-
• Promotion of the podcast's membership program and self-hosted platform
|
| 105 |
-
• Mention of a Matrix instance for Jupyter broadcasting
|
| 106 |
-
• Acknowledgement of Alex for updating the infrastructure due to OpenSSL patches
|
| 107 |
-
• Setting up unattended upgrades on Ubuntu boxes
|
| 108 |
-
• Alex recommends using Ubuntu systems with auto-updates
|
| 109 |
-
• Discussing the effectiveness of automated security patches
|
| 110 |
-
• Mentioning feedback and contact information for the podcast
|
| 111 |
• Off-topic discussion about Elon Musk's projects and a notable financial transaction
|
|
|
|
| 1 |
+
• The host has been experimenting with new home server setups
|
| 2 |
+
• They're looking for a Discord bot to help with title suggestions for their show
|
| 3 |
+
• The bot would allow viewers to suggest titles by typing "bang!" followed by a suggestion, and then publishing the top-voted options on a web page
|
| 4 |
+
• The host has attended an open source conference and shares his thoughts on its quality, noting that it's semi-commercial and had both good and bad sessions
|
| 5 |
+
• Jim Salter was scheduled to speak about ZFS but cancelled due to illness.
|
| 6 |
+
• Microsoft's shift in focus towards Linux and open-source development tools
|
| 7 |
+
• Scott Hanselman's presentation on WSL2 and its integration with GitHub and VS Code
|
| 8 |
+
• Criticism of Windows' limitations and "corporate tax" strategy
|
| 9 |
+
• Comparison of WSL2 to running a native Linux system
|
| 10 |
+
• Acknowledgment that there are situations where Linux does not cut it, but WSL provides an alternative for developers who must use Windows
|
| 11 |
+
• Development containers as a solution to encapsulated development environments
|
| 12 |
+
• Scott's talk on development containers, which provide a JSON manifest for project requirements
|
| 13 |
+
• Microsoft's creation of the Windows Terminal and its recognition as an open-source project
|
| 14 |
+
• The presenter's own experience with Docker containers during their master's degree program
|
| 15 |
+
• The presenter's friend Michael Dominick's journey from Mac to Windows, including using WSL and VS Code
|
| 16 |
+
• A meetup at All Things Open conference, where attendees met up in the lobby using a Matrix chat
|
| 17 |
+
• Burnout and stress management
|
| 18 |
+
• All Things Open conference sessions and content
|
| 19 |
+
• Red Hat Tower and meeting with listeners
|
| 20 |
+
• Boar's Head sauce and its commercial availability
|
| 21 |
+
• LearnNixTV and Jay's talk on RetroPie and retro gaming
|
| 22 |
+
• CM4 module and its uses in home lab setup
|
| 23 |
+
• Discussion about the fun projects that open-source developers want to work on
|
| 24 |
+
• Event at All Things Open, including meeting cool people and networking
|
| 25 |
+
• Introducing Sync Thing as a great tool for ambient file system sync
|
| 26 |
+
• Using Sync Thing to keep progress in sync between devices
|
| 27 |
+
• Advertising Linode.com as a sponsor of Jupyter Broadcasting and offering $100 off new accounts
|
| 28 |
+
• Discussing the importance of trying out a product before committing to it
|
| 29 |
+
• Introducing Linode.com and encouraging users to sign up with the SSH option
|
| 30 |
+
• Announcing the arrival of Home Assistant Yellow, a year after crowdfunding
|
| 31 |
+
• Experiencing issues with the device's storage and performance, including:
|
| 32 |
+
+ Not using the MVME disk as expected
|
| 33 |
+
+ Moving data from EMMC to MVME through a migration process
|
| 34 |
+
+ Initial stress due to lack of understanding of the process
|
| 35 |
+
• Outlining the benefits of resetting and starting fresh on Home Assistant devices
|
| 36 |
+
• The speaker had a difficult time setting up Home Assistant in the past
|
| 37 |
+
• They were able to recover their configuration from an old backup and made adjustments manually
|
| 38 |
+
• Z-Wave migration was easier than expected, with devices still paired to the new controller
|
| 39 |
+
• The speaker suggests that Home Assistant could benefit from an onboarding wizard or assistant for new device setup
|
| 40 |
+
• The interface has become much more user-friendly over time, making it easier to set up and manage devices
|
| 41 |
+
• They have a significantly reduced number of automations compared to previous setup, relying more on scheduling cards instead
|
| 42 |
+
• The user discusses their positive experience with Home Assistant Yellow using NVMe storage, noting significant improvements in speed and performance.
|
| 43 |
+
• They mention that the generic thermostat and scheduler card features have greatly simplified automations and saved time.
|
| 44 |
+
• The user describes the benefits of using a leaner system, including smaller backup sizes (now 70-80 megabytes vs. 1.2 gigabytes).
|
| 45 |
+
• A problem with their Shelley device is described, where it was rebooting and resetting itself every 30-60 seconds when under load.
|
| 46 |
+
• The user replaced the stock firmware on their Shelly device with an open firmware using a tool called MG2X for over-the-air firmware upload.
|
| 47 |
+
• Discussion of the Shelly smart plug's update process and its integration with custom firmware
|
| 48 |
+
• Concerns about a Shelly smart plug going offline in the speaker's new setup
|
| 49 |
+
• Investigation into possible causes, including temperature limits set by Mongoose OS
|
| 50 |
+
• Comparison of different smart home ecosystems (HomeKit vs. Zigbee) and devices (ESP Home vs. TAS motor)
|
| 51 |
+
• Review of a Zenglid Zigbee Smart LED light strip for use with Home Assistant
|
| 52 |
+
• The speaker is trying out a new setup with Nix OS and Jellyfin media server
|
| 53 |
+
• They set up Infuse on Apple TV for streaming
|
| 54 |
+
• The speaker had an issue with the Jellyfin app not working due to incompatible server version
|
| 55 |
+
• The issue was caused by Jellyfin being out of date on NixOS, but it's close to getting updated
|
| 56 |
+
• The speaker notes that Nix is a rolling distribution and depends on maintainers
|
| 57 |
+
• Discussing the need for intro detection plugins in Jellyfin
|
| 58 |
+
• Comparing Plex and Jellyfin media setups
|
| 59 |
+
• Mention of issues with TV breaking at inconvenient moments
|
| 60 |
+
• Adoption of Plex and NVIDIA Shield as default media setup due to reliability
|
| 61 |
+
• Real-time updates on Hia's face in Discord chat
|
| 62 |
+
• The speaker is having trouble with Netflix on their NVIDIA Shield TV due to an auto-update of the Jellyfin app.
|
| 63 |
+
• They mention the irony that if they were using Apple TV and Infuse, the issue wouldn't exist.
|
| 64 |
+
• The speaker expresses optimism about Jellyfin's future improvements and believes it will be "good enough" within a year or two.
|
| 65 |
+
• They plan to use Jellyfin at home and keep Plex running on their studio server for archived media.
|
| 66 |
+
• A plugin is mentioned that allows for skipping intros in Jellyfin, with some limitations.
|
| 67 |
+
• Comparison of Jellyfin and Plex media libraries
|
| 68 |
+
• Discussion of Jellyfin's progress and potential as an alternative to commercial projects like Plex
|
| 69 |
+
• Mention of Rune and its limitations in offline playback
|
| 70 |
+
• Reference to XBMC and the potential for Jellyfin to be a modern version of that project
|
| 71 |
+
• Promotion of jupiter.party and membership benefits
|
| 72 |
+
• Comparison of home assistants for privacy and functionality
|
| 73 |
+
• Integration of Mycroft with Home Assistant and potential issues with Google speech-to-text
|
| 74 |
+
• Concerns about relying on cloud-based services for voice transcription
|
| 75 |
+
• Alternative text-to-speech service through Nebukasa Cloud offering improved sound quality
|
| 76 |
+
• Use of Nebukasa's service for nighttime scripts in Home Assistant setup
|
| 77 |
+
• Discussion of bedtime mode and its limitations
|
| 78 |
+
• Desire for a local solution to tie into speakers and control devices
|
| 79 |
+
• Introduction to Mycroft integration and request for user feedback
|
| 80 |
+
• Boost from Gene Bean and his question about backing up Nextcloud
|
| 81 |
+
• Explanation of the speaker's backup strategy using ZFS, replication, and other tools
|
| 82 |
+
• The cost of backing up large amounts of data (25 terabytes) and the limitations of current backup options
|
| 83 |
+
• AWS Glacier as a potential backup solution, but expensive for large data sets
|
| 84 |
+
• Alternative option: building a server to store data at a friend's house or on-site
|
| 85 |
+
• Use of Jupyter.tube for live streaming and recording podcasts
|
| 86 |
+
• Fountain app for value-for-value podcast boosting, with mixed reviews from users
|
| 87 |
+
• The Rune Lifetime used to cost $499, but is now $699.
|
| 88 |
+
• The CEO threatened to pull the product due to unsustainable costs.
|
| 89 |
+
• A listener bought the lifetime subscription because they prefer a one-time payment over monthly fees.
|
| 90 |
+
• Feature voting on the Rune forum showed that users want the offline grace period for servers re-enabled.
|
| 91 |
+
• This may be a defining moment for the company, and how they respond will impact future decisions.
|
| 92 |
+
• The Zimra board was mentioned as an alternative to Raspberry Pi, but the speaker is skeptical about buying one.
|
| 93 |
+
• Device is designed for installation in a vehicle due to its ruggedized features
|
| 94 |
+
• Concerns about company viability and potential Kickstarter pitfalls
|
| 95 |
+
• Discussion of device's performance, storage, and compatibility with peripherals
|
| 96 |
+
• Comparison to Odroid solution and concerns about form factor and design intent
|
| 97 |
+
• Potential uses and customizations of the device despite reservations
|
| 98 |
+
• Great submissions and boosts from community members, including MG, J-Cube, Nev, Acorn, and Thumbs
|
| 99 |
+
• Discussion of terminal emulators and apps, with user recommending Hollywood as a favorite app
|
| 100 |
+
• User memories of listening to the podcast in specific places and how it brought back memories
|
| 101 |
+
• Conversation about careers and life-changing moments sparked by listening to the podcast
|
| 102 |
+
• Discussion of an old interview where Docker wasn't yet called Docker
|
| 103 |
+
• Mentions of boosts and messages sent by "Ninja Mort" with no context or explanation
|
| 104 |
+
• Promotion of the podcast's membership program and self-hosted platform
|
| 105 |
+
• Mention of a Matrix instance for Jupyter broadcasting
|
| 106 |
+
• Acknowledgement of Alex for updating the infrastructure due to OpenSSL patches
|
| 107 |
+
• Setting up unattended upgrades on Ubuntu boxes
|
| 108 |
+
• Alex recommends using Ubuntu systems with auto-updates
|
| 109 |
+
• Discussing the effectiveness of automated security patches
|
| 110 |
+
• Mentioning feedback and contact information for the podcast
|
| 111 |
• Off-topic discussion about Elon Musk's projects and a notable financial transaction
|
84: Hidden NAS _summary.txt
CHANGED
|
@@ -1,58 +1,58 @@
|
|
| 1 |
-
• Host Alex is out sick
|
| 2 |
-
• Joe Resington joins the show to discuss building a new NAS box
|
| 3 |
-
• Host had issues with Raspberry Pi 4 and rebuilding his home setup
|
| 4 |
-
• Discussion of current Celeron J1800 NAS box and its quirks (requiring monitor to reboot)
|
| 5 |
-
• Considering replacing it with more powerful hardware due to age and limited capabilities
|
| 6 |
-
• Host's backup workstation is an i5 9600K, which could be used for the new NAS if needed
|
| 7 |
-
• Upcoming move and increased space may lead to new possibilities for the NAS box
|
| 8 |
-
• Discussion of data collection by smart TVs
|
| 9 |
-
• Connectivity issues with a network and VLAN
|
| 10 |
-
• Consideration of installing a GUI on top of a server for TV box functionality
|
| 11 |
-
• Testing and performance issues with an i5 box playing 4K content
|
| 12 |
-
• Decision to use Plex or Jellyfin for media management
|
| 13 |
-
• Hardware decoding and Intel QuickSync capabilities for improved performance
|
| 14 |
-
• Discussion of using a single device as both NAS and TV box
|
| 15 |
-
• Setting up a PC next to a TV on an IKEA sideboard
|
| 16 |
-
• Using the Odroid H3 as a home PC due to its features and performance
|
| 17 |
-
• Exploring alternative options for storing media files
|
| 18 |
-
• Configuring a NAS with multiple containers and file services
|
| 19 |
-
• Discussing software for smooth 4K playback on top of Zubuntu LTS
|
| 20 |
-
• Advertising Linode's cloud hosting service, highlighting its benefits and tools
|
| 21 |
-
• Installing Zigbee devices for home network
|
| 22 |
-
• Devices dropping off network, disappearing randomly
|
| 23 |
-
• Possible cause: interference from other wireless devices (microwaves, Wi-Fi) and low power devices
|
| 24 |
-
• Importance of proper antenna placement and strength
|
| 25 |
-
• Comparison to previous Z-Wave experience, which worked better due to operating at 915 MHz
|
| 26 |
-
• Solution: using smart plugs as network repeaters to compensate for signal gaps
|
| 27 |
-
• The speaker is experiencing issues with their Wi-Fi network and IoT devices, but finds Z-Wave devices to be more reliable.
|
| 28 |
-
• They compare the performance of various multi-sensor devices, including an expensive Aotec Multi-Sensor 7 that they highly recommend.
|
| 29 |
-
• The speaker notes that many Zigbee devices are becoming available due to Matter's adoption, which may lead to a decline in popularity for Z-Wave devices.
|
| 30 |
-
• They discuss the benefits of using the 900 MHz radio frequency for IoT devices, citing its reliability and efficiency.
|
| 31 |
-
• The conversation then shifts to note-taking apps, with the speaker sharing their experience with Evernote and expressing concerns about the app's future following an acquisition by Bending Spoons.
|
| 32 |
-
• Textual data store with index, search, and OCR capabilities
|
| 33 |
-
• Phone app and desktop app for easy access
|
| 34 |
-
• Sync and offline support for seamless use
|
| 35 |
-
• Multi-user or sharing features for collaborative work
|
| 36 |
-
• Comparison of Obsidian, Notion, and other note-taking apps
|
| 37 |
-
• Current system using a mix of Telegram messages, Google Docs, and text files on a server
|
| 38 |
-
• Desire for self-hosted solution to avoid dependence on external services like Evernote
|
| 39 |
-
• Feedback on Matrix rooms and their growth
|
| 40 |
-
• Belgian listener mentions monitoring software options, including Nagios, Prometheus, and Zabbix
|
| 41 |
-
• Discussion of uptime monitoring tools Uptime Kuma and Uptime Robot
|
| 42 |
-
• Mention of a German website itsco.de with secondhand small form factor systems for sale
|
| 43 |
-
• Boosts from The Helpful Idiot and C-dubs using Satoshis
|
| 44 |
-
• NixOS router setup with multiple LANs and Wi-Fi
|
| 45 |
-
• Wonky Wi-Fi connection causing client connections to drop randomly
|
| 46 |
-
• WireGuard proxy not routing traffic correctly due to firewall issues
|
| 47 |
-
• Suggested debugging steps: break down problems into separate issues, focus on Wi-Fi first, check logs, roll back kernel version
|
| 48 |
-
• Discussion of Wi-Fi issues with recent Linux kernels (6-series)
|
| 49 |
-
• Alternative solutions proposed: try a live Ubuntu session, install an older kernel, or use a different OS.
|
| 50 |
-
• Tailscale's business model
|
| 51 |
-
• Giving away free service to hook users, then charging for multiple device access
|
| 52 |
-
• Comparison to Dropbox's free tier strategy
|
| 53 |
-
• Peer-to-peer communication in Tailscale network
|
| 54 |
-
• Authentication process and key management
|
| 55 |
-
• Boosts from listeners, including Rapid Mustang and WM
|
| 56 |
-
• Job opportunity as site reliability engineer at selfhosted.show
|
| 57 |
-
• Upcoming features on the members feed, expected in early 2023
|
| 58 |
• Timeline dependent on completion of other projects by Santa, Wes, and Joe
|
|
|
|
| 1 |
+
• Host Alex is out sick
|
| 2 |
+
• Joe Resington joins the show to discuss building a new NAS box
|
| 3 |
+
• Host had issues with Raspberry Pi 4 and rebuilding his home setup
|
| 4 |
+
• Discussion of current Celeron J1800 NAS box and its quirks (requiring monitor to reboot)
|
| 5 |
+
• Considering replacing it with more powerful hardware due to age and limited capabilities
|
| 6 |
+
• Host's backup workstation is an i5 9600K, which could be used for the new NAS if needed
|
| 7 |
+
• Upcoming move and increased space may lead to new possibilities for the NAS box
|
| 8 |
+
• Discussion of data collection by smart TVs
|
| 9 |
+
• Connectivity issues with a network and VLAN
|
| 10 |
+
• Consideration of installing a GUI on top of a server for TV box functionality
|
| 11 |
+
• Testing and performance issues with an i5 box playing 4K content
|
| 12 |
+
• Decision to use Plex or Jellyfin for media management
|
| 13 |
+
• Hardware decoding and Intel QuickSync capabilities for improved performance
|
| 14 |
+
• Discussion of using a single device as both NAS and TV box
|
| 15 |
+
• Setting up a PC next to a TV on an IKEA sideboard
|
| 16 |
+
• Using the Odroid H3 as a home PC due to its features and performance
|
| 17 |
+
• Exploring alternative options for storing media files
|
| 18 |
+
• Configuring a NAS with multiple containers and file services
|
| 19 |
+
• Discussing software for smooth 4K playback on top of Zubuntu LTS
|
| 20 |
+
• Advertising Linode's cloud hosting service, highlighting its benefits and tools
|
| 21 |
+
• Installing Zigbee devices for home network
|
| 22 |
+
• Devices dropping off network, disappearing randomly
|
| 23 |
+
• Possible cause: interference from other wireless devices (microwaves, Wi-Fi) and low power devices
|
| 24 |
+
• Importance of proper antenna placement and strength
|
| 25 |
+
• Comparison to previous Z-Wave experience, which worked better due to operating at 915 MHz
|
| 26 |
+
• Solution: using smart plugs as network repeaters to compensate for signal gaps
|
| 27 |
+
• The speaker is experiencing issues with their Wi-Fi network and IoT devices, but finds Z-Wave devices to be more reliable.
|
| 28 |
+
• They compare the performance of various multi-sensor devices, including an expensive Aotec Multi-Sensor 7 that they highly recommend.
|
| 29 |
+
• The speaker notes that many Zigbee devices are becoming available due to Matter's adoption, which may lead to a decline in popularity for Z-Wave devices.
|
| 30 |
+
• They discuss the benefits of using the 900 MHz radio frequency for IoT devices, citing its reliability and efficiency.
|
| 31 |
+
• The conversation then shifts to note-taking apps, with the speaker sharing their experience with Evernote and expressing concerns about the app's future following an acquisition by Bending Spoons.
|
| 32 |
+
• Textual data store with index, search, and OCR capabilities
|
| 33 |
+
• Phone app and desktop app for easy access
|
| 34 |
+
• Sync and offline support for seamless use
|
| 35 |
+
• Multi-user or sharing features for collaborative work
|
| 36 |
+
• Comparison of Obsidian, Notion, and other note-taking apps
|
| 37 |
+
• Current system using a mix of Telegram messages, Google Docs, and text files on a server
|
| 38 |
+
• Desire for self-hosted solution to avoid dependence on external services like Evernote
|
| 39 |
+
• Feedback on Matrix rooms and their growth
|
| 40 |
+
• Belgian listener mentions monitoring software options, including Nagios, Prometheus, and Zabbix
|
| 41 |
+
• Discussion of uptime monitoring tools Uptime Kuma and Uptime Robot
|
| 42 |
+
• Mention of a German website itsco.de with secondhand small form factor systems for sale
|
| 43 |
+
• Boosts from The Helpful Idiot and C-dubs using Satoshis
|
| 44 |
+
• NixOS router setup with multiple LANs and Wi-Fi
|
| 45 |
+
• Wonky Wi-Fi connection causing client connections to drop randomly
|
| 46 |
+
• WireGuard proxy not routing traffic correctly due to firewall issues
|
| 47 |
+
• Suggested debugging steps: break down problems into separate issues, focus on Wi-Fi first, check logs, roll back kernel version
|
| 48 |
+
• Discussion of Wi-Fi issues with recent Linux kernels (6-series)
|
| 49 |
+
• Alternative solutions proposed: try a live Ubuntu session, install an older kernel, or use a different OS.
|
| 50 |
+
• Tailscale's business model
|
| 51 |
+
• Giving away free service to hook users, then charging for multiple device access
|
| 52 |
+
• Comparison to Dropbox's free tier strategy
|
| 53 |
+
• Peer-to-peer communication in Tailscale network
|
| 54 |
+
• Authentication process and key management
|
| 55 |
+
• Boosts from listeners, including Rapid Mustang and WM
|
| 56 |
+
• Job opportunity as site reliability engineer at selfhosted.show
|
| 57 |
+
• Upcoming features on the members feed, expected in early 2023
|
| 58 |
• Timeline dependent on completion of other projects by Santa, Wes, and Joe
|
85: Wendell's Hot Pi _summary.txt
CHANGED
|
@@ -1,83 +1,83 @@
|
|
| 1 |
-
• Alex discusses his recent COVID-19 experience and recovery
|
| 2 |
-
• Wendell returns to the show after a long absence
|
| 3 |
-
• Discussion of liquidation sales for self-hosting equipment, including servers and hardware
|
| 4 |
-
• Chris shares his experience with low-power hardware in self-hosting, specifically Odroid
|
| 5 |
-
• Intel's new chip architecture and its implications for self-hosting
|
| 6 |
-
• Comparison of different virtualization platforms (VMware, Proxmox, XCPNG) and their performance on multi-core systems
|
| 7 |
-
• Discussion of the appeal of $100 processors and DDR4 memory for home server use cases
|
| 8 |
-
• The author discusses their $100 Alder Lake P core processor and its turbo capabilities.
|
| 9 |
-
• They compare it to a previous Gigabyte board with two Xeon sockets, citing its performance and features as impressive.
|
| 10 |
-
• The author mentions a new Gigabyte board that combines 12th and 13th gen CPUs, M.2 slots, PCIe slots, and DDR4 memory.
|
| 11 |
-
• They note the significant performance increase of Alder Lake P cores compared to older generations.
|
| 12 |
-
• The author expresses excitement about Intel's resurgence in innovation and efficiency.
|
| 13 |
-
• They also discuss AMD's Ryzen 7000 series, which they acknowledge as expensive but powerful options.
|
| 14 |
-
• The author compares different processor configurations, highlighting the balance between power consumption and performance.
|
| 15 |
-
• Home server requirements and performance comparisons
|
| 16 |
-
• Importance of media encoding engines (QuickSync vs AMD support)
|
| 17 |
-
• Energy efficiency and power consumption considerations
|
| 18 |
-
• BMCs (Baseboard Management Controllers) and their potential cryptocurrency mining activities
|
| 19 |
-
• Storage management techniques (e.g., ZFS, metadata special device, RAID configurations)
|
| 20 |
-
• Personal storage setup and configuration details
|
| 21 |
-
• Discussing the difficulty of creating YouTube content about Blu-ray due to potential copyright issues
|
| 22 |
-
• Sharing a personal experience of ripping and re-ripping a DVD collection and the shift from streaming to local storage due to concerns about availability
|
| 23 |
-
• Mentioning petabyte-sized storage solutions and their advantages
|
| 24 |
-
• Discussing home automation projects, specifically:
|
| 25 |
-
+ The re-server device with low power consumption and high performance
|
| 26 |
-
+ Using Optane for fast storage and discussing its "fire sale" price
|
| 27 |
-
+ Setting up a home automation system with ZFS and metadata on M.2 drives
|
| 28 |
-
+ Using Bluetooth low energy sensors in the home automation setup
|
| 29 |
-
• The speaker has integrated their Home Assistant system with a touchscreen display
|
| 30 |
-
• They've replaced an old thermostat with a new one that's connected to the Home Assistant system
|
| 31 |
-
• The speaker discusses designing for redundancy in case of failures or component breakdowns
|
| 32 |
-
• They show interest in the re-terminal device from Siege Studio, which is an all-in-one Raspberry Pi board
|
| 33 |
-
• The conversation turns to considerations for mounting and powering the touchscreen display
|
| 34 |
-
• Discussion of power over Ethernet and potential future projects
|
| 35 |
-
• Seed electronic project platform and DIY electronics
|
| 36 |
-
• Use of pre-existing CO2 sensor module and experimentation with various sensors
|
| 37 |
-
• Home alarm system integration with home assistant for 100% reliability
|
| 38 |
-
• UPS discussion, including the idea of using lithium-ion battery packs as a UPS alternative
|
| 39 |
-
• Lithium-ion battery management: keeping charge levels below 70-72%
|
| 40 |
-
• Overcharging lead acid batteries with a specific UPS model
|
| 41 |
-
• Introducing CrowdStrike's LogScale tool for centralized log management and observability
|
| 42 |
-
• Features of LogScale, including index-free architecture and reduced hardware footprint
|
| 43 |
-
• Using LogScale Community Edition for no-cost data ingestion
|
| 44 |
-
• Experiences with Zigbee devices dropping off the network
|
| 45 |
-
• Concerns with Zigbee and Z-Wave sensor reliability and connectivity issues
|
| 46 |
-
• Experiences with PIR sensors dropping out of the alarm panel and water sensors not alerting in time
|
| 47 |
-
• Comparison between Zigbee and Z-Wave device reliability
|
| 48 |
-
• Frustration with unreliable IKEA Tradfri buttons and NFC tags
|
| 49 |
-
• Desire for a reliable, always-on protocol for smart home devices
|
| 50 |
-
• Criticism of Home Assistant's handling of sensor status and notifications
|
| 51 |
-
• Reliability issues with temperature sensors
|
| 52 |
-
• Comparison of older alarm sensors and modern IoT devices
|
| 53 |
-
• Discussion of radio frequency interference (RFI) and its impact on IoT networks
|
| 54 |
-
• Critique of modern design assumptions based on outdated technology
|
| 55 |
-
• Explanation of spread spectrum algorithms and their benefits for reducing RFI
|
| 56 |
-
• Personal experience with separating WiFi and Zigbee devices to improve network reliability
|
| 57 |
-
• Reflection on the failure of modern IoT technologies to live up to expectations
|
| 58 |
-
• Hosting provider discussed, with the speaker preferring Linode due to its reliability and support
|
| 59 |
-
• Linode's features and offerings, including MVME rigs and dedicated CPU rigs
|
| 60 |
-
• Alternative hosting options mentioned, but dismissed in favor of established providers like Linode
|
| 61 |
-
• Note-taking system discussed, with feedback on Evernote and alternatives such as Obsidian
|
| 62 |
-
• Obsidian plugin ecosystem and flexibility for note management and organization
|
| 63 |
-
• Use cases for Obsidian, including book tracking and management with Calibre and Google Books API plugins
|
| 64 |
-
• Discussion of OCR capabilities in Obsidian, including local and cloud-based options.
|
| 65 |
-
• Discussion of using Azure OCR for document processing
|
| 66 |
-
• Alternative methods for note-taking and organization (Office Lens, OneNote, Obsidian, NextCloud)
|
| 67 |
-
• Introduction to Zettelkasten method for knowledge capture
|
| 68 |
-
• Description of how to implement the Zettelkasten method with index cards and digital tools
|
| 69 |
-
• Comparison of Obsidian and other note-taking apps (MK docs, Tiddlywiki)
|
| 70 |
-
• Discussion about plugin options and first-mover advantages in the plugin space
|
| 71 |
-
• Notion mentioned as a versatile tool for daily work diary entries and programming
|
| 72 |
-
• App flowy.io introduced as an open-source alternative to Notion
|
| 73 |
-
• Concerns about data ownership with proprietary tools like Notion
|
| 74 |
-
• Joplin with Nextcloud discussed as a potential replacement for Evernote or other note-taking apps
|
| 75 |
-
• Experiences with data loss in the past, particularly with Joplin
|
| 76 |
-
• Discussion of data loss and reliability in storage solutions
|
| 77 |
-
• Comparison and debate between ZFS and ButterFS for file systems
|
| 78 |
-
• Licensing issues affecting the use of ZFS on certain platforms
|
| 79 |
-
• Personal experiences with re-architecting home setup using Proxmox, XCPNG, OpenShift, Ceph, and hyperconvergence
|
| 80 |
-
• Discussion of running complex software solutions at home, including OpenShift
|
| 81 |
-
• Mention of Intel Arc and intention to discuss it in a post-show
|
| 82 |
-
• Excitement about building a desktop computer after a five-year break, possibly due to crypto and COVID supply chain issues
|
| 83 |
• Discussion of social media alternatives (Matrix Fediverse, Mastodon, Truth Social) and the desire for a simple, single-binary solution like a Go or Rust-based Twitter clone
|
|
|
|
| 1 |
+
• Alex discusses his recent COVID-19 experience and recovery
|
| 2 |
+
• Wendell returns to the show after a long absence
|
| 3 |
+
• Discussion of liquidation sales for self-hosting equipment, including servers and hardware
|
| 4 |
+
• Chris shares his experience with low-power hardware in self-hosting, specifically Odroid
|
| 5 |
+
• Intel's new chip architecture and its implications for self-hosting
|
| 6 |
+
• Comparison of different virtualization platforms (VMware, Proxmox, XCPNG) and their performance on multi-core systems
|
| 7 |
+
• Discussion of the appeal of $100 processors and DDR4 memory for home server use cases
|
| 8 |
+
• The author discusses their $100 Alder Lake P core processor and its turbo capabilities.
|
| 9 |
+
• They compare it to a previous Gigabyte board with two Xeon sockets, citing its performance and features as impressive.
|
| 10 |
+
• The author mentions a new Gigabyte board that combines 12th and 13th gen CPUs, M.2 slots, PCIe slots, and DDR4 memory.
|
| 11 |
+
• They note the significant performance increase of Alder Lake P cores compared to older generations.
|
| 12 |
+
• The author expresses excitement about Intel's resurgence in innovation and efficiency.
|
| 13 |
+
• They also discuss AMD's Ryzen 7000 series, which they acknowledge as expensive but powerful options.
|
| 14 |
+
• The author compares different processor configurations, highlighting the balance between power consumption and performance.
|
| 15 |
+
• Home server requirements and performance comparisons
|
| 16 |
+
• Importance of media encoding engines (QuickSync vs AMD support)
|
| 17 |
+
• Energy efficiency and power consumption considerations
|
| 18 |
+
• BMCs (Baseboard Management Controllers) and their potential cryptocurrency mining activities
|
| 19 |
+
• Storage management techniques (e.g., ZFS, metadata special device, RAID configurations)
|
| 20 |
+
• Personal storage setup and configuration details
|
| 21 |
+
• Discussing the difficulty of creating YouTube content about Blu-ray due to potential copyright issues
|
| 22 |
+
• Sharing a personal experience of ripping and re-ripping a DVD collection and the shift from streaming to local storage due to concerns about availability
|
| 23 |
+
• Mentioning petabyte-sized storage solutions and their advantages
|
| 24 |
+
• Discussing home automation projects, specifically:
|
| 25 |
+
+ The re-server device with low power consumption and high performance
|
| 26 |
+
+ Using Optane for fast storage and discussing its "fire sale" price
|
| 27 |
+
+ Setting up a home automation system with ZFS and metadata on M.2 drives
|
| 28 |
+
+ Using Bluetooth low energy sensors in the home automation setup
|
| 29 |
+
• The speaker has integrated their Home Assistant system with a touchscreen display
|
| 30 |
+
• They've replaced an old thermostat with a new one that's connected to the Home Assistant system
|
| 31 |
+
• The speaker discusses designing for redundancy in case of failures or component breakdowns
|
| 32 |
+
• They show interest in the re-terminal device from Siege Studio, which is an all-in-one Raspberry Pi board
|
| 33 |
+
• The conversation turns to considerations for mounting and powering the touchscreen display
|
| 34 |
+
• Discussion of power over Ethernet and potential future projects
|
| 35 |
+
• Seed electronic project platform and DIY electronics
|
| 36 |
+
• Use of pre-existing CO2 sensor module and experimentation with various sensors
|
| 37 |
+
• Home alarm system integration with home assistant for 100% reliability
|
| 38 |
+
• UPS discussion, including the idea of using lithium-ion battery packs as a UPS alternative
|
| 39 |
+
• Lithium-ion battery management: keeping charge levels below 70-72%
|
| 40 |
+
• Overcharging lead acid batteries with a specific UPS model
|
| 41 |
+
• Introducing CrowdStrike's LogScale tool for centralized log management and observability
|
| 42 |
+
• Features of LogScale, including index-free architecture and reduced hardware footprint
|
| 43 |
+
• Using LogScale Community Edition for no-cost data ingestion
|
| 44 |
+
• Experiences with Zigbee devices dropping off the network
|
| 45 |
+
• Concerns with Zigbee and Z-Wave sensor reliability and connectivity issues
|
| 46 |
+
• Experiences with PIR sensors dropping out of the alarm panel and water sensors not alerting in time
|
| 47 |
+
• Comparison between Zigbee and Z-Wave device reliability
|
| 48 |
+
• Frustration with unreliable IKEA Tradfri buttons and NFC tags
|
| 49 |
+
• Desire for a reliable, always-on protocol for smart home devices
|
| 50 |
+
• Criticism of Home Assistant's handling of sensor status and notifications
|
| 51 |
+
• Reliability issues with temperature sensors
|
| 52 |
+
• Comparison of older alarm sensors and modern IoT devices
|
| 53 |
+
• Discussion of radio frequency interference (RFI) and its impact on IoT networks
|
| 54 |
+
• Critique of modern design assumptions based on outdated technology
|
| 55 |
+
• Explanation of spread spectrum algorithms and their benefits for reducing RFI
|
| 56 |
+
• Personal experience with separating WiFi and Zigbee devices to improve network reliability
|
| 57 |
+
• Reflection on the failure of modern IoT technologies to live up to expectations
|
| 58 |
+
• Hosting provider discussed, with the speaker preferring Linode due to its reliability and support
|
| 59 |
+
• Linode's features and offerings, including MVME rigs and dedicated CPU rigs
|
| 60 |
+
• Alternative hosting options mentioned, but dismissed in favor of established providers like Linode
|
| 61 |
+
• Note-taking system discussed, with feedback on Evernote and alternatives such as Obsidian
|
| 62 |
+
• Obsidian plugin ecosystem and flexibility for note management and organization
|
| 63 |
+
• Use cases for Obsidian, including book tracking and management with Calibre and Google Books API plugins
|
| 64 |
+
• Discussion of OCR capabilities in Obsidian, including local and cloud-based options.
|
| 65 |
+
• Discussion of using Azure OCR for document processing
|
| 66 |
+
• Alternative methods for note-taking and organization (Office Lens, OneNote, Obsidian, NextCloud)
|
| 67 |
+
• Introduction to Zettelkasten method for knowledge capture
|
| 68 |
+
• Description of how to implement the Zettelkasten method with index cards and digital tools
|
| 69 |
+
• Comparison of Obsidian and other note-taking apps (MK docs, Tiddlywiki)
|
| 70 |
+
• Discussion about plugin options and first-mover advantages in the plugin space
|
| 71 |
+
• Notion mentioned as a versatile tool for daily work diary entries and programming
|
| 72 |
+
• App flowy.io introduced as an open-source alternative to Notion
|
| 73 |
+
• Concerns about data ownership with proprietary tools like Notion
|
| 74 |
+
• Joplin with Nextcloud discussed as a potential replacement for Evernote or other note-taking apps
|
| 75 |
+
• Experiences with data loss in the past, particularly with Joplin
|
| 76 |
+
• Discussion of data loss and reliability in storage solutions
|
| 77 |
+
• Comparison and debate between ZFS and ButterFS for file systems
|
| 78 |
+
• Licensing issues affecting the use of ZFS on certain platforms
|
| 79 |
+
• Personal experiences with re-architecting home setup using Proxmox, XCPNG, OpenShift, Ceph, and hyperconvergence
|
| 80 |
+
• Discussion of running complex software solutions at home, including OpenShift
|
| 81 |
+
• Mention of Intel Arc and intention to discuss it in a post-show
|
| 82 |
+
• Excitement about building a desktop computer after a five-year break, possibly due to crypto and COVID supply chain issues
|
| 83 |
• Discussion of social media alternatives (Matrix Fediverse, Mastodon, Truth Social) and the desire for a simple, single-binary solution like a Go or Rust-based Twitter clone
|
86: Disqus-ting Tracking _summary.txt
CHANGED
|
@@ -1,70 +1,70 @@
|
|
| 1 |
-
• Configuring HTOP to expose additional data
|
| 2 |
-
• Reddit's Lazy Mode feature for auto-scrolling
|
| 3 |
-
• Recommendations for a good Reddit client (Infinity app)
|
| 4 |
-
• Discussion of Reddit scrolling habits and potential health effects
|
| 5 |
-
• Request for help with Android home automation notifications using Home Assistant
|
| 6 |
-
• Introduction to AppRise, a notification consolidation framework
|
| 7 |
-
• Discussing notification and templating options for Home Assistant
|
| 8 |
-
• Considering alternatives to Telegram for messaging, including Fluffy Chat
|
| 9 |
-
• Exploring Tasker as an automation tool on Android devices
|
| 10 |
-
• Introduction to Linode and its features for hosting servers in the cloud
|
| 11 |
-
• Promotion of Linode's services, including $100 free credit and various pricing plans
|
| 12 |
-
• Community support and commitment for various platforms
|
| 13 |
-
• Experience with ad blockers and website adverts on personal blog
|
| 14 |
-
• Switching from Disgust commenting engine to Giscus, which uses GitHub notifications
|
| 15 |
-
• Exporting comments from Discuss and importing them into Giscus using scripts
|
| 16 |
-
• Setting up the backend software for Giscus, including self-hosted options
|
| 17 |
-
• Ghost API and automatic theme changes
|
| 18 |
-
• GitHub dependency for comment moderation
|
| 19 |
-
• Compromises made for ease of use vs self-hosting
|
| 20 |
-
• Matrix comment moderation and bot integration
|
| 21 |
-
• Centralization of comments on GitHub
|
| 22 |
-
• Safety and reputation system on GitHub
|
| 23 |
-
• Alternative solutions including no comments at all
|
| 24 |
-
• The user has a similar motherboard setup at their mother-in-law's house in England, which now has fiber internet with high upload speeds.
|
| 25 |
-
• The user purchased an HD Home Run device to access over-the-air network TV channels and stream them using Plex.
|
| 26 |
-
• The user set up the HD Home Run device at their mother-in-law's house and was able to easily add it to their Plex server after entering their postcode.
|
| 27 |
-
• The user is now able to watch live TV and record shows using their self-hosted infrastructure, including Plex on an iPad in an airport.
|
| 28 |
-
• The user considers purchasing another HD Home Run device for local news and other channels, potentially canceling a paid streaming service.
|
| 29 |
-
• CrowdStrike Falcon LogScale: a centralized log management and observability tool
|
| 30 |
-
• Ingests logs from various sources without schema or formatting requirements
|
| 31 |
-
• Index-free architecture allows for high data ingestion rates (over a petabyte per day) with sub-second latency
|
| 32 |
-
• Community Edition offers up to 16 GB/day log ingestion and 7-day retention at no cost
|
| 33 |
-
• Potential use in troubleshooting, infrastructure building, and home network management
|
| 34 |
-
• HDMI signal transmission over LAN using IP-based network and multicast
|
| 35 |
-
• The person is discussing their recent gaming experience with Dwarf Fortress on a portable device.
|
| 36 |
-
• They mention being sensitive to video compression artifacts and discuss the importance of a solid network for using multicast technology.
|
| 37 |
-
• The conversation shifts to a product review, specifically a KVM (Keyboard, Video, Mouse) solution that allows remote access to multiple devices over a network.
|
| 38 |
-
• The person describes how the KVM system works and its potential applications, such as having a dashboard or video feed in various rooms of a house.
|
| 39 |
-
• They compare the product to building a Pi-based KVM solution and conclude that it is a cost-effective alternative with similar capabilities.
|
| 40 |
-
• The conversation ends with a mention of wanting to follow up on the product review and possibly doing a giveaway.
|
| 41 |
-
• The host has a 14-terabyte hard drive for sale
|
| 42 |
-
• A giveaway is being held for a 10-terabyte hard drive to a deserving person or organization
|
| 43 |
-
• Eligibility and rules for the giveaway are discussed, including location restrictions and audience voting
|
| 44 |
-
• Discussion of note-taking tools and apps, including Obsidian, Hugo, and Working Copy
|
| 45 |
-
• Tips and recommendations shared by listeners on various topics, including Android use and YouTube alternatives
|
| 46 |
-
• NewPipe is an alternative YouTube client that offers a lean and customized experience
|
| 47 |
-
• It supports multi-threaded downloads and sends videos directly to preferred players
|
| 48 |
-
• However, it does not support live streams or timestamps and video chapters
|
| 49 |
-
• The user prefers the YouTube app's download feature over NewPipe's
|
| 50 |
-
• The user discusses the benefits of using Albie, including generating a lightning address and participating in boosts
|
| 51 |
-
• Albie can be used to host a node and manage lightning liquidity, with Saturn providing a live boost dashboard
|
| 52 |
-
• Boosts and boostograms
|
| 53 |
-
• Saturn's self-hosted shows page
|
| 54 |
-
• Albie extension for boosting without new podcast app
|
| 55 |
-
• Moon pay as a service for topping off sats in Albie
|
| 56 |
-
• Boost of the week from "helpful idiot" for 555,556 sats
|
| 57 |
-
• Comments on the show, including GIF equals GIF joke and pronunciation discussion
|
| 58 |
-
• Discussion of using standard notes for privacy due to local encryption
|
| 59 |
-
• Mention of Zettler and Zettelkasten as note-taking methods
|
| 60 |
-
• Explanation of linking documents in a digital workspace for complex connections
|
| 61 |
-
• Reflection on the speaker's difficulty implementing Zettelkasten in practice
|
| 62 |
-
• Brief discussion of computers' capabilities compared to past models
|
| 63 |
-
• Comments on the podcast's self-hosted setup and sponsors
|
| 64 |
-
• Acknowledgement of listeners who have sent boosts
|
| 65 |
-
• The system forces creators to produce engaging content, including silly thumbnails and begging for comments.
|
| 66 |
-
• This tactic can be frustrating for viewers and takes down the experience.
|
| 67 |
-
• The algorithm considers even negative comments as engagement, encouraging creators to provoke reactions.
|
| 68 |
-
• A special promotion is available for Jupiter.party membership with a promo code "2022" for a discount.
|
| 69 |
-
• Upcoming topics may include the Raspberry Pi hoopla and witch hunt in the self-hosting community.
|
| 70 |
• Contact information and social media links are provided.
|
|
|
|
| 1 |
+
• Configuring HTOP to expose additional data
|
| 2 |
+
• Reddit's Lazy Mode feature for auto-scrolling
|
| 3 |
+
• Recommendations for a good Reddit client (Infinity app)
|
| 4 |
+
• Discussion of Reddit scrolling habits and potential health effects
|
| 5 |
+
• Request for help with Android home automation notifications using Home Assistant
|
| 6 |
+
• Introduction to AppRise, a notification consolidation framework
|
| 7 |
+
• Discussing notification and templating options for Home Assistant
|
| 8 |
+
• Considering alternatives to Telegram for messaging, including Fluffy Chat
|
| 9 |
+
• Exploring Tasker as an automation tool on Android devices
|
| 10 |
+
• Introduction to Linode and its features for hosting servers in the cloud
|
| 11 |
+
• Promotion of Linode's services, including $100 free credit and various pricing plans
|
| 12 |
+
• Community support and commitment for various platforms
|
| 13 |
+
• Experience with ad blockers and website adverts on personal blog
|
| 14 |
+
• Switching from Disgust commenting engine to Giscus, which uses GitHub notifications
|
| 15 |
+
• Exporting comments from Discuss and importing them into Giscus using scripts
|
| 16 |
+
• Setting up the backend software for Giscus, including self-hosted options
|
| 17 |
+
• Ghost API and automatic theme changes
|
| 18 |
+
• GitHub dependency for comment moderation
|
| 19 |
+
• Compromises made for ease of use vs self-hosting
|
| 20 |
+
• Matrix comment moderation and bot integration
|
| 21 |
+
• Centralization of comments on GitHub
|
| 22 |
+
• Safety and reputation system on GitHub
|
| 23 |
+
• Alternative solutions including no comments at all
|
| 24 |
+
• The user has a similar motherboard setup at their mother-in-law's house in England, which now has fiber internet with high upload speeds.
|
| 25 |
+
• The user purchased an HD Home Run device to access over-the-air network TV channels and stream them using Plex.
|
| 26 |
+
• The user set up the HD Home Run device at their mother-in-law's house and was able to easily add it to their Plex server after entering their postcode.
|
| 27 |
+
• The user is now able to watch live TV and record shows using their self-hosted infrastructure, including Plex on an iPad in an airport.
|
| 28 |
+
• The user considers purchasing another HD Home Run device for local news and other channels, potentially canceling a paid streaming service.
|
| 29 |
+
• CrowdStrike Falcon LogScale: a centralized log management and observability tool
|
| 30 |
+
• Ingests logs from various sources without schema or formatting requirements
|
| 31 |
+
• Index-free architecture allows for high data ingestion rates (over a petabyte per day) with sub-second latency
|
| 32 |
+
• Community Edition offers up to 16 GB/day log ingestion and 7-day retention at no cost
|
| 33 |
+
• Potential use in troubleshooting, infrastructure building, and home network management
|
| 34 |
+
• HDMI signal transmission over LAN using IP-based network and multicast
|
| 35 |
+
• The person is discussing their recent gaming experience with Dwarf Fortress on a portable device.
|
| 36 |
+
• They mention being sensitive to video compression artifacts and discuss the importance of a solid network for using multicast technology.
|
| 37 |
+
• The conversation shifts to a product review, specifically a KVM (Keyboard, Video, Mouse) solution that allows remote access to multiple devices over a network.
|
| 38 |
+
• The person describes how the KVM system works and its potential applications, such as having a dashboard or video feed in various rooms of a house.
|
| 39 |
+
• They compare the product to building a Pi-based KVM solution and conclude that it is a cost-effective alternative with similar capabilities.
|
| 40 |
+
• The conversation ends with a mention of wanting to follow up on the product review and possibly doing a giveaway.
|
| 41 |
+
• The host has a 14-terabyte hard drive for sale
|
| 42 |
+
• A giveaway is being held for a 10-terabyte hard drive to a deserving person or organization
|
| 43 |
+
• Eligibility and rules for the giveaway are discussed, including location restrictions and audience voting
|
| 44 |
+
• Discussion of note-taking tools and apps, including Obsidian, Hugo, and Working Copy
|
| 45 |
+
• Tips and recommendations shared by listeners on various topics, including Android use and YouTube alternatives
|
| 46 |
+
• NewPipe is an alternative YouTube client that offers a lean and customized experience
|
| 47 |
+
• It supports multi-threaded downloads and sends videos directly to preferred players
|
| 48 |
+
• However, it does not support live streams or timestamps and video chapters
|
| 49 |
+
• The user prefers the YouTube app's download feature over NewPipe's
|
| 50 |
+
• The user discusses the benefits of using Albie, including generating a lightning address and participating in boosts
|
| 51 |
+
• Albie can be used to host a node and manage lightning liquidity, with Saturn providing a live boost dashboard
|
| 52 |
+
• Boosts and boostograms
|
| 53 |
+
• Saturn's self-hosted shows page
|
| 54 |
+
• Albie extension for boosting without new podcast app
|
| 55 |
+
• Moon pay as a service for topping off sats in Albie
|
| 56 |
+
• Boost of the week from "helpful idiot" for 555,556 sats
|
| 57 |
+
• Comments on the show, including GIF equals GIF joke and pronunciation discussion
|
| 58 |
+
• Discussion of using standard notes for privacy due to local encryption
|
| 59 |
+
• Mention of Zettler and Zettelkasten as note-taking methods
|
| 60 |
+
• Explanation of linking documents in a digital workspace for complex connections
|
| 61 |
+
• Reflection on the speaker's difficulty implementing Zettelkasten in practice
|
| 62 |
+
• Brief discussion of computers' capabilities compared to past models
|
| 63 |
+
• Comments on the podcast's self-hosted setup and sponsors
|
| 64 |
+
• Acknowledgement of listeners who have sent boosts
|
| 65 |
+
• The system forces creators to produce engaging content, including silly thumbnails and begging for comments.
|
| 66 |
+
• This tactic can be frustrating for viewers and takes down the experience.
|
| 67 |
+
• The algorithm considers even negative comments as engagement, encouraging creators to provoke reactions.
|
| 68 |
+
• A special promotion is available for Jupiter.party membership with a promo code "2022" for a discount.
|
| 69 |
+
• Upcoming topics may include the Raspberry Pi hoopla and witch hunt in the self-hosting community.
|
| 70 |
• Contact information and social media links are provided.
|
87: Jellyfin January _summary.txt
CHANGED
|
@@ -1,104 +1,104 @@
|
|
| 1 |
-
• Introduction and welcome of guests
|
| 2 |
-
• Home Assistant SkyConnect dongle review: description, features, and benefits
|
| 3 |
-
• Matter standard updates and potential impact on existing Zigbee networks
|
| 4 |
-
• Discussion of the need for an open smart home platform and Home Assistant's growing mainstream traction
|
| 5 |
-
• Personal anecdotes about family members' interest in Home Assistant and its ease of use
|
| 6 |
-
• Hardware strategy discussion for setting up a Home Assistant system at a distant location
|
| 7 |
-
• Lady Joupes' lithium ion battery bank malfunctioning due to cold temperatures
|
| 8 |
-
• Power outage caused by a series of electrical hits affecting a home's Wi-Fi network
|
| 9 |
-
• Frequent dropouts and losses of Wi-Fi connectivity despite hardware remaining online
|
| 10 |
-
• Decision to replace existing Wi-Fi system with a new TP-Link EAP 245 version 3 unit
|
| 11 |
-
• Comparison of TP-Link and UniFi systems, including self-hosted control centers
|
| 12 |
-
• Troubleshooting efforts to identify cause of Wi-Fi dropouts and losses
|
| 13 |
-
• Discussion of Linus Tech Tips video on Wi-Fi issues caused by Z-Wave devices
|
| 14 |
-
• Use of SDR (Software Defined Radio) for troubleshooting Wi-Fi and radio frequency interference
|
| 15 |
-
• Personal experience with using Android Wi-Fi analyzer tool to improve network performance
|
| 16 |
-
• Description of neighbor's strong printer AP causing interference
|
| 17 |
-
• Plans for a giveaway of a Western Digital 10TB hard drive
|
| 18 |
-
• Promotion of Linode hosting services, including $100 credit offer
|
| 19 |
-
• Supporting the show through Linode
|
| 20 |
-
• Jellyfin January challenge: disabling Plex servers and switching to Jellyfin for a month
|
| 21 |
-
• Raising the profile of Jellyfin and creating a viable alternative to Plex
|
| 22 |
-
• Criticisms of Plex's business model and its impact on users
|
| 23 |
-
• Discussion of cloud connectivity, authentication, and ad-supported media features
|
| 24 |
-
• Concerns about Plex's shift in focus from core streaming functionality to more extensive industry positioning
|
| 25 |
-
• The user is frustrated with Jellyfin's automatic startup behavior
|
| 26 |
-
• Concerns about data ownership and linking to Plex servers
|
| 27 |
-
• Invitation to Brent, a Jellyfin user, to provide feedback on his experience
|
| 28 |
-
• Discussion of the user's past experience with Jellyfin, including setup and potential improvements
|
| 29 |
-
• Review of Jellyfin's GitHub activity, showing 90 PRs accepted in one month and 800 contributors in total
|
| 30 |
-
• Interest in testing the Watch Together feature and reporting back on its performance
|
| 31 |
-
• Ground rules for the challenge, including Plex servers being offline and no switching to other apps during the test period
|
| 32 |
-
• Jellyfin devs mentioned in chat for adding feature requests
|
| 33 |
-
• Audiobook playback and spousal approval discussed as important features
|
| 34 |
-
• Discussion of switching from Prologue to Jellyfin and potential continued use of Plex for audiobooks and music
|
| 35 |
-
• Hardware transcoding issues on Linux server, including Intel GPU and NVIDIA usage
|
| 36 |
-
• Monitoring and metrics, specifically using Tautuli to track streaming activity and device usage
|
| 37 |
-
• Integration of Tautuli with Jellyfin or rewriting Jellyfin server metrics
|
| 38 |
-
• Importance of hardware acceleration and its benefits (e.g. quick sync)
|
| 39 |
-
• Strategies for achieving hardware acceleration (e.g. Linux server IO image, project image, packages)
|
| 40 |
-
• User experience issues with Jellyfin (e.g. skipping intros, subtitles/audio tracks/video quality)
|
| 41 |
-
• Comparison of Jellyfin to Plex and its performance
|
| 42 |
-
• Lack of Apple TV app support and potential limitations
|
| 43 |
-
• Jellyfin's default functionality does not include intro skipping
|
| 44 |
-
• A community plugin can skip intros, but has limitations and is not elegant
|
| 45 |
-
• Native Jellyfin client Swiftfin for iOS and tvOS is under development
|
| 46 |
-
• Hosts plan to test Jellyfin on their servers, including one in England with live TV capabilities
|
| 47 |
-
• Listener Brent has multiple options for running Jellyfin, including Raspberry Pis and a NAS server, and seeks advice from the hosts
|
| 48 |
-
• Discussing the goal of trying Jellyfin media server
|
| 49 |
-
• Comparing the ease of use and administrative burden of Jellyfin versus Plex
|
| 50 |
-
• Considering using a Raspberry Pi with Ubuntu LTS for running Jellyfin, with pros and cons discussed
|
| 51 |
-
• Evaluating the performance and potential issues of running multiple streams on a Raspberry Pi
|
| 52 |
-
• Exploring options for network storage and setup
|
| 53 |
-
• Weighing the decision to use a Raspberry Pi or an x86 system for running Jellyfin
|
| 54 |
-
• Suggesting a two-phased approach to deploying Jellyfin, setting it up first on an x86 box and then transferring to a permanent home
|
| 55 |
-
• Introduction of CrowdStrike Falcon LogScale for log management and observability
|
| 56 |
-
• Description of LogScale's index-free architecture and benefits, including fast search capabilities and lower cost compared to other platforms like Splunk or Elastic
|
| 57 |
-
• Announcement of CrowdStrike.com/LCE as a free trial for LogScale Community Edition with up to 16 GB/day ingestion and 7 days retention
|
| 58 |
-
• Discussion of the Matrix Project's financial struggles, including layoffs of core team members and funding issues due to lost value in tech stocks
|
| 59 |
-
• Support for the Matrix project and community
|
| 60 |
-
• Financial contributions to the Matrix Foundation
|
| 61 |
-
• Criticism of the foundation's approach to fundraising and sustainability
|
| 62 |
-
• Comparison with other projects, such as Linux
|
| 63 |
-
• Ambitious goals and scalability challenges for Matrix
|
| 64 |
-
• Personal opinion on the effectiveness of current methods
|
| 65 |
-
• Discussion of Matrix's goals and relevance in the market
|
| 66 |
-
• Comparison to Linux Foundation and its business model
|
| 67 |
-
• Analysis of Patreon revenue and credit card processing fees
|
| 68 |
-
• Concerns about Matrix's funding strategy and transparency
|
| 69 |
-
• Patreon income is not sufficient to cover Matrix's costs
|
| 70 |
-
• Matrix needs a sustainable membership program to support its development and maintenance
|
| 71 |
-
• Running and managing Matrix is a significant cost center for the organization
|
| 72 |
-
• People conflate "free" and "open-source" with "no cost"
|
| 73 |
-
• Development, management, and maintenance of open-source projects have financial and non-financial costs
|
| 74 |
-
• Log4j
|
| 75 |
-
• Shucking Western Digital drives and SATA power connector issues
|
| 76 |
-
• Potential damage to hard drives due to incorrect power supply usage
|
| 77 |
-
• Troubleshooting steps for drive connectivity problems
|
| 78 |
-
• Importance of visual inspection of connectors after shucking drives
|
| 79 |
-
• Using Capton tape to block electrical contact on a drive
|
| 80 |
-
• Comparison of using Capton tape vs cutting the voltage wire
|
| 81 |
-
• Troubleshooting methods for non-functional drives, including testing in different setups and isolating variables
|
| 82 |
-
• Concerns about drives being used in a NAS and not functioning properly after switching between devices
|
| 83 |
-
• Location-based notifications in Home Assistant
|
| 84 |
-
• Using Slack module to send messages to family members
|
| 85 |
-
• Concerns about triggering false notifications on repeated routes
|
| 86 |
-
• NFC tags and their potential uses for home automation
|
| 87 |
-
• Tasker as an alternative to Home Assistant for automation tasks
|
| 88 |
-
• Nix OS integration with Home Assistant and Tasker
|
| 89 |
-
• Successful use of IKEA Trådfri plug to resolve modem disconnection issues
|
| 90 |
-
• User's internet connection kept dropping and they created a home automation script to reset modem power and send notification when it comes back online
|
| 91 |
-
• Similar issue with ESP home devices, user reboots them daily due to memory leak issue
|
| 92 |
-
• Discussion about ntfy.sh (notify.sh) for server notifications and its integration with Graphene OS
|
| 93 |
-
• User is considering self-hosting their notification server and exploring options including Nextcloud integration
|
| 94 |
-
• Self-hosted notification servers and their benefits
|
| 95 |
-
• Anonymous user sends in stats using Albi Umbral setup
|
| 96 |
-
• Boost CLI is praised as a self-hosted setup
|
| 97 |
-
• Upcoming feature: per episode split setup for podcast index.org
|
| 98 |
-
• Future plans to self-host and generate own RSS feed
|
| 99 |
-
• Discussing the benefits of supporting the show, including an ad-free feed and post-show special content
|
| 100 |
-
• Mentioning self-hosted.show/SRE for SRE-related content and jupiter.party for whole network support
|
| 101 |
-
• Hard drive giveaway submission methods (email to Alex at self-hosted.show/contact)
|
| 102 |
-
• Email sob stories submissions and reading them on the show
|
| 103 |
-
• Mastodon presence discussion, with one host discovering they had an account since 2017
|
| 104 |
• Discussing where to find hosts online (Linux Unplugged, Office Hours, Jupyter Broadcasting's Matrix server, Discord)
|
|
|
|
| 1 |
+
• Introduction and welcome of guests
|
| 2 |
+
• Home Assistant SkyConnect dongle review: description, features, and benefits
|
| 3 |
+
• Matter standard updates and potential impact on existing Zigbee networks
|
| 4 |
+
• Discussion of the need for an open smart home platform and Home Assistant's growing mainstream traction
|
| 5 |
+
• Personal anecdotes about family members' interest in Home Assistant and its ease of use
|
| 6 |
+
• Hardware strategy discussion for setting up a Home Assistant system at a distant location
|
| 7 |
+
• Lady Joupes' lithium ion battery bank malfunctioning due to cold temperatures
|
| 8 |
+
• Power outage caused by a series of electrical hits affecting a home's Wi-Fi network
|
| 9 |
+
• Frequent dropouts and losses of Wi-Fi connectivity despite hardware remaining online
|
| 10 |
+
• Decision to replace existing Wi-Fi system with a new TP-Link EAP 245 version 3 unit
|
| 11 |
+
• Comparison of TP-Link and UniFi systems, including self-hosted control centers
|
| 12 |
+
• Troubleshooting efforts to identify cause of Wi-Fi dropouts and losses
|
| 13 |
+
• Discussion of Linus Tech Tips video on Wi-Fi issues caused by Z-Wave devices
|
| 14 |
+
• Use of SDR (Software Defined Radio) for troubleshooting Wi-Fi and radio frequency interference
|
| 15 |
+
• Personal experience with using Android Wi-Fi analyzer tool to improve network performance
|
| 16 |
+
• Description of neighbor's strong printer AP causing interference
|
| 17 |
+
• Plans for a giveaway of a Western Digital 10TB hard drive
|
| 18 |
+
• Promotion of Linode hosting services, including $100 credit offer
|
| 19 |
+
• Supporting the show through Linode
|
| 20 |
+
• Jellyfin January challenge: disabling Plex servers and switching to Jellyfin for a month
|
| 21 |
+
• Raising the profile of Jellyfin and creating a viable alternative to Plex
|
| 22 |
+
• Criticisms of Plex's business model and its impact on users
|
| 23 |
+
• Discussion of cloud connectivity, authentication, and ad-supported media features
|
| 24 |
+
• Concerns about Plex's shift in focus from core streaming functionality to more extensive industry positioning
|
| 25 |
+
• The user is frustrated with Jellyfin's automatic startup behavior
|
| 26 |
+
• Concerns about data ownership and linking to Plex servers
|
| 27 |
+
• Invitation to Brent, a Jellyfin user, to provide feedback on his experience
|
| 28 |
+
• Discussion of the user's past experience with Jellyfin, including setup and potential improvements
|
| 29 |
+
• Review of Jellyfin's GitHub activity, showing 90 PRs accepted in one month and 800 contributors in total
|
| 30 |
+
• Interest in testing the Watch Together feature and reporting back on its performance
|
| 31 |
+
• Ground rules for the challenge, including Plex servers being offline and no switching to other apps during the test period
|
| 32 |
+
• Jellyfin devs mentioned in chat for adding feature requests
|
| 33 |
+
• Audiobook playback and spousal approval discussed as important features
|
| 34 |
+
• Discussion of switching from Prologue to Jellyfin and potential continued use of Plex for audiobooks and music
|
| 35 |
+
• Hardware transcoding issues on Linux server, including Intel GPU and NVIDIA usage
|
| 36 |
+
• Monitoring and metrics, specifically using Tautuli to track streaming activity and device usage
|
| 37 |
+
• Integration of Tautuli with Jellyfin or rewriting Jellyfin server metrics
|
| 38 |
+
• Importance of hardware acceleration and its benefits (e.g. quick sync)
|
| 39 |
+
• Strategies for achieving hardware acceleration (e.g. Linux server IO image, project image, packages)
|
| 40 |
+
• User experience issues with Jellyfin (e.g. skipping intros, subtitles/audio tracks/video quality)
|
| 41 |
+
• Comparison of Jellyfin to Plex and its performance
|
| 42 |
+
• Lack of Apple TV app support and potential limitations
|
| 43 |
+
• Jellyfin's default functionality does not include intro skipping
|
| 44 |
+
• A community plugin can skip intros, but has limitations and is not elegant
|
| 45 |
+
• Native Jellyfin client Swiftfin for iOS and tvOS is under development
|
| 46 |
+
• Hosts plan to test Jellyfin on their servers, including one in England with live TV capabilities
|
| 47 |
+
• Listener Brent has multiple options for running Jellyfin, including Raspberry Pis and a NAS server, and seeks advice from the hosts
|
| 48 |
+
• Discussing the goal of trying Jellyfin media server
|
| 49 |
+
• Comparing the ease of use and administrative burden of Jellyfin versus Plex
|
| 50 |
+
• Considering using a Raspberry Pi with Ubuntu LTS for running Jellyfin, with pros and cons discussed
|
| 51 |
+
• Evaluating the performance and potential issues of running multiple streams on a Raspberry Pi
|
| 52 |
+
• Exploring options for network storage and setup
|
| 53 |
+
• Weighing the decision to use a Raspberry Pi or an x86 system for running Jellyfin
|
| 54 |
+
• Suggesting a two-phased approach to deploying Jellyfin, setting it up first on an x86 box and then transferring to a permanent home
|
| 55 |
+
• Introduction of CrowdStrike Falcon LogScale for log management and observability
|
| 56 |
+
• Description of LogScale's index-free architecture and benefits, including fast search capabilities and lower cost compared to other platforms like Splunk or Elastic
|
| 57 |
+
• Announcement of CrowdStrike.com/LCE as a free trial for LogScale Community Edition with up to 16 GB/day ingestion and 7 days retention
|
| 58 |
+
• Discussion of the Matrix Project's financial struggles, including layoffs of core team members and funding issues due to lost value in tech stocks
|
| 59 |
+
• Support for the Matrix project and community
|
| 60 |
+
• Financial contributions to the Matrix Foundation
|
| 61 |
+
• Criticism of the foundation's approach to fundraising and sustainability
|
| 62 |
+
• Comparison with other projects, such as Linux
|
| 63 |
+
• Ambitious goals and scalability challenges for Matrix
|
| 64 |
+
• Personal opinion on the effectiveness of current methods
|
| 65 |
+
• Discussion of Matrix's goals and relevance in the market
|
| 66 |
+
• Comparison to Linux Foundation and its business model
|
| 67 |
+
• Analysis of Patreon revenue and credit card processing fees
|
| 68 |
+
• Concerns about Matrix's funding strategy and transparency
|
| 69 |
+
• Patreon income is not sufficient to cover Matrix's costs
|
| 70 |
+
• Matrix needs a sustainable membership program to support its development and maintenance
|
| 71 |
+
• Running and managing Matrix is a significant cost center for the organization
|
| 72 |
+
• People conflate "free" and "open-source" with "no cost"
|
| 73 |
+
• Development, management, and maintenance of open-source projects have financial and non-financial costs
|
| 74 |
+
• Log4j
|
| 75 |
+
• Shucking Western Digital drives and SATA power connector issues
|
| 76 |
+
• Potential damage to hard drives due to incorrect power supply usage
|
| 77 |
+
• Troubleshooting steps for drive connectivity problems
|
| 78 |
+
• Importance of visual inspection of connectors after shucking drives
|
| 79 |
+
• Using Capton tape to block electrical contact on a drive
|
| 80 |
+
• Comparison of using Capton tape vs cutting the voltage wire
|
| 81 |
+
• Troubleshooting methods for non-functional drives, including testing in different setups and isolating variables
|
| 82 |
+
• Concerns about drives being used in a NAS and not functioning properly after switching between devices
|
| 83 |
+
• Location-based notifications in Home Assistant
|
| 84 |
+
• Using Slack module to send messages to family members
|
| 85 |
+
• Concerns about triggering false notifications on repeated routes
|
| 86 |
+
• NFC tags and their potential uses for home automation
|
| 87 |
+
• Tasker as an alternative to Home Assistant for automation tasks
|
| 88 |
+
• Nix OS integration with Home Assistant and Tasker
|
| 89 |
+
• Successful use of IKEA Trådfri plug to resolve modem disconnection issues
|
| 90 |
+
• User's internet connection kept dropping and they created a home automation script to reset modem power and send notification when it comes back online
|
| 91 |
+
• Similar issue with ESP home devices, user reboots them daily due to memory leak issue
|
| 92 |
+
• Discussion about ntfy.sh (notify.sh) for server notifications and its integration with Graphene OS
|
| 93 |
+
• User is considering self-hosting their notification server and exploring options including Nextcloud integration
|
| 94 |
+
• Self-hosted notification servers and their benefits
|
| 95 |
+
• Anonymous user sends in stats using Albi Umbral setup
|
| 96 |
+
• Boost CLI is praised as a self-hosted setup
|
| 97 |
+
• Upcoming feature: per episode split setup for podcast index.org
|
| 98 |
+
• Future plans to self-host and generate own RSS feed
|
| 99 |
+
• Discussing the benefits of supporting the show, including an ad-free feed and post-show special content
|
| 100 |
+
• Mentioning self-hosted.show/SRE for SRE-related content and jupiter.party for whole network support
|
| 101 |
+
• Hard drive giveaway submission methods (email to Alex at self-hosted.show/contact)
|
| 102 |
+
• Email sob stories submissions and reading them on the show
|
| 103 |
+
• Mastodon presence discussion, with one host discovering they had an account since 2017
|
| 104 |
• Discussing where to find hosts online (Linux Unplugged, Office Hours, Jupyter Broadcasting's Matrix server, Discord)
|