KyleSanderson

His takes on IBM were always interesting, especially during that turbulent time with Ginny. He is missed.

I've noticed a number of modem issues. I don't think this is actually related to network behavior. Pixels specifically when roaming up until the 9 had severe issues typically after 24 hours with full disconnects. The majority of users don't roam, and when they do they blame the network, but I'm becoming more inclined to believe this is an end-device issue.

Why did this get moderated off the front page.

Bit of both, if you're building from a service provider you now don't need v4 to push (OVH, Hetzner, etc.)

Less so than road warriors, who are typically CGNAT'd anyway.

Go for a run, hit the ski hill, all before you start work. The sun runs your health (circadian rhythm). I'm in Vancouver and this is the dumbest change. We're going to pay for this for a decade in premature deaths, and we'll end up on standard time anyway.

In his memoir, Gerstner described the turnaround as difficult and often wrenching for an IBM culture that had become insular and balkanized. After he arrived, over 100,000 employees were laid off from a company that had maintained a lifetime employment practice from its inception. Long allowed by their managers to believe that employment security had little reference to performance, thousands of IBM employees had grown lax, while the top-performing employees complained bitterly in attitude surveys. In the goal to create one common brand message for all IBM products and services around the world, under Gerstner's leadership the company consolidated its many advertising agencies down to just Ogilvy & Mather. Layoffs and other tough management measures continued in the first two years of his tenure, but the company was saved, and business success has continued to grow steadily since then.

There's a rewrite command now, it defrags and does all kinds of nice things for your array.

We're also introducing GoStringUngarbler, a command-line tool written in Python that automatically decrypts strings found in garble-obfuscated Go binaries.

The meeting was the animals who evolved to not be able to consume this, lived in more harsh conditions than those that had the readily available sugar. Evolution.

OpenWRT is pretty much the oldest still running (and popular) with UCI. There's the classic nvram ones, but those are hardly manageable manually.

It's still pretty slow, but overall correct. There's tricks, like reader connections and a single writer connection to reduce contention. There was a blog post on here detailing some speedups in general.

nice to see you around still :)

The implementation is just wrong from what's been presented. basic jitter (20-100ms), and a dynamic payload size are what's actually missing here. The question now becomes though how interactive should your session be. Timing the connection latency might help to an extent, but this is about mitm and you don't necessarily know where your adversary is (first hop, or towards the end). Batching keystrokes would also help here.