text stringlengths 9 408 |
|---|
[2015.52 --> 2017.84] So I don't know, maybe next house. |
[2018.24 --> 2019.48] I'll give it a whirl. |
[2019.84 --> 2022.24] I'm going to keep it in my back pocket for a future project. |
[2022.34 --> 2024.12] And it has a cool acronym too. |
[2024.54 --> 2024.84] Mocha. |
[2025.28 --> 2026.02] M-O-C-A. |
[2026.34 --> 2026.62] Mocha. |
[2026.92 --> 2027.88] Mo-C-A-C-E-N-O. |
[2027.88 --> 2028.18] Mocha. |
[2028.18 --> 2029.24] So I kind of like it already. |
[2029.46 --> 2030.08] Sounds delicious. |
[2030.30 --> 2030.52] Mocha. |
[2030.70 --> 2035.06] If the reports from the email are true, it's like if they say it's a gigabit, it's a true gigabit. |
[2035.14 --> 2036.12] It's actually that fast. |
[2036.62 --> 2037.06] Mocha. |
[2037.06 --> 2037.18] Mocha. |
[2037.18 --> 2037.46] Mocha. |
[2037.46 --> 2037.54] Mocha. |
[2037.54 --> 2037.82] Mocha. |
[2037.94 --> 2038.00] Mocha. |
[2038.00 --> 2038.12] Mocha. |
[2038.12 --> 2038.26] Mocha. |
[2038.26 --> 2039.14] Mocha. |
[2039.14 --> 2040.22] Mocha. |
[2040.22 --> 2041.30] Mocha. |
[2041.30 --> 2042.08] Mocha. |
[2042.08 --> 2042.38] Mocha. |
[2042.38 --> 2042.46] Mocha. |
[2042.46 --> 2042.64] Mocha. |
[2042.64 --> 2043.32] Mocha. |
[2043.32 --> 2044.48] Mocha. |
[2044.48 --> 2047.00] our site reliability engineers who support the show. |
[2047.32 --> 2048.50] They keep us independent. |
[2048.74 --> 2051.28] They get a limited ad feed available to them as a member, |
[2051.48 --> 2053.76] and they get a little bit of extra content, a post-show. |
[2054.18 --> 2056.38] So if you'd like to support the show and become a member, |
[2056.52 --> 2058.72] go to selfhosted.show slash SRE. |
[2059.08 --> 2062.00] Yes, big thank you to our site reliability engineers. |
[2062.30 --> 2066.18] You can go to selfhosted.show slash contact to get in touch with us, |
[2066.26 --> 2068.56] and you can find me on Twitter at Ironic Badger. |
[2068.78 --> 2069.32] I'm there too. |
[2069.44 --> 2074.04] I'm at Chris LAS, and the show is at selfhostedshow. |
[2074.04 --> 2076.52] Don't forget at Jupitersignal for the network. |
[2076.90 --> 2077.54] Thanks for listening. |
[2077.78 --> 2080.00] That was selfhosted.show slash 36. |
• Home Assistant Security Bulletin: discussion of its handling and lack of clear information from the project |
• Update on the show's first anniversary and future plans |
• Discussion of milestones for podcast success (episode 300) and celebration |
• Brief review of the show's growth and reception over its first year |
• Upcoming schedule and potential changes to release frequency |
• High standards for platform security and communication |
• Importance of clear communication in resolving security issues |
• Reliability of vendor-supported OS vs project-controlled stack |
• Challenges of building a comprehensive home automation platform |
• Need for delegation of complex tasks to specialized vendors |
• Home Assistant update process and potential issues with custom integrations |
• The speaker experiences issues with the update process in Home Assistant |
• Problems are resolved after a reboot and running the update again |
• Issues with config checker and custom integration explained |
• Discussion of using Home Assistant on an RV's Internet connection |
• Speaker shares experience with using Home Assistant's snapshot feature to back up data |
• Discussion of using Google Drive backup plugin for automated snapshots |
• The speaker discusses their use of Linode as a server provider, mentioning its ease of use and customer support. |
• They explain that Linode offers one-click deployments for applications like Minecraft and CSGO servers, making it simple to set up private gaming spaces. |
• The speaker also talks about Linode's human-powered customer support and its history as an independently owned company founded in 2003. |
• They share their experience using Linode's services for their own infrastructure and personal projects, including experimenting with different WordPress stacks. |
• The conversation shifts to the topic of building versus buying solutions, with the speaker sharing a personal anecdote about regretting building a solution that could have been purchased more affordably. |
• Finally, they showcase a small Bluetooth temperature sensor from Xiaomi, discussing its features and potential uses in home automation projects. |
• Temperature sensors and display |
• ESP32 devices for temperature monitoring |
• Web configurator tool for flashing firmware |
• Automating thermostats using Home Assistant |
• Generic thermostat component in Home Assistant |
• Smart thermostat integration issues |
• Difficulty with thermostat settings and heat distribution in specific room |
• Desire to use a sensor to monitor temperature and adjust heating accordingly |
• Interest in automation that turns off heating when a certain threshold is reached |
• Consideration of energy efficiency and potential for future development |
• Discussion of solar power options, including Tesla Powerwall and Tractor Supply |
• Research process for installing solar panels, including reading reviews and seeking advice from online communities |
• Listener Phil asks about protecting backups from ransomware and accidental mass deletion |
• Host discusses using ZFS for backups, including snapshot support and data set encryption |
• Host explains his backup strategy, which includes hourly, daily, weekly, monthly, and annual snapshots |
• Host mentions potential issue of ransomware requiring execution to affect the system |
• Discussion turns to backup solution for a NAS (Network-Attached Storage) device, and the challenge of backing up large amounts of data (15 terabytes) |
• Host shares personal experience with losing access to media due to DVDs/Blu-rays becoming obsolete and online availability issues |
• Plans to sync a large amount of data locally and then offsite via personal setup |
• Discussion of backup solutions, including using Google Drive and duplicati for encryption and multi-cloud storage |
• Concerns about relying on Google services due to changes in terms and API access revocation |
• Alternative solutions like cloudfree.shop devices that are pre-configured for local network use without cloud connections |
• NFC automation tricks and using NFC tags for tasks like D&D and turning on lights |
• Android users' workaround for using NFC tags on iOS |
• Using HomeKit to integrate with Home Assistant for automation |
• Two workarounds for avoiding notification confirmation when using NFC tags: Billy's method and Quinton Ronan's web hook solution |
• Discussion of preparing a setup to be accessible by others in case of absence or incapacitation |
• The speaker is considering transitioning from LastPass to another password manager like Bitwarden |
• They need a solution that allows for different logins with separate credentials, especially for sharing with their wife and others |
• The speaker questions whether their family would be able to maintain the current setup if they were no longer around |
• They discuss the importance of documentation and making systems accessible to others |
• The conversation touches on the concept of "craftsmanship" in setting up technical solutions and leaving a legacy for others |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.