text stringlengths 9 408 |
|---|
[2559.32 --> 2564.40] explore, but it's unfortunate. It's sort of like when people tell you to solve the problems with an |
[2564.40 --> 2569.14] Android phone by flashing a custom ROM on there. It's like, come on, man. Yeah, I know you can do |
[2569.14 --> 2574.16] that, but most consumers aren't going to do that. They're just not. On that note, Will actually wrote |
[2574.16 --> 2578.86] in, and that's why we're talking about this, asking if you could put lineage on the shield. And I think |
[2578.86 --> 2583.86] that's a pretty interesting idea, actually. I don't think it's supported today, but certainly moving |
[2583.86 --> 2589.82] forward, I could see a much more motivated community emerging around this kind of stuff now. |
[2590.16 --> 2593.14] I tell you what, if a decent lineage image showed up for that thing, I'd try it. |
[2593.14 --> 2596.64] Yeah, me too. And I mean, I, even though I just said most people aren't going to, |
[2596.76 --> 2600.54] the vast majority of consumers who bought this won't, I'd still, I'd use it. |
[2600.66 --> 2606.62] Now, another option you've got is to replace the tvlauncher.apk via Team Win Recovery Project |
[2606.62 --> 2611.78] to one of the old versions of the launcher that doesn't have ads on the home screen. |
[2612.14 --> 2616.72] You'll need to unlock your bootloader to do that, but it doesn't require root or anything like that. |
[2616.94 --> 2621.02] Well, David from North Carolina wrote in, he said, I'd love to know a little more details |
[2621.02 --> 2625.22] around the solar panels that Alex recently had installed, especially since they seem |
[2625.22 --> 2628.50] to integrate with Home Assistant. I've been trying to convince my wife that it would |
[2628.50 --> 2632.62] be a worthwhile investment, love the show, and keep up the work. Thanks, David. And I |
[2632.62 --> 2635.72] think he's like extra excited because he's from your home state. |
[2635.98 --> 2637.84] Yeah, North Carolina. Hey, David, how you doing? |
[2638.16 --> 2640.74] Is it called a home state now? I mean, your new home state? |
[2641.92 --> 2646.84] Well, is it? I don't know. I still refer to England as home, and I still watched England |
[2646.84 --> 2651.42] crash out of the Euros in the final, and I still wept like a small child when that happened, |
[2651.54 --> 2656.38] but you know. But you also have the first state that you called home in the US. |
[2656.58 --> 2660.46] It's also the first state where I, it's the first place in the world where I had a child, |
[2660.60 --> 2664.08] so you know, there is that. So it's your home, I think it's like, as far as states go, |
[2664.16 --> 2666.40] it's your home state. Yeah, yeah, it probably is. |
[2667.98 --> 2669.70] So what do you think? You got details for them? |
[2669.92 --> 2673.70] I've got a few, yeah, not, I don't have, you know, specific model numbers or anything like |
[2673.70 --> 2678.76] that, but I went to a company called NC Solar Now. I looked at Tesla and a few others, but |
[2678.76 --> 2684.74] the NC Solar Now folks were the ones that came out with the, you know, the best overall price |
[2684.74 --> 2690.72] and package and service and financing and all that kind of stuff. And I ended up going for a |
[2690.72 --> 2696.22] SolarEdge system, and this has a home assistant integration which connects to the, they've got |
[2696.22 --> 2701.98] this website, and it will connect through the API to the website for up to 15 times an hour, |
[2701.98 --> 2707.56] I think it can pull the website through the API. And it was just a case of providing an API key. |
[2707.76 --> 2713.28] It took literally five minutes to set it up. I had to spend an extra few hundred dollars on the |
[2713.28 --> 2721.06] little Zigbee monitoring device to enable the inverter that's outside to talk to the internet, |
[2721.06 --> 2726.06] because by default it doesn't come with any Wi-Fi capabilities. But apart from that, you know, |
[2726.32 --> 2731.52] extra few hundred dollars to get the monitoring capabilities. Yeah, it's been very straightforward |
[2731.52 --> 2737.44] to set it up. And not only does it talk to home assistant, but the SolarEdge company also provides |
[2737.44 --> 2744.40] a really nice dashboard and a really pretty slick mobile app as well. So I've got a little widget on |
[2744.40 --> 2749.02] my Android home screen that tells me exactly what my solar is doing right now, which is pretty cool. |
[2749.02 --> 2757.44] That's great. Yeah. I love that they're using Zigbee for that. Just the thing, Zigbee's all over the |
[2757.44 --> 2762.32] place here. Nate wrote into the show asking about security implications for sharing Ansible playbooks |
[2762.32 --> 2766.96] publicly. You know, he sees them on GitHub, all of that. He got thinking about this after he listened |
[2766.96 --> 2770.52] to an episode of the Darknet Diaries, and he wondered if you have any thoughts on it. |
[2770.52 --> 2778.10] Well, all of my stuff's open source on github.com slash ironicbadger slash infra. You know, I have |
[2778.10 --> 2783.72] open sourced everything for years now. That's kind of my default policy. So I sure hope there isn't a |
[2783.72 --> 2786.44] privacy implication of doing that. You know? |
[2787.72 --> 2788.66] Good answer. |
[2788.66 --> 2795.94] Yeah. I do encrypt everything using Ansible Vault. So all of my secrets and things like that are stuck |
[2795.94 --> 2803.08] behind AES-256 encryption. So hopefully, unless I commit a secret directly in clear text, I think |
[2803.08 --> 2806.66] I'm okay. Yeah. I just, you know, when I go through your GitHub, I just look at it. I think, you know, |
[2806.66 --> 2810.40] everything looks pretty good except for that passwords.txt file where you just put all your |
[2810.40 --> 2816.72] passwords in there. Well, funny story on that. I actually published my Gmail password one time to |
[2816.72 --> 2824.46] that repo. And I had a guy, a listener in Australia message me. Like, it must have been first thing in |
[2824.46 --> 2828.62] the morning for him because it was just before I went to bed saying, hey, by the way, did you know |
[2828.62 --> 2833.92] that commit you pushed 12 minutes ago has your Gmail password in it? And I'm like, okay, first of all, |
[2834.06 --> 2840.20] thank you for letting me know. Secondly, it was 12 minutes ago. Like, were you just waiting for me to |
[2840.20 --> 2840.90] push something? |
[2841.78 --> 2843.92] Yes. He's got some sort of like alert. |
[2843.92 --> 2851.12] Uh, so to get around that, uh, Nick Busey from the HomeLab OS project, uh, helped me out with a |
[2851.12 --> 2857.72] pre-commit, uh, hook that I have in my Git repo that just checks that my secrets file is encrypted |
[2857.72 --> 2863.48] before I push and do a Git commit and push. That's been very, very useful. It doesn't protect against |
[2863.48 --> 2868.88] me actually putting API keys and variables and stuff like that directly into other files, which, |
[2868.88 --> 2874.14] you know, there comes a point where you've got to be like, right, okay, this, you know, my safety net |
[2874.14 --> 2880.72] is checking that file is encrypted or not. It's not going to go and scan every single file. Um, so |
[2880.72 --> 2885.78] yeah, I guess it's up to you whether you feel comfortable with that risk or not. And, uh, I, |
[2885.84 --> 2891.04] I tend to think that even if you're using a private repo on GitHub, you may as well treat that as a public |
[2891.04 --> 2895.04] repository anyway, because one day it will be whether you like it or not. So. |
[2895.04 --> 2899.00] And it really just means, can you stick to like a good hygiene with that kind of stuff? |
[2899.26 --> 2903.28] If you'd like to get your question in or have a comment or something you think we should check out, |
[2903.66 --> 2906.98] let us know, go over to selfhosted.show slash contact. |
[2907.46 --> 2911.26] And you can go to selfhosted.show slash SRE to show your support for the show. |
[2911.52 --> 2916.40] Yeah. Become a member, get access to the post show. And of course, uh, help us keep the show |
[2916.40 --> 2917.68] on the tracks. |
[2918.04 --> 2921.52] I think this episode, we're going to talk about the future of the gasoline engine |
[2921.52 --> 2923.16] and the internal combustion engine. |
[2923.16 --> 2925.26] Oh, I have thoughts on that. Interesting. |
[2925.60 --> 2931.08] Yeah, me too. Now I was browsing some, I always seem to come up with YouTube on these things, |
[2931.16 --> 2936.48] don't I? But anyway, uh, about steam trains the other week. And, uh, I found this union Pacific |
[2936.48 --> 2942.40] steam loco called the big boy. And this thing is freaking enormous. And it was designed, uh, |
[2942.40 --> 2948.42] in the early, uh, part of last century to get over some of the Rocky mountain passes because |
[2948.42 --> 2954.82] they're just so vast here and the trains are so heavy. And so Union Pacific have actually restored |
[2954.82 --> 2960.36] one of these big boy steam locos, which is essentially two massive steam locos glued together. |
[2960.58 --> 2967.40] This thing has basically two sets of drive wheels and two, two full sets of pistons. And it's just |
[2967.40 --> 2973.90] awesome. Just go look it up. Big boy Union Pacific steam loco. And it's going on tour in August around |
[2973.90 --> 2980.66] the US. So it's, it's leaving Cheyenne, Wyoming and going all the way down to Houston past, uh, |
[2981.08 --> 2984.10] our beloved cheese bacon's hometown of Beaumont. |
[2984.50 --> 2986.12] I know he lives in Denver now, doesn't he? |
[2986.40 --> 2988.28] Okay. Well, so much for that. |
[2988.28 --> 2990.26] You could say it's his original hometown though. |
[2990.62 --> 2997.28] So much for that plug. Um, so yeah, it's going up to, I think, uh, through Dallas at some point |
[2997.28 --> 3002.02] and then up through Kansas city and St. Louis. So if you're in the center of the country, |
[3002.02 --> 3006.98] by all means go take some pictures for me, cause I'm not going to be able to make that one. But, |
[3007.02 --> 3009.02] uh, throughout August, it's traversing the country. |
[3009.48 --> 3013.04] That does look like an incredible route. Actually. We'll have a link in the show notes. |
[3013.10 --> 3016.12] And when you go there, they have a map that shows you the route that they're going to be on. |
[3016.46 --> 3020.68] Well, you know, it's either side of our Denver meetup, don't you? So I reckon if you were creative |
[3020.68 --> 3023.16] with your schedule, Chris, you could probably find it for a day. |
[3023.20 --> 3029.04] Our route for the Denver meetup in total is a good, it's going to be just over 5,000 miles. |
[3029.04 --> 3036.40] That's a long way. I drove that myself in 2018. We flew into Orlando, drove up to DC, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.