...won't know beforehand what functions and such they would need to hook to fully hide the evidence of their cheat. If they miss even one, banned.

Lastly, I think there's just a lot of unexplored potential in anti-cheat tooling that doesn't act like it owns my PC. I think before I talked elsewhere about an AC where the server sends a completely dynamic payload and the client is supposed to execute it and return the result. So a cheat maker...

The second is that we're already at the point where you don't necessarily even need to have "privileges far above your game" when the future of cheating is just looking at the screen and having an AI model use that to send inputs to the game. KAC doesn't do anything to help here.

It's a question worth answering. My problem with it is threefold. Cheaters have found a way around every anti-cheat escalation so far, so the real loser is innocent players who are subject to more and more invasive ACs while still having cheaters in the game.

Oh and the best part is if you do get hired, they probably use workday for internal HR stuff too, and it's not much better for that.

>upload resume
>resume parser gets the entire thing wrong
>have to manually rewrite it all
>repeat this for every individual company because workday instances are separate, can't even import/export

It's always something related to the middle click or scroll wheel for me. I feel like they tend to use cheaper switches on the middle.

Try unplugging it and mashing the button a lot to clean the contacts.

And then there's of course the obvious issue that SE is likely to take far more drastic action if this instance gets popular. The Mare takedown already hit gaming news circles - imagine the headlines if this one gets popular. It would force them to take action, and we're back to square one. (4/4)