tburkhol

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.

Hell, for even just $1M per instance, I'll be happy to start up a dozen to sell him.

You can't just launder $2B of campaign contributions overnight. You need a year or two to filter it credibly through pundits, consultants, pollsters, and advertisers.

If you start with the founding of Harvard in 1636 and go to SCOTUS deciding that laws requiring the 10 commandments in classrooms are unconstitutional in 1980, then you get almost 350 years.

The CO2 sensor calibration thing is inherent in the technology. They drift, a lot, and without occasional reference to a known standard, there's no way to know whether "1000" is really 1000, or 500, or 2000, but exactly how that gets implemented seems to vary a lot. I have an SCD30 board from Adafruit, which internally records CO2 minima and, over the course of week or so, adjusts its calibration so that minimum is 420. That means no special calibration procedure, but it does have to be somewhere that it gets periodic fresh air exposure.

There's a newer, photoacoustic sensor technology that doesn't seem to require continuous recalibration, but (at least this one: https://www.sparkfun.com/products/22956 ) require an extensive initial calibration.

My CO2 sensor has dramatically changed my routines. My space isn't small - maybe 1200 square feet/100 sq m - but it must be pretty well sealed, because I can easily see my own breathing add to CO2. Nevermind cooking on the gas stove. Treadmill time adds 500+ ppm.

Now, I open windows every chance I get (which isn't super often, because the dewpoint is 70 oF/20 oC in Atlanta), and I've shifted a lot of my cooking to an electric tea kettle, hot plate, and toaster oven.

I see a lot of workplace horror stories on social media, but my best and closest friendships formed through work. A crew of good people can do just amazing things and be a source of pride that absolutely can't be replicated solo. Almost indescribable.

But that focus on work can hide some flaws and conflicts, even during downtime. It can feel like betrayal, and definitely enormously disappointing when those come out. And who knows, maybe, if one had been there at the right time, been supportive in the right way, then that slide down the rabbit hole could have been stopped, so there can be some guilt, too.

Glory days, man. Don't be sad that they're passed, be glad that you had the chance.

I have isc-bind running behind pihole so network clients can register their own hostnames, and as near as I can tell, that's outside the scope of pihole's DHCP and dnsmasq. Pihole alone is probably fine if you only want to name static hosts, but (I understand) Unbound doesn't support ddns, either.

Have you seen Trump's suits? Dude could be wearing half inch plate under that monstrosity.

pihole, in front of my own DNS, because it's easier to have them to domain filtering.

mythtv/kodi, because I'd rather buy DVDs than stream; rather stream than pirate; but still like to watch the local news.

LAMP stack, because I like watching some local sensor data, including fitness equipment, and it's a convenient place to keep recipes and links to things I buy regularly but rarely (like furnace filters).

Homeassistant, because they already have interfaces to some sensors that I didn't want to sort out, and it's useful to have some lights on timers.

I also host, internally, a fake version of quicken.com, because it lets me update stock quotes in Quicken2012 and has saved me having to upgrade or learn a new platform.

If you email to people on gmail or outlook, won't Google and Microsoft still end up with copies of most of your mail?

Ditto on hardware raid. Adding a hardware controller just inserts a potentially catastrophic point of failure. With software raid and raid-likes, you can probably recover/rebuild, and it's not like the overhead is the big burden it was back in the 90s.