All I do:

• Run updates daily
• Disable password logins
• Run sshguard
• Daily backups to a cloud and off-site host

I think that’s it. I have my host exposed to the Internet. As far as I know, it’s fine.

BTW, sshguard is for the IMAP and SMTP that run on the host, which do allow password logins. But it helps reduce load from brute force attacks on port 22 (which are pointless anyway).

I’m much more worried about my son installing dodgy Minecraft mods, or my wife installing another app that she saw on TikTok. I really should put them each on a separate VLAN…

I’m old school, and would set up Fetchmail. It can pull down either POP or IMAP (I haven’t used POP in 25+ years, but I guess it works fine still). Then I’d run Dovecot or some other IMAP server on my host to read mail from there.

Increases in productivity go to the owners, not the workers. Even imaginary increases in productivity.

DNS is never the Domain Name Service.

The very first sentence of RFC 1034, the document that is the basis of DNS, identifies it as the Domain Name System.

Also, buying or building something to cover the less is cheap, and possibly fun, mini-project. As long as you allow a bit of airflow…

What do you use for your Kubernetes build?

Also, do you have an S3 compatible storage? If not, what do you use for persistence?

If it unlocks with a simple pattern, if you use a unlock code that someone can guess, and so on.

Or did you mean remotely?

I guess this is the original:

https://youtube.com/shorts/e_Z7st2AeaM

Totally off topic, but man that is one terrible table design. 😆

AI wouldn’t be so bad if the planet wasn’t being turned into computronium.