[–] 4 points 3 weeks ago

Up front cost and maintenance time is the one that really gets you as things age and software packages get retired or require systemic updates that break other things in the system. Containerization helps a lot but isn’t perfect.

  • source
  • [–] 3 points 3 weeks ago

    I’ve been running mine for over 20 years. It’s certainly got more difficult, especially to be able to reliably communicate with Gmail-hosted servers and outlook.com addresses, but SPF, DMARC, and DKIM are all pretty straightforward to set up. Tightening the encryption/hash algorithms you accept and “anonymizing” your server greetings takes some finesse as well, but I definitely prefer it this way.

    I avoid the entire webmail and spam filtering aspects, smtp(s) and imap(s) only.

  • source
  • parent
  • context
  • [–] 8 points 1 month ago (3 children)

    Like I tell my children, allowing yourself to act in such a way is harmful to yourself. It’s not going to make you an evil person or something, but that kind of behaviour is corrosive to your soul. How you think shapes how you behave, and your behaviour trains your future self. Be good to yourself. It’s not about the clanker; it’s about you.

  • source
  • parent
  • context
  • Absolutely. I refuse to rely on cloud anything after being bitten too many times: company gets purchased, unstable pricing or service changes/discontinuation, data trapped in someone else’s server, internet or service instability… 100% self hosted is the safer, saner, more predictable option.

  • source
  • parent
  • context
  • Automatic code formatting, and failing a PR due to an automatic formatter is lazy and wrong. Code formatting should be a (strong) set of guidelines, but never a hard and fast rule. Every code base ends up with some section that is visually easier to understand but breaks the formatting check.

  • source
  • parent
  • context
  • view more: next ›