

When the tribe which they’re appealing to is a death cult with a huge body count then that’s just being reasonable
Cryptography nerd
Fediverse accounts;
Natanael@slrpnk.net (main)
Natanael@infosec.pub
Natanael@lemmy.zip
Lemmy moderation account: @TrustedThirdParty@infosec.pub - !crypto@infosec.pub
Bluesky: natanael.bsky.social
When the tribe which they’re appealing to is a death cult with a huge body count then that’s just being reasonable
They made an attempt. It’s called Windows RT. It’s a sandbox more locked down than iOS.
The Win32 desktop environment isn’t built to support stuff like “timer coalescing” for all the API calls which all the software is designed to run continously in the background. Changing how it idles would change so many things which all kinds of software depends on that it would barely be the same OS anymore.
If you’ve already noticed incoming traffic is weird, you try to look for what distinguishes the sources you don’t want. You write rules looking at the behaviors like user agent, order of requests, IP ranges, etc, and put it in your web server and tells it to check if the incoming request matches the rules as a session starts.
Unless you’re a high value target for them, they won’t put endless resources into making their systems mimic regular clients. They might keep changing IP ranges, but that usually happens ~weekly and you can just check the logs and ban new ranges within minutes. Changing client behavior to blend in is harder at scale - bots simply won’t look for the same things as humans in the same ways, they’re too consistent, even when they try to be random they’re too consistently random.
When enough rules match, you throw in either a redirect or an internal URL rewrite rule for that session to point them to something different.
The trick is distinguishing them by behavior and switching what you serve them
“freeing up space on the user’s device”