• 4 Posts
  • 323 Comments
Joined 3 years ago
cake
Cake day: January 5th, 2024

help-circle



  • Uhh, no… It’s because that’s not how anything works. There’s so many flaws in your argument, but here’s just one: if an enemy player is really well camouflaged but technically visible, then they would be rendered on the client side, but a human player would have to be very observant to spot them and kill them.

    A cheater can replace the enemy character’s texture so that, on their screen, the enemy’s camouflage is useless and the player can spot them with no effort.

    From everything the server can see, the cheater’s gameplay is legit. They could just be really good at spotting enemy camouflage. Only by looking at the client side render output, you can spot the cheat.

    Unless the server is actually rendering the game for each player (which, spoiler alert, isn’t the case), most cheats are not detectable nor preventable on the server side.


  • While I agree with you (and upvoted to match), I also acknowledge that not every game is suited for that kind of server structure. Competitive ranked games, that rely on a fair matchmaking algorithm and consistent server performance, simply can’t just route matchmaking players to a random community-hosted server. And communities can’t really form that way, either.

    Or to make it short, esports can’t do this while maintaining their esport status. And those are the games that need anti-cheat the most.

    Me personally? I don’t even like those kinds of games. I barely play multiplayer games at all, and when I do it’s because I’m playing with friends, and couldn’t care less about my rank (if I even get one). So for my kinds of games/scenarios, community or self-hosted servers are the obvious choice with zero drawbacks. But I can still acknowledge that it’s not a solution for all cases.

    Lo and behold, most multiplayer games do run on Linux!


  • Switched WiFi backend to wpa_supplicant by default for new installations, improving compatibility with various WiFi networks

    Fantastic. The only reason I enabled developer options is to switch this, since I wasn’t able to connect to my university’s wi-fi otherwise.

    Known issue: Existing installations will continue to use iwd unless manually enabled in Developer Settings

    Damn.










  • Honestly I’m so sick of it being called the “GabeCube”, partly because it’s too close to GameCube phonetically that it actually sounds pretty much identical to GameCube in most cases, but moreso because it’s the result of the hard work of so many talented and passionate engineers at Valve, it feels really disrespectful to call it after the businessman who funded it.

    It’s an amusing pun, I enjoyed hearing/reading it the first time. Second time onwards it’s just annoying.


  • Right, I guess that’s what turns me off from it, somehow you put it into words better than I ever could. But it’s still nowhere near “slop”, and I don’t like it being slandered. It’s entertaining (for those who enjoy it), it’s harmless, and the smoothness of the animations can even scratch a “competence porn” itch. I really think they’re going for an ASMR kind of thing, and it’s working. And I see absolutely nothing wrong with that.

    I can also guess that that’s why they’re going for those kinds of subjects in most of their videos. Anything that is even a little bit controversial or political can turn people away, so it’s safer to stick with things that are a bit detached from the world. … Or something like that.

    Not to mention that any topic that doesn’t call for cool animations is immediately out of the running. The coolest animations come from the exact kinds of topics you described. Something on the cusp of science and science fiction.



  • Took me a while to understand what you’re warning against. Allow me to rephrase, and tell me if I got it wrong.

    The || will execute what’s after it in two cases:

    1. The preceding command (in this case the rm) never ran because of an earlier &&
    2. The preceding command ran and returned nonzero

    OP’s code relies on the 1 case, but wrongly assumed that the 2 case will never happen. That’s the footgun.