Hacker Newsnew | past | comments | ask | show | jobs | submit | ghxst's commentslogin

I think they released this in 2023 somewhere, it's been hidden behind an experiment in the devtools settings.

The absolute safest way to grab all traffic is capturing a netlog (https://www.chromium.org/developers/design-documents/network...) unfortunately there's been a lot of quirks with network captures through devtools and even with some of the recent bugfixes (https://issues.chromium.org/issues/40254754) they can still be lossy.

Tried a similar approach but found that putting the browser in a VM has a tendency to expose a few data points that stand out as less trust worthy which means you end up getting a lot of captchas on some websites (like using swiftshader for renderer, not having some fonts installed, among other things), lying about these can typically be detected as well (like injecting noise into a canvas, modifying the advertised renderer). If you've found any solutions to these please share.

What approach did you end up going with instead?

This is awesome


The hardware in the pictures of the NYT article don't resemble what I am familiar with when it comes to mobile data farming, they look like traditional sim equipment for texting.


I'd be surprised if you had no one around you that didn't have an old android laying around collecting dust. I'm still on an old A52s and it works fine.


i might, but i wouldn't want to rely on something i'm uncertain exists.


I usually hit robots.txt when I want to make fetch requests to a domain from the console without running into CORS or CSP issues. Since it's just a static file, there's no client-side code interfering, which makes it nice for testing. If you're hunting for vulnerabilities it's also worth probing (especially with crawler UAs), since it can leak hidden endpoints or framework-specific paths that devs didn't expect anyone to notice.


In my experience a good aimbot is impossible to tell from a normal player when you play ranked at a high competitive level, at least not with any degree of certainty that I think is worth banning people for. The cheaters you lose to at that level are the ones calling out your positions to their team because they can see you on the minimap while they aren't supposed to, things like that.


The DMA cheaters are caught when riot gets access to the vendors firmware and ban the people that are using it, not by the cheats themselves. Colorbots run on the same PC so these can be caught in various ways.


This article reads like it was written by an LLM and it doesn't mention how these "undetected" DMA cheats are actually caught. The anti-cheat teams join discords of vendors to get access to the cheats and flag users based on the heuristics they observe from the vendors firmware (that DMA card / hardware has to show up as _something_). So yeah, your setup can work (as long as you’re sticking to the drivers and input methods they tolerate), and the same goes for private DMA cheats.


Yes the hallmarks of llm is there.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: