Being able to see the contents without the inefficiency of opening the door or having the problems of a translucent door or doing admin work could be cool. But now I hate them too. So glad we have no “connected” kitchen gear yet except Tasmota switch and power monitoring sockets.

Check your autorenewal failure alerts go somewhere you’ll react to.

Yeah, said that, or “you’ll work on this as a contractor” as contracting isn’t classed as being employed by the hirer in some countries. The confused language makes them look like they could give you tax and social security problems, which might deter some good people.

No, but could you feed the website with mismatched tags through something like tidy first? That error looks like maybe it’s expecting xhtml and getting html. Maybe the site is declaring one, then using the other. Lots of software won’t care because it’s a pretty common error, but some panics.

They used .unwrap(…) in production, which can escape notice until there’s an error, then it panics. It’s better to always handle the potential error, or at least use ? to pass the error back to the caller.

Even if you self-host, other people’s mailservers still interact with it, unless you only chat with other users you host. And some of the big webmails variously get really pernickity about your DNS, DKIM and more, or they deploy some pretty obnoxious countermeasures against your server with little explanation. So I’d say it’s more often both than not, no matter what you do. If you think it’s not being a pain, there’s probably an unpleasant surprise in your server logs or coming soon!

It’s still often worth self-hosting, but that’s more big webmail really sucks, even ISPs often don’t set their mailservers up well and it’s often an early casualty of ISP managers looking for costs to cut.

Those apt commands are in a less-good order. It’s usually better to update apt, then upgrade the system.

I upgrade as soon as reasonably possible after the notification appears, if the system isn’t on auto-upgrade.