• 0 Posts
  • 22 Comments
Joined 2 months ago
cake
Cake day: May 1st, 2026

help-circle
  • I started doing the One True Database method because I got worried that the high write count on all the little db’s was abusing a raspberry pi’s SD card. Moved them all to a bigger server with NVME and mirroring to a RAID.

    Not all the compose files make obvious how to reconfigure the db host. Homeassistant uses s a sqlite db built into the container, rather than a separate unit, but you can force it to use a remote db through its config file. May or may not be worth hiding db user/pass in a .env And sometimes there’s trouble restarting after power failure, depending on what order the database, pi, and various containers come back up.

    I also feel it’s worthwhile. I feel better being able to check on all the databases. Feel better not writing to the SD card so much. Feel better offloading those megabytes and cpu cycles from the little pi. It’s been fun snooping through database structures. There have been a couple times where I decided to query one of the ccontain databases directly, or cross from one project to another, and it’s easier (for me) to give a different user privileges to the database and query some deep bit of data than to figure out how to extract it from an API or frontend.

    I’m not even running that many services, but why would I want the overhead of 6 separate mysql instances when I could just have one?



  • The very broad funds definitely will - VTI/VTSAX - but at lower weights and under less time pressure than the rigid index funds (VOO/VFIAX). That takes off a lot of the liquidity squeeze and (presumably) reduces their loss.

    But you have to remember that people who use these funds intentionally invest in obvious losers and willingly overpay for hyped stocks because they believe, in the long run, that buying obvious losers is more than balanced by also buying the unexpected winners.

    SpaceX is just the first time an oligarch tried so obviously to rig the passive investor structure to his favor, and I’m glad the S&P people didn’t cave.






  • What I’ve seen indicates SpaceX will become something like 0.1% of S&P and 0.5% of Nasdaq. If a retirement fund is one of those indexes, and they get ‘forced’ to buy at 2x SpaceX’s eventual value, then that’s a loss of 0.05-0.2%. $50-200 on $100,000 principal.

    Most normal people won’t notice that among the usual stock market noise. Over a hundred million account, though, it’s a huge amount of money getting funneled into the thousands accounts able to front-run the index inclusion, which means, in turn, a huge amount of money getting funneled into the dozens of VCs who got into SpaceX pre-IPO.

    It’s like the scam from Office Space where they collect the rounding errors on interest.









  • I added homeassistant and some power monitors to my stack, and the IT rack comes in around 1.5 kWh/day - one of the biggest power budgets in the house, even with a low-power CPU, after adding in a few HDDs, a couple switches, and the cable modem. I’m also in a cheap power state, so it’s not a financial pressure, just surprising how quickly 10W here, 10W there…add up. At $0.50/kWh, I’d think solar would be a no-brainer.


  • Keep power in mind. For most home-use services, you don’t really need much computing power, and you might be able to do all you want with a single box. Even 30W, 24/7 is $25 (@10¢/kWh)-125(@50¢)/year of electricity. That said, it’s a small price to learn how to do clustering or swarms.

    I’d guess that your biggest load would be transcoding in Jellyfin, for which Intel Gen 6 added h265 to quicksync. The Gen 3/4 CPUs in M73 would be extra slow with most modern codecs.


  • My setup is a pile of kludges built on top of each other over the last two decades.

    I started with ULAs distributed through DHCP, connected to named, which allows hosts do declare their own name and let me access local services as though I had a real domain.

    My ISP eventually started supporting IPV6, but only assigned /128, so the ULAs got NAT-6ed out to the real world.

    I eventually learned how to request prefix delegation from the ISP and set up SLAAC.

    So now, my PIv6 clients have a) their link-local address, b) the ULA, c) a “privacy” SLAAC, and d) a unique SLAAC. All my internal services still refer to the ULAs.

    I don’t think I’d recommend this system for someone setting up from scratch. The easiest thing would be to go with SLAAC, if you can get prefix delegation, and set your DNS/pihole to send the unique-SLAAC address of any servers you run.