I’ve had decent success scaling down recipes, but what I’ve found is that I make more consistent beers when I use a recipe designer instead of just taking 20% of the 5 gallon recipe. I’m just a beginner though. Someone more experienced could probably just eyeball it.

This is an amazing bit of advice that every home brewer needs to understand. IBU only tells part of the story, and you have to understand that there are other factors that go into perceived bitterness. Many of your darker beers have higher IBU values, but the non-fermentable sugar and the other roast flavors counter the hop bitterness. Adjuncts like lactose can also smooth out some of the sharper hop notes (again, non-fermentable sugars). I found a guide that shows ibu ranges for a bunch of styles and you can see that a lot of heavier beers are rather high in IBU even though you’d never call the style “bitter” or “hoppy”

I feel like this is legitimately more true than a lot of people think. Say what you want about the average end user, but UX is a HUGE driver with regard to adoption and user uptake. You can have the best of everything else in your application, but if the UX sucks, folks just aren’t going to use it

Yo, please tag this NSFW… we didn’t come here to see this kind of smut

I was just saying that there can be a lot of good reasons for downtime. Heck, I use a secondary in my network because sometimes my unraid host starts dnsmasq and it clobbers my adguard container

Depending on the client, it can be. The Microsoft page pretty cleanly defines expected dns client behavior [https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-client-resolution-timeouts#what-is-the-default-behavior-of-a-windows-7-or-windows-8-dns-client-when-two-dns-servers-are-configured-on-the-nic](Microsoft learn). There haven’t been any published changes to this that I’ve seen, and it more or less matches my experience. Linux is a lawless land in this respect, but it really boils down to “it might”, so caveat emptor there. That’s also why I suggested a public ad blocking dns server as a secondary, in case multicast dns does its multicast dns thing

No worries, I had the same thought at first and was very confused for a minute

OP already said that their current DHCP solution (the router) can’t push multiple DNS servers. Having a good secondary can be really helpful for things like power blips, maintenance windows, and cats pulling power cables. There are a few solutions that also do ad blocking that can make good secondaries

This would be great except OP said that their router can’t push 2 DNS addresses. Otherwise, ya, redundant services is always best

If you already have pihole in your environment, I would just use that. DHCP is pretty light weight, so the pi should be more than capable, and you don’t want to complicate your core services more than you need to

I use tandoor myself, but mealie is also a solid choice