xep

This is why it is critical to contain memetic hazards. Has the Foundation taught us nothing?

This is where you’d normally go “there must be a better way…”

Some anti cheat work better than others, and it depends on how much you’d like to play the game that needs it. Plenty of games without.

EAC does not hide its process and you can see it running. If it’s not, perhaps it has left files behind, but that’s a Windows issue more than EAC’s.

there’s no way for users to reliably remove it

I’m not sure if this is true for the ones backed by the larger companies, like EAC. It’s possible to completely remove EAC using their installer.

Games like valorant are filled with cheaters despite using kernel anticheat

In my experience, this is untrue. Valorant isn’t “filled” with cheaters in the same way Apex Legends is.

Lots of other games to play.

I love my Vader 3

What on earth did I just read

We do what we must because we can…?

Wouldn’t mind something that would fix my tinnitus.

It’s ef sock in my head

Ah, a low radar signature house.

Looks solid! Very nice.

He’s giving them a free lesson.

I use SyncThing for syncing things, and LocalSend for just sending things.

The WTF case isn’t allowed because it would allow modification of the const. From https://en.cppreference.com/w/cpp/language/implicit_conversion

int main() { const char c = ‘c’; char* pc; char** ppc = &pc; const char** pcc = ppc; // Error: not the same as cv-unqualified char**, no implicit conversion. *pcc = &c; *pc = ‘C’; // If the erroneous assignment above is allowed, the const object “c” may be modified. }

Cue GrapheneOS refusing to support the feature in 3…2…1…

You’ll need PowerTools for Decky: https://git.ngni.us/NG-SD-Plugins/PowerTools

Passthrough input, or charge limiting? Charge limiting was added after release but that was a while ago.

The deck has passthrough input and you can set a charge limit of 50% if it’s docked most of the time to reduce battery wear.

I use a bluetooth keyboard for this, solves it quite handily.