Evansbee

Is there some way to do this work of memory hacking from OUTSIDE the VM? I've always thought that it would be "safer" to do the work by just being able to scrub the hosts side of VirtualBox, then stuff events back in through the keyboard and mouse rather than getting on the inside of the VM and hooking/injecting inside the target executable.

I bet you just nerd-sniped them into their next FFF post.

This is almost certainly a side effect from their belt optimization from years (?) ago? Strangely I do sushi belt science sometimes and I’ve never noticed this bug, I’d wager the splitters and circuit network stuff changes the behavior enough to avoid the problem.

Do these numbers actually make any sense? I feel like I'm missing something here, 800k of 1.4m refuse the vaccine, but 68% of the 1.4 are already fully vaccinated? Is there a primary source out there for this?

I would do this just to play starsiege: tribes.

Trying to figure out why the hn post screen didn’t flag this for me, I’m usually pretty religious about amplifying existing posts and not reposting.

Disagree. This is utility classing and you can target pseudo elements and deal with responsiveness. Tailwind is pretty popular and uses this methodology.

Don’t 404 links on your new site, 302 redirect to previous versions on different hosts until you run out, then 404.

But perhaps an ai could be trained by it.

That's in a separate section of the article. "Point and Call" isn't nudge theory either.

> would it even work on an MMO?

CheatEngine is a great first step in developing any bot, for any game.

GW2 doesn't have to trust the client for CE to be useful, it's just that the usefulness is different than what you're using it for currently. The goal of CE in developing an MMO bot is to figure out where in memory things like player location, party members, linked list of all nearby objects, etc, are. This allows the user to write the bot in a way that's pulling information directly from memory. CE is a great way to back into this data (coupled with a debugger/disassemble, of course).

But hiring and the work force AREN'T fair. My performance review, salary increases, and bonus aren't based on some normalized criteria, we're rewarded for going above and beyond.

Even on the surface "fairness" isn't really the objective, because there are going to be different hiring managers and interviewers throughout the whole process. The salary negotiation isn't going to be "fair" in this way.

I'd rather have someone who had a rich github history and a record of real accomplishment than someone who had none but could produce a good hacker rank score. Hiring is the most important thing that we do as managers, I'd be selling myself short if I didn't take it all into consideration.