You're presuming their decision to self insure was based on an actuarial assessment.
From my experience, it's also plausible that some poor schlep in the accounting department was tasked with looking into self insuring, and created a not-very-robust risk model. At AOL's size one would hope an actuary was involved, but that may not be the case.
As well, even if am actuary was involved, that doesn't stop upper management getting peeved when payouts are towards the upper bound of the model, as all they likely saw was the potential cost savings of the lower bound of the model, not the full risk.
The new bit is that you can now get local IPs. But that doesn't help someone trying to figure out if you're using a VPN.
The demo shows both my USA VPN IP address and my China Telecom IP address under "public addresses" (I strongly doubt this was possible before WebRTC). This means that Hulu, YouTube, Netflix etc. can now start blocking me even when I'm behind a VPN.
> Sailors and scientists needed to know the range and lethality of underwater nuclear explosions. Would they harm the crews, ships and planes delivering the weapons?
This reminded me of the Mark 45 nuclear torpedo exhibit at the USS Bowfin mueseum at Pearl Harbor. The targeting procedure was for the torpedo to be "aimed in the general direction and to the far side of the target, in order to place as much distance as possible between the submarine and the nuclear explosion." Yikes. See http://svsm.org/gallery/mk45/IMGP6756
TCP reorders segments just fine but it treats disordering as a congestion signal and slows down. That's why link aggregation frequently uses the technique of pinning flows to a single link- to minimize disordering so as to avoid triggering TCP congestion control.
In Linux, you can change the sensitivity to disordering by writing to /proc/sys/net/ipv4/tcp_reordering.
We sell a multi-connection VPN between customer premises and datacenter, managed by a behind-the-firewall web application. Our office overlooks the farms and mountains in Chilliwack, British Columbia. You’re far enough from Vancouver to avoid the congestion, but close enough to attend industry events.
We need a software developer who can handle the whole stack. You use BSD sockets in the morning and WebSockets after lunch. Your toolbox includes gdb, jsPerf.com, and everything in between. You’re at home with Less- both the pager and the stylesheet language. Your colleagues love you because your software is clear, cohesive, and unit tested, and your users adore you because your UIs are tested and proven effective. You know the meaning of CAP_NET_ADMIN and CSRF. Your apps run on a 10 year old machine with 256 MB of memory, then scale up to a 32 GB server built yesterday. We don’t care if you know our stack, because you learn quickly (and our training program doesn't hurt, either).