Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I tried making a chrome dev tools network throttling profile set to "0 kbps", and it seems to work...you get "no internet" if you try and reload the page, xhr in the console fails, etc. So cumbersome, but it does work.


>if you try and reload the page, xhr in the console fails, etc.

what about:

* DNS leaks (eg. trying to connect to payloadhere454098357987.attacker.example, leaks payloadhere454098357987 to the attacker)

* websocket

* webRTC

* prefetching

* service workers (background sync)

* beacons

* CSP reports


Sure, there is probably more needed. Some of your list is covered though. For example, I tried websockets, and those are blocked by the throttle.


I guess one may disable wifi+data if on mobile.

Disconnect wifi of on Desktop, but agree with OP there is no good way to check if processing is actually happening locally.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: