text stringlengths 7 369 |
|---|
• Hardware strategy discussion for setting up a Home Assistant system at a distant location |
• Lady Joupes' lithium ion battery bank malfunctioning due to cold temperatures |
• Power outage caused by a series of electrical hits affecting a home's Wi-Fi network |
• Frequent dropouts and losses of Wi-Fi connectivity despite hardware remaining online |
• Decision to replace existing Wi-Fi system with a new TP-Link EAP 245 version 3 unit |
• Comparison of TP-Link and UniFi systems, including self-hosted control centers |
• Troubleshooting efforts to identify cause of Wi-Fi dropouts and losses |
• Discussion of Linus Tech Tips video on Wi-Fi issues caused by Z-Wave devices |
• Use of SDR (Software Defined Radio) for troubleshooting Wi-Fi and radio frequency interference |
• Personal experience with using Android Wi-Fi analyzer tool to improve network performance |
• Description of neighbor's strong printer AP causing interference |
• Plans for a giveaway of a Western Digital 10TB hard drive |
• Promotion of Linode hosting services, including $100 credit offer |
• Supporting the show through Linode |
• Jellyfin January challenge: disabling Plex servers and switching to Jellyfin for a month |
• Raising the profile of Jellyfin and creating a viable alternative to Plex |
• Criticisms of Plex's business model and its impact on users |
• Discussion of cloud connectivity, authentication, and ad-supported media features |
• Concerns about Plex's shift in focus from core streaming functionality to more extensive industry positioning |
• The user is frustrated with Jellyfin's automatic startup behavior |
• Concerns about data ownership and linking to Plex servers |
• Invitation to Brent, a Jellyfin user, to provide feedback on his experience |
• Discussion of the user's past experience with Jellyfin, including setup and potential improvements |
• Review of Jellyfin's GitHub activity, showing 90 PRs accepted in one month and 800 contributors in total |
• Interest in testing the Watch Together feature and reporting back on its performance |
• Ground rules for the challenge, including Plex servers being offline and no switching to other apps during the test period |
• Jellyfin devs mentioned in chat for adding feature requests |
• Audiobook playback and spousal approval discussed as important features |
• Discussion of switching from Prologue to Jellyfin and potential continued use of Plex for audiobooks and music |
• Hardware transcoding issues on Linux server, including Intel GPU and NVIDIA usage |
• Monitoring and metrics, specifically using Tautuli to track streaming activity and device usage |
• Integration of Tautuli with Jellyfin or rewriting Jellyfin server metrics |
• Importance of hardware acceleration and its benefits (e.g. quick sync) |
• Strategies for achieving hardware acceleration (e.g. Linux server IO image, project image, packages) |
• User experience issues with Jellyfin (e.g. skipping intros, subtitles/audio tracks/video quality) |
• Comparison of Jellyfin to Plex and its performance |
• Lack of Apple TV app support and potential limitations |
• Jellyfin's default functionality does not include intro skipping |
• A community plugin can skip intros, but has limitations and is not elegant |
• Native Jellyfin client Swiftfin for iOS and tvOS is under development |
• Hosts plan to test Jellyfin on their servers, including one in England with live TV capabilities |
• Listener Brent has multiple options for running Jellyfin, including Raspberry Pis and a NAS server, and seeks advice from the hosts |
• Discussing the goal of trying Jellyfin media server |
• Comparing the ease of use and administrative burden of Jellyfin versus Plex |
• Considering using a Raspberry Pi with Ubuntu LTS for running Jellyfin, with pros and cons discussed |
• Evaluating the performance and potential issues of running multiple streams on a Raspberry Pi |
• Exploring options for network storage and setup |
• Weighing the decision to use a Raspberry Pi or an x86 system for running Jellyfin |
• Suggesting a two-phased approach to deploying Jellyfin, setting it up first on an x86 box and then transferring to a permanent home |
• Introduction of CrowdStrike Falcon LogScale for log management and observability |
• Description of LogScale's index-free architecture and benefits, including fast search capabilities and lower cost compared to other platforms like Splunk or Elastic |
• Announcement of CrowdStrike.com/LCE as a free trial for LogScale Community Edition with up to 16 GB/day ingestion and 7 days retention |
• Discussion of the Matrix Project's financial struggles, including layoffs of core team members and funding issues due to lost value in tech stocks |
• Support for the Matrix project and community |
• Financial contributions to the Matrix Foundation |
• Criticism of the foundation's approach to fundraising and sustainability |
• Comparison with other projects, such as Linux |
• Ambitious goals and scalability challenges for Matrix |
• Personal opinion on the effectiveness of current methods |
• Discussion of Matrix's goals and relevance in the market |
• Comparison to Linux Foundation and its business model |
• Analysis of Patreon revenue and credit card processing fees |
• Concerns about Matrix's funding strategy and transparency |
• Patreon income is not sufficient to cover Matrix's costs |
• Matrix needs a sustainable membership program to support its development and maintenance |
• Running and managing Matrix is a significant cost center for the organization |
• People conflate "free" and "open-source" with "no cost" |
• Development, management, and maintenance of open-source projects have financial and non-financial costs |
• Log4j |
• Shucking Western Digital drives and SATA power connector issues |
• Potential damage to hard drives due to incorrect power supply usage |
• Troubleshooting steps for drive connectivity problems |
• Importance of visual inspection of connectors after shucking drives |
• Using Capton tape to block electrical contact on a drive |
• Comparison of using Capton tape vs cutting the voltage wire |
• Troubleshooting methods for non-functional drives, including testing in different setups and isolating variables |
• Concerns about drives being used in a NAS and not functioning properly after switching between devices |
• Location-based notifications in Home Assistant |
• Using Slack module to send messages to family members |
• Concerns about triggering false notifications on repeated routes |
• NFC tags and their potential uses for home automation |
• Tasker as an alternative to Home Assistant for automation tasks |
• Nix OS integration with Home Assistant and Tasker |
• Successful use of IKEA Trådfri plug to resolve modem disconnection issues |
• 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 |
• Similar issue with ESP home devices, user reboots them daily due to memory leak issue |
• Discussion about ntfy.sh (notify.sh) for server notifications and its integration with Graphene OS |
• User is considering self-hosting their notification server and exploring options including Nextcloud integration |
• Self-hosted notification servers and their benefits |
• Anonymous user sends in stats using Albi Umbral setup |
• Boost CLI is praised as a self-hosted setup |
• Upcoming feature: per episode split setup for podcast index.org |
• Future plans to self-host and generate own RSS feed |
• Discussing the benefits of supporting the show, including an ad-free feed and post-show special content |
• Mentioning self-hosted.show/SRE for SRE-related content and jupiter.party for whole network support |
• Hard drive giveaway submission methods (email to Alex at self-hosted.show/contact) |
• Email sob stories submissions and reading them on the show |
• Mastodon presence discussion, with one host discovering they had an account since 2017 |
• Discussing where to find hosts online (Linux Unplugged, Office Hours, Jupyter Broadcasting's Matrix server, Discord) |
[0.00 --> 5.54] It's episode 87 of the show, and this is going to be a fun one because we have a challenge that we're about to get into. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.