Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BO
Posts
1
Comments
232
Joined
2 yr. ago

  • Whoosh!

    That's literally the point: he can't. His apology is useless.

    The point of an apology is to acknowledge a mistake and signal that you will attempt to change your behaviour to prevent or avoid that mistake in the future.

    A really good apology will also identify the steps that will be taken to avoid the mistake going forward.

    I argue that if you don't or can't make an attempt to change your behaviour, your apology has no meaning. That is, the apology is not sincere and therefore not useful.

  • Users often don't take care to separate private and public environments. They just dump all their stuff into one and expect their brain to make the correct decision all the time.

    Put your private data into a private space. Never put private data into a mixed use space or a public space.

    e.g. Don't use your personal email at work. Don't use your personal phone for business. Don't put your passwords or crypto keys in the same github or gitlab account or even instance and don't reuse passwords and keys, etc.

  • Start with a simple, basic service. Think of something like a web server or ntp. Understand how these services affect your environment with respect to security, performance, availability, maintenance, backups, other services, firewalls, routing, DNS, monitoring and notification, documentation, change control, etc. Those are the hard parts of hosting and if you find ways to be effective with a simple service the others will be less daunting.