| • Welcome back to a show after a holiday break
|
| • Discussion of game Anno 1800 and its gameplay mechanics
|
| • Mention of a possible follow-up on Linux Unplugged predictions episode
|
| • 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
|
| • Discussion of the cost of new graphics cards (3080) and used storage drives
|
| • Discussing hard drive reliability and potential failures
|
| • Considering alternative backup solutions, including shipping drives to an off-site location
|
| • Mention of the possibility of a catastrophic event (nuclear attack) and its potential impact on data storage and backup systems
|
| • Discussion of off-site backups and decentralizing data storage
|
| • Prediction of a 20 terabyte easy store for $250 or less
|
| • Alex's possible success rate with his project being 0%
|
| • Concerns about diminishing returns with hard drive capacity
|
| • Physical limitations of hard drives and innovations in the field
|
| • Discussion of HomeKit and its capabilities
|
| • Integration of HomeKit with Siri, Apple TV remote, and Shortcuts app
|
| • Ecosystem limitations as a "sandbox" with walls
|
| • Seamless control experience through iOS devices
|
| • Compatibility with non-HomeKit devices (e.g., LG TV)
|
| • Robustness of HomeKit security features, including encryption and partnership with Matter
|
| • Integration with Home Assistant for expanded capabilities
|
| • HomeBridge was used to connect non-HomeKit devices to Apple's HomeKit
|
| • LG TVs were controlled using this bridge before official HomeKit support
|
| • The bridge translates proprietary device protocols to HomeKit format
|
| • HomeBridge is no longer necessary for most users since LG added HomeKit support
|
| • It can still be useful for controlling non-HomeKit compatible devices
|
| • Linode is mentioned as a cloud hosting service and sponsor of the podcast
|
| • Linking Home Assistant with HomeKit
|
| • Connecting non-HomeKit devices to HomeKit through integration
|
| • Adding camera feeds and automations as HomeKit devices
|
| • Importing existing HomeKit devices into Home Assistant
|
| • Setting up a central hub for family devices to access and control shared devices
|
| • Integration of smart devices with HomeKit
|
| • Apple TV as a hub for HomeKit integration
|
| • Issues with certain device types (e.g. robot vacuum) and their integration
|
| • Curation process to disable unnecessary devices in HomeKit
|
| • Comparison between HomeKit and other smart home platforms (e.g. Home Assistant)
|
| • Philips Hue ecosystem and its replacement with Zigbee bridge and buttons
|
| • Integration of HomeKit with Home Assistant
|
| • Use of Siri as voice control for home automation
|
| • Comparison with Google and Amazon services
|
| • Apple's LAN-based protocol vs cloud-based API
|
| • Nebu Casa cloud service and its limitations
|
| • HomeKit integration bypassing need for complicated setup
|
| • Easy setup and use of HomeKit devices with Siri
|
| • The speaker is looking to acquire a mini DV camcorder at a cost lower than $150
|
| • They are also seeking suggestions on how to digitize the tapes properly
|
| • Tailscale VPN service is recommended, which allows secure network connections between devices and provides features such as multi-factor authentication and stable IP addresses
|
| • Tailscale offers support for up to 20 machines
|
| • NVIDIA Shield has been updated to Android TV 11 with a Stadia button
|
| • Update does not eliminate ads from interface
|
| • User experiences buffering issue while watching Deadwood on NVIDIA Shield due to Plex transcoding audio codec
|
| • Discussion of differences in hardware capabilities between NVIDIA Shield and Apple TV
|
| • Discussion of the Nintendo Switch and NVIDIA devices
|
| • Comparison of Apple TV to NVIDIA Shield
|
| • Use cases for a media streaming device, including iPlayer and Kodi
|
| • Concerns about getting WireGuard VPN to work on an Apple TV
|
| • Difficulty replicating certain features or settings on the Apple TV compared to other devices
|
| • Discussion of video player software for Apple TV
|
| • Comparison of Plex and Jellyfin on Apple TV
|
| • Use of WireGuard VPN with Apple TV
|
| • Rooting the Apple TV and installing third-party apps
|
| • Kodi vs Infuse as a set-top interface for video playback
|
| • Infuse's features, including codec support and syncing capabilities
|
| • Development teams behind Plex and Infuse
|
| • XBMC (Kodi) on a PlayStation 3
|
| • DLP televisions and their technology
|
| • Nostalgia for old tech and software design
|
| • Review of Kodi's evolution and comparison to other media players like Plex
|
| • Features of Kodi, including video playback engine and blur effect for spoilers
|
| • Installing Kodi on Mac and Apple TV with iCloud sync settings
|
| • Comparison of media server devices
|
| • Discussion of Jellyfin's performance and features
|
| • Brent's personal experience with Jellyfin and its impact on his household setup
|
| • Comparison between Jellyfin and Plex as a media server software
|
| • The advantages of using Jellyfin for centralized media management
|
| • The speaker is using Jellyfin on their Android phone to browse and stream media content to their TV
|
| • They experience occasional connection drops and glitches with Jellyfin compared to Plex
|
| • This leads the speaker to consider alternative solutions, such as a set-top box with a dedicated client
|
| • Apple TV and Infuse are mentioned as an alternative solution that provides a more stable streaming experience
|
| • The speaker is excited about exploring Docker and its potential for opening up new possibilities for app development and deployment
|
| • The speaker was initially frustrated with the blurring of lines between application and data on a home server.
|
| • They found that using containers (specifically Docker) provided a solid way to separate applications from data.
|
| • Containers allow for easy recreation of an environment, making disaster recovery simpler and easier to manage.
|
| • The speaker's experience with troubleshooting a container failure had an "aha moment" where they realized the power of recreating a container from scratch.
|
| • The speaker is interested in using containers, particularly Docker and Docker Compose
|
| • They have questions about troubleshooting and interacting with containers
|
| • The importance of understanding that each container has its own contained environment
|
| • Docker Compose as a tool for launching apps and viewing logs
|
| • Accessing logs is key to understanding what's happening within a container
|
| • The benefits and usage of a command that prints the last 50 lines of a container's standard output
|
| • Challenges with container logs, including some applications not logging by default
|
| • Ways to troubleshoot and increase log verbosity for problematic containers
|
| • Introduction to Dozzle, a tool for viewing container logs in a browser
|
| • Upcoming meetup at the studio on January 30th and promotion of new network membership
|
| • Apologies for not being able to attend a birthday party in person
|
| • Scheduling issues due to weather conditions (frozen tundra vs warm location)
|
| • Discussion of Seattle's rough winters
|
| • Invitation for feedback on content ideas, apps, and self-hosted projects |
