ngrok

The arrest exposed that Microsoft keeps a Global Device Identifier for every Windows install and can correlate it with the IPs it used and the URLs it reached. What unsettled the thread is the scope, not the ID itself.

The sharpest question is which layer does this. A machine ID sitting on disk is normal; an OS vendor tying it to your live network activity is not. Nobody could say for sure whether it's Edge, Defender, or something lower in the stack.

An ngrok developer educator ported a slice of Kubernetes to TypeScript so a cluster runs entirely in the browser: pods, DNS, deployments, garbage collection, all client-side. LLMs wrote almost all of it, roughly 100,000 lines across 552 commits in two months.

His answer to the inevitable 'is this just slop?': read every line, plus 204 integration tests and 1,855 unit tests asserting it matches a real cluster via the official k8s client. An SRE in the thread noted the easy 80% is done; ConfigMaps, Secrets and Ingress are where the pain lives.