text stringlengths 9 408 |
|---|
[2877.02 --> 2877.54] That's a good idea. |
[2877.88 --> 2878.20] Goals, |
[2878.30 --> 2878.50] Alex. |
[2878.80 --> 2879.12] Goal. |
[2880.06 --> 2880.28] All right. |
[2880.30 --> 2880.40] Now, |
[2880.42 --> 2880.92] if you want to send |
[2880.92 --> 2881.70] us in your feedback, |
[2881.82 --> 2882.14] you can go to |
[2882.14 --> 2883.02] self-hosted.show |
[2883.02 --> 2883.68] slash contact. |
[2883.84 --> 2884.36] That's the place to |
[2884.36 --> 2884.98] go to get in touch |
[2884.98 --> 2885.28] with us. |
[2885.52 --> 2886.22] And as always, |
[2886.34 --> 2887.06] you can find me on |
[2887.06 --> 2887.58] Twitter at |
[2887.58 --> 2888.42] ironic badger. |
[2888.88 --> 2889.60] There you go. |
[2889.96 --> 2890.98] I'm at Chris LAS |
[2890.98 --> 2891.38] on there. |
[2891.46 --> 2892.46] The podcast itself, |
[2892.54 --> 2892.94] that's at |
[2892.94 --> 2894.60] self-hosted show. |
[2894.68 --> 2895.02] What is it? |
[2895.06 --> 2895.42] I don't know. |
[2895.48 --> 2896.28] I can barely say it. |
[2896.52 --> 2897.16] I'm kind of feeling |
[2897.16 --> 2897.68] like I'm done |
[2897.68 --> 2898.34] plugging the Twitter. |
[2898.42 --> 2899.22] Now that Jack's out, |
[2899.28 --> 2899.76] I feel like we |
[2899.76 --> 2900.24] should be out, |
[2900.34 --> 2900.56] Alex. |
[2903.06 --> 2903.50] All right, |
[2903.52 --> 2903.76] everybody. |
[2903.90 --> 2904.48] Thanks for listening |
[2904.48 --> 2905.12] and not going on |
[2905.12 --> 2905.34] Twitter. |
[2905.52 --> 2905.78] That was |
[2905.78 --> 2906.74] self-hosted.show |
[2906.74 --> 2907.70] slash 59. |
• Congratulatory tone towards Sir Lewis Hamilton's eighth World Drivers title |
• Criticism of Formula One management for "shenanigans" and "corrupt" behavior |
• Discussion of Amazon Web Services (AWS) outage and its impact on various services |
• Analysis of the "butterfly effect" of AWS outage on smart home users |
• Comparison of sports (Formula One and FIFA) with technology outages (AWS) |
• Critique of Amazon's response to the outage, particularly their status page |
• Discussion of unrelated API outage affecting WISE devices |
• Amazon's Route 53 DNS service is based out of a single US East 1 location |
• Single points of failure can impact availability even with highly available systems |
• Dependence on cloud services like Amazon, Cloudflare, and Google creates centralized internet issues |
• Homogenization of the internet leads to single points of failure and decreased decentralization |
• Architecting for high availability is challenging when relying on cloud services |
• TCP/IP's design allows for decentralized routing around failures, but this has been largely ignored in favor of convenience and quality of service |
• Decentralization and self-hosting are being explored as alternatives to reduce dependence on centralized services |
• The use of IPFS and other decentralized technologies is becoming more prevalent |
• Discusses internet bandwidth management, preferring to use LAN for less critical tasks |
• Mentions a log4j vulnerability in Java and its potential impact on remote code execution |
• Notes that Linuxserver.io has posted an info notice about the vulnerability |
• Warns users who self-host with Unify controller about its vulnerability and recommends updating |
• Advises listeners using Airsonic to be aware of its current vulnerability |
• Shares personal anecdote about internet outages when self-hosting |
• Discusses finding a website change detection app called ChangeDetection.io |
• Monitoring and notification service features |
• COVID UK government page monitoring example |
• Apprise integration for push notifications |
• Linode hosting and infrastructure security |
• Deckbot testimonial about Linode's performance |
• Minecraft server setup on Linode |
• New Home Assistant update (2021.12) |
• State of the stream project live stream event |
• Virtual reality meetings using Oculus Quest 2 |
• Discussion of VR technology being faster due to lower latency and data transfer |
• Idea of using VR for podcasting, including potential hardware requirements and costs |
• Mention of the Home Assistant Yellow device, previously known as Amber, and its availability for order |
• Comments on current tech shortages and supply chain issues, citing specific examples such as graphics cards and diesel exhaust fluid |
• Discussion of repurposing old PCs and finding creative ways to reuse technology instead of buying new equipment |
• The speaker's home systems and servers use eighth gen Intel CPUs for consistency |
• Upgrading to newer CPU generations may not be worth it due to relatively small performance differences |
• PCIe gen 4 is a slight change but doesn't significantly impact daily experience |
• Apple M1 Mac Mini is of interest as a potential home server, with low power consumption |
• The speaker uses older gear for home systems and servers, including a Raspberry Pi, and has recently upgraded Home Assistant on their Blue device |
• Home Assistant OS snapshot functionality |
• Concerns about updating potentially harming Z-Wave controller or network |
• New configuration panel and button entity features |
• Integration of local users who can only log in from the local network |
• Jellyfin integration with music support (potential for future video support) |
• Hue integration updated to support API version 2 |
• Pie Hole integration update |
• ESP home project updates, including easier flashing process |
• The host mentions issues with automations at their studio and decides to wait before upgrading their RV system. |
• A listener asks about naming conventions for Home Assistant automations, and the hosts discuss different approaches. |
• One of the hosts shares their own experience trying various naming schemes, including grouping by type or location. |
• Another listener asks how to approach a company about building a Home Assistant integration based on their API. |
• The hosts discuss possible approaches, including contacting the company for permission versus releasing an open-source library. |
• The government can issue cease and desist letters for publicly available API data |
• Companies may not understand that public APIs are intended to be accessed by anyone |
• Responsible disclosure is a better approach than posting findings on social media first |
• Some companies have been contacted about integrating their products with Home Assistant, but progress has been slow |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.