Comment Re:Wasn't there... (Score 1) 453
It was TWA 840. Not finding any references to the bomb being carried in a body cavity, but I remember hearing it in news reports at the time.
It was TWA 840. Not finding any references to the bomb being carried in a body cavity, but I remember hearing it in news reports at the time.
...a bomb in the 80s that was left aboard by a woman who snuck it on...um..."internally"?
Shameless plug follows...
Seriously, once you're free from having to remember your own passwords, you can make them as long and complex as you like, and you can use a different *truly random* password for every login, so one compromise won't lead to others. There are freeware workalikes, but none that match 1P's feature set (syncing, browser auto-fill/change plugins, etc). Highly recommended.
I'll point out that CGI rendered to film is done at 2,000 lines per frame - that's about twice the resolution of 1080p. So theatergoers would have noticed this as well.
That's why you run apache with mod_mono on a Linux box instead.
Came here to say exactly that. Done in one
Yes, you can configure a proxy server (squid, pound, varnish, etc) to cache SSL content. However, client browsers don't and won't.
I'm curious as to why this is - I'm guessing that it had been decided that if the data should be encrypted in transit, then it should not be saved unencrypted on the client's system.
You're talking about UCC certificates, and yes, they've been around for a while. The problem is browser adoption - there are still waaay too many people using IE6 out there.
Anyone know how to right-click-drag on a unibody Macbook Pro to get this to work? Double-tap doesn't seem to do the trick for me.
..."Apple is rumored to have an exclusive on this technology until 2012."
*shakes head* So much for wide support. Lots more people buy Mac then they used to, but 8 times as many people still buy PCs. Peripheral vendors aren't stupid.
I can't imagine how Macbook shipments would be affected, given the flaw only affected SATA ports beyond the first two. Presuming that SATA devices linked through Thunderbolt don't count either.
Kind of like running VMWare inside of another VMWare machine then?
Also, when that happens, it won't break the site completely, just cause a delay while the browser attempts to connect over IPv6, fails, then falls back to IPv4. That can take 10-30 seconds depending on the browser, however - far beyond most users' "the site is broken" thresholds.
That's the main reason Google, Facebook and Yahoo are all doing this on the same day - if only one site exhibits this issue, it's easy for a user to assume the problem is with that site. If multiple large sites are problematic, they'll call their ISP who will (hopefully) fix their IPv6 implementation, or (more likely) instruct the user on disabling IPv6 on their computers.
From what I've heard from internal Netflix IT folks, it's extremely dysfunctional in there, which may explain why it's easier for them to just cut a check and have someone else do it.
Now, if someone with IT competency were to purchase Netflix (Google? I mean, their job is to organize the world's information, and movie content *is* information), I'm sure you'd see a swift internal CDN roll out occur.
I've heard similar, along with some highly visible departures in their systems/network engineering groups rumored to be due to exactly those decisions.
Speaking of cutting checks, has anyone noticed that the movies.netflix.com site is actually hosted by Amazon AWS?
macbook:~$ host movies.netflix.com
movies.netflix.com is an alias for merchweb-frontend-1502974957.us-east-1.elb.amazonaws.com.
merchweb-frontend-1502974957.us-east-1.elb.amazonaws.com has address 204.236.218.69
This place just isn't big enough for all of us. We've got to find a way off this planet.
