• 1 Post
  • 67 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • I came to MySQL and Apache because they were the backend for other services I wanted to start,. Later, when I wanted to build my own, I already had Apache running, so why would I add nginx? I did let other services add sqlite, but have (in most cases) figured out how to switch those to MySQL.

    All of that has been running for 20 years. I’m sure it would be good for my dementia-risk to learn how to start ngnix and migrate all those services, but it’s far more attractive not to mess with what works.


  • In the US, plug-in hybrid is a decent way to cover the breadth of consumer desires. Get a battery big enough for 50 miles of daily commuting, but have the ICE for 500 mile holiday trips. More complicated, having both power systems, and you still have the tie to gasoline, but you don’t have to lug a massively oversized battery pack everywhere you go and you still get most of your transportation energy from the electric grid.




  • IPv6 does have private spaces. Any prefix beginning with fd is ‘private,’ and (IIRC) there’s a formula to generate the next 40 bits of prefix to minimize the chance of intersections. i.e., you can generate your own internal /48 functionally equivalent to 192.168/16 or 10/8

    Don’t know if you can use that with SLAAAC, but it works if you run a dhcpv6 and makes ipv6 feel a lot like ipv4. You have to NAT everything inside &c, but if you already have a functioning internal IPv4 network, IPv6 is just a matter of figuring out which config options need to be changed (eg, dhcp6.name-servers for option domain-name-servers)


  • I don’t so much care where it’s made. The real selling point, to me, for Pi is that their products are well documented, in English, and solutions for problems are easily googled. There’s tons of SBCs out there, some of them even inexpensive, but I can’t tell if any are going to last longer than a single production run. Meanwhile, I can still buy a Pi 3 after almost a decade. Or I can take the hat I made for a Pi3, plug it straight into a new Pi Zero, and expect it to work without changes.

    IPO is a big step down the path to enshittification, especially when there’s no clear, dominant alternative.





  • With 25 GbE, even 10, I’d be tempted to PXE boot client systems. Maybe still have a local PCIe SSD for windows game files.

    Dunno how that would actually work with Windows, but it was fun when I did it for beowulf nodes. Setting RPis to netboot is a little involved, but you can create an OSMC image and give all your TVs a consistent ‘smart’ interface. You don’t even need 10GbE to be pretty functional for the Pi, but my experience is that WiFi is not fast enough.





  • Depends a bit on screen size and placement, too. I play on 27", 1440p, about 3 feet from my face, and my eyeballs are definitely the lowest resolution link in the chain. 32" screen on my desk, 60" screen in front of the couch, and 1080-1440 will start showing their pixels. I’m not anxious to upgrade my screen, because 1440p gives me great framerates with a cheaper video card. Also a 32" screen at a viewing distance of 3’ is hard to actually see everything.

    I’d much rather have a good game that runs fast at 1080p than have to get a $700 card for OK framerate and style-over-substance gameplay just to get 4k.

    Agree that using VR to get immersive, wide-field graphics from fewer pixels is a great alternative.




  • HA doesn’t require 4/4/32, that’s just the hardware the HA people sell. (which, given that your phone may be 8/16/128, is hardly “robust”). Generally, the Home Assistant crowd kind of target an audience that’s probably already running some kind of home server, NAS, or router, and HA can probably be installed on that device.

    Theoretically, there’s no reason the HA server couldn’t be installed on your phone, except then your smart home functions would only work while your phone is in the house and not sleeping. Kind of defeats the point of a lot of it, unless you’re just thinking of smart home like “remote control for everything.” Regardless, much smaller niche for an already-small market, and apparently not a priority for the dev team.




  • Ditto. Started 20 years ago with one service I wanted. Complicated it a little more every time some new use case or interesting trinket came up, and now it’s the most complicated network in the neighborhood. Weekend projects once a year add up.

    If you have the resources, experiment with new services on a completely different server than everything else. The testing-production model exists for a reason: backups are good, but restoring everything is a pain in the ass.

    I also like to keep a text editor open and paste everything I’m doing, as I do it, into that window. Clean it up a little, and you’ve got documentation for when you eventually have to change/fix it.