

The dead give away is the warm smile. Trump never smiles, at least not in a phoney way.


The dead give away is the warm smile. Trump never smiles, at least not in a phoney way.
I guess it depends what you run, and how the projects/containers are configured to handle updates and “breaking changes” in particular.
But also, I’m being a bit broad with the term “breaking changes”. Other kinds of “breaking changes” that aren’t strictly crashing the software, but that still cause work include projects that demand a manual database migration before being operational, a config change, or just a UI change that will confuse a user.
The point is, a lot of projects demand user attention which completely eclipses the effort required to execute a docker update.
Are you updating 1000’s of stacks every week? I update a couple critical things maybe once a month, and the other stuff maybe twice a year.
I don’t recommend auto updates, because updates break things and dealing with that is a lot of work.
Documentation is for onboarding other people. Why on earth would I need to onboard other people to something self-hosted?


Hear me out: what if repealing section 230 would end up killing our social media monoculture, since it would be impossible for these platforms to operate. Instead, what if people had to host their content themselves, you know, like we did back in the day, when the Internet was fun.
Did they haul out a nativity scene? Go to church? No? Then it was a cultural celebration, not a religious one. Nothing hypocritical about that.
Might be a good time to remember that Christmas has adopted many pagan traditions.