• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle


  • Not sure if this still happens, but for groups of 4 that used to want to play together, there was no way to lock the team or kick from lobby. So what would happen is you’d get match-maked in as the 5th player, and as soon as the game started, your team would kill you. This would happen about 25% of the time with random matchmaking.

    I ended up quitting R6 Siege because of the toxicity and constant slurs on voice chat. It’s a shame because it was otherwise my favourite competitive FPS.



  • IMHO all these approaches are convoluted and introduce way too many components (SPOFs) to solve the problem. They’re “free” but they come at the cost of maintaining all this extra infrastructure and don’t forget that certificate transparency logs mean all your internal DNS records that you request a LetsEncrypt certificate for will be published publicly. (!)

    An alternative approach is to set up your own internal certificate authority (CA), which you can do in a couple minutes with step-ca. You then just deploy your CA root cert to all the machines on your network and can get certs whenever you need. If you want to go the extra mile and set up automatic renewal, you can do that too, but it’s overkill for internal use IMHO.

    Using your own CA introduces only a single new software component and it doesn’t require high availability to be useful…