| • The narrator experiences a hardware failure with their Raspberry Pi home server, which runs multiple instances including Home Assistant.
|
| • 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.
|
| • The failed device controls many automations in the RV, causing inconvenience for the users.
|
| • The narrator considers using a dedicated hardware device for Home Assistant instead of the Raspberry Pi.
|
| • Discussion about the Home Assistant Yellow device and its expected delivery date
|
| • Power and heat considerations for the device
|
| • Comparison to a potential x86 system with BMC chip
|
| • Issues with Raspberry Pi availability due to industrial demand
|
| • Concerns about Home Assistant shipping devices after long delays and possible lack of future stock
|
| • Suggested alternative payment methods, similar to Valve's queue system
|
| • The Raspberry Pi Foundation's product has become incredibly popular and ubiquitous
|
| • Broadcom is reportedly unhappy with the foundation due to their plans to commercialize the product
|
| • This may lead to slower supply from Broadcom and changed licensing rates for the company
|
| • The M1 platform from Apple could be a worthy successor for home labbers, especially if it gains decent Linux support
|
| • Current limitations in macOS Server and Docker Desktop on Mac are mentioned as issues to be addressed
|
| • Discussion around choosing an M1 chip or other options for a computer system
|
| • Concerns about power consumption and space limitations in the RV environment
|
| • Consideration of building a custom x86 box with hosting capabilities
|
| • Decentralization and portability as desirable features
|
| • Mention of Intel NUC and tiny mini micro computers as alternatives
|
| • Discussion of video decoding requirements, including QuickSync support and transcoding options
|
| • Use of pre-encoding tools like TDAR or Handbrake to bypass transcoding requirements
|
| • Storage needs, with a preference for 4 terabytes in the Joops environment
|
| • Discussing current TV show season on a streaming device
|
| • Researching affordable SSD options for data storage
|
| • Exploring the idea of using low-cost Leven SSDs in a RAID configuration
|
| • Describing a modular approach to building and maintaining a media server setup
|
| • Brainstorming ideas for a custom-built studio setup with mixing board, storage, and production capacity
|
| • Matter's stability is uncertain
|
| • Home Assistant is going all-in on Zigbee
|
| • They've hired a Z-Wave integration specialist, causing mixed messages about their direction
|
| • It seems they'll support multiple protocols, but it's unclear how well each will be supported
|
| • The user is considering whether to invest in Zigbee or Z-Wave devices
|
| • Linode services mentioned as reliable and cost-effective compared to hyperscalers
|
| • Multiple data centers available globally, with more coming soon
|
| • Performance and support balance makes Linode a recommended choice
|
| • $100 offer for users to try Linode
|
| • Invoice Ninja app discussed for creating customisable invoices and quotes
|
| • Using Invoice Ninja software for freelance work
|
| • Creating customers and products in the software
|
| • Generating invoices based on customer and product information
|
| • Sending invoices via email through the software (optional)
|
| • Self-hosting options for the software
|
| • User's experience with the software over two years
|
| • The speaker is using a self-hosted invoicing system on their server.
|
| • The system requires three containers: app, database (using MySQL), and front-end (using Nginx).
|
| • The speaker likes the user interface and features of the system, including a chart that displays pending invoices.
|
| • The system is useful for those who send many invoices daily, but still provides benefits to users with lower invoice volumes.
|
| • The speaker appreciates the ability to tweak settings and customize the system's functionality.
|
| • The pricing of hosted invoicing services can be expensive, with some options costing around $50-60 per month.
|
| • The self-hosted system offers cost savings compared to traditional invoicing solutions like QuickBooks.
|
| • Invoicing capabilities, including quotes and proposals
|
| • Ability to track different vendors and manage transactions
|
| • Reporting features for tracking invoices and financial data
|
| • Comparison with other invoicing software, such as Invoice Plane
|
| • User's experience switching from a Google sheet to Invoice Ninja
|
| • Difficulty in extracting data from software
|
| • Importing and exporting database options
|
| • CSV export as a viable solution for invoicing
|
| • Catherine's experience with the software
|
| • Import options, including CSV, JSON, XLS, and others
|
| • What are YubiKeys
|
| • How they work for 2-factor authentication
|
| • Benefits of using a YubiKey (e.g., security, no need to store secrets online)
|
| • Disadvantages of using a YubiKey (e.g., physical access required, inconvenient placement in the house)
|
| • Two-factor authentication and security keys
|
| • YubiKey promotion by Cloudflare for affordable pricing
|
| • Discussion of the benefits and usefulness of YubiKeys in workplaces
|
| • Cloudflare's offer to provide security keys at discounted prices
|
| • Personal anecdotes about using YubiKeys and their accessibility on various devices
|
| • Discussion of trying out a $10 entry price for NFC devices
|
| • Comparison of different features and methods of authentication (FIDO)
|
| • Complexity and difficulty of choosing the right authenticator
|
| • Recent advancements in simplifying authentication processes
|
| • Debate about the best approach: hardware device vs. software app
|
| • Potential benefits of combining two-factor code with a hardware device
|
| • The speaker has shared a password on GitHub and acknowledges it was not the best decision.
|
| • 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.
|
| • 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.
|
| • 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.
|
| • Discussion of a hypothetical feature where everything read on Reddit automatically goes to Pocket
|
| • Comparison with other services and desire for similar functionality
|
| • Introduction to RSS and Bitwarden features, including email aliasing with FastMail integration
|
| • Explanation of how the FastMail integration allows users to create genuine email aliases instead of semi-obfuscated addresses
|
| • Discussion of password management and unique email addresses for each service
|
| • Thoughts on bridging the gap between advanced security practices and everyday user behavior
|
| • Discussion of whether NetBird is a suitable alternative to TailScale
|
| • Analysis of NetBird's features and how they compare to TailScale
|
| • Mention of the proliferation of VPN solutions based on WireGuard
|
| • Prediction that there will be multiple options for users, with some possibly being more popular than others
|
| • Tail Scale and subnet routing
|
| • Using Tail Scale with non-PC devices (e.g. Victron solar equipment)
|
| • Setting up subnet routing at different locations (e.g. Airbnb, home)
|
| • Pulse Audio Network Streaming as an alternative for whole-home audio
|
| • Comparison of Netbird and Tail Scale
|
| • Plan to discuss subnet routing in a future episode
|
| • Discussion of audio streaming solutions, including PulseAudio and Volumio
|
| • Recommendation of Rune Audio as a paid solution for multiple-room music streaming
|
| • Troubles with IR blaster reliability and potential alternatives using ESP devices
|
| • Intersection of hardware and software in home entertainment systems
|
| • Request for tips on content request systems for music
|
| • Discussion of reliable smart switches, specifically the Z-Wave 700 series
|
| • Discussion of a favorite radio frequency (900 megahertz)
|
| • Smart home setup and recommendations for Zigbee router
|
| • Comparison of two Zigbee gateways, Con Be 2 and Zalish Zigbee 3.0 stick
|
| • Coupon code offered by Cloudfree.shop
|
| • Alex's Proxmox and Docker setup on a server
|
| • Documentation for setting up similar server configuration available at perfectmediaserver.com
|
| • Discussion of a Proxmox setup, including how it's used and its simplicity
|
| • Overview of setting up Proxmox on Debian, with options for direct installation or installing Debian first
|
| • Mention of John's decision to set up his own email server after listening to the last episode
|
| • Comments from listeners who have also set up their own email servers, including one using Comcast
|
| • Discussion of new podcast apps, specifically Podverse and Calyx, and a mention of Graphene
|
| • Alternatives to popular podcast apps
|
| • Alby as an option for web-based podcast listening
|
| • Office Hours' recent episode and their trip to JPL
|
| • The Europa Clipper mission and live cam stream on YouTube
|
| • Linux Unplugged's audience and meetup experience
|
| • A guest from JPL bringing a prototype computer from the Mars copter
|
| • Gratitude expressed to Tim, JB, and Linode for support
|
| • Discussion of swag distribution at JPL meetups
|
| • Thanks to members who make the show possible
|
| • Promotion of self-hosted.show's site reliability engineers and ad-free version
|
| • Announcement of final meetup and future meetups
|
| • Mention of attending All Things Open in Raleigh |
