There's a subreddit called /r/vacsucks which is full of pro players blatantly cheating and getting away with it while the rest of the idiots think they're just good players.

Or, depending on your point of view, full of idiots flagging any player better than they are as cheating.

Aimbots can be "humanized" enough that any such determination becomes subjective.

The bare minimum so that I can use the device I bought as I wish, even if the manufacturer later decides to "alter the deal".

If you dare turn off Play Protect for example, you will be asked to turn it on every time you install or update anything. Never mind that you said no the last thousand times it asked.

You fix that by making root access inconvenient enough that companies can't rely on the average random user having it enabled.

For example force you to wipe the device to unlock it as another person said in another comment. Or make it so that if you don't unlock it within 7 days of the device purchase and first boot, you cannot unlock it anymore.

The problem though is that rooting by itself is not that useful when a lot of apps use remote attestation to deny you service if you're rooted.

We don't just need root access, we need undetectable root access.

Thanks to the efforts of Google to "simplify" smartphones the average young person now couldn't find and double-click a downloaded file if their life depended on it.

In the US, a manual car is considered an anti-theft device. In Europe, basically everyone that isn't obscenely rich has driven a manual car at some point.

People learn what they're expected to learn.

In Android phones for example you cannot screenshot banking apps. And if you root (modify the OS of) your phone, banking apps refuse to work.

If you modify it thanks to remote attestation you can no longer prove that it is unmodified using the TPM.

Expensive, yes, but at that point you're already spending real money on a second computer with a GPU to do computer vision on the game video stream, so...

This is obviously less relevant in America where you can still buy fast cars without being murdered by taxes.

- AI answers are grammatically correct and verbose so it looks like the poster put effort into it which deceives people into thinking the answers is more trustworthy than it is.

Barring trolls, humans (for the most part) only answer if they think they're right, and the more effort put into the answer the more likely they don't get it wrong.

    on_click() {
        if (last_one()) alert('You must keep at least one item selected.');
        else actually_toggle_it_off();
    }

    box = !cd ${GIT_PREFIX:-.} && git config --get remote.origin.url > .gitboxinfo && git rev-parse --abbrev-ref HEAD >> .gitboxinfo && git rev-parse HEAD >> .gitboxinfo && mv .git .gitbox && git add -f .gitboxinfo && true
    unbox = !cd ${GIT_PREFIX:-.} && mv .gitbox .git && true

If you ever need to regenerate the gitbox folder from scratch you can take a peek at the gitboxinfo file and git clone and reset the dependency repo in a temp folder, then move the git folder next to the gitboxinfo file.

Plus unlike submodules with this you can have local changes to the submodule files without having to fork the submodule itself.

Why this behavior is legal is beyond me. They do the same thing with Play Protect which I don't want to enable no matter how many times they ask.

You could for example make it so that phones could only be unlocked within a few days of the purchase (first boot) date, and put a scary warning on it. That'd put a stop to 99% of people being tricked into unlocking it.

You could also put a scary warning on boot that allowed anyone to tell it was rooted to stop people selling them while rooted.

The point of blocking rooted phones isn't "security", it's to maintain control of the user experience.

While it also serves as a security mechanism the most important benefit of memory protection is that it protects against processes *accidentally* corrupting other processes due to mistakes, invalid pointers, etc.

If you want to intentionally mess with other processes memory most OS give you the means to do it in a controlled way, with ptrace in Linux or WriteProcessMemory in Windows, because sometimes it is a useful thing to do.

The problem with Wayland is that they veto useful features they aren't interested in (that admittedly if misused could be a security problem or at least a nuisance) and they don't give any alternative way of doing them, choosing instead to punt the problem downstream to the compositors, who will each do them (or not) in a different way making the whole thing a mess.

You cannot, for example, move your own window in Wayland. If you have a multi-window application, like GIMP [1], you cannot have your application position its windows in a reasonable way.

[1]: https://gitlab.freedesktop.org/wayland/wayland-protocols/upl...