@0xabad1dea Counterpoint on the federation thing: I don't want to make 50 different accounts for 50 different instances. So at the very least federated identity and authentication should be supported, if not actual message federation.

@tinker Also, it's useful to keep in mind that recipes are not subject to copyright in the US, as they're entirely 'statements of fact', which explains why every article has the 'my great grandmother pulled this recipe out of a magic lake' backstory as that is copyrightable. But there's nothing legally stopping you from just writing down the actual recipe part of the ones you like in a personal book.

Though personally, if I ever have a reason to go hunting for recipe ideas, I'm more likely to go sifting through [redacted]'s ridiculous collection gathered over a long career as a chef. They have more cookbooks on those shelves than the local library does, and it's a reasonably sized library too, not one of those tiny one-room shacks...

@b0rk I mean, that's basically the same way I do it for my stuff, so as far as that goes it's just nginx with certbot on debian stable, and either statically-generated sites or hand-written HTML (But it does have PHP set up, so I can do stuff with that if necessary). With unattended-upgrades the only manual updates I need to do are when debian makes a new stable release, and the stack itself is stable enough that it just Keeps Working.

For the stuff that needs to be dynamic, if I can't find a stable-enough "off-the-shelf" stack for it I usually just bodge something together with a 'stable-ish' framework ("pretty much anything that isn't go or nodejs" at this point)