Urgent.News

What's breaking now, across thousands of outlets.

Tech

Podcast, episode 1: The green check lies — backups, networking, self-hosting and a turtle

Three AI hosts, real homelab answers. The first episode of the Homelab the Right Way Podcast is out: Ep. 1: The green check lies — backups, networking, self-hosting and a turtle (46 minutes, published October 18, 2026, free). Disclosure first: Maya, Sam and Theo are fictional AI hosts. Their voices are AI-generated, the script was written with AI help and edited by a human, and every fact comes…

The Homelab the Right Way Podcast released its inaugural episode on October 18, 2026. Hosted by AI-generated voices Maya, Sam, and Theo, the show dives into practical homelab tips from the Homelab the Right Way books and blog. The 46-minute episode explores critical topics in home lab management, without relying on any actual hosts or real-life experiences.

The first segment, titled "Backups: The green check lies," debunks the misconception that a single green checkmark on a Proxmox backup job guarantees its reliability. Listeners learn about the 3-2-1 backup strategy, the importance of keep-daily=7, and the pitfalls of backup jobs that overlook newly created VMs. The episode also highlights the significance of restoration drills to verify the effectiveness of backups.

Storage solutions are dissected next, revealing that RAID does not serve as a backup by itself. The episode explains why an NFS share can consume the entire root disk and showcases sanoid + syncoid pull replication for ZFS as a more robust alternative.

Networking fundamentals take center stage, unpacking the meaning of a /24 subnet mask and addressing the issue of Proxmox clusters freezing. The QDevice fix is presented as a potential solution. Additionally, the episode explains what a /24 subnet mask actually represents and why a 2-node Proxmox cluster may freeze, alongside the implementation of the QDevice fix.

Self-hosting platforms like Immich, Nextcloud, and Vaultwarden are scrutinized, emphasizing the potential complications and offering guidance on managing these services effectively. The discussion extends to Home Assistant, touching on the motion light that unexpectedly turns off and how a Zigbee fix can surpass any existing settings.

The episode concludes with a cautionary tale about the ESP32 wire that can damage the board, alongside the precise readings obtained from a DS18B20 sensor that accurately measure temperatures.

Listeners can tune in to the full episode via the episode page on RedCircle, the show's dedicated website, or their preferred podcast platform. The Homelab the Right Way show notes, chapters, and all referenced articles are available on the Chartmann1590 GitHub repository. The episode features the TP-Link TL-SG105 5-port gigabit switch and the Kasa Smart Plug Ultra Mini EP10, with affiliate links available in the show notes.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

'Human Vs. Robot' Cage Match Was Illegal, Says California

"A human defeated two of the three robots he faced in a cage fight recently held in San Francisco," reports the Los Angeles Times, noting that videos of the event drew more than 10 million views on…

  • Frankie LaPenna defeated three humanoid robots in San Francisco
  • Event garnered over 10 million YouTube views
  • California bans human vs. robot combat sports

Powered by beehiiv

  • beehiiv simplifies newsletter creation and monetization.
  • Users can launch newsletters with no cost or credit card.
  • Success stories show rapid subscriber growth and acquisitions.

Property Import Rollbacks with a Node.js Feature Flag Kill Switch

TL;DR: Put the kill decision in a small server-side gate, cache the last valid flag snapshot, and make the fallback disable the new import path.

  • Implement kill switch using feature flag in Node.js backend property import system
  • Cache last valid flag snapshot and have fallback mechanism disabling new import path
  • Monitor progress of scheduled import with run ID, watermark, counts, completion time

The Provenance Layer — Or, You Can't Audit What You Can't Rebuild

Yesterday was the solvency layer (#63): the vendor holding your switch can run out of money. Today's front page answers the next question down — how do you know what the thing on your machine actually…

  • Provenance Layer addresses authenticity of software dependencies
  • Most dependencies cannot be rebuilt from public inputs
  • Implement provenance by pinning dependencies by digest and using lockfiles

More from Monday 19 October →